I'm trying to make a ghost image of a laptop and need to know how to configure for tcp/ip using Linksys ethernet card in my tower and a pcmcia Linksys card in the laptop (both with 98se).

The laptop hdd has a wierd connector, or I would just use my 2.5" hdd adapter and stick it in my tower to do this.

Any help will be GREATLY appreciated; and please, keep it simple and spell everything out. I've never done this before and have no idea.

Thanks! :)

did you read this

http://ghost.radified.com/ghost_network.htm

Yes, keltik1, I've read that. It's more complicated than I understand right now. I'm not using Linux, but 98se on both machines. I need to know how to set up the tcp/ip values, etc.

Thanks:) anyway for posting the url.

I've never used Ghost's network feature, so won't be much help. But if you get things sorted out, you might consider detailing your findings and I would be glad to update the guide which would help others in your predictament.

Rad

Roxe


Quote:

Any help will be GREATLY appreciated; and please, keep it simple and spell everything out. I've never done this before and have no idea.

and


Quote:

I need to know how to set up the tcp/ip values, etc.

It's unclear--tcp/ip values are software settings, but have you already established a peer-to-peer connection between the two computers, i.e. the hardware connection between the two so each computer 'sees' the other computer under 'Network Neighborhood' in Windows Explorer?

If not, that's your first step.  You will need a 'crossover cable' if you want to connect directly from network card to network card, or using standard ethernet cable you can connect from each card to a router to allow for communication between the two (I'm not sure, but you may also be able to connect to a simple 'hub' from each network card and have each computer talk to each other as well--you'd have to ask someone who's done that--I've only done the router and crossover cable connections myself).

Once connected, Win98se should take care of the configuration of TCP/IP for the two computers to communicate.  If you're running ZoneAlarm or other firewall, you may have to configure it on each computer to place the other computer's network card in the 'Trusted' zone so it allows the network communication between the two computers.

Once that's set-up and running correctly, then you can move on to seeing if Ghost can use the connection and if any special tcp/ip values will be needed.

Look at the 'Norton Ghost User's Guide' under Norton System Works/Norton Ghost/Ghost Utilities for 'Launching Ghost.exe peer-to-peer' and in the index for other 'peer-to-peer' references.

Thanks :) Rad for the vote of confidence! Am waiting now for a new Linksys card - since my other two don't work. I'd be honored to file my success here in simple language  ;D

NightOwl, thanks too for your help :)  As soon as I can get the PC card on the laptop installed and the two machines seeing each other, then will go from there.

Some here have said that Ghost needs to be installed on both machines to do this??  Why??

I'm hoping to use a Ghost boot floppy from the laptop to copy the image to my tower.... with LOTS of prayer :)

Roxe

See here for more detailed description about setting up peer-to-peer for Ghost:

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

Click on the 'Tutorials' at the top of the article for a run through of the procedure.

Apparently, you have to have Ghost on one computer 'talking' to Ghost on the second computer in order to do tcp/ip peer-to-peer imaging.  And it looks like you need two separate 'Peer-to-Per Network Boot Disks' if you do not have a DHCP Server that automatically assigns the NIC cards' IP addresses.  You will be setting the IP addresses for each card 'statically' by using the two separate boot disks, each with its own defined IP address that you manually input for each of the boot disks.

Under 'Norton SystemWorks/Norton Ghost/Ghost Utilities/Norton Ghost User's Guide/6.  Creating boot disks with the Ghost Boot Wizard/Creating boot disks and boot images/Boot disks with network support/ it says the following:


Quote:

9.   Do one of the following: Click DHCP will assign the IP settings if your network contains a DHCP server. Click The IP settings will be statically defined and complete the fields below this option if your network does not contain a DHCP server. If you create more than one boot disk, then the static IP address incrementally increases as each boot disk is created.

The above suggests that after you define the first static IP address for the first boot disk, the boot wizard will automatically increase the address by one for each additional boot disk created.

Also, other Symantec Documents are here:

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

This article talks about starting your Network supported Ghost session from within Windows, rather than using the floppy boot disk.

and here:

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

