Boot from floppy created on other computer/s

Ghost 03 from boxed 10 produced the fault at the start of loading disk 2, "containing Ghost.exe"
Ghost 02 from boxed System Works 01 worked although I haven't verified the clone.

The 03 disks were made on a different computer than the M4A79, as was the disk from 02 (it's an old copy from a long time ago)
Cloning on IDE from slave, new WD, to master, new Lite-on.

Why would the 02 work but not the 03?
Any suggestions?



BIOS

- Express Gate:      disabled      (instant-on internet and skype)
- AI Net2:                  disabled      (check LAN cable)
- Lan:                        disabled


- Firewire:                  disabled
     (all inc. high speed)





- GART report:            disabled


- Cool n Quiet:                  disabled


- C1E:                              disabled
- ACC:                              disabled
- PnP OS:                        disabled
- Q-Fan Control:            disabled

George

Quote:

I probably answered that question in your other thread that I read first and answered there--

but,...Ghost 2002 is not SATA aware--so the presence of a SATA controller is probably ignored.  But, Ghost 2003 is SATA aware and is probably trying to mount that controller to see if there is a HDD attached.  But, if Ghost 2003 and the SATA controller are not compatible both in settings and software/hardware compatibility--probably Ghost is *freezing* when it tries to communicate with one of those SATA controllers.

And, Ghost 2003 may be compatible with *std* SATA, but perhaps not *eSATA*--I don't know how much differences there may be!

Some SATA controllers have been optimized to work best with Windows based OSs--and not DOS.  So, often DOS programs will not boot or work correctly if SATA is set to those optimized settings for Windows.  In the BIOS, some systems let you select the *Mode* setting for SATA--the terms I've seen reported are *combined* or *compatibility* for use with DOS based Ghost.

If the system is set to use SATA in its Windows optimized settings, then you could possibly shut down Windows, re-boot, go to the BIOS, set SATA to *compatibility* mode, save and do your DOS Ghost.  Then re-boot and go to the BIOS again, switch SATA back to the Windows optimized settings and then boot to Windows again!

Some folks found that they may have to use a switch to start Ghost that allows functioning with SATA controllers--the *-fni* switch.  I don't know if that switch needs to be used with the SATA *mode* setting set to *compatibility* as well--you would have to experiment!

But, the build of Ghost 2003 that came with your Ghost 10 boxed program should be the most recent version of Ghost 2003--i.e. build 793.  Most folks seem to *not* have SATA problems with that build--but each system is unique!

Quote:

Usually, the boot disks are not specific to the system that they are made on--at least with Ghost 2003!

Quote:

That would be the best approach--and possible not *disabling* but changing the *mode* might work--and/or using the *-fni* switch to start Ghost:

ghost.exe -fni