I'm looking for the following.
The cable that goes between the DEC VT1200 (looks like an N connector)
and their monochrome video monitors like a vt262 and a DEC VSXXX-AA
mouse.
I've got a working VT1200 minus mouse and video cable.
I was going to cobble one up with some RG6 and a BNC connector and
an N connector (if that's really an N connector) but I'd really rather
find the right cable and spend more time enjoying the toy rather than
fixing it.
Bill
--
d|i|g|i|t|a|l had it THEN. Don't you wish you could still buy it now!
bpechter@shell.monmouth.com|pechter@ureach.com
[For once I did not crosspost and now PDP-8 Lovers list
is not working right, so it goes to classiccmp again.]
Hi,
after dishwashing I reassembled my "new" PDP8/A and it's
working again, after David Gesswein hinted me to the
programmers console quick reference, I was able to enter
my first manually assembled programs and it's indeed working!
I must say that I never thought I would ever manually
assemble a machine program, but with the PDP8 it's
remarkably easy.
My first PDP-8 program is a memory test, and I was glad I
did it because I found a problem. My test goes through all
memory fields and writes into each cell its address in the
field. Then it reads that address out of each field again
and so finds problems.
I have 3 16k words boards and one 8k word board. Two of
the 16k boards are good but both seem to want to play the
role of the lower fields 0 to 3. The third 16k board
plays the high fields 4 to 7, but it has a systematic
error masking out bits 6 and 7. All data X I write into
it is read as X AND 7717. The 8k board has a similar bit
mask error, it's mask is 6777. Is this a fatal problem
or can one fix it by cleaning some contacts or redo some
crummy soldering? I assume the core mats are all fine,
because they would not just lose a few columns of data
bits, right? I also assume that others had to deal with
similar issues, because apparently such errors are not
uncommon. What's the trick?
(I did swap them into various backplane slots, just to
make sure it's not just a gap in the data bus lines.
... BTW, does the OMNIBUS need something like grant
continuity cards for intermittent empty slots?)
thanks for your advice,
-Gunther
PS, just to show off (and to save this stuff from my hand-
written notes) here's my program. It's ugly spaghetti code
with quirks because I had to modify it at the console
(remember: never start coding without having done your
work on paper :-) I now understand much better :-)
I'm not sure I have the symbolic assembly language right,
I may use some things (like the Z modifier for zero-page
addressing) that is not standard but helps me code right.
0020 0000 LOC , 0 TESTED MEMORY LOCATION
0021 0000 FLD , 0 TESTED FIELD NUMBER
WRITE LOOP
0200 7200 CLA A = 0
0201 1254 TAD FLDINI A += FLDINI
0202 3021 DCA Z FLD FLD = A; A = 0
0203 1257 TAD LOCINI A += LOCINI
0204 3020 DCA Z LOC LOC = A; A = 0
0205 1020 WRLOOP, TAD Z LOC A += LOC
0206 3420 DCA IZ LOC *LOC = A; A = 0
0207 2020 ISZ Z LOC IF(++LOC == 0)
0210 5205 JMP WRLOOP ELSE GOTO WRLOOP
0211 4234 IFRET, JMS INCFLD THEN A = INCFLD()
0212 7450 SNA IF(A != 0)
0213 5205 JMP WRLOOP ELSE GOTO WRLOOP
/*FALLTHROUGH*/
READ/CHECK LOOP
0214 7200 CLA A = 0
0215 1254 TAD FLDINI A += FLDINI
0216 3021 DCA Z FLD FLD = A; A = 0
0217 1257 TAD LOCINI A += LOCINI
0220 3020 DCA Z LOC LOC = A; A = 0
0221 1020 RDLOOP, TAD Z LOC A += LOC
0222 7041 CIA A = -A
0223 1420 TAD IZ LOC A += *LOC
0224 7440 SZA IF(A != 0)
0225 7402 ERROR, HLT ELSE HALT
0226 2020 ISZ Z LOC THEN IF(++LOC == 0)
0227 5221 JMP RDLOOP ELSE GOTO RDLOOP
0230 4234 JMS INCFLD THEN A = INCFLD()
0231 7450 SNA IF(A != 0)
0232 5221 JMP RDLOOP ELSE GOTO RDLOOP
0233 7402 OK, HLT THEN HALT
INCREASE DATA FIELD SUBROUTINE
returns 0 if success
resets field to 0 and returns -1 if overflow
0234 0000 INCFLD, 0
0235 2021 ISZ Z FLD IF(++FLD == 0)
0236 7300 CLA CLL ELSE { A = 0; L = 0 }
0237 1021 TAD Z FLD THEN A += FLD
0240 7047 CIA A = -A
0241 1255 TAD FLDMAX A += FLDMAX
0242 7510 SPA IF(A >= 0)
0243 5261 JMP RSTFLD ELSE GOTO RSTFLD
0244 7300 CLA CLL THEN { A = 0; L = 0 }
0245 1021 TAD Z FLD A += FLD
0246 7006 RAL 2 A <<= 2
0247 7004 RAL A <<= 1
0250 1260 TAD CDFTMP A += CDFTMP
0251 3252 DCA CDFDO CDFDO = A; A = 0
0252 0000 CDFDO, 0
0253 5634 JMP I INCFLD RETURN
INITIALIZATION VALUES
0254 0000 FLDINI, 0
0255 0007 FLDMAX, 7
0256
0257 0300 LOCINI, 0300
0260 6201 CDFTMP, CDF
RESET THE MEMORY FIELD BACK TO 0
assert A == -1
0261 7000 RSTFLD, NOP
0262 1254 TAD FLDINI A += FLDINI
0263 3021 DCA Z FLD FLD = A; A = 0
0264 4234 JMS INCFLD A = INCFLD()
0265 7040 CMA A ~= A
0266 5212 JMP IFRET GOTO IFRET
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
I thought I'd give folks a chance on these before I took them back. I
bought them labelled "SO-DIMMs for older Dell Laptops" - apparently, my
laptop is too old. What I have in my Latitude LM are what I think of
as SO-DIMMs - 36-pins, double-sided, no keying groove. What I have
appears to be for a Latitude CP machine. It _does_ have a keying
groove and a lot more pins... more than double.
One of these is new in the package, one has been opened (before I
got them). The part numbers on the DRAMs is D42S65165G5-A60-7JF.
The CDW part number is 118982, the Visiontek part number appears
to be 54073.0
If anyone is interested in a pair of 32Mb SO-DIMMs, contact me
off-list at ethan_dicks(a)yahoo.com. If there's no interest, I can
take them back, but they'll hit me for a 10% restocking fee.
-ethan
__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
> -----Original Message-----
> From: Doc [mailto:doc@mdrconsult.com]
> Either have a key or "mknod /dev/big_screwdriver" and be handy with a
> soldering iron. The key not only locks the cabinet, but controls the
> boot sequence. You need it.
I imagine one could fit a switch in place of the keylock, if you really
want.
> Some things you will want to consider.
> The 320 & 32h need proprietary serial cables. I can supply pinouts.
> They, as well as a few others, also have a proprietary external SCSI
> interface. It looks like a 68-pin connector, but it's not.
Reminds me of the interface on the MicroVAX 3100 machines, which also looks
like a 68-pin connector, and it is(!), but it's a SCSI-1 interface.
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
On December 26, Christopher Smith wrote:
> > I think this is less of a pro-Linux issue and more of a
> > use-the-right-tool-for-the-job issue, which sure as hell ain't Windows
> > if you want to put stuff on the web.
>
> Then again, when is windows the right tool for the job? (Unless you want to
> orchestrate a cruel practical joke...)
Hmm. It's the right tool if you want to put on a tie, be a "team
player", use the word "key" a lot (and not meaning a piece of metal
with "XX2247" stamped on it), and pretend to be indespensible while
collecting a huge salary for little or no real work. ;)
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
> -----Original Message-----
> From: Dave McGuire [mailto:mcguire@neurotica.com]
> I think this is less of a pro-Linux issue and more of a
> use-the-right-tool-for-the-job issue, which sure as hell ain't Windows
> if you want to put stuff on the web.
Then again, when is windows the right tool for the job? (Unless you want to
orchestrate a cruel practical joke...)
Regards,
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: UberTechnoid(a)Home.com [mailto:UberTechnoid@Home.com]
> Help does nothing really useful. What I'd like to know for
> instance, is
> how do I set the vax to do an unattended boot. It has been
> stuck at a two
> stage boot since before I even got an OS on it. It powers
> on, self-tests,
> boots to a second-level CLI, I type C for Continue and there we go.
Actually that's probably a problem with your default boot options. Those
are AFAIK unique depending on the system you're booting, and as such ought
to be handled in the O/S documentation.
> A prom manual would tell me how to get rid of the second-level cli.
See above -- I'm not so sure. :)
All else aside, though, you may consider checking the values of all the
built-in variables for obvious problems.
Regards,
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: UberTechnoid(a)Home.com [mailto:UberTechnoid@Home.com]
> Good luck! I can't even find a PROM command manual for the
> thing. Come
> to mention it, DOES anyone have a prom command listing for
> the vs400/60
> and/or the Sparcstation 4/330 (sun4)?
I have a Sun SBUS development kit which contains (among other things) a
quick-reference card which lists most OpenBoot monitor commands, and a full
(realatively large, and I'd rather not copy the whole deal if I can help it.
:) forth-like-monitor-language reference manual.
As for the VAX, I have no reference, but the 4000s were new enough to
support the "help" command. :)
Regards,
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: James L. Rice [mailto:jrice@texoma.net]
> You are lucky. I changed from Wife 1.0 who hated technology and
> computers to Wife 2.0 who is an avid user (even if I can't
> get her off
> M$ products) and not only tolerates my collection but encourages it.
> She is the contributer of the second cube as well as the NeXT Color
> Printer. The change over from version 1.0 to 2.0 was very expensive
> ...in fact so expensive that I would hesitate to do it again.
On the other hand, your current wife device seems very well-behaved, so I'd
not see why you should change again. ;) It's difficult to find one that
will maintain stability with even a nominally normal relationship signal at
any rate, and you're better off sticking with what works.
It helps, of course, if you can handle the PayAttentionToME signals in
real-time.
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
Did anyone snag this?? (see below...). I haven't caught up on my digest
reading ....
This is about 1/2 hour from me, straight shot down Route 2. My wife would
divorce me if I took it, but I'd LOVE to help rescue it for someone else...
And I own a pickup w/ a cover...
Rich B.
-----------------------------
From: "Thomas R. Fitch" <tfitch(a)esleeck.com>
To: "'mrbill(a)pdp11.org'" <mrbill(a)pdp11.org>
Subject: PDP11
Date: Fri, 21 Dec 2001 15:19:23 -0500
Mr. Bill,
I have a PDP11 in two towers, with 2 crt's and keyboards, and a keyboard
printer. All in excellent condition. I also have all of the original
documentation. This product is available for pickup from our Turners
Falls, MA location. Please contact me if you have any interest.
Tom Fitch, Treasurer
Esleeck Manufacturing Company
36 Canal Road
Turners Falls, MA 01376
(413) 863-4326 ext 206
