blinkdt

Here's mine, and lovin' this 5.6. "Nice job" just doesn't capture it. A tip of the fedora to Kel, Mr. Ritter, and company. I just modified the existing Glossy theme files. Get my .rar package HERE.

Unbelievable You're missing the entire point of the MSFN forum, my friend. It's for people who want to learn and share their new-found knowledge along the way. All of the information you need to do what you say you are trying to do is available to you at no cost, other than your time. Refer to my Signature below for further amplification.

You can change the color of individual entries by adding a little HTML as seen from an earlier post: green, red, blue, purple <font color="#00FF00"><b>AVG Free</b></font> <font color="#FF0000"><b>Trend Micro</b></font> <font color="#0000FF"><b>Symantec</b></font> <font color="#9966FF"><b>NOD32</b></font> ...but the headers themselves are probably colored using .css and applied in blanket fashion to ALL headers.

No real need at this point, I expect. It's a short list as of this writing, only seven updates available at the Office update site. Download each of the KBxxxxxx files, extract them, and put the .msp files in your updates directory. All too easy.

@kitkit Check The Guide --> Beginning Users --> Step 3 --> Installing the Hotfixes. Welcome aboard.

Sgt, I don't disable the screen saver but I do select a custon screen saver and adjust the timing . . . through the custom theme file that I have integrated into my disc. If you search for "Royale Theme" you should probably find it. You can most likely change your dpi there as well. It's not a reg tweak, I know, but it does the job nicely.

I use a testbed machine (1 HDD, two partitions) and keep an Acronis image of a fresh Windows install on the D: partition. When I want to test an app install routine, I image back to C: and then install the app using WPI. The imaging operation takes a few minutes, and I can test the app install either alone or in combination with other apps, adjusting the ordering and timing along the way. WPI RULES!

Hey, folks, thought I would throw this out there for those who like to do it the convoluted way based on the excellent insights found in this thread. 1. . . extract the files using WinRAR and edit the conf.txt file to EXCLUDE the bloat per SubD's notes (nice!). 2. . . create a .cmd file to perform the actual install: @ECHO OFF %TEMP%\SetupX.exe /QUIET /NORESTART RebootYesNo="No" serialnum_userval="xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx" AgreeToLicense="Yes" EULA_AGREEMENT=1 CLS EXIT 3. . . create a .reg file to remove program nags, based on the installed options: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce] "NeroHomeFirstStart"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "NeroFilterCheck"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Ahead\Nero Home\MediaLibrary] "DisableNeroScout"=dword:00000001 4. . . use IconsExtract to grab a Nero icon. 5. . . put those files, together with AutoIt3.exe and the script 'install.au3' into the Nero directory: TraySetIcon( @ScriptDir & '\Nero7.ico') TraySetState (4) TrayTip('Unattended Installation', 'Installing Nero 7 Ultra Edition . . . please wait . . .', 0, 1) RunWait(@ScriptDir & "\Redist\DirectX\dxsetup.exe /silent") Sleep(1000) RunWait( @ScriptDir & "\install.cmd", "", @SW_HIDE) Sleep(1500) RunWait ( @Comspec & ' /C regedit /S ' & @ScriptDir & '\NERO7nags.reg', '', @SW_HIDE ) Sleep(500) FileDelete( @DesktopCommonDir & "\Nero StartSmart.lnk") TrayTip("clear tip","",0) TraySetState (8) MsgBox(4096, "Unattended Install", "Installation completed successfully!", 5) Exit 6. . . archive the Nero directory contents using WinRAR with the icon and the following comment: Path=.\%TEMP% Setup=AutoIt3.exe install.au3 Silent=2 Overwrite=1 It installs really well and looks pretty snazzy with the balloon tip and custom flashing tray icon, couldn't be happier. I had tried editing the .msi to no effect, very frustrating. This method worked for me.

Yep, for Enterprise just run X:\setup.exe /admin, configure the silent install per your tastes, drop the saved .msp in the updates directory and you are good to go. No need for a batch file at all.

That's a tough question based on the available information. Your use of parens in the theme file name strikes me as odd. Other than that, I've never had a setup hang at "installing devices," but then again I've never used nLite, edited a bootscreen or billboard, used an image of a setup disk to perform an install, or installed on a virtual PC. I tend to adher to the guide and do things manually, then install on a testbed machine.

Can't help you with your partitioning woes, but any chance that you would share your answer file? I'd love to have a look at it and thanks in advance.

