CompuServe Thread

#Amiga RS-232 input

17 messages in this thread
#42108From: Larry Phillips/ICUGNov 15, 1985 12:46 AM
Glad it helped Jeff. I will be UPLoading a C program that strips all the unAmiga junk that gets transferred from most sources as soon as I figure out how to get the program and source over to the 64. I can't seem to UPL with Maxicomm, which arrived today. Regards, Larry. *** There are replies: 42110, 42111 Enter command, N for next message or <CR> for menu : n
#42110From: Joe RumseyNov 15, 1985 12:56 AM
I had some problems uploading to a local bbs with maxicomm..it didn't stop at the end of the file, but I've uploaded 2 programs to CIS successfully (1 of which hasn't appeared yet) with it. Joe R. Enter command, N for next message or <CR> for menu : n
#42168From: Larry Phillips/ICUGNov 16, 1985 4:52 AM
Joe, did you use the ASCII or BINARY option of XMODEM? I'll try another UPL with BINARY to see if it works. Regards, Larry. *** There is a reply: 42180 Enter command, N for next message or <CR> for menu : n
#42180From: Joe RumseyNov 16, 1985 1:01 PM
for uploading sport.bas and saucer.bas I used send text with Xmodem from maxicomm, and told CIS it was 7 bit ascii, worked fine. BUT when I try to upload to a local fido-net board, it doesn't work..just keeps sending blocks after the file has all been sent(ie:says the file has 28 blocks, and keeps sending up to like 36 blocks before I stop it.) so I'm going to download xterm3.bas as a temporary solution, but hopefully there is a way to get maxicomm to work correctly. Joe R. *** There are replies: 42183, 42184, 42237 Enter command, N for next message or <CR> for menu : n
#42183From: Kaelin ColclasureNov 16, 1985 1:56 PM
Joe, I wrote Xterm3 and have used it to download several programs, but some people seem to be having problems with it. Could you let me know if you have any trouble? I already know it hangs up a lot, and I am working on a fix to thet problem as well as adding a bigger buffer and upload capability. If you have any suggestions for improvments I am more than willing to listen, but I'm not going to get *too* fancy until I get either MSBASIC or a 'C' compiler… PS. When the program hangs, just tap the space bar and it will resume just fine. It hangs because there is no timeout in the routine to recieve a character, and I have fixed this in the newest version (which isn't ready for release yet). Xterm3 wasn't really ready for the public, but I figured anything was better than nothing… — Kaelin C. Enter command, N for next message or <CR> for menu : n
#42184From: HR LaserNov 16, 1985 2:03 PM
Joe; The way to get Maxicomm to work correctly is to put your original disk in an envelope and mail it back to Maxicorp and tell them that you want it upgraded to version 1.02. I spoke with the author and president of Maxi, Mike Lehman and that is exactly what he told me to do. Regards *** There is a reply: 42190 Enter command, N for next message or <CR> for menu : n
#42190From: Joe RumseyNov 16, 1985 3:25 PM
ahhh, thanks. I'll send it monday(too late to send it today) later. Joe R. Enter command, N for next message or <CR> for menu : n
#42237From: Larry Phillips/ICUGNov 17, 1985 3:12 AM
Thanks Joe, I will try an ASCII UPLoad tonight (of my little 'strip' program source in C). Hope it works. If not, I'll try a buffer transfer instead, and take a look at it when it's posted. Regarding the problems of some users in DOWnloading, that of truncated lines seems most likely to be caused by the difference betwen UNIX-like line terminators (Linefeed) and the rest of the world (C/Rs). This STRIP program will do the job of converting any text file to the proper format by the simple expedient of removing C/Rs, and any other non-printing characters. The C/Rs are replaced with Linefeeds. As soon as I can get hold of UPL capabilities (proper Xmodem binary), I'll UPL the object for those that don't have C. Regards, Larry. *** There is a reply: 42253 Enter command, N for next message or <CR> for menu : n
#42253From: Joe RumseyNov 17, 1985 1:31 PM
I've had some problems with the buffer transfer on maxicomm..tried sending my saucer program using it, but it only sends the program up through about line 890(that's line 890 in basic, it's not an 890 line file) the only reason I can figure out is that while it's sending the file, compuserve is echoing the characters, and at the same time trying to send a ctrl-s, but MaxiComm doesn't look at what CIS is serving until AFTER the send is complete, so it doesn't see the ctrl-s's until it's already sent too much for CIS to handle. tell me what you think. Joe R. *** There is a reply: 42284 Enter command, N for next message or <CR> for menu : n
#42284From: Larry Phillips/ICUGNov 17, 1985 10:44 PM
<sigh> Joe, I am even having problems with Maxicomm on text buffer capture when trying to grab stuff that way from the DLs. I xalled the bulletin board that Maxicorp set up in Pebble Beach, and at considerable expense, captured probably 80K of text, only to find out later that all the files contained were $51CB repeated over and over. Earlier tonight, I tried to get some stuff from another SIG, (an XMODEM, KERMIT, and a B protocol in C), and found that though two files captured perfectly, the other five or so didn't. Time to start serious telecomm code generation I think. Regards, Larry. Enter command, N for next message or <CR> for menu : n
#42318From: Joe RumseyNov 18, 1985 9:01 PM
haven't had any problems capturing stuff with maxicomm, only sending stuff. (of course, I haven't tried any 80k text files either). hope either maxicorp gets their act together, or someone writes a good term prog.(I'd do it right now if only I knew C. I do know some, but I'm still learning it.) adios.. Joe R.
#42333From: Larry Phillips/ICUGNov 19, 1985 1:17 AM
Well Joe, mine will replaced very soon, and I'll post a critique as soon as I have used it for a while. Regards, LArry.
#42111From: Tim AveryNov 15, 1985 1:31 AM
Larry…RE MaxiComm: How did you configure your RS-232 cable? The Amiga book is full of 'Don't use standard cables' messages. (because of voltage output of some Amiga pins) Enter command, N for next message or <CR> for menu : n
#42169From: Larry Phillips/ICUGNov 16, 1985 4:54 AM
Tim, I used a cable that has 11 pins wired in only, none of which are dangerous. The only ones I am using right now are pins 2, 3, and 7. Easy enough to wire your own, and a lot less money too. Regards, Larry. *** There is a reply: 42264 Enter command, N for next message or <CR> for menu : n
#42264From: Kelly KauffmanNov 17, 1985 5:50 PM
I discovered something interesting about hooking up a Hayes modem to the Amiga. All the pins that carry voltage aren't even connected internally in the Hayes. I use a cable that has all of the pins connected, and it works fantastic!!! You don't have to worry about hooking up voltage lines and it makes it VERY easy to make your own cable and save $$$$$$$$$$$$$$$$$$$$$!! *** There are replies: 42279, 42285 Enter command, N for next message or <CR> for menu : n
#42279From: Larry MillerNov 17, 1985 9:51 PM
There are few products so well thought out and engineered as the Hayes modems. They seem to work on just about anything. Enter command, N for next message or <CR> for menu : n
#42285From: Larry Phillips/ICUGNov 17, 1985 10:47 PM
That's good to hear Kelly, though I would advise anyone doing the same to check the modem they plan to use, especially if it is not a Hayes, but a compatible. Speaking of saving money, I currently am using a three wire hookup. GND, RXD, TXD. The only reason I'm doing it this way is is because I'm too lazy to keep hauling the Amiga out from under the monitor shelf to change the cable over to the 64 and back. Regards, Larry. Enter command, N for next message or <CR> for menu : n