blinkdt

Yeah, Adobe can be a beast. They don't make it easy, do they? Here's what I did:1). Edited the Abcpy.ini file answering "NO" to all entries except DisplayUserInfoDlg=YES and DisplayRebootDlg=YES if, like me, you want to reboot and get busy. 2). Copied all files from the "Premiere Pro" directory into a directory called "Files" and replaced the DirectX9 files with relevant files from the DirectX9c version. 3). Created an Autorun.inf [autorun] OPEN=setup.exe icon=setup.ico label=Premiere Pro shell\verb\command=setup.exe shell\verb=Run &Setup 4). Created a setup executable using AutoIt (the old version v.2.64) ; +++++++Adobe Premiere Pro+++++++ ; ========================= ; Installation Script for Windows XP SP-1 HideAutoItWin, on BlockInput, on ;Search these lines for source directory and run setup IfExist, C:\\Files\\setup.exe, run, C:\\Files\\setup.exe IfExist, D:\\Files\\setup.exe, run, D:\\Files\\setup.exe IfExist, E:\\Files\\setup.exe, run, E:\\Files\\setup.exe IfExist, F:\\Files\\setup.exe, run, F:\\Files\\setup.exe IfExist, G:\\Files\\setup.exe, run, G:\\Files\\setup.exe IfExist, H:\\Files\\setup.exe, run, H:\\Files\\setup.exe IfExist, I:\\Files\\setup.exe, run, I:\\Files\\setup.exe IfExist, J:\\Files\\setup.exe, run, J:\\Files\\setup.exe IfExist, K:\\Files\\setup.exe, run, K:\\Files\\setup.exe IfExist, L:\\Files\\setup.exe, run, L:\\Files\\setup.exe IfExist, M:\\Files\\setup.exe, run, M:\\Files\\setup.exe IfExist, N:\\Files\\setup.exe, run, N:\\Files\\setup.exe IfExist, O:\\Files\\setup.exe, run, O:\\Files\\setup.exe IfExist, P:\\Files\\setup.exe, run, P:\\Files\\setup.exe IfExist, Q:\\Files\\setup.exe, run, Q:\\Files\\setup.exe IfExist, R:\\Files\\setup.exe, run, R:\\Files\\setup.exe IfExist, S:\\Files\\setup.exe, run, S:\\Files\\setup.exe IfExist, T:\\Files\\setup.exe, run, T:\\Files\\setup.exe IfExist, U:\\Files\\setup.exe, run, U:\\Files\\setup.exe IfExist, V:\\Files\\setup.exe, run, V:\\Files\\setup.exe IfExist, W:\\Files\\setup.exe, run, W:\\Files\\setup.exe IfExist, X:\\Files\\setup.exe, run, X:\\Files\\setup.exe IfExist, Y:\\Files\\setup.exe, run, Y:\\Files\\setup.exe IfExist, Z:\\Files\\setup.exe, run, Z:\\Files\\setup.exe ;Enter User Information WinWaitActive, Adobe Premiere Pro Setup, User Information Send, +none Send, {TAB}{TAB} Send, +none Send, {TAB}{TAB} Send, XXXXXXXXXXXXXXXXXXXXXXXX <--Your Serial Number Here sans dashes Send, {ENTER} ;Reboot WinWaitActive, Adobe Premiere Pro Setup, I want to restart my computer Send, {ENTER} exit [ADLIB] 5). Placed the Autorun.inf, compiled setup.exe, and setup.ico files alongside the Files directory and burned the mess to disc. I found a premiere.sif file inside data1.cab and ran across some writings on the subject via Google, but poop on that. Much better to Google for info on Autorun.inf and get to know AutoIt, IMHO, as you will use them time and again, I suspect.

@prathapml: You, sir, are a scholar and a gentleman. Thank you.

at the same time: Soooo...how important is it to include "ManagedDX.cab," or can that 3+MB file be safely excluded as well? I can't begin to fathom which, if any, of my applications require such support.

Anyone found a way to silently install Google's photo organizer, Picasa? I ended up using InstallRite to get the job done, but I'm curious to know of different methods that may have worked for others. I couldn't locate anything in the way of switches for the funky installer used for Picasa.

