Date: Mon, 14 Feb 2005 11:42:41 -0600 From: Eric Kjeldergaard <kjelderg@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Freebsd vs. linux Message-ID: <d9175cad0502140942a7244b2@mail.gmail.com> In-Reply-To: <308024811.20050213085323@wanadoo.fr> 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> <308024811.20050213085323@wanadoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Feb 2005 08:53:23 +0100, Anthony Atkielski <atkielski.anthony@wanadoo.fr> wrote: > 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. > I have to go with Loren, the BSOD certainly still comes up with NT/2k/(especially)XP systems. I have had systems that would Blue Screen about once a week. And, before someone (read Anthony) comes out saying "You're using bum drivers or flaky apps" I definitely was. I was, however, using ONLY things coming from the Windows Install CDs or the Windows updates system which means that it's the OS itself that is at fault. It's likely not representative of a lot of cases, but just a little reminder that people shouldn't make such definitive conclusions (read assumptions) before hearing the facts. -- If I write a signature, my emails will appear more personalised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9175cad0502140942a7244b2>