4 Apr
2004
4 Apr
'04
9:03 a.m.
Hi people!
I'm looking for two things (one or the other).
A Manual for an AERCO Easie-ST Ram upgrade Kit for the
Atari 520-ST.
OR
An upgrade kit to upgrade an Atari ST to 4mb of RAM.
I have an Aerco Adapter that isn't working, and I
think I need the manual to tech it out, AND to upgrade
it to 4mb of RAM.
I have a Spectre-128 for it, and I'd love to be able
to use this machine as a MacPlus for kicks.
But 512k isn't enough RAM to do anything useful.
Also.. Looking for a SCSI Adapter for the ST as well.
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
12:22 p.m.
In message <407044F0.2070009(a)jetnet.ab.ca>
ben franchuk <bfranchuk(a)jetnet.ab.ca> wrote:
Al Hartman wrote:
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?
Hi people!
But 512k isn't enough RAM to do anything useful
Look what Bill Gates can do
in 640K. :) Well memory relative I guess, 512 MEG don't seem
to
CUT it now days!
My fileserver's running OK with 96MB, the graphics workstation
(Linux based
P3-560) works fine with 128MB of RAM. Oh, and the RISC PC only has 64MB, but
I very rarely see "Out of memory" errors on it.
A long jump from 4k of memory on the early machines.
4K?! Luxury! "Why, when I was a kid, we had 256 BYTES of RAM, and we jolly
well liked it!" (yeah, sure, Grampa). :)
I did have a Sinclair ZX81 at one point - unfortunately the power supply blew
and took out the voltage regulator and most of the ICs on the board. It was
deemed beyond repair :(
Later.
--
Phil. | Acorn Risc PC600 Mk3, SA202, 64MB, 6GB,
philpem(a)dsl.pipex.com | ViewFinder, 10BaseT Ethernet, 2-slice,
http://www.philpem.dsl.pipex.com/ | 48xCD, ARCINv6c IDE, SCSI
... Now where did I put that fire extinguisher?
12:26 p.m.
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?
12:54 p.m.
On Sunday 04 April 2004 16:26, Jeffrey H. Ingber 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.
SMB == the protocol on top of NetBEUI/IPX/IP that is Microsoft disk and
printer sharing. And MS Lan Man does speak IP, I've set it up before.
> 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?
Pat
--
Purdue University ITAP/RCS --- http://www.itap.purdue.edu/rcs/
The Computer Refuge --- http://computer-refuge.org
5 Apr
5 Apr
12:08 p.m.
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
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.
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?
12:26 p.m.
On Mon, 5 Apr 2004 16:08:25 -0500
Scott Stevens <sastevens(a)earthlink.net> wrote:
Correction. That should read:
back when all some of us could afford was a single 386
box to run
a Freenix on, so we had to use 286 and earlier boxes to 'fool around'
with networking at home.
7374
days inactive
7375
days old
6 comments
6 participants
participants (6)
-
alhartman＠yahoo.com -
bfranchuk＠jetnet.ab.ca -
jingber＠ix.netcom.com -
pat＠computer-refuge.org -
philpem＠dsl.pipex.com -
sastevens＠earthlink.net