Re: DOS 6.22, DESQview386, QEMM 7.5 and USB Floppy on a Dell 745
- From: buck <buck@xxxxxxxxxxx>
- Date: Wed, 05 Sep 2007 13:37:36 -0700
On Wed, 5 Sep 2007 15:43:51 -0400, "Dave R." <dwragle at drbsystems
dot com> wrote:
Since it appears that no one has posted anything here other than test
posts for some time now, this may be futile, but it is at least worth a
try I suppose. :-)
Anyhow. I have a new Dell Optiplex 745 that uses a USB floppy drive
instead of a "legacy" floppy port. I need to be able to use this floppy
drive in DOS (6.22) under DESQview. It appears that in some ways the
Dell folks have the USB thing pretty well figured out as I can actually
boot to DOS from the USB floppy, and can access the floppy in DOS if I
boot to DOS from the hard drive without loading QEMM386 in config.sys.
However, as soon as I load QEMM386 with the RAM parameter, I lose the
ability to access the USB floppy. The system hangs if I try to pull a
directory from the USB floppy, try to copy a file to or from the USB
floppy, etc. Depending on the other QEMM386 parameters in use, the hang
varies from hard (have to hold the power button for 4 seconds to power
down) to soft (simply pressing the power button works).
I've found that if I exclude all available memory regions that QEMM386
wants to use as High RAM, the system doesn't hang when I access the USB
floppy. For example:
DEVICE=QEMM386.SYS RAM X=B000-B7FF X=D000-DFFF
This works and allows me to access the USB floppy, but of course then I
don't have any high memory I can use.
Looking at the memory with Manifest shows that A000-AFFF and B800-BFFF
are Video, C000-CFFF and F000-FFFF are ROM and E000-EFFF is Page Frame.
If I then allow ANY section of memory to be mapped as High RAM, I'm back
to square one. For example:
DEVICE=QEMM386.SYS RAM X=B100-B7FF X=D000-DFFF
DEVICE=QEMM386.SYS RAM X=B000-B6FF X=D000-DFFF
DEVICE=QEMM386.SYS RAM X=B000-B7FF X=D100-DFFF
DEVICE=QEMM386.SYS RAM X=B000-B7FF X=D000-DEFF
All cause a system hang when I access the USB floppy. In the past, when
I've had conflicts or other problems with QEMM/DESQview, I've always
been able to identify which region of memory is causing my problem, but
this one has me stumped.
I really need to get this working if at all possible. Any help will be
much appreciated.
Regards,
Dave
I rather doubt that this will help, but here's what I would do:
config.sys
DEVICE=QEMM386.SYS ON
autoexec.bat
DIR A:
Obviously,. you need a diskette with something on it in A:
Look in MFT to see if you see accesses to any high memory area after
booting that, and exclude all such areas. Reboot and run OPTIMIZE
(and pray).
You will almost certainly be better served to use a normal floppy
drive. Since QEMM was long before USB there isn't a lot of chance
that you can make this work, and the cost of the floppy drive,
controller and cable is worth a lot less than your sanity.
--
buck
.
- Follow-Ups:
- References:
- Prev by Date: DOS 6.22, DESQview386, QEMM 7.5 and USB Floppy on a Dell 745
- Next by Date: Re: DOS 6.22, DESQview386, QEMM 7.5 and USB Floppy on a Dell 745
- Previous by thread: DOS 6.22, DESQview386, QEMM 7.5 and USB Floppy on a Dell 745
- Next by thread: Re: DOS 6.22, DESQview386, QEMM 7.5 and USB Floppy on a Dell 745
- Index(es):
Relevant Pages
|
