> - lo and behold, "Booting up XXDP-XM Extended
>Monitor" followed by ... "V2.4, Rev. E1, booted from DL0, 124Kw
>memory, Non-Unibus system, restart address 152000, type H for
>help".
>
>Looks like I now have a working PDP-11 :)
>
>The pack has 727 files on it whose names are meaningless (to me
>anyway). XXDPXM.SYS etc. is obvious but there are hundreds of
>files from A to Z with names like "VKMHA0.BIN", "ZAFAC0.BIC" and
>some .LIB and .OBJ files too.
>
>What on earth do I have here? Is it something that anyone would be
>interested in copying?
>
>-Charles
>
Charles, congratulations on getting the PDP-11 booting! What you
have there is an XXDP diagnostics pack. All those "meaningless"
files are various diagnostics that can perform tests such as memory
checks, CPU tests, and tests of various peripherals. There are several
places online that describe what the various diagnostics are. One
site that I can think of is Henk's site at http://www.pdp-11.nl
Ashley
More "operator error". Sometimes I think I have mild dyslexia.
The RL02 Fault and Ready lights stayed on which is usually a sign
of bad cabling (lost clock). Although I had carefully aligned the
IDC connectors while making my substitute RL02 ribbon cable, I
thought I'd save some effort by using a 40 pin header as a
male-male connector directly to the Berg connector (that mates
with the drive bulkhead connector inside).
However - after considerable schematic, DVM and scope work I
belatedly discovered that this connects the headers in a mirror
image and although left/right can be swapped by turning over the
ribbon cable, the two rows are now swapped as well! The four
corner pins are 3 grounds and the BPOK H signal. Wrong cabling
doesn't hurt anything on the RL8E since the power-ok circuit has a
100 ohm resistor in the collector of the driver transistor. But on
the RLV12 there is no protective current limiting and the PNP
transistor (MPS-A55) is turned on hard between +5 and the (short
to) ground! Fortunately it just got hot but didn't fry, although
it might if it'd taken me much longer to figure out the trouble :)
Anyhow this time when I powered up there were no lamps lit on the
RL02 (normal) and after the requisite 15 sec. powerup the Load
light came on. I crossed my fingers and pushed the Load button and
the drive spun up and the Ready lamp lit. So far so good.
So I flipped the restart switch on the CPU, answered "Y" to
"Start?" and got a message "Please boot from system disk". I have
one other disk pack that is known to have come from a PDP-11, so I
put it in the drive - lo and behold, "Booting up XXDP-XM Extended
Monitor" followed by ... "V2.4, Rev. E1, booted from DL0, 124Kw
memory, Non-Unibus system, restart address 152000, type H for
help".
Looks like I now have a working PDP-11 :)
The pack has 727 files on it whose names are meaningless (to me
anyway). XXDPXM.SYS etc. is obvious but there are hundreds of
files from A to Z with names like "VKMHA0.BIN", "ZAFAC0.BIC" and
some .LIB and .OBJ files too.
What on earth do I have here? Is it something that anyone would be
interested in copying?
-Charles
On Mon, 02 Jan 2006 12:00:55 -0600 (CST), you wrote:
>Is the terminator installed on the drive? IIRC, without the
>terminator the fault light will come on.
I have heard this before, but omitting the terminator does not
cause a fault on either my 8/A or 11, at least while idling. It
probably will cause trouble on reads or writes depending on how
fast the data transitions are and how much "ringing" there is.
-Charles
For SCO, the release numbers were different (at least at the end), Release 2.3.2 was 286, 2.3.4 was 386. Earlier (2.2 series) I'm not as sure of, my disks specify "SCO XENIX 386" on the 386 specific bits, and they just say "SCO XENIX" on the utility & games volumes (likely common). Minix 1.1+ can be had from www.minix3.org/previous-versions/index.html, and Coherent is available online if you poke around, too, but I think it might be the 386+ only V4.10.
Regarding the ImageDisk project:
I was surprised at how much positive and supporting email I received
in the past two weeks regarding ImageDisk, and I have been even more
surprised at the number of people who asked me to continue the project
- I did not think that many people were using (or at least interested
in using) the program.
In the light of this feedback, I am willing try and not allow the bad
vibes from a few to bring down what so many indicate they still consider
to be a good thing. To that end, I have reconnected the images archive
on my web site, and I will continue to make the latest versions of
ImageDisk available there. As this is a privately developed/funded
project, you can choose to use it or ignore it as suits your particular
mindset.
I do not wish to re-open the can of worms that has aleady played out
here, so please consider the following my "final say" on the subjects.
If you disagree with my decisions, I invite you to excercise your option
of creating your own software package more suitable to your requirements.
Binary / Image Format
---------------------
Some people have expressed concern about the future of the program
as well as it's current legal status, especially given that I was ready
to withdraw it from circulation. To address this, I have released a new
version (1.09) of the program which contains an explicit license, which
essentially states:
- You may use the program for as long as you like.
- You may distribute copies of the program as long as you do not alter
or omit the original content. (You may make additions as long as they
are clearly marked as such).
- You may create/manipulate .IMD image files with no restriction (at
least not from me) - I have included a statement explicitly placing
the .IMD image file format specification into the public domain.
- I guarantee nothing / I take no responsibility for what you do with
any of this material.
FYI: 1.09 also correctly supports the secondary controller, and should
support 4 drives/controller - although I am unable to test the latter.
It also has a new command in the Align/Test function that lets you
write out a .IMD file containing a single track (read by 'D'), which
can be useful for recovering marginal/bad sectors. (It was to me!)
Source Code
-----------
As noted in one of my earlier postings, I have no plans to release
the ImageDisk source code under GPL - I don't agree with GPL. If
your position is an inflexible "GPL or the highway", then please
locate the nearest on-ramp and be on your way with no further ado.
It is interesting to note that although I offered to make the source
code available under a Non-Distribution-Agreement to anyone who had
need of it, only one person asked for it, and this person was not one
of those involved in the "discussion" (in fact this person does not
subscribe to the mailing list and heard about the source code offer by
another channel). I also gave the code to a second person (from the
list) who was trying to get ImageDisk running under DOSEMU and I saw
that he would benefit from seeing exactly what it was doing with the
hardware (although he never actually asked for it).
I'm not sure exacty what the above means, but it would suggest that
the negative statements made in the mailing list and in private email
were motivated more by "religion" than by any pressing need for the
source code.
At this time, for reasons I have already stated, I am not ready to
make the ImageDisk source code generally available for modification.
To address concerns that my source code policy is preventing people
>from developing similar programs (I can't see why), and for those who
stated that they simply can't use the program without looking at it's
source code (and for whatever reasons are unwilling to simply ask for
it), I have made the concession of allowing the ImageDisk source files
to be anonymously accessed on a "view only" basis. You can download
IMDSRC.ZIP from my web site, which contains a viewer which will let
you browse the source code files.
I have no doubt that there are plenty of people here with the technical
skills to break the viewer and extract the source code files, however I
I ask that you please not do so. Please refer to the README.TXT file in
the archive for my reasons. If you have a legitimate need to use the
source files, please contact me and I am sure we can work out an
arrangment. It is my wish to fully support anyone who is developing an
ImageDisk compatible program for other environments.
Regarding concerns that not using GPL will prevent anyone from using
"ideas" from my source code - please note:
I hold copyright on this code which protects this particular
implementation/representation of the ideas and algorithms used within
it, however I have neither applied for, nor received patents on any
portion of the program. This means the ideas and algorithms themselves
are NOT restricted. In other words you can use any of the techniques
which I have employed in your own programs. To clairify this point, I
have made an explicit statement to this effect in the terms and
conditions which accompany the code viewer (although such a statement
is not strictly necessary).
--
dave04a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools: www.dunfield.com
com Collector of vintage computing equipment:
http://www.parse.com/~ddunfield/museum/index.html
On Jan 2 2006, 10:13, Tim Shoppa wrote:
> Pete Turnbull <pete at dunnington.plus.com> wrote:
> > It was used because there was a rad-hard silicon-on-sapphire
version,
> > and then some people used the standard versions so they could use
the
> > same code and tools.
>
> Up until just a few years ago (2002?), Harris/Intersil web pages
listed the
> SOS 1802 as a current product, along with more conventional CMOS
1802's
> and support chips.
I'm not so sure they were really available, though. Take a look at
http://www.amsat.org/amsat/articles/g3ruh/124.html
> If I have the chronology right, Harris bought much of RCA's line in
> the 90's and Intersil bought them out a few years later.
>
> But they've been dropping a lot of classic parts (including the
CA3046,
> which I never believed would go out of style! There are newer
> surface-mount differential pairs of course but not quite the same
> as the good old CA3046 in a can...) Many of the hobbyist-oriented
> retailers still have plenty of old stock though.
>
> What 70's era micros are still in production? Z80, I'm sure. 8088,
probably
> (although probably not in an Intel fab.) Anything else?
I was going to say I thought the Z80 was no longer in production,
although some of the descendants are. However, Zilog still show
several 40-pin DIL and 44-pin PLCC versions as active.
Intel still list a couple of members of the MCS-48 family and sell
modern versions of the 8051 for automotive applicatons. I think MCS-51
is mid-1980s though.
--
Pete Peter Turnbull
Network Manager
University of York
Since you guys are bringing up some unusual stuff with modems, I thought of
something else I have in storage...
Got a pair of units that are designed to be used on a 4-wire (!) leased line,
or something. There's no "smarts" in the modem portion of it at all, though
there is a separate board in there (with a separate serial connector) that
has a z80 on it to do some sort of diagnostics. They're 9600 baud, but
since they're set up for a 4-wire connection I don't forsee me having any
possible use for them.
Was thinking about scrapping them out, as they're in cases that are quite
nice, but I'll entertain offers to the contrary. :-)
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, a critter that can
be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin
>What are the Burroughs L-series computers? I started working for
>Burroughs just before the Sperry merger and I guess I missed the
>L-series.
I> collect B1000 stuff (or, I would collect it if I could find
anything)
>and acquired a bunch of B20 systems a couple of years ago, so I
collect
>them now.
>Other than a museum that asked me if I ever found a B1000, I haven't
>found any other collectors of Burroughs stuff.
>alan
That's funny - I use to design them ;-) I was a CPU design engineer on
the last two iterations of the B1000 (B1955/B1965). (Hans P should
probably saw something next ;-) Curious what you've got in your
collection?
I'd buy a B1965 if one ever were available! ( I should be able to help
with B1955 too if anyone has one..) I should be able to help get one
running again if required.
Steve Wilson
Hi there,
I came across the webpage where you mentioned you have a copy of the intel sdk manual.
I would not mind getting a copy of it too. I'll need to study it for my school projects. I am a student in Nigeria. I would be really grateful if you can let me have a copy.
Thanks a lot.
Maleeq
Nigeria
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
On Jan 2 2006, 15:19, Gooijen, Henk wrote:
> Yes, and I seem to remember that an other reason to use the 1802
> was because RCA exactly specified what the CPU would do on *any*
> "opcode", even for the codes that were not actually instruction
codes?
That's right -- I'd forgotten that. There was also some work done to
see what effect ionising radiation would have on them. Another factor
was that the 1801 and 1802 were the first available low-power CMOS
microprocessors.
--
Pete Peter Turnbull
Network Manager
University of York
