Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
---------------------
The Two USB Devices:#1. An external enclosure(USB2) with an IDE NEC ND3500A(G) DVD burner inside.
#2. A 9in1 Generic card reader with a 32MB MMCard inserted
-------------
The Goings On:DOS loads fine and all seems to go well.
Both devices are detected, NEC blahbalh with ID=0... 32MB blah with ID=2...
When detecting USB, loading drivers and assigning the devices letters(ID=2 is E:\ and ID=0 is MSCDEX'dwith other drives and given I:\) etc :)
...I'm returned to the command prompt...
But, I can't do anything useful with the PS2 keyboard! :0 But :( the blinky cursor thingy blinks happily
The DOS USB had done it's part but couldn't give keyboard control after aspiohci.sys loaded. What happenedthere??
Also, the keyboard can interrupt the loading and detecting of USB process and halt the system instantly!
So close but-> DENIED!
------------------------
The Dumb Question Time:Must be a compatability and driver issue or???
I'm assuming the devices are OHCI, how can I tell?
What if I had a USB keyboard and the DOS drivers too, would this still happen?---------------
The SpecsASUS P4S800
PIV 3.0-HT
DDR PC3200 1024MB---------------
THE CONFIG.SYS:device=oakcdrom.sys /D:mscd001
devicehigh=aspiohci.sys /INT /ALL
devicehigh=DI1000DD.SYS /H1
devicehigh=ASPICD.SYS /D:USBCD001 /ID=0-------------
THE AUTOEXEC.BAT:MSCDEX.EXE /D:MSCD001 /D:USBCD001 /L:%CDROM% /M:12

I guess there's more to your autoexec than that, but I don't think you need this:
/D:USBCD001
TWICE
And since you're using:
/L:%CDROM%
I guess you're using that goofy FINDCD which is part of a 98 startup disk.
I just use:
/L:R
If the var
%CDROM%
is not set, your line will have:
/D:
Which can't be a good thing.
*****
HTHM2

Sry bout the unedited post...
Anyway, I forgot this part too[COMMON]
device=himem.sys /testm:off
files=40
buffers=40
dos=high,umb
stacks=9,256
devicehigh=ramdrive.sys /E 2048
lastdrive=z

Thanx Mechanix
/L:R didn't work at first, as I remember, but then I'll try again cause %CDROM% repeats in twice in autoexec.bat as I've found out.
It is a win98 disk. -> FINDCD?? How about SMARTDRV.exe.
thx

All to no avail. The /L:R does its job, I've disposed of all the garbo and tidied the necessities. I've trimmed and dosey-doed with this but fall short of the successes with USB in DOS functionality... It does the same ole freeze thing.
It might be the controller program that has issues. Are there newer programs released?
I've tried USBASPI.SYS and ASPIOHCI.SYS.
Is DUSE worth the while?

------------
THE BARE MINIMUM - I've tried config by itself[CONFIG.SYS]
devicehigh=aspiohci.sys /INT /ALL
devicehigh=DI1000DD.SYS /H1
devicehigh=ASPICD.SYS /D:USBCD001 /ID=0
files=40
buffers=40
dos=high,umb
stacks=9,256
lastdrive=z----------------
THE OTHER MINIMUM - With HIMEM and MSCDEX[CONFIG.SYS]
device=himem.sys /testm:off
devicehigh=aspiohci.sys /INT /ALL
devicehigh=DI1000DD.SYS /H1
devicehigh=ASPICD.SYS /D:USBCD001 /ID=0
files=40
buffers=40
dos=high,umb
stacks=9,256
lastdrive=z[AUTOEXEC.BAT] <--- with and without
MSCDEX.EXE /D:USBCD001thx Mechanix

I'd assume that ID=0 is assigned by the ASPIOHCI.SYS controller, as so to IDentify each unique device detected in a user friendly fashion; ID=0, ID=1, ID=2 etc.
This can be helpful with configuration parameters i.e. In CONFIG.SYS driver assignment.What is used to detect the USB-CD/DVD(The NEC ND3500A(G)DVD-RW)is the ASPICD.SYS driver.
So, the ID tag is use as an argument when initiating the driver in CONFIG.SYS:devicehigh=ASPICD.SYS /D:USBCD001 /ID=0
As far as I know, ASPICD.SYS, supports the ID=? tag.
And, of course, the '/D:USBCD001' spec is sent off to MSCDEX for execution in AUTOEXEC.EXE, as discussed earlier.These ASPI drivers seem to do a better job than any else when used with the specific devices that are attached to the USB ports.
Maybe I should check out a few settings in the BIOS. The PS2 keyboard freezes, so maybe the IRQ is hijacked somehow??

![]() |
Java Thread Explanantion
|
'Spaces' in strings
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |