TeraByte Unlimited

I used Image for Linux to perform an offline image of a particular NTFS partition. The imaging process seemed to go usual and fine, and I *can successfully* open using TBIView. I can even extract content while still using TBIView.

HOWEVER, I cannot mount the image via TBIMount. I get the error:

"Z:\ is not accessible. The media is write protected."

After I get the error, *there is* a virtual Z: drive in existence (created by TBIMount), but every time I click on it, I get the above error message.

I did my homework, and I found the same issue as experienced by a similar/competitive imaging product by PassMark:

http://www.passmark.com/forum/showthrea ... ted-Solved

Are there any suggestions for resolving this issue within the Terabyte Unlimited ecosystem?

If you're using an older Windows version, it can't mount NTFS volumes.
Here's a note in the tbimount readme (somewhere).

Windows NT and Windows 2000 do not support mounting of NTFS partitions
from Read-Only media. Since the image files are mounted read-only, this
means you will not be able to access NTFS partitions on those Operating
Systems. FAT type partitions will still be accessible and TBIView can
be used to access NTFS partitions on those platforms.


It can also occur if the file system is dirty needs to be unrolled. You can
still use tbiview.



"clargent4image" wrote in message news:[email protected]...

I used Image for Linux to perform an offline image of a particular NTFS
partition. The imaging process seemed to go usual and fine, and I *can
successfully* open using TBIView. I can even extract content while still
using TBIView.

HOWEVER, I cannot mount the image via TBIMount. I get the error:

"Z:\ is not accessible. The media is write protected."

After I get the error, *there is* a virtual Z: drive in existence (created
by TBIMount), but every time I click on it, I get the above error message.

I did my homework, and I found the same issue as experienced by a
similar/competitive imaging product by PassMark:

Are there any suggestions for resolving this issue within the Terabyte
Unlimited ecosystem?