Does norton ghost 2003 support sata

Some symantec employee will show up sooner or later and tell you to go to the backup exec forums to Probably because I suggested it because anytime someone comes here and posts about norton ghost in Broadcom Employee.

Migration User. Posted May 13, PM. Reply Reply Privately Options Dropdown. I've seen on other forums that does not work with SATA drives, can you please tell me what version of Ghost will work? Some symantec employee will show up sooner or later and tell you to go to the backup exec forums to ask this question because ghost solution suite is not the same thing.

Probably because I suggested it because anytime someone comes here and posts about norton ghost in this forum someone with a "symantec employee" tag says to put it there because norton ghost is not the same product this forum deals with.

Regards, Ranger P. It's Friday arvo. I'll be back in 48 hrs. Ciao for now. Reply 6 - Apr 19 th , at pm. After several tries I finally was able to bring my version of ghost up to the. In Googling sata backups I have read all kind of horror stories of people trying to ghost sata drives permanently locking their system up with irreversable consequences. My new system will shortly arrive with at least one sata boot or system drive. It has always been my custom to ghost a new setup after every two or three software installations.

If I run into trouble that way I can go back similar to system restore to a previous install and start over from there.

Since the early 90's I have produced scores if not hundreds of images of my hard drive. I cannot think of any major problem I had with any of these "disk to image" efforts. Is there any thing I need to be aware of before starting a backup of my new system?

I used Night Owl's formula for creating a boot disk and put it on one of my thumb drives. It is lighting fast and has never failed. Do I need to change any of my settings or re-set any special parameters or switches on the thumb drive before attempting a back up of the sata drive. After updating ghost to the. Hopefully this was the correct thing to do. Any other suggestions would be greatly appreciated HELP! Reply 7 - Apr 19 th , at pm.

Thanks edarnell; Rad; Christer and Jer Hi Jerry, Not unlike you your method, I have multiple partitions with clones of each progressive build so hopefully you don't have to go right back to the start if something goes wrong. Re "How to obtain program updates that are archived on Symantec LiveUpdate server. Be careful with the instructions you find at this link. The 'symantics' for me didn't line up. The upgraded program is probably fine, but "how to get there" I've tried it three times - something is not written in these instructions that should be.

Whether partition to partition within the same drive or between a pair of these drives, both my GB SATA drives have always worked fine with this version of Ghost Therefore, I don't think Ghost v. When I rebooted the system with my trusty v. All I got was a title page and a frozen egg timer. With the P4 systems, no problems, I managed to clone partition to partition - easy. No so however with the Q system. After installing the program, everything seemed to be going fine.

While in Windows, I set things up for Ghost to clone P1 to P10, however after I executed and the system restarted, it only got to display the first screen with a title and frozen egg-timer. The new system had locked up. When I manually shut down and rebooted, I found i was locked into a loop. The on screen display had the following text mesages. Enter a choice. If no action is selected the computer will return to DOS within X seconds. Even if I chose the option to reboot to Windows by typing "ghreboot" and hitting enter as instructed it was still dead.

When scrolled down a new message appeared, "Internal stack overflow. System halted. Anyway, I ended up having to re-install Win XP from scratch, but there's no point doing anymore until I can find an effective way of upgrading the Ghost boot disk to v.

I'm determined to get this right and then document it.. Reply 8 - Apr 19 th , at pm. What procedure did you use to update to ? Must have the faster fingers. Reply 9 - Apr 20 th , at am.

Ranger Just the kind of horror stories yours I was talking about in my post. In upgrading my version of ghost I followed directions here in the forum which pointed me to It's the time you eat up with trial and error That's what I want to avoid up front.

Hopefully someone here will be able to jump in and provide some help I should get my new system next week sometime, and so am stymied for now. I don't want to install my array of software without being able to make incrimental backups with ghost as I go along Jerry aka jerliz. Since my initial post, I've come across more information that strongly suggests that 1 TiB is the maximum destination HDD size limit for Ghost It also appears that this is a hard disk not partition size limit, much like the GB bit LBA limit.

You bring up a good point - I don't know what the maximum source HDD size limit would be. That would be interesting to test and experiment around with.

Yes I also noted the erroneous info cited about Ghost vs. However, I'm not familiar with the cdrlib parameter you mentioned. What exactly is that? You must've edited your initial reply as I don't recall seeing that. Thanks, and yes that's exactly where I got the technical information about 1 TiB being the likely size limit.

I'm also a member of that forum BTW and did post a similar inquiry. PDR driver will handle the full 2TiB. I have written a Patch that allows 2TiB Partitions to be used. Prozactive: Yes, I edited that post and added the info, but forgot to enable the "Edited by" field, which is not mandatory and is off by default for smods.

Hi all, im not sure im i out of topic to reply this at here. I had try to make partition to both drive GB, but still unable to dectect. I would love to know if there have a solution for the ghost DOS version, can use for the harddisk GB and above. Thanks for reading. You pulled this thread out of the dusty vaults! Well that's a long complex topic that's been extensively discussed both in this forum and in Radified forums, but off the top of my head, it's been fairly well established anecdotally that Norton Ghost has around a 1 TiB maximum HDD size limit.

There are a lot of technical factors and caveats that go into that, much too long to concisely explain here. Your best bet is to search this forum and Radified forums for this topic. But yes, GB should be well within the capability of Norton Ghost Any idea how to update to version 8. I've gone through Live Update two or three iterations were required and this brought Ghost 8. It's a typo.

The correct version is 8. Me and my typos! Thanks, Den!!! I recently encountered an issue with Ghost 8. Searching for solutions on the 'net all said to run 'scandisk' or similar tools to correct for disk corruptions. However, all tools I could find, reported nothing wrong with the disk data structure. Also, the other hard drives on the same machine did not exhibit this random error when backing up their partitions, just the WDC drive. That is indeed strange. I also wonder if there's some sort of quirky disk geometry setup misconfiguration or related type thing going on.

You need to be a member in order to leave a comment. Sign up for a new account in our community.