nikolatesla20
April 12th, 2002, 05:08
Well thanx all for your help I did a search of the MB for commview and I finally got it unpacked and working, but still some probs!
The program runs just fine on its own, it doesn't "appear" to have any size checks or the like. It comes up and functions normal. But as soon as you try to patch ANY of its bytes on disk it crashes like a mother, spitting out delphi exceptions..I beleive this is written in delphi isn't it? DeDe won't decompile it at all.
It almost seems like there is another layer of protection or something. I can't even use a memory loader like I did for BPFTP Server. It still creates exceptions. What it almost looks like is that when it detects a change in its code, (or "critical" sections of code, like that jmp the fixes the half the packets bug
), that it then tries to call asprotect or something.
I kinda know when asprotect gets called because on my win98 machine it comes up as a 084:00000000 address where the crash happened. Yep obscure as hell. ANyway I've got to get some sleep tonite so gotta wait until tomm. to try fixing the bugs.
Thanks though for your knowledge all out there, I've never been able to dump this program before.
OH WELL OOPS and another thing, yep it crashes after a min or so with an error 212. I beleive that is a delphi memory access error. Looks like there are some good trix in this build. No wonder they don't need a size check. Time to find that damn timer....and possibly some weird crc check of some sort. Well at least it runs :P for like 40 seconds. lol.
-nt20
The program runs just fine on its own, it doesn't "appear" to have any size checks or the like. It comes up and functions normal. But as soon as you try to patch ANY of its bytes on disk it crashes like a mother, spitting out delphi exceptions..I beleive this is written in delphi isn't it? DeDe won't decompile it at all.
It almost seems like there is another layer of protection or something. I can't even use a memory loader like I did for BPFTP Server. It still creates exceptions. What it almost looks like is that when it detects a change in its code, (or "critical" sections of code, like that jmp the fixes the half the packets bug

I kinda know when asprotect gets called because on my win98 machine it comes up as a 084:00000000 address where the crash happened. Yep obscure as hell. ANyway I've got to get some sleep tonite so gotta wait until tomm. to try fixing the bugs.
Thanks though for your knowledge all out there, I've never been able to dump this program before.

OH WELL OOPS and another thing, yep it crashes after a min or so with an error 212. I beleive that is a delphi memory access error. Looks like there are some good trix in this build. No wonder they don't need a size check. Time to find that damn timer....and possibly some weird crc check of some sort. Well at least it runs :P for like 40 seconds. lol.
-nt20