
                  OS/2 Lan discussion              (Fidonet)

                 Saturday, 30-Oct-1999 to Friday, 05-Nov-1999

+----------------------------------------------------------------------------+

From: Will Honea                                        30-Oct-99 15:30:00
  To: Bryan Rubingh                                     30-Oct-99 15:30:00
Subj: LAN Server 3 & Big HD

Bryan Rubingh wrote to Will Honea on 10-28-1999
Bryan Rubingh wrote to Will Honea on 10-28-1999

BR>  WH> Two major problems, Bryan.  The most obvious is that Warp 3 is not
Y2K
BR>  WH> compliant without at least fp32 and it takes up to fp38 to straighten
BR>  WH> some of the PMMERGE problems.  Personally, I'd suggest fp40 and be
BR> 
BR> I think there is a 41 (and maybe 42) available now.  Any reason
BR> not to just go all the way?

Best one I can think of is that they will not install on your
configuration without cheating.  You appear to be using standard Warp
3 with LS 3 over it while fp41/42 specifically check for Warp Server
in syslevel.os2.
 
BR>  WH> done with it.  That will also tweek the IBM1S506 to a level that
should
BR>  WH> handle the 20g drive.  Just to be on the safe side, throw a copy of
BR>  WH> DANIS506.ADD in your kit - easier than chasing the IBM1S506.ADD revs
BR>  WH> all over the place.
BR> 
BR> I haven't checked DANIS506.ADD at all, but from messages I've been
BR> seeing, isn't that just for the VIA chipset or does that work with
BR> any IDE chips?

According to Daniela, it is pretty much a tossup with Intel chips but
with SIS, ALI, VIA, etc it's a much better solution.  Reason I suggest
it as a 'just in case' is that the last version she put out (on the
Hobbes site) should cover the 20gb drive without a hassle.

BR>  WH> The other problem is not so simple.  As far as I can tell, there has
BR>  WH> never been a fixpak released that brings LS 3 up to Y2K compliant and
BR>  WH> I know that there are parts of the IP stack that will die from 
BR> When you say IP, I assume you mean Internet Protocol.  We are
BR> using NetBeui as the protocol and there are no internet connections,
BR> so is there still a problem?  We actually did a test back in July of
BR> last year by advancing the date to 12/31/99 and letting it rollover.
BR>  We only spent a couple hours with it that way, but everything
BR> seemed to work correctly.

I seem to recall several fixes that called out Y2K related NetBeui
problems that mostly involved logon and session integrity issues,
especially if there were any other servers involved.  There were a
couple of odd account problems as well.  It would be worth a little
research time, certainly.

BR>  WH> timestamp problems.  LS 3 is long out of support but you might be
able
BR>  WH> to find the lastest updates at the IBM sites.  The most current
listing
BR>  WH> I have are at:
BR> 
BR>  WH> http://service5.boulder.ibm.com/pspfixpk.nsf/3f5d9c073e8a667
BR>  WH> 8625662800691e9b?OpenView
BR> 
BR> Thanks.  I was wondering if there were any updates available for
BR> it. However we really haven't had any problems with it.  I have some
BR> customers with Novell and NT and this one with LAN Server and you
BR> can easily guess which one has the least problems.

Yes, I work in an environment with multiple servers and that does seem
to be the case.  One other consideration would be the number of
nagging memory leaks that have been fixed over time.  BTW, the fixes
for NetBeui and TCP/IP are essentially inseperable since both are
actually protocol elements of what was still LAPS at the time 3.0 was
current.  They have merged the transport functionality into a single
overall package that supports all NetBeui, Novell, and TCP/IP protocols
and call the whole thing MPTS now.

Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: Bryan Rubingh                                     01-Nov-99 00:00:00
  To: Will Honea                                        01-Nov-99 00:00:00
Subj: LAN Server 3 & Big HD

-=> Quoting Will Honea to Bryan Rubingh <=-

 BR> I think there is a 41 (and maybe 42) available now.  Any reason
 BR> not to just go all the way?

 WH> Best one I can think of is that they will not install on your
 WH> configuration without cheating.  You appear to be using standard Warp
 WH> 3 with LS 3 over it while fp41/42 specifically check for Warp Server
 WH> in syslevel.os2.

