[comp.sys.apple] Questions about //c ROMs and Kermit

ct@mit-caf.UUCP (11/24/87)

Hello,

I have an early model APPLE //c purchased in 1984 with the System
Utilities V1.0 (Prodos 1.0.2), Appleworks V1.1, and Apple Access V1.0
that has been gathering dust for a while.  I have a few questions that
I hope some one on the net can answer for me.

1. What is the scoop on the new revisions of ROMs for the //c?  Is it
important to get them replaced?

2. I'm having trouble installing Kermit from the EXEC files downloaded
from LISTSERV@BROWNVM, how do I get a copy of it on 5 1/4" floppies?
I am aware that the version of Apple Access I have has bugs in the
XMODEM transmit and receives.

You can reply to me at this account or post it if you think others
might be interested in the information.

Thanks in advance.

Curtis Tsai	ARPA: ct@caf.mit.edu

fiddler%concertina@Sun.COM (Steve Hix) (11/25/87)

In article <561@mit-caf.UUCP>, ct@mit-caf.UUCP (Curtis Tsai) writes:
> Hello,
> 
> I have an early model APPLE //c purchased in 1984 with the System
> Utilities V1.0 (Prodos 1.0.2), Appleworks V1.1, and Apple Access V1.0
> that has been gathering dust for a while.  I have a few questions that
> I hope some one on the net can answer for me.
> 
> 1. What is the scoop on the new revisions of ROMs for the //c?  Is it
> important to get them replaced?
> 
The new ROMs give you MouseText character support, some improvement in
screen handling during modem use at 1200 baud and above, and support
for 3.5" drives on the //c.  Nothing on the old ROMs are really "broke".

If you plan on using a modem sometime in the future, you should have
the system clock crystal replaced; the original ones tend to be just
a bit out of spec, making trouble with 1200 baud and above operation.

	seh

kamath@reed.UUCP (Sean Kamath) (11/28/87)

In article <34871@sun.uucp> fiddler%concertina@Sun.COM (Steve Hix) writes:
>In article <561@mit-caf.UUCP>, ct@mit-caf.UUCP (Curtis Tsai) writes:
>> 
>> 1. What is the scoop on the new revisions of ROMs for the //c?  Is it
>> important to get them replaced?
>> 
>The new ROMs give you MouseText character support, some improvement in
>screen handling during modem use at 1200 baud and above, and support
>for 3.5" drives on the //c.  Nothing on the old ROMs are really "broke".
>
>If you plan on using a modem sometime in the future, you should have
>the system clock crystal replaced; the original ones tend to be just
>a bit out of spec, making trouble with 1200 baud and above operation.
>
>	seh

You are just a little confused about what got upgraded to what.

The //e ROM upgrade consisted of four chips, a 65C02, a video ROM, and
the CD and EF ROMS. They gave the improved screen handling which inprove
things at 1200 baud (they turn on interrupts, as far as I know, besides
doing things right.)  Also, they have "improved" but slower interrupt
handling, caused by such niceties as knowing the machine state on
interrupt.  The video ROM is responsible for the mousetext characters.
The 65C02 didn't really do much of anything, but it came with it.

The //c has had three or four facelifts, depending on how you look at
it.  The first //c has a known problem with it's system crytal, which
made it fail with modems at 1200 baud.  This involved a complete
motherboard exchange, and was free, provided you proved either A) You
had purchased an Apple modem, or B) that it failed at 1200 baud with a
modem correctly set up.

The next upgrade was to 32K ROMs.  When I upgraded Robins, I did it
because she got a 3.5 inch drive.  Thus, the upgrade was free, as you
need them to run the 3.5 incher.  On the //e, the ROM on the card take
care of it.  I thought when I first read about it from Apple that it was
just a ROM upgrade, but when we went to do it, it turned out to be a
motherboard swap.  Of course, the only difference was the ROM and a
butterfly trace was cut (or mabe it was a -<||>- that was soldered, but
I don't think so.)  This ROM contained the smartport stuff, got rid of
pr#7 booting of the external disk, put appletalk stuff there instead,
and generally did good things for the //c.

The third change was to the motherboard, allowing easy memory expansion
with *APPLE'S* upgrade only.  I don't know of any change it made, except
that the mouse stuff is in slot 7 now, and the RAM drivers are in 4.
Nice, since mousepaint, which comes with the mouse, wouldn't run with
the mouse anywhere but slot 4.  Figgers eh?

Fourth and last, the //c has a new case, platinum, and generally looks
more "business like"  Ever wonder why Apple went to platinum?  Seems
they did a survey and found out people found platinum more business
like.  Thanks IBM.

Tan hides hand grease better, though.

Question.  Since they moved the pr#7 stuff (the old AppleTak stuff that
never worked) is it still around?  Note that I may have the last change
a little bungles, as I haven't actaully run into it.  Robin's going to
get an Ultra 2, since I want the clock in it. . .(Yeah, I know, it'a
Robin's machine. . .But, hey, I use it too!)


Sean kamath



-- 
UUCP:  {decvax allegra ucbcad ucbvax hplabs ihnp4}!tektronix!reed!kamath
CSNET: reed!kamath@Tektronix.CSNET  ||  BITNET:  reed!kamath@Berkeley.BITNET
ARPA:  tektronix!reed!kamath@Berkeley <or> reed!kamath@hplabs
US Snail: 3934 SE Boise, Portland, OR  97202 (I hate 4 line .sigs!)

kamath@reed.UUCP (Sean Kamath) (11/28/87)

I almost forgot.  The //e enhancement added some new monitor commands,
among them search and text entry (i.e.  fded<f800.ffffs would look for
fded between f800-ffff, and 300:'h 'e 'l 'l 'o would put the hex codes
for "hello" at $300.) as well as a miniassembler, enterable by '!' en
exitable (are those real words?) by CR alone.

In the //c, they gave us back step and trace, but no search.

However, on the //e, there is no support for miniassembling 65C02, or
even listing it.  type this 300:80 n 300L and you get 300: 80  ???
on a //c, you get 300: 80 xx BRA xxxx.  THe //c new it was using a C02.

Sean Kamath

-- 
UUCP:  {decvax allegra ucbcad ucbvax hplabs ihnp4}!tektronix!reed!kamath
CSNET: reed!kamath@Tektronix.CSNET  ||  BITNET:  reed!kamath@Berkeley.BITNET
ARPA:  tektronix!reed!kamath@Berkeley <or> reed!kamath@hplabs
US Snail: 3934 SE Boise, Portland, OR  97202 (I hate 4 line .sigs!)