mc134

Here is a VB script that i wrote last year and posted to this forum to turn on the network icon but to ignore the 1394 devices. I use this in my batch file to run it... ECHO Turning On Network Connection Icon(s) ECHO. ECHO Please wait... start /wait %systemdrive%\install\Network\NetworkIcon.vbs ECHO. networkicon.rar

Just to let everyone know, the port.sys error that people are getting on laptops can be worked around. When you get the bluescreen restart the machine and the install will finish. The only difference is in device manager the sound card will have a yellow exclamation point beside it. I have installed 5 or 6 different laptops using the sound driver and this works for me. BTW...I wanted to thank bashrat once again for continuing to work on the driver packs because without him I would still be limited to installing only a few machines without downloading hundreds of drivers.

The error that i got was caused by corruption in my i386 directory so the extract command was not working properly. Fixed the problem and it installed correctly. Thank you for your quick reply.

Found error in sound pack (newest build of all packs and base) because the cr.exe is never extracted so the script errors out. I extracted it and it installs perfect. Just to let you know. I also had the problem with the updater going into a loop that never stops.

I have a dell machine that has a perc controller on it and the winnt.sif looks like this: [unattended] NtUpgrade=no OverwriteOemFilesOnUpgrade=no FileSystem=ConvertNTFS OemPreinstall=yes ConfirmHardware=yes ExtendOemPartition=20907 OemFilesPath="c:\dell\$oem$" OemPnPDriversPath="Dell\PnP\m\co;Dell\PnP\Storage;Dell\PnP\Storage\Mraid35x;Dell\PnP\N\Intel;Dell\PnP\N\BC;Dell\PnP\Mgmt" TargetPath=\windows OemSkipEula=yes [MassStorageDrivers] "Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers"=OEM [OemBootFiles] txtsetup.oem afamgt.sys perc2.sys perc2.cat perc2.inf perc2cin.dll perc2evt.exe perc2mgt.inf raidisk1 Here is a copy of the txtsetup.oem contents: [Disks] d1 = "Dell PERC 2, 2/Si, 3/Si, 3/Di Windows 2000/2003 Device Drivers", \raidisk1, \ [Defaults] scsi = perc2 [Computer] [scsi] perc2 = "Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers", perc2 [Files.Scsi.perc2] driver = d1, perc2.sys, perc2 catalog = d1, perc2.cat inf = d1, perc2.inf inf = d1, perc2mgt.inf driver = d1, perc2cin.dll, none driver = d1, perc2evt.exe, none [Config.perc2] value = "", Type, REG_DWORD, 1 value = "", Start, REG_DWORD, 0 value = "", Group, REG_SZ, "SCSI miniport" value = "", ErrorControl, REG_DWORD, 1 value = Parameters\Device, NumberOfRequests, REG_DWORD, 0fe value = Parameters\Device, UncachedExtAlignment, REG_DWORD, e [HardwareIds.scsi.perc2] id = "PCI\VEN_1011&DEV_0046&SUBSYS_13649005", "perc2" id = "PCI\VEN_1011&DEV_0046&SUBSYS_13659005", "perc2" id = "PCI\VEN_1028&DEV_0001&SUBSYS_00011028", "perc2" id = "PCI\VEN_1028&DEV_0002&SUBSYS_00021028", "perc2" id = "PCI\VEN_1028&DEV_0003&SUBSYS_00031028", "perc2" id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D11028", "perc2" id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D91028", "perc2" id = "PCI\VEN_1028&DEV_000A&SUBSYS_01061028", "perc2" id = "PCI\VEN_9006&DEV_2140&SUBSYS_21409006", "perc2" id = "PCI\VEN_9005&DEV_00C5&SUBSYS_00C51028", "perc2" id = "PCI\VEN_1028&DEV_000A&SUBSYS_011B1028", "perc2" id = "PCI\VEN_1028&DEV_000A&SUBSYS_01211028", "perc2" The weird thing is that the txtsetup.oem is not in the oem directory, it is right on the root of the C drive. All of the other files are inside the dell\pnp\storage directory. Maybe this is the missing puzzle piece that will fix this problem?? Bashrat, If you think it will help, i can compress these files and send them to you for comparison with the 3ware drivers.

