I installed the hotfix and I updated Java, but each time I try to run the program it gives me the following message in a dos prompt:
C:\Matrix Games\War in the Pacific Admiral's Edition\tools\witpstaff>echo off WitpStaff AE V0.7 (C) 2006-9 by M.Baumeister. Please wait! Press any key to continue . . .
Pressing enter just closes the window. I'm running Vista x64.
I installed the hotfix and I updated Java, but each time I try to run the program it gives me the following message in a dos prompt:
C:\Matrix Games\War in the Pacific Admiral's Edition\tools\witpstaff>echo off WitpStaff AE V0.7 (C) 2006-9 by M.Baumeister. Please wait! Press any key to continue . . .
Pressing enter just closes the window. I'm running Vista x64.
Thanks for your help.
Is your PC running Vista? Vitas "dos" isn't Dos and it cant run certain things that are DOS..mine refuses run 16 bit Dos
You might tinker with Compat mode if using vista, I havent yet installed AE on my vista so cant test if works on mine (the tool)
_____________________________
Noise? What Noise? It's sooooo quiet and Peaceful! Battlestar Pegasus
I installed the hotfix and I updated Java, but each time I try to run the program it gives me the following message in a dos prompt:
C:\Matrix Games\War in the Pacific Admiral's Edition\tools\witpstaff>echo off WitpStaff AE V0.7 (C) 2006-9 by M.Baumeister. Please wait! Press any key to continue . . .
Pressing enter just closes the window. I'm running Vista x64.
Thanks for your help.
Enter the tools folder, then the witpStaff folder and click on the witpdecoder2.jar file....
...this is a known issue for those of us with x64 Vista....the .bat file doesn't work with x64 Vista.
Tried running it, it initilizes a DB, I had an first error of "TF90 lead by No or a Foreign Officer" error, after going on past that comes up the above error.
This is Vista Home and tried Vista mode, XP mode, 98/Me mode no go on all.
I note too the hot fix DLL is SMALLER then the one author provides
_____________________________
Noise? What Noise? It's sooooo quiet and Peaceful! Battlestar Pegasus
Well the coral Sea scenario has production off and I've just checked it and get the same error message. Without knowing Woo's code, I've looked at the error log
quote:
There is a problem with LCU 3825 (20th) as follows: Couldn't write things to the DB due to java.sql.SQLException: Integrity constraint violation - no parent PreparationOnlyForExistingTargets table: BaseStatus
I'm guess that this is something to do with the LCU not having a particular field correctly assigned - which is required, so the DB is chucking it out ... This looks to be preparation for a base, which is not in the scenario but I looked in the scenario DB, and couldn't see what was missing, so I'm
--Damian--
[edit]Witstaff, is really tailored to the full campaign, not small scenarios ...
< Message edited by n01487477 -- 7/28/2009 5:19:54 AM >
Well, just to repeat myself, there is very little, to no need to use witpstaff for the smaller scenario's anyway, especially as they all have production off iirc ... but this problem does not seem to be about production rather a LCU/Base problem (I stated 2 posts earlier)
No worries then if it's not designed/needed for scenarios. Was just wanting to play around with it. I will give it a try with the GC someday when I get to playing it.
Tried running the witpdecoder2.jar file ... and then to load the save file
Keep getting the same load errors as before.
Is there a next step or should I just stop using the file on my Vista PC...or can I load and run the witpstaff tool on another pc and transfer the save file.
It looks and sounds very useful.
I spent over six hours last night working on my first turn in the campaign 2 scenario before hitting execute to confirm it was working. The game is working well, just very intimidating several times as I seemed to be checking every single base, and task force.
I'm another person having problems getting this program to run. And yes, I have installed the hot fix. When I attempt to "Load Savefile" the program just closes after I click on my game file (saved in slot 9). Why and how do I fix this??
I'm another person having problems getting this program to run. And yes, I have installed the hot fix. When I attempt to "Load Savefile" the program just closes after I click on my game file (saved in slot 9). Why and how do I fix this??
No messages Michael, just CTD ? In the staff folder, can you see a witpdecoder.txt file, it lists some of the DB functions ?
< Message edited by n01487477 -- 7/28/2009 3:00:50 PM >
config.directory is db You didn't correctly closed the DB last time. LeaderPrefs exists. You didn't correctly closed the DB last time. ACFactors exists. Now trying plugin UPGTestPlugin
I have the hotfix installed. The tool starts well, I can load the database, log out and log back in, my error occurs when trying to then load the save file.
Tried running on older laptop running XP, basically getting the same error on both machines.
I am trying to attach the error note.
I can send the error file if it will help.
Sorry I didn't provide details before appreciate your assistance.
The problems show that WitpStaff internally uses a different database format than WitpAE does (in my opinion of course a better one ;-). But the WitpAE format allows scenario designers all kind of strange things, like having a base being an HQ of a unit, units preparing for bases which are excluded from the scenario, ..... and WitpAE works happily ever after. Well, WitpStaff does not. It uses a somewhat more OO approach and a base can not be a HQ and dangling pointers are not allowed.
The same problem BTW existed with WitP_Original where several scenarios would not load into witpDecoder. Complain to the scenario authors. Or better don't, they had enough things to do without caring to make a scenario compatible with a tool which is actually only needed for handling the complexity if the main campaign.
Posts: 4378
Joined: 4/8/2003 From: USA Status: offline
quote:
ORIGINAL: Woos
Concerning the problems with scenarios.
The problems show that WitpStaff internally uses a different database format than WitpAE does (in my opinion of course a better one ;-). But the WitpAE format allows scenario designers all kind of strange things, like having a base being an HQ of a unit, units preparing for bases which are excluded from the scenario, ..... and WitpAE works happily ever after. Well, WitpStaff does not. It uses a somewhat more OO approach and a base can not be a HQ and dangling pointers are not allowed.
The same problem BTW existed with WitP_Original where several scenarios would not load into witpDecoder. Complain to the scenario authors. Or better don't, they had enough things to do without caring to make a scenario compatible with a tool which is actually only needed for handling the complexity if the main campaign.
Ah thanks that explains it! I will try with the big campaign!
Well I run win vista 64 bit and wirpstaff doesnt start either:
config.directory is . Exception in thread "main" java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.C.<clinit>(Unknown Source) at org.eclipse.swt.widgets.Widget.<clinit>(Unknown Source) at de.retsiemuab.witpDecoder.gui.aQ.d(Unknown Source) at de.retsiemuab.witpDecoder.gui.aQ.a(Unknown Source) at de.retsiemuab.witpDecoder.Main.a(Unknown Source) at de.retsiemuab.witpDecoder.Main.main(Unknown Source)
The problems show that WitpStaff internally uses a different database format than WitpAE does (in my opinion of course a better one ;-). But the WitpAE format allows scenario designers all kind of strange things, like having a base being an HQ of a unit, units preparing for bases which are excluded from the scenario, ..... and WitpAE works happily ever after. Well, WitpStaff does not. It uses a somewhat more OO approach and a base can not be a HQ and dangling pointers are not allowed.
The same problem BTW existed with WitP_Original where several scenarios would not load into witpDecoder. Complain to the scenario authors. Or better don't, they had enough things to do without caring to make a scenario compatible with a tool which is actually only needed for handling the complexity if the main campaign.
Well I run win vista 64 bit and wirpstaff doesnt start either:
config.directory is . Exception in thread "main" java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.C.<clinit>(Unknown Source) at org.eclipse.swt.widgets.Widget.<clinit>(Unknown Source) at de.retsiemuab.witpDecoder.gui.aQ.d(Unknown Source) at de.retsiemuab.witpDecoder.gui.aQ.a(Unknown Source) at de.retsiemuab.witpDecoder.Main.a(Unknown Source) at de.retsiemuab.witpDecoder.Main.main(Unknown Source)
You need to look at your configuration that you have both 32 and 64 bit JVM, I don't have Vista 64, but have a look here, or do a search on Cannot load 32-bit SWT libraries on 64-bit JVM
--Damian--
< Message edited by n01487477 -- 7/29/2009 8:09:21 AM >
Printable Version
All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Tech Support >> WITP Staff Fails to Run 
WITP Staff Fails to Run - 
RE: WITP Staff Fails to Run - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread