> From: "Rick Bensene" <rickb at bensene.com>
>
> Earlier controls had RS-232 ports. I wrote a system on a PC running
> FreeBSD Linux using Perl (a very early version) that would send and
> receive programs to all of the controls in the shop over RS-232. I used
> a SCSI terminal server box from Central Data that hooked up to the PC
> over a SCSI channel, and provided 16 RS-232 serial ports that went out
> to all of the machines. Amazingly enough, this thing is still in
> service (in a shop environment) after over 15 years, providing an easy
> way to load programs on some of the older controls.
I wrote a similar program in 1979 to do a similar job with an Apple ][ europlus (to a Bridgeport Series 1). It was written in my own high level assembler (for the 6502) and worked with only one machine at a time and included Apple's word processor integrated in (by disassembly, converting to high level and inclusion in the source with suitable links) and we sold a normal version with it with permission from Apple.We also had a program which emulated a vertical mill and drew the programmed path on screen or on a pen plotter. I know they were in use about 20 years later but probably all dead by now. We also did a version which allowed operators to program a Heidenheim 131 or 145(?) controller on the Apple 2 without tying up the real machine which cost about 30 times as much as an Apple 2.
Will writes:
> What machine does the DEC 54-21139 SIMM go with? VAXstation or Alpha?
> I have quite a pile - available cheap!
It goes in at least some of the DEC 3000 Alphastations. Which themselves
could use commodity PC-clone memory with parity (at least for the 8MB SIMM's,
there's some special sensing resistor in the DEC 32MB SIMM's)
so they would probably work in anything needing 8MB Parity SIMMs.
Geeze, I haven't thought about DEC 3000 memory in a decade. IIRC
the Alphastations shipped with 8MB SIMM's and these often were pulled
and replaced with 32MB SIMM's.
Tim.
Chuck writes:
> What we no longer have is convenient inexpensive storage for modest
> amounts of information, say a megabyte or two? Ideally, such a
> medium would be read-mostly or write-once and a handful of them would
> buy a cup of coffee at your local watering hole.
When I got started in computing, a RK05 pack was circa $200 and
a 8" floppy was circa $5. A researcher or student might have
had a personal RK05 or two and a box of floppies.
Today for the non-inflation-amount of money
I get a couple of Terabyte portable drives for $200 and a cheapie
USB keychain for $5. And they're used for similar purposes (despite
a factor of 5 or more orders of magnuted in byte capacity) as the 30-year
old equivalents. I see things really staying the same in price
and in usage more than changing.
What's really cool, is both the USB keychain and the terabyte
portable drive use the same cheap and ubiquitous low-end interface.
That is an improvement over 30 years ago (don't take that as a slam
against the Unibus, if I wanted to insult the Unibus I would call
it "cheap and ubiquitous" 30 years ago!)
Tim.
>
> From: "Jonas Otter" <jonas at otter.se>
> The architecture has so-called display registers, each of which pointed
> to a stack frame for a lexicographical level in the code, i.e. the
> procedure call level. Data is addressed as an address couple consisting
> of a display register number and an offset, stored in a so-called
> Indirect Reference Word (IRW). Data outside of the stack can be
> addressed by means of descriptors. Data in another program's stack is
> addressed by means of Stuffed Indirect Reference Words (SIRW), which
> include a stack number and an offset. The operating system keeps track
> of individual program stacks by means of a tree of pointers to job
> stacks. Also, to keep track of the procedure calling and return linkage,
> Mark Stack Control Words (MSCW) are created whenever a procedure is
> called. The Display Registers point to the MSCWs.
>
Yes, that all sounds familiar.
Do you recall the sizes?
> All this is designed to support block-structured high level languages, in
> fact all the operating system software is (was) written in various ALGOL
> dialects.
>
My favorite dialect was NEWP. I particularly liked the UNSAFE directive.
I worked for Burroughs from just before the name change to Unisys
(summer '86) to spring '89, my first job out of college. I worked on A
Series, V Series, B1000, BTOS and DOS stuff while I was there. At
school, I used BSD Unix on VAX and DEC-20, so the Burroughs stuff was
really different (from stack machines to two-wire direct, poll/select
terminals) and fun to play with and learn.
alan
A successful build of GopherVR on Mac OS X:
http://www.floodgap.com/iv/632
As you can see, this is the famous unfinished "virtual reality" gopher
client. And it really works!
I just wanted to share the joy. It doesn't do much more than this, and
required some unholy hacking to get it this far, but I'm hoping to release
source soon. For those who want to play with GopherVR on classic Mac OS
now, you can get it from
gopher://gopher.floodgap.com/1/gopher/clients/mac/
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- If it's tourist season, why can't we shoot them? -- Justice Gustine --------
Hello. I am searching for these documents or books related with Systems
Analysis:
* Study Organization Plan, IBM, (Form C20-8075), 1961
* Time Automated Grid System, IBM, (Form GY 20-0358), 1971
* A Study Guide for Accurately Defined Systems, NCR, 1968
Regards
Sergio
DM74LS 244WM
Octal tri-state buffers/line drivers/line receivers
20 pin chip, surface mount.
I need one for an 8 bit ISA SCSI card so the ROM I installed works.
Looking over my junk boards I dont see any I can snag.
If you have one let me know.