DOS networking, MS workgroup add-on, and Drive Image
bob olbrich
I would like to create a network boot disk
to access a network drive while using Powerquest
Drive Image (it runs in DOS). Powerquest referred
me to Microsoft Add-On for MS-DOS. I have not
found it on the Microsoft site. Does anyone know
if it's still available? Is there an alternative?
I have not worked with DOS for years and am
a novice to DOS networking. My computers are
networked with an Intel Anypoint parallel port
phoneline home network (Win98).
Thanks, Bob Olbrich rj...@gulftel.com
Jim Horvath
ftp://ftp.microsoft.com/bussys/clients
These were originally part of Windows for Workgroups and WinNT 3.51, but I
believe it they are capable of connecting to Win9X machines as well (using
netbeui I think). Perhaps someone else can explain the setup or the
differences between the versions in the various subdirectories.
I'm not familiar with your network adapter, but if it's a newer product than
1995, you probably won't find a driver for it in these files.
Jim
bob olbrich <rj...@gulftel.com> wrote in message
news:3A286C6F...@gulftel.com...
Jim Horvath
Jim Horvath <nos...@nothere.com> wrote in message
news:#KCNTCGXAHA.196@cppssbbsa05...
> You can still download the MS DOS Network Client from subdirectories
under:
>
> ftp://ftp.microsoft.com/bussys/clients
>
> differences between the versions in the various subdirectories.
>
The file ftp://ftp.microsoft.com/bussys/clients/readme.now appears to have
descriptions of the various clients and their installations.
Outsider
>
> Hello,
>
> I would like to create a network boot disk
> to access a network drive while using Powerquest
> Drive Image (it runs in DOS). Powerquest referred
> me to Microsoft Add-On for MS-DOS. I have not
> found it on the Microsoft site. Does anyone know
> if it's still available? Is there an alternative?
> I have not worked with DOS for years and am
> a novice to DOS networking. My computers are
> networked with an Intel Anypoint parallel port
> phoneline home network (Win98).
>
> Thanks, Bob Olbrich rj...@gulftel.com
Workgroup Add-on for MS-DOS
ftp://ftp.microsoft.com/Softlib/MSLFILES/MSWGCN.EXE
Or if its just the client you need:
ftp://ftp.microsoft.com/bussys/Clients/msclient/
You can use TCP/IP with MS Client, just choose it from the MS Client
setup [1]. The net drivers can be loaded high if you need to conserve
conventional memory. If your NIC isn't on the supplied list, see [2].
Then add server capability by modifying system.ini for file and
printer sharing and adding 'net start server' to the autoexec.bat file
[3] and upgrade net.exe by running WG1049.exe or NNET.exe [4].
Set up your shared resources on the DOS servers with netshare [5].
[1] www.wown.com/J_HELMIG/Dosclnt3.htm
http://www.wown.com/J_HELMIG/Doscltcp.htm
[2] http://www.wown.com/J_HELMIG/Doscl3up.htm
[3] http://www.wown.com/J_HELMIG/Dosservr.htm
[4] http://support.microsoft.com/support/kb/articles/Q129/1/64.asp
[5] ftp://ftp.microsoft.com/Softlib/MSLFILES/NETSHAR.EXE
http://www.wown.com/j_helmig/dosclien.htm
There are two ways to go.
MS Client. This is the one MS push because they were still charging for it.
Makes your DOS 6.22 system a client of any Win3.11/95/98/2k/etc system on
the net. Uses NetBIOS protocols. CLIENT ONLY. Comes with wide variety of
device drivers, and a supplementary disk is available for later NICs.
MS Add-On for DOS. Makes your system into a client AND a server. Uses
NetBIOS protocols. Uses essentially the same drivers as MS Client.
TCP/IP is available as an add-on to both.
ftp://ftp.microsoft.com/softlib/MSLFILES/TCP32B.EXE
TCP/IP network protocol files
--
<!-- Outsider //-->
MS-DOS 6.22, Windows for Workgroups 3.11, Netscape Navigator 4.08
"I think we ought to raise the age at which juveniles can have a gun."
--G. W. Bush
Marshall Price
--
Marshall Price of Miami, Florida
d021...@dc.seflin.org : "Oh, to unfree one's heaven!"
Tom Lavedas
The LAN-Manager/MSClient drivers implement network protocols from 'pure'
DOS which are completely compatible with TCP/IP and NT/Win 9x networks.
Pure DOS means any version from 3.? through 6.22 and Win 95/98/ME run
without the GUI ('booted to DOS').
Tom Lavedas
-----------
http://www.pressroom.com/~tglbatch/
Marshall Price
start-up files was "SHARE", which I only vaguely understand. Something
else (I forget what) suggested it was set up for a networking environment.
(It runs the Win95 with a "B" at the end, but I rarely invoke WIN, except
to read PDF docs.)
The nearest I've ever gotten to a network is INTERLNK/INTERSVR. But I
can't imagine a non-gui computer taking advantage of Windows programs! It
suggests there might be a way around the annoying "Get lost, you DOS bum!"
messages -- too good to be true.
Tom Lavedas wrote:
Tom Lavedas
require Windows.
This kind of networking gives access to shared resources like disk
drives and printers on a network that has a Windows (or Novell)
server(s). AFAIK, it doesn't even provide a way for the Windows
equipped machines to get to the resources on the DOS machines.
However, it is useful in integrating legacy systems into a new network.
That's what I am using it for. We have an ancient PCB development
system, with all of our companies designs, that is completely
incompatible with Windows. The DOS to NT link gives us access to our
new printers and provides an easy path for routine backups.
Tom Lavedas
-----------
http://www.pressroom.com/~tglbatch/
bob olbrich
Outsider wrote:
Outsider (12-2-2000, 9:07) or anyone else,
I 've reviewed the www.wown.com/J_HELMIG sites. Thanks for the info.
One problem - he discusses the file modifications necessary in the .INF files
for updated NIC's only. My network adapter is a Intel Anypoint, which , in my case
is an external parallel port adapter! I have found a anypoint.inf file to use for the
Anypoint adapter, but if I need to copy parts into the wcnet.inf file,
I don't understand what to do. Does anyone have any advice?
Thanks, Bob
bob olbrich
vn
running setup from msclient. When selecting a network card
you'll get an "other" choice.
Here is something I put put together a while back ...
Use MS Client to make a DOS PC network ready. Build software on a hard
drive. After a sucessful test copy files to a floppy.
Items -
Bootable c: drive
Bootable floppy
MS Client - Disk 1 network configuration. Disk 2 tcpip protocol.
Manufacturer's driver diskette.
1. Boot up DOS from the hard drive.
2. Insert Disk 1 and run a:\setup.exe.
3. Press Enter to set up network client.
4. Press Enter to copy files to c:\net. This is the default target
directory.
5. Select *Network adapter not shown on list below ...
Type in the path of the OEM driver disk. Insert manufacturer's
driver diskette.
The path has to be specific. Try a:\, a:\ndis2\dos, etc. One
time I had to use a:\wfwg. When the path is correct you should see
your network card listed.
6. Press Enter to select full redirector for best performance.
7. Enter user name. You can use a domain account. NOTE - username
will also become the node name. You can change this later. Press
Enter.
8. A boxed menu appears with The listed options are currently
selected.
Now you'll have a chance to change settings. Use arrows and TAB
to navigate.
Change Names - can change the username, node name, workgroup
name, and domain name.
Setup Option - can change to logon to domain.
Network Configuration - Use TAB to navigate between boxes. Use
arrows to select choices.
Add protocol. Default is nwlink. If not using nwlink you can
unselect it.
9. If choosing tcpip you should see Please Insert OEM driver disk.
This is misleading. Insert disk 2.
10. Insert Network Client disk. This is disk 1.
11. Setup will edit your config.sys and autoexec.bat files. All done.
Reboot to test. You will be prompt to enter a username and password.
PWL password files
are located in c:\net. You will get a sucessful completion message
when done.
Now you can connect to network shares by using the net command. Here
are some examples
net use g: \\server\share
net view \\server
net logoff
net logon
Copy files to a floppy -
The c:\net files are larger than what a floppy can hold. Remember this
is a bootable floppy and some space is alreadied taken. You do not
need the following files ...
setup.exe
*.dll
*.386
rascopy.bat
in some cases you can also delete at least one *.msg file.
Files that can be helpful but if space is needed you can delete.
addname.exe ( never used this )
ping.exe ( good for troubleshooting )
ipconfig.exe ( check tcpip status. to use type ipconfig a:\net )
I usually have fdisk, format, edit, himem.sys, emm386.exe in my DOS
directory.
I try to keep the a:\net directory about 1mb. If you're using dhcp you
need to copy the hidden file dhcp.prm.
Edit config.sys and autoexec.bat to change the drive letter from c: to
a:.
Edit a:\net\system.ini and change the path from c:\net to a:\net.
Edit a:\net\protocol.ini if needed. You can change the ipaddress,
subnet mask, gateway,
disable dhcp.
Edit hosts and lmhosts if needed. You may need these files if not
using dhcp.
NOTE - ip address should be entered without any decimals ( xxx xxx xxx
xxx ).
The same goes for the subnet mask.
Using Network Client Administrator -
If you have a NT server you can use this gui utility to build network
floppies.
If your network card is not listed you have to edit a file on the
server. Look
at MSKB Q128800 for more details. NCA will build a floppy specific for
installing
NT over the net.
Good Luck,
Vic
On Fri, 15 Dec 2000 20:36:59 -0600, bob olbrich <rj...@gulftel.com>
wrote: