HAV requirement removed from Windows XP Mode/Windows Virtual PC
Hyper-Me
Banned Posts: 2,059
Windows XP Mode now accessible to older PCs - Born To Learn - Born To Learn - Born to Learn
Kinda cool, I guess.
Remember if you are taking 669 or another Windows 7 exam that references this that this change isnt reflected in those exams.
Kinda cool, I guess.
Remember if you are taking 669 or another Windows 7 exam that references this that this change isnt reflected in those exams.
Comments
-
earweed Member Posts: 5,192 ■■■■■■■■■□But it still wont run on home versions?
Sister in law has new Windows 7 Home comp and can't run her old SIMS (XP) games on it. Any way to get around this?No longer work in IT. Play around with stuff sometimes still and fix stuff for friends and relatives. -
Hyper-Me Banned Posts: 2,059You could install Virtual PC 2007 and run an XP VM but you would need an XP license.
-
earweed Member Posts: 5,192 ■■■■■■■■■□You could install Virtual PC 2007 and run an XP VM but you would need an XP license.
I actually have a copy of XP Pro here I could use. Only used a few times while VM'ing with Server2k3 while studying for my Sec+.
Would Sun VirtualBox work as well?
ThanksNo longer work in IT. Play around with stuff sometimes still and fix stuff for friends and relatives. -
Claymoore Member Posts: 1,637But it still wont run on home versions?
Sister in law has new Windows 7 Home comp and can't run her old SIMS (XP) games on it. Any way to get around this?
First, you could try running the program in a compatibility mode. Right-click on the shortcut, select the Compatibility tab, and choose an operating system compatibility mode. Compatibility modes are collections of shims from the ACT database.
Next, you can use the Application Compatibility Toolkit to create a shim that can make the program compatible. One of the most common shims is an Windows Version Lie where, when the application checks on the OS version, the shim lies and tells the program it is running in a different OS. There a lots of shims from which to choose, tools to analyze the programs, pre-installed compatibility fixes, and the ability to create shim databases for deployment with the application.
Download details: Microsoft Application Compatibility Toolkit
More information can be found over on Chris Jackson's blog
Chris Jackson's Semantic Consonance
Virtualization is really a last resort when it comes to application compatibility. Try using the ACT first and pick up some skills that will help you in corporate IT. -
earweed Member Posts: 5,192 ■■■■■■■■■□Virtualization is really a last resort when it comes to application compatibility. Try using the ACT first and pick up some skills that will help you in corporate IT.
Edit
The PC came with Windows 7 so I don't know if the MACT is really applicable. Just went over and got it to install but for some reason it says not enough memory. Her new PC has 2GB and her old PC had 1GB so it must be compatibility issue. I'll check out the Win 7 Forum to see if there are any answers there.No longer work in IT. Play around with stuff sometimes still and fix stuff for friends and relatives. -
JDMurray Admin Posts: 13,091 AdminYou could install Virtual PC 2007 and run an XP VM but you would need an XP license.
-
dynamik Banned Posts: 12,312 ■■■■■■■■■□I believe that's actually a violation of OEM licenses; I believe that would be acceptable with retail though.
-
Hyper-Me Banned Posts: 2,059I believe that's actually a violation of OEM licenses; I believe that would be acceptable with retail though.
It might be, although I have P2V'd older servers before that had OEM keys and even told MS this when I called to activate and they didnt seem to really care. -
dynamik Banned Posts: 12,312 ■■■■■■■■■□Yea, you're not supposed to be doing that either; that is also a license violation. The activation reps basically just ask if you have it installed on more than one system, so I wouldn't make licensing decisions based on their actions.
-
Hyper-Me Banned Posts: 2,059It was for temporarily moving legacy systems so the old hardware could be removed and new hardware put its in place,and then the VMs were shutdown and archived.
If MS gets upset over something running in a VM for a couple of weeks....well thats a little absurd.