RogueSpear

Well it certainly looks fine.. are you also putting the two .cmd and two .reg files in $OEM$ ?

I can tell you with absolute confidence that Mhz was correct in stating that it goes into $OEM$ and that setup will look for it automatically. Perhaps the contents of your cmdlines.txt file has errors in it and that's why it's not working.

Yea that's a pretty bad hotfix. RyanVM decided not to include it in his update pack for good reason. It seems to screw up a lot of things. I sure hope that Microsoft works this one out sometime soon because the premise of the hotfix is here to stay. Only thing that could change it now is an unlikely court ruling. I would simply avoid using the hotfix as it does not address any security issues nor does it fix any bugs.

Another thing is that you can call an AutoIt script against the AutoIt interpreter (correct phrase?) or compile it into an executable file. The latter can be handy since you don't always know what computer you're going to run the script on. This way you don't need any runtimes at all. Just double click.

I wish people here in the states paid as much respect to organizations like those. It's not uncommon to have to try booting a remote machine twice and restarting the BINL service. I even put in an artificial pause of 30 seconds after the service restart to try and avoid such situations. I usually don't have to boot twice anymore, but I do have to wait an inordinate amount of time before the VM will DHCP. Microsoft TechNet Script Center - This has a lot of good examples and tutorials.VBscripting.com - An excellent site, but it can be hard to find what you're looking for sometimes. Code Comments - This has to be the mecca of programming web sites. Unfortunately I get a "Server too Busy" message more than 50% of the time. If they would appropriately boost server capacity, it would be an amazing resource. Win32 Scripting - Some of the examples in their repository are simply mind blowing. They are incredibly useful, but at the same time they also make you want to hang it up because you know you'll never reach the point where your entire thought process is in binary... or whatever it would take to come up with some of the Rube Goldberg like creations they have.

I use a Logitech mouse, but I only use the driver, not their software. I've never found mouse and keyboard software all that useful, but it usually swallows up a good chunk of RAM.

I've never quite liked the idea of "keeping" so many drivers, so I made a script that only keeps the directories I chose. In my case, that would be drivers supporting hardware that uses USB, FireWire, or PCMCIA. The attached download contains a VBscript and an .ini file. I have tested this on multiple computers now and have plugged in various USB devices. It even properly detected and installed the Logitech driver for my Logitech Bluetooth Travel Mouse when I paired it up. In the .ini file are options for your source and destination directories, and whether or not you want to cab the files that can be cabbed. Here are the basic requirments: [KtD] SourceDir=%SystemDrive%\D DestinationDir=%SystemRoot%\D CompressFiles=Yes The value for SourceDir must begin with either %SystemDrive% or %cdrom%. The value is not case sensitive and whatever you put after the variable is up to you.The value for DestinationDir must begin with either %SystemDrive% or %SystemRoot%. The value is not case sensitive and whatever you put after the variable is up to you.The SourceDir and DestinationDir can be the same. The script will simply not perform a copy or move operation if this is the case.If the SourceDir is on the CD, a folder copy operation takes place (takes longer). If the SourceDir is on the hard disk, a folder move operation takes place (much faster).The value for CompressFiles is either Yes or No.The script requires SetDevicePath.exe in order to work and that executable must be located either in %SystemDrive% or %cdrom%\OEM. Either location will work.The script requires that the .ini file be named KtD.ini and that it be located in the same directory as the script itself. You can change this yourself if you are handy with VBscript.This should work with Method 1 sources (untested) even if you select CompressFiles=Yes as it will just skip over everything. It will just take longer than if you select CompressFiles=No.The remainder of the .ini file is a listing of directories that you do not want to keep. With the exception of one USB based device in DriverPak Graphics, all other USB devices, FireWire, and PCMCIA devices will be integrated. I also included directories to not keep in the .ini file for some of the Unofficial DriverPacks. Feel free to modify the listing as you see fit, just remember you are listing what you don't want. [KtD-List] ;Chipset C ;CPU CPU ;Graphics G ;Lan L\AD L\AU L\AM L\3 L\B L\BU\1 L\BU\2 L\C\1 L\CO\1 L\CO\4 L\DA\1 L\DA\2 L\D\1 L\D\2 L\D\3 L\D\4 L\D\5 L\D\6 L\D\7 L\I L\IN L\L L\LI L\M L\N\2 L\N\5 L\N\6 L\N\7 L\N\8 L\NV L\O\1 L\R\1 L\S L\SM\1 L\SM\7 L\SM\8 L\SM\9 L\SM\A L\SU\1 L\SU\2 L\SU\3 L\SU\4 L\SU\5 L\SU\6 L\TR L\U\1 L\U\2 L\U\5 L\V ;Mass Storage M ;Sound A S\CR\1 S\CR\3 S\N S\R S\V ;Sound B S\A S\AV S\C S\CO S\CR S\H S\M\1 S\M\C S\M\D S\SC S\S S\SI S\SM S\T S\TR S\Y ;VMware VMware ;WLAN W\3\3 W\AS W\AT W\B\2 W\B\5 W\B\9 W\B\A W\BL\8 W\BL\9 W\BR W\BU\5 W\CR\2 W\D\3 W\D\6 W\D\7 W\D\B W\D\D W\DE W\E\4 W\E\D W\E\E W\E\I W\G\1 W\G\2 W\I\2 W\LI\1 W\LI\2 W\LI\3 W\LI\4 W\LI\5 W\LI\7 W\LI\8 W\LI\9 W\LI\A W\LI\B W\LI\F W\LIT W\M W\N\4 W\N\5 W\N\6 W\N\7 W\RE\1 W\RE\2 W\SE\3 W\SI\1 W\SIT\9 W\SIT\A W\SIT\C W\SM\3 W\SM\4 W\SM\A W\SU\1 W\SU\2 ;Misc X\C X\F X\P X\R ;HID Z\A Z\M Z\P Z\S MD5 for attached file: 372BFDDAF72B3E53F9239FCCACE46CA8 KtD.7z

