[haiku-development] Re: Haiku R1/alpha decisions

my bad.lemme explain:

made a new image (qcow) with qemu.i think 250mb.
used haiku to format with driveUtil.formats fine, show as 250mb drive.
do the same on a hard disk attached as emu disk with -hdb=/dev/yyy and the size is misreported.(2TB on a 112GB drive as i recall...)
Not only that, makebootable, when run from within Haiku at this point, does work on both.
[zero offset for emu drive, non-zero for actual drive.you have to give makebootable the partition number on the phys. disk, as trying it normally hangs the process.(or either leave the disk still unbootable, i forget its been over a few weeks.)] 

during this process you must use:
makebootable /dev/ata/0/disk/<partnum> (pulled from DiskUtil)for the phys. disk to be 'made' bootable, else returns the offset of zero, but wont work.
you cant 'makebootable' the phys. disk as a whole drive, nor can you 'format' it that way.it has to be done as a partition.this is what haiku already does if you use a cleared hard disk thru qemu and try to format it or 'make' it 'BEOS'. 

the emu disk does not have this limitation.
NOTE: copying the FS over is not necessary to reproduce this error, however it still occurs after a full copy with 'cp -R / <destination>'. 

However, the only BOOTABLE volume is the emulated one.(the file you made)

hence the bug.
-----
Stephan Assmus wrote:

richard jasmin <jasminr@xxxxxxxxxxx> wrote:
'Either you use a version of BeOS to do the setup with DriveSetup or mkbfs or you use Haiku itself with the Installer or DriveSetup. Once you've created and initialized the target partition you can mount the image (using tools like Mount Image <http://bebits.com/app/3576> or through the Terminal) and copy over all the files. If you are under Haiku, you can just as well use the Installer to make a duplicate of your currently booted installation.' 

no.try again.doesn't work.formats okay.not bootable.
'If you for example copy such an image directly to a USB drive starting from 0, overwriting the MBR (destoying all partitions already there), then this will boot.'
like the dd command or the russian software that does this? dont think so, tried and failed.
' To make sure a partition boot record is there and it contains the right partition offset, you can use the tool "makebootable". Makebootable will do both, write the partition boot code to the beginning of the partition and detect and write the partition offset to where it is needed. You can use the makebootable from BeOS if you have a BeOS installation that has access to the partition in question.' 

not quite.its SUPPOSED to do this.it doesn't.
ive used VBox and qemu, no luck.
If you boot a BeOS in emulation and point it to the partition, are you sure the harddrive is mapped completely, or is the *partition* by any chance mapped as the harddrive in the emulation? I think you will have to get more specific in describing what you did. At least I have a hard time deciphering your description. 

Best regards,
-Stephan

Other related posts: