crap I already lost 2 long posts!  Lucky you - short and sweet version now

I need to run ghost (corp 7.5) on a laptop with XP-NTFS (also 2.5gb fat32 partition) to get files off a hosed laptop that won't boot win98.    I need to connect thru LPT and grab the image - place it on the Fat32 partition to extract the needed files through Ghost Explorer, so I can refomat the other computer.

I've tried in the past to creat a bootable CD, but I end up making alot of coasters.  Been to Barts CD FAQ and 911cd.net (looks promising for what I want to do) but I'm just totally confused about what files I need beyond the one that Norton Book Disk Wizard creates (lpt-usb-cdrw support)

Am I missing something in the autoexec.bat and config.sys files?  I did get one to boot months ago using winimage and EZ CD to make the disk bootable.  Norton loads (after many errors including missing command.com when it's there) and then locks up.

I have Nero on this laptop (where I'll create the bootable CD) but I just need to know what files to add to the CD.

Sure wish Symantec would offer downloadable iso's of bootable CD's from their site!  With more and more new computers not having FDD's, it's a real problem.  If anyone can create an idiots gui to create bootable CD's they will make a fortune!!

TIA for any ideas or clues to what I'm missing.  Nothing more frustrating that spending hours creating coasters, only to have them boot to a little heart and sit there at a __ prompt

thx again.

Yes my old and new burners are supported.  It shouldn't make a difference for the bootable CD though, because I don't even plan to burn a .gho image to the CD.  I just want the CD to BOOT norton for an LPT connection.  I only want to make sure the CD is compatible with 98 with common hardware.

Sids guide is the best I have seen so far for editing the config.sys file correctly.  Norton's standard one left much to be desired. 

device=aspi2dos.sys
device=aspi8dos.sys
device=aspi4dos.sys
device=aspi8u2.sys




I assume if I leave out the norton.bat it should create what I want.  I don't want to restore an image, although I could add it b/c I may want to at a later time.

Bootdisk.com is where I found out about Emergency Boot CD http://www.ebcd.i-am.ru/. (under their beta iso section) It automates the process like 911cd.net, but I'm still not sure how to customize it for Norton.  911cd has a 911 Utilities folder where you can add Norton by adding norton.exe, ghost.env, and ghost.ini to their Ghost folder.  Only problem is I don't have a ghost.ini on my hard drive.  I think that's where my confusion is coming from.  Everyone has a "method" but there is no sure fire method that fits all.

Thanks for the links.  I'll give Sids method a try.  As I said I will be booting the CD on a computer without Ghost on the HD, so I just wanted to be sure what files I needed.  Also overwriting the autoexec.bat with another one (sids or ms-dos's) is confusing. Should I just call the the autoexec.bat that Norton's Boot Wizard creates, norton.bat and add the lines:

@echo off
LPT\PARALINK.COM /i
MOUSE.COM
CD GHOST
echo Loading...
GHOST.EXE

leaving the boot disk's autoexec.bat in place? 

thanks again.

Thanks for your input.  I was hoping someone with similar trouble would know what to do, but I do appreciate your taking the time.  

The Radified batch file is beyond the scope of what I want to do, but it is useful information for a later time.  I searched  your Symantec message forum link and found several with the same problem.  Symantec, unfortunately was of little help.  One tech even suggested not using Norton.  Others suggested adding functionality to create a bootable CD as a boot disk option.  Gawd I hope they jump on that idea!

In my search of their KB I did find information that I think will solve my problem. "How to create an MS DOS system disk for Ghost".   Why Norton's boot disk wizard doesn't create these files is a total mystery to me!! They list what files are needed >>  

EDIT: RAD note: I removed the long-@ss link cuz it was screwing up the forum display in some browsers. I re-posted the link at the very bottom of this page:
http://ghost.radified.com/ghost_network.htm

"Keep or remove the SCSI drivers
Ghost Boot Wizard automatically copies SCSI drivers to the bootable floppy disk. (DIDN'T ON MINE!)

   * If you have SCSI devices or use a CD-ROM boot disc, then do not delete the following files. SCSI devices and CD-ROM boot discs require one or more of these files.
   * If you do not have SCSI devices or will not have a CD-ROM boot disc, then delete the following files.


ASPI2DOS.SYS
ASPI4DOS.SYS
ASPI8DOS.SYS
ASPI8U2.SYS
ASPICD.SYS
BTCDROM.SYS
BTDOSM.SYS
OAKCDROM.SYS
FLASHPT.SYS

Verify remaining files
After you delete the previous files, the floppy disk still includes the following files. These files are required for starting the computer into a DOS environment and connecting to various devices.
COMMAND.COM
MSDOS.SYS
IO.SYS
AUTOEXEC.BAT
CONFIG.SYS

Verify Ghost files
Verify that Ghost copied the files that are appropriate for your version of Ghost to the bootable floppy disk. If the files are not on the floppy disk, copy the files from the hard disk to the Ghost bootable floppy disk.

   * Symantec Ghost 7.0 and Symantec Ghost 7.5
     Ghost.exe
     Ghost.env
     Wattcp.cfg  <<<<<Didn't create it on mine
   * Norton Ghost 2002, Norton Ghost 2001 and Ghost in Norton SystemWorks version 5.x
     Ghostpe.exe
     Ghost.env
     Wattcp.cfg


NOTE:
Not all situations require the files Ghost.env and Wattcp.cfg:

   * The consumer Ghost versions require Wattcp.cfg only when cloning over a TCP/IP peer-to-peer connection.
   * The corporate Ghost versions require Wattcp.cfg in the same circumstances as the consumer versions, plus in some instances when using Ghost Multicast Server, GhostCast Server, and Ghost Console.
   * The consumer Ghost versions require Ghost.env only when copying Ghostpe.exe directly from the Ghost CD (instead of from the hard disk to which Ghost was installed).
   * The corporate Ghost versions require Ghost.env in the same circumstances as the consumer versions and in some instances that involve customizing Ghost or licensing Ghost. For customization information, see the document How to customize Ghost for individual users.



Edit the file Config.sys
To edit the file Config.sys that is on the bootable floppy disk, open the file with any text editor, such as Notepad.

   * If you have SCSI devices or you will use a CD-ROM boot disc, verify that Config.sys contains the following lines.
   * If you do not have SCSI devices or will not have a CD-ROM boot disc, then delete the following lines.

device=oakcdrom.sys /D:mscd001
device=btdosm.sys
device=flashpt.sys
device=btcdrom.sys /D:mscd001
device=aspi2dos.sys
device=aspi8dos.sys
device=aspi4dos.sys
device=aspi8u2.sys
device=aspicd.sys /D:mscd001

Edit the file Autoexec.bat
If you want Ghost to start automatically when starting from the bootable floppy disk, add the following line to the end of the file Autoexec.bat that is on the bootable floppy disk:

ghostpe.exe

If you are using Symantec Ghost 6.x or later, rather than Norton Ghost 2001 or later, use the line Ghostpe.exe rather than Ghost.exe.


Hopefully this will solve my problem and help someone else.  It sounds like a step in the right direction anway  It's unfortunate I had to sift thru their entire site to find what their techs should know off the top of their heads.

message too long errors.  grr. will try this in multiple messages

sure no problem.  The easiest way is to use Sids bootdisk.exe

http://www.ping.be/satcp/ghostresq01.htm

I had errors with it when trying to copy to floppy (tried several) so I don't know if it's a corrupt DL or my drive.  Anyway,  create the disk.

2) create a Ghost boot disk of your choice from the bootdisk wizard. then -

3) open the autoexec.bat from the Ghost boot disk that you created and rename it 'ghost.bat'. Make sure any drivers on the Ghost Boot Disk  are also on Sid's bootdisk that you created.   If Sid's disk also has the same drivers great, if not, add them to the disk.

