RogueSpear

Update - 20060228 Updated Windows Live Messenger to V8.0.0566

I haven't begun work on these latest Adobe releases as of yet, but I can tell you that in the case of Adobe Acrobat Pro 7 and Photoshop CS2, that removing the custom action worked just fine. It then allowed me to activate online upon first running the app. Perhaps Adobe really really wants you to activate during the install and they changed the way their installs operate now.

I made a full version installer recently. The installer only associates audio files, but I left the video capability in there for those who want it.

Update - 20060228 Added Desktop Sidebar V1.05.111 Removed Macromedia Shockwave Player There were some problems with the Shockwave installer so I removed it until I have a chance to look it over and fix it. In the meantime I'm sure there are plenty of other Shockwave installers out there.

Well I've run into the exact same problem as you with RIPrep. It seems like sometimes it works, sometimes it doesn't. It really seems like a half baked addon to RIS itself and with the new WIM technology Microsoft is developing I doubt that they're going to pay much more attention to it.

In one of the scripts you had to enter in the Admin name and password in order for that to happen. If I remember correctly, I commented the area with instructions to put in your name and pass. If you don't want it to do that, simply replace the name and password with nothing but a double quote "". The reason I put it in there is that there is always something that I want to do when the install is finished. It's been literally over three years since I've bothered to mess around with RIPrep. Once I figured out that everything can be done with scripts and group policy, I abandoned all efforts with it. Given the choice I will always go with a real install.

@coucou, I have up QuickTime and Real Alternatives, FFDShow, and AutoGK (which contains XviD among other things). That's about as far as I'm going with it. The only thing additional I'm working on is the DivX web player.

@Shigadeyo, I hate to say it but probably no. I have so much going on right now that it's a struggle just to keep up with what's here already. Besides the installers here, I also have to maintain as least as many which I don't post. These are mostly commercial apps or proprietary programs for work or clients. At some point soon something is going to have to give and unfortunately new titles here is probably going to be first. Also updates to existing titles may not show up here the week they're released from the developer either. Luckily some others here at MSFN have started to release more and more installers, most notably Shark007. He's been putting out some really excellent work lately.

I've spoken with nuhi about running nLite in an unattended fashion using the command line to call on a preset .ini file, but I think it's not at the top of his priority list. There may be more to implementing that feature than would seem likely. From what I've heard from BTS, he will be supporting all manner of automation with his next generation of slipstreamer. I'm really looking forward to it as I think it will make things go much smoother in AutoRIS.

Yea I'm going to have to rework all of the scripts with better error trapping. They depend on some utilities that I had in my Update Addon Pack, which has been discontinued. Things like SysInternal's PageDefrag and a little utility called NTRegOpt.

You mean this problem went away ?

I am providing links to my hosting because Panasonic makes you register an account in order to download drivers Thought that I'd spare you that On a side note, also here is a driver for a NeoMagic 256 video adapter. Not sure if you want to support yet another video device. Sound Driver Video Driver hwids_ToughBookCF_27.txt

Well if you can tell me at what point the BSOD pops up, it would certainly help. Also, BTS recently updated most of the Driver Packs, including DP Sound which has newer RealTek drivers.

Are you are getting BSOD during the PnP device installation portion of the setup? If so does the target computer have an Analog Devices SoundMAX in it?

Yes it's very strange. nLite reports very odd image sizes for me too. I just updated my main RIS image this morning with AutoRIS and it reported a size over 900MB. After so long I pretty much ignore this. Regarding Driver Packs. What I do is use the M2 helper addon with the RVM Integrator and then just plop all of the Driver Pack .7z archives into $OEM$\$1. Keep in mind that you will not have any additional mass storage device support using this method. But in the few locations where I do support RIS, I've never needed it either. Generally speaking I would assume most corporate / government environments won't be implementing any crazy desktop RAID solutions. If you need to support deploying Windows Server 2003 via RIS, then that could be another matter.

Appears to be a Broadcom adapter: Dell TrueMobile 1180 MiniPCI on a Inspiron 8200. Driver Link hwids_Inspiron8200.txt

Update - 20060225 Added Microsoft Web Services Enhancements V2.0 SP3 and V3.0 (multi-installer) Updated InstallShield Script Engine to include V10.5 Updated Paint.NET to V2.6 Updated Real Alternative to V1.47 Updated SyncBack to V3.2.10.0 Updated Winamp to V5.2 Additionally, I made available QuickTime Alternative V1.67 since there are quite a few people (me included) who are having difficulties with V1.68. I believe the problems with V1.68 stem from Apple's crappy V7.0.4 release of QuickTime. So anyway, both V1.67 and V1.68 are available for download.

Perhaps I should have explained a little better. Lately I've been taking to putting all of my drivers on the DVD. I run the first half of a Method 1 so that they get cabbed up and then plop the "D" directory in the root of the DVD. What I actually run in the setup is a Method 2, pointing SetDevicePath.exe at %CDROM%\D. I know this is an unsanctioned menthod of driver integration, but it seems to work pretty nice and saves a bit of time. The other benefit is that if you leave the entries made by SetDevicePath.exe, all you need to do is pop the DVD in when you plug in a new device.

