Pab

I believe it originally had to do with the drivers for the SX212 modem, which is what I used to develop Version 2.0. If not that, there was at least one modem that I had reports of not dropping into command with a DTR drop.

Figured out one thing. The modem isn't getting the initialization string if there is an existing connection. Easy fix: 32093 O.#2,13,0,"R:":X.36,#2,DBAUD,0,"R:":X.40,#C2,O,O,"R:":GOS.TWOSEC:?#2;"+++";:GOS.TWOSEC:? #2;"ATM0HV0X2Q0E0S0=1^M"; Replacing the ^M with a CTRL-M character.

The VBLANK routine stores 8 in this register to clear (actually set) the status of all console keys and set the console speaker line to output. When you read the register the it clears bit 1 for START, bit 2 for SELECT, and bit 3 for OPTION.

New build, 2023-12-17 Changes since last build: * When using SELECT key to log in locally, will now wait for all console keys to be released before performing local login. Avoids accidentally banning your own account. * Y2K compliance: Years from 80-99 assumed to be 20th century, all others 21st. * Deletes DOORPASS on successful return from external program, preventing perma-log of last user. * Fix to FTX crashing under Altirra BASIC. (Note: no configuration file changes have been made so you will not have to reinstall or run a converter program. Just copy these files over top of your existing install.) Link201X-231217-alpha.atr

It will push me to finish work on a new feature while debugging. I’m changing the menus from being hard coded in data statements to configured in files to allow a lot more customization.

When we pick a date/time, I'll post a new build here so we're all working on the same page.

Sure. Sundays are the best bet for me.

How do you think I feel? It’s kicking my ass and I WROTE the damn thing.

The connection and handshaking over Telnet converted to modem by Altirra can take a while. I've had to wait 30 seconds or more to connect. Are you giving it enough time? Weird thought: if you're running Altirra on PC for the BBS, can you connect through Bobterm running on Atari800Mac?

Grrr. Line 905: L$="CONNECT" Change L$ to F$.

Sigh. Yep. I broke a few dozen things with these add-ins.

I'm getting the Oops loop now, so it's something in selecting extenders I think. Working on it.

Playing around with some of my old Atari BASIC programs, I have a number of ML routines I had stored in dynamic strings. X=USR(ADR("hhh.... etc. and so forth. I'm thinking I might like to move some of these routines out of dynamic strings and into fixed locations in memory. Mainly so I can then port those programs to BASIC XE's EXTEND mode. But where to put them? These programs already use Page 6 for their non-relocatable routines. Mapping the Atari says that in addition to the cassette buffer, 480-4FF are "spare bytes" and implies that BASIC and floating point need $57E-$5FF. I know SpartaDOS X uses pages 4 and 5 at least at bootup and probably after, but I can deal with that. What hazards would there be to using locations $480-$57D for some of these short routines?

I have full network simulation, dialing and handshaking, and 19.2K, but otherwise same as you, Rick.

Weird. "2" is the numeric response for "RING." The modem should have been set up to auto answer. I was going to go through some long debugging steps, but in the end I think we might as well just pretend it's a 1030. 893 INPUT #C2,L$:IF L$="2" THEN ? #C2;"ATA{^}m";:GOTO 820 894 INPUT #C2,L$:BAUD$=L$:? L$:IF L$<>"1" AND L$<>"5" AND L$<>"10" AND L$<>"12" AND L$<>"15" AND L$<>"16" THEN 820 895 GOSUB 8953 896 POKE 77,I:? "{esc}{clear}";:TRAP ETR:POKE 752,O:POKE 82,O:POKE C7,O:GOSUB 481:U=-I:GOSUB SF:MSE=O Replace the carat contained text in 893 with CTRL-M. Replace the {esc}{clear} in 896 with a clear screen character. This way, if the modem sends a "RING" message, the BBS will send the answer command in case the auto-answer is screwed up.

But at least it's not working in a different way than it was not working before.

The error 12 is because it doesn't know where to go after reporting the error. (The variable WH - for 'where' - hasn't been set by that point.) It calls the error handling routine, prints an error code, and then tries to go to the recovery line number - which doesn't exist, so error 12. Eventually the real error scrolls off the screen. Plug a STOP in before the GOTO WH. Then you can take that out once we know the "real" error and I can fix it. Hopefully.

NEW BUILD: 231128 Alpha. Contains some major changes; suggest a reinstall if just playing around. Changes since last build: * Support for four file extenders for text files - ATASCII, ASCII, and up to two custom. * Initialization program now creates text files for each extender from cabinet files. No need to copy from “work disk” * Support for custom directory for E-mail base; no longer confined to D1: * Changing references to programs and CONFIG files to “D:” instead of “D1:” for DOS’s that default to current drive and path for "D:" * Message base sizes now defined in kilobytes, not sectors. * BBS now hangs up modem before waiting for call * All communication with serial port now at max speed * Path definitions for message bases and directories currently limited to 13 characters. Will expand that, but will take effort. * Delays in sending modem commands now timed by jiffy counter, to compensate for faster BASICs and hardware. * Renamed “AUTODOOR” to “MAINT” to better identify its purpose. * Expanded MAINT to allow more than one maintenance program to be run, the way it was originally intended. * Fixed bug preventing people from properly entering passwords or phone numbers, preveniting logins. Link201X-231128-alpha.atr

Wow. The things you forget after 30 years. Look at line 3231 of link20x.bas. I was starting work on networked E-mail! I'd forgotten all about that!

Weird question. I originally wrote this for the T: driver for the 830 and SX and have it doing an XIO 36 to adjust the transmission speed. With the R: driver(s), do I really need to adjust the transmission speed with each connection? Or could I just talk to the serial port/modem at 9600/19.2 and let the modem downshift the communication speed to whatever it needs? I'm finding difficulties taking incoming calls at 9600 and 14.4. The BBS keeps wanting to default down to 300 bps.

Sparta X. I can try with SD 3.2.

No guarantee it will solve your problem yet, but it's a step in the right direction. I think it has to have something to do with not properly responding to codes from the modem.

New build: 11/20/23 Adds support for speeds of 9600, 14400, 19.2K Removes all references to the printer and logging to printer Increased delay before and after sending modem escape codes, required for Altirra and other faster BASICs. link201x.bas

And another question: which BASIC are you running? Atari BASIC C or Altirra BASIC? I've found that Altirra BASIC runs too fast for the modem to respond to the escape code sequence before trying to send a command. Working on that.

Playing around with connecting through Altirra. What speeds are you connecting to the BBS at? I tried configuring Altirra to report a 9600 baud connection, and AtariLink didn't recognize the "Connect" message as having connected. Going down to 2400 and I was able to connect through Telnet correctly. Apparently "12" is the numeric response code equivalent of "CONNECT 9600." I never accounted for this because the fastest modems when I wrote the thing were at 2400. Looks like I've got some codes to start recognizing. Do you get to the "Waiting for a call" screen?