Cloister Maximus III
Guest
|
Post by Cloister Maximus III on Oct 1, 2005 21:59:14 GMT -5
I've figured out the trick to connecting with a real c64 in a modem to modem session. Here are the instructions:
1) Take a normal phone cable and connect one end to your c64 modem and another to the modem on your computer running windows (Some modems don't provide power to the line. If you have problems connecting, either feed 9v to the phone line or try a different modem. If anyone has problems I'll elaborate on this)
2) Set your q-link client software to use the last modem type (Other manual command driven modem). Enter in your +5551212 number as well.
3) Load up qlink on the 64 side. Launch Hyperterm (or another term proggie for windows) on the windows side.
4) Issue the AT command "AT&D1" in Hytperterm (This keeps the modems connection alive even after you close Hyperterm and close the COM port. This is the missing link I've been working on for that last week)
5)Type ATDT1 in qlink in hit return. Type ATA in hyperterm and hit return.
6)Once the two sides have connected (CONNECT 1200), close hyper term.
7)Launch TCPSER on the windows side with the correct switches ("tcpser -d /dev/ttyS0 -s 1200 -i"e0&k0&c0" -n"5551212=server:port -tsS" substitute ttyS0 for the correct COM port your modem is on.. a serial device is one less that what the COM port number is)
8)Type atdt5551212 into qlink and hit return.
9)Once TCPSER reports that a connection to the qlink server has been made, hit F1 on your 64.
10)Profit.
I'll be around q-link if anybody has any questions about this method. I'll also post a more in depth tutorial on how to do this later this week.
Cheers,
-cm3
|
|
|
Post by Jeff Ledger on Oct 1, 2005 23:15:11 GMT -5
Wow! Wonder if theres a way replace the hyperterm step with TCPSER or TCPSERj somehow. (Without Jim writing more code. ) Neat stuff! Would you mind doing a "fat crayon" drawing of the your phone wire/power setup for this thread? Awesome work.. Jeff
|
|
d0c
Junior Member
Posts: 57
|
Post by d0c on Oct 2, 2005 7:55:27 GMT -5
while your at it take some pictures also
|
|
|
Post by snarlytaz on Oct 2, 2005 11:39:02 GMT -5
From MagicCharm!
I was able to connect my 128 this morning following the Modem to Modem method! ;D
Cloister will explain in order to keep Hyperterm alive after modem connections, you first have to issue in Hyperterm a AT&D before doing anything. (This will keep modems alive after closing Hyperterm.)
In MY case however, TCPSER would not work as while it recognized my modem COM port, it would not talk. (My PC modem likes COM5 and doesn't seem to force too well to COM2.)
TCPSER4J "does" work in my case, so if you have trouble with TCPSER - try 4J out. My problem is when I used TCPSER4J with WinVICE 1.15 after a couple logins TCPSER4J would hang at the F1 press waiting for 1st escape character. So lets hope it doesn't cause me problems later when putting my 128 online!
I also believe if I start running into troubles, I have to do a full reboot of WinXP to get things rolling right. (Also, I shut off ALL firewall setting through my 2 routers. Next time I will try them with them back on - I doubt they really caused issues, but I will know soon.)
|
|
|
Post by Golan Klinger on Oct 3, 2005 0:48:08 GMT -5
I think it would be awesome if people could get their 64s online by using a cheap, readily available modem rather than finding an obscure RS-232 adaptor or worse, having to build their own (which most non-technical folks wouldn't attempt) and connecting it to a PC. We'd probably see an increase in the number of telnet accessible bulletin boards too.
|
|
|
Post by Relayer on Oct 3, 2005 12:46:36 GMT -5
This may sound obscure, but it might work. Do modems REALLY need to have a dial tone? Couldn't they just connect to each other via the phone cable and send/receive a signal without the dialtone in place? If so, then maybe you can hook a C= modem to a PC modem via a phone cable. TCPSER would see the serial data from a modem instead of a direct connection. The modems would negotiate between themselves. I though modems can pick up in answer mode for an indefinate period of time. Set the PC modem to sit and wait "off-hook" and manually dial in with the C= modem within the Q-Link interface. Depending on the 'quality' of the modems, a direct connection should work. However, you might need to get a "line simulator" which can be done with a couple Radio Shack parts. This would be much easier than building an IC based RS232 solution if you already have the modems. www.jagshouse.com/modem.html
|
|
|
Post by snarlytaz on Oct 3, 2005 19:13:49 GMT -5
Relayer,
That is basically what we are doing. Directly connecting the two modems with a phone cord line port to line port - not through the home for dial tone. To do this though with nothing in between, the PC modem needs to offer up voltage. If it does not, the modems wont connect. that is why Cloister explains you may need to put a voltage source on the phone cord between the two modems.
In my case, my internal PC modem offers up voltage. I Issue an ATDT command from Qlink client which dials the 1670 modem, and as it goes to dial, I issue ATA on the PC modem to answer the 1670 modem.
Then TCPSER (4J in my case) takes over.
|
|
|
Post by snarlytaz on Oct 8, 2005 11:33:02 GMT -5
I was having trouble and believe I figured out why. Sometimes when I tried to connect after launching TCPSER or TCPSER4J, it would not communicate with my modem (even though modems were connected.)
I tracked it back to when I launched Hyperterm. In my case if I issue AT&D1 - while modems stay alive, TCPSER or TCPSER4J wont talk to my modem.
By typos, I found that if I issued AT&D without the following 1 - the TCPSER and TCPSER4J communicate just fine!
|
|
ghost
New Member
Posts: 3
|
Post by ghost on Oct 13, 2005 23:14:16 GMT -5
**I'll also post a more in depth tutorial on how to do this later this week
Hey Cloister did you ever get a chance to put together amore in depth tutorial yet? I am asking because I keep getting No Dialtone. Also could you or someone explain subject 7. where you say to launch TCPSER with the correct switches?
Thanks and great job getting the C64 modem to connect with a PC.
|
|
|
Post by ghostboa on Oct 15, 2005 18:42:28 GMT -5
Ok nevermind the connecting. I got that. Odd though, with my PC I can only get the C64 to answer an ATD from the PC. But with my Mac, I can set it to ATA and connect by ATD etc from the C64.
Anyway, I get it connected. My trouble now is TCPSER. I cant seem to get any version to work for me. Can anyone please help with this. I am very new to any of this TCPSER so it may be something simple. Thanks guys.
|
|
|
Post by snarlytaz on Oct 15, 2005 22:20:41 GMT -5
Are you issuing the AT&D command in Hyperterm to keep the modems alive after you close hyperterm first? (AT&D before you do the ATD or ATA command.)
Then, in the TCPSER launch settings, make sure the /dev/ttyS0 is correctly set to your PC modem's com port. the number after the S is your com port - 1, so ttyS1 would mean com2.
|
|
ghost
New Member
Posts: 3
|
Post by ghost on Oct 15, 2005 23:26:28 GMT -5
Are you issuing the AT&D command in Hyperterm to keep the modems alive after you close hyperterm first? (AT&D before you do the ATD or ATA command.) Yes, I keep them connected with no problem. Then, in the TCPSER launch settings, make sure the /dev/ttyS0 is correctly set to your PC modem's com port. the number after the S is your com port - 1, so ttyS1 would mean com2. This is where I am having the most trouble. I am a bit confused about the 'launch settings'. Right off, I see that I was trying to set my Comport incorrectly, but am still unsure it I am doing it right. Is the string Max posted what I create a .bat file out of? Just that line? Also, a bit off topic. Has anyone been able to use a Mac to get this to work? Is there any software out there for it? Thanks
|
|
|
Post by snarlytaz on Oct 15, 2005 23:44:29 GMT -5
I will have to look at my TCPSER launch string. I think you can copy the one from the qlink reloaded site though and paste it into notepad to create a .bat file. Just make sure you edit in the server location and ttySn setting. I actually have better luck using TCPSER4J though.
|
|
ghost
New Member
Posts: 3
|
Post by ghost on Oct 16, 2005 0:04:59 GMT -5
Hmm I tried the string from Max and it just opens and shuts back down. Another question though.. it keeps being mentioned to shut down Hyperterm. Is this a must? Reason I ask is because when I enter AT&D1 and hit enter i get OK. Then I send the commands to connect. They connect. I shut down Hyper and it asks me if I am sure I want to disconnect. Well of course when I say yes, it breaks the connection. Another Hyperterm maybe? I am using the one that comes with XP. Thanks alot for your help. btw I have also tried 4j. But if the problem starts with the Hyperterm still running then I have to solve that first and maybe 4j will work for me, who knows
|
|