Skip to content
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

When will create a new driver ext4 for Windows 10 #31

Open
AlexandrMakukhin opened this issue Oct 27, 2019 · 16 comments
Open

When will create a new driver ext4 for Windows 10 #31

AlexandrMakukhin opened this issue Oct 27, 2019 · 16 comments

Comments

@AlexandrMakukhin
Copy link

Hello!

I can not mount point ext4 on Windows 10.

Does not work Ext2Fsd.
October, 2019.

@vanphong1310
Copy link

vanphong1310 commented Nov 19, 2019

Ext2Fsd works on Windows 10, but you need convert Ext4 partition to 32bit mode.
Ext2Fsd doesn't support Ext4 64bit mode.

@TomJansen
Copy link

Are there any plans to support ext4 64bit mode?

@AlexandrMakukhin
Copy link
Author

Are there any plans to support ext4 64bit mode?

Yes.

@mirh
Copy link

mirh commented Mar 23, 2020

You can try bobranten's branch
http://www.acc.umu.se/~bosse/

@hacker1024
Copy link

hacker1024 commented Jun 11, 2020

I've built the latest version of @bobranten's branch, as of 11/06/2020 (commit: 9551666fbf60b707e997d3dc046e6c34044b2386).

It's a bit of a pain to build, so I'm uploading it: https://drive.google.com/drive/folders/1ctTwT4v46nmnThNCcdpkpAvxXNwGNOGI?usp=sharing

X64 only.

It works fine for me, and was able to open my Linux partition when this project couldn't.

You'll need to turn off driver signing, and reboot, before installing:
bcdedit /set testsigning on

Note: I haven't tried editing files. I don't recommend doing so.

@triforce
Copy link

bobranten's build doesn't work for me. The filesystem type is Linux 83.

@bobranten
Copy link

bobranten commented Jun 23, 2020 via email

@triforce
Copy link

On Tue, 23 Jun 2020, Chris Andrews wrote: bobranten's build doesn't work for me. The filesystem type is Linux 83.
A number of testers has reported that my update works for them, could you be more specific about the problem? Bo Branten

Hi Bo,

It turns out that there were bad blocks / disk partitions were corrupted so it was nothing to do with your code.

@vezaynk
Copy link

vezaynk commented Sep 15, 2020

@bobranten @hacker1024 Is there a possibility of uploaded a signed build? I have all sorts of things breaking because of being in test mode.

@bobranten
Copy link

bobranten commented Sep 16, 2020 via email

@vezaynk
Copy link

vezaynk commented Sep 16, 2020

It's just applications that explicit check for test mode. For an example, anything that relies of BattlEye or any similar anti-cheat game systems will detect it and refuse to launch. Some DRM-locked files may do the same.

Nothing critical, but annoying.

What are the limitations of self-signing? If self-signing is not effective for one reason or another, purchasing a 300$ certification all that is required?

@bobranten
Copy link

bobranten commented Sep 16, 2020 via email

@mirh
Copy link

mirh commented Sep 16, 2020

https://forums.vigem.org/topic/264/i-ve-started-a-company
Companies can be even single-man enterprises for as much verisign and whatnots are concerned.
I think the difficulty and paperwork needed to set up one, is kind of the point for releasing a certificate.

@vezaynk
Copy link

vezaynk commented Sep 17, 2020

What about self-signing it and sharing the public key?

@mirh
Copy link

mirh commented Sep 17, 2020

Self-signing is still test-signing?

@vezaynk
Copy link

vezaynk commented Sep 17, 2020

Well yes, but my understanding is if we add the certificate to the chain of trust locally, we should be able to use it without enabling test signing. It's a hassle, but it should work, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants