I have a Documation D150 card reader that I am trying to make operational.
I fired it up today and ran a card through, only to have a big black
streak get "printed" to the card. I thought this was odd, so I opened it
up and found several problems.
The black streak was caused by the roller that pulls the card through the
slot. It's basically melted into a gooey ink-like mess. Actually, only
one side of it has melted. The other side is mostly intact, so I may be
able to just eliminate the melted side and still use this roller. It
looks like this:
__ __
| \/ |
==| |== <-- spindle
|__/\__|
^- one side melted
Then there is a rubber gasket that was around a disc that was situated
perpendicular to the way the card slides through. This roller dried up
and crumbled into several different pieces.
^
card goes in this way ---> and the rubber disk spun this way |
|
I think the purpose of this roller was to push the card against the guide
so that it goes through the reader straight.
Then there are two toothed belts driving cams from motors. One of them
got completely obliterated. The radial threads inside the belt got
wrapped around the drive cam and left a gooey residue on it. The other
belt is still in tact but very gooey, and is probably going to go at some
point as well. I was able to get this code off of it: SDP 6R6-055018C
I did a Google search but didn't turn anything up on this reader.
Does anyone know of a source to get replacement belts and parts for this
reader?
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
* Old computing resources for business and academia at www.VintageTech.com *
On April 12, Cameron Kaiser wrote:
> > Yeah. She's gonna get a flood of marriage proposals from dweebs
> > she's never met.
>
> Actually, she already does and has publicly lamented about this before.
Bummer. We should all have such problems.
> Did I miss where you asked if she was cute, keeping in line with your
> trademark theme? ;-)
I already know she's cute. :)
-Dave
--
Dave McGuire "Hush and eat your vegetables, young lady!"
St. Petersburg, FL - Mr. Bill
On April 12, James B. DiGriz wrote:
> > I wasn't going to mention it...but yes, quite cute indeed.
>
> Absolutely. The thing is, I look at her work, and I tend to forget or
> not care about that. I'm getting an inferiority complex, in fact.
Me to, for the latter anyway. I don't forget...it just makes me
wonder if she's single. ;)
> Bet she's dreading slashdot, though :-)
Yeah. She's gonna get a flood of marriage proposals from dweebs
she's never met.
-Dave
--
Dave McGuire "Hush and eat your vegetables, young lady!"
St. Petersburg, FL - Mr. Bill
> -----Original Message-----
> From: ard(a)p850ug1.demon.co.uk [mailto:ard@p850ug1.demon.co.uk]
> Here's how I'd do it (to make an 8 * 1 bit fusible-fuse PROM).
[snip]
> The way it works is like this. Normaly the Rd/Pgm relay is in the Rd
> state (as shown). In which case the sense relay is energised if the
> selected fuse is intact. You can use the contacts of the
> sense relay to
> turn on/off a light bulb or something.
Very close to what I imagined doing -- though, I hadn't gotten as far as
an address decoder. :) Thanks.
> To blow a fuse, select it with the decoder tree and then energise the
> Rd/Pgm relay briefly. Enough current will flow via the
> limiting resistor
> to blow the selected fuse. When the Rd/Pgm relay returns to
> the normal
> position, there will no longer be a path to ground for the
> bottom end of
> the sense relay, so this relay will not be energised.
Again -- a good plan. I was thinking about using a momentary switch
for programming anyway, rather than anything more complex, so that
fits exactly with what I wanted.
> I am going to _have_ to make one of these just for fun....
I'm glad that I'm not the only one crazy enough to consider trying it.
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
ard(a)p850ug1.demon.co.uk (Tony Duell) wrote (after Vassilis Prevelakis):
> > The built-in printer takes hp92261a print cartridges which (amazingly)
>
> Is this the Thinkjet cartridge (little clear plastic thing with a black
> rubber ink sack inside)? If so, then the printer electronics is likely to
> be close to the Thinkjet as well (see above for my comments on HPIL on
> this, etc).
Yes, the Integral takes Thinkjet cartridges. I think the Integral's
printer is just a Thinkjet repackaged to fit in the top of an
Integral, though it's been a while since I've looked at or inside an
Integral and lately my memory for these sorts of details has gone
to hell.
-Frank McConnell
I'm certainly not going to get involved in a discussion about PALs and
FPGAs, but if anyone wants to know more about microprogrammed machines,
I have a book which I will gladly trade for any interesting terminal
manuals. Beware, it's over 400 pages of machines I've never heard of.
Contents follows:
ACM Monograph Series
Foundations of Microprogramming: architecture, software and applications
Ashok K. Agrawala and Tomlinson G. Rauscher
Academic Press, Inc. 1976
ISBN 0-12-045150-6
Chapter 1 - Introduction to Microprogramming Concepts
1.1 Basic Computer Organization
1.1.1 Basic Hardware Resources
1.1.2 Control of Primitive Operations
1.1.3 Generation of Control Information
1.2 Evolution of Microprogramming
1.3 A Simple Microprogrammble Machine - An Example
1.4 Microprogramming and Programming
1.5 Microprogrammability
1.6 Microprogramming, Microprocessors, and Microcomputers
Chapter 2 - Architectural Characteristics of Microprogrammed Computers
2.1 Introduction
2.2 Hardware Components
2.2.1 Overview of Hardware Components
2.2.2 Control Store Design
2.2.3 Arithmetic and Logic Unit Design
2.2.4 Local Store
2.2.5 Main Memory
2.2.6 Data Paths
2.2.7 Summary of the SMM
2.3 Microinstruction Design
2.3.1 Introduction
2.3.2 The Vertical-Horizontal Characteristics
2.3.3 The Encoding Characteristic
2.3.4 Microinstruction Design for the SMM
2.3.5 Microinstruction Sequencing
2.3.6 Residual Control
2.3.7 Control Store Literals
2.4 Microinstruction Implementation
2.4.1 Introduction
2.4.2 The Serial-Parallel Characteristics
2.4.3 The Monophase-Polyphase Characteristics
Chapter 3 - Microprogramming Languages and Support Software
3.1 Introduction
3.2 Microprogramming Languages and their Translators
3.3 Simulators and their Implementation
3.4 Computer Description Languages
Chapter 4 - Computers with Vertical Microinstructions
4.1 Introduction
4.2 The Standard Logic CASH-8
4.2.1 CASH-8 Background
4.2.2 CASH-8 Architecture
4.2.3 CASH-8 Microprogrammability
4.3 The Burroughs B1700
4.3.1 Burroughs B1700 Overview
4.3.2 B1726 Architecture
4.3.3 B1726 Microprogrammability
4.3.4 B1726 Microprogramming Language
4.3.5 Sample B1726 Microprograms
Chapter 5 - Computers with Diagonal Microinstructions
5.1 Introduction
5.2 The Hewlett-Packard HP21MX
5.2.1 HP21MX Background
5.2.2 HP21MX Architecture
5.2.3 HP21MX Microprogrammability
5.2.4 HP21MX Microprogram Examples
5.2.5 Additional HP21MX Features
5.3 The Digital Scientific META 4
5.3.1 META 4 Background
5.3.2 META 4 Architecture
5.3.3 META 4 Microprogrammability
5.3.4 META 4 Examples
5.4 The INTERDATA Model 85
5.4.1 INTERDATA Model 85 Background
5.4.2 INTERDATA Model 85 Architecture
5.4.3 INTERDATA 85 Microprogrammability
5.4.4 INTERDATA 85 Microprogram Example
5.5 The Microdata 3200
5.5.1 Microdata 3200 Background
5.5.2 Microdata 3200 Architecture
5.5.3 Microdata 3200 Microprogrammability
5.5.4 Microdata 3200 Microprogram Example
5.6 Other Computers with Diagonal Microinstructions
5.6.1 The Datasaab FPU
5.6.2 The MLP-900
5.6.3 The CONTROL DATA 5600
5.6.4 The Data General ECLIPSE
Chapter 6 - Computers with Horizontal Microinstructions
6.1 Introduction
6.2 The Cal Data Processor
6.2.1 Cal Data Background
6.2.2 Cal Data Architecture
6.2.3 Cal Data Microprogrammability
6.2.4 Cal Data Microprogram Example
6.3 The PRIME 300
6.3.1 PRIME 300 Background
6.3.2 PRIME 300 Architecture
6.3.3 PRIME 300 Microprogrammability
6.4 The Varian 73
6.4.1 Varian 73 Background
6.4.2 Varian 73 Architecture
6.4.3 Varian 73 Microprogrammability
6.4.4 Additional Varian 73 Features
6.5 The Nanodata QM-1
6.5.1 QM-1 Background
6.5.2 QM-1 Architecture
6.5.3 QM-1 Microprogrammability and Nanoprogrammability
6.5.4 QM-1 Examples
6.6 The Burroughs Interpreter
6.6.1 Interpreter Background
6.6.2 Interpreter Architecture
6.6.3 Interpreter Microprogrammability
6.6.4 Interpreter Examples
6.6.5 Interpreter Applications
6.7 The Argonne Microprocessor (AMP)
6.7.1 AMP Background
6.7.2 AMP Architecture
6.7.3 AMP Microprogrammability
6.7.4 AMP Example
6.7.5 AMP Experiences
6.8 MATHILDA
6.8.1 MATHILDA Background
6.8.2 MATHILDA Architecture
6.8.3 MATHILDA Microprogrammability
6.8.4 MATHILDA Example
6.8.5 Additional MATHILDA Features
Chapter 7 - Developments in Microprogramming Languages
7.1 Introduction
7.2 Register Transfer Microprogramming Languages
7.3 Higher Level Machine-Dependent Languages
7.4 Higher Level Machine-Independent Languages
7.5 An Evaluation of Developments in Microprogramming Languages
Chapter 8 - Applications of Microprogramming
8.1 Introduction
8.2 Emulation
8.3 Program Enhancement
8.4 Executing Higher Level Language Programs
8.5 Operating Systems
8.6 Signal Processing
8.7 Graphics
8.8 Microdiagnostics and Fault Tolerance
8.9 Other Applications of Microprogramming
Chapter 9 - Perspective
9.1 Overview
9.2 The Past
9.3 The Present
9.4 The Future
9.5 Concluding Remarks
On April 12, Gene Buckle wrote:
> > > > the I/O is custom PLD logic that is impressive, if it is standard logic
> > > > chips, that is great that he could find the chips in prototype
> > > > quantities.
> >
> > > It's not a he, it's a she. :)
> >
> > or inbetween ?
> >
> Not a chance. From the pictures at http://www.commodoreone.com, she's a
> cute little wisp of a girl. :)
I wasn't going to mention it...but yes, quite cute indeed.
-Dave
--
Dave McGuire "Hush and eat your vegetables, young lady!"
St. Petersburg, FL - Mr. Bill
> -----Original Message-----
> From: Ben Franchuk [mailto:bfranchuk@jetnet.ab.ca]
> The main reason I have never played with them is I could never find a
> Fuse Prom Burner schematic that looked reasonable. I still
> would like to
> do a TTL computer with fused based proms ( or EEPROM's as modern
> substitute )for control logic. I am just finishing up a nice
> FPGA design
At one point I considered making an "illustrative project" of building
a pseudo fuse blown PROM out of several inline type fuses -- like are used
in power supplies, for instance.
It would be possible to illustrate not only electronically, but visually,
the way that the ROM works. :) "The black ones are 0s... ;)" (or is that
a 1?)
Anything beyond a size of several bytes would be unmanageable, of course.
I figured you might fit 64 bytes in the size of a VHS tape if you use
small fuses.
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'