When the LVPM alters menu.lst it puts the the original wubi install (with loop mounted code removed) into the automagic kernels list. This gives error 17 on default boot. This should be changed to pt the dedicated install into the automagic kernels list. I

[Kenny]

When the LVPM alters menu.lst it puts the the original wubi install (with loop mounted code removed) into the automagic kernels list. This gives error 17 on default boot. This should be changed to put the dedicated partition install into the automagic kernels list. This may seem trivial but it causes problems when the kernel is updated. I dont know if this has already been resolved by any updates

[Marc-André Turcotte (matmat07)]

For those who it will happen and don't know how to go back on th right partition, you will have to from grub) pres the e button on the line you wish to boot from, and e again to edit each other line so it points to where your installation is, exemple: (hd0,2) instead of ()ubuntu/...

I also tried to upgrade to grub 2 and it detected correctly my partitions, bu I still don't know what will happen afte a kernel upgrade.

For you question about updates, there was no since 2008 summer and I got LVPM after that with the same issue you have, so I don't think it was solved

[Kenny (kennywardle)]

Thanks for the follow up

regards

> Date: Tue, 7 Apr 2009 14:27:29 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 302943] Re: When the LVPM alters menu.lst it puts the the original wubi install (with loop mounted code removed) into the automagic kernels list. This gives error 17 on default boot. This should be changed to pt the dedicated install into the automagic kernels list. I
>
> For those who it will happen and don't know how to go back on th right
> partition, you will have to from grub) pres the e button on the line you
> wish to boot from, and e again to edit each other line so it points to
> where your installation is, exemple: (hd0,2) instead of ()ubuntu/...
>
> I also tried to upgrade to grub 2 and it detected correctly my
> partitions, bu I still don't know what will happen afte a kernel
> upgrade.
>
> For you question about updates, there was no since 2008 summer and I got
> LVPM after that with the same issue you have, so I don't think it was
> solved
>
> --
> When the LVPM alters menu.lst it puts the the original wubi install (with loop mounted code removed) into the automagic kernels list. This gives error 17 on default boot. This should be changed to pt the dedicated install into the automagic kernels list. I
> https://bugs.launchpad.net/bugs/302943
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Loopmounted Virtual Partition Manager: New
>
> Bug description:
> When the LVPM alters menu.lst it puts the the original wubi install (with loop mounted code removed) into the automagic kernels list. This gives error 17 on default boot. This should be changed to put the dedicated partition install into the automagic kernels list. This may seem trivial but it causes problems when the kernel is updated. I dont know if this has already been resolved by any updates

_________________________________________________________________
View photos of singles in your area Click Here
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fdating%2Eninemsn%2Ecom%2Eau%2Fchannel%2Findex%2Easpx%3Ftrackingid%3D1046247&_t=773166080&_r=Hotmail_Endtext&_m=EXT