* Mike Grello (mgrello@sc.rr.com) [030427 17:48]: ->Ben, -> ->I also have Mandrake, and have never had the hw scan eat my mouse. Mandrake ->hw scan has an option when it runs to "butt out". This is a good compromise. -> ->i.e. ->(paraphrased) ->I see your mouse seems to have changed, should I: ->1. Try to identify your new mouse (in real time, using the same rules that I ->used to identify it correctly the first time) ->2. Kill Your mouse ->3. You tell me what mouse you use ->4. Butt out, the world is not perfect, change nothing (note if you had a power ->failure, or your dog tripped on the mouse cord, and all is well, choose this ->one, but 1. will work also, as I am using the same method I used to identfy ->the mouse 4 months ago when you installed). Well, under 8.1 I changed some hardware on my workstation in the office. It stopped on boot and said " You changed this..blah..blah.." and fired up YaST2 to configure it. I just told it to quit and the boot continued without any other problems. I haven't changed anything at work since and on the homefront I just rebuild my box with a ton of new hardware the week before 8.2 hit...so I just backuped everything and did a fresh install. So I don't quite know how 8.2 handles it because I've only had it "detect" new hardware on 8.1. *shrug* I wasn't advocating hwscan or anything like that. I've been using SuSE long enough and many kinds of hardware ..I don't need an autodetect but some do. I hope SuSE gets the problems ya'll are having fixed. Please..everyone who's having issues send email to feedback@suse.com because 9.9 out 10 SuSE employee's DO NOT subscribe to this list and won't hear your cries. Let them know the problems your having and let them fix them. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.