I have a Boot CD with a DOS version of Ghost in it (Ghost 11). I used to use it for booting a PC, running Ghost from there, and creating an image of a hard drive partition. For Symantec Ghost Solution Suite 2.5.x and Symantec Ghost 11. DOS command prompt in the Advanced. Incorporated into the Ghost program (Ghost.exe.

Archived from groups: comp.sys.ibm.pc.hardware.storage () We are using Ghost ver 7.5 or something like that. This has worked fine a hundred times in the past. I create a network boot disk with the ghost wizard. I boot the computer with it.

Once i get to the A prompt I type ghost.exe and it loads the ghost program. Works everytime fine.

Today I am trying to ghost a new computer. So i created a new boot disk with these broadcom netxtreme drivers. It boots fine and maps a network drive fine. However, when i put the ghost program floppy in and type ghost.exe at the a prompt, the cursor just goes down the next blank line. It blinks and just hangs there.

The ghost program doesn't load. It just hangs on that screen, ad infinitum. Is this a PC Dos memory problem??

If so how to i resolve it? Archived from groups: comp.sys.ibm.pc.hardware.storage () I found an older version of the ghost.exe from 1999. Antariksh ek amar katha all episodes download in zip file online. When I launch that one the program actually loads. However, when i try to create the image it errors saying, NTFS Error: Error reading FILE_VOLUME MFT record.

I just can't win. Any idea why i'm getting this error? The ghost exe that was hanging is from 2001. When I check the properties on it, it was created on Dec 1, 2001. > What happens if you boot using the Ultimate Boot CD, > and selecting Bart's Network Boot on that, and then > run ghost from a floppy after that has booted? I booted from Ultimate Boot CD got to my network, mapped a drive, and then ran the ghost.exe from the network.

It hangs too. Just like the other way. > And you still need to work out exactly which ghost version you are > using to get much useful in the way of comments if its a subtle problem. When I launch any of the ghost programs on the server that I installed it (symantec ghost console, ghost explorer, ghostcast server) and click on help> about, they all list Program Version 7.5.0.335.

Thanks for your help! Archived from groups: comp.sys.ibm.pc.hardware.storage () wrote in message news.770@f14g2000cwb.googlegroups.com. > > is this a PC Dos memory problem??

If so how to i resolve it? > Ah an MCSE in distress. C'mon, do some basic trouble shooting yourself first so you can tell us what's been tried sofar.

- if you're using Caldera DOS try different DOS version - does Ghost load with a clean boot diskette (so without network)? - how much free mem after loading NIC drivers etc. - that kind of stuff.

Then of course you check the Symantec KB to see if this is some kind of known problem. > We are using Ghost ver 7.5 or something like that.

Ah, or something like that. I can see you're very keen on getting this fixed.

Archived from groups: comp.sys.ibm.pc.hardware.storage () > When I launch any of the ghost programs on the server that I installed > it (symantec ghost console, ghost explorer, ghostcast server) and click > on help> about, they all list Program Version 7.5.0.335. > > Thanks for your help! > Workaround Depending upon the mix of SATA and IDE drives installed to your system, one of the following switches should resolve the problem: a. If you have an IDE and an SATA drive, or only IDE drives: -FNI Forces Ghost to use the BIOS to gain access to the IDE drive. If you have an SATA drive and no IDE drives: -NOIDE Disables access to IDE devices. Archived from groups: comp.sys.ibm.pc.hardware.storage () wrote in message news.790@o13g2000cwo.googlegroups.com. > i created a boot disk with ms dos this time rather than pc dos.