Working Parser?

[Wenslydale]

It's another parser option. I actually like it better the Dparse (no offense) but yeah, I gave up screwing around with trying to change the memloc on the thing. Windower Forums have some suggestions that may work for you, but they didn't for me so...

And on a hunch, I re-downloaded the latest Timestamp. Dparse is working now with Timestamp so... guess that was the problem? Though, I remember updating ALL my plug-ins when the server was down a week ago. It's still Timestamp 2.1 and it doesn't say that they've updated it recently so... your guess is as good as mine at this point.

[Amele]

It's another parser option. I actually like it better the Dparse (no offense) but yeah, I gave up screwing around with trying to change the memloc on the thing. Windower Forums have some suggestions that may work for you, but they didn't for me so...

And on a hunch, I re-downloaded the latest Timestamp. Dparse is working now with Timestamp so... guess that was the problem? Though, I remember updating ALL my plug-ins when the server was down a week ago. It's still Timestamp 2.1 and it doesn't say that they've updated it recently so... your guess is as good as mine at this point.

couldn't tell you.

as for kparse, I don't know which pointers they are referencing or if they're even building it the same way we are so I couldn't tell you - it's unlikely that our pointer is the same.

[Wenslydale]

I wanna say that they are using the old Kapersky Model for it, but I'm too lazy to look. It had the option of parsing BLU spells indivdually, or so I had heard. Like I said, I could never get it work so I gave up on it.

[Zhais]

couldn't tell you.

as for kparse, I don't know which pointers they are referencing or if they're even building it the same way we are so I couldn't tell you - it's unlikely that our pointer is the same.

I want to say that kparser originally based its memory reader off of the directparse chatmon section as far as I understood it. I remember going through his code at one point and seeing that. Been a while tho, but the memloc is the same.

[Wenslydale]

Yeah, If I remember correctly, Kapersky used slot of the Dparse source. It would make sence that if Kparser = Kapersky = Dparse....

[KSDI]

it doesn't seem to accept the "x" in the new memloc, when i switch that for a 0 it allows the change to happen but not when i try to put in the correct one. When 0x575968 is put in the OK button to close the dialog box becomes unclickable.

[Amele]

it doesn't seem to accept the "x" in the new memloc, when i switch that for a 0 it allows the change to happen but not when i try to put in the correct one. When 0x575968 is put in the OK button to close the dialog box becomes unclickable.

oh. heh.

it's wanting the hex directly, whereas dParser is explicit. a "0x" prefix is the C-language way of saying 'this is in base 16' other common indicators used are "#" like with colors, or % like in urls, or a trailing h like in intel

0x575968
%575968
#575968
575968h etc.

in our case, we want it as a 0x number, in their case they don't want a prefix or suffix.

[buttson]

simply changing the x to a zero worked for me. the parser works.

[Amele]

simply changing the x to a zero worked for me. the parser works.

that's what I said. mathematically 00575968 is the same as 575968 which is also the same as 00000000000000000000000000575968 >.>;

you shouldn't need the leading 0's if it's doing what I think it is doing.

if they coded it poorly (and it requires 8 places) then yes, it's necessary to do 00xxxxxx but that's a pos code job if so.

[Wenslydale]

The problem I have with Kparser is that when I do change the memloc and hit ok, nothing happens.

[KSDI]

It did work when I changed the x to a zero, thanks for the help.

[Arximiro]

Does anyone know how to get DVS Parse to work with Windows XP pro 64Bit? I'm not even sure if it can since it says 32bit OS's only on Sourceforge. I have .net 2.0 for 64bit Os's installed and the parser will start up with no errors but it won't parse. If any of you know how to get it working on xp64 and could tell me it would be greatly appreciated. ^^

[Amele]

Does anyone know how to get DVS Parse to work with Windows XP pro 64Bit? I'm not even sure if it can since it says 32bit OS's only on Sourceforge. I have .net 2.0 for 64bit Os's installed and the parser will start up with no errors but it won't parse. If any of you know how to get it working on xp64 and could tell me it would be greatly appreciated. ^^

it's stable on vista 64 but I don't think any of the dev's (current or past) ever tried to get it to work on XP64.

personally I recommend dumping your OS.

you need to be running DirectParse with Admin permissions by the way, inter-process memory mapping requires more permission than a typical user/program gets. (dunno enough about XP64 to say if this is the cause but it's worth trying.)

[Arximiro]

Well I'm the admin so I should have the permissions. I'm not sure what you mean by dumping my OS unless you mean to literally get rid of it. Thanks for the advice though, hopefully someone knows about xp64, I'd hate to have to format yet again and go back to 32bit.

[Amele]

Well I'm the admin so I should have the permissions. I'm not sure what you mean by dumping my OS unless you mean to literally get rid of it. Thanks for the advice though, hopefully someone knows about xp64, I'd hate to have to format yet again and go back to 32bit.

I mean literally get rid of it.

now that vista SP1 is out, if you *must have* 64 bit support there's no reason to use XP64. and if you don't there's no reason not to be using XP32 over XP64.

[Arximiro]

I mean literally get rid of it.

now that vista SP1 is out, if you *must have* 64 bit support there's no reason to use XP64. and if you don't there's no reason not to be using XP32 over XP64.

Well a few hundred dollars is the only reason I don't have Vista lol. I've had this 64bit version of XP pro for a couple of years since it came with a 32bit one from college. I suppose I don't have to have a 64bit OS but my system does seem to run smoother on it. Anyways thanks for tips, looks like I'll have to switch back.

[Amele]

Well a few hundred dollars is the only reason I don't have Vista lol. I've had this 64bit version of XP pro for a couple of years since it came with a 32bit one from college. I suppose I don't have to have a 64bit OS but my system does seem to run smoother on it. Anyways thanks for tips, looks like I'll have to switch back.

OEM copies should run you about 130$ from an online retailer (newegg etc).

[Zhais]

So I finally unlazied myself and put out a new release.

All changes since last were done by releenaseraph. A new changelog is included in the release folder as well detailing what all has been done.

https://sourceforge.net/project/plat...roup_id=211255

Enjoy! Hopefully I'll get around to doing something myself soon

[Wenslydale]

Sweets! I love new toys.

[Amele]

this release should fix the japanese non-unicode + timestamp issues btw.