Path: utzoo!attcan!uunet!tektronix!reed!kamath From: kamath@reed.UUCP (Sean Kamath) Newsgroups: comp.sys.apple Subject: Re: More Kermit Problems Message-ID: <9361@reed.UUCP> Date: 18 May 88 00:54:20 GMT References: <8805160043.aa28782@SMOKE.BRL.ARPA> Reply-To: kamath@reed.UUCP (Sean Kamath) Organization: Reed College, Portland OR Lines: 61 In article SEWALL@UCONNVM.BITNET (Murph Sewall) writes: >> [misc problems with Kermit and a "65c02" upgrade. . .] >> >>I upgraded the //e by buying a 65c02 and having a friend burn the eproms >>for me. OK, this is wrong. But at least he could have just said "I enhanced my //e". In anycase. . . >Ah, there's the rub. Unlike most commware, Kermit actually USES Applesoft >ROM routines for I/O (which is why your problem appears when you try >file transfer). Yes, but a lot of stuff uses applesoft routines for math as well. >Whyever don't you get your ROM's from Apple instead of trying to pirate >what is really a pretty cheap upgrade. OR just leave the old ROM chips >in (I'm using a 65C02 but haven't upgraded the ROM's, I've found only a >few pieces of software that won't work; most things either work on an >unenhanced //e or only need the 65C02 but not the ROMs). Yeah. It was $70 and I kept everything. In anycase, using a 65C02 instead of the 6502 isn't really going to do much for you. In fact, darn little besides letting you run BLU. What is important (as far as I see it) is A) that you can now use interrupts more easily, and B) the screen update is a lot faster, as well as interruptable. This is all in the ROM, not the 65C02. (Yeah, I know you know this, but do *they*? :-) ) Sincethe new ROM's don't use any 65C02 code, you could actually just use the new ROM's. . . >If your going to violate copyright in public, don't expect a lot of >sympathy. No sympathy here. He should at least have known what he was doing. . . :-) Actually, I burned my own Proms (and thanks to jsilva, I can do that again) so that I could get rid of various and sundry nasty things in the monitor, and speed up AppleSoft insignificantly with a faster bascalc routine. What sorta bothers me is that if he did burn the proms correctly, then why doesn' it work? If it's because of a new applesoft, then where did it come from, and how can it work on a //c? All versions of applesoft are identical on all ][+ and //e, but not in the c. This included an upgraded //e. I mean, the enhanced //e AppleSoft ROM's haven't changed. So . . . . What's really wrong here? My guess is that he has somehow gotten a bad PROM or somesuch, and he really ought to go buy an upgrade. >--------------------- >Disclaimer: The "look and feel" of this message is exclusively MINE, > except when I modify it. > (subject to change without notice; void everywhere) > >ARPA: sewall%uconnvm.bitnet@mitvma.mit.edu Murphy A. Sewall >BITNET: SEWALL@UCONNVM School of Business Admin. >UUCP: ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL University of Connecticut Sean -- UUCP: {decvax allegra ucbcad ucbvax hplabs ihnp4}!tektronix!reed!kamath CSNET: reed!kamath@Tektronix.CSNET || BITNET: reed!kamath@PSUVAX1.BITNET ARPA: reed!kamath@PSUVAX1.CS.PSU.EDU US Snail: 3934 SE Boise, Portland, OR 97202-3126 (I hate 4 line .sigs!)