MapPhysToLin C# example

[Usipusi]

Hi Mate!

I can't find an example of how to properly export functions in C#...

Code: Select all

        [DllImport("inpoutx64.dll",  EntryPoint = "MapPhysToLin", CallingConvention = CallingConvention.StdCall)]
        [return: MarshalAs(UnmanagedType.LPArray)]
        private static unsafe extern byte* MapPhysToLin(UIntPtr pbPhysAddr, uint dwPhysSize, out IntPtr pPhysicalMemoryHandle);

        [DllImport("inpoutx64.dll", EntryPoint = "UnmapPhysicalMemory", CallingConvention = CallingConvention.StdCall)]
        [return: MarshalAs(UnmanagedType.Bool)]
        private static extern bool UnmapPhysicalMemory(IntPtr PhysicalMemoryHandle, byte[] pbLinAddr);

[phil]

Last time I looked, the .NET 2.0 samples worked (both VB and C#) and they are still available for download on my website. Whats the problem?
https://www.highrez.co.uk/downloads/inp ... efault.htm

NOTE: This is completely unsupported and a dead project now as far as I am concerned. I am unable to to rebuild it as I don't have the ability to sign drivers (etc.etc.). It should still work but its not something I can commit any time to other than the odd question here and there!

[Usipusi]

The example does not contain the function I am asking about, so I wrote to the forum.

[phil]

Sorry, I missed that!

Not sure those functions even work as its not something Ive ever used (or tested), so I don't have a great answer for you I'm afraid.
If I recall, I copied them from WinRing0 but never actually used them. The C++ signatures should be in the header files in the source archive - so it should be relatively easy to work out (comparing to the ones that are imported in the .NET example, but as I said, I have no idea if they actually work!)

Regards,
Phil

[Usipusi]

All functions work and even this one (Latest Win10). This is good news. By the way, Winring is not able to read physical memory even if you use #define _PHYSICAL_MEMORY_SUPPORT and recompile DLL. Your project is unique.

Code: Select all

        [DllImport("inpoutx64.dll",  EntryPoint = "MapPhysToLin", CallingConvention = CallingConvention.StdCall)]       
        private static unsafe extern byte * MapPhysToLin(UIntPtr pbPhysAddr, uint dwPhysSize, out IntPtr pPhysicalMemoryHandle);

        [DllImport("inpoutx64.dll", EntryPoint = "UnmapPhysicalMemory", CallingConvention = CallingConvention.StdCall)]
        [return: MarshalAs(UnmanagedType.Bool)]
        private static extern bool UnmapPhysicalMemory(IntPtr PhysicalMemoryHandle, byte[] pbLinAddr);

I may be of use to someone, I will leave the solution to the problem here

_____

P.s. I have heard that MS has influenced all similar projects. Is this true?
I'm sorry, I don't know where to read about the reasons.

[phil]

Glad to hear it works (didn't really expect that) and thanks for updating this thread - I hope it will help others!
I must have got the code from somewhere, I assume WinRing0 as it was open source like InpOut. I didn't write InpOut, only ported it to x64 and my driver experience is pretty much that!

By "Influence" I think you are referring to the almost impossible requirements to build drivers. They have to be signed with a driver code signing certificate - these are not available to hobbyists, only legally registered companies and cost quite a bit ($300+ a year). So it kind rules out these little projects. WinRin0 was killed when MS revoked their certificate meaning the driver will not install. That hasn't happened to InpOut yet but it could if someone were to abuse it like WinRing0 was used and abused (by malware developers). If/When that happens, InpOut will be dead unless someone manages to sign it with a new certificate - and take the risk that it will also be revoked (its a lot of pain, money and effort to get a certificate, to have it revoked because some random out there abuses the driver is not feasible).

So you could say Microsoft influenced it - but I can see why (if WinRni0 was used to bypass HDCP or other naughty things, they had every right to I guess).

[Usipusi]

Thank you very much for the information.
I really hope that MS policy never affects your project.
Happy upcoming holidays