This article answers the question about using a 'hub' under 'Method 3 - TCP/IP Peer-to-Peer Connections'.  Apparently that will work, and when using a hub, you would just use standard network cables, and not the crossover type cable that would be for direct network card to network card connection.

O wow, NightOwl... and here I thought this was gonna be easy  :-/

So I'mma glutton for punishment  :o

thankyouthankyouthankyou for all the links and help... you really want me to succeed, huh.


Later:
After looking at the first link you gave me, I found the article how to Ghost using a LPT cable... I'm sure I already have one of those, so am gonna cheat and do that, since it sounds the easiest.

Thanks! again for those links ;D

Roxe

The problem is that Ghost is running under old native DOS, and so you have to load DOS drivers to control the network card on each computer.  So apparently Ghost's answer to that is for both computers to be running Ghost with network support so they communicate properly.

Here's a thought...is there a simple plug-in adapter for the laptop hard drive that would allow you to hook it up to the 'standard' hard drive connector on your desktop?

NightOwl,

I was editing my post just as you were posting ;D

This laptop hdd has a connection I've never seen before; and the two laptop adapters I have don't fit.

See my edited post above your last one to see my "solution" to this whole thing... sounds way easier than the tcp/ip.

However, & this is scary :),  I now understand about the subnet masks and ip addresses... makes sense to me.

Always learning...

Thanks again!

Roxe

No problem.

The TCP/IP route has a number of steps you have to follow, but it probably 'looks' harder than it actually is once you work your way through the steps.

Let us know how the LPT route works out.

SUCCESS !!

Ok, here is how I did it:

Using Ghost over an LPT connection

1)  Using Ghost's boot floppy wizard, make two standard boot floppys. Be sure to check the LPT box under Peer-to-Peer when you get to that screen. Also make sure you have Mouse.com included with your DOS files in the Command folder inside Windows. You will need to leave these two boot disks unlocked. Use one for each computer.
2)  Check the port settings on both computers in the BIOS. Make sure they both are set for the exact same mode - bidirectional, ECP, or EPP. Do not set them to unidirectional.

3)  Turn off both computers.
4)  Attach a hi-speed bidirectional LPT (printer) cable to the real parallel port of each computer. Ghost does not support virtual ports. You can use a Belkin (what I used), LapLink, or pcAnywhere cable.
5)  Decide which computer will be the Master and which will be the slave. In all cases but two, the source computer should be the Master and the destination should be the Slave. The exceptions are when restoring a Disk Image or a Partition Image. In these cases, the destination drive should be the Master and the source drive should be the Slave.
  In my case, the laptop speed was only 133mhz; my tower is 800mhz. Since I wanted to image the laptop, it worked very well using it as the Master. I would guess that going from "slower" speed to "faster" works better than the other way around, which I haven't tried.

6)  Boot the SLAVE computer FIRST! When Ghost starts and displays the splash screen, hit enter or click OK. The next screen displays the menu. STOP - don't go any further yet.
7)  Now boot the Master computer. STOP when you get to the same screen as shows on the Slave computer.

8)  Using the Slave keyboard and the arrow keys, navigate to Peer-to-Peer - LPT - Slave, and hit enter. Or you can use the mouse to do this.
9)  IMMEDIATELY, using the Master keyboard and arrow keys, navigate to Peer-to-Peer - LPT - Master,  and hit enter.

10)  The Slave computer will show on the screen "Program connected in LPT slave mode". It will continue showing this screen through the entire process.
11)  Timing with a second hand, WAIT AT LEAST TWO WHOLE MINUTES!! This is important. It can take that long for the connection to really set up.

12)  Then start your Ghost menu for making the image. When you get to the destination drive screen, you should see the Slave computers' drives showing in the drop-down menu.

When the image is completed and you continue so to make another image, you will need to redo steps 8 and 9 above. Only this time, you won't need to wait the two minutes before starting the imaging process.

I used the following Symantec documents to come up with the steps above in a more logical order.

http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1999051310014225?Open

http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1999012510105425?Open

I don't understand why there is a space in the word Open of each URL. It doesn't show up that way when I type it.

So how would I fix it??

The link works. That's all that matters.

Thanks!! pookie  :D

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:

Also make sure you have Mouse.com included with your DOS files in the Command folder inside Windows.

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.

