> From: Earl Evans
> I have a BA11-N mounting box with Q18 9-slot quad-height backplane.
> The power supply is toast.
Toast, how? Physically mangled, or just not working? If the latter, it
might be possible to fix it. (Even if you're not up to that, don't pitch
it - someone else might be interested in it as a repair item.)
The other thing you could do is install a BA11-S power supply (H7861); some
are available on eBay. They are compatible (physically/electrical interface),
the H7861 just has a few more amps of +5V.
Noel
Sincere Greetings
This is a quick email to remind you that DEC Legacy 2015
<http://wickensonline.co.uk/declegacy/> is just around the corner!
I've recently updated the web page with some exciting presentations and
demonstrations <http://wickensonline.co.uk/declegacy/presentations>including
the following topics:
*VAX MP - Simulating a SMP VAX*
*Mark Wickens, DEC Legacy Organiser*
*Unearthing an important historical computer at the computer sheds museum*
*Jim Austin, The Jim Austin Computer Collection*
*Video Presentation*
*Bernd 'vaxman' Ulmann*
*An Update from the Living Computer Museum*
*Rich Alderson, Senior System Engineer*
*The MCPRINT Utility, 30 years in the making*
*Malcolm Blunden, retired VMS Systems Manager*
*The Future of VMS *
*Sue Skonetski, VP of Customer Engagement, VMS Software*
*Getting the DEC experience on modern hardware*
*Peter Allan, ex VAX system manager and VMS programmer*
*HECnet - A worldwide DECnet network*
*Mark Wickens, DEC Legacy Organiser*
... and there will be more yet to come.
We also now have quite an impressive list of exhibits
<http://wickensonline.co.uk/declegacy/hardware> which I expect to continue
to grow throughout the next month. Whatever your favourite era of DEC kit
you are sure to find something of interest.
The registration page <http://wickensonline.co.uk/declegacy/register> allows
registration for a single day or the whole weekend.
Please come, join in and experience the best computing equipment from the
best manufacturer!
Kind regards,
Mark Wickens
*Event Organiser*
p.s. please forward this email to anyone else you think might be interested
in attending!
Glen Slick <glen.slick at gmail.com> wrote:
> What is an HP 82306C GPIO Interface? Is that the same as thing as an 82306A?
>
> http://www.hpmuseum.net/display_item.php?hw=1111
> http://www.ebay.com/itm/281557879632
Probably close but not identical. The datasheet (catalog page actually, http://www.premerec.com/pdf/hp11835a.pdf, English version on second page) for the 11835A Data Buffer I have explicitely calls for the C suffix card - but maybe just because it was the current variety at that time. I got the device from a surplus outfit figuring it might come in handy one day, say for demonstrating or debugging bit-serial circuitry, as it can spew out bits at an arbitrary rate between zero and about 4 MHz. It has two banks of 1024 Mbits data memory each that are alternately loaded from the computer and read for driving the serial output, plus some additional memory for configuring an internal state machine and driving auxiliary signals, originally intended for a frequency hopping synthesizer. Intended application for the device was mobile phone and related equipment development; my example came out of a Nokia R&D facility of in Oulu, Finland according to its inventory tag.
Sean Caron <scaron at umich.edu> wrote:
> Interesting... appears to be some kind of temperature controller... I found
> a NASA technical report that mentions it and discusses some of the specs;
> apparently it's based on the Signetics 2650A at 1.25 MHz and according to
> the spec sheet, it's designed to use standard 4-20 mA interface to
> instruments, etc.
>
> Maybe worth it if someone's looking to hunt down some 2650A CPUs and maybe
> some support chips for a vintage SBC project.
>
> http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19870004136.pdf
Thanks for the hints. File however doesn't load for me (from Germany).
Might not even take ripping the device apart and rebuilding it into an SBC - I find the case, display and keyboard quite nice and would be looking to preserve as much as possible of that. The provided keyboard and display (that look as if they're seven-segment, but might even be alpha-numeric "star" type) could be be quite sufficient for many an application - mostly depending on how much RAM and ROM and which sorts of I/O there are in, can be crammed into or hung off that box - to realize a hex monitor or whatever floats your boat.
So Long,
Arno
I picked up a really heavy line printer last week.
It is a General Electric TermiNet 340. My searches for doc
were not very successful. It seems to be a line printer
that prints 340 lines of 132 characters per minute!
At the rear side near to the floor is a large rectangular
connector. Lucky me, the previous owner had a connection
cable. It is a ribbon cable. At one side is the mating
rectangular plug, at the other side is an IDC header.
Is it possible that this printer is also sold by others using
a different name? So far I have not been able to find any
documentation. I'd love to get this beast operational!
Thanks for pointers,
- Henk
On Fri, Feb 20, 2015 at 7:22 AM, Shiresoft <ggs at shiresoft.com> wrote:
>
>
> > On Feb 19, 2015, at 11:35 PM, Chuck Guzis <cclist at sydex.com> wrote:
> >
> >> On 02/19/2015 08:23 PM, Guy Sotomayor wrote:
> >>
> >> Nope. It was (and still is) how I write code (sit down and compose at
> >> the keyboard). One of my old bosses at IBM once said "Yea, Guy just
> >> waves his hands over the keyboard and programs come out".
> >
> > That would have been impossible in my case, unless I had the most
> prodigious eidetic memory in history.
> >
> > Writing code almost always involved using an on-disk or -tape source
> code library. Even if it was new code, there were significant advantages
> to creating a library then modifying it as one progressed.
> >
> > One would typically work with a bound listing or listings and work out
> the control system directives to update the existing code base. Remember,
> this was in the day of batch processing with almost no access to
> terminals. Everything happened on the keypunch.
> >
> > So for one to remember all of the correction set IDs and sequence
> numbers for a group of programs or system programs would be more than
> impressive--it'd probably merit a vivisection.
>
> ;-)
>
> I never said that I didn't / don't use references while I write code.
> It's just that I don't write my code down first. Of course most of what I
> do is new (from scratch) rather than modifying existing code.
>
> When I first started at IBM because build time for our software was about
> a week, we'd fix bugs and such with patches. Folks in the lab would stop
> looking up the instruction encodings and would just ask me...I could do the
> assembly in my head...I'm sorely out of practice now. :-/
> >
>
My first (paid) programming job was in 6800 assembler, using the Motorola
EXORCISER system. It took hours (as in a major part of a day, longer than
the work day) to reassemble the entire code base, so we would patch the
program in the PROM programmer. We would, of course, back port the changes
in symbolic assembler to the source, and every few days just take the
downtime hit to rebuild the code base. Keep in mind that this was natively
hosted on a 6800 system.
Another interesting tidbit: its simple filesystem did not segment files and
reuse blocks, so you had to purge old versions of files, preferably before
a dozen or so files were lined up after it. In that case, it would tie up
the system for way too long while an old file was purged and all the new
files were packed into the recovered space, block by block. It was barely
a step above magtape.
One other note: there was a bug in certain mask sets that required a NOP
before you could set the interrupt mask. Since the ENTIRE memory/IO space
was 64k bytes, every byte was sacred, every byte was great, and if a byte
was wasted?.
--
Ian S. King, MSIS, MSCS
Ph.D. Candidate
The Information School
University of Washington
There is an old Vulcan saying: "Only Nixon could go to China."
Hello everybody,
stumbled across this while looking for a HP 82306C GPIO Card to go with my 11835 data buffer (hint hint).
Looks just old and arcane enough that it might be of some interest to the community here ;)
http://www.ebay.com/itm/251594970760 (no ending date given, BIN/OBO)
Micricon 823 Chassis Microprocessor 82306-3 Teleray NASA Research Lot of Two
No association whatsoever to the seller, not interested in bidding on the item (TWO units) myself. Then again, if somebody decides to go for it and wants to split up (provided this can be made into two reasonably complete units), we can talk. I'm in Europe but can effect PayPal payments and CONUS -> EUR shipping with some (reasonable) effort.
So Long,
Arno
On 4 March 2015 at 18:56, Todd Goodman <tsg at bonedaddy.net> wrote:
> * Guy Sotomayor <ggs at shiresoft.com> [150304 12:45]:
>>[...] I had several cases where one program needed a
>> specific version of a system library, another program needed a
>> *different* specific version of the library and the rest of the system
>> wanting yet a 3rd version of the same library.
>>
>> TTFN - Guy
>>
>
> After running into that particular package hell early on in my Linux
> experience, I switched to Gentoo linux where multiple versions of
> libraries can be installed at the same time and used by whatever
> software needs them.
>
> Todd
As can Debian, so I'm a bit surprised. It's straight forward on *nix-like
systems to have multiple run-time versions of a library. It's designed
for it.
The problem is when you need different *compile time* (aka development)
versions of a library, then you'll need to have different name spaces.
The remaining issue may be that the distro may not provide different
versions of all the libraries you need out of the box. Then there will
be additional
work. And that may or may not be more effort than it's worth, granted.
-Tor
Hi!
Anyone owning the service manual for an ADM-5?
Seems like this terminal is not as common as the ADM-3(A).
Couldn't find it on bitsavers or anywhere else :(
--map
--
Martin Peters
martin.peters at news.uni-stuttgart.de