I'm trying to build a minifilter driver to log all IRPs. Logging takes place in the driver itself (using FltCreateFile(), FltWriteFile()...).
Without specifying an altitude in the .inf file, the minifilter loads but does not attach to any volume. Manually attaching using fltmc attach also fails (Attach failed : incorrect parameter).
When specifying an altitude, fltmc load filter leads to BSOD.
Any idea what might be causing this?
The problem seems to be with the INF driver installation file. Making sure the Strings section of the INF file is correct (no typos) may help.
Creating a new Minifilter driver project solved the problem for me.
Related
I am using Petalinux, built with Yocto SDK. I want to automatically install my kernel module and make the devices available in /dev/*.
With KERNEL_MODULE_AUTOLOAD+="modulename" I can see the appropriate entries in /etc/modules-load.d/ as well as entries in /sys/class/misc/** , but not in /dev/*. Is there something I am missing?
Well, the structure of Yocto has nothing to do with the creation of device nodes. Either your driver does that for you (upon loading / probing), or you had some script that made them earlier. As long as your module has been loaded upon boot, you've got KERNEL_MODULE_AUTOLOAD correctly. If the module gets loaded, but you're not getting any device nodes automatically (and you got that before) you'll need to investigate what has changed in your system. (Versions of kernel and eg mdev/udev etc)
I have been trying to load a mat file on my distributed computing environment. When I load running in a matlab terminal on any computer I can load it no problem. When I submit it as a job to my cluster it fails saying
Error using load
Bad version of endian-key
even though the version of matlab is identical. Just the environment is changed. I have stripped away everything to just simply
load ~/Desktop/model.mat
disp('Done');
exit;
and the problem persists. We are running this using Sun Grid Engine.
That particular error message can either mean the file is corrupted, or it can mean that the system failed to allocate memory while loading the data (and no, that isn't obvious from the message...)
I'm new to using WinDbg and am running into a problem. I've set the server for symbols and downloaded them, but I keep getting stuck when I try to run !htrace (or any other command actually). The error message I get is
Cannot load 'ntsdexts'
I get this on any command that starts with an exclamation point (i.e. !drivers, !heap, !htrace, etc.) which is making tracking down a handle leak a problem.
I'm using the srv*...* link direct to Microsoft for symbols.
The last line before I get the breakpoint is:
Module Load: C:\WINDOWS\SYSWOW64\VFRCORE.DLL (no symbols loaded)
From the comments:
Somehow I managed to get two different version of windbg installed and the one in the path is the wrong one. Put the dll file into the right place, ran from that specific directory and now it works.
I've managed to install the psychtoolbox-3 from the NeuroDebian repository without any explicit errors, but running AssertOpenGL yields this very verbose error message.
My system specs are as follows: Intel-based PC with Ubuntu 12.04 LTS
I've tried adding ~/Documents/MATLAB and all it's subdirectories to the Matlab pathdef, as this is where I pointed the DownloadAdditionsForNeuroDebian function to. Similarly, I've tried adding /usr/share/octave/site/m/psychtoolbox-3/ and it's subdirectories to the matlab path as well.
The error seems to be originating from a failed call to Screen; according to the above error message, Screen can't be found. That having been said, I'm able to run Screen at the Matlab console, although I get this error:
>> Screen
In place of the expected mex file this placeholder file was executed:
Screen
This mex file seems to be missing or inaccessible on your Matlab path or it is dysfunctional:
Screen.*
Hmm. I cannot find the file on your Matlab path?!?
One reason could be that your Matlab path is wrong or not up to date
for the current Psychtoolbox. You may want to run SetupPsychtoolbox to
fix possible path problems.
??? Error using ==> AssertMex at 210
Missing or dysfunctional Psychtoolbox Mex file for this operating system. Read the help text above carefully!!
Error in ==> Screen at 161
AssertMex('Screen.m');
Running SetupPsychtoolbox yields an error that is very similar to the first one.
I tried installing the suggested packages, but they were all already installed -- nothing seems to work.
I have absolutely no idea where to go from here. Does anyone have any suggestions?
The SetupPsychtoolbox command seems to have a bug. What is happening for you (and for me, when I tried this) is that the folder containing Screen.mex is being placed at the bottom of the search path. Here's how to fix;
type "pathtool" at the Matlab commandline
find the PsychtoolboxAddons entry and move it to the top (for me this was /usr/share/psychtoolbox-3/PsychtoolboxAddons)
If you don't have a folder PsychtoolboxAddons you may need to follow the instructions at http://docs.psychtoolbox.org/DownloadAdditionsForNeuroDebian
Don't forget to move your personal Matlab directory to the top also (the SetupPsychtoolbox command moves your personal directory to be underneath it's directories, which is a bit mean).
Save the path. Don't ever run SetupPsychtoolbox again!
Good luck!
Whenever I try to run this application (I didn't write it) that uses Crystl32.OCX, I get the error...
Run-time error '372':
Failed to load control 'CrystalReport' from Crystl32.OCX. Your version of
Crystl32.OCX may be outdated. Make sure you are using the version of the
control that was provided with your application.
For a long time, I was getting an error about Crystl32.OCX could not be found, but I ultimately managed to register it. However, it's not working properly now. Any ideas?
I solved this problem by reloading the Crystl32.ocx file and installing it in the path. C:\Windows\System\crystl32.ocx or C:\Windows\SysWow64\crystl32.ocx and you can download the update file this link ---> https://www.ocxme.com/files/crystl32_ocx