0000107: Base pointer error

(0000237)
Dark Byte (developer)
2009-02-21 15:32

You're right. The new scan routines has mode this obsolete inocompatible

2 solutions:
1: try ce 5.3
2: find the actual pointer, then you don't need this option.
This routine is only semi-usefull when you find out the original pointer was wrong. But you can already know that beforehand because the address isn't green in the addresslist.

anyhow, to find it manually:
do a hexadecimal scan for addresstofind-offset1
then do a hexscan for the found address-offset2
repeat that till all the offste shave been done

Perhaps you get multiple paths, but that can't be helped

(0000238)
sven3107 (reporter)
2009-02-22 05:53

I tried on 5.4 as well and it works there but none of my tables are compatible anymore...

(0000239)
Dark Byte (developer)
2009-02-22 19:13

hmm, weird. Anyhow:
If you make sure your tables don't contain any structure information you can make it compatible by doing the following:
In the processlist click on "Open file"
click add address manually and add address "b"
change the 8 to 7
and reopen ce
the table can now be loaded

(0000240)
sven3107 (reporter)
2009-02-24 09:38

well, i tried to use it with 5.4 and 5.3but they have the tendency to crash the program as soon as i attach the debugger so i can't even get a starting pointer.

(0000241)
sven3107 (reporter)
2009-02-24 09:46

I found something that might help: when hyperscan is enabled the error message won't pop up but the scan just opens and closes instantly.

(0000307)
Dark Byte (developer)
2009-10-22 20:48

find base pointer has been removed and is now replaced by the pointer scan with preset offsets. Same effect and allows for better configuration

Issue History
Date Modified	Username	Field	Change
2009-02-21 08:58	sven3107	New Issue
2009-02-21 08:58	sven3107	File Added: Error.bmp
2009-02-21 15:32	Dark Byte	Note Added: 0000237
2009-02-21 15:32	Dark Byte	Status	new => confirmed
2009-02-22 05:53	sven3107	Note Added: 0000238
2009-02-22 19:13	Dark Byte	Note Added: 0000239
2009-02-24 09:38	sven3107	Note Added: 0000240
2009-02-24 09:46	sven3107	Note Added: 0000241
2009-10-22 20:48	Dark Byte	Note Added: 0000307
2009-10-22 20:48	Dark Byte	Status	confirmed => resolved
2009-10-22 20:48	Dark Byte	Resolution	open => fixed
2009-10-22 20:48	Dark Byte	Assigned To	=> Dark Byte

Notes
(0000237) Dark Byte (developer) 2009-02-21 15:32	You're right. The new scan routines has mode this obsolete inocompatible 2 solutions: 1: try ce 5.3 2: find the actual pointer, then you don't need this option. This routine is only semi-usefull when you find out the original pointer was wrong. But you can already know that beforehand because the address isn't green in the addresslist. anyhow, to find it manually: do a hexadecimal scan for addresstofind-offset1 then do a hexscan for the found address-offset2 repeat that till all the offste shave been done Perhaps you get multiple paths, but that can't be helped

(0000238) sven3107 (reporter) 2009-02-22 05:53	I tried on 5.4 as well and it works there but none of my tables are compatible anymore...

(0000239) Dark Byte (developer) 2009-02-22 19:13	hmm, weird. Anyhow: If you make sure your tables don't contain any structure information you can make it compatible by doing the following: In the processlist click on "Open file" click add address manually and add address "b" change the 8 to 7 and reopen ce the table can now be loaded

(0000240) sven3107 (reporter) 2009-02-24 09:38	well, i tried to use it with 5.4 and 5.3but they have the tendency to crash the program as soon as i attach the debugger so i can't even get a starting pointer.

(0000241) sven3107 (reporter) 2009-02-24 09:46	I found something that might help: when hyperscan is enabled the error message won't pop up but the scan just opens and closes instantly.

(0000307) Dark Byte (developer) 2009-10-22 20:48	find base pointer has been removed and is now replaced by the pointer scan with preset offsets. Same effect and allows for better configuration

Relationships