Perhaps I do not know the expected behavior... I specify --com1=SOCKET:127.0.0.1:18080 on command line or INI file. I then wrote a quick "server" app that would watch for incoming connections on port 18080. I expected that either a) the port would be opened/closed when pc-basic starts/stops, or b) the port would be opened when I tried
open "o", #1, "com1:"
...and close on the "close #1" statement. When I tried this however I did not detect any tcp connections, using pc-basic 15.08.11. I did get "device unavailable" error on "open" statement.
Any advice on what I'm doing wrong? BTW, thank you for pc-basic, takes me back to the good ol' days.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Perhaps I do not know the expected behavior... I specify --com1=SOCKET:127.0.0.1:18080 on command line or INI file. I then wrote a quick "server" app that would watch for incoming connections on port 18080. I expected that either a) the port would be opened/closed when pc-basic starts/stops, or b) the port would be opened when I tried
open "o", #1, "com1:"
...and close on the "close #1" statement. When I tried this however I did not detect any tcp connections, using pc-basic 15.08.11. I did get "device unavailable" error on "open" statement.
Any advice on what I'm doing wrong? BTW, thank you for pc-basic, takes me back to the good ol' days.
SOCKETonly takes a local TCP/IP port number as a parameter, not an IP address - what happens if you use--com1=SOCKET:18080?Hope this helps
Rob