false copy with ext4plugin

[Hanisch]

Hello,

I have copied an virtual disk-image 'Siduction.vdi' (15 GByte) from an Linux-ext4-Partition to an Windows VISTA system by Total Commander Plugin ext4plugin.
When I start the Siduction Guest-system in VirtualBox 4.3.2 it shows only:
grub>

I have than copied the 'Siduction.vdi' from inside the Linux-system with krusader to c:\Users\benutzer\.VirtualBox\HardDisks\Siduction.vdi
and now it works fine.

Ithink, the ext4plugin is buggy.

regards
Ch. Hanisch

[krasusczak]

Did you check crc from this both files?

[Hanisch]

Did you check crc from this both files?

How can I do it?

When ext4plugin read only files on Linux-partitions can ext4plugin write those files on Windows file systems too?


regars
Ch. Hanisch

[krasusczak]

You can compare crc in Vista after you copy this two files, but probably plugin failed because of file size, maybe this plugin not support such huge files..

[Hanisch]

You can compare crc in Vista after you copy this two files, but probably plugin failed because of file size, maybe this plugin not support such huge files..

Ok. - it maybe possible for such huge files - why?
But can't write ext4plugin files from Linux-partitions to windows-partitions as a matter of principle?

regards
Ch. Hanisch

[iana]

Are you using 32 or 64 bit tc and obviously the 32/64bit version of the plugin, there is a known limitation of file size handling 2^32=4GiB (or was it 2^(32-1)=2GiB) anyhow there is a file size limit using 32bit architecture, there are ways around it like building the 32 bit wfx with large file support, 32 bit Windows it self has problems handling large files that problem doesn't exist in PAE Linux Kernels.

If you have 32bit Windows there's nothing the author can do even with large file support 32 bit Windows can't handle 15GiB files, split the file in 2GiB chunks and then work with them.

for more info http://en.wikipedia.org/wiki/Large_file_support

[Hanisch]

Are you using 32 or 64 bit tc and obviously the 32/64bit version of the plugin,...

I am using 32Bit tc and 32Bit ext4plugin on Windows VISTA (32Bit).
No error occurs while I copy with ext4plugin - why?

If you have 32bit Windows there's nothing the author can do even with large file support 32 bit Windows can't handle 15GiB files, split the file in 2GiB chunks and then work with them.

for more info http://en.wikipedia.org/wiki/Large_file_support

When I copy from Linux inside to NTFS Partition it works fine. No error came on while handling 15 GByte file. And the copied file works fine for VirtualBox virtual disk 'Siduction.vdi'.
How can I make the 15GByte file in 2GByte chunks and than work with them?
I think it is not necessary, while it works with large file.

regards
Ch. Hanisch

[iana]

I am using 32Bit tc and 32Bit ext4plugin on Windows VISTA (32Bit).

That's it 32bit Windows and the 32bit wfx can't handle the file there seams to be a bug in the code there should be an exception when trying to access too large a file, most 32 bit linux's uses PAE http://en.wikipedia.org/wiki/Physical_Address_Extension and don't have that problem, the author should take a look at his code and add some error handling for big files, I'm not sure what the size limit is for Large File Support compiled 32bit dll's, also I don't know how the plugin copies the files does it use the System Memory (RAM+Virtual) in any case the RAM on 32bit Windows-es is limited to 4GiB as is the Virtual memory so no 32 bit app that uses the Memory can handle files bigger then 8GiB's.

[krasusczak]

plugin probably not supported by the author anymore, contact with author is also very limited, there is a sources of this plugin in the network but this is simple & buggy plugin & this is not only one problem with it..

[iana]

There are ways around the file size limitation on 32bit windows those are direct disk reads/writes bypassing the OS functions, those applications don't read the whole file but parts of it, you can try a different plugin
http://www.totalcmd.net/plugring/diskinternals_reader.html
that one does support reading Linux partitions but it still might have problems reading big files.

[krasusczak]

or you can use some soft & split one 15GB file in to a few ~3GB or something & copy one by one:D

[Hanisch]

or you can use some soft & split one 15GB file in to a few ~3GB or something & copy one by one:D

I can't understand the problem. With copying the big file from Linux inside with Krusader to NTFS file system there are no problems.

Is the ext4plugin not able to do this in right manner?

Can I show with ext4plugin only files on Linux partitions which are not big files?


regards
Ch. Hanisch

[iana]

I can't understand the problem. With copying the big file from Linux inside with Krusader to NTFS file system there are no problems.

I thought I explained it to you, there is no 32 bit plugin that can handle 15GiB files, Krusader uses the Linux Kernel that has PAE support and can handle big files, 32 bit Windows Vista (or 7 or 8 or 8.1) and 32 bit applications or plugins can not handle such files, you can install 64bit Windows and use the 64 bit TC + 64 bit plugin and you'll be able to access files up to 2^64= 16 EB.

In general 32 bit exe's or dll's (the plugin is a dll) files can address up to 2GiB the Maximum is 4 as 2 are left for the OS, if you try to access a file bigger then 2GiB the plugin should report an error, the only way around it is to use 64 bit TC and the 64 bit plugin in that case the size limit is around 8 Exa bytes 8*10^18.

Why doesn't Windows have full PAE support is a question for
Mcrosoft.

[Hanisch]

...
In general 32 bit exe's or dll's (the plugin is a dll) files can address up to 2GiB the Maximum is 4 as 2 are left for the OS, if you try to access a file bigger then 2GiB the plugin should report an error,....

No, the ext4plugin report no error when access a file bigger than 2GiB.
That is what me wonder.

regards
Ch. Hanisch

[Sob]

Even 32-bit Windows have 64-bit file API, so there's no problem with files over 4GB. Known limitations are FAT filesystem and older programs that don't use 64-bit file API.

As for the ext4plugin, I can confirm there's something wrong with it. 1GB test file was copied ok, but 5GB test file was damaged. But it's not 32-bit only thing, 64-bit plugin damaged it too in exactly the same way (md5s of both copied files were the same).

Edit: DiskInternals Reader works fine. Windows XP (32-bit) and 5GB file => no problem at all.