On Sun, 04 Apr 2004 17:26:14 -0400
"Jeffrey H. Ingber" <jingber(a)ix.netcom.com> wrote:
On Sun, 2004-04-04 at 22:22 +0100, Philip Pemberton
wrote:
How are you doing this? MS Lan Manager doesn't speak SMB AFAIK, and
Samba doesn't speak NetBEUI.
Jeff
I've got a 386 PC sitting behind me running
Caldera DR-DOS 7.03. It's got 8MB
of base RAM and is fitted with an Ethernet card. I've even got it
communicating with the SAMBA (Windows File And Print Sharing) server. Without
the SMB junk loaded, it's got 617KB of free "conventional" RAM. With SMB
(well, M$ Client for DOS) loaded, it usually has about 417KB free. Did I
mention the fact that both Turbo Pascal 7 and Turbo C++ 3 will run quite
happily on this system?
There are TCP/IP drivers for the Microsoft Client for DOS. Samba 'just
works' with it.
I used to run it years ago with a Linux box with the 1.2 kernel. You can set up the
Microsoft Client to boot up from just a single diskette if you trim down the config to the
bare minimum. Then you can put up a system with just a floppy disk, no hard drive, with
the Samba share mounting as C:. I found through experimentation that you can then install
Windows 3.1 on that 'C' drive from the floppy disks. Windows 3, installed this
way, doesn't even know there is a network involved. So you can then have a whole
system booting from a floppy that has a network mounted Windows 3 on it. This is, of
course, of limited value today, but it's interesting to fool with, or it was back when
all some of us could afford was a single 386 box to run Windows, so we had to use 286 and
earlier boxes to 'fool around' with networking at home.
And to be honest, I wish I'd been scarfing up Dec and old Sun stuff back then and not
diddling around with PC junk and those 3Com ethernet cards I got at a surplus store
(ancient 3c501s) for $2.50 a pound.