RogueSpear

@gordo, I have run across the problem you described with FFDShow. I am not experiencing the problems on all computers however, so it's hard to nail down the issue at hand. I have the newest build which is 11112005 and I have what is described as a "stable" build from 08082005. I'm going to pack up both of them and post within the next day or so. With builds of this project coming out on what seems like a daily basis latley, I'm tempted to just pack up the recommended stable build and leave it at that.

@BTS, please refer to this post for the hwid for an S3 Twister video adapter not found during setup.

Here is the hwids.txt file generated from a Compaq Evo N115. It has a SoundMax adapter in it and windows setup used to generate a bluescreen until RealTek finally got their crap together. Now it attempts to install the device as a C-Media sound adapter which of course doesn't work. I downloaded the drivers direct from HP and here is the resulting file. Oh.. also, the video adapter does not install either. It's an S3 Twister video chip. So the hwid for that is in this file as well. hwids.txt

It should work from there, though I have not personally tested that method.

Using RyanVM's Update Pack is far superior to using /integrate or any other method I've ever seen. I can't possibly recommend it enough, whether for RIS or optical media. Now as far as upgrading to a newer version - Version 2.0.0 is a clean break from the past. You can't upgrade over a source that used a previous version. The newly released V2.0.1 can be used on top of V2.0.0. Personally, I always go fresh. This is the entire reason I created AutoRIS. Using a fairly modern PC (P4-3.2HT), AutoRIS takes me around a half hour to run and this includes RVM with two addon packs, XPize, and nLite. Not too shabby I think. I've begun work with integrating the BTS Driver Packs using Method 2 and a couple of other things that should hopefully save some time.

No. As stated in the installer description, it can only be run from RunOnceEx. I've tried various methods of getting to install from svcpack.inf and cmdlines.txt, but it won't go. The other problem is that the VBscript won't run from cmdlines.txt because WMI is not yet available. EDIT: I won't be messing around with VMware 5.5 until it's officially released. I have to many other things to do than to mess with their test code that still has all the debugging turned on.

The BSODs aren't caused by the Driver Packs. They caused by hardware vendors that either don't know how to make a proper device driver or they just don't care about following the generally accepted best practices of driver design and driver behavior. When's the last time you ever saw a blue screen having do with anything that Intel makes? It seems to me that around 80% of the complaints of blue screens here are a direct result of hardware made by RealTek or nVidia.

No I can't write a cmd script because the whole process is dependant upon WMI. That's one of the main reasons I started using VBscript for everything.

@coucou, I've never used WPI before so I can't really be of much assistance there. The point of the script itself is that it will NOT run the installer unless the "computer" is a VMware computer. This is determined by using WMI to read BIOS strings. I suppose if WPI can launch a VBscript then you'd be all set.

I haven't had this problem. With some of the .msi files, you will get one instance of an activation. A good example is Eraser. The first time you right click anything in Explorer, the msi routine will kick in. But then that's it, you won't see it again. The only product I seem to be having a problem with these days is Spybot and it's curious since I never had the problem until quite recently. But, this is also why I haven't posted an installer for Spybot. All of the installers, both silent switchless and msi file, I have tested. Some, like FFDShow, I've been repacking for over a year now and haven't had this issue. EDIT: Are you assigning the application to the computer in your GPO? Or to the user?

From what I could see inside of the .msi file, there were maybe 6 to 8 languages supported. If memory serves me correct English, Spanish, French, German, Traditional Chinese, Simplified Chinese. I don't remember if Dutch, Portugese, Arabic, Hebrew, etc. were in there.

That's a prerelease beta or RC of VMware. My installer is for the most recent final version (5.0.0.13124).

Well I included the script because what it does it check the BIOS strings for "VMware", to verify that your install is being done in a VM as opposed to a real computer. For testing purposes, to make sure this thing will work for you, why don't you just hard code calling the file from RunOnceEx, so you know it'll run. Also, I didn't mention this before (probably need to do an edit), but this version of VMware Tools is for the latest release version (V5). I don't know if it would work in earlier versions or the more recent beta releases (V5.5).

That's one I've been using forever now, without a problem. Are you running it from svcpack.inf? Because it wont work from there. It needs to be run from RunOnceEx.

@dgould393, hey you're actually supposed to modify the .SIF file to suite your needs. I threw in the OemPnPDriversPath in there for those who might want it there. That way they wouldn't have to look up which section it needs to go into. Lord knows I could never remember. So I don't mind at all. Also, thanks for the driver. I'll make sure it gets in the next release. @all, currently I'm working on a partial solution to automating the BTS Driver Packs. This is really turning out to be more of a problem of logistics than code. I feel like the instructions are already getting lengthy for a program that does so little. I really need to get this thing ported to AutoIt ASAP so that I can implement a GUI interface and an .INI file to store settings.

Updated 20051107 - Added Crap Cleaner V1.25.201 - Updated FileZilla to V2.2.17 - Added QuickTime Alternative V1.65 - Added Real Alternative V1.45 - Added SpywareBlaster V3.4 - Added SyncBack V3.2.8.500 - Added WinPcap V3.1 Beta 4 - Discovered the single post size limitation I guess I'll be ditching the alphabetical order listing and just start appending as new titles are added.

WMI isn't available during setup at all.

I was thinking more along the lines of setting setup.exe to idle and your AutoIt script to high. Perhaps a double whammy like that could force the issue.

I haven't been closely following this thread, and I've tried to read through and follow everything, but to be honest I don't have everything down that's going on here. Soooo, if this has been brought up, my sincerest apologies. With all of the recent use of pssuspend and pskill, I'm just wondering if using AutoIt's builtin function ProcessSetPriority has been explored here. On it's face, it seems like it would do what you want it to do.

@BTS, I don't know if this is a problem or not as I don't have a system available to test this on at the moment, but I noticed during a Method 1 slipstream that .cab file are compressed. Will this create issues? I don't believe there are too many drivers with .cab files, but there are some. Has anyone tested this out?

Seriously.. some of you people need to do your homework and read a little. The more I get into this stuff and the longer it's been since I started coming around here, the more I realize that about 5% of the people actually do anything or contribute in some way or another to our common cause of creating optimized unattended installations. The rest just seem to take and ask the same questions over and over. I don't have a problem helping people out. Heck I've gotten an incredible amount of help here myself, but the spoonfeeding gets tiring after a while.

It's possible that nLite is not creating the ISO image properly. Personally, I use UltraISO, which I'm not entirely satisfied with but it does create 7GB ISO files for me that burn properly to a DVD. And the DVD installs without issue. There's a lot of options with ISO file creation, most of which I'm really not so clear on. I chose options in UltraISO that seemed to indicate to me the greatest level of compatibility.

Man, I didn't realize it was that bad. Are there any BIOS updates for your mobo? Also have you tried things like disabling USB Legacy Support, RAM shadowing, etc. ?

For clarification, that's a no go with the new V5.11 Chipset DP ? And if so, could you give a description of any error messages / blue screens. I'm going to start calling around to see if I can find anyone around me with an nForce 3 system I can fool around with. I'd love to see all this nForce stuff put to rest.

This sounds like the kind of project that could benefit from teamwork. It also sounds like the type of thing, even with the driver compressor, where it could easily go beyond the size of a regular CD, possibly requiring a dedicated DVD.