- #Norton ghost image maker how to
- #Norton ghost image maker drivers
- #Norton ghost image maker verification
- #Norton ghost image maker Pc
- #Norton ghost image maker windows
I used 640 chunks because did not like filling cds too close to their capacity to avoid any possible future reading errors.
Then try an integrity check on those cds, I never had a problem with this method, but don't need the split since using dvds. Then burn normal data cds with each of the 640MB chunks, obviously labelling in order.
#Norton ghost image maker Pc
I backup much more frequently to image file and place on another Hard Disk but I also try to (ever so often) backup (also) to CDR so I have the provisions to restore when (and if) I have a failure that brings the PC "to it's knees" to where I can Boot only using Ghost 2003 Dos Boot Disk.Īnd backup to your second partition or hard drive. I had hoped that I would not have to backup to hard disk and split the files to match the CDR size then copy these to CDR's, however if I can not get a solution to my error problem I will have to use that option. Hello Bernd, Thanks for your reply and suggestions. Went out today and bought an external USB drive. Meantime I know that there is a workaround. It's a hassle if the programs don't work as they should, in the Then I just burned the three files onto three CD's again with
#Norton ghost image maker verification
The other hard drive with verification and ended up with three I configured PM to write the image in CD sized chunks (650MB) onto The program booted to DOS and started writing, but always hung onĪfter many times and a few toasters later, I gave up on the idea to Had multiple times yesterday with DriveImage. Sorry I can't help with Ghost, but like to share a similar saga i Will appreciate any helpful suggestions and/or comments.
Has anyone had any similar problem(s) OR can someone offer any suggestions since I have not found any answers to this problem on the Symantec web site. Since I have my Symantec installed systems set for automatic updates and I wonder if there have been some changes implemented in Ghost 2003 that is contributing to the problems I am now having and NO previous Integrity problems. Also, today I did an Integrity check on the CDR’s of 1-20-2004 and it failed when starting the 3rd CDR. My previous backup & Integrity check, (using CD-R’s) was 1-20-2004 and there were NO errors. I run a backup (to image file(s) & Integrity check for my primary drive (C & D) to a partition of my second physical Hard drive and there were NO errors.
#Norton ghost image maker windows
Then, I used the NO compression Backup CDR,s started the Integrity check in windows XP and it stopped at the same place with the same error # and a slightly different error description: Corrupt CRC Packet Header encountered. When using NO compression during the backup, the Integrity error is # 27101 Corruption in the image file.īoth of these Integrity checks were run using the Ghost 2003 Boot Disk. When LOW compression (called fast I believe) was used during the backup, the Integrity error is # 27076 Corrupt Packet length in compressed image file. The backup appears to run normal, however when I do an Integrity check on the CD-R’s, I get an error when it starts to read the 2nd CD-R in the group. Computer is a Pentium 4 PC using XP Pro, CDR, CD-RW, 3hard drives, etc… After that, future bootable ghost cd/dvd's are a breeze.Currently, I have a problem with Norton Ghost 2003 when performing a backup from my first Hard Drive to CD-R. The first time you go through this it takes a few tries to get the command line switches right, just a matter of getting comfortable with how ghost works. Once done, reburn the DVD with this floppy as the image. Now you can edit the switches and test until you get the desired behavior. Set the Boot Order in the Bios to look to the floppy first. Step Six: At this point the only thing that could be wrong is you want the commadline switches changed, use the dvd you burned and the original floppy you used to make it. Step Five: Test the dvd on your target machine (you might want to use a separate Hard drive on the inital run in case something doesn't work/you need to edit the command line switches again) If it works like you want, you are done. Step Four: Burn the *.gho file to a dvd with Nero or whatever your program of choice is, using your floppy as the bootable image. Step Three: Boot from the floppy to ensure that the dvdrom drive is seen properly and that you can list the contents of a data dvd fine.
#Norton ghost image maker how to
how to reference the image, partition options etc., refer to the online manual, it details them all quite well)
(for the command line switches in ghost, i.e. Also add the ghost executable to it and then edit the autoexec.bat to launch ghost after mscdex is loaded.
#Norton ghost image maker drivers
Step Two: Make a dos boot floppy that will load the drivers for the cdrom/dvdrom drive. gho file to a separate local drive or to a network drive via a boot floppy. I usually do the following process, just use a dvd instead of a cd:
0 kommentar(er)
