Turn off "Found New Hardware"?

  • Thread starter Thread starter Martin
  • Start date Start date
M

Martin

I have a NetVista running WinXP. I just installed a second hard drive
(as a slave) and have installed Linux on it. A dual-boot utility
allows me to run either OS.

When I boot to Windows, it launches the "Found New Hardware" wizard
and tries to install the added drive. It then encounters an error
condition that says, "One of the filter drivers installed for this
device is invalid". I click my way out of that and everything is fine.

Even if it didn't encounter the error, I would not expect Windows to
be able to recognize this drive - after all, it's a Linux drive.
(FWIW, when running in Linux, as far as I can tell, the Windows drive
is not recognized).

Can someone suggest some way that I can tell Windows to just ignore
the Linux drive altogether? Or, alternatively, to get past the error
condition, install the drive and be done with it?

Thanks
 
-----Original Message-----
I have a NetVista running WinXP. I just installed a second hard drive
(as a slave) and have installed Linux on it. A dual-boot utility
allows me to run either OS.

When I boot to Windows, it launches the "Found New Hardware" wizard
and tries to install the added drive. It then encounters an error
condition that says, "One of the filter drivers installed for this
device is invalid". I click my way out of that and everything is fine.

Even if it didn't encounter the error, I would not expect Windows to
be able to recognize this drive - after all, it's a Linux drive.
(FWIW, when running in Linux, as far as I can tell, the Windows drive
is not recognized).

Can someone suggest some way that I can tell Windows to just ignore
the Linux drive altogether? Or, alternatively, to get past the error
condition, install the drive and be done with it?

Thanks

.
Are you booting with the Grub boot loader or Winxp?
Click to expand...
 
Are you by any chance using LIBRANET or a variation.
This happens.
Click to expand...

I don't know what that is but apparently I'm not using it because
there is no such file by that name on the computer.

I am a total newbie as far as Linux is concerned. I posted my question
here assuming that the situation was related to Windows XP.
 
I got this resolved. Thought I'd post it here in case someone else
runs into this same situation.

It turns out that the problem was caused by some kind of interference
with the CDRom drive's DLA utility. An IBM NetVista computer with a
RW-CD drive has an IBM-supplied program (DLA) that, I thought, was
required to enable writing to a CD. Apparently, this is not the case.
By un-installing the DLA program, the computer was able to recognize
the 2nd hard drive and all is well now.

It's my understanding that Windows XP has some kind of native,
built-in ability to write to the CD. I haven't tried it yet. We'll
see..
 
Back
Top