is there a way to access the network from DOS?

Duckers

Platinum Member
Mar 30, 2000
2,089
1
0
Let's assume that I have 2 computers connected with a crossover cable and say that I have a ghost image of the hard drive of one computer stored in the hard drive of the other computer.

Let's assume one computer gets screwed up and I cannot get to windows98, then in DOS mode, how would I access the network in order to use the ghost image file that is in the other computer?

I realize that there would be ways around to deal with this particular situation, for example, burning a cd with the image file, but however, is there a way to access the network in DOS mode?
 

Breaker78

Senior member
Oct 9, 1999
293
0
0
Yes. But I do not know the exact syntax. You would have to load dos drivers for you're NIC Card, then use a command like NET USE \\PATH. Also, there may be a network edition of ghost that handles this for you. I know that PowerQuests Drive Image Pro can create a boot disk that can save and image from a network, But it basically does the same thing i just outlined above. Anyone else have any input?
 

pm

Elite Member Mobile Devices
Jan 25, 2000
7,419
22
81
Yes, it's possible, but it's a huge pain. You need to get a bunch of old drivers and software. I have a old email which details how to do it, and I can look it up if you like.

Can't you pull the drive out of the backup computer and install it in the to-be-recovered computer, set up the master/slave jumpers and copy the file over?
 

velvetfreak

Member
Nov 24, 2000
84
0
0
On the NT4 Server CD-ROM there's a folder with the DOS utilities to make a boot disk which connects to the network. You can automate the boot disk creation with the Administrative Tools\Network Client Administrator utility. The Autoexec.bat on the boot disk (when created) looks something like this:

path=a:\net
a:\net\net.exe initialize
a:\net\netbind.com
a:\net\umb.com
a:\net\tcptsr.exe
a:\net\tinyrfc.exe
a:\net\nmtsr.exe
a:\net\emsbfr.exe
a:\net\net.exe start

There's also the WFW driver for your NIC to worry about, and specifying computer and workgroup names in the system.ini on the disk, and an IP address in the protocol.ini. In fact you'll get real familiar with modifying the system.ini and protocol.ini files.

There could be a way do do this easily via WFW 3.11 but I think I remember going down that path once and having a nightmare of a time. But don't let that discourage you :)

If you have access to an NT Server CD and want full instructions, PM me.
 

Duckers

Platinum Member
Mar 30, 2000
2,089
1
0
pm,
yes, that's another way to deal with this problem :)
Anyway, I would appreciate if you look up that info for me.


velvetfreak,
I can't send PM you because AOL is banned from these forums. The way I deal with this problem is by using a proxy server, however, when I tried to PM you, I got a weird messag saying something about entering a non-secure area, blah, blah....

I would really appreciate if you explain me step by step how to set this up.

I do not have an NT Server CD though.
Windows 98 is installed in both machines.

Do you think I could download this boot disk from some web site?

PS: If you don't mind, please write me at Duckerslt@aol.com
 

Castellan

Senior member
Nov 16, 1999
624
0
0
If you had Ghost 6.5, you could just use the network boot disk wizard ;) At any rate, velvetfreak is right. Make sure you find the DOS drivers for your nic.
 

velvetfreak

Member
Nov 24, 2000
84
0
0
Duckers -

I just sent you a PM, check your "Today" link. There are several sources for the files, I'll try and get back to you on that one.

BTW what NICs are you using?
 

Duckers

Platinum Member
Mar 30, 2000
2,089
1
0
hi,
As i said before I cannot PM you :(

Could you please e-mail me at Duckerslt@aol.com ?

BTW, could you also please get me these files?

Thanks for the info, i am gonna work on that as soon as I get the boot disk :)


 

Duckers

Platinum Member
Mar 30, 2000
2,089
1
0
My PC has a D-Link PCI NIC and my laptop has a 3COM PCMCIA NIC.

I don't know the model numbers right now, but I will check.