I'm using Diskeeper2007 and do it this way: 1) Extract needed files to the Program Files directory using WinRAR with the following comment: Path=Diskeeper Corporation\Diskeeper SavePath Setup=Install.exe Silent=1 Overwrite=1 Install.exe is a compiled AutoIt script that runs after extraction: TrayTip('Unattended Installation', 'Installing Diskkeeper 2007 Pro Premier . . . please wait . . .', 0, 1) RunWait('msiexec /i "' & @ProgramFilesDir & '\Diskeeper Corporation\Diskeeper\DK2007.msi" /qn') Sleep(500) FileDelete(@ProgramFilesDir & '\Diskeeper Corporation\Diskeeper\DK2007.msi') TrayTip("clear tip","",0) TrayTip('Unattended Installation', 'Defragmenting the C: partition . . . please wait . . .', 0, 1) RunWait ( @ComSpec & " /c Diskeeper C", "", @SW_HIDE ) TrayTip("clear tip","",0) Nice. The Diskeeper2007 user manual has a brief section entitled "Running Diskeeper From the Command Prompt" spelling it out clearly. You can defragment multiple partitions by repeating the command and specifying different drive letters, no harm done if the drives are optical or do not exist. Lastly, you can shut down the machine by adding 'Shutdown(x)' to the end of the AutoIt script, where 'x' is any of several values. You're going to need to install AutoIt anyway to compile the script, might as well take a peek at the help file, eh? But 'Shutdown(1)' should work fine.

Read THIS. Please.

Wow, lots of threads about Foxit, but only one describing the AutoIt method of install? That's just wrong Here's how I'm doing it to accomplish a silent install, with balloon tip indicator, that places a shortcut to the program in the Accessories directory, registers the program as the default PDF reader, and opens the program on first run with no advertising: 1. Get the zipped version directly from Foxit and put the executable in a directory of your choosing. 2. Put this registry file in the same directory, I called mine "adverts.reg:" Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Foxit Software\Foxit Reader\MainFrame] "AdvertiseIndex"="6" "ShowEditorAd_908"="0" "ShowReaderAd_908"="0" "ShowTypewriterAd_908"="0" "ShowPOAd_908"="0" "ShowSDKAd_908"="0" 3. Run this AutoIt script from the same directory: TrayTip('Unattended Installation', 'Installing Foxit PDF Reader . . . please wait . . .', 0, 1) FileCopy( @ScriptDir & "\FoxitReader.exe", @ProgramFilesDir & "\Foxit Software\Foxit Reader\", 9) FileCreateShortcut( @ProgramFilesDir & "\Foxit Software\Foxit Reader\FoxitReader.exe", _ @ProgramsCommonDir & "\Accessories\Foxit PDF Reader.lnk") RunWait( @ProgramFilesDir & "\Foxit Software\Foxit Reader\FoxitReader.exe -register") RunWait( @Comspec & ' /C regedit /S ' & @ScriptDir & '\adverts.reg', '', @SW_HIDE ) TrayTip("clear tip","",0) Done! As Darth Vader would say, "all too easy." Edited for typos

It appears one can perform basic modifications to the new menu system at this reg key: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\CommandBar But a quick search of the IE7 development Web site reveals nothing but basics. Maybe pursue this issue directly with the Dev team at MS? I'm outta here.

Thanks for that, snooz. I wonder if install order has anything to do with it? I'm pretty sure I installed IE7 after MSUpdate on the machine I'm at now, but I normally install IE7 and then MSUpdate during a normal install routine. Let me look at some other machines around here and see what's up. Edit: Nope, no luck there. Just installed MSUpdate over a fresh install that included IE7, and I still get "Windows Update" in Tools. I use an IEAK package to install IE7 but do not have restrictions set . . . that's the only thing I can think of at the moment that might be affecting the MSUpdate install's ability to make standard changes to the Menu.

No, it doesn't, at least not in my case. I have IE7 and Microsoft Update and--like BoardBabe--IE7 is still displaying "Windows Update" in Tools. Hmmm . . .Edit: for those interested, you might want to check out the program HERE. Looks like it's designed to revamp the look and feel of your browser.

