In my library of recent finds, along the same lines...
Microcomputer - Alalog COnverter Software & Hardware Interfacing
Interfacing & scientific data communications experiments
Microcomputer interfacing with the 8255 PPI chip
Interfacing to S-100 / IEEE 696 microcommputers
They're all quite fascinating.
From: The Adept <adept(a)mcs.com>
To: Discussion re-collecting of classic computers
Date: Wednesday, April 01, 1998 10:27 AM
Subject: Special book find today
>A friend I work with donated the following book to my collection today:
> VIC-20 Interfacing Blue Book, by V.J. Georgiou
Here's a possibly stupid question...
I may have mentioned it earlier, but I got a copy of PDPXASM and I'm playing
with it. Just pitching code at the 11/83 to see what I can make it do...
Anyway, I'm playing with telling the RL02 what to do.
Push the head around, write things, etc...
Anyway, Is there a way to, given the the sector number, figure the head/cylinder/sector? Also, is there some mechanism to keep me from screwing up and sending
the heads below track 0 or past 512?
By the figuring CHS question, I mean this: I want to make a single routine
I can call to position the head whereever and dump a sector to disk, but I
don't want to have to know the disk geometry to do it. I pass to it
a unit number, RAM start address, and a sector number. Now how do I divide
the sector number to get the C/H/S? And I don't want to have to use
floating-point to do it...
> From: Daniel A. Seagraves [mailto:DSEAGRAV@toad.xkl.com]
> Subject: ANyone have DHV11 docs?
> Anyone have docs for the DHV11? Does it emulate a DH11?
> (It's the Q-bus 8-line MUX)
> I'd like to figure out how to tell mine what to do...
I might have a DHV11 manual around, I'll have to check. I do have a
board in an old uVAX II. Do you need anything in particular? Like the
CSR and interrupt switch settings? As I recall, the Q-bus DHV isn't
quite the same as a the Unibus DH11, but it does use DMA, much faster
than a DZQ11. The DHV11 uses floating CSRs, do you know how to set
them? (I assume you are going to use VMS)
I have the following for those interested:
Two 19mb and a 10 mb Computer Memories hard disks 5.25" full height all
have very bad stiction and and two are bad...
Why would anyone want these? The logics are good and they have a R6522
and MC6803P in sockets. The 6803 is a 6800 with a few enhancements like
internal ram, timer, serial and parallel IO and also bus for external
program rom and ram.
Or maybe someone would want to see the inside of a hard disk.
If interested contact me.
At 05:58 PM 3/30/98 -0800, you wrote:
>I'm curious to know how people deal with old data found on systems
>they rescue/restore. The question was put in my mind recently by
The way I see it, if they want to make sure the data doesn't get out, they
need to delete files.
But, I wouldn't take someone's personal spreadsheet of their monthly
finances and post it on the 'net, either.
What I've done in the past is look at it, and then generally delete it.
Why? Because it's generally boring as hell.
Now, if I came across some Hubble stuff, and I knew how to use it/what it
meant, I'd probably hang on to that. But only for my own personal
As I see it, when someone gives you a computer with data on it, they're
giving you the data as well. However, they're not giving you license to
sell that data to the Weekly World News.
I'm working with Long's Drugs, a chain of pharmacies on the west coast. If
I poked around in the store databases and told you that, say, Grace Hopper
was taking birth control pills, that would definitely be an invasion of
privacy. (and would likely get me thrown in jail.) However, there's
nothing wrong with telling you that there are 13 women who go to the
Serramonte store to get birth control pills.
Same thing with e-mail, word processing documents, spreadsheets and the
like. If your buddy Joe gives you his old computer, you should go poking
around his old e-mail or wp files. If, however, you get a computer from
company x that was used by employee y that you don't know, the data is only
I think generally, it's a moot point because it's usually too uninteresting
to keep around.
Uncle Roger "There is pleasure pure in being mad
roger(a)sinasohn.com that none but madmen know."
Roger Louis Sinasohn & Associates
San Francisco, California http://www.sinasohn.com/
On Mon, 30 Mar 1998 "Seth J. Morabito" <sethm(a)loomcom.com> wrote:
] I'm curious to know how people deal with old data found on systems
] they rescue/restore.
As one facet of this, we might consider what people would do with
their old systems, if they even got the *impression* that their
private information might be read by a new owner. They might
prefer to totally destroy the machine than to take a risk like
In this respect, the actions of each collector impinges on all of
us; it may take only one publicized breach of privacy to reroute
a lot of old boxes to trash compactors that would have otherwise
gone to collectors. It wouldn't even matter whether it was someone's
personal love letters or a company's records. The impact would be
With this in mind, I suggest we adopt the common policy of wiping
everything but obvious system software and such. There will always
be the practical matter of determining which is which, but it seems
best for all concerned to religiously respect privacy, irrespective
of whether it is that of an individual or an organization.
You forgot the traditional motivator: "...or it goes in the dumpster".
On Mon, 30 Mar 1998, Russ Blakeman <rhblake(a)bbtel.com> wrote:
] I have the full documentation package for the Plus+ HardCard 20 which
] If anyone thinks they can use these in the US I'd take $5 for the
] package which basically covers me shoving it in an envelope and mailing
] it to you. Drop me a note, first come first served.
A friend I work with donated the following book to my collection today:
VIC-20 Interfacing Blue Book, by V.J. Georgiou
Anyone seen this before? It is an incredibly neat book on hardware
projects for the VIC-20, including such things as Liquid Level Sensor,
ram expansion cards, eprom programmer for micromon, ring detector and
lots more. It is overall a superb text. If you would like more info,
let me know. I'm not interested in getting rid of the book but would be
willing to share via scans or photocopies. ;)
<I could have sworn the UK field servoids carried a normal 99MP kit with
<the Bristol Spline keys. No idea why as I've _never_ found such a screw
<in a DEC machine (although didn't the PDP1 have a Friden Flexowriter as
<the console ;-)).
No it didn't have splines in the kit. The only recent product that
required them was the LN01 xerographic printer, that used a bunch of
I have had some disks for a long time and would like to give them to
someone who has a need, a use, or even a clue as to what they are.
Three have hand-written labels
1: XYLOGICS 450
tar cvbf 20 /dev/rdvfo
2: XYLOGICS 450
tar cvbf 20 /dev/rdvfo
3: XYLOGICS 472
tar cvbf 20 /dev/rdvfo
I can't do anything with them on a PC, Norton won't let me see a
thing. I can see the sectors with my TI-99; #1 might not have valid
data, but 2 and 3 do. The second line of the labels might be 905
instead of 405 and rdvf0 instead of rdvfo. There may be nothing useful
on the disks, but...
The other disks are original (not too fancy) Intel disks:
4: SYP 286/300 DIAGNOSTICS 19 MB, #1A
DS/DD IRMX 86 FORMAT, 48TPI
PART NO. 174133-001
(c) 1982, 1983 INTEL CORP.
May not be copied without a license. Refer to price list for copying
#5, #6, #7 and #8 are identical except for the disk# and the part#:
5: #1B, PART NO. 174134-001
6: #2A, PART NO. 174135-001
7: #2B, PART NO. 174136-001
8: #2C, PART NO. 174356-001
If you want them, send an address, if they're not notable, I'll
reformat them. All, with the possible exception of #1, all have data
of some kind.
Barry Peterson bmpete(a)swbell.net
Husband to Diane, Father to Doug,
Grandfather to Zoe and Tegan.