OSDev.org

Hello, Giese

I've ever written to you, but it seems you couldn't
be reached via that mail address. So, I have to post
it here.

I've read your pm tutorial series. That's cool.
It's not only clear but also very profound. Many
many thanks to you.

Currently I meet some problems. That is:
   (pm12 is taken as an example.)

1) pm12 originally is compiled and linked into
   .com format. I modified the linker script and tried
   to output binary format, then I wrote a bootsector.asm
   for loading in the binary file(i.e. pm12.bin).
   But I can't make it even after trying many many times.

   a. How could I modify the initialization code of pm12a.asm
      to output a usable binary kernel?
   b. What's the critical difference there?
  
2) Within the linker script, the .text address of
   the output file--pm12.cof-- is 0x0100 .

   a. Is this address an absolute physical address or
      a relative address?
   b. What's on earth this address used for?
   c. finally pm12.cof is 'objcopyed' to binary format,
      Could that address(I mean, 0x0100) influence the
      loading address of that binary file? If so, how
      could the file in binary format store the additional
      information?

3) There're many labels within pm12a.asm, how do you set
   the segment address of them? I mean, if you want to
   get the physical address, how to do that?

Actually, I've thought of them and have tried
over and over again, still, I can't make it.
I really feel tired. Would you please give me a hand?

Any help would be sincerely appreciated!

ExVie  <[email protected]>

I think he follows the alt.os.development newsgroups if you need to contect him but here is a pointer to help you:-

The address that pm12a.asm is linked to must be where it is loaded into memory by the boot sector.

Therx

Thanks for your reply.

Then, why should the .text address of pm12a.o be consistent
with the loading address by boot sector?

ExVie