Here are MY HWIDs for the record. This is an AS5516-wxyz (I don't have the secondary model #s ATM)

=========== 
PCI Devices 
=========== 
PCI\VEN_1002&DEV_4380&SUBSYS_02131025&REV_00\3&2411E6FE&0&90: Standard Dual Channel PCI IDE Controller
PCI\VEN_1002&DEV_4383&SUBSYS_02131025&REV_00\3&2411E6FE&0&A2: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1002&DEV_4384&SUBSYS_00000000&REV_00\3&2411E6FE&0&A4: PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_4385&SUBSYS_02131025&REV_14\3&2411E6FE&0&A0: ATI SMBus
PCI\VEN_1002&DEV_4386&SUBSYS_02131025&REV_00\3&2411E6FE&0&9D: Standard Enhanced PCI to USB Host Controller
PCI\VEN_1002&DEV_4387&SUBSYS_02131025&REV_00\3&2411E6FE&0&98: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4388&SUBSYS_02131025&REV_00\3&2411E6FE&0&99: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_438B&SUBSYS_02131025&REV_00\3&2411E6FE&0&9C: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_438C&SUBSYS_02131025&REV_00\3&2411E6FE&0&A1: Standard Dual Channel PCI IDE Controller
PCI\VEN_1002&DEV_438D&SUBSYS_00000000&REV_00\3&2411E6FE&0&A3: PCI standard ISA bridge
PCI\VEN_1002&DEV_7910&SUBSYS_00000000&REV_00\3&2411E6FE&0&00: PCI standard host CPU bridge
PCI\VEN_1002&DEV_7912&SUBSYS_00000000&REV_00\3&2411E6FE&0&08: PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_7916&SUBSYS_00000000&REV_00\3&2411E6FE&0&30: PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_7917&SUBSYS_00000000&REV_00\3&2411E6FE&0&38: PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_791F&SUBSYS_02131025&REV_00\4&14AFA61C&0&2808: ATI Radeon X1200 Series 
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&2411E6FE&0&C0: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&2411E6FE&0&C1: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&2411E6FE&0&C2: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&2411E6FE&0&C3: PCI standard host CPU bridge
PCI\VEN_168C&DEV_001C&SUBSYS_04281468&REV_01\4&1B08A035&0&0030: Atheros AR5007EG Wireless Network Adapter
PCI\VEN_1969&DEV_1062&SUBSYS_02131025&REV_C0\4&2499A833&0&0038: Atheros AR8132 PCI-E Fast Ethernet Controller
21 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&242342D4&0                                   : USB Root Hub
USB\ROOT_HUB\4&3A42705A&0                                   : USB Root Hub
USB\ROOT_HUB\4&EB3FA61&0                                    : USB Root Hub
USB\ROOT_HUB20\4&35C4107A&0                                 : USB Root Hub
USB\VID_045E&PID_0039\5&3B93886&0&1                         : Microsoft USB IntelliMouse Optical
USB\VID_0BDA&PID_0159\20071114173400000                     : USB Mass Storage Device
USBSTOR\DISK&VEN_GENERIC-&PROD_MULTI-CARD&REV_1.00\20071114173400000&0: Generic- Multi-Card USB Device
7 matching device(s) found.
 
============= 
Input Devices 
============= 
HID\VID_045E&PID_0039\6&80104D5&0&0000                      : Microsoft USB IntelliMouse Optical
1 matching device(s) found.
 
============ 
ACPI Devices 
============ 
ACPI\ACPI0003\4&839A984&0                                   : Microsoft AC Adapter
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_124\_0              : AMD Athlon(tm) Processor TF-20
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\PNP0000\4&839A984&0                                    : Programmable interrupt controller
ACPI\PNP0100\4&839A984&0                                    : System timer
ACPI\PNP0103\4&839A984&0                                    : High Precision Event Timer
ACPI\PNP0200\4&839A984&0                                    : Direct memory access controller
ACPI\PNP0303\4&839A984&0                                    : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0800\4&839A984&0                                    : System speaker
ACPI\PNP0A08\1                                              : PCI bus
ACPI\PNP0B00\4&839A984&0                                    : System CMOS/real time clock
ACPI\PNP0C01\4&839A984&0                                    : System board
ACPI\PNP0C02\3&2411E6FE&0                                   : Motherboard resources
ACPI\PNP0C02\4&839A984&0                                    : Motherboard resources
ACPI\PNP0C04\4&839A984&0                                    : Numeric data processor
ACPI\PNP0C09\4&839A984&0                                    : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\SYN1B1D\4&839A984&0                                    : PS/2 Compatible Mouse
ACPI\THERMALZONE\THRM                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Uniprocessor PC
25 matching device(s) found.

27

(14 replies, posted in DriverPack Mass Storage)

I trust this BSOD is of the Error 7B variety (inaccessible boot device)?

I have used nLite for years and would be happy to assist in your troubleshooting efforts.

In my experience, it's not WHAT you do that determines success or failure, it's THE ORDER YOU DO IT.

Feel free to share the Readers Digest version of your process here or email me directly. More eyes see better, farther, faster.

I usually do my nLite thing and do NOT integrate drivers, only using it to perform unattended setups and system tweaks and configuration changes. I NEVER use nLite to remove any drivers (just foreign keyboards and languages), only turn off certain services and change MS default settings, as well as slipstream update packs and (very rarely) add-ons.

I always use a fresh virgin install flat, never nLiting it more than once, then lastly integrate DriverPacks as needed. I return to nLite to generate the .ISO file that I test in VirtualBox and finally burn to optical media.

I hope I wasn't TOO brief in my description. I've walked this path many hundreds of times, so I'm sure to forget SOMETHING. I am working on a much more detailed treatment of how to use nLite and DriverPacks and will publish it (hopefully) very soon. I'll be certain to provide details here.

Best wishes on your project, and thanks for helping me "pay it forward."


MARK STRELECKI

I have an Acer Aspire 5516 (I'm assuming it's some kinda relative to the 5515 and 5517 models) and I fixed my AHCI problems by using the latest UNRELEASED Mass Storage pack (DP_MassStorage_wnt5_x86-32_909r6.7z) as this seems to have the driver needed to boot this puppy when the BIOS is set to AHCI mode.

This laptop is an AMD TF-20 64-bit CPU with 2GB RAM, purchased at Best Buy on sale for a measly $279 plus tax. It is NOT a great performer, has no webcam, but it DOES have onboard ATI video which seems better than that Intel poopoo that came on my other Acer (6930).

Details aside, I sweated for a LONG time trying to locate a driver, so THANK YOU to the DriverPacks Crew for having my back covered. Now YOU know where to get what you need!

Best wishes from cooler, Falltime Atlanta, GA.


MARK STRELECKI

alto -

One more thing:

You might slipstream SP3 into XP and then save that so you don't need to do it each time you run nLite. I've used nLite to do nothing else than slipstream service packs. You CAN do one thing at a time with it, too. <grin>

Do your nLite thing all the way up to making the ISO, quit, and do your DriverPacks thing, then return to nLite to make your ISO. That's how it works for me.

There is a lot more detailed directions out there if you will look for them (hint - GOOGLE IS YOUR FRIEND "nLite and DriverPacks").

You can do this. It's not hard.

Keep us advised as to your progress.

Best wishes from sunny and warm Atlanta.

MARK STRELECKI

alto -

Overflow is a very busy man, and he has instructed you correctly. READ and Ye Shall Learn.

The reason for my response is to say two things:

1. The BASE and Mass Storage Packs (including TEXT MODE) are sufficient to do what you've mentioned.

2. DO NOT REMOVE OLD WINDOWS DRIVERS with nLite. DriverPacks are meant to augment, not replace, these old drivers, and there is little benefit in doing so. My years of nLiting suggest that the fewer things you Remove from your install media, the better you'll be able to support a wider variety of hardware. It's OK to turn OFF an option like a service, but do yourself a BIG favor and DON'T REMOVE STUFF.

If you're making an nLite disk for a particular system, by all means hack away if that works for you. But for broader utility, be very sparing in your removals and stuff should just work better.

Good luck in your endeavors, and thanks for asking. Gives the oldtimers a chance to prove some worth. <grin>

MARK STRELECKI

I've found drivers for the SMBus to be included with the Intel chipset installation, downloaded from the Intel website.

Hey, I like to use and want to use DriverPacks for everything, but sometimes my "detective half" takes over and I just go huntin'.....

<grin>

Best wishes from a thawing Atlanta, GA.

I have used nLite AFTER DriverPacks integration, but ONLY to make an ISO file:

1. Run (Wi)nLite to make changes to source folder.
2. Run DriverPacks to integrate drivers including 3rd party, if desired.
3. Run nLite and ONLY select MAKE ISO option (no other changes after DriverPacks integrated).
4. Burn ISO as image file and go off to the races.

I've done it this way at least a hundred times and it always works.

Heck, with the great support available here, how could any of us get it wrong? <grin!>

Thanks again to the whole team. When I'm not learning from you, I am entertained, at least.

Best wishes from Atlanta, GA.

MARK STRELECKI
http://www.strelecki.com

33

(41 replies, posted in Vista / 7 DriverPack Graphics B)

download link not working as of 4PM ET 2-6-09.

Thank you for all your hard work!!!


MARK STRELECKI

34

(11 replies, posted in DriverPack Mass Storage)

Just a note from the peanut gallery.

Recent Dell XP Pro setup CDs ALREADY have support for systems that support SATA controllers in AHCI mode.

I ran into this previously while setting up a similar Dell, and I'm working around it again as I type this as I make another new Dell-generic Windows XP Pro SP3 setup disk.

I spoke with Dell "Gold" support yesterday, to discuss what I needed to do to backrev/"downgrade" a Vista Business OEM Dell laptop (Latitude D630 - nice little box!) to XP Pro, and I was told something VERY interesting: you can use ANY recent Dell WinXP Pro setup CD to install on ANY Dell system and you will not be asked for a Product Key, and it will (supposedly) pass activation without incident.

Imagine my surprise when I took a peek at the Dell CD with WinLite and saw (gasp!) the Product Key field was ALREADY FILLED IN!

Seems that those pesky Dell setup CDs already have their Product Key act together, so be aware of that while building your customized media, pilgrims. I wrote that key down and can re-enter it on the Unattended page in nLite if and when I need to do so. Of course, my Dell systems have a sticker on the case with their very own Product Key and I normally use that when I do my bare metal clean installs.

To address this topic's challenge, I suggest slipstreaming any/all of the wonderful DriverPacks EXCEPT Mass Storage, and see how that works for you. That's what I'd do, and I'm sticking to my story.

OK, I'm gonna go be quiet again, now.

Please return to your regularly scheduled forum activities, until next time.....



MARK STRELECKI
DriverPacksLand
Outside Atlanta GA. USA

Your method works OK if a REINSTALL (clean install) is needed, and it is a bit complicated.

Fred Langa documented a REPAIR procedure which can be used to update and refresh an XP install without loss of settings or user data:

http://www.informationweek.com/news/win … =189400897

I have used my customized XP install media to repair many sick and ailing systems that needed to be fully operational in the least amount of time, and it has always worked as Fred outlines it.

Just BE CAREFUL whenever you're doing this level of system re-engineering. Read twice, install once.

Thirds, a great article and thank you for your gracious efforts to enlighten us.


MARK STRELECKI

36

(15 replies, posted in Hardware)

Here's how I setup a new box:

Create customized install media. For XP I use nLite and slipstream SP3 and Ryan Vandermulen's RVM Update Pack for SP3 1.02.

I then add ONLY the Driver Packs Mass Storage drivers, text mode and GUI (two check boxes in DPs_BASE), and create a Stand Alone Drivers (SAD) disk with ALL the Driver Packs including some of the wonderful 3rd Party packs.

I create CDs of XP with SP3 and RVM updates and DP Mass Storage, Stand Alone Driver CD, and a third disk with most important apps.

The XP install CD will (thanks to Driver Packs!) boot and support these latest laptops that use SATA drive controllers in the new AHCI mode.

After XP is complete, I insert the SAD CD and install all the drivers my system could ever need.

Lastly, the APPS CD makes the system completely ready to run, all updated and slick as...., well, you know how cool that is.

Overflow Jeff is right - there is a proper sequence you must use to make this magic work properly.

Do some research, study it a bit, then begin testing until you get it the way you want.

You can do this - and it'll be a great lesson that you'll use over and over again each time there's a new PC to setup.

Best wishes from cold Atlanta, GA.


MARK STRELECKI
DriverPacks True Believer
IT Warrior Emeritus.

37

(22 replies, posted in Vista / 7 DriverPack WLAN)

404 File Not Found - is there a different URL for this baby?

Thanks and greets from Atlanta GA. USA.

MARK STRELECKI

38

(36 replies, posted in News)

Merry Christmas and Happy, Safe and Healthy Holidays from Atlanta, GA. USA.

Rain expected on the holy day, but none o' that white stuff.

Thank you to all the wonderful folks who have freely given their time and masterful expertise to provide me with the unequaled majesty we know as the Driver Packs.

We've got just under four hours before Christmas here in the eastern US, so I'm off to begin celebrating.

God bless us all and may we all have a wonderfully prosperous and peaceful 2009.


MARK STRELECKI

39

(34 replies, posted in News)

Holey Moley, Batdudes!

Since I recently acquired a fine Acer lappytop that came with Vista X64 installed, I would love to volunteer for this latest chapter in the Driver Packs development saga.

I am using both 32-bit and 64-bit Vistas in my experimentation to see which works better for this mobile Core2Duo machine. I like the X64 platform if for no other reason I can see all 4GB installed RAM.

I am gonna continue to hit the XP DP's hard with any releases you provide, so don't think I'm looking for "extra" work. <grin>

For the record, I'm a big user of Nuhi's nLite and vLite proggies, UBCD4Win, and of course, the world famous Bâshrat the Sneaky Driver Packs. Plus, I've been around the mulberry bush quite a few times since starting my programming and computing career in 1975. Were any of you folks even around in 1975??? <grin more>

OK, there it is. If you think I can help, I'll be there for you. It's the least I can do for such a great group of nerds who've helped me more than I can say.

Best holiday wishes from a VERY chilly (but sunny) Atlanta, GA. (It was 17 F this morning, wind chill 6 F)

I hope to clarify Overflow's thinking a bit.

There is NO NEED to change the compression format of the existing files. I am in total agreement with Fragbert that these files should be copied over to HD BEFORE they are expanded (like he says during OEM setup somewhere - I was thinking during the early text mode file copy phase of Windows setup), so they exist on the MUCH faster HD medium for subsequent extraction and processing.

Let's keep this as simple as we can, and leverage the most work from past efforts.

Same .7z files, just copied (early on, if possible) to HD prior to extraction.

Besides, I always hated seeing those thin little windows at 1st GUI boot saying "extracting x of y" that seemed to take SO long.....

Gosh, this next release is shaping up to be a real HUMMER, baby. SAD, "M3", better BartPE support (??), and mucho more drivers. I'm feeling a bit faint.

Can you say "butter my backside and call me a BISCUIT!"

Yeah, it's THAT kinda happy thing you got going here. I'm loving the ride, too.

Thanks again from another IT Warrior Emeritus in Atlanta, GA.

Yes, Fragbert.

Yes!

CD/DVD transfers ARE slowed VERY much over HD transfers, and small files take MUCH longer to transfer from optical drives to hard drives. It has always been so.

Your idea of copying the (highly) compressed .7z files to HD for subsequent extraction is a REALLY GOOD IDEA.

Jeff, you are also right on to remind us that storage capacity is FAR greater than it ever was, so it makes sense to have a decompressed flat of driver files somewhere on the HD for easier/quicker access by the driver installation application.

I dunno why I just jumped right in here, but Fragbert has a really good idea that will decidedly improve the user experience and should not require y'all to do any kind of major re-architecting of the otherwise sterling Driver Packs executable.

Heck, I'm still wrestling with X64 challenges, both with XP and Vista, and all the headaches that come with downgrading a new system from Vista back to tried-and-true XP, whether X64 or X86. It's a shame you can get a great deal on a Core2Duo laptop ($599) and be stuck in the cold with only Vista X64 driver support from a MAJOR hardware vendor (hey sir, ya know what I mean? Rhymes with "hey sir".)

If it weren't for you guys, this IT Warrior Chief would be outta luck and stuck with the terribly slow and bloated OS they call "Vista".

Thanks for all your hard work. I'm hoping y'all can pull off a small miracle and give us all a truly wonderful holiday gift of your latest and greatest handiwork. You're my heroes, plain and simple.

Best wishes from balmy, rainy Atlanta, GA.

MARK STRELECKI

Greets from Atlanta, GA.

Haven't heard very much about y'all's progress for the BASE or Packs other than Graphics.

So, "How ya doin'?"

High fives to all of you for keeping up on a monumental undertaking, to say the least.

Much respect and more anticipation from a Big Fan down south!

Thank you and have a Happy Thanksgiving.

Mark Strelecki, Atlanta, GA. reporting as ordered, Sir! <grin>

OK, here's what I did.

I used DPs_BASE_81102RC and DP_MassStorage_wnt5_x86-32_810H.7z and I was SUCCESSFUL in creating a UBCD4Win/BartPE plugin. I then used UBCD4Win (current version) to author a new ISO and it worked without complaint.

So, I guess this one does get to move to the DONE stack. And well done it was! Thank you again.

I noticed that when I made the plugin previously, I must have specified all DriverPacks because the Base folder in the plugin folder has a Driver Packs folder with ALL the .7z files in it. If they aren't being used, why are they being copied to the BartPE/UBCD4Win plugin location? And would it be better that IF we decide to make a BartPE plugin that ONLY the DriverPacks that are compatible show as available options on the page we select them from? And when I regenerate the plugin, I'm asked if I want to delete the BASE, but the existing DriverPacks are not deleted or the user asked if they should be deleted. Curious minds NEED to know these things.

So, when might other Driver Packs be made to work as BartPE/UBCD4Win plugins (if ever), and when will the next Base version and all the updated DriverPacks be released? And what about the Vista Generation - do you think there will be a BartPE/UBCD4Win that works on the Windows 6 platform, or will y'all just do the driver support thing for tools like Vlite (Vista version of nLite)?

(Those Southerners are NEVER satisfied, darnit.)

If there is anything else you need from this corner, just holler. I'm happy to help you advance your technology and make it work so I have a great tool in my own Bag of Tricks. (Actually I call it my Utility Belt, but that's just me.....)