Some day or another I'll probably get a PayPal donation thingy set up. I've just been too caught up in other things and I never really planned on making anything out of all this anyway. If you wanted to make a small donation to the SPCA, Humane Society, etc. I'm not sure what organizations of that type they have in the UK. That would be fantastic though I'll be putting out V2.01 shortly. I've spent the last two weeks pretty much doing nothing but working on my post install scripts and at this point they're starting to look shiny. Also, there will be a few updated NIC drivers, including experimental support for nForce NICs.

Hmm.. I made a Java installer myself. Knowing Ryan, I'm guessing he made his similarly to how I made mine. Basically, just a few tweaks to the .msi file. It's one of the more straight forward installers to make and not much different than running whatever you get from Sun themselves. Regarding .NET 2.0. I believe someone made an installer that will do it from svcpack.inf, but it's just the original installer from Microsoft compressed - which is quite large. Most of the switchless silent installer you'll find out there for .NET 2.0 are compressed administrative installation point installs. This makes for a much smaller install file. The downside is that there is a known issue - known to Microsoft - that prevents that type of installer from working within svcpack. It's really not too big of a deal as installing it from RunOnceEx works just fine. I'm hoping that when Microsoft releases an update to the .NET 2.0 runtimes, they'll address this issue. It's been quite a while now since the initial release, so perhaps it will be before too long.

Great.. this probably means the control panel applet is an .msi that will require the ISE runtime. Similar to what ATI has done.

At this point, I can't think of any reason to use Method 1 other than you are only integrating drivers specific to one single computer.

From the reading I do here, it seems given the choice most people do in fact pick svcpack.inf when it's available. I specifically chose to install as many applications as possible from svcpack.inf. Indeed, some do not support this functionality, but the majority do. It is especially convenient to install applications that require a reboot before they start to function because then they are available after Windows finishes off the GUI portion of setup. Further, applications installed from svcpack.inf apply all of the user registry entries to the Default User profile.

; Disable the tray icon for hardware devices [HKEY_LOCAL_MACHINE\SOFTWARE\Intel\Display\igfxcui\igfxsrvc\TrayIcon] "ShowTrayIcon"=dword:00000000 ; Intel Extreme Graphics [HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\Display\igfxcui\igfxtray\TrayIcon] "ShowTrayIcon"=dword:00000000 ; Intel Extreme Graphics 2 [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NvCplApi\Policies] "TaskbarUIPolicy"=dword:00000000 ; nVidia GeForce [HKEY_CURRENT_USER\Software\Realtek\HDAudio] "ShowIcon"=dword:00000000 ; RealTek HD Audio [HKEY_LOCAL_MACHINE\SOFTWARE\Avance\AC97 Audio\ALSMTray] "ShowIcon"=hex:00 ; RealTek AC97 Audio It's little more than what you asked for, but there it is...

I run tons of VBscript from RunOnceEx. Here is a little piece of my VBscript that I run from cmdlines.txt to set it up: If fs.FileExists(OEM & "\060_VPN.vbs") Then ws.RegWrite strKeyPath & "060\", "VPN software" , "REG_SZ" ws.RegWrite strKeyPath & "060\1", OEM & "\060_VPN.vbs", "REG_SZ" End If If fs.FileExists(OEM & "\070_VMwareTools.vbs") Then ws.RegWrite strKeyPath & "070\", "VMware Tools" , "REG_SZ" ws.RegWrite strKeyPath & "070\1", OEM & "\070_VMwareTools.vbs", "REG_SZ" End If There's no need to make an SFX or compile it or anything. The only real limitation is with cmdlines.txt. From there you must specify cscript.exe.

