MCR is not working on windows 7 professional - matlab

I have compiled and standalone application using MATLAB (32-bit windows 7 ultimate).
even though I have installed MCR of required version on target PC (32-bit windows 7 professional) my application is not working. (installation path C:\Program Files\MATLAB\MATLAB Compiler Runtime)
Note: on other windows 7 Ultimate 32-bit system my application is working fine

That message is indicating that it cannot find the path - I know you said that the path is set correctly.
However I would try setting the PATH variable manually in a dos prompt and then run the exe and see if it will launch.

Related

Installing WinDbg 32-bit on a 64-bit system

I've installed WinDBG on Windows 7 64-bit, however, I want to install the 32 bit version, not the 64 bit version.
I found this link on the internet:
https://social.msdn.microsoft.com/forums/windowsdesktop/en-us/cd004535-75f1-48ee-9176-574b344ddce1/how-to-install-windbg-32bit-on-64bit-system
Following the accepted answer, I do not have that path on my computer.
I have:
C:\Program Files\Microsoft SDKs\Windows\v7.1\Redist
However, there is no "Debugging Tools for Windows" folder in that direcotry like the answer says, only the VC folder. WinDBG is installed and working.
What can I do? Thanks.
You could download Windows SDK ISO file (https://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx) and install 32bit version from there. Also you could use !wow64exts.sw command to debug win32 process or dump using x64 version.

Why my m-file compiled with mcc does not run on my laptop (with Matlab) and on my pc (with MCR 8.2)?

I compiled an M-file on my laptop, obtaining an EXE file (lets say myexe.exe). I have MATLAB 2011b installed.
If I double click on myexe.exe, or if I run it from MATLAB command prompt with !myexe.exe, a window pops up saying:
Could not find version 7.16 of MCR. Attempting to load mclmcrrt7_16.dll.
Please install the correct version of the MCR.
Now, MATLAB Compiler Runtime (MCR) should be a standalone set of shared libraries that enables the execution of compiled MATLAB applications or components in computers in which MATLAB is not installed. I have MATLAB on my PC so why is it complaining about MCR?
Also, I copied this file to another computer in which I do not have MATLAB but I have MCR 8.2, it gives me the same error. I thought MCR was ensuring backward compatibility. Should I copy the MCR version 7.16 from my laptop to my PC and install it (I saw it is located in C:\Program Files\MATLAB\R2011b\toolbox\compiler\deploy\win64\MCRInstaller.exe, and I saw here that 7.14 is the MCR corresponding to MATLAB 2011b)?
What about my Laptop? Do I have to install MCR version 7.16 also there? I don't get why I should.
thanks
A.

Is it possible to create a 32bit standalone executable on a 64bit machine?

I'm creating a standalone executable from MATLAB .m file using mcc.
My machine is a 64bit machine and the target machine is 32bit machine, is it possible to create such an application (and to be able to run it on the target machine of course)?
Probably the simplest way to do this is to install the 32 bit version of MATLAB and use the mcc from that installation.
Don't worry about the warnings that you get about installing 32 bit MATLAB on 64 bit Windows. It works just fine. I have lots of different versions of MATLAB installed on my machine for development purposes, both 32 and 64 bit, all happily co-existing side by side.
The documentation also mentions a -win32 option that can be passed to mcc:
-win32 Run in 32-Bit Mode
Use this option to build a 32-bit application on a 64-bit system only
when the following are both true:
You use the same MATLAB installation root (matlabroot) for both 32-bit and 64-bit versions of MATLAB.
You are running from a Windows command line (not a MATLAB command line).
Since you have to install 32 bit MATLAB, no matter what, it seems to me that it's just easier to run the 32 bit mcc directly.

Cannot install Oracle Forms on Windows 7

I have downloaded Oracle Forms but I am not able to install it in Windows 7 (32bit). I am getting an error
Using paramFile: ..\install\oraparam.ini
Checking installer requirements...
Checking operating system version: must be 5.0, 5.1 or 5.2. Actual 6.1
Failed <<<<
Exiting Oracle Universal Installer, log for this session can be found at C:\Program Files\Oracle\Inventory\logs\installActions2012-06-09_09-56-47PM.log
Please press Enter to exit...
Kindly assist me in installation.
if you're using windows 7 then right click on the setup file and properties and do like this
Change Compatibility Mode
Click Check On Run This Program In Compatibility Mode For:
Windows Xp Service Pack 3
then setup will run and oracle will install on windows 7
Under Oracle Reports 10g directory go to install folder then open oraparam file in note pad and change [Certified Versions] windows values like bellow:
[Certified Versions]
Windows=5.0,5.1,5.2,6.1
There's a tickbox next to it to ignore the condition. Put a tick to it & the setup will continue.

WinDbg is not loading my symbol files

I'm writing a Kernel mode usb-driver primary for Windows Vista 32bit but hopefully it will also be able to be builded for Win XP, Win Vista, Win 7 32 and 64 bit.
Anyway, I'm debugging from an Windows 7 32bit laptop to a Windows Vista 32bit laptop (the target). The laptops are connected via Firewire and the connection seams to be ok since I can set some breakpoints and step trough parts of my code. All information is in assembly though and WinDbg says "Your debugger is not using the correct symbols..." when I hover over an function in my driver.
Symbol file path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Me\MyDriver\objchk_wlh_x86\i386
Source file path is:
C:\Me\MyDriver
Everything is newly compiled but WinDgb still won't accept my symbol files. Why?
If you can set breakpoints and step through your code it sounds like your symbols are fine. You can try:
!itoldyouso mydriver
If you want the debugger to convince you that your symbols are OK.
I never use the hover feature in the GUI, but it's entirely possible that it just doesn't work properly in some cases.
-scott