-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open multiple image #6
Comments
What exception did you receive? I haven't tried two images at the same time. One temp solution is to save the files to your local drive and then transfer to the new image |
I tried saving them to the local disk but I would need to keep the file permissions, that way they are lost. There are two kinds of exceptions(I assume there is a static pointer used by both): 1) Could not read disk MBR
2) Could not register partition.
|
Probably yes. When you transfer the file, keeping file permissions in a Dictionary<path, permission> in the memory, after the transfer, you can use |
Yes of course but it would be much more convenient to move files directly between images. Do you think it would be possible to fix the problem? |
I need take a look. |
This is the limitation of lew4. It only can take one disk image at a time, because the underline implementation is C. All variables are global variable and shared across the library. |
I tried to view the code, are you sure it is not a SharpExt4 problem?
|
I have done the quick fix. It seems working ok on my side. Let me know if you still have the issue. |
It now allows you to open two filesystems, the problem is that it always displays the last opened disk.
In my project, the same pointer for ExtDisk.bd always remains. |
Hope this time, this issue get fixed. I did a quick test, and it's working. |
Perfect everything seems to be working correctly, many thanks |
I would need to copy some files from one ext4 disk to another.
The problem is that when I try to open the second image if I haven't dispose of the first one first an exception is thrown.
The text was updated successfully, but these errors were encountered: