In my case, I simply changed the boot option name, but QGRUBEditor changed the Root from (hd2,0) to (hd0,0), this is show in the edit entry dialog but it's easily overlooked since you are not messing with that field.
Basically, it appears that when you edit a boot option, QGRUBEditor reset the Root to hd0,n instead of reading the field from the actual entry. So if you have the /boot partition on a different primary partition/HD it will break the boot process.
I'm sorry I cannot be more precise, but I re-organized my HD so I cannot duplicate it again and go step-by step.
If I'm to fix the bug, I'd double check that when the edit dialog comes up, it populates the fields using actual entries from menu.lst and does not use any other hard-coded default.
In my case, I simply changed the boot option name, but QGRUBEditor changed the Root from (hd2,0) to (hd0,0), this is show in the edit entry dialog but it's easily overlooked since you are not messing with that field.
Basically, it appears that when you edit a boot option, QGRUBEditor reset the Root to hd0,n instead of reading the field from the actual entry. So if you have the /boot partition on a different primary partition/HD it will break the boot process.
I'm sorry I cannot be more precise, but I re-organized my HD so I cannot duplicate it again and go step-by step.
If I'm to fix the bug, I'd double check that when the edit dialog comes up, it populates the fields using actual entries from menu.lst and does not use any other hard-coded default.