Deleting drivers is going to be rather problematic for those who read the drivers off of a DVD.

No, the example .ini file for nLite will not make that automated unfortunately. I've exchanged a couple of PMs with Nuhi about implementing a command line option for nLite. Hopefully that will find it's way into a release before too long. Also, I've tried to automate the whole procedure by calling AutoItX from within AutoRIS, but some of the dialogs are simply not capable of being manipulated. Specifically the dialog where you load an .ini file. The main reason I included the sample file was to show people what I remove from the image. Keep in mind that the drivers I supply with AutoRIS will only allow you to do a RIS boot and get through the text mode portion of the setup. You'll still need to follow one of the "normal" procedures for integrating drivers. The easiest is to use the M2 helper addon I supply with AutoRIS. It needs to be used in conjuction with the RVM Integrator. Then all you have to do is download Bashrat the Sneaky's Driver Pack LAN and put the .7z archive file inside of $OEM$\$1.

muiz I'm well aware of when updates are released. I've got a subscription list about a mile long at both FileForum and Softpedia.

Yes, RIS does not look for WINNT.SIF in i386. It looks for .SIF files inside of \Templates. Now I can't stress this enough: use a virgin, untampered with, unmodified XP SP2 CD to make the initial image. When RIS sucks all the files off of your CD and contructs the initial image, it doesn't give a hoot what you've got inside of $OEM$. If you were to use a CD that had hotfixes integrated via RVM or some other process, it will most likely copy those down, but like I stated previously I can't predict what all will happen. As best as I can tell, RIS has a static list of files it copies down from the CD, some of them RIS will uncompress or "decab". If you mess with the initial source I think you're only asking for trouble. This is really the point of AutoRIS. To take that initial pristine image, back it up first, then mess around with it. If you make a mistake just run AutoRIS again. You won't have to be bothered with the "insert the CD then make image" phase of things. I've had the same image on my server pretty much since SP2 was released. I just have AutoRIS copy it down and mess with the copy, not the original.

As per your AutoRIS.ini settings above, you have OEM set to No. You need to set it to Yes in order for the $OEM$ folder to be copied over. RIS does not use a WINNT.SIF file per se. It uses anyfilename.sif files. You can have a half dozen of them if you like, they just need to be placed in the \Templates subdirectory of your RIS image. I included support for RVM in AutoRIS because indeed it makes deployment of domain member workstations much easier, faster, and secure. At this point, with version 2.0.3, there is one known issue and that has to deal with msi.dll or something like that. Essentially if you run an install routine that is Microsoft Intaller based, the dialog boxes disappear after you set it off an running. This has no effect on GPO application deployments and it seems to be a problem on Microsoft's end rather than Ryan's. But if the issue is a serious one for you, Ryan released an Addon that will revert the file to an older one which does not exhibit the problem. If you have AutoRIS launch VMware or VirtualPC, you'll need to restart the BINL service on the RIS server prior to performing a RIS boot with either of those products. In the end, you will need to restart the service on the server no matter what, before you can sucessfully deploy workstations. And yes, the drivers I provide should work just fine. Precisely That code is the compression of .inf and .pnf files. It will only run if you have Optimize=Yes in the AutoRIS.ini file.

The fellow who was using 2003 SBS reported the same problem. I'm guessing there's some sort of additional security measure on 2003 that was never implemented on 2000. I'll implement an option in the .ini file to not restart the BINL service in the next release. Maybe put in yet another popup that instructs the user to restart it themselves then click OK. EDIT: for the time being you could just comment out the line so there is no attempt to restart the service.

You know what, I think BTS run_me.cmd may in fact be deleting filecase.exe as a part of it's cleanup process. If you copy filecase.exe over to system32 or somewhere in the path, that should clear up that issue. Now another thing you may have noticed is that the first time you run AutoRIS against a particular RIS image is that it creates a backup of the image on the RIS server for future use. Look for the directory i386-Original. I did this so that you wouldn't have to be continually making a new RIS image from the CD. Again, I'm not quite sure how XPcreate works, so perhaps that could be a difference here, but the RIS image you make from the source CD should be a SP2 integrated image with nothing else at all. That's the point of having RVM integration built into AutoRIS. If you're making any modifications to the original image, then I can't predict what will happen as AutoRIS was designed to start out with an SP2 image that is untouched in any other way. I'm not going to try and sell you on Ryan's update pack, but if you check out his web site, read the FAQs, etc., you'll find that there isn't any voodoo involved. It's actually quite straight forward what's going on and IMHO it's without question the best way to get your source up to date. I understand your hesistance in that you want to know exactly what's going on. That's my problem with nLite; I don't know every little thing that's going on. But nonetheless, I use it anyway to remove a few minor components in the interest of better workstation security and also I find it an easy way to implement some registry tweaks.