pepito
10-24-2002, 06:20 PM
i was wondering is win2k advanced server an advisable OS for an ordinary computer user only? is it that stable compared to XP? or win98SE is still better?
thanks for your opinions!
thanks for your opinions!
Click to See Complete Forum and Search --> : is win2k advance server an advisable OS?
Bigjakkstaffa
10-24-2002, 06:55 PM
Its as stable as XP if not more... 98 isnt even in the same ballpark as it just plain sucks for Resource managment and crashes regularly unlike XP and 2k.. if your and average user Advanced Server is probably a lil bit more than you need.. 2k pro would prolly be better suited, unles syou were intedning to set up a large LAN at a later date and use the OS as a server for it...
--Jakk:t
--Jakk:t
Bigjakkstaffa
10-24-2002, 07:39 PM
LOL - this is a double post innit, i saw thew other in Apps + Os' and got all condifused there for a moment :x
-Please in future try and avoid this, it causes much confusion for simpletones liek me :)
--Jakk:t
-Please in future try and avoid this, it causes much confusion for simpletones liek me :)
--Jakk:t
pepito
10-24-2002, 09:05 PM
well, i just forgot to put this thread to its proper location. thanks for your advice and sorry for my mistake!
Bigjakkstaffa
10-25-2002, 07:29 AM
It's okay :)
Good luck with whichever OS you choose :) :t
--Jakk:t
Good luck with whichever OS you choose :) :t
--Jakk:t
jonat8
10-26-2002, 04:02 PM
I don't think it'd be that ideal for day to day use to be honest unless you needed a specific feature that only it provides, like the Windows Media server for example.
I have a great setup at home... 1 PC with W2K Advanced Server as a domain controller, controlling the grand total of...wait for it... 1 PC with XP Pro on it. Oh and there's another PC that has XP Home that sits in a workgroup by itself because it can't join the domain. :D Great setup, eh! But they all manage to talk to each other and share files... somehow. A botched example of a network if I've ever seen one, and I set it up :r
I have a great setup at home... 1 PC with W2K Advanced Server as a domain controller, controlling the grand total of...wait for it... 1 PC with XP Pro on it. Oh and there's another PC that has XP Home that sits in a workgroup by itself because it can't join the domain. :D Great setup, eh! But they all manage to talk to each other and share files... somehow. A botched example of a network if I've ever seen one, and I set it up :r
sm8000
10-27-2002, 05:00 AM
Just goes to show....if there's a wrong way to do something, we'll find it! :D
OpK Chowdy
10-27-2002, 05:44 PM
i'm running win2k adv. serv. right now. it's very stable, although Half-life seems to not like it :p :x :D
Logan[TeamX]
10-28-2002, 09:11 AM
My little Celeron 600MHz laptop loved it (when it had 512MB RAM)... but for average everyday use, you better tweak the **** out of it (disable components like DNS, DHCP, and IIS) before you use it, or the overhead will slaughter you, especially for gaming.
hoodedrat
10-28-2002, 11:35 AM
controlling the grand total of...wait for it... 1 PC
LOL !
LOL !
AllGamer
10-28-2002, 11:46 AM
LOL :r what a broken "network"
user0209
10-29-2002, 09:04 PM
Originally posted by jonat8
I don't think it'd be that ideal for day to day use to be honest unless you needed a specific feature that only it provides, like the Windows Media server for example.
I have a great setup at home... 1 PC with W2K Advanced Server as a domain controller, controlling the grand total of...wait for it... 1 PC with XP Pro on it. Oh and there's another PC that has XP Home that sits in a workgroup by itself because it can't join the domain. :D Great setup, eh! But they all manage to talk to each other and share files... somehow. A botched example of a network if I've ever seen one, and I set it up :r
omg, you cracked me up.. haha
Why the home xp can't join the network, again?
What "domain controlling" means? (sorry I'm so novice at networking craps) I thought filesharing, lan games are everything you need of a network :x :p
I don't think it'd be that ideal for day to day use to be honest unless you needed a specific feature that only it provides, like the Windows Media server for example.
I have a great setup at home... 1 PC with W2K Advanced Server as a domain controller, controlling the grand total of...wait for it... 1 PC with XP Pro on it. Oh and there's another PC that has XP Home that sits in a workgroup by itself because it can't join the domain. :D Great setup, eh! But they all manage to talk to each other and share files... somehow. A botched example of a network if I've ever seen one, and I set it up :r
omg, you cracked me up.. haha
Why the home xp can't join the network, again?
What "domain controlling" means? (sorry I'm so novice at networking craps) I thought filesharing, lan games are everything you need of a network :x :p
Logan[TeamX]
10-30-2002, 08:44 AM
XP Home is like light beer - saves you money, but you get nothing rewarding in the end :D
XP Home is still like running a Win9X operating system - the machine itself can't join the domain. A user can sign in with a domain-recognized username and password (as long as that identical account already exists on the XP Home box), and still access network resources, but it will never be an authenticated member of the domain.
Say I have the domain running called homelan.local (I use this one a lot at home). Say I have the domain account "wiseguy", and the password "biteme".
I could access a shared printer that specifically only allows the "wiseguy" account to print to it (besides Print Operators and Domain Admins, System, etc) by logging on to the XP computer as "wiseguy" and "biteme". I wouldn't be authenticated by a Domain Controller, but the account name and password would stand up to a security check.
Did that exact thing all through college on a laptop that was formatted bi-weekly just to check out new ideas... it actually had 4 operating systems on it at one time - WinME, Win2K Pro, Win2K Server, Win2K Adv. Server.
Hope that clears things up some...
XP Home is still like running a Win9X operating system - the machine itself can't join the domain. A user can sign in with a domain-recognized username and password (as long as that identical account already exists on the XP Home box), and still access network resources, but it will never be an authenticated member of the domain.
Say I have the domain running called homelan.local (I use this one a lot at home). Say I have the domain account "wiseguy", and the password "biteme".
I could access a shared printer that specifically only allows the "wiseguy" account to print to it (besides Print Operators and Domain Admins, System, etc) by logging on to the XP computer as "wiseguy" and "biteme". I wouldn't be authenticated by a Domain Controller, but the account name and password would stand up to a security check.
Did that exact thing all through college on a laptop that was formatted bi-weekly just to check out new ideas... it actually had 4 operating systems on it at one time - WinME, Win2K Pro, Win2K Server, Win2K Adv. Server.
Hope that clears things up some...
SysOpt.com
Copyright Internet.com Inc. All Rights Reserved.
Copyright Internet.com Inc. All Rights Reserved.