That's what I was led to believe also, but it's not true. Even though the
ODI driver set is quite a bit bigger than the earlier
IPX.com, for every
card I've tried out, my threshhold is the required transient area (useable
low memory) under DOS 3.22 or 6.22, with all my SCSI drivers, etc, (I can
leave out the CDROM stuff) loaded, so I can still use my DOS-based OrCAD for
schematic capture, digital simulation, and PCB routing. The PCB router is
the crux, since it won't do everything if there's not 600+ KB of available
low memory. Not even all the ODI drivers will leave enough space for that.
A few of the cards I use will do it though.
Dick
-----Original Message-----
From: Bill Pechter <pechter(a)pechter.dyndns.org>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Monday, November 15, 1999 3:38 PM
Subject: Samba
> >SAMBA is that NETBEUI-compatible protocol used
by Windows for
Workgroups,
> >isn't it? I've heard a lot of mention
of it but no details except that
its
> >DOS client is HUGE by comparison with the
already large but purportedly
MUCH
smaller NOVELL IPX+NETX. (about 96K).
Actually, the dos client works with the MS Dos and Windows IP stacks
and it's netbios over TCP/IP. It's the IP stack that's the real issue.
IPX and NETX are real small. Try loading LSL, IPXODI, and the VLMs and
it is more like the microsoft stuff in size 8-(.
>
> BTW, I've found the real trick of working with Samba (on the Admin side)
is
remembering
where the &)# @*^% smb.conf file on a particular machine is!
Zane
Ain't it the truth... Redid the servers this weekend with 2.6 of Samba.
Now I've got to try to do the domain thing and login scripts for it.
Bill
---
bpechter@shell.monmouth.com|pechter@pechter.dyndns.org
Three things never anger: First, the one who runs your DEC,
The one who does Field Service and the one who signs your check.