My unattended XP quit working on my VIA based motherboard after integrating the newest Mass storage pack. I have finally narrowed it down to the files in this directory: UWXPCD_ROOT\DPfiles\DP\M\V\2 It totally kills the unattended portion of the install. When the install is finished it ends up with half of an operating system. No Program Files, most of the Windows folder is missing but the drivers from WINNT.SIF are installed. There is something wrong with these drivers. I tried it on 3 different VIA based motherboards and it failed on all three (2 of them are older VIA chipsets). So if your unattended stops working, you can blame it on these VIA drivers.

Remove those lines because you will never notice a speed increase only problems like you are having.

No, thank you for taking the time to put these wonderful packs together for us. Just trying to help out.

After installing the newest sound driver pack (Much thanks to Bashrat) the Creative Audigy 2 driver worked great but the control panel didn't work. I created this control panel silent install and added it to bashrats' sound pack and it installed correctly and works!! Wanted to share it with everyone else and hopefully Bashrat can integrate it into his packs. Download the silent install below (It is made from the newest Creative driver in the pack v. 1.84.55) and place it in the UWXPCD_ROOT\DPfiles\DP\S\CR folder and then change the Sound_Control_Panel.cmd to what is in bold: @ECHO OFF IF EXIST %WINDIR%\CMDOW CMDOW @ /HID REM#################################### SET D=%SYSTEMROOT%\system32\drivers\ SET C=%SYSTEMDRIVE%\DP\S\ SET S=%SYSTEMROOT%\system32 REM#################################### IF EXIST %D%ctaud2k.sys %C%CR\CTZAPXX.exe /S IF EXIST %D%ctaud2k.sys %C%CR\CtPanel_Silent.exe IF EXIST %D%P17.sys START %C%CR\LS\CTZapxx.Exe /S IF EXIST %D%nvapu.sys START %C%N\AudioUtl.exe IF EXIST %D%FM801.SYS START %C%T\1\Setup.exe /S IF EXIST %D%cmaudio.sys START %C%T\3\T_3.exe IF EXIST %D%TT1724ht.sys START %C%T\4\T_SSU.exe IF EXIST %D%dmxsens.sys START %C%T\5\T_DMX.EXE IF EXIST %D%envysens.sys START %C%V\V_ENVY.exe -y -o%S% IF EXIST %D%viaudios.sys START %C%V\V_VINYL.exe -y -o%S% IF EXIST %SYSTEMROOT%\system32\VPatch.exe START %S%\VPatch.exe IF EXIST %D%SMWDM.SYS START %C%SM\SM.exe -y -o%S% EXIT Hope this helps everybody!! CTPanel_Silent.exe

Probably a BIOS limitation instead of a Windows one. Try going to Maxtor and downloading the MAxBlast program. It is a work-around to this limitation. I have used this in the past with success. Hope this helps.

The reason that the two commands error out is that they are compressed along with the drivers. I just decompressed them and the error went away.

Error is caused by an error in the BTS_DriverPacks_slipstreamer.cmd file Change to what is in bold: REM ### Cabs all driver files ### ATTRIB -R -A -S -H /S /D %FOLDER%\DPfiles ROBOCOPY "%FOLDER%\M1" "%CD%" CABfiles_M1.cmd /MOV /NS /NC /NFL /NDL /NP /NJH /NJS START /WAIT CABfiles_M1.cmd DEL /Q CABfiles_M1.cmd ECHO _ Drivers compressed with CAB compression...

I have it so just PM me if you want me to send it to you.

