I am using W95 privately on my box that has the old scanner and printer
(driver availability issue), W2K on my data-backup-box that has no screen
attached and "professionally" NT on my ofice laptop and PC.
W95 is a completely different issue so I am careful not to start too many
apps and do not use the scanner while having network traffic etc....
W2K and NT are really stable (my CPU is always on 100%), my taskbar is four
rows high so I can see all my apps. Of all the crashes I get 99% are Dr.
Watson or other application problems, the OS runs until some hardware fails
(I suspect my worn out hard disk on the laptop meanwhile). My
data-backup-box at home is running without screen and keyboard since I only
switch it on ... transfer file via network and occasionaly use it via
TightVNC (and to shut it off). I also used to have some VMWARE virtual
machines on these PCs which also ran very smoothly.
In the office we have some servers (NT 4.0 and W2K) which also host some VMs
(same OSs and XP). They run mostly unattended but I have made it an
about-weekly-task to reboot them all because it seems after some weeks they
tend to get strange network misbehaviours which do not appear when rebooted
regularly. The only machine that I do not reboot for months is our old AIX
server (which is rarely used).
It might be of interest to some: Since it is very hard to remember which PC
has which software version, where did I put those files on due to lack of
space here and so on... I put up some automated inventory of file structure
and registry backup for all PCs in the network (that I feel responsible
off).
It uses psexec, WinBatch and a combination of system and freeware tools so
that I have a historic record of most information (including all DLL
versions via DUPS and network settings) that allows me to find out what was
(!) on a PC some time (you know users saying "but last time I used it it
worked!" ..." When was that?" ... "Uh maybe two months ago"). It can turn
out to be quite a hassle to find out what actually caused the problems but
at least I do have information of past states to work on.
All information is collected onto 1 single machine where I have scripts to
search for file names, dll versions, disk free space and so on. In the last
months 2 PCs (MAXDATA) had a motherboard failure and at least I was able to
exactly know what I had lost.
In case anybody would be interested in these pieces of software let me know.
Regards
Armin Freiberg
> ----------
> From: The Fool[SMTP:[EMAIL PROTECTED]
...
> > From: William T Goodall <[EMAIL PROTECTED]>
...
> > >> " Mr. Gates acknowledged today that the company's error reporting
> > >> service indicated that 5 percent of all Windows-based computers now
> > >> crash more than twice each day."
...
> No, windows NT was always that way. People are just using NT descended
> code more now. NT never crashes.
>
> _______________________________________________
> http://www.mccmedia.com/mailman/listinfo/brin-l
>
_______________________________________________
http://www.mccmedia.com/mailman/listinfo/brin-l
