Ghost Solution Suite

 View Only
  • 1.  Create an ISO returns write protected error?

    Posted Dec 31, 2009 06:02 AM
    I am trying to create an ISO of a spanned ghost image. The issue I am having is when the ISO "finishes" I get an error saying the it could not finish because the destination is write protected.  The image name is image, the size of the gho and ghs files are all at the default 2gb that console spans. They are all in the same folder. This is running on a XP machine with the administrator. I am running the latest update for GSS2.5.

    As far as the process I am using to create the ISO it goes as follows.

    Open GBW    /     Standard boot image  / default settings     /    add image.gho    /  no custom scripting

    The same thing happens whether I try to burn to dvd or create an iso.

    I can push the image fine with console in my test lab, I just cant seem to get the thing burned so I can send to out to my sites.

    Any idea's?


  • 2.  RE: Create an ISO returns write protected error?

    Posted Dec 31, 2009 09:22 AM
    Before we go any further, can we confirm that your file system is not running FAT32 ?


  • 3.  RE: Create an ISO returns write protected error?

    Posted Dec 31, 2009 01:07 PM
    Confirmed I am not running Fat32.  I did finally manage to get a cd to burn with no error by moving the files to the root drive. However the iso did not work it says the cd is not the first in the set.

    Am I right in my thinking that I need to burn the iso with the .gho on the boot disk and burn the .gho's to disks via nero?


  • 4.  RE: Create an ISO returns write protected error?

    Posted Jan 03, 2010 04:59 AM
    You need to get first or second Live update. In the original version we added feature to add additional files to ISO. This was meant to be for small files but people wanted to include images. Feature was not designed for huge files so we changed it to include any additional files directly to the media instead of inside WIM file. This was either 1st or 2nd live update. You might as well run Live update 3 times to get all updates.
    This will solve your problem.