There isn't anything what can not be red in any advocacy group, just can't
resist joining in......
Your mileage seems to be different from mine, I have NT servers with
applications running a lot longer than 2 weeks. From my perspective your
claim is totally false. Not to mention the fact that using the minimum
amount of required memory for NT isn't a wise decision to start with. On
16MB memory even Linux has hard time running, under the same circumstances
as NT. That is, start up and X-Windows on the Linux box and you'll know what
I mean.
Otto
----- Original Message -----
From: "Paul Surgeon" <[EMAIL PROTECTED]>
To: "Noonan, Wesley" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, February 12, 2001 2:33 PM
Subject: Re: Squid and Samba
> ----- Original Message -----
> From: "Noonan, Wesley" <[EMAIL PROTECTED]>
> To: "'Paul Surgeon'" <[EMAIL PROTECTED]>; "Noonan, Wesley"
> <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, February 12, 2001 8:56 PM
> Subject: RE: Squid and Samba
>
> > As for the culprits of blue screens, since 90% of them
> > are drivers, and Microsoft doesn't make drivers, who is really
responsible
> > here?
>
> Hmmm ... I was under the impression that what comes out of the MS box was
> written by MS and is CERTIFIED by MS?!
> Who actually writes the drivers that come out of the box and why do
> Microsoft certify them if they are buggy?
>
> I can take a brand spanking new version of Windows out of the box, install
> it and boot it and it will crash within 2 weeks even if I don't use it at
> all.
> I have added no extra non-MS certified software and haven't run anything
on
> it during that time.
>
> I can do the same with a HP-Unix, Linux, Solaris box and after idling for
2
> weeks they are all ready to get some work done.
>
> > Dare I say, it might not be the software that is the problem.
>
> No, not if I notice that same thing on about the 10 different systems I
have
> used.
> Different processors, different make of memory, different motherboards,
> differnet hard drives, etc, etc, etc.
>
> > Not because it is really bad software but because it is flawed in both
> > design and stability.
> >
> > Rarely have I found the design and stability to be the result of the
> > software. For more often, it is the result of the admin.
>
> Ummm ... yes you are right - I am a crap admin.
> I installed the OS and it crashes so I got a Microsoft Certified Whatever
to
> do the install for me and Windows still crashes.
> Guess MS don't know how to get their techies to do the magic stuff either.
>
> The best they can do is delay the crashes by installing more RAM at my
> expense which is a solution I do not accept when I am paying for a
solution
> that works!
>
> I once learnt something (one of the few things I have learnt) in Ansi C
and
> C++ programming and it's this :
> If you allocate memory, point a pointer to it and forget to de-allocate
the
> memory before destroying the pointer you get something called a "Memory
> Leak".
> Windows (out of the box) obviously suffers from this because after 1 week
on
> 16 MB of RAM it is a slow as a dog and is thrashing the disk to pieces
> because it has lost nearly all of the 16MB.
>
> > This should really go to private mail...
>
> I though this was a public mailing list?
> You are right ... I should have discussed this in an MS mailing list.
>
> Regards
> Paul Surgeon
>
>
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
