OK, back to the Smartdrv wars ...
I went to 6.22 HELP and read what it said about which drives might need
double buffering; it seemed clear my drive controller was *not* the
problem, particularly since "smartdrv" at the prompt produced "no" for
buffering on all drives [including the CDROM], and both drives had
clearly operated correctly with an emm386 handler [qemm386] prviously.
But I went ahead and reconfigured, moving device smartdrv to prior to
device emm386, adding the double buffer switch, and then adding smartdrv
to autoexec ... reboot and do all the checks detailed in "notes" to see
if double_buffering is required.
As I could have told you right from the beginning, my SCSI Host
Controller is more than adequate to the task [it's the controller not
the drive that counts] of living with upper and extended memory.
Remember I run QEMM in every config except the one with the NIC, and
have with Arachne forever.
But I went ahead and did the mem/c thing, and yes I'm using upper
memory. And I did the "smartdrv at the prompt" thing, and yes -- each
and every drive shows "no" for "no double buffering needed" ...
That should remove the factor of "It must be the SCSI drive causing the
problems with Arachne" from the formula, right?
Now, if you'll excuse me, I want to go back and set up my config &
autoexec so speed comes back and caching is done to my specs.
l.d.
====
On Wed, 26 Jul 2000 09:11:52 +0200 (MET DST), Bernie <[EMAIL PROTECTED]>
wrote:
> I didn't say smartdrv.exe/help I said "help smartdrv.exe" - that help is
> diffrent from what "help smartdrv" gives and therefor the two have nothing
> in common (and both are more detailed than smartdrv/help).
> Please try and get a smartdrv.exe into your system (with perhaps
> setver.exe) and add the following to config.sys:
> devicehigh=c:\dos\smartdrv.exe/double_buffer
> You can still use whatever hard drive caching program you want (or none if
> you want that) just please can't you try this, it will probably take you
> far less time to do it then it took me to respond to this mail anyway...
