Other Software > Developer's Corner

Issues with ERAM (An Open Source RAM Disk Driver) and its CPL

(1/2) > >>

Zero3K:
1. I managed to fix its BSODs thanks to a member of community.osr.com but now after removing the 4 GB limit it has in place and using a 6 GB drive, I get BSODs when trying to copy files 2 GB or greater in size to it. One of the BSODs I get is one that mentions it trying to access memory that was set to be read-only. The source code and instructions for compiling it are available at https://github.com/Zero3K/ERAM/ and the Pull Request containing the modifications I did to remove the limit (along with a link to an analysis of the BSOD I mentioned) can be found at https://github.com/Zero3K/ERAM/pull/10.

2. Regarding its CPL (which is used to configure it), I tried to compile it using Visual Studio 2017 Community but have ran into some "unresolved external symbols" errors which you can see by going to https://pastebin.com/HCv1WW3M.

3. I compiled the CPL using WDK 7.1.0 and isn't working in Windows Server 2003, etc (It shows up in the list of Control Panel Applets but nothing happens when double-clicked on).

How do I fix one or more of those issues?

KodeZwerg:
I get BSODs when trying to copy files 2 GB or greater in size to it.
-Zero3K (November 25, 2018, 05:42 PM)
--- End quote ---
You need to code in 64bit to have access to larger file operations without further problems.
2GB is 32bit limit, you can not increase that value on its own, you only could workaround by reading/writing in chunks and not as one whole mapped memory block or as mentioned before, 64bit....

> I have not looked your source <

KodeZwerg:
I was slightly wrong, you actual can increase to 2.5/3GB by setting PE flags.
I need to look how I did it within my beloved Delphi if you like to get that information.
But I really dont know if that is possible with a System Driver..... I am very unsure/sceptic!

Zero3K:
1. I managed to compile it with Visual Studio 2017. The 64-bit driver that is made as a result isn't working in Windows 7 (but it does work in Windows 10).
2. The 64-bit version does allow a 4 GB RAM Disk to be made.

KodeZwerg:
1. I managed to compile it with Visual Studio 2017. The 64-bit driver that is made as a result isn't working (but the 32-bit one does).
2. The 64-bit version does allow a 4 GB RAM Disk to be made.
-Zero3K (November 26, 2018, 02:40 PM)
--- End quote ---
I really have no idea what you said.
VStudio I do not own so a "The 64-bit driver that is made as a result isn't working" with a followed "The 64-bit version does allow a 4 GB RAM Disk to be made" sound a bit wierd information.

If you need help, I sure can assist with knowledge, but i will not install that piece of software.
When you tell whats not working, giving some text passages from source to describe where you stuck, then i could more help.
When you encounter problems with 64bit, you should be sure that your program is using proper types and calls and memory settings to work with 64bit. Especialy pointer operations are very sensible with 64bit.
Just tell compiler to compile as 64bit target wont change code for you, that you must handle on your own.
That said, my first guess is that you try use 32bit pointers with 64bit = BSOD

Navigation

[0] Message Index

[#] Next page