Curby wrote:
> I recently did a system restore and now my C drive has only 2Gb memory and my
> D drive has 40G, but the system won't utilize the D drive and therefore I
> keep running low on memory and can not run any programs (I only have 60MB of
> memory)) ???
There are free tools for resizing disk partitions. No matter whether you use
a free tool, or a commercial tool like Partition Magic, make sure your disk data
is *backed up* first. The operation you attempt with tools like this, can fail,
and if this is your only copy of some data, you might have nothing left. I've
heard of this tool ruining at least one partition, so it happens.
http://www.partition-tool.com/easeus-partition-manager/help/resizing-and-moving-partition.htm
*******
A good question would be, how did this happen in the first place ?
If these are all primary partitions (i.e. the partition entries are in the
MBR sector), this tool will be able to list the sizes of the partitions,
their starting location and so on. It could be, that some tool you used
in the past, has put the entries in the partition table in the wrong order,
and the automated restoration ended up writing to the wrong partition as
a result.
PTEDIT32 for Windows
ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/PTEDIT32.zip
In this example, there are three primary partitions, and they're in order. The
first entry is at the beginning of the disk. The third is near the end of the disk.
If two of these entries got swapped, nothing bad happens. It is just that some
tools don't handle such a situation properly. Some tools might assume that the
first partition is always their "C:" for example. And that could result in
a mixup and your situation, with the restore going into the small partition.
PTEDIT32 screenshot
http://www.vistax64.com/attachments...n-partiton-recovery-dell-xps-420-dell-tbl.gif
I've never used PTEDIT32 to make changes. I only use it for verifying what is
going on. I make actual changes to the table with a Linux LiveCD (because at
that point in time, Windows is not running, and no file systems are "live").
I've never bothered to test whether PTEDIT32 can edit the MBR and make changes
or not. In any case, don't change anything in the PTEDIT32 window, as you
could easily lose data that way. I use the tool as a convenient way to
observe the four primary partitions listed in the MBR sector, and that is
all I do with it.
You don't need to use PTEDIT32 at all, and you can just use a partition
resizing tool to fix the problem. But it could be, that if you go to
restore the system a year from now, the same thing could happen, for
the same reasons.
HTH,
Paul