I have been using this method for about 6 months now and it works great. Add this to your batch file: ECHO. ECHO Installing TweakUI 2.10 Powertoy ECHO Please wait... start /wait %systemdrive%\install\PowerToys\TweakUI.msi /QB ECHO. Of course have the Tweakui.msi in the right folder and then add this to your registry tweaks so that it is added to control panel: ;Show TweakUI in Control Panel [HKEY_CLASSES_ROOT\CLSID\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}] @="TweakUI" "InfoTip"="Start TweakUI" [HKEY_CLASSES_ROOT\CLSID\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}\DefaultIcon] @="%SystemRoot%\\\\System32\\\\tweakui.exe,0" [HKEY_CLASSES_ROOT\CLSID\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}\Shell] [HKEY_CLASSES_ROOT\CLSID\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}\Shell\Open] [HKEY_CLASSES_ROOT\CLSID\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}\Shell\Open\command] @="tweakui.exe" [HKEY_CLASSES_ROOT\CLSID\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}\ShellFolder] "Attributes"=dword:00000030 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{D14ED2E1-C75B-443c-BD7C-FC03B2F08C17}] @="Tweakui of the system control adds"

The hpt3xx driver was for another motherboard that I had problems with (BSOD). I got it working with this configuration also. The ulsata2 driver was actually needed on this motherboard when i hooked a drive to the VIA controller so windows xp would find the SCSI driver for the promise controller. Weird, huh? If i hook a drive to the promise controller it only shows this: VIA SATA RAID Controller (viamraid.sys) WinXP Promise SATA378 IDE Controller (ulsata.sys) When I hook a drive to the VIA controller is shows three devices!! VIA SATA RAID Controller (viamraid.sys) WinXP Promise SATA378 IDE Controller (ulsata.sys) Promise SATA Console SCSI Processor (ulsata2.sys) I have messed with this problem for way too long so i really don't care why its working I'm just glad it is!! One more thing: If i hook a drive to only the VIA controller and leave the ulsata2 driver out of my dvd, windows has a question mark for the promise controller. If i include ulsata2 windows finds everything on the frst try.

After 5 weeks of working on the Promise Driver problem I have finally got it working flawlessly. I have an Asus A8V Deluxe Motherboard with the Promise 20378 SATA Controller on it as well as the VIA SATA controller. Using Bâshrat the Sneaky's Mass Storage Driver Pack the VIA would install everytime but the promise would always fail to detect. This is how i got it working no matter which controller that you attach the drives to. This solution is not perfect but it works for me!! Here is my TXTSETUP.SIF Config [SourceDisksFiles] hpt3xx.sys = 1,,,,,,4_,4,1,,,1,4 ulsata.sys = 1,,,,,,4_,4,1,,,1,4 ulsata2.sys = 1,,,,,,4_,4,1,,,1,4 fasttrak.sys = 1,,,,,,4_,4,1,,,1,4 viapdsk.sys = 1,,,,,,4_,4,1,,,1,4 viamraid.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1103&DEV_0004 = "hpt3xx" PCI\VEN_1103&DEV_0005 = "hpt3xx" PCI\VEN_1103&DEV_0005&SUBSYS_100415BD = "hpt3xx" PCI\VEN_1103&DEV_0006 = "hpt3xx" PCI\VEN_105A&DEV_3373&SUBSYS_80F51043&REV_02 = "ulsata" PCI\VEN_105A&DEV_3373&SUBSYS_80F51043 = "ulsata" PCI\VEN_105A&DEV_3373&CC_010400 = "ulsata" PCI\VEN_105A&DEV_3373&CC_0104 = "ulsata" PCI\VEN_105A&DEV_3D75 = "ulsata2" PCI\VEN_105A&DEV_3D18 = "ulsata2" SCSI\ProcessorPromise_SATA_Console____ = "ulsata2" PCI\VEN_105A&DEV_5275 = "fasttrak" PCI\VEN_105A&DEV_7275 = "fasttrak" PCI\VEN_1106&DEV_4149 = "viapdsk" PCI\VEN_1106&DEV_3149 = "viamraid" PCI\VEN_1106&DEV_3149&SUBSYS_80ED1043&REV_80 = "viamraid" PCI\VEN_1106&DEV_3149&SUBSYS_80ED1043 = "viamraid" PCI\VEN_1106&DEV_3149&CC_010400 = "viamraid" PCI\VEN_1106&DEV_3149&CC_0104 = "viamraid" PCI\VEN_1106&DEV_3164 = "viamraid" PCI\VEN_1106&DEV_3249 = "viamraid" [SCSI.Load] hpt3xx = hpt3xx.sys,4 ulsata = ulsata.sys,4 ulsata2 = ulsata2.sys,4 fasttrak = fasttrak.sys,4 viapdsk = viapdsk.sys,4 viamraid = viamraid.sys,4 [SCSI] hpt3xx = "HighPoint HPT3xx ATA100 Controllers" ulsata = "WinXP Promise SATA378 (tm) IDE Controller" ulsata2 = "Promise SATA Console SCSI Processor" fasttrak = "WinXP Promise MBFastTrak133 Lite (tm) Controller" viapdsk = "VIA ATA/ATAPI Host Controller" viamraid = "VIA Serial ATA RAID Controller" I only have the ulsata and the ulsata2 drivers in the same folder. The problem all along was the promise drivers not playing nice with one another. I think the problem is actually the "fasttx2k" driver but i have not tested to see if this is the actual culprit. You can leave all of the drivers included in bashrats mass storage alone but i chose to remove the other promise drivers because i got tired of seing the BSOD! Hope this helps everyone having problems with Promise drivers!!

