John Donohue wrote in a message to Mike Bilow:
MB> There is also a product available from Microsoft for
MB> about US$50, Workgroup Add-On for DOS, which will act
MB> as both a client and as a peer server.
JD> I know this has been out for some time (we use the free
JD> client for our DOS machines to use our NT servers) but I've
JD> never actually seen it anywhere. It also doesn't seem to be
JD> described anywhere on Microsoft's web site. Maybe you can
JD> answer some questions about it.
It definitely exists. I have a copy.
JD> - how much memory does it need?
I don't know exactly. It is a superset of the client. I think it needs
about 20-30 KB more than the client, although it can be loaded into UMB if
that exists, just like the client.
JD> - does it support the microsoft TCPIP add-on that WfWG's uses?
I think so. I have used the TCP/IP components for support of NetBIOS over
TCP/IP, but I have never done anything else with them. The Microsoft TCP/IP
implementation is very, very minimal.
JD> - will it run on a microchannel box?
I don't see why it wouldn't, provided that you had the proper NDIS drivers.
On the other hand, I've never tried it.
JD> - does it have native support for the IBM Lan Adapter/A card on
JD> MCA?
It uses straight NDIS.
JD> - why am I asking all these questions? ;-)
JD> somebody gave us a PS/2 model 80 server with a gig of
JD> disk(s), 2 megs of memory, and no software. I found NDIS
JD> drivers on an IBM web site, but can't quite make the thing
JD> work with Lantastic 7. 2 megs isn't enough for WFWG or OS/2
JD> 2.x, or the MCA tweaked Linux. So, at present, it's a big
JD> door stop....
You can throw more memory in there. It takes standard 72-pin SIMM, as far as
I can remember; they may have to be true-parity, however. You should be able
to boot OS/2 to a command prompt in 2 MB, but you really have to know what
you are doing in that configuration.
JD> - should I move this to the LANTASTIC echo?
No, I think Lantastic is unlikely to work.
-- Mike
---
---------------
* Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107)
|