>A search of the web yielded lots of links, but no datasheet. I want to
know
>how to program it and its electrical characteristics. You know, the stuff
>on a datasheet. Zilog's web site doesn't have it.
8530 is the Zilog SCC chip, as is the 8030. The differ only in bus
interface.
The 8530 is the non multiplexed bus part.
It's a dual channel serial device with DMA and interrupt logic for Z80
series cpus. Programming of the functions are similar to Z80 SIO
and related parts in a general way. It's a nontrivial device to use.
Contact Zilog for data or check their page under SCC.
>[ Its the chip used in the Apple Lisa and Mac and LOTS of other devices. ]
You sure of this?? It's not really friendly to the 68k buses.
Allison
Hmm, if someone writes a way to do all the archiving, I'd be happy to
provide my 4381 for some serious processing power ;p
Will J
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Sounds like a cache card for a PowerPC-based Mac. -dq
> -----Original Message-----
> From: Stan Perkins [mailto:stan@netcom.com]
> Sent: Thursday, June 01, 2000 6:22 PM
> To: classiccmp(a)classiccmp.org
> Subject: Please help ID this Mac board--I hope it's old enough for the
> list!
>
>
> Hello all,
>
> I just came across this small PCI type board, labeled:
>
> APPLE COMPUTER INC.
> 820-0510-A c1993
>
> It also has a chip on it with the label:
>
> 341S0021
> c 1983-93 Apple
> ^
> |
> |-----That's why I'm hoping it's old enough to qualify :-)
>
> Anyway, on one side of the PCB it's got four large quad flat
> pack chips,
> from Philips, TI, VLSI, and BT, and on the other side (with the Apple
> labeled chip I mentioned earlier) it has two rows of 8 each Toshiba
> TC528128BJ-80 RAM chips. On the back end it has a DB-15F
> connector (like
> the old Apple monitor connector) and two round DIN connectors
> labeled "S
> IN" and "S OUT" with 7 female contacts each.
>
> It came in a box labeled DOS Compatibility Card for Macintosh, but I'm
> beginning to think it's not.
>
> Any clues are greatly appreciated!
>
> Thanks,
> Stan
>
> I don't think that would work. I've cooked EPROMs for months
> without any change in their functioning.
So did a partner of mine.... using a homemade eraser made from
a UV sterilizer unit taken from a scrapped dialysis machine.
It was an Intel eprom, a 2732 or 2764, ceramic case, quartz
window. The embedded system we were developing was an auto-
mated knife sharpener (not to be a consumer product).
During debugging, we had the prototype out of the case. Things
were working fine and it was time for the first install into
the van (which would drive from restaurant to restaurant doing
the knife sharpening thing). Put unit in case, fire up, no
operation. Take unit out of case, fire it up, everything works.
We looked for warping of the PC board, kinking of cables, and all
sort of things that coould glitch the unit out. Nada. Finally,
thinking that we were only going to see how the case was screwing
with the PC board from inside the assembled unit, we cut an access
panel in the aluminum, and shined a flashlight inside. It happened
to hit the EPROM window and voila! the unit starts running.
After a long call with Intel engineers, it was determined that
too much UV could fry the EPROM such that it would only function
correctly when light was shining onto the substrate through the
window!
An EPROM that was afraid of the dark. To get the prototype out
the door, we built it a night-lite, and everything was fine.
-doug quebbeman
>Sellam Ismail <foo(a)siconic.com> writes:
>> But can you dedcode 6&2 encoded bytes in realtime on a 6502? Something
>> tells me it's not fast enough to do this.
>
>If you're clever enough, you can do it. I previously cited several
packages
>that did it.
Cant speak for the 6502, but NS* did it with minimal hardware a few years
earlier and it was a respected design. Not a whole lot of ttl on the board
either considering it was S100, Boot prom and FDC.
Allison
In a message dated 6/2/00 2:31:30 AM Eastern Daylight Time, foo(a)siconic.com
writes:
> On Fri, 2 Jun 2000, David Vohs wrote:
>
> > I'm sorry I can't help you find one. But I hope that you are looking for
> > them only for their collectable value. I think that AT&T, and any other
> > phone company, has probably long since removed this nice little
"feature"
> > from the computers that run the lines. So if you're looking to make some
> > free phone calls, I don't think it will work. But then again, I don't
work
>
> > for a phone company, so I could be completely wrong on this.
>
> C'mon, give me a break. I don't even think the youngest of fools can be
> that naive :)
>
> No, this is purely for historical reasons. I'm developing an exhibit
> around the now legendary (and now very useless) "blue box".
>
> Sellam
back then, the telco used electromechanical systems which were easy to hack
and get away with. nowadays, it's electronic with much more automation and
security so its harder to cover one's tracks. i think red boxes still work,
but some COCOTs have been modifed to prevent this.
DB Young
hurry, hurry, step right up! see the computers you used as a kid!
http://members.aol.com/suprdave/classiccmp/museum.htm
>I'm looking for one of the original Cap'n Crunch cereal >whistles that
>could produce the 2600Hz tone. If you >know the story of John Draper
>(a.k.a. Cap'n Crunch) then >you know what I'm talking about.
>
>I'd also like to get a hold of the box the whistle came >in. I'm also
>looking for the October 1971 issue of >Esquire magazine that featured the
>article with John >Draper talking about the "blue box".
>
>If anyone has any idea where I might find these items, >please e-mail me
>directly at <sellam(a)vintage.org>.
>
>Thanks!
>
>Sellam International Man >of Intrigue and
>Danger
>--------------------------------------------------------->----------------------
>Looking for a six in a pile of nines...
>
> Coming soon: VCF 4.0!
> VCF East: Planning in Progress
> See http://www.vintage.org for >details!
I'm sorry I can't help you find one. But I hope that you are looking for
them only for their collectable value. I think that AT&T, and any other
phone company, has probably long since removed this nice little "feature"
>from the computers that run the lines. So if you're looking to make some
free phone calls, I don't think it will work. But then again, I don't work
for a phone company, so I could be completely wrong on this.
Best of luck either way.
____________________________________________________________
David Vohs, Digital Archaeologist & Computer Historian.
Home page: http://www.geocities.com/netsurfer_x1/
Computer Collection:
"Triumph": Commodore 64C, 1802, 1541, FSD-1, GeoRAM 512, Okimate 20.
"Leela": Macintosh 128 (Plus upgrade), Nova SCSI HDD, Imagewriter II.
"Delorean": TI-99/4A.
"Monolith": Apple Macintosh Portable.
"Spectrum": Tandy Color Computer 3.
"Boombox": Sharp PC-7000.
____________________________________________________________
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
> From: Stan Perkins <stan(a)netcom.com>
> Subject: Please help ID this Mac board--I hope it's old enough for the list!
>
> Hello all,
>
> I just came across this small PCI type board, labeled:
If it's what I think, it's actually a PPC 601 PDS (processor direct slot)
card.
> APPLE COMPUTER INC.
> 820-0510-A c1993
>
> It also has a chip on it with the label:
>
> 341S0021
> c 1983-93 Apple
> ^
> |
> |-----That's why I'm hoping it's old enough to qualify :-)
Not that old... but none the less...
> Anyway, on one side of the PCB it's got four large quad flat pack chips,
> from Philips, TI, VLSI, and BT, and on the other side (with the Apple
> labeled chip I mentioned earlier) it has two rows of 8 each Toshiba
> TC528128BJ-80 RAM chips. On the back end it has a DB-15F connector (like
> the old Apple monitor connector) and two round DIN connectors labeled "S
> IN" and "S OUT" with 7 female contacts each.
Sounds like the AV card for the 1st-generation (NUBUS) PowerMacs
(6100/7100/8100).
> It came in a box labeled DOS Compatibility Card for Macintosh, but I'm
> beginning to think it's not.
More likely, someone removed it from an AV 6100 to install the DOS card.
Interesting find, though...
> Any clues are greatly appreciated!
You're welcome.
<<<John>>>
My two cents, in decreasing order of sanity.
Maybe it's a little far from the original goal*, but for the cost of a
few extra bytes in track/sector numbers, the same format might handle
the contents of hard disks. And there's probably a lot fewer "whacko"
formatting concerns with those than with floppies - 99.44% of the time,
just getting a big pile of sectors might be as much as you'd need.
AFAIK, nobody wrote quarter-tracks on hard disks, or tried to copy-
protect software by making bad sectors, or any similarly-goofy stuff.
And machines that used hard disks didn't generally fixate on the number
of tracks or sectors.
(How much of that is true? Discussion?)
My reaction to XML et al is generally negative too, and also not for
any good reason that I could put my finger on. Maybe it seems like
it would be work to parse, and I like to imagine my poor old 8-bitters
being able to make use of the images themselves, not just the recipients
of an end-product that was produced by a modern machine that digested
the image. As I said, it's not entirely a rational concern; those old
8-bitters could do it just as well as any modern machine, given enough
time and storage and programming... Maybe that's it, coding up an XML
parser for a CoCo seems like it would be much more work than having
some byte-by-byte record definition. So maybe you XML supporters need
to hit that point a little harder.
Speaking of which, maybe some compressed representation of repeated
identical sectors could be good. If a floppy was 10% full, and the
remaining sectors were full of some "empty" byte pattern, It would be
nice if those "empty" sectors didn't take up space in the image. Of
course, the image could just omit sectors, but then you'd need
intelligence to decide which sectors to omit; almost as bad as needing
to know which files to keep. The only way to be safe is to get it all,
and maybe take advantage of patterns in the data to compress it a bit.
Then again, if I care about image size, I suppose I could always use
any standard compression utility on the image. And then I'd want to
get decompression going on the TRS-80...
Okay, I think it's time to stop babbling.
Bill.
* I'm _not_ going to make any bad puns about being on the wrong track. :-)
On Thu, 1 Jun 2000 13:34:55, Sellam Ismail <foo(a)siconic.com> wrote:
] Current iteration:
]
] Desk Descriptor Header
]
] 1. Host computer type (2 bytes allowing up to 65536 models to be specified)
] 2. Hard/soft sector flag (1 byte)
] 3. Number of tracks (1 byte)
] 4. Disk drive RPM (2 bytes: 1 for whole number, 1 for fraction) [1]
]
] Optional:
]
] 5. Archiver Name (24 bytes)
] 6. Archiver E-mail Address (48 bytes)
] 7. Disk Title (64 bytes)
] 8. Publisher (if applicable) (24 bytes)
] 9. Year of Publication (2 bytes)
] A. Archive Description (256-512 bytes)
] B. Archive Date (4 bytes: 2 bytes = year, 1 byte = month, 1 byte = day)
] C. Archive Time (3 bytes: hour, minute, second)
]
] ***Does it make sense to have separate fields as specified #7-9 or should
] we rely upon the archivist to include that data in the description? I
] think so since this is important information that should be forced to be
] included with the archive.
]
] Maximum size: 685 bytes
]
] [1] If applicable
]
] Note: Encoding type moved to Track Descriptor Header
]
]
] A Track Descriptor Header will precede each track and give an overall
] description of the track:
]
] Track Descriptor Header
]
] 1. Track number (2 bytes: 1 for whole number, 1 for fraction) [1]
] 2. Disk Side (1 byte)
] 3. Track format (logical or raw; host computer specific) (1 byte) [2]
] 4. Track size in bytes (2 bytes) [3]
] 5. Sector format (single-density, double-density, etc) (1 byte)
] 6. Encoding type (1 byte)
] 7. Sectors in this track (1 byte)
] 8. Interleave (1 byte)
] 9. Bytes per sector (2 bytes)
] A. Bits per byte (1 byte)
] B. Offset to next Track Descriptor Header (2 bytes)
]
] Size: 15 bytes
]
] [1] Fraction allows for specifying half- or quarter-track.
] [2] If the track is in "raw" format then fields 3-9 are ignored.
] [3] The total size in bytes of the raw track image.
]
]
] I can start to see where the flexibility afforded by a markup language
] makes sense. I just can't figure out why I am still resisting it though.
]
] So, are we on the right track? The wrong track?
]
] Sellam International Man of Intrigue and Danger
] - -------------------------------------------------------------------------------
] Looking for a six in a pile of nines...
]
] Coming soon: VCF 4.0!
] VCF East: Planning in Progress
] See http://www.vintage.org for details!