#drive mapping
3 messages in this thread
Mike,
As far as I can tell there is no relation between the buffers in the device
driver and those in MSCDEX. Since I have the luxury of 20Mb I give 64 to both
<g>. In my case the Mitsumi driver uses XMS, while MSCDEX uses EMS, but there's
no effective difference (and yes you're right, /E takes no arguments and can go
anywhere).
The Mitsumi docs suggest, without actually saying it, that it's better to give
more space to the driver in preference to MSCDEX, which intuitively makes sense
since the driver _may_ be able to read-aheads (I have no idea if it does in
fact).
It's possible the software is going straight to the driver using IOCTL calls,
but I really doubt it's going lower than that. Just out of idle curiosity what
do you get if you do
TRUENAME \\g.\a.
In case you've not seen this, this is an undocumented COMMAND.COM command which
fully expands a path name. Try TRUENAME C: and you'll get the current directory
on C: for example.
I tried \\z.\a. (Z: is my CDROM drive letter) and got back the same, IOW DOS
didn't recognise it, maybe something on your system does.
Robin
I tried the TRUENAME thing and just got back what I put in (\\G.\A.).
BUT, I fixed my problem. This program uses path\filename resolution and has a
documented switch (/NORES) to shut that off. Once I added that switch my
problem was gone.
Thanks for the info on the switches. I'll play with the buffer settings and
see what I come up with.
mike
Mike,
Can't say I understand _what_ got fixed, but glad to hear it _did_ get fixed
<g>.
Robin