Wow!  Thanks much for that info.  I'd probably have been stuck without
that knowledge.  Are you saying that fp41/42 check for Warp Server &
won't install if it exists?

 BR>  WH> done with it.  That will also tweek the IBM1S506
 BR>  WH> to a level that should
 BR>  WH> handle the 20g drive.  Just to be on the safe side, throw a copy of
 BR>  WH> DANIS506.ADD in your kit - easier than chasing the IBM1S506.ADD revs
 BR>  WH> all over the place.
 BR>
 BR> I haven't checked DANIS506.ADD at all, but from messages I've been
 BR> seeing, isn't that just for the VIA chipset or does that work with
 BR> any IDE chips?

 WH> According to Daniela, it is pretty much a tossup with Intel chips but
 WH> with SIS, ALI, VIA, etc it's a much better solution.  Reason I suggest
 WH> it as a 'just in case' is that the last version she put out (on the
 WH> Hobbes site) should cover the 20gb drive without a hassle.

Thanks again for that info.  I'll certainly snag a copy of it.

  Bryan Rubingh


... Rube Ink - Custom Programming/Computer Solutions

___ Blue Wave/QWK v2.20

--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: Will Honea                                        01-Nov-99 19:58:00
  To: Bryan Rubingh                                     01-Nov-99 19:58:00
Subj: LAN Server 3 & Big HD

Bryan Rubingh wrote to Will Honea on 11-01-1999

BR> Wow!  Thanks much for that info.  I'd probably have been stuck
BR> without that knowledge.  Are you saying that fp41/42 check for Warp
BR> Server & won't install if it exists? 

Just the opposite.  They ONLY install to Warp Server and NOT to Warp
3/Warp Connect.  If you have Warp Server then 41/42 will work.  I can
only speak personally of FP40 - that's where we are now until we have
time to qualify 42.

Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: Linda Proulx                                      01-Nov-99 22:11:11
  To: ALL                                               02-Nov-99 05:20:17
Subj: Lan OS/2 w/DOS

Greetings & Salutations,

Looking for a solution to network an older dos unit to a Warp 3 blue
connect unit.

Any peer-to-peer with a laplink type setup?  Can W4W on the DOS unit do
this with the os2 unit?

Anon,

-=Linda=-
... A clean desk is a sign of a cluttered desk drawer.
--- wsOMR v1.20b [UNREG]
 * Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     02-Nov-99 20:32:01
  To: Linda Proulx                                      02-Nov-99 07:45:03
Subj: Lan OS/2 w/DOS

Hi Linda,

 LP> Looking for a solution to network an older dos unit to a Warp 3 blue
 LP> connect unit.

 LP> Any peer-to-peer with a laplink type setup?  Can W4W on the DOS unit do
 LP> this with the os2 unit?

Ummmm, this is exactly what I was suggesting with my other reply, OS/2 Warp 3
Connect and W4WG both contain SMB/Peer-to-Peer style networking S/W so all you 
have to provide is the physical network between them and they can share
files/printers fine.

Cheers.................pk.

--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Bryan Rubingh                                     02-Nov-99 08:46:00
  To: Will Honea                                        02-Nov-99 08:46:00
Subj: Warp Connect & FP41


Are you certain on your facts?  I have Warp Connect here and I'm pretty
sure it was fp41 that I installed several months back.  I don't have
Warp Server.

  Bryan Rubingh


-=> Quoting Will Honea to Bryan Rubingh <=-

 WH> Bryan Rubingh wrote to Will Honea on 11-01-1999

 BR> Wow!  Thanks much for that info.  I'd probably have been stuck
 BR> without that knowledge.  Are you saying that fp41/42 check for Warp
 BR> Server & won't install if it exists?

 WH> Just the opposite.  They ONLY install to Warp Server and NOT to Warp
 WH> 3/Warp Connect.  If you have Warp Server then 41/42 will work.  I can
 WH> only speak personally of FP40 - that's where we are now until we have
 WH> time to qualify 42.

 WH> Will Honea <whonea@codenet.net>
 WH> -!- Maximus/2 2.02
 WH>  ! Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)



