OK, this is what comes of writing threads from memory...
My disk layout is as follows:
DISK0 (IDE), partitions E:, F:
DISK1 (SATA), partitions C:, D:
DISK0 is connected to IDE channel 0 (or 1 - whichever is the first one)
DISK1 is connected to SATA channel 0 (or 1 - whichever is the first one)
Following tests, I found the following (with only one instance of the wubi folder anywhere on any drive):
Copying \wubi to e: results in find --setroot failing
Copying \wubi to f: results in find --setroot failing
Copying \wubi to d: results in a proper boot and install.
The wubi folder I am using is a complete Ubuntu Feisty 7.04 install, patched up to last night, with NVidia 755 proprietary drivers installed and working, with a working implemetation of Beryl, with a 6Gb primary image file.
At boot, the find --setroot finds the /wubi/linux folder on hd(0,1)
And for completeness, here's fdisk-l when booted into Ubuntu (which sees both disks...):
Code:
Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 12210 98076793+ 7 HPFS/NTFS
/dev/sda2 12211 24321 97281607+ 7 HPFS/NTFS
Disk /dev/sdb: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 2550 20482843+ 7 HPFS/NTFS
/dev/sdb2 2551 19929 139596817+ 7 HPFS/NTFS
I didn't bother trying c:, I figure it'll work OK.
Bookmarks