Best wishes from sunny and warm Springtime in Atlanta, GA. USA.


MARK STRELECKI

Thank you kindly for the DP Base update - I checked it and it seems to work OK for making a S.A.D. disk. I will duplicate prior testing parameters later.

BUT....

In the file named "DP_Install_Tool.cmd" the spelling of the word Preparing is incorrect ("Prepareing").

Yeah, I know. Nitpicker. What can I say - I call 'em like I see 'em.

Y'all have a GREAT technology and it works wonderfully well to make those other tools we Digital Warriors need every day.

As soon as this economy shakes loose, I'm sending part of it back to you all as tribute for jobs well done!

Best wishes from another soldier on the front line of the technology wars.


MARK STRELECKI
Atlanta, GA. USA
"I Make It Go."

If that means just putting the SAD disk into the drive automagically runs the driver installation application, then Heck, YES!

It's gonna be the default action to use a SAD resource, right?

Save us pros the clicks and the newbies the heartache of screwing something up. <grin>

Perhaps a wizard dialog appears saying CLICK NEXT TO INSTALL ALL DRIVERS or something simple and powerful like that.

A secondary screen in the wizard might prompt for the classes of drivers, copied from the list of Driver Packs, to be installed.

And some option for updating/improving already installed drivers if a newer/better one is in the DriverPacks.

