CUSTOM BOOT
Menu location: GO > System > Custom Boot

Custom Boot will allow you to run your own commands when the CD boots. If present in the root directory of C:\, the files aubcd1.cmd and aubcd2.cmd will run automatically. The files may exist independently or concurrently. They will run synchronously in that no subsequent boot processes continue until execution is completed. The CD boot process is as follows:

run aubcd1.cmd
. . .
load networking
load wallpaper
load Remote Administrator server
load VNC callback (if c:\vnc.tok exists)
. . .
run aubcd2.cmd

The important thing to remember is that aubcd1.cmd runs before networking support is loaded and aubcd2.cmd runs afterwards. So, if you want to write a script to perform a backup to a local USB hard drive, then reboot the computer, aubcd1.cmd would be preferred since no network support or remote access is necessary.

Example of aubcd2.cmd script to turn computer into a file server:
::===Share drive. Edit username, password, drive letter on "net share"
setlocal
set _user=username
set _pass=password
bartpe.exe -c s -i ms_server
net start server
renameuser.exe Administrator %_user%
net user %_user% %_pass%
net share c=c:\ /grant:%_user%,FULL
endlocal

For examples of custom backup scripts, see Acronis True Image Backup.

Installing drivers for hardware that is not supported on Alan's Ultimate Boot CD: Alan’s Ultimate Boot CD (AUBCD) includes drivers for the most popular network cards and SCSI controllers. In such instances where the driver for your particular hardware is not included, there is a procedure, using Custom Boot, for installing drivers “on-the-fly”:

1) Boot the computer hosting your particular piece of hardware into Windows 2000, XP, or 2003. Other operating systems probably won’t work for this procedure since AUBCD is not compatible with drivers outside the three listed. Make sure the hosting computer already has the proper driver installed and the hardware is operating properly.

2) Start AUBCD so that the small GO button overlaps the Windows Start button, then click GO -> Programs -> Utilities -> Driver Backup/Restore. Close the registration nag screen.

3) Click the Collect All icon, highlight your particular piece of hardware in the list, then click the Backup icon. Save the backup log file for later use. As an example, a USB controller generated the following log file:
New directory created C:\Drivers\Intel(R) 82371AB EB PCI to USB Universal Host Controller
Retreiving and copying files ......
C:\WINDOWS\System32\drivers\usbd.sys
C:\WINDOWS\System32\drivers\usbehci.sys
C:\WINDOWS\System32\drivers\usbport.sys
C:\WINDOWS\ServicePackFiles\i386\usbohci.sys
C:\WINDOWS\System32\drivers\usbuhci.sys
C:\WINDOWS\System32\drivers\usbhub.sys
C:\WINDOWS\System32\usbui.dll
C:\WINDOWS\System32\hccoin.dll
C:\WINDOWS\Inf\usbport.inf

Package created successfully!

4) Choose a convenient location for storing your driver so that when AUBCD is booted, the storage location is accessible. A USB flash drive is convenient for portability but it may present a problem if the flash drive is not accessible before its own drivers have loaded during the boot stage. In such a case, a superior location would be a folder on the hard drive such as C:\drivers. When in the field, you can still carry your custom drivers on a portable flash drive and copy them to the C:\drivers folder before booting AUBCD. After choosing the folder, click the Start button which will copy the current Windows drivers to that folder.