From: Newt <gen...@gm...> - 2009-10-12 20:31:22
|
Hello, Things are definitely getting better - not that they were bad before - but they're even better now!! Here's my list of little notes: During Install: -Lilo installs correctly to bootsector with VL and WinXP (good job!!) (but problems, see below) -OSX bootable partition is not detected -osprober and fdisk-l identify the partition as 'unknown' -parted-l identify the partition as 'hsf+' -I manually added an 'other' option to lilo.conf and it works correctly -ISO 'Search Again' problem persists -try: next, next, back, search again, search again -Cannot find ISO after that -Partition selection shows ntfs drives as 'fuseblk' (maybe by design?) After Install: -Lilo cannot boot the WindowsXP boot entry -just sits at lilo message saying 'booting WindowsXP' with a cursor below -KDM starts/runs correctly with proprietary nvidia driver (good job!!) -the backdrop for KDM leaves black sides on widescreen 1400x900 -Analog clock issue will persist for small resolution screens (1024x768 and below) -the clock will be out of viewable range at these lower resolution screens -KDE taskbar/panel could be configured as 'centered' and would look better at resolutions higher than 1280. As it stands, the panel is left-aligned and anything higher than 1280 wide leaves a gap on the right-hand side of the panel. I think a "centered" config is more aesthetically pleasing (opinion of course). -vburn-iso does not start and has no icon -opera, wpa_gui, and browser have no icons -I noticed that opera.desktop points to wrong location for icon (hicolor) -Icons added to desktop from KDE menu show up different than existing icons. -maybe they are configured in 'desktop view' because they appear over-top of existing icons and have the fly-out options. Plus, they can't be drag/drop into trash with this configuration. Most of these points are pretty minor and don't actually affect functionality. The only major item on my list is the fact that WinXP would not start from the lilo menu option. During installation, I quickly glanced at the lilo entry and it seemed correct but I wasn't paying a lot of attention to the winxp lilo entry (I'll have to have another look to confirm). It very well could be my boot setup. I'm trying to leave the sda mbr alone (sda is my first bootable device), as well as create the ability to boot directly from ISO, so I'm using various techniques to accomplish this. However, my feeling is that once LILO actually boots, my system should effectively be ignorant to the complex nature of my boot scenario (perhaps not??). sda_mbr: windows bootloader (boot.ini) with following options: -windowsxp (works) -osx (chainloads to sdc) (works) -grub4dos (boots grldr at sda1 root partition) (works) grub4dos with following options: -vector iso (located at sda1 root partition) (works) -lilo on hda1 (works) VectorLilo (hda1) options: -windowsxp (does not work) -vector-cli (untested, but likely works) -vector (works) -osx (works) Cheers, newt |