flat assembler
Message board for the users of flat assembler.
Index
> Compiler Internals > Suspicious Weird 16 bit output in FASM 1.68 |
Author |
|
_santa 15 Dec 2009, 14:29
I tried to compile a simple bootloader using FASM 1.68 in Windows 7 Professional x64. It did not work. The code was ok, and I decided to disassemble the binary. The output was weird. I aksed my friend to compile the same code under Windows XP Professional 32 bit and disassemble it, the output was ok. I think FASM has some troubles with Windows 7 or 64 bit OSes.
Here I attach the source of the bootloader I tried to compile, my disassembler output (Win 7) and my friends disassembler output (WinXP). Can anyone tell me what's happening?? I will be grateful if someone suggests a solution to fix this.
|
|||||||||||||||||||||||||||||||
15 Dec 2009, 14:29 |
|
rCX 16 Dec 2009, 01:52
I think we'll have to wait for someone with 64-bit OS to test this. Just so everything's clear, it may be a good idea to post the command line used to assemble it and the resulting binary.
|
|||
16 Dec 2009, 01:52 |
|
Madis731 16 Dec 2009, 07:21
I just tried it on Server 2003 (x64) and I got the WinXP_disasm.txt
I don't have a Win7 installation at hand right now, but I guess that the other listing comes from a different source. Both FASMW 1.68 and 1.69 result the same binary. It is really odd that the Win7 one omits the "int" and just dumps hex 10 in there. Its like db 0x10 not int 0x10. Are you *really* sure, its the same source? |
|||
16 Dec 2009, 07:21 |
|
_santa 16 Dec 2009, 15:58
Answering your questions ...
Madis 731, Yes, I'm absolutely sure that the source is the same. Recompiled the source 3 more times, the result is the same. rCX, I used a batch file to build the source... the command line looks like this: "C:\Program Files (x86)\FASM\fasm.exe" "C:\Users\Alex\Documents\Projects\KERNEL\Sources\boot\bootstrap.asm" "C:\Users\Alex\Documents\Projects\KERNEL\Cd-Rom\boot\bootstrap.bin" I would appreciate if someone could test it on another windows 7 installation. It would be really nice. Until this i have no idea what causes this strange compilation and how to fix it. revolution, I've scanned my pc with AV, no malware nor potentially unwanted software found. The pc is virus-clear. |
|||
16 Dec 2009, 15:58 |
|
_santa 16 Dec 2009, 16:29
Recent tests showed that problem is only when using the command-line compiler fasm.exe, not fasmw.exe. I think it is a bit not logical coz fasmw.exe is only a front-end to fasm.exe and is not a separate compiler (or maybe I am mistaken), but the facts are that only command line compilers are affected. I tried the older version, fasm 1.64 and got the same odd output as before.
Any ideas how to fix it? Compiling in fasmw is not a solution for me. Need command line tool. |
|||
16 Dec 2009, 16:29 |
|
LocoDelAssembly 16 Dec 2009, 16:39
I've tried with a Windows 7 and replicating your paths as much as I could (the only difference is that I've used volume F).
Please try exactly what I'm uploading now to be sure we are both testing the same thing. I left a copy of my binary file (Loco.bin) so you can compare differencies. PS: No, FASMW has the assembler built-in so you could percieve some differences. PS2: Be sure to execute Make.bat at the very same location I did.
|
|||||||||||
16 Dec 2009, 16:39 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.