4) open the config.sys file on Ghost's Boot Disk and compare all the "device=" lines to the config.sys file that Sid's disk has under [GHOST].  If they match, great, if not add them to Sid's config.sys.

The image that you write to the CD will have to be good to go with your customization, so get it customized before you burn = reboot your pc with your modified Sids disk - choose Boot with CD Rom Support  and make sure all the drivers load, that you can read C: drive and any other partitions or CDrom drives that you have. If it boots fine it's useable.

Unfortunately, because Norton will not fit on Sids disk, you'll have to do a test burn to test it with Norton.   If you renamed Ghosts boot disk's autoexec.bat to 'ghost.bat' as described above, and placed the drivers and folders from the Ghost Boot Disk to Sids, it should burn fine.

5) open the CD writing program of your choice. 

EZCD - file/new/bootable CD - 1.44MB - from floppy- next
Nero (see Sids pictorial)

final part >

In theory, all the above should work for whatever boot disk Ghost's Boot Disk wizard creates.  Right now I'm having a bitch of a time getting my cordless USB mouse to not lockup with Ghost in DOS.  I had to remove mouse.com from my ghost.bat file AND references to the USB directory entirely on the boot disk.  I'm still having a bit of trouble with Sid's mouse.com loading and screwing with my USB mouse.  The mouse works, but after a few clicks Norton locks up and I have to reboot.  I'll have to find out what the keyboard key is to drop down the drive box

