Does anyone happen to have ROM dumps of from the RML 380Z CPU board?
All three 2716's on the board in front of me seem to have gone blank.
(I've verified that the 2716 chargen ROM from the video board reads OK,
so it's not my programmer failing to read properly!)
The three ROMs in question are labelled "4.0B" (M0, M1 and M2).
My 380Z fileserver won't have the same ROMs in it, and my own 380Z
'desktop' only has a pair of ROMs in it labelled "3.4E".
ps. are 2716's known for failure in this way?
cheers
Jules
> the Intel data book makes it very clear you do have to program
> all locations.
> The unchanged ones have to be reprogrammed with their existing
> contents, you can't skip over them.
Not true on both counts, you only need to go through the program
cycle for bytes that need to be programmed and if you want to leave
a byte unchanged but still go through the program cycle then you
set the data to $FF as bits can't be programmed high.
What the data sheets say often did differ from the practice, even
on official programmers.
I used to use 2708s in CB to 11m conversions and got away without
the -5v supply by using a lamp to illuminate the chip and generate
the -ve bias photoelectrically, this only worked with one brand of
EPROM though.
Lee.
.
___________________________________________________________
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
On Wed, 22 Jun 2005 Paul Koning <pkoning at equallogic.com> wrote:
> >>>>> "Guy" == Guy Sotomayor <ggs at shiresoft.com> writes:
>
> >> So tell me, what are the really cool methods to transfer data
> >> between a PC and a real PDP11 at a reasonable speed? SCSI
> >> controller and SCSI disk? Something else? Ethernet?
> >>
> >> Or is a backup over serial line a normal thing...?
>
> Guy> I found that the best way to backup/restore is to use tape. I
> Guy> have a TU80 on the PDP and a SCSI 9-track on the PC. Works
> Guy> great and is much faster than the serial line.
>
> Ethernet is another good way; DECnet is available on Linux.
Unfortunately, the DECnet for Linux sucks so bad it isn't usable. Well, it
is kindof usable if you want to talk with a VMS machine, but it don't work
against RSX. I've tried it... :-(
Appearantly the DECnet/Linux guys only have had VMS machines to test
against, and I didn't manage to stir much interest when I reported how
badly it failed with RSX. I only got responses like "well, that don't
surprise us, since we've only tested against VMS".
(I haven't tried DECnet/Linux against VMS, so I don't know if it works,
but that's what they say anyway.)
Johnny
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Jun 28 2005, 1:48, lee davison wrote:
> > Sure you're not looking at the specs for a 2716? Tony's
> > information is correct for a 3-rail 2708 according to my
> > Intel, Motorola, Texas data books.
>
> Yup, I'm reading from the Softy notes. I do have a datasheet
> for a 2708 but that only says "it is customary to begin with
> the '0' address" and that there are two programming voltages,
> +12v on the PE pin and +25v pulse on the program pin. With
> that part, identified only as N2708 on the sheet, the pulse
> is 1.0ms minimum and the total time per location is a minimum
> of 100ms.
The standard programming voltage is 26V for 2708s and 3-rail 2716s
(like the Texas ones). It's 25V for single-rail 2716s.
N2708 is a Signetics part. Somewhat later than the Intel and others.
--
Pete Peter Turnbull
Network Manager
University of York
> Sure you're not looking at the specs for a 2716? Tony's
> information is correct for a 3-rail 2708 according to my
> Intel, Motorola, Texas data books.
Yup, I'm reading from the Softy notes. I do have a datasheet
for a 2708 but that only says "it is customary to begin with
the '0' address" and that there are two programming voltages,
+12v on the PE pin and +25v pulse on the program pin. With
that part, identified only as N2708 on the sheet, the pulse
is 1.0ms minimum and the total time per location is a minimum
of 100ms. Also of note is that the address setup in program
mode is 1us minimum and the time between exiting program mode
and the first valid read is 10us minimum.
Lee.
.
___________________________________________________________
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
On Mon, 27 Jun 2005 Doc Shipley <doc at mdrconsult.com> wrote:
> Johnny Billquist wrote:
>
> > Huh? You had problems getting a CD to work? I just plugged one in, and in
> > RSX I suddenly had a DU device of the type RRD40.
>
> I think it depends on the SCSI adapter.
>
> I have 2 RQDX1 adapters, and they are incredibly temperamental. I
> haven't gotten either one to work with a CD-ROM. They want DEC drives,
> although I've gotten non-DEC 4GB Seagates to work, and a TZ30. A TLZ06
> or a TLZ07 will load RT-11 or BSD, but not RSX or the RSTS/E images that
> are available on the 'net.
Since when is a RQDX1 a SCSI adapter? :-)
I guess you actually mean the RQZX1.
I haven't tried that one. I have CMD adapters myself, and they really are
excellent.
Johnny
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Sun, 2005-06-26 at 21:17 -0700, vrs wrote:
> Anyone want to ship this thing across the USA for me :-)? Looks like a
> beauty!
:-)
Out of interest, what drives are those? Our 8 has a pair of Dectape
55's, which have bronze-coloured faceplates rather than the black of the
Ebay system. Is Dectape 55 a different animal to TU55?
cheers
Jules
I have an HP 16500A analyzer with original 720k disks.
Problem is that only the rear drive seems to read the disks.
I am suspicious that the front drive is bad. I am using
stock 720k (single hole for write protect only) and trying
to format them in both front and rear.
I also am not able to read the stock originals with any
program under either linux or dos. I realize that these
seem to be formatted in a proprietary HP format.
I luckily downloaded all the kits from the Agilent site before
they were thoughtfully erased by Agilent. However these
programs have not produced anything but floppy images
which I cannot get onto a disk either.
I should also explain that I am trying to use the 1.44 disks
on my PC to do the format of the 720k disks. All I can seem
to do is get formatted dos disks, but the HP write program
fails.
Also all attempts as mentioned to get data off HP disks onto
a linux box or windows box have failed. I know that under dos
there is a format byte in the first sector that confuzes the bios
and windows systems if it is not properly set. I tried the
read mode of "rawrite" that i had anyway just as a desperation
move. I also tryed a forced format "dd" input from the 720k
device on linux. This last should bypass any media format
bytes, and set the floppy path to just that format. Still no
joy.
My current thought is to dredge my stock of junk for a 720 K
drive and try it on a dos or linux box. the main problem that
I can think of between making new disks on the pc and reading
them on the analyzer is the possiblity of formatting problems
due to the head width.
I pretty much am convinced the front floppy on the thing is
bad, so I need one of those. I don't know if it is common, or
a weird one specialized to HP yet or not. I also have not been
able to clean it, as I need to buy a fresh supply of alcohol (isopropyl)
to clean with.
thanks
jim
But I probably will need CS/80 docs of some sort. There apparently is
some MI driver code for HP-IB disks in NetBSD, which is likely to help.
Unless there's some kind of CS/80 spec among the doc we have online...
--
the CS/80 programming spec is at
http://www.bitsavers.org/pdf/hp/disc/5955-3442_cs80-is-pm.pd
the AMIGO protocol is described in
http://www.bitsavers.org/pdf/hp/disc/09134-9032-Aug-1983.pdf
a piece that is still missing is what commands are supported
in the SS/80 subset protocol used in drives like the 9153C
and 9354A/B
The HPIB code for the 9000 code in NetBSD is the 'rd' driver
along with hpib.c
