I followed instructions and was sucessfully able to creat a bootable CD to launch ghost 2003 with a system without a floppy drive. YAHOOO!!!  

Now for the problem...

Intention = image c:\ drive to USB 2.0 drive

#1 Problem:  Using the newly created CD-R Ghost boot disc, once in Ghost 2003, I can see both drives (C & USB) when I have to select source drive.  But when I go to the next window to select location to put image file, the drive (USB) that was visible, is no longer seen.  Incidently,  when I try to use the USB drive as Source, and select a location on the c:\ drive I CAN do it.

What is up with this???  

#2 Problem: I should also mention, my monitor/display is very hard to read on boot up of ghost.  I've never seen that before either.

I hope to hear some good leads solving this problem.  

Thanks for posting the great instruction on the bootable CD/DVD  without a floppy drive...I've been wrestling with that for literally YEARS. I am so glad I found this sight.  http://nightowl.radified.com/bootcd/steroids.html

Thanks, G!

gman


Quote:

#1 Problem:  Using the newly created CD-R Ghost boot disc, once in Ghost 2003, I can see both drives (C & USB) when I have to select source drive.  But when I go to the next window to select location to put image file, the drive (USB) that was visible, is no longer seen.

How many partitions do you have?  The drop down menu in DOS Ghost 2003 has a *bug* in that the scroll function does not work--so if you have more than about 6 drives listed, you can't put the mouse on the down arrow and get additional drives further down the list!

But, using the down arrow on the keyboard allows you to see what's further down!


Quote:

#2 Problem: I should also mention, my monitor/display is very hard to read on boot up of ghost.  I've never seen that before either.

There have been various reports regarding DOS Ghost's video display--I think some have found that loading the DOS *himem.sys* has helped.  Some video card/monitor combinations may not display a DOS program well--I don't know if there is any *fix* for this problem!

Thanks for the response. Here's my answers to your questions with some commments:

1 -  The usb drive that I want to write the ghost image to is "invisible" and has only 1 partition.  The only other drive on the system is the drive that  I want to backup/image is an NTFS drive with 4 partitions (created by Dell).  I want to clone "Disc to Image" but cant get the USB drive to be seen in the dialog box that says "File name to copy image to" and selecting the "Look IN" dialog.  I tried using the down arrow, but it will not work at all.  The mouse finds my DVD drive and a 1.44.  I don't even have a 1.44 drive onboard. Weird to me.  Maybe it's a virtual drive created by the CD boot disc i created, I have no idea.

The USB drive IS however visible in the "SELECT SOURCE DRIVE" WINDOW.  I can see details of size, type cylinders,  etc.  They all seem accurate especially SIZE.  This is the part that doesn't make sense.  WHY CAN'T I SEE THE DETAILS OF THE DRIVE AND WRITE TO IT?

Is there a USB driver that needs to be added to the Bootable Ghost '03 CD i created?  When I checked, I don't think I saw one?  

Lastly, I know the Dell laptop i am trying to clone has USB emulation turned on in the Bios.  I thought this was good news...but perhaps a USB driver that is normally copied to the 1.44 floppy when created inside create boot disc in ghost is needed.  If so, I HAVE NO IDEA HOW TO DO THIS and could use some help.  If so, should I turn off USB emulation?

Thanks for helping me!

Cheers,

G!man

gman


Quote:

WHY CAN'T I SEE THE DETAILS OF THE DRIVE AND WRITE TO IT? I know the Dell laptop i am trying to clone has USB emulation turned on in the Bios

Hmmm....this could very well be the issue--that USB support from the BIOS may be allowing Ghost to *read* the USB external HDD--but, not to access for writing!


Quote:

perhaps a USB driver that is normally copied to the 1.44 floppy when created inside create boot disc in ghost is needed

The Ghost supplied DOS USB driver is one possibility.

Here's an alternative USB DOS driver that has shown the most compatibility:

A Better USB 2.0 DOS Driver for Ghost + More!

Creating a custom bootable CD:

Creating Bootable CD/DVD's Without A:\Floppy Drive

Adding the USB DOS drivers to the custom bootable CD:

Adding USB to Ghost Boot CD


Quote:

should I turn off USB emulation?

If you load DOS USB drivers from the boot files, then the BIOS USB support should be disabled while using those other drivers to avoid possible conflicts of software competing for the same hardware resource.

