blinkdt

Perhaps, do you have "Disable Script Debugging (Internet Explorer)" checked in IE's Tools-->Internet Options-->Advanced set of features? That might turn the trick.

Doc, wouldn't you need a fuller reference to the location of the file, for example: cmd1[pn]=['%cdrom%\\Programs\\ColorPic.exe'] ?? Seems the path is a little barren and therefore Windows can't locate the file.

It's installing now but I'm off to bed. Will post a quick result in the morning. I saw something in a recent nLite forum thread regarding registry tweaks, Nuhi talking about "locking down" something-or-other for stability reasons. I guess I will have to step back to manual SP slipstream and hotfix integration if this doesn't work. The ability to add app-by-app reg tweaks via WPI is just too important to my install routine. ;-------------------------------------------- Edit: who's foolin' who, there's no way I'm hitting the sack. Yes, it worked. My reg files now merge silently again after adding the tweak via Cmdlines! Thanks, K!

@kelsen... Bizarre, I just rebuilt my CD--used nLite to integrate SP2 and apply RyanVM's Lite pack--and now none of my registry entries are merging. Period. Not from WPI nor if I manually merge the reg file. But the settings DO take if I manually configure the app or setting! Been searching the forums and have seen a few others suffering the problem, but no solutions. Three culprits have come to mind while researching this: GDI Detection Tool, RyanVM's pack/nLite, and/or the Data Execution Prevention feature, but I can't wrap my mind around this one. I do note that I have always applied my Quick Launch tweak from Cmdlines.txt and it continues to work. Do you think that applying your fix above at that stage will allow for later merging of .reg files when WPI runs?

@lionhrt You can read up on my method for creating an autorun WPI disc, together with scripts, HERE. Good luck.

MPC comes bundled in a variety of forms. I install it as part of the K-Lite Codec Pack, for example. Does a great job of playing DVDs, but although I use /regvid I'm still prompted to select MPC as my preferred player when inserting a DVD. Only after I manually configure Options-->Formats-->Autoplay to play Video and DVD will it load up by default. Another thing I like to do is launch the movies in fullscreen. But I would rather not configure all of this manually. I expect all of this could be done with some registry settings imported during unattended after the install? Looks like a job for RegSnap.

Also, check your config.js file for duplicate or nonsequential ordr[pn]= entries. I have experienced the problem you describe and have traced it to duplicate entries.

I don't really understand what benefit an "always on top" feature would provide. WPI creates an instance of RunOnce and then disappears. Your AutoIt scripts (and mine) are then exposed during the app installs as RunOnce counts them down. Unless you mean you want WPI to stay around during the installs, hiding the RunOnce Window as well. That could be kinda cool. Maybe add a funky progress indicator, like the Windows install itself? Hmmm.

Discussion Removed.

Discussion Removed.

Discussion Removed.

Don't know about the extra fonts, but it is easy enough installing ATM Pro 4.1 using standard Installshield methods. Create the .iss file by running the installer with the following flags: -a -r -f1C:\setup.iss Copy setup.iss to the directory containing setup.exe and run with the /S switch. Works for me.

Discussion Removed.

Discussion Removed.

@orustom Nice and clean. Very nice, thanks for posting.

Dunno, bonedaddy. What specifically is it you like about W.A.I.T. over WPI?

Yes, there appears to be a method endorsed by prathapml, which is good enough for me, as posted on THIS PAGE of the longer DirectX9c thread. Get the DirectX9c redistributable HERE. Use WinRAR to extract the files, then your runonce entry might look like this: REG ADD %KEY%\015 /VE /D "DirectX9c" /f REG ADD %KEY%\015 /V 1 /D "%systemdrive%\install\Applications\DirectX9c\dxsetup.exe /silent /noreboot" /f Change the directory structure to match your placement of the files, of course. Hope my earlier comments did not offend, I was feeling a little yappy last night. Let us know how it goes.

Touche, MHz. And thanks for the code, I'll give it a try.

Hold it. You are operating your own forum, working on your MCSE, and have a hand in nLite, but silently installing DirectX and MSN Messenger are throwing you for a loop. With all due respect, could it be a language issue? I don't envy any non-native speaker who tries to wade through this forum. That said, the DirectX threads have gotten out of hand, I would agree. But if I recall correctly, it is included with SP2, although you may want to reduce the size. You certainly do not need to do any Hex editing, just unpack the files and run dxsetup.exe with the /silent switch if you are working with Win2K or some such. As for MSN Messenger 6.2, here's what I do: 1) get the installer and run it, but stop at the first dialog box. Don't actually install, right? Instead, go to Windows Explorer and locate C:\Documents and Settings\Administrator\Local Settings\Temp directory. You should find the file "MsnMsgs.msi" in there somewhere. Copy it onto the desktop. Then cancel the install, you want only the .msi file. 2) install the .msi with the /qn switch using your preferred method (batch, runonce, wpi, etc.). That's it. I also add the following registry entry: Windows Registry Editor Version 5.00 ;Remove MSN Messenger From Startup [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "MsnMsgr"=- ;Stop MSN Messenger from Running on Windows Startup [HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger] "AppSettings"= hex:22,04,00,00 And don't discuss payment, you make me feel like a whore.

Yeah, the problem with sleep is that it's always too long on a fast machine and never long enough on a slow machine. Which program are you working with? I'd be happy to take a look if I can help. I still use the "old" version of AutoIt for about half of my scripts, as Au3 appears so convoluted to a non-coder like me. Au3 does have its moments, however, like its ability to completely hide batch files, e.g.: Run( @ScriptDir & "\cleanup.cmd", "", @SW_HIDE) and eject the CD after the install: $driveArray = StringSplit("DEFGHIJKLMNOPQRSTUVWXYZ", "") For $i = 1 To 23 $opened = CDTray($driveArray[$i] & ":", "open") If $opened Then ExitLoop Next If NOT $opened Then Shutdown(6) EndIf I suspect Au3 aficionados are going to scream, but those are the only two features that I prize, together with the cleaner looking message boxes, e.g.: SplashTextOn("", "" & @CRLF & "Installing Microsoft Money 2005 Premium..." & @CRLF & "" & @CRLF & "Please wait..." & @CRLF & "", 275, 90, -1, -1, 1, "Arial", 12, 12) Sleep(4000) SplashOff() Those three, and a few others, have a place in my AutoIt snippet library.

I think you need to set the script to run in Mode 4. From the AutoIt help file: I know I have done it, but I'll be danged if I can find an example for you, sorry. Search "Window Titles and Text" in help and read the section regarding Advanced Mode. Maybe others can come up with a script example?

@ChipCraze23 As Frank said: Specifically, after creating the admin install point (using the .exe vs. the .msi) and updating it with the latest download, build 524, you must delete the new .msi file from the admin install point and replace it with the original. Clearly, the original .msi file is required to defeat the "check for previous version" nag. Then run with the /qb switch and you will find version 9.0.524.0 installed on the system. I RAR'd mine using Asta's instructions. Search and you will find.

Frank, I think you mean you ran the .exe vice the .msi to create the admin install? It threw me for a loop the first time I tried it. Anyhoo, thanks for the great insight, your method works fabulously.

@Laptonic Really, really nice app, exactly what I was looking for. Thank you!

@TheeBeets Glad to see you were able to find a solution to this, per my read of your other posts. The .hta file is the heart and soul of WPI.