Anyway, it's totally doable and with some tweaking it will make Norton usable for ppl with no floppy drives.  Tweaking the USB problem may be a bit harder to do.  Alot of ppl have USB keyboard and no PS/2 ports at all.  Depending on BIOS options available, Norton could not work at all for ppl with USB keyboards.  I've tried enabling and disabling legacy USB in Bios with little change in Norton locking up with mouse.com loading.  I know that USB in BIOS is funky from past experience.  ie: I have to disable  legacy USB if I want to use my PS/2 keyboard AND my wireless USB mouse when I get to windows.  One or the other, but not both!  What a pita that was to figure out

I found one suggestion of adding 'hidusb.sys' (find/files and folders) to the bootdisk and loading it at the A: prompt.  I had no luck with that, and when added as a device= line to Sid's config.sys, the boot process locks up.

Like I said, talk to Sid.  He has a great config.sys and auto.exec bat configuration on his bootdisk.  You could add your own menuitems for other DOS tools and create bat files for them to load the same way [GHOST] and ghost.bat work together.  That would be pretty cool.  I'm not sure, but I assume you would just add your toolsfilename.bat to Sid's autoexec.bat under ghost.bat.  ??  Like I said, Sid would know.  That would be very cool.  Wish I knew more about batch and config files.

Hope this all made some sense.  It's not meant as a tutorial by any means, but it will work to create a bootable CD to run Ghost, and the tweaking possibilities for a multi-boot Norton Ghost Boot Disk CD would be awesome =

1) boot to Ghost with USB Boot Disk.
2) boot to Ghost with Network Boot Disk.
3) boot to Ghost with TCP/IP Network Book Disk.

yowza!!  oh man if anyone knows how to do that I'd love to hear it.  It can't be that hard for someone that understands autoexec.bat files.  Would definitely need a way to make a bigger boot floppy image to support the additional drivers, unless there is a way to add a device=/path/tothesysfile.sys that would work.  Then the limitations of the boot floppy size would not be a problem.  Could even do a DY own cab file like ebd.cab (?) that extracts the drivers like a windows setup disk.  Endless possibilities for someone that knows how to do that stuff.

Hello everyone. Im new at this place and ive been searching for about 2 weeks to solve my problem....i recently got norton ghost 2003  and for some reason...when i choose Backup and i go through the process, at 5% it says Error 12020. Sometimes it says a different number...but this has wasted 15 cds and i already tried doing it from the boot disk but it still wont work...after it fails it makes a file in C:\  called "Virtual partition.DAT"....am i supposed to keep that inside or delete it? i havn't tried doing a back up with it in there. I have checked the the website for supported cd-rws but im not shure what brand it is i just know its a CD-RW 24x10x40 ATAPI and i had bought it about 1 year ago...so if anyone knows any ways i can try to fix this problem it would help me and my cds a lot ..........sorry if i posted in the wronge section but i was lost

jacklz, I did find this at symantec on error 12020 >

http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000103010201025

If you still can't get it to work, can you write the image to your hard drive instead of the CD and put the image on the CD later?  Like with Sid's tutorial here:

http://www.ping.be/satcp/ghostresq01.htm

Okay, I did a little more research. This link here:

http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000030611414425

says:

"Choose Yes when Ghost asks whether to make the disk bootable."

Have you seen this question posed to you?

If you don't have a floppy, can't you simply navigate to a directory somewhere on your hard drive?

I can't seem to locate that option/question, tho.

You say, "I didn't see any utility that would create a bootable CD without writing an image at the same time. "

What is wrong with writing the image to CD?

As an obvious point, you know u can buy a cheap floppy for your laptop, right? I mean, most manufacturers offer the option.

I have a friend who just got a Dell 8200, and she ordered one. It was only like $30 I think.