banderlog wrote:wrd wrote:.. I thought these machines only understood the fat system, but the fat system cannot be the size of 60 Gb and the tools I use always want to reformat the whole disk not just a part of it.
/wrd
BIOS just can copy the so-called "Stage1 boot loader" from the first sector of boot device to memory addresses from 0x7C00 to 0x7DFF. Then, the contorol is given to Stage1 boot loader.
What this effectively means: either you need a filesystem that has a boot-sector as the first block (usually the first three bytes being a machine code jump to the actual boot code), or you need a master boot record (which usually just jumps to the individual boot sector).
In other words: you need a boot manager or a bootable operating system on the drive. As suggested, try LiLo/GRUB, because they are free.
banderlog wrote:So all the stuff about loading operation system lies on that loader that you use. So use the proper loader and OS ))) or just another disk operation tools, which can regullary format any drive. I can recommend Acronis Disk Director, Linux cfdisk or Paragon Partition Magic.
Not really. Usually the boot code is not related to the operating system (though some have their own boot code, like DOS). Also the boot code is not related to any of the tools you mentioned. If you, for example, edit your partition table by cfdisk, you're not changing the boot code, but just the partition table. This also explains, why programs like
Partition Magic and
Boot Magic are unrelated and can be used simultaneously without problems, or even without worrying about intersections, from the programmer's point of view.