Hi
I've just got to say that I'm not sure why I didn't
look in bitsavers for the data sheets. I think it
was that at first, I wasn't sure if it was
a Western Digital part or someone elses.
I can only claim stupidity. Google ready indexing
would have made the difference though.
Dwight
A simple citation of Blair/Maron will show much of what is wrong, even
though it is pre-WWW.
Blair/Maron:1985
D. C Blair and M. E. Maron: "An evaluation of retrieval effectiveness for a
full-text document retrieval system", Communications of the ACM, 28, pp.
280--299, 1985
I assume.
--
http://pi0959.kub.nl/Paai/Onderw/V-I/Content/history.html
is an interesting little overview (found with a Google search, of course :-)
I'm trying to help a friend locate a replacement tape drive wheel for an HP 9144 tape drive. He says that there's a hard roller inside the tape cartridge, and there's a softer (rubber?) roller in the drive that pushes against it, pulling the tape along. Apparently the softer rollers tend to turn to "goo" after many years. He's been working to recover some archived files from the beginnings of the company he works for, mostly for historical interest, and his last tape drive recently succumbed to the "goo" problem. Anyone have any replacement rollers that would be in any better shape, or any suggestions for alternatives? Thanks!
>
>Subject: Re: Datasheet or info for Fairchild uA3656D?
> From: "Joe R." <rigdonj at cfl.rr.com>
> Date: Thu, 19 May 2005 17:26:49 -0400
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
>
>>My Databooks and drawings from when I was designing with the beastie
>>says with +5 Vcc and -9Vdd all IO will be TTL compatable.
>>
>>FYI back in that time frame Signetics, Intel and Fairchild had a
>>DTL/TTL product in the 3xxx class numbering. For example:
>>
>> 3205 similar to 74138 may be differnt pinout
>> 3009 similar to 7432
>> 9602 onshot similar to 74123 however the 9602 was truly a better part.
>> 3404 8bit wide latch maybe similar to 74100 or 74373
>
> Correct but I still haven't found any Fairchild 36xx part numbers so I'm
>still not sure what these two parts are. Fairchild did build some memory,
>the ram was PN 3530 (I THINK!).
>
>
>>
>> 1101 256x1 Pmos (two voltages) and really slow (1.5us parts were the
>> fast ones)
>>
>>There were others but those appear on my drawing and those of the
>>MCS-8.
>
> Are you sure you're not thinking of the Sim-8? That's what's shown in
>the 8008 manual. If you have other drawings I'd like to get a copy.
>
The MCS-8 manual has the SIM-8 in it. The other two designs are mine
and on B sized blue line (they are ca1973ish). They used more contemporary
7400 stuff save for the 3205 (intel 8205 in 1980s or better 74LS138 which
all the same thing.). Nothing to wild, 2102 ram instead of 1101 and the
IO was a series of ports that drove a Burroughs Panaplex 32 char display
and a numeris and function keyboard. The application was serial frame
time encoding/decoding for 8Track commercial tape systems. Copying the
drawing would be a pita being B sized and very little per page (near
20 pages of drawings).
I keep wanting to build a 8008 system as I have a chip using current
(ca 1980s) parts for laughs. The problem is an 8048 can blow it's
doors off.
Allison
> It works surprisingly well but it still misses a lot.
If you want your ear talked off, ask someone trained in library science
what is wrong with Google searches.
>From: "Brian Wheeler" <bdwheele at indiana.edu>
>
---snip---
>
>I think the optimum format for doing this isn't a single file, but a
>collection of files bundled into a single package. Someone mentioned
>tar, I think, and zip would work just as well. The container could
Hi
tar yes, zip no!!!! Any form of compression will make recovery
difficult if there is a small amount of data lost in the middle
someplace. I have some disk that were nicely archived of some
FIG ( Forth Interest Group ) stuff, done by a well meaning
librarian, earlier. In handling, the one copy ( the other mistake )
got damaged. Now, all the bundled information is lost.
Do not compress! In fact I recommend human readable forms such
as HEX or octal, regardless of the media.
Dwight
Big thank you to whoever got my PDA history article on Slashdot! I was a
Slashdot virgin 'til now.
-----------------------------------------
Evan Koblentz's personal homepage: http://www.snarc.net
Also see http://groups.yahoo.com/group/midatlanticretro/
*** Tell your friends about the (free!) Computer Collector Newsletter
- 700 readers and no spam / Publishes every Monday / Write for us!
- Mainframes to videogames, hardware and software, we cover it all
- W: http://news.computercollector.com E: news at computercollector.com
> One extra caveat would be when listing page numbers both the printed
> page numbers and the PDF's declared page numbers should be included.
When I started building bitsavers, I didn't have an easy way to put the
page numbers on each page in the format they were in the original. Once
Eric had tumble working, I started bookmarking every page with the
'real' page number with the intent of fixing the PDF page to match.
> Al can decide if it should be text only, html, excel, etc.
ASCII space separated fields
Actually, I wasn't totally out of computing since January...
I built a 400+GB music archive at the radio station that I
do a weekly show at, and built the master indexes as text
files. They are post-processed into SQL form, but the original
data is all easily readable and editable.
It is really, really easy to manipluate the data later if you
do this.
> Just out of curiosity, is this program something you could use Al?
It isn't something I currently need. It would have been handy when I was
recoving some data a few years ago.
There are a lot of VMS data sets kicking around on tape, but no
inexpensive reliable recovery solutions in non-VMS environments.
