Closed Zero3K closed 4 years ago
Now it just results in an "Automatic Repair" loop.
The second problem was because it was unsigned, which is now fixed thanks to the developer of ImDisk. I have managed to get an analysis of the BSOD in question. I am attaching it to this comment.
Here's a conversation I had on IRC regarding it:
I cannot afford to do. Sorry.
Okay.
I managed to fix them but now have ran into ones that occur when I removed the 4 GB size limit and tested a 6 GB size RAMDisk. The pull request that I made which contains the changes I did is available at https://github.com/Zero3K/ERAM/pull/10.
Last version - the failure to load OS.
Parameters:
Drive = M: Alloc unit = 32 Disk size = 500 000 Rootdir ent = 128 Media ID = F8 Memory source = OS: NonPaged pool Local device = [checked on] Make TEMP dir = [checked on]
To restore the OS boot, I deleted the eram file.sys from the command line. while booting. Is there a help on the parameters? I'm afraid to experiment further ))) Thank you.
Please try the latest version (using the correct one for your OS's architecture) and make sure to boot into Driver Signature Enforcement disabled mode after installing it.
Any luck?
Any news?
@mshakurov Have you gotten it to work? Regarding the issue you're having, I will fix it by buying an EV code signing certificate and dongle, etc. with the money I'm getting for my birthday (which is in a little over a month) and making a new version that uses it.
I just tried a fresh build of it and have been able to use an 8 GB RAM Disk with no crashes under Windows 7 x64. So, I am closing this issue since it has been fixed for a while now.
It crashes when loading the OS with it active no matter the size that was chosen.