R
Ray
My Win2K can't handle hardware changes all lot.
1. Adding a USB memory stick pops up the new hardware found wizard and
there is no way to bypass that. On other Win2K installs, the memory
stick will mount itself without a problem.
2. A while ago, my CD-writer was broken. The replacement (another make
and type) asked for a driver via the new hardware found wizard. Had to
reinstall the
Nero to solve this (does Nero install a CD-writer driver?).
3. Recently I replaced an ATAPI ZIP disk with an additional 20 GB IDE
harddisk and same happens: new hardware wizard comes in and does not
leave me anymore. I guess it already has a suitable drive for
harddisks.
4. Then I tried to swap the IDE assignment (slave/master) of the
CD-writer and the additional harddisk. Now I have 2 devices begging
for a driver via the new hardware found wizard: the CD-writer and the
additional harddisk.
Apperently, Win2K has some mechanism that determines whether a device
requires a new driver, or to consider it as new hardware. Is there any
way to stop that mechanism? Any help on this issue is appreciated?
Thanks,
Ray
1. Adding a USB memory stick pops up the new hardware found wizard and
there is no way to bypass that. On other Win2K installs, the memory
stick will mount itself without a problem.
2. A while ago, my CD-writer was broken. The replacement (another make
and type) asked for a driver via the new hardware found wizard. Had to
reinstall the
Nero to solve this (does Nero install a CD-writer driver?).
3. Recently I replaced an ATAPI ZIP disk with an additional 20 GB IDE
harddisk and same happens: new hardware wizard comes in and does not
leave me anymore. I guess it already has a suitable drive for
harddisks.
4. Then I tried to swap the IDE assignment (slave/master) of the
CD-writer and the additional harddisk. Now I have 2 devices begging
for a driver via the new hardware found wizard: the CD-writer and the
additional harddisk.
Apperently, Win2K has some mechanism that determines whether a device
requires a new driver, or to consider it as new hardware. Is there any
way to stop that mechanism? Any help on this issue is appreciated?
Thanks,
Ray