Re: Word Processor format?

[stockhunt10 <stockhunt10@gmail.com>]

On Jul 30, 1:49 pm, schmidtd <schmi...@my-deja.com> wrote:
> On Jul 29, 3:44 pm, "Bill Garber" <willy4...@comcast.net> wrote:
>
> > "schmidtd" <schmi...@my-deja.com> wrote in message
>
> >bd45fa58-ba8a-4fd4-af74-6b460b49b165@25g2000hsx.googlegroups.com">news:bd45fa58-ba8a-4fd4-af74-6b460b49b165@25g2000hsx.googlegroups.com...
>
> > > I've got some DOS disks with files written with an unknown word
> > > processor.  Looking at the disks in CiderPress after transfer, all
> > > files have a filetype of $f3, auxtype of $0000, and a "size" of
> > > 156160.  (Which is laughable, since all the files on a disk have that
> > > same size.)
>
> > > Line breaks seem to have the sequence $00 $40 $03.  The beginning of
> > > files seem to be the sequence $40 $03 $02, and the end-of-file seems
> > > to be the sequence $00 $41 $01 $06.  Looking at a few more files, I
> > > could probably pinpoint the sequence a little better.  But does any of
> > > this start ringing any bells with anyone?
>
> > Could you send me a couple images to look at?
>
> Thanks much for the offer, Bill!  As it happens, the data's not mine,
> so I can't do that just yet.  I've reduced the file filter to a few
> sed rules - lop off the high bit, delete all $00, transform those $40
> contraptions to newlines, terminate the file after seeing $41 $01
> $06.  My only problem now... sed really, really likes $0a.  I really,
> really need it to treat $0a like any other byte.  I was hoping to
> avoid going to a higher level language, but may have to bite the
> bullet.

Check out Stockhunt.com, turn $150 into $1,000,000.
It works for Jim Cramer why wont it work for.
Sign up now!
http://www.stockhunt.com/news-letter.aspx