TH> calls, then write it to a file such as "BOOT.COM"
Sorry, that won't work.
Then it will assume COM file, assume base offset 0100h,
and most of the variables will be *really* fucked up...
Bootrecords work with base offset (origin, .org) 7C00h,
therefore all pointers to variables will differ:
0100 - 7C00 = -7B00
You will have to deal with that diffrence if you program
bootsectors, and even more if you disassemble them.
I used a 0EAh jump in my bootsector to fix up the base
offset when loading the "real" bootsector (the first one
just displays logo and load the next sector)
How to work around this while disassembling? Well, looks
like Sourcer 5.x got some sort of feature for this (it
made one hell of a job disassembling ROM chips with org
0 anyway)
 TH> That depends on the maker. The boot record is loaded into
 TH> RAM, but i
 TH> don't know where. It doesn't get used for very long.
Realy, I think you are a bit confused. You don't seem to differ
BIOS chip from bootrecords (MBR/bootsector)
[peter]
--- FMail 1.02
---------------