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

Marble

Post a copy of your *config.sys* file content, + copy of your *autoexec.bat* content--and a list of files you are placing in the boot sector.

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

Sorry for all the screwups.Not a good morning
boot sector
bootcdp1.ima

j c ames


Quote:

bootcdp1.ima

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


Quote:

went to F:\Norton Ghost & ckicked on Ghost exe & got  this "double  fault at EIP or (ELP)=1d5; Flags=3a86.

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:

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

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.

The owel & v are typo's (I'll try to do better)
Files are
autoexe.bat
config.sys
ghost.exe
nouse.com
msdos.sys
command.com
io.sys
mscdex.exe
oakcdrom.sys
The F: was when the bootup stopped on the DrDos A: prompt
I changed directories to F:then typed in  ghost.exe
& got that message.
When I read your answer to this post (so I can try to answer any questions you may have) I will reboot & send you an
A: prompt directory list
Thanks

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?

UPDATE
I took a deep breath walked around the block 6 times took a short nap deleted all the files I had created & started all over (your program worked flawless this time)
Some joy but not completely.Everything goes right till it boots to ghost then the blue screen with the hourglass comes  up but nothing happens..The hour glass is there but it doesn't turn so what have I done wrong this time ?  One time at the blue screen I let it run for 15 minutes & nothing happened .I have reinstalled ghost but no joy.
I really appreciate all the help you have given.Any other suggestions ?
Thanks

J C Ames


Quote:

Everything goes right till it boots to ghost then the blue screen with the hourglass comes  up but nothing happens

Do you have a system with SATA HDD's?

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

I have sata HDD.
Will update & keep you informed

J C Ames


Quote:

I have sata HDD.

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

(NightOwl edit:  9-7-2006, apparently the above link has gone *bad*--too bad--it had some good troubleshooting info!)

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:

Working on a Dell SX 280 I was able to change the BIOS settings for the SATA controller to Combination. The default is *normal*. This worked. I am ussing Ghost 7.5 enterprise. Dannypcs

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:

C:\Program Files\Norton SystemWorks\Norton Ghost>ghost.exe -ver Norton Ghost 2003 (build=793, cdrlib=3.1.25) Copyright (C) 1998-2003 Symantec Corp. All rights reserved.

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

Let us know if/what works for you!

Update
I went to the automatic update & it downloaded & installed the latest but it didn't  help.I'm going to try all the other suggestions
when I have time.I'v got to slack off for a while (must earn a living) but  I'm not quitting 'till it's working or I die.Iwill keep you posted as to what is taking place but I'm going to start another thread.I will call it"update on Ghost " I really appreciate you sticking with me on this so maybe it will be solved down the line.If you come up with any more suggestions just post it to a new thread (update on ghost  & I will know it is from you
Thanks again

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

Looks like the most common *fixes* are: 1.  In some BIOS's, changing the setting from *normal* or *native* to *combination*-- 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: There are a number of other suggestions scattered throughout the thread. Let us know if/what works for you!

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!

serpico,

It can be done and I've added NIC drivers too. I'm sure Ghost 10 can be edited the same way as Ghost 9.

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1113183318

When I tried anything other than AHCI/SATA in the bios, my computer wouldn't boot so I needed a CD solution.

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

serpico, It can be done and I've added NIC drivers too. I'm sure Ghost 10 can be edited the same way as Ghost 9. http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=general;action=display;num=1113183318 When I tried anything other than AHCI/SATA in the bios, my computer wouldn't boot so I needed a CD solution.

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?

I used UltraISO to make an .iso file of the Ghost CD. You then extract the txtsetup.sif and edit it in Notepad. When finished you drag this file as well as the latest iastor.inf and iastor.sys into the relevant folders in UltraISO, save the .iso and then burn to CD. The hardest part is finding the correct txtsetup.sif edits.

Brian wrote on Apr 3^rd, 2006 at 12:24am:

I used UltraISO to make an .iso file of the Ghost CD. You then extract the txtsetup.sif and edit it in Notepad. When finished you drag this file as well as the latest iastor.inf and iastor.sys into the relevant folders in UltraISO, save the .iso and then burn to CD. The hardest part is finding the correct txtsetup.sif edits.

OK, I think I get the gist of it.  You are editing the .sif file, telling it to look for iastor.inf and iastor.sys, which are now part of the new cd.  What about iastor.cat?

How did you figure out the right edits to make?

When you look at the txtsetup.sif it will start to make sense. Iastor.cat doesn't need to be changed.
I was lucky. I just copied the edits that were in the web page I quoted. I haven't looked at it since then so I don't know whether they will work for you but it is likely that they will.

I just had a look at the txtsetup.sif of Ghost 10.


