I'm using Norton  Ghost 2003 and trying ti do the Nightowl bootable CD thing  but It  stops on the   A prompt for DR Dos.I  went to F:\Norton Ghost & ckicked on Ghost exe & got  this "double  fault at EIP or (ELP)=1d5; Flags=3a86.There was several more lines but did't get them (I can go back & copy them & repost but it will be tomorrow if they matter)so I guess
the problem is with the Ghost.exe file.I reinstalled Ghost 3 times but it was the same each time.Is it possible to get a Ghost.exe somewhere & install to see if there is a difference ? I am open to any suggetions & will appreciate any info.What is worse than not having Ghost is not being able to make it work.
Thanks

Here 'ya go

config.sys
device=oakcdrom.sys /d:nightowl
lastdrive=z

autoexec.bat
path=a:\;x:\
mouse.com
mscdex.exe  /d:nightowel  /l:x  /m:16 v
ghost.exe

Thanks for the prompt reply.Hope this is what you need

j c ames

Quote:

What files have you placed in that bootsector image *bootcdp1.ima* above?

Quote:

Not sure I understand this reference in your first post--if following the Guide steps, *ghost.exe* should be present on the virtual A:\ drive that a bootable CD creates from the CD's boot sector list of files.  But you are switching to F:\ ?

And, once booted to DOS, the DOS interface is what's know as a *command line* OS--you can not *click on* a file and have it execute like in Windows--you have to change to a given directory (or have it listed in the *path* statement), and then *type* the name of the executable file at the DOS prompt to lauch it--i.e. *ghost.exe*.

At the A:\ prompt, after booting, type *dir*--is your *ghost.exe* listed?

Quote:

Typo errors in posting?--or errors in the *autoexec.bat* file?  Your optical drive will not be correctly assigned a drive letter with this--should be:

[autoexec.bat]

path=a:\;x:\
mouse.com
mscdex.exe  

/d:nightowl

 /l:x  /m:16

/v

ghost.exe

But the above should not have any bearing on *ghost.exe* not launching.

J C Ames

Well--I don't see anything wrong with the list of files.

What do you get with the directory command at the A:\ prompt?

J C Ames

Quote:

Do you have a system with SATA HDD's?

Have you updated Ghost 2003 using Live Update after the initial install?

J C Ames

Quote:

Ah!...well you may be having a hardware/software incompatibility with running Ghost in DOS.

Here's a reference that talks about a couple ways others have dealt with the issue:

Norton Ghost Sata problems

SATA HDD's and Ghost!

Looks like the most common *fixes* are:

1.  In some BIOS's, changing the setting from *normal* or *native* to *combination*--

Quote:

2.  Starting Ghost with the following command line:

*ghost.exe -fni*

According to the thread, this allows access to both IDE and SATA HDD's.

3.  Or, staring Ghost with the following command line:

*ghost.exe -noide

This allowed for SATA HDD access, but now could not access other IDE HDD's if they too where on the system (this might also prevent access to optical drives that are hooked up to IDE controllers as well--don't know this for sure though).

4.  Live Updating Ghost 2003 to the most current version seemed to help some.  To check you version of DOS Ghost 2003, open a *command window* in the sub-directory where your *ghost.exe* program is located, and type *ghost.exe -ver*.  Here's what I get:

Quote:

There are a number of other suggestions scattered throughout the thread.

Let us know if/what works for you!

NightOwl wrote on Mar 10^th, 2006 at 9:11am:


I have Ghost v10.  When I run the driver validation tool from the cd, it tells me the following:

The following devices do not have drivers in the Symantec Recovery Disk.
Intel(R) 82801GBM SATA AHCI Controller
Intel(R) PRO/Wireless 3945ABG Network Connection

Like a lot of people with laptops, I do not have a floppy drive, so I cannot load the SATA drivers by hitting F6 when the Ghost cd boots.

OK, so here are my questions:
1. Can I create a bootable cd that contains Ghost 10 and the SATA drivers?  Is this difficult to do?  I generally know the basics of computers, but I'm no IT wizard.

2. When I switch the SATA setting in the BIOS from "AHCI" to "Compatability" mode, Ghost can see the hard disk.  I was able to do a mini-test by restoring a small folder to the hard disk from a partition backup I had stored on a USB drive.
Is there any drawback to using Ghost while the BIOS setting is "Compatibility"?  If my boot partition became FUBAR'ed, and I restored a backup to the boot partition while the disk is in "Compatibility" mode, would there be any difference relative to doing the recovery while the disk is in "AHCI" mode (other than Compatibility mode being slightly slower, presumably)?

If not, then it would seem that it's really not worth the trouble of creating a boot cd with Ghost and the SATA drivers.

3. How are people getting to the command prompt to run things like
"ghost.exe -fni"?  Ghost 10 cd boots straight into a GUI.  Is the command line part of earlier versions of Ghost?

TIA for any advice on the above!

Brian wrote on Apr 2^nd, 2006 at 11:29pm:


The MSFN pages are talking about integrating drivers into a Windows install cd.  How did you go about integrating drivers into another program's cd?