probably depends on where you are, but here the employer is in the weak position.
* First of all you do this during your own free time (not company time) The company does not "own" you during your free time.
* There is no realistic way that the knowledge you gain during company time cannot be used further down the road (if that was so "experience" would not exist) You're only really in trouble if you start re-using code (and selling it) from your company. In this case it's probably even more beneficiary for the company as you will learn new things on your own time and bring that back in.
* Even if the contract states you cannot do something in the line of a competitive company, this can be narrowed down. Your company could be a development company for a reporting tool eg, but you can still develop and sell applications of your own (or your knowledge) as long as it is not directly (and competitively) related to reporting tools.
* The OS has nothing to do with it and if you have a laptop you're allowed to use it for personal use. (here they sell a laptop as extra-legal benefits on top of your salary). I rarely use my laptop for real personal use though.
But personally I think your main worry is that your software might be competitive to your company's. What you could do to be on the safe side is talk to HR and your boss to check if this is OK. I would recommend that even.
I'd require a written quitclaim from your prospective partner's day job, lauren, specifically releasing any claim to his work on your project before I'd let him contribute anything. There's no such standard form that I've heard of, but letting one corporate lawyer in the door will pollute the entire project. Most companies I've worked for in my life included a clause somewhere in the hiring papers to the effect that anything I produce of an intellectual kind, they own. The courts in the US have generally bent over backward here in the Colonies to favor the employer, even when it was perfectly clear that the company had no conceivable current or future interest. Trust nothing, unless it's in writing, and then take out insurance.
You don't likely want to try to VM your media center. First of all, you want to "see" your media center full-screen (which you can only do via a hyper-v window or RDP, which I doubt you want to do), and video/audio drivers are limited to the Hyper-V integration tools. If your trying to use WMC as a media server and not a media client you're likely fine, but if you are expecting to use it as a client, you probably won't get the results your looking for.
Windows 7 Virtual PC will not support x64 (if I remember correctly), so you won't be able to run the NOS necessary to run Exchange using Virtual PC. This means updating to Windows 8 (but then dealing with the lack of media center as you had mentioned), or using another VM tool. I ran VMWare on Windows 7 with a Windows Server x64 and it did the job.
I'm using this kind of configuration for years.
I started actually back on XP time, with the host running XP Media Center edition, with MS Virtual Server 2005 installed, which hosted a Win Server 2003 (for web server, ftp, SVN, mail server, etc).
Currently, my configuration is host running Windows 7 Ultimate (with Media Center) and VMWare Server, running VM with Win Server 2008R2
As a suggestion on VM server, it has two VHDs - one for OS and applications, and one for data, (where I have actually stored the FTP server root, the web sites, SVN repositories and mailserver root folder)
Nothing to do with your query. Virtual Box does not play at all when HyperV or VMWare are running. In fact, you will get BSOD. VMWare and HyperV don't play together either. VMWare and Virtual PC play together.
What peripherals do you need to share? Some VM engines want exclusive access to perihperals; others are willing to share.
Yes but that's because they're all 3 trying to do the same thing with the same hardware - i.e. opening it up for a virtual machine inside themselves. It would be just as silly to use the same port number across IP for ftp, smpt, pop, http, etc. You'd get corrupt data whenever something sends while something else is also sending, or a timeout.
Only with VM's it's much worse than a network port - stuff like shared resources (CPU cores, RAM areas, Discs, etc.) will not be handled in a consistent manner. DO NOT install 2 or more of those on the same machine, and NEVER run 2 together, pick one and make several VMs inside it.
The Windows Runtime is the API developers use for building Windows Store apps, sometimes
called WinRT. Don't confuse it with Windows RT, the ARM version of Windows 8. The Windows
Runtime API ensures apps can meet the design goals around portability, performance, and
trust and with it Microsoft can also ensure ...
I think we are left with just one option there : Get Confused
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
Over years I've heard 3 version for NT
1. N-10 === N-Ten, the codename for that version
2. Northern Telecom (Today Nortel), it has something to do with some patents that Microsoft used from NT in the low level
3. New Technology
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Dunno, I thought he might this morning, but there has only been one actual and one almost repost. The others have been more or less stuff relating to him. Leslie's death was re-reported for several days after it happened IIRC
The amount of energy necessary to refute bullsh*t is an order of magnitude bigger than to produce it.