On 8/10/07, Erik Osterholm <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 09, 2007 at 06:02:54PM -0400, Jerry McAllister wrote:
> > On Thu, Aug 09, 2007 at 08:25:17PM +, V.I.Victor wrote:
> >
> > >
> > > It sure seems that this should be simple, but my searches have only
> > > turned up inter-active
On Thu, Aug 09, 2007 at 06:02:54PM -0400, Jerry McAllister wrote:
> On Thu, Aug 09, 2007 at 08:25:17PM +, V.I.Victor wrote:
>
> >
> > It sure seems that this should be simple, but my searches have only
> > turned up inter-active hex/disk editors. I'm probably "asking" wrong.
> >
> > I have
On Thu, Aug 09, 2007 at 08:25:17PM +, V.I.Victor wrote:
>
> It sure seems that this should be simple, but my searches have only
> turned up inter-active hex/disk editors. I'm probably "asking" wrong.
>
> I have a large binary file (>700 meg) and I know that there is a
> single wrong byte.
On Thu, 09 Aug 2007 20:25:17 +
"V.I.Victor" <[EMAIL PROTECTED]> wrote:
> It sure seems that this should be simple, but my searches have only
> turned up inter-active hex/disk editors. I'm probably "asking" wrong.
>
> I have a large binary file (>700 meg) and I know that there is a
> single w
It sure seems that this should be simple, but my searches have only turned up
inter-active hex/disk editors. I'm probably "asking" wrong.
I have a large binary file (>700 meg) and I know that there is a single wrong
byte. I also know it's exact location in the file.
Is there a command-line u