Page 3 of 3
Re: BootSector problem
Posted: Thu Jun 09, 2011 10:29 am
by opc0de
berkus wrote:You seem to be a little dissociative, so no thank you but no.
i don't know what is your problem ... can you make me a favour and ignore this thread you are to experienced for me...
Re: BootSector problem
Posted: Thu Jun 09, 2011 1:29 pm
by iocoder
Oh dear, you have erased partition table??????
Re: BootSector problem
Posted: Thu Jun 09, 2011 1:49 pm
by iocoder
opc0de: could you please send us the 512 binary image of your MBR and the 512 byte binary image of the original MBR??? I will edit your proggy MBR and add the partition table to it, then write it to sector 0 and your issue might be solved..
Re: BootSector problem
Posted: Thu Jun 09, 2011 2:02 pm
by opc0de
I have done it didn't knew that overwriting the partition table will stop the machine from booting since the actual MBR is restored in memory...Thanks all for your help and good luck with you projects.
Re: BootSector problem
Posted: Fri Jun 10, 2011 5:13 am
by iocoder
I have done it didn't knew that overwriting the partition table will stop the machine from booting since the actual MBR is restored in memory...
NTLDR needs to know how your computer is partitioned, so it loads sector 0 [MBR] to memory and expects that it contains the partition table.
Thanks all for your help and good luck with you projects.
You are welcome
Regards,
Mostafa Abd El-Aziz
Re: BootSector problem
Posted: Fri Jun 10, 2011 5:00 pm
by Brendan
Hi,
"org" is used by the assembler to calculate the offset of labels (withing whatever segment), and what segment you're using makes no difference. For example, if the code is loaded at 0x0123:0x4567 then the "org" would be "0x4567". If the code is loaded at 0x1000:0x0000 then "org" would 0x0000.
Cheers,
Brendan