It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I recently bought JA2:UB. I've found that no matter what I do the game crashes before it loads. I double click the icon, my screen goes black as if it's loading, then just goes back to desktop.
I've tried running the game in win98, winxp compatibility mode. I've turned on "run as administrator", but don't know what else to do.
I've also tried running the game with a different exe (the one from the 800x600 mod someone posted), but no luck.
Any ideas?
Perhaps try add .exe of game to exceptions in video & audio codecs, especially from codec pacs, If you have any. FFdshow make most problems because sometimes it's overtake any video sequnces from game to run through it. If you have ffdshow this option is in vide & audio codec configuration, second bookmark -> 'Don't use ffd show in':
I have the same problem on my computer with vanilla Jagged Alliance 2: game crashes on start after blacking the screen, without any error message.
I tried various compatibility settings configurations (Run as admin or not, Windows Themes or not, XP compatibility, Win 98 compatibility...) without any improvement.
Running Windows 7 x64 with up to date graphic drivers...
I got this too. It will only let me load saves on my vista x64 if I run as administrator
I've recently upgraded to Windows 7 and still get this problem...
Post edited December 17, 2009 by kashwashwa
avatar
wpegg: I got this too. It will only let me load saves on my vista x64 if I run as administrator

Does not work with windows 7...
The game does not work either with seven pro's windows XP mode (the one with virtual PC, not the compatibility setting)
Also having this issue. Not sure of the cause, running Visa64.
Made sure I have "run as admin" ticked, and have tried other options to no avail.
Strangely, the crash logs (found in the data folder in the JA2 install directory), state the following:
Exact Error Message
"The thread tried to read from or write to a virtual address for which it does not have the appropriate access."
No idea what that means, especially since it should have access...
I have Win7Pro 64-bit and it works fine with and without 1.13 patch/mod for me. I just installed it and it ran, so I don't know....
My rig:
AMD PhenomII X4 620 - 2.6Ghz quadcore CPU
Nvidia 9500GT Video Card
3GB PC5700 RAM
Asus Mobo and built-in soundcard, works better than a $20 sound blaster oddly
Windows 7 Professional 64-bit with latest updates
avatar
Andy_Panthro: "The thread tried to read from or write to a virtual address for which it does not have the appropriate access."
No idea what that means, especially since it should have access...

Access... Is it, by any chance, installed under Program Files ? That's a folder you should avoid in Vista at all costs.
avatar
Andy_Panthro: "The thread tried to read from or write to a virtual address for which it does not have the appropriate access."
No idea what that means, especially since it should have access...
avatar
Vestin: Access... Is it, by any chance, installed under Program Files ? That's a folder you should avoid in Vista at all costs.

How does that make a difference? I've installed plenty of games there, with no problems (including several GOG games).
I'll try installing to a different directory, and report back with the results.
[edit] results are in... no go.
Exactly the same problem, but have it installed in D:\Games...
Post edited February 06, 2010 by Andy_Panthro
avatar
Vestin: How does that make a difference? I've installed plenty of games there, with no problems (including several GOG games).
I'll try installing to a different directory, and report back with the results.
[edit] results are in... no go.
Exactly the same problem, but have it installed in D:\Games...
avatar
Andy_Panthro:

The reason Vestin was referring to Program Files folder is because in Vista (and I assume win 7) this folder can only be written to by processes that have admin privileges. This is why you've had to tick the run as admin box on the shortcut, otherwise it can't write its savegames and temp files to this location.
In your case because you've checked the run as admin, you've covered this one.
I'm running the game on Vista 64, so it's definitely compatible. The error from the crash log that you've posted sounds like a programming bug though, have you installed any mods, or are you running the game in its GOG vanilla flavour?
Post edited February 06, 2010 by wpegg
avatar
Andy_Panthro: The reason Vestin was referring to Program Files folder is because in Vista (and I assume win 7) this folder can only be written to by processes that have admin privileges. This is why you've had to tick the run as admin box on the shortcut, otherwise it can't write its savegames and temp files to this location.
In your case because you've checked the run as admin, you've covered this one.
I'm running the game on Vista 64, so it's definitely compatible. The error from the crash log that you've posted sounds like a programming bug though, have you installed any mods, or are you running the game in its GOG vanilla flavour?
avatar
wpegg: Completely vanilla GOG JA2. It's rather frustrating, as you can imagine. Thankfully I have other games to play while I wait on GOG support.

[edit]
Well, I decided to search for newer drivers (just in case) today, and found some for my sound card and video card (2010 drivers, so very new). That seems to have sorted it!
No idea what the problem was with the previous drivers, I would never have believed that a different driver release would affect an older game.
Now playing with the latest 1.13 patch, and having plenty of fun...
Post edited February 08, 2010 by Andy_Panthro
Just to recap, turns out it wasn't the new drivers after all.
The difference was turning off the nvidia 3D vision software.
No idea why that makes a difference, but it only works with 3D vision off.
I'm in the process of discovering how it affects other games.
I've been debugging this same issue for several hours today and I think I tracked down the actual issue for JA2. It's not necessarily 3D Vision but the 120hz refresh rate that causes the crash. I had this error over and over today until I used my Nvidia control panel to override my system default refresh rate (120hz) to use the Application-Controlled setting for JA2.

Hope that helps anyone else getting this error :)
Switching from dedicated to integrated graphics on my sandy bridge i7 solved the issue.