I like Sonic's method, wish I had thought of it myself earlier . As a side contribution to this discussion, I rely on AutoIt and use this modifiable script after first logon to adjust the visuals: TraySetToolTip(" Unattended installation is active . . . ") TrayTip('Unattended Installation', 'Adjusting visual settings . . . please wait . . .', 0, 1) Sleep(2000) Send("#r") WinWaitActive("Run") Send("sysdm.cpl{Enter}") WinWaitActive("System Properties") Send("{TAB 3}") Send("{RIGHT 3}") Send("!s") WinWaitActive("Performance Options") Sleep(2000) ControlClick("Performance Options", "", "Button3") Sleep(500) ;Use visual styles on windows and buttons ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Space}') Sleep(500) ;Use drop shadows for icon labels on the desktop ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up}{Space}') Sleep(500) ;Use common tasks in folders ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up 2}{Space}') Sleep(500) ;Use a background image for each folder type ;ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up 3}{Space}') ;Sleep(500) ;Smooth edges of screen fonts ;ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up 5}{Space}') ;Sleep(500) ;Show windows contents while dragging ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up 8}{Space}') Sleep(500) ;Show translucent selection rectangle ;ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up 9}{Space}') ;Sleep(500) ;Show shadows under mouse pointer ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up 10}{Space}') Sleep(500) ;Show shadows under menus ;ControlSend ('Performance Options','Tree1','SysTreeView321','{End}{Up 11}{Space}') ;Sleep(500) Send("{ENTER}") WinWaitActive("System Properties") Send("{ENTER}") TrayTip("clear tip","",0);clear tray icon balloon tip I expect GunSmokingMan will be along soon with a .vbs script as well?

Do tell? Can you explain how you did that, sounds pretty cool!

Apparently not, hope all is well with BoardBabe. I have resorted to using SpywareBlaster to keep the list up-to-date on my installs. Seems to be working well.

Well, don't let it drive you crazy . . . take a walk and clear your head. I'm rebuilding my disc today and tried HFSLIP (I love that tool) but went a little overboard, tried to incorporate EVERYTHING ("HFSLIP means no OEM" as they say), and I'm crapping out at the 9 minute mark, freezing up just as in your case. So I'm going back to tried and true manual methods. We have an MSDN disc now so SP2 is already incorporated, "one less thing" as Gump would say. Here's what I plan on doing: 1. Use the SVCPACK method to incorporate hotfixes, sticking religiously to the MSFN list for XP Pro SP2. 2. Hack the theme file and apply my own theme. 3. Incorporate Pyron's Drivers from CD method of driver install. Nothing comes close to being as easy. If later I need to incorporate SATA drivers I will cab and drop them into I386 and modify txtsetup.sif, manually, and reburn. So that's my basic disc. My $OEM$ schtick incorporates a cmdlines.txt effort that adds registry tweaks, imports a domain blocklist, renames the admin account, configures any partitions other than C: that I might have created, and autologs the admin user. It also--here's the good part--places a compiled AutoIt script on the Desktop, so after logon I double-click to run my post-install routine over the network. A drive is mapped and EVERYTHING gets done here, too much to mention, really. Somewhere along the way the routine stops and I am prompted to rename the machine, install printers via an AutoIt GUI, and install optional stuff via WPI, and then it continues. It's done when the disc pops out and the message "The installation completed successfully" appears. Some of my cohorts use it and they love it. No, it wasn't simple, been playing with individual facets for years now. It's challenging, its fun, and its rewarding. The downside, from where I stand, is the need to incorporate hotfixes and drivers into the disc, requiring a reburn. But I don't reburn as often as you might think, not a hassle really. So my question is: do you really need a fulsome network install? I don't use the method and fear it somewhat based on my experience with Ghost imaging over a network. What a nightmare! Those days are gone, thank goodness. EDIT: Also, check my edited comment above regarding $OEM$ placement!

See, that's the part that concerns me. Heaven and you are the only ones who know what that means. Are you getting stuck at the T-13 or T-12 mark? Baby-steps may be a bit of an exaggeration. No, slipstreaming a service pack and adding critical updates shouldn't cause issues, so combine them and test with a basic unattend.sif file maybe. I'm going to try BartPE one of these days.

OK, can you confirm that you used the 'Drivers from CD' method in the past? I imagine you are now trying to adapt that installation to the network? If so, you replaced the original setup.ex_ with the one downloaded from the Drivers from CD instruction page and that may be the problem. I believe you want to put the original setup.ex_ back into your install as a first step, and cut/paste $OEM$ from I386 to your CD's root as well. Me? I would rebuild from scratch and take baby-steps, testing each modification made to the source on a testbed machine. It's difficult to troubleshoot when multiple mods are made to the installation source, in my experience.

Pretty certain that $OEM$ needs to be alongside I386 when installing over a network (but inside when installing from CD). Also, aren't setupORG.exe and presetup.cmd related to the 'Drivers from CD' method of driver install? If you're installing over a network, then 'Drivers from CD' is moot, eh? EDIT: "Pretty certain that $OEM$ needs to be alongside I386 when installing over a network (but inside when installing from CD)." Nope, pretty certain that it's the other way around!

Hmm, so no need for qchain.exe then?