Bâshrat, Yes I get the control panel icon but it gives me the same error as Snakesnake when i click on the control panel icon. I used method one just in case it matters.

Bâshrat, I have a Creative Labs Audigy 2 PCI and with your sound driver pack, the driver gets installed correctly but the control panel does not work (and yes, I have sound). Have you made any breakthroughs with this problem? No hurry but I thought that you should know. And by the way, thank you so much for the amount of effort that you have put into making these packs perfect.

I do not turn off system restore in my unattended xp. I was wondering why so many people were having problems with such a simple application. Learn something new everyday!

Download the media connect installer (wmcsetup.exe) place it in a folder: $OEM$\$1\Install\MediaConnect and add this to your batch file: ECHO Installing Windows Media Connect Software Update ECHO Please wait... start /wait %systemdrive%\install\MediaConnect\wmcsetup.exe /Q ECHO. This must be done after .Net framework and Windows Media Player 10. Works everytime.

Thank you prathapml for your quick response. I will try another build with signed drivers and will post back.

I integrated the nvidia drivers using the OEMpnpDriversPath method and when the install was done they were installed but no nVidia control panel or tray icon. When you go to device manager it says nvidia on the driver manufacturer and the driver version number is number 71.21. There must be something else that needs to be done. Any help would be appreciated.

Go to http://www.laptopvideo2go.com and download the newest drivers. Should fix your problem. One more thing to do is to check your refresh rate and make sure that it is set to 60Hz.

I have discovered that by using the registry tweak to fix the logitech and microsoft keyboards f-Lock problem if you don't have one of those keyboards the registry fix kills the function keys. I discovered this after installing three laptops. Here is the key that i am talking about... ;Reverses F-Lock key for new Microsoft and Logitech keyboards (Not for use on Laptops) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout] "Scancode Map"=hex:00,00,00,00,00,00,00,00,19,00,00,00,3b,00,3b,e0,3c,00,08,e0,\ 3d,00,07,e0,3e,00,3e,e0,3f,00,3f,e0,40,00,40,e0,41,00,41,e0,42,00,42,e0,43,\ 00,43,e0,44,00,23,e0,57,00,57,e0,58,00,58,e0,3b,e0,3b,00,08,e0,3c,00,07,e0,\ 3d,00,3e,e0,3e,00,3f,e0,3f,00,40,e0,40,00,41,e0,41,00,42,e0,42,00,43,e0,43,\ 00,23,e0,44,00,57,e0,57,00,58,e0,58,00,00,00,00,00

The 169.254.x.x IP address range is reserved for IP Autoconfiguration. When the installed NIC is configured...it defaults to DHCP. When you log onto a network it then attempts to find a DHCP service. If it can't find one... the IP Autoconfig feature kicks in and assigns it a random ClassB IP address using the subnet 169.254.x.x . If the NIC is defaulting to a 169 address, that means that it is not finding your default gateway (Router or Modem)