RE: WitPTracker AE Release 1.2 Available (Full Version)

All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition



Message

KenchiSulla -> RE: WitPTracker AE Release 1.2 Available (12/21/2009 5:16:33 PM)

Is it possible to add information regarding resources to base hexes? Especially changes relative to previous turn are interesting.



floydg -> RE: WitPTracker AE Release 1.2 Available (12/21/2009 8:34:13 PM)


quote:

ORIGINAL: Cannonfodder

Is it possible to add information regarding resources to base hexes? Especially changes relative to previous turn are interesting.


Already supported. From the Bases panel, select a base you own and the current resource level is shown in the bottom part. Select the "Resource History..." button for turn-by-turn history.

Floyd



jb123 -> RE: WitPTracker AE Release 1.2 Available (12/22/2009 3:00:15 PM)

I keep getting this error trying to load new turns.


# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d901afd, pid=2596, tid=2340
#
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# V  [jvm.dll+0x101afd]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#



floydg -> RE: WitPTracker AE Release 1.2 Available (12/22/2009 3:04:26 PM)


quote:

ORIGINAL: jb123

I keep getting this error trying to load new turns.


# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d901afd, pid=2596, tid=2340
#
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# V  [jvm.dll+0x101afd]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#


I think that it ran out of memory.

Are you running WitPTracker from the .bat file or the .jar file?



Smeulders -> RE: WitPTracker AE Release 1.2 Available (12/22/2009 4:01:39 PM)

Hey guys, I was wondering if you could change something in the devices tab to make it easier to follow up upgraded devices. Bit hard to explain, so an example, a unit has device A in it's TOE, but has upgraded this to device B. Right now we have the following.
Unit shows up in the list for device A, with the TOE amount and 0 for current
Unit shows up in the list for device B, with the TOE amount = 0 and the number of current devices.

Is it possible to change this to get this unit out of the list for device A and get the TOE for device A to show up for device B ?

Guessing this could be a bit tricky, but it would make tracking device usage and needs a good deal easier.

Thanks for adding the pools to the LCU device screens, it's a very nice addition.



floydg -> RE: WitPTracker AE Release 1.2 Available (12/22/2009 4:06:56 PM)


quote:

ORIGINAL: Smeulders

Hey guys, I was wondering if you could change something in the devices tab to make it easier to follow up upgraded devices. Bit hard to explain, so an example, a unit has device A in it's TOE, but has upgraded this to device B. Right now we have the following.
Unit shows up in the list for device A, with the TOE amount and 0 for current
Unit shows up in the list for device B, with the TOE amount = 0 and the number of current devices.

Is it possible to change this to get this unit out of the list for device A and get the TOE for device A to show up for device B ?

Guessing this could be a bit tricky, but it would make tracking device usage and needs a good deal easier.

Thanks for adding the pools to the LCU device screens, it's a very nice addition.


Yeah, that could be tricky, since I'd need to check for device upgrades. I believe that eventually the TOE will upgrade and then the unit will no longer show the "old" TOE counts.

Let me see what I can do... (I love challenges)

Floyd



floydg -> Intel Reports (12/23/2009 3:27:10 PM)

