Jan 7, 2007. That's the day that I finally decided to take the plunge and install Suse 10.2 on a spare 60GB drive that I installed in my P4/2.4GHz 512MB ram system. The install went as smoothly as any OS that I had ever loaded. I should have known that was a bad omen. Feb 6, 2007 System is now able to recognize the DVD part of the CD/DVD burner. I have had ample time to examine Suse's new (to me) way of doing things like the Yast Update system that sucks big time because it takes so long. Smart is much better. Mar 13, 2007 Have yet to get mplayerplugin to work with Firefox on any of the 3 Suse 10.2 boxes that I have installed it on. A 4th test system with Fedora Core 6 works perfectly. Wine is much improved over what I had been using before the changeover, but kmail lost some functionality and it's address book system has been screwed over. Media devices mount by the volume info which renders any software invalid that expects to see a fixed mount point. Yes, someone here posted a link to a workaround but my question is: why in Hell did Suse allow this bastardized code to make it into production in the first place? It shouldn't take a rocket scientist to figure out that the system should provide static mount points for a device, not the &%$#@ volume info of the media in it. I am 2 months into Suse 10.2 and I still do not have a polished system running as well as my old Suse 9.1 that I ran for over 2 years. Yes, I think that Suse's potential is there or I wouldn't still be using it. I have tried Ubuntu, Knoppix, FC-6 and Suse 10.2 and it looks like Suse is the most polished. If I cannot get past some of the "ease of use" issues that it presents, though, I may be forced to abandon Suse 10.2 and use another distro until such time as Suse gets it's act together. Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org