lopwed.blogg.se - Allmänt

VBS file type association (don't forget to call restore_vbs_assoc.bat at the end of the installation to restore the original file type association).Īnd last but not least, log the results of each action of your install scripts. VBS with Notepad, as a safety precaution, to block macro viruses.Īlways run VBScript files with the CSCRIPT command, or use my VBSAssoc.bat to temporarily change the. Check the current Windows version, and if necessary write different subroutines for each Windows version.After issuing any command, check its return code or " ErrorLevel" to see if it succeeded or failed.Use "%~dp0 command_name.exe" if an executable is located in a batch file's own startup directory. Use the full path to files and executables if possible, instead of assuming they will be located in the current directory.

This is explained on my Clever Tricks page. For example, a batch file's startup directory can be made the working directory by starting with the command PUSHD "%~dp0" (don't forget the POPD command at the end of the batch file).Verify your assumptions, or make them true: VBS extension will be associated with CSCRIPT.EXE, don't assume DIR won't display hidden files,.

don't assume Command Extensions will be enabled,.

don't assume the first partition or even the first harddisk is the one where Windows is installed,.

don't assume write access to the current directory, nor to HKEY_LOCAL_MACHINE,.

don't assume a batch file's startup directory is its working directory (fails when started from UNC paths),.

don't assume CapsLock will be off when using SendKeys( ) to enter passwords,.

don't assume someone is logged in when using SendKeys( ),.

When you write scripts for unattended installations, try to assume as little as possible:.

A must-read if you are going to prepare unattended installations: Unattended/silent installation switches for Windows apps at.

Unattended installation procedures for specific software.

The installation commands or scripts are roughly categorized: I won't restrict myself to a single script language, the goal is Windows itself, though some links will be provided. Windows (NT 4 and later, not 9*/ME), not on installing The main focus will on installing software, drivers, etcetera in Silent installations are installations without any visible interface elements. My definition of an unattended installation is any installation that does not require user input but may display dialogs or progress bars etc. On this page I'll collect (links to) sample scripts and commands for unattended and silent software installations (and migrations). VoltCraft Energy Logger 3500 Configuration.