I am having trouble with OpenCV2.0 on Win7 32bit, I have recompiled it using MinGW 4.5.0 and everything went OK until I tried to run examples. Anytime it opens NamedWindow it crashs down. On the other side on on different machine Win7 64 bit everything runs without problem. Any idea?
Thx, Jan
It is a known problem due to some sort of "stack misalignment" with SSE under certain circumstances.
It has been posted before namedWindow() causes crash in opencv 2.3.1? (Eclipse+MinGW on XP, C++)
/Lars
Check that you are picking up the correct DLLs, and if you built with Qt, that you are getting the correct Qt DLLs.
Did you just install somethign that also uses Qt - but a different version (like AMDs codeprofiler)
Related
I have a problem loading meshes in the Ogre3D framework with the
'getMeshInformation' function from http://www.ogre3d.org/tikiwiki/RetrieveVertexData
when compiled on Ubuntu.
The program crashes due to a segmentation fault.
It is said that it has problems on AMD64 Linux,
but there is no mention of a version that works on that system
or what has to be changed in order for it to work.
The program runs fine on Windows when compiled with VisualStudio.
Thanks in advance.
Working code here:
http://www.ogre3d.org/tikiwiki/tiki-index.php?page=Raycasting+to+the+polygon+level#Adapted_version
It was kinda hidden though.
I've got the printer driver, P-touch Editor, b-PAC 3.1 and client tools, all 64-bit, downloaded from the Brother website and installed on my 64-bit Windows 7 laptop. The P-touch Editor works/prints fine.
However, b-PAC failed, and none of the samples worked. I debugged the code:
bool b = doc.PrintOut(1, bpac.PrintOptionConstants.bpoDefault);
where b is false. What could be wrong?
I was hitting the same problem, everything appears to work right up to the point where I called "PrintOut", which fails with error 11, "The currently specified printer is not supported".
It turns out the problem I had was with the driver. I had installed the printer driver from the CDROM that came with the label printer. Windows 7 also comes with an "in-box" driver for the printer and in fact this is the one you should install (it's marked with an "LE" at the end).
To fix the problem, all you need to do is go to the "Devices and Printers" dialog, select the printer, right click on it and select "Printer properties", select the "Advanced" tab and click "New Driver". Find the printer in the list that matches yours but with an "LE" at the end and click OK.
Printing is possible with either of the drivers using the P-Touch editor. Odd thing is, "LE" appears to stand for "Light Edition", but the "Heavy" version doesn't work!... strange.
On my Windows 10 x64 machine, I've had a similar issue using Ruby to print through the bPAC SDK (using win32ole). My code worked on another machine, but not mine.
After fighting with this for a long time, I figured out that all was fine and dandy when using the 32 bit version of the bPAC SDK (and Ruby). Don't know exactly what went wrong here, but it might be that the 64bit SDK is just broken.
I had a similar problem, so I added this after the printOut to see which code I was getting.
string sError = doc.ErrorCode
It returned Error 11, which corresponds to "Device is not supported", but the device was a QL-570 which IS supported.
To get it working, I used the following steps:
Side-install the 32bits sdk.
Open your 64bit sample.
Change target configuration platform from "any cpu" to "x86"
Compile
See also: Label printing development using b-pac SDK in a C# application
The important thing is the application that you uses.
If your app is a 32bitapp (inclusive excel) you need the bPAC SDK for 32bit even when they are running on 64-bit Windows OS.
Some printers only support 32-bit b-PAC SDK ver.
(even if you use windows 10 64-bit with Excel 64-bit)
please check:
https://support.brother.com/g/s/es/dev/en/bpac/environment/index.html
I had the same problem (printOut gave me the error code 11).
The error appeared after switching from the printer PT-9800 to PT-P950.
Trying 32 and 64bit did not work for me.
What fixed it was uninstalling the driver of the PT-9800. I found a hint in the b-PAC 3.4 SDK Help in the section Troubleshooting: "if the old label printer will no longer be used, we recommend deleting the printer driver."
Apologies in advance for the dated software question:
According to Code Composer help documentation the "Memory Load/Save Utility" should be be in the Tools menu. In my Code Composer 3.3 (which I have to use for this project, so I cannot upgrade), does not have this option in the tools menu, or any menu that I could find. It is not greyed out - it is just simply missing as far as I can tell. I've changed every view option to try and enable this.
Can anyone help me figure out how to enable/activate this option? Does the processor need to be in a specific state? Is this a special plug-in that I can't find?
Here is my setup:
Code Composer 3.3, Windows Xp, Using a Spectrum Digital xds510pp JTAG emulator on a TI ARM 9 processor.
Specifically the option is here: 13. Memory Load/Save Utility:
http://www.ti.com/lit/an/spraa07c/spraa07c.pdf
[EDIT] The File > Data > Save - this is not the same as the Memory Load/Save Utility. This sounds similar but does not export the values.
For example, I need to export data at a certain memory address for a certain length into a hex format.
Somehow my installation went bad.
I checked the Code Composer Studio Component Manager by running C:\CodeComposer3.3\cc\bin\comp_mgr.exe. Now, in this window un the TI node, there should be numerous plugins and one of which should be: "Memory Save/Load Utility Control..."
For me this was missing.
Repairing the installation via windows control panel did not work. I had to uninstall and then reinstalled. Upon reinstalling a TMS470 driver was reported missing. Not sure why this was.
Again, I uninstalled then complete removed the C:\CodeComposer3.3\ directory, then reinstalled. This time everything seemed to have worked and I do have the Memory Save/Load Utility and it is working.
EDIT:
It should also be noted that the plugins are bundled with the installer and could not be re installed separately.
Is it technically possible (I don't think this would be restricted), and how do you go about it?
I got my little test app building fine, but when I run it I get a failure dialog.
The debug output is slightly more informative:
The thread 0xe4c has exited with code -1073741515 (0xc0000135).
The program '[3400] OpenCVTest2.exe' has exited with code -1073741515 (0xc0000135) 'A dependent dll was not found'.
Then I created a Win8 Desktop app, which also built fine but failed to run.
MSVP100D.dll is part of the VC++ 2010 Redistributable which is not compatible with Win8. (Being a hacker I tried it anyway, the installer runs to completion - but the bits aren't installed.)
Is there a compiler flag I can try? Possibly a custom build of OpenCV would fix it, but that would be a last resort, and it might only fix the desktop app.
This guy shows an example of using OpenCV library for performing face detection in a Windows 8 Store app written using C++/CX:
http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/DEV322
Also, at the below post he also describes how the C++ Runtime works for Windows 8Store apps:
http://blogs.msdn.com/b/vcblog/archive/2012/09/28/10354327.aspx
MSVP100D is not a part of VC10 redist. Note the "D" at the end of its name. That package only includes release builds. Your release builds should work fine. But mixing libraries from different VC versions might get you in trouble. See this. Your best chance is to build from source with VC11.
I am interested in trying to get a program ported to 64-bit and would like to know if it's even a good candidate for porting. I am a lighting director and have built a SUSE 11.1 Linux box for a program called MagicQ made by Chamsys (http://www.chamsys.be/download.html). I have been working on this for about 6 months now and have all hardware recognised. I am still working on stage visualizers, and I have a separate CPU/board generating the DMX512 code via PoE. I don't think getting it to run in SUSE will be a problem "it was natively built for Ubuntu".
Any help or direction is greatly appreciated!!
Unbuntu and Suse are subtlely different in how things are laid out for file sytems, home directories and such. Usually when you try to install a package on either on you need to use their own package manager programs so that all dependincies are handled and you don't need to manually try to find package 'x' version 'y' and package 'a' version 'b' just to get something working.
If you know that you have all the dependencies covered, and if you have the raw source code, you should be able to just run a compilier against the source code and have it compilied for a 64-bit processor.
Here is a link to the GCC, the GNU Compiler Collection for your reference.
Good luck with your porting project.