New version FDA32.

[hutch--]

I have rebuilt FDA2 with a diffferent interface, an embedded manifest file and a version control block which should shut up the crappy end of AV scanners. Application needs read and write access like normal and will assemble any file into a COFF format object module. It writes a matching include file for each module that it writes.

[Magnum]

It's a shame you have to do that extra programming.

I don't even use an AV scanner.

And I run Spybot only when I have eliminated everything else.

I think AV companies are getting some funds for wearing out hard drives quicker.  :bg

[ToutEnMasm]

Beautiful
No sources Code ?

[oex]

No sources Code ?

Hidden from the GPL monster :lol

[hutch--]

 :bg

I will get there, this is written in MASM like the earlier versions but its not "consumer" ready yet.  :P

[drizz]

Beautiful
No sources Code ?

let me dig up my old project...

Code Select Expand


MakeObj proc uses ebx esi edi pFile,pBuff,pBuffSize,pStrSym
LOCAL fh:IMAGE_FILE_HEADER
LOCAL psymoffs:dword
LOCAL sh:IMAGE_SECTION_HEADER
LOCAL sym:IMAGE_SYMBOL
LOCAL strsymlen:dword
LOCAL symstrtablesize:dword
LOCAL symstrtable[100h]:byte
LOCAL nbr

mov eax,pBuffSize
add eax,sizeof IMAGE_FILE_HEADER + sizeof IMAGE_SECTION_HEADER
mov psymoffs,eax
mov symstrtablesize,0
invoke StrLen,pStrSym
mov strsymlen,eax
;----------------------------------------------------------------
mov fh.Machine,IMAGE_FILE_MACHINE_I386
mov fh.NumberOfSections,1
mov fh.TimeDateStamp,0
m2m fh.PointerToSymbolTable,psymoffs
mov fh.NumberOfSymbols,1
mov fh.SizeOfOptionalHeader,0
mov fh.Characteristics,IMAGE_FILE_RELOCS_STRIPPED or IMAGE_FILE_LINE_NUMS_STRIPPED
mov dword ptr sh.Name1[0],'tad.'
mov dword ptr sh.Name1[4],'a'
mov sh.Misc.VirtualSize,0
mov sh.VirtualAddress,0
m2m sh.SizeOfRawData,pBuffSize
mov sh.PointerToRawData, sizeof IMAGE_FILE_HEADER + sizeof IMAGE_SECTION_HEADER
mov sh.PointerToRelocations,0
mov sh.PointerToLinenumbers,0
mov sh.NumberOfRelocations,0
mov sh.NumberOfLinenumbers,0
mov sh.Characteristics,IMAGE_SCN_CNT_INITIALIZED_DATA
mov sym.N.Name1.Short1,0
mov sym.N.Name1.Long1,0
.if strsymlen<=8
invoke CopyMemory,addr sym.N.ShortName,pStrSym,strsymlen
.else
mov sym.N.Name1.Long1,4
mov eax,strsymlen
add eax,4
mov symstrtablesize,eax
.endif
mov sym.Value,0
mov sym.SectionNumber,1
mov sym.Type1,IMAGE_SYM_TYPE_NULL
mov sym.StorageClass,IMAGE_SYM_CLASS_EXTERNAL
mov sym.NumberOfAuxSymbols,0
.if strsymlen > 100h
mov strsymlen,100h
.endif
invoke CopyMemory,addr symstrtable,pStrSym,strsymlen
;----------------------------------------------------------------
invoke fwrite,addr fh,sizeof fh,1,pFile
invoke fwrite,addr sh,sizeof sh,1,pFile
invoke fwrite,pBuff,pBuffSize,1,pFile
invoke fwrite,addr sym,sizeof sym,1,pFile
invoke fwrite,addr symstrtablesize,sizeof symstrtablesize,1,pFile
.if symstrtablesize
invoke fwrite,addr symstrtable,strsymlen,1,pFile
.endif
;----------------------------------------------------------------
ret
MakeObj endp

[hutch--]

 :bg

The source for the last 2 versions is already in the MASM32 SDK, the new version just has a new interface.

[ToutEnMasm]

I have rebuilt FDA2 with a diffferent interface

I agree,but Master Hutch ( :bg) such a beautiful dialog box would be in the masm32 package.
I don't know how to made such a beautiful dialog box.
Perhaps source code with only the dialog box ?? or a sample dialog??.

[hutch--]

 :bg

Yves,

One of your countrymen who writes Axialis tools, Marc Emile. A 24 bit RGB background tile stretched with LoadImage() and a toolbar strip made with IconWorkshop as a 32 bit RGB/a bitmap.

[ToutEnMasm]

many thanks

[ToutEnMasm]

Here is a sample of use
If I can suggest a modify:
General usage for a project is to put all the files in the same directory
In this case,the full path of the data file is an enough answer of the user to create:
                              * the object file in the same directory
                              * the include file in the same directory