Win XP Pro installation and HPT366 conflict

[ChurchOfSubgenius]

I am doing some remote tech for my dad who is trying to install WinXP Pro- upgrading from Win98, he has a Soyo BA+ IV with the onboard Highpoint HPT366 controller and it's giving him a conflict report when he starts up install, there are WinXP HPT366 drivers on the Soyo site but it won't let him install it to load them.

Any ideas?

 

[LiLithTecH]

Is he trying to load the drivers at the Install by Pressing F6 (To install third-party SCSI and host controller drivers)
when the "Setup is loading" screen appears?

 

[ChurchOfSubgenius]

if I remember correctly, that screen comes up with one of the reboots after the system files have loaded, he can't get past the initial conflict report that XP gives you before it installs any files.

 

[LiLithTecH]

The only other alternative would be to disable the Highpoint controller
in the BIOS, provided that he is not using that as the boot drive.

 

[Kanly]

He needs to put the drive on the ATA-33 controller for the install/upgrade.

Then: (its been a while since I did this for my 2 6BA+IV)

1) Go into device manager and upgrade the drivers for the HPT-366 (need to do it twice, once for each channel)

2) Shutdown and put the HD back on the HPT-366

3) Power up.


There are some old threads about this -- I contributed to them and so did Larry Joe if you want to search that way.

 

[huesmann]

Leto is right. You need to install XP with the OS drive on the chipset IDE port, not the add-on IDE. Then you can switch it over to the HP once you've installed the drivers for it. Had the same problem with my Abit BE6.

 

[Vic]

Originally posted by: LiLithTecH
The only other alternative would be to disable the Highpoint controller
in the BIOS, provided that he is not using that as the boot drive.

The HPT366 controller cannot be disabled on a Soyo 6BA+IV (had one of those for years, loved it, but it died an unfortunate and tragically sudden death ).

Have you tried using the Win2k drivers? It's been some time, but I believe that worked for me. You get an error about the drivers not being "certified" but you just go by that .

edit: doh! should have read all the posts. When I installed XP on that rig, I did a full install. The advice of others, to put the boot drive on the ATA/33 controller, is probably your best option. Make sure your dad completes the entire install with the OS completely setup and then installs the HPT366 drivers before he moves the drive back to the HPT366 controller.

 

[Fusman]

Well, coincidentally I did an XP pro install on an Abit board just a few days ago and that mobo has the HPT366 controller built in. I found some drivers on the net, version 1.30 beta, put those on a floppy and used them when xp prompted for additional storage drivers, F6, during install. Xp did complain about the drivers not being certified but I used them anyway. Everything works fine and I didn't have to put the hard drive on the ATA33 controller during install.

Here's a link for the 1.30 beta drivers
http://www.soyousa.com/dl/drivers/highpoint/

file called 366XP.zip

 

[ChurchOfSubgenius]

alright, thanks guys, I'll see if I can get him to switch the IDE cable over without gutting it. Thanks for your help.

 

[sep]

I got the Abit BE6 v1.2 with the same controller. I used the ATA33 until all drivers where installed.

Also, make sure he's got no IRQ conflicts in device manager. I found many article with the SB Live and the ABIT BE6 motherboards.

Good Luck!
-JC

 

[huesmann]

Originally posted by: ChurchOfSubgenius
alright, thanks guys, I'll see if I can get him to switch the IDE cable over without gutting it. Thanks for your help.

Actually, I think Fusman's idea might be your best initial bet. Do what you said above if it doesn't work.

 

[ChurchOfSubgenius]

Originally posted by: huesmann

Originally posted by: ChurchOfSubgenius
alright, thanks guys, I'll see if I can get him to switch the IDE cable over without gutting it. Thanks for your help.

Actually, I think Fusman's idea might be your best initial bet. Do what you said above if it doesn't work.

I didn't think that XP propmted you for drivers until later (after it does the conflict report)