Hey, it's just an idea, and I could be wrong, but that's my story and I'm stickin' to it.

SAD is just such a freakin' HAPPY idea that I..... oh, nevermind.... I'm getting carried away, now....

Thank you for all the great work you're doing and giving it away for free. Driver Packs Rock.



MARK STRELECKI
Atlanta, GA.
"I Make It Go."

I love your attitude, thanks for the pleasant response.

I am using the latest UBCD4WIN 3.20.

HWID readout for the Dell Latitude E5500 laptop:

=========== 
PCI Devices 
=========== 
PCI\VEN_1180&DEV_0476&SUBSYS_02631028&REV_BA\4&1A998396&0&08F0: Ricoh R/RL/5C476(II) or Compatible CardBus Controller
PCI\VEN_1180&DEV_0822&SUBSYS_02631028&REV_21\4&1A998396&0&0AF0: SDA Standard Compliant SD Host Controller
PCI\VEN_1180&DEV_0832&SUBSYS_02631028&REV_04\4&1A998396&0&09F0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1180&DEV_0843&SUBSYS_02631028&REV_11\4&1A998396&0&0BF0: Ricoh SD/MMC Host Controller
PCI\VEN_14E4&DEV_1674&SUBSYS_02631028&REV_00\4&2DA1E264&0&00E4: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_14E4&DEV_4315&SUBSYS_000C1028&REV_01\4&84CCC20&0&00E1: Dell Wireless 1397 WLAN Mini-Card
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_92\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_2919&SUBSYS_00000000&REV_02\3&61AAA01&0&F8 : Intel(R) ICH9M LPC Interface Controller - 2919
PCI\VEN_8086&DEV_2929&SUBSYS_02631028&REV_02\3&61AAA01&0&FA : Intel(R) ICH9M-E/M SATA AHCI Controller
PCI\VEN_8086&DEV_2930&SUBSYS_02631028&REV_02\3&61AAA01&0&FB : Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_2934&SUBSYS_02631028&REV_02\3&61AAA01&0&E8 : Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_2935&SUBSYS_02631028&REV_02\3&61AAA01&0&E9 : Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2936&SUBSYS_02631028&REV_02\3&61AAA01&0&EA : Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2937&SUBSYS_02631028&REV_02\3&61AAA01&0&D0 : Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2938&SUBSYS_02631028&REV_02\3&61AAA01&0&D1 : Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2939&SUBSYS_02631028&REV_02\3&61AAA01&0&D2 : Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_293A&SUBSYS_02631028&REV_02\3&61AAA01&0&EF : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_293C&SUBSYS_02631028&REV_02\3&61AAA01&0&D7 : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_293E&SUBSYS_02631028&REV_02\3&61AAA01&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_2940&SUBSYS_00000000&REV_02\3&61AAA01&0&E0 : Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_8086&DEV_2942&SUBSYS_00000000&REV_02\3&61AAA01&0&E1 : Intel(R) ICH9 Family PCI Express Root Port 2 - 2942
PCI\VEN_8086&DEV_2948&SUBSYS_00000000&REV_02\3&61AAA01&0&E4 : Intel(R) ICH9 Family PCI Express Root Port 5 - 2948
PCI\VEN_8086&DEV_2A40&SUBSYS_00000000&REV_07\3&61AAA01&0&00 : Mobile Intel(R) 45 Express Chipset Series Processor to DRAM Controller - 2A40
PCI\VEN_8086&DEV_2A42&SUBSYS_02631028&REV_07\3&61AAA01&0&10 : Mobile Intel(R) 4 Series Express Chipset Family
PCI\VEN_8086&DEV_2A43&SUBSYS_02631028&REV_07\3&61AAA01&0&11 : Mobile Intel(R) 4 Series Express Chipset Family
25 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&1121DEF3&0                                   : USB Root Hub
USB\ROOT_HUB\4&1C6EFE57&0                                   : USB Root Hub
USB\ROOT_HUB\4&248D73&0                                     : USB Root Hub
USB\ROOT_HUB\4&2D9CC754&0                                   : USB Root Hub
USB\ROOT_HUB\4&2FF4ECD&0                                    : USB Root Hub
USB\ROOT_HUB\4&3304F345&0                                   : USB Root Hub
USB\ROOT_HUB20\4&20D1B484&0                                 : USB Root Hub
USB\ROOT_HUB20\4&8AFD7EE&0                                  : USB Root Hub
USB\VID_045E&PID_0047\5&33DC01FA&0&2                        : Microsoft USB IntelliMouse Explorer 3.0
USB\VID_090C&PID_1000\AA04012700007853                      : USB Mass Storage Device
USBSTOR\DISK&VEN_CORSAIR&PROD_FLASH_VOYAGER&REV_1100\AA04012700007853&0: Corsair Flash Voyager USB Device
11 matching device(s) found.
 
