Cakmak,

There is no any restrictions with the DLLs listed in scan.ini.You can add any valid DLL
to the list.

The cinvoke macro is used to call "C" functions,so instead of:



push msg
call printf
add esp,4 ; The stack needs to be balanced.


We use:



cinvoke printf,msg


which generates the required push,call,add esp,x instructions.

You can check the new example in the attachment using the scanner.

Thanks for your kind words.

Regards,

Vortex
Posted on 2003-07-01 03:20:50 by Vortex
Thanks for your helps,

Anyway, i solved the problem after my last post. It is, in scan.ini after last char, added one more space, thats all. Btw, w/o this, it says,
E:\Fasm\Utils\scan300>scan.exe CMDLINE.ASM -f
Unable to read msvcrt.dl
my scan ini is,

kernel32.dll
user32.dll
gdi32.dll
comctl32.dll
comdlg32.dll
msvcrt.dll

i know this is not required but maybe you may see. I will download scan300 one more, maybe i missed an update.

Regards
Posted on 2003-07-01 22:00:35 by cakmak
Cakmak,

All the lines in the file scan.ini must be followed by a CR+LF (ASCII 13,10)
When you are editing this file,you must not put any space characters or empty lines.
You can check my scan.ini files.

Regards,

Vortex
Posted on 2003-07-02 08:30:12 by Vortex
ehm now i checked. I suppose after i added the new dll name i didn't entered. But in fact i suppose it must be so.

And, if used ascii version api names, for example "MessageBoxA" then scanner says undefined. Little thing but why so? I think if that api has A or W then just don't add "equ" line but only import or declare it.

Regards
Posted on 2003-07-02 15:25:47 by cakmak
Cakmak,

The scanner is designed to make a little easier the life. :)
Why you should memorise all the functions terminating with A or W?
Posted on 2003-07-03 05:16:10 by Vortex