Bizarre Device Problem

I just recently upgraded to Windows XP and i am suprised to say so far I am highly impressed.

Got 1 weird problem. XP thinks I have 2 SCSI/Raid controllers which have identical resource usage to my primary and secondary ata66 ide channels, and its playing havoc.

I cant get rid of the buggers so far, not even experimental regedit attempts have worked. Updating the IDE drivers doesnt work and trying to reassign them to a different driver fails too.

I'm normally very good with windows hardware but this ones got me.

Any Ideas?

 

Just curious....

CyberPunk... Go into the Device Manager,

While you are on this, click on the offending Disk Drive controllers the way that they are..
On this menu, Uninstall them... Comletely remove them..

NExt when you back out of this it is going to ask you to reboot..
This is where it gets fuzzy for me...
I've done this in lower version but not XP...
You can first off, let the system shut down, and reboot as it is definately going to. Then when it comes back up the finding driver hard ware wizard should take over, If it asks you for new drivers for the found item, great, tell it where to find the drivers.

If it does not.. Then redo this same way one more time, only after removing the drivers, don't let windows reboot, just go ahead and MANUALLY FIND NEW HARDWARE point it to your drivers...
Afterwards reboot..

Now then IF that does not work, last resort. go to the SCSI controller in the System manager look up wehre the Drivers are, try to figure out WHAT INF drivers those are. And remove those from where it will look. Then try removign the drivers and manually reinstalling then rebooting.
best of luck to you, adn let me know how it works....

 

With you

Already tried everything you list, but theres no uninstall for them, thats where the trouble starts....

The problem is tied in with the via storage drivers for my chipset, deleting the files is just about last resort, hadnt thought of that one although I ought to have (embarrased h/w tech hangs head in embarrasment).

going to have a crack just now, you'll know the results if I dont come back to this post tonight

 

Windows XP

In the Device Manager, when you click on an item of hardware
Then go for properties, one of the further options is resources, and drivers details...
This gives you a listing of ALL associated drivers that are associated with that particualr piece of hardware.

Let me know how you make out....

 

Bluescreen!

Wiped the files in question, utterly destroyed the ability to boot xp in any config, ouch. But I found a way to repair/reinstall salvaging everything but a couple of device driver settings without using the useless repair console.

Forget the crappy xp startup disks.

Boot using a win98 boot disk. Go to your i386 files directory. (My setup files are on the hdd under C:\xp - basically the root cd files plus the i386 dir). Go to the i386 dir and run winnt.exe - initiate an install and it will prompt you for location of the install files with in my case c:\xp\i386 - follow it through to the point where you can choose to upgrade/clean install and somewhere about there your should get a repair option for existing, choose it and it will initiate the latter part of the install process for setting up xp and hey presto youre back in!

The advantages of using install files copied to the hdd is you will never be bugged for the i386 dir on the install cd

Plus, those annoying raid/scsi drivers are gone

 

Same as mine

cyberpunk, I have been installing Winodws OS's for a bunch of years now, just exactly like that.

Then when it normally asks you for a disk, it does not ask, it just goes to get what it needs, and does not ask you for anything, unless it is new drivers that your trying to install of course...

 

cyberpunk

Which part of the UK are you from .. because I know a cyberpunk from England as well.

 

I'm in NE Scotland

Sorry, not the same one.

By the way, anyone got any ideas on this.

Since the repair of XP shutdown icon has turned into restart!

Havent figured out how to sort it yet.