Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!rutgers!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hp-pcd!uoregon!omepd!intelisc!littlei!ogcvax!schaefer From: schaefer@ogcvax.UUCP (Barton E. Schaefer) Newsgroups: comp.sys.cbm Subject: Re: Kermit 2.0 Message-ID: <1388@ogcvax.UUCP> Date: Thu, 20-Aug-87 14:23:35 EDT Article-I.D.: ogcvax.1388 Posted: Thu Aug 20 14:23:35 1987 Date-Received: Sun, 23-Aug-87 05:35:56 EDT References: <9500001@altger.UUCP> <2668@husc6.UUCP> <1336@killer.UUCP> <401@astroatc.UUCP> Reply-To: schaefer@ogcvax.UUCP (Barton E. Schaefer) Organization: Oregon Graduate Center, Beaverton, OR Lines: 51 Summary: was Re: vt100 on C-64 wanted In article sentinel@killer.UUCP (The Sentinel) writes: >In article <401@astroatc.UUCP>, brucec@astroatc.UUCP (Bruce Cantrall) writes: >[inclusions and counter-inclusions deleted to save space and time] >> I load a program I wrote myself and login to the system and as soon as >> the login is sucessful, I cycle the power on the C-64 and boot Kermit. >> It works OK, I guess. I am going to try to relocate Kermit somewhere else >> in memory and add my auto-dial routines to the boot program. >> >> Is there an easier way of doing this? > > Not really. Perhaps you could try having your program LOAD and RUN >the main Kermit program... it will LOAD just fine without the autoboot >loader, and it can be RUN directly. If your dialing program is in BASIC, >just end it with a LOAD"KERMIT",8... > I have tried Sentinel's suggestion, and it doesn't seem to work predictably. The 4.3 BSD system to which I login won't wait more than 60 seconds after carrier-detect for me to type my login name; I then have another 60 seconds to type my password, about 120 seconds to respond to the prompt from tset in my .login, etc. That means I don't have time to load Kermit after connecting before I have to start talking to the host. My solution was to hack up a dumb-terminal program (written in BASIC) that came with my modem to do two things: 1) load a machine-language program to dial the !#*%&@ modem, which is not Hayes compatible; and 2) load Kermit when I hit a function key, which I do after I have talked to the host long enough to get a csh prompt. About 30% of the time, Kermit will load and run. Another 60% of the time, it will load and bring up the prompt, but then just sits there with the keyboard dead. The other 10% of the time it won't even finish loading. I can't cycle power on my 64 and then load kermit, because the blasted modem hangs up when the 64 is shut off. Anybody out there have any suggestions? I have noticed this appear-to-load-and-then-sit-there behavior with other programs loaded after another program has been running awhile. Is this a common problem or is something wrong with my 64? Aside: I occassionally suspect I have a weird 64. According to one place I had it serviced, it came from the factory with one of the video chips installed backwards. This didn't cause any problems (the chip evidently drives the monitor outputs, and I was using the 64 hooked up to a TV) until I left it on for 24 hours once; then it overheated and fried something else with it. -- Bart Schaefer Dept. of CS&E CSNET: schaefer@Oregon-Grad Oregon Graduate Center UUCP: {ihnp4,seismo,sun}!verdix \ 19600 NW Von Neumann Dr {hplabs,ucbvax,decvax}!tektronix !ogcvax!schaefer Beaverton, OR 97006