L.D wrote:
>Now that I'm back from my extended vacation in Washington DC area, I'm
>catching up on mail. [Can you say 2,000??]
Jikes, and the list seems to be getting more and mroe active lately - and
I'm going away soon for 9 days so I'll have some 400-500 mails to read when
I get back, not close to what you have but still more than I would want...
(but it's fun to see the list so active).
>Read what you wanted me to try on smartdrv and figured why not.
Thank you.
>Then I went to config.sys to make the actual change. Discovered I don't
>*have* to do that.
No please do...
>I can now say, with the ultimate level of assurance, that Smartdrv.Exe
>is *NOT* the cause of lost chains.
I never said it was - I said that it was the cure.
>How can I be so certain? Well, it
>seems I'd modified my config.sys back on April 23rd, said modification
>consisting of the command REM being placed in front of the device line
>for smartdrv. Yup ... I've been running Arachne 1.61 & now 1.64
>*without* any diskcaching, but the lost chains are still there.
That doesn't matter, this goes deeper - to a conflict between HD and DOS. I
would also suggest that others that have problem with lost clusters
(Michael for instance) atleast try and do this.
>Just to make you happy, and to speed up things on this end [maybe], I'll
>go into config.sys and unREM the smartdrv line, adding the double-buffer
>command. Betcha I still get lost chains. <G>
If you do you have prooven M$ wrong, and that's always fun isn't it? ;-)
//Bernie
http://bernie.arachne.cz/ DOS programs, Star Wars ...
