Well, sometimes you get a blue screen message listing the
registers and sometimes things like IRQ_NOT_EQUAL (or some
such) and maybe some module (like emk101). However, many
times it locks up without error messages or you ones like
"error at someaddress in app xxyz", none of which help
much! It doesn't seem that you can troubleshoot windows
as you can with Linux/Unix/VMS. In addition most of the
sysadmins for Windows have the reboot mentality and really
don't dig into the problem.
On Mon, 9 Jun 2003 21:32:31 +0100
Tom Wesley <[EMAIL PROTECTED]> wrote:
On Monday 09 June 2003 21:29, brett holcomb wrote:
On Mon, 9 Jun 2003 21:27:07 +0100
Probably because Linux/Unix/VMS people don't accept that
an OS will crash regularly so they go looking for the
cause. Windows people have been conditioned to reboot,
reboot, reboot, then reinstall and accept that as
normal.
Besides with Windows you can't tell if it's the
hardware
or Windows <G>.
last time i will reply, honest,
I thought you could tell it was Windows causing the
problem because of the
boot screen?
--
Tom Wesley
Please encrypt personal replies if possible.
--
[EMAIL PROTECTED] mailing list
