|
Notes |
|
|
(0000010)
|
|
Vier57
|
|
2006-04-30 04:57
|
|
I test this : I prepare a CD with simple a WINNT.sif file, I integrate with newer base nad older (name 6.03 and 6.04)
- with 6.04RC1 : no detect
- with 6.03.4 : detect HDD
I replace TXTSETUP.sif gone with 6.03.4 in CD build with 6.04RC1 : HDD detect ?! |
|
|
|
(0000011)
|
|
Vier57
|
|
2006-04-30 05:11
|
|
I test with replace section HArdwareIDsDatabase from 6.03 to 6.04 TXTSETUP file !
The problem persist ! No this section is the problem ! |
|
|
|
|
|
I can only say this: please test the other sections as well. I don't SEE any error in the file and it did work for at least one controller not supported by default, which means the problem is probably limited to this single device. |
|
|
|
(0000013)
|
|
Vier57
|
|
2006-04-30 05:52
|
|
|
I test with SCSI.LOAD section from 6.03.4 to 6.04 and HDD detect ! |
|
|
|
(0000015)
|
|
Vier57
|
|
2006-04-30 10:56
|
|
|
It's possible to write line in the same order that in 6.03.4 SCSI.LOAD section ? |
|
|
|
|
|
Your suggested solution has been implemented in 6.04 RC2. Don't forget to let me know if it worked! |
|
|
|
(0000018)
|
|
Vier57
|
|
2006-05-02 03:58
|
|
After many chnages for test newer version RC2, no solved the problem, you change hardwareidsdatabase ? No the problem, the problem is SCSI.load section :
- if I used old hardwareidsdatabase with scsi.Load section provide 6.03.4 slipstream no problem !
You modify SCSILoad section ! Why doesn't work I don't know, but with list from 6.03.4 works ! |
|
|
|
(0000030)
|
|
Vier57
|
|
2006-05-04 15:08
|
|
|
|
|
|
Thanks to Vier57's hard efforts to find the cause, he was able to conclude that the reason for his HDD not being detected was the following: in the old DriverPacks BASEs the order in which the text mode mass storage drivers would load, was by reversed alphabetical order (that is: VMware, then VIA, then SiS, then...)
Apparently there is some driver that is conflicting with the iastor driver, though no HWIDs match, not even partially (no other driver even has the same vendor ID). Until an exact cause is identified, this is the best solution, that won't interfere with any other drivers. |
|
|
|
|
|
It's still not fixed according to Vier57. He has suggested got another possible solution though. |
|
|
|
(0000041)
|
|
Nakatomi2010
|
2006-05-10 19:59
(edited on: 2006-05-11 08:43) |
|
I was thinking about adding to my other problem, but I'll just throw myself into this one...
Today I tried using a disc on two systems, both with Intel chipsets, the first was an 800 series, didn't pay much attention to it... Honestly didn't connect the dots between this issue and that one...
The second problem was on an Intel D945GTP motherboard, so I'm assuming the D945G chipset... This attempted install was on a virtual PC... I've done a successful install in the past both with and without the virtual PC and this is the first time I ran into this error...
Basically said there was no hard drive. The 8000 series chipset was an IDE drive in no array in an eMachine T3645, the second one was on a SATA drive on the D945G chipset... Again, not in an array.
Edit: The chipset of the eMachine appears to be an 845G chipset...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DP base.7z (76,615) 2006-04-30 04:51