On Sunday 13 January 2002 09:35 pm, Rafael Herrera wrote: ---------snipped old quotes---------------------

...

Once while in single user and once at a normal login I was able to view the output of SuSEconfig and noticed alot of gobbledygook (looked like a binary file viewed in a text editor) just before the lockup/reset. The last line printed before locking up is something about "susewm".

-----------snip-------------------------

Have you considered that you may be having hardware problems? Maybe your hard drive is failing and when you run suseconfig, it may be trying to access a part of your disk that is corrupted, initiating a sequence of events that leads to a freeze. Just a guess.

Its not out of the question although the whole box is less than 2 years old. I did use maxtors utilities to check 2 of my 3 hard disks and they reported ok. I'll try more in depth testing. right now I've got almost 12 hrs of uptime but worry what will happen the next time I run SuSEconfig thanks for the reply dh