You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by piper28
Pages 1
7059test3 is a definite no go. Doesn't detect in the textmode (comes up as Unknown [MBR]), and then ends up in a constant reboot mode, and it's an even earlier reboot that the original problem I had, reboots almost immediately after the splash screen comes up.
So far it seems to me that the best working setup for the 27C1 has been the 6.2.1.x drivers with the updated chipset pack. That detected fine in textmode, and ended up with a setup that worked.
Thanks,
Gary
PLEASE; IF you are testing these 7058 and 7059 test versions, PLEASE REPORT
Sometimes takes me a bit to get around to testing it (have to work doing it around doing other things).
Handful of typos in the 7059 version. A comma as the first character in the file, the [IN-3] section referred to iastor2.sys when the directory has iastor3.sys, and some screwed up quotes around one of the compaq entries (sorry, can't remember which one off the top of my head).
After cleaning those up, I ran it up to the partitioning spot, where with this package I again get "unknown [MBR]" as the device the disk is on. Probably won't get a chance to run it all the way through the complete setup today (which also means I won't till next week).
Have to admit, I'm a little suspicious of the 7.5 drivers. It kinda bothers me that intel still doesn't list them for download at their site. And they definitely don't seem to like to come up for my chipset.
Ok, did a little more playing around with this. If I move the PCI\VEN_8086&DEV_27C1&CC_0106 from the 7.5.0 drivers and put them on the 6.2.1 drivers, I no longer the the "unknown [MBR]" in the textmode setup (I get "iastor1" which is what I'd expect), and do end up with the 6.2.1 drivers installed when all is finished. These also seem to be working, which I have to admit is kinda odd, because it seemed to be the 6.2.1 drivers that were causing the reboots before. Don't know if the updated chipset drivers would have gotten rid of those reboots.
So I guess from what I can tell, at least using the updated chipset drivers, and putting the 27C1 device with the iastor1 driver (6.2.1), that appears to solve the problem I was having. So I guess that'd be my recommendation for the next release of the driverpack.
Thanks,
Gary
Well, that sort of seems to work, with a couple caveats. It was a little weird that in the textmode phase when you can select the partition to install on, it seemed to identify the device as "unknown [MBR]", which to me implies it didn't find the right driver at the time. However, the install goes fine, and the machine no longer suffers from the reboot problems when starting that it used to. Here's the really odd part: It actually seems to have pulled up driver version 6.2.1, but when I look at the ini file in mass storage, I'm pretty sure it should be pulling up 7.5.0.
So like I said, the plus is it seems to work. I'm just not sure that the way it got to the working stage is quite right 
.
BTW, there are a couple of extra carriage returns in the MassStorage test file there, both in the ms_1_hwids lines of [IN-1-0] and [IN-2] I believe. Causes bad txtsetup.sif files until they're removed. (Easy enough to find and fix though).
Thanks,
Gary
Heh, now it doesn't appear to be there at all .
(Also tried the rapidshare link from the chipsets forum, and shows as deleted, even after your post saying they were back).
I think however that I might have figured out how to put in the updated chipset drivers myself, so I think I'll try building a version myself and giving it a try.
That Chipset pack seems to be corrupt. I only get a 272k file that isn't openable in 7zip.
Ok, here's the HWID's.
===========
PCI devices
===========
PCI\VEN_1002&DEV_5B60&SUBSYS_06021002&REV_00\4&1A646D2D&0&0008: RADEON X300 SE 128MB HyperMemory
PCI\VEN_1002&DEV_5B70&SUBSYS_06031002&REV_00\4&1A646D2D&0&0108: RADEON X300 SE 128MB HyperMemory Secondary
PCI\VEN_1102&DEV_0004&SUBSYS_20061102&REV_04\4&5855BE9&0&20F0: Creative SB Audigy 2 ZS (WDM)
PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_04\4&5855BE9&0&22F0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_04\4&5855BE9&0&21F0: Creative Game Port
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_E1\3&172E68DD&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2770&SUBSYS_00000000&REV_00\3&172E68DD&0&00: Intel(R) 945G/P Processor to I/O Controller - 2770
PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_00\3&172E68DD&0&08: Intel(R) 945G/P PCI Express Root Port - 2771
PCI\VEN_8086&DEV_27B8&SUBSYS_00000000&REV_01\3&172E68DD&0&F8: Intel(R) 82801GB LPC Interface Controller - 27B8
PCI\VEN_8086&DEV_27C1&SUBSYS_01A71028&REV_01\3&172E68DD&0&FA: Intel(R) 82801GR/GH SATA AHCI Controller
PCI\VEN_8086&DEV_27C8&SUBSYS_01A71028&REV_01\3&172E68DD&0&E8: Intel(R) 82801GB USB Universal Host Controller - 27C8
PCI\VEN_8086&DEV_27C9&SUBSYS_01A71028&REV_01\3&172E68DD&0&E9: Intel(R) 82801GB USB Universal Host Controller - 27C9
PCI\VEN_8086&DEV_27CA&SUBSYS_01A71028&REV_01\3&172E68DD&0&EA: Intel(R) 82801GB USB Universal Host Controller - 27CA
PCI\VEN_8086&DEV_27CB&SUBSYS_01A71028&REV_01\3&172E68DD&0&EB: Intel(R) 82801GB USB Universal Host Controller - 27CB
PCI\VEN_8086&DEV_27CC&SUBSYS_01A71028&REV_01\3&172E68DD&0&EF: Intel(R) 82801GB USB2 Enhanced Host Controller - 27CC
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&172E68DD&0&E0: Intel(R) 82801GB PCI Express Root Port - 27D0
PCI\VEN_8086&DEV_27DA&SUBSYS_01A71028&REV_01\3&172E68DD&0&FB: Intel(R) 82801GB SMBus Controller - 27DA
PCI\VEN_8086&DEV_27DC&SUBSYS_01A71028&REV_01\4&5855BE9&0&40F0: Intel(R) PRO/100 VE Network Connection
PCI\VEN_8086&DEV_27DF&SUBSYS_01A71028&REV_01\3&172E68DD&0&F9: Intel(R) 82801GB Ultra ATA Storage Controllers - 27DF
PCI\VEN_8086&DEV_27E0&SUBSYS_00000000&REV_01\3&172E68DD&0&E4: Intel(R) 82801GB PCI Express Root Port - 27E0
PCI\VEN_8086&DEV_27E2&SUBSYS_00000000&REV_01\3&172E68DD&0&E5: Intel(R) 82801GB PCI Express Root Port - 27E2
21 matching device(s) found.
===========
USB devices
===========
USB\HASP\6&B85AF19&0&00 : Aladdin HASP Key
USB\ROOT_HUB\4&196F55AC&0 : USB Root Hub
USB\ROOT_HUB\4&22A54C7D&0 : USB Root Hub
USB\ROOT_HUB\4&379ABCCE&0 : USB Root Hub
USB\ROOT_HUB\4&D36040A&0 : USB Root Hub
USB\ROOT_HUB20\4&14DCF352&0 : USB Root Hub
USB\VID_0409&PID_0058\5&2936E24E&0&6 : Generic USB Hub
USB\VID_04B4&PID_0101\5&2214EF1A&0&2 : USB Composite Device
USB\VID_04B4&PID_0101&MI_00\6&33F48EA2&0&0000 : USB Human Interface Device
USB\VID_04B4&PID_0101&MI_01\6&33F48EA2&0&0001 : USB Human Interface Device
USB\VID_0529&PID_0001\5&2BA979EE&0&2 : Aladdin USB Key
USB\VID_413C&PID_3010\5&2214EF1A&0&1 : USB Human Interface Device
12 matching device(s) found.I'm guessing that the SATA controller in there matches up to the PCI\VEN_8086&DEV_27C1&CC_0106 that I find in the mass storage ini file (although I have to admit, I don't know enough to understand how the subsystem and CC things there match up).
If that is the right matchup (and if it's the mass storage device causing problems), it looks like the version that works is 5.5.0.1035 and the version on the current driverpack is 6.2.1.1002. Hmm, I'm guessing that building a version of the disk using the older driver might be in order.
Ok, this is kinda weird, and I'm not sure where the problem is. I've got a Dell 9100 and 9150 machine that after everything installs, reboots while in the splash screen when windows is booting. However, for a while, it worked perfectly fine. Going back and looking at old versions of the disk, it looks like back when I was using version 6.02 of the driverpacks, they'd work fine. Sometime shortly after that is when it started working (and yeah, I'm just saying anything about it now). I did some boot logging at one point (afraid I don't have those anymore), but couldn't see anything in there that seemed to indicate a problem. The machines would boot into safe mode fine, and nothing really seemed out of place.
Now, to be entirely honest, I can't be completely sure that the problem is driver related. Obviously, that disc that works was built with ryanvm files from back then, and subsequent disks were built with later versions. (I also think that the disk that I have that works, which seems to be from March 2006, was just before the black screen issue that popped up for a while).
I've never seen anyone comment on having problems with these systems, so I don't know if it's just people aren't using them, or if it's just that I happen to run into problems for some reason. Unfortunately, because of some changes around here, there's kinda a limit to how much testing I can do (one of the machines currently can't be reformatted because it's needed, the other is the one I do all the building of disks on), so I guess at this point I'm mostly just wondering whether anyone is successfully using the current driverpacks on one of these two systems? If I at least knew someone had it working, that'd at least give me some hope to keep digging into it.
Pages 1
DriverPacks.net Forum » Posts by piper28
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.023 seconds, 7 queries executed ]