Bâshrat the Sneaky

This install is on a laptop, right? Then that is the reason why the default Microsoft drivers have been installed: the nVidia GeForce Go drivers are NOT WHQL certified. And er, 'Intel SoundMAX' drivers? That would be 'Sony VAIO SoundMAX' drivers, if the download link you posted is correct. After reading your HWIDS.txt file, it seems you're right about that Intel SoundMAX claim... You might explain this... EDIT: in the original topic description you wrote you had this BSOD on two systems, which is why... I understand it now...

All updates requested in this topic have been implemented, as well as some other updates/enhancements. That means the DriverPack MassStorage update is almost ready!

I've always had problems with that function... Another limitation is the inability to use the windows key in your own shortcuts. A solution to that problem is a piece of simple, yet very effective software: HoeKey. I'd recommend it to anyone!

Thank you. This confirms my theory. As a result, your problem should be fixed in the next version of the DriverPacks BASE!

A separate partition for VMWare only is an option, not a requirement. It can have a nice effect on the speed.

I'll check that link when I get back home. That screenshot you posted is indeed your HWID. Could you please tell me which VERSION of the viaMraid.sys driver you're using? Thanks.

ATI Catalyst 5.10a has been released as well. Updated version should be online this weekend.

Could you please post the HWID of that mass storage controller? There's a tool to find your HWIDs in my signature.

A fixed (at least that's what I hope it to be...) version should be online this weekend.

Hehe didn't notice that was also from you Next time please reply to the same topic BEGGING for a reply, but not please don't open a new topic regarding the same issue! Thank you. As for that other topic, you've got a [http://www.msfn.org/board/index.php?s=&showtopic=55184&view=findpost&p=407009]reply (with good news ). Topic closed, to keep the forum clean.

Sorry for the late reply! I think we can conclude the problem lies in the MassStorage controller of that motherboard. I'm currently going through the driver used for it. EDIT: it seems I've added too many HWIDs... In the .inf file 4 HWIDs are listed, while in the txtsetup.oem only one; this implies that only one of them is supported by the driver during textmode setup. Therefor you have this BSOD: your motherboard has the AMD 768 mass storage controller and only the AMD 8111 mass storage controller is supported during textmode setup. This will be fixed in the next version of DriverPacks BASE, which should be ready for release this weekend.

@Shamwari: this method is ONLY applicable if you are using a limited amount of drivers! The reason is simple: DetachedProgram executes it entries and runs concurrently with setup. Drivers will get installed at [T-37]. Combine these two facts and you understand if there are too many drivers to extract (or to copy), driver installation might not find the drivers (any?) it needs!

Are you using RIS? If not, please specify...

I'd recommend Everest Home Edition, that's a very userfriendly program!

Try Quicktime Alternative & Real Alternative

he was installing it on win 2000 Hmmm, didn't notice that. @iomicifikko: the DriverPacks are designed/optimized for Windows XP, please don't use it on Windows 2000 installations unless you KNOW what you're doing!

The easiest is to restart from STEP 2: the copying of the files to your UWXPCD folder!

We're still awaiting your response...

Eh... RogueSpear? EXPLAIN!

Sorry for the late reply! The txtsetup.oem method really is a pain in the ... ! When everything is entered correctly, it's still possible that you get that error #18, without ever finding the cause. And all of a sudden it does work another system! The conclusion: if you are able to, I'd recommend you to use the txtsetup.sif method! P.S.: this question in fact belongs in the Device Drivers forum, so if you still have questions, please start a new topic over there.

No, that is NOT ok... Please enter the default number, it will not be selected automatically if you proceed without entering anything. (If I remember well, I'll check the code when I get home.)

They're both superb! Notepad or Notepad++?

Sorry for the extremely late reply! But I'm kind of ... stunned by your report! These two hardware IDs you reported: PCI\VEN_8086&DEV_24DB&SUBSYS_498015D9&REV_02\3&267A616A&0&F9: IDE Controller PCI\VEN_8086&DEV_24DF&SUBSYS_498015D9&REV_02\3&267A616A&0&FA: RAID Controller ... and this is what you can find in aarich.inf: PCI\VEN_8086&DEV_24DF.DeviceDesc = "Adaptec Embedded Serial ATA HostRAID" PCI\VEN_8086&DEV_25B0.DeviceDesc = "Adaptec Embedded Serial ATA HostRAID" Do you see what I'm talking about? You've got both DEV_24DB and 24DF, while only 24DF is supported by the driver! Could you please confirm this is a) on a non-Intel chipset based motherboard, B) the 'DB' HWID is from an origin different from the Adaptec SATA Host RAID controller. Thanks!

Without DriverPack MassStorage, loading all txtmode mass storage drivers from the CD (cannot be disabled, hardcoded setup routine) takes already more than one minute. If you include DriverPack MassStorage, that will easily increase to 3 minutes and longer... Though this is rather 'presetup' than 'setup', people who have automated the partition selection/formatting part(s) of setup, might have some notifiable reduction in installation time, certainly when these installations are being used in corporate environments. EDIT: P.S.: it's txtsetup.SIF, not txtsetup.INF!