Date: Sun, 13 Feb 2005 08:53:23 +0100 From: Anthony Atkielski <atkielski.anthony@wanadoo.fr> To: freebsd-questions@freebsd.org Subject: Re: Freebsd vs. linux Message-ID: <308024811.20050213085323@wanadoo.fr> In-Reply-To: <20050213035851.GV8619@alzatex.com> References: <200502112313.28082.hindrich@worldchat.com> <823196404.20050212105644@wanadoo.fr> <420DE422.3020102@wanadoo.es> <1546398643.20050212123202@wanadoo.fr> <420E0164.7090300@wanadoo.es> <27964692.20050212160046@wanadoo.fr> <20050213035851.GV8619@alzatex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Loren M. Lang writes: > That's not true in my expeirence, I still see the blue screen > occassionally on both WinNT 4.0 and 2K systems. Then you have bad device drivers, or you are running software with OS privileges that contains bugs. > Most of the time though the 2K machine just reboots without warning. Look for common characteristics of the situations in which you observe a reboot (especially particular programs running, or particular hardware devices in use). > Also, my brother is constantly telling my how he fixed his WinXP > machine by rebooting it. That may not be a blue screen, but it's still > not good. It's a matter of user education; it has nothing to do with the OS. I haven't used systmatic rebooting to fix problems since the 16-bit Windows 3.x (the old Windows 9x family of operating systems could get stuck that way, but I went directly to NT myself and never bothered to waste my time with Windows 95). -- Anthony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?308024811.20050213085323>