Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!columbia!rutgers!sri-spam!sri-unix!hplabs!sdcrdcf!trwrb!sansom From: sansom@trwrb.UUCP (Richard Sansom) Newsgroups: net.micro.atari16 Subject: Re: ARC for the ST (apologies) Message-ID: <1343@trwrb.UUCP> Date: Wed, 8-Oct-86 16:51:28 EDT Article-I.D.: trwrb.1343 Posted: Wed Oct 8 16:51:28 1986 Date-Received: Thu, 9-Oct-86 23:57:30 EDT References: <573@chinet.UUCP> <1341@trwrb.UUCP> Reply-To: sansom@trwrb.UUCP (Richard Sansom) Distribution: net Organization: TRW EDS, Redondo Beach, CA Lines: 65 Keywords: a bug in my xmodem program >This time it's your recent >posting of ARC and ALITE. In both cases, the UUENCODED files seem to have >been clobbered. In particular, in both cases there are three or four lines >in the UUENCODED files that are longer than all the other lines, i.e., >something like 113 characters across rather than the usual 62. Looks like >something went wrong in the transmission. > >Since this may be only at our site, do you think you could re-send the two >SHAR files to me? Thanx a lot... Unfortunately, the error is due to a new (buggy) version of xmodem I just wrote. Tonight I'll use the old version and repost the whole mess. Sorry to all burned by this one ("...we can all cut down considerably the amount of time and money we spend..." if some people would test their stuff before they post it! :-). While I'm here... >I'll probably go ahead and assemble the .S file, but just out of curiosity, >how do I edit a .PRG file? You could do one of a number of things: 1) edit the sector on which the bad bytes reside using a sector editor (easy) 2) load the program into memory using a debugger, modify the offending bytes, re-write the file (kind of easy) 3) write a small program to read in the file (in binary mode) and then re-write it (in binary mode) with the corrected bytes (not so easy) >Is there a way to choose whether you boot with TOS in RAM or TOS in ROM? I >have a TOS in ROM machine; how can I do the former? > >About FRMTPLUS: (a) Will disks formatted with FRMTPLUS work with the >ordinary TOS, and (b) will ordinary disks work with FRMTPLUS overlaid on the >basic TOS? In other words, (a) does FRMTPLUS only use unused portions of the >disk, such that you can still read them using the old slow algorithm if you >don't have FRMTPLUS loaded, and (b) is FRMTPLUS smart enough to use the >standard algorithm if it doesn't find the extra formatting information it >needs? I think you were saying that (a) would work, but I'm not sure. > >This sort of compatibility would be really nice. If it doesn't exist, how >can one copy an ordinary disk to a FRMTPLUS disk with only one disk drive? You can boot your ST with a RAM TOS image file disk in the disk drive and it will "override" the ROM TOS. You can probably get such a boot disk from a dealer, a club, or a BBS. One of the nice things about frmtplus is that the disk format is recognizable by TOS - you _can_ do such things as straight disk copies, etc., without having to reboot with RAM TOS and frmtplus.prg in AUTO. -Rich -- __________ ______ ____ _____ ___ /_________//___ ||__|/____|/__/ Richard E. Sansom ___ ____/ / ____________ TRW Electronics & Defense Sector / / / /\ < | /| / One Space Park Drive, R3/1028 / / / / \ \ | / | / Redondo Beach, CA 90278 /__/ /__/ \__\|__/ |__/ {...decvax,ucbvax,ihnp4}!trwrb!sansom