You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 13 of 14)
Bâshrat the Sneaky wrote:Try this: open your txtsetup.sif file, do a search for "SCSI.Load" and now find the line that references "iastor" (i.e. the newer driver, not the old one) and put a semi-colon in front of it. That will prevent this driver from loading. Now retry.
Will do. I'll report back on Sunday.
Thanks!
Second comfirmation of the ICH5R "no hard disk drives can be found" error. This time on Intel's retail 875P desktop board. So that eliminates the possibility that Asus was implementing something non-standard on their 875 board.
Bâshrat the Sneaky wrote:You can trust me when I say that that that is a trusted method, it's been working for well over a year now. The CABbed file is renamed, but the internal filename remains unaltered, so Windows will still use iastor.sys! 
It's very odd that it isn't working...
Bâshrat,
What other troubleshooting steps are there to take? Switching to method 1 shouldn't affect the outcome since we are dealing with txtsetup.sif stuff here, right? I verified that the XPCD and driverpacks work fine on all machines I have used it on this week (about 5 pc's of varying configs), and it just *will not* install the ICH5R driver on a 875P based motherboard. 
I can only go by a hunch, and a my hunch tells me it's a simple syntax error somewhere, pathing or otherwise.
Update: I tried a trick where I copied drivers from folder "O" to the "1" directory and edited the txtsetup.sif so that ICH5R is "iastor" instead of "iastrold". I also removed all references to iastrold in txtsetup and dosnet.inf, and the iastrol_.sys in i386. No dice, but then again I'm admittably not quite sure of what I'm doing here.
Bâshrat the Sneaky wrote:I'm sorry to disappoint you, but those ARE the original files. The date has changed solely because they have been copied once. But please feel free to compare the MD5 checksums. They'll be identical. I am using the right version. I've compared the drivers in detail to avoid problems/mistakes.
By the way, your hwid is this one: PCI\VEN_8086&DEV_24DF. That hwid is not supported by the driver in D\M\I... but it is by the one in D\M\I\O, so it CAN'T have installed the newer driver!
What was the exact error/BSOD you had when booting?
No BSOD, I get the "no hard disk drives can be found" error after the "starting windows" stage of setup (before partitioning and copying). Checking again, you are right, they are the same drivers! AND I made a mistake in my last F6 disk - I copied the later drivers instead. The ones in "O" work when using manual F6 - however, after yet another install using the normal driverpackms for whatever reason the "O" drivers are not recognized/copied. Pathing problem maybe?
Bâshrat the Sneaky wrote:By looking in the .inf file. You will see that your device is supported by the driver in the D\M\IN\1\O directory. (Just verified that.)
I assume you've installed the driver manually now? Since it seems to be installed just fine according to your hwids.txt.
Yeah I used the F6 option instead using the drivers I referenced earlier and it installed fine. To test, I used the drivers in "O" on my floppy and F6 *did not* work.
Doing a little more research, it seems that even though your supplied driver states it will support the controller in the .inf - according to intel the last driver release to support ICH5R are in an older release of these drivers and no longer supported afterwards.
Going here - http://downloadfinder.intel.com/scripts … bmit=Go%21 - you will see the latest drivers that state full support of ICH5R are v5.5.0.1035 from 1/5/2006. Your "O" drivers are dated from 2/26/2006. All driver releases (floppy and manager) after v5.5.0.1035 do not list any 8XX series intel chipsets and therefore do not support ICH5R (which is a controller onely used on 875P, 865, and 845 boards). So according to Intel on their own website, despite what their later infs may contain, the last driver to support ICH5R is here: http://downloadfinder.intel.com/scripts … p;lang=eng
If you are keeping two separate driver folders of intel sata raid controllers to keep legacy support, then v5.5.0.1035 is the one you want to keep instead of the later one.
Where would I look in the DP or base to see if the reference ID is correct?
Here you go Bâshrat, as promised here is my HWID.txt. You'll note that the ICH5R SATA RAID controller is PCI\VEN_8086&DEV_24DF&SUBSYS_80A61043&REV_02\3&267A616A&0&FA
===========
PCI devices
===========
PCI\VEN_1002&DEV_4E48&SUBSYS_00021002&REV_00\4&1A99067F&0&0008: RADEON 9800 PRO
PCI\VEN_1002&DEV_4E68&SUBSYS_00031002&REV_00\4&1A99067F&0&0108: RADEON 9800 PRO - Secondary
PCI\VEN_1102&DEV_0004&SUBSYS_10021102&REV_04\4&2E98101C&0&58F0: Creative SB Audigy 2 (WDM)
PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_04\4&2E98101C&0&5AF0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1102&DEV_7003&SUBSYS_00601102&REV_04\4&2E98101C&0&59F0: Creative Game Port
PCI\VEN_1106&DEV_3044&SUBSYS_808A1043&REV_80\4&2E98101C&0&18F0: VIA OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_8086&DEV_1019&SUBSYS_80F71043&REV_00\4&3B3CB9B1&0&0818: Intel(R) PRO/1000 CT Network Connection
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&267A616A&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&267A616A&0&F8: Intel(R) 82801EB LPC Interface Controller - 24D0
PCI\VEN_8086&DEV_24D2&SUBSYS_80A61043&REV_02\3&267A616A&0&E8: Intel(R) 82801EB USB Universal Host Controller - 24D2
PCI\VEN_8086&DEV_24D3&SUBSYS_80A61043&REV_02\3&267A616A&0&FB: Intel(R) 82801EB SMBus Controller - 24D3
PCI\VEN_8086&DEV_24D4&SUBSYS_80A61043&REV_02\3&267A616A&0&E9: Intel(R) 82801EB USB Universal Host Controller - 24D4
PCI\VEN_8086&DEV_24D7&SUBSYS_80A61043&REV_02\3&267A616A&0&EA: Intel(R) 82801EB USB Universal Host Controller - 24D7
PCI\VEN_8086&DEV_24DB&SUBSYS_80A61043&REV_02\3&267A616A&0&F9: Intel(R) 82801EB Ultra ATA Storage Controllers
PCI\VEN_8086&DEV_24DD&SUBSYS_80A61043&REV_02\3&267A616A&0&EF: Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD
PCI\VEN_8086&DEV_24DE&SUBSYS_80A61043&REV_02\3&267A616A&0&EB: Intel(R) 82801EB USB Universal Host Controller - 24DE
PCI\VEN_8086&DEV_24DF&SUBSYS_80A61043&REV_02\3&267A616A&0&FA: Intel(R) 82801ER SATA RAID Controller
PCI\VEN_8086&DEV_2578&SUBSYS_00000000&REV_02\3&267A616A&0&00: Intel(R) 82875P/E7210 Memory Controller Hub - 2578
PCI\VEN_8086&DEV_2579&SUBSYS_00000000&REV_02\3&267A616A&0&08: Intel(R) 82875P Processor to AGP Controller - 2579
PCI\VEN_8086&DEV_257B&SUBSYS_00000000&REV_02\3&267A616A&0&18: Intel(R) 82875P/E7210 Processor to PCI to CSA bridge - 257B
20 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&1C4B7D9B&0 : USB Root Hub
USB\ROOT_HUB\4&1FCB28C&0 : USB Root Hub
USB\ROOT_HUB\4&24D2BE59&0 : USB Root Hub
USB\ROOT_HUB\4&CB41D3B&0 : USB Root Hub
USB\ROOT_HUB20\4&F180E13&0 : USB Root Hub
USB\VID_046D&PID_C221\6&BACBDC6&0&1 : USB Composite Device
USB\VID_046D&PID_C221&MI_00\7&1D789EAB&0&0000 : USB Human Interface Device
USB\VID_046D&PID_C221&MI_01\7&1D789EAB&0&0001 : USB Human Interface Device
USB\VID_046D&PID_C222\6&BACBDC6&0&4 : USB Human Interface Device
USB\VID_046D&PID_C223\5&160F4E1&0&2 : Generic USB Hub
USB\VID_050F&PID_0003\5&3AD090D&0&2 : Generic USB Hub
USB\VID_051D&PID_0002\NB0206151021__ : American Power Conversion USB UPS
12 matching device(s) found.
twig123 wrote:Fragbert wrote:Bâshrat the Sneaky wrote:I already AM handling this. I'm using 2 drivers, also for textmode setup!
Please post your HWID so I can find out if I have assigned a HWID to the wrong driver.
Thanks, I'll edit this post tonight when I get to that specific machine again. It turned out that I had to make a new unattended XPCD without any driver pack integration in order to get F6 disk install to work properly. Disabling the masstorage integration for whatever reason still would not allow for the floppy to copy files at the "copying windows files" stage, even though the floppy was read during F6.
The motherboard was the Asus P4C800-E Deluxe.
Your F6 copy files issue is caused by having the "UnattendedSwitch=Yes" in your Winnt.sif file I believe...
I haven't found a way to make F6 work with an unattended disk succesfully yet.
Actually F6 worked fine as long as I did not use any driverpacks. My WINNT.SIF was still set as an unattended install. Strange...
Bâshrat the Sneaky - sorry no time last night to get the HWIDs, will do tonight.
Bâshrat the Sneaky wrote:I already AM handling this. I'm using 2 drivers, also for textmode setup!
Please post your HWID so I can find out if I have assigned a HWID to the wrong driver.
Thanks, I'll post tonight when I get to that specific machine again. It turned out that I had to make a new unattended XPCD without any driver pack integration in order to get F6 disk install to work properly. Disabling the masstorage integration for whatever reason still would not allow for the floppy to copy files at the "copying windows files" stage, even though the floppy was read during F6.
The motherboard was the Asus P4C800-E Deluxe.
Intel's latest matrix storage drivers no longer support the older ICH5R SATA RAID chip (82801ER). This controller is common on intel 875/865/845 chipset based motherboards. Intel dropped support for ICH5R sometime last year.
I found this out while using base 6.08.4 and masstorage 6.08. Because of how things are integrated, the only way to get my installation going was to uncheck masstorage and do a manual F6.
Intel may start pulling support for the ICH6 series as well, so masstorage will need separate folders within the "IN" folder for these older raid controller drivers. What a pain!
Here is the last driver (from 2005) that officially supports ICH5R / 82801ER:
http://downloadfinder.intel.com/scripts … p;lang=eng
I've got some time free now and I'd like to beta test the new product if you please. 
What people care about most here are the driver packs themselves. The majority of users here utilize DriverPacks to create UWXP CDs, and a fringe amount for other OSes. Just speaking freely here; I personally would rather have constantly updated driver packs with the older version of base than the situation as it is now. The new version of base is a tremendous undertaking, I don't think anybody expected how big an undertaking the project would amount to and how it has thrown a wrench into driver pack updates. It is obvious Bâshrat the Sneaky deserves all the praise (and $$$) for the work he has done. If this were to become a professional service that people shall pay for, I would more likely pay for a continuously updated driver pack set than a more slick integration tool with less frequent driver pack updates.
Bâshrat the Sneaky wrote:I will look into this, but if you can post direct download links, then I will handle it sooner.
For the Dell Optiplex GX520 / GX620
Audio: http://support.dell.com/support/downloa … eid=126932
Graphics: http://support.dell.com/support/downloa … eid=168176
I deploy the GX520, which is exactly the same as the GX620 minus the trusted platform module. They are both based on the Intel 945G chipset. The intel integrated graphics, even the latest driver, is not *exactly* the same as the OEM supplied by dell. The intel driver will work, but msupdate will tell you that a Dell driver is available. The sound driver will only work with Dell's driver. The LAN will work fine with the latest Broadcom driver. Chipset and mass storage should not be an issue.
I ended up making a custom driver pack for the GX520s so the Dell branded graphics and sound will install.
Probably the cmdow.exe is triggering the false positive. NAV and SACE both classify (wrongly) that cmdow.exe is a hacktool.hidewindow threat.
Have not heard much from him this month. I guess the pace of updating a project like his slows down once you're done with school
Bâshrat the Sneaky wrote:Changed to 'OPEN', I don't remember why I had set it to 'SOLVED' about a month ago :s. I will try to reproduce this, which I already have tried, without success.
I think you said it was solved because the solution was "blame windows"
Hedgehogmsx wrote:No, it seems that the first method doesn't work anymore. He surely made a mistake in his programmation. I noticed that there is another topic that deals with this problem, they find why (a bad path) but nobody told us how to solve this
http://forum.driverpacks.net/viewtopic.php?id=22
Same issue. Labeled "solved" as well?
Bâshrat the Sneaky, did you look at the suggestion at the end of the thread?
I can verify that the latest sound DP *still* does not install these sigmatel drivers for intel retail desktop boards. Nothing is listed in the device manager under sound/multimedia, and of course, no sound
I noticed when I set only the 3rd party packs in KTD, *all* drivers were kept.
Helmi wrote:Fragbert wrote:A search of the forum for "hacktool.hidewindow" yields zero results.
A search for virus does, however.
Actually, no, it does not.
A search of the forum for "hacktool.hidewindow" yields zero results.
Posts found [ 301 to 325 of 335 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.035 seconds, 5 queries executed ]