... Rube Ink - Custom Programming/Computer Solutions

___ Blue Wave/QWK v2.20

--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: Bryan Rubingh                                     02-Nov-99 08:49:01
  To: Linda Proulx                                      02-Nov-99 08:49:01
Subj: Lan OS/2 w/DOS

Linda,

I've been using Warp Connect as my server & main system connected to
several W4W machines for years.  Works fine.  Let me know if you have
any questions.  I also now have one W95 machine on the network with it.

  Bryan Rubingh


-=> Quoting Linda Proulx to All <=-

 LP> Greetings & Salutations,

 LP> Looking for a solution to network an older dos unit to a Warp 3 blue
 LP> connect unit.

 LP> Any peer-to-peer with a laplink type setup?  Can W4W on the DOS unit
 LP> do this with the os2 unit?

 LP> Anon,

 LP> -=Linda=-
 LP> ... A clean desk is a sign of a cluttered desk drawer.
 LP> -!- wsOMR v1.20b [UNREG]
 LP>  ! Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)



... Rube Ink - Custom Programming/Computer Solutions

___ Blue Wave/QWK v2.20

--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: Cyrill Vakhneyev                                  02-Nov-99 16:11:24
  To: Linda Proulx                                      02-Nov-99 16:27:05
Subj: Lan OS/2 w/DOS

Hello Linda!

01 Nov 99 22:11, Linda Proulx wrote to ALL:
 LP> Looking for a solution to network an older dos unit to a Warp 3 blue
 LP> connect unit.
    Using netbeui
    1) DOS LAN Client from M$-DO$ 6.22 full edition
    2) M$ wynndoze for WorkGroups (LAN part can work without GUI)
    3) DOS LAN Services aka IBM LS Client for DOS

    Using TCP/IP
    1) KA9Q
    2) Waterloo TCP
    3) PC-TCP
    1) DOS LAN Client from M$-DO$ 6.22 full edition
    5) IBM TCP/IP for DOS
    6) M$ wynndoze for WorkGroups with winsock

Bye!
Cyrill                                [Team OS/2 CV004]

... The best way to accelerate Windows is at escape velocity.
---
 * Origin: I feel like Popeye!  (2:5053/7.1)

+----------------------------------------------------------------------------+

From: Elvis Hargrove                                    02-Nov-99 10:27:05
  To: Linda Proulx                                      02-Nov-99 23:12:11
Subj: Lan OS/2 w/DOS

-> Looking for a solution to network an older dos unit to a Warp 3 blue
-> connect unit.

There is a way to do that using Lantastic that works very well for me
here.

There is a file called LANTASTI.ZIP  (available for freq here, less
than 3K ) that explains exactly how to set up a virtual Dos machine on
the OS/2 Box which can then network with other Dos machines on your
network.

The LAN only works in THAT window, and cannot perform as a Server, but
it sure beats "Sneakernet" for getting information and Data back and
forth between platforms.

For instance, I can run a mini-bbs program in the OS/2 virtual machine
and access the message bases and files on the Dos BBS.  I do it daily.


  ^..^
--- FidoPCB v1.5 beta-'j'
 * Origin: Personal Freedom is NEVER really FREE! (1:397/6.2)
397/1

+----------------------------------------------------------------------------+

From: Will Honea                                        02-Nov-99 19:16:02
  To: Bryan Rubingh                                     02-Nov-99 19:16:02
Subj: Warp Connect & FP41

Bryan Rubingh wrote to Will Honea on 11-02-1999

BR> Are you certain on your facts?  I have Warp Connect here and I'm
BR> pretty sure it was fp41 that I installed several months back.  I
BR> don't have Warp Server. 

Repeating rumors, but the IBM sites list FP40 as the most current for
Warp 3 and Warp Connect but 42 for Warp Server.

Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: George White                                      31-Oct-99 19:41:14
  To: Bryan Rubingh                                     03-Nov-99 00:38:02