Quote:

iaStor="Intel(R) 82801ER/FR/GR/GH SATA RAID/AHCI Controller"

There is no GBM. Which you knew anyway. The layout of the txtsetup.sif is completely different to the Ghost 9 file. Sorry.

Brian wrote on Apr 3^rd, 2006 at 12:58am:

When you look at the txtsetup.sif it will start to make sense. Iastor.cat doesn't need to be changed. I was lucky. I just copied the edits that were in the web page I quoted. I haven't looked at it since then so I don't know whether they will work for you but it is likely that they will.

I found another (similar) method.  This guy modified his Drive Image cd to include SATA RAID and NIC drivers.  If his method works, it's great in that it doesn't require much editing, which as you point out, is the toughest part.  He just changes one line to point to one folder containing the SATA drivers.  I'll give it a shot once I get my hands on an ISO editor.

"Thanks to your pointer, and some research, I've found out that Drive Image 7
/ V2i Protector use the Windows PE (Pre-installation Environment) for their
'boot disk' Power Quest Recovery Environment (PQRE).  WinPE is the actual
W2K, XP, 2K3 installer platform.

Also, with a little noodling, I found out that not only can you use the F6
key at startup to manually add a mass-storage (although not any other type
driver), but you can modify the disk to make it a automatically include, not
only the mass-storage hardware of the 8KNXP, but also the on-board Intel NIC
as well.

Here's the steps I performed to successfully make the Drive Image disk
support the 8KNXP SATA RAID and the on-board Intel NIC:

I) Generated an ISO file from the existing CD
II) Edited the ISO file
A) SATA RAID Support
1) Deleted the (unnecessary extra) sub-directories in
\I386\SYSTEM32\DRIVERS\ADDITIONAL_OEM\
2) Created a sub-directory called INTEL_ICH5R in
\I386\SYSTEM32\DRIVERS\ADDITIONAL_OEM\
3) Copied the ICH5R XP boot drivers -- IASTORE.CAT, IASTOR.INF, IASTOR.SYS,
AND TXTSETUP.OEM -- to the new
\I386\SYSTEM32\DRIVERS\ADDITIONAL_OEM\INTEL_ICH5R sub-directory
4) Edited the OemDriverDirs= line in \I386\SYSTEM32\WINPEOEM.SIF to read
OemDriverDirs=INTEL_ICH5R
B) On-board Intel NIC
1) Using the latest on-board Intel NIC drivers, replaced the E1000325.INF in
\I386\INF
2) Using the latest on-board Intel NIC drivers, copied the E1000325.CAT to
\I386\INF
3) Using the latest on-board Intel NIC drivers, replaced the E1000MSG.DLL in
\I386\SYSTEM32
4) Using the latest on-board Intel NIC drivers, replaced the E1000325.DIN in
\I386\SYSTEM32
5) Using the latest on-board Intel NIC drivers, replaced the INTELNIC.DLL in
\I386\SYSTEM32
6) Using the latest on-board Intel NIC drivers, replaced the PROUNSTL.EXE in
\I386\SYSTEM32
7) Using the latest on-board Intel NIC drivers, replaced the E1000325.SYS in
\I386\SYSTEM32\DRIVERS
III) Burned the edited ISO as an image to a new (bootable) CDR

The end result was a new boot CD which automatically included the SATA RAID
and the on-board Intel NIC drivers.  I suppose one could just as easily add
support for the GigaRAID and/or the 8KNXP-Ultra SCSI XP boot drivers by
likewise adding driver sub-directories to
\I386\SYSTEM32\DRIVERS\ADDITIONAL_OEM\ and pointing to them in the
OemDriverDirs= line of the \I386\SYSTEM32\WINPEOEM.SIF file."

Brian wrote on Apr 3^rd, 2006 at 1:25am:

The layout of the txtsetup.sif is completely different to the Ghost 9 file

Actually it's the formatting that threw me. They are not all that different at all and an edit is worthwhile if your other approach fails.

Brian wrote on Apr 3^rd, 2006 at 5:34am:

Actually it's the formatting that threw me. They are not all that different at all and an edit is worthwhile if your other approach fails.

OK, the other approach didn't work, I'll have to try your way.
Did you set up a RAID controller or an AHCI controller?  If AHCI, why didn't you also copy iaahci.inf to the new ISO?

Brian, three coasters later . . . success!

I'll post  a new topic explaining how to do this for Ghost 10.

Thanks for your help!

serpico wrote on Apr 3^rd, 2006 at 12:00pm:

Did you set up a RAID controller or an AHCI controller?

The only setting that is bootable in my BIOS is "RAID Autodetect/AHCI".