This document provides general support for possible problems with the
Rescue Disk program. 


Rescue problems generally fall into 2 categories, with sub 
categories...

Problems creating the rescue set (covered in Part I of this 
document)
            a) Initializing problems
            b) File copying problems

Problems booting from the rescue set. (covered in Part II of this 
document)
            a) Missing files problems 


Part I: 


Initializing problems
*********************

Problem: My a: drive doesn't show up on the list of drives on the 
Rescue window.

Solution: You may have a 5.25" drive set as the a: drive. Rescue will
only work on 3.5" (1.44 Meg) floppy drives set as the a: drive. If you
have a 5.25" floppy drive as the a: drive and a 3.5" floppy drive configured
as the b: drive, reassign the drive letter designations so that the floppy
drive letters are switched. 


Problem: When I run Rescue, it freezes up the computer while Rescue is 
initializing and I have to reboot to get the computer working again.

Solution: You can have freezing problems, or crashes, with rescue for a 
few reasons

1. Corrupted rescue files.
2. Program conflicts.
3. Registry problems.


To resolve problems with corrupted rescue files, do the following:

1. Re-install the program that included Rescue Disk.


To resolve problems with program conflicts:

a) Close all programs down before running the program again. To check if 
you've shut down all programs, press the CTRL-ALT-DEL keys. This should 
produce a Close Programs box. Inside this box should only be one or two
applications, namely Explorer and Systray. (Note: On some systems, it may be
shown as Windows Explorer.)
b) Click on the windows Start button, click on RUN, and type the following:
RESCUE32 /RESET
c) When you click on the OK button, the Rescue Disk window should appear. 


To resolve problems with the registry:

a) You'll need to use a utility program, such as the Optimization Wizard
(a component of Norton Utilities), to keep the registry in proper condition
so that programs may run correctly.


File copying problems
*********************

Problem: When I hit the Create button, rescue reports that "Certain Files
could not be copied." What do I do?

Solution: On that message, you should see a Details button. If you click on
this button, another screen should appear with a list of files that could
not be copied. Click on the plus sign next to each file to find out why the
file could not be copied to the disk.

If the reason is "file not found," do a search for the requested file(s) to
see whether it exists on the drive. If the file(s) is not on the hard drive,
proceed with the creation of the rescue set as the file(s) may not be
necessary. After all the files are copied over to the disk, you'll be
asked to reboot to test the rescue set.


Problem: Rescue reports that PARTINFO.DAT cannot be copied over to the disk.

Solution: PARTINFO.DAT is the file that stores a copy of the partition data
on your computer. If you have an IDE or ATAPI zip drive, make sure it is not 
configured in the BIOS settings as it can cause this error to appear. You can
look at these settings from a setup program that can run when your computer
is booting up. Usually, you will see a message on bootup to enter a setup 
utility by pressing F1 or Del. It is from this program that you can see 
whether the zip drive is listed among devices attached to the IDE ports on
your computer. You can set up the port that contains the zip drive to NONE,
instead of AUTO, to stop the BIOS configuration of the zip drive from
occuring.

Note: this error is also common if you have security software like Your
Eyes Only, or if you have NTFS partitions on the hard drive.


Problem: When rescue starts to copy files over, I see a Disk Write Error
message on the screen.

Solution: The floppy diskette may be physically damaged.

Try to full format the floppy. Double-click on My Computer and right-click
on the a: drive. Choose Format, followed by Full Format on the next screen.
If the format procedure fails, the disk (or drive) is likely damaged. 


Part II:


Missing Files
*************

Problem: When I reboot with the rescue set in place, I am left at a blinking
a: prompt.

Solution: The startup files on the rescue floppy diskette were probably
not created correctly, and so the rescue program will need to be reset. 

a) Click on the Windows Start button, click on RUN, and type the following:
Rescue32 /RESET
b) When you click on the OK button, Rescue Disk window should appear. 


Problem: When I bootup with the rescue set, I see the a Non-System Disk
error on the screen.

Solution: Try creating a new rescue set using a different floppy, if the 
problem persists, reset the rescue program as follows:

a) Click on the windows Start button, click on RUN, and type the following:
rescue32 /RESET
b) When you click on the OK button, Rescue Disk window should appear. 


Problem: When I bootup with the rescue set, the floppy drive is accessed for
a moment and the screen freezes.

Solution: Try the solution listed to the problem above. If the problem
continues, replace the diskette as the system area on it is probably
faulty.


**********

For additional information please see the readme.txt file in the Rescue Disk
folder.
