Re: [Dokan] Installer does not install dokan.dll on 64 bit Windows 7
2,480 views
Skip to first unread message
William Levra-Juillet
Apr 26, 2012, 4:17:38 AM4/26/12
to do...@googlegroups.com
Hi Tobias,
We have our own installer.
On a 64bits os, the x64 version of the dll should go in C:\Windows\System32
and the 32bits version in C:\Windows\SysWOW64
That way, 64bits exe and 32bits exe will link against the correct version.
Hope it helps
William
On 26 April 2012 01:00, Tobias Patton
<tobias...@semaphoresolutions.ca> wrote:
> Hello
>
> I'm new to Windows development, so please forgive me if this is an
> ignorant question.
>
> I had been working on a 32 bit Windows 7 development machine, and
> everything was working fine. I've now switched to a 64 bit version of
> Windows 7.
>
> When I run the installer for Dokan-0.6.0, dokan.dll is not installed.
> That is, I'm expecting to see dokan.dll in c:\Windows\System32
>
> This means I can't link against the DLL in my project.
>
> Here's the output of dokanctl.exe /v
>
> driver path C:\Windows\system32\drivers\dokan.sys
> mounter path C:\Users\tobias.patton\git\RemoteFilesystem\Distribute
> \Dokan-0.6.0\DokanLibrary\mounter.exe
> dokanctl : Jan 10 2011 21:49:18
> Dokan version : 600
> Dokan driver version : 0x0
>
> Do I have to download the driver development kit and build for myself?
>
> Thanks,
> Tobias.
>
> --
> You received this message because you are subscribed to the Google Groups "Dokan" group.
> To post to this group, send email to do...@googlegroups.com.
> To unsubscribe from this group, send email to dokan+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/dokan?hl=en.
>
We have our own installer.
On a 64bits os, the x64 version of the dll should go in C:\Windows\System32
and the 32bits version in C:\Windows\SysWOW64
That way, 64bits exe and 32bits exe will link against the correct version.
Hope it helps
William
On 26 April 2012 01:00, Tobias Patton
<tobias...@semaphoresolutions.ca> wrote:
> Hello
>
> I'm new to Windows development, so please forgive me if this is an
> ignorant question.
>
> I had been working on a 32 bit Windows 7 development machine, and
> everything was working fine. I've now switched to a 64 bit version of
> Windows 7.
>
> When I run the installer for Dokan-0.6.0, dokan.dll is not installed.
> That is, I'm expecting to see dokan.dll in c:\Windows\System32
>
> This means I can't link against the DLL in my project.
>
> Here's the output of dokanctl.exe /v
>
> driver path C:\Windows\system32\drivers\dokan.sys
> mounter path C:\Users\tobias.patton\git\RemoteFilesystem\Distribute
> \Dokan-0.6.0\DokanLibrary\mounter.exe
> dokanctl : Jan 10 2011 21:49:18
> Dokan version : 600
> Dokan driver version : 0x0
>
> Do I have to download the driver development kit and build for myself?
>
> Thanks,
> Tobias.
>
> --
> You received this message because you are subscribed to the Google Groups "Dokan" group.
> To post to this group, send email to do...@googlegroups.com.
> To unsubscribe from this group, send email to dokan+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/dokan?hl=en.
>
שאול פרידמן
Apr 26, 2012, 5:02:36 AM4/26/12
to do...@googlegroups.com
Hi William,
Did you need to compile the Dokan library from source, to Windows 7 x64 platform ?
Is it a trivial task ? I never compiled drivers to windows before.
Shaul
William Levra-Juillet
Apr 26, 2012, 5:09:14 AM4/26/12
to do...@googlegroups.com
Yes, you need to build source using Windows DDK (freely available).
The most important part is that the driver needs to be digitally signed.
Good luck
William
The most important part is that the driver needs to be digitally signed.
Good luck
William
שאול פרידמן
Apr 26, 2012, 5:20:13 AM4/26/12
to do...@googlegroups.com
Why is this 'the
most important part' ?
You don't mean as technical setback, do you ?
William Levra-Juillet
Apr 26, 2012, 5:24:39 AM4/26/12
to do...@googlegroups.com
Sorry, "most important" was probably not the right words.
I meant that it costs time and money, and buying a signing-cert is
most of the time not something developers or R&D team can manage in a
company
Not in mine anyway :)
I meant that it costs time and money, and buying a signing-cert is
most of the time not something developers or R&D team can manage in a
company
Not in mine anyway :)
שאול פרידמן
Apr 26, 2012, 5:41:00 AM4/26/12
to do...@googlegroups.com
Thanks for the heads up.
I understand that your company works with Dokan.
By your experience, is Dokan stable enough to use in production ?
Are there bad IT configurations - as a customer might pool - that can make the use of Dokan driver dangerous ?
Like crashing windows - Blue screen of death ?
Are there any cons that I should know of, before recommend it to my bosses ?
I believe that the most important issues for my company will be stability, performance, workload.
If you know of a good article\blog that sums this things up, I would be happy to get a link to.
Thanks for the help,
Shaul
Jonathan Lin
Apr 26, 2012, 12:09:32 PM4/26/12
to Dokan
Windows Vista's and Windows 7's 64bit operating systems require all
drivers to be signed before allowing them to be installed whereas
their 32bit counterparts do not. That is why you were able to install
Dokan by compiling from the source code on a 32bit operating system
without further action but were unable to do so on the 64bit os. I
would suggest signing the driver yourself, especially if you do plan
on using Dokan in production. Signtool comes with WDDK I believe, but
as William pointed out you will have to purchase a signing
certificate. If you do, drivers in addition to being signed with your
certificate must also be cross-signed with the respective cross-sign
certificate which is publicly available.
To answer your second question, there is a list of issues
http://code.google.com/p/dokan/issues/list that people have found.
Some of these are old, and of those that are current not all of them
affect usability so keep that in mind while perusing them. I know
there is a method that puts a 32kb buffer onto the stack (I dun
remember which one, but Prefast which also comes with WDDK will catch
it), which I would recommend reallocating to the heap, but otherwise
it seems stable to me.
On Apr 26, 5:41 am, שאול פרידמן <shaul.frid...@gmail.com> wrote:
> Thanks for the heads up.
>
> I understand that your company works with Dokan.
> By your experience, is Dokan stable enough to use in production ?
> Are there bad IT configurations - as a customer might pool - that can make
> the use of Dokan driver dangerous ?
> Like crashing windows - *Blue screen of death ?*
> *Are there any **cons that I should know of, before recommend it to my
> bosses ? *
> *I *believe* that the most important issues for my *company* will be *
> stability*, *performance*, workload.*
> *If you know of a good *article*\blog that sums this things up, I would be
> happy to get a link to.*
> *
> *
> *Thanks for the help,*
> *
> *
> *Shaul*
drivers to be signed before allowing them to be installed whereas
their 32bit counterparts do not. That is why you were able to install
Dokan by compiling from the source code on a 32bit operating system
without further action but were unable to do so on the 64bit os. I
would suggest signing the driver yourself, especially if you do plan
on using Dokan in production. Signtool comes with WDDK I believe, but
as William pointed out you will have to purchase a signing
certificate. If you do, drivers in addition to being signed with your
certificate must also be cross-signed with the respective cross-sign
certificate which is publicly available.
To answer your second question, there is a list of issues
http://code.google.com/p/dokan/issues/list that people have found.
Some of these are old, and of those that are current not all of them
affect usability so keep that in mind while perusing them. I know
there is a method that puts a 32kb buffer onto the stack (I dun
remember which one, but Prefast which also comes with WDDK will catch
it), which I would recommend reallocating to the heap, but otherwise
it seems stable to me.
On Apr 26, 5:41 am, שאול פרידמן <shaul.frid...@gmail.com> wrote:
> Thanks for the heads up.
>
> I understand that your company works with Dokan.
> By your experience, is Dokan stable enough to use in production ?
> Are there bad IT configurations - as a customer might pool - that can make
> the use of Dokan driver dangerous ?
> *Are there any **cons that I should know of, before recommend it to my
> bosses ? *
> *I *believe* that the most important issues for my *company* will be *
> stability*, *performance*, workload.*
> *If you know of a good *article*\blog that sums this things up, I would be
> happy to get a link to.*
> *
> *
> *Thanks for the help,*
> *
> *
> *Shaul*
>
> On 26 April 2012 12:24, William Levra-Juillet <will...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Sorry, "most important" was probably not the right words.
> > I meant that it costs time and money, and buying a signing-cert is
> > most of the time not something developers or R&D team can manage in a
> > company
> > Not in mine anyway :)
>
> On 26 April 2012 12:24, William Levra-Juillet <will...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Sorry, "most important" was probably not the right words.
> > I meant that it costs time and money, and buying a signing-cert is
> > most of the time not something developers or R&D team can manage in a
> > company
> > Not in mine anyway :)
>
> > On 26 April 2012 10:20, שאול פרידמן <shaul.frid...@gmail.com> wrote:
> > > Why is this 'the most important part' ?
> > > You don't mean as technical setback, do you ?
>
> > > Why is this 'the most important part' ?
> > > You don't mean as technical setback, do you ?
>
> > > On 26 April 2012 12:09, William Levra-Juillet <will...@gmail.com> wrote:
>
> > >> Yes, you need to build source using Windows DDK (freely available).
> > >> The most important part is that the driver needs to be digitally signed.
>
> > >> Good luck
> > >> William
>
>
> > >> Yes, you need to build source using Windows DDK (freely available).
> > >> The most important part is that the driver needs to be digitally signed.
>
> > >> Good luck
> > >> William
>
> > >> On 26 April 2012 10:02, שאול פרידמן <shaul.frid...@gmail.com> wrote:
> > >> > Hi William,
>
> > >> > Did you need to compile the Dokan library from source, to Windows 7
> > x64
> > >> > platform ?
> > >> > Is it a trivial task ? I never compiled drivers to windows before.
>
> > >> > Shaul
>
> > >> > On 26 April 2012 11:17, William Levra-Juillet <will...@gmail.com>
> > >> > Hi William,
>
> > >> > Did you need to compile the Dokan library from source, to Windows 7
> > x64
> > >> > platform ?
> > >> > Is it a trivial task ? I never compiled drivers to windows before.
>
> > >> > Shaul
>
> > wrote:
>
> > >> >> Hi Tobias,
>
> > >> >> We have our own installer.
> > >> >> On a 64bits os, the x64 version of the dll should go in
> > >> >> C:\Windows\System32
> > >> >> and the 32bits version in C:\Windows\SysWOW64
>
> > >> >> That way, 64bits exe and 32bits exe will link against the correct
> > >> >> version.
>
> > >> >> Hope it helps
> > >> >> William
>
> > >> >> On 26 April 2012 01:00, Tobias Patton
>
> > >> >> Hi Tobias,
>
> > >> >> We have our own installer.
> > >> >> On a 64bits os, the x64 version of the dll should go in
> > >> >> C:\Windows\System32
> > >> >> and the 32bits version in C:\Windows\SysWOW64
>
> > >> >> That way, 64bits exe and 32bits exe will link against the correct
> > >> >> version.
>
> > >> >> Hope it helps
> > >> >> William
>
> > >> >> On 26 April 2012 01:00, Tobias Patton
שאול פרידמן
Apr 26, 2012, 12:20:04 PM4/26/12
to do...@googlegroups.com
Thank a lot for the clarification on the certificate issue.
I had no idea that its a prerequisite for driver installation on win 7 x64.
Thanks for the list. I will review it to see if Dokan current state, meets my specific requirements.
Shaul
Frediano Ziglio
Apr 26, 2012, 2:41:00 PM4/26/12
to do...@googlegroups.com
I think on this thread someone confused the dll with the driver. In
order to use or recompile the dll you don't need a driver (.sys)
change.
Dokan came with a 32bit dll version so if you want to develop a 64bit
program you have to recompile the dll but you can keep the same driver
(which is 64bit on 64bit OSes).
Frediano
order to use or recompile the dll you don't need a driver (.sys)
change.
Dokan came with a 32bit dll version so if you want to develop a 64bit
program you have to recompile the dll but you can keep the same driver
(which is 64bit on 64bit OSes).
Frediano
Reply all
Reply to author
Forward
0 new messages