roxe

Great post!!!

It's always helpful for the community if people come back and let us know if they were successful or not and how they accomplished the task.

Couple questions:

1.  Did you use the Ghost's PC-Dos or the MS-Dos for you boot floppies?

2.
Quote:


Why is this in your procedure?  What happened to make this an important step to include?

Looking at the steps involved in the LPT procedure, the TCP/IP procedure looks much the same, except you have the added steps of possibly having to supply the DOS drivers for your NIC card if Ghost does not already have them, and possibly having to manually set the NIC card addresses.

Hi NightOwl

Thanks to your links, I not only had great success but had fun in the process

TCP/IP for me would involve putting my NIC dos drivers into Ghost AND setting the addresses manually. I could not find a detailed "how to" for doing that, so for me it would be more WORK than I have time for right now.

Plus, I have a feeling that it's going to be a royal pain getting the Linksys PCMCIA card set up in the laptop - another thing I don't have time for, since the laptop owner is wanting his machine ASAP.

I used MS-DOS, cuz I'm running 98se. Also, I had to download the Mouse.com and put it into my DOS folder inside Windows. For some reason, it would never install there. So, without it, I could NEVER get the destination drop-down menu to "drop".

I suppose one of these days when I have nothing else to do, I'll check out my cab files to see if it's in there.

I included it in my instructions, just cuz it makes things so MUCH easier inside DOS Ghost.

As for the "O pen", pookie said "the links work and that's all that matters"

Thanks! again a bunch for all your help!

NightOwl,

Quote:


Yep, that is exactly what I mean. Until tonight...

I went into the boot disk wizard and chose the CD boot disk. When it got to the screen where I chose which DOS version I use, I left it at MSdos, and for the first time it came back with a notice that becuz I'm "using MSdos there will NOT be a Mouse.com used in making the disk."

ALL the other kinds of MSdos boot disks I've made have always had the Mouse.com used. (I went into the Command folder and there was NO Mouse.com in there... so I added it - but it made no difference to that sweet notice    Now I'm wondering how the other disks got made.)

So, I just switched to PCdos and made it with that!!

But... when I booted with it, loading the CD drivers failed.

This is getting to be an exercise in patience,  hard thinking, using hours searching the Symantec knowledge base, etc.

I'll switch to the other topic I have in making a boot disk that will assign a letter to the CDrom... and ask you a question there,  OK??

Thanks! Rad for allowing me to share my little bit of knowledge for everyone

Re-reading my steps again, there is only one small change I would make - to make it more clear.

Step 12 would start:
Using the MASTER keyboard or mouse, start your Ghost menu . . . etc.

Thanks! again for all the help I've received from some of the nicest people I've met - especially NightOwl

roxe

From your post #19:

Quote:


The other boot disks that you made were probably the 'Standard Ghost Boot Disk' which is for using Ghost to directly image to your optical writer(s).

The 'CD/DVD Startup Disk with Ghost' is for accessing your optical drives with CD's or DVD's that were not originally made using Ghost, i.e. you've imaged to a hard drive and copied the image to a CD that may and may not be bootable.

Symantec's Ghost program 'hides' the Mouse.com program that it uses here if you need a copy:

C:\WINDOWS\All Users\Application Data\Symantec\Ghost\Template\common

roxe

Quote:


What menu is that?  If it's listed and you could identify it, couldn't you use it?

Quote:


That's really strange...I thought that's what you ment, but I never had Mouse.com in my C:\Windows\Command folder and I always had mouse support except when using MS-DOS and the 'CD/DVD Startup Disk with Ghost' , and the bootable CD created when imaging from the Windows interface.

It's always interesting .

Revised step #12 per your comment.

This may help anyone who's trying to create a bootable DVD with Ghost containing an image of a computer that doesn't have a DVD burner.  It's roundabout way of doing it, but it works.  I too was unable to successfully  run Ghost across two computers using a TCP/IP connection.  That sounded like it was over my head.  So here's what you do.  Image the partition on the computer without the burner.  Then network that computer with the one with a burner (using a hub, crossover cable, etc.).  Transfer the file from the non-burner computer to the burner computer.  Then restore the image to an empty partition on the burner computer.  Finally, image that partition onto a DVD.  Presto, a bootable DVD with the image of the non-burner computer.