Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Professional Discussion / window XP crash

Author
Message
basjak
16
Years of Service
User Offline
Joined: 16th Apr 2010
Location: feel like signing up for mars
Posted: 17th Jul 2013 18:00 Edited at: 27th Jul 2013 20:15
Link
Hi:

am experiencing crashes on win XP while things work fine on win vista, win 7 and win 8.

the following plugins are used:


EZrotate
Styx.
matrix1_Util. (data files, directories)

the software is compiled on win XP.
error message: "software name" encountered an error and need to be closed. would you like to tell mirosoft about it. [send] [don't send]

Back to top
Profile PM Email Website
Green Gandalf
VIP Member
21
Years of Service
User Offline
Joined: 3rd Jan 2005
Playing: Malevolence:Sword of Ahkranox, Skyrim, Civ6.
Posted: 22nd Jul 2013 03:11
Link
Only thing I can think of is that some plug-ins might use a later version of DX9 that comes built-in with Vista etc but not with XP. If that's the reason then it might be worth installing a more recent version of DX9 from Microsoft. But then I'd expect a different error message. Might be worth a try though.
Back to top
Profile PM Email
Chris Tate
DBPro Master
17
Years of Service
User Offline
Joined: 29th Aug 2008
Location: London, England
Posted: 22nd Jul 2013 04:36 Edited at: 22nd Jul 2013 04:57
Link
Worth a try.

Where does it crash? Before or after any code execution? Any particular command?

Back to top
Profile PM Email Website
basjak
16
Years of Service
User Offline
Joined: 16th Apr 2010
Location: feel like signing up for mars
Posted: 27th Jul 2013 01:03
Link
the software crashes after it's built. surprisingly the compiled code on XP works on 7/vista but crashes on XP.

I don't know what caused the crash because I have 20000 of coding. so the only way is to re-write the code on XP then I may know the cause of the crash.

Back to top
Profile PM Email Website
Chris Tate
DBPro Master
17
Years of Service
User Offline
Joined: 29th Aug 2008
Location: London, England
Posted: 28th Jul 2013 01:25
Link
Nah, just us a hierarchical search to narrow down the region of concern.

Display a message box to display the progress of your process, at each major stage in your app; usually 10 or so message boxes will indicate what major part of the program is at fault. Hopefully it will be the first part. After you find out the faulty section, run the same procedure on that section, and so on until you detect the cause.

Does your 20,000 liner have a logger? It might be a good idea to have your program tell you what it is doing and what happened in a log file; Ian created a log function library in Matrix1. Implement it and create an option to log the progress of the app so in future if a customer has trouble running your software, this log file will 9 times out of 10 report the issue.

Back to top
Profile PM Email Website
basjak
16
Years of Service
User Offline
Joined: 16th Apr 2010
Location: feel like signing up for mars
Posted: 28th Jul 2013 20:20
Link
luckily, the customer is happy to run the software on win 7 not xp but, something to learn for the future is to build a software step by step on all windows versions.

Back to top
Profile PM Email Website
Back to top

Login to post a reply

Server time is: 2026-07-07 06:23:50
Your offset time is: 2026-07-07 06:23:50