|
Post by LordNikon64 on Oct 19, 2005 9:26:21 GMT -5
|
|
|
Post by Jeff Ledger on Oct 19, 2005 11:29:05 GMT -5
My guess is that your problem is with TCPSER4J. The boot screen you have doesn't appear to be completely started. Is there a chance that something else is also holding the COM port open? Post your TCPSER4J setup, and OS. Here's what mine looks like. Jeff
|
|
|
Post by lordnikon on Oct 19, 2005 12:26:59 GMT -5
no ... the com port is free... i found out that the config.xml seems to be wrong ... but i dont get the same message like your ... it stops at parsing at command
|
|
|
Post by lordnikon on Oct 19, 2005 13:56:52 GMT -5
... hmm i changed the config to get nearly the same output as you.. if i start the tcpser4j the screen flashes shortly on the c64. What do i have to do at the connection screen?
I tried ATDT5551212 but then screen flashes but tcpserv4j puts nothing out.
well... maybe the attached config.xml could help.
<Settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="TCPSerial.xsd"> <PhoneBook> <Entry number="5551212" value="66.135.38.238:5190"/> </PhoneBook> <ModemPool> <Line port="6400"/> <TemplateModem> </TemplateModem> <Modem type="rs232" device="COM1" speed="2400"> <!-- Per modem init string. If DefaultInit is also specified, per-modem init is added to end of default --> <Initialization>&c0e0</Initialization> <Initialization>&k0</Initialization> </Modem> </ModemPool> </Settings>
|
|
|
Post by RaymondDay on Oct 19, 2005 14:44:23 GMT -5
I wanted to post back here how to do it. So I run it on my Windows. But it's just takes a lot of time to get it to work and I never did. There must be some easyer way. I guess this is why a lot are not getting on with real commodore 64's. Here is a photo of what I did. Sort of like what you put up. My comcast is running out of space 25MB. It's just filling up now. So this last one don't look to good. But I guess you can make it out.
|
|
|
Post by Jim Brain on Oct 19, 2005 19:12:41 GMT -5
Do you use the recommended cable pinout noted on the main qlink web page?
Jim
|
|
|
Post by Jim Brain on Oct 19, 2005 19:27:29 GMT -5
As well, if you are using a real 64/128, set the modem type to Hayes, as a real 64 can autodial the number.
When you do this, you shoudl get more debugging information from tcpser4j. You should see it do +++ and then atdt5551212. If you do not, then I suspect a cable issue.
Jim
|
|
|
Post by RaymondDay on Oct 19, 2005 19:37:19 GMT -5
Some one should just do a text file that tells step-by-step how to set this up.
I wanted to do that but I could not find out how may self. I did get it to do a lot of lines going like send and receve but it never got on. Q-Link never went past on - when it shows it's connecting.
I ran the auto bat file to do that one.
|
|
|
Post by lordnikon on Oct 19, 2005 22:13:02 GMT -5
Big THANX to ALL! ... got it to work.. see you on Qlink
|
|