Hi!
Since I had to leave my 8/L behind for the next couple months I got
myself a smaller toy for the meantime. It's a PDP-11/03 with LSI-11/2
CPU, 32k MOS memory and a DLV11-J serial interface card.
It also had an EPROM-board and an unknown interface card (40-pin
connector) by a company called "sprecher + schuh" but I removed those
till I figure out what exactly they do.
Some TU58 tapes came with the machine so I guess the EPROMs only contain
some kind of bootloader and the main program came from the tape. I don't
have the tape drive though.
I made some adapter cables for the DLV11 and can talk to the ODT and
execute small programs. To try something bigger I guess I can use
VTserver. I don't have any tape-images to use with VTserver though. I
found hints on the net saying it is possible to create xxdp and RT-11
tape images using simh or E11 or something like that.
I didn't manage to do that myself though. I can boot both systems on the
emulator but E11 crashes whenever I try to access the emulated DECtape
II and simh doesn't seem to support it at all...
Is there an idiot proof howto somewhere on the net that I missed?
Could someone maybe send me some images to try?
Is this the way to go at all or is there a better alternative to get
software into the PDP?
thanks in advance,
Sebastian
> I have 925 manual(s) and control code info somewhere. I'll try to
> get them typed in.
This trip into the attic was well worthwhile. I found several things,
include my Yarmish&Yarmish 370 assembler book, and my Baase Vax
assembler book. I also found the old Prime PL/P manual, the MTS
sysprog and operator docs, etc. Cool!
But, for this thread, the useful info is the Esprit 6310 and Televideo
925 manuals. I've scanned these, and they are available as PDF and
zipped TIFFs, at:
http://yagi.h-net.msu.edu/tvi925_ig.pdfhttp://yagi.h-net.msu.edu/tvi925_ig.ziphttp://yagi.h-net.msu.edu/esprit6310.pdfhttp://yagi.h-net.msu.edu/esprit6310.ziphttp://yagi.h-net.msu.edu/esprit6310errata.pdfhttp://yagi.h-net.msu.edu/esprit6310errata.zip
I did the 6310 stuff because the terminal emulated, among other
things, the 925, and the manual has some control code info which
might prove useful. Esprit was the name later used by Hazeltine.
(I suppose they had to escape from the legacy of a name associated
with using a printing character as a control code. :>)
Al Kossow, if you're listening: these are available for your archive
if you want them. They were built using tumble; the TIFF files were
generated using a Canon iR copier and OmniPage Pro 10. (Did I mention
I'm a non-Windows guy? Grrr.) Unfortunately, the combination doesn't
seem to be able to do anything but 300 dpi.
Hope all of this does someone some good.
De
On 3/31/06, 9000 VAX <vax9000 at gmail.com> wrote:
>
> I forward this email from the linux-vax mailing list. The machine is still
> available waiting to be picked up. It is in Lexington, Ohio, USA. Please
> contack Tom directly. Thank you.
>
> vax, 9000
>
>
> ---------- Forwarded message ----------
> From: Ruckman, Thomas <Thomas.Ruckman at hst.stoneridge.com >
> Date: Mar 9, 2006 8:33 AM
> Subject: [LV] VAX 4000/500A System
> To: linux-vax at pergamentum.com
>
> We have a VAX 4000/500A we have just decommissioned. We are now looking
> for someone to take it off our hands. Would you be interested?
>
>
>
> Tom Ruckman
>
> Systems Administrator
>
> Stoneridge, Inc. Hi-Stat Lexington Div.
>
> Phone: 419-884-4126
>
> E-mail: thomas.ruckman at hst.stoneridge.com
>
>
>
>
>
> ------------------------------
>
> This electronic mail transmission contains confidential information
> intended only for the person(s) named. Any use, distribution, copying or
> disclosure by any other person is strictly prohibited. If you received this
> transmission in error, please send an electronic mail message to
> postmaster at hst.stoneridge.com.
>
> _______________________________________________
> Linux-Vax mailing list
> Linux-Vax at pergamentum.com
> http://www.pergamentum.com/mailman/listinfo/linux-vax
>
>
>
I forward this email from the linux-vax mailing list. The machine is still
available waiting to be picked up. It is in Lexington, Ohio, USA. Please
contack Tom directly. Thank you.
vax, 9000
---------- Forwarded message ----------
From: Ruckman, Thomas <Thomas.Ruckman at hst.stoneridge.com>
Date: Mar 9, 2006 8:33 AM
Subject: [LV] VAX 4000/500A System
To: linux-vax at pergamentum.com
We have a VAX 4000/500A we have just decommissioned. We are now looking
for someone to take it off our hands. Would you be interested?
Tom Ruckman
Systems Administrator
Stoneridge, Inc. Hi-Stat Lexington Div.
Phone: 419-884-4126
E-mail: thomas.ruckman at hst.stoneridge.com
------------------------------
This electronic mail transmission contains confidential information intended
only for the person(s) named. Any use, distribution, copying or disclosure
by any other person is strictly prohibited. If you received this
transmission in error, please send an electronic mail message to
postmaster at hst.stoneridge.com.
_______________________________________________
Linux-Vax mailing list
Linux-Vax at pergamentum.comhttp://www.pergamentum.com/mailman/listinfo/linux-vax
On Mar 31 2006, 18:16, Ethan Dicks wrote:
> Yes... the lowest trap vectors on _all_ PDP-11s are fixed and mean
> something special when you hit them. I don't have a reference right
> in front of me (should be in all of the small computer handbooks),
but
> on a different spot on that page, it mentions this...
>
> Location Contents Opcode Comment
>
> 000004 000006 Bus Error trap
> 000006 000000 halt
> 000010 000012 Reserved
instruction trap
> 000012 000000 halt
> 000024 000026 Power fail trap
> 000026 000000 halt
>
> ... so if you really are halting at 000004, sounds like a bus error.
> Perhaps the code you toggled in can't find an I/O register it's
> expecting.
No, if you have set up the standard trap catcher, and you halt at 4, it
loaded the vector from 0, executed the HALT instruction at 2, and the
PC contains 4 by the time it stops or returns to ODT.
--
Pete Peter Turnbull
Network Manager
University of York
On Mar 30 2006, 19:09, Jay West wrote:
> I enter and run the Line Time Clock Interrupt test from that webpage,
and
> the system halts at location 4. How on earth? Does the 11/45 have
some
> interrupts to specific locations for things like power fail or
something?
> Should a unexpected trap to location 4 mean something special to me?
I just had another thought. Standard traps for errors and software
traps start at 4, and zero is reserved. Normal interrupt vectors for
hardware devices use the area from 100 up to 400. 000000 is reserved,
so if anything uses that as a vector, it's because you have some
hardware fault.
My guess would be something along the lines of a hardware device
generating an interrupt, but apparently giving 000000 as a vector
instead of the true value intended. Unlikely all three of your LTCs
would do the same thing. Could be the CPU reading zeros due to a fault
in the interrupt logic, as Tony suggested.
--
Pete Peter Turnbull
Network Manager
University of York
On Mar 30 2006, 19:09, Jay West wrote:
> I enter and run the Line Time Clock Interrupt test from that webpage,
and
> the system halts at location 4. How on earth? Does the 11/45 have
some
> interrupts to specific locations for things like power fail or
something?
> Should a unexpected trap to location 4 mean something special to me?
You mean the PC contains 4 when it halts? The LTC interrupt test you
ran sets each of the vectors in low memory to contain two words: when
the processor uses the vector, the first word is loaded into the PC.
The LTC test fills each vector with a pointer to the second word of
the vector, and put a halt instruction in the second word, so the
reason your PC contains 4 when it halts is that it tried to use the
vector at zero. The PC gets loaded with 000002 from location zero, and
the processor executes the HALT instruction at 000002. By the time you
see it, the PC has been autoincrememnted and contains 000004.
> I also wanted to run the trap catcher program from that website to
help test
> software traps & interrupts. However, I don't understand part of what
they
> say to do. I can certainly enter the program, but then they say to
deposit
> 777 into loc 1000. That would overwrite the first word of the
program. Not
> sure what they want done there or I'd run that to see what it comes
up with.
Standard stuff. You're supposed to enter _and_execute_ the little
program that fills memory with zeros -- that fills the vectors like the
LTC test. After it's run, the vectors are set up, and *then* you
replace the first instruction, at 001000, with 000777, which is a
branch-to-self instruction. When you run *that* the processor will run
in a tight loop until an interrupt or trap makes it jump through one of
the vectors. If you use the first, shorter program, all the vectors
contain 000000, and 000000 contains a halt instruction, so the
branch-to-self halts at 000000 (so the PC will contain 000002) when it
gets any interrupt or trap.
If you use the second test instead of the first, each vector contains a
pointer to its own second word, so it halts with the PC pointing to
4+the vector it used.
--
Pete Peter Turnbull
Network Manager
University of York
Richard <legalize at xmission.com> wrote:
>In article <447524F844B59D48B8F7AE7F560935EE06C20047 at
OVL-EXBE01.ocevenlo.oce.net>,
> "Gooijen, Henk" <henk.gooijen at oce.com> writes:
>
>> Perhaps I should not type this message, and go to bed instead ...
>> I am not going to sell my book, if that is what you suggest, Richard.
>> I can scan or make a paper copy, but I will keep the original book.
>
>Sorry, I should have been more explicit... I meant that if the
>original poster who is looking for the book has an ISBN then they
>could find it through the Usual Suspects.
The ISBN is available through the usual suspects - simply lookup at
Amazon, but I wrote I haven't
seen it pop up for used-sale for a while. I also do not expect Henk to
sell it to me, BTW; copies or scans would be perfect for me.
>Henk, I thought you said you didn't want to copy/scan it since that
>would impose heavy wear on the spine?
Now, I remember these paperbooks were not too thick (I once had
Emmerichs Tiny Assembler and MONDEB from that class - unfortunately got
lost - TinyAsm at least can be copied from old 1977 Byte issues), so
I'am not sure whether it will wear out more than by simply reading the
book. Unless you have
a multi-page scanner where you'd have to destroy the spine.
Regards
Holger
Correct, I prefer to keep my books in good shape.
But keeping a book on the shelf is not why they are printed.
So, if I can be of help, the book will be *used* instead of
just collecting dust.
- Henk.
> -----Original Message-----
> From: cctalk-bounces at classiccmp.org
> [mailto:cctalk-bounces at classiccmp.org] On Behalf Of Richard
> Sent: vrijdag 31 maart 2006 0:23
> To: General Discussion: On-Topic and Off-Topic Posts
> Subject: Re: RA6800ML?
>
>
> In article
> <447524F844B59D48B8F7AE7F560935EE06C20047 at OVL-EXBE01.ocevenlo.
oce.net>,
> "Gooijen, Henk" <henk.gooijen at oce.com> writes:
>
> > Perhaps I should not type this message, and go to bed instead ...
> > I am not going to sell my book, if that is what you
> suggest, Richard.
> > I can scan or make a paper copy, but I will keep the original book.
>
> Sorry, I should have been more explicit... I meant that if
> the original poster who is looking for the book has an ISBN
> then they could find it through the Usual Suspects.
>
> Henk, I thought you said you didn't want to copy/scan it
> since that would impose heavy wear on the spine?
> --
> "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
> <http://www.xmission.com/~legalize/book/>
> Pilgrimage: Utah's annual demoparty
> <http://pilgrimage.scene.org>
>
>
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
