On Dec 21 2004, 22:39, Gooijen H wrote:
> > Pete wrote:
> > ... when my department gets its big scanner, probably in January
> > (Sorry, Henk, it's not an Oce).
>
> I hate to go off-topic for a moment, but I can't resist here,
> I am very loyal / pro-minded to my employer :~) <shameless plug>
> Does your scanner do 55 pages Letter or A4 size (1-sided per minute,
> or 27 ditto (2-sided) automatically at 600 DPI ?
No, I don't know the actual figures, but the one we had on eval seemed,
subjectively, about 2/3 or maybe 3/4 of that speed. It's an HP, but I
can't remember the model number either. You have to understand that it
was a huge battle getting any scanner at all in our department!
> And besides, the software that moves the scanner carriage was
entirely
> written by me! For the mechanics under us: the carriage accelerates
> to approx 1 m/s in 33 msec!
> Don't ask what happened after I made a mistake in the path
calculation
> software and tried to run that code on the engineering prototype (way
> back in 1994) ...! I was not the only one unhappy with the results!!
When I worked in CompSci, we got a big fast Oce scanner/copier, about
1997, I think. One of those that collects the output internally,
safely away from fingers, because the paper goes fast enough to cut
fingers off if they're not out of the way. I remember the first print
job I sent it, a large A4 manual printed from a PDF file. I walked the
length of the corridor to the print room, saw no output, and was
slightly surprised -- for about 3 seconds, when a *large* block of
paper was neatly deposited on the output tray.
> LOL, this (..) is typical "Pete humor".
(Yeah, I must do something about those () keys as well).
--
Pete Peter Turnbull
Network Manager
University of York
Hi
From the looks of the back, it is one of the battery backed
units as well. I suspect that the front panel lights come
on but nothing works, like my unit did until I learned
the resistor in the connector trick.
Dwight
>From: "Joe R." <rigdonj(a)cfl.rr.com>
>
> He certainly hasn't found your website, has he Al? At least he's not
>claiming that it's "complete and fully functional" like the seller of that
>recent F-series 1000 did.
>
> Joe
>
>
>
>At 08:59 AM 12/21/04 -0800, Al wrote:
>>
>>http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&category=1247&item=5150357271
>>
>>"A shroud of mystery hangs over the history and specification of this
>classic computer system."
>>
>>--
>>
>>Good thing he wasn't trying to sell something was really WAS obscure.
>>
>>
>
>
> Pete wrote:
> ... when my department gets its big scanner, probably in January
> (Sorry, Henk, it's not an Oce).
I hate to go off-topic for a moment, but I can't resist here,
I am very loyal / pro-minded to my employer :~) <shameless plug>
Does your scanner do 55 pages Letter or A4 size (1-sided per minute,
or 27 ditto (2-sided) automatically at 600 DPI ?
And besides, the software that moves the scanner carriage was entirely
written by me! For the mechanics under us: the carriage accelerates
to approx 1 m/s in 33 msec!
Don't ask what happened after I made a mistake in the path calculation
software and tried to run that code on the engineering prototype (way
back in 1994) ...! I was not the only one unhappy with the results!!
> Sorry about the spelling and dropped characters in my last post, BTW.
> Must fix this keyboard (right after I fix these fingers).
LOL, this (..) is typical "Pete humor".
- Henk.
Hi All,
Can anyone id this cable?
<http://www.classiccmp.org/hp/cable/Mvc-002f.jpg> It looks DEC-ish but it
has fewer pins (24) than the DEC HP-IB cables. I keep finding these but
I've never found them on the equipment that they're made for. Right now I
have four of them, 2 are made from Belden cables, one for a HP cable and
the other doesn't have a manufactures name.
Thanks and Happy Holidays,
Joe
Ok, I checked.
I am that fast back because I remembered exactly where to look :~)
I have one before me on the desk.
It has the following description:
PRODUCT CODE: AC-8528C-MC
PRODUCT NAME: CZDLDC0 DL11-W DIAG
DATE CREATED: MARCH 1978
MAINTAINER : DIAGNOSTIC ENGINEERING
AUTHOR : DAN CASALETTO
Don't be fooled, it is printed on Letter format, 2-sided!
Only the first 6 pages are one page per side, all the following
pages are scaled: 2 pages per side, thus 4 pages (or images) per sheet.
The first 6 pages describe the load and start procedure, the switch
bits to get special functions, etc. just as described on my site.
The scaled pages contain the assembly source (output) listing ...
they are numbered from "seq 0012"up to "seq 0103", and I checked,
the numbering is not octal but decimal!
If there is interest I could start to scan these to 600 dpi PDF files,
but I have a stack of approx 20-30 cm high, so that will be a lot MB's!
I could start making a list of what's in the box. Xmas is coming :~)
- Henk.
-----Original Message-----
From: cctalk-bounces(a)classiccmp.org
To: info-pdp11(a)village.org; General Discussion: On-Topic and Off-Topic Posts
Sent: 21-12-2004 17:27
Subject: Old Unibus PDP-11 XXDP diagnostics
Does anyone have any info/documentation on the XXDP diagnostics for
older PDP-11 systems and peripherals? I'm looking in particular for the
11/40 (11/35), RK05, DZ11, RL02, MM11 core memory, RX01, RL01
diagnostics. I have found some info on Henk's site, but would like to
know if anyone has a comprehensive list and hints on how to run these,
what the output means, how to answer the prompts, etc.
I have created RL02 packs with XXDP 2.5 and XXDP 2.2 and I can boot and
run stuff from these packs. It appears that the 11/40 diagnostics are
on XXDP 2.2, but not on XXDP 2.5. I have an old 1976 DEC field rep
troubleshooting guide that refers to various MAINDECs, which seem to
have been the diagnostics prior to XXDP. Is there a list somewhere
showing what the XXDP equivalents of the old MAINDECs are?
Any help would be appreciated. I want to exercise my 11/40 and attached
peripherals and see if any subtle gremlins are lurking anywhere within.
Everything appears to be working perfectly with the exception of one of
my three RK05 drives that I knew was problematic.
Ashley
Ok, I have looked around in the documents for Angelfire, at other sites
and I am still having problems getting this..
<a href="download/RockScissorPaper.dmg">RockScissorPaper</a>
trys to download RockScissorsPaper.HTML when I click it (the html I
actually get
is angelfire's 404 page)
phhht.
What is the "right" way to make a file available on my web page?
I could go and check ... AFAICR I also have a stack of listings that
belong to XXDP programs. When a stop/halt occurs at an address, you
read the listing of the XXDP diagnostic program to learn near the
address where the stop occurred for what reason that stop occurred.
I'll report back later!
- Henk.
-----Original Message-----
From: cctalk-bounces(a)classiccmp.org
To: info-pdp11(a)village.org; General Discussion: On-Topic and Off-Topic Posts
Sent: 21-12-2004 17:27
Subject: Old Unibus PDP-11 XXDP diagnostics
Does anyone have any info/documentation on the XXDP diagnostics for
older PDP-11 systems and peripherals? I'm looking in particular for the
11/40 (11/35), RK05, DZ11, RL02, MM11 core memory, RX01, RL01
diagnostics. I have found some info on Henk's site, but would like to
know if anyone has a comprehensive list and hints on how to run these,
what the output means, how to answer the prompts, etc.
I have created RL02 packs with XXDP 2.5 and XXDP 2.2 and I can boot and
run stuff from these packs. It appears that the 11/40 diagnostics are
on XXDP 2.2, but not on XXDP 2.5. I have an old 1976 DEC field rep
troubleshooting guide that refers to various MAINDECs, which seem to
have been the diagnostics prior to XXDP. Is there a list somewhere
showing what the XXDP equivalents of the old MAINDECs are?
Any help would be appreciated. I want to exercise my 11/40 and attached
peripherals and see if any subtle gremlins are lurking anywhere within.
Everything appears to be working perfectly with the exception of one of
my three RK05 drives that I knew was problematic.
Ashley
On Dec 21 2004, 9:14, Guy Sotomayor wrote:
> On Tue, 2004-12-21 at 08:27, Ashley Carder wrote:
> > Does anyone have any info/documentation on the XXDP diagnostics for
> > older PDP-11 systems and peripherals? I'm looking in particular for
> > the 11/40 (11/35), RK05, DZ11, RL02, MM11 core memory, RX01, RL01
> > diagnostics. I have found some info on Henk's site, but would like
to
> > know if anyone has a comprehensive list and hints on how to run
these,
> > what the output means, how to answer the prompts, etc.
It would be a big list :-) I had a whole box of microfiche of them,
once. Later diagnostics use a common set of "switches" to tell them
whether to halt on error, loop on erro, produce lots of reports, etc;
alsmost all diagnostics have specific settings to determine what they
do in detail. If they halt on error, you need the isting to determine
exactly what caused the halt -- they don't, in general, print much
informative info.
> OK, the "magic decoder ring" for converting the MAINDECs to XXDP
names
> is quite simple. The MAINDEC # is of the form:
> MAINDEC-11-Dxxxx-*
>
> To convert this to the XXDP diagnostic name keep only the xxxx part
of
> the MAINDEC #. To run it, do:
> R xxxx??
>
> The first letter in the diagnostic name tells you what processor it's
> for. If I remember correctly C=11/40, Z=any
B is 11/40; C is 11/45
> There's a document that tells all about it (but I can't remember
where I
> found it at the moment).
That would probably be mine, at
http://www.dunnington.u-net.com/public/PDP-11/XXDP.pdf
XXDP.ps is the same content, just a different format.
The bits from page 6 to 12 are from V2.4, but the rest is mostly
version-independant.
> The pack images that you're talking about don't have the correct
memory
> diagnostic, but I've found that ZMSDD0 (wow! from memory...can you
tell
> I've used it a bunch?) works OK enough to be able to find bad memory
and
> you'll know when you hit bad memory. I've also found that having a
> hardcopy terminal is preferable to a CRT when you're getting
failures.
>
> If a diagnostic loads and then gives you a prompt like "DB>", START
is a
> good choice as a response.
--
Pete Peter Turnbull
Network Manager
University of York
