Re: X86 assembler by Sankarraj
Sankarraj
Wed Mar 19 04:08:01 PDT 2008
I firstly thank you. (built .obj file)
I wanted to build the bsec.img file for exfat file system. In the build.bat
file these lines are mentioned
@REM It relies on a 16-bit assembler and linker. As well, it executes a
debug.com
@REM script at the end to extract the boot sector text area from the resultant
@REM COM file. Since the boot sector code runs in a loader-less
environment, the
@REM better part of the COM file is of no use to us.
@REM
@REM ** NOTE: the debug.com script extracts just the text area of the boot
sector
@REM and doesn't include the BIOS parameter block (BPB) area. This is
because
@REM the BPB created by the format operation is used instead and an offset
@REM (62d/0x3E) is applied to the boot sector code before it's written into
@REM the boot sector.
@REM
@ECHO OFF
ml /Zm /Flbsect.lst /c bsect.asm
link bsect.obj,bsect.com,,,
debug bsect.com < getbsect.scr
I could able to build bsect.obj and bsect.lst. While linking with the above
batch file "bsect.obj,bsect.com,,,", i got linker error file not found.
So i deleted the bsect.com,,, and tried to link it with link bsect.obj
alone. I am getting the error bsect.obj : "fatal error LNK1190: invalid
fixup found, type 0x0001". I searched and tried to fix it. Could you tell me
where i am wrong?
I wanted to make Exfat file system as wince bootable...
"AndreasSander1@gmx.net" wrote:
> On 19 Mrz., 08:02, "Luca Calligaris"
> <anonym...@discussions.microsoft.com> wrote:
> > masm is a 32 bit assembler but there are directive to write 'dos' code (for
> > example .model tiny);
> > then you can use the prefixes address size (0x67) or operand size (0x66) to
> > override the default.
> > google for 'masm reference guide'
>
> Luca,
>
> The bootloader must swich from real mode to protected mode. So you
> need a mix of 16 bit code and 32 bit code. I never succeeded to mix
> this in one file. Do you have a small example?
>
> Andreas
>