Hello -- Well, I did something too early in the morning (read: stupid).... There is a simple solution, but I can't find it. Can anyone point me the right way? I upgraded MD 2.2.17 to 2.2.19 on-line -- but I was careless, and did the upgrade as a user, not as root. The upgrade took, sort of.... Here are the parameters: 1. Upgraded alsa, kernel, kernel-doc, kernel-headers (and reiserfs, but it's not the problem) 2. I have Win4Lin installed. 3. Booting into Win4Lin kernel, finds 2.2.17, but without support for vfat, hpfs, supermount, lockdsvc, sound, midi and kppp. 4. Rebooted as root (single user), ran rpm -Uvh -- message that 2.2.19 already installed, but 2.2.17 boots. 5. Ran rpm -i --allfiles -- installed all files for 2.2.19, but 2.2.17 boots. 6. Checked lilo, there is a new kernel load point for 2.2.19, tried that but the kernel is not correctly compressed (?), and the system halts. 7. Tried all lilo load points, all show system halts, except for Win4Lin kernel (still showing symptoms of (3) above. 8. I can mount the CD under root only, and have the full (purchased) set of MD 7.2 distribution disks. I am worried that if I unistall the kernels as user (where I loaded 2.2.19 in the first place) that I will trash the system. However, I should be able to fix this problem with rpm from root. One option is to force install the 2.2.17 kernels from the CDs as root, but I don't know its effects either. Stuck -- any advice would be very much appreciated -- there should be a simple or at least straightforward solution to this.s Thank you! - Andy Lazarewicz
