robnjay

Yes. Graphics Driver installed OK. BTW... I have another issue with this install on the IBM T30. The sound driver did not install: SOUNDMAX HWID: PCI\VEN_8086&DEV_2485&SUBSYS_05081014&REV_02\3&61AAA01&0&FD I posted this as another topic on this board.... You might have missed it

Did some more nosing around.... It's really a SOUNDMAX..... I looked in my UA's txtSetup for the device ID, couldn't find anything similar (probably didn't do it right ) Thanks Rob

The audio controller on an IBM T30 Laptop was not recognized (I guess), so the drivers were not installed. BTS 6111 M2 GuiRunOnce No KTD Here is the ID: PCI\VEN_8086&DEV_2485&SUBSYS_05081014&REV_02\3&61AAA01&0&FD : Multimedia Audio Controller This is what PC Wizard 2006 says it is: Device Audio : 82801CA/CAM (ICH3-S/ICH3-M) AC'97 Audio Controller FYI...

DriverPacks completely slipstreamed into a fresh Win XP SP2 (slipstreamed SP2) image... I am borrowing an IBM laptop (T30) for testing, so I need to get this on... The install also had a problem with the sound driver (sound card not recognized ?). I'll document that and submit it as another topic...

I used: DriverPack_Graphics_A_V6011.7z DriverPack_Graphics_B_V5111.7z Are there newer versions? Do you ship the latest version of InstallShield with the DP_Graphics packs? ISScript.msi is the InstallShield Scripting engine.... I wonder if the Win XP being installed needs to have a newer version of this than the one that comes with XP SP2 in order to run these ATI drivers.. EDIT: I looked at Bashrat's site, found the Driverpacks Graphics page, and noticed that the version shown for Graphics_A is 6.02. However, when I attempted the download, the file that was being downloaded was "DriverPack_Graphics_A_V6011.7z". Tried it twice....

Bashrat: I got this error message in the Event Viewer from an install on an IBM Laptop: "Product: ATI Catalyst Control Center -- 1: The InstallScript engine is missing from this machine. If available, please run ISScript.msi, or contact your support personnel for further assistance." The video adapter is ATI Mobility Radeon 7500. Integrated .net Framework 1.1 using siginet's program add-on in RyanVM's Integrator (1.05). It was installed by svcpack method. Used GUIRunOnce to install .net 2.0 over the top of 1.1, but this happened after your ATI Catalyst control center install was attempted....