I tried disabling the USB emulation...no good. didn't work.

I then tried following trying what you suggested in the following link -below :


__________________
You're looking for 'USB-DOS files' down at the bottom on the left side.


So, using the same outine in the Creating Bootable CD/DVD's Without A:\Floppy Drive Project #1, you would add the following two lines to the config.sys file:

[config.sys]

Device=usbaspi.sys /e /v  
Device=di1000dd.sys

Then add the following two files to the other list of boot files that you are injecting using WinImage:

[Added files]

Di1000dd.sys  
Usbaspi.sys

Unfortunatly, that makes the total MB greater than the 1.44 of a floppy disk.  So you have two choices:

1.  Use WinImage to make the emulated disk size 2.88 MB instead of the 1.44 MB, leave Ghost.exe in the group of files being injected into the bootable image.  Your burning program has to allow you to change form 1.44 MB floppy emulation to 2.88 MB floppy emulation.  All other steps would be the same.

2.  Leave WinImage at the 1.44 MB disk size, and now remove Ghost .exe from the list of files.  Instead, put the Ghost .exe on the data part of the CD you are about to burn.  This brings you back down below the total of 1.44 MB that can fit in the boot sector.  Because your CD can be accessed after booting and the Guide had you include drive 'X:' in the path statement, you should have Ghost up and running with USB support.  Again, the other steps remain the same.

Questions?  

Report back with your results.
___________________________________

I added the two files, and updated config.sys


A few problems:

I can't make or figure out how to make my cd burner software Nero express 6 use 2.88 format instead of 1.44MB.  I couldn't even find an option to select 1.44 or anything else.

Although I did select 2.88 in WINimage.

Then I went to plan B - go with 1.44 in WinImage and take out Ghost, and try to burn bootable CD and then add Ghost.exe as a data file after creating the boot disc.  The boot disc sucessfully completed, but the burn of ghost afterwards was not allowed - with a message that said you can not write to this disc.  
This didn't work out.  

Any suggestions?

gman


Quote:

I tried disabling the USB emulation...no good. didn't work.

When you disable the BIOS USB support, you have to replace it with some other DOS USB driver in its stead!


Quote:

I can't make or figure out how to make my cd burner software Nero express 6 use 2.88 format instead of 1.44MB.  I couldn't even find an option to select 1.44 or anything else.

If you don't have the full, paid version of Nero--but instead, a crippled *free* or *included* version with an optical drive--for instance--then you often do not have the *advanced* settings options!


Quote:

Then I went to plan B - go with 1.44 in WinImage and take out Ghost, and try to burn bootable CD and then add Ghost.exe as a data file after creating the boot disc.  The boot disc sucessfully completed, but the burn of ghost afterwards was not allowed - with a message that said you can not write to this disc.

Correct--once you burn the bootable disc, you can not add to it!  You want to add *Ghost.exe* to the data portion of the CD before the burn!

Are you following the outline here?--:  Step-by-Step Instructions

I did copy the USB drivers and added them to the files that I burned on CD.

I even tried using the disc without ghost to boot. Then took my CD data disc with only ghost on it and launch ghost.  That worked, but the "invisible drive" didn't appear.  

My thought is that there must be  driver that I'm missing on boot to get that drive seen.


I tried burning a data disc with ghost.exe first then tried creating a boot disc from the same disc.  Unfortunately,  the message I got said the data portion would not be accessible if I create a boot disc.

Is there a step that I missed?

What's the correct step by step procedure to get ghost on the CD first, the create a boot disc without disturbing the ghost file?

Thanks Nightowl!  You're awesome!

gman


Quote:

I tried burning a data disc with ghost.exe first then tried creating a boot disc from the same disc.  Unfortunately,  the message I got said the data portion would not be accessible if I create a boot disc. Is there a step that I missed? What's the correct step by step procedure to get ghost on the CD first, the create a boot disc without disturbing the ghost file?

Nero should ask for the boot image file after you have indicated that you want a bootable disc.  Then you should be presented with the standard Nero interface for burning data to an optical disc--that's where you add *ghost.exe*.  

So you do both at the same time--setup the bootable disc + add the data to the disc--then you *burn, baby, burn*!

Quote:
Nero should ask for the boot image file after you have indicated that you want a bootable disc.  Then you should be presented with the standard Nero interface for burning data to an optical disc--that's where you add *ghost.exe*.  

