🚀 go-pugleaf

S.D.C. <gempac@hotmaildeletethis.com> wrote in message
358c0c0c.57741047@news.magmacom.com...
>
>At last, one person in this group with intelligence!!

Heh... I'm probably the least trained (on NT) person in this newsgroup.  I
like operating systems in general, but am not an NT admin, just a humble
(and sometimes frustrated) workstation user.

OK, point by point....

>>S.D.C. <gempac@hotmaildeletethis.com> wrote in message
>>>Why NT is not a true client-server (aka real NOS)

>>>- real NOS's don't use a GUI
I'm comfortable without the GUI, so for me this is mainly an matter of
preference.  The GUI requires more resources which affects performance,
true.


>>>- cursor animations, wav files
Cutesy stuff like this is fine for home hobbiests who like it.  I turn it
off, easy to do.


>>>- trash/garbage bins that don't even support network wide activities
I usually turn off the trash can, too.  If I delete it, I want it off the
disk, usually.


>>>- requires constant 'babying' because of memory leaks
MS could do better here. Some memory leaks are caused by other vendor's
code, however.


>>>- mediocre diagnostic tools
Task manager and Performance Monitor (in the Administrative Tools group)
have many options to monitor CPU, memory, and disk.  What is lacking?  How
could they be improved?


>>>- must be defragged
NTFS could be improved, yes.  At least with NT 5.0, Microsoft will stop
claiming that NTFS doesn't need defragging, since a defrag utility will be
included.  BTW, Novell doesn't need defragging?


>>>- cannot shut off GUI to save on resources
I've read that this is easily done.  It's a matter of renaming files, and
rebooting.  I don't know which files.  I haven't done it, or wanted to.


>>>- an inefficient and easily corruptible registry (need I say more?)
Yep.  When installing applications, individual *.ini files are a better way
to go -- better protection against bad installs, easier to tailor, less
bulky.


>>>- Requires IE4 to be installed just to install its own applications
Point taken about IE4.  Although I use it at home, tacking (oops,
"integrating") this bug collection into NT has not helped Microsoft's claims
that NT Server is "robust, mission-critical, enterprise-ready, etc....).
This joke is reminiscent of SP2, but as NT gets used in more
mission-critical applications, buggy sloppy code gets less and less
funny......  MS should improve their quality control.


>- The inability to recover data without resorting to tape is a life
>saver in a Net Admins job!
>
>- The GUI uses valuable memory and slows performance significantly.
>Ditto for the animations.
>
>- A fragmented NTFS volume....does the same (above)
>
>- Diagnostic tools?  Ever look at what MS gives you with Exchange
>Server.  Isinteg, edbutil are nearly completely useless!  The only
>fail safe utility (xmerge) wasn't even written by Microsoft and fails
>to backup all the Exchange user information.  Absolutely shameful!!
>Microsoft should be sued for this blatant disregard for it's clients.
>
>Opinions and preferences?  Hardly...more like simple facts.
>

I basically agree these are facts, but don't conclude they prevent NT from
being used as a NOS.  Some of them do increase resource requirements and
slow performance, significant concerns.


>>>- Require nearly twice as many servers as Novell or Unix (Linux) to do
>>>the same job (a well documented fact)
>>>- Does not support multi-processors as well as other NOS's.
>>>- Uses RAM and disk space very inefficiently
>>
>>These are legitimate problems with NT.


>I neglected to mention one of Microsoft's bigger lies.  Little or no
>scalability and it's inconsistent at best.

MS ethics aside, there is opportunity for improvement here, true.  NT 4.0 is
not efficient and its performance suffers relative to other offerings on the
market.

There is some reason to hope for better performance from NT 5.0.  We will
see......

Steve Shaw