>DEC's customer runnable MicroVax stuff was fairly lame though.
Generally, if you can boot the diagnostics on a Microvax, you
know that the Microvax is OK. Yep, pretty useless, considering
that if you can't boot VMS, you can't boot the diagnostics.
The PDP-11 based diagnostics were much more flexible. You could
load from paper tape if your disk or tape drive system was sick. You
didn't need interrupts or even DMA operational to load them, so you
could do some basic tests on a box that didn't even have full
backplane continuity!
Tim.
I have the teacher's edition of 'Computer Fundamentals with BASIC
programming', copyright 1986. It's in the form of pages to be inserted
into a binder. Does anyone want this?
--Max Eskin (max82(a)surfree.com)
At 03:37 AM 4/8/99 -0700, Sellam wrote:
>On Thu, 8 Apr 1999, Mike Ford wrote:
>
>> Coincident with all this chatter on floppy drives I have run into a streak
>> of uncooperative drives. I happen to be using macs with 3.5" Sony
>> mechanisms, but my question is somewhat general. What do you do with floppy
>> drives that need repairs?
><...>
>> Do any of you fix your floppies?
>
>Yes. As much as I can at least. The drive electronics are beyond me but
>mechanically I can mend most problems. The issue with the Mac drives
>usually tends to be the lubricant that gets gooey over time. You must use
>an electronic cleaner like Blue Shower or similar to wash away the gooey
>lube, then re-lube it with a suitable lubricating element (I don't
>know...sewing machine oil?) This usually unsticks the eject mechanism.
HP (sony made) floppy drives have the same problem. They stick part way
open and don't eject the disk. If you pull the disk out, you WILL rip the
top head off of a double sided drive. Never take a disk out or put a disk
into a partially open HP floppy drive. Take the drive out and clean the
old lube off so that it opens properly.
Joe
> On Thu, 25 Mar 1999, KNIGHT G.A wrote:
>
> > http://www.nwfl.net/haynesdl/requests/games-a-rottin.JPG
> > if ever you're wondering if saving computers from the scrap
> > heap is the right thing, check out this link. It's rather a
> > sorry sight.
>
Ow! I'm also a bit of a video-game restorer (presently my best example
is a fully restored Gorf), but I've done more to help a friend of mine
than I have for myself. At one point, my friend needed some AMD 2901's
which are used in the 16-bit math co-pro for Battlezone. We had a pile
of dead VAX-11/730 boards at work (self-maintained), so I desoldered
some 2901's for him and he was so happy to have VAX parts in his video
game. (I still have that 11/730; it was the first machine I ever installed
UNIX on, Ultrix 1.1; we used it at work for Usenet before the Great Renaming)
Every once in a while, I still go to video-game auctions. It is possible to
pick up full-sized games for under $100 if you don't want the hottest games.
PacMac, Galaga and other classics are still available, but for big bucks.
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
> "In programming, it doesn't matter how well it runs or does it's job.
The
> bottom line is, 'can we sell it to someone?'"
Terrible as it seems, that is a cold hard fact.
I'm not sure why everyone thinks that MicroSoft's goal is to build good
software. Their ONLY goal is to make money! I don't think anyone can
dispute their success at doing that.
So, how many billionaires has Linux created?
Steve Robertson - <steverob(a)hotoffice.com>
Late in Februrary I pulled out of a corner of my workshop a box containing
my old Mark-8 computer, the one whose construction was the subject of the
cover of Radio Electronics magazine in July 1974. I hadn't looked at in
over 22 years! Ah, the memories...
When I first read the RE issue, I was in no position financially to purchase
anything but the plans ($5 and a SASE, IIRC), being a poor college student
(of computer science). It was not until the fall of 1976 that I was able to
buy an already constructed Mark-8 from someone who was selling it because he
was upgrading (buying a newer microcomputer). I don't know who the original
owner was, as the computer was bought by a third party for me.
It was astounding to me that I owned my own computer! I proceeded to
experiment with it for weeks, hand assembling programs and then keying them
in through the front panel! But entering the code through the front panel
switches got old real quick, and I endevored to design and build an "octal
keyboard and display" for it. The original "backplane" made working on any
individual board a real problem: you had to "fan out" the boards to get at
the inside ones. So I attempted to make a backplane out of 100-pin wire
wrap sockets and bolting edge connectors removed from surplus boards onto
the edges of the six Mark-8 circuit boards. After all the work of rewiring
the boards with their new edge connectors and wiring the backplane, and then
building a new octal front panel board, the computer didn't work at all.
(Surprise! ;-) After some time trying to debug it with just a VOM, I
abandoned the whole project because I did not have access to the tools
(triggered 'scope, logic analyzer, etc.) that I realized I would need to
reasonably debug it. Of course there were some great new microcomputers
available that were faster and easier to use and program. I bought a KIM-1
and never looked back.
Until now.
So, I have been attempting to restore the Mark-8 to as close to original
condition as possible, which of course includes making it work! ;-). I am
pleased to announce that I've been successfull and I'm again the proud owner
of a working, .5MHZ computing colossus! I've removed the attempt at a
"backplane" and restored it to as close as possible to the origional
condition.
Originally the computer came with 1K ram, composed of 32 * 256 bit sram
chips (Intel 1101A and equivilents). I was dissapointed when I noticed that
1 of the ram chips was missing (I believe it failed, and I threw it out and
never replaced it). After getting the system to run with a minimum of 256
bytes, I used memory test routines to check out the remaining memories. I
found many more failures, which leaves me with 26 working memory chips. I'm
trying to locate more 1101A, so that I'll have enough for 1K and a few spare
ones too. Anyone out there have any 1101A or equivilent? (256 bit, pmos,
16 pin package +5V, -9V supply).
Another problem I had was a missing 8263 chip (Signetics dual 3-to-1
multiplexor) on the input mux board. I cannot remember why that chip was
gone, as the computer certainly wouldn't run at all without it. I probably
had removed it to test it, then lost it. I've found that the 8263 chip is
impossible to find and have subsequently replaced it with some 74XX chips.
I didn't have the data sheet, so I deduced its function by examining the
circuit. Only later did I realize that it had inverting outputs, requiring
a third chip (a 7404) to complete the replacement circuitry. If anybody out
there has an 8263 chip, I'd love to install it an get rid of the replacement
circuity.
During debugging, I found and replaced three other bad chips, all dealing
with the "bus" that I had tried to replace. The other problems were a
coupld of solder bridges and various broken connections, especially on the
"back plane", which gets flexed every time you fan open the boards in order
to access components on them. But the bottom line is.. IT WORKS!!!! And
I'm having a great time messing with it.
Now what?
In the short term, I'm installing the Mark-8 in an appropriate enclosure
with a modern switching power supply and fan. I plan on adding an EPROM and
UART to it. The EPROM will contain a bootstrap routine for performing a
memory check and a "monitor" routine allowing upload from the UART. I want
the UART and EPROM to be "vintage" parts (like the AY-3-1013 or COM 2052
UARTs, and 1702A EPROMs. Anyone out there capable of burning a 1702A (or
two) for me?
I also plan on using a cross-assembler or cross-compiler to write routines
for the Mark-8. I'm looking for Intel's PL/M cross compiler and
cross-assembler for the 8008. Apparently there also was an 8008 similator.
Intel has been suprisingly helpful in reproducing old manuals for the 8008,
but the source code for these old tools, THOSE are hard to find. All were
written in Fortran, and I understand that Gary Kildall wrote the CP/M
compiler. I figure that if I can get the sources, I could port them to the
PC. Anybody out there have these old software tools? I also heard that
there was a BASIC language for the 8008. Any help with that?
Anyone out there have a Mark-8?
- John Lewczyk
- IO Consulting
- 401 Queens Row Street
- Herndon, Virginia 20170-3131
- jlewczyk(a)his.com
> On Thu, 8 Apr 1999, Richard Erlacher wrote:
>
> > My contempt for Apple begins and ends with their total disregard for the
> > value of your data.
> > They designed the MAC with no memory parity assuming that you'd not mind
> > if your data was corrupted without your knowledge...
Multiple studies of memory reliability (DRAM) show that parity memory is
more prone to failure than non-parity memory. If you want reliability, you
have to go to something like Error Correcting Codes (ECC) like the big boys
use. We had 39-bit memory on a 32-bit VAX (11/750) because the extra seven
bits let you *detect* two faulty bits and *correct* a single bit failure.
The Sun Enterprise servers I babysit have ECC memory - we used to get one or
two failures in the machine room per year, but they were logged and corrected
without any loss of data. My Alpha board (AXP-133 "no-name" board) uses 72-pin
*parity* SIMMs in pairs to implement ECC on a 64-bit memory bit.
The problem with parity is that yes, you do know that you had a failure, but
now you have 9 bits that might fail, not 8, raising your risk by 12%. DRAM
failures are more often total rather than intermittent. A memory test at
power-up is a better insurance policy than relying on parity to save your butt.
I did have the parity circuit on a PeeCee cough up a lung once... it was even
a five-slot original PC (256K on M.B.). We were using it into the 90's because
it was merely the terminal for a Northwest Instruments logic/CPU analyzer that
we used to check for problems in our MC68000-based serial boards. One day, the
PC would not come up. Because everything was socketed and because I owned an
IC tester, we got a bottom-of-the-totem-pole tech grunt to pull each chip and
test it. It was a faulty 4164. Labor costs: $25. Parts cost: $0.60 for a
part
we stocked thousands of for one of our older products. I still have the
machine. It still works. I wish I had the invoice for that CPU; the company
bought it new in 1981, around $5K, I know, but I'd like to know the exact
figure.
Bottom line: Apple not using parity is not a reason to trash the Mac. How
many PCs have parity since we moved to EDO and SDRAM? It's extra cost and
extra complexity and extra possibilities for failure. Unless you can correct
the failure, it's not mathematically worth the extra expense and reduced
reliability.
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
I have just gotten an old GRiDCase 1530 running and now I need to rig some
things.
First the harddisc:
1) The manual says that it uses an IBM AT compatible harddisc. What's the
difference between an IBM AT style harddisc and an IDE? Is there anyway to
rig an adapter?
2) There's a floppy expansion plug on the back but I do not know the
signals needed for a generic floppy. Is there a web page with the pinouts,
signal directions and a signal description?
Thanks,
Arfon
----------------------------------------
Tired of Micro$oft???
Move up to a REAL OS...
######__ __ ____ __ __ _ __ #
#####/ / / / / __ | / / / / | |/ /##
####/ / / / / / / / / / / / | /###
###/ /__ / / / / / / / /_/ / / |####
##/____/ /_/ /_/ /_/ /_____/ /_/|_|####
# ######
("LINUX" for those of you
without fixed-width fonts)
----------------------------------------
Be a Slacker! http://www.slackware.com
Slackware Mailing List:
http://www.digitalslackers.net/linux/list.html
see imbedded comments below, please.
Dick
-----Original Message-----
From: Arfon Gryffydd <arfonrg(a)texas.net>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Friday, April 09, 1999 7:59 AM
Subject: Floppy and Hard disc questions....
>I have just gotten an old GRiDCase 1530 running and now I need to rig some
>things.
>
>First the harddisc:
>
>1) The manual says that it uses an IBM AT compatible harddisc. What's the
>difference between an IBM AT style harddisc and an IDE? Is there anyway to
>rig an adapter?
The PC/AT disk drive used the ST-506 interface (20-conductor data cable,
34-conductor control cable) and what was essentially a WD-1002 WAH
controller. The IDE interface is, from a software perspective, essentially
the same interface as what was used with the WD controller card. The
controller hardware has simply been migrated to the drive. Now, EIDE is
another bird. It has enhancements which make it less compatible with that
old firmware. It's advisable you try your Grid machine with an old disk
drive first before you fiddle with the drive adapter hardware.
>2) There's a floppy expansion plug on the back but I do not know the
>signals needed for a generic floppy. Is there a web page with the pinouts,
>signal directions and a signal description?
>
What you have to find out is what the pinout of that particular connector
is. There are lots of sources for standard FDD interface cable pinout.
>
>Thanks,
>
>Arfon
>----------------------------------------
> Tired of Micro$oft???
>
> Move up to a REAL OS...
>######__ __ ____ __ __ _ __ #
>#####/ / / / / __ | / / / / | |/ /##
>####/ / / / / / / / / / / / | /###
>###/ /__ / / / / / / / /_/ / / |####
>##/____/ /_/ /_/ /_/ /_____/ /_/|_|####
># ######
> ("LINUX" for those of you
> without fixed-width fonts)
>----------------------------------------
>Be a Slacker! http://www.slackware.com
>
>Slackware Mailing List:
>http://www.digitalslackers.net/linux/list.html
>> The only deliberately non-deterministic development tool I've ever used
was
>> a Xilinx FPGA fitter. Somehow it seemed reminiscent of the bogosort
>> algorithm.
>
>Don't get me started on the Xilinx tools. Suffice it to say, I spent
>enough time undoing the damage that they did to my designs. I hate
>computers that think they can design better than I can. They are almost
>always wrong ;-)
>
>-tony
>
My point, exactly. It is clearly the case that automated mechanisms are
inferior to a quality human intelligence. For anyone to think otherwise
is to relegate decisions of life to a computer program. As we all know,
or should all know, artificial intelligence falls _way_ short of its lofty
goals.
William R. Buckley
Yes, increasing the amount of memory by 1/8 increases the likelihood of
failure by 1/8. The inclination to bury one's head and ignore the potential
for memory or bus failure comes from the competition for price advantage on
the personal computer market, though. The argument I've heard is "if MAC'c
can live with it, so can PC's" which may not be true, but appears to be true
enough for the typical user.
Once such a memory failure is detected, there's nothing you can do about it
except endeavor NOT to save the data which may be corrupted and become aware
of the problem. I see memory parity errors (most of the PC's here use
parity or single bit error correction)
about twice a year. Normally it's when a new box is being brought up and
memories aren't seated right or something on that order. I don't know what
that says about the memory systems of today.
It's been a few years, but I always preferred single-bit correction over
parity in sizeable memory arrays. I designed one fairly large buffer memory
for Honeywell, which had 72-bit-wide memory, 64 MB deep, which was quite a
bit for that time (1991) with single bit correction only to have the manager
tell me it was not needed. "Whom are we helping with this added expense?"
was his position. I pointed out that it would make memory problems a depot
or even field repair whereas it would be a return-to-factory otherwise. He
insisted, though. The software lead and I agreed we'd base our memory check
on parity, which still allowed for isolation of the faulty SIMM. Since this
was not a main system memory but just a data buffer, it didn't matter that
it ws defective and firmware could rigorously isolate the faulty device.
I'm not sure what you're saying about the relative value of the extra bit of
memory versus the risk of promulgating a transient error into infinity by
recording it as though it were correct, Ethan. You seem to suggest that it
would have been better not to have had the 60-cent memory part in place
rather than to find and repair it once its failure was detected by parity
circuitry. I doubt you believe that, however. It is true that the addition
of parity circuitry means that there is an elevated likelihood of failure
proportinal to the increased memory size. It is also true that parity
checking circuitry requires time to work, and can, itself, fail as well.
Increased circuit complexity does increase the statistical probability of
failure. ECC circuitry doesn't decrease the probability of memory failure.
It does decrease the amount of down-time resulting from it, and it avoids
the data loss and down-time associated with single-bit transient failures,
which are more common than hard failures.
I guess it's like automobile insurance. If you have assets you need to
protect, you buy it. If you haven't you don't. My assessment is that Apple
started with the assumption that you don't.
Dick
-----Original Message-----
From: Ethan Dicks <ethan_dicks(a)yahoo.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Friday, April 09, 1999 6:10 AM
Subject: Parity (was Re: stepping machanism of Apple Disk ][ drive)
>
>
>> On Thu, 8 Apr 1999, Richard Erlacher wrote:
>>
>> > My contempt for Apple begins and ends with their total disregard for
the
>> > value of your data.
>> > They designed the MAC with no memory parity assuming that you'd not
mind
>> > if your data was corrupted without your knowledge...
>
>Multiple studies of memory reliability (DRAM) show that parity memory is
>more prone to failure than non-parity memory. If you want reliability, you
>have to go to something like Error Correcting Codes (ECC) like the big boys
>use. We had 39-bit memory on a 32-bit VAX (11/750) because the extra seven
>bits let you *detect* two faulty bits and *correct* a single bit failure.
>The Sun Enterprise servers I babysit have ECC memory - we used to get one
or
>two failures in the machine room per year, but they were logged and
corrected
>without any loss of data. My Alpha board (AXP-133 "no-name" board) uses
72-pin
>*parity* SIMMs in pairs to implement ECC on a 64-bit memory bit.
>
>The problem with parity is that yes, you do know that you had a failure,
but
>now you have 9 bits that might fail, not 8, raising your risk by 12%. DRAM
>failures are more often total rather than intermittent. A memory test at
>power-up is a better insurance policy than relying on parity to save your
butt.
>
>I did have the parity circuit on a PeeCee cough up a lung once... it was
even
>a five-slot original PC (256K on M.B.). We were using it into the 90's
because
>it was merely the terminal for a Northwest Instruments logic/CPU analyzer
that
>we used to check for problems in our MC68000-based serial boards. One day,
the
>PC would not come up. Because everything was socketed and because I owned
an
>IC tester, we got a bottom-of-the-totem-pole tech grunt to pull each chip
and
>test it. It was a faulty 4164. Labor costs: $25. Parts cost: $0.60 for a
>part
>we stocked thousands of for one of our older products. I still have the
>machine. It still works. I wish I had the invoice for that CPU; the
company
>bought it new in 1981, around $5K, I know, but I'd like to know the exact
>figure.
>
>Bottom line: Apple not using parity is not a reason to trash the Mac. How
>many PCs have parity since we moved to EDO and SDRAM? It's extra cost and
>extra complexity and extra possibilities for failure. Unless you can
correct
>the failure, it's not mathematically worth the extra expense and reduced
>reliability.
>
>-ethan
>
>_________________________________________________________
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
Careful, now! He would have played hell trying to interleave memory
accesses between an 8080 and the video refresh process, since its various
cycle types were so different. It would have been worse YET with a Z-80!
The 6502 also allowed him to proceed with his own DOS and his OWN version of
BASIC, without which he mightn't have gotten the strangle-hold on the
personal-computers-in-business market. It's pretty hard to criticize his
choices, however little I liked the result from the standpoint of seeing it
as a tool, but his (and his partner's) decisions were definitely vindicated
in the marketplace.
Dick
-----Original Message-----
From: Ward D. Griffiths III <gram(a)cnct.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 10:34 PM
Subject: Re: stepping machanism of Apple Disk ][ drive (was Re: Heatkit 51/4
floppies)
>On Thu, 8 Apr 1999 allisonp(a)world.std.com wrote:
>
>> Actually there are two points. One is track 000 and the other is the
>> innermost (for sa400 35-40 tracks later). Only track 000 was sensored
>> save for apple didn't use that either. Apple cut the interface to the
>> minimim number of wires and signals possible and made up the difference
>> with software, rather clever in my mind.
>
>During the design phase, Woz had more time than money, chips cost money
>and software only cost time. Remember that he _wanted_ to use the 8080
>but the 6502 cost only a tenth the price. (Imagine what the Apple
>might have been like with a decent CPU from the start).
>--
>Ward Griffiths
>"the timid die just like the daring; and if you don't take the plunge then
>you'll just take the fall" Michael Longcor
>
--- Roger Merchberger <zmerch(a)30below.com> wrote:
> Once upon a midnight dreary, Ethan Dicks had spoken clearly:
>
> >Every once in a while, I still go to video-game auctions. It is possible to
> >pick up full-sized games for under $100 if you don't want the hottest games.
> >PacMac, Galaga and other classics are still available, but for big bucks.
>
> Where? I'd like to pick up a video game (over 10 years old -- something
> like "Time Pilot" or somesuch, so this *is* on topic... ;-), but where I
> live nothing like that is available.
As I said, in my area, there is a company that has a rolling road show
that auctions off games and ordinary people and companies alike can buy
and sell. I no longer have the contact info for the auction company
since I haven't been to an auction in long enought that they have dropped
me from the mailing list.
> Also, is there a web (or other) reference as to what games used which
> processors? I think several games used the Moto6809, and if I had my
> druthers, I'd get a game based on that processor, as it's my favo[u]ite.
I would think that some of the arcade emulation sites would have that
info as it pertains directly to what you can emulate. I don't have
any sort of list, but I can say that Gorf and Wizard 0f Wor use the Z-80
and many Atari games use the 6502.
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
>How one place characters on terminal, give examples of terminal
>coding as sent from computer to terminal?
>
>-outputting characters to screen?
Say you want to print the character 'W'. You put the letter 'W'
into the accumulator, and tell it to output to the serial port.
>-resetting cursor to different places?
For a truly portable interface, you use a mix of carriage returns,
line feeds, and spaces/tabs to put the cursor where you want. If
you know you'll have a VT52 or VT100 or ADM3A or (insert generic
type of terminal here) you can send a specific character sequence.
If you're going to be eventually turning this machine into a CP/M
platform, I heavily recommend that you read the copy of your "CP/M
Customization Guide" that shipped with your CP/M distribution.
You'll find the terminal output/input routines explicitly coded as
an example in that book.
>Which CPU is very friendly for creating basic codings to put into
>ROM and assembling? Z80? or suitable CPU?
Just about anything. The Z80 certainly is a popular and easy-to-interface
to choice.
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
----------
> From: Robert Lund <lundo(a)interport.net>
> To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
> Subject: Re: Microsoft is about to arrest me!
> Date: Friday, April 09, 1999 1:45
>
> Oh, god! Does Lord Gates now even have his own police force??
Nothing would surprise me.
> Supreme Court battle ahead of you to get out of MS Jail.
I thought MS Jail was Windoze 9x/NT? You get in to it then it locks up?
Cheers
Geoff Roberts
VK5KDR
Computer Systems Manager
Saint Marks College
Port Pirie, South Australia
geoffrob(a)stmarks.pp.catholic.edu.au
The disk drive has a place beyond which its head assembly won't move. If
you've ever written FDC code, you know what it sounds like when you try to
go beyond the limit. What's more, there's a sensor to tell you when you're
at that point, though I doubt Apple used it. It's just as easy to move the
heads until you're sure they've gone as far as they can. Once you've done
that, what better way could there be than to look for a track and then
adjust until the signal is readable? That's how drives of all sorts work
today. Of course, they all have some way of establishing where a track
ought to be to begin with.
Dick
-----Original Message-----
From: Max Eskin <max82(a)surfree.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 8:53 PM
Subject: Re: stepping machanism of Apple Disk ][ drive (was Re: Heatkit 5
1/4 floppies)
>On 8 Apr 1999, Eric Smith wrote:
>>> These fellows
>>> spent a couple of sessions talking about and demonstrating the screwy
means
>>> by which certain game vendors in the Apple market were "protecting"
their
>>> wares by altering the timing of the positioning routine, thereby making
it
>>> possible to write tracks "off the track" by changing the time delay
between
>>> a known cylinder position and the point at which the specific track was
to
>>> be written. This made it impossible for someone using the stock timing
of
>>> the positioning mechanism to read the diskettes so written.
>
>How does this work? Do you mean that the disk drive has no internal means
>of judging whether or not it's on the right track and that this is
>determined by the contents of the disk?
>
> --Max Eskin (max82(a)surfree.com)
>
In a message dated 08/04/99 15:36:36 Eastern Daylight Time,
mikeford(a)netwiz.net writes:
<< When you say not reading, is it;
Fails to spin at all, so all discs are immediately rejected?
Doesn't reliably read? My wet cleaning floppy often helps this case.
I have a few diagnostic programs, and I think it is TechTool Pro that will
do a full drive test, with a 0% to 100% rating that fairly accurately ranks
condition of drives. A few of the refurb places sell drives using this
rating, with a 90%+ drive fetching a 100% premium over just a working drive.
>>
well, my mac IIcx had a drive that wouldnot eject disks. the grease had
gummed up so i used an aerosol cleaning product and cleaned all that out and
used moly grease to fix the stickiness. i also ran a head cleaning disk in
the drive for several minutes and amazingly got the drive reading disks
again. my IIx will spit disks out ok but refuses to read known good mac
formatted floppies. that was cleaned with a head cleaning disk as well but no
improvement. unfortunately, the IIx only has one drive instead of two. I
recently got a IIci (nice machine!) and it works great, but there seems to be
a drive alignment problem. disks formatted on the cx wont always read right
on the IIci. seems that i have to use one external floppy between both macs
in order to get 800k disks to be read reliably. grrr.
A reasonable example of how to do these things would be available in the IBM
PC Technical Reference, since their display boards used the 6845. The
scheme is based on the notion of SHARED memory. The processor writes to the
video memory, or to the character memory, and the 6845, once initilized,
generates the cursor, and scans through memory at the proper rate to effect
display of the content. Unfortunately, Motorola unfortunately didn't
include a delay stage to allow for translation of ASCII data to video, so an
external latch has to be used to delay sync and blanking by a character
clock period, which means you might have to accomodate that in your sync
timing as well. it means there will be a 1-character period offset between
blanking and character video while the graphics will be "right on."
-----Original Message-----
From: jpero(a)cgocable.net <jpero(a)cgocable.net>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 11:28 PM
Subject: Re: homemade computer for fun and experience...
>On my homebuilt computer quest.......
>
>There's two groups:
>Built in video and serial i/o to terminal attached concepts.
>
>Can you explain the process to "init" and operate video chip based
>on 6845 chip with own ram ? Possible to use SRAM with it?
>Is there CPU specific limitations?
>
>I have many of them and certainly get put in use on computer.
>
>And alteratives:
>
>How one place characters on terminal, give examples of terminal
>coding as sent from computer to terminal?
>
>-outputting characters to screen?
>-resetting cursor to different places?
>
>Which CPU is very friendly for creating basic codings to put into
>ROM and assembling? Z80? or suitable CPU?
>
>Thanks!
>
>Wizard
I think there may be a semantic problem at hand. The single-density (FM)
and double-density (MFM) modulation schemes operate on precisely the same
density of flux reversals at the media/head boundary. The difference is
that the FM imposes a flux reversal between every bit window, while the MFM
does not. What this means is that data encoded in MFM can be written to the
media at twice the rate as that at which FM is written without taxing the
media or read/write channel ordinarily limited to FM. There were some
improvements between earlier and later head designs, and media selected for
MFM were required to be better because the bits had half as much material in
which to be recorded. With MFM, if a clock was missing, which happened half
the time a transition was lost, it didn't necessarily make a difference
unless the controller happened to be looking for an address mark.
So, if your definition of "double density" means twice as many flux
reversals per linear inch, well, you're right, I guess, but that's not what
the industry meant when the called it double density. I meant the same
thing the rest of the folks in the business meant, i.e twice as much data
capacity on the same size medium.
It's the same with the difference between MFM and RLL hard disk drives.
There were a few drives which, as a matter of course, didn't work with RLL
encoding. I don't know why this was. I do know that if you use any of a
number of translation schemes, of which ANSI GCR is one, you generate a bit
stream which, though it uses more than half the channel bandwith to do so,
can be recorded at twice the transfer rate as the corresponding NRZ data
without allowing excessive accumulation of charge on the heads as would
occur if too many ones or zeroes in succession were recorded in NRZ. These
schemes don't require the complicated time domain filters and other "neat"
circuits commonly used in read/write channels of that time, and provided
sufficient densities of transitions to allow clock recovery. The ANSI GCR
translates 4 input bits into 5 recorded bits, and recovers them, and ensures
that there are enough transitions to allow clock recovery yet no two
adjacent cells have transitions. (?) I suppose this is easily achievable
with a PROM, and some folks use a state machine to accomplish the same task.
I used a prom. It was easy enough to translate 4 bits received at 5 Mb/sec
into 10 bits at 8 Mb/sec. A number of code sets have been developed over
the years for the purpose of exploiting such "compression" over digitized
voice channels, and many other comm channels.
Like I said, the Perscis are hangar queens. Like a BMW . . . in the shop a
week a month. That's a hyperbole, of course, but it seems that way when
you've paid what the things cost back then only to have to pay that much a
year again to keep it running. They were fast, though, and hard disks cost
a lot more than the Persci drives.
Dick
-----Original Message-----
From: CLASSICCMP(a)trailing-edge.com <CLASSICCMP(a)trailing-edge.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 9:03 PM
Subject: Re: stepping machanism of Apple Disk ][ drive (was Re: Heatkit 5
>>with positioning. They now use voice-coil actuators rather than steppers,
>>and therefore can make quite subtle adjustments in head-stack position
>>depending on what is read. Back in the early days, that wasn't so.
>
>Actually, Persci floppy drives in 1976 or so were voice-coil (and quite
>a pain to maintain, even then - these days the glue that holds the
>optical graticules in place is often failing, and gluing and realigning
>from scratch is even harder, even with all the special Persci
>realignment jigs and electronic panels.) And a common modification
>to these drives (at least for folks like me who specialize in data
>recovery) is software-controlled offsets from the normal track positioning,
>something that does use the drive's ability to do fine positioning.
>
>>One interesting thing about the Apple GCR modulation format is that it
>>essentially was a "double-density" technique.
>
>Eric said the same thing, and I disagree with you both. To me (and all
>the tech pubs I've read) the density is how many flux transitions you can
>do per second (or revolution). GCR is a way of getting more real data with
>the same number of flux transitions. Apple GCR drives use single-density
>heads and single density data rates, a considerable cost saving factor
>in 1977.
>
>>cost plenty back then. This was at a time when Radio Shack still stayed
>>with single-density, and Apple exceeded their capacity easily.
>
>While using cheap single-density drives!
>
>--
> Tim Shoppa Email: shoppa(a)trailing-edge.com
> Trailing Edge Technology WWW: http://www.trailing-edge.com/
> 7328 Bradley Blvd Voice: 301-767-5917
> Bethesda, MD, USA 20817 Fax: 301-767-5927
I don't feel it necessary to defend what was an obvious memory failure.
Eric Smith (much younger than I, and an Apple-owner, unlike me at the time,
hence more likely to have paid close attention to the discussion because it
affected him and his interests) has already pointed out that I must have
been suffering from "old-timer's disease" when coughing up the account of
those discussions, though I've corroborated the vague recollection with
another old-timer who was there at the time as well, but who also was not an
Apple-owner at the time.
Since the time of these discussions, I've had occasion to purchase, for a
pre-defined purpose, several Apple-II's, some of the wreckage of which and
one (maybe more) functional unit of which is serving as a doorstop or spacer
between shelves, or some such function. I've nonetheless NEVER looked
inside an Apple disk drive, nor have I pondered the schematics beyond
noticing that there were such things among the paperwork we got with the
half-dozen or so of these units. I never even got particularly familiar
with them. I'm certainly not an expert on Apple's hardware, software, or
anything else about them. I merely was attempting to recount what I seemed
to recall about a specific discussion I witnessed. Clearly the passage of
some 20+ years has muddled my recollection.
As for the tristate multiplexers, that was an error probably influenced by
the fact I'd just plugged a half dozen of them in to three S-100 memory
boards I'm giving to some guy in Minnesota who offered me something for
them, so I populated them with the requisite IC's, including the 'S257's. I
just looked back at the emails I've received in the past month, and couldn't
find the specific reference to the part in question, but I must have slipped
a couple of numbers in the course of replying to the email in which this
subject came up. If they are, indeed, '259's, then they are, as you
suggest, addressable latches.
Now, I'll hapily accept responsibility for having introduced some error into
the discussion of this topic. I guess I'm just going soft in the head. . .
That's clearly evidenced in the amount of time I've spent on the discussion
of Apple products.
Dick
-----Original Message-----
From: Tony Duell <ard(a)p850ug1.demon.co.uk>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 8:48 PM
Subject: Re: Heatkit 5 1/4 floppies
>>
>> Let me qualify this, first of all, with two bits of fact . . .
>
>I'll also post some facts. Actually, I'm suprised that nobody else has
>done what I've just done, and looked at (a) the Disk II circuit diagrams
>and (b) an actual Disk II. Neither are particularly rare.
>
>> (2) - I remember lengthy discussions among those members of the Denver
Area
>> 6502-Users' Group who were presumably qualified to discuss the
intricacies
>> of the internals of APPLE's disk I/O routines at a level I neither knew
nor
>> cared about, beyond the superficial details I gleaned from the several
and
>> varied sessions discussing that set of details. Now, I attended these
>> weekely and typically 4-hour long meetings for several years, and KNOW
the
>> guys who were hashing out the details of the hardware and software in
>> question knew what they were talking about, so I accept that as fact.
If
>> it wasn't true, no harm done, but I doubt that was the case. These
fellows
>
>If they claimed that the positioner was a normal DC motor and not a
>stepper, then I'm afraid they didn't know what they were talking about.
>
>Every Disk II that I have ever seen (and I've been working on them for
>some 20 years or so) has a stepper as the head positioner. The circuits
>show this, with a '259 addressable latch on the controller card to
>provide the drive signals and a ULN2003 on the 'analog board' to drive
>the windings.
>
>I'll believe that a drive with a DC motor positioner exists when somebody
>shows me one in operation, or provides reasonable evidence (schematics,
>software to drive it) that it exists.
>
>> The scheme with the tristate multiplexers came later, I believe, than the
>
>What tri-state multiplexers? I can't find a tri-state multiplexer in any
>part of the Disk II.
>
>> was among them. Having said that, I would point out that, given a
software
>> scheme sequenced the stepper, it is just as possible that one could have
>> read the diskettes written a half track off by fiddling with the stepping
>
>Indeed, and that was done for some copy-protection schemes.
>Quarter-tracks might be possible as well...
>
>> sequence. I doubt, however, that Wayne Wall would have allowed the waste
of
>> several sessions of the meetings he so firmly controlled back in those
days,
>> if the assumptions presented as fact in those discussions had not been
>> verified.
>>
>> The helical cam I remember didn't have a groove, but rather, a ridge or
>> "fence" in the shape of a helix, which was tracked by a small,
>> spring-loaded, roller bearing. This worked quite well, but, because of
>
>The one I have here has a groove. There's a ball bearing in that groove,
>with a spring leaf on top of it fixed to the head assembly. As the disk
>rotates, the ball bearing tracks along the groove and moves the head.
>
>-tony
>
Due to some kind of editing error, the Classic Computer Rescue
list has just the last few words of an entry from someone in New
Hampshire. The same problem exists in my backup copy as of about
a week ago, and there is no such entry at all in the backup from
several months ago. (Yes, I know, I should keep this in RCS. I
should do a lot of things.)
If your hunting grounds are Southern New Hampshire ("about an hour
north of Boston"), please take a moment to send me your new entry.
I'll try really hard not to mess it up again!
That URL again: http://www.cs.unc.edu/~yakowenk/classiccmp/ccrs_list.html
Operators are standing by. :-)
Thanks,
Bill.
Oh, god! Does Lord Gates now even have his own police force?? I think their
arrest powers would have to be severely limited - though you might have a long
Supreme Court battle ahead of you to get out of MS Jail.
--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Robert Lund | "So many good ones, and so many bad ones; +
+ lundo(a)interport.net | that's what you get for trying." +
+ New York City | Dutch Schultz, last words +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
There are also the "digital" alignment diskettes. These have certain forms
of misalignment intentionally written to certain tracks in a certain way.
Together with appropriate software, you can ostensibly detect, quantify, and
correct (if you know how and feel you can do it) whatever defects it finds.
I've read about this but never got around to trying it. I don't know anyone
who's tried it, so I can't even ask the relevant questions. Dysan made a
whole series of such digital diagnostic diskettes, as they were called, for
various types of disk drives. Unfortunately, they were priced such that it
was cheaper to buy a new drive than to buy one of these and the software and
fix it yourself. IIRC the price would have crossed over at about 50 drives,
not counting the labor savings, since I provided that.
The analog alignment process is quite straightforward, but not something I
want to do again. Moving the heads back and forth, then tightening the
screw holding the lead screw/motor in a fixed position only to have to
repeat the process because the changing stresses from tightening things down
has caused them to move . . . UGH! . . .
Dick
-----Original Message-----
From: Dwight Elvey <elvey(a)hal.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 4:53 PM
Subject: RE[2]: Fooling with floppy drives
>Steve Robertson <steverob(a)hotoffice.com> wrote:
>>
>> I've never used the DYSAN alignment disks and would be really interested
to
>> learn more about them.
>>
>> How effective are they?
>> What other tools do you need?
>> How much do they cost?
>
>Hi
> I've used alignment disks. You need an oscilloscope
>to use them. You also need to write a low level
>driver to keep the system from freaking when doing
>the actual alignment check. They record two signals
>on the disk that are 1/2 track above and below the
>normal track position ( I don't recall what track you
>select but as I recall, it is about half way up
>the disk ). The two signals are exactly 1 cycle
>per revolution of the disk different in frequency.
>You look on your oscilloscope at the analog signal
>that comes out of the read amplifier and adjust
>for what is call a cats-eye pattern. If the track
>alignment is right on, you'll have equal height
>signals from the first half of the revolution
>as the second half ( sync of the index pulse ).
> They also include a constant amplitude track. This
>is used to look for contact problems of the disk/head.
>One another track they usually have several different
>frequency tones recorded. These are used to check the
>band pass of the drive.
> Other than the cats-eye pattern, there is usually little
>that you can adjust on a finished drive. The cats-eye
>pattern can be used to fine tune the stepper position.
>There are usually some slotted screws someplace that allow
>slight changes in the rotation of the stepper. One does
>have to check the proper operation of the track zero
>sensor after this adjustment because there is interaction.
> As for price??? I bought the one I have at a surplus
>shop for $1.
>Dwight
>
Well folks,
The 8F is now up and basically healthy. The stuck bit was a bad 74L54
that had a stuck input. Shame the replacement I have is a year older than
the machine!
I ran one program that will execute on a DECMATE but the result is not
visible! ;)
/ TEST PROGRAM FOR pdp-8f
/ inchworm view with pannel switch set to Acc (8E/F/M)
/
0200 *0200 / start address
0200 7200 START, CLA /CLEAR ACC
0201 1211 TAD WORM /PUT WORM CHARACTER IN ACC
0202 7004 MAIN, RAL / PUSH THE WORM LEFT
0203 7000 DELAY, NOP
0204 7000 NOP
0205 2212 ISZ DELCNT /DELAY 4096 (~20MS) INNER
0206 5203 JMP DELAY
0207 5202 JMP MAIN
0210 7402 HLT
0211 0007 WORM, 0017 / FOUR BIT LONG INCH WORM
0212 0000 DELCNT, 0000 / INSIDE LOOP COUNT
0213 $
Next step is to get the terminal interface in and try it aand also verify
all of CORE as all I've checked is most of 00200, page 0 and random words.
Allison
> I recently got a IIci (nice machine!) and it works great, but there seems
to be
> a drive alignment problem. disks formatted on the cx wont always read
right
> on the IIci. seems that i have to use one external floppy between both
macs
> in order to get 800k disks to be read reliably. grrr.
>
To me, that is the most frustrating problem. I've got drives that only work
with certain disks, disks that only work with certain drives, drives that
only format certain densities. Grrr... I guess it could be that both
components (disk and drive) are slightly out of tolerance.
The end result is, I've got a stack of drives and don't really know if
they're good or not.
I've had some success by just cleaning the slides and positioning
mechanisms. The lubricants really attract the dust and will inhibit
movement of the heads. I generally like to use alcohol or another common
agent to remove the gunk. Blue Rain works great but, is kinda expensive.
You have to be careful not to wash all the lubricant out of the servo
bushings. Without any lubrication, they can wear out pretty fast.
Especially the spindle motors. I generally use a fine machine oil to
lubricate the moving parts. You can also use a very thin coat of vasoline.
At least it stays where you put it.
I've never used the DYSAN alignment disks and would be really interested to
learn more about them.
How effective are they?
What other tools do you need?
How much do they cost?
Steve Robertson - <steverob(a)hotoffice.com>
I'm with you on this one. I didn't make or wish it so. AlI did was state
how things are. There ought to be a way to fix these things, but since
their cheaper bretheren are available for the PC (throw-away) market, it's
hard to get someone to fix them for less than a new one costs. Keep in mind
that a guy who fixes them himself can do the job, but even an altruistic
fellow indeed would rather spend $25 to replace a drive than spend half a
day only to find he can't fix the $#@!! thing.
Many of the drives to which I refer have only a switch, a couple of optical
interrupters, and a single IC on board. . . . . . maybe a few resistors . .
. . . They're just not made to repair. Now, if you save a few, perhaps a
board swap can help, but be careful! Those high-density connectors
attaching the FLEX to the board aren't made to be cycled more than once.
They break!
Dick
-----Original Message-----
From: Sellam Ismail <dastar(a)ncal.verio.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 1:49 PM
Subject: Re: Fooling with floppy drives
>On Thu, 8 Apr 1999, Richard Erlacher wrote:
>
>> Since new floppy drives cost about $25 including shipment, it's difficult
to
>> justify repairing them. This is frustrating for people like you who have
>> drives for which replacements are not readily available for $20 or so.
>
>What? What if you don't have $25 laying around, or $25 * 12 = $300 as
>Mike says is his current number of broken drives. You don't just go and
>pull $25 out of your pocket everytime a drive breaks. The last I checked
>money still doesn't grow in the pasture (believe me, I check every
>morning).
>
>> Your experience with sloppy workmanship gives clear indication that $10
per
>> hour is not enough to pay a competent technician. The occasional look
>> inside should give you good indication of why one who can't spend more
than
>> 15 minutes' time fixing a $20 drive, can't get the job done. These
devices
>> must be considered "throw-away" items by now. You've got to learn to
>> fix-em-yourself.
>
>Well, exactly. That's why its called a hobby.
>
>Sellam Alternate e-mail:
dastar(a)siconic.com
>---------------------------------------------------------------------------
---
>Don't rub the lamp if you don't want the genie to come out.
>
> Coming in 1999: Vintage Computer Festival 3.0
> See http://www.vintage.org/vcf for details!
> [Last web site update: 04/03/99]
>
Is anywhere here in or near Houston? I need someone to retrieve and ship
a rather large set of items (non-computer related) to California for me.
I'll make it worth your while of course.
Please contact me privately. Thanks!
Sellam Alternate e-mail: dastar(a)siconic.com
------------------------------------------------------------------------------
Don't rub the lamp if you don't want the genie to come out.
Coming in 1999: Vintage Computer Festival 3.0
See http://www.vintage.org/vcf for details!
[Last web site update: 04/03/99]
--- Joe <rigdonj(a)intellistar.net> wrote:
> Ethan,
>
> Can you give me a list of machines that you know of that have 2901s? I
> know 2901s are in short supply. I'll try to find some in those old game
> machines.
Any of the Atari vector machines are likely to have 2901's as the core of
a math co-processor to manupulate those vectors faster than the little 6502
ever could. My friend Tony is the Atari vector king; I've never owned one,
unfortunately.
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Let's not confuse things here. Today, most disks use either a servo track
on an unused surface or they use embedded servo written right in with the
data they're storing. That certainly helps with speed control as well as
with positioning. They now use voice-coil actuators rather than steppers,
and therefore can make quite subtle adjustments in head-stack position
depending on what is read. Back in the early days, that wasn't so. In that
sense, it's fair to say that Apple was somewhat forward in their thinking.
Normally they only thought inward, hence, they did this because it saved
them money.
FM, MFM, RLL including GCR, are simply modulation schemes. They
characterize how the data is actually written on the track, but really
aren't involved in decoding the position when a track is being found. The
data format, however, customarily has extensive information allowing the
system to verify the current position of the head on the medium. A typical
sort of format layout would have a sync field, followed by an address mark
(a framing-sync character sort-of like the unique word used in HDLC and
other protocols) to tell the controller what's next, then a position
indicator data field to tell the system the current head and sector
information, then a CRC, followed by another sync field containing a write
splice (write turn-on gap) followed by a data address mark followed by the
data and its CRC and yet another sync field containing yet another write
splice(write turn-off gap). There are variations on this theme, but that's
basically what's there. The basic format is written in the "low-level"
format process while the data fields are written in the "high-level" format.
On old drives, the drive's internals don't care about the data. They just
transfer it. Newer drives, since they have to fiddle with the data in order
to set the data rate, manipulate the heads, buffer the data, correct the
errors, etc. care very much about and involve themselves greatly with the
media content. Hence, they rely less on hardware specifically in place to
yield position information.
Floppy drives, AFAIK, don't bother with this, though the ZIP and LS-120
drives may very well do so. They have a track-zero detector, and, normally,
that's what's used by the system to find track-00. Apple didn't even use
one of those because they could move the heads until it seemed reasonable
for one reason or another to assume track zero had been reached, perhaps by
reading where they were and then making an adjustment, or perhaps by moving
the head in one direction or the other until it had to be at the limit.
Then they could step inward until data was encountered, and could be
interpreted. Someone else will have to elucidate on that, however, because
although I know a fair amount about what they might have done, I don't
actually know what they did. How about it Eric? How dit they manage a
recal?
One interesting thing about the Apple GCR modulation format is that it
essentially was a "double-density" technique. It was cleverly implemented
in a way which saved on hardware, capitalized on software's ability to
exploit the time window normally spent waiting for a transfer, and,
especially, didn't wed them to one or another FDC chip maker. Those IC's
cost plenty back then. This was at a time when Radio Shack still stayed
with single-density, and Apple exceeded their capacity easily. Radio Shack
was the only major competitor Apple had. This was a real coup!
Dick
-----Original Message-----
From: Cameron Kaiser <ckaiser(a)oa.ptloma.edu>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 6:32 PM
Subject: Re: stepping machanism of Apple Disk ][ drive (was Re: Heatkit 5
>::> How does this work? Do you mean that the disk drive has no internal
means
>::> of judging whether or not it's on the right track and that this is
>::> determined by the contents of the disk?
>::
>::Basically, yes. The track and sector are stored in the sector header of
>::each sector, among other data.
>
>In fact, most floppy disk systems work that way. Commodore GCR does that.
>So does MFM, doesn't it?
>
>--
>-------------------------- personal page:
http://calvin.ptloma.edu/~spectre/ --
>Cameron Kaiser Database Programmer/Administrative
Computing
>Point Loma Nazarene University Fax: +1 619 849
2581
>ckaiser(a)ptloma.edu Phone: +1 619 849
2539
>-- FORTUNE: You will feel gypped by this
fortune. -----------------------------
Coincident with all this chatter on floppy drives I have run into a streak
of uncooperative drives. I happen to be using macs with 3.5" Sony
mechanisms, but my question is somewhat general. What do you do with floppy
drives that need repairs?
Normally I just put them aside, but after this week I have close to a dozen
in the defective box and ZERO (actually a negative number since I need even
more) reliable units that aren't already installed in other systems.
I have already performed the first aid procedures like cleaning the heads
(using a wet cleaning floppy), and disassembly down to the bare mechanism
and blowing out the bunnies with canned air. This pile is the hard core
rejects, floppy doesn't spin, floppy doesn't eject, which I guess means a
drive motor or support electronics is shot.
For perspective, Apple still wants like $150 for a new floppy, mail order
sources have the same for about $70, and reliable refurbs run the gamut
>from a low of about $20 up to $50 or more (used OK drives are $10 to $20.
and my last pesky supplier was asking $5 for untested pulls). What I am
finding disturbing is that more and more of the drives I see have OBVIOUSLY
been swapped from another machine, or show other signs of being opened up
by non techs (missing screws or other parts).
What are your opinions, practices, or sources?
Do any of you fix your floppies?
Thanks.
Well, perhaps you're right about the discussions you recall, Eric. I do
recall that there was an effort afoot to use 80-track drives to read some
diskettes written with the off-track method used by (Bill Budge?) games,
etc, in order to defeat their copy protection. I do recall the comment
being made, however, that a while person might defeat that particular copy
protection, since the mechanism under discussion was capable of putting a
track literally anywhere on the diskette, ( which certainly couldn't have
been done with a stepper ) the protection scheme wouldn't hold up. In any
case, it's good someone else was paying attention at the time, as it didn't
really matter to me, though I found it interesting. It was, after all, over
20 years ago.
Dick
-----Original Message-----
From: Eric Smith <eric(a)brouhaha.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 8:37 PM
Subject: stepping machanism of Apple Disk ][ drive (was Re: Heatkit 5 1/4
floppies)
>"Richard Erlacher" <edick(a)idcomm.com> wrote:
>> (2) - I remember lengthy discussions among those members of the Denver
Area
>> 6502-Users' Group who were presumably qualified to discuss the
intricacies
>> of the internals of APPLE's disk I/O routines at a level I neither knew
nor
>> cared about, beyond the superficial details I gleaned from the several
and
>> varied sessions discussing that set of details. Now, I attended these
>> weekely and typically 4-hour long meetings for several years, and KNOW
the
>> guys who were hashing out the details of the hardware and software in
>> question knew what they were talking about, so I accept that as fact.
>
>Then, as you'll recall, I was one of the people who spoke at those meetings
>regarding the operation of the Disk ][. Armed with information provided by
>Wayne Wall, Larry Fish, and Peter Boyle, I delved into the disk system in
order
>to figure out how to defeat various copy protection schemes, including the
>various half-track and quarter-track positioning methods. Larry was
involved
>in Apparat's efforts to interface standard Teac FD55 series disk drives to
>the Apple ][ controller.
>
>> These fellows
>> spent a couple of sessions talking about and demonstrating the screwy
means
>> by which certain game vendors in the Apple market were "protecting" their
>> wares by altering the timing of the positioning routine, thereby making
it
>> possible to write tracks "off the track" by changing the time delay
between
>> a known cylinder position and the point at which the specific track was
to
>> be written. This made it impossible for someone using the stock timing
of
>> the positioning mechanism to read the diskettes so written.
>
>No, the postioning that was discussed was the half-track positioning I
>described earlier. If you look at the Apple RWTS routines (for either 13-
>or 16-sector diskettes), you'll find that the low level postioning routine
>actually takes an argument that is two times the track number.
>
>The only thing about it that was non-obvious was the timing of the
>acceleration/decelleration profile used to speed up the seek process.
>However, this did not affect the final head position.
>
>> The scheme with the tristate multiplexers came later, I believe, than the
>> one I remember.
>
>I'm not sure what tristate multiplexers you're referring to. The
controller
>for the Disk ][ never changed in any non-trivial way. Some later cards for
>use with the Unidisk and Duodisk used a 19-pin D-subminiature connector in
>place of the pair of 20-pin right angle headers, but the electronics was
the
>same. Starting with the Apple ][c they used the IWM chip, which was a
>slightly fancier single-chip version of the original controller, but the
>positioner control method didn't change.
>
>> Apple had several patents, all of which are there to be
>> examined if one wishes. I believe this software-timed positioning scheme
>> was among them.
>
>They had exactly one patent from that era which covers the disk controller.
>It describes (among other things) how they use a stepper motor for
positioning.
>
>> I doubt, however, that Wayne Wall would have allowed the waste of
>> several sessions of the meetings he so firmly controlled back in those
days,
>> if the assumptions presented as fact in those discussions had not been
>> verified.
>
>I'm sure he wouldn't have. Which is why there was not any discussion of
>using DC motors for head positioning.
>
>> The helical cam I remember didn't have a groove, but rather, a ridge or
>
>Regarding mechanical details of the Disk ][ drive I'll readily concede that
>you are likely correct, as I never bothered to study the mechanism, only
>the electronics and code.
>
>Cheers,
>Eric
Let me qualify this, first of all, with two bits of fact . . .
(1) - I didn't care about the APPLE drives because they didn't work with the
type of controller I produced, so if I'm wrong, it's caused little damage so
far . . .
and
(2) - I remember lengthy discussions among those members of the Denver Area
6502-Users' Group who were presumably qualified to discuss the intricacies
of the internals of APPLE's disk I/O routines at a level I neither knew nor
cared about, beyond the superficial details I gleaned from the several and
varied sessions discussing that set of details. Now, I attended these
weekely and typically 4-hour long meetings for several years, and KNOW the
guys who were hashing out the details of the hardware and software in
question knew what they were talking about, so I accept that as fact. If
it wasn't true, no harm done, but I doubt that was the case. These fellows
spent a couple of sessions talking about and demonstrating the screwy means
by which certain game vendors in the Apple market were "protecting" their
wares by altering the timing of the positioning routine, thereby making it
possible to write tracks "off the track" by changing the time delay between
a known cylinder position and the point at which the specific track was to
be written. This made it impossible for someone using the stock timing of
the positioning mechanism to read the diskettes so written.
The scheme with the tristate multiplexers came later, I believe, than the
one I remember. Apple had several patents, all of which are there to be
examined if one wishes. I believe this software-timed positioning scheme
was among them. Having said that, I would point out that, given a software
scheme sequenced the stepper, it is just as possible that one could have
read the diskettes written a half track off by fiddling with the stepping
sequence. I doubt, however, that Wayne Wall would have allowed the waste of
several sessions of the meetings he so firmly controlled back in those days,
if the assumptions presented as fact in those discussions had not been
verified.
The helical cam I remember didn't have a groove, but rather, a ridge or
"fence" in the shape of a helix, which was tracked by a small,
spring-loaded, roller bearing. This worked quite well, but, because of
inertia and resonances in the system, required an unduly long period to
settle. The somewhat more costly band-actuator positioned drives settled in
3ms, typically, a rate which could be advertised and made a drive look
"better," although FDC's for the smaller drives had been designed such that
the faster step rate couldn't be exploited without fancy external gyrations
involving increasing the oscillator rate, since, previously, the
mini-floppies, as they were then called, could seldom step faster than 6ms
per track.
By the time the IBM PC became available, all the drives you saw were capable
of the fast step rate, yet IBM's hardware/software wouldn't readily
accomodate it. There were freebie patches published by third parties to
speed up the step rate, which caused the drives to quiet down considerably.
Dick
-----Original Message-----
From: Eric Smith <eric(a)brouhaha.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 6:16 PM
Subject: Re: Heatkit 5 1/4 floppies
>"Richard Erlacher" <edick(a)idcomm.com> wrote:
>> Apple drives
>> used a form of GCR on their drives, the heads of which were positioned
with
>> a software timed DC motor, while nearly everyone else used FM or MFM on
>> drives which used steppers driving band actuators.
>
>Correct about GCR, but not about head positioning. If you look at the
>schematics of the Disk ][ controller card and that of the drive, both of
>which were in the DOS reference manuals up through the early 3.3 manuals
>(before the Apple //e shipped), you will see that the controller uses four
>outputs of a 74LS259 (or 9334) 8-bit addressable latch to control the four
>phases of the head positioning stepper motor.
>
>IIRC, in the drive the four TTL-level phase signals from the controller
>are inputs to a ULN2003 which actually drives the motor phases.
>
>The stepper motor has an additional stable states halfway between any pair
>of adjacent tracks. However, due to the head width, it was not possible to
>get twice the number of usable data tracks. But you could use non-standard
>track positions as long as they were at least two steps apart. One of the
>earliest copy protection schemes was to use track 0, 1.5, 2.5, 3.5, etc.
>Of course, the copy programs quickly started supporting half-track
>positioning.
>
>The screwy part of Apple's head positioning system is the absence of a
track 0
>sensor. The technique to home the positioner was to step away from track 0
a
>few steps (call it N), then step toward track 0 by more than 68+N steps
>(the number 96 comes to mind but I could be mistaken). This results in the
>famous "Disk ][ mating call" sound.
>
>In fact, you can actually get quarter-track positioning, but you
>have to keep one (two?) of the stepper coils driven to hold the positioner
>in place. This can be viewed as a very crude form of microstepping.
>
>Of course, you can potentially also write data *during* the postitioner
>motion. However, this was seldom done even for copy protection, because
>the repeatability was poor even on the same drive, and very poor between
>drives.
>
>Because the stepper motor was under software control, the RWTS subroutines
>(Read/Write Track & Sector, the low-level disk driver) actually used a
>ramped acceleration/deacceleration profile, for faster seek times than
>in typical systems which used a fixed track-to-track step time.
>
>Eric
>Can someone explain how the Apple II GCR worked? I tried deciphering this
>several years ago and I could figure it out (the only references I found
>were very vague).
There's one reference which is extremely non-vague: _Beneath Apple
DOS_, by Don Worth and Peter Lechner. In it you'll find wonderful
illustrations featuring Sir Isaac Newton and leading you through the
wonderfully intertwined world of the Disk ][ state machine, 6502
machine code, and modulation formats. This book is still available
new (see my past posts to comp.sys.apple2 for details on how to buy it.)
If you're too cheap to buy the book (again, buy the book! It's
worth every last cent!), the relevant section of it (minus the
cute drawings) is online at
http://www.umich.edu/~archive/apple2/misc/hardware/disk.encoding.txt
But, again, buy the book! Woz is not my super-hero, but he could do
amazing things with a half-dozen TTL chips, that everyone else was
doing with a hundred or more...
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
>On Mon, 5 Apr 1999, Derek Peschel wrote:
>
>> I was going to mention RPG in my original post but I changed my mind. ...
> ...
>Believe it or not people still use that abomination. ...
>
>Its funny because it's programmed much like the earlier versions of
>ForTran, where each statement and associated arguments and data must start
>in a particular column due to its origins as a punched card language.
>
>I would hope the latest version of RPG does away with the archaic column
>specificity.
Don't know about the latest versions of RPG, but it should not be forgotten
that RPG was developed as an emulator for the 407 Tab machine. You could
use it to turn a 1401 with a very small memory, i.e. 1.2K, into a 407 Tab
machine, thusly you could turn the legion of 407 plug board programmers
into computer programmers. One 1401 could do the same amount of work as
several 407 Tab machines, much to the chagrin of IBM because the rent on
one 1401 could be less than the rent of three 407s, depending on the
configurations of each.
-- Dean
At 11:31 AM 4/7/99 -0700, Sellam wrote:
>...
>I tried to get him to speak at VCF 2.0 after he got axed by Conner (was it
>Conner?) but I could never get ahold of him. I think he would have a good
>story to tell so I may try again this year.
Finis Conner worked for Al Shugart years ago, then left to start his own
company. A couple of years ago it was in trouble and Shugart bought Conner
Peripherals, but Finnis Conner soon departed. Last year sometime the board
of directors of Seagate terminated Al Shugart's contract.
-- Dean
>
> I was doing a bit of research and came across an interesting page:
>
> http://www.lysator.liu.se/adventure/
>
> lists adventure games for various computers, including machines like the
> PDP series and the much, much better (and far too infrequently mentioned)
> HP 3000. 8^)
>
>
Ahhh.... Adventure.... All the plugh's and plovers and xyzzy's you could
shake a stick (of dynamite) at....
Does anyone remember a version that:
If you went down from the hall of the Mt. king, you
were in a room with a vault door. If you tried to
apply any of the standard magic words (xyzzy etc)
the door would fuse shut and something (a blob? a djinn?)
would show up several turns later, chase you down, and
kill you?
It ran on a CPM machine in the early 80's.
clint
I was doing a bit of research and came across an interesting page:
http://www.lysator.liu.se/adventure/
lists adventure games for various computers, including machines like the
PDP series and the much, much better (and far too infrequently mentioned)
HP 3000. 8^)
--------------------------------------------------------------------- O-
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/
8" drives typically spun all the time, as their motors were AC types. If
your 5-1/4" drive spins all the time, something's wrong. They had a
nMOTOR_ON signal which you can monitor to determine whether it's a defective
drive or a bunged-up driver. One important reason for the popularity of the
smaller drives over the AC-powered 8" types was noise. If the drive is
running all the time, clearly there's something wrong. It could be in the
jumpering of the drive or in the controller firmware. It could even be a
jumper option on the controller. You'll ruin lots of floppies in a drive
which doesn't stop and which doesn't unload its heads. It's easy to monitor
the control signals. If the controller tells the disk drive to keep
spinning, you need to "fix" the BIOS code.
Dick
-----Original Message-----
From: Joe <rigdonj(a)intellistar.net>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 9:13 AM
Subject: Re: Heatkit 5 1/4 floppies
>At 09:43 PM 4/7/99 -0700, you wrote:
>
>People today don't realize that the old
>>systems used a floppy like present systems use a hard drive, almost all
the
>>time, which is a heck of a lot of wear for a contact media.
>
> I used to work for Burroughs and they had a computer that used 8"
>floppys that spun continously. Burroughs said to replace the disks every
>100 hours. I have no idea how long they would actually run before failing.
> Does anyone know? I have a CPM machine that spins it's 5 1/4" disk
>continously but I haven't run it enough for a disk to fail.
>
> Joe
>>
>>
>
I received this message and I do not know what it is about!
Stephanie sring(a)uslink.net
-----Original Message-----
From: Derek Peschel <dpeschel(a)u.washington.edu>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 4:16 AM
Subject: Re: sending you a book?
>I asked you about a book I got for you; you seemed interested but I still
>want to confirm. Also I need your postal address.
>
>-- Derek
>
Not all mini-floppy drives have the ability to load/unload the head. If
yours doesn't, it's advisable to fix the spin-up/spin-down problem with
either software or hardware, i.e. jumpers or the like. The decision to go
ahead and wear down the emulsion of your floppy diskette was made when
drives and media were common. That's no longer the case, and since you're
into retrocomputing, the slower(oops, I mean "more realistic") it is, the
better you'll like it, right??? The last time I checked (a long time ago)
my CP/M-ulator ran at 6-7x the speed of the "real McCoy" so I doubt you're
running the old hardware just to run those old programs.
While it's true that 8" drives can run constantly without media or head
damage they had head-load solenoids as opposed to a spring which loads the
heads once the drive door is closed as the mini-floppies often do. The
emulsion on a floppy diskette becomes increasingly abrasive as the emulsion
ages and, not only will it dirty the heads by leaving whatever dust or other
glutch is present on the diskette in the head gap, but it will polish and
grind on your heads. If you want your heads worn and dirty, running them in
constant contact with the media and spinning will do it just fine.
Dick
-----Original Message-----
From: Joe <rigdonj(a)intellistar.net>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 1:21 PM
Subject: Re: Heatkit 5 1/4 floppies
>Dick,
>
> I don't know if they're supposed to run all the time or not, but both
>drives do it so I don't think it's a problem in the drives. A lot of the
>older drives had jumpers to cause them to run continously. I guess it
>saved the time needed to spin the drive up to speed. Several people have
>said that they have systems with 5 1/4" drives that spin all the time so it
>may be normal. Allison says that her 8" drives have run thousands of hours
>without problems so I hope it's not a problem.
>
> Joe
>
>At 11:50 AM 4/8/99 -0600, you wrote:
>>8" drives typically spun all the time, as their motors were AC types. If
>>your 5-1/4" drive spins all the time, something's wrong. They had a
>>nMOTOR_ON signal which you can monitor to determine whether it's a
defective
>>drive or a bunged-up driver. One important reason for the popularity of
the
>>smaller drives over the AC-powered 8" types was noise. If the drive is
>>running all the time, clearly there's something wrong. It could be in the
>>jumpering of the drive or in the controller firmware. It could even be a
>>jumper option on the controller. You'll ruin lots of floppies in a drive
>>which doesn't stop and which doesn't unload its heads. It's easy to
monitor
>>the control signals. If the controller tells the disk drive to keep
>>spinning, you need to "fix" the BIOS code.
>>
>>Dick
>>-----Original Message-----
>>From: Joe <rigdonj(a)intellistar.net>
>>To: Discussion re-collecting of classic computers
>><classiccmp(a)u.washington.edu>
>>Date: Thursday, April 08, 1999 9:13 AM
>>Subject: Re: Heatkit 5 1/4 floppies
>>
>>
>>>At 09:43 PM 4/7/99 -0700, you wrote:
>>>
>>>People today don't realize that the old
>>>>systems used a floppy like present systems use a hard drive, almost all
>>the
>>>>time, which is a heck of a lot of wear for a contact media.
>>>
>>> I used to work for Burroughs and they had a computer that used 8"
>>>floppys that spun continously. Burroughs said to replace the disks every
>>>100 hours. I have no idea how long they would actually run before
failing.
>>> Does anyone know? I have a CPM machine that spins it's 5 1/4" disk
>>>continously but I haven't run it enough for a disk to fail.
>>>
>>> Joe
>>>>
>>>>
>>>
>>
>>
>
In a message dated 08/04/99 10:22:43 Eastern Daylight Time, edick(a)idcomm.com
writes:
<< Since new floppy drives cost about $25 including shipment, it's difficult
to
justify repairing them. This is frustrating for people like you who have
drives for which replacements are not readily available for $20 or so.
Your experience with sloppy workmanship gives clear indication that $10 per
hour is not enough to pay a competent technician. The occasional look
inside should give you good indication of why one who can't spend more than
15 minutes' time fixing a $20 drive, can't get the job done. These devices
must be considered "throw-away" items by now. You've got to learn to
fix-em-yourself. >>
agreed, but i'd only apply this throw away mindset to ordinary pc floppy
drives. mac suprdrives are hard to find and expensive. i've one now in my mac
IIx that's not reading any disks. apple drives are plentiful and cheap, but
i'd fix them as well since none are produced anymore, obviously.
Since new floppy drives cost about $25 including shipment, it's difficult to
justify repairing them. This is frustrating for people like you who have
drives for which replacements are not readily available for $20 or so.
Your experience with sloppy workmanship gives clear indication that $10 per
hour is not enough to pay a competent technician. The occasional look
inside should give you good indication of why one who can't spend more than
15 minutes' time fixing a $20 drive, can't get the job done. These devices
must be considered "throw-away" items by now. You've got to learn to
fix-em-yourself.
Dick
-----Original Message-----
From: Mike Ford <mikeford(a)netwiz.net>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Thursday, April 08, 1999 2:29 AM
Subject: Fooling with floppy drives
>Coincident with all this chatter on floppy drives I have run into a streak
>of uncooperative drives. I happen to be using macs with 3.5" Sony
>mechanisms, but my question is somewhat general. What do you do with floppy
>drives that need repairs?
>
>Normally I just put them aside, but after this week I have close to a dozen
>in the defective box and ZERO (actually a negative number since I need even
>more) reliable units that aren't already installed in other systems.
>
>I have already performed the first aid procedures like cleaning the heads
>(using a wet cleaning floppy), and disassembly down to the bare mechanism
>and blowing out the bunnies with canned air. This pile is the hard core
>rejects, floppy doesn't spin, floppy doesn't eject, which I guess means a
>drive motor or support electronics is shot.
>
>For perspective, Apple still wants like $150 for a new floppy, mail order
>sources have the same for about $70, and reliable refurbs run the gamut
>from a low of about $20 up to $50 or more (used OK drives are $10 to $20.
>and my last pesky supplier was asking $5 for untested pulls). What I am
>finding disturbing is that more and more of the drives I see have OBVIOUSLY
>been swapped from another machine, or show other signs of being opened up
>by non techs (missing screws or other parts).
>
>What are your opinions, practices, or sources?
>
>Do any of you fix your floppies?
>
>Thanks.
>
>
On Thursday, April 08, 1999 6:16 AM, Charles E. Fox [SMTP:foxvideo@wincom.net] wrote:
>
> Did anyone catch the bit on ABC news last night about the use of old
> computers to fill potholes?
> I think some of our Windsor potholes would require at least a mini.
>
> Regards
Here's the story:
http://www.cnn.com/NATURE/9904/07/computers.potholes.ap/
Steve Robertson <steverob(a)hotoffice.com>
It is interesting to me that others view Lisp as a high level language. For
my money, it is an assembly language for an abstract computer. Sure, it
has much of the form of a high level language but, the simplicity of its
minimal number of required operators makes it ideal as a machine
language. As I recall, CAR, CDR, CONS, and four or five more operators
is all that is necessary for a complete implementation. This is RISC
processing if ever there is such a thing. Moreover, the fact that all
things
are handled as a single data type sure does imply an object point of
view, however much that point of view is myopically constrained (that
the objects are all lists!).
The most interesting aspect of Lisp, for me, is that code can be
constructed by the operation of a program, and thereupon caused to
be executed. This is another parallel with machine languages.
William R. Buckley
I don't believe those were the earliest of the 5-1/4" types. The early
SA-400's I remember used a lead screw just like the 8" drives, but that was
too costly for the competition that followed. When Apple started buying
"partial" drive mechanisms in order to implement their more software-driven
approach, with the idea of saving a few bucks . . . multiplied by a milion
or two drives . . . other manufacturers including SIEMENS and BASF, among
others, tried a two-phase stepper on a helically-tracked drive wheel as
opposed to the stepper driving a lead screw. Most makers later went to a
band-actuator system using a small stepper.
Since the business of designing floppy and hard disk controllers was my long
suit back then, I had several of nearly every type of FDD and HDD lying
around the shop, and there were LOTS. By the time IBM got into the game,
the positioning mechanism contest was pretty well settled. Apple drives
used a form of GCR on their drives, the heads of which were positioned with
a software timed DC motor, while nearly everyone else used FM or MFM on
drives which used steppers driving band actuators. Once the volume was up,
the cost wasn't that much greater, while the precision and accuracy were
quite a bit greater. I don't even remember what the nature of the physical
linkage between the motor an the head positoner was, since I stayed away
>from them. I still have an Apple drive somewhere. I suppose I could look .
. .
Of course, Apple's orientation toward YOUR data was that nobody really cared
if you had to punt and hit the reset button just because the FDD wouldn't
read the floppy it wrote just a few minutes before . . . After all, if you
were serious, you didn't use an Apple. If you were serious it's for sure
you had some 8" drives for the data you wanted to keep.
Dick
-----Original Message-----
From: James Willing <jimw(a)agora.rdrop.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 1:57 PM
Subject: Re: Heatkit 5 1/4 floppies
>On Wed, 7 Apr 1999, Jeffrey l Kaneko wrote:
>
>> These were in common use on Z89's and Z-90's. Heathkit used drives made
>> by
>> Tandon and Siemens. The Siemens drives were kinda unique: It used a
>> disk with a spiral groove for the head positioner.
>
>Hmmm... hardly that unique it would seem... The Shugart SA-400 series
>drives used that same positioning systems (first?).
>
>-jim
>---
>jimw(a)agora.rdrop.com
>The Computer Garage - http://www.rdrop.com/~jimw
>Computer Garage Fax - (503) 646-0174
>
Well, I just bought something at a used bookstore called "SOFTCARD; VOLUME II"
Its a microsoft product, and apparently its illegal to even give it away,
let alone to resell it ;) I'm going to ignore that obviously illegal
wording ;)
Apparenly this is the software and manual for the Microsoft Z80 card
for the Apple II series. I have one floppy disk, never used, in
16-sector format for DOS 3.3 or language card. Apparently there should
be another manual with chapters 1-3 (unfotunately these are the
more interesting chapters), whereas this is chapter 4 on the latest and
greatest microsoft basic ever created, which is apparently on the
floppy disks ;) plus a little information in the final chapter 5.
I dont suppose i can use any of this without the Z80 card? The cp/m wont
work without it i'm guessing. Am I correct in guessing all this is
good for is Ebay or trades?
-Lawrence LeMay
PS: I also picked up a nice copy of "the programmers CP/M handbook" which
provides extensive coverage of CP/M 2.2, mainly assebly listings. It
looks like more than 50% of it is assembly listings. Interesting...
PPS: I really should go back and buy that UCSD P-system book, I suppose.
On Tue, 6 Apr 1999, ard(a)p850ug1.demon.co.uk (Tony Duell) wrote:
] > To put this slightly on topic, we all know that computer systems have
] > become more reliable in the last 20 years but does anyone have any real
]
] I am not totally convinced. Computers have become a lot more complicated
] in the last 20 years, and IMHO some of that complexity has led to
] unreliablity (cf the comparative crash rate of say Windows and CP/M).
I am totally unconvinced. :-)
The number of times per day that I run into something that doesn't
work has steadily gone up over the years. Years ago, although the
machine might crash from time to time, it would generally work pretty
well. Nowadays, even when the machine is "working", I have to wait
for the characters that I type to show up on my screen, and programs
that I run every day will often refuse to work because some server
that I've never even heard of is down or unreachable.
Prediction: between ten and twenty years from now, somebody will
discover "standalone" computing; that a computer can be made to
function even when not attached to a network. It will be a
revolution, paving the way for systems that keep working once
they are set up, even with evil sysadmins reconfiguring everything
they can get their hands on three times a week.
] Also, I have had _far_ more built-to-a-price PC parts land on my bench to
] be repaired than (say) DEC PDP11 and PDP8 parts. For all I have had to
] maintain many _more_ of the latter type of machine.
]
] -tony
Did anyone catch the bit on ABC news last night about the use of old
computers to fill potholes?
I think some of our Windsor potholes would require at least a mini.
Regards
Charlie Fox
Charles E. Fox
Chas E. Fox Video Productions
793 Argyle Rd. Windsor N8Y 3J8 Ont. Canada
email foxvideo(a)wincom.net Homepage http://www.wincom.net/foxvideo
Anyone know if there's ever anything like this in/near/around Western PA
(Eastern Ohio, Northern VA)?
--
-Jason Willgruber
(roblwill(a)usaor.net)
ICQ#: 1730318
<http://members.tripod.com/general_1>
-----Original Message-----
From: Lawrence Walker <lwalker(a)mail.interlog.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 6:34 PM
Subject: Re: SoCal TRW Swap and DEC Open House
On 7 Apr 99 at 17:04, John Lawson wrote:
>
>
> As promised last month... this month, April, on Saturday the
> 24th, I will offer hospitality and welcome to anyone wishing to
> view/play with/make bad jokes about my DEC collection. As many
> systems as I can get running will be 'on the air' (tho not all at
> once... zzzzzmp!) for your perusal and happiness. You can paw thru
> the junk and maybe find something you've wanted for months... we can
> trade... you can help me clean out the garage... (please....!)
>
> I will attend the TRW Swap Meet the morning of the 24th, and all
> are invited there, and immediately afterwards to the usual post-swap
> brunch-n-brag (around noon). Then I will travel to My Place, and any
> folk wishing to join in at any point in the day's activities are most
> welcome.
>
> We can party until Sunday night, if that's what you want. I have
> to be at work Monday morning, and so do you. Otherwise, it's
> unstructured.
>
> I would prefer to give directions privately, since where you are
> coming from will modify them. Please e-mail me if you think you
> might like to participate. It's completely informal, all are
> welcome, and if no one shows up, I'm gonna play with the machines
> all by myself. Directions will also be available from me at TRW.
>
> I know that several NorCal (Bay Area) listmembers [Sam?] told me
> they were going to try and make it down... let me know and we'll
> leave alll the lights on. :)
>
> Just a heads-up for all, and I encourage others in other locales to
> consider hosting a Compu-crawl for your area... it's a lot more
> interesting to me than Tupperware...
>
>
> Cheerz
>
> John
--- Bruce Lane <kyrrin(a)my-dejanews.com> wrote:
> Arrrgh! Why couldn't this guy have been in north Seattle or something?
> I've been hunting for an 11/83!
>
> Anyone in Ohio looking for a nice PDP in a Worldbox?
I've been looking for any PDP-11 faster than an 11/23. The WorldBox is
a nice touch (I've already got one for my uVAX-II)
> Attachment follows.
Thanks. I was out of town for the original announcement. I'll see if it's
still available (probably not).
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--- Mike Ford <mikeford(a)netwiz.net> wrote:
> >Anyone know if there's ever anything like this in/near/around Western PA
> >(Eastern Ohio, Northern VA)?
>
> Yes of course. Find hams, any ham, and they will know all the horsetrading
> within unreasonable driving distance.
I am in Central Ohio (not exactly Eastern Ohio, but probably as close to the
request as we're likely to see). The big mother of swapmeets in my immediate
area are the shows in Dayton in March and August (Dayton Computerfest) and
the massive Dayton Hamfest in May. Admittedly, none of these shows are purely
people with cool, used stuff to sell (there are more vendors selling new
stuff),
but I got some great bargains at the computerfest last month on lots of used
items that I have been seeking for some time.
These days there aren't many classics at the Dayton shows, but I have purchased
at Dayton in the past things like a COSMAC VIP, an ASR-33, a PDP-8L (my first
-8, about 15 years ago), DECmates, CPU chips from the 1970's, etc. Lately,
it's been easier to find older components than systems; I've gotten boxes of
Teac FD55's for a song (still untested ;-), MFM disk drives for less than $0.20
per meg, uVAX and DECmate cables for $1, some older IC's occasionally, etc.
Other than Dayton, there are a few Hamfests that I make a point of going to,
first and foremost: the Mansfield Hamfest, one of the first of the season.
It's where I picked up that Apple //c+, recently. Someone had a Kapyro 2
there, but I wasn't going to pay $100 for it.
We don't have as many opportunities here as on the coasts, but things can
be found. I just last night rescued a uVAX 2000 with a pair of VR290's
(one working, one with a bad power supply) from the widow of a friend of
mine who died last year. I was told to get this "junk" this week or it
was going out with the neighborhood bulk collection next week. Besides the
CPU and monitors, there's a TK50-FA, an LA120 and an 8-port terminal server.
Does anybody but DEC speak LAT?
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--- Ethan Dicks <ethan_dicks(a)yahoo.com> wrote:
>
>
> Further, I am also told that a 6XX/MP board _will_ work in any sort of
> Sun VMS cage, including a 4/110 tower, one of the smaller configurations
> that Sun sold.
Doh! Make that a "VME" cage.
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
On Apr 7, 22:38, Chuck McManis wrote:
> Subject: Q-bus pinout
> Hello, is the Q-bus pinout on line? I've got an extender card and I'd
like
> to know if it was compatible or not.
There's a PostScript file showing the pinout at
http://www.dunnington.u-net.com/public/QBusConns.ps
(and a larger copy there also). Can't help with the PDP-8 PSU, though.
--
Pete Peter Turnbull
Dept. of Computer Science
University of York
Erm, I really don't think Smalltalk began with Lisp in any way.
The key idea in Smalltalk is encapsulization via class definition;
Lisp is all about lists and (to a purist) functional programming.
Both are very cool, and generally cleaner than the more "practical"
languages, maybe because they define a model that isn't so close
the the hardware. But they are really wildly different from each
other, right down to the bone. Lisp is not at all object oriented,
and Smalltalk is nothing but.
If all the languages you've used are the close-to-hardware
procedural kind, then these will seem novel. In that case, you
might also check out ML, Prolog, APL, SNOBOL, and Icon. APL and
Icon are still comfortably procedural, and SNOBOL is crude by
modern standards, but each of those has its own way-out-of-the-
mainstream aspects. Maybe none have the simplicity of pure Lisp,
though. There is something attractive about a language that does
just one thing, but does it well.
Bill.
PS. As a bonus, these all pass the ten-year rule. (Well, I'm not
100% sure about ML, but I *think* it does.)
] From: Max Eskin <max82(a)surfree.com>
] To: Discussion re-collecting of classic computers
] <classiccmp(a)u.washington.edu>
] Date: Saturday, April 03, 1999 11:44 PM
] Subject: Hallelujah!
]
]
] I've finally gotten around to reading a LISP book that I had bought months
] before, and I can see why people refer to LISP as a religious experience
] (I've seen that said at least twice). It's really a wonderful language. I
] wonder how it is worse than BASIC or Perl. Also, although I didn't really
] take the time to really understand smalltalk (Squeak is slow and
] unstable), I can see the beginnings of smalltalk in LISP. Wow. This thing
] really is pretty amazing. This should be taught in every computer
] programming course, along with PAL-8, C, and Perl. I am now certain that
] if a language is hard to learn (C++ comes to mind), there's something
] wrong with it :)
]
] --Max Eskin (max82(a)surfree.com)
Cheap would be cost of postage. I've been trying to get rid of
three of them for that price for, oh, probably a year now.
Finally, as of last week, I may have a taker. Though I haven't
heard back from him, and it has been several days now...
Bill.
On Tue, 6 Apr 1999, Mike Ford <mikeford(a)netwiz.net> wrote:
] In todays wanderings I found two seemingly very nice condition 4869
] external floppy drives, they were not cheap, but then I don't know what
] cheap for them would be. If anybody is interested email me as I will return
] to that haunt on Thursday.
<On Wed, 7 Apr 1999, Richard Erlacher wrote:
<> I don't believe those were the earliest of the 5-1/4" types. The early
<> SA-400's I remember used a lead screw just like the 8" drives, but that w
the SA800 was lead screw but, the sa400 was the spiral groove disk. I
know as I still have the working SA400 (not the later L) that came with
the Northstar* MDS purchased in 1977 (very low sn#).
Allison
--- Aaron Christopher Finney <af-list(a)lafleur.wfi-inc.com> wrote:
> Speaking of sparcs,
>
> This might be a little OT, but it does *involve* a Sun 3/50. At least the
> dead shell of one. John Lawson was kind enough to donate the mainboard
> from a Sparcserver 600MP to the cause today, but I don't have anywhere to
> put it (no comments on that, please). The question is this: can I put this
> board into the 3/50's case? From what I understand, the old VME chassis
> only provided power. Of course, the capacity of the 3/50's ps is a
> question too; I think it's rated somewhere around 20A at 5v, and the 600MP
> board requires something like 15A @ 5v, with no RAM or Mbus modules.
I tried that with no good results. I'm told that the 3/50 PSU doesn't
provide both +12v and -12v on the single power connector, or that the
6xx/MP board doesn't get comm voltages from that particular connector
or some other power-related reason why RS-232 doesn't work in that
configuration.
I was also told that the 6xx/MP board wants to see some kind of termination
on some of the VME signals or it won't past self-test. As I said, I could
never make it work, and the original 3/50 mainboard _does_ work in my 3/50
chassis, so it's not an overall PSU problem.
Further, I am also told that a 6XX/MP board _will_ work in any sort of
Sun VMS cage, including a 4/110 tower, one of the smaller configurations
that Sun sold.
BTW, don't try to run a newer version of Solaris on that board... Solaris 2.6
has checks for the 6XX/MP line and halts on startup. 2.7 (Solaris 7) is
completely missing kernel support for any VME machines.
If you find out any of this is wrong, I'd love to hear it; maybe someday
I could get my configuration working. For now, I'll restore the 3/50 as
is.
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
These were in common use on Z89's and Z-90's. Heathkit used drives made
by
Tandon and Siemens. The Siemens drives were kinda unique: It used a
disk with a spiral groove for the head positioner.
The cabinets are among the best floppy enclosures ever made IMHO
(although
they can be a bitch to put back together). I have several of them
myself.
The (linear) power supplies in 'em are fairly beefy.
Jeff
On Wed, 7 Apr 1999 10:35:59 +0000 "Lawrence Walker"
<lwalker(a)mail.interlog.com> writes:
> I made a curbside rescue of a dual ext. fdd. Two FH 5 1/4 floppies
>mounted
>vertically. ZenithDS Heathkit H77 with ribbon cable connector. Looks
>more like
>an 8" mechanism than your standard floppies. I'm assuming these were
>for a
>Z-100 guaged by the ZDS H-K label timeframe . Any info on them ?
> Judging by the mechanism that I can see , like Rainbow drives but not
>
>laterly opposed , they're SS.
>
>ciao larry
>lwalker(a)interlog.com
>
>Collectors info http://members.xoom.com/T3C
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
From: Christian Fandt <cfandt(a)netsync.net>
>>Anyone know if there's ever anything like this in/near/around Western PA
>>(Eastern Ohio, Northern VA)?
nope but here's an open invitation for anyone passing through Jacksonville
anytime.
- Mike: dogas(a)leading.net
This is one of APPLE & wierd Woz's patents. It's in almost every well
equipped electrical engineering library. There's also an ANSI standard for
GCR as applied by the 9-TRACK TAPE people to get up to 6250 bpi, which will
shed some light as well, should you choose to look it up. I used that
information to lay a groundwork for my APPLE HDC, which never made it to
market.
Dick
-----Original Message-----
From: CLASSICCMP(a)trailing-edge.com <CLASSICCMP(a)trailing-edge.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 7:12 PM
Subject: RE: Apple GCR
>>Can someone explain how the Apple II GCR worked? I tried deciphering this
>>several years ago and I could figure it out (the only references I found
>>were very vague).
>
>There's one reference which is extremely non-vague: _Beneath Apple
>DOS_, by Don Worth and Peter Lechner. In it you'll find wonderful
>illustrations featuring Sir Isaac Newton and leading you through the
>wonderfully intertwined world of the Disk ][ state machine, 6502
>machine code, and modulation formats. This book is still available
>new (see my past posts to comp.sys.apple2 for details on how to buy it.)
>
>If you're too cheap to buy the book (again, buy the book! It's
>worth every last cent!), the relevant section of it (minus the
>cute drawings) is online at
>
>http://www.umich.edu/~archive/apple2/misc/hardware/disk.encoding.txt
>
>But, again, buy the book! Woz is not my super-hero, but he could do
>amazing things with a half-dozen TTL chips, that everyone else was
>doing with a hundred or more...
>
>--
> Tim Shoppa Email: shoppa(a)trailing-edge.com
> Trailing Edge Technology WWW: http://www.trailing-edge.com/
> 7328 Bradley Blvd Voice: 301-767-5917
> Bethesda, MD, USA 20817 Fax: 301-767-5927
I saw a hardcover book from 1957 at the used bookstore, that discussed
digital computer circuits, and had chapters on vacuum tube logic circuits, corememory circuits, some transistor circuits, etc. If this is something
that someone here is dieing to have, perhaps because you're designing
a vacuum tube computer circuit, just let me know and i'll try to get it
before someone else does ;)
-Lawrence LeMay
Grab it before it's gone! Good chance for someone in or near Chicago
to mess with VME hardware.
-=-=- <snip> -=-=-
On Wed, 07 Apr 1999 18:32:42 GMT, in comp.arch.bus.vmebus you wrote:
>>From: mike(a)gmx.com
>>Newsgroups: comp.arch.bus.vmebus
>>Subject: Free! Motorola VME-10 System and Motorola Development Hardware
>>Date: Wed, 07 Apr 1999 18:32:42 GMT
>>Organization: Deja News - The Leader in Internet Discussion
>>Lines: 20
>>Message-ID: <7eg8ca$gmi$1(a)nnrp1.dejanews.com>
>>NNTP-Posting-Host: 199.179.170.230
>>X-Article-Creation-Date: Wed Apr 07 18:32:42 1999 GMT
>>X-Http-User-Agent: Mozilla/2.0 (compatible; MSIE 3.01; Windows 95)
>>X-Http-Proxy: 1.0 x17.dejanews.com:80 (Squid/1.1.22) for client 199.179.170.230
>>Path: news1.jps.net!news.pbi.net!206.190.128.10!newsfeed.yosemite.net!news1.ltinet.net!news.he.net!newshub.northeast.verio.net!news-feeds.jump.net!nntp2.dejanews.com!nnrp1.dejanews.com!not-for-mail
>>Xref: news1.jps.net comp.arch.bus.vmebus:23
>>
>>We have the following equipment which is going to be scrapped in the next
>>week or so unless someone in the Chicago area (we are in Northbrook) is
>>willing to come and pick it up (sorry, no shipping available).
>>
>>1 Mot VME10 System w/monitor & keyboard
>>1 Mot HDS-400 Hardware Development Station
>>1 Mot HDS-400/BSA 68020 Emulator/Analyzer
>>1 Mot HDS-300 Control Station
>>1 Mot Benchmark 20
>>1 Mot ExorTerm 155
>>
>>Plus miscellaneous manuals, cables, etc. This equipment was all working when
>>put in storage so years ago, but there are no guarantees... If interested,
>>contact me via email.
>>
>>Mike Magnus
>>mike(a)gmx.com
>>
>>-----------== Posted via Deja News, The Discussion Network ==----------
>>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
-=-=-=-=-=-=-=-=-
Bruce Lane, Owner and head honcho,
Blue Feather Technologies -- kyrrin (at) bluefeathertech [dot] com
Web: http://www.bluefeathertech.com
"...No matter how we may wish otherwise, our science can only describe an object,
event, or living thing in our own human terms. It cannot possibly define any of them..."
I don't know about designators, but the first mini-floppy drives I got all
had lead screws like the 8" drives. Later on, the SA400-<something> became
available, and I don't remember what the <something> was, but they had the
helical cam with a 2-phase stepper.
Dick
-----Original Message-----
From: Fred Cisin (XenoSoft) <cisin(a)xenosoft.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, April 07, 1999 5:41 PM
Subject: SA-400's (was: Heatkit 5 1/4 floppies
>On Wed, 7 Apr 1999, Richard Erlacher wrote:
>> I don't believe those were the earliest of the 5-1/4" types. The early
>> SA-400's I remember used a lead screw just like the 8" drives, but that
was
>> too costly for the competition that followed. When Apple started buying
>> "partial" drive mechanisms in order to implement their more
software-driven
>> approach, with the idea of saving a few bucks . . . multiplied by a
milion
>> or two drives . . . other manufacturers including SIEMENS and BASF, among
>> others, tried a two-phase stepper on a helically-tracked drive wheel as
>> opposed to the stepper driving a lead screw. Most makers later went to a
>> band-actuator system using a small stepper.
>
>Interesting. All of the SA400s that I've seen used the spiral groove on a
>rotating disc. The only 5.25" drives of that vintage that I have with a
>helical lead screw were the Micropolis 35 track 48TPI and 77 track 100TPI
>(NOT 96TPI!!). Was there any sub model designation for the Shugarts to
>differentiate different positioners?
>
>--
>Fred Cisin cisin(a)xenosoft.com
>XenoSoft http://www.xenosoft.com
>2210 Sixth St. (510) 644-9366
>Berkeley, CA 94710-2219
>
Interesting. The Siemens drives were the only ones I've
ever seen that use this scheme. But then again, I didn't
look closely at the Shugarts in the Burroughs word processors
when I took my first real job ("you're not qualified").
These were the only ones I've ever seen.
Jeff
On Wed, 7 Apr 1999 12:22:56 -0700 (PDT) James Willing
<jimw(a)agora.rdrop.com> writes:
>On Wed, 7 Apr 1999, Jeffrey l Kaneko wrote:
>
>> These were in common use on Z89's and Z-90's. Heathkit used drives
>made
>> by
>> Tandon and Siemens. The Siemens drives were kinda unique: It used a
>
>> disk with a spiral groove for the head positioner.
>
>Hmmm... hardly that unique it would seem... The Shugart SA-400
>series
>drives used that same positioning systems (first?).
>
>-jim
>---
>jimw(a)agora.rdrop.com
>The Computer Garage - http://www.rdrop.com/~jimw
>Computer Garage Fax - (503) 646-0174
>
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
At 22:33 31/03/99 +1, Hans wrote:
>For a usefull system a Country identyfier and the ZIP code
>should be used, like US-90210 or DE-81541 or CA-M2R3G3
>(ISO 2 Char Country identifyer plus up to 9 char for ZIP -
>there is _no_ ZIP code in the world with more than 9 digits).
>And for the state/province thing - that's not used outside
>US/CA and defacto redundant information, since the ZIP code
>already includes this - everybody knows the location of
>(at least) the first two or 3 digits within his country.
>
>Servus
>Hans
I fully agree with this kind of format
[CC-XXXXXXXXX]
C=International country identifier
X=National ZIP code
that I think it is also a recomandation from the international postal
organization.
Riccardo Romagnoli
<chemif(a)mbox.queen.it>
I-47100 Forl?
I don't think I have cp/m. I've got a bunch of software mothballed for just
this occasion but havent got to it yet. Ahhh... software.... good. good.
Does the 6 weeks start today?
:)
- Mike: dogas(a)leading.net
-----Original Message-----
From: Sellam Ismail <dastar(a)ncal.verio.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Tuesday, April 06, 1999 7:29 PM
Subject: RE: Chicago trs-80s
>On Tue, 6 Apr 1999, Steve Robertson wrote:
>
>> After careful disassembly, cleaning, and reassembly, the Model 2 returned
>> to life. Another list member has located a keyboard for me (thanks) so,
>> that one is complete. I haven't found a boot disk for it yet but, I'm
sure
>> it'll work just fine.
>
>I recently made a CP/M and TRSDOS-II boot disk for another list member and
>I'd be happy to do the same for both you and Mike. Of course, you'll
>probably have to wait as long as Aaron did (about 6 weeks).
>
>Sellam Alternate e-mail:
dastar(a)siconic.com
>---------------------------------------------------------------------------
---
>Don't rub the lamp if you don't want the genie to come out.
>
> Coming in 1999: Vintage Computer Festival 3.0
> See http://www.vintage.org/vcf for details!
> [Last web site update: 04/03/99]
>
>
As promised last month... this month, April, on Saturday the
24th, I will offer hospitality and welcome to anyone wishing to
view/play with/make bad jokes about my DEC collection. As many
systems as I can get running will be 'on the air' (tho not all at
once... zzzzzmp!) for your perusal and happiness. You can paw thru
the junk and maybe find something you've wanted for months... we can
trade... you can help me clean out the garage... (please....!)
I will attend the TRW Swap Meet the morning of the 24th, and all
are invited there, and immediately afterwards to the usual post-swap
brunch-n-brag (around noon). Then I will travel to My Place, and any
folk wishing to join in at any point in the day's activities are most
welcome.
We can party until Sunday night, if that's what you want. I have
to be at work Monday morning, and so do you. Otherwise, it's
unstructured.
I would prefer to give directions privately, since where you are
coming from will modify them. Please e-mail me if you think you
might like to participate. It's completely informal, all are
welcome, and if no one shows up, I'm gonna play with the machines
all by myself. Directions will also be available from me at TRW.
I know that several NorCal (Bay Area) listmembers [Sam?] told me
they were going to try and make it down... let me know and we'll
leave alll the lights on. :)
Just a heads-up for all, and I encourage others in other locales to
consider hosting a Compu-crawl for your area... it's a lot more
interesting to me than Tupperware...
Cheerz
John
There exists a well known file, the Field Guide, which lists all
PDP and VAX DEC boards by number and description. I have created a
web page on VAXarchive, my site with information on old DEC VAX
hardware and its operating systems, which is to be the visual version
of this list. It shows pictures of boards, and their number
and function. This makes it easy to identify boards with unreadable
or missing module numbers. There are now 24 pictures on this page,
which is of course just a tiny part of all boards that exist.
I am hoping that the readers of this list are able to help me get
more pictures.
If you own boards that are not on this page, I would appreciate
it very much if you could send me an image of them. If it is a dual
or quad width board, you do not need a digital camera to make this
picture, you can just lay it face down on a flat bed scanner.
(This is how all the pictures on the page were made.) Please mail
any pictures to pb0aia at iae.nl, or let me know on which ftp or www
site they are. Thanks in advance!
The URL of the page is:
<http://www.vaxarchive.org/hw/vfg/>
The boards already on the page are:
Dual width: M7270, M7504, M7546, M7555, M7607, M7954, M8043, M8044,
M8047, M8659, M9047.
Quad width: M3104, M7164, M7165, M7168, M7169, M7196, M7454, M7602,
M7606, M7608, M7609, M7624, M8639.
Non-DEC: QD21.
Regards,
Kees.
--
Kees Stravers - Geldrop, The Netherlands - kees.stravers(a)iae.nl
http://www.iae.nl/users/pb0aia/
I'm Sysadmin and DEC PDP/VAX preservationist - Visit VAXarchive!
http://www.vaxarchive.org/ (primary)
http://www.sevensages.org/vax/ (mirror)
http://www.coyote.org/mirrors/vaxarchive/ (mirror)
"D. Peschel" <dpeschel(a)u.washington.edu> wrote:
> I guess posting something on-topic is the best solutioon. Does anyone have
> a Corvus Concept? I bet Blockout (3D Tetris) would look pretty cool on it.
What do you think a Corvus Concept would bring to Blockout? I don't know,
and it's been years since I played Tetris.
Yep, I've got one, the fancy landscape/portrait display boils down to
a VERT/HORIZ switch on the back of the CPU that the software reads to
figure out how to draw the display. (It's up to the user to make sure
the switch and the monitor are set the same way, and the switch doesn't
change anything about the beam deflection.)
-Frank McConnell
>On Mon, 5 Apr 1999, Tony Duell wrote:
>
>> > computers, the service representative came to the site, opened a panel
>> > on the operator console, and changed the 5 1/4" floppy disk. By doing
>>
>> I think I read somewhere that the 8" floppy was originally designed for
>> this purpose.
>
>IBM invented the floppy disk to distribute microcode updates.
>
>Sellam
I believe that I saw the first floppy disk drive invented at IBM San Jose
in late 1969. It was designed to load microcode into the new selector
channels being designed for the IBM S-370. Unlike the CPU's and selector
channels of the S-360 that had a variety of ROM designs, the System 370 and
the stand alone selector channels had writable control stores for microcode.
The device was very primitive since it was essentially a read only device
when installed in the channel. It was designed by Al Shugart or a team
under his direction. I know he was credited with it within IBM. I have
always hoped somebody would do an oral history with him of his IBM days and
the reasons that he left to start his own company.
Dean
hmm.. also in looking through the xenix docs I see mentioned, the DT-1.
I've got a PT-210 and pre-coco vidtex and have been looking for a DT-100 but
dont remember the DT-1. What's it like?
- Mike: dogas(a)leading.net
Having had a small chance to digest the new trs pillsI find that I newly
have:
- a 6000hd 15meg 1d that I'm currently running xenix 3.01.00 on
-a 16 1d that is missing some internal cables, this one has an odd model
16 vanity plate and matching keyboard.
-a 6000hd 15meg 1d
-a 16 2d with a bad floppy and intermittant keyboard
-a 6000 15meg 1d
-a 6000 15meg 1d
-a 16b 2d with a bad monitor
-a 16b 2d
- keyboards for 6000 (and a white key one) 12, 16, and 16b
- 8meg hd system (big black)
- 20meg hd sytem (small white)
- 3 extra 8" floppies
- a bad 15meg winchester replacement
- assundry cabling
And digging into the closet (past all the skeletons) I pulled the following
software out of stasis
- xenix basic interpreter
- model II cobol dev system
- versaledger
- scripsit
- multiplan
-profile plus
- ar/ap/payroll
- trs-dos
- videotex Plus
- trs-dos II
- trs-dos 4.0
- model 16 system disk
- xenix CTAR
- profile 16
- xenix 3.02.00
- xenix profile upgrade
- xenix multiuser upgrade
- profile 16 upgrade
- xenix 1.3.xx for model 16
Will the trsdos stuff above work under tsh?
Now to dust off the drive heads and install some stuff. If anyone has any
complimentary warez or needs copies yada yada yada.
;)
- Mike: dogas(a)leading.net
--- allisonp(a)world.std.com wrote:
> > > boxes of paper tapes labeled "262.1-S PDP-8 Printer Driver Source",
> > > "265.1-OB PDP-8 printer Diagnostic Object 1 of 3", and the other 2 boxes.
--- After _I_ wrote:
> > I myself cannot tell what printer those work with from the numeric portion
> > of the title, but I can say that just for parallel printers, OMNIBUS -8's
> > supported
> > the LA180, the LQP01 and LQP02. Common serial printers...
> You forget LE8, LP14, lp25 series of line printers.
I didn't forget them... I never knew about the LE8 nor the LP14, and I didn't
know that there was ever an interface for the LP25 for any model of 8. It's
all news to me.
> PDP-8s were used with large and faster line printers of the day.
I have only ever seen PDP-8's used with what would be termed "personal" class
printers.
> Also the LA30 DECwriter was a parallel interface at 30cps.
I have heard of the LA30. I didn't know it was parallel. Never seen one.
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
>So I've got a Q-bus system with 64KW (128KB) of RAM that is allegedly an 18
>bit backplane. When I'm in ODT I can type:
>
>@177770/
>And enter values for 1777772, 1777774, 1777776, and then it wraps around to
>000000.
>
>If I start at 200000 it works until 3777777 and then wraps to 2000000. So
>it seems to not cross a 64KB boundary.
That's how it's supposed to work. If you look in the tech manual for the
processors, you see that there's a 16-bit register for the "low" part
of the ODT address, and another register for the high part of the ODT address,
but there's no carry connecting the two.
> Also the boot area is 177300 ? so it
>is in the upper 4K of the 64KB address space, is it legal to have memory
>"above" the I/O page?
Absolutely. In fact, some configurations had only a 2Kbyte I/O page
to allow a little bit of extra memory, and this still works (albeit not
officially supported) under RT-11 (it was tested before the 5.7
release.)
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
Ethan Dicks wrote:
>
> --- Marvin <marvin(a)rain.org> wrote:
> >
> > I was rummaging around the back bedroom last night and found (again) three
> > boxes of paper tapes labeled "262.1-S PDP-8 Printer Driver Source",
> > "265.1-OB PDP-8 printer Diagnostic Object 1 of 3", and the other 2 boxes. I
> > have no idea what printer this might be used with. It came with the PDP-8L I
> > acquired many years ago. These tapes are rolled black tape. Anyone know what
> > these might be?
>
> Do you have any way of reading the tapes in? One way to tell is by reading
> the comments. Another way is by checking the IOT's used for the printer I/O.
The only paper tape reader I have right now is an ASR-33 and aside from it
being buried :), I can use it to read the tapes in. The PDP-8 was bought new
by someone here in Santa Barbara, and then donated to a local school which
is where I got it. It came with an ASR-33 (which I sold years ago <sigh>), a
Tri-Data tape recorder (anyone familiar with them?), and a schematic
package. One of these days, it would be fun to fire it up (hopefully not a
pun!)
> > boxes of paper tapes labeled "262.1-S PDP-8 Printer Driver Source",
> > "265.1-OB PDP-8 printer Diagnostic Object 1 of 3", and the other 2 boxes. I
> > have no idea what printer this might be used with. It came with the PDP-8L I
>
> I myself cannot tell what printer those work with from the numeric portion of
> the title, but I can say that just for parallel printers, OMNIBUS -8's
> supported
> the LA180, the LQP01 and LQP02. Common serial printers were the older members
You forget LE8, LP14, lp25 series of line printers. PDP-8s were used with
large and faster line printers of the day. Also the LA30 DECwriter was a
parallel interface at 30cps.
THey were far from limited to ASR33s (LT33).
Allison
--- Marvin <marvin(a)rain.org> wrote:
>
> I was rummaging around the back bedroom last night and found (again) three
> boxes of paper tapes labeled "262.1-S PDP-8 Printer Driver Source",
> "265.1-OB PDP-8 printer Diagnostic Object 1 of 3", and the other 2 boxes. I
> have no idea what printer this might be used with. It came with the PDP-8L I
> acquired many years ago. These tapes are rolled black tape. Anyone know what
> these might be?
Do you have any way of reading the tapes in? One way to tell is by reading
the comments. Another way is by checking the IOT's used for the printer I/O.
I myself cannot tell what printer those work with from the numeric portion of
the title, but I can say that just for parallel printers, OMNIBUS -8's
supported
the LA180, the LQP01 and LQP02. Common serial printers were the older members
of the DECWriter line (e.g., LA-36, probably not the LA-120). If that source
is for an older, non-OMNIBUS model, I wouldn't have a clue as to what model of
printer it would want to talk to. I think only the LA-36 was available in
current-loop configuration (excepting, of course, real TTY's).
Do you have a way of reading in the tape?
-ethan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
I made a curbside rescue of a dual ext. fdd. Two FH 5 1/4 floppies mounted
vertically. ZenithDS Heathkit H77 with ribbon cable connector. Looks more like
an 8" mechanism than your standard floppies. I'm assuming these were for a
Z-100 guaged by the ZDS H-K label timeframe . Any info on them ?
Judging by the mechanism that I can see , like Rainbow drives but not
laterly opposed , they're SS.
ciao larry
lwalker(a)interlog.com
Collectors info http://members.xoom.com/T3C
At 06:13 PM 4/6/99 -0400, you wrote:
>Hi Uncle, been away for several days... Did I miss anything?
Nope, still working on getting them out. My dad is currently
sorting/separating cables. Be patient, everybody. (Paying the mortgage is
a little higher priority. 8^)
--------------------------------------------------------------------- O-
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/
At 11:14 AM 4/1/99 -0500, you wrote:
>Almost every computer involved person I know who
>has any control of their work schedule:
>
>1) Gets up after the sun has properly warmed the earth
> where they live
Dysania: (n) an inability to function early in the morning.
I've got it bad. (It's a real word, at least according to Balderdash, a
commercial version of the game Dictionary.)
--------------------------------------------------------------------- O-
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/
It is exactly that. . . a YMMV thing . . . My experience with terminals was
always a disappointment. I can't even think of a way to fix it. The people
who wrote and sold software made assumptions about what's out there, and, if
you used three different vendors' software, it was unlikely any of the
sophisticated features, including emulations, by the way, would work well
enough to use the same terminal in all cases. Only with the lowest common
denominator (ADM-3A) did one have a reasonable time of it.
Dick
-----Original Message-----
From: Allison J Parent <allisonp(a)world.std.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Tuesday, April 06, 1999 9:08 PM
Subject: Re: homemade computer for fun and experience...
><This is going to be a YMMV thing, but I've never had problems with normal
><serial terminals, especially not DEC ones.
>
>AS someone actively running s100 and assorted other cpm systems... A soft
>terminal that can emulate ADM1, ADM3, Vt100 and telvideo covers the crowd
>right up until you get some oddball code that used a 64x16 VDM1. The
>reality was no standards and it's really not gotten that much better.
>
>My solution... An H19 thats over 21, A vt100 (all others are broken),
>a few Vt320s and a Vt340. The thing is I also run DEC hardware and while
>they will support any ansi tube a real VT is still easier to use.
>
><> I have never had a desire for DEC hardware, mainly because of my distast
><> (and disdain) for their application of technology, and of course for
thei
>
>Personal preference. I happen to like them and they seem to run a long
>time. At least all of mine still runs and the 11/03 cpu I have has turned
>20!
>
><Don't forget that this started with somebody who wanted to homebrew their
><first computer. In which case it should be as simple as possible.
>
>therein is the essence of the string and why terminals are somewhat nicer
>even if they lack color graphics you can play doom on.
>
><> See . . . there are reasons NOT to use a terminal.
><
><Sure. Not every machine should use a serial terminal, but equally, not
><every machine needs a built-in graphics display. Which you build is up to
><you.
>
>I'll add you still need a serial line for a modem. Then you still need a
>printer. CPM being a nongraphic OS and there is a distinct lack of
>software that uses graphics for it... kind of a moot point if you can
>have a 1280x1024 color tube. I can say this as I have a visual 1050
>that has a rather elaborate display system and there is lttle use for it
>save for it can emulate a terminal at a cost of another micro, ram and
>firmware to run it. Nothing like debuging two systems and blind at that.
>
>Allison
>
<> To put this slightly on topic, we all know that computer systems have
<> become more reliable in the last 20 years but does anyone have any real
Potentially they are. there are fewer chips and connectors to fail and
chips can be highly reliable however...
The average PC is tossed togeher from a motly assortment of parts and
software and usually works, sometimes. With that cases are more a fashon
statment rather than given the thought toward cooling... those 333mhz
celerons do get mightly hot and those cheap bushing fans do fail often.
When new system have the uptime records of my 12 year old uVAXII we can
debate this... the record is 422 days contuinious uptime without reboot, it
was limited by a power failure.
I've built Z80 based systems with uptimes measured in years (still
counting as they are battery backed). They are running very debugged code
and power failure is not seen due to power systems that expect brownouts.
It's not to say they cannot out do that, only that reliability is a
measure of quality and sadly most PCs greatly lack the latter.
Technology does not automagically beget reliability, it affords the
opportunity to create it. Often that boat never docked at the airport.
Allison
<This is going to be a YMMV thing, but I've never had problems with normal
<serial terminals, especially not DEC ones.
AS someone actively running s100 and assorted other cpm systems... A soft
terminal that can emulate ADM1, ADM3, Vt100 and telvideo covers the crowd
right up until you get some oddball code that used a 64x16 VDM1. The
reality was no standards and it's really not gotten that much better.
My solution... An H19 thats over 21, A vt100 (all others are broken),
a few Vt320s and a Vt340. The thing is I also run DEC hardware and while
they will support any ansi tube a real VT is still easier to use.
<> I have never had a desire for DEC hardware, mainly because of my distast
<> (and disdain) for their application of technology, and of course for thei
Personal preference. I happen to like them and they seem to run a long
time. At least all of mine still runs and the 11/03 cpu I have has turned
20!
<Don't forget that this started with somebody who wanted to homebrew their
<first computer. In which case it should be as simple as possible.
therein is the essence of the string and why terminals are somewhat nicer
even if they lack color graphics you can play doom on.
<> See . . . there are reasons NOT to use a terminal.
<
<Sure. Not every machine should use a serial terminal, but equally, not
<every machine needs a built-in graphics display. Which you build is up to
<you.
I'll add you still need a serial line for a modem. Then you still need a
printer. CPM being a nongraphic OS and there is a distinct lack of
software that uses graphics for it... kind of a moot point if you can
have a 1280x1024 color tube. I can say this as I have a visual 1050
that has a rather elaborate display system and there is lttle use for it
save for it can emulate a terminal at a cost of another micro, ram and
firmware to run it. Nothing like debuging two systems and blind at that.
Allison
I wonder is it would be possible to devise something that would use some
sort of disc with a bunch of holes in it and the sensors from an old (8"?)
floppy drive?
A desperate attempt to get this somewhat back on topic :)
--
-Jason Willgruber
(roblwill(a)usaor.net)
ICQ#: 1730318
<http://members.tripod.com/general_1>
===============================
---------------Original Message-----
From: Stan Perkins <stan(a)netcom.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Tuesday, April 06, 1999 3:01 PM
Subject: Re: OT: ABS - or is it Pure BS/wheel sensors
>
>It's probably a similar system to the one used by Etak with their early
>car navigation systems. Basically, they used a special adhesive tape
>that contained a small bar magnet every inch along its length. This was
>applied to the circumference of the inside of each front wheel rim, and
>a Hall effect sensor was attached to a point on the front axle (usually
>to a part of the brake caliper assembly) where it was within an inch of
>this tape as it passed by. Each magnet passage would produce a countable
>pulse, and the Etak computer could determine the wheel speed and
>direction of rotation for each front wheel. *Supposedly* it could also
>detect a turn by the differential speed of the front wheels, but it also
>had a flux gate compass to help determine direction and turns.
>
>A pretty clever system that worked quite well, considering it was all
>done without reference to external navigation data sources like GPS,
>LORAN, etc!
>
>Since your system apparently produces only a single pulse per
>revolution, I would guess there's one magnet somewhere on each wheel
>rim. The speed resolution with only a single pulse per revolution is
>probably not good enough for ABS use.
>
>Hope this helps,
>Stan
>
My vacation/computer-rescue-mission has come to a close and there is now a
big honkin pile of trs-80 6000 and 16b toys on my living room floor. :)
Several of them have broken this or thatsz but the first one I pulled, a
6000hd 15mhd, booted into Xenix 3.0.1 I think (Microsoft '84). the 68k in
it crashed after about 20min of xenix frolicking. She's resting now. I'd
like cc and tcp for this if anyone can help me out? I 'm sure some parts
will be available as soon as I figure out what I have. Software, give me
software or give me death.
;)
- Mike: dogas(a)leading.net
I am looking for an "Industrial" IBM-compat PC... the kind that
is mounted in a 19" rack enclosure with a small monitor integral to
the box, and usually a keyboard underneath on a slide-shelf.
My purpose is to run one of the PDP11 sims and Linux, and to
function as a more modern 'peripheral farm' and a comm node to my
Real PDP collection.
I am looking for a 486 or Pentium I unit with 8-16 meg of RAM, .5 -
1.5 G HD, compatible BIOS and able to run Win95... if it *has* to.
One serial, one parallel, one SCSI, and Ethernet, or capable of
supporting all these at once.
I am looking to trade or buy. Obviously I prefer not to have to
buy new, I would much rather keep it 'local'.
NOTE: ABS braking is neither required nor desired on the above unit.
Cheerz
John
Just wanted to let eveyone know that I have been contacted by someone
who works for a company where they have three (3) KS10s. One of the
machines is *CURRENTLY OPERATIONAL*. One was shut down several months
ago, and the person who wrote to me doesn't know about the third.
There are nine (9) RP06 disk drives distributed between the three
systems, two additional ones are broken. Two tape drives are on
line (with problems) and one is broken (one TM03 and two TU77s).
The computers are in a room without a raised floor, so the cables
are simply laying around.
The terms are that we (whoever) takes the equipment must do so at
their own cost, and must take everything, including cables and
non-working units.
Dismantling can start April 21st, removal has to be by April
27th. No later than this.
The KS10s take up about 6sqft of floor space each, and are about 600 lbs.,
the RP06s apparently take up about 7-9 sqft and I don't know how much they
weight. I don't know about the tape drives.
Someone told me it may be between 6000 and 8000 lbs all together...
Systems are located in Cambridge, Massachussetts.
We need to give an answer by April 13th at the latest.
I suspect that if it isn't saved, it will go to the scrapheap,
landfill, crusher, <fill_in_your_own_worst_nightmare_here>.
So, is anyone game? Please contact me off-list. I'll *try* to
coordinate this.
This is a chance to handle some *REAL IRON*...
Megan Gentry
Former RT-11 Developer
+--------------------------------+-------------------------------------+
| Megan Gentry, EMT/B, PP-ASEL | Internet (work): gentry!zk3.dec.com |
| Unix Support Engineering Group | (home): mbg!world.std.com |
| Compaq Computer Corporation | addresses need '@' in place of '!' |
| 110 Spitbrook Rd. ZK03-2/T43 | URL: http://world.std.com/~mbg/ |
| Nashua, NH 03062 | "pdp-11 programmer - some assembler |
| (603) 884 1055 | required." - mbg |
+--------------------------------+-------------------------------------+
G'day,
Yesterday four geeks (including myself) had tried to convince a HP 88780
9-track SCSI drive (cleverly disguised as Tandem 5160) to accept 6250 bpi
tapes. It works OK at 1600 bpi, but refuses to admit it knows about 6250:
"mt setdensity 3" on a Linux box results in "Incompatible media installed"
error (when the tape written at 6250 bpi is loaded.)
The problem is: no docs. By playing with front panel buttons, we
discovered lots of interesting knobs to turn (CONF 40..199), but weren't
inclined to try them all. What CONF will allow 6250 bpi density to be
used? Or is it permanently disabled by Tandem-customized firmware?
--
Sergey Svishchev -- svs{at}ropnet{dot}ru
*Having had decades of extensive driving during the long cold winters in
*western Canada, Qebec and Ontario , I would consider myself a quite skilled
*slippery road driver. The worst thing you can do when you go into a skid is
*lock your brakes. The best is to turn into the skid and use your
accellerator
*and steering to bring it back under control. I would rather have any brake
*action under my control and hope I can steer out of it without using
them.There
*are courses up here which teach this technique. ABS seems just damnright
*dangerous to me,
What happens when that novice (or anyone for that matter) who is used to
ABS,
when the ABS system fails?
* except perhaps for the complete novice who would lock his
*brakes out of fear and inexperience. I have also had experiences of
*power-steering failure one of which resulted in a serious accident for
myself.
*
*ciao larry
*lwalker(a)interlog.com
*
*Collectors info http://members.xoom.com/T3C
*
Amen.
:)
- Mike: dogas(a)leading.net
-----Original Message-----
From: Max Eskin <max82(a)surfree.com>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Saturday, April 03, 1999 11:44 PM
Subject: Hallelujah!
>I've finally gotten around to reading a LISP book that I had bought months
>before, and I can see why people refer to LISP as a religious experience
>(I've seen that said at least twice). It's really a wonderful language. I
>wonder how it is worse than BASIC or Perl. Also, although I didn't really
>take the time to really understand smalltalk (Squeak is slow and
>unstable), I can see the beginnings of smalltalk in LISP. Wow. This thing
>really is pretty amazing. This should be taught in every computer
>programming course, along with PAL-8, C, and Perl. I am now certain that
>if a language is hard to learn (C++ comes to mind), there's something
>wrong with it :)
>
>--Max Eskin (max82(a)surfree.com)
>
>
I'm not sure if anyone else knows about what I'm talking about, but in my
Jeep (pre-ABS), there's a little panel on the dashboard (not original).
There's 4 LED's on the panel (one corresponding to each wheel). When the
wheel corresponding to a particular LED is completely stopped, the LED
lights steadily red. When the wheel is turning, the LED flashes green (one
flash for each revolution).
Anyone know how this would work (with out me pulling it out of my Jeep)? It
would be probably a good accessory for non-ABS cars.
--
-Jason Willgruber
(roblwill(a)usaor.net)
ICQ#: 1730318
<http://members.tripod.com/general_1>
>2) even if the ABS system fails it still works just like non-ABS brakes.
unless
>the vacuum (power assisted) system fails or the brake line is cut, or (very
>unlikely) the piston sticks open, the brakes will work just fine.
>
ABS - American Bull Shi...
I have noted one difficulty with ABS, and that is its failure to operate on
snow
and ice. Since I live in Southern California, I do not get that much snow
but,
in any quick application of my Mustang's breaks, on snow covered roads,
they always seem to lock up. Well, the pumping action occurs but, at each
application of the pump, I notice wheel lock-up. There is no stopping.
William R. Buckley
>>Sure. And the microcode compilers I've written and used are much better
>>at optimizing horizontal microcode than I have the time or patience to
>>do by hand.
>Your lack of time and patience is not equal to the claim you make
>regarding the quality of optimisation possible.
well put... I've yet to find a compiler which can produce code which
could not then be further optimized in some way by a person well
versed in that machine's architecture...
Megan Gentry
Former RT-11 Developer
+--------------------------------+-------------------------------------+
| Megan Gentry, EMT/B, PP-ASEL | Internet (work): gentry!zk3.dec.com |
| Unix Support Engineering Group | (home): mbg!world.std.com |
| Compaq Computer Corporation | addresses need '@' in place of '!' |
| 110 Spitbrook Rd. ZK03-2/T43 | URL: http://world.std.com/~mbg/ |
| Nashua, NH 03062 | "pdp-11 programmer - some assembler |
| (603) 884 1055 | required." - mbg |
+--------------------------------+-------------------------------------+