I must have a lot of stored-up energy for the winter, since I started working on an intel panel. I think the first release will be about this level:
  • Reads in the sigint text files
  • Displays in a table that you can sort and filter

    Eventually, I'll add this to the map and expand to include the operations report and Combat Events files. Not so sure about the combatreport...

    Any comments or suggestions?

    Floyd

    [image]local://upfiles/12459/80C666EA891B43869D9B578C94E13E9A.jpg[/image]



    • Nomad -> RE: Intel Reports (12/23/2009 3:55:42 PM)

    That looks really useful.



    Roger Neilson II -> RE: Intel Reports (12/23/2009 4:02:31 PM)

    My poor brain gave up trying to find a way to do this. This look great Floyd.


    ETA?

    Roger



    1EyedJacks -> RE: Intel Reports (12/23/2009 4:04:33 PM)


    quote:

    ORIGINAL: floydg

    I must have a lot of stored-up energy for the winter, since I started working on an intel panel. I think the first release will be about this level:
  • Reads in the sigint text files
  • Displays in a table that you can sort and filter

    Eventually, I'll add this to the map and expand to include the operations report and Combat Events files. Not so sure about the combatreport...

    Any comments or suggestions?

    Floyd



    • Would there be any way to post several days of intel on the map at the same time? If I can examin a week's worth of reports on a single map I could try to plot my TFs away from suspected coastal watchers? Or are coastal watchers kind of a random die thing?

    Also, I might get some idea of troop movements if I can add display only details of the 88th JAAF AF Coy on a map over a week or two of intel reports.



    Nomad -> RE: Intel Reports (12/23/2009 4:37:56 PM)

    quote:

    ORIGINAL: 1EyedJacks


    quote:

    ORIGINAL: floydg

    I must have a lot of stored-up energy for the winter, since I started working on an intel panel. I think the first release will be about this level:
  • Reads in the sigint text files
  • Displays in a table that you can sort and filter

    Eventually, I'll add this to the map and expand to include the operations report and Combat Events files. Not so sure about the combatreport...

    Any comments or suggestions?

    Floyd



    • Would there be any way to post several days of intel on the map at the same time? If I can examin a week's worth of reports on a single map I could try to plot my TFs away from suspected coastal watchers? Or are coastal watchers kind of a random die thing?

    Also, I might get some idea of troop movements if I can add display only details of the 88th JAAF AF Coy on a map over a week or two of intel reports.


    Floyd has 3 days showing now. The turn filter will have some options, probably current turn, 5 or 7 days, and all.



    floydg -> RE: Intel Reports (12/23/2009 5:38:05 PM)


    quote:

    ORIGINAL: Roger Neilson II

    My poor brain gave up trying to find a way to do this. This look great Floyd.


    ETA?

    Roger


    ETA: target is around New Year's, give or take a few days.



    floydg -> RE: Intel Reports (12/23/2009 5:41:14 PM)


    quote:

    ORIGINAL: Nomad

    quote:

    ORIGINAL: 1EyedJacks


    quote:

    ORIGINAL: floydg

    I must have a lot of stored-up energy for the winter, since I started working on an intel panel. I think the first release will be about this level:
  • Reads in the sigint text files
  • Displays in a table that you can sort and filter

    Eventually, I'll add this to the map and expand to include the operations report and Combat Events files. Not so sure about the combatreport...

    Any comments or suggestions?

    Floyd



    • Would there be any way to post several days of intel on the map at the same time? If I can examin a week's worth of reports on a single map I could try to plot my TFs away from suspected coastal watchers? Or are coastal watchers kind of a random die thing?

    Also, I might get some idea of troop movements if I can add display only details of the 88th JAAF AF Coy on a map over a week or two of intel reports.


    Floyd has 3 days showing now. The turn filter will have some options, probably current turn, 5 or 7 days, and all.


    Right now the turn filter is "All" and "Current turn". I could add more, not sure what's the most useful.

    I'll eventually plot these on the map, but not for this coming release. I thought coastwatchers were fixed things - some bases always have 'em and some don't.

    But that does give me an idea to add filters for specific bases and specific units, which I'll do.



    1EyedJacks -> RE: Intel Reports (12/23/2009 5:54:16 PM)

    btw - thanks Floydg & Damian - for your support and work on Tracker. It is a most excellent tool.

    Wishing you both a Merry Christmas and a happy New Year,

    Mike



    floydg -> RE: Intel Reports (12/23/2009 6:02:08 PM)


    quote:

    ORIGINAL: 1EyedJacks

    btw - thanks Floydg & Damian - for your support and work on Tracker. It is a most excellent tool.

    Wishing you both a Merry Christmas and a happy New Year,

    Mike


    Thanks, Mike!

    I can't speak for Damian, but I do this work to boost my ego... [;)] (my wife, however, feels that I do it to avoid my family)



    Smeulders -> RE: Intel Reports (12/23/2009 6:27:14 PM)


    quote:

    ORIGINAL: floydg
    But that does give me an idea to add filters for specific bases and specific units, which I'll do.


    Would be immensely useful when planning attacks, first check the bases you're planning on attacking then checking if the units weren't deployed anywhere else. Seems like a great addition.



    tc464 -> RE: Intel Reports (12/23/2009 6:58:21 PM)


    quote:

    ORIGINAL: floydg

    I must have a lot of stored-up energy for the winter, since I started working on an intel panel. I think the first release will be about this level:
  • Reads in the sigint text files
  • Displays in a table that you can sort and filter

    Eventually, I'll add this to the map and expand to include the operations report and Combat Events files. Not so sure about the combatreport...

    Any comments or suggestions?

    Floyd



    • I had started doing something along these lines for myself, and a few things in the combat reports would be useful...

    I was going to attempt to track the location of every ship mentioned in those reports because they give a location for that day. I don't know if anyone would be able to spot trends over time or anything, but spotting ships that you know are part of a carrier TF would be useful. I may not spot the Akagi for instance, but if one its escorts popped up for a day.... Also, spotting AK, TK, etc at roughly the same locations could indicate shiiping lanes your opponent has established or changed. Useful for deploying your subs.

    LCU's are also listed for the ground combat reports. Again, that gives their location, if only for a couple days.

    Finally, I was going to track the number and frequency of air raids. Not very useful really, but an increase in frequency could indicate that your opponent has an interest in a particular location. This would probably be more useful for the Japs later on.

    Just my 0.02



    floydg -> RE: Intel Reports (12/23/2009 7:54:14 PM)


    quote:

    ORIGINAL: tc464


    quote:

    ORIGINAL: floydg

    I must have a lot of stored-up energy for the winter, since I started working on an intel panel. I think the first release will be about this level:
  • Reads in the sigint text files
  • Displays in a table that you can sort and filter

    Eventually, I'll add this to the map and expand to include the operations report and Combat Events files. Not so sure about the combatreport...

    Any comments or suggestions?

    Floyd



    • I had started doing something along these lines for myself, and a few things in the combat reports would be useful...

    I was going to attempt to track the location of every ship mentioned in those reports because they give a location for that day. I don't know if anyone would be able to spot trends over time or anything, but spotting ships that you know are part of a carrier TF would be useful. I may not spot the Akagi for instance, but if one its escorts popped up for a day.... Also, spotting AK, TK, etc at roughly the same locations could indicate shiiping lanes your opponent has established or changed. Useful for deploying your subs.

    LCU's are also listed for the ground combat reports. Again, that gives their location, if only for a couple days.

    Finally, I was going to track the number and frequency of air raids. Not very useful really, but an increase in frequency could indicate that your opponent has an interest in a particular location. This would probably be more useful for the Japs later on.

    Just my 0.02



    Good ideas -- I'll incorporate everything I can (eventually).



    ny59giants -> RE: Intel Reports (12/25/2009 10:48:10 PM)

    I'm playing 2 day turns against the Japanese AI using Andy Mac's Ironman. I can initialize Tracker for the first turn (which was just 25 Dec 41), but when I tries to load the last two day turn, it crashes as soon as it starts to load the new turn. What am I doing wrong?? [&:]



    floydg -> RE: Intel Reports (12/25/2009 11:02:30 PM)


    quote:

    ORIGINAL: ny59giants

    I'm playing 2 day turns against the Japanese AI using Andy Mac's Ironman. I can initialize Tracker for the first turn (which was just 25 Dec 41), but when I tries to load the last two day turn, it crashes as soon as it starts to load the new turn. What am I doing wrong?? [&:]


    If the second turn read crashes quickly, it's probably a memory issue (and there should be some crash log created). Are you running from the .bat or the .jar?

    Floyd



    ny59giants -> RE: Intel Reports (12/26/2009 2:23:00 AM)

    I'm running from the .jar (I have created a shortcut and relabeled it under the "SAVE" folder on my desktop).

    Where is the crash log found??



    floydg -> RE: Intel Reports (12/26/2009 2:26:08 AM)


    quote:

    ORIGINAL: ny59giants

    I'm running from the .jar (I have created a shortcut and relabeled it under the "SAVE" folder on my desktop).

    Where is the crash log found??



    If you have to run it from the .jar, you'll need to find a way to ensure the JVM has the memory settings in the .bat. Or you can create the shortcut to the .bat file... [;)]

    The crash log should be in the WitPTracker AE folder.



    ny59giants -> RE: Intel Reports (12/26/2009 2:35:05 AM)

    Thanks Floyd! [&o]

    I got it to run from the .bat file and will make a shortcut this way. Is there a simple explanation of why I had to go this route?? I've been using various versions of Tracker (WITP and now AE) for some time. This was the first time I couldn't use the .jar shortcut.



    floydg -> RE: Intel Reports (12/26/2009 2:56:40 AM)


    quote:

    ORIGINAL: ny59giants

    Thanks Floyd! [&o]

    I got it to run from the .bat file and will make a shortcut this way. Is there a simple explanation of why I had to go this route?? I've been using various versions of Tracker (WITP and now AE) for some time. This was the first time I couldn't use the .jar shortcut.



    "Classic" WitPTracker didn't need more memory, so it was never an issue.

    The AE version needs more memory because of the DLL. I don't know how you got it to work via the jar file before, so I can't explain it.



    n01487477 -> RE: Intel Reports (12/26/2009 11:01:58 AM)

    Just to let you know that while Floyd is steaming ahead, I'm chugging along slowly(with his help) ... but I've updated the Industry - > Global screen to show a breakdown history of Res,Oil,Fuel,Supplies. It looks very cluttered etc ... I will render arrows for the totals, but does this look ok or do you just want the totals ?

    Also added some more cargo information to the TF histories... but will decide later if it is ready for inclusion.

    Have a good holidays ;)



    [image]local://upfiles/19798/CC78CD3E24F44A5FA6C2BF3D753CC660.jpg[/image]



    n01487477 -> RE: Intel Reports (12/27/2009 1:29:32 PM)

    Someone requested that I make the Air Production screen able to do full screen & with dates - it took a while to do cause I had to re-engineer most of it ... anyway here it is. I can't do this for the Industry screen due to the chart (or until I find a way to contain it properly) + have time to do that. Still a lot I'd like to do before next release...


    [image]local://upfiles/19798/F37BB40B5F4A466B8F538659E7F66E84.jpg[/image]



    Oliver Heindorf -> RE: Intel Reports (12/28/2009 2:43:16 PM)

    In the early days of witp before anyone released a tool, I had a spread sheet which contained all units ever heard of by sigint, all ships by sigint etc. by date and where (if data is aviable.

    the next page contained intel on the enemy ships sighted.(by battle for example, or by op.txt file (wehre, when) etc. to give me a closer look how Xargun&other pbem enemies used their stuff.




    floydg -> RE: Intel Reports (12/28/2009 3:34:04 PM)


    quote:

    ORIGINAL: Oliver Heindorf

    In the early days of witp before anyone released a tool, I had a spread sheet which contained all units ever heard of by sigint, all ships by sigint etc. by date and where (if data is aviable.

    the next page contained intel on the enemy ships sighted.(by battle for example, or by op.txt file (wehre, when) etc. to give me a closer look how Xargun&other pbem enemies used their stuff.




    Lomg-term, that's the goal. For the next release, it'll be a start.



    AFIntel -> RE: WitPTracker AE Release 1.2 Available (12/31/2009 6:05:09 AM)

    Guys,

    I know that you are probably tired of us "non-techies" asking for your help to solve (very likely) simple problems [:D]

    ...and I am sure that the answer to my question is in the forum somewhere (but please trust me when I say I've been through the entire WitPTracker AE Release thread...honestly). In fact, most of my prior Tracker problems were solved by patiently reading through the thread.

    [&:] But I am now at wits end. I cannot for the life of me get the Tracker running correctly.

    Here is the issue:

    I can initially load Tracker and read the first turn. However, when I click "Multi-turn", select "all .pws", check the turns I want to load and click "Load", the program closes and creates the below-listed error.

    I load from the .jar as I have never had luck running from the .bat

    Here is my PROPERTIES file if that would help in any way - I copy the .pws files to the Tracker folder:

    Dir=[D:\Matrix Games\WITP_AE]
    GameType=[0]
    Side=[1]
    Password=[abc123]
    SaveFile=[wpae003.pws]
    SaveMode=[0]

    And, yes, I am running one of those pesky 64-bit systems that seem to cause y'all a headache!

    Any help you can spare this poor lad is greatly appreciated!!

    Eddie

    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d901afd, pid=110780, tid=111248
    #
    # JRE version: 6.0_17-b04
    # Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode, sharing windows-x86 )
    # Problematic frame:
    # V [jvm.dll+0x101afd]
    #
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    #

    --------------- T H R E A D ---------------

    Current thread (0x054e6800): JavaThread "SwingWorker-pool-2-thread-1" [_thread_in_vm, id=111248, stack(0x0a720000,0x0a770000)]

    siginfo: ExceptionCode=0xc0000005, reading address 0x00000000

    Registers:
    EAX=0x00000000, EBX=0x054e6800, ECX=0x054e6800, EDX=0x6d9f1158
    ESP=0x0a76f7b8, EBP=0x0a76f7d4, ESI=0x054e6910, EDI=0x00000000
    EIP=0x6d901afd, EFLAGS=0x00010246

    Top of Stack: (sp=0x0a76f7b8)
    0x0a76f7b8: 0546d3b0 054e6910 00000000 054e6800
    0x0a76f7c8: 0515948c 00000094 6d9f1158 04aa7200
    0x0a76f7d8: 10002eaf 054e6800 00000000 00000000
    0x0a76f7e8: 00e7ef00 1aeb67f0 100035fd 00000000
    0x0a76f7f8: 00000000 00e7ef00 1aeb67f0 287ab538
    0x0a76f808: 0a76f85c 054e6800 287ab538 04aa7260
    0x0a76f818: 00000014 00000017 00e7ef00 1aeb67f0
    0x0a76f828: 1001c90c 02559e37 04aa71e8 04aa7248

    Instructions: (pc=0x6d901afd)
    0x6d901aed: 8d 4d f0 e8 cb ce 07 00 8b 7d 10 85 ff 8b 45 0c
    0x6d901afd: 8b 10 7c 50 8b 45 14 85 c0 7c 49 8b 72 08 8d 0c


    Stack: [0x0a720000,0x0a770000], sp=0x0a76f7b8, free space=317k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    V [jvm.dll+0x101afd]

    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    j JNIpws.JNIpws.jPWSGetNextItem()V+0
    j witptracker.SaveFileReader.<init>(Ljava/lang/String;Lwitptracker/Properties;ZLwitptracker/Database;Lwitptracker/InMemoryDB;Lwitptracker/Footer;I)V+322
    j witptracker.ReadTurnTask.doInBackground()Ljava/lang/Void;+136
    j witptracker.ReadTurnTask.doInBackground()Ljava/lang/Object;+1
    j javax.swing.SwingWorker$1.call()Ljava/lang/Object;+14
    J java.util.concurrent.FutureTask$Sync.innerRun()V
    J java.util.concurrent.FutureTask.run()V
    j javax.swing.SwingWorker.run()V+4
    j java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Ljava/lang/Runnable;)V+59
    j java.util.concurrent.ThreadPoolExecutor$Worker.run()V+28
    j java.lang.Thread.run()V+11
    v ~StubRoutines::call_stub

    --------------- P R O C E S S ---------------

    Java Threads: ( => current thread )
    =>0x054e6800 JavaThread "SwingWorker-pool-2-thread-1" [_thread_in_vm, id=111248, stack(0x0a720000,0x0a770000)]
    0x054e5c00 JavaThread "Swing-Shell" daemon [_thread_blocked, id=111184, stack(0x056d0000,0x05720000)]
    0x054e5800 JavaThread "Image Fetcher 0" daemon [_thread_blocked, id=111176, stack(0x05680000,0x056d0000)]
    0x054e5000 JavaThread "D3D Screen Updater" daemon [_thread_blocked, id=111144, stack(0x098f0000,0x09940000)]
    0x05496000 JavaThread "TimerQueue" daemon [_thread_blocked, id=111120, stack(0x0a190000,0x0a1e0000)]
    0x003f9000 JavaThread "DestroyJavaVM" [_thread_blocked, id=110800, stack(0x00b50000,0x00ba0000)]
    0x053c1800 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=111088, stack(0x05760000,0x057b0000)]
    0x0539e800 JavaThread "AWT-Windows" daemon [_thread_blocked, id=111076, stack(0x05570000,0x055c0000)]
    0x054fc800 JavaThread "AWT-Shutdown" [_thread_blocked, id=111072, stack(0x05520000,0x05570000)]
    0x054f8c00 JavaThread "Java2D Disposer" daemon [_thread_in_native, id=111068, stack(0x04d70000,0x04dc0000)]
    0x024af400 JavaThread "HSQLDB Timer @1ff5ea7" daemon [_thread_blocked, id=110856, stack(0x04c20000,0x04c70000)]
    0x02439800 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=110840, stack(0x048f0000,0x04940000)]
    0x02432c00 JavaThread "CompilerThread0" daemon [_thread_blocked, id=110832, stack(0x04860000,0x048b0000)]
    0x02430400 JavaThread "Attach Listener" daemon [_thread_blocked, id=110828, stack(0x047d0000,0x04820000)]
    0x02427c00 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=110824, stack(0x04740000,0x04790000)]
    0x023e6800 JavaThread "Finalizer" daemon [_thread_blocked, id=110812, stack(0x046b0000,0x04700000)]
    0x023e2000 JavaThread "Reference Handler" daemon [_thread_blocked, id=110808, stack(0x04620000,0x04670000)]

    Other Threads:
    0x023e0800 VMThread [stack: 0x04590000,0x045e0000] [id=110804]
    0x0243ac00 WatcherThread [stack: 0x04980000,0x049d0000] [id=110852]

    VM state:synchronizing (normal execution)

    VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
    [0x003f75d0] Threads_lock - owner thread: 0x023e0800

    Heap
    def new generation total 4544K, used 30K [0x24550000, 0x24a30000, 0x24a30000)
    eden space 4096K, 0% used [0x24550000, 0x24557b28, 0x24950000)
    from space 448K, 0% used [0x249c0000, 0x249c0000, 0x24a30000)
    to space 448K, 0% used [0x24950000, 0x24950000, 0x249c0000)
    tenured generation total 60544K, used 50551K [0x24a30000, 0x28550000, 0x28550000)
    the space 60544K, 83% used [0x24a30000, 0x27b8dda0, 0x27b8de00, 0x28550000)
    compacting perm gen total 12288K, used 7132K [0x28550000, 0x29150000, 0x2c550000)
    the space 12288K, 58% used [0x28550000, 0x28c47018, 0x28c47200, 0x29150000)
    ro space 8192K, 63% used [0x2c550000, 0x2ca68b20, 0x2ca68c00, 0x2cd50000)
    rw space 12288K, 53% used [0x2cd50000, 0x2d3c5138, 0x2d3c5200, 0x2d950000)

    Dynamic libraries:
    0x00400000 - 0x00424000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\javaw.exe
    0x76f70000 - 0x770d0000 C:\Windows\SysWOW64\ntdll.dll
    0x76450000 - 0x76560000 C:\Windows\syswow64\kernel32.dll
    0x76ae0000 - 0x76ba6000 C:\Windows\syswow64\ADVAPI32.dll
    0x766f0000 - 0x767e0000 C:\Windows\syswow64\RPCRT4.dll
    0x74f40000 - 0x74fa0000 C:\Windows\syswow64\Secur32.dll
    0x76130000 - 0x76200000 C:\Windows\syswow64\USER32.dll
    0x76200000 - 0x76290000 C:\Windows\syswow64\GDI32.dll
    0x768b0000 - 0x76910000 C:\Windows\system32\IMM32.DLL
    0x767e0000 - 0x768a8000 C:\Windows\syswow64\MSCTF.dll
    0x76560000 - 0x7660a000 C:\Windows\syswow64\msvcrt.dll
    0x76f40000 - 0x76f49000 C:\Windows\syswow64\LPK.DLL
    0x76a60000 - 0x76add000 C:\Windows\syswow64\USP10.dll
    0x7c340000 - 0x7c396000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\msvcr71.dll
    0x6d800000 - 0x6da8b000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\client\jvm.dll
    0x73c30000 - 0x73c62000 C:\Windows\system32\WINMM.dll
    0x76910000 - 0x76a55000 C:\Windows\syswow64\ole32.dll
    0x762a0000 - 0x7632d000 C:\Windows\syswow64\OLEAUT32.dll
    0x73bf0000 - 0x73c2d000 C:\Windows\system32\OLEACC.dll
    0x73c70000 - 0x73c9c000 C:\Windows\system32\apphelp.dll
    0x6d7b0000 - 0x6d7bc000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\verify.dll
    0x6d330000 - 0x6d34f000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\java.dll
    0x6d290000 - 0x6d298000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\hpi.dll
    0x76120000 - 0x76127000 C:\Windows\syswow64\PSAPI.DLL
    0x6d7f0000 - 0x6d7ff000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\zip.dll
    0x6d610000 - 0x6d623000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\net.dll
    0x752a0000 - 0x752cd000 C:\Windows\syswow64\WS2_32.dll
    0x76290000 - 0x76296000 C:\Windows\syswow64\NSI.dll
    0x6ff40000 - 0x6ff7b000 C:\Windows\system32\mswsock.dll
    0x74e10000 - 0x74e15000 C:\Windows\System32\wship6.dll
    0x6d630000 - 0x6d639000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\nio.dll
    0x10000000 - 0x1d357000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\pwsdll.dll
    0x74a30000 - 0x74acb000 C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d\MSVCR80.dll
    0x6d000000 - 0x6d14a000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\awt.dll
    0x73e70000 - 0x73eb2000 C:\Windows\system32\WINSPOOL.DRV
    0x74600000 - 0x7479e000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\comctl32.dll
    0x76690000 - 0x766e9000 C:\Windows\syswow64\SHLWAPI.dll
    0x6ffd0000 - 0x6ffdc000 C:\Windows\system32\DWMAPI.DLL
    0x72970000 - 0x729f0000 C:\Windows\system32\uxtheme.dll
    0x6d230000 - 0x6d284000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\fontmanager.dll
    0x698a0000 - 0x69a5a000 C:\Windows\system32\d3d9.dll
    0x74e50000 - 0x74e58000 C:\Windows\system32\VERSION.dll
    0x731a0000 - 0x731a6000 C:\Windows\system32\d3d8thk.dll
    0x6ac40000 - 0x6b032000 C:\Windows\system32\atiumdag.dll
    0x6a7a0000 - 0x6ac3b000 C:\Windows\system32\atiumdva.dll
    0x752d0000 - 0x75de0000 C:\Windows\syswow64\shell32.dll
    0x745c0000 - 0x745fb000 C:\Windows\system32\rsaenh.dll
    0x73a90000 - 0x73aae000 C:\Windows\system32\USERENV.dll
    0x74e00000 - 0x74e0f000 C:\Windows\system32\NLAapi.dll
    0x73880000 - 0x73899000 C:\Windows\system32\IPHLPAPI.DLL
    0x73700000 - 0x73735000 C:\Windows\system32\dhcpcsvc.DLL
    0x738c0000 - 0x738ec000 C:\Windows\system32\DNSAPI.dll
    0x73ae0000 - 0x73ae7000 C:\Windows\system32\WINNSI.DLL
    0x73850000 - 0x73872000 C:\Windows\system32\dhcpcsvc6.DLL
    0x74df0000 - 0x74dff000 C:\Windows\system32\napinsp.dll
    0x74db0000 - 0x74dc2000 C:\Windows\system32\pnrpnsp.dll
    0x74de0000 - 0x74de8000 C:\Windows\System32\winrnr.dll
    0x76610000 - 0x76659000 C:\Windows\syswow64\WLDAP32.dll
    0x6ffa0000 - 0x6ffa5000 C:\Windows\System32\wshtcpip.dll
    0x74e20000 - 0x74e26000 C:\Windows\system32\rasadhlp.dll
    0x6d450000 - 0x6d474000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\jpeg.dll
    0x6d1a0000 - 0x6d1c3000 D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\bin\dcpr.dll
    0x763c0000 - 0x76444000 C:\Windows\syswow64\CLBCatQ.DLL
    0x74fa0000 - 0x7512a000 C:\Windows\syswow64\SETUPAPI.dll
    0x662d0000 - 0x664f3000 C:\Windows\system32\NetworkExplorer.dll
    0x70960000 - 0x70a1b000 C:\Windows\system32\PROPSYS.dll
    0x6c3e0000 - 0x6c4e8000 C:\Windows\System32\shdocvw.dll
    0x73e50000 - 0x73e64000 C:\Windows\system32\MPR.dll
    0x72ec0000 - 0x72ed3000 C:\Windows\System32\ntlanman.dll
    0x748c0000 - 0x74936000 C:\Windows\System32\NETAPI32.dll
    0x73170000 - 0x73178000 C:\Windows\System32\drprov.dll
    0x72d60000 - 0x72d72000 C:\Windows\System32\davclnt.dll
    0x72870000 - 0x72962000 C:\Windows\System32\CRYPT32.dll
    0x738a0000 - 0x738b2000 C:\Windows\System32\MSASN1.dll
    0x73180000 - 0x7318b000 C:\Windows\system32\cscapi.dll
    0x66060000 - 0x662ce000 C:\Windows\system32\wpdshext.dll
    0x72320000 - 0x724cb000 C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18005_none_9e50b396ca17ae07\gdiplus.dll
    0x6e390000 - 0x6e3e6000 C:\Windows\system32\PortableDeviceApi.dll
    0x73740000 - 0x7376d000 C:\Windows\system32\WINTRUST.dll
    0x76660000 - 0x76689000 C:\Windows\syswow64\imagehlp.dll
    0x6e6f0000 - 0x6e71b000 C:\Windows\system32\PortableDeviceTypes.dll
    0x72d20000 - 0x72d5f000 C:\Windows\system32\audiodev.dll
    0x71e70000 - 0x720bb000 C:\Windows\system32\WMVCore.DLL
    0x72830000 - 0x72869000 C:\Windows\system32\WMASF.DLL
    0x73290000 - 0x732af000 C:\Windows\system32\EhStorShell.dll
    0x72cc0000 - 0x72ce0000 C:\Windows\SysWOW64\EhStorAPI.dll
    0x72f10000 - 0x72f19000 C:\Windows\system32\LINKINFO.dll
    0x65e50000 - 0x66060000 C:\Windows\system32\oobefldr.dll
    0x72df0000 - 0x72e04000 C:\Windows\system32\ATL.DLL
    0x6c080000 - 0x6c157000 C:\Windows\system32\WINBRAND.dll
    0x71980000 - 0x719ba000 C:\Windows\system32\slc.dll
    0x6e730000 - 0x6e74e000 C:\Windows\system32\Shimeng.dll

    VM Arguments:
    java_command: D:\Matrix Games\WITP_AE\Extras\WitPTracker AE Release 1.2\witptracker.jar
    Launcher Type: SUN_STANDARD

    Environment Variables:
    CLASSPATH=.;C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip
    PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Common Files\Roxio Shared\9.0\DLLShared\;C:\Harpoon 3 Advanced Naval Warfare\Delta3d;C:\Harpoon 3 Advanced Naval Warfare\Delta3d\ext;C:\Program Files (x86)\QuickTime\QTSystem\
    USERNAME=Eddie
    OS=Windows_NT
    PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 23 Stepping 6, GenuineIntel



    --------------- S Y S T E M ---------------

    OS: Windows Vista Build 6002 Service Pack 2

    CPU:total 2 (2 cores per cpu, 1 threads per core) family 6 model 23 stepping 6, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1

    Memory: 4k page, physical 4191636k(1833632k free), swap 4194303k(4194303k free)

    vm_info: Java HotSpot(TM) Client VM (14.3-b01) for windows-x86 JRE (1.6.0_17-b04), built on Oct 11 2009 00:52:06 by "java_re" with MS VC++ 7.1

    time: Thu Dec 31 00:00:24 2009
    elapsed time: 56 seconds




    n01487477 -> RE: WitPTracker AE Release 1.2 Available (12/31/2009 6:22:52 AM)

    AFIntel,
    This is a Java memory setting problem, so your basic problem is that you are running from the JAR file and not the batch.

    Many 64 bit users have to use this command window to then run the batch file.
    C:\Windows\SysWOW64\cmd.exe
    So you can make a shortcut to it in your tracker folder. Click it ... Then type the command in the dos screen "witptracker.bat"

    OR
    Is there a way to make a shortcut so I dont have to do the DOS command manually each time? By default, when I double click on the .bat file, it uses the wrong .cmd file. How can I set this up?

    Well the quick way I did it was to make a copy of the bat file and rename the extension to something wacky then associate ("Open With..") that extension to the correct cmd which will open the cmd window in that directory.

    Failing this, I have a build using a 3rd party Java extension that I can email to you if you PM me ur details...

    Sorry, I sent Floyd some details about this some time ago, although I think the email got lost ... and hasn't been put up on the web site.



    Page: <<   < prev  21 22 [23] 24 25   next >   >>

    Valid CSS!




    Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
    2.40625