Forum Moderators: open
Remember, you don't have to install software in the Program Files directory. If you are running out of space on the C: drives (and that's where Windows is installed) simply installing new software in another drive will, presumably solve the problem.
Kaled.
Windows XP Pro. SP2
Windows XP CD upon install
NTFS
12 BG
messed up upon install; did not consider how much space isneeded for C
I've removed as much s/w as I can from C; going to reinstall on other drive. But, how come it seems so hard to assign memory! I would think it can be done with right clicking on MY COMPUTER; and select: GIVE ME MORE MEMORY!
With NTFS, unless you are dual booting, there's not much to be gained by partitioning a large disk.
12 GB for the C: drive should not be a problem. The swap file can be allocated almost entirely to another drive and software can be installed in another drive.
Kaled.
I find myself in essentially the same situation as fashezee, with a 12-Gb "C" partition, which I had assumed would be large enough for anything I'd ever want to install, but it's turned out to be pretty tight. I also have NTFS, XP Pro SP2, etc.
I bought myself a bit of space by putting most of my swap file on a different drive, but my "C" (program) partition is relatively close to full, and I have 100-Gb or so of empty space on my "D" (data) partition.
I bought Partition Magic v8.0 when I had the system built for me. I'm not sure whether it was used to set up the original partitions. I had used the original Partition Magic successfully with Windows 9x, but that was before Symantec acquired the company. I've developed a deep dislike of Symantec products over the years, and have in fact stopped using System Works. Still use NAV, because it's too much of a pain to switch.
Though I have my data backed up, I don't yet have my C-drive cloned (plan to get Acronis to do that). I'm reluctant to run Partition Magic until I do... but I do remember that it was relatively easy to use and seemed to work like "magic." The clone builder says he's seen a lot of problems created by people resizing partitions containing data on XP, though.
Anyone use Partition Magic with XP?
Put in the amount of MB you want to reduce it by in the "Free Space Before". This is the amount you want to increase your C: partition by.
Then right-click on C: partition and place 0.0 in "Free Space After". Then simply click Apply (lower left column in PM 8.0).
The thing to remember in PM is the free space you create has to be adjacent to the partition in which you want to move it to (if that makes sense). Meaning if you reduced D: leaving the unpartitioned free space at the end ("Free Space After") of D: - you could not move it to C:.
[edited by: The_Contractor at 8:35 pm (utc) on Nov. 14, 2007]
The adjacent free space explanation is very clear. Only partitioning question I have is with regard to something I didn't mention... viz, I have three partitions on my drive, C, D, and E. The E partition is OK the way it is.
I'm assuming that if I just handle the C-D boundary, this will not affect the D-E boundary at all.
Also, I don't have PM currently installed (but fortunately I do have sufficient space on C for it, so that's not a problem). I'm assuming I can just install PM and apply it to the current partitions... that it doesn't matter whether my clone builder originally used PM to create the partitions or not (and that a partition is a partition is a partition, as the saying goes.
Ballpark, what size is a realistic figure for a C partition these days (and I understand there's no set answer... that it depends on my apps), but does 20-gigs sound like it should hold things for a while?
I'm assuming that if I just handle the C-D boundary, this will not affect the D-E boundary at all.
Correct, it will not affect it.
I'm assuming I can just install PM and apply it to the current partitions... that it doesn't matter whether my clone builder originally used PM to create the partitions or not (and that a partition is a partition is a partition, as the saying goes.
Correct again.
Ballpark, what size is a realistic figure for a C partition these days (and I understand there's no set answer... that it depends on my apps), but does 20-gigs sound like it should hold things for a while?
Hmm..can't answer that. I have two 500GB drives that each have 4 partitions. My C: drive and "most" program files take up 27.8GB at this time.
Look at it this way, drives are very reasonable and you can always add another ;)
Yes, on a desktop, but it's not so easy on a laptop. The 30GB partition on c (was preconfigured) just isn't enough. The cost of a new HD for the laptop is crazy, especially when you buy a brand new laptop for not much more than the cost of a new drive. In addition, if I were to upgrade the drive, i'd have to get the o/s onto the new drive.
The cost of a new HD for the laptop is crazy, especially when you buy a brand new laptop for not much more than the cost of a new drive.
I see many 160GB drives for laptops under $100 at Newegg along with 250 GB drives running under $175.
In addition, if I were to upgrade the drive, I'd have to get the o/s onto the new drive.
If you use a software product like DriveImage or something similar you can copy your existing drive/partitions to the new drive using this handy little adapter (hope I can post the link, as it's a handy little piece of hardware [newegg.com] that works with all drives - ATA, SATA, and laptop drives. I just used it for doing exactly what you are referring to.
I have no affiliation with NewEgg