We have one xp pro pc which when we image it takes a Loooong time. We discovered that img is grabbing a file $extend$usnjrnl that it thinks is 11gb. The entire amount of disk space in use is only 8.5 gb. This is some kind of virtual file that xp creates. Is this a bug in img? Isn't it aware of the ntfs file structures so that if it encounters a virtual file, it can only grab the real data out of it? This reminds me of the sparse file problems we used to have with netware.