There are 9 messages totalling 350 lines in this issue. Topics of the day: 1. Backing up Pirates! 2. Rich Text Format (2) 3. Novaterm 9.6 w/ swiftlink and RAM expansion unit (4) 4. Re[2]: Backing up Pirates! 5. ACEterm: 14.4 ---------------------------------------------------------------------- Date: Wed, 7 Aug 1996 09:08:33 -0400 From: Christopher McLeod Subject: Re: Backing up Pirates! Thank you all for your help, but I do not think I made my problem clear, :-) I loaded Maverick, loaded the parameter disk with Pirates! v2 on it, highlighted that parameter, and to the left of the parameter name it said "custom copier." I pressed return to select the highlighted Pirates! v2 and it booted up a Pirates! copier. (try this in your own Maverick and you will see what I mean.) I went through the process of Inserting the Source Disk, and Inserting the Destination disk - for both sides - then attempted to boot the backup disk. I got a blue screen. That's it. :-( So I tried it again with a differet disk and a different drive. Same thing :-( HELP!! What am I doin wrong? Thanks Chris McLeod (of the clan MacLed) ------------------------------ Date: Wed, 7 Aug 1996 10:56:00 EST From: Christopher McLeod Subject: Rich Text Format Bob, Thanks so much for your help in learning more about the flexible "Rich Text Format." I have been keeping an eye on this format for converting between C= and PC, but the info you pointed me to gave me the closest shot yet. BUT, the only thing I could find was info on RTF codes for formatting your own converter. That is GREAT but I don't know how to program. :-( Could you help me find a C= to PC RTFer? Or how bout even teaching me how to modify my C= word processor to use RTF codes? Thanks again!!! Chris McLeod (of the clan MacLeod) ------------------------------ Date: Wed, 7 Aug 1996 11:09:00 EST From: Christopher McLeod Subject: Novaterm 9.6 w/ swiftlink and RAM expansion unit Question: If I am using SwiftLink in my cartridge port, how do I use a RAM expansion unit as well? Using a cartridge expander will not work because only one port can be selected (on a cartridge expander) at a time (thus you cannot be receiving data through your swiftlink AND writing data to your RAM expander). I am very excited about 9.6, but is there a way around this problem (without having to buy a RamLink for the pass-through port)? If worse came to worse, I could switch BACK to my Aprotek mini modem at 2400, but that would be NO fun at all! :-) Chris McLeod (of the clan MacLeod) ------------------------------ Date: Wed, 7 Aug 1996 11:25:05 -0500 From: Aaron Baugher Subject: Re: Novaterm 9.6 w/ swiftlink and RAM expansion unit Date: Wed, 7 Aug 1996 11:09:00 EST From: Christopher McLeod Question: If I am using SwiftLink in my cartridge port, how do I use a RAM expansion unit as well? Using a cartridge expander will not work because only one port can be selected (on a cartridge expander) at a time (thus you cannot be receiving data through your swiftlink AND writing data to your RAM expander). I use an EX3 from CMD, with a 512K REU plugged into the first port, and a Swiftlink in the second port. It's worked flawlessly from the start, with no need to change any dipswitches. I'm guessing that it couldn't talk to three cartridges at once, due to conflicts in their memory usage. Aaron -------------------------------------------------------- Aaron J. Baugher http://www.bcl.net/~abaugher Software Engineer abaugher@bcl.net Basic Communications, Ltd. _Roark_ on IRC -------------------------------------------------------- ------------------------------ Date: Wed, 7 Aug 1996 12:41:39 -0500 From: Irv Cobb Subject: Re: Novaterm 9.6 w/ swiftlink and RAM expansion unit On Wed, 7 Aug 1996, Christopher McLeod wrote: > Question: If I am using SwiftLink in my cartridge port, how do I use a > RAM expansion unit as well? > > Using a cartridge expander will not work because only one port can be > selected (on a cartridge expander) at a time (thus you cannot be > receiving data through your swiftlink AND writing data to your RAM > expander). You need a cartridge port expander -- lets you plug in more than one thing at once, and if everything's right, use them all at once, too! Mine is an old Aprospand that I found at a flea market. CMD will gladly ;) sell you one, too! > If worse came to worse, I could switch BACK to my Aprotek mini modem > at 2400, but that would be NO fun at all! :-) Zero fun, no doubt! :-) =============================================================================== | irv_cobb@radiks.net http://www.radiks.net/irv_cobb | | "Listen, for I will speak Files for Commodore Geos | | of excellent things..." Links to GARBC organizations | =============================================================================== ------------------------------ Date: Wed, 7 Aug 1996 12:44:58 -0500 From: Irv Cobb Subject: Re: Novaterm 9.6 w/ swiftlink and RAM expansion unit On Wed, 7 Aug 1996, Christopher McLeod wrote: (and I just re-read it after my previous reply. ;-) > Using a cartridge expander will not work because only one port can be > selected (on a cartridge expander) at a time (thus you cannot be > receiving data through your swiftlink AND writing data to your RAM > expander). > Yes it will. The SwiftLink and the REU map to two different memory locations, so they do not interfere with each other. So with the SL and the REU it is OK to have both selected on the expander. =============================================================================== | irv_cobb@radiks.net http://www.radiks.net/irv_cobb | | "Listen, for I will speak Files for Commodore Geos | | of excellent things..." Links to GARBC organizations | =============================================================================== ------------------------------ Date: Wed, 7 Aug 1996 13:53:22 -0400 From: Tony Perotti Subject: Re: Rich Text Format Where is the info on RTF available? ______________________________ Reply Separator _________________________________ Subject: Rich Text Format Author: COMMODORE COMPUTERS DISCUSSION at internet Date: 8/7/96 10:56 AM Bob, Thanks so much for your help in learning more about the flexible "Rich Text Format." I have been keeping an eye on this format for converting between C= and PC, but the info you pointed me to gave me the closest shot yet. BUT, the only thing I could find was info on RTF codes for formatting your own converter. That is GREAT but I don't know how to program. :-( Could you help me find a C= to PC RTFer? Or how bout even teaching me how to modify my C= word processor to use RTF codes? Thanks again!!! Chris McLeod (of the clan MacLeod) ------------------------------ Date: Wed, 7 Aug 1996 14:45:23 -0400 From: Tony Perotti Subject: Re[2]: Backing up Pirates! Subject: Re: Backing up Pirates! Author: COMMODORE COMPUTERS DISCUSSION at internet Date: 8/7/96 9:08 AM >I loaded Maverick, loaded the parameter disk with Pirates! v2 on it, >highlighted that parameter, and to the left of the parameter name it said >"custom copier." >I pressed return to select the highlighted Pirates! v2 and it booted up a >Pirates! copier. (try this in your own Maverick and you will see what I >mean.) Is there a V1 copier? >I went through the process of Inserting the Source Disk, and Inserting >the Destination disk - for both sides - then attempted to boot the backup >disk. I got a blue screen. That's it. :-( Sometimes these things just don't work. I don't know why but I have experienced the same frustration. Sometimes your hardware configuration can make a difference. Sometimes a vanilla 1541 is the only way the copier will work properly. Sometimes they don't like cartriges, or printers, or any devices besides #8 to be connected. Sorry, no really helpful advice here. Tony Perotti ------------------------------ Date: Wed, 7 Aug 1996 14:44:01 -0500 From: Aaron Baugher Subject: Re: ACEterm: 14.4 Date: Mon, 5 Aug 1996 22:12:21 -0230 From: Adam Vardy Whenever I load ACEterm, the bps is always set to 2400. So I always have to change it to 14.4. Does anyone know how to get around that so that it is always set to 14.4? From the ACE15.DOC manual (ftp://ccnga.uwaterloo.ca/pub/cbm/os/ace/): ********************************************************************* 3. SYSTEM CONFIGURATION The program entitled "config.edit" is used for editing the system configuration. The system will be configured according to the data in the file ".acerc" every time it starts up. Note that ".acerc" is a loadable binary PRG file; it is not in text format and is not meant to be edited with a text editor. The following data is included in the ".acerc" file: OFF SIZ DESC --- --- ---- $00 128 device descriptors, 32 entries of four bytes each. [For each entry, offsets: 0=device driver type, 1=device address, 2=secondary address, 3=flags. Described further below.] [stuff skipped.....] The offsets from $00 to $7F contain 32 four-byte fields, which are used to define the devices in the system. These fields will correspond to device names "@:", "A:", "B:", ..., "Z:", "[:", "\:", "]:", "^:", and "_:" (forgive the non-letter device names). The four fields will be defined as follows: 0 device driver type (0=Kernal non-disk, 1=Kernal disk, 2=console, 3=null, 4=ramdisk, 5=userport, 6=swiftlink, 255=empty) 1 device primary address (SwiftLink: I/O page of hardware) 2 device secondary address (SwiftLink: size of receive buffer in pages) 3 flags (KernalDisk: $80 for a disk will means that it has a CMD Real-Time clock) (UserPort: $00=use raw communication, $80=use packet-oriented communication, $40=use PA2 raw comm (use this w/GEOcable), $C0=use PA2 packet comm) (SwiftLink: below) For the swiftlink device, the "primary address" field contains the I/O page of the swiftlink chip (normally $de, but you can use any page you want). The "secondard address" field should be set to the number of pages that you want in your receive buffer. The factory-set default is for one page (256 bytes). This value is selected to conserve memory; you may be happier with a value of 4 (meaning 1024 bytes) or so. The maximum for this setting can be to the point at which the receive buffer crosses the transient-program area (about 12K with the standard configuration, less with a soft-80 C64), and the minimum setting is for 1 page. The size of this value doesn't matter when you are using 115.2kbps, since a special, dedicated-purpose, high-speed 256-byte buffer is used then. The "flags" field for the swiftlink should be set as follows. The 128 bit should be set to "0" if you want your modem parameters to be "8N1" or set to "1" if you want "7E1". No other word-length/parity/stop-bits settings are supported. The 64 bit should be set to "0" if you have a normal (double- speed) clock crystal (what CMD ships) or set to "1" if you have a hacked (standard-speed) clock crystal (1.8432 MHz). You will only be able to get 115.2kbps if you have this hack. The lower four bits should be set to select the baud rate, according to the following table. The factory-set default is to 2400 baud with 8N1 and a non-hacked SwiftLink ($08). bits hex dec baud ---- --- --- ------ 0000 0 0 unused 0001 1 1 50 0010 2 2 110 0011 3 3 134.5 0100 4 4 300 0101 5 5 600 0110 6 6 1200 0111 7 7 1800 1000 8 8 2400 1001 9 9 4800 1010 a 10 7200 1011 b 11 9600 1100 c 12 19.2k 1101 d 13 38.4k 1110 e 14 57.6k (not actually supported) 1111 f 15 115.2k (only available on a Fast C128 with hacked SL) If you don't want to waste memory on SwiftLink transmit and receive buffers in your configuration, then just remove the device entry for the swiftlink (normally device slot "x:") by setting the device type to 255 (empty). You don't have to worry about any memory-bleed problems with this device, since ACE will touch its I/O registers and intialize the SwiftLink chip only if you open a file to the device driver (i.e., use the "term" program). **************************************************************** Aaron -------------------------------------------------------- Aaron J. Baugher http://www.bcl.net/~abaugher Software Engineer abaugher@bcl.net Basic Communications, Ltd. _Roark_ on IRC -------------------------------------------------------- ------------------------------ End of COMMODOR Digest - 6 Aug 1996 to 7 Aug 1996 ************************************************* =END=