blinkdt

Get the Office 2003 Resource Kit (ORK.exe) from Microsoft. Make a silent install, customize the setup, and so much more. It's pretty intuitive, you'll think you died and went to heaven.

Yes, I think you might have visited the wrong forum to solve your problem, Samurai Princess, but since you are here at MSFN: Does Paint open if you click Start --> Run and type "mspaint" (without the quotes) and hit enter? If so, you may simply be missing a shortcut to the program found in the WINDOWS\System32 directory. Recreate the shortcut and you are good to go. If someone has actually REMOVED mspaint.exe from your machine, then you will need to get your hands on a disc to reinstall this Windows accessory. Ditto with WordPad and Calculator (Start --> Run --> wordpad and Start --> Run --> calc).

Beautiful. Absolutely beautiful! This is going into all of my installs, just what the doctor ordered. Hope you can keep this updated as time allows, but as you say, this is a great baseline to work from.

Yeah, this one is tough. Tying an action to a process is one thing, but when the process will not reveal itself then you're stuck guessing. I have "settled" on a splash text that hides the command window for the duration of the defrag process: SplashTextOn("", "" & @CRLF & "Defragmenting the C: partition..." & @CRLF & "", 275, 58, -1, -1, 1, "Arial", 12, 12) RunWait ( @ComSpec & " /c defrag c: -f", "", @SW_HIDE ) SplashOff() Pretty boring to be sure, but I know it is working and I'm not trying to entertain an audience. I just want it to look clean. Here are some script ideas with promise found at MHz's other hangout: HERE. This adaptation seems to work pretty well, and the $TimeLimit variable can be adjusted with quite a bit of accuracy depending upon the fragmentation level at any given point during the install: Func renew() $TimeLimit = 10000 $start = TimerInit() $pid = Run(@ComSpec & " /c defrag c: -f", "", @SW_HIDE ) ProgressOn( "Progress", "Defragmenting the C: partition") While ProcessExists( $pid ) $current = TimerDiff($start) ProgressSet( $current * 100 / $TimeLimit) Sleep(20) WEnd ProgressOff() EndFunc;==>renew renew() The required tweaking is well-suited for the perfectionist. If anyone can devise a way to tie a progress bar to the actual length of the defrag process, I will lobby to add another star to their profile.

How about placing a WinRAR SFX in the $OEM$ "All Users" Startup directory ($OEM$ | $Docs | All Users | Start Menu | Programs | Startup) that runs a .cmd file in TEMP mode? The .cmd file would delete the SFX from Startup at the end of the operation. Name the SFX "Install.exe" and the .cmd "run.cmd." Maybe something like this: Install.exe Path=%windir%\Temp Setup=run.cmd Silent=1 Overwrite=1 Title=Extracting files... run.cmd @ECHO OFF Routine 1 Routine 2 DEL "%userprofile%\Start Menu\Programs\Startup\Install.exe" CLS EXIT Edit: @MHz (below) Good point, I missed that completely. Guess I don't fully understand what's trying to be accomplished here, will try rereading this when I'm a little less bleary. Edit/Edit: I get it. I see no unattended option either.

I reinstalled on 26 machines last night. I was my privilege to walk to each of them, open MU and choose custom install, and then hide six non-critical updates so that my students won't inadvertently install them "because they're there." Thank goodness all of the machines were in the same room. I've incorporated this routine in the past, but need to stay on top of it as the updates roll in. Lesson learned, the hard way. Lest we forget, the name of the game is unattended.

