Clean Boot?

"Jim" wrote in message
...

I am not a gamer. I don't know. This is a bit like a dosgame though.

The USB 2.0 needs a floppy that is dos and it is UHCI driver with some
other
component software for Active@ Disk-Image.net program.

Beware . . .
1. What your USB devices need is drivers i.e. OS files.
These files may be stored on a floppy and that floppy
may conveniently formatted for DOS but no USB device.
"needs a floppy that is dos."
2. Device drivers are hardware-specific. You may have
difficulty making a particular program run from a particular
device, but no USB drivers are specific for any particular program.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

These are good points, and it is exactly where I am stuck.
The drivers and some app.exe have made the USB device program specific for
that disk image program. I copied over to a EBD [Emergency Boot Diskette]
the driver aspiUHCI.sys and let the program have access to the driver, but
still not working. I also thought that MS win98se upgrade cd would have this
type of driver, but it does not. This is circa 2002 USB 2.0 hi-speed drivers
15-480 MB/sec ...
"Don Phillipson" wrote in message
...
"Jim" wrote in message
...

I am not a gamer. I don't know. This is a bit like a dosgame though.

The USB 2.0 needs a floppy that is dos and it is UHCI driver with some
other
component software for Active@ Disk-Image.net program.

Beware . . .
1. What your USB devices need is drivers i.e. OS files.
These files may be stored on a floppy and that floppy
may conveniently formatted for DOS but no USB device.
"needs a floppy that is dos."
2. Device drivers are hardware-specific. You may have
difficulty making a particular program run from a particular
device, but no USB drivers are specific for any particular program.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

In order to use a USB device from a DOS boot you need to have drivers for
the USB as well as drivers for the device. Getting those drivers setup up
for an EBD requires that the drivers are on the floppy and that they are
correctly referenced from CONFIG.SYS and (possibly) AUTOEXEC.BAT. If the
EBD you are using creates a RAM disk (because the startup files are too
large to fit on a floppy) then configuring the whole disk correctly is quite
difficult, and I would avoid it if possible.

I don't entirely understand your problem, but I do not believe it will be
useful to set up with an EBD disk with drivers for that device. It seems
more likely that you will get it to work under Windows using a simplified
Windows setup and installing the device drivers as provided by the
application supplier. A clean boot startup might be helpful for diagnostic
purposes, but you will need to know how your USB drivers and the drivers for
that USB device are installed and set up within Windows in order to know
what is OK to disable and what's not. It is unlikely that completely
disabling CONFIG.SYS and AUTOEXEC.BAT will prevent USB and the device
working, but if the device is specially configured to work with that
software only then anything is possible.

