Discussion Locked

Setting up new computers

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I couldn't diagree more on the recommended partition sizes for desktop computers. If you setup a 2GB primary partition for your system files there are major shortcomings that scheme!

1). Win2K Pro takes approximately 1GB of disk space already, more if you follow the paging file size recomendation. WinXP Pro uses approximately 1.4GB of disk space!

2). When you install software it installs on the primary partition by default. Even if you point to a different partition many files are still installed on C: which eat up your primary partition space. Compound that when you have many programs to install.

3). WinXP Pro, by default enables Hibernation which creates a hiberfil.sys file equual to the amount of physical memory. The file is located on the root of C:.

My experience is NOT to have a primary partition < 4GB.

Also, creating multiple partitions usually mean one of more partitions do not get used which effectively means you end up with less disk space to use!

I partition desktop computer drives as one large partition and by using the computer (or User) group policy, lock specific users out of the system folder and system settings. The one large partition eliminates disk space headaches and eventually having to span partitions using Disk Administrator because the disk partitions were too small!

3 replies

by radiic

I have to say first I agree that MS partition sizes were very limiting in NT 4 but W2K I thought you could have up to a 16Gig primary partition. Which should be more than enough. I have found in my work environment that Having a second partition where all the drivers and stuff for that pc are located has saved me lots of time, especially when reloading the OS. Before you say it...Yes NT4 W/S needs reloads when you get to a certain point.

Partioning your drive into 2 sections makes sense to me. Keep your system Files on primary and data on secondary.

Rad

by mlivingston

I haven't had much success with ERDs on User machines in the past. This caused me to create 3 partitions on the user's drives - c:\ and d:\ with separate bootable NT OSes, and an e:\ for user's data. When we had smaller drives we had c: and d: setto about 2G each. If the c:\ fails to boot - we boot via floppy to the d:\ drive - recover any data, copy off the profile to another partition - then reload NT (if restoring the basic boot files doesn't fix the problem). After that restore the user's profile, and usually all is well! We've also stored the various drivers off in folders on the d:\. This strategy has come in handy fairly often.

ML

by gennews

Before any partitioning is considered the OS's needs require defining. For the older OS's 3.1/95/98 types 650meg for C works well with the same for application drives D & E. The swap file is moved to the beginning 500meg of a 2nd drive with the temporary internet files going into another partition. After all this the remaining space is optimized for cluster size as data drives. By the way there is no primary partition setup on 2nd, 3rd, etc. drives. Lastly as the installation is progressing an imaging program, Drive Image, Ghost, IC3 type is used to make images on a seconary data drive. When the installing is complete and stable earlier copies are removed leaving only the last valid copy. In the event of a major crash normally requiring re-installation of the OS a simple restoration of the last valid image, typically less than 10 minutes, takes care of it. Other OS versions simply have the C drive adjusted to the minimum, plus a bit extra, space. With all other steps remaining. After hundreds of setups this has saved thousands of hours of down time and rebuilding time normally needed when the inevitable nasty things happen. When available the working image is also placed on a server & burned to a CD.

James

This discussion is closed to new replies.