Dependencies in a windows 7 x64 driver - dll

I'm writing a video capture driver for windows 7 x64.
The driver is "pin centric" and is based on the avshws example provided by Microsoft.
The driver has to use a third party dll.
No problem at compilation, linking, signing.
On installation time, I get a code 39 error.
The problem is that in load time, windows in unable to resolve the dependencies that have the "third party dll". The dependencies are "msvcrt.dll" and "kernel32.dll"
Any suggestions will be welcome.

Related

Vulkan Building error

I want to build a sample included in Vulkan SDK.
I downloaded the SDK from http://vulkan.lunarg.com and install it.
Then I opened the Visual Studio (I have a 2013 version), I open the solution from this path: (C:\VulkanSDK\1.0.13.0\Demos). I choose DEMOS.sln file. Then when I click on LocalWindowsDebugger this message pops up:
vkCreateInstance Failure:
vkEnumerateInstanceExtensionProperties failed to find the VK_KHR_surface extention.
Do you have a compatible Vulkan installable client driver (ICD) insatalled? Please look at the Getting Started guide for additional information.
I have never worked with vulkan, but as it named "Demo", I think that everything inside of it should be set in order to work.
I searched the web, but as it is new, there are few resources talked about it.
What is ICD? and how to install it? (is it different from installer of VulkanSDK?) OR this error is about completely different property? like setting properties of VisualStudio?
ICD is basically your GPU driver...
Both the SDK and driver install vulkaninfo app. Use it to determine what extensions you have and whatnot.
BTW Some time ago AMD drivers forgot to export the extensions like VK_KHR_surface. Make sure you are using the latest driver (16.5.2.1 on AMD and 365.19 on NVIDIA as of time of writing).
Also you need supported GPU. Consult:
NVIDIA supported GPUs
AMD supported GPUs
Khronos maintained list
BTW: All the demos work for me.
Do you have a compatible Vulkan installable client driver (ICD) installed?
This message tells you that Vulkan's loader wasn't able to find a Vulkan driver on your device. ICD is the installable client driver that comes with the driver of your graphics card.
What GPU are you using and do you have a driver installed that actually supports Vulkan? Note that while your card may support OpenGL it may not support Vulkan.
Check NVIDIA(performance mode) is selected at "Nvidia X Server Settings" application if you are using ubuntu.

Failed to Load JNI shared library when trying to use titanium

I am having difficulty with Titanium cross mobile development platform, i am getting error "failed to load JNI shared library c:\programfiles\java\jdk 1.6.0 _45\bin\server\jvm.dll.
could any one help.Thanks in advance.
Did you read System Requirements?
From Documentation:
For Windows, the 32-bit version of Java JDK is required regardless of
whether Titanium is running on a 32-bit or 64-bit system.
Try to install additional 32bit version of Java (without removing the 64bit) and set the system variable.
You can refer the following links for it
Failed to load the jni shared library jvmdll Titanium
Failed to load the jni shared library jdk - Eclipse
Hope it helped you

Unable to install JDK7u21x64 on Windows 8 x64

I have just upgraded to Windows 8 Pro, mostly because my Windows 7 license has reached maximum activations and I have a free copy of 8, and partially so I can ensure my software is 8-compatible.
I seem to be incapable of installing the JDK. I just downloaded it from the Oracle website (jdk-7u21-windows-x64.exe).
Windows reports itself as: 64-bit Operating System, x64-based processor.
When I try and run it, either normally or as administrator is shows up with the message:
This app can't run on your PC
To find a version for your PC, check with the software publisher
Does anyone have any ideas on this, a quick Google indicates it should just install same as usual.
While 8 still insistently refuses to install the JDK even after re-downloading and checking the hash, the Netbeans + JDK bundle does install which includes the JDK so that solves this issue sufficiently for now.
Update: The 64-bit version now works fine.
Try the x86 version: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html , I don't think there is a proper build for Windows 8 Pro.

Using WebKit for SWT Browser inside Eclipse plugin

I tried today to use the WebKit as the Browser's underlying renderer for my eclipse plugin but no luck.
I followed the recommended instructions and my current environment is as follows:
OS: Windows 7 (x64)
Safari installed (in the PATH too)
32 bit SWT (eclipse RCP indigo SR1 32)
added the following line to eclipse.ini
-Dorg.eclipse.swt.browser.DefaultType=webkit
Now when I try to instantiate the browser:
Browser b = new Browser(parent, SWT.WEBKIT);
b.setUrl("http://whatismybrowser.com");
I get the following error:
Failed to load the swt-webkit library
Any suggestions?
Thanks.
I got this problem too
What you need to do use
JVM : 32bit
SWT :32 bit
set the safari.exe path in your environment settings , (If you are using older version of Windows)
Else if SWT and JVM are not of same 32 bit it will generate error .

Simple-OpenNI for Processing fatal errors with the Kinect

I have been using SimpleOpenNI, a wrapper for Processing, all summer now. I use it for the Kinect to make games and demos. Last week, I have been getting a fatal error in my processing window and none of the SimpleOpenNI projects will work. Here is the error:
SimpleOpenNI Version 0.20
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x72e8f955, pid=4596, tid=4624
JRE version: 6.0_24-b07
Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 )
Problematic frame:
C [OpenNI.dll+0xf955]
An error report file with more information is saved as:
C:\Users\mss042\Desktop\processing-1.5.1\hs_err_pid4596.log
If you would like to submit a bug report, please visit:
http://java.sun.com/webapps/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
It appears as if the new OpenNI/NITE/SensorKinect drivers do not work with the SimpleOpenNI wrapper. I have tried it with people using the old drivers and everything still works. Problem is, you cannot download the old drivers off of the websites so I cannot test if it's that or not. You can see everything I've downloaded from the simpleopenni site: http://code.google.com/p/simple-openni/
Any help with this error would be appreciated. Thanks.
Mike
It looks like there's a problem with OpenNI.dll. Make sure that:
You have the dll (It should be in Program Files where you've installed OpenNI)
Make sure you've got the Environment Variables for the Open NI paths and that the paths are correct, otherwise, you might have the .dll file, but the .jnilib wouldn't know where it is.
Had a Kinect Workshop in Uni, and my colleagues using Windows all had issues with the drivers,
so I'm just passing on what they did:
Even though they had 64-bit versions of Windows they used the 32-bit version, and used Brekel OpenNI Kinect Auto Installer - Developer Edition v1.3.2.3.exe(direct link via developkinect.com) after reading this message:
Comment 4 by tijmenva...#gmail.com, Oct 21, 2011 Hey all I have Solved
the unsatisfied link dll error on windows 7 64 bits by installing java
runtime (jre-7u1-windows-i586.exe)and (Brekel OpenNI Kinect Auto
Installer - Developer Edition v1.3.2.3.exe) I uninstalled everything
and than it worked :)
hope this helpes
in Issue#17 on the SimpleOpenNI project issues page.
Another colleague used Synapse and OSC in Processing instead of SimpleOpenNI, but she had loads of errors with the drivers (basically spent a few good hours uninstalling/installing different versions). In her case, uninstalling any previous partial or complete drivers from the machine and deleting any registry entries related to PrimeSense(Sensor, Nite) and OpenNI, then using the installers from the links on the Synapse page, worked for her.
HTH
This is a long shot, but that exact error is also given if the Kinect USB and/or power supply simply becomes unplugged. Thought it was worth mentioning as it is not obvious from the error message itself and it may help someone out if they kicked their power supply and started searching for the above exception :)