Tweak request, for Registry Experts Only. In Taskbar and Start Menu Properties (right-click on the Taskbar and select properties, don'tcha know), with "Hide inactive icons" selected, is there any way to ensure that ALL icons--present, past, and future--are in "Always hide" mode? I've been playing with RegSnap and am curious to see what anyone else might have. What do I have? A confused mess so far.

@snakefood Believe you need REGEDIT /S to kick off the registry.reg file. My Cmdlines.txt file looks like this: [COMMANDS] "useraccounts.cmd" "REGEDIT /S autologon.reg" ".\RunOnceEx.cmd" I'm only now playing with the autologon portion.

De nada, snakefood. I should mention that I import the tweaks at the 12 minute mark AND after first boot. Some of the tweaks are merely cosmetic, for example, placing a check mark in a TweakUI interface box even though a different tweak actually changes the system setting, if that makes sense. Lots of folks are commenting in this thread about tweaks that are "applied" but do not work. The tweak might actually NOT be implemented just because the box is checked. In my experience, anyway.

Here's a tweak I've not seen mentioned previously: ;Disable 'Send administrative alert' found in Control Panel-- System-- Advanced-- Startup and Recovery [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl] "SendAlert"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl] "SendAlert"=dword:00000000 My completed tweak file can be found HERE. It's heavily commented, should prove useful for noobs. Like me.

Finally got this bugger to work! I ended up using InstallRite to create an installation package, entering serial number and applying the theme of my choice along the way. I run the package AFTER first boot (many attempts to install this package from RunOnceEx failed miserably). After the package is installed I end the routine by adding the following key to the registry so that the theme will be applied following a forced reboot: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "WindowBlinds"="C:\\Program Files\\stardock\\object desktop\\windowblinds\\wbload.exe" I'm using AutoIt to run my first boot routine, which installs CursorXP, Belarc Advisor, Window Washer, and WindowBlinds. The routine also cleans up icons and directory structures along the way, the whole thing looks magical. I don't know who thought up the idea for this forum, but my hats off to them! Couldn't have done this in a million years without everyone's help.

Cretak, rasken posted a method that works HERE. Works great, you will never need that floppy again!

Thanks, Joe. OnDemand Software claims their product--WinInstallLE--is the same one that was bundled with the 2000 server CD. Gonna give it a try later this summer, but for now I will stick with your method as suggested in this thread. I ran into some 'hidden window' issues while using AutoIt and just can't seen to get past them, so poop on that route.

