SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Fortunately, I do know where windows is installed, /dev/sda1, with the system reserved partition on /dev/sda2. Perhaps had you read my posts, you would have seen that. I do know why I would change the lilo.conf to agree with yours; is it because the label is different, or that they point to different partitions? Anyway, thanks for looking, wish it was helpful.
problem could be the BIOS device numbering at boot time. Maybe Windows remembers the numbering from when it was installed, or it has certain undocumented expectations. This theory can be tested by installing LILO in /dev/sda and changing the boot device in the BIOS.
Btw, are you sure you need the "change-rules reset"?
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Determine the partition Windoes is installed on using parted. Then point LILO to the bootable partition.
Win7 normal install tends to create 3 partitions. A rescue partition (dev/sda1), a boot partition (dev/sda2) and a user partition (dev/sda3) Parted wil show what you have and which is marked bootable.
Thanks for the suggestions. First, I was able to save the \Users directory onto USB drive. Then installed Win 7 onto an NTFS partition on another drive. When bootmgr came up, I selected the second Windows 7 entry and the original Windows 7 came up. Whew. Never saw installing lilo breaking an existing Win 7 installation, been using linux since 1.2.8. Turns out the original Win7 install was, in fact, on /dev/sdb2.