Closed GoogleCodeExporter closed 8 years ago
Another note - KParser was working fine for me at first, then this started
occuring
out of nowhere seemingly, can't remember the first time I had the issue with
having
to maximize it, at first I thought it just wasn't loading properly, a couple
days
later I discovered I could view it by maximizing it, first time I attempted
parsing
after this problem first occurred was April 9th.
Original comment by cynicalsaint1@gmail.com
on 15 Apr 2009 at 10:25
Ok, the problem here is that the location of the window has somehow been set to
some
extreme value that are outside the range of the normal viewport. It happens
rarely,
when Windows flakes out for no particular reason I've been able to determine.
I'll
be adding code to watch for it and reset the base position.
To fix it manually, go to the following directory:
C:\Documents and Settings\<user>\Local Settings\Application
Data\Wayward_Gamers\KParser.exe_Url_<randomString>\1.3.7.0
In that directory is an XML file called user.settings. Edit it with a text
editor,
and change the mainWindowPosition coordinates to reasonable values (and
optionally
the window size values, if they're out of line as well).
Original comment by Kinemati...@gmail.com
on 16 Apr 2009 at 6:00
Alright, that fixed the problem with the window not showing up unless
maximized, but
I'm still unable to Parse.
1. Load KParser
2. Load FFXI
3. Set to parse from memory, have not manually changed the memloc
4. Begin Parse
5. Kill a couple random enemies, say a few things in chat
6. Alt-tab to parser to check, nothing has been parsed
7. Stop Parsing
8. Switch to parse from chat logs
9. Ensure that its pointing to my FFXI TEMP folder
10. Begin Parse
11. Kill a couple random enemies, say a few things in chat
12. Alt-tab to check parser, nothing has been parsed.
Original comment by cynicalsaint1@gmail.com
on 17 Apr 2009 at 6:13
I've double checked the memory settings and everything appears to be running OK.
Rereading the initial bug, I realized you're upgrading from 1.3.4. 1.3.5 added
a
feature to upgrade settings values (ie: remember open tabs and window location)
across versions. Because of that, simply copying in the new version of the
parser
will not automatically update the memloc value for you; it will copy the value
from
the previous version.
To fix that, you can manually modify the value (the new value is 0x0057d768),
or hit
Reset to restore settings to the defaults. The default value for the new
version is
the correct memloc. You may need to adjust the other settings after that,
though.
Have also updated the window code to force the window to be visible if it ends
up in
a location out of normal visible range.
Original comment by Kinemati...@gmail.com
on 21 Apr 2009 at 10:32
Still having trouble, I'm wondering if some obscure setting somewhere hasn't
been
messed up, like the window location, b/c the two seemed to start occurring at
the
same time. Also I don't think its the memloc as it wasn't parsing from the log
files
either.
What would I need to do to completely uninstall the program and start with a
fresh
install? Anything other than delete the current directory?
Original comment by cynicalsaint1@gmail.com
on 27 Apr 2009 at 9:07
Delete the directory that you extracted KParser to, and also delete the
mentioned
Wayward_Gamers directory and subdirectories.
Original comment by Kinemati...@gmail.com
on 29 Apr 2009 at 7:59
Doing a fresh install worked. I had to take an additional step however to get
things
working: Delete the directory c:\Program Data\Wayward Gamers
Here's the detailed steps:
1. Deleted the extraction directory
2. Deleted the <user_name>\App_Data\local\Wayward_Gamers (this is where the
settings
xml is for Vista)
3. Download latest version of KParser and extract it
4. Set the .exe to run as admin
5. Load FFXI and attempt to parse
6. No parsing occurs
7. Repeat step 1-2
8. Delete directory c:\Program Data\Wayward_Gamers (this is where default parse
file
is located)
9. Repeat steps 3-5
10. Parsed Successfully
Maybe the default Parse file was corrupted somehow?
Original comment by cynicalsaint1@gmail.com
on 29 Apr 2009 at 6:42
Closing this bug as fixed. More changes have been made to the settings/install,
including dealing with certain Vista/Win7 requirements. As such any new
incidences
should open a new bug.
Original comment by Kinemati...@gmail.com
on 2 Nov 2009 at 8:53
Original issue reported on code.google.com by
cynicalsaint1@gmail.com
on 15 Apr 2009 at 10:18