There are a few people out there struggeling with their 4052's :
On ftp.dreesen.ch/FTP/TEK4052 they will find description, schematic, pictures and romdumps for the Diagnostic ROM pack, as used by the TEK engineers in the day.
Also listed are the the TEK-supplied CRC's for all ROMS in the 4052/54 systems.
No special components used, so nothing to stop you building your own Diagnostic pack. If anyone does so they can contact me if they need further info.
?Jos
Sorry for the spam - I'm trying some ideas to see if I can figure out why I
don't get cctalk/cctech messages anymore (for about a month now). -- Ian
--
Ian S. King, MSIS, MSCS, Ph.D. Candidate
The Information School <http://ischool.uw.edu>
Dissertation: "Why the Conversation Mattered: Constructing a Sociotechnical
Narrative Through a Design Lens
Principal Investigator, "Reflections on Early Computing and Social Change",
UW IRB #42619
Archivist, Voices From the Rwanda Tribunal <http://tribunalvoices.org>
Value Sensitive Design Research Lab <http://vsdesign.org>
University of Washington
There is an old Vulcan saying: "Only Nixon could go to China."
> From: Dave Wade
> ENIAC had been configured in stored program mode earlier in the year
> and had run a program stored in the function switches, e.g. ROM
> ...
> Despite the fact that when running stored programs ENIAC's parallel
> processing features were not available, it was exclusively in this mode
> from 1948 onwards.
This may have been mentioned here already, but if not, there's a good new
book out which covers this phase of ENIAC's existence in considerable detail:
Thomas Haigh, Mark Priestley, and Crispin Rope, "ENIAC In Action: Making and
Remaking the Modern Computer", MIT Press, Cambridge, 2016
It's a very interesting and well-done book; I highly recommend it.
> From: Brent Hilpert
> The best that can be said for your position is that you (and the
> ENIAC/Mauchlyite crowd) have a particular opinion and definition
> regarding 'stored-program computer'.
I'm harly a member of the "ENIAC/Mauchlyite crowd" (in fact, I used to not
have a good impression of them at all), but I thought Haigh et al made a
pretty good case.
Noel
In case you missed it we (the Vintage Computer Federation) is putting
together a Vintage Computer Festival (VCF PNW) at the Living Computer
Museum+Labs in Seattle. We are actively looking for exhibitors and
speakers for this new show.
The show will be held February 10th and 11th, 2018. We are not planning to
charge for admission to the show so visitors will be able to enjoy the
museum, the exhibits, speakers and the consignment area all for the normal
cost of museum admission.
We would like to get exhibitor registrations wrapped up by the end of
November so that we can move to the next stage of planning. If you have an
idea for an exhibit and would like to hang out at the museum for two days
talking vintage computers then consider signing up today. Have an
interesting topic for a presentation? We need those too ... Newbies need
not be scared; I'm new to this as well.
More information can be found at
http://vcfed.org/wp/festivals/vintage-computer-festival-pacific-northwest/
. Please email me directly if you have questions or need encouragement.
Regards,
Mike Brutman
michael at vcfed.org
I have successfully built a rl02 disk using pdpgui on a windows XP laptop,
the newer version works on window 10. All you need other than the software
is a serial card like a m7800. Pdpgui acts as a gui. Do you have a m9312
rom/terminator card with a terminal console rom?
Bill Degnan
twitter: billdeg
vintagecomputer.net
On Nov 11, 2017 7:04 AM, "Aaron Jackson via cctech" <cctech at classiccmp.org>
wrote:
> Well, some progress.
>
> It seems that a terminator is not required so long as the cable is VERY
> short. The controller RLV12 controller appears to have a few termination
> resistors on it anyway. There is no fault light appearing and the drives
> spin up fine. Mine cable is less than 20cm and the PDP is sitting just
> on top of the drive.
>
> I can see that the drive is communicating because the lsb of the csr
> changes flips between 0 and 1 when I load and unload the drive.
>
> I wanted to try and dump the disks using vtserver, but when I run the
> copy program I end up with the following
>
> ]] Enter name of input record/device: rl(0,0,0)
> ]]
> ]] Can't get rl(0,0,0) sts
> ]] rl(0,0,0) err cy=0, hd=0, sc=2, rlcs=142205, rlmp=0
> ]] rl(0,0,0) error reading labelsector
> ]] Enter name of input record/device:
>
> The same happened on both packs - they have both been cleaned and look
> as though they are in good condition. The heads have been cleaned too.
>
> Given that the drive appears to be communicating with the PDP-11, where
> might this problem come from?
>
> Thanks,
>
> Aaron.
>
> Aaron Jackson via cctech writes:
>
> > Hi everyone,
> >
> > I have managed to hook up an RL02 drive to my PDP-11 (thanks to Dave
> > Wade for the drives) . This took me longer than I thought it would - I
> > tried with a flat ribbon cable with a DIY terminator going straight into
> > board , but couldn't get it to work. Removed the terminator, and the
> > fault light turned off. So that's positive.
> >
> > I tried to load a cartridge, which I had cleaned, inspected and
> > generally appears to be in good condition. It started to spin up and I
> > could hear it getting faster, but after 30-40 seconds the fault light
> > returns. I made a short video demonstrating this:
> >
> > https://www.youtube.com/watch?v=japwBBodO8U
> >
> > According to the manual the fault light can appear for the following
> > reasons:
> >
> > - Drive select error... Surely this would come on at the start?
> > - Seek time out error... I'd have to hear the heads move first
> > - Write current in heads during sector time error... Same as above
> > - Loss of system clock... The fault light would be on from the start.
> > - Write protect error... I don't think it got that far
> > - Write data error... Same as above
> > - Spin error... Is this the only remaining fault?
> >
> > So could the only cause be a spin error? I am wondering if the belt is
> > slipping or something like that?
> >
> > Can anyone offer some advice?
> >
> > Thanks,
> >
> > Aaron.
>
>
> --
> Aaron Jackson
> PhD Student, Computer Vision Laboratory, Uni of Nottingham
> http://aaronsplace.co.uk
>
> From: Aaron Jackson
> The RL02 technical manual says to figure out why a drive error
> occurred, I can execute a get status command (?) and then perform an
> MPR read (?). So while I don't know how to do that,
RLV 12 User Guide, section 5.2.
Noel
Many Thanks for this.
A useful addition to our HP docs here.
Ed# _www.smecc.org_ (http://www.smecc.org)
In a message dated 11/9/2017 7:29:40 A.M. US Mountain Standard Time,
cctalk at classiccmp.org writes:
The manual has been scanned and is on our FTP server:
ftp://computermuseum.informatik.uni-stuttgart.de/hp/hp2648/13245-90001_2640S
eriesCharacterSetGeneration_Oct1975.pdf
Enjoy :-)
@Al: you may push it to bitsavers
Christian