Hello,
if you got ghost 11 it means you got ghost32.exe forget about DOS and ghost.exe
use windows ghost32.exe use windows 7 PE it should have lots of SATA drivers it has 40MB driverstore.

windows 7 PE is  made by going to system and security > recovery >and on left choosing to make a recovery CD
or down load from here
http://neosmart.net/blog/2009/windows-7-system-repair-discs/
use WAIK now

I used imagex /mountRW
to mount boot.wim the image
and droped nu2menu.exe and all its assosiates in the system32 folder

then opened winpeshl.ini and channged
path=x:\windows\system\nu2mnu.exe

and then un mounted then made iso

I now have a windows7 pe with all utilities
ghost32 and a43.exe are on the menu
and to get microsoft menu back put it on nu2mnu
X:\sources\recovery\recenv.exe
=========================================
put ghost32.exe to auto load replace nu2menu.ece with ghost32.exe e.g.

path=x:\windows\system\ghost32.exe.exe
=======================================
you need WAIK from microsoft  site to mount your wim use imagex.exe(and no DISM )
======================================
Regards Ben
PS if you are new to making  PE go to 911CD
also you need that CD to repair boot up on a new
HDD after you put ghost image on it .

bllo

I don't know what the status of SATA support for optical drives with Ghost 11.5--seems like they would have added that by now!

Your syntax seems okay (GCDROM for DOS command line syntax).  Have you checked to be sure you only have one space between the device statement and the switches:

Quote:


In your first post, this photo of your screen error messages:  http://img263.imageshack.us/i/ghostissues.jpg/

Sure looks like the command *device=gcdrom.sys* is successfully being executed--is that you SATA optical drive that is listed there?

How about changing to small letters in the command for the following lines so it's similar to *device=gcdrom.sys* that seems to be loading without an error message:

Quote:


If you're able to boot from a floppy disk on the system with the SATA optical drive, you could save on optical discs until you work out the bugs!

And, it might help to avoid the menu items that add complexity to the boot files until you get the basic commands working successfully!

Sorry, I don't have better suggestions--I don't have SATA optical drives to work with and test boot files for!

bllo

Quote:

The only reason I suggested it was because the command line *device=gcdrom.sys* (which apparently is loading and seeing your optical drive successfully) just before the lines that give you the error is in lower case!  I use mixed upper and lower case in my *config.sys* and *autoexec.bat* quite often--it has never been a problem for my systems--but, long ago in the dark ages of DOS, I vaguely remember seeing a recommendation to keep it either all caps or all small letters (but, I don't know if that was just someone's personal idea--or if it actually was a software necessity--perhaps it made a difference for older versions of DOS--i.e. pre v6.xx)--but, for me it has never made a difference or caused a problem.

Quote:

The */D:xxxx* and the */Cx* are command line switches to control how how the device software that's being loaded is supposed to *work*--assuming there are options--if no options, then no command line switches!

The *DEVICE=GCDROM.SYS* loads the DOS driver for SATA optical drives--it *mounts* the drive so DOS can see it!  It is comparable to the *oakcdrom.sys* driver for PATA based optical drives.

The */D:* switch is to give the optical drive a *name*--that name is necessary for the *mscdex.exe* driver in *autoexec.bat* to assign a drive letter--the *mscdex.exe* has to have the same device name in its command line in order to *assign* a DOS drive letter.  What comes after the */D:* part can be almost anything--I don't know how many characters are allowed--but I have always kept it 8 or less because of the DOS file name limitation--but I don't know if that applies to this particular switch--probably not, but why tempt fate  !  So, those different *names* after the */D:* are fine, and don't make a difference as long as they are the same for the *mscdex.exe* command line--and the names are unique for each device that is mounted successfully by *gcdrom.sys* (or other DOS optical drivers such as *oakcdrom.sys*, etc.).

Another thought has come to mind--your *config.sys* has the following:

Quote:

Maybe that first line (device=gcdrom.sys) which seems to correctly see your optical drive somehow is interfering with the following load lines that have the additional command line switches.  Maybe removing that first command line (device=gcdrom.sys) that does not have the necessary command line switches to actually successfully *mount* the drive is preventing the additional commands to load and work properly!

As a quick test of that--if you press F8 just as DOS begins to load--timing is critical!--you should get a DOS boot menu that allows you to select a *step-by-step* loading of the command lines in *config.sys* and *autoexec.bat*--you can say *No* to creating a log file, but *Yes* to all other lines until you get to *device=gcdrom.sys*--say *No* to that line, and let the next line execute to see if the behavior has changed.  When you have your boot files with the more complex *menu* setup, it can get confusing as to which command line to say *Yes* to in order to follow the correct path to the boot sequence you're after.

Quote:

Yes, please let us know how your testing goes!  As I said, I don't have SATA optical drives--so any additional information posted to the forum may help others!

bllo

Thanks for the feedback--glad to hear it's sorted out!