I upgraded from 7.1 to 7.2 last night, and it was pretty strange. When Yast2 finished looking at all the packages to upgrade, checked dependencies, etc. it told me that 710 packages needed updating (I had selected "Default plus Office"). When it actually starting the update (the screen w/ the progress bars), it said it was going to update 107 packages ??? After updating 79 packages, it said it was going to reboot. After the boot messages scrolled by, the screen went black, and there was a flashing cursor in the upper left corner of the screen. I had to push "reset" to get anywhere. Then yast2 acted like it was starting all over again. It then noted that it had "found a broken update", and "should we continue with this update". I said Yes, and once again it updated 79 packages from CD1 and wanted to reboot. The same thing happened - black screen. This time when I restarted and it found the "broken update", I answered No to the question of continuing w/ that update. This time, it said it was going to update 608 packages. Then, at the top of the update screen (w/ progress bars) it first indicated that it was going to update 646 packages. Shortly thereafter, the number changed to 641. That's what it stayed with, and it eventually updated 641 packages. The reboot after CD1 worked fine this time. Needless to say, I wasn't feeling very confident at this point. But after logging in as root, I started KDE, and it came up OK (seemed very slow though). System sounds still worked which made me feel a little better, but I had problems w/ some other stuff. 1. jscalibrator: after the update, this was no longer installed. I re-installed it, but it can't find /dev/js0 or /dev/input/js0. jstest finds /dev/js0 with no problem.???? 2. In the KDE control center, I wanted to see if my printer was still set up. So I went to "Hardware / Printer" and Yast2 started up. First it told me there was a conflict between cups and lprold. So I got rid of lprold. Yast2 correctly identified my printer (HP 712c), but when I tried to print a test page, it said it could not print because it couldn't find /bin/lpr. I don't know anything about cups - could anyone shed a little light on this for me? After all the update nonsense, it was pretty late (early rather....) so I didn't have much time to check much else out. If I find too many problems, I will probably just do a clean install. But I haven't given up on the update just yet........:-) TIA, Mike ------------------------------------------------------------------------- Cleary_Mike@emc.com ------------------------------------------------------------------------- "We are born wet, naked and hungry......then things get worse."