DLL naming problem on the sigmarion 3

I've got an annoying problem I'm having trouble getting around. I've got a driver that is trying to load a DLL from ROM called SDBus.dll. Well, on the sig3 this file is called SDBusDriver.dll instead. Normally I would just use execheck to rewrite the driver name but the real one is longer so I can't do that. I thought about pulling the dll from ROM and renaming it but after going to the trouble of extracting the sig3 ROM I realized pulling a particular DLL out of there may be very very challenging. I looked around in the registry and there isn't a place to specify that the driver should use SDBusDriver.dll instead of SDBus.dll, it's hard coded into the DLL.

Any ideas how to proceed here?

Edited by thenzero 2023-09-02 1:38 AM

I was able to copy .exe out of the ROM very easily by copy & paste to a SD card, it is not the case for .DLL ?

Edited by stingraze 2023-09-02 1:56 AM

I don't think you can copy paste anything out of rom can you?

I could copy and paste the .exe out of Windows folder. That's how I used strings command in my Macbook to look at the strings inside the Mobile Custom related .exe files from the ROM. It might be worth trying out.

Oh, I see. Mobile custom is actually not in ROM. The sig uses a trick with some of the files like that and actually copies them out of ROM into RAM after a hard reset. The DLL I'm talking about is actually resident in ROM, not copied out into RAM so I can't copy/paste it like you can with the mobile custom exe.

Edited by thenzero 2023-09-02 2:54 AM

Windows CE should let you replace system dll files though. Can you just rename the file to the one you need and “replace “ the one in ROM?

Edit. Disregard. I see what you mean now. Sorry

Edited by torch 2023-09-02 3:29 AM

Wait. Can you read this article?

See if the sig has these registry options?

https://developer.toradex.com/windows-ce/knowledge-base/disable-the-...

Also background stuff I found too

https://guruce.com/blogpost/sdmmcandwindowsce

https://groups.google.com/g/microsoft.public.windowsce.platbuilder/c...

Not sure I'm following you here. How does this apply to what I'm doing?

Edited by thenzero 2023-09-02 4:07 AM

Does this SD DLL directory exist in the registry for the Sig?

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SDBusDriver] 
"Dll" = "SDBus.dll"

Yes, that is how windows CE identifies the name of the dll for the SD bus driver. Unfortunately it is named SDBusDriver.dll instead of just SDBus.dll.

Turns out the difference in the names has to do with the supported version of SD. SDBus.dll is SD v2 and SDBusDriver.dll is SD v1. So what I was trying to do probably isn't possible anyway. I think my device and the drivers may simply be too new for the sig3.

It also turned out that the hardware I was trying to get to work was actually DOA