Is OpenNI 2 compatibile with Windows 8.1? - compatibility

I installed OpenNI 2 on my MacBook Pro that runs Windows 8.1 natively with Bootcamp.
The sensor does his job perfectly on an older white MacBook with Windows 7 and OpenNI 2 but when I try to run NiViewer on the newer MacBook Pro it just says it cannot find a device.

OpenNI 2.2 works perfectly fine on windows 8.1. I have tested it on a 64 bit Windows machine and I got good results. Check if you have installed all the drivers properly and try out all the USB ports.

The issue I had regarded specifically MacBook Pro Retina and ASUS Xtion. I'm not sure if all models are affected but it happened on my Intel i5 2013 and I think the same issue would apply to any OS.
The problem is due to some incompatibilities with (some or all I don't know) USB 3.0 ports.
The solution, luckily, is quite simple as ASUS, being aware of this, published a firmware update for Xtion 1080 which you can find here: ASUS Xtion Support Page (this link is for Xtion PRO but you can easily find the one for your device on ASUS website).
Obviously, as the Xtion won't connect to your laptop, to run the firmware update successfully you'll need to use another computer with OpenNI drivers installed so that your operating system can recognize the device and upload the firmware.

Related

Xamarin.Forms development with old Macbook Pro

I have a new Surface Laptop 3 for Windows development. I'm just starting to learn Xamarin.Forms and I'm using Visual Studio 2019. The device emulators work fine as does debugging on a physical Android. I'd like to debug on an iOS device. However, I only own a Late 2011 MBP (16GB RAM, SSD). I am limited to High Sierra and XCode 10.1. Is this Macbook good enough for me to at least debug and just learn Xamarin.Forms using iOS devices?
If you want to release your app some time soon, you'll be required to use the iOS 13 SDK (source). To use the iOS 13 SDK you'll need Xcode 11+, unfortunately
Xcode 11 requires a Mac running macOS Mojave 10.14.4 or later. (source)
And Mojave is not intended to run on devices older than 2012 (see here for example). Anyway, this does not necessarily mean that you can't use your old MBP at all. Even though Mojave is not intended to run on devices that old, people have been able to run it anyway. Have a look at dosdude1's Mojave patcher. I have been able to successfully install Mojave on my (early 2011) MBP and it works without any reason for complaint. However, since the OS is not intended to run on our MBP YMMV.
And please note (shamelessly copied from this answer of mine)
This is probably a violation of Apples ToS
If you want to release your application in the App Store you might still run into troubles (unlikely, albeit, still conceivable)
You'll have to trust dosdude1, the patches are not open source, as far as I can tell
The machine is not guaranteed to work as it did before

Xcode 10 iOS simulator slowing down entire system

Since the upgrade to Xcode 10 on my iMac, all newer iOS simulators (iPhone X and up) are running terribly slow, and the same is on with any other app running including Xcode.
I literally can't type a single character in Xcode due to the slow response time (one keyboard keypress takes 1-6 seconds until the character appears in the editor).
There doesn't even seen to be such a huge load on the machine:
Here's my system specification:
macOS High Sierra 10.13.6
iMac (27-inch, Mid 2011)
2.7 GHz Intel Core i5
12 GB 1333 MHz DDR3
AMD Radeon HD 6770M 512 MB
Has anyone else faced the similar issues? Any ideas how to have at least a normal usable workflow?
I've read somewhere, that you need a graphic card with metal support to work simulator of xcode 10 properly. I have the same issue on mac pro 5.1 with radeon 5770, which does not support metal. But on macbook pro 2013 it works fine.

Updating the Chrome NaCl SDK for a Different OS

I need to download (update) my NaCl toolchain on my Mac Mini, but I don't have internet access where I am. I'm able to get my Windows laptop to a Wifi hotspot, but I can't see any option to download a pepper version for a different operating system.
Does anyone know if this is possible?
The NaCl updater uses this file to search for downloads:
http://commondatastorage.googleapis.com/nativeclient-mirror/nacl/nacl_sdk/naclsdk_manifest2.json
If you examine the file in a text editor, you will see links to the different OS versions and you can download them using any computer.

Running iPhone 5 Simulator on Snow Leopard

I am running the iOS6 SDK on my mac running Xcode 4.2 on Snow Leopard using steps from this Stack Overflow post.
I'm now trying to get the iPhone 4" screen to work. I have been able to get iOS 6 to show up in the iOS simulator under the Hardware > Version menu. When I try to load an iOS 6 device, I get the error: "The simulated application quit" - "Click Relaunch to try again". It then gives me an option to switch to a different SDK. If I choose iOS6, it again crashes. If I choose iOS 5, it loads correctly.
I also don't have an iPhone 4" screen option under the Hardware > Device menu.
I have copied the iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.0.sdk folder from the Xcode Disk Image to my computer.
I'm not able to upgrade my computer past Snow Leopard.
So I need to be able to:
load iOS 6 in the iOS Simulator
load an iPhone 4" in the simulator
Problem is Xcode 4.5 on your mac.
The original post says how to run ios 5.1sdk on "Xcode 4.2 on Snow leopard".
Xcode 4.5 is not available on snowleopard.
Install Xcode 4.2 and follow the steps again.
Another idea is to use Virtual Box and run XCode in it. Of course, running OS X on virtual box is quite difficult and not entirely legal (although you do have a Mac, so it can be justified). You can follow this link if interested.
http://www.sysprobs.com/guide-mac-os-x-10-7-lion-on-virtualbox-with-windows-7-and-intel-pc
It's for windows 7, but you should be able to get it to work on OS X as well.
I VMware Fusion 5 (and maybe 4 also, I don't remember) allows Mac OS X Lion and Mountain Lion to run in a VM. So you could install VMware Fusion, and use it to run a virtualized instance of Mountain Lion. Since the hardware is virtualized, it shouldn't matter that your Mac doesn't support anything newer than Snow Leopard.
Performance will likely be poor, though - my experience is that you need at least 4 gigs of RAM for VMware Fusion to run smoothly. If your Mac is too old for Lion and Moutain Lion, it'll probably won't have that amount of RAM installed.
It's said that Xcode 4.2 is the last supported version on Snow Leopard. So no it won't work and you'll have to get Lion.
I found the answer on another StackOverflow post
You would have to be under Lion in this case with both Xcode 4.2 and
4.5 installed. There should be no problem with this.
Don't forget...
As stated in a Stack Overflow post
"I installed Xcode 4.2 on a Snow Leopard and when iOS SDK was published I imported the iOS 5.1 SDK" Look at another Stack Overflow post
Use the 2nd post link. It works perfectly, just copy "6.0" instead of "5.1".
Don't forget that you could just use an external iOS device that can run iOS6
You could always ask for support from developer.apple technical support
Delete your simulator and re-download

How to change intel BIOS screen from Ubuntu 11.04

I have dell voestro 220s series desktop computer with BIOS version : 1.2.2. Ubuntu 11.04 is installed on it. At the time of system boot it shows Dell voestro and Intel logo on the screen. I want to change this intel and dell voestro BIOS splash screen. I got the solution for widows system but I want to change it from my ubuntu 11.04 system. How is it possible ?
Thanks
amar
I believe the only way to do this is by changing the BIOS. Either you dump the original BIOS image (using for example a Linux live image with flashrom, like sysrescuecd) and open it with a HexEditor to search where the image is located (it's probably a Bitmap image), or you can consider changing the BIOS into an open source one (like Coreboot + SeaBIOS) and rebuild them to include a custom image (see this page for more info).
I should warn you that neither option is easy. The first involves low level "hacking" and tinkering (and is possibly dangerous), while the second depends mainly on if your motherboard is supported (unfortunately, most motherboards for Intel processors aren't) and how familiar you are with compiling stuff in Linux.
Hope this helps. =)

Resources