[quote author=jcd link=topic=3546.msg20875#msg20875 date=1199894046]Is this a typo in your post or are you really missing a space between "78785b3c-875f-4e35-8529-09f0e63d96cc" and "ro" in your menu.lst?[/quote]

Yes, it was an error in my menu.lst. I fixed it, rebooted into the 0710 partition, got an error on my LCD monitor while Kubuntu booted that signal frequency is out of range (H: 64.2Khz / V: 60.2Hz). Again it finished booting into only initrd.

The existing MBR I installed with my previous (FAT32 sda3, a la USB Flash) process to point at that old 0704 menu.lst with 0710 added as an option, and I hadn't edited that menu.lst to fix the bug (thinking, like you, that it wasn't in the critical path). I fixed the sda1 menu.lst, booted into it, and now it works! 0710 loaded, and is now sitting at the AV Wizard Step 0. Thanks for all the help, mostly just correcting my boneheaded mistakes.

The net instructions I'm following now don't specify how to make the MBR point at the 0710 installer partition's menu.lst , even though that's the clean way to do this. If I have that MBR instruction, I'll revise and post this complete, tested process in the wiki.

The existing MBR I installed with my previous (FAT32 sda3, a la USB Flash) process to point at that old 0704 menu.lst with 0710 added as an option, and I hadn't edited that menu.lst to fix the bug (thinking, like you, that it wasn't in the critical path). I fixed the sda1 menu.lst, booted into it, and now it works! 0710 loaded, and is now sitting at the AV Wizard Step 0. Thanks for all the help, mostly just correcting my boneheaded mistakes.

The net instructions I'm following now don't specify how to make the MBR point at the 0710 installer partition's menu.lst , even though that's the clean way to do this. If I have that MBR instruction, I'll revise and post this complete, tested process in the wiki.

That's why I choose to have a common /boot partition mounted by all my linux installations on this system. This sda1 (/boot) partition hold the MBR and the GRUB menu.lst. From there it points to different / (root) partition depending on the system to boot. And I can modify the menu.lst from any linux version I boot.

The existing MBR I installed with my previous (FAT32 sda3, a la USB Flash) process to point at that old 0704 menu.lst with 0710 added as an option, and I hadn't edited that menu.lst to fix the bug (thinking, like you, that it wasn't in the critical path). I fixed the sda1 menu.lst, booted into it, and now it works! 0710 loaded, and is now sitting at the AV Wizard Step 0. Thanks for all the help, mostly just correcting my boneheaded mistakes.

The net instructions I'm following now don't specify how to make the MBR point at the 0710 installer partition's menu.lst , even though that's the clean way to do this. If I have that MBR instruction, I'll revise and post this complete, tested process in the wiki.

That's why I choose to have a common /boot partition mounted by all my linux installations on this system. This sda1 (/boot) partition hold the MBR and the GRUB menu.lst. From there it points to different / (root) partition depending on the system to boot. And I can modify the menu.lst from any linux version I boot.

I agree, for actual multiboot systems. But I multibooted this beta expecting it to multiboot only once or infrequently, after which I'd delete the 0704 boot partition. In any case, could you tell me the instructions for installing the MBR/grub/menu.lst in each of sda1 and sda3 , so I can complete these instructions for either scenario and add them to the wiki?

Not really sure where to post this. I am downloading the beta 3 right now and have downloaded the beta 2 previously. I have been downloading the torrent for a whole day and it looks like it will be another whole day before I have a completed ISO. I am wondering why you all aren't using zsynch for iso distribution. Zsync can be easily used to upgrade any Ubuntu derivative iso from the last iso to the new one. It's available in the Ubuntu repositories. Zsync compares the last release iso to the new one and downloads only the new bits and creates a verifiable iso that is identical to the original new iso in minutes. All you have to do is use the command zsyncmake in the directory of the new iso and it will in moments create a file with the same name and the iso.zsync extension. The zsynch file is then located on the server in the same folder as the new iso. The zsync file is only a few MB's. The end user downloads the zsynch file and places it in a folder with the old iso. Then from that directory commands zsynch "old iso" "zsync file" "address/new iso"

In minutes zsync figures the differences between the beta 2 and beta 3 iso's and downloads just the new bits, downloads them and recreates an exact copy of the new iso. The md5sums will be identical. zsync checks them at the beginning, all through the process on the fly and then again at the end of the process and produces a report. My main home distro is Klikit which is still in beta. We are using zsync for upgrading iso's from old to new with great success and less coasters overall. The downloads are a fraction of what they would be otherwise. Saving the end user many hours and the servers much bandwidth. Just an idea. It would be especially nice for those of us who a testing the beta's sequentially. Just a thought, thanks for your kind attention. Later... cos