I have a simple command line utility that I wrote for linux. I ported it to Win2000 which was really only a matter of getting it to work with the windows "cmd" command line. It also runs on Mac OS X. Its all great. Unfortunately, some friends of mine who need to run this program have WinXP and it mysteriously doesn't work on windows XP. It doesn't crash, it doesn't quit, it just doesn't do what its supposed to. Its a network utility and it seems like its not receiving particular packets off the network.

To make matters much much worse, while I do have a spare computer lying around, everytime I try to install Windows XP on it, it blue screens half way through, so I have no way of testing it on an XP system.

This is straight C with network code send, recv, printf, really standard stuff. It does use the OpenSSL libraries but only sparingly and that part works fine.

My question: what in gods name would cause a program compiled for windows2000 that worked perfectly to just sort of quietly not do what it was supposed to in windowsXP? Could this be some buffer overrun protection in XP that doesn't like my code? Again, it doesn't quit or crash, it just doesn't function quite right. I know this isn't strictly a linux question, but it was originally linux code and maybe someone here knows.

What compiler did you use to compile it for Win2000?

Codewarrior, one of the later versions if not the latest, fully updated.

I actually do support for MS for windows xp and windows 2000

As far as i know the networking part of windows 2000 wasent changed when moving to windows xp this is the offical response.


Now my own opionin bull crap. They changed it somehow and remeber seeing something about having access to low level tcp/ip ports so you can create invalid ip adresses or something but I doubt this is the issue.


The main thing that I can think of is that windows xp has ipv 6 cabablities and 2k doesent.

Maybe its the MS firewall on there computers that was defently not something that was on 2k

A lot of it works, its just one particular tcip/ip message that its not getting. So I was thinking maybe its some WindowsXP service pack 2 buffer overflow thing that doesn't like my code. But I would think it would just quit in that case.