Quick Search	Power Search	Search Filter	Interest Finder	Browse Groups	Post Message

Article 16 of 27

Text Only   Help

Previous Article

Next Article

Current Results

View Thread

Post Message

Subject:      Re: Networking a Dos machine and Win95
From:         gerry@dds.nl.SPAM.BLOCK (Gerry W. Veerman)
Date:         1997/07/30
Message-Id:   <33e02020.6970300@news.xs4all.nl>
Newsgroups:   comp.os.ms-windows.networking.win95
[More Headers]

On Tue, 22 Jul 1997 19:35:10 GMT, **bfeuchuk@jumppoint.com (Bruce
Feuchuk) wrote:

>With Deft Fingers, cyrus@linknet.net (CJ) wrote:
>
>>I am in search of Microsoft Networks for MS-Dos.  I've explored all the 
>>various ways of connecting an MS-DOS box and a Win95 box together, and think 
>>the best way for me to go right now is to get 2 NIC cards and the OSes to work 
>
>Get the DOS Workgroup Client from ftp.microsoft.com, in directory
>/bussys/clients/MSCLIENT.  Get both files.  They're self-extractors.
>
>Extract all the files, run SETUP.  Now your DOS machine is a client on yourt
>Windows P-t-P network.
>
>Go back to ftp.microsoft.com, and get WG1049.EXE, from /softlib/mslfiles.
>It's another self-extractor.  Run it in your /NET directory, and let it
>overwrite whatever it wants to.
>
>Now you HAVE TO enable the sharing of their Hard drive (and LPT's if you
>wish).
>
Aha. The mysterious sharing rituals revealed at last.
:-)

>If you take a look in SYSTEM.INI you will see the two lines near the top:
>
>[network]
>directhost=yes
>sizworkbuf=1498
>filesharing=yes        <<--------
>printsharing=yes      <<--------
>autologon=yes
>
>These two lines are NO as the default... just change them to YES.  Note that
>IF you make any future changes via SETUP (for the dos client/server) it WILL
>change things back to NO (trust me on this one)...
>
>Also in your Autoexec.bat file you have to tell the system what to share and
>what it's name is.  An example is:
>
>C:\NET\net initialize
>C:\NET\nwlink
>C:\NET\net start
>net share Printer=Lpt1 /full /yes
>net share C-Drive=C:\ /full /yes
>
My experience is you don 't want to execute the full sharing commands
every time the network starts. You 'll have errors like 'share name
already used'..
Just the command 'net share' will do, as the configured shares seem to
be saved the first time.

>In other words, you 'assign' C-Drive as the log in name for other system to
>map to (ie: map E: as \Sys2\C-Drive)...
>
>And as you can see, you 'NEED' to assign a name for your LPT1 as wall.  In the
>example above, I've assigned 'printer' for LPT1 and 'c-drive' for the Hard
>drive (this is what is needed for mapping and port capturing - identical as
>for Windows Networking).
>
>Once you've assigned the above, AND your SYSTEM.INI file has the correct Dos
>machine Name and Workgroup, then you 'should' be able to see the Dos machines!
>Here is an example of my System.Ini for the above:
>
>computername=RFA8
>lanroot=C:\NET
>username=PLOTTER
>workgroup=WORKGROUP
>reconnect=yes
>dospophotkey=N
>lmlogon=0
>logondomain=WORKGROUP
>
>We have 12 machines (RFA1 to RFA12).  This machine is used for a Laser Server
>(so instead of a User 'name' like BRUCE, I call it PLOTTER).  And we use the
>default Workgroup name.
>
>Hopefully this will solve your issues!
>
It brought mine a step further at solvation, thanks Bruce.

Now I see the DOS in machine in Netw. N., can open a window on its
shared drive and even drag and drop files through the coax.
(MS is amazing Mike would say)

BUT. Trying to _map_ the DOS drive on the W95 machine will lose the
connection and cause the DOS machine to freeze beyond soft reboot. 
How to tackle this one ?

The DOS machine uses the IPX/SPX compatible protocol since setup
provides it default and it uses less dear memory than NetBUI I
understand. Basic redirector, no optimizing.


 - Gerry

--
  | X | gerry@dds.nl
  | X | Amsterdam, Holland
  | X | The ultimate medium for the loudmouth & obsessed: USENET