You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 1 of 2)
I'm running into an issue when I'm trying to run the script from a network share. The script sets a default drive letter Z:, but then once the elevate.cmd script runs I get a script error 'Can not find script file "Z:\SAD2-120326\bin\elevate.vbs".'
I did some more experimenting and found it's a UAC timing issue in my virtual Vista. It works if I use your timing script "For /L %%A in (1,1,1)..." for just one second and put that at the end of the elevate.cmd script. Right after "start wscript...". The normal script worked the first time I ran it a few hours ago, but ever since then it's not. Tried moving it to a different share location and even extracting from the download again.
The only thing that fixed it was to add a slight delay after the "start wscript..." to give Vista a little time to popup the UAC prompt so I can elevate the permission to 'cmd.exe'. I don't know if this is something you'd consider adding? Maybe just a 2 second delay or something.
mr_smartepants wrote:I'd recommend moving to Win7 ASAP. Win8 will be out next year and Vista will just be a bad memory for most.
Well, I work in a computer shop, so unfortunately we still have to reinstall Vista every now and then. Still install XP too, which is why recently I made another customized/updated XP disc. Now it's time to update our Vista discs. Haven't made any updated Win 7 discs yet, haven't really needed them for now, since 7 seems to install more smoothly/quickly than the others. But I'll check out that site, thanks.
Since there's no more builds or support of Vista-Tool, what's a similar easy way to integrate drivers into the Vista install.wim file?
Mr.Tom wrote:I integrated the drivers again into a fresh Vista SP0 (AIO) image and I get the same error. I am trying to integrate all the drivers provided in the download section for Vista x86.
The message is :
------------
Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
blah blah etc etc...
File: ifp60x32.sys
Status: 0xc0000098
Info: Windows failed to load because a required file is missing, or corrupt.
------------
So I wonder if maybe another driver is at fault, like a MassStorage driver or something that's not letting it access the OS during the install. I'm trying to install this OS in a virtual machine using VMware Player. It also fails if I burn to CD and try on a real computer.
I've used this same process when I had downloaded drivers from November 2010 and integrated drivers using Vista-Tool v1.0.
I'm trying to use version 1112 this time, and I'm getting the same error as I did more than a year ago. I thought this bug was fixed? Suppose I'll have to delete those 6 files that I deleted last time. Maybe that will help again. Makin lots'o coasters.
Files: Ifcoemp.cat, ifcoemp.inf, Ifcoepr.cat, ifcoepr.inf, Ifcoevb.cat, ifcoevb.inf
TechDud wrote:That driver is WHQL'ed for NT6.1. VistaSP1??? You did delete the Win7 folder before integration?
Ack.. I didn't realize I had to manually alter the driver packs. I figured everything would be smart enough to pick and choose the correct driver for the correct OS. Thanks for the help. 
So once I extract all the driver packs, I should do a search for 'Win7' folders and delete all of them?
Tried to integrate the latest drivers into my SP1 ISO. But after the GUI setup installs the OS doesn't boot and just gives me an error (0xc0000098) on a iusb3hcs.sys file. But the strange thing is that these files are located in a Windows 7 folder, but I'm installing Vista. And my computer doesn't have USB 3.0 either.
I checked v12.02 and the Intel USB drivers are not included in that version.
I will have to use v12.02 for now so I can get a good install going.
Ahh, okay, figured it out. There's a bug in the script? Missing some quotes.
The line:
for %%f in (%DPLoc%\DP_*.7z)
Should have some quotes:
for %%f in ("%DPLoc%\DP_*.7z")
Now a directory path can have spaces. 
Having a problem with SAD2. I extract the archive, 110505 version and run the CMD script. Since there's an example file in there it should just run off the bat, right? But I get an error from un7zip of "No files to extract" then "Invalid files list and". Even if I add more DriverPacks inside the NT5\x86 directory, I still get the same error messages.
I was able to create a directory using DPBASE and run the CMD file it created, but it looked different than SAD2. I'm assuming it was SAD1? The .7z files were all renamed too, makes it difficult to replace with a newer version in the future. What am I doing wrong?
mr_smartepants wrote:Thanks for confirming. Yes, we always recommend that you use the official DriverPacks (and graphics Third Party DriverPacks) ONLY for integrated discs. Use SAD2 for all DriverPacks & Third Party DriverPacks during post-install (not affected by bug).
That works perfectly.
So I downloaded the SAD2 script to check it out. Nothing too clear on when it's to be used. After running DPBASE to create the stand alone directory and copying it into the SAD2 directory, can the DP_Install_Tool.cmd be run at anytime in windows? Anything to worry about if I add it to the Startup folder so the drivers continue right when the desktop appears after an integrated install? Sorry, this is a bit OT.
mr_smartepants wrote:That's WAY too many Third Party DriverPacks! I'd bet money that's your problem.
If you're just removing DriverPacks from a built .iso, then just open the .iso in poweriso or magiciso (or similar) then delete the Third Party DriverPacks and rebuild the .iso then burn to dvd-rw and retest.
If the disc "sees" your HDD on the Intel controller and it allows you to begin the install but then BSOD AFTER the restart, then it sounds as if you're overloading the disc with all the DriverPacks and Third Party DriverPacks will cause this problem.
I timed my broken disc, and it takes about 1.25 minutes to complete T-37 to T-33 (Installing Devices). The working disc without the 3rd party drivers takes 2.25 minutes to compete, and the screen flashes black a lot while the display driver installs at some point too. So it appears my broken disc does have the too many drivers bug mentioned in your link.
The strange thing is that an old disc from Dec 2010 has 21 total drivers and works okay, while while the one I just made has only 20 and has the driver install bug. I'll reduce some 3rd party drivers and determine which ones I want to keep. I guess some of the new drivers just have too many directories than before.
Also to note, the 7B I was having before with only chipset & MS 11.09 caused a BSOD after the GUI reboot, testmode worked fine. 
mrhanman wrote:I'll give that a shot after lunch. I wish I had a DVD or CD-RW handy. I'm making a lot of coasters!
Quick question: do I need to re-extract the ISO, or can I simply rerun the Driverpack base on my existing folder?
I'd imagine starting fresh would be the best. So you don't run into overlapping driver versions. I created an updated folder all the way up to driver install, then just copy the files from there into a new directory when I want to experiment with new drivers. I tried copying the install files directly to a hard drive, but I needed to use FAT32 for DOS mode and manually run WINNT.EXE to install XP. But then it was slow due to SMARTDRV not installed.
I'm making a lot of coasters too. Trying to figure out why it's 7Bing when it was fixed. I was able to repair the 7B from changing into IDE mode then running a mass storage batch file repair from a boot CD that swapped out and installed the correct IDE driver. But who wants to repair a new install every time, and you end up with only IDE.
A quick experiment would be to just include the DPMS only to see if you get a 7B. You will most likely need to post your HWIDs here so the mods can grab it an include into a test pack.
With my issue, I'm trying to narrow down which 3rd party pack is bringing back the 7B, when it should have been fixed from using an older known working DPMS without 3rd party packs. The odd thing is that they have nothing to do with hard drive controllers.
Seems to have been some major changes in the driver packs recently. So now this makes a 7B issue for ICH8, ICH9, & ICH10? I can use an older mass storage version and everything's okay, but when I also include some standard 3rd party ones I get a 7B again, kind of odd.
OverFlow wrote:Thanks again
You're welcome. And thanks for the prompt service and replies. I think I'll stay away from modding driver packs. The trick is to slow down my gray hair, not accelerate it.
I get really poor graphics performance, as it used some type of default display driver.
The thing looks like a smart phone on my monitor. It's like a very large windows phone 7 with a windows desktop plug-in. I sure wouldn't like it as my home desktop system. If I had a tablet screen, I'm sure this OS would be kinda cool. But I don't see how this is going to work with current OEM desktop computers. All windows 7 software we've tried seem to install okay. Maybe this won't get installed into mainstream desktop computers, but who knows.
mr_smartepants wrote:That's what I expected. Glad it worked for you. Seems the 7.8 driver doesn't like your HWID during textmode but is fine post-install. No matter. The end result is correct.
I'll make sure that fix makes it into the next final release.
Oh, and DriverPacks Finisher will be deleted on the following restart. That sometimes happens.
So this 2007 version is better than the 2010 version in the b1 driver for this HWID?
Okay, the force to 10.6.0.1002 worked okay.
There's also a left over DPsFnshr.exe in the root of the drive. Not sure if something didn't get a chance to finish correctly.
mr_smartepants wrote:OK, here's another pack to test. This time I removed the 10.1 Intel drivers and moved the HWIDs to the 10.6 which should be much better.
download 11.09.1b2
Okay, this one installed driver version 7.8.0.1012 9/29/2007. The description is 82801HR/HH/HO SATA AHCI, which is different from the 10.1 version. Was it supposed to be v10.6?
mr_smartepants wrote:I'll move your HWID from the 10.1 driver to the 10.6. All you need to do is test on your hardware (AHCI mode) and let us know if it works. If not, then we'll stick with the 10.1 drivers for that HWID.
Okay, I can give that a shot for this HWID. Is this test different than the test I just did yesterday using 11091b1?
The discs I create are used for reinstalling customer's computers that need to get out of here in a day or two. So I really don't have the time to experiment. This HWID is from a customer's abandoned system, so there's no hurry. I guess what I could do is create an all updated disc, then when I run into 7B computers I could use a modified 11.04 disc then post the HWIDs for repair later. I just probably won't be able to test the updated pack.
mr_smartepants wrote:Sure, I can try it if you're willing to test.
Well, I suppose I won't be able to test all the HWIDs. I'm just concerned on finding more chipsets that they removed and won't be able to use my updated disc. I'd end up having to revert to the old disc. Not the most efficient use of time. So I think I'll just end up reverting the dpms to 11.04 for maximum compatibility and update everything else.
mr_smartepants wrote:Mr.Tom wrote:What happened after 11.04? Something removed by accident, or was it just Intel?
After dpms 11.04, the Intel RST 10.1 drivers were replaced by the newer (and much stabler) 10.6 drivers. Not all the HWIDs moved to the new drivers so a few (like yours) were moved to the older v7 series.
So was this something Intel had done? Is there a way you can fix it by extracting all the HWIDs from 10.1 and port them into 10.6? Or would that be too dangerous not knowing if Intel removed them for a reason?
awnz wrote:I hope to test that version on the Toshiba laptops I was having trouble with tomorrow, fingers crossed (I get a lot of distractions, the client being a school!). With all the new hardware in them, it should be a good test.
Maybe give 11.04 a try. At least it worked for my HWID.
mr_smartepants wrote:OK, try this on for size!
download
Works like a $100 rimjob.. Thanks.
Even though the driver version is still 10.1.0.1008 11/6/2010 as I believe the 11.04 version had. What happened after 11.04? Something removed by accident, or was it just Intel?
Isn't there a way to copy over the HWIDs from 11.04 into new ones? I'm concerned which other HWIDs are missing after 11.04, since I've seen 2 other computers here with the issue a while back.
Aaight.. I found that v11.04 works, but v11.06, 7, 8, & 9 don't. No v11.05 for XP?
Hope that helps some.
EDIT: And for the heck of it, I tested v11.01 and that worked too.
OverFlow wrote:Don't use KTD if you don't have to ... you more than likely don't need it 
HWIDs tool linked in in our signatures
thanks again
KTD was disabled. I used the same settings as I always do and I don't see that popup message. But somehow only including one driver gave that popup. But it doesn't matter since everything works fine normally.
Here are the IDs.
===========
PCI Devices
===========
PCI\VEN_11C1&DEV_5811&SUBSYS_2A36103C&REV_70\4&11B6166B&0&08F0: IEEE 1394 Controller
PCI\VEN_14F1&DEV_2F20&SUBSYS_200C14F1&REV_00\4&11B6166B&0&20F0: PCI Simple Communications Controller
PCI\VEN_4444&DEV_0016&SUBSYS_88010070&REV_01\4&11B6166B&0&18F0: Multimedia Video Controller
PCI\VEN_8086&DEV_104C&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&C8: Ethernet Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&2411E6FE&0&F0: PCI to PCI Bridge
PCI\VEN_8086&DEV_2812&SUBSYS_00000000&REV_02\3&2411E6FE&0&F8: PCI to ISA Bridge
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FA: PCI Device
PCI\VEN_8086&DEV_2830&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&E8: Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_2831&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&E9: Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_2832&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&EA: Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_2834&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D0: Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_2835&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D1: Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_2836&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&EF: Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_283A&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D7: Universal Serial Bus (USB) Controller
PCI\VEN_8086&DEV_283E&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FB: SM Bus Controller
PCI\VEN_8086&DEV_283F&SUBSYS_00000000&REV_02\3&2411E6FE&0&E0: PCI to PCI Bridge
PCI\VEN_8086&DEV_284B&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D8: PCI Device
PCI\VEN_8086&DEV_29A0&SUBSYS_00000000&REV_02\3&2411E6FE&0&00: PCI HOST Bridge
PCI\VEN_8086&DEV_29A1&SUBSYS_00000000&REV_02\3&2411E6FE&0&08: PCI to PCI Bridge
PCI\VEN_8086&DEV_29A2&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&10: Video Controller (VGA Compatible)
20 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&1F382921&0
USB\ROOT_HUB\4&28EA960E&0
USB\ROOT_HUB\4&2DD613DB&0
USB\ROOT_HUB\4&34A77194&0
USB\ROOT_HUB\4&9EA459D&0
USB\ROOT_HUB20\4&174FF8C8&0
USB\ROOT_HUB20\4&2E713CA1&0
USB\VID_045E&PID_0040\5&22B77046&0&1 : Microsoft 3-Button Mouse with IntelliEye(TM)
USB\VID_058F&PID_6362\058F312D81B1 : Mass Storage Device
USB\VID_13FE&PID_3100\07A31B00647A68E3 : Patriot Memory
USBSTOR\DISK&VEN_&PROD_PATRIOT_MEMORY&REV_PMAP\07A31B00647A68E3&0: Patriot Memory USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_CF_READER&REV_1.01\058F312D81B1&1: Generic USB CF Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_MS_READER&REV_1.03\058F312D81B1&3: Generic USB MS Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SD_READER&REV_1.00\058F312D81B1&0: Generic USB SD Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SM_READER&REV_1.02\058F312D81B1&2: Generic USB SM Reader USB Device
15 matching device(s) found.
=============
Input Devices
=============
HID\VID_045E&PID_0040\6&1942EEC7&0&0000
1 matching device(s) found.
============
ACPI Devices
============
ACPI\AWY0001\2&DABA3FF&0
ACPI\FIXEDBUTTON\2&DABA3FF&0
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_0
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_1
ACPI\INT0800\4&3AAE508&0
ACPI\PNP0000\4&3AAE508&0
ACPI\PNP0100\4&3AAE508&0
ACPI\PNP0200\4&3AAE508&0
ACPI\PNP0303\4&3AAE508&0
ACPI\PNP0800\4&3AAE508&0
ACPI\PNP0A08\1
ACPI\PNP0B00\4&3AAE508&0
ACPI\PNP0C01\2&DABA3FF&0
ACPI\PNP0C02\1
ACPI\PNP0C02\2
ACPI\PNP0C02\4
ACPI\PNP0C04\4&3AAE508&0
ACPI\PNP0C0B\2&DABA3FF&0
ACPI\PNP0C0C\2&DABA3FF&0
ACPI\THERMALZONE\THRM
ACPI_HAL\PNP0C08\0
ROOT\ACPI_HAL\0000
22 matching device(s) found.
============
HDA Audio
============
No matching devices found.
============
RAID Devices
============
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FA
Name: PCI Device
Hardware ID's:
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C&REV_02
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C
PCI\VEN_8086&DEV_2821&CC_010601
PCI\VEN_8086&DEV_2821&CC_0106
Compatible ID's:
PCI\VEN_8086&DEV_2821&REV_02
PCI\VEN_8086&DEV_2821
PCI\VEN_8086&CC_010601
PCI\VEN_8086&CC_0106
PCI\VEN_8086
PCI\CC_010601
PCI\CC_0106
1 matching device(s) found.
EDIT: Here's another ID log. Taken after I installed XP using v11.01. Seems to have a more descriptive name for the RAID Devices.
===========
PCI Devices
===========
PCI\VEN_11C1&DEV_5811&SUBSYS_2A36103C&REV_70\4&11B6166B&0&08F0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_14F1&DEV_2F20&SUBSYS_200C14F1&REV_00\4&11B6166B&0&20F0: PCI Simple Communications Controller
PCI\VEN_4444&DEV_0016&SUBSYS_88010070&REV_01\4&11B6166B&0&18F0: Multimedia Video Controller
PCI\VEN_8086&DEV_104C&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&C8: Ethernet Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&2411E6FE&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2812&SUBSYS_00000000&REV_02\3&2411E6FE&0&F8: PCI standard ISA bridge
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FA: Intel(R) ICH8R/DH/DO SATA AHCI Controller
PCI\VEN_8086&DEV_2830&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&E8: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2831&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&E9: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2832&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&EA: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2834&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D0: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2835&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D1: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2836&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&EF: Standard Enhanced PCI to USB Host Controller
PCI\VEN_8086&DEV_283A&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D7: Standard Enhanced PCI to USB Host Controller
PCI\VEN_8086&DEV_283E&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FB: SM Bus Controller
PCI\VEN_8086&DEV_284B&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D8: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_29A0&SUBSYS_00000000&REV_02\3&2411E6FE&0&00: PCI standard host CPU bridge
PCI\VEN_8086&DEV_29A1&SUBSYS_00000000&REV_02\3&2411E6FE&0&08: PCI standard PCI-to-PCI bridge
PCI\VEN_8086&DEV_29A2&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&10: Video Controller (VGA Compatible)
19 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&1F382921&0 : USB Root Hub
USB\ROOT_HUB\4&28EA960E&0 : USB Root Hub
USB\ROOT_HUB\4&2DD613DB&0 : USB Root Hub
USB\ROOT_HUB\4&34A77194&0 : USB Root Hub
USB\ROOT_HUB\4&9EA459D&0 : USB Root Hub
USB\ROOT_HUB20\4&174FF8C8&0 : USB Root Hub
USB\ROOT_HUB20\4&2E713CA1&0 : USB Root Hub
USB\VID_045E&PID_0040\5&22B77046&0&1 : Microsoft USB Wheel Mouse Optical
USB\VID_058F&PID_6362\058F312D81B1 : USB Mass Storage Device
USB\VID_13FE&PID_3100\07A31B00647A68E3 : USB Mass Storage Device
USBSTOR\DISK&VEN_&PROD_PATRIOT_MEMORY&REV_PMAP\07A31B00647A68E3&0: Patriot Memory USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_CF_READER&REV_1.01\058F312D81B1&1: Generic USB CF Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_MS_READER&REV_1.03\058F312D81B1&3: Generic USB MS Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SD_READER&REV_1.00\058F312D81B1&0: Generic USB SD Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SM_READER&REV_1.02\058F312D81B1&2: Generic USB SM Reader USB Device
15 matching device(s) found.
=============
Input Devices
=============
HID\VID_045E&PID_0040\6&1942EEC7&0&0000 : Microsoft USB Wheel Mouse Optical
1 matching device(s) found.
============
ACPI Devices
============
ACPI\AWY0001\2&DABA3FF&0
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_0 : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_1 : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
ACPI\INT0800\4&3AAE508&0 : Intel(R) 82802 Firmware Hub Device
ACPI\PNP0000\4&3AAE508&0 : Programmable interrupt controller
ACPI\PNP0100\4&3AAE508&0 : System timer
ACPI\PNP0103\4&3AAE508&0 : High precision event timer
ACPI\PNP0200\4&3AAE508&0 : Direct memory access controller
ACPI\PNP0303\4&3AAE508&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0800\4&3AAE508&0 : System speaker
ACPI\PNP0A08\1 : PCI bus
ACPI\PNP0B00\4&3AAE508&0 : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C02\2 : Motherboard resources
ACPI\PNP0C02\4 : Motherboard resources
ACPI\PNP0C04\4&3AAE508&0 : Numeric data processor
ACPI\PNP0C0B\2&DABA3FF&0 : ACPI Fan
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\THERMALZONE\THRM : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
23 matching device(s) found.
============
HDA Audio
============
HDAUDIO\FUNC_01&VEN_10EC&DEV_0885&SUBSYS_103C2A36&REV_1001\4&2DCFB91F&0&0001: Audio Device on High Definition Audio Bus
1 matching device(s) found.
============
RAID Devices
============
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FA
Name: Intel(R) ICH8R/DH/DO SATA AHCI Controller
Hardware ID's:
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C&REV_02
PCI\VEN_8086&DEV_2821&SUBSYS_2A36103C
PCI\VEN_8086&DEV_2821&CC_010601
PCI\VEN_8086&DEV_2821&CC_0106
Compatible ID's:
PCI\VEN_8086&DEV_2821&REV_02
PCI\VEN_8086&DEV_2821
PCI\VEN_8086&CC_010601
PCI\VEN_8086&CC_0106
PCI\VEN_8086
PCI\CC_010601
PCI\CC_0106
1 matching device(s) found.
EDIT: Interesting though, IDE Mode works fine using v11.08.
Here's the IDE Mode IDs, even though it seems to work okay.
===========
PCI Devices
===========
PCI\VEN_11C1&DEV_5811&SUBSYS_2A36103C&REV_70\4&11B6166B&0&08F0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_14F1&DEV_2F20&SUBSYS_200C14F1&REV_00\4&11B6166B&0&20F0: PCI Simple Communications Controller
PCI\VEN_4444&DEV_0016&SUBSYS_88010070&REV_01\4&11B6166B&0&18F0: Multimedia Video Controller
PCI\VEN_8086&DEV_104C&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&C8: Ethernet Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&2411E6FE&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2812&SUBSYS_00000000&REV_02\3&2411E6FE&0&F8: PCI standard ISA bridge
PCI\VEN_8086&DEV_2820&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FA: Intel(R) ICH8 4 port Serial ATA Storage Controller - 2820
PCI\VEN_8086&DEV_2825&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FD: Intel(R) ICH8 2 port Serial ATA Storage Controller - 2825
PCI\VEN_8086&DEV_2830&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&E8: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2831&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&E9: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2832&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&EA: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2834&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D0: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2835&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D1: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_2836&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&EF: Standard Enhanced PCI to USB Host Controller
PCI\VEN_8086&DEV_283A&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D7: Standard Enhanced PCI to USB Host Controller
PCI\VEN_8086&DEV_283E&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FB: SM Bus Controller
PCI\VEN_8086&DEV_284B&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&D8: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_29A0&SUBSYS_00000000&REV_02\3&2411E6FE&0&00: PCI standard host CPU bridge
PCI\VEN_8086&DEV_29A1&SUBSYS_00000000&REV_02\3&2411E6FE&0&08: PCI standard PCI-to-PCI bridge
PCI\VEN_8086&DEV_29A2&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&10: Video Controller (VGA Compatible)
20 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&1F382921&0 : USB Root Hub
USB\ROOT_HUB\4&28EA960E&0 : USB Root Hub
USB\ROOT_HUB\4&2DD613DB&0 : USB Root Hub
USB\ROOT_HUB\4&34A77194&0 : USB Root Hub
USB\ROOT_HUB\4&9EA459D&0 : USB Root Hub
USB\ROOT_HUB20\4&174FF8C8&0 : USB Root Hub
USB\ROOT_HUB20\4&2E713CA1&0 : USB Root Hub
USB\VID_045E&PID_0040\5&22B77046&0&1 : Microsoft USB Wheel Mouse Optical
USB\VID_058F&PID_6362\058F312D81B1 : USB Mass Storage Device
USB\VID_13FE&PID_3100\07A31B00647A68E3 : USB Mass Storage Device
USBSTOR\DISK&VEN_&PROD_PATRIOT_MEMORY&REV_PMAP\07A31B00647A68E3&0: Patriot Memory USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_CF_READER&REV_1.01\058F312D81B1&1: Generic USB CF Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_MS_READER&REV_1.03\058F312D81B1&3: Generic USB MS Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SD_READER&REV_1.00\058F312D81B1&0: Generic USB SD Reader USB Device
USBSTOR\DISK&VEN_GENERIC&PROD_USB_SM_READER&REV_1.02\058F312D81B1&2: Generic USB SM Reader USB Device
15 matching device(s) found.
=============
Input Devices
=============
HID\VID_045E&PID_0040\6&1942EEC7&0&0000 : Microsoft USB Wheel Mouse Optical
1 matching device(s) found.
============
ACPI Devices
============
ACPI\AWY0001\2&DABA3FF&0
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_0 : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_1 : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
ACPI\INT0800\4&3AAE508&0 : Intel(R) 82802 Firmware Hub Device
ACPI\PNP0000\4&3AAE508&0 : Programmable interrupt controller
ACPI\PNP0100\4&3AAE508&0 : System timer
ACPI\PNP0103\4&3AAE508&0 : High precision event timer
ACPI\PNP0200\4&3AAE508&0 : Direct memory access controller
ACPI\PNP0303\4&3AAE508&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0800\4&3AAE508&0 : System speaker
ACPI\PNP0A08\1 : PCI bus
ACPI\PNP0B00\4&3AAE508&0 : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C02\2 : Motherboard resources
ACPI\PNP0C02\4 : Motherboard resources
ACPI\PNP0C04\4&3AAE508&0 : Numeric data processor
ACPI\PNP0C0B\2&DABA3FF&0 : ACPI Fan
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\THERMALZONE\THRM : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
23 matching device(s) found.
============
HDA Audio
============
HDAUDIO\FUNC_01&VEN_10EC&DEV_0885&SUBSYS_103C2A36&REV_1001\4&2DCFB91F&0&0001: Audio Device on High Definition Audio Bus
1 matching device(s) found.
============
RAID Devices
============
PCI\VEN_8086&DEV_2820&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FA
Name: Intel(R) ICH8 4 port Serial ATA Storage Controller - 2820
Hardware ID's:
PCI\VEN_8086&DEV_2820&SUBSYS_2A36103C&REV_02
PCI\VEN_8086&DEV_2820&SUBSYS_2A36103C
PCI\VEN_8086&DEV_2820&CC_01018A
PCI\VEN_8086&DEV_2820&CC_0101
Compatible ID's:
PCI\VEN_8086&DEV_2820&REV_02
PCI\VEN_8086&DEV_2820
PCI\VEN_8086&CC_01018A
PCI\VEN_8086&CC_0101
PCI\VEN_8086
PCI\CC_01018A
PCI\CC_0101
PCI\VEN_8086&DEV_2825&SUBSYS_2A36103C&REV_02\3&2411E6FE&0&FD
Name: Intel(R) ICH8 2 port Serial ATA Storage Controller - 2825
Hardware ID's:
PCI\VEN_8086&DEV_2825&SUBSYS_2A36103C&REV_02
PCI\VEN_8086&DEV_2825&SUBSYS_2A36103C
PCI\VEN_8086&DEV_2825&CC_010185
PCI\VEN_8086&DEV_2825&CC_0101
Compatible ID's:
PCI\VEN_8086&DEV_2825&REV_02
PCI\VEN_8086&DEV_2825
PCI\VEN_8086&CC_010185
PCI\VEN_8086&CC_0101
PCI\VEN_8086
PCI\CC_010185
PCI\CC_0101
2 matching device(s) found.
Posts found [ 1 to 25 of 36 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.017 seconds, 5 queries executed ]