Urbiduino-urbi-launch.exe stops responding - arduino

I'm tesing Urduino but can't make it work.
Run urbi.bat
Either run the .u script or loadModule("Arduino");
Error: urbi-launch.exe has encountered a problem and needs to close.
I have tried with Win8 64bit, Win 7 and XP SP3 32 bit. All have the same problem.
Thanks if you can find me a solution.

It's currently only compatible with Urbi 2.7.5 We can use an older Urbi version.

Related

An error occer when call a Java Stored Procedure in c-treeACE

When I call a Java Stored Procedure in c-treeACE SQL Explorer, for example: call myProc(), an error happened:
Error : -20160    Error Description : Java SP/T Feature not supported.
My environment:
OS: Win 10 64bit
c-treeACE: V11.0.0 32bit
JDK/JRE: jdk1.6.0_31 64 bit, or jdk 1.8 64 bit, or jdk 1.6 32 bit
Also, I have already Setting in ctsrvr.cfg for Java Stored Procedure
Support(also restart the c-treeACE service):
SETENV  CLASSPATH=D:\Work\Db\d3dxsapi\Java\jre6\lib\rt.jar;C:\FairCom\V11.0.0\win32\bin\ace\sql\classes\ctreeSQLSP.jar
SETENV  JVM_LIB=D:\Work\Db\d3dxsapi\Java\jre6\bin\client\jvm.dll
SETENV  JAVA_COMPILER=D:\Work\Db\d3dxsapi\Java\jdk1_6_0_31\bin\javac.exe
Any one know this, could you please help me? Thanks!
I used another jdk 1.6(32 bit) to figure it out.  

MSXML 6 IServerXMLHTTPRequest.Open Fails on WIndowsEmbeddedPOSready7 & windows7 Pro

Application that uses MSXML6 IServerXMLHTTPRequest.Open Fails when run on machines with OS WIndowsEmbeddedPOSready7 & windows7 Pro. Works fine on Windows 8 and Windows 10. I have installed MSXML 6 on all the machines. The application creates the object ok on all machines but the open fails on machines running OS
WindowsEmbeddedPOSready7 & Windows7 Pro
Turns out a URL of http://10.1.1.61:10009 is fine for windows 8, windows 10 but on windows 7 and POSReady7 and XP SP3 the open will fail.
If you add a / to the end the open worls on all OSs.
So http://10.1.1.61:10009/ solves all the problems. The cryptic result from the open of
lResult& = OBJRESULT returns -2147012891 does not tell you much. It was pointed out to me that if you search the web, but use the hexadecimal value for the search you can find out the error means Invalid URL?

Parallel detectCores() giving incorrect output on a Virtual machine

I'm just doing some performance testing on a new laptop. My problem starts when I tried to test it on parallel computing.
So, when I run the function detectCores() from parallel the result is 1. The problem is that the laptop has an i7- 4800MQ processor which as 4 cores.
As a result when I run my code it thinks that it has only one core and the time to execute the code is exactly the same as without the parallelization.
I’ve tested the code in a different machine with an i5 processor also with 4 cores using the same R version (R 3.0.2 64 bits) and the code runs perfectly. The only difference is that the new computer as installed windows 8.1 while the old one has windows 7
Also, when I run Sys.getenv(“NUMBER_OF_PROCESSORS”) I also get 1 as an answer.
I've search the internet looking for an answer with no joy. As anyone came across this problem before?
Manny thanks
Make sure you are loading the parallel package before running detectCores(). I also have an i-7 processor (Windows 8.1, 64 Bit) and I am able to see as 8 cores when I run detectCores(logical = TRUE) and I get 4 when I run detectCores(logical = FALSE). For more, kindly refer this link. HTH

TypeInitializationException when running my application with Caliburn.Micro.Platform on Win 7?

