boot0md: dual boot Windows 7 and Mac OSX from Win7 drive

[Azimutz]

Seems so. ...

Definitely is. I gave it another try and i can clearly see "boot1:/boot" before the spinning cursor.
I really only mentioned this because it seemed a boot0 thing; as i mentioned the debug build helps...
it's the first time i see any debug on boot0; boot1 also fails to compile with debug enabled.

If you are booting from this drive, then I guess boot0 will find boot1 on 2nd partition and continue with booting, but since GPT is not valid, maybe Chameleon stage 3 gets confused.

yep, your guess is right, just it fails from any drive.
You mean stage2 (/boot), right!?

Anyway, I guess you would not be able to boot anything from this drive, but if the issue here is in the stage 3, then this could be fixed to allow to boot from some other drive.
 

Super Grub does load a OS X, not sure which one though... will check again, got me curious now.
If you say it can be fixed on stage2, i believe i'm pretty noob at this stuff and
this falls on an area of the code i don't know that well.

boot0 fix from my previous post would deal with the  corruption of LBAs (GPT array LBA or partition start LBA), but only if those LBAs are out of the range for the current disk. This is just to avoid boot0 from stopping in case of errors and to allow it to continue with boot1 search on other partitons and disks.

I got it, but don't know how to test this specific scenario.

[dmazar]

You mean stage2 (/boot), right!?

stage2, yes. sorry.

boot0 fix from my previous post would deal with the  corruption of LBAs (GPT array LBA or partition start LBA), but only if those LBAs are out of the range for the current disk.

I got it, but don't know how to test this specific scenario.

I was using iBored to write large numbers to those LBAs. Was doing that from Windows, but had some problems with it. I got the impression that Windows or iBored is making some changes to GPT header also in the background and it get hard to make desired corruption. It would be ideal to boot in some os that does not understand GPT and use disk editor from there, I guess.

[Azimutz]

Well, i will get back to this from time to time; it's not a major fatality so...

About boot0work, think you already know my opinion; i'm using it and pretend to keep using

[Blackosx]

Quick update from me just to say I have been using boot0workV2 for a month now with no issues whatsoever. The other day I made dmazar's amends and have not seen anything untoward. I'll keep running this version from now on and report if I ever come across any issues (which I don't expect), though I won't be corrupting any GPT tables here  .

[Azimutz]

... though I won't be corrupting any GPT tables here  .

why not?1... it's so funny
yeah, my only doubt is RAID; i don't expect problems with it, but it would be nice having someone testing it.

[Blackosx]

why not?1... it's so funny

Lol.. maybe one day if I get bored. 

I agree to the need to having dmazar's latest amends tested by a RAID user. Maybe we can create a topic somewhere for RAID users to test and give feedback?

[dmazar]

... though I won't be corrupting any GPT tables here  .

why not?1... it's so funny

People are eating bugs, making tattoos all over the body, having S/M sex, joining political parties and all kind of stuff ... but corrupting GPT tables ... that's weird man. 

[Azimutz]

People are eating bugs, making tattoos all over the body, having S/M sex, joining political parties and all kind of stuff ... but corrupting GPT tables ... that's weird man. 

That's why i'm leaving it alone for now before it turns to some weird obsession...

Lol.. maybe one day if I get bored. 

I agree to the need to having dmazar's latest amends tested by a RAID user. Maybe we can create a topic somewhere for RAID users to test and give feedback?
 

No more topics, please someone with a RAID volume will eventually stumble with this one, or be forced to
I meant to set up one, but i can't find a WD5000AACS (500GB caviar green, 16MB cache) anymore on the stores
to pair with the one i have and i ain't gonna pay 75€ for one over the net, when the new 1TB (32MB cache) ones
are cheaper in the store (around 60€). Also, the new 500GB ones don't even use 16MB cache anymore.
Just need to get my budget a tad fatter

[Blackosx]

Quick update from me just to say I have been using boot0workV2 for a month now with no issues whatsoever. The other day I made dmazar's amends and have not seen anything untoward. I'll keep running this version from now on and report if I ever come across any issues (which I don't expect), though I won't be corrupting any GPT tables here  .

I've applied these changes to the boot0md code in the trunk.

[presley]

Source attached.
- should be put in i386/boot0/ of Chameleon source tree and compiled with the rest of it because of config options

Compiled boot0md attached.

Install from terminal:
- determine windows disk with
diskutil list
- install with
sudo fdisk440  -f boot0md -u /dev/rdiskX

Hi,

I can't make to boot W7...
-Source files must be puted in i386/boot0/ of Chameleon source tree and compiled... I have puted files boot0md.s and Makefile, but how to compile it?
-MBR has updated with boot0md.

My configuration now:

Disk0: MBR (boot0md), P1=Win7 (NTFS, bootable, active)
Disk1: P1=MacOSX 10.7.2

BIOS boots from Disk0 with Win7:
-boot shows Chameleon menu with MacOSX and Win7:
  if select MocOSX it boot
  if select W7 - don't boot (BOOTMGR IS MISSING)
BIOS boots from Disk1 with MacOSX:
 the same situation.

If removing Disk1 with MacOSX - Windows7 boot.
I think it happens because chameleon not compiled.

[Blackosx]

if select W7 - don't boot (BOOTMGR IS MISSING)

How did you install boot0md?
Did you use fdisk440?

[presley]

Yes, I've used
sudo fdisk440  -f boot0md -u /dev/rdisk0 (Disk with Win7)

Mode Edit: Quote removed as there's no need to quote from a post directly above.

[Blackosx]

Have you a System Reserved partition? if so you need to select from that Chameleon to boot Windows 7.

I think it happens because chameleon not compiled.

It must be compiled as:
1) You can boot in to Chameleon from disk0, then in turn boot OS X on disk1.
2) You can boot Windows from disk0 when you disconnect disk1 (which is default behaviour for boot0md if it can't find a stage 1 booter).

[dmazar]

Presley, I would like to help, but do not know how.
Since you can boot OSX that means you are using Chameleon. This means that boot0 is done it's job (finding and starting Chameleon). This also means that you have it compiled.

As Blackosx said, maybe you are not choosing System reserved partition if you have one?

[presley]

I dont know why, but I've removed and reinstalled chameleon to newest version 2.1, puted mod files again and now Windows boot from Reserved partition 
Thanks Dmazar for great job!