So you do both at the same time--setup the bootable disc + add the data to the disc--then you *burn, baby, burn*!

I tried this and still have  USB drive that I can not select in order to write to it.  What the heck is going on?  

I don't know, but it sure sounds like a driver issue to me.  I have written may gho files to this disc before using a boot floppy with no problem.  Please help!!

gman


Quote:

I have written may gho files to this disc before using a boot floppy with no problem.

Okay--list the files on your successful boot floppy that works with your USB HDD.  Additionally, list the contents of your *config.sys* and your *autoexec.bat* boot files.

Now, list the same information that you are attempting to use as you boot files for your bootable optical disc!

Let's see where there may be differences!

Sorry for the delay....and thanks for your suggestions so far

Here is the file data that you have asked for:

WORKING USB 3.5" FLOPPY DISC

FILE NAMES:

GHOST FOLDER
  GHOST.EXE
  GHOST - CONFIG SETTINGS

USB FOLDER
  aspiohci
  aspiuhci
GUEST
IBMBIO
IBMDOS
MOUSE


THERE ARE NO OTHER FILES ON THIS 3.5" DISC INCLUDING "HIDDEN FILES".  Config.sys and autoexec.bat are not listed on the floppy.



NON-WORKKING CD-R BOOT DISC
FILE NAMES:

AUTOEXEC.BAT

path=a:\;x:\
mouse.com
mscdex.exe /d:nightowl /l:x /m:16 /v
ghost.exe




CONFIG.SYS

device=oakcdrom.sys /d:nightowl
lastdrive=z
Device=usbaspi.sys /e /v
Device=di1000dd.sys



files put into boot image IMA file:

autoexec.bat
command.com
config.sys
di1000dd
io.sys
msdos.sys
oakcdrom.sys
mscdex.exe
mouse.com
USBASPI


Ghost.exe was added as a data file, not as part of the boot image file in win-image.

FYI - I wound up running Sonic CD burner software in addition to the Nero express 6 and have come up with the same result.   can see USB drive and select it as source for image but can not select it to WRITE data.

gman


Quote:

WORKING USB 3.5" FLOPPY DISC THERE ARE NO OTHER FILES ON THIS 3.5" DISC INCLUDING "HIDDEN FILES".  Config.sys and autoexec.bat are not listed on the floppy.

I have no idea as to how this floppy is working without a *autoexec.bat* or *config.sys*--I have never booted to DOS without those files having to be present in some form--without them your other files (such as *aspiohci* or *aspiuhci*--the Ghost provided USB DOS drivers) should not know to load themselves!

You can hit F8 when the system first says it's loading DOS, PC-DOS, Win98..., or whatever the message is--and you should get the option to go through the boot files in a *step-by-step* fashion--so you have to say *Yes, or No* to each line--you should see then whether a config.sys and/or autoexec.bat is loaded and read during boot.


Quote:

Device=usbaspi.sys /e /v

This line forces the Panasonic USB DOS drivers to work only with USB 2.0 compatible drives--is it possible that your USB HDD is 1.0 or 1.1?  Even if it is 2.0, if the USB HDD hardware is not completely compatible with the Panasonic USB 2.0 software--then you may be getting that failure to be able to write to your USB HDD.

You can delete the *space + /e* from that load command line, and then the Panasonic USB DOS driver will load all available USB formats that it finds available--i.e. USB 1.0, 1.1, and 2.0.  So, it looks like this:

Device=usbaspi.sys /v  

If you do that, does your USB HDD now show up as a destination HDD for writing to?

USB 1.0 and 1.1 will be very slow!

Hi Nightowl...

it's been a while since my last post and I've continued to struggle with my problem with my CD boot disc for ghost.

Here is an update that hopefully will shed some light on making some tweaks that will get me secure to create an image file.

I started over.  And, I bought the new Easy Media Creator 10 by Roxio.

I took my NEW boot image file and made it bootable and burned it. Low and behold, it WORKED like MAGIC on my Desktop PC to make a ghost image file.  I verified the image integrity and it's fine.  

NOW, for the problem....I tried using the same disc in my Dell Laptop and upon boot into ghost, again, I can select the USB drive as source but it is not seen in the "destination" dialog box.

Since we know the CD is good, are there setting I can change in CMOS or something that will help me.  Keep in mind, I've enabled USB emulation, still no change.

