|
Post by Glenn Holmer on Sept 18, 2005 0:10:42 GMT -5
How to connect with Linux? Looking at the "RS232 Settings" dialog on the web page, VICE 1.16 running under Linux seems to expect a device name where 66.135.38.238:5190 is entered.
|
|
|
Post by pablot on Sept 19, 2005 12:11:38 GMT -5
How to connect with Linux? Looking at the "RS232 Settings" dialog on the web page, VICE 1.16 running under Linux seems to expect a device name where 66.135.38.238:5190 is entered. You must have netcat installed and use Vice 1.15 (1.16 does not work) the do this: RS232 Settings->Userport 1200 baud RS232 emulation RS232 Settings->Userport RS232 device->Exec process RS232 Settings->Program name to exec and type EXACTLY: |nc -p 31337 66.135.38.238 5190 Note the leading pipe (the 31337 does not mean nothing, just type a port number) Enjoy!!!
|
|
|
Post by Glenn Holmer on Sept 19, 2005 19:39:23 GMT -5
I'm using SUSE 9.3, where the binary is named "netcat" (package netcat-1.10-869). The piped command I'm using is "|netcat -p 31337 66.135.38.238 5190". Uninstalled VICE 1.16 and compiled 1.15 instead.
A packet sniffer shows about twenty packets exchanged with 66.135.38.238, but I don't see anything after "Connecting -" (just the single dash).
|
|
|
Post by pablot on Sept 20, 2005 18:53:17 GMT -5
I'm using SUSE 9.3, where the binary is named "netcat" (package netcat-1.10-869). The piped command I'm using is "|netcat -p 31337 66.135.38.238 5190". Uninstalled VICE 1.16 and compiled 1.15 instead. A packet sniffer shows about twenty packets exchanged with 66.135.38.238, but I don't see anything after "Connecting -" (just the single dash). Hmm, works ok for me. Are you sure the packets are really exchanged or just sent in one direction? (perhaps blocked by your firewall) Also, it can be an occasional problem, have you tried more than once at different times? Try putting qlink.quantum-link.org instead of 66.135.38.238, but it's the same.
|
|
|
Post by RickFriedman on Sept 21, 2005 1:07:09 GMT -5
How to connect with Linux? Looking at the "RS232 Settings" dialog on the web page, VICE 1.16 running under Linux seems to expect a device name where 66.135.38.238:5190 is entered. You must have netcat installed and use Vice 1.15 (1.16 does not work) the do this: RS232 Settings->Userport 1200 baud RS232 emulation RS232 Settings->Userport RS232 device->Exec process RS232 Settings->Program name to exec and type EXACTLY: |nc -p 31337 66.135.38.238 5190 I'm running Debian Sid. I had installed the Debian package of vice 1.16, along with downloading the ROMs. I was unable to get Q-Link Reloaded to work. So, I've downloaded the source for vice 1.15. Unfortunately, while building it, I received the following errors: In file included from uimenu.c:44: ../../../../../src/arch/unix/fullscreenarch.h:52: error: array type has incomplete element type ../../../../../src/arch/unix/fullscreenarch.h:53: error: array type has incomplete element type make[7]: *** [uimenu.o] Error 1 make[7]: Leaving directory `/home/rick/downloads/archives/vice-1.15/src/arch/unix/x11/xaw' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/rick/downloads/archives/vice-1.15/src/arch/unix/x11/xaw' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/rick/downloads/archives/vice-1.15/src/arch/unix/x11' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/rick/downloads/archives/vice-1.15/src/arch/unix' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/rick/downloads/archives/vice-1.15/src/arch' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/rick/downloads/archives/vice-1.15/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/rick/downloads/archives/vice-1.15/src' make: *** [all-recursive] Error 1 Any help is appreciated. Or, if anyone knows where I can find a debian binary pkg of vice 1.15, that would do as well. Rick
|
|
path0s
Junior Member
Posts: 52
|
Post by path0s on Sept 22, 2005 0:29:02 GMT -5
I've got Vice 1.15 compiled fine under Mandriva linux, and gnu netcat v0.7.1.. Not that it matters I dont think, but kernel is 2.6.11-6mdk (mandrake)
I can't get it to work right with the above config. If I start x64 from a console window, and try to connect to qlink, I get a bunch of broken pipe errors when it tries to use the rs232..
By itself at the console, netcat does what it should. So it's my guess that there's something not right with the exec process line? I guess I'll fiddle with it..
-P
|
|
path0s
Junior Member
Posts: 52
|
Post by path0s on Sept 22, 2005 0:40:28 GMT -5
Well, if I specify the full path to netcat, it doesn't give me the broken pipe errors, but the x64 console log shows "Frame error!" about 10 secs after trying to initiate a rs232 connection.. Hmm I'm out of ideas..
-P
|
|
|
Post by Niedobry on Sept 23, 2005 12:06:40 GMT -5
Well, if I specify the full path to netcat, it doesn't give me the broken pipe errors, but the x64 console log shows "Frame error!" about 10 secs after trying to initiate a rs232 connection.. Hmm I'm out of ideas.. -P Can you put up a sample of your vicerc file? Just the parts that deal with RsDevice.
|
|
|
Post by Cenbe on Sept 24, 2005 15:36:26 GMT -5
OK, finally got it to work. I posted above as Glenn Holmer, but now I'm a real person, LOL! Under SUSE Linux 9.3 (still using VICE 1.15). the piped command is "|/usr/bin/netcat 66.135.38.238 5190". Of course, the real reason it's working now is that I'm drinking coffee out of my new Q-Link mug, heh.
I just logged in to Q as ShadowM for the first time in 11 years!
The only problem I'm still having is that my original Q-Link function key template doesn't fit on my ThinkPad.
|
|
|
Post by Earendil on Sept 24, 2005 21:26:32 GMT -5
I posted above as RickFriedman. I now have my Qlink name back (Earendil). Anyway, I just wanted to say I've also gotten on using Linux (Debian Sid) and Vice. I had tried Vice 1.16 but, as others have said, it just doesn't seem to work as it should. So, I searched for a binary Debian package for Vice 1.15 but was unable to find one. I decided to download the Vice 1.15 source and build it myself. Upon attempting to compile it, I received many errors which killed the compile. I then thought it might be the compiler I was using. I am currently using gcc 4.0. I decided to retry the build using gcc 3.3. This time the build proceeded without a hitch. I started up the Vice 1.15 binary and made the following changes to the settings: RS232 Settings->Userport 1200 baud RS232 Emulation RS232 Settings->Userport RS232 Device-> Exec Process RS232 Settings->Program name to exec: | nc -p 31001 66.135.38.238 5190 After creating these settings and attaching and running the QuantumLink.d64 image, I was able to logon and enjoy QuantumLink once again. The only thing I have noticed is that, as I type, Vice seems to miss a character every few words. I seem to have corrected that however by going into settings and changing the maximum speed. You might think that increasing the speed would fix it but I found this not to be the case. Instead, SLOWING the speed, seems to have solved the problem. What I did was: Maximum speed->50% After this Quantumlink Reloaded seems to run fine. Ear
|
|
path0s
Junior Member
Posts: 52
|
Post by path0s on Sept 25, 2005 0:04:26 GMT -5
For you guys who have gotten it to work.. What version of netcat are you using? And is it the normal GNU netcat or ??
Do a "netcat -V" (vapital V) for me.. thanks -P
|
|
|
Post by Earendil on Sept 25, 2005 3:26:43 GMT -5
For you guys who have gotten it to work.. What version of netcat are you using? And is it the normal GNU netcat or ?? Do a "netcat -V" (vapital V) for me.. thanks -P As far as I know, I'm using the normal GNU netcat. It comes from a binary Debian package. The version number is 1.10. Hmmm... I just checked the netcat homepage, netcat.sourceforge.net. That says the current version is 0.7.1 and that one of the goals of the project is, "full compatibility with the original nc 1.10 that is widely used...". So, apparently, the version I am using is "the original". I found the following link to source code for version 1.10: www.securityfocus.com/data/tools/nc110.tgz. Ear
|
|
path0s
Junior Member
Posts: 52
|
Post by path0s on Sept 25, 2005 15:31:42 GMT -5
Hmm.. Installed the original 1.10 netcat and it's a no go too. Still the same "Frame Error!" message.
Using it via commandline works without a hitch. Hit enter a couple of times and the familiar TERMINAL= message pops up as it should. I'm baffled at this point. -P
|
|
path0s
Junior Member
Posts: 52
|
Post by path0s on Sept 25, 2005 23:28:46 GMT -5
Well.. Isn't this interesting... I hooked up a null modem cable between my linux box and my PC running BBS server -- wanted to see the diagnostic idiot lights in the program to try and diagnose my problem. I still get the same exact Frame Error! message that I get from using netcat. So it's definitely not netcat's problem. It's gotta be my compile of Vice 1.15 (compiled from scratch on my machine, not from rpm), or some kind of weird change they did in the mandriva/mandrake kernel. BBS server did get the ATDT1 command I sent to it through the QLink connection screen and connected via tcpip to the qlink server, then BBS server sent the "CONNECT" response back which I did see on my Qlink screen.. I pressed F1 then the Frame Error hit. So it can send some kind of transmission through the null cable. Hmm. -P *** EDIT *** Well, after tinkering for a while, I'm convinced the problem lies with VICE.. I'm able to cat a 100k file over ttyS0 at 1200 baud, type back and forth between 2 terms at 1200b, login via mgetty over 1200b, send a file via zmodem over 1200 baud, etc etc all with no errors. So next question, why the heck is my VICE compile different than others? It's 1.15 directly from viceteam.org using pretty standard compile options from the INSTALL file (-O5 -funroll_loops etc).. I've tried running VICE in warp mode, 100%, 200%, 50% when connecting.. All the same "Frame Error"
|
|
|
Post by Earendil on Sept 26, 2005 17:46:38 GMT -5
So next question, why the heck is my VICE compile different than others? It's 1.15 directly from viceteam.org using pretty standard compile options from the INSTALL file (-O5 -funroll_loops etc).. I've tried running VICE in warp mode, 100%, 200%, 50% when connecting.. All the same "Frame Error" Hmmm... what version of gcc are you using? I found I had problems trying to build Vice with gcc 4.0. When I substituted gcc 3.3, the build gave me no further problems. Ear
|
|