Now, the only working operating system is Windows 10. When I go to my Pc in windows, I don't even see my hhd. Is there anyway to save this mess? I tried to unplug my ssd and see if ubuntu shows but nothing.
You probaly go two problems here, the first one is:
the only working operating system is Windows 10.
You probably just replace the default boot drive with the drive where Windows is installed, in this case, you will need to change the boot order, and place the HHD where ubuntu is installed as the first option on the boot order list, (this guide can give you some idea of how to do it. ) after this you will probably see the grub system selector page when your PC starts.
Now to the second problem:
When I go to my Pc in windows, I don't even see my hhd.
The reason that Ubuntu drive doesn't show up is that Windows and Ubuntu use different types of file system technology. Windows uses NFTS and Linux (Ubuntu, Debian, etc) uses EXT4, Windows doesn't support EXT4. To see the Ubuntu drive on Windows, you will need to divide the Ubuntu drive into two partitions, one EXT4 for Ubuntu and another one in NFTS.
I have installed Windows Server 2012 in my 3 Desktop PCs. I am using it for study purpose. In that PCs I need to install Ubuntu Desktop OS Like Dual OS. I searched in internet. All I got was Dual OS for Windows Server is possible with Windows 7, 8, 8.1 and 10.
Please help me to find a solution to install Windows Server 2012 and Ubuntu 16.04 LTS in Same Machine. Or else suggest me a Free OS Like Ubuntu which supports Dual OS with Windows Server 2012 in Same machine.
Thanks,
Rokesh
There are several ways to do that, the easiest is to have two HDs, physically, witch would be safer, during the installation you could detach the drive with Windows Server, install Ubuntu and then reattach the Windows HD. If this is not a possibility you could use the Windows partition tool to remove a part of the NTFS, you will have to make some research on this. Since you don't say either or not you have tried to do that all i can say is what I usually do:
1 - Windows Installation:
Boot from a flash drive containing the Windows.
In the moment I can select the drive in which I will install the SO, choose to change It then remove the existing partition, confirm.
Create a new partition with, in a case
like this, half the available size in the HD, install the Windows normally.
2 - Ubuntu Installation:
Boot from a flash drive with Ubuntu installation files.
Use the device boot list/options key, (in a desktop PC will be F8 key, in a notebook will vary, F11 and F12 are the most common).
In the boot list choose de flash drive to boot, follow the initial parts of the Ubuntu installation 'till the partitioning part.
In the disk option choose the empty space in your HD. You can let Ubuntu automatically create the set for you or manually do it.
Case you decide to try manually, create one small partition, like up to 30% of the space to the mounting point /, a swap partition with twice the size of you RAM memory, all the remaining space can be assigned to the /home mounting point, this way you can reinstall Ubuntu formatting the system partition and keep your data on /home.
This link, brought to us by JHBonarius, have a detailed step by step to do it with Windows 10 and 8.1. With Windows Server should not be too different.
I first created system images using Windows backup then realized that those VHD files cannot be booted using Virtual PC.
So I found the utility Disk2VHD and spent a few hours making a new VHD and tried booting it with Virtual PC but it too cannot boot.
It is giving the error:
PXE-E53: no boot filename received
I followed some instructions found online on going into the Virtual PC settings and ensuring I have the right vhd set up which I do, I also have integration features unavailable.
I then went into the Virtual PC's BIOS and in The Boot menu and it says under Hard Disk Drives [Virtual HD] and in the boot priorities the 1st boot device is the Hard Drive.
This VHD is created from my C: which is my main Windows install (Windows 7 Pro 64-bit)
The whole goal of this is I want to format my drive and install new Windows but I wanted to be able to make a bootable image I could go into later to recover things as needed and see how stuff was setup if I forgot.
When you converted it over, did you check in the checkbox which allows the file to be used in Virtual PC? I forget what it's called but in there is a checkbox you have to click in before you convert it over.
Also make sure the drive isn't bigger than 127GB or Virtual PC won't recognize it.
I was so happy today that I have been finally able to install Windows Phone 8 SDK and try it a bit. I installed fresh new installation of Windows 8 Pro into my virtual machine (I am running if from Parallels) and then installed Windows Phone 8 SDK.
Everything went smooth, Visual Studio Express is installed and running, but when I created new project and tried to deploy it, VS fails with really weird message.
First of all, message box informing that "The Windows Phone Emulator wasn't able to create the virtual machine: Generic failure" appears. Really informing, really professional - generic error, that's really good. Then the information that deployment failed appears (thanks a lot for keeping me informed about that, I didn't noticed that it crashed completely). And then in the Error List, there is an information about "Invalid pointer" - even better. No clue at all about what failed or what's wrong.
Can anybody help me with that? There is nothing on the internet about this topic so far and I don't know where the problem is. I scanned the Windows events and logs, but there is nothing (probably I haven't been searching properly, so please guide me through that if you can).
Anybody can help?
The Windows Phone 8 emulator requires hardware Hyper-V support. In particular, it requires second-level address translation, hardware assisted virtualization, and hardware DEP support enabled and to not be ran in a hypervisor(no nesting). If you bought your machine within the past 4 years you should have no problem with these requirements. You can check out this article to see more information about that and how to find if your PC supports it.
Because of these hardware requirements, this means you can't run the phone emulator inside of most virtualization technologies... With one exception: I've been using VMWare 9 which appears to include an "unsupported" feature to allow Hyper-V to work though.. So your only choice for running the phone emulator is to either buy VMWare 9 (or 8 with more configuration) or upgrade a physical machine to Windows 8
The unsupported way VMWare allows you to run Hyper-V inside of a VM is that there is a manual option (hypervisor.cpuid.v0 = “FALSE”) which basically tells VMWare not to report to the virtual machine that it's running in a VM. Hyper-V checks if it's running in a VM and won't work if it is, so this gets Hyper-V to work past that check. I personally have tested this whole nested-VM thing with the Phone emulator(including before public release), and other than being quite slow, it does work pretty well with no immediate crashes or anything.
There is a workaround for VMWare Workstation 8 as well in an answer below. However, 9 is much easier to configure, so if you have it use this method.
I ran into the same issue and I fixed it by enabling Hypervisor applications in this virtual machine and adding the following line to the .vmx file:
hypervisor.cpuid.v0 = "FALSE"
This got the emulator working just fine. I found this answer here.
Hope this helps.
Actually, it works quite nicely with VMware Fusion 5.0.1
All I had to do is to add to the .vmx file of the virtual machine the following lines:
hypervisor.cpuid.v0 = “FALSE”
vhv.enable = "true"
Save and restart VMWARE (obviously the VM must be stopped before the changes are made)
I'm right now debugging a test app from VS2012 using the emaulator inside a VM in my Macbook
I'm a happy camper
:-)
I posted the same question on Parallels forum.
Reply:
The emulator is actually a virtual machine, so we are talking about a vm inside a vm, this requires support for nested Hyper-V, which afaik is planned but not implemented yet, also VMWare Fusion already supports this, if you are so desperate.
————-
See Parallels forum post: http://forum.parallels.com/showthread.php?p=646448#post646448
This works for me
Set RAM to 4g
Set at least 2 cores
add to vmx file.
vhv.enable = "TRUE"
hypervisor.cpuid.v0="FALSE"
Goot article
http://social.msdn.microsoft.com/Forums/en-US/wptools/thread/ed72010c-321c-4667-97b2-3ff1540e7f87/
You need SLAT compatible hardware to run Hyper-V, which is a requirement for using the emulator.
Can you clarify what kind of hardware you're attempting to run this on, and if you have enabled Virtualization in your BIOS settings?
The "Invalid pointer" error just means it cannot connect to the emulator (and/or device).
Just as an addition to https://stackoverflow.com/a/13163762/1964969 (top answer at the moment):
manually appending "hypervisor.cpuid.v0" key works for VmWare Player 5 as well (the main reason - this software is free for non-commercial use so it's perfect product if you test the waters, just download from VmWare website and install, it's fully-functional).
Slightly unexpected, any of the following amends solve the problem with WP8 emulator:
hypervisor.cpuid.v0="FALSE"
hypervisor.cpuid.v0="TRUE"
hypervisor.cpuid.v0=""
Yeah, you can apply empty value for that key - but why? Have no idea but it works. I did some notes in my blog as well:
http://windowsasusual.blogspot.ru/2013/01/how-to-launch-windows-phone-8-emulator.html
Under Parallels Desktop 8 follow this guide: http://kb.parallels.com/en/115211
Edit:
Oh, I didn't noticed that you are trying to run emulator on VM. My answer is for non-VM environment.
First of all, you need to check hardware requirement at here
Be careful, successful installation of SDK does not guarantee "your hardware is compatible"
If your hardware is compatible and Hyper-V is running(described in the link above), please check your BIOS and be sure to enable hardware virtualization in CPU Configuration
(for me, I could find it at Booting > BIOS > Advanced > Advanced > CPU Configuration)
Brief summary:
64bit CPU and OS
4GB RAM
Hardware-assisted virtualization supported CPU
Second Level Address Translation (SLAT) supported hardware
Hardware-based Data Execution Prevention (DEP) supported hardware
Proper BIOS settings
For me the solution adding line:
hypervisor.cpuid.v0 = "FALSE"
I use VMware Player and added the line (hypervisor.cpuid.v0 = "FALSE")in the .vmx file.
My virtual machine with Windows 8 Pro runs the emulator for Windows Phone 8 perfectly.
Solved the problem by uninstalling an older VPN client from the machine. It turns out some VPN clients might have compatibility issues with Windows 8. After uninstalling VPN client I was able to run the emulator without issues (of course after making sure Hyper-V was installed and enabled on the machine)
Not enough rep. to comment on the accepted answer, but Microsoft provide instructions specifically for Fusion here. It worked for me, after a couple of reboots of both Mac and VM. I installed W8.1 without Hyper-V support initially and had to install it after the fact ("Turn Windows Features On or Off" in Control Panel), but apart from that no problems. Quite speedy on a 16Gb 2013 MBP.
I would like to check out Windows7 and install all of my developer programs on it just to test if everything works fine. In the mean time I want to continue my work on my Vista os. Is it possible, using Virtual PC, to install Windows7 and afterwards replacing my Vista installation with this Virtual PC Windows 7?
Take a look at using a bootable VHD. I have one with Windows 7 and use this as my "playground" for testing things like VS2010 Beta 2, Office 2010, etc. The VHD is a single file so it's portable and the performance hit for the virtualization is minimal.
Instead of running a Windows 7 VPC inside Virtual PC inside Vista, you are booting into a Windows 7 VPC - no Vista. works great for multi-booting. Once you're ready to move to Windows 7 as your primary OS, you can still use it in a VHD.
This link may help out...
http://4sysops.com/archives/how-to-add-a-windows-7-vhd-to-vistas-boot-manager-menu/
In theory, yes. Back up the virtual image, then restore it to your hard drive.
In practice you may find issues with drivers, specifically video, as effectively you're moving a Windows image from one "computer" to another.
You'll also need to make sure that the Windows license comes over properly - best to not activate it while it's virtual.
If it were my box I'd probably want to do this to a fresh hard drive, so I can fall back to Vista if all goes wrong. So rather than virtualize, I'd just buy a new hard drive and use that for Windows 7 straight away.
Have you considered dual-booting?
Also: Windows 7 was designed to be compatible like Windows Vista, unlike how Vista was sometimes incompatible with XP. You probably shouldn't have any problems with compatibility.