search

ArsenalRecon / Arsenal-Image-Mounter

Arsenal Image Mounter mounts the contents of disk images as complete disks in Microsoft Windows.
https://ArsenalRecon.com/weapons/image-mounter
Other
496 stars 85 forks source link

Free ver of AIM do not mount splited vmdk, need DiscUtils/DIY something? #14

Closed ccchan234 closed 4 years ago

ccchan234 commented 4 years ago

hi.

i tried to use AIM to mount splited vmdk disk.

The install worked with splited raw, but have "object reference not set to an instance of an object"error when i wanna mount a splited vmdk.

the vmdk was created as shown in the picture, and is recognized by virtualbox so should be valid.

I only have free ver and not sure free ver need DIY or manually build discutils for this? I downloaded the zip file from https://arsenalrecon.com/downloads/, named Arsenal-Image-Mounter-v3.1.101.zip

btw,

As in the discussion elsewhere, not all discutils support .vmdk size of larger than 20KB. it would be nice if in later versions AIM could be modified to handle the .vmdk of larger than 20KB. otherwise the total vmdk disk will be limited to be 1TB.

thank you.

Screenshot (7)

LTRData commented 4 years ago

The fix for split vmdk images with large descriptor files that I made for DiscUtilsDevio (from another discussion) will be included in next version of AIM as well. I am not entirely sure that it is related to this particular error message though, I would have expected another error message. I'll check that!

ccchan234 commented 4 years ago

my platform is win10, 64bit.

i read AIM need .net 4?

i am not sure my system comes with that, if .net 4 need manually install?

thanks

EricZimmerman commented 4 years ago

windows 10 has everything you need already

LTRData commented 4 years ago

Just confirmed that I saw the same error in version .101 and this will be fixed in next version.

ccchan234 commented 4 years ago

oh i saw the .107 version.

could mount splited vmdk now.

and the .vmdk must < 20KB problem is solved too. but vbox's way of create .vmdk tops at 2TB, it's vbox's problem. (old standard of .vmdk is max at 2TB, new standard could max 62TB).

thank you.