Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
When I load usbaspi.sys and di1000dd.sys under Win98 DOS (from CD drive), my 8GB cruzer mini becomes functional but the keyboard stops responding - no further input possible on my Toshiba Notebook. Anybody know why or how to keep it active?

In CONFIG.SYS put the two lines for the USB.. first prior to any other TSR's etcetc
device=usbaspi.sys /w/v
device=di1000dd.sysThe USBASPI should be Panasonic version 2.2x or later
The Di1000DD should be Novac version 2.xx or laterThough if you are using an USB Optical Drive, basic BIOS USB support is loaded and may be conflicting..

I have config.sys entries added (at the bottom) as follows:
device=usbaspi.sys /v/w/norst
device=di1000dd.sys /dmDrive m: becomes enabled to the flash drive. But the keyboard is dead. Will try moving them to the top.
Regarding versions: I have been able to find versions 2.06 & 2.15 (usbaspi). The Novac di1000dd.sys is dated 08/16/2001 (not sure of version, extracted from hd352u_dos.zip). Have tried to find the most recent versions I could. Have found some of the link references posted are no longer functional and require a little tweaking (on the Novac site in particular) to locate the download pages. Any updated links to the latest downloads would be much appreciated.
Still don't know why the keyboard goes south. Is this a known side affect or is my case an anomaly?

No USB Bootable Bios. When I asked, Phoenix eSupport responded with "while a newer version of bios is available i do not thing that it includes boot from USB.". Seems to me like a no-brainer to include this on any new versions. But maybe it's not really new, just the newest for my model.

Further test results confirming that the keyboard is being stopped:
I tried F8 on boot and confirmed each config.sys line execution. After usbaspi.sys is finished scanning the di1000dd.sys line is offered for confirmation. But the keyboard has stopped responding at this exact point. So, usbaspi.sys is definitively causing the keyboard outage. On normal boot (without F8) di1000dd.sys is processed fine and the flash drive found and assigned the m: drive as specified (/dm).
I had removed the /norst from an earlier setup. Could some keyboard bios setting be reset by usbaspi.sys? I'm perplexed...

Sounds like a IRQ/Memory Address conflict, maybe time to use Linux ??? Lets face it MS-DOS is well past its sell-by-date...

![]() |
RAM upgradation
|
OPEN A PROGRAM IN DOS Ve...
|
| Login or Register to Reply | |
| Login | Register |
| Ads by Google |