Windows just keeps getting bigger, or so it appears. People bring their machines to me and I find Dells with 128MB RAM running a patched Windows XP SP2 install. That might have been OK for the initial release years ago, but not now. You can learn lots more about slipstreaming--what it is, how it works, what it does--by using the magical search functionality, no offense intended. Off the top of my head, it's my understanding that slipsltreaming is not integrating, where I386 files are actually replaced with updated CABed versions (integrate the latest Flash player, for example) from the get-go. But unlike a post-install patch operation, slipstreaming "revamps" the OS during the T-13 install stage--removing vulnerability issues--and is faster that a post-install patch operation. By slipstreaming, you prep the OS to do the work of integration during the initial install, and it does it all by itself using Microsoft's method. It takes longer because you have added files, but nothing is "reinstalling." I am confident this has all been explained in greater detail in specific portions of the Unattended Guide. A lot of time has been spent creating that Guide, and it deserves a close read.

I think that was me. Was waiting until the coder dudes had finished polishing the 4.xx version, and before I knew it summer was gone and I was back at work. I really would like to take a stab at it but time is limited. Who is the point of contact on this? Kelsenellenelvian, or the folks (can't recall names off the top of my head ) who did much of the under-the-hood coding? Edit: and it looks like K- has already grabbed the bull by the horns and done some work on it, HERE.

Try this: REG ADD %KEY%\015 /V 1 /D "%CDROM%\software\autoit3.exe %CDROM%\software\install_avant.au3" /f

Doesn't matter. As Yzowl stated and druiddk demonstrated, you need the full path on both ends, to locate the source and destination. From my WPI: SET shortcuts=%cdrom%\Programs\00Shortcuts COPY "%shortcuts%\Windows Explorer.lnk" "%systemdrive%\Documents and Settings\USER_HERE\Application Data\Microsoft\Internet Explorer\Quick Launch" And, yeah, the path could be shorter.

The dreaded Code 19 error. Have you checked to see what values appear for "UpperFilters" and "LowerFilters," or even whether only one (probably UpperFilters) or both exist? That might provide a clue as to what is causing the problem.

It's COMPLETELY inappropriate.

Maybe use an AutoIt script to install the program and then close the program: AutoItSetOption("TrayIconHide", 1) AutoItSetOption("WinTitleMatchMode", 4) BlockInput(0) DirCreate( @MyDocumentsDir & "\LIMEWIRE_downloads") RunWait( @ScriptDir & "\LimeWireWin.exe /S", "", @SW_HIDE) ProcessWait("LimeWire.exe") Sleep(2000) ProcessClose("LimeWire.exe") Sleep(5000) Exit

I use HFSLIP for Windows 2000 installs (peerlessly integrates IE6, WPM9, and DX9 as well) and the SVCPACK method for WinXP. Search and you will find.

Try again. HERE. Or Google the term "acrobat7chaining.zip" to locate the working link.

Beautiful, MHz. Thank you.

Oh, this one is easy. HP. READ ALL ABOUT IT.

@Tomcat76 I understand the frustration with AVG, but I believe they made the right call in identifying compiled scripts as a potential danger. And after reading the thoughts of others who use AutoIt, in this case, there really was no downside to running the script in raw form: you edit the final product directly (no need to compile) and uses less space. It took a little time to revamp my routines, but once I was finished it was all good. @MHz Wow, you are the master. I would love to adapt the countdown feature for a simple SplashText box, but I suspect such an option is a no-go with AutoIt(?).

How about an AutoIt script to get the job done? AutoItSetOption("TrayIconHide", 1) AutoItSetOption("WinTitleMatchMode", 4) BlockInput(0) SplashTextOn("", "" & @CRLF & "Installation completed successfully!" & @CRLF & "", 275, 58, -1, -1, 1, "Arial", 12, 12) Sleep(2000) SplashOff() Sleep(1000) SplashTextOn("", "" & @CRLF & "Restarting the machine..." & @CRLF & "", 250, 58, -1, -1, 1, "Arial", 12, 12) Sleep(30000) SplashOff() Sleep(1000) Shutdown(6) You can compile the code (but AVG will likely have a hissy-fit) or run as a raw script [%cdrom%\\AutoIt3.exe %cdrom%\\Programs\\restart.au3].

Yes, Quick Batch File Compiler proved frustrating for me as well, as it did not work correctly in a true DOS environment. But several free utilities are available that can get the job done. Grab them HERE. BAT2EXEC and C2E convert a batch file to a .COM format and then to a .EXE format, respectively. After unzipping the downloaded file, open Windows Explorer and click on the Batch File Utilities folder in the left window pane to display its contents in the right window pane. --Copy your batch file to the folder so that it is clearly visible in the right window pane together with the conversion tools. --Right-click on the Batch File Utilities folder and select the Open Command Windows Here option from the menu (use a registry setting or the CmdHerePowertoy Windows XP Power Toy to add an "Open Command Windows Here" context menu option to file system folders if necessary). --Convert the batch file to a .COM format first by typing "bat2exec yourfilename.bat" and hitting the Enter key. You should see a "yourfilename.com" file appear in the right window pane. --Now convert the .COM file to an .EXE format by typing "C2E yourfilename.com" and hitting the Enter key. You should see a "yourfilename.exe" file appear in the right window pane. Very cool. Edit: the two utilities were provided by PC Magazine, if I recall correctly.

How about importing a registry setting to turn off balloon tips altogether? If that solution would work for you, check the 'Unattended Windows' "Registry Tweaks Pt 3" sticky for the correct setting.

Looks like the upgrades are not needed excepting for 7.0.5. I used the Adobe tool to create/edit the transform, then renamed the upgrade file to 705.msp. Works wonderfully, and I have only one entry in 'Add or Remove Programs' for the program.

I use HFSLIP for Windows 2000, integrates IE6 and so much more. Then install Symantec from RunOnce? Search and ye shall find TommyP/FDV's fantastic magic HFSLIP package. It takes a little bit to set up, but it's a joy watching it work.

Yeah, I believe this was a somewhat costly program before Microsoft bought it and started giving it away to save all of those Windows boxes from the closet. Update: I can confirm that copying the lone gcUserData.gcd file to the Microsoft AntiSpyware directory worked for me on a fresh install. Very nice. Picking up on BoardBabe's method, my WPI entry looks like this: cmd1[pn]=['"%cdrom%\\Programs\\MSantispy\\Microsoft AntiSpyware.msi" /qn'] cmd2[pn]=['"%PROGRAMFILES%\\Microsoft AntiSpyware\\gcasDtServ.exe" /regserver'] cmd3[pn]=['%cdrom%\\AutoIt3.exe %cdrom%\\Programs\\MSantispy\\settings.au3'] where settings.au3 is an AutoIt script that does the job of copying the file: AutoItSetOption("TrayIconHide", 1) AutoItSetOption("WinTitleMatchMode", 4) BlockInput(0) FileCopy( @ScriptDir & "\gcUserData.gcd", @ProgramFilesDir & "\Microsoft AntiSpyware") I did notice that some of the other eight .gcd files are updated when certain settings are configured. For example, I like to run deep scans and three of the eight where changed together with gcUserData when I saved that setting. But I only copied over the gcUserData file during my virgin install and everything appears OK. All of my settings were preserved and the progam runs just fine. @RogueSpear: I will be using this method for the foreseeable future and will report any problems back here, but none are anticipated. If this works as planned, then we are set until at least July 2006, so I figure it's worth the up front effort, eh?

I concur. Edit: Looks like the settings are held in a .gcd file called "gcUserData.gcd." When MSAntispy is uninstalled from a system, this file and eight (8) other .gcd files are left behind behind in the Microsoft AntiSpyware directory (so much for a clean uninstall). I noticed that when uninstalling the old version and then installing the new version--where the directory remnants remain in place--my settings where preserved. After experimenting with the nine .gcd files that are left behind, I found that I could 1) uninstall 2) delete the Microsoft AntiSpyware directory completely 3) reinstall 4) copy only the gcUserData.gcd file into the fresh install directory. Upon first launch, the setup walk-through is skipped and all of my settings are configured. Nice. Must test this on a clean install.