(It's quite possible that the device is provided with a custom driver that
works for that software only - this is common where hardware manufacturers
believe they can improve performance by creating a custom interface, or
possibly for security reasons. In that case the supplier should have
detailed instructions for installing and using the driver in all
circumstances - Windows, DOS boot, etc. There may be other drivers that
allow general access to the device, but if I understand the problem
correctly that's not important for now.)

Note that Windows 98 (original or upgrade) couldn't possibly have the
correct drivers for a device created in 2002 unless that device was
carefully designed to conform to a standard that was in use in 1998. Even
if that was the case, it's likely that W98 would not recognise the device
type and would not be able to find matching default drivers, even if they
existed.

Much sharing of an IRQ isn't a problem provided that all devices are
working. You should uninstall devices that you don't need for the present
task or which aren't working properly. If you can't uninstall them for
some reason, at least diable them.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Jim" wrote in message
...
These are good points, and it is exactly where I am stuck.
The drivers and some app.exe have made the USB device program specific for
that disk image program. I copied over to a EBD [Emergency Boot Diskette]
the driver aspiUHCI.sys and let the program have access to the driver, but
still not working. I also thought that MS win98se upgrade cd would have
this
type of driver, but it does not. This is circa 2002 USB 2.0 hi-speed
drivers
15-480 MB/sec ...
"Don Phillipson" wrote in message
...
"Jim" wrote in message
...

I am not a gamer. I don't know. This is a bit like a dosgame though.

The USB 2.0 needs a floppy that is dos and it is UHCI driver with some
other
component software for Active@ Disk-Image.net program.

Beware . . .
1. What your USB devices need is drivers i.e. OS files.
These files may be stored on a floppy and that floppy
may conveniently formatted for DOS but no USB device.
"needs a floppy that is dos."
2. Device drivers are hardware-specific. You may have
difficulty making a particular program run from a particular
device, but no USB drivers are specific for any particular program.

I will give that windows simplified setup approach a try. ( I believe that
this is a custom software write [floppy] and although the EBD says it only
needs the driver and configuration to autoexec they do need the correct
reference and syntax to work.)
"Jeff Richards" wrote in message
...
In order to use a USB device from a DOS boot you need to have drivers for
the USB as well as drivers for the device. Getting those drivers setup up
for an EBD requires that the drivers are on the floppy and that they are
correctly referenced from CONFIG.SYS and (possibly) AUTOEXEC.BAT. If the
EBD you are using creates a RAM disk (because the startup files are too
large to fit on a floppy) then configuring the whole disk correctly is
quite
difficult, and I would avoid it if possible.

I don't entirely understand your problem, but I do not believe it will be
useful to set up with an EBD disk with drivers for that device. It seems
more likely that you will get it to work under Windows using a simplified
Windows setup and installing the device drivers as provided by the
application supplier. A clean boot startup might be helpful for
diagnostic
purposes, but you will need to know how your USB drivers and the drivers
for
that USB device are installed and set up within Windows in order to know
what is OK to disable and what's not. It is unlikely that completely
disabling CONFIG.SYS and AUTOEXEC.BAT will prevent USB and the device
working, but if the device is specially configured to work with that
software only then anything is possible.

(It's quite possible that the device is provided with a custom driver that
works for that software only - this is common where hardware manufacturers
believe they can improve performance by creating a custom interface, or
possibly for security reasons. In that case the supplier should have
detailed instructions for installing and using the driver in all
circumstances - Windows, DOS boot, etc. There may be other drivers that
allow general access to the device, but if I understand the problem
correctly that's not important for now.)

Note that Windows 98 (original or upgrade) couldn't possibly have the
correct drivers for a device created in 2002 unless that device was
carefully designed to conform to a standard that was in use in 1998. Even
if that was the case, it's likely that W98 would not recognise the device
type and would not be able to find matching default drivers, even if they
existed.

Much sharing of an IRQ isn't a problem provided that all devices are
working. You should uninstall devices that you don't need for the present
task or which aren't working properly. If you can't uninstall them for
some reason, at least diable them.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Jim" wrote in message
...
These are good points, and it is exactly where I am stuck.
The drivers and some app.exe have made the USB device program specific
for
that disk image program. I copied over to a EBD [Emergency Boot
Diskette]
the driver aspiUHCI.sys and let the program have access to the driver,
but
still not working. I also thought that MS win98se upgrade cd would have
this
type of driver, but it does not. This is circa 2002 USB 2.0 hi-speed
drivers
15-480 MB/sec ...
"Don Phillipson" wrote in message
...
"Jim" wrote in message
...

I am not a gamer. I don't know. This is a bit like a dosgame though.

The USB 2.0 needs a floppy that is dos and it is UHCI driver with
some
other
component software for Active@ Disk-Image.net program.

Beware . . .
1. What your USB devices need is drivers i.e. OS files.
These files may be stored on a floppy and that floppy
may conveniently formatted for DOS but no USB device.
"needs a floppy that is dos."
2. Device drivers are hardware-specific. You may have
difficulty making a particular program run from a particular
device, but no USB drivers are specific for any particular program.