Page 1 of 1

Sockets on Windows (runrev 4)

Posted: Tue Dec 22, 2009 4:16 pm
by dzervas
Hello,

I am using Runrev 4.0 on Mac.

I have made an application which uses Sockets to control a hardware system via a network connection.
This system has an API which I call using socket commands, I open a socket, send some text command and close it.

It works very well, both through the IDE but also as a standalone application from the MAC.

If I switch to windows and use the Windows .exe generated by Runrev 4.0 ... it just does not work...
I am wondering if this is a limitation for sockets functionality when in Windows.
(Tried with Windows Vista but also XP).

Thanks for your time.

Regards

Re: Sockets on Windows (runrev 4)

Posted: Mon Jan 04, 2010 6:02 pm
by SparkOut
Not tried anything like that to test your situation here, but I wonder if it would be the native windows firewall blocking the traffic?

Re: Sockets on Windows (runrev 4)

Posted: Sat May 22, 2010 2:28 pm
by SirWobbyTheFirst
Hi dzervas, what firewall are you running for Windows, because I have had a few cases where Windows Firewall has kept quiet about a socket being opened in a rev application.

Additionally if you use Windows Firewall, what configuration do you have it set too?

Re: Sockets on Windows (runrev 4)

Posted: Tue May 25, 2010 3:02 pm
by dzervas
Hello and thanks for your interest and your replies.
Actually, I have disabled Windows firewall and also the Norton Symantec Antivirus that I' m using at work.
That's why I thought that it must be a limitation of the Windows version of Runrev.

I just installed a Windows 7 laptop, so I could also try that to see what happens.

Thanks again, any ideas welcome.

Dennis

Re: Sockets on Windows (runrev 4)

Posted: Tue May 25, 2010 6:16 pm
by SirWobbyTheFirst
Hmm, dzervas I did read a message once on these forums about someone who developed an application for Mac but the same source code would not work on Windows or Linux.

As a suggestion, have you tried creating a new stack under Windows and re-doing it to match the Mac version. If it works, then I would suggest their must be a bug when compiling a Mac written stack for Windows. Additionally once the Windows version is complete, if you can get your hands on a Linux distro, you could try both versions.

Once done report the results back here. With regards Michael.