Hi,
I'm using ImDisk from a .net application.
Hence, Im not using the installer, I just copy and register the sys-file manually.
Like this:
On my Xp machine I have no problems to do the following using cmd in the background:
1) Copy the (proper) imdisk.sys to the system32\drivers directory
2) Register the driver using SC create ImDisk type= kernel start= demand error= ignore binPath= system32\drivers\imdisk.sys
3) Set the driver starting mode with SC config imdisk start= auto
4) Start the driver using NET START imdisk
5) And then mount the images I need
But since my app needs to work on Win7/Vista and 32/64 bit platforms, I'm struggling with this.
I have managed to (running my app as an administrator and turning UAC off)
1) Copy the (proper, i think) imdisk.sys to the system32\drivers directory
2) Register the driver using SC create ImDisk type= kernel start= demand error= ignore binPath= system32\drivers\imdisk.sys
3) Set the driver starting mode with SC config imdisk start= auto
4) This is when things go down the shitter. The command NET START imdisk returns Windows system error 1275, this driver has been blocked from loading.
This happens on Win7 Professional, not sure which processor architechture (not easy to find out either?).
I tried all 3 imdisk.sys just to be sure, same response.
What am I missing here anyone?
Driver blocked from loading
Started by
aNoR
, Jan 31 2011 02:19 PM
4 replies to this topic
#1
Posted 31 January 2011 - 02:19 PM
#2
Posted 31 January 2011 - 02:25 PM
Hi,
You need to copy imdisk.sys for the correct machine architecture to system32\drivers directory. So, depending on machine type you will need to select one of amd64\imdisk.sys, ia64\imdisk.sys or i386\imdisk.sys from the install files.
Any particular reason why you are not using the .inf install for this? It would select correct file and register driver automatically for you.
You need to copy imdisk.sys for the correct machine architecture to system32\drivers directory. So, depending on machine type you will need to select one of amd64\imdisk.sys, ia64\imdisk.sys or i386\imdisk.sys from the install files.
Any particular reason why you are not using the .inf install for this? It would select correct file and register driver automatically for you.
rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 .\imdisk.inf
#3
Posted 31 January 2011 - 02:43 PM
Hi!
I dont know if you remember but i emailed you some time ago about an application for an SD card reader that needs to mount virtual floppy disks in windows.
It really doesnt matter, but I will distribute my application using an installer and honestly I'm no good at these things, I'm just into the coding part. I don't know exactly how to modify the installer or how to create a 7zip package that will do all this for me (I'm just using a simple NSIS zip-package at the moment). That's why I felt I have more control over what is happening when I do it this way. All I want to do is to get the imdisk driver working silently behind the scenes, and preferably not showing in the control panel or the explorer context menu etc.
I just tried using the imdisk installer and it works fine (of course
) on the win7 machine as well. Is it impossible to get it to work the way I'm trying to explain? Maybe it's easier to let my app run the imdisk installer package the first time it is started?
I dont know if you remember but i emailed you some time ago about an application for an SD card reader that needs to mount virtual floppy disks in windows.
It really doesnt matter, but I will distribute my application using an installer and honestly I'm no good at these things, I'm just into the coding part. I don't know exactly how to modify the installer or how to create a 7zip package that will do all this for me (I'm just using a simple NSIS zip-package at the moment). That's why I felt I have more control over what is happening when I do it this way. All I want to do is to get the imdisk driver working silently behind the scenes, and preferably not showing in the control panel or the explorer context menu etc.
I just tried using the imdisk installer and it works fine (of course
#4
Posted 31 January 2011 - 03:14 PM
I'm just using a simple NSIS zip-package at the moment
You can try using the NSIS co-installer:
http://nsis.sourcefo...InstDrv_plug-in
http://www.msfn.org/...on-for-project/
http://www.msfn.org/...ect/page__st__8
If I managed in a few attempt to have a working installer, I am sure you can do it also.
Wonko
#5
Posted 31 January 2011 - 03:31 PM
Wonko: Thank you, I will have a look at that!
Also, I noticed a probable source of my problem.
On 64-bit OS, the driver of course ends up in the SysWOW64/Drivers folder, and the .net environment directory for some reason still keeps returning System32/Drivers. Which means i registered the wrong driver.
My bad, it's typical i found the problem just when posting in the forum (I have been struggling with this problem a long time).
This seems to solve my problem, thanks for your fast response!
Also, I noticed a probable source of my problem.
On 64-bit OS, the driver of course ends up in the SysWOW64/Drivers folder, and the .net environment directory for some reason still keeps returning System32/Drivers. Which means i registered the wrong driver.
My bad, it's typical i found the problem just when posting in the forum (I have been struggling with this problem a long time).
This seems to solve my problem, thanks for your fast response!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users








