I noticed that wrapper and it does get past loading it in, but by the time the crash occurs it seems the state seems a bit corrupted so it is *really* hard to follow (especially by the time it starts jumping into inaccessible memory, bit of an indication that something is corrupted by then). So *something* is unique and broken with the most recent version, but what is it? I cannot seem to find the issueĮDIT1: And yes, this was a fresh install from the CD itself (had a fun time hunting that down again).ĮDIT2: And I tried on another freshly made admin user account with no frills or anything, same error. Testing Fleet Ops 3 beta (you know, the 2006 version, wow it has been a long time.) shows it runs perfectly (other than the long path bug that I reported and showed how to fix for you a while back, which from reading around here apparently other people ran into as well). Since this occurs before WinMain, it is not occurring in your code upon further inspection it happens while loading system libraries (although, admittedly I do have a few, though none of the many thousands of other installed applications have any issues whatsoever, leading to the belief that the executable or some library it links to is conflicting).
Running the executable in a debugger reveals that these exceptions are thrown before WinMain is ever reached (well before you ever set your own exception handler, hence why I do not see your special box). Now, if I look at the Armada2 executable I notice that the mapped memory between 0x166B000 to 0x01760000 (which so happens to contain both of the above listed locations) contains unallocated memory (reserved area for loading system libraries, but nothing is loaded in that location). The instruction at "0x016e24e0" referenced memory at "0x016e24e0". This *specific* box pops up a total of 6 times. If I click OK then the box pops up again. If I click Cancel then the application process disappears quite instantly. The instruction at "0x016e24b0" referenced memory at "0x016e24b0". When I launch FleetOps (or if I launch the Armada2 executable directly) I get a bog-standard Windows Application Error dialog box containing: (Don't you hate seeing me around, every time I stop by I have some nasty error for you, oddly this is just about the only program out of the thousands I have that has any issues.). I am not adding this to the Launch Error topic because of a reason I will describe shortly.
0 kommentar(er)