I've got a computer at a friend's house which has the "Insert your Windows XP Service Pack 2 CD" issue following an unattended nstall before I fixed the cmd file and made a new UA cd (thanks to help from this forum). The thing is, I really don't want to reload everything from scratch (all my friend's apps, settings & files have already been copied to the machine). I would assume the easy fix for this is to run KB892559 hotfix (it's bitching about the portcls.sys file version from that hotfix). Problem is, I can't find a download for this hotfix anywhere (I could "call Microsoft" - yuk). Is there any other cute trick to fix this without a reload? Another problem I have with the reload is it's XP Home and he will have to call M$ _again_ to activate the key, even though it's a legal copy. How about finding the (KB892559 V2) hotfix file? Anyone got it? If you have the hotfix file, would you e-mail it to me? Thanks

Ok, so I'm replying to myself, but more proof that it's the Driverpacks.... I took a look at svcpack.inf after RyanVM 2.0.0 (using RVM_Integrator 1.0), then nLite 1.0 RC2. Then I compared it with what happens if I use BTS 5.105 M2, no ktd, GuiRunOnce. Here's what I found: svcpack.inf after RyanVM Integrator, then nLite: **** RyanVM 2.0.0 nLite 1.0 RC2***************** [Version] BuildNumber=2600 MinorVersion=1 MajorVersion=5 Signature="$WINDOWS NT$" [SetupData] CatalogSubDir="\I386\svcpack" [ProductCatalogsToInstall] KB319740.cat KB842520.cat KB870981.cat KB873339.cat KB883523.cat KB884538.cat KB884575.cat KB884868.cat KB884883.cat KB885626.cat KB885835.cat KB885836.cat KB885894.cat KB886677.cat KB886716.cat KB887170.cat KB887173.cat KB887472.cat KB887606.cat KB887742.cat KB887797.cat KB888111.cat KB888113.cat KB888302.cat KB888321.cat KB888795.cat KB889016.cat KB889315.cat KB889527.cat KB889673.cat KB890046.cat KB890463.cat KB890644.cat KB890733.cat KB890831.cat KB890859.cat KB890927.cat KB891593.cat KB891781.cat KB892233.cat KB892489.cat KB892559.cat KB893008.cat KB893476.cat KB893756.cat KB893803.cat KB895961.cat KB896256.cat KB896269.cat KB896344.cat KB896358.cat KB896360.cat KB896422.cat KB896423.cat KB896428.cat KB896626.cat KB896688.cat KB896984.cat KB897574.cat KB897663.cat KB898108.cat KB899337.cat KB899418.cat KB899510.cat KB899527.cat KB899587.cat KB899589.cat KB899591.cat KB900387.cat KB900725.cat KB900930.cat KB901017.cat KB901026.cat KB901122.cat KB901214.cat KB902149.cat KB902400.cat KB902841.cat KB903234.cat KB904412.cat KB904706.cat KB905414.cat KB905519.cat KB905749.cat KB905816.cat KB906472.cat KB906569.cat KB906688.cat KB907865.cat MSXML3SP7.cat scripten.cat [SetupHotfixesToRun] SPYBOT.EXE JAVA.EXE ADOBE.EXE ADAWARE.EXE ********************************************************** svcpack.inf from same image, after BTS DriverPacks, M2, GuiRunOnce, no KTD: *********** RyanVM 2.0.0, nLite 1.0RC2, BTS 5.051 ********* [Version] BuildNumber=2600 MinorVersion=1 MajorVersion=5 Signature="$Windows NT$" [SetupData] CatalogSubDir="\i386\SVCPACK" [ProductCatalogsToInstall] KB319740.cat KB842520.cat KB870981.cat KB873339.cat KB883523.cat KB884538.cat KB884575.cat KB884868.cat KB884883.cat KB885626.cat KB885835.cat KB885836.cat KB885894.cat KB886677.cat KB886716.cat KB887170.cat KB887173.cat KB887472.cat KB887606.cat KB887742.cat KB887797.cat KB888113.cat KB888302.cat KB888321.cat KB888795.cat KB889016.cat KB889315.cat KB889527.cat KB889673.cat KB890046.cat KB890463.cat KB890644.cat KB890733.cat KB890831.cat KB890859.cat KB890927.cat KB891593.cat KB891781.cat KB892233.cat KB892489.cat KB893008.cat KB893476.cat KB893756.cat KB893803.cat KB895961.cat KB896256.cat KB896269.cat KB896344.cat KB896358.cat KB896360.cat KB896422.cat KB896423.cat KB896428.cat KB896626.cat KB896688.cat KB896984.cat KB897574.cat KB897663.cat KB898108.cat KB899337.cat KB899418.cat KB899510.cat KB899527.cat KB899587.cat KB899589.cat KB899591.cat KB900387.cat KB900725.cat KB900930.cat KB901017.cat KB901026.cat KB901122.cat KB901214.cat KB902149.cat KB902400.cat KB902841.cat KB903234.cat KB904412.cat KB904706.cat KB905414.cat KB905519.cat KB905749.cat KB905816.cat KB906472.cat KB906569.cat KB906688.cat KB907865.cat MSXML3SP7.cat scripten.cat [SetupHotfixesToRun] SPYBOT.EXE JAVA.EXE ADOBE.EXE ADAWARE.EXE After BTS, KB888111.cat & KB892559.cat are missing from svcpack.inf!

Bâshrat: I have an unattended install that I've built using nLite 1.0RC2, RyanVM 2.0.0, and BTS 5051. When I run the install without adding the driverpacks, everything is fine. After the DP's I get a WFC error. In "Windows\System\setuperr.log" is this: Error: Setup detected that the system file named [c:\windows\system32\drivers\portcls.sys] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. Is this from your hotfix for HDA, or from anything else installed by the Driverpacks? If not, I'll ask Ryan and Nuhi about this... BTW, what other means can I use to get a list of any files WFP is complaining about? I ran SFC /scannow, but it just keeps throwing up the "Files that are required for Windows to run properly have been replaced by unrecognized versions" dialog, with the option to retry, cancel, etc. and no real info. [Edit 11/3] I've done some more sleuthing. Deep in a log file named "SetupAct.log" there is this: This file may be necessary to maintain system stability. Setup detected that the system file named [c:\windows\system32\drivers\portcls.sys] is not signed properly by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability. Setup detected that the system file named [c:\windows\system32\drivers\portcls.sys] is not signed properly by Microsoft. This file could not be restored to the correct Microsoft version. Use the SFC utility to verify the integrity of the file. Am I making some mistake with this build? [Edit 11/3 #2] Ok, I'm getting a real education here... On the computer with the installed image and the WFP error "svcpack.inf" has no reference to either kb888111 or kb892559. I've found that you are using the portcls.sys from kb982559 - shouldn't there be at least a reference to this hotfix (probably both??)

Use 7-Zip to extract all the driverpacks into a directory. If you are using a DVD the driverpacks will fit. If you are using CD-R's, everything but WLAN fits nicely. I have used 2 CD-R's to make one driverpack CD for everything but WLAN, and another one for WLAN driver. What I am asking for is a way for the CD or to detect what drivers are installed, and install (or better yet give the option to install) the associated tools. BTW this would come in handy for WLAN drivers as well as the Graphics/Sound drivers....

I've tried to search this forum for this, but I couldn't find it... I would like to build a DVD I would name "Every Freakin Driver". This thing would have Bash's DriverPacks on it (expanded). The way I would envision it working is: Install unknown POS hardware item (your friend/customer has an unmarked Elbonian-made Video Card, etc.)... When Windows finds it, tell Windows you "Have Disk" and give it your "Every Freakin Driver" CD - Windows finds the driver and loads it (This is the easy part - already done this, comes in mighty handy). Next is the harder part.. After Windows loads the driver, AutoRun the CD again, it runs some subset of Bashrat's .cmd files, finds the appropriate sound/video control panel and installs the mixer, system tray app, etc. I know this is a really simplistic approach, but has anyone done this (or anything even better)?

Had a problem with 2 attachments.... Here's the 2nd one. This is really the txtsetup.oem file - had to rename it TXTSETUP.txt

OK I'll attach the txtsetup.oem as well... Winxp.7z

Bashrat: I think you are missing a part of this... Even though your txtsetup.sif says my HWID is a "viamraid", when the computer boots to the very first part (Formatting the partition) it sees a "visraid", and I get a BSOD after the boot to GUI mode (really the 3rd restart). I have to change the txtsetup.sif file to make my HWID a "viasraid". Then it boots correctly into GUI mode setup (no BSOD). When I boot from a vanilla WXPCD and use "F6" and insert the MSI RAID driver floppy, it sees a "viamraid" on the very first restart (again, the partition format), and proceeds through the install (no BSOD). That's why I called it a "split personality"... which one should it really be?? Here's an excerpt from txtsetup.sif for a BSOD: [HardwareIdsDatabase] PCI\VEN_104B&DEV_1040 = "vmscsi" PCI\VEN_1106&DEV_4149 = "viapdsk" PCI\VEN_1106&DEV_3149&SUBSYS_80ED1043&REV_80 = "viasraid" PCI\VEN_1106&DEV_3149&SUBSYS_71421462&REV_80 = "viasraid" PCI\VEN_1106&DEV_3149&SUBSYS_70201462&REV_80 = "viasraid" PCI\VEN_1106&DEV_3149&SUBSYS_59011462&REV_80 = "viamraid" PCI\VEN_1106&DEV_3149&SUBSYS_1419147B&REV_80 = "viasraid" PCI\VEN_1106&DEV_3149&SUBSYS_04701462&REV_80 = "viamraid" PCI\VEN_1106&DEV_3149 = "viamraid" PCI\VEN_1106&DEV_3164 = "viamraid" PCI\VEN_1106&DEV_3249 = "viamraid" Given this, why does the computer come up to the Format partition part of textmode seeing the partition as a "viasraid"? Here's another excerpt from the same txtsetup.sif file Check this out: [SourceDisksFiles] hdaudres.dll = 100,,,,,,,2,0,0 hdaudio.sys = 100,,,,,,,4,0,0 hdaudio.inf = 100,,,,,,,20,0,0 hdaudbus.sys = 100,,,,,,,4,0,0 hdaudbus.inf = 100,,,,,,,20,0,0 hdashcut.exe = 100,,,,,,,2,0,0 hdaprop.dll = 100,,,,,,,2,0,0 vmscsi.sys = 1,,,,,,4_,4,1,,,1,4 viapdsk.sys = 1,,,,,,4_,4,1,,,1,4 viasraid.sys = 1,,,,,,4_,4,1,,,1,4 viamraid.sys = 1,,,,,,4_,4,1,,,1,4 So the question is, does the VERY first part of textmode setup use the [HardwareIDsDatabase] section? Or not? Thanks Rob

Bashrat: Hidden in my thread here is something both VoYaGeRTM1977 and I may have stumbled across, with different RAID controllers. He is using a SI 3112 and I am using a VIA 8237. In my case, I have noticed that the 8237 appears, in the first textmode reboot (drive format step) as _either_ a "viasraid" _or_ a "viamraid", depending upon whether I use the MSI floppy (F6) in a standard install (it's a "viamraid") or my UWXPCD with BTS driverpacks (it's a "viasraid"). Obviously the HWID hasn't changed.... He might be having the same problem with 3112 and 3112r..