Partitions don't show up in Ghost, Paragon Drive Backup

[LaphLaw]

I tried posting this in a backup-related forum, but didn't really get
any answer. I'm really mystified as to what's going on here. Neither
Norton Ghost (ver. 2003) nor Paragon Drive Backup sees my 2 other
partitions. One is D:, formatted as NTFS, the other E:, as FAT32.
Under the disk management tool provided in Windows, it sees both
partitions, and reports them as "healthy". When I try and save my C
partition on another one, Ghost simply does not see them. With
Paragon's Drive Backup, it sees them, but says the file system is
"invalid". Invalid?? How the heck did that happen? Of course, I did
format them with Partition Magic, and I've had nothing but trouble
with them...

Can anyone help me w/ this? Thanks

 

[Rob Stow]

I tried posting this in a backup-related forum, but didn't really get
any answer. I'm really mystified as to what's going on here. Neither
Norton Ghost (ver. 2003) nor Paragon Drive Backup sees my 2 other
partitions. One is D:, formatted as NTFS, the other E:, as FAT32.
Under the disk management tool provided in Windows, it sees both
partitions, and reports them as "healthy". When I try and save my C
partition on another one, Ghost simply does not see them. With
Paragon's Drive Backup, it sees them, but says the file system is
"invalid". Invalid?? How the heck did that happen? Of course, I did
format them with Partition Magic, and I've had nothing but trouble
with them...

Can anyone help me w/ this? Thanks

It all depends on the OS you booted up with before
running the imaging program.

When reading/writing a partition for the purposes
of imaging that partition or loading an image onto
that partition, the imaging application essentially
ignores the file system on the partition and directly
accesses the sectors.

However, when the imaging app saves images files to a
different partition or when it read images files from
that partition, it does so through the OS and hence is
limited to partitions that are accessible to that OS -
with accessibility determined both by the location of the
partition and the file system of that partition.

Example 1:
If you boot DOS, you can only save images to or load
images from a FAT16 partition. Even then, you will
need to deal with the fact that DOS has problems with
large hard drives - partitions that are too far from
the beginning of the disk will be inaccessible.

Example 2:
If you boot Win9x/WinMe, then you are restricted
to saving images to or loading images from images
FAT16 and FAT32 partitions. And although those
OSes are not as bad as DOS with regards to large
hard drives, you may still run into problems with
partitions that are more than 32 GB from the start
of the drive.

If you are running your imaging app from NT, W2K, or
XP, then the sky is the limit - your will be able to
save image to/load images from any FAT16/FAT32/NTFS
partition.


Easy NTFS workaround for DOS & Win9x:
Download NTFSDos from www.winternals.com or
www.sysinternals.com and follow the instructions in the
readme file to create a DOS or Win9x boot disk that can
read NTFS partitions. To write to NTFS partitions you
will need to buy the "pro" version.

 

[LaphLaw]

If you are running your imaging app from NT, W2K, or
XP, then the sky is the limit - your will be able to
save image to/load images from any FAT16/FAT32/NTFS
partition.

Well, that's the thing -- I *am* running Windows 2000, so theortically
I shouldn't be having any problems with this... yet I am. I've tried
both Ghost and Paragon under Windows 2000, and they refuse to see my
partitions, or report them as being "invalid".

Why would this happen under W2K?

 

[John John]

How many partitions do you have and how did you create these partitions?
If you can't resolve the problem I would suggest that you email the
software support team.

John

 

[LaphLaw]

3 partitions: c, d, and e. C and D are ntfs, e is fat32. I created
them with partition magic 8.0.