Keithsha,
Please stop flicking these silly little tidbits on "how to crash a NW server" because a MSFTer should learn not to throw stones when they live in a glass NT house. If you want to bring a production NT server out of production - just make a configuration change of any kind! "Its time for a reboot! Just apply the latest SP4 patch to NT and its time for a system crash. Just let NT sit long enough on its own and its time for a reboot.
NW and your SYS volume being full and freezing the server, one must be pretty stupid to have this error occur (oops, I guess you must have accomplished it since you knew all about it). That would be like knowing your crossing a long desert highway and going on an empty tank of gas.
NW servers that get abends can trap them and continue operating. NT server that crash - CRASH!
BTW - nowhere did I ever say that a protocol constitutes an OS. As for your "NetWareOS remains the same" statement...there is nothing that can be said to change your statement - MSFT has brainwashed you way too deeply on that. So you keep living your little lie.
Modesto - NW6 is primarily being developed to be ready as a 64 bit OS when Intel releases the chip. Its got nothing to do with the garbage your spreading. Exactly when will NT7,8,9 have a 64bit OS? It is taking them 2+ years beyond the due date just to get NT5 out the door. And even then it will be a stripped down version in order to get something out the door. Every few weeks the industry reports yet another few services and features that MSFT has admitted they will be removing from the intial NT5.
NetWare 4.x is already substantially more efficient than NT4. NW5 is even faster. NW6 which, unlike MSFT, will be ready upon the release of the Merced chip will run circles around NT5 - if its even out by then! LOL (Again NT is named Windows 2000 for a reason - that will be when its finally released).
NW5 can allow clients to login using SLP, DNS, or IP-addresses. Active Directory uses nothing because until its actually released onto the market as production - no one knows what Active Directory will or will not have! But if it remains as a DNS as a service locator then thats just another limitation of Active Directory and NT. Its too bad that NT5 will rely on a STATIC name database to locate its servers. That is why NW5 uses and sat on the SLP RFC committee to flesh out its development. SLP is a dynamic service locator protocol. If a Server goes off-line in the NT world, your poor DNS-based system will not know about it. Likewise - if a new NT service goes on-line, no clients will know about it until someone changes the static DNS database. So I am glad you pointed that out for all of us.
I also like your statement that IDNS is "compatible with DNS RFCs 1034 and 1035". So why would MSFT not use the straight complete standard RFCs themselves. Why did they have develop a "Compatible" solution? I'm sure many of us know why - another form of a MSFT trap to tie its poor users into some obscure proprietary system.
NDS needs to learn absolutely nothing from Domains! Domains are the joke of the computer industry. And if you think otherwise, then look around buddy! Even die-hard NT biggots agree that Domains are a weakness of NT. If they were so great then why is MSFT trying to make sooo many major enhancement in the release of Active Directory? Enhancements that are meant to try to equal the functionality of NDS.
You still did not answer how NT4 communicates with each other and its clients. Come on, say it, tell us all how Netbios is required. And tell us how Netbios will be around to plague NT5 as well. Funny that it was MSFT that used to throw stones at NOVL for using chatty RIP/SAP in IPX and yet now the only one that still has to rely on an 70's chatty protocol is NT.
Lots of nice talk Keithsha, but NT4 is and NT5 will be based on 80's domain technology and 70's protocols. The most hypocritical statement is to call NT5 Windows 2000 based on the technology that it will be based on.
Toy |
