"R.Wieser" <address@[EMAIL PROTECTED]
> wrote in message
news:44cfc2c5$1$4526$e4fe514c@[EMAIL PROTECTED]
> Rod Pemberton <do_not_have@[EMAIL PROTECTED]
> schreef in berichtnieuws
> eanldc$299b$1@[EMAIL PROTECTED]
>
> Hello Rod,
>
> <snip>
>
> > > So, I'm looking for a(n electronic copy of the) users-manual. If
you
> > > have one or know where to find one I would appriciate the
information.
> >
> > Nope.
>
> Too bad, I could really use one.
>
A couple Yahoo searches pulled up this:
http://www.filesearching.com/cgi-bin/s?t=n&l=en&q=ftp.elektra.ru/pub/OtherSoft/C_ASM/BORLAND
They appear to be valid, but run them through your virus checker anyway...
You might also want to try a P2P network..."valuable" old software tends
to
collect on them.
> > Hey, did you ever find a solution for that network filesystem you
> > were writing? What was it....uh, something with findfirst/findnext...
>
> Correct. The answer is Yes, and No. Yes, I think I have found a method
to
> solve the not-closing of a communication-socket because a DOS
> find-first/next sequence does not know a find-close. The idea is to
regard
> any find-first or -next as a seperate action, using the index stored in
the
> DTA to signal to the other side which entry it needs to return.
>
> Ofcourse, that could lead to problems when files get deleted or added to
> that directory at the same time (files being skipped or appearing twice,
> something I have not found a solution for) ...
>
> And No, I have not implemented it yet : my intrest was pulled into
another
> direction.
>
Yeah, I've got too many projects going on too!
I'm not sure if I posted these. First is some stuff on SDA. Second is
"network" ramdisk.
http://groups.google.com/group/comp.os.msdos.programmer/msg/f90a923e093a6254?hl=en
http://groups.google.com/group/comp.os.msdos.programmer/msg/36b34f208807076b?hl=en
Ted Davis' original idea of calling findnext repeatedly when findfirst is
called and caching the results locally, may be the only solution...
Rod Pemberton
|