I have an application that runs fine on my Win 8.1 development machine but when I go to install it on my Win 7 64 bit test box I run into a TypeInitializationException with Caliburn.Micro.Platform. What could be causing this? the error log that leads me to believe it is Caliburn.Micro is below.
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7601 Service Pack 1</Build>
<Product>(0x30): Windows 7 Professional</Product>
<Edition>Professional</Edition>
<BuildString>7601.18409.amd64fre.win7sp1_gdr.140303-2144</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ParentProcessInformation>
<ParentProcessId>2356</ParentProcessId>
<ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath>
<ParentProcessCmdLine>C:\Windows\Explorer.EXE</ParentProcessCmdLine>
</ParentProcessInformation>
<ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>MyApp.exe</Parameter0>
<Parameter1>0.6.25.0</Parameter1>
<Parameter2>546dfbc7</Parameter2>
<Parameter3>Caliburn.Micro.Platform</Parameter3>
<Parameter4>2.0.1.0</Parameter4>
<Parameter5>53f41236</Parameter5>
<Parameter6>92</Parameter6>
<Parameter7>0</Parameter7>
<Parameter8>System.TypeInitialization</Parameter8>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.1.7601.2.1.0.256.48</Parameter1>
<Parameter2>1033</Parameter2>
<Parameter22>2b5c</Parameter22>
<Parameter23>2b5cea20275728230acc663702d2e8da</Parameter23>
<Parameter24>5bd8</Parameter24>
<Parameter25>5bd8dc1fa50918888316b6b5f643c5e9</Parameter25>
</DynamicSignatures>
<SystemInformation>
<MID>BA765621-6E94-49A3-BF5C-4CA9CB339779</MID>
<SystemManufacturer>Microsoft Corporation</SystemManufacturer>
<SystemProductName>Virtual Machine</SystemProductName>
<BIOSVersion>090006</BIOSVersion>
</SystemInformation>
</WERReportMetadata>
And you are building against .NET 4.5, and you have the assemblies all correctly referenced. The one that tends to pop out is the Interactivity assembly, it gets buried hard to detected. Since it is a .NET usually version changes between Windows version. Can only suggest it is missing or a version number needed mismatch. Make sure the one from the lib folder in your packages from nuget is present on the install of your WIN7 box. If that is how you got the CM framework. otherwise pull the latest github release

LLVM ERROR: Cannot yet select: error

Hello i am getting the following error when I am running my app in the simulator.
LLVM ERROR: Cannot yet select: ...
It seems that other have reported similar issues for the same combo:
* New sandy bridge MBP
* Iphone 4.3 Simulator
* opengl
Anyone have some clue?
Here is a short excerpt from the log:
LLVM ERROR: Cannot yet select: 0xa0237d8: v16i8 = bit_convert 0xa02aa48 [ORD=259] [ID=170]
0xa02aa48: v8i16 = X86ISD::PSHUFLW 0xa02a828, 0xa02a608 [ID=166]
0xa02a828: v8i16 = X86ISD::PSHUFHW 0xa0235b8, 0xa02a608 [ID=162]
0xa0235b8: v8i16 = llvm.x86.sse2.packssdw.128 0xa023530, 0xa0234a8, 0xa023420 [ORD=256] [ID=158]
0xa023530: i32 = Constant<647> [ORD=256] [ID=21]
0xa0234a8: v4i32 = bit_convert 0xa023310 [ORD=255] [ID=139]
0xa023310: v4f32 = llvm.x86.sse.cmp.ps 0xa023200, 0xa028d70, 0xb03c4e8, 0xa023288 [ORD=252] [ID=130]
0xa023200: i32 = Constant<784> [ORD=252] [ID=19]
I'm getting this same error. I just got the new sandy bridge MBP today, and on my previous computer, I do not have this problem.
Changing the target to iPad 4.2 instead of iPad 4.3 resolves the issue.
Here's how to change the target in the new version of Xcode:
http://developer.apple.com/library/mac/#documentation/IDEs/Conceptual/Xcode4TransitionGuide/Orientation/Orientation.html
I had the same Error on my MacBook Pro Intel Core i7 in the 4.3 simulator. I updated to Xcode 4.0.2 and now its working again.
This means that LLVM cannot do the instruction selection for some code. Usually this happens when you request some target-specific stuff in the code and disable the features via cmdline.
For example, if you'll use sse2 gcc intrinsics, but will compile for, say, i486, the same sort of message might occur (if not caught earlier by a frontend).
It's hard to say anything more definite without the full error line.
I had the same situation. It looks like a bug of LLVM 2.8 for the new sandy bridge. The work around is to use 4.2 simulator as NoEvilPeople said.
OpenGL apps exit in 4.3 Sim but work...
MacRuby build issues with LLVM
Attempt to force LLVM to treat sandy bridge as core2
In case this helps anyone, I was having the same problem too, but don't have the older SDK for the other fix here. Kazuki posted a link to a discussion over at Apple, and it looks like its a bug that a few people have reported, but that it has something to do with the simulator. That being said, the app I was having a problem with runs fine on-device for me, so that's another potential workaround while this is looked at more.

Resources