============= 
Input Devices 
============= 
HID\VID_045E&PID_0047\6&23FC78A5&0&0000                     : Microsoft USB IntelliMouse Explorer 3.0
1 matching device(s) found.
 
============ 
ACPI Devices 
============ 
ACPI\ACPI0003\2&DABA3FF&0                                   : Microsoft AC Adapter
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_0                : Intel(R) Core(TM)2 Duo CPU     T7250  @ 2.00GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_1                : Intel(R) Core(TM)2 Duo CPU     T7250  @ 2.00GHz
ACPI\PNP0000\4&3468AAC5&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&3468AAC5&0                                   : System timer
ACPI\PNP0103\4&3468AAC5&0                                   : High Precision Event Timer
ACPI\PNP0200\4&3468AAC5&0                                   : Direct memory access controller
ACPI\PNP0303\4&3468AAC5&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0800\4&3468AAC5&0                                   : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&3468AAC5&0                                   : System CMOS/real time clock
ACPI\PNP0C01\1                                              : System board
ACPI\PNP0C01\2                                              : System board
ACPI\PNP0C01\3                                              : System board
ACPI\PNP0C01\4                                              : System board
ACPI\PNP0C01\5                                              : System board
ACPI\PNP0C04\4&3468AAC5&0                                   : Numeric data processor
ACPI\PNP0C09\0                                              : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\PNP0F13\4&3468AAC5&0                                   : PS/2 Compatible Mouse
ACPI\THERMALZONE\THM_                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
28 matching device(s) found.

