What I meant was to use disassembler to convert it and then create all beautiful "invoke" and "stdcall" and ".if" and other macro things, and of course "repare" bad codes (so that we can show that we are smarter than the computer and make an Assembler art of it), but it can be done the other way, because we have nice C++ code thanks to strap89
I actually like a reverse engineering (Paycheck movie), because I fill like a cool hacker. ReactOS is doing that with their system but they do not have source code to look at

regards

Hi revolution, I solved problem with the VC2005 Error spawning 'cmd.exe'.
(I am not that smart, I found it on the web)
solution:

and now I am happy

Oh, a compiler problem. Hehe, well, thankfully, I have never used that compiler. Well done on solving the problem. Looks like the compiler doesn't know how to set it self up properly. Doesn't say much good about the automated installer from MS.

You are right, but I enjoyed programing C# with it

That means he has something else named cmd.exe in his PATH. Since %SystemRoot%\system32 is the first thing there. Definitely not a good idea.

If you have %SystemRoot%\system32 instead of $(SystemRoot)\System32
then you are in deep trouble

Terrible code. Real programmer's horror.

Care to elaborate please? We would all be happy to learn from you.

hey, im no expert(but use to be a 3D modeler), but isnt .obj a 3d model file?

.obj could be anything. But in the programming world, .obj usually means an intermediate file that can be linked into an executable.

Hi Sir:

Where can I get the pecvt.exe utility or source code of it?

Please tell me , thank you.

My email is chychen.chen@msa.hinet.net

Ok, after i Register an login account and I get all the code I need, thank you all!

how can I automate this process (*.fas2pdb) in the sheaf radasm+ollydbg? Manually this process is a very slow & labor-consuming

D:\1\tools>FASM.EXE -s "C:\Documents and Settings\admin\Рабочий стол\some_progra
m.fas" "C:\Documents and Settings\admin\Рабочий стол\some_program.Asm" "C:\Docum
ents and Settings\admin\Рабочий стол\some_program.obj"
flat assembler version 1.68 (1144758 kilobytes memory)
2 passes, 0.1 seconds, 1024 bytes.

D:\1\tools>pecvt.exe -v "C:\Documents and Settings\admin\Рабочий стол\some_progr
am.fas"
incorrect fas file signature

D:\1\tools>pecvt.exe -v "C:\Documents and Settings\admin\Рабочий стол\some_progr
am.fas"
incorrect fas file signature

D:\1\tools>pecvt.exe -v "C:\Documents and Settings\admin\Рабочий стол\some_progr
am.fas" "C:\Documents and Settings\admin\Рабочий стол\some_program.obj"
incorrect fas file signature

What I do wrang ?

i recompile pecvt with if(head.signature!=0x1A736166) and now get error Unsupported machine type
use fasm 168

Hello,

I'm trying to use this nice tool "pecvt.exe" on a file assembled with FASM 1.69.29 but I get "incorrect fas file signature"

I have older version of FASM 1.68 but it also says the same error.

Any help in making "pecvt.exe" to work with FASM 1.69.29?

Thanks!

alorent, hex-edit pecvt.exe. Search for byte sequence 66 61 73 1b and replace 1b with 1a. Or you can fix it in the source: file fas_dispatcher.cpp line 312.

Thanks SFeLi!!! That did the trick!

Hello again,

I have seen that debug information for procedures ("proc") parameters and local variables in procedures are not added in the debug information with "pecvt".

Would it be possible to add it to the debug ouput?

Thanks!

pectv file.fas file.obj

I'm debbugin in ollydbg and reading topic after.

for pecvt15-03-09-SE:

004046C9 |. 8D77 09 LEA ESI,DWORD PTR DS:[EDI+9] ; |
004046CC |. 6A 38 PUSH 38 ; |size = 38 (56.)
004046CE |. 56 PUSH ESI ; |ptr
004046CF |. FF15 44D14000 CALL DWORD PTR DS:[<&MSVCR80.fread>] ; \fread
004046D5 |. 83C4 10 ADD ESP,10
004046D8 |. 813E 6661731B CMP DWORD PTR DS:[ESI],1B736166
004046DE |. 74 25 JE SHORT pecvt.00404705
004046E0 |. 68 98D44000 PUSH pecvt.0040D498 ; /format = "incorrect fas file signature
"
004046E5 |. FF15 A4D04000 CALL DWORD PTR DS:[<&MSVCR80.printf>] ; \printf
004046EB |. 83C4 04 ADD ESP,4
004046EE |. 68 58DC4000 PUSH pecvt.0040DC58


need for pectv 1B736166, in *.fas 1A736166
search for 813E6661731B in winhex and replace 1B on 1A