Hi, all having trouble with openmsx debugger
i start openmsx and i see the socket.pid file on C:\Users\\AppData\Local\Temp\openmsx-
when i run the openmsx debugger i cannot connect because the debugger do not see any session.
working on windows 7
any idea?
Для того, чтобы оставить комментарий, необходимо регистрация или !login
Hi, you check for any zombie openmsx process or orphaned socket file?
Can you communicate with openmsx through socket.pid (via SOCAT and NETCAT Windows versions)?
Try to clear any file in %USER%/AppData/Local/Temp/openmsx-default and %USER%/AppData/Local/Temp/openmsx before start the openmsx and debugger.
Hi, you check for any zombie openmsx process or orphaned socket file?
Can you communicate with openmsx through socket.pid (via SOCAT and NETCAT Windows versions)?
Try to clear any file in %USER%/AppData/Local/Temp/openmsx-default and %USER%/AppData/Local/Temp/openmsx before start the openmsx and debugger.
cheers!
i think this is not the problem. on the active sessions i cannot get any entry listed.
no zombie files on folder.
i can successfully telnet to the port openmsx has stored in the socket.pid file.
openmsx version 0.14.187-<> release
debugger version ---------------------------
openMSX Debugger 0.10.0-258-g85db7c3
"windows defender smartscreen" says that the debugger is evil.
I had the same problem a year ago and then did nothing.
does anyone know whether maybe smartscreen is a joke?
the german text says
"the start of an unknown app was hindered"
"under circumstances a risc"
both is a joke
still I dont dare to click
Can you be more specific? Do you mean it behaves the same as described in your first post?
I don't know what it is though, I didn't hear complaints from other people, so there must be something local on your PC that influences this. Firewall software perhaps?
