Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
Did not attempt to get the Symantec image to boot prior to having the CD crash. We assumed the image would work as designed/advertised.
We created the boot disk from an ISO image downloaded from the Symantec site (twice, onto two separate PCs) and burned onto a CD-R disk using the Sonic Data Disk v.6.0 product.
What is the secret to creating a usable Symantec boot disk? How can we resolve this in less than one business day? We are already looking at 96 hours of system downtime because we can't recover our last good backup.
M Kalmus
I've not seen a clear statement from you that having downloaded what I assume is an ISO image from Norton that you burned it to a disk using the special procedure for transferring an ISO image onto a disk, not as a burned copy but as a resulting product that will do what the original (before the ISO image was made by Norton) -- ie be bootable in your case.
If you just used Burn to disk with your software then you get on the disk exactly what you downloaded -- an ISO image.
What you have to do is to use another procedure that says it is taking the ISO image specifically and not treating that as just one more file.
I can't tell you what to do with your software but check the instructions for something about Burning ISO image to disk or Making bootable disk from ISO image.
Apologies if this is what you did but it's not crystal clear from what you have written so far, unless I missed something.
Hope this helps but it's a situation many find themselves in .....
You are correct. We are using the procedure for making a bootable image according to Roxio's instructions. We've tried using a CD-R and a CD-RW following the steps below.
Using Easy Creator LE, we begin the process of creating a data disc but first indicate the blank CD is to be bootable (by clicking the Make Bootable button).
When we restart the PC, it either boots into the XP operating system or throws an error stating "No operating system."
If possible, I would like to hear from someone who created a bootable CD from the Symantec image available online so we can duplicate their process.
We are using Ghost v.12.0 to back up our drives and we experienced a Boot Volume Error requiring us to replace a hard drive. We have the new hard drive installed and need to recover our last good image but can't get the PC to boot to the Symantec Boot Disk.
We downloaded a new boot disk image off the Symantec support site and burned it onto a CD-R disk.
We can get the PC to boot to the XP Installation Disk, but not the Symantec Boot Disk containing the necessary ISO image.
The BIOS is set to boot to the CD drive first. We have a Dell E510 with 4GB RAM and the new drive is partitioned into 300 GB and two 100 GB partitions.
Any advice on getting the PC to boot to the recovery environment?
M Kalmus
The Symantec Recovery Disk might not be booting because of the 4 GB RAM on the system. Try removing 2 GB of RAM, then booting to the Recovery Disk.
<< but first indicate the blank CD is to be bootable (by clicking the Make Bootable button). >>
I think that is what is causing the problem. If the ISO image is of a bootable disk then it contains the "boot instructions".
I don't have EMC Light but I've just fired up EMC 7.5 Creator Classic and checked the HELP (Not the F1 but the second line if it's like mine) for Image file and here's the part after how to create an image file (that's what you got from Norton):
To burn the disc image file to disc:
The Burn from Disc Image File dialog box appears.
The Burn dialog box appears.
There's an image that I can't reproduce here.
I hope I'm not wrong about this but please try it.
Removing 2GB RAM did not allow us to boot into the Symantec Recovery Environment.
Using the Burn Image to CD feature in Easy Creator produced a bootable image that allowed us into the Recovery Environment, but during the recovery process an error was thrown stating: Error EA3905FE: Cluster Not Allocated.
<< Using the Burn Image to CD feature in Easy Creator produced a bootable image >>
Deeee-lighted -- BTDT <g>
I'll let others help you with the error message.
What are the details of the image you created, and the destination of the image? Size, drive type, make, etc.
This might not help you now, but when you get your system up and running, I would use the Ghost bootable disc to create a custom bootable disc that includes all of the drivers on your system. You can do this within Ghost 14.
I saw something in the Norton Ghost instructions mentioning not to use CD-RW discs. I don't know why. I use DVD-RW discs without any problems and I recovered from a problem on my C Drive using Norton Ghost 14.
whbos wrote:
I saw something in the Norton Ghost instructions mentioning not to use CD-RW discs. I don't know why.
I commented on this to someone else here recently.
In general RW disks are considered less reliable and permanent than R disks. If you consider that the dyestuff in RW disks is designed to change with different lights and that the dyestuff in R disks is designed not to but to be long lasting, this is understandable.
FWIW
I agree with you in the difference between the permanent DVD (R) and the rewriteable (RW). I have the permanent DVD without the custom drivers and the DVD+RW with the custom drivers. I've thought about creating a more permanent custom disc since I'm assuming I shouldn't have to do it again unless I change computers. I am also waiting to buy more CDs since DVDs were all I had at the time. I rarely use CDs.
As long as one knows about the possible disadvantages which include, not so much in the recovery world but in recording DVDs for playback through the TV that some DVD players won’t read RWs.
Were ypu ever able to boot the Symantec boot disk before the HD crashed?
Are you SURE you have a valid iso image, and how did you create the boot disk?
If you can boot the Windows install disk, then the system is probably ok but it points
to a bad boot disk that you created.