2 replies to this topic

[jakson]

Why can't I create files larger than 2GB in VMware WorkStation
(Windows 7 x64) on ramdisk created by ImDisk?
Is it ImDisk bug / VMware bug / Windows 7 bug?

PS
I was using Gavotte RamDisk (PAE) to create/store guest virtual machines
(VMware WorkStation) under Windows XP (x86) with success.

After upgrading from Windows XP (x86) to Windows 7 (x64)
I started using ImDisk ramdisk.
It is a great tool (thanks Olof , but now VMware says,
that I can't "store virtual disk as single file",
because "the destination file system does not support large files":
(BTW: it is 12GB NTFS formatted ramdisk)


after click on "Next" I've got:

I've tried many ramdisks and always got
"the destination file system does not support large files"
...except SuperSpeed RamDisk.
The only difference I've noticed is
that ramdisk created by SuperSpeed RamDisk
is shown under Microsoft Management Console / Disk Management
(and probably has partition table).

The only workaround I know is:
mklink /D C:\VM R:\VirtualMachines
C: - hdd ntfs partition
R: - ramdisk
but it doesn't work ok when available space on C: is less than available space on R:

[Olof Lagerkvist]

Why can't I create files larger than 2GB in VMware WorkStation
(Windows 7 x64) on ramdisk created by ImDisk?
Is it ImDisk bug / VMware bug / Windows 7 bug?

PS
I was using Gavotte RamDisk (PAE) to create/store guest virtual machines
(VMware WorkStation) under Windows XP (x86) with success.

After upgrading from Windows XP (x86) to Windows 7 (x64)
I started using ImDisk ramdisk.
It is a great tool (thanks Olof , but now VMware says,
that I can't "store virtual disk as single file",
because "the destination file system does not support large files":
(BTW: it is 12GB NTFS formatted ramdisk)

It reminds me somewhat about a problem some time ago when I was unable to use other than DOS 8.3-compatible filenames in Explorer on an ImDisk drive in Windows 7. This was because Explorer had not internally registered the volume properties correctly, which was caused by a missing device arrival notification. I thought things like that had been finally solved, but it could be that there is still some catch with it. Especially since it no longer wait for "hung" applications to process the notification messages.

Other than this, which just affects the connection between applications and how they could query filesystem properties, there is no places where ImDisk as a disk driver is involved in filesystem properties since this is rather a task for filesystem drivers.

We could try to check this more thoroughly when I (or someone else) get some time. Thanks for reporting it!

[jakson]

Ok, it looks like VMware bug - maybe thay fix it in next WorkStation releases:

http://communities.v...400063?tstart=0