thx, for help but please look at the first lines: before getting the phyton error , the problem is the invocation of moc (meta object compiler). this does not work because moc is executed but the path he need is not correct......
this also causes the phyton error
Yeah, you're right Sorry. I can't tell, I never compiled it myself on Windows. Maybe it depends on where you installed the t developer tools or something?
Sorry to rebump. but the problem for me it's not solved.
I run openmsx via catapult, then launch openmsx debugger.
using file monitor i see it read a file where the socket number to connect to is saved. (when i try to connect)
I've ispected the file, it does contains 6 bytes, 4 bytes are the digit identifying the port number. for me it is 9995.
then i telnet localhost 9995 to see if it does connect.
It does.
but on the window where there are active session listed i do not see anything (empty list).
hint: looking opened sockets to openmsx process i see that someone try to connect to the 9995 port when i click the rescan button on the window.
What data should i read in the window?
can i try to get this data via a telnet session? What command should i send to openmsx on the listening socket to read the data?
AFAIK usually there is only one such file and the debugger connects via that port to openMSX to give it commands and get responses. It does SSPI negotiation on Windows, I forgot what it is (other than that it is for security, so only the user who created the openMSX process can connect with the debugger, if I remember correctly). If connection fails, the socket (file) is cleaned up.
I still think there must be some anti-virus-like software preventing the debugger connect to openMSX...
Sorry. I can't tell, I never compiled it myself on Windows. Maybe it depends on where you installed the t developer tools or something? 