Will any of you be attending Macworld in SF next week?
Decide a place and time inside or nearby?
I plan to attend at least the first and last days, other days optional
depending on how my cash holds out.
Hi,
I just found a scanned/OCR'd copy of "State of the Art" by Stan Augarten on
the Smithsonian's website. It covers integrated circuits from their creation
right up to the 1980s - the URL is:
<http://smithsonianchips.si.edu/augarten/index.htm>
Some of the pictures are quite neat, as are a few of the little facts - the
origin of ZiLOG's name for one (that's on the Z-80 page).
I also came across the "Silicon Zoo" in my Firefox bookmarks list. It's a
site full of "chip art" - little doodles that chip designers sneaked into the
chip masks.
<http://microscopy.fsu.edu/creatures/>
There are also a few more on the Chipworks site - URL:
<http://www.chipworks.com/gallery/gallery_home.asp>
Later.
--
Phil. | Acorn Risc PC600 Mk3, SA202, 64MB, 6GB,
philpem(a)philpem.me.uk | ViewFinder, 10BaseT Ethernet, 2-slice,
http://www.philpem.me.uk/ | 48xCD, ARCINv6c IDE, SCSI
... Let's organize this thing and take all the fun out of it.
The 960 and 980 are completely different architectures.
980s are fairly conventional 16bit accumulator arch machines
while the 960s were oriented towards process control.
I have one of each.
Rumor has it that Steve Thatcher may have mentioned these words:
>if they allowed it, then they had to support it...
That sounds more like the M$ I know... ;-)
>As for Traveling Software, seeing how I worked for them for five years, I
>don't recall any buyout attempts from Microsoft. Traveling did go through
>hard times and it still around but not as they were back in the 90s.
Do you know of anything remaining from the days when they (you?) made
products for the Tandy Model 100/102/200 / NEC 8201A laptop machines?
Source code especially... ;-) There are still quite a few people
(relatively speaking, of course) using those little critters (me included)...
*Anything* that's still around would be greatly appreciated!
<Shameless Plug>
By the by, the mailing list I run for those laptops has 185 subscribers,
and one tireless Rick Hanson that *still* supports them.
</Shameless Plug>
<Shameless Plug2>
The archives for that mailing list can be found at:
http://ccarchive.30below.com/cgi-bin/wrapper
Right next to the Classic Computer Archive project list archives...
Hint, Hint, Hint -- we could always use more *volunteers* for that!
</Shameless Plug2>
Laterz,
Roger "Merch" Merchberger
--
Roger "Merch" Merchberger -- SysAdmin, Iceberg Computers
_??_ zmerch(a)30below.com
(?||?) If at first you don't succeed, nuclear warhead
_)(_ disarmament should *not* be your first career choice.
ard(a)p850ug1.demon.co.uk (Tony Duell) wrote:
> Problem is that if you use them as they were originally intended then
> you'll have problems because nobody else does that.
DEC was very good about using EIA-232 (and EIA-423 and other related
interfaces) the way it was supposed to be used, not the way the pee sea
world uses it.
MS
On Jan 6 2005, 13:48, Vintage Computer Festival wrote:
> On Thu, 6 Jan 2005, Pete Turnbull wrote:
>
> > Ditto for the serial card driver's HEX file. Finally you type
"PR#6"
> > so output goes to the disk, and you EXEC the two HEX files to
create
> > the actual binary as a disk file. Easy ;-)
>
> Actually, if you type PR#6 you'd issue a reboot to the disk drive ;)
So I would. Hmm.. I'm sure there was a PR#6 somewhere along the line,
though I don't remember why. It was 15 years ago I last did this
stuff.
--
Pete Peter Turnbull
Network Manager
University of York
Are there any significant differences between a TI-960B and TI-980B CPU?
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
Hi crew. Question about a Gridacase 1520. Is anyone familiar with
these laptops? This is a 286, really good shape. It won't boot, dead
as a doornail. The guy at the thrift shop told me it was working when
it was brought in the day before, now I see that two (or one) chips
are missing from under the flap in the top left right above the
keyboard. I figure they were lifted between dropoff and my buying it.
Any ideas if these chips, which I think are application roms, would
prevent the thing from booting? If so, is there such a thing as a
replacement available from someone here or elsewhere? The thing must
have been the first Toughbook or something, and I'd love to see it
working.
Thanks for any info anyone can share.
(does anyone still need a gmail invite? I have lots. )
Brian Mahoney
On Jan 6 2005, 12:05, Vintage Computer Festival wrote:
> On Thu, 6 Jan 2005, Steve Thatcher wrote:
>
> > the only reason Microsoft would not add binary transfer capability
as an
> > integral part of early DOS is that the people that needed it were
in a
> > small minority. It made no business sense to include features that
they
> > believed that most people really didn't need. Later in DOS, they
did
>
> What? It seems to me they had to do more programming work to prevent
> binary copying to the serial port.
No, actually much less. To make binary transfers work, they'd have had
to change the already-existing methods that they had. To prevent them,
they only had to add an error message and add one more case to a test
for a command-line switch.
--
Pete Peter Turnbull
Network Manager
University of York
This is the exact same method that's used to initiate the install of ADT,
the Apple Disk Transfer utility that's used to get Apple II disk images over
a serial link to a PC for archiving and use with emulators.
I believe that DOS has something similar which redirects the CTTY device to
COM1: (CTTY=COM1: or something like that). CTTY is the DOS shorthand for the
console terminal (screen and keyboard). Obviously this works only in
text-only DOS.
-----Original Message-----
From: cctalk-bounces(a)classiccmp.org
[mailto:cctalk-bounces@classiccmp.org]On Behalf Of Pete Turnbull
Sent: Thursday, January 06, 2005 3:19 PM
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Re: Importing binary files without removable storage nor
non-bundled software (was: TKermitFTP
On Jan 6 2005, 9:30, Vintage Computer Festival wrote:
> On Thu, 6 Jan 2005, Dwight K. Elvey wrote:
>
> > >And the programmers were not smart enough to figure a way around
this
> > >because...why?
> >
> > It would have been trivial for them to adopt a simple
> > block transfer for serial binary at the begining. I suspect
> > that the reason they didn't do this was that they didn't
> > wan't people to transfer programs from machine to machine.
> Your theory would make sense in an alternate universe where the
floppy
> disk was never invented ;)
I think the reason is simpler than Dwight implies, and more along the
lines of John's comment. Microsoft were in a hurry to make DOS work
for IBM, and there was simply no perceived need to add the
functionality. If you look at CP/M-related and Apple ][ systems, you
see they had (er, have) the same problem: no out-of-band way to signal
end of file. Several versions of kermit for Z80 machines and Apple ][s
therefore come with a little program to talk from a remote machine to
the serial port, start debug or equivalent, and stuff an
ASCII-converted copy of kermit over which debug then saves in
executable format.
I've still got the ASCII HEX files for an Apple ][. As far as I
remmeber there are two ways to get Kermit-65 onto an Apple. The first
way is to type "IN#2" to set he serial card as the input, and then on
the remote machine give the command to send the main file. It starts
with "CALL -151" to jump into the monitor, and then follows that with a
series of lines like "E00:38 A5"... which cause those bytes to be
stored in memory; then it calls the code it's just stuffed in, and that
in turn loads a huge number of much more compact (no addresses, no
spaces) lines, before finally issuing a "3D0G" to get back to BASIC.
Ditto for the serial card driver's HEX file. Finally you type "PR#6"
so output goes to the disk, and you EXEC the two HEX files to create
the actual binary as a disk file. Easy ;-)
The other way is superficially simpler; you type IN#2, transmit a small
file which creates a BASIC program and runs it; that program receives
and saves the two HEX files, and then tells you what to do with them.
Seems slightly simpler, but actually takes a lot longer, as I recall.
--
Pete Peter Turnbull
Network Manager
University of York