Maybe ..
please read carfully...sorry for bad english ...

one day i try to crack an OCX protected by lock .. i try to install int as an component n delphi but i was received an error message saying LOCK SN Error:305

ok then i disassembled it by W32dsm and look at string table the string not found and other string of lock error was there like this
LOCK ... ERROR:303
LOCK ... ERROR:304

BUT error number 305 not found ... ooooh
then i was opened my OCX in EXEscope WOW
it Extract All Strings from file include all lock errors ... such as Lock sn Error:305

may W32dsm have a bug ...
Note : Hiew Was tested too and no more string extracted (like w32dasm)

Tanx to all

Hi

I'm not sure if this answers your question, but if I remember correctly, Win32Dasm is *known* not to recognize all Delphi strings. Not really a bug, but not unusual either. Try DeDe for Delphi apps, you'll find strings not listed in Win32Dasm.

Kayaker

Please remember it is an OCX and not a delphi program.. I want to add it into components of delphi .. but tanx for your assist . i wil try it and anwer soon ..

Sorry my mistake, I guess I misunderstood. Good luck.

the string is probably referenced indirectly in the code, so w32dasm won't "see" it. use ida instead (granted, if this is the case, then ida won't automatically decode it either, but at least you can manually decode it with ida if you know the offset)

Hi,
Like Disavowed said, use IDA you can configure strings type using the option menu :

\OPtions
\ASCII Strings Style ( Alt+A)

If IDA still don't recognize the string, locate it with an hex editor and try to find a string ID (usually some bytes before) and then search in the disassembly anything like : PUSH String_ID.

Maybe because W32dasm does not read Unicode strings.

Have Phun

i have problem with this file ...
please verify it and tell me how it work ..

attachment deleted...

Hi Meteor,
don't attach target specific file! You are new here and maybe you have not yet read the faq, please read the faq!!!

Yes Sure Sorry ..