I hope to hear from you....I'm getting bald on this one.  Do you know anyone who makes a good wig! ;-)

PS - I even installed Roxio on y laptop and burned a CD on its CD/DVD burner.  This didn't make any changes. When I verified in DOS file names, sizes etc. they all matched up as mirror images.

Please Please Please throw me a bone on this one.
Kind regards,

Gil

gman


Quote:

I started over.  And, I bought the new Easy Media Creator 10 by Roxio. I took my NEW boot image file and made it bootable and burned it. Low and behold, it WORKED like MAGIC on my Desktop PC to make a ghost image file.  I verified the image integrity and it's fine.

Although it's great that it now worked--doesn't that experience of having to install the next updated version to make things work just *frost* you?!  It's great how we are continually conditioned to have to update!


Quote:

Please Please Please throw me a bone on this one.

Hmmm...sure--this one will *taste* good!--there are some USB controllers out there that just will not work compatibly with DOS USB drivers!  Yuk!

But, which version of the Panasonic USB DOS drivers are you using?  There are three that I know of:

v2.06, size=37,903, dated 11/26/2002

v2.15, size=39,093, dated 10/26/2003

v2.20, size=39,179, dated 11/07/2004

After clicking on the downloaded *.exe* file which extracts the enclosed files, you will find the *Usbaspi.sys* file in the *F2h* subdirectory.

If you're using ver2.15, maybe the 2.20 will help!?

Thanks for the quick reply...

I downloaded all 3.  I have them stored in a temp directory.

I'm not sure what to do with all the extracted files and where to "put them" or locate them on my system and which one(s) I should use.

Please tell me what to do and how to check what version of USB driver I currently have installed.  

YOU're awesome!
Thank you.

gman


Quote:

Please tell me what to do and how to check what version of USB driver I currently have installed.

The answers are in the various posts above in this thread!


Quote:

After clicking on the downloaded *.exe* file which extracts the enclosed files, you will find the *Usbaspi.sys* file in the *F2h* subdirectory.

Put each downloaded file in a separate sub-directory, click on it to run the extraction process, and then you find the *usbaspi.sys* file in the *F2h* directory created by the extraction process.

That's the Panasonic USB DOS driver.  Make up three subdirectories with the version as its name, copy and paste the *usbaspi.sys* file from each extracted file to the appropriate version sub-directory.

Because the driver name is the same for each version, you have to keep them separate--you can not extract the files to the same sub-directory or you will over-write the previous files.  And you can save the *usbaspi.sys* file of the three versions to the same sub-directory because again they will over-write each other.

Re-create your boot disc files, and use the version of *usbaspi.sys* that you want to use in the process.


Quote:

You can hit F8 when the system first says it's loading DOS, PC-DOS, Win98..., or whatever the message is--and you should get the option to go through the boot files in a *step-by-step* fashion--so you have to say *Yes, or No* to each line--you should see then whether a config.sys and/or autoexec.bat is loaded and read during boot.

When using the step-by-step boot, when the *usbaspi.sys* file is loaded, it displays the version as part of the load message you will get.

I'm curious, did you ever do that with your *successful* boot floppy that you do not find an autoexec.bat or config.sys file listed--what was the result?

Thank you!  Ok.  I think I got it with one question before I run anything....
On my current "working boot CD", there is no Usbaspi.sys file.  Can I just add that file to my boot image - the IMA file and then burn it?  And, do I need to delete the driver on the boot image file (name???) that does NOT work on the DELL laptop so that it won't conflict with newer driver(s) you pointed me to to avoid driver conflicts?

thanks!

G!


PS - I tried adding one Usbaspi.sys file and win Image says the "Image is Full".  I guess I have to delete something....

Thank you!  One question before I run anything....

On my current "working boot CD", there is no Usbaspi.sys file.  Can I just add that file to my boot image - the IMA file and then burn it?  Before I burn, do I need to delete a USB driver in the boot image file (name???) that does NOT work on the DELL laptop so that it won't conflict with newer driver(s) you pointed me to ?

thanks!

G!


PS - I tried adding one the 2.20 Usbaspi.sys file and win Image says the "Image is Full".  I guess I have to delete something....

Then I made a new image with a 2.88 file size and added the same file and still had no luck...what am I missing???

gman


Quote:

