I have an old driver which works properly on Windows 10 32-bit.
I need to compile it to work on windows 10 64-bit.
I managed to compile it in 64-bit, but when I am trying to install it to a test PC, I am getting this error:
Windows found driver software for your device but encounter an error while attempting to install it
A problem was encountered while attempting to add the driver to the store.
How can I find information about the problem?
I can not see any log in the event log or any other place.
Is there any place where I can find more information about this error?
Related
Created application using VS2015 on Windows 10 64 bit system, on this system it works fine, but when i run same application on Windows 7 64 bit machine get an assembly reference exception.
Tried installing CRforVS runtime installer or redist packages but no use.
Can anybody tell me how to resolve this exception.
Thanks,
I've been having trouble figuring out why I can't get pgAdmin GUI to run after I've installed PostgreSQL 8.2 successfully with all the default options. A few things that I've tried is to add in any missing DLLs (MSJAVA.dll) after running Dependency Walker on the exe file, updating the Windows XP to the latest update on the Windows Virtual PC VM, turning off my firewall, reinstalling PostgreSQL, but to no avail. I'm still getting this same error:
C:\PostgreSQL\8.2\bin\pgAdmin3.exe
This application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix the problem
I've read to make sure that the version of PostgreSQL is compatible with XP, and that people have successfully got it to work on a VM. I can't seem to figure out why this is not working out for me. Any thoughts?
I have created the driver for our device and installed in windows xp. While installing first time it will install successfully and shows in windows driver list. But when again install the windows xp shows that error code 28 and in driver list is showing that unknown device.
Please note that the multiple time installation done in windows 7, windows 8 successfully, but only create the problem in windows xp.
Any idea?
Heap memory was not free properly. Deleted the memory properly that is working in all platform.
I have been trying to install and run a program written in vb 6.0 on windows 7. It was working fine installing and running in windows xp. The error message after installing and running it say that
Run-time error 339" : Component voice.ocx or one of its dependencies not correctly registered: a file is missing or invalid.
This program has voice recording things.
I manually register that ocx component but still error that shown like
The module "voice.ocx" failed to load.
And I try to install VB run-time and still shows the same error. I believe that Windows 7 support vb 6.0 programs.
One thing here I am not sure of is that the ocx component I have is whether 16 or 32 bit version. I don't think we cannot register 16 bit version ocx in windows 7.
And I also try to install and run in compatibility mode or even as administrator. I think it is a platform related issue? And it might be some other work-around. So, I appreciate your hints or clues on this program runnable in windows 7.
Thanks in advance.
Regards,
SEE
Just encase anyone else sees this.. here is what I did
I knew the program was running on Windows XP, with visual basic installed. I had only been given the exe and the MDB. So I created a virtual machine (stick with me) of Windows XP, installed visual basic and test the app. It was fine. Then I downloaded a dependency tool called Dependency Walker from http://www.dependencywalker.com/. I installed this in the virtual machine and asked it to open my exe.
Once this was loaded I ignored the warnings and asked it to start profiling. I ran the app, stepped through everything I could see, then exited the application. This left me with a log of the DLLs that had been accessed. Slowly I went through these checking if they existed on my windows 7 setup, when one was missing I copied it to my application directory and then from an elevated command prompt run "regsrv32 [missing_name.dll]" until there were no files which my windows 7 desktop didn't have.
the application then worked fine! This may not work all the time, because of the way third party OCX's or DLLs have been written. But it may help someone out.
Few of old Win32 components are not supported in Windows 7. There are possibilities of failure of a VB Program in Windows 7.
But there are some possible ways to fix those.
Check the following links to avail the same.
http://www.personalcomputerfixes.com/general-errors/how-to-successfully-fix-the-339-runtime-error/
http://social.msdn.microsoft.com/Forums/en-US/vbpowerpacks/thread/8cb5ab97-8407-4e49-8db6-30dcef87cbd1/
http://yang.articlesbase.com/operating-systems-articles/simple-solutions-on-how-to-fix-runtime-error-339-1830111.html
I have developed several programs with VB5 on a WinXP32 machines and then installed them on Windows 7 (32 and 64) PCs without problems.
This applications use different OCXs (16 and 32 bit version) and till now I never get problem with them. Thus I do not think that the VB5 or Vb6 could have any issue on Windows 7 machines.
On the other hand I would point out the module "voice.ocx" and investigate if it can run on a windows 7 pc, because as Katturaja sais some old ocx have problem on win7. To do that, I would create a simply VB6 project that uses voice.ocx (just an Hallo-World"), then create the installation pack and finally try to install on a clean win7 machine (for example a virtual machine). In this way you could isolate the problem.
I hope this could help you.
I'm trying to use WIA in an older VB6 program running in Windows 7 and when I run from source everything works great and I can import images. When I run from the compiled version I get the following error:
Automation error. The specified module could not be found.
(Error number 2147024770)
I found the wiaaut.dll in both system32 and SysWOW64 so I don't know if that is potentially causing a problem. I tried unregistering and registering both to no avail. Any help would be much appreciate.
As far as I know wiaaut.dll is preinstalled in Vista and Windows 7, but this is not the redist version for XP that comes in the downloadable SDK, and it should not be deployed to those newer OSs. perhaps somebody tried to run some application installer on your machine that forced the XP version into place blindly?
Perhaps try How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 to see if it can restore the original Win7 version?