Subj: LAN Server 3 & Big HD

Hi Bryan,

On 28-Oct-99, Bryan Rubingh wrote to Will Honea:


  -=> Quoting Will Honea to Bryan Rubingh <=-

 WH>> Two major problems, Bryan.  The most obvious is that Warp 3 is
 WH>> not Y2K compliant without at least fp32 and it takes up to fp38
 WH>> to straighten some of the PMMERGE problems.  Personally, I'd
 WH>> suggest fp40 and be

 BR> I think there is a 41 (and maybe 42) available now.  Any reason
 BR> not to just go all the way?

Because 40 is the last official one released for Warp 3.
41 & 42 are for Warp Server, although they can be fooled into applying
to Warp 3 you are on your own if anything goes wrong.

 WH>> done with it.  That will also tweek the IBM1S506 to a level that
 WH>> should handle the 20g drive.  Just to be on the safe side, throw
 WH>> a copy of DANIS506.ADD in your kit - easier than chasing the
 WH>> IBM1S506.ADD revs all over the place.

 BR> I haven't checked DANIS506.ADD at all, but from messages I've been
 BR> seeing, isn't that just for the VIA chipset or does that work with
 BR> any IDE chips?

Most ATA chipsets are supported, although there is little need for it
if you have an Intel ATA chipset as that is fully supported by the IBM
driver.

George

--- Terminate 5.00/Pro 
 * Origin: A country point under OS/2 (2:257/609.6)
397/1

+----------------------------------------------------------------------------+

From: Linda Proulx                                      02-Nov-99 18:04:18
  To: Peter Knapper                                     03-Nov-99 05:14:26
Subj: Re: Lan OS/2 w/DOS

Greetings and Salutations,

     -=> Peter Knapper wrote to Linda Proulx <=-

 PK> Hi Linda,

 PK> Ummmm, this is exactly what I was suggesting with my other reply, OS/2
 PK> Warp 3 Connect and W4WG both contain SMB/Peer-to-Peer style networking
 PK> S/W so all you have to provide is the physical network between them and
 PK> they can share files/printers fine.

But run programs on each other's hard drive?


Anon,

Linda

... Beat me!  Whip me!  But don't make me read my mail online.
--- MultiMail/MS-DOS v0.32
 * Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     03-Nov-99 20:29:06
  To: Linda Proulx                                      03-Nov-99 06:34:07
Subj: Re: Lan OS/2 w/DOS

Hi Linda,

 PK> Ummmm, this is exactly what I was suggesting with 
 PK> my other reply, OS/2 Warp 3 Connect and W4WG both 
 PK> contain SMB/Peer-to-Peer style networking
 PK> S/W so all you have to provide is the physical 
 PK> network between them and they can share files/printers 
 PK> fine.

 LP> But run programs on each other's hard drive?

Yes! OS/2 Warp Connect contains both the Server and Client code, it can access 
files (and therefore programs) on other machines, and it can offer up files
(and therefore programs) to other machines.

However be warned that the DOS Code is a CLIENT ONLY, it does NOT contain any
Server code. Performing a fully functional Server on a DOS machine        
requires a LARGE amount of memory, and there is normally not enough memory
left after loading Sserver and Client Networking code for runing other tasks,
so most people do not consider this as a practical apprpoach.

Cheers...........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Linda Proulx                                      02-Nov-99 22:17:25
  To: Bryan Rubingh                                     03-Nov-99 06:34:07
Subj: Re: Lan OS/2 w/DOS

Greetings and Salutations,

     -=> Bryan Rubingh wrote to Linda Proulx <=-

Can you send your DOS autoexec & config?  I am running DOS 6.22.  I
gather I won't actually have to run W4W just have it set up for
connection?



Anon,

Linda

... Beat me!  Whip me!  But don't make me read my mail online.
--- MultiMail/MS-DOS v0.32
 * Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)

+----------------------------------------------------------------------------+

From: Bryan Rubingh                                     03-Nov-99 09:34:00
  To: Linda Proulx                                      03-Nov-99 09:34:00
