there is HTP370 driver in windows?
No there is not, unfortunately some people assume things without actually looking 
You can look at your mshdc.inf to verify.
there is HTP370 driver in windows?
No there is not, unfortunately some people assume things without actually looking You can look at your mshdc.inf to verify.
I would say that at least default(?) (there is HTP370 driver in windows?) driver might have *some* problems - at least in RAID mode.
I don't know if the newest Highpoint driver is better.
If I had 1200A card I could test it but as I don't have it - I can't
There are (I googled for it) some pages that speak about successful use of HTP370 drivers but under Linux not Windows.
]]>At least we know AD is causing an issue. I will look into it, for now I suggest you get rid of it if you don't need it of course. I will download the latest driver of both manufacturer and keep the one that fits both. (If possible)
The drivers for HP in pack is the lastest avilable. So no need to look for new.
I have no problem with installing WinXP.
I'm doing ~ once per week - friends/family helper, some outside work - a few beers are always welcome 
.
I've been using driverpacks for long time - I had much more posts in old forum - now I don't have much free time.
This one PC - it was 15 minutes more work - after BSOD I knew what was wrong since beginning so I moved HDD to standard intel IDE controler (ATA33 max), instaled unnatended windows/ get rid of wong driver (forced update to HPT)/ moved HDD to HPT370 (ATA 100), works done.
GHOSTed C: partition for duration of tests. PC will go one floor down to neighbour tomorrow.
So the problem is not to me but to others with HTP370 who wont know what to do.
So if You or anyone else have some ideas what to put into .ini (no need to make whole pack - I will make it myself) come forth and speak
The PC has to go in ~16 hours. so if anybody has an idea what hwdid need to be added to ini...
]]>Will report in ~10 minutes
]]>So 810I doesnt work.
Next try- somebody?
As long as I have hardware to test.
I did check, all OK...
My bad I checked only AD and H dirs not ini file.
---------------
Still BSOD.
I will check without other packs /cpu / chipset/ etc.
-----
I checked the HDD after BSOD in system on CD with HDD pluged to normal controler
Inside Windows/recovery/system.log
It looks like the driver loaded is:
ahpt3xx.sys size: 44,998
I supose name change comes from
DriverPack_MassStorage_wnt5_x86-32.ini
[AD]
ms_count=1
ms_1_deviceName="Adaptec ATA RAID 1200A Controller"
ms_1_tag="ahpt3xx"
ms_1_sysFile="hpt3xx.sys"
ms_1_hwids="PCI\VEN_1103&DEV_0004&CC_0104"
ms_1_isBusExtender=false
and as I can see it still loads driver from AD/ dir not h/ dir
]]>not via, but same problem.
SP3 has changed support to highpoint.
OverFlow once wrote a exception and later on, in testpacks, it got diluted or abandoned.
Samlab has reported this over and over for VIA, and I think he has no fixed fix.
Neither do I.
SamLab is Russian, and I hope he takes lessons in English. He is a sharp shooter and finds problems, but he gets misunderstood, or not understood at times. (We are an international bunch, and we better learn that 'on line translate' is not the better tool?)
edit; oops; Via is NOT Highpoint brand.. a Highpoint controller Can have a rebranded Via chip, but so can adaptec.
(I was writing from the top of my head.. thinking 370 is Via..)