Product Overview

1.4 BootDisk Drivers and BootDisk Scripts

You can automate some functions using Active@ Boot Disk.

While Active@ Boot Disk is starting, you may install drivers and run scripts that can reduce the amount of time it takes to perform maintenance functions on your data storage system.

If you know that your hard drive has damaged drivers, or if you have older or uncommon RAID type or SCSI type drivers, you may create a folder named BootDisk_Drivers on the root of any logical drive and load drivers along with their configuration files into it. Active@ Boot Disk will detect these drivers and install them automatically during the boot process.


 

livecd

Before adding your own drivers, try a full version of Active@ Boot Disk (supplied after purchasing a registration key). It contains 152 driver packs for different types of USB3 controllers, Mass Storage Devices and Network cards. There is a good chance your device will be detected automatically.

 

While Active@ Boot Disk is loading (described in the next section, below), the utility searches for the BootDisk_Drivers folder in the root of all devices. That includes the floppy drive, a USB device, a working hard drive, and so on.

If Active@ Boot Disk finds .INF files inside a folder named BootDisk_Drivers, it tries to load them along with all other files required by the drivers.

Whether or not the utility loads drivers, Active@ Boot Disk proceeds to search for a folder named BootDisk_Scripts – again in the root of any logical drive. Active@ Boot Disk will run any CMD files, assuming that they are scripts.

 

livecd

Active@ Boot Disk Lite version (included in other Active@ software packages, like Active@ KillDisk) launches a primary application by default without any command lime parameters.
If you need to configure a default application to be run with some command line parameters, you need to create a proper script and place it to the BootDisk_Scripts folder.
In this case we recommend you to turn off default application launch (Boot Settings tab in Boot Disk Creator) to avoid two copies of software to be launched after boot disk start up.