Forth and PostScript are quite similar but I wouldn't
<say that LISP was a stack based language. It uses stacks
<but most languages use stacks. In Forth, you have direct
<control of two stacks as necessary for the language.
First to me stack languages are the post-fixed non register
variable oriented ones that are very unlike Pascal, C or Basic.
< Forth has the advantage that action is read
<left to right or "Do-it As You See It". LISP
<has the ability to concatenate several of similar
<operations like (+ ).
I know Forth by way of postscript as they are very similar if you pull
the graphic operators out of postscript. Lisp, I doubt I've seen it.
<LISP has the advantage over
<Forth in that all parameters are specific in the
This is lost one me as lisp is largely unknown.
Allison
Hello all,
I just obtained a box of goodies, and these Intersil ICL7601CPD 14 pin
ceramic dips were in the lot. I can't seem to locate any information on
them. Can anyone give me a clue?
BTW, also in the box were a bunch of common NOS (mid 1970s era) TTL, 2 Zilog
Z-80s, and a National Semi DT1050 Digitalker Standard Vocabulary Kit still
in the original NS box in an antistat bag, along with the DT1050 docs
Thanks,
Bill
whdawson(a)mlynk.com
In a message dated 2/27/2000 8:16:47 AM Pacific Standard Time,
kyrrin(a)bluefeathertech.com writes:
> The annual Mike and Key Amateur Radio Club swap meet is coming up again at
> the Western Washington (Puyallup) Fairgrounds on Saturday, March 11, from
> 09:00-15:00 Pacific time. Parking is free, admission is $6.00 with kids
> under 16 free when accompanied by an adult.
>
One great swapmeet. Very large. Get there early. Or better yet get a table.
Paxton
Aaron:
I happen to like the combination of Acrobat Exchange 3.01 and my HP Scan
Jet with document feeder. It's not blazingly fast, but it works. I have it c
onnected to my AHA2940UW controller.
Rich
[ Rich Cini
[ ClubWin!/CW1
[ MCP Windows 95/Windows Networking
[ Collector of "classic" computers
[ http://highgate.comm.sfu.ca/~rcini/classiccmp/
<================ reply separator =================>
On February 28, Shawn T. Rutledge wrote:
> Do they still have performance advantages over less specialized systems?
> What kind of hardware modifications would optimize execution of Lisp?
Hmm...what processor instructions might one create to deal with a
language with more parens than actual code? ;)
-Dave McGuire
On February 28, Shawn T. Rutledge wrote:
> > Hmm...what processor instructions might one create to deal with a
> > language with more parens than actual code? ;)
>
> I doubt that is an issue... I've never written a lisp interpreter (wish
> I'd had one of those CS classes where they do that) but I'd guess the
> ASCII source code gets tokenized into some kind of tree structure which
> is probably interpreted by doing a tree traversal, so the parens are all
> gone by that point (they just tell it how to build the tree). But I can't
> think of any hardware optimizations that help with trees, other than the
> concept of a "stack", which is hardly a new one. Evidently there are some
> though.
'Twas a joke, man...
-Dave McGuire
Greetings;
I've finally gotten (again) my HP2100's to the point where I can run real
diagnostics. The memory architecture doesn't appear all that different from
a PDP-8E at the board level anyways (there's a memory controller board, a
load board, an ID board, an XY driver board, and the core array).
My question is this: I heard from a reseller that one should run the memory
diagnostics in loop mode for 48 to 72 hours before assuming the memory
subsystem is a good one. Bear in mind that when the diagnostic is run
without loop mode, it only takes about 8 minutes to complete. This would
mean 360 passes being made in 48 hours. From others experience, is 48 hours
really necessary? I mean, isn't a good 4 hours enough to test for heat
problems, etc? Unlike the reseller, I don't need to be 100% positive a board
is perfect before sending it to a customer, I just want to be reasonably
sure I can remove the memory system from the list of possible trouble spots
as I go on to test other things. I was hoping that there would be nothing
about the HP core subsystem that would require that long of burn in, and
thus the experience others have had with other systems might be valid
experience.
So how long do YOU loop memory diags to test a core memory system to be
reasonably sane?
Thanks in advance!
Jay West
Yes, I consider this on-topic because two of my intranet's servers will be
MicroVAX III's. ;-)
After much fencing with my local telco over loop lengths, and a snail-mail
letter asking them why their competition (AT&T and Covad) were willing to
do what they were not (at the time), I have a due date for my DSL
connection! It'll be (minimum) 256K up/downstream guaranteed, and those
rates could fluctuate a bit depending on the usual variables.
This means that, shortly thereafter, I'll be taking full control of my own
domain, including all servers, and (finally!) starting to set up what I
hope will be a very useful FTP and web site for anyone who futzes with
"classic" computing or electronic equipment (ham radio stuff included).
This won't happen overnight! It's going to take some time to build up the
thing the way I want it to be.
With that in mind, I have a request: Those of you who are fluent with
setting up servers (Unix/NetBSD-based) on a small intranet, and tying said
intranet through a Livingston IRX/Firewall router to the outside world, AND
that would be willing to help me keep from making too many mistakes in
setting things up, please raise your hand and let me know if I can contact
you periodically for help and advice.
FWIW, I plan to have: Two DNS, two mail (for redundancy/fault tolerance),
single news/FTP box combined, and a single web server.
My current setup is on one of the InterNIC-reserved Class C net spaces:
192.168.42.0 - 192.168.42.254. The DSL "modem" (a misnomer if I ever saw
one) will be a Cisco 675. Its Ethernet port will tie to one side of the
Livingston router. Said router will provide firewalling and
packet-filtering capabilities that the Cisco lacks.
The Livingston will also provide NAT services to translate the five static
IPs I get from USWest onto the private network side.
I plan to use my own pair of DNS servers as primary and secondary hosts
for my domain, with USWest acting as tertiary. The DNS boxes will be old
Sun IPC's. They've already been configured.
Thanks much!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Bruce Lane, Owner and head honcho, Blue Feather Technologies
http://www.bluefeathertech.com // E-mail: kyrrin(a)bluefeathertech.com
Amateur Radio: WD6EOS since Dec. '77
"Our science can only describe an object, event, or living thing in our
own human terms. It cannot, in any way, define any of them..."
I just talked to a guy that worked (in an executive type position) years ago
at a company called MeasureX. According to him, MeasureX bought a lot of
HP2100's for their process control stuff. They got tired of the problems
associated with the cpu card set consisting of 8 cards (9 with DMA - er -
DCPC in HP lingo) and the problems with the wire-wrapped backplanes.
They redesigned the 2100 cpu to fit on a single card - one PCB - no
wirewrapping, all etched traces. They sold this redesigned cpu (actually
just a relayout of the circuits) back to HP, and HP dubbed it the 21MX
(where the MX is for MeasureX). This was also the origin of the "build your
own modular HP", called the K series where you pick and choose cpu boards,
slot assemblies, etc. at time of order.
He also mentioned that HP used to charge (at the time) $1400 to "clean the
backplane". MeasureX found out that the CE's were just taking out all the
cards and taking the unit to a car wash and spraying them with pressured
water and then sun-drying them in the back of a closed up station wagon in
the summer. So---- MeasureX just started doing it themselves and save a huge
sum of money :)
I found these tidbits interesting!
Regards,
Jay West
