We’ve been trying to get SikuliX 2.0.5 to run on a RHEL 8 system, and not having much luck.
We went through the instructions on this webpage:
https://sikulix-2014.readthedocs.io/en/latest/newslinux.html#newslinux
We started on RHEL 7, but the OpenCV shared library required a newer version of GLIBC than is standard on RHEL 7 (version ‘GLIBC_2.27’ not found (required by ~/.Sikulix/SikuliLibs/libopencv_java430.so)), so we moved up to RHEL 8. We had to build OpenCV (v4.3.0) from source because we could not find a java companion package for RHEL 8, which required quite a few other dependencies, but in the end we got it built with most options enabled, and installed as root on the system. We also got Tesseract installed via a package, as well as xdotool and wmctrl.
We are setting LD_LIBRARY_PATH to ensure that the OpenCV libs are picked up, and when we run with the “-v -c” options to the IDE, there are no obvious problems reported. It seems to believe it is moving the mouse, though we can see that it is not, and when we try to capture a screenshot, the “canvas” from which to capture is either uninitialized/garbage frame buffer memory, or a totally black screen. On rare occasions we have seen the actual desktop, but most times we do not.
Originally the system had 2 monitors, but was subsequently reconfigured to a single display system. We were originally running remotely over NoMachine, but have also tried running locally and observed no difference in behavior.
Any pointers or suggestions would be most welcome. Given that no error messages are being reported, we are out of ideas for how to proceed in debugging the problem. It appears that more native support is provided for Debian-based systems, but we’re attempting to validate a product which only advertises support for RHEL systems, so we’d prefer to get it working in this environment if at all possible.
First off I used to be an XP guy and I still have the copy that I bought back in 2002. I had to downgrade my computer to an old iMac I had in storage and the only copy that I have of XP (I really do not want to buy a new one) is the old copy. I installed into a fully formatted drive and then realised that this XP disc came out before service pack 1. Which means that there really is no support for this. Next I noticed that the ethernet driver is unrecognized (big shock) therefore I have no internet, so I cannot install using windows update. Therefore I do not have any updates (again this disc is very old) and no access to the internet.
I have another computer that I can burn discs off of and it has the internet but I will not have it for much longer.
The device I installed the XP on is an 20-inch iMac (Early 2006), 2.0 GHz Intel(R) CPU T2500 with 1.98GB RAM
Is it possible to update my machine and be able to do use it the way it should be?
How I managed it was that I downloaded found an executable version of SP1a and then updated the system by moving the file over, then I downloaded the service pack SP3 ISO, updated the system.
However it didn't fix the ethernet driver and since I had no idea what the controller's actual name nor the company that made it, I moved over the Auslogics System Information, did a diagnostics took the problem devices "Value" and did research in order to find the needed information, and got the driver and moved it over. Yay monotony.
We recently moved from Windows XP to Windows 7 and ever since the move I've found that I can't run the !dlk command from Sosex in WinDbg anymore, it simply runs forever. It used to be a handy way to catch deadlocks in our code.
Did something change in Sosex that I should know about?
We're on Windows 7 64 bit debugging a crash dump from a x86 process that ran on a Windows 7 64 bit machine.
In the meantime I can try and work through !syncblk, but !dlk was sooooo nice.
As Rockstart said in a comment, major performance improvements have been made to SOSEX in recent weeks. Please let us know if you continue to have difficulty with the latest version of SOSEX. You can also email the address listed in !sosex.help for support.
I am trying to run an app I created at work (I sent myself the .exe file) so that I could see how it looks on Windows 7.
My laptop (running 64-bit Windows 7) won't even open it, though. It opens some compatibility wizard to try to rectify whatever the problem is, but that doesn't work either.
Is there anything I need besides the .exe itself, that I should have copied over?
A team member using Windows 7 can run it (by checking it out of Subversion and running it in the VS IDE, anyway), but the display if "off" (The FlowLayoutPanel's controls are experiencing a kind of "wardrobe malfunction"). But I, as mentioned, can't even run it.
What might be the problem/solution?
If you are running the Professional edition of Windows 7 or higher then it will include the option to install the "Windows XP Virtual Machine". You can then run your app as normal under the virtual machine, quckest and easiest way to resolve these sort of issues in Windows 7.
It seems that the Windows Phone 7 SDK doesn't support running inside a VM. On Parallels, the entire VM simply crashes when the emulator is starting up.
Around the web, though, a few people have reported that they were able to use it by changing a lot of the VM settings.
What do I have to change to be able to run it? I'm specially interested in Parallels, but VMWare or any other simulator that run on OSX if fine for me!
The WinPhone7 (and WinPhone8) emulator is itself a VM and few (if any) general-purpose VM's will host another VM infrastructure, which is why it crashes Parallels etc.
If you want to have the emulator run from within a different VM to the one MS provides, then you're into the realm of extracting images, toggling bits and trying to tack it into your VM of choice. Of course, the chances of the emulator then working as expected with no residual issues is as close to nil as makes no difference ;)
[Update 2013-01-30] VMWare5 & Parallels Desktop 8 now support running Hyper-V guest VM's. This is particularly useful for those wanting to develop against the Windows Phone 8 SDK which runs Windows Phone 8 guest VM's on Hyper-V.
Here's a guide to how to run Visual Studio 2012 & Windows 8 SDK (inc. the Windows Phone 8 Hyper-V-based emulator) in VMWare5 or Parallels desktop 5: Link
Note: Running Windows & Hyper-V inside a VM will be slower than running natively. Dual-booting into Windows (using Boot Camp on OSX) is stil the recommended method of developing for the Windows platform, especially if you want to use Hyper-V guest VM's.
I'm working in VMware Fusion with Expression Blend 4 RC AND the emulator.
works like a charm!
As others have said, WP7 is itself a virtual machine. Even if you can get it to run inside a virtual machine like Parallels, the performance will be abysmal. If your computer supports hardware virtualization, the emulator runs really smooth, without it it's very very sluggish. Running it inside another VM will make it even more sluggish - I am guessing to the point that it's unusable.
I know this is not the answer you want to hear, but I would recommend running Windows in Bootcamp, you will have much better experience developing and emulating.
I'm not so sure about compatibility for long term development, but in last september, I remembering trying the Windows Phone 7.1beta SDK on VirtualBox (I'm using mac SL), a free virtual machine from oracle (previously by Sun) and it works well there.
I just do a regular install of Windows 7 Home Basic (any Win7 except Starter will do, CMIIW) in the VBox with no tweaking at all, install the GuestAddition inside win7 (provided by VBox), then install the SDK. I create new WP project, arrange UI, make some codes as usual, then run it in emulator. Surprisingly, the emulator works fairly well and showing the app I've developed.
I'm not even experience any lag (my macbook is i5, 4GB ram, the VBox setting is dual core, 2GB ram, note that no other heavy mac process is on the run, so I solely run the VBox ... and iTunes for listening musics).
So if you still want to try WP SDK 7.1 on VM, why don't you try VirtualBox? My current VBox is installed with Windows 8 and have no extra space to reinstall the win7+WPSDK. If you do give a try on VBox, please report the result here to inform everyone.
I've run the Android emulator inside a VM before. It was slower, but still usable to test basic apps. Also, the Android emulator was then slow to where you couldn't tell a difference from between native or from within running Eclipse from within a virtual machine running Linux
x86-to-x86 emulation tends to be pretty fast nowadays due to both Intel and AMD CPUs having hardware to help it along. A lot of x86-to-x86 emulation also doesn't do a full emulation (see Android's emulator to see how a full emulator runs in comparison). In the x86-to-x86 case, the faster ones will try to pass as many instructions to the host OS so that a chunk of the code runs natively
People have made claims like 80-95% performance, which is pretty good. If you have a 3.2 GHz CPU, you get knocked down to around a 2.4 GHz equivalent of your CPU. That's not bad at all, and I honestly don't notice that much overhead running in a good x86-to-x86 VM
The biggest reason why the WP emulator has problems with VMs doesn't have to deal with it being a VM-in-a-VM, but it's most likely that it requires DirectX 10. This might have to do with XNA, which is Microsoft's really nifty gaming API that lets you easily port between Windows, WP, and the Xbox 360. A lot of VM programs don't support hardware 3d acceleration
On another note: if you want to use a low-end system, AMD CPUs may fare better since AMD doesn't tend to disable hardware virtualization features in their lower-end CPUs
If you're deploying to a device, you should be able to use a VM, since it's the emulator that has issues being a VM itself.
We have successfully deployed, and performance is acceptable in our environment, virtual Windows 8.1 Pro Desktop under VMware vSphere 5.5 (ESXi 5.5), and have the Windows 8 SDK and Emulator working correctly with no performance issues. (In Education - to University Labs for Windows Phone development).
The issue experienced by most, is you most have the Hypervisor pass through the Intel-VT into the VM, to effecticely create Nested Hypervisors. This is possible using VMware vSphere 5.5.
This option is available in virtual machine version 10, enabled in the vSphere Web Client - Enable Hardware Virtualisation.