GBBS 2.3, Apple IIgs
#1
I have gone through the threads here and trying to piece together a solution with not much luck.  I can cause the system to answer but it always at 300 baud and there is nothing on the client side and anything typed on the client side does not appear on the BBS side.

Specs:
Apple IIgs
Apple Super Serial Card in Slot 2 (Set with DIP switches for 9600 baud 8N1)  Triangle block set to modem
Using a custom, pin moveable connectors so I can experiment.

SSC Switches:

SW1: off off off on on on on
SW2: on on on on off on off

I am using a cable with pins 1,2,3,4,5,6,7,8,19,20 on the SSC to Modem the only difference is that the DSR(6) on modem is going to CD(8) on the SSC.  I read that somewhere but do not remember where.

Init String: ATS0=1S2=128V0*D1&C1&S2&D2&Q0X1

The BBS will come up and it will connect, I will see nothing on the client.  When disconnecting, the BBS then locks up and it shows everything on the wait screen except for the time and the upper right spot where the letters spin about is locked as well.  I have to reboot the machine.

One time, one time only I had a terminal program on my iPhone and it connected at 9600 baud and I could type to the BBS from the phone.  Only odd thing was every character in the response of what I was typing was duplicated, like hheelloo  wwoorrlld.  When I disconnected, the BBS locked up as described above.  I have not been able to do this since.

1) Is there a pinout of the WiModem232 OLED?  I skimmed through the manual to no avail.
2) Anyone have a cable, speed, and init string that works with GBBS?

I have purchased the GBBS manual from Apple Puget Sound Program Library Exchange.  But as one would expect, the highest modem they reference is a US Robotics Courier 2400.  But in the configuration of the BBS when you install it you can use a Hayes Smartmodem 9600 CTS/RTS (I Believe is the title for the CTS/RTS, I am not near the Apple at this time)  But I am using this modem as my reference connected to the super serial card which is the question before when setting up the modem in the software.

I really want to get this to work, I feel so close, yet so far and I have been working on this almost a year.

Your help is greatly appreciate.

BTW: I updated to the latest firmware on the modem.
Reply
#2
You should check the thread here about the SSC to make sure the DIP switches really are correct. There are tested setups posted. I don't have a IIgs anymore, so I can't directly help with this issue. See here for details on the IIgs setup:

https://www.cbmstuff.com/forum/showthrea...57#pid3157

If you can call out from this machine and connect to other BBS's then the WiModem232 itself is fine, and that would also prove that the SSC and IIgs serial interface are working.

The pinout for the WiModem232 is 100% exactly the industry standard for a modem (they are all the same). MAKE SURE you are using the proper cable for your IIgs! MAKE SURE you are not using a NULL modem cable! YOU DEFINITELY do not want DSR going to CD!

Type that Init string into your terminal program and see if it comes back with an error. That is a bunch of odd settings for sure (see link above for the normal init string used with terminal software, which would be the same for a BBS). Pay particular attention to the polarity information as that might apply to the BBS program you are using. Getting characters echo'd back to you can be normal, depending on the setup... the ECHO is enabled (ATE1).

The WiModem232 is a 100% exact Hayes modem emulation. This is just like plugging a real Hayes modem into your computer. So, if there is a Hayes modem driver, select that for use with the WiModem232.
Reply
#3
Hey man, if you manage to figure out a solution post it on here. i'm having the exact same problem you are except with a IIe Platinum.
Reply
#4
(10-16-2024, 08:00 PM)Dr. Felch Wrote: Hey man, if you manage to figure out a solution post it on here. i'm having the exact same problem you are except with a IIe Platinum.

I definitely will as I have not been able to find any detailed success writeuos outlining everything from cable to config. 

So far the latest I did was try to set it up exactly as described in the gbbs 2.3 manual I purchased. I have been able to get it to answer, albeit 2400 baud, but if you were to drop the connection from the client, gbbs never knows and stays where the client left off, it does not even timeout to inactivity. 

If you log off properly, you will see the init string appear on the client before complete disconnection then the wait screen will hang for about a minute and then will appear to restart recycling and then wait for the next call. Not ideal though. 

I have even done this through the super serial card and the IIgs modem port. I find the iigs modem port more favorable just from a configuration standpoint as I do not have to open up the computer and flip switches. 

Also, I have used tcpser on a raspberry pi because that is how the gbbs manual wants you to set it up. One way it is nice as you can trace a log of all communication but ultimately want to use the wimodem. 

Interesting when at 2400 baud I can get Proterm to work not failing at modem initialization but you have to half duplex to see your typing along with the response. As soon as you go to a higher baud rate, startup fails but if you force online it works and full duplex. Weird. 

I think the same thing was happening with gbbs, go above 2400 and you think it is working but it locks up. Using tcpser, at 9600 you will see the init string, ring, connect 9600 but the bbs never picks up. 

There may be something to do with DCD, CD, etc. not sure yet. I have tried so many combinations. Now I read gbbs around 1.2 or so does not support above 2400 but 2.3 has modem profiles of 9600 and they state can support up to 38400. 

So that is my update for now. More to come. I think I am going to try all this on my iie enhanced but probably the same results but who knows I need to leave no stone unturned  

I am telling you, I am close! ?
Reply
#5
One thing for you guys to keep in mind is that a real modem is typically locked at a fixed speed. So, a 9600 baud modem is 9600 baud. If you are using a 9600 baud setting you need to set the WiModem232 to that baud rate, and store that (AT&W). If you don't the baud rate of the computer will not match the modem. If you were using your SSC with a 2400 baud modem and were using the 300 baud setting it would answer but never respond.

So, if you want to use 9600 baud go to ProTerm and setup the modem to use 9600 baud (switching baud rate to that and storing the change with AT&W). Once you do that then you can run the BBS software for 9600 baud.
Reply




Users browsing this thread: 1 Guest(s)