Hi Linda,
On 29-Oct-99, Linda Proulx wrote to All:
LP> Want to network new & old units. The new will have OS/2 but
LP> the old will run DOS. If I have Lantastic on the old unit, will
LP> OS/2 Connect "connect" :-) with it?
No. Lantastic will only network with Latastic :-(.
There are ways of networking DOS. From my archives:
/* (DOSNET.TXT)
===========================================================================
BBS: DoNoR/2
Date: 28-10-97 (18:57) Number: 5421
From: MARK LEWIS Refer#: 5420
To: ALEC HERRMANN Recvd: NO
Subj: OS/2 to DOS & Win95 Conf: (16) Os2lan
---------------------------------------------------------------------------
AH> As for the DOS box - you will have to get some networking
AH> software for it. The little known Microsoft Workgroups for
AH> DOS will work.
i just went hunting for this... had to search for
"microsoft workgroup add-on for dos" to find it... then i
located the following article...
http://support.microsoft.com/support/kb/articles/Q108/3/91.asp
on microsoft's page... it states, in part...
===== quote =====
The purpose of this article is to inform you that the Microsoft Network
Client - Workgroup Connection can be obtained free of
charge.
Microsoft Network Client version 3.0 replaces
Microsoft Workgroup Add-On for MS-DOS and Microsoft
Workgroup Connection. Microsoft Network Client version 3.0
is the preferred MS-DOS network client software. However,
Microsoft will continue to make Workgroup Connection
available for customers who want its file and print server
capabilities.
===== quote =====
i'm pulling the file(s) mentioned in the article now and
will likely be playing with them over the next weeks... i'm
looking to do plain old netbios... maybe over tcp/ip or ipx
if needed... will have to see what i can break, eh?
)\/(ark
===========================================================================
BBS: DoNoR/2
Date: 28-10-97 (11:32) Number: 5426
From: LEE ARONER Refer#: 5425
To: STEVEN COX Recvd: NO
Subj: OS/2 to DOS & Win95 Conf: (16) Os2lan
---------------------------------------------------------------------------
SC> I now have 3 different computers running 3 different
SC> os's. I have specific
> uses for each & need to connect them all. The main
> machine runs OS/2. The
> Win95 machine is important & the dos box could go away.
SC> What is the best way to connect these boxes? The OS/2
SC> & win95 boxes are in
> different rooms but running cable is not a problem.
> The dos box is next to the
> OS/2 box.
SC> All I need is a communication link between the 2 boxes.
SC> I would like to be
> able to access my BBS from the Win95 & dos boxes.
You can run the MS network client on the DOS box, then all three
boxes will be able to see each other.
Here's how:
Download the following files from MS:
ftp.microsoft.com in /bussys/clients/msclient - Files are:
DSK3-1.EXE and DSK3-2.EXE
You also need to get the newer NET.EXE file from
/softlib/mslfiles - File is: WG1049.EXE (Adds server capability)
You will need a network card that includes an NDIS 2.0 or greater
driver. (Most all do...). Don't expect a bus-mastering driver to
work without some pain. (I could NOT get a Kingston PCI 100mbs
card to work with QEMM at all, had to go back to an ISA card).
Install the first two disks and get it working as a client. Then
overwrite your original NET.EXE file with the above version, and
you will have server capability.
Suggest you change the default values for "Sessions" and "NCBs"
in PROTOCOL.INI to at least 16 and 32 respectively. The default
values are insufficient.
Using QEMM and the Helix mouse driver and disk cache, and running
QEMM's VIDRAM, I get about 609k free for my DOS BBS to run in,
and that's WITH a 8 meg ram disk, and FAX and Stomper modem
sharing TSR's installed. Works like a champ, but it gets a bit
unstable when a BBS caller does a Doorway shell and pokes around
the network.
LRA
*/
George
--- Terminate 5.00/Pro
633/260
2501/209
* Origin: A country point under OS/2 (2:257/609.6)
|