Diablo Series 30 removable disk drives & sector sensor
I've been researching uses of the IBM 2315 disk pack design in various systems. There appear to be two styles of sensors used for sector identification in IBM 2315 disk pack designs. The IBM 2310 disk drive used an optical sensor and notched-ring integrated into the spindle so that a U-shaped assembly of light+sensor is appropriately positioned when the pack is mounted (see: https://www.manualslib.com/products/Ibm-2310-10271354.html ). DEC also used this style in their RK05 drives (see: EK-RK5JF-MM-001_RKO5_RK05J_RK05F_Disk_Drive_Maintenance_Manual_Nov76.pdf, Figure 1-3 and Section 4.2.6 on page 4-16 (56-of-135) "an optical device that contains a light emitting diode and a photosensor". The other style utilizes a magnetic sensor and the hub (perimeter of the flat surface to which the pack is affixed when mounted) itself is notched. A flat sensor including a magnet is suitably positioned with respect to that face when the pack is mounted. HP used this style in their HP7906 drive, which combined a removable disk with a fixed disk (the fixed disk actually provided the sector-timing information for the removeable disk pack; the removeable disk itself only had a single index notch on the hub). I've become confused about the one used with Diablo Series 30 drives, typically employed by OEMs (e.g., Data General). I assume that it was one-or-the-other, but perhaps either might be used based on the requirement of a particular OEM? In D3140-171_Maintanance_Manual_For_Series-30_Disk_Drive_Jan72.pdf, on page 7-17 (92-of-103) Figure 7-9 SECTOR TRANSDUCER ASSEMBLY clearly illustrates the mechanism of a magnetic transducer, although nowhere can I find Series 30 technical documentation that specifically discusses the nature of its sector transducer. All schematics that I have checked do not seem to include any provisions for powering a light source, which is consistent with the use of a magnetic transducer. However https://www.righto.com/2018/03/a-1970s-disk-drive-that-wouldnt-seek.html from Ken Shirriff shows a Diablo drive where Ken clearly (https://lh3.googleusercontent.com/-_meZQXUR5NQ/Wr-34VTNwUI/AAABQe4/fhC1 75xg0Mcm6eeytILHMyUGZ1TFAUzkwCHMYBhgL/w/disk-opened.jpg) illustrates a disk pack that is hard-sectored based on slots-in-ring which AFAIK implies an optical sensor. He references 81503-02_Series_30_Disk_Drive_Maintenance_Nov75.pdf which is non-specific regarding the sector transducer, but on page 5-6 (41-of-63) it refers to there being "two interconnecting wires at the transducer" and Figure 5-7 SECTOR TRANSDUCER ADJUSTMENT appears to me to be consistent with the earlier maintenance manual Figure 7-9 SECTOR TRANSDUCER ASSEMBLY - a magnetic transducer. So is the opened disk pack not actually one for a Diablo Series 30 drive? Or did the Diablo Series 30 include an OEM-specific (?) variant that used an optical sensor? Or perhaps there's something else going on here with the various IBM 2315 disk pack designs regarding sector sensing that I fail to understand? - paul
RE: Digitronics P135-20 Paper Tape Punch
Yes indeed. No response whatsoever :-<. Not even a receipt acknowledgement. From: Adrian Stoness Sent: Friday, March 11, 2022 10:21 AM To: pbir...@gmail.com; General Discussion: On-Topic Posts Subject: Re: Digitronics P135-20 Paper Tape Punch did u try talking to that outfit to see if they got more documents with it? On Fri, Mar 11, 2022 at 9:08 AM Paul Birkel via cctech mailto:cctech@classiccmp.org> > wrote: I have the mechanism for a Digitronics P135-20 Paper Tape Punch. It turns out that Surplus Sales currently has one of these for sale; see item "(EQP) P135-20/35". It is accompanied by a three-page snippet of a much longer manual for this punch. See: https://www.surplussales.com/equipment/pdf/eqp-p135-20-35.pdf That's the only documentation that I've been able to find :-{. I'd very much like to find/acquire the remainder of this manual, or other relevant documentation. Can anyone help me? Thank you, paul
Digitronics P135-20 Paper Tape Punch
I have the mechanism for a Digitronics P135-20 Paper Tape Punch. It turns out that Surplus Sales currently has one of these for sale; see item "(EQP) P135-20/35". It is accompanied by a three-page snippet of a much longer manual for this punch. See: https://www.surplussales.com/equipment/pdf/eqp-p135-20-35.pdf That's the only documentation that I've been able to find :-{. I'd very much like to find/acquire the remainder of this manual, or other relevant documentation. Can anyone help me? Thank you, paul
Seeking a MC75325L Dual Memory Driver
I have here in my hands a DEC H222A (16Kx18), part of a MM11-DP, that took a blow at sometime in the past. In consequence there are a number of small parts damaged (snapped diode, crushed axial electrolytic, chipped mica capacitor, cracked/broken SIP resister net) but those all appear to be relatively easy to replace. What's not so easy to replace is the MC75325L Dual Memory Driver (L = Ceramic) that was de-lidded in the process :-<. I am wondering whether anyone has one of these ICs in their spare parts drawer that I could acquire? I do see a MC75325P (plastic) on eBay at littlediode_components for ~20USD, plus a surprisingly modest shipping charge (Royal Mail International). UTSOURCE claims to have a supplier of the ceramic part "new", with a significantly higher shipping charge. Before I go with the ceramic part (IMO not the sort of packaging that gets . remarked) I thought that I would check here for alternative sources. Thank you, paul
Memory Tech you don't see very often
Selectron Vacuum Tube: https://www.ebay.com/itm/174977901251 Really nice photo-shoot! I wonder what the back-story to this particular tube might be. I don't think that $16.18 shipping would be, um, adequate protection by any measure. Cheap, but not so sure about "cost-effective" . -
RE: Need picture of power supply mounted in 11/40 cabinet
Marc: Do you have the 11/40-specific wiring harness? Assuming that you do it's a bit tricky -- not so much mounting a given supply (aside from the fact that they are heavy and awkward to work with even when minimally populated), but because there is a very tight tolerance between them to thread the wiring harness. I've determined the hard way that you really need to install the lower one first, then the harness, then the upper one. At least for me it wasn't practical/possible to install the harness after-the-fact. There's also a bit of work involved in threading both of the AC power cables plus the pair of power-control cables (assuming that you're using a DEC power controller) via the right-side vertical rack channel -- which also interact with the power harness placement. Once everything is cabled-in-place the result is maximally compact, but getting there is not simple. Yes, the power cable wiring isn't well-described anywhere IMO. You have to stare at the puzzle-pieces for a while and "dry fit". Harness shape/stiffness helps eyeball how to fit the pieces together, but the importance of the rack vertical side-channel in making everything fit is not, IMO, made at all clear anywhere in the various documentation -- although it can be inferred from careful examination of a few graphics in various documents. The 11/40, the 11/45-50-55, and the 11/70 share the same design in this respect so documentation for one will serve you well in any of these cases. If you can tackle the task *before* installing the BA11 chassis you'll find it easier. If you're not using a standard DEC rack or don't have an equivalent vertical side-channel to work with then IMO you'll need to get very creative ... and the 11/40-specifics wiring harness may not work at all and you'll need to build your own. Fortunately I didn't need to explore that path ... Good luck! -Original Message- From: cctech On Behalf Of Marc Howard via cctech Sent: Saturday, December 4, 2021 10:28 PM To: General Discussion: On-Topic Posts Only Subject: Need picture of power supply mounted in 11/40 cabinet Hi, I've got an 11/40 I'm going to start working on. Problem is that there are two power supplies (H742 and H7420) that came with it but neither was mounted in the rack. Could someone post/send/etc. photos of how the power supply mounts in the rack? Also how is the power cabling routed (I think I'm missing this part)? Thanks, Marc Howard
RE: Early Programming Books
Well, utility depends on the objective. One that immediately springs to mind in an era when "computing" had a dearth of practitioners would be to inform various audiences "what is involved". The Dekker (1957) reference seems to be targeted at an audience interested in expressing mathematical statements in terms of the von Neumann model, generally building up to the idea of algorithms and their general reduction to a sequence of computational steps in that model of computation. This would be a pre-ALGOL 58 world and one can see the paper as a motivation for an ALGOL- (or FORTRAN-) like language. (Caveat: I've just skimmed a poor translation; more careful study required!) The McCracken (1957) book seems to be targeted at an audience of future practitioners, giving a feel for how a hypothetical instruction set would be employed "in daily practice" to solve problems. Perhaps answering the question of "would I like to become [or could I handle becoming] a 'programmer' " in an era when that was about to become a new specialty and career path. A numerical analyst (e.g.) might find the Dekker text more accessible; an engineer might find the McCracken book more to their liking. IMO, "in the world before 1960" both are "useful" without becoming a machine-specific instruction manual or cook-book. -Original Message- From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Chuck Guzis via cctech Sent: Sunday, June 20, 2021 12:34 PM To: Paul Birkel via cctech Subject: Re: Early Programming Books Aside from the very general Algol report and the Iverson book on APL, I have to admit that most of my programming knowledge came out of manufacturer's manuals, specific to a maker's systems. The APL book was, at the time, pretty much useless for writing any sort of serious code until you got hold of the manual for a particular system that you were going to use. Even the early McCracken books on FORTRAN had a section in the rear that attempted to gloss over different manufacturer's features and "extensions" (e.g. What does "B" punched in column 1 of a FORTRAN statement card mean--and for what system?) Lest anyone forget, that in the pre-1960 world, a lot more of production code was written in the assembly code/autocoder of a particular system. Even the DEC "Introduction to Programming" dealt specifically with the PDP-8 and was useless for the PDP-10. ACM CALGO back then accepted algorithm submissions in FORTRAN or Algol, but that's hardly an instructional text. I guess the question boils down to 'In the world before 1960, how *useful* was a general book on programming?" --Chuck
RE: Early Programming Books
Google document translate gives a modestly useful result after OCRing the UT original scan (www.cs.utexas.edu/users/EWD/MCReps/CR1957-009.PDF). Needs significant further work for readability :-<. Deeker, et al. appear to approach the topic from the perspective of mathematics (that is, modestly abstractly) after introducing the standard von Neumann 5-part model of a machine. They keep that general description, mapping mathematical expressions to general operations within that model. TOC: 1. General Introduction to Automatic Calculators 2, The word 3. The number 4, The Command 5. Block diagrams 6. Subroutines I 7, An elaborate~ example 8. Subroutines II 9. Subroutines III 10. Speed 11. Scaling, Control and Flexibility 12. The Administrative Subroutine I 13. The Administrative Subroutine II 14. Super programs McCracken approaches the topic with the same von Neumann model of a machine but then proceeds from the perspective of a hypothetical "typical" instruction set and a modestly specific architecture (e.g. signed ten-digit storage). AFAICS neither envisions representations for characters/text and the processing thereof. Both in 1957. Something in the air :->? -Original Message- From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Paul Koning via cctech Sent: Sunday, June 20, 2021 5:06 PM To: Norman Jaffe; General Discussion: On-Topic Posts Subject: Re: Early Programming Books > On Jun 20, 2021, at 1:19 PM, Norman Jaffe via cctech wrote: > > Basically, pre-1960, there couldn't be a 'general book on programming', since every system was a unique environment - the only languages that could even be remotely considered to be common were ALGOL 60 and FORTRAN II... and they were 'extended' by every manufacturer to provide, at least, some form of I/O beyond line printers and punch card readers / punches or to support different character sets. True, unless you were to set out to write a general course on programming that doesn't dig down to the level of any particular assembly language or machine architecture. From a quick look, I think the 1957 course by Dekker, Dijkstra, and van Wijngaarden I mentioned in my previous note does just that. And that explains the title, "Programming automatic calculating machines" (as opposed to the more common "Programming the xyzzy-42 machine"). paul
RE: Early Programming Books
Thank you Michael, for both the pointer and the scan :-}. From: Michael Mulhern [mailto:mich...@jongleur.co.uk] Sent: Sunday, June 20, 2021 11:22 PM To: Paul Birkel; General Discussion: On-Topic Posts Subject: Re: Early Programming Books I recently scanned my copy of "Electronic Computers: Principles and Applications" by TE. Ivall (1956) and there is a chapter on "Programming Digital Computers". It is more of a general overview, rather than any machine specifics. https://archive.org/details/electronic-computers/page/183/mode/2up The book also covers analogue computers for any interested. //m
RE: Early Programming Books
Sounds very promising, thank you for the tip. -Original Message- From: dave.g4...@gmail.com [mailto:dave.g4...@gmail.com] Sent: Sunday, June 20, 2021 4:01 PM To: 'Paul Birkel'; 'General Discussion: On-Topic Posts' Subject: RE: Early Programming Books Paul, What about Approximations for Digital Computers Cecil Hastings Jr., Jeanne T. Wayward, and James P. Wong Jr. Whilst its about a specific problem its not machine specific. It was originally published as papers in 1955 and as book later, but my copy retains its 1955 copyright. Dave
RE: Early Programming Books
Thanks Bill. Presume that you mean “Giant Brains, or Machines that Think” (1949)? Conveniently scanned and online: https://monoskop.org/images/b/bc/Berkeley_Edmund_Callis_Giant_Brains_or_Machines_That_Think.pdf From: Bill Degnan [mailto:billdeg...@gmail.com] Sent: Sunday, June 20, 2021 3:31 PM To: Paul Birkel; General Discussion: On-Topic Posts Subject: Re: Early Programming Books Paul, I have been compiling a library of such. Ioks here, if you are traveling north swing by to review the books on hand. The one that comes to mind is Thinking Machunrs by Berkeley but here on the patio at my parents house I dont know the date. Harvard press put out some early computing books but they may be Mark 1-specific. Remind me and I can check when I get to the office. Bill Kennettclasic.com
RE: Early Programming Books
TYDAC (TYpical Digital Automatic Computer) is very much an instruction set of its time. Memory is 2000 words of ten decimal digits and sign. Words are either numbers or instructions. I/O is punch cards, special typewriter, or a paper-tape reading device on the typewriter. Four magnetic tapes are assumed as auxiliary memory. ALU includes an Accumulator (11 digits + sign) and Multiply-Quotient (10 digits + sign). Instruction set includes floating-decimal add, multiply, and divide. 46 instructions (out of a possible 100) are defined. -Original Message- From: dave.g4...@gmail.com [mailto:dave.g4...@gmail.com] Sent: Sunday, June 20, 2021 10:51 AM To: 'Paul Birkel'; 'General Discussion: On-Topic Posts' Subject: RE: Early Programming Books Paul, I assumed that was the case, but the inclusion of the Wilkes book confused me. I think there really is a spectrum of books, so say pre-1955 all books assumed the reader had little knowledge of programming. For example the MK1 guide I pointed you to is V2. Its rumoured that Turing wrote V1 and no one could understand it but I think it more likely the machine changed. I also looked at the IBM 701 manuals and they too have some generic info at the front. However I also wonder what the earliest books were like. Dave G4UGM (You might want to e-mail Simon Lavington https://www.essex.ac.uk/people/lavin12900/simon-lavington he has done a lot of research on early computing, and might know more.) > -Original Message- > From: Paul Birkel > Sent: 20 June 2021 13:40 > To: dave.g4...@gmail.com; 'General Discussion: On-Topic Posts' > > Subject: RE: Early Programming Books > > Dave; > > I'm much more curious about programming books that were *not* machine > specific. > That is, about "general principles" of designing/preparing software for > execution. > > Of course, one needs a language; McCracken (1957) defines TYDAC. > Much later (1968) Knuth defines MIX. > > In between perhaps one could argue that ALGOL 58 qualifies as such a > language-for-demonstration, but I don't believe that there were any books > specifically about programming in ALGOL 58. I presume that there were > eventually such books for ALGOL 60. > > Then there's FORTRAN, in which context I first encountered McCracken > (1961: > Guide to FORTRAN Programming). > > Obviously my first example was EDSAC-centric. And yours is specific to the > Manchester MK1. > > -Original Message- > From: dave.g4...@gmail.com [mailto:dave.g4...@gmail.com] > Sent: Sunday, June 20, 2021 6:57 AM > To: 'Paul Birkel'; 'General Discussion: On-Topic Posts' > Subject: RE: Early Programming Books > > Paul, > What about machine specific manuals, so for example the Manchester MK1 > programming manual, the second edition of which is archived here:- > > https://web.archive.org/web/20090526192456/http://www.computer50.org > /kgill/m > ark1/progman.html > > In fact I expect that first book refers specifically to EDSAC, so is in effect > machine specific. There must have been similar manuals for other machines? > > I know there is a Ferranti Pegasus Programming manual, the copy I have is > dated 1962 but as the last Pegasus was produced in 1959 there must have > been earlier editions. > > Dave > > > -Original Message- > > From: cctech On Behalf Of Paul Birkel > > via cctech > > Sent: 20 June 2021 09:44 > > To: 'General Discussion: On-Topic Posts' > > Subject: Early Programming Books > > > > I know of two early computer (in the stored program sense) programming > > books. > > > > 1951: Preparation of Programs for an Electronic Digital Computer > (Wilkes, Wheeler, & Gill) > > 1957: Digital Computer Programming (McCracken) > > > > What others were published prior to the McCracken text? > > > > Excluded are lecture compendia and symposia proceedings, such as: > > > > 1946: Moore School Lectures > > 1947: Proceedings of a Symposium on Large-Scale Digital > > Calculating > Machinery > > 1951: Proceedings of a Second Symposium on Large-Scale Digital > Calculating Machinery > > 1953: Faster Than Thought, A Symposium On Digital Computing > > Machines > > > > These were principally about designs for, and experience with, new > hardware. > > > > I'm curious about texts specifically focused on the act of programming. > > Were there others prior to McCracken? > > > > paul >
RE: Early Programming Books
When it comes to McCracken I feel a bit like Homer Simpson "Donuts ... is there anything they can't do?" He certainly made a career out of writing programming language instruction texts. -Original Message- From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Norman Jaffe via cctech Sent: Sunday, June 20, 2021 10:26 AM To: General Discussion, On-Topic Posts Only Subject: Re: Early Programming Books I have two books on ALGOL 60 from 1962 - A Guide to ALGOL Programming, Daniel D. McCracken A Primer Of ALGOL 60 Programming, E.W. Dijkstra For APL, there is this from 1962 - A Programming Language, Kenneth E. Iverson However, I also have a reference from 1960 - LISP I Programmer's Manual, J. McCarthy et al. From: "General Discussion, On-Topic Posts Only" To: "Paul Birkel" , "General Discussion, On-Topic Posts Only" , "dave g4ugm" Sent: Sunday, June 20, 2021 5:57:08 AM Subject: Re: Early Programming Books On 2021-06-20 1:39 p.m., Paul Birkel via cctech wrote: > Dave; > > I'm much more curious about programming books that were *not* machine > specific. > That is, about "general principles" of designing/preparing software for > execution. Not sure if it's what you are looking for, but if you haven't, check out "Classic Operating Systems" by Per Brinch Hansen. > > Of course, one needs a language; McCracken (1957) defines TYDAC. > Much later (1968) Knuth defines MIX. > > In between perhaps one could argue that ALGOL 58 qualifies as such a > language-for-demonstration, but I don't believe that there were any books > specifically about programming in ALGOL 58. I presume that there were > eventually such books for ALGOL 60. Pretty sure I own one, by Dijkstra. Will get details later if you are interested. --Toby > > Then there's FORTRAN, in which context I first encountered McCracken (1961: > Guide to FORTRAN Programming). > > Obviously my first example was EDSAC-centric. And yours is specific to the > Manchester MK1. > > -Original Message- > From: dave.g4...@gmail.com [mailto:dave.g4...@gmail.com] > Sent: Sunday, June 20, 2021 6:57 AM > To: 'Paul Birkel'; 'General Discussion: On-Topic Posts' > Subject: RE: Early Programming Books > > Paul, > What about machine specific manuals, so for example the Manchester MK1 > programming manual, the second edition of which is archived here:- > > https://web.archive.org/web/20090526192456/http://www.computer50.org/kgill/m > ark1/progman.html > > In fact I expect that first book refers specifically to EDSAC, so is in > effect machine specific. There must have been similar manuals for other > machines? > > I know there is a Ferranti Pegasus Programming manual, the copy I have is > dated 1962 but as the last Pegasus was produced in 1959 there must have been > earlier editions. > > Dave > >> -Original Message- >> From: cctech On Behalf Of Paul Birkel via >> cctech >> Sent: 20 June 2021 09:44 >> To: 'General Discussion: On-Topic Posts' >> Subject: Early Programming Books >> >> I know of two early computer (in the stored program sense) programming >> books. >> >> 1951: Preparation of Programs for an Electronic Digital Computer > (Wilkes, Wheeler, & Gill) >> 1957: Digital Computer Programming (McCracken) >> >> What others were published prior to the McCracken text? >> >> Excluded are lecture compendia and symposia proceedings, such as: >> >> 1946: Moore School Lectures >> 1947: Proceedings of a Symposium on Large-Scale Digital Calculating > Machinery >> 1951: Proceedings of a Second Symposium on Large-Scale Digital > Calculating Machinery >> 1953: Faster Than Thought, A Symposium On Digital Computing Machines >> >> These were principally about designs for, and experience with, new > hardware. >> >> I'm curious about texts specifically focused on the act of programming. >> Were there others prior to McCracken? >> >> paul > >
RE: Early Programming Books
Dave; I'm much more curious about programming books that were *not* machine specific. That is, about "general principles" of designing/preparing software for execution. Of course, one needs a language; McCracken (1957) defines TYDAC. Much later (1968) Knuth defines MIX. In between perhaps one could argue that ALGOL 58 qualifies as such a language-for-demonstration, but I don't believe that there were any books specifically about programming in ALGOL 58. I presume that there were eventually such books for ALGOL 60. Then there's FORTRAN, in which context I first encountered McCracken (1961: Guide to FORTRAN Programming). Obviously my first example was EDSAC-centric. And yours is specific to the Manchester MK1. -Original Message- From: dave.g4...@gmail.com [mailto:dave.g4...@gmail.com] Sent: Sunday, June 20, 2021 6:57 AM To: 'Paul Birkel'; 'General Discussion: On-Topic Posts' Subject: RE: Early Programming Books Paul, What about machine specific manuals, so for example the Manchester MK1 programming manual, the second edition of which is archived here:- https://web.archive.org/web/20090526192456/http://www.computer50.org/kgill/m ark1/progman.html In fact I expect that first book refers specifically to EDSAC, so is in effect machine specific. There must have been similar manuals for other machines? I know there is a Ferranti Pegasus Programming manual, the copy I have is dated 1962 but as the last Pegasus was produced in 1959 there must have been earlier editions. Dave > -Original Message- > From: cctech On Behalf Of Paul Birkel via > cctech > Sent: 20 June 2021 09:44 > To: 'General Discussion: On-Topic Posts' > Subject: Early Programming Books > > I know of two early computer (in the stored program sense) programming > books. > > 1951: Preparation of Programs for an Electronic Digital Computer (Wilkes, Wheeler, & Gill) > 1957: Digital Computer Programming (McCracken) > > What others were published prior to the McCracken text? > > Excluded are lecture compendia and symposia proceedings, such as: > > 1946: Moore School Lectures > 1947: Proceedings of a Symposium on Large-Scale Digital Calculating Machinery > 1951: Proceedings of a Second Symposium on Large-Scale Digital Calculating Machinery > 1953: Faster Than Thought, A Symposium On Digital Computing Machines > > These were principally about designs for, and experience with, new hardware. > > I'm curious about texts specifically focused on the act of programming. > Were there others prior to McCracken? > > paul
Early Programming Books
I know of two early computer (in the stored program sense) programming books. 1951: Preparation of Programs for an Electronic Digital Computer (Wilkes, Wheeler, & Gill) 1957: Digital Computer Programming (McCracken) What others were published prior to the McCracken text? Excluded are lecture compendia and symposia proceedings, such as: 1946: Moore School Lectures 1947: Proceedings of a Symposium on Large-Scale Digital Calculating Machinery 1951: Proceedings of a Second Symposium on Large-Scale Digital Calculating Machinery 1953: Faster Than Thought, A Symposium On Digital Computing Machines These were principally about designs for, and experience with, new hardware. I'm curious about texts specifically focused on the act of programming. Were there others prior to McCracken? paul
CLCC68 Covers
I intend to restore a pair of boards that used Intel Ceramic Leadless Chip Carrier (CLCC) parts. Unfortunately the socket covers were tossed when the boards were scavenged for their chips. The sockets and attached clips are themselves just fine. eBay item # 252830664338 is an example of this style of 68-pin socket. Item # 362702811275 is an example IC in CLCC form. If anyone has a par (or even just one) of these covers lurking in their odds-n-ends collection somewhere I'm interested in putting them back into service. Thank you for taking a look! paul
Microcap12 Spice simulator
Forwarding from another list because of its general interest: . A heads up that the guy who was responsible for the full professional grade Spice simulator Microcap (latest version 12) has retired, and made his software downloadable free of charge. It was $4,500 per seat before. Download page here http://www.spectrum-soft.com/download/download.shtm . paul
DEC Scalps
https://www.ebay.com/itm/312738923353 Sez: "Older DEC PDP console face-plates DEC PDP 11/55 rare, PDP 8-straight 8 'glass'rare, PDP 8/L, PDP 8/I, DEC TU58 status/diag. Panel . All in goodshape. $1000 for the lot or $200 apiece. " -
RE: DEC VT20 boot device
>-Original Message- >From: Jay Jaeger [mailto:cu...@charter.net] >Sent: Saturday, August 10, 2019 11:02 PM >To: Paul Birkel; General Discussion: On-Topic Posts >Subject: Re: DEC VT20 boot device > >On 8/10/2019 1:56 PM, Paul Birkel via cctech wrote: >> The DEC VT20 terminal apparently included a PDP-11/05 with a direct mapped >> character display and was intended for text editing and typesetting. It >> seems to have been followed by the VT21, and then VT71/VT72, all three based >> on an LSI-11 (KD11-F). There's a real lack of documentation about these >> online, although the VT72 does have a print set. >> >> Apparently the VT20 used the M792-YK as its bootstrap; the Field Guide is >> silent regarding the boot device and M792 documentation stops earlier in the >> series of variants. >> ... >> So . is the boot device in these systems the remote host via the serial >> line? What protocol would that have been? Something native to Typeset-11 >> and DECset-11? >> >> paul > >I wonder if, maybe, it used the same protocol as the GT40, which also >had a boot-over-serial line capability. > >JRJ That's a promising lead! The GT40/42 User's Guide (EK-GT40-0P-002), Section 5.1 Communications Bootstrap/Read-Only Memory (ROM) describes a 256 word (GT40) and 512 word (GT42) ROM, however it appears that the bootstrap loader portion is intended to occupy 63 words which fits the M792 capacity (on the GT40 just the absolute addresses 15700-15776 (base 8)). Section 5.1.1 Bootstrap Loader describes the packed-and-serialized 6-bit "byte" stream, including some nice diagrams. Section 5.1.2 Character Encoding includes an illustrated example starting from a pictorialized 8-level paper tape. Appendix D has an annotated (and unexpurgated) program listing of the full GT40 ROM, including the loader and Figure D-1 Communications Bootstrap Loader Flow Diagram. Program comments suggest that a PDP-10 was expected as the host for a GT40. I imagine that the same expectation would have applied for the earlier VT20? Appendix E is similar, but for the "scrolling ROM - GT42" which appears to be a VT05 emulation It includes more conventional loaders as well: RF11, RK11, RC11, RP11, TC11, TM11, and paper tape. According to the program comments, "the fearsome power of the 11" is brought to bear :->. Both loaders are credited to Jack Burness. If I understand the listings correctly then in the smaller VT20 ROM, presumptively based on the same code, one would be expected to successfully fall off the end of the ROM into freshly loaded code that signals back to the host that a successful load has taken place. In the GT40 with the larger ROM that acknowledgement ("SENDIT") is part of the ROM itself. paul
DEC VT20 boot device
The DEC VT20 terminal apparently included a PDP-11/05 with a direct mapped character display and was intended for text editing and typesetting. It seems to have been followed by the VT21, and then VT71/VT72, all three based on an LSI-11 (KD11-F). There's a real lack of documentation about these online, although the VT72 does have a print set. Apparently the VT20 used the M792-YK as its bootstrap; the Field Guide is silent regarding the boot device and M792 documentation stops earlier in the series of variants. According to the VT72 print set, it used the MRV11-VC (M9942-YC; described in the Field Guide as a "bootstrap/diagnostic module") for its bootstrap but is also silent regarding the boot device. In interestingly, the Field Guide also describes a MRV11-AA (M7942-TB) as a "M7942 with VT52 emulator, VT71 bootstrap". For async. communications the VT20 used a DL11-B (M7800 (EIA)). the VT72 a DLV11-F (M8028). Looking in a DEC "Options and Modules" listing I see VT20 bundles including Typeset-11 and DECset-11, and it appears that the VT20 could be configured with two displays & serial lines in a single 11/05. So . is the boot device in these systems the remote host via the serial line? What protocol would that have been? Something native to Typeset-11 and DECset-11? paul
RE: HP 1000 A900 ("Magic") Questions
>-Original Message- >From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Glen Slick >via cctech >Sent: Friday, May 10, 2019 1:34 PM >To: General Discussion: On-Topic Posts >Subject: Re: HP 1000 A900 ("Magic") Questions > >On Fri, May 10, 2019 at 4:14 AM Paul Birkel via cctech > wrote: >> >> Aficionados; >> >> I'm interested in acquiring an HP1000 A900, in any form-factor. >> (http://www.hpmuseum.net/display_item.php?hw=594) >Another hard part is the 1 memory frontplane. Maybe it wouldn't be >too hard to build an equivalent PCB if the proper connectors can be >acquired. They are 3-row 96-pin connectors. Maybe common DIN 41612 >connectors would work, I haven't looked at that closely. I can confirm that DIN 41612 connectors should work fine, along with a 4-layer PCB. HP doesn't seem to have gone "odd-ball" in that particular design choice. I'd need to get someone to buzz out the connections to ensure that they are 1:1 all the way across before designing a PCB to fit. >At a minimum you need either a 12005 serial card or a 12040 serial mux >for a console interface. Both of those are fairly common, although you >might pay more for cables than the boards if you don't build cables >yourself. There are several firmware versions for the 12040 mux. If >you have a D mux you need need VCP firmware 4020 or higher on the >12203A cache controller. Cables, and those specialized HP connectors, are always a pain. I would need to make up my own, given my budget, I expect. I do have one or two possible spares from a 21MX I/O environment that probably could be repurposed assuming that the edge-connectors match up ... which they may not. We'll see. Thanks for the notes about the firmware version issue. >As you also said you need a 12009 HPIB card for a storage interface. >Running HPDrive on a PC to emulate disk and tape drives works well if >you don't have any real HPIB disk and tape drives. I managed to pick >up a 12016 SCSI card. Those are rare and expensive. I'll bet! Yes, I was assuming that HPDrive would be the way to proceed; it's good to get confirmation on that point. Also the availability of a suitably configured RTE. paul
HP 1000 A900 ("Magic") Questions
Aficionados; I'm interested in acquiring an HP1000 A900, in any form-factor. (http://www.hpmuseum.net/display_item.php?hw=594) Basic need would be a chassis/backplane/PS and minimal set of CPU/memory/HPIB-controller/terminal-IO PCA, however I'd be interested in simply acquiring a PCA-set and I'll work the chassis/backplane/PS separately. Even single PCAs would give me a helpful push forwards. And I need to stick to my hobby (beer") budget. I'm located in Maryland, USA, and pretty sure that the cost of overseas shipping would be ghastly for a chassis. But maybe not as bad for the tower configuration as for the rack-mount. If I understand correctly, the CPU consists of: 12201A A900 Sequencer Card 12202A A900 Data Path Card 12203A A900 Cache Controller 12204A A900 Memory Controller 12220A 768KB RAM (Or I presume 12103D 1MB, 12221A 3 MB, or 12221B 8 MB.) I imagine that I'll need to synthesize my own OTT "frontplane" for the memory. 12009A HP-IB Controller 12040D Asynchronous Multiplexer interface board Thank you for your insights, and opportunities (I hope), paul (offlist at pbir...@gmail.com)
RE: [rescue] Sun2/120 SunOS 3.2 suntools movie (was: advise on Sun2 disk install)
-Original Message- From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of allison via cctech Sent: Thursday, December 06, 2018 9:13 AM To: cctech@classiccmp.org Subject: Re: [rescue] Sun2/120 SunOS 3.2 suntools movie (was: advise on Sun2 disk install) On 12/06/2018 07:28 AM, Liam Proven via cctech wrote: > On Thu, 6 Dec 2018 at 12:44, Tony Duell wrote: >> I don't think anyone is questioning that it's a workstation, and that it was >> made by Sun. >> >> I think the problem is over 'first' and that a Sun-2 is not going to be the >> 'first' model. > Ah! Excellent point. I have to admit, I was totally unfamiliar with > the very early Sun products. I was happy with my little ZX Spectrum > back then, and being about 14, wasn't paying much attention to the > world of academic Unix usage. :-) > > Looking up the SUN-1, I see that it lacked a graphics adapter, and was > a text-only machine. I didn't know that. That alone means that it's > not really what I think of when I think of a Sun workstation: no > windowing system means that for me it's not really a workstation. > > But as a single-user Unix machine, yes, it unquestionably qualifies, > and I need to redefine my terms and my thinking a little... During my days at DEC in the later 80s the definition of workstation was 1MIPS processing power, 1M pixels, Desktop or desk side (fairly compact). Graphics and processing power were high and lots of ram and sufficient local disk as well. Most of the machines were RISC based, Sun (sparc), MIPS, or ARM powered. Allsion - And cost no more than a "megapenny" ;->. See the CMU "3M" definition: https://en.wikipedia.org/wiki/3M_computer -
Operation Codes
https://www.asc.ohio-state.edu/dunlap.3/humor/instruction.set.html ERS Erase Read-only Storage FPT Fire Photon Torpedoes GCAR Get Correct Answer Regardless XIO Execute Invalid Op code Among others! -
VAX 11/785 "Superstar" Backplanes
On the 'bay: 183405165416 and 183405165414 "Scrap / Gold Recovery" Six total. One wonders what the scrappers did with the rest, and where they came from given that the location is Goffstown, New Hampshire. paul
ARPANET Reaches the Royal Signals and Radar Establishment (RSRE, Malvern)
The following extract comes from a History of Programming Languages (HOPL) retrospective on the development of the Ada programming language written by the individual who was the government lead at DARPA for much of the time of its development (Colonel William A. Whitaker). I found it humorous. Perhaps you will too. - The ARPANET connection was inaugurated during a visit to RSRE by Her Royal Highness Queen Elizabeth II. Her Majesty sent a message of greetings to the members of the HOLWG from her net account, EIIR, by pressing a red velvet Royal carriage return. Because the address list was long, it took about 45 seconds for the confirmation to come back, 45 seconds of dead air. Prince Philip remarked, joking respectfully, that it looked like she broke it. - I suspect that we've "all been there" at one time or another! paul
RE: Details about IBM's early 'scientific' computers
Wonderful document. Thank you IBM Customer Engineering! -Original Message- From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Camiel Vanderhoeven via cctech Sent: Tuesday, November 14, 2017 4:01 AM To: Noel Chiappa; cctech; cct...@classiccmp.org Subject: Re: Details about IBM's early 'scientific' computers Have you really looked at everything that is on Bitsavers? It¹s much more than just the engineering manuals. If I may offer a suggestion, have a look at this document and see if it fits your needs: http://www.bitsavers.org/pdf/ibm/7090/ce/223-6895-1_7090_CE_Reference_System _Fundamentals_7100_7151_7606_Sep61.pdf Camiel On 11/14/17, 4:32 AM, "cctech on behalf of Noel Chiappa via cctech"wrote: >Please, everyone, I do actually know of BitSavers; you don't need to >point me >at it. > >When I said: > >>> I could look at the engineering manuals, but I was hoping for something >>> in between them and Bashe et al. > >I assumed everyone would understand that by "engineering manuals", I was >meaning the kind of things one finds in BitSavers. > > Noel
RE: RX02 Emulator
Check at: www.vcfed.org/forum/showthread.php?51918-Is-there-an-RX01-Emulator -Original Message- From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of Douglas Taylor via cctech Sent: Friday, September 01, 2017 11:42 AM To: General Discussion: On-Topic Posts Subject: RX02 Emulator In my other post I asked about DEC 11/2 and 11/03 cpus and 18/22 bit backplanes. I am still interested in this but I am considering what type of disk to run from. I ran into a rx02_emulator on github and looks quite interesting, since it uses an actual DEC RXV21 interface it would be compatible with the 18 bit addressing. Does anyone have experience with this emulator? Where can you get the circuit board that is part of this project? Doug
RE: Kryoflux or Catweasle
>-Original Message- >From: cctech [mailto:cctech-boun...@classiccmp.org] On Behalf Of ben via cctech >Sent: Thursday, May 25, 2017 1:32 AM >To: cctech@classiccmp.org >Subject: Re: Kryoflux or Catweasle > >On 5/24/2017 7:19 PM, allison via cctech wrote: > >> I have a load of all of those... 2901Cs the faster ones. The 2901 tends >> to force >> the flavor of the hardware and instructions toward microcoded machine. > >But if you want 9 or 18 bits, 2901 is not the answer. >A 74181 can be tricked in to being used as 3 bit alu. > > >Ben. Can you tell more about the 3-bit trick? - paul