roxe


Quote:

I don't understand why there is a space in the word Open of each URL. It doesn't show up that way when I type it.

I think you can just delete the '?Open' part at the end and just leave everything through the doc id part and it will still work fine.

Hi NightOwl :)

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

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" ;D

Thanks! again a bunch for all your help!

roxe


Quote:

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".

So, are you saying that you did not have mouse support from your Ghost basic boot floppy before you added Mouse.com to your Windows\Command directory, and after you added it there you did have mouse support when you created a new boot floppy?

NightOwl,


Quote:

So, are you saying that you did not have mouse support from your Ghost basic boot floppy before you added Mouse.com to your Windows\Command directory, and after you added it there you did have mouse support when you created a new boot floppy?

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??

Included these findings in today's update of the Ghost guide (14june2004).

http://ghost.radified.com/ghost_network.htm

Rad

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 :D

roxe


Quote:

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

Are you sure it 'failed'.  As I mentioned in the other thread about assigning letters to the CD or DVD drive, I got a lot of 'driver failed' notices for drives that were not present on my system when I booted from either the MS-DOS based boot disk or the PC-DOS based boot disk, but the drives that were on my system, were listed and assigned drive letters successfully when Ghost finally started and I looked in the drop down listing of 'source drives'.

roxe

From your post #19:


Quote:

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.)

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

NightOwl,


Quote:

Are you sure it 'failed'.  As I mentioned in the other thread about assigning letters to the CD or DVD drive, I got a lot of 'driver failed' notices for drives that were not present on my system when I booted from either the MS-DOS based boot disk or the PC-DOS based boot disk, but the drives that were on my system, were listed and assigned drive letters successfully when Ghost finally started and I looked in the drop down listing of 'source drives'.

Yes, it failed. The CDrom drive was still at the top of the menu with a @ at the beginning of the line.

But, using my modified 98se bud, the RAM drive is on "S" and the CDrom is on "T"; and like I said in the other thread, it WORKS just fine!

Finally!

About the Mouse.com...
The first time I used the Ghost boot wizard with MSdos, it did NOT include a mouse driver on the floppy; but after downloading Mouse.com and putting it in my Command folder inside Windows, all the different boot disks I've made with MSdos - except for the CD/DVD one - had the mouse driver on them.

Thanks! again for all your help :D

roxe


Quote:

The CDrom drive was still at the top of the menu with a @ at the beginning of the line

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


Quote:

About the Mouse.com... The first time I used the Ghost boot wizard with MSdos, it did NOT include a mouse driver on the floppy; but after downloading Mouse.com and putting it in my Command folder inside Windows, all the different boot disks I've made with MSdos - except for the CD/DVD one - had the mouse driver on them.

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 :-/.

NightOwl,


Quote:

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

It's the drop menu for either source or destination...

I guess it's because the @ is not a drive letter.

With the @, all you get if you manage to click on it (the down arrow key jumps right over it; but if you arrow down and then arrow back up you can click on it) is the sweet message "Image file not created with Ghost".

http://service1.symantec.com/SUPPORT/ghost.nsf/8f7dc138830563c888256c2200662ecd/b28a76d33822f17d88256c4e00654fbb?OpenDocument&src=bar_sch_nam

"This problem happens when Norton Ghost 2003 cannot detect a drive letter for the CD-R, CD-RW, or DVD drive. To resolve the problem, configure Ghost to assign a drive letter to the device."

Since I've been using a 98se BUD to get to A:\>, then starting Ghost, I've had no problem in being able to check integrity or restore images burned on CD's.

http://service1.symantec.com/SUPPORT/ghost.nsf/pfdocs/1999020111084825?Open

Revised step #12 per your comment.

[glb]Thanks! Rad :D[/glb]

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.

Whoo-eee... Imagine seeing this topic again after a year :D

Mike S... thanks for sharing your success. It's amazing the work-arounds folks come up with here on this forum.

Has it really been 5 years since starting this topic??  WOW! God is so good!! cuz I sure didn't think I'd still be alive this long :)

With three autoimmune thingies trying to take me out... well... all I can say is

THANK YOU LORD!  :D