Before I burn, do I need to delete a USB driver in the boot image file (name???) that does NOT work on the DELL laptop so that it won't conflict with newer driver(s) you pointed me to ?

Yes, if the driver does not work, you should deleted it--and you have to change the *autoexec.bat* and/or the *config.sys* accordingly as well.

List the current *config.sys* and *autoexec.bat* file contents--and the list of boot files you are including in the boot image file.

If you change to 2.88 MB image size--your burning program has to have the needed setting to work with that boot image size as well--you can not use the standard size of 1.44 MB setting in the burning program if it does not allow for changing to the 2.88 MB size.  Does you burning program support the 2.88 MB size?

I tried to send a pdf file but it didn't work...


here is a jpeg file for the boot contents:

winimage.jpeg

Thanks for all your help....I don't know what I'd do without you.  I feel I'm getting close to solving this crazy problem!

---

gman

You will not be able to add USB DOS drivers unless you place *ghost.exe* on the data part of the disc, instead of the in the hidden boot sector with the other boot files.  Unless you can change the boot sector to 2.88 MB--but, then your burning program has to support that too!

Post the contents of *autoexec.bat* and *config.sys*.

You will not be able to add USB DOS drivers unless you place *ghost.exe* on the data part of the disc, instead of the in the hidden boot sector with the other boot files.  Unless you can change the boot sector to 2.88 MB--but, then your burning program has to support that too!

I did find out that the software will allow me to use 2.88.

Post the contents of *autoexec.bat* and *config.sys*.

I' CONFUSED?  I did post the contents of autoexec.bat and config.sys in the last post.  Did you see it.

I think what I need to know is what file I need to delete on my boot disc that is the USB driver that will potentially conflict with the new ones you pointed me too.  Which file on the boot image is the USB driver???
I need to knock this problem out today...or I'm going to be fired.  Please help!

What changes do I need to make in autoexec.bat and config sys for adding the updated USB drivers???

gman


Quote:

I' CONFUSED?  I did post the contents of autoexec.bat and config.sys in the last post.  Did you see it.

I see a list of the boot files in an image box--but I don't see a listing of the command lines that are *inside* those files that control what's loaded during booting!


Quote:

I think what I need to know is what file I need to delete on my boot disc that is the USB driver that will potentially conflict with the new ones you pointed me too.  Which file on the boot image is the USB driver???

In the above listing of DOS files on that boot disc (image?), you do not have a USB DOS driver listed!

To add the Panasonic DOS USB driver files, you need to add the *Motto Hairu USB Driver*
(Device=di1000dd.sys), and the *Panasonic USB DOS driver* (Device=usbaspi.sys /v), as discussed here:  A Better USB 2.0 DOS Driver for Ghost + More!

Is there any way you can edit my config.sys file and autoexec.bat file with the command lines you feel I need listed and reply with that in your message.  I have no knowledge of computer programming language and writing command lines...

did you get my last message with the 2 file details?

gman

Here's the response to your PM message:


Quote:

gman You're not loading any USB DOS drivers--only optical drive drivers, and mouse. [quote]config.sys device=oakcdrom.sys /d:nightowl lastdrive=z   autoexec.bat path=a:\;x:\ mouse.com mscdex.exe /d:nightowl /l:x /m:16 /v ghost.exe

This would load the Pansonic USB DOS drivers--and you have to add those files to the list of boot files to be used:

[config.sys]

device=oakcdrom.sys /d:nightowl
device=usbaspi.sys /v
device=di1000dd.sys
lastdrive=z[/quote]

Ok. I added these files to the disc.  Made it 2.88 on winimage and in the burnining software and edited config.sys with the additions and burned.

When the laptop boots, i see a new post that shows he usb panasonic driver loading (hooray!) but it gets hung up and says "...inititializing host controller 1/5..."  It's been there a couple of minutes...no changes.  Any ideas?

gman


Quote:

but it gets hung up and says "...inititializing host controller 1/5..."  It's been there a couple of minutes...no changes.  Any ideas?

Hmmm...does the laptop's BIOS have built-in USB support?--for instance can you boot from a USB flash drive?

I think if the Panasonic DOS USB driver hangs like you mention--there may be a conflict with another USB driver.

You might see if you have the option of disabling *legacy USB support* in the BIOS, and re-boot to see if that helps!

thanks for your continued help and follow up with me...

This is such a pain in the butt!