All due respect to MCT, but my heart goes out to Sgt Strider or anyone trying to search the "Registry Tweaks" thread. The four keys you need, sarge, are: ;enable Quick Launch toolbar w/ (your preferred number of) spaces [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop] "TaskbarWinXP"=hex:0c,00,00,00,08,00,00,00,02,00,00,00,00,00,00,00,b0,e2,2b,d8,\ 64,57,d0,11,a9,6e,00,c0,4f,d7,05,a2, yadda, yadda, yadda, etc., etc., etc. ;disable Hide Inactive Icons feature in Status Notification Area [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer] "EnableAutoTray"=dword:00000000 ;Use personalized menus=false [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "IntelliMenus"="No" ;Enable ClearType for ALL Users [HKEY_USERS\.DEFAULT\Control Panel\Desktop] "FontSmoothing"="2" "FontSmoothingType"=dword:00000002 [HKEY_CURRENT_USER\Control Panel\Desktop] "FontSmoothing"="2" "FontSmoothingType"=dword:00000002 The first key is created by exporting the [...\Streams\Desktop] key from the registry AFTER you have the Quick Launch bar set up as you like on a clean machine. I then remove the "Toolbars" and "Upgrade" entries found at the bottom of the key. It works for me.

@Joe User 99 I would love to know what tool you used to repackage this app, especially with a new theme and the serial intact. A brief rundown on the repackaging procedure would be nice, too. I'm using AutoIt right now--and it's a pain--and have no real experience with the method you mentioned. I'm pretty good with "paint by numbers" though. Any help would be much appreciated.

Dunno, but running a simple search on the term "spybot" turned up flattspott's excellent entry.

Nice, flattspott, thanks. Works great with version 1.3 as well.

Thanks, Frank, sounds intriguing, but I already have the install worked into the AutoIt routine. The browser window is closed at the end and then a .cmd file fires up to delete the four (4) shortcuts (possibly five) Belarc scatters on the system during the install (Desktop, Quick Launch, Programs, and Favorites), placing instead just one shortcut in System Tools. Needy little program, isn't it?

Has anyone discovered the switches needed to install Belarc Advisor from RunOnceEx.cmd silently? The /s switch does much of the job, but as anyone who uses this handy little app knows, the program fires up following the install. A switch that suppresses this action would be most helpful. I've tried a few with no result. Alternatively, I could add the install to my post-install AutoIt routine and be done with it, I suppose. I was surprised to find that my search for "Belarc" turned up only two hits. Noone uses this thing but me?

Spoke too soon, Zoster, found it as part of version 3. I will have to gear up from version 2 and give this a try, thanks again.

ZoSTeR, very cool, thanks. But when you mention "Use the AutoIt Spy," I'm at a loss. Is 'AutoIt Spy' a reference to the AutoIt Reveal Mode tool, is it a new feature built into version 3, or is it an add-on tool that someone is selling? Sounds great, I have to get my hands on it.

Blam-O! THANK YOU! That Windows Media Player first run annoyance was driving me crazy. Your registry merge fix was just the ticket.

Been awhile since I've visited this board, it just gets better and better. Was looking for help on installing Webroot's Window Washer, found some references in the forums to include one member who asked that he be PM'd for an AutoIt routine to install this program (but I can no longer locate the thread!). Haven't heard from him, so here's what I came up with: SplashTextOn, 290, 110, Installation in Progress, Installing Window Washer 5.5... Sleep, 2000 SplashTextOff ;Install Window Washer 5.5 Run, %systemdrive%\\Extras\\WindowWasher\\setup.exe Sleep, 500 WinWaitActive, Window Washer, Setup will now install Window Washer Send, {ENTER} WinWaitActive, Window Washer Installation, I Agree Send, {TAB 2}{ENTER} WinWaitActive, Window Washer, tabOptions Send, {TAB 4}{DOWN}{SPACE}{TAB 4}{ENTER} WinWaitActive, Window Washer, tabInstallPath Send, {TAB 3}{SPACE},{DOWN}{SPACE}{DOWN 3}{SPACE}{TAB 2}{ENTER} Sleep, 22000 WinWaitActive, Window Washer LeftClick, 340, 280 WinWaitActive, Window Washer, tabPluginScan LeftClick, 114, 154 LeftClick, 114, 172 Send, {TAB}{ENTER} WinWaitActive, Window Washer, Finished Send, {ENTER} run, regedit /s "%systemdrive%\\Extras\\WindowWasher\\prefs.reg" For those not familiar with AutoIt, it is similar to VBS sendkeys, I suppose. I am NOT a coder (I live vicariously through my coder friends) and AutoIt is intuitive enough for me to use. The prefs.reg file is a combination of two registry entries: 1. [HKEY_CURRENT_USER\Software\Webroot] 2. [HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\Shell\Washer] @="&Shred Contents" and [HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\Shell\Washer\Command] @="\"C:\\Program Files\\Webroot\\Washer\\wwShred.exe\" \"/recycle\"" Note: the entries found in the second instance are drawn from HKEY_CLASSES_ROOT\CLSID\{645FF040-5081-101B-9F08-00AA002F954E}, I just run a search on the default naming convention found when a user right-clicks on the Recyle Bin and discovers the amazingly long name given to the shred option by Window Washer. Yeesh. I suppose one only needs the first entry that actually renames the Recycle Bin text, but hey.... The routine is thrown in to a larger AutoIt routine that is run at reboot. I copy that routine into the Startup folder using a batch file that is activated via RunOnceEx.cmd, which is activated via cmdlines.txt. After some playing around, I was able to get the whole thing to self-destruct at the end of the routine from within the AutoIt routine itself. Whew, hope that's confusing to you, too!

I've only just begun to mess with this, but I think you need to preface any .vbs with "wscript.exe" within a .bat/.cmd file, like so: CLS @ECHO OFF TITLE Importing Registry Settings... COLOR 8f wscript.exe "yourpath\invis.vbs" "yourpath\RegTweaks.cmd" exit In this example, invis.vbs holds the following: CreateObject("Wscript.Shell").Run """" & WScript.Arguments(0) & """", 0, False The first batch is packaged as "launch.cmd," which flares briefly and disappears. RegTweaks.cmd runs in absolute invisible mode. I found this on another site and am in no position to comment (non-programmer), dunno if it's off the screen, or really not there, but it works like a charm. No more scrolling batch files, ever. Any VBSers out there care to interpret invis.vbs?

@IcemanND: Nice work! Installs flawlessly! I used AutoIt to get past the Internet Sharing Configuration nag. I took your code above and saved it as "firewall.vbs," then used notepad to write the following: Run, wscript.exe %systemdrive%\\kill\\firewall.vbs Sleep, 2000 [ADLIB] Internet Sharing Configuration,, Send, !y Save this as an .aut file and use AutoIt's script compiler to create an executable. The [ADLIB] section takes care of unforeseen events such as nag windows. Now if that window pops up AutoIt will ensure that the clicking is done for you! You may want to adjust the sleep timing, from 2 seconds to say 5 seconds, on a slower machine. If sleep is not set properly this won't work! I don't know if this can be used during the OS install, for example during the Windows Update portion of your unattended. I have included the script in a larger executable that I run from startup following final reboot. All of my post-reboot files are stored on the root in a directory called "kill"

@shareef59 I hope this doesn't sound like I'm avoiding your request for help, but my best advice is to spend a good bit of time with the AutoIt Help File, particularly the Script Commands section. The help file is the only comprehensive tutorial available, as far as I know. You'll also find excellent solutions to nettlesome problems like the one cerw1n described by searching Google. Some pretty talented IT people use this little proggy for odds and ends jobs. In my case, I copy a compiled AutoIt script to the Administrator's startup folder during the Windows Update process, when I'm fiddling with other shortcuts changes, etc. At startup following reboot, the configuration file launches after a 10 second delay (user input is blocked during this period) and the tweaking begins. For example: IfWinExist, PsShutdown, The system is shutting down, Goto, Quitnow BlockInput, on Sleep, 10000 BlockInput, off MsgBox, 36, Attention!, Configure this PC? IfMsgBox, YES, Goto, next1 IfMsgBox, NO, Goto, next2 next1: SplashTextOn, 290, 110, Installation in Progress, Configuring the Task Bar and Start Menu... Sleep, 2000 SplashTextOff RightClick, 600, 750 Sleep, 300 Send, r WinWaitActive, Taskbar and Start Menu Properties Send, !h Sleep, 500 Send, {TAB} Sleep, 500 Send, {ENTER} SplashTextOn, 290, 110, Installation in Progress, Configuring TweakUI Powertoy... Sleep, 2000 SplashTextOff ;adjust TweakUI Run, tweakui WinWaitActive, Tweak UI, Tweak UI for Windows Sleep, 1000 Send, {DOWN} Sleep, 500 ;General settings Send, {TAB} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN 2} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {TAB 4} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {DOWN} Sleep, 500 ;Explorer settings Send, {TAB} Sleep, 500 Send, {DOWN 6} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {TAB 4} Sleep, 500 Send, {RIGHT} Sleep, 500 Send, {DOWN} Sleep, 500 Send, !N Sleep, 500 Send, {TAB 4} Sleep, 500 Send, {UP} Sleep, 500 Send, {LEFT} Sleep, 500 Send, {DOWN} Sleep, 500 ;Common Dialogs settings Send, {TAB} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {TAB 4} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {DOWN} Sleep, 500 ;Desktop settings Send, {TAB} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {TAB 4} Sleep, 500 Send, {DOWN} Sleep, 500 ;My Computer settings Send, {TAB} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {TAB 4} Sleep, 500 Send, {DOWN} Sleep, 500 ;Control Panel settings Send, {DOWN} Sleep, 500 ;Templates settings Send, {DOWN} Sleep, 500 ;Internet Explorer settings Send, {TAB} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {TAB 4} Sleep, 500 Send, {DOWN} Sleep, 500 ;Command Prompt settings Send, {DOWN} Sleep, 500 ;Logon settings Send, {TAB} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {DOWN} Sleep, 500 Send, {SPACE} Sleep, 500 Send, {TAB} Sleep, 500 Send, {ENTER} WinClose, Tweak UI .... That's where I better end, unless someone says it's OK to post 476 lines! My IT pals chuckle when they see me working with this, but they're always peeking over my shoulder with interest. And again, the process described above goes on to complete a few operations that, well, I wouldn't know how to begin to accomplish using any other method. For example, how would you give a user the option to install Intellipoint post-unattended? I ask point-blank whether they want to install it, and if the answer is affirmative, another script runs and installs it, cleaning everything up afterward. This is not something that a non-programmer newbie (like me) is going to tackle on a weekend but it's worth a close look. Check it out.

I began using AutoIt last summer, long before stumbling upon this forum. Most of the AutoIt builds I had painstakingly created where trounced by the automation genius found here, but I still use it for a few things, for example to configure TweakUI after the setup is complete and run batch files to configure the Quick Launch toolbar. I also use it to present dialog boxes asking whether the user wants to rename the PC, install additional drivers for specific hardware items, defragment the hard drive when the whole mess is completed, etc. Not "pure unattended" to be sure, but the little proggy has it's place in the unattended world, IMHO. Remember, too, that you can compile those .aut scripts as executables, negating any need to install AutoIt itself on the target machine. Any operation that can be accomplished with a keyboard and mouse can be done with AutoIt, in my experience. Want to install MusicMatch, MS Money, etc. and fully configure them to your tastes? AutoIt! And it's a gas watching it work!