thank you for your attention as well as your technical chops. I salute y'all.

I just may have relatives I didn't know about up in your part of the lower 48. Who knows?

Apologies for: posting location.  I wanted you to have this info ASAP, especially knowing you want to go RTM on the new build.

I hope to chat with you again soon, and best wishes from ALL the Streleckis. <grin!>

MARK STRELECKI, ACP

Greetings from Atlanta, y'all.

Man I almost pulled out ALL my remaining hair to get this to work.

Challenge:
Create a UBCD4Win disc that can boot a new Dell Latitude E5500 laptop, featuring those oh-so-fancy SATA AHCI controllers. This means creating a UBCD4Win plugin so I can build the disk with what I need.

Approach:
Use latest BASE (8.10rc3 is what I have here) and the latest Mass Storage Driver Pack (DP_MassStorage_wnt5_x86-32_810F1.7z). RESULT: Nope

Revised Approach:
Use current BASE 8.05 with same Mass Storage Driver Pack. RESULT: SUCCESS!

Conclusion:
What I assumed was a problem with the new Mass Storage Pack is really an issue with the BASE 8.10rc3.

Just so you know I HAVE been testing your fabulous work.

And it really does work some serious magic for me.

Thanks again for all the fish, and when will the new BASE be released? This month, next, or....?