Ok - with USB emulation turned off, I can now see the drive as source and destination.  A FIRST!  

BUT, when I get into ghost, I get hung up and nothing happens once I direct the program to go ahead with creating the image.

I tried several different versions of boot discs, trying to get away from this and one time it started writing, then it failed within about 5-10 minutes after writing about 300MB of data:

here are some details of what I did:


TEST DISC #1

THIS cd  DIDN’T SEE USB IN SOURCE.

CONFIG SYS

device=oakcdrom.sys /d:nightowl
device=aspiuhci.sys
Device=usbaspi.sys /v
Device=di1000dd.sys
lastdrive=z


AUTOEXEC.BAT

path=a:\;x:\
mouse.com
mscdex.exe /d:nightowl /l:x /m:16 /v
@echo off

--
ASPIOHCI.SYS
ASPIUHCI.SYS
**USBASPI.SYS – 11/7/04




TEST DISC 2

CHANGED USB DRIVER TO VER 2.15

THIS DISC DID NOT RECONGNIZE THE USB DRIVE AT ALL – ONLY C DRIVE WAS SEEN IN SOURCE…


Test disc 3

Added Aspiehci.sys to image file

Changed autoexec to include ghost.exe

Config sys

Added
Device=Aspiehci.sys

WAS ABLE TO SEE SOURCE AND DESTINATION USB DRIVE IN GHOST.
WHEN IT LAUNCHES, GHOST SHOWS WEIRD TIME REMAINING AND ELAPSED TIME.  

NOTHING SHOWS IN THE PROGRESS INDICATOR, % COMPLETE, MB/MIN, MB COPIED


TEST DISC #4

DELETED 2 FILES
ASPIUHCI.sys
ASPIOHCI.sys

Could see USB drive in source and destination.  Once directed system to write image, ghost gets hung up and nothing seems to happen.

gman


Quote:

Ok - with USB emulation turned off, I can now see the drive as source and destination.  A FIRST!

Yes!!!


Quote:

one time it started writing, then it failed within about 5-10 minutes after writing about 300MB of data

Noooooooo  :( !

Okay--do that again, but before you do, add *himem.sys* to your config.sys commands and the file to the list of boot files!!!  Use the following as the first line in config.sys:


Quote:

device=himem.sys

There's been a couple other posters in the past where their systems needed a DOS memory manager--and their problem was similar--Ghost loaded and started, but at some point during the Ghost procedure it would fail.

Any *joy* now?!

Unfortunately not.  But I thought we were in!

After messing around and losing another few days of my life with this, here is what I've done:

I bought a USB floppy drive and tried using it changing USb emulation on and off.  Neither worked.

At the same time, I bought the new version of ghost (12) after I called  symantec and thought if the USB drive didn't take, then investing a few bucks to free me (and you) from some serious pain would be more than worthwhile.

I THINK IT WORKED!

I say "I think"  because the interface is so different and the instructions are so weak that I'm flying blind and not sure how to check my work.

The gho ghs files of the past are not more and it seems to me that I can't even access the image files from windows explorer unless i'm in ghost recovery mode.

So, long last after a truly exhaustive search with a lot less hair, I feel a little more at ease.

Here is a believe one of my last questions on this issue (I hope).

If you're familiar with Ghost 12, is there a way to do an integrity check as in ghost 2002, 2003 etc.?

If there is and I can run it, my peace of mind will be put to rest.

I did make a System recovery disc in ghost 12 that is supposed to have all the drivers required for my machine.  

So my friend in cyberspace, I'm am certain you are curious as can be about what the heck is the stop on the 2003 issues, and after already getting an image late yesterday in ghost 12, I did just for grins try your himem.sys just to see.

Please let me know your thoughts on my questions to ghost 12.

With many many thanks.

Gman

gman

Well--you gave it a good try--and sometimes USB in DOS just isn't meant to be!!!


Quote:

If you're familiar with Ghost 12, is there a way to do an integrity check as in ghost 2002, 2003 etc.?

I think you do a *Verify Image* or something to that effect.  You can do it as part of creating the image--there's should be a box you put a check mark in to tell Ghost 12 to do that--or you can go back later to do it.

If you can't find the option to do it, head over to the other forum here that's dedicated to Ghost 9, 10, and 12--the folks there are equally happy to help with questions such as this!

As Rad has said, it's not so much which imaging program you use for backup--it's that you do it!