ImageStor Version 1.5 Copyright (c) 1995, 1996 by McAfee Associates, Inc. New for Version 1.5 =================== ImageStor V 1.5 uses a DOS extender to allow all systems with extended memory to run the GUI ImageStor product. ImageStor can now also be run directly under Windows 95. The Make Diskette function (either via the GUI or the DOS ISBOOT program) will now use the alias files CONFIG.DSK and/or AUTOEXEC.DSK in the ImageStor installation directory to re-create the required bootfiles, if they exist. Otherwise, the boot diskette will be created by scanning the actual CONFIG.SYS and AUTOEXEC.BAT files to locate necessary mouse and ASPI SCSI drivers. FEATURE/FIX SUMMARY =================== * Integrated with Pharlap RTK for actual shippable product. * Fixed bug due to assumption that partitions would be arranged in ascending order on a disk drive. * Added "last ditch" scan of C:\ (root dir) to look for mouse and SCSI drivers if they were not discovered in CONFIG.SYS. * Added default geometry determination for blank, non-BIOS drives so that FDISK should not be required. * Refinements to help items, especially relating to preferences screen and image file usage. * Fixed bug when pressing Enter key in image file path edit box on Prefs screen. * Added support for /95 cmdline option to trigger Windows 95- specific warnings. GENERAL INFORMATION =================== Appending to tape: This version of ImageStor does not support appending images to tapes. Each tape cartridge can hold only one image. Restoring an aborted copy: If you attempt to restore a partial image (from a tape, for example), the operation will fail when it reaches the point where the original copy was terminated. The resulting disk will be in an undefined state; though it may be bootable, the filesystem will not be intact, and any attempt to use the disk may result in data loss. Trouble Shooting ================ Boot Diskette Basics When you use the "Make Diskette" function from ImageStor or run the ISBOOT utility from DOS, a bootable ImageStor disaster recovery diskette is created. This diskette contains the DOS operating system, some memory-management system files, ASPI SCSI drivers (if present), and a mouse driver (if present), as well as the ImageStor program and support files. A new CONFIG.SYS and AUTOEXEC.BAT file is created on the floppy which loads these drivers and starts ImageStor. Boot Diskette creation under Windows 95 ImageStor will attempt to locate drivers by scanning CONFIG.SYS and AUTOEXEC.BAT under Windows 95, also. But this may not be sufficient. Because Windows 95 does not require many of the real mode drivers traditionally used by DOS and Windows 3.1 for example, ASPI SCSI drivers (ASPI4DOS.SYS) or DOS mouse MOUSE.SYS) drivers), these files may not be called out by CONFIG.SYS or AUTOEXEC.BAT. These drivers may not even exist on the Windows 95 hard disk. Since you own/possess the mouse and/or SCSI host adapter hardware, you can obtain these real mode (16 bit) drivers from the hardware manufacturer. When Windows 95 did not inherit the required real mode drivers from an earlier DOS/Windows 3.1 installation, ImageStor provides an alternate method for building the boot diskette. This method may also be used to enable a network connection from the boot diskette, even in a Windows 3.1 environment. You can create the .DSK "override" files to control which drivers get copied to the ImageStor boot diskettes. This may be necessary if you are running a Windows 95 system which doesn't use DOS mouse drivers or DOS ASPI drivers. Though these drivers may not be required to run ImageStor copies from Windows 95, they will be necessary to run ImageStor restores from the DOS boot diskette. In addition, if you use a DOS-based local area network and if you copy local disk images to a network file, you can use the .DSK files to specify which network compnents need to be loaded when the floppy disk boots for a restore operation. If ImageStor discovers the files CONFIG.DSK and AUTOEXEC.DSK in the ImageStor installation directory, it will use these files as templates for CONFIG.SYS and AUTOEXEC.BAT on any boot diskettes it creates, rather than performing the default file scans. In addition, any drivers referenced within these two files will be placed on the boot diskette. Note that everything in these files will be used for the boot diskette; keyword matching is not performed in this case. The CONFIG.DSK and AUTOEXEC.DSK files allow ImageStor to build a customized boot diskette for your particular system, including network drivers, if desired. When the necessary DOS drivers do not exist on your disk drive, you may place them in the ImageStor installation directory itself. In in event, ImageStor will always use the paths you specify in CONFIG.DSK and AUTOEXEC.DSK to locate these drivers and copy them to the boot diskettes. If the .DSK files do not exist, ImageStor will scan the root directory for MOUSE or .SYS files and use these to create a bootable disk. If an AUTOEXEC.BAT file doesn't exist, ImageStor will create on using a default template. Run Modes ========= ImageStor will run under a Windows 95 DOS box with no problems. This can be done by simply double-clicking the filename under Windows Explorer, by selecting ImageStor from the Start menu, or by creating a "short-cut" on the desktop. Another way to run ImageStor is from DOS. This can be done by "shutting" Windows 95 down to run in MS-DOS mode or by pressing F4 at boot time and selecting MS-DOS mode from the menu that will come up. The last way to run ImageStor is by floppy. The can only be done if at installation time, you chose to create the boot diskette. This diskette can be left in the floppy drive and you should have full access to your disk(s) for copy to disk/lan/tape drive. If copying to an image on the network drive, you may need to load the network drivers from another floppy (if your boot disk is trashed) or from the C: drive subdirectory where they are held. This will allow for network access. Possible SCSI Problems ====================== If using a SCSI tape drive with a SCSI hard and you are daisy chaining, make sure there is no conflict with the SCSI ID. Each device needs to have its own SCSI ID. Other possible problems could arise due to pin orientation on the SCSI cable, a bent pin, a bad cable, a bad terminator, double termination or no termination on the SCSI chain. You should also verify that the tape drive can cycle a tape, to ensure that drive recognizes a tape in the tape drive.