I'm not sure what you're getting at there, but I'll attempt to reason things out. With RIS installs, you're not using a CD or DVD. I suppose technically you could pop one in there, but that would defeat half the purpose of RIS itself. So all of your files need to be placed in $OEM$\$1 in order to make it to the hard disk. So you need to look for SetDevicePath.exe and WatchDriverSigningPolicy.exe in both places. It seems like introducing For loops, to what is otherwise a fairly straightforward script, is unnecessary. And I doubt it would improve performance to any noticeable degree. Like I said, I'm trying to cover all the possible scenarios that I either use or have run across.

Old: If Left(objBIOS.SerialNumber(i),6) = "VMware" Then If fs.FileExists(OEM & "\VMWareTools.exe") Then ws.Run(OEM & "\VMWareTools.exe"),0,True End If New: If Left(objBIOS.SerialNumber(i),6) = "VMware" Then If fs.FileExists(OEM & "\VMWareTools.exe") Then ws.Run(OEM & "\VMWareTools.exe"),0,True Else If fs.FileExists(OEM & "\VMWareWorkstation.exe") Then ws.Run(OEM & "\VMWareWorkstation.exe"),0,True End If

IMHO Analog Devices and Microsoft are as much to blame in this fiasco. The BSOD as far as I know, only happens on computers with a SoundMAX audio adapter and for some reason Analog Devices has seen fit to make 29 dozen different HWIDs for the exact same audio chipset. Granted it's the presence of a RealTek device driver coupled with the presence of the Analog Devices sound chip. Personally I think they both suck a**. I really long for the days of Creative Labs dominance in this particular hardware category.

DriverPack Modem V1.8 /D File size: 6.89MB MD5: 40C503A2506806BCC3F9CFB797BC0C12 Last updated: 20060331 Notes: Who ever made V1.7 made it from updating V1.5. I consolidated the changes from V1.6 and V1.7. One more Conexant driver was added that should support most HP-Compaq laptops. I did not make an html support file for this DriverPack like I did with Broadband. Nobody has commented one way or another about it, so I'm going to assume that it's not a worthwhile endeavor. A couple things to keep in mind if you're going to submit an updated DP: Make sure you are updating the latest version of that particular DriverPack.Do not cab any of the files. This makes the .7z file larger and it could interfere with Method 1 integrations.Do not include the original self extracting executable that just contains all of the files which are in the directory anyway.If at all possible, please try to weed out the files which are not specifically used by the driver's .inf file.

I did this quite a while back. I believe you throw the extra directory parallel to \i386. I ended up removing the image because nobody ever used the Tablet features (and half the pens got lost too). So now they just get regular XP.

The only thing I can see different here is that according to the instructions, they're telling you to copy far more than just the .inf and .sys files of the driver. There's also a couple of .dll files, an .exe and one other misc file. Perhaps it will work. I've read here before that nForce4 NICs have a MAC address of all zeros by default? If this is the case I really fail to see how the NIC could communicate in any fashion at all until one is programmed in. EDIT: Just for the heck of it, I'll throw these drivers in with an update of AutoRIS. Who knows, maybe this set from Tyan will do the trick.

To be totally honest, I have no idea what "-aoa" denotes. I first saw it probably two years ago and it's always worked for me. So I figured why break it When you decompress the DriverPack .7z files to your hard drive, they end up in directory off the root of %SystemDrive% called D. So most of the time you're going to end up with C:\D. The script allows for you to have the drivers already decompressed, but residing in the root of your CD/DVD, thus the line %CDDRIVE%\D. I do so many different kinds of installations and I do in fact use CD, DVD, and RIS (not all at once obviously). It just started to get cumbersome managing different files for different installs, so I've started to make everything modular, autodetecting, etc.

This started out similar to my previous experiences with Dell Inspiron and Latitude laptops. Unfortunately this one did not finish properly. Like the Dells, when the video card is detected during setup, the screen goes all haywire and you can't see a thing. With the Dells, the screen eventually cleared up and I was able to finish things off after pointing to some files in the DriverPack directory tree. With this HP-Compaq, the screen never did clear up. It did seem to finish off the GUI portion of setup though as the computer rebooted. Unfortunately when the computer got back up and running, the screen was still all garbled. I tried this twice, but eventually I just had to get the laptop up and running (it's my work laptop), so I had to remove the Graphics DriverPacks. I'm attaching the HWID file just in case that helps you in anyway. I can't give you any other specifics because the screen was completely unreadable. And for my last bit of bad news - I won't be able to do any further testing on this particular laptop. As I stated earlier it's my work laptop and I use the thing all day every day. hwids_nx9010.txt

It detected as a RealTek AC97 with the yellow exclamation point on it. I'm guessing the HWID just needs to be added to a driver already in the DriverPacks. EDIT: Here is the driver page. It looks like the driver covers nx9000, nx9005, and nx9010. hwids_nx9010.txt

If you want a GUI interface, take a look at DameWare NT Utilities. It does quite a bit more than just WOL, but's a pretty slick and easy package. Been using it for years and don't let the "NT" in the name disuade you, they've just never bothered changing the name.

I'm not sure anyone has ever sucessfully PXE booted using an nForce NIC. You may have to go out and buy some cheap PCI NICs.