Subj: Re: Lan OS/2 w/DOS


Linda,

You are correct.  You don't have to run W4W, although you probably do
want to run it to set up the network card and protocol.  After you set
that up and get them talking, you can tweak the autoexec.bat so it will
start and give you full connections.  You can also add and remove
connections from DOS.  Be sure to put some shares in your OS/2 machine
so that other users can access them.

Here's my autoexec.bat:

@echo off
LH /L:0;1,45456 /S C:\DOS\SMARTDRV.EXE 2048
c:\mouse\mouse
Prompt $p$g
PATH C:\DOS;D:\WINDOWS;C:\;C:\UTIL;C:\BAT;C:\MCAFEE\DOS
SET QBACKUP=P:\QBACKUP
set TEMP=C:\TEMP
set d=/f
C:\DOS\doskey
C:\DOS\subst p: c:\dapp
LH /L:0;1,59888 /S D:\WINDOWS\net start full /yes
C:\DOS\share.exe /L:500 /F:5100
menu

The change I made after W4W set it up was to add the word "full" (and
perhaps the /yes too, I don't remember) on the windows\net start line.
Type "net /?" for info on all the commands.

Here's my config.sys:

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE RAM X=C600-C6FF
BUFFERS=20,0
FILES=50
dos=UMB
LASTDRIVE=Z
FCBS=4,0
dos=HIGH
REM Buffers=40
stacks=15,512
DEVICEHIGH /L:1,4560 =D:\WINDOWS\IFSHLP.SYS
DEVICEHIGH /L:1,9072 =C:\DOS\ANSI.SYS
SHELL=C:\DOS\COMMAND.COM C:\DOS\  /p

One word of warning.  This will start and appear to come up normally
even though you may not have a connection to the OS/2 machine.  It shows
me making all the connections to drives/dirs that I have shared &
connected.  I think there is a way to make it fail if the connection
doesn't exist, but I didn't set mine up that way.

BTW I have an NE2000 clone in both of my machines and am using NetBeui
as the protocol.  I have another machine with a 3C503 card.  The 3c503
will not work unless I start W95 first (I have all three OS's on that
one).  After I boot to W95 I can shut down and boot to DOS and it will
connect.  I think it is a problem in my DOS driver, but I don't use DOS
often enough on that machine to fix it.

If you set everything up in W4W you shouldn't need this, but here's my
protocol.ini file from windows:

[network.setup]
version=0x3110
netcard=ms$ne2clone,1,MS$NE2CLONE,3
transport=ms$nwlinknb,NWLINK
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,NETBEUI
lana0=ms$ne2clone,1,ms$netbeui
lana1=ms$ne2clone,1,ms$nwlinknb
lana2=ms$ne2clone,1,ms$ndishlp

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP

[NWLINK]

BINDINGS=MS$NE2CLONE
[MS$NDISHLP]
DriverName=ndishlp$
BINDINGS=MS$NE2CLONE

[NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=MS$NE2CLONE
LANABASE=0


[MS$NE2CLONE]
DriverName=MS2000$
INTERRUPT=11
IOBASE=0x300

[NE2000]
Adapters=MS$NE2CLONE

  Bryan Rubingh


... Rube Ink - Custom Programming/Computer Solutions

___ Blue Wave/QWK v2.20

--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: Neil Walker                                       02-Nov-99 21:08:21
  To: Linda Proulx                                      03-Nov-99 10:23:26
Subj: Lan OS/2 w/DOS

Hello Linda!

Monday November 01 1999 22:11, you wrote to ALL:

 LP> Looking for a solution to network an older dos unit to a Warp 3 blue
 LP> connect unit.

 LP> Can W4W on the DOS unit do this with the os2 unit?

Yes. My network consists of 3 machines running WfWG, Win98 and OS/2. I elected 
to go for TCP/IP so had to download the (free!) TCP/IP add-on for WfWG but
they all talk to each other "out-of-the-box" with NETBIOS/NETBEUI.


Be lucky,


Neil

--- GoldED/2 3.0.1
 * Origin: The Electric Pigeon - <01952 414247> (2:2500/509)
397/1

+----------------------------------------------------------------------------+

From: Leonard Erickson                                  03-Nov-99 00:06:02
  To: Linda Proulx                                      03-Nov-99 14:31:00
Subj: Lan OS/2 w/DOS

 -=> Quoting Linda Proulx to ALL <=-

 LP> Greetings & Salutations,

 LP> Looking for a solution to network an older dos unit to a Warp 3 blue
 LP> connect unit.

 LP> Any peer-to-peer with a laplink type setup?  Can W4W on the DOS unit
 LP> do this with the os2 unit?

I was able to transfer files *using* Laplink in a DOS window. I was
using Laplink III.  The transfers would lock up occasionally, but I
just closed the window on the OS/2 system, deleted the partial file and
restarted the transfer with that file.


--- Blue Wave/DOS v2.30
 * Origin: Shadowshack (1:105/51)

+----------------------------------------------------------------------------+

From: Linda Proulx                                      03-Nov-99 13:16:21
  To: Elvis Hargrove                                    03-Nov-99 22:31:21
Subj: Re: Lan OS/2 w/DOS

Greetings and Salutations,

     -=> Elvis Hargrove wrote to Linda Proulx <=-

 EH> There is a file called LANTASTI.ZIP  (available for freq here, less

Can you attach the file to me to my email address?


Anon,

Linda

... Beat me!  Whip me!  But don't make me read my mail online.
--- MultiMail/MS-DOS v0.32
 * Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)

+----------------------------------------------------------------------------+

From: Linda Proulx                                      03-Nov-99 13:17:28
  To: Peter Knapper                                     03-Nov-99 22:31:21
Subj: Re: Lan OS/2 w/DOS

Greetings and Salutations,

     -=> Peter Knapper wrote to Linda Proulx <=-

 PK> However be warned that the DOS Code is a CLIENT ONLY, it does NOT
 PK> contain any Server code. Performing a fully functional Server on a DOS

So I will have to access the lan from the old unit & not the os2 unit?


Anon,

Linda

... Beat me!  Whip me!  But don't make me read my mail online.
--- MultiMail/MS-DOS v0.32
 * Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)

+----------------------------------------------------------------------------+

From: Linda Proulx                                      03-Nov-99 13:19:14
  To: Leonard Erickson                                  03-Nov-99 22:31:21
Subj: Re: Lan OS/2 w/DOS

Greetings and Salutations,

     -=> Leonard Erickson wrote to Linda Proulx <=-

 LE> I was able to transfer files *using* Laplink in a DOS window. I was

I wnat more to run programs on the DOS unit.  Not just a file transfer.


Anon,

Linda

... Beat me!  Whip me!  But don't make me read my mail online.
--- MultiMail/MS-DOS v0.32
 * Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     04-Nov-99 21:06:06
  To: Linda Proulx                                      04-Nov-99 07:58:28
Subj: Re: Lan OS/2 w/DOS

Hi Linda,

 PK> However be warned that the DOS Code is a CLIENT ONLY, it does NOT
 PK> contain any Server code. 

 LP> So I will have to access the lan from the old unit & not the os2 unit?

I am not too sure what you mean by "access the lan from the old unit"???. This 
may help to explain it better -

I general terms, standard Windows style Networking consists of 2 main
"functions", Server and Client. A Server performs the function of making a
RESOURCE (Printers, drives, directories and files, etc), as a SHARE, to
CLIENTS. A CLIENT "Connects" to those RESOURCES (SHARES) and USES them.

OS/2 (and W4WG) networking provides both functions in the one package. The DOS 
LAN Requestor, only provides the CLIENT function, so this means you cannot
offer up any of your DOS resources to other machines on the network. Any data
you wish to transfer TO or FROM your DOS machine to any other machine on the
network MUST be performed from the DOS (CLIENT) machine. 

This also means that from the DOS machine, you can run a DOS program that is
stored on an OS/2 machine, and is made accessible by CONNECTING the DOS
machine to the drive that is SHARED from the OS/2 machine.

I hope this helps.........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

+============================================================================+
