In this tutorial you can see how to extract the VHD image file of the Windows XP contained in the "Windows XP Mode".
The tutorial also explains how to run it on VirtualBox and it works nicely (no special parameter, you just add the disk).
But I want to run it on QEmu and there I get a blue screen.
This is the command I'm using:
qemu-system-i386 -m 1G --enable-kvm -drive file=VirtualXP.vhd
I tried to convert the image to qcow2, raw, ... same issue.
I tried x86_64... same issue.
I tried without --enable-kvm... same issue but the blue screen is covered partly by a black rectangle.
After the blue screen it restarts and allows me to choose safe mode. But all options give this identical blue screen.
When I boot the image with VirtualBox I noticed that the VM has already a driver installed to allow the use of the host's mouse cursor. I suspect that this image has VM guest drivers installed that are not compatible with QEmu and maybe make it crashes.
Important note: I don't have a Windows XP CD-ROM to help me.
Here is a screen shot of the blue screen (I suppose it will be the exact same error on all machines):
This might have to do with the drivers windows expects, there are various results using search engines to fix/repair this issue I found but they mostly boil down to:
Install standard IDE drivers
Registery edit to add these IDE drivers
If BSOD 0xCE
Remove Intelppm driver
Edit registery to reflect the removal of this CPU driver
I like the idea of a Windows XP image converted to another, for qemu. And it sounded awesome if this was a legal way. And I now know how they solved this. There is a 30 days trail period and after this, our downloaded image will nolonger boot. (unless you redo all your steps on a fresh copy that never has been started).
Sources to help you (and I ) anyway: https://learn.microsoft.com/en-us/windows/client-management/troubleshoot-inaccessible-boot-device
wich was to me very cryptic and what to do?
But it was also reverenced by the following more helpfull article, and i was almost capable of making a bootable harddisk image for qemu because of this: http://0x0badc0de.blogspot.com/2013/05/converting-windows-virtual-machine-from.html
But after some hours back and forth, I wasnt fully successful and even the author mentions the 30day trial. legal, maybe, but still troublesome.
There is however a key included and if you where to acquire a XP install disk, maybe able to obtain a successful install of windows XP with the same 30 days trial. Hope this answer helps you or any traveler to decide their own story.
I am taking over a project done under QT5 by someone else. The purpose of this program is to connect to a mySql server (5.5) running locally (on the same machine) and perform operations. It does that by connecting to the ip Address of the machine it is installed on.
One major bug of this program is that, when it is running on a 32bit platform e.g. win7 32 bit, it connects to the mySql database just fine. But when it is running on a 64bit win7 and the mySql database became a 64bit one too, it consistently fail to connect.
We setup several machines running win 7 64 bit OS to make sure that it wasn't anything accidental and sure enough it wasn't, except one of these machines happens to be my work computer and strange enough the program connects just fine. In other words, the program is connecting to the 64bit build of mySql 5.5 server correctly on a win 7 64 bit platform, something it failed consistently on all other machines.
We also noticed that the connection will not take place properly if we run the program and the mySql server on a freshly installed win7 64 bit OS.
Based on that I suspected that it it is because of all the software that I installed on my machine. But so far installing a copy of Qt5 development suit on a freshly configured machine did not solve that problem, which was quite surprising because it is quite reasonable to assume the Qt5 brings with itself files needed to perform certain operation correctly.
Can anyone please shed some light on how to proceed next? I'm quite helpless here and I don't even know the general direction to move on next.
i have been working on a project using Visual Studio 2015 along with vb.net and mysql. I deployed my application using ClickOnce to my company server then installed on all the computers in my company. It is working fine. Recently, i have it installed on three new computers which has the exact same os and specs with the existing computers, however, the application installed on the three new computers showed a very significant difference in performance comparing to the existing computers, it is much slower in the new computers.
I have checked through
the networks
the connection to MySql database
the memory it consumes
the .net framework version
but it is all exactly the same with the existing computers. does anyone have any idea what might be the cause? Or anyway to troubleshoot this problem?
Just add timers, stopwatches, etc to instrumented builds. In fact, in an application of any size I build-in, from the off, at least a skeletal diagnostic system with a display window and stopwatches that can be used to time specific bits of code - typically database queries. With that in place, it's simple to add specifics to produce instrumented builds to drill down to any problems that only occur on end-users' machines. You can also download DbgView from Microsoft and use that in conjunction with Trace statements in your code.
I've been trying to get the emulator to work for days. Previously I tried the Windows Phone 8.1 Emulator as well as the Windows 8.1 Simulator and both were stuck at loading the OS.
Earlier today I installed the new Windows 10 Tools and thought I should give it another try with the new Windows 10 Emulator... And no, still the same result.
What's strange is that, the Hyper-V Manager seems to be doing OK. I can see the app displays correctly on the little Preview window (see the box on the left side of the picture below).
Also, breakpoints are hit, the project seems to be running OK.
As many answers have already suggested, I tried letting it running for an hour, but still nothing came up.
Things that I've also tried include uninstalling all the Virtual Machines as well as repairing the WP 8.1 Emulator, nothing has worked so far.
Please help, this has driven me completely insane. :(
Update
Not sure if this would help, but if I change the Windows Phone Emulator Internal Switch to use Private network instead of Internal, I will get a couple of warnings saying Unable to determine the Host IP address and then the Emulator will show up with the Emergency Call screen. Not much I can do from there as the three buttons on the bottom are not functioning at all.
I understand that changing the connection type is not the right way to do it, but this at least tells me that the Emulator can work, it's just a matter of how.
I believe you have two Windows Phone Internal Switch connections and one seems to be unplugged while the other is running. Disable the one that is unplugged and leave the latter. This worked for me after 2days of tinkering. God speed.
Try the following.
Open the Hyper-V Manager
In the Actions pane, click Hyper-V Settings
In the Server pane, select Physical GPUs
Uncheck, Use this GPU with RemoteFX
Click OK to save/close.
Attempt to start the Windows Phone emulator VM from within Hyper-V Manager or Visual Studio.
I solved this problem by simply adding XDE.EXE as an exception to my Windows Firewall.
Just today
Many times it is not stuck. It just does take too long to start. I have an 8 core processor and it took like 5 minutes to launch, I tought it was stuck but it did launch.
Not sure if this would help, but if I change the Windows Phone
Emulator Internal Switch to use Private network instead of Internal, I
will get a couple of warnings saying Unable to determine the Host IP
address and then the Emulator will show up with the Emergency Call
screen. Not much I can do from there as the three buttons on the
bottom are not functioning at all.
when you set it to private network, Windows can't interact with your WP Emulator. Open Network Adapter, and try disable and try start emulator again, then enable again this adapter if it is not work *
I contacted the Visual Studio Team a couple of weeks ago and looks like they have fixed this issue in the latest update. And here is how I finally got it all working.
Update your Windows 10 TP to the latest version (currently 10074).
Install the latest Visual Studio 2015 (currently RC).
Install Windows 10 developer tools preview from here (I got
some weird errors with Error code: -2147023294. Ignore them, go
straight to the next step).
Install the standalone Windows SDK for Windows 10 Insider
Preview from here.
Install the Pre-release Microsoft Emulator for Windows 10 Mobile
from here.
That's all! After all these are done, both my Simulator and Emulator are loading up fine.
In my case, deleting the internal switch from Hyper-V virtual switch manager helps, whenever you run your app using emulator as the target, it'll add a new internal switch by itself and the emulator will run normally (no longer stuck on loading screen)
The problem is, I have to do it every single time I restart my PC
The workaround steps to install the Windows SDK and Emulator are no longer needed.
We have released a fix as of 7PM PDT 30 April 2015 for the setup error
Windows 10 SDK 10.0.10069 : The installer failed.
User cancelled installation. Error code: -2147023294"
New setups should no longer encounter this issue.
For existing installations, and for more information, see this forum post:
https://social.msdn.microsoft.com/Forums/en-US/17bc9d5e-2ea7-4149-bb75-23997db8bd25/
This worked for me:
Go to Windows Defender.
Add exclusion following path: "C:\Users\UserName\AppData\Local\Microsoft\XDE\YourEmulatorVersion"
YourEmulatorVersion - for example 10.0.14393.9
2 days, tried all that is posted here but nothing worked! Finally, since it is a lot easier nowadays to (re)install windows without loosing your files (3 hours including updates), I just resorted to that. Same thing happened, but then I saw the alert that I had not yet activated my VS to run in developer mode :) Did that, and voila, the emulator now works.
If this might be helpful: my problem started when I installed Android Studio and disabled Hyper-V from Android. Enabling it back for VS just couldn't get me to run it again. But I hear there is a way to run both Android & VS emulators using VS emulator for Android. I will try to see how that works later...
I know the question is old, but none of the above answers worked for me so I write down my two cents:
Go to Hyper-V console and remove all emulators
Go to Devices Management, under network adapters tree node, delete all virtual switches
Run an emulator from Visual Studio and see the magic happen
I decided to start developing for Windows Phone, downloaded Visual Studio 2013 with Windows Phone SDK and in finishing window installer said that I can`t use emulator because of not SLAT-compatible computer. What should I do?
I found Windows Phone 8 Emulator on non-SLAT Machines and now I ask Is it really a solution:
It works, but not on Windows 8. Windows 2012 server uses hyper-V version without requirement of SLAT.
So:
Windows Server 2012 trial (i use Developer version).
Installed on physical device - not on VM.
Install slat-less feature Hyper-V. Standard WP8SDK.
And voila. It worked like a charm. And it's kinda fast. First emulator on list in VS loads about 30 sec. More advanced take longer but not much. Deploying is instant. Give it a try if youre not to buy phone or new computer :)
Yes it's possible to develop apps on a machine without SLAT. It is not, however possible to run the emulator (in any kind of supported manner) on such machines.
It is possible to develop without an emulator though. You'll just need an actual device to test on.
This shouldn't be a barrier though because even if you have an emulator you should always test on a physical device. It's just a little bit more awkward to use a physical device sometimes.
On the plus side a physical device will let you test some things that the emulator can't. e.g. proximity
But on the downside the emulator makes it easier to test other things, like location changes or how the app will look on different resolution devices.