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.
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. I did that under Win Vista, Win 7, Win 8. Now I have a PC with Windows 10 and no CD reader. My intention is to be able to backup and restore images, without having Ghost installed in my system. Nov 6, 2017 - DOS. Topics Ghost. Identifier Norton.Ghost.11.5.Corporate.DOS.Boot.CD_201711. The Vintage Software Collection.
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.
When I launch that one the program actually loads. However, when i try to create the image it errors saying, NTFS Error: Error reading FILEVOLUME 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 CDand 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 [email protected]. 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 [email protected].
i created a boot disk with ms dos this time rather than pc dos. It boots to network fine and maps network drive. I launch ghost.exe and it still hangs. Same problem.
New PC you say? Does it have onboard SATA?
I have had to either disable SATA (if its unused) or adjust the settings to 'legacy mode' for ghost 7.5 to work. Really, you should try to put more effort into your post like spending the 1 minute it takes to find out EXACTLY which version you are running. Archived from groups: comp.sys.ibm.pc.hardware.storage wrote in message [email protected]. ok i think i figured it out. Is it the serial ATA? If so i don't think i can disable it since it's connecting my HDD.
Yes this is a brand new computer, DELL. Does the BIOS contain any SATA options like 'legacy mode' or something like that? If so, try it.
If I am not mistaken, I have used ghost 7.5 on SATA drives using this option on an Intel motherboard. Archived from groups: comp.sys.ibm.pc.hardware.storage wrote in message [email protected]. gee don't you think if i would have known to try those things, i would have. That's what i'm posting on here for. That was a comment on your silly stuff about him needing psych help.
You should just do what he suggested you do on the basics instead. i created a boot disk with ms dos this time rather than pc dos. it boots to network fine and maps network drive. I launch ghost.exe and it still hangs. Same problem.
So what happens if you use a standard bootable floppy instead with no network with ghost on it? Does that hang too? Likely it will and its something ghost doesnt like about the new PC. That test eliminates some oddity with the different NIC drivers etc. 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? 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.
A ghost as old as 7.5 may be having a problem with something more recent like SATA on a new PC. Archived from groups: comp.sys.ibm.pc.hardware.storage wrote in message [email protected]. I found an older version of the ghost.exe from 1999. When I launch that one the program actually loads. However, when i try to create the image it errors saying, NTFS Error: Error reading FILEVOLUME 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 CDand 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! Likely its just to old to be able to handle SATA. Try ghost 9 if you can. Archived from groups: comp.sys.ibm.pc.hardware.storage wrote in message [email protected].
gee don't you think if i would have known to try those things, i would have. What we think is irrelevant, you better do some thinking of your own first. Some facts about what has been tried are. i created a boot disk with ms dos this time rather than pc dos. It boots to network fine and maps network drive. I launch ghost.exe and it still hangs.
Same problem. Yes, however at that point you didn't exclude the NIC drivers etc.
Whole point of troubleshooting is eliminating points of failiure. Please get professional help for your psychological issues. Wow, snappy dude! Or also one of your areas of 'expertise'? Just to add to this thread. I had a very similar problem with a machine using an Intel D915GAG motherboard.
I don't know if the problem was related to the motherboard, per se, but this was one of the few machines that I've had a problem getting to boot properly with either a standard 'universal' Ghost boot CD or even a custom boot CD with the specific NDIS2 driver. Anyway, my 'problem computer' had a WD SATA HDD and a SATA DVD-RW. The universal CD appeared to be working properly. The system would boot just fine, etc.
When Ghost started to load, it would freeze up. The fix was creating a new Ghost Boot CD (using the Universal driver) and simply adding -NOIDE as a parameter when booting Ghost. Or, of course, if you're booting the machine manually and then running Ghost from a command prompt, type: 'ghost.exe -NOIDE' That's all. I hope this helps someone!! Mike BTW, I'm using Ghost v11 (Symantec Ghost Solution Suite 2).
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |