Average size system with Win XP Pro

[1Drisnil]

Could someone share with me what the average size harddrive/memory is on workstations running Windows XP Pro in the corporate workspace these days?

Also, are there any log files that are generated everyday in Win XP Pro ? Some of the systems in my work place are eating up the drive space when compared to other systems and the end user is not allowed to write to the local hard drive.

Anyone ?

Inquiring Minds,

 

[bcastner]

The average is likely something like 20 gb, 128 RAM. The mode is likely 40 gb, 256 RAM with large standard deviation.

40/256 for new purchases is pretty much the norm. The sizing of hard disks and RAM Modules for new purchases forces this even with a "thin client" thinking in mind.

You second question about space is complicated. It is not log files that are at issue, but virtual memory stores, temp caches for Internet and other uses, etc.. are more likely to blame for your hardware use. I found this article by Microsoft one of the better explanations for "hidden" file bloat under XP:

http://support.microsoft.com/default.aspx?scid=kb;en-us;315688

 

[linney]

Hey Bill, how could you forget to mention our old friend System Restore?

 

[bcastner]

aliens, I guess.

(SR is mentioned as an issue in the MS checklist)

sheesh.

 

[linney]

Are you sure it's mentioned, i agree it should be as it can eat up a lot of hard drive space. For example after doing Service Pack updates just one restore point maybe over half a GB.


The average size of a restore point is about 30MB but there can be many of them created up to a total combined maximum size of 1.2GB.

 

[bcastner]

Darn Linney,

You are right. The System Restore usage is not mentioned as a specific item.

It is included in space in use by "system files" from both chdksk and ntfsbackup.

Start, Run, chkdsk

It will take a few minutes, but total system usage of file space will be reported, and this includes System Restore usage. (I believe)

As the System Restore files are stored in folders marked during install with the System attribute, and that is what is accumulated and reported. (I believe)

This "catchall" catagory includes the Last Known Good, and System file protection file caches. (I believe)

If you want a break-out by use for the system reserves, I am clueless, though enumerating by folder attribute in a script seems perfectly possible. There likely is a Third-party software that enumerates in this detail, but I never looked for one.

alien possession, I guess.

Now look at my thread and tell me why I cannot download from MS Download but have no problems from MS Update..

Bill

 

[1Drisnil]

I read an article on Windows & .Net magazine's web site, called " Problems with Network and System Upgrades" and their main feeling was with todays ever growing technology requirements, the best setup to get to assure that you will be ready for the next OS and productivity suite is:

2.0 Ghz P4 with 512MB RAM. The article never mentioned anything of Hard drive sizes though.

Anyone feel this is too much or right on target?

Inquiring Minds,
[no evil]

 

[bcastner]

If planning for future OS upgrades is the consideration, then with MS intentions to move Longhorn to 2005 I would most certainly wait on resetting the standard new purchase for a workstation in a network setting from the current average of 256 RAM and a 40 gig hard disk drive.

Even if you keep the workstations and add to them it has got to be cheaper to dos so in two years.