Oh, also, when I last closed Windows, it was hang on Windows closing
screen, so I did disconnect and reconnected the computer. So, sure
enough, the FAT32 partition was not cleanly unmounted.
But I would expect it to be added to the menu anyway.
Anyway, I am not so sure of what I should expect now.
I tried this:
paul@ArcturusK:~$ sudo mv /boot/grub/menu.lst /boot/grub/menu.lst.old
paul@ArcturusK:~$ sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file...
Could not find /boot/grub/menu.lst file. Would you
like /boot/grub/menu.lst generated for you? (y/N) y
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-2.6.12-8-386
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done
paul@ArcturusK:~$
Is update-grub supposed to see a Windows partition and automagically
add an option to boot it?
Oh, also, when I last closed Windows, it was hang on Windows closing
screen, so I did disconnect and reconnected the computer. So, sure
enough, the FAT32 partition was not cleanly unmounted.
But I would expect it to be added to the menu anyway.
Anyway, I am not so sure of what I should expect now. menu.lst. old
I tried this:
paul@ArcturusK:~$ sudo mv /boot/grub/menu.lst /boot/grub/
paul@ArcturusK:~$ sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub .
Testing for an existing GRUB menu.list file...
Could not find /boot/grub/menu.lst file. Would you 2.6.12- 8-386 +.bin
like /boot/grub/menu.lst generated for you? (y/N) y
Searching for splash image... none found, skipping...
Found kernel: /boot/vmlinuz-
Found kernel: /boot/memtest86
Updating /boot/grub/menu.lst ... done
paul@ArcturusK:~$
Is update-grub supposed to see a Windows partition and automagically
add an option to boot it?