MARK STRELECKI, ATLANTA GA.

I've been meaning to register and contribute my experiences with the super Driver Packs but the beta of 8.09 was enough to send me over the edge and here I am.

First, THANK YOU for all the great effort and thought you all put into the DriverPacks and this website. You doing this work allows many others to seem like magicians to the untechnical masses. I am REALLY excited about the new ("Method 3") SAD feature, and that's why I'm writing today.

I did an experiment last night/this morning (yeah, one of **those**) while in the process of clean installing my Toshiba Satellite Pro laptop, and I got errors in the results, so maybe you can educate this ole geezer and point me in the proper direction.

I made my installation media WITHOUT specific drivers for this system (in particular, specific drivers refer to video, audio, wired and wireless networking, and maybe chipset) with the idea of using the SAD Method 3 to install those drivers after the fact. I use nLite and have for many years, so I have a science that works there, and I normally integrate specific drivers for the system I'm clean installing.

I used DPBase 8.09rc1 and ONLY RELEASED DRIVER PACKS (no pre-release packs) and the SOUND driver was not installed by SAD when I got finished. The laptop uses SoundMAX Integrated Digital Audio with this Device ID:

PCI\VEN_8086DEV_24C5SUBSYS_02021179REV_03\361AAA010FD

Perhaps I SHOULD've used the pre-release packs, and I WILL try that soon enough. I just wanted to see if I was doing this part correctly.

Do I understand that SAD will be usable POST-Windows setup to add any drivers for devices that lack them? Is the proper method:

1. Complete Windows setup.
2. Insert SAD DP CD or open folder on hard drive.
3. Run DP_Install_Tool.cmd.

Please feel perfectly free to set me straight if I'm off course. If I can learn the best way to use your great Driver Packs, I will be a VERY happy camper.

Thank you ALL again from the bottom of my heart. I wish you the very best luck in all your journeys.

See y'all around.



MARK STRELECKI