BlitzKrieg
Content Type
Profiles
Forums
Events
Posts posted by BlitzKrieg
-
-
2003 Server as a server or workstation kicks XP in the nuts. I've tried several tests dual booting them off of the same machine with the same hardware configuration, 2003 Server as a workstation or server out performs XP in every aspect. XP is full of holes and SP2 doesn't even come close to 2003 out-of-the-box stability. 2003 Server Standard can easily replace XP and do everything you need it to do. I've ran 2003 Server Standard for almost 2 years from the same install and uptime of months with zero BSOD or problems...can't say the same with XP. When I worked for Dell I encountered so many problems with XP I learned to hate it with every fiber of my being. Want a stable workstation? Install 2003 Server Standard. Want a stable server? Install 2003 Server Enterprise. I defy anyone to claim XP even with SP2 is better vs 2003 Server Standard...it just isn't true.
0 -
Nevermind, I forgot I disabled the Cryptographic service for testing on something. Whoops.
0 -
My 2003 Enterprise Server uses NTFS 3.1, so would it be better to use NTFS 5.x? If so...how to convert to it? And would it be even worth it?
0 -
BLITZKRIEG
YEs, and here's the output:
Directory of C:\DOC.OLD\Tomi\SendTo23.11.2003 12:49 <DIR> .
23.11.2003 12:49 <DIR> ..
23.11.2003 12:17 129 3ìFLOP~1.LNK
1 File(s) 129 bytes
2 Dir(s) 8.316.723.200 bytes free
C:\DOC.OLD\Tomi\SendTo>attrib
A C:\DOC.OLD\Tomi\SendTo\3ìFLOP~1.LNK
C:\DOC.OLD\Tomi\SendTo>attrib *.* -s -r
Unable to change attribute - C:\DOC.OLD\Tomi\SendTo\3ìFLOP~1.LNK
C:\DOC.OLD\Tomi\SendTo>attrib *.* -s -r del 3*.lnk
Parameter format not correct -
C:\DOC.OLD\Tomi\SendTo>attrib *.* -s -r "del 3*.lnk"
Parameter format not correct -
Try this:
C:\DOC.OLD\Tomi\SendTo>attrib *.* -s -r
Then:
C:\DOC.OLD\Tomi\SendTo>del 3*.lnk
0 -
If you would of read the first few sentances of my post I explained how to remove the file attributes and delete the file. Did you try it?
That shortcut is for 3½ Floppy that is present in the SendTo menu upon a right click...open that folder in a command window (start -> run -> cmd.exe) and just do type the following: "attrib *.* -s -r" without the quotes followed by: "del 3*.lnk".You use an asterisk and not a question mark.
0 -
If we are talking about the HISTORY of television then it's easy, Barbara Eden. But if you're talking about CURRENTLY then it's got to be "Do" aka Dominique the extremely hot Dutch singer from the song: DJ Sammy - Heaven.
0 -
That shortcut is for 3½ Floppy that is present in the SendTo menu upon a right click...open that folder in a command window (start -> run -> cmd.exe) and just do type the following: "attrib *.* -s -r" without the quotes followed by: "del 3*.lnk".
OR, you need to install support for language packs. What version of Windows is that 2000? Pagefile.sys is your virtual memory so don't worry about that, I do not know what hiberfil.sys is.
Hope this helps.
0 -
Simple answer...but often overlooked. Check your jumper on your HDD's, if that fails run the recovery console and then fixboot...that should fix your problem. If either these do not...I have NO clue what it could be without seeing it for myself. When you say "blank screen" you don't mean a QUICK flash of a Blue Screen of Death followed by a black screen do you? If so then your Windows installation is possibly corrupted.
Also, some HDD's require the jumper to be set at Cable Select to function, check the HDD manufacturer's website for information on jumper settings. Good luck.
0 -
Some basic programming code would be your best bet. As in Visual Basic, Visual C++, or maybe even QBasic. I'm not aware of a DOS command that runs a size compare...or even gets and stores the file's sizes in RAM for comparison then Prints it on screen.
0 -
shady problems call for shady solutions....
try this program to bypass the version check
Ohhh cool. Thanks, I'll take a looksie at this.
0 -
in 2-4 years a 2003 Server platform
That's not a good idea. 4 years from now it will replaced with something else.
Check out my timeline...I was being a smartass.
0 -
but 2003 server to me is way better because of it's features.
Agreed.
Also, NT4 had it's day...now every NT4 server should be on a 2000 Server platform by now...then in 2-4 years a 2003 Server platform...then some other non windows server platform...since all "new" windows editions are going to suck hardy if they don't already do...longhorn is a joke so far that I've seen/used/screamed at it. I'm about to install Linux and get it over with now while I still can.
0 -
I understand it's just a pre-release beta but is the new filesystem working in anyway? I just got the MSDN disc with it on it...should I even bother? I haven't installed it yet, I can install it on a pretty hefty system so I won't worry about system resources even with a memory leak. Most of the reason why I want to even play with Longhorn is the new filesystem. Any relevant info is appreciated.
0 -
Who cares...a bunch of rich white people, so let's drop everything and bask in thier "glory".
I'd care if they reported on a subject that MEANS something or is worthwhile to mankind like; Who gave the most money to charity. Or something of that nature. Rich people make me sick.
0 -
Reinstall Internet Explorer? Edit sysoc.inf (C:\Windows\inf\) first. Remove any hide or HIDE.
for example:
Cluster=clusocm.dll,ClusOcmSetupProc,clusocm.inf,hide,7
-->
Cluster=clusocm.dll,ClusOcmSetupProc,clusocm.inf,,7Now, you can delete the component:
Start -> Control Panel -> Software -> Add/Remove Windows-Components
look out for Internet Explorer and unselect it.
Download Internet Explorer here.
As I said...Microsoft's site detect Server 2003 and won't allow any IE installations that are currently offered on thier download site. I've tried this already...oh well I'll just convert him to Opera and be done with it.
0 -
A friend of mine's IE crapped out on him and since you can not download/fix it from Microsoft's site how can I JUST reinstall the included IE6 on his machine without reinstallation of windows server 2003?
0 -
VS .NET installs and works perfectly on 2003 Server...without a hitch. No need to set compatibility mode.
0 -
Drivers that say "Windows 2000/XP" are compatible for the most part. If they say XP only you have a decent chance of them working. I've not had any real problems with drivers on Server 2003 either.
0 -
As far as I know, there arent any "official" drivers for nVidia based cards running under Windows 2003 Server. The only drivers that are listed on their site are for the 64-bit versions of 2003. I have tried loading the current reference drivers for 2k/XP and ran into some problems. And also, I'm not running it as a workstation, but as a bonafide file server. Hope this helps.
and just a quick offtopic question, what part of germany are you in blitzkrieg. im hoping to try and visit germany later this year, and have been trying to narrow down just what part to visit. drop me a line with any suggestions if you would. thanks.
I've been using the 2000/XP display drivers and they seem to work very well in Standard...I guess there's just something erie about Enterprise.
I'm not actually in Germany (yet). Since I'm of German decent I choose the flag to have patriotism for my "motherland".
0 -
I have tested the ent edition and turned it into a full workstation with no problems at all. Works like a charm and it is very stable.
Then how did you disable the policies. And no the "guide" here doesn't work with Enterprise.
Here's what you'll get:
As you can see it's not here.
I seriously doubt Microsoft would do this to only the MSDN Enterprise Server... :/0 -
In the 6 months of using Enterprise Edition I've never gotten a blue screen, perhaps its a driver/hardware problem?
Also, the Enterprise and Standard editions arn't too different, as you can get a single CD that has all the versions of Server 2K3 on it.
I have the MSDN DVD with all the versions on it. Other than the policy disabling (or lack thereof) they are about the same.
I'm running STD now and haven't got a single BSOD...I'm guessing maybe the nVidia drivers were corrupted based on the BSOD message. Oh well, I'll just stick with standard and be in heaven.
0 -
Ok I've legitamately obtain legal pieces of these software and used Standard for 7 months without one single crash, had uptimes of repeatedly 10 days or more with no system bog down doing seriously draining multitasking. Well I decided to give Enterprise a try and installed it...I wasn't happy with it when I tried to disable a few things to make it a workstation such as the Event Tracker and Error/Bug Reporting to MS. I know I installed it correctly and I'm not a computer novice by any means so I guess it's somehow hardcoded into Enterprise (which kind of makes no sense). I also would get a few BSODs everynow and then, reformat+reinstalled it a few times with 2 different legal versions of ENT and still recieved poorer performance than 2003 Standard.
Anyone else have any input on why 2003 STD > ENT? I'm rather dissatisfied with Enterprise--granted as a workstation mind you--yea it's an oxymoron...a "server" as a "workstation".
ALSO: If anyone knows where in the registry the "Event Tracker" and other such polices are stored please tell me as I cannot find them for the life of me...I WAS planning on coding a little VB utility to change ENT/STD/WEB to a workstation and I couldn't find the information I needed. Thanks in advance.
0
Why Workstation a 2003 Server
in Windows 2000/2003/NT4
Posted
Ok first of all, you should trying being more tact and less condescending. Secondly, don't throw up your "extensive" resume...this isn't a job interview I don't care where you work or what you do. I worked TECHNICAL support for Dell not in the mail room or lunch room as you boldly claimed I did. Nor am I some "1337" 15 yearold up at 3am eating potato chips--that's quite immature to just automatically call anyone who doesn't agree with you a teenager. For all I know YOU are the young person picking the fight. I wasn't rude nor being an assh*le in my post YOU however predictably were in yours. I quit coming here before for a reason, now I wish I never came back to give this place a second chance. Instead of having a civil intelligent debate you turned it into a juvenile flame war. Only thing left for you to do is to run to the teacher and get me in time out--AKA ask a moderator to ban me. I don't need to prove myself to you or anyone else my age, my work experience, or my credentials, I stated my OPINION based on my own personal EXPERIECE to add to this discussion. And based upon my experience with XP and 2003 Server in my current job, my personal use, and past technical background I do insist 2003 is more stable as well as trouble free as a workstation vs XP. Didn't "install it right" you said? Hah, what a crock. I've personally build and serviced hundreds of computers myself in which a portion of those were XEON server machines...but that doesn't matter nor should anyone care. I simply added my opinion to the discussion in hopes at least one person would take something positive out of it. Now if you'll excuse me I'll log out and refrain from coming here again. Take solice in the fact that I won't be back to read your drivel. Good day.