Hi all,
Anyone know if Purebasic-generated executables (.exe files) can execute on a windows 2008 server environment? We had a PB-made program running on a win 2003 server and it worked just fine (this program only uses GUI and Network routines). After we upgraded to Windows Server 2008, running the program causes it to crash, and a "Program has stopped working" message to be displayed. We tried re-compiling with PB 5.00 (it was originally made in 4.41), both 32- and 64-bit versions, to no avail.
Any info you can provide will be greatly appreciated.
Windows 2008 compatibility
Re: Windows 2008 compatibility
I don't see why not since it's based on Vista (right?).
For the program, doesn't crash running inside the PB-IDE with the debugger ?
Try enabling the purifier too.
There is not much to say, you have at least to find where it crashes, then if you have a problem in understanding why you can always come back to the forum an try to ask here!
For the program, doesn't crash running inside the PB-IDE with the debugger ?
Try enabling the purifier too.
There is not much to say, you have at least to find where it crashes, then if you have a problem in understanding why you can always come back to the forum an try to ask here!
"Have you tried turning it off and on again ?"
Re: Windows 2008 compatibility
You might compile it with on-error lines support and see if that will narrow it down.
-
sec
- Enthusiast

- Posts: 792
- Joined: Sat Aug 09, 2003 3:13 am
- Location: 90-61-92 // EU or ASIA
- Contact:
Re: Windows 2008 compatibility
My .exe runs in 32bit mode on win 2008 datacenter 64bit w/o problem. .exe does server stuff, registry, file...
You can to add some breakpoint in your code to seew which part not working. I had make brwakpoint by messageresquester().
You can to add some breakpoint in your code to seew which part not working. I had make brwakpoint by messageresquester().
-
BorisTheOld
- Enthusiast

- Posts: 542
- Joined: Tue Apr 24, 2012 5:08 pm
- Location: Ontario, Canada
Re: Windows 2008 compatibility
In situations like this it's my experience that the problem lies in user code and that the bug has always been there - it just didn't show up in other versions of Windows.tutiplain wrote:We tried re-compiling with PB 5.00 (it was originally made in 4.41), both 32- and 64-bit versions, to no avail.
It's highly unlikely that exe files suddenly stopped working just for you. So you have to ask yourself why it is that this program fails while your other programs work fine (I assume).
These sort of bugs cause a lot of grief and are not easy to find. Doing it right the first time is a much better approach to program design.
For ten years Caesar ruled with an iron hand, then with a wooden foot, and finally with a piece of string.
~ Spike Milligan
~ Spike Milligan
Re: Windows 2008 compatibility
Thanks for your replies. Using MessageRequester for breakpoints seems like a good strategy to narrow down the problem. I'll see what I can dig up.
Re: Windows 2008 compatibility
You could also use an ASSERT macro (even if it is better suited for the development process).tutiplain wrote:Using MessageRequester ...
"Have you tried turning it off and on again ?"

