I had a stub program that I had originally assembled using MASM that I converted to Fasm syntax and assembled. This stub has a cab file appended to it using the DOS copy command (/b switch). The stub offloads the cab file, unpacks it and then loads the dll that was compressed in the cab. The dll actually creates an installation Wizard. The weird thing is though everything runs okays, if you click Cancel when the wizard is running the dialog box that pops up with the FASM assembled version is resized and doesn't use the font specified in the resource file (looks like the system font???). I was wondering if anyone could let me know why this is happening?? The zip file contains both versions plus the cab and a .bat file for quickly making the "setup" program.
Any help much appreciated.
Cheers,
Andrew

I deleted everything from the dll the stub loads just on the offchance that maybe there was some resource in the dll that was responsible. I ended up with a dll that simply displays a 3 page wizard with no resource allocation and almost no code. However the problem with the FASM assembled stub persists. If you click cancel when the wizard is loaded the dialog is incorrectly displayed. Something is happening in memory somewhere... I checked out the PE headers with the MASM and FASM stubs to note any differences. This resulted in my increasing the stack and heap reserve with the FASM .exe (in the assembly using the stack/heap directives) but, as I expected, this made no difference. If anyone could give me a few tips as to what I should be looking at this would be most appreciated.
Thanks,
Andrew

No ideas anyone?