Open GoogleCodeExporter opened 8 years ago
This is what a .Net 64 app running on x64 states (It works okay if the .Net app
is compiled as x86 !)
2010-10-01 18:54:31.9785[5][] INFO DokanNet.Dokan: Start DokanMain
2010-10-01 18:54:32.0354[5][] ERROR LiquesceSvc.ManagementLayer: Start has
failed in an uncontrolled way: System.DllNotFoundException: Unable to load DLL
'dokan.dll': The specified module could not be found. (Exception from HRESULT:
0x8007007E)
at DokanNet.DokanDll.DokanMain(DOKAN_OPTIONS& options, DOKAN_OPERATIONS& operations)
at DokanNet.Dokan.DokanMain(DokanOptions options, IDokanOperations operations)
at LiquesceSvc.ManagementLayer.Start(Object obj)
Original comment by smurf...@gmail.com
on 1 Oct 2010 at 5:56
[deleted comment]
OKay.. Seeing as the first Exception is stating that it "Cannot find" the dll,
I copied in the Dokan.dll into the executing dierctory (I did this with the 32
abd the 64 bit variants, and they both throw the following error
2010-10-01 20:08:01.8812[5][] INFO LiquesceSvc.ManagementLayer: Make sure it's
unmounted threw: System.BadImageFormatException: An attempt was made to load a
program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at DokanNet.DokanDll.DokanVersion()
at LiquesceSvc.ManagementLayer.Start(Object obj)
Original comment by smurf...@gmail.com
on 1 Oct 2010 at 7:14
Bot of the Dll's 33K and 43K are marked as Win32 intrnally (Usinf a PE explorer
application) So.
No 64 bit app can load a 32 bit dll (It's the way things are!)
Anyone have an idea on when 64 bit Dokan (Dll & sys) will / can be done ?
Original comment by smurf...@gmail.com
on 1 Oct 2010 at 8:43
I can confirm that no 64 bit dll was installed, only a 32 bit one.
Original comment by Nask...@gmail.com
on 8 Oct 2010 at 9:05
I am in the process of revamping the "User Space" part of the Dokan dll's.
As I cannot add the code back into here, it being kept as part of my offerings
in Liquesce:
"http://liquesce.codeplex.com/releases/view/88353"
Original comment by smurf...@gmail.com
on 7 Jun 2012 at 11:08
Original issue reported on code.google.com by
smurf...@gmail.com
on 1 Oct 2010 at 5:08Attachments: