Night0wlFanBoy

Quote:


That appears to be a SATA optical drive:  TSST TS-U633A 9.5mm Tray SATA DVDRW

The *DEVICE=OAKCDROM.SYS /D:NIGHTOWL* driver if for PATA optical drives.

Quote:

So, you need to add that DOS SATA optical drive driver--*gcdrom.sys* to the boot files included with the other boot files, and add these SATA optical drive driver command lines to the boot files:

[to config.sys--after the *DEVICE=OAKCDROM.SYS /D:NIGHTOWL* command line]

Quote:


You need to load all three lines because they tell the driver to look on SATA controller #1 (C0), SATA controller #2 (C1), and SATA controller #3 (C2)--for some reason the driver doesn't automatically check all the possible SATA controllers unless it's manually specified!

And you would replace the line *mscdex.exe /d:nightowl /l:x /m:16 /v* in autoexe.bat with:

[to autoexec.bat]

Quote:

You can leave the *OAKCDROM.SYS* driver command line in config.sys, and the reference to the *device--i.e. */d:nightowl* in the mscdex.exe command line in autoexec.bat--you will simply get the *device not found* error message if you do not have a PATA optical drive.

And, you will get a load error for each SATA controller where there is no SATA optical drive present as well--all normal behavior!

This DOS SATA optical drive driver will give you the ability to access files on an optical disc--but, writing an image to an optical disc can only occur if Ghost's built-in optical drive drivers are compatible with your optical drive--this would be noted in DOS Ghost by showing your optical drive listed after the *@* symbol in the destination drop down menu list--if it's not listed, then Ghost can not write to that optical drive.

Let us know if this helps!

Thanks very much, I'll give those other drivers a shot tommorow and let you know how it goes.

Also, in reference to your second post, I have been putting the ghost.exe on the root directory for all of my projects, as the version of ghost that I'm using has a 1MB executable which, after adding the size of all the other files in the standard project, puts the image it over the 1.44MB limit. I did try the 2.88 initially in hopes of circumventing the problem, but as you mentioned, it wasn't recognized correctly and that avenue was blocked.

Night0wlFanBoy

Quote:

Sure....press F8 as soon as the system begins to load DOS--I usually press it several times to make sure the system *see* the key stoke--but, it's probably more a matter of timing things *just right*--if it doesn't bring up the menu to select *step-by-step* confirmation--just do a *control-alt-delete* and try again!

Night0wlFanBoy

Quote:

How new is your system?  Notice how *old* the gcdrom driver is!  It's entirely possible that a newer breed of optical drives are not being supported by the older driver!

Any chance your system has more than 3 SATA controllers--might have to add an additional line: 

Quote:

You did add all those lines--you need one for each potential SATA controller that the optical drive is hooked up to?

I presume you got error messages for each line during loading?!

But, something seems wrong!

Quote:

That driver name (MSCD000) is in reference to the PATA optical DOS driver used by the Microsoft boot disks.  I changed that to */D:NIGHTOWL* as outlined in the Bootable CD/DVD Guide!  So, unless you changed it in your config.sys....

Quote:

Ah...okay, I see you did use the command line differently in your *config.sys*.

Post the *autoexec.bat* and *config.sys* files you are attempting to use so we can look them over for syntax errors.

I'm probably gone for the rest of the day, so won't be able to respond until later.....

Night0wlFanBoy

Well, nothing there to consider an obvious problem!

Darn!  I know SATA started out as a single standard, but now there is SATA I and SATA II--so maybe the newer controllers are not compatible with older driver.

You might put a *rem + space* (remark--so the line is not loaded) in front of this line:  *device=oakcdrom.sys /d:nightowl*  So like this:

Quote:


Or, say *No* to that load line during the *step-by-step* loading process if you are using that--just to make sure that driver is not causing a problem during DOS boot--driver load order or driver conflict can cause DOS problems--but I really doubt that will help--but, if you don't try, you'll never know!

Also, this line (MSCDEX.EXE /D:MSCD000 /D:MSCD001 /D:MSCD002 /l:x /m:16 /v) needs to list the */d:nightowl* device name if you want the *oakcdrom.sys* to be functional--so like this:

Quote:


Now, theoretically the boot disc will load either/or or both PATA and SATA optical drives if they are present and recognized!

Prozactive

Quote:

Do you have any links to those *other* DOS SATA drivers????

Prozactive

Thanks for those links--I checked them out--and unfortunately, I think those drivers may only apply to PATA and not SATA type controllers (unless the SATA controller is set to *look like* a PATA type controller):

For the *xcdrom* driver--from its *Readme.txt* file:

Quote:


For the *UIDE.sys*--from its *Readme.txt* file:

Quote:

Certainly sounds like SATA is supported!!!


But, at the very end, under *Technical Notes*:

Quote:

So, only if the SATA is set to run as a PATA device--or, an add-on board is used that converts the SATA to PATA, can the UIDE.sys work with a SATA device!