LiveCode Forums.

Howdy,

I use sockets to transfer data from one program to another. This works great on Windows 7, but I have been unable to get the programs to work with XP. I run XP as the administrator; in the IDE, it seems the proper sockets are open; I've disabled the firewall and the anti-virus. What am I missing for socket application in Windows XP? Is it possible for the IDE to show the openSockets, but for XP to actually be blocking them? If it is XP blocking, how do I stop the blocking?

I'm using LiveCode 4.5.3; Windows 7 with VMware and Windows XP with VMware.

Thanks,
E

Well, sockets *do* work on xp <g>. Do you have network connections working otherwise in your VM (can you ping other machines, etc.)? Are you running anything else in the xp vm that might also be using the same ports (server software)? What errors are you getting? What ports are you trying to use?

Thanks for the reply.

I do not seem to be able to ping other systems. The ports are way up on the list to avoid conflicts: 6060 and above. I do not get any errors, but what works for Windows 7 doesn't in XP. I still have some testing to look at, but any other advice would be great. Keep in mind that although my development is with VMware, I have had the same issues in the past using XP natively.

Eric

Hmmm. Don't know about the native xp problems, sockets have always worked for me there. But I've found that VMWare is touchy about network settings. If bridged mode isn't working, try NAT mode, and vice versa. I dropped VMWare for VirtualBox a while back for just these kinds of reasons. If simple tcp actions like ping or telnet aren't working in the vm then sockets won't be working there for you. Launch a command prompt box and see what ipconfig returns. Once you've gotten basic networking going in the vm, try the sockets app again. High-number ports should be fine, and as you said, out of conflict areas.

Thanks mwieder,

I'm going to test using my XP on bootcamp and I think the office has an old, dusty pc in storage that should be an XP machine. The ping testing said a lot and helps to narrow down the problem being sockets and not the code, hopefully.

E

Cool. Post the results back here - we should have you running in no time.