>The fact (well, at least my opinion) is that Apple makes it easy to
>remain completely ignorant of most important things about their
>computer while still "using" them.
I won't disagree with you.
But Richard spouts out as an expert in all things computer... if he has
half the brains, and computer smarts he trys to claim... then he should
have known far more about the Mac then he appears to if he has "5+ years
of daily use".
I have friends with the IQ of a potato, who have less than 5+ years of
non daily use of a Mac, and know far more than Richard appears to know.
I just find it hard to swallow... taken in context with everything else
Richard says.
I just went over as many of Richards emails as I still have on this
machine, and I found that maybe it isn't so much that Richard is lying,
so much as he is twisting the truth. Like for instance, he said he bought
the AppleVision monitor for $3.95 when he got it ("It's only a small risk
at $3.95."), but then just now said he paid $2.95 ("including the
Applevision monitor for $2.95").
Sure, he isn't lying, he just forgot the price by a $1 since last week...
acceptable, understandable, not a problem.
Except that he does that thru almost EVERYTHING he writes (he paid ~$10
for two performa's including tax... but then later the reduced by a buck
monitor was lumped into that same approx $10 price, significantly
reducing the price he is implying he paid... again, it is a rounding
issue, it isn't a lie... it is just implying something that is not quite
true.)
He also tries to spout off as an expert in any topic he is discussing,
but when you go back and look at the facts, he admits that he has no idea
what he is talking about (he claims Mac's have a 250% price premium...
but he hasn't looked at pricing in over 15 years... except he checked
ebay and it says prices are 2.5:1). So what he REALLY said is... he has
NO idea what current prices are, but he is going to pretend he knows, and
he is going to hold Apple responsible for the prices that he will assume
to be true, and he will base as his only source of proof, the used prices
he finds on eBay, and he will ignore the historically higher resale value
of the Mac over the generic PC.
So I appologize, Richard isn't lying, he is simply not telling the whole
truth, and is implying far more than he should, and attempts to make
people believe he is an expert on topics by speaking of things as if they
are fact, when in reality he has no real knowledge of the facts, but just
assumes anything he thinks must be correct, and treats it as such.
>like a mouse that has only
>one button... to avoid confusion
I really wish Apple would cut the crap with that. They freaking introduce
contextual menus with OS 8, but STILL refuse to release a two button
mouse. But then, maybe they are not bundling a multi-button mouse in
order to help 3rd party companies sell them... who knows.
>> Not to mention, you stated back when it all started that you haven't
>> seriously touched a computer by Apple in 15 years except to pull the
>> power supplies from them.
>
>Ok, that's somewhat of an odd statement in context.
>
>Could it be that he wasn't doing "serious" work on the systems at the
>time?
see... that is just what I am talking about. He will claim he hasn't
seriously touched them in years, implying that he never uses them, and
knows little about them. Then later, when it suits his statements, he
will claim that he has 5+ years of daily useage of them. It may be that
neither is false. Maybe 10 years ago, he stopped using the Mac after
having done 5+ years working with them. That would let him have 5 years
of useage under his belt AND not have touched them in years. Or maybe,
like you say, he means serious in the strictest of senses, and he hasn't
used the Mac for "hard core" work in years, but uses them for games every
day.
With the way he twists everything to fit what he wants at a given moment,
you just can't tell.
I do know one thing... if I ever need a someone to argue a case for me...
I think I want Richard on my side... he has the best doublespeak I have
ever seen (read?).
-chris
<http://www.mythtech.net>
> From: Richard Erlacher
>
> ----- Original Message -----
> From: "Chris" <mythtech(a)mac.com>
>
>
> > I can't... I just can't any more. I have been trying to be nice to
> > Richard despite all the clear flame bait he has been throwing out here.
> >
> > But with his comment above, I just can't any more.
> > ...
>
> >
> > I'm sorry... I just can't do it any more.
> >
> Then don't ... When you get old enough that you're out in the working
> world,
> where your performance is measured on whether or not you meet schedule and
> budget, and not on how cute your comments are, you'll understand the
> realities
> of why people use what they do. If you're just idly fiddling with
> something
> interesting at home, nobody cares how long it takes you.
>
>
Chris ---
This is cute, and kinda funny, since Rich has seemed to have
forgotten all the times you talk about being in the fire dep't, well, and
the fact that you _are_ in the working world...
I thought one of the rules of engagement was to 'know your enemy'?
--
--- David A Woyciesjes
--- C & IS Support Specialist
--- Yale University Press
--- mailto:david.woyciesjes@yale.edu
--- (203) 432-0953
--- ICQ # - 905818
Mac OS X 10.1 - Darwin Kernel Version 5
Running since 01/22/2002 without a crash
From: Loboyko Steve <sloboyko(a)yahoo.com>
>An additional ugliness in the spec is that apparently
>the -5 has to be the first and last voltage the chip
>sees. I hope that this is not TOO critical...sometimes
>I forget how "good" we have it now.
It is critical. I've destroyed 2708s in a system that did +12
first by error. FYI: it doesnt matter howmuch before the
two positive supplies on that -5V is first on and last off.
4104s and 4116s (drams) also had a similar requirement
as did many of the other three voltage parts.
Allison
> From: John Allain
>
> From: Richard Erlacher <edick(a)idcomm.com>
> Sent: Monday, May 06, 2002 1:37 PM
>
> <delete>
>
- ***chuckle, chuckel*** While that is a good idea, I am getting some
good giggles and grins from reading this whole exchange, especially since
I've met Chris in person a couple times...
--
--- David A Woyciesjes
--- C & IS Support Specialist
--- Yale University Press
--- mailto:david.woyciesjes@yale.edu
--- (203) 432-0953
--- ICQ # - 905818
Mac OS X 10.1 - Darwin Kernel Version 5
Running since 01/22/2002 without a crash
> -----Original Message-----
> From: Richard Erlacher [mailto:edick@idcomm.com]
> That stuff is irrelevant, since *nix was demonstrated to be
> an insufferable
> cost and pain back in '82. Someting that ugly and
> unfriendly, that tore down
> the system each time an application had to be patched,
> resulting in days of
> downtime was just not acceptable. As a result, *nix hasn't
> gotten much of a
> look around here since then, aside from a brief peek at
> Linux. ... and
> neither has SUN hardware.
General relevancy aside (I assume you're speaking subjectively
for you own use above)... In the context of being used for --
whatever you use your computer for -- I'd agree that its relative
ability in any area is irrelevant if you won't consider using it
anyway.
I just wanted to mention, in case anyone reading may not know, that
it's no longer the case (and has not been for a very long time)
that you must re-build the kernel every time you'd like a new driver.
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
On Sun, 5 May 2002, Ted Harris wrote:
>
> The Freshest Bulk Email Lists
> at Deep Discount Prices
>
> Datasurplus is the best source for bulk email lists.?
>
> All lists are harvested within the last 3 weeks.
Well, at least now I know who harvested my email address from the list...
(I started getting massive amounts of spam a couple weeks after my first
post here...)
-Toth
> -----Original Message-----
> From: Cameron Kaiser [mailto:spectre@stockholm.ptloma.edu]
> > Sorry, I have to argue with you here ;)
> > The fact (well, at least my opinion) is that Apple makes it easy to
> > remain completely ignorant of most important things about their
> > computer while still "using" them.
> For five years? Granted, I'm a bit more clueful than the
Well, again, all I can say is that I've seen it happen. More extreme
than the usual case, of course, but it's certainly not impossible.
Though, Dick actually strikes me as more clueful than the last
person that I know who managed it.
> average home computer
> user, but within weeks I was into the guts of my Macs. Not to
> the extent I'm
> into my C64, but that's a less complex system.
Yep. It's not impossible, given the motivation. Most people
are missing that part, though ;)
> At the very least, in five years he could have learned to
> write Macintosh
> correctly.
Could have -- may not have.
> Apple actually has very good utility software. MPW has been
> free for some
> time, for example. And there's the Apple Developer
Hey, I love MPW. It's great. I used it daily when I was writing
Mac code, but it certainly didn't come with the system, and it's
not something that Apple encourages people to have.
> Connection, too, which
> you can browse freely, and oodles of tech notes and explanations.
Indeed. Apple is much friendlier to developers than microsoft,
who I find that I have to deal with recently. :/
> Like everything else in life, you get out of the system what
> you put into it.
Yep, which brings us back to my point that Apple really doesn't
encourage people to learn about their systems. They've positioned
themselves as "the system that you don't have to put so much
into," have they not?
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
> -----Original Message-----
> From: Chris [mailto:mythtech@mac.com]
> Richard... are you being treated for your compulsive liar behavior
> problems? You can not possibly have 5+ years of daily Mac use
> under your
> belt, and show the ignorance of Mac concepts you showed when
> asking about
> the AppleVision monitor and the Performa 630 (or whatever
> model it was
> you bought).
Sorry, I have to argue with you here ;)
The fact (well, at least my opinion) is that Apple makes it easy to
remain completely ignorant of most important things about their
computer while still "using" them.
(I'll define "using" in the above as "doing the same mundane things
that everyone else does with their computer")
I'd say that Apple even encourages user-ignorance by not including
applications that will even let you get at the filesystem with their
O/S -- Finder doesn't count because it won't show desktop (and friends)
at all, and God help you if you want to set file attributes. With
OS X, that's hopefully changed.
That lack of utility software, among other things done by Apple (think
all-in-one, closed box designs) serves to keep users in the dark about
many things.
Now, I can't prove this, but I've personally seen it, so take that
how you will. I've of course heard all of the Mac Zealot spin on
my complaints above and I know all about how some people think that
those things are actually advantages -- like a mouse that has only
one button... to avoid confusion -- , but I don't buy it :)
The thing is that I really do like Apple, and a lot of their hardware
and software, and I hope to see it become a good product (for me, It's
already a fine product for some people) some day.
> Not to mention, you stated back when it all started that you haven't
> seriously touched a computer by Apple in 15 years except to pull the
> power supplies from them.
Ok, that's somewhat of an odd statement in context.
Could it be that he wasn't doing "serious" work on the systems at the
time?
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
> -----Original Message-----
> From: Richard Erlacher [mailto:edick@idcomm.com]
> word. People who've never even heard the word computer
> before can be writing
> letters and reports within 10 minutes of their first contact
> with Windows. In
Are you sure? That's remarkable, but I don't believe it for
a minute. :) I'd be impressed if you've seen this demonstrated,
and more impressed if, after writing the letter, they could ever
find it again.
> the first time I ever encountered Windows, I loaded it up started an
> application and was going within minutes, having read no doc's, having
> compiled no kernel, and having done little else other than
> typing the setup
... but you had seen a computer before, right?
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
> -----Original Message-----
> From: David Woyciesjes [mailto:DAW@yalepress3.unipress.yale.edu]
> ...and now some flashbacks to the DB15 - DE15 naming convention
> thread...Eeek!
I vote that we hereafter call the DE15 "ZQ32," and the Macintosh, to
avoid confusion, can be "Grundey."
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
> From: Chris
>
> >... and just exactly where does one find a precise reference to this
> >convention?
>
> I can't quote a source, but I can say that traditionally, in English, all
> caps refers to an anacronym. And since MAC has something it stands for,
> each and every time you refer to a Macintosh as "MAC" you are in fact
> refering to something other than the Macintosh computer.
>
> And typing it as MacIntosh is just simply wrong. Look at any literature
> by Apple, you will never see it with a capitol I. I think that is a throw
> off from people that are typing it via the name of the fruit, which is
> ALSO wrong, since the name of the fruit is McIntosh (no a).
>
> Its just a pet peeve... I'm not going to really care if you continue to
> type it MAC... but doing so shows a gross ignorance of the platform, and
> really undermines any and all arguments you may have to say for or
> against it. You can't really take someone seriously in discusssions of a
> system if they can't refer to it correctly, as it just shows that they
> have spent so little time dealing with the system, that they clearly
> can't base their statements on anything educated. It doesn't matter if it
> is the Mac, or if it is something else.
>
> -chris
>
...and now some flashbacks to the DB15 - DE15 naming convention
thread...Eeek!
--
--- David A Woyciesjes
--- C & IS Support Specialist
--- Yale University Press
--- mailto:david.woyciesjes@yale.edu
--- (203) 432-0953
--- ICQ # - 905818
Mac OS X 10.1 - Darwin Kernel Version 5
Running since 01/22/2002 without a crash
>but I do have 5+ years of daily
>Macintosh use under my belt.
I can't... I just can't any more. I have been trying to be nice to
Richard despite all the clear flame bait he has been throwing out here.
But with his comment above, I just can't any more.
Richard... are you being treated for your compulsive liar behavior
problems? You can not possibly have 5+ years of daily Mac use under your
belt, and show the ignorance of Mac concepts you showed when asking about
the AppleVision monitor and the Performa 630 (or whatever model it was
you bought).
Not to mention, you stated back when it all started that you haven't
seriously touched a computer by Apple in 15 years except to pull the
power supplies from them.
So unless your 5+ years of daily use are to clean the screen, you must be
full of BS (is that it, you aren't really into computers... you just work
as a janitor at a computer museum, and like to pretend?)
I'm sorry... I just can't do it any more.
-chris
<http://www.mythtech.net>
Christopher Smith said:
> Debian's nice, but it has its share of "political" garbage too, like
> the "GNU/Linux" plastered all over the place, or the fact that they
> insist on keeping "non-free" software separate.
It's not just "garbage". There is a reason for it, that the majority
of the Debian community agrees with, or it wouldn't be done. Plain and
simple. I'm sure you are already aware of the reasons, but reject them.
What you label "garbage" are the very attributes that many Debian members
hold dear.
If you don't like Debian, you are free to either attempt to improve it,
or join the ranks of others who use a different system. It's a personal
choice. Debian is different for a reason.
--
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
I just found some old N* Horizon parts during a cleaning fit. I have the
following:
Lots of hard sector disks
2 64 RAM board.
2 FD controllers
2 Z80B boards
2 FD drives
1 motherboard
I do have the cases (with the PS and such, but only until Thursday, since
they are scheduled to be pitched this week. They aren't in the best of
shape, and they are SO heavy, so I pulled what I thought was worth the
shipping weight cost out of the 2 units. If you do want a case part or a
capacitor, let me know before Thursday so I can have my wife pull the part
off the chopping block.
Anyone interested in S100 parts and hard sector disks? The units were
working last time I used them, but that was 5 years ago. I make no
promises. If there are a few folks, I want to spread the wealth.
Basically, I just don't want the parts to sit in the landfill.
You might want to email me directly, to not clog up the list, and because I
have limited access to email this week while out of the office and lists
will probably get queued until next week.
Jim
Jim Brain, jbrain(a)aegonusa.com
"Researching tomorrow's decisions today."
(319) 369-2070 (work)
SYSTEMS ARCHITECT, ITS, AEGON FINANCIAL PARTNERS
> From: Christopher Smith
>
> > -----Original Message-----
> > From: David Woyciesjes [mailto:DAW@yalepress3.unipress.yale.edu]
>
> > ...and now some flashbacks to the DB15 - DE15 naming convention
> > thread...Eeek!
>
> I vote that we hereafter call the DE15 "ZQ32," and the Macintosh, to
> avoid confusion, can be "Grundey."
>
> Chris
>
huh? Where did you get that from?
--
--- David A Woyciesjes
--- C & IS Support Specialist
--- Yale University Press
--- mailto:david.woyciesjes@yale.edu
--- (203) 432-0953
--- ICQ # - 905818
Mac OS X 10.1 - Darwin Kernel Version 5
Running since 01/22/2002 without a crash
> -----Original Message-----
> From: Chris [mailto:mythtech@mac.com]
> I know you like to make sure your grammer and spelling is
> correct, so I
> figured I should point out the painfully mistake you have been making
> thru all your conversations.
Wow, that's almost as good a quote as the previous one about Dick being
a "pain in the ass..."
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
From: Fred Cisin (XenoSoft) <cisin(a)xenosoft.com>
>Allison is, of course, absolutely correct.
>ST506/412, what is often sloppily called "MFM" provides a set of signals
;) call it the right thing and duh the're baffled. Better to obscure.
>> The problem with EDSI was it sued the same cables as MFM IE: the pair
> ^^^^
>We live in a litigious society.
Let e'm, they still have to prove I'm not isdlexyc. ;)
>> of 26 pin and 34pin. The interfaces however were toally incompatable.
> ^^
>Odd. Mine seem to have 20
Ok, sumptin like that. Blame it on prescription drugs for this @#$%^&!!!
bug.
Allison
On May 6, 8:21, Loboyko Steve wrote:
> I obtained a bunch of 2708 UVEPROM's, and I'd like to
> be able to program them. As you may know, they require
> a different algorithm than the 2716 and on, and three
> voltages, +5, +12, and -5.
>
> I'm building a little board that will program 1/2 (the
> upper or lower) of a 2716 to a 2708 (I can program
> 2716's). But I can't find a description of the
> algorithm that is detailed enough. What I think I know
> is:
>
> 1. The /OE line must be high
> 2. select address and data (start at addr 0)
> 3. bring PGM line from 0 to 27 volts for 1 mSec, then
> drop back to 0 (this seems very strange)
> 4. repeat 100 times per address (not all at once,
> increment the address lines and loop to avoid
> "overheating" a byte.
> 5. drop /OE and verify.
My 1976 Intel databook differs slightly from that.
1. raise /CS (pin 20) to +12V
2. select address and data
3. not less than 10 microsecs later, apply programming pulse to pin 18
4. hold address and data for at least 1 microsec, then move on to next
5. repeat for required number of iterations
6. drop /CS to normal (*without* changing the address) and verify.
The required number of iterations depends on the width of the program
pulse. Minimum pulse width is 0.1ms, max is 1ms. The spec calls for a
total of 100ms programming time per location.
V(IHP) on pin 18 is 25V (min) to 27V (max)
I(IPL) on pin 18 is 3mA
I(DD) is 50mA (typical) to 65mA (max) -- Vdd (+12V +/- 5%) supply current
I(CC) is 6mA (typical) to 10mA (max) -- Vcc ( +5V +/- 5%) supply current
I(BB) is 30mA (typical) to 45mA (max) -- Vbb ( -5V +/- 5%) supply current
Yes, these are almost identical to the read currents.
> 3. bring PGM line from 0 to 27 volts for 1 mSec, then
> drop back to 0 (this seems very strange)
Why does that seem strange? It's the programming pulse, which overcomes
the barrier imposed by the floating gate on the EPROM cell. It needs to be
high enough to overcome the barrier potential, and you don't want address
or data changing while that is possible.
--
Pete Peter Turnbull
Network Manager
University of York
Steve,
That sounds bogus. I'd have to check and I'm not at home.
Memory says that the 2708 was one of the first with the
relatively easy program sequences but the 1mS*100 sounds
strange for that part.
Allison
-----Original Message-----
From: Loboyko Steve <sloboyko(a)yahoo.com>
To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org>
Date: Monday, May 06, 2002 11:38 AM
Subject: 2708 Programming Algorithm?
>I obtained a bunch of 2708 UVEPROM's, and I'd like to
>be able to program them. As you may know, they require
>a different algorithm than the 2716 and on, and three
>voltages, +5, +12, and -5.
>
>I'm building a little board that will program 1/2 (the
>upper or lower) of a 2716 to a 2708 (I can program
>2716's). But I can't find a description of the
>algorithm that is detailed enough. What I think I know
>is:
>
>1. The /OE line must be high
>2. select address and data (start at addr 0)
>3. bring PGM line from 0 to 27 volts for 1 mSec, then
>drop back to 0 (this seems very strange)
>4. repeat 100 times per address (not all at once,
>increment the address lines and loop to avoid
>"overheating" a byte.
>5. drop /OE and verify.
>
>
>Does anybody have an authoritative description, and a
>current requirement for the +5, +12, -5, and
>programming pulse? Thanks.
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Health - your guide to health and wellness
>http://health.yahoo.com
>From: "Jay West" <jwest(a)classiccmp.org>
>
>
>And then posts like this always spread like wildfire as another user or two
>chimes in "Hey, I just joined here and started getting spam too!" Geeze -
>look at the sample size people.
>
Hi Jay
I re-joined here about 1 month ago and haven't seen any
spam other than the noise level of this group.
Dwight
> -----Original Message-----
> From: Allison [mailto:ajp166@bellatlantic.net]
> I disagree. The UCSD version was an excellent teaching tool but
> slower than sludge due to the P-code thing. Later implementations
> namely JRT and Borland were very useful tools.
I'm also of that opinion. I like Pascal, and Modula, and Oberon...
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
> -----Original Message-----
> From: Sellam Ismail [mailto:foo@siconic.com]
: reply ( originalmessage -- newdrivel)
">" . .
> function reply(void)
> {
> > > 20 C MY GRIPE WITH PASCAL WAS THAT IT WAS ALL ONE PROGRAM
> > > 30 C EVERY FORTRAN AFTER II COULD HAVE MODULES DEFINED
> > (* Pascal had adherents early, but it remained a teaching
> > language until the early 1980s. Although Turbo Pascal
> > didn't permit modules, it did provide $INCLUDE files,
> > and depending on the application area, you could often
> > accomplish the same thing using includes. *)
> // What about the "uses" directive? I didn't program in
> Pascal a whole
> // lot but I remember when I did need something like a
> graphics library
> // I "use"d it.
(I remember the directive, but it's been a long time since)
(I've used it.)
"too" " " "Me"
> > > 100 STOP
> > END.
> }
;
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
> >The MAC, for example,
>
> I have been ignoring this, but I just can't any more.
[..spelling lession snipped..]
There is one acceptable situation wherein one would capitalize
the name of the Mac...
WHEN SHOUTING!
;)
> "Douglas H. Quebbeman" wrote:
>
> > My Data Structures prof lamented the fact (by his observation)
> > that most people write Pascal in its FORTRAN subset...
>
> 10 C WHAT SUBSET IS THAT?
(* The subset wherein everything is type in UPPER CASE
and no variable names were longer than six characters. *)
> 20 C MY GRIPE WITH PASCAL WAS THAT IT WAS ALL ONE PROGRAM
> 30 C EVERY FORTRAN AFTER II COULD HAVE MODULES DEFINED
(* Pascal had adherents early, but it remained a teaching
language until the early 1980s. Although Turbo Pascal
didn't permit modules, it did provide $INCLUDE files,
and depending on the application area, you could often
accomplish the same thing using includes. *)
> 40 C .NOR. COULD YOU EVER FIGURE OUT
> 50 C WHEN TO PUT A SEMI-COLEN .OR. .NOT. AT THE END OF A
> 60 C STATEMENT
(* Oh, IIRC, the semicolon is a STATEMENT TERMINATOR in Algol;
in Pascal, it's statement seperator. That should make it clear. *)
> 100 STOP
END.
-Douglas Hurst Quebbeman (DougQ at ixnayamspayIgLou.com) [Call me "Doug"]
Surgically excise the pig-latin from my e-mail address in order to reply
"The large print giveth, and the small print taketh away." -Tom Waits
Not a _great_ score, as I'll have to pay real cash for it, but I
picked up an Altos ACS 8000-2 today, to be delivered the 15th. Yay!
Now I guess I _really_ need to find the CP/M man pages.....
Also grabbed:
Quadra 700 $1
A spare CPU and 2 more drive drawers for the NEC Risc Server I'll be
working on this weekend. Anybody with any info on this one -
a dual-CPU RT-4620-27A5S - is more than welcome to chime in.
(Update: the NEC seems to have cabling/termination issues on
the RAID backplane. Project on hold pending documentation)
An IBM Model 9577-ATG PS/2 - 486DX4/100 w/ Future Domain SCSI adapter,
32M ram, token ring, and 541M SCSI hdd. Which I'll be working
on instead of the NEC box.... $4
Spare Future Domain MCA SCSI, internal cable & 1G drive Free
A box (6) of Model 77 CPU stands Free
A CPU stand for my 7043-140 (I think) Free
2 SCSI cold-swap drive drawers (narrow SCSI) w/Connor drives installed.
No model on the drives yet $5 each
2 Piper 16 MCA sound cards Free
1 Tandon full-height 48tpi 5.25" floppy (TM100?) $.50
1 Mitsumi 5.25" floppy w/full-height black bezel and "EMI cage."
Haven't looked at the model # yet. $.50
1 No-labelled full-height 5.25" floppy. Black bezel, center trap
latch, not a rotating lever. $.10
Doc