Windows 8.1 Pro - installed Hyper-V
 

As I reported yesterday, today I'd be working on getting Hyper-V
running and install a VM WinXP. Because I'd never done that before, I
was nervous and really wasn't sure what to expect.

FWIW, I found two articles that I found very useful. They provided
step by step instructions with screenshots to highlight the
instructions.
http://www.techrepublic.com/blog/win...-hyper-v/6690/

and
http://www.techrepublic.com/blog/win...-hyper-v/6732/

With one or two exceptions, things went smoothly. As far as I can
tell, Hyper-V and the VM WinXP are working as expected. I still have a
long way to go, but the biggest hurdle seems to be over.

John

Windows 8.1 Pro - installed Hyper-V
 

Yes wrote:
As I reported yesterday, today I'd be working on getting Hyper-V
running and install a VM WinXP. Because I'd never done that before, I
was nervous and really wasn't sure what to expect.

FWIW, I found two articles that I found very useful. They provided
step by step instructions with screenshots to highlight the
instructions.
http://www.techrepublic.com/blog/win...-hyper-v/6690/

and
http://www.techrepublic.com/blog/win...-hyper-v/6732/

With one or two exceptions, things went smoothly. As far as I can
tell, Hyper-V and the VM WinXP are working as expected. I still have a
long way to go, but the biggest hurdle seems to be over.

John

Hyper-V requires SLAT. I could not install Hyper-V on my "pitiful"
hardware, because my processor doesn't have SLAT.

And it's handy to understand what happens when using a Hypervisor.
*All* OSes running on the computer are "Guest OSes". That means,
even Windows 8.1 is a Guest OS. And Windows 8.1 has the same status
as your WinXP does. The Hypervisor is the "boss", and everything else
runs underneath it.

SLAT (second level address translation) is part of enhancing
the performance of the graphics card. Since Windows 8.1 is
now a guest, it shares the video card with other OSes. It
doesn't have a privileged position, when playing a 3D game
on the computer. This could mean a reduced frame rate,
something you could have tested for, before installing
Hyper-V. (Do a before and after test, like run 3DMark
before and after, and see how much slower it is.)

So unlike other virtual machine environments, where the
"guests" go through some graphics emulation layer, the
model is a bit different when Hyper-V is involved. If
you don't notice anything, all is fine and dandy.

Note that some executables you download, they do a
check of the environment. As an example, when working
on an encrypted transport stream problem (.ts file),
I downloaded a program called TSDoctor, which has
a trial period. As is usual with programs of
unknown trust, I loaded it in a VM for testing.
It refused to run (presumably, to prevent a user like
me from using the trial period over and over again,
via throw-away VMs). If I wanted to use it, I would
be required to install it on my "main" OS.

When you load that program on your new Hyper-V setup,
it will run in *no* OS for trial purposes. Because the
status of all OSes, is they're all guests. You can test my
hypothesis if you want. If you purchase a license key
for the program, then you can run it where you want.
Or, so it's claimed.

http://www.videohelp.com/tools/TS-Doctor

So your new Hyper-V, does make a tiny difference
to programs wired up like that one. I'm sure the
author of that program, spent more lines of code
"arming and protecting it", than actually working
on transport streams.

Paul

Windows 8.1 Pro - installed Hyper-V
 

Paul wrote:

Yes wrote:
As I reported yesterday, today I'd be working on getting Hyper-V
running and install a VM WinXP. Because I'd never done that
before, I was nervous and really wasn't sure what to expect.

FWIW, I found two articles that I found very useful. They provided
step by step instructions with screenshots to highlight the
instructions.

http://www.techrepublic.com/blog/win...-hyper-v/6690/

and

http://www.techrepublic.com/blog/win...-hyper-v/6732/

With one or two exceptions, things went smoothly. As far as I can
tell, Hyper-V and the VM WinXP are working as expected. I still
have a long way to go, but the biggest hurdle seems to be over.

John

Hyper-V requires SLAT. I could not install Hyper-V on my "pitiful"
hardware, because my processor doesn't have SLAT.

And it's handy to understand what happens when using a Hypervisor.
All OSes running on the computer are "Guest OSes". That means,
even Windows 8.1 is a Guest OS. And Windows 8.1 has the same status
as your WinXP does. The Hypervisor is the "boss", and everything else
runs underneath it.

SLAT (second level address translation) is part of enhancing
the performance of the graphics card. Since Windows 8.1 is
now a guest, it shares the video card with other OSes. It
doesn't have a privileged position, when playing a 3D game
on the computer. This could mean a reduced frame rate,
something you could have tested for, before installing
Hyper-V. (Do a before and after test, like run 3DMark
before and after, and see how much slower it is.)

So unlike other virtual machine environments, where the
"guests" go through some graphics emulation layer, the
model is a bit different when Hyper-V is involved. If
you don't notice anything, all is fine and dandy.

Note that some executables you download, they do a
check of the environment. As an example, when working
on an encrypted transport stream problem (.ts file),
I downloaded a program called TSDoctor, which has
a trial period. As is usual with programs of
unknown trust, I loaded it in a VM for testing.
It refused to run (presumably, to prevent a user like
me from using the trial period over and over again,
via throw-away VMs). If I wanted to use it, I would
be required to install it on my "main" OS.

When you load that program on your new Hyper-V setup,
it will run in no OS for trial purposes. Because the
status of all OSes, is they're all guests. You can test my
hypothesis if you want. If you purchase a license key
for the program, then you can run it where you want.
Or, so it's claimed.

http://www.videohelp.com/tools/TS-Doctor

So your new Hyper-V, does make a tiny difference
to programs wired up like that one. I'm sure the
author of that program, spent more lines of code
"arming and protecting it", than actually working
on transport streams.

Paul

Hi Paul,

I'm glad you saw my post my experience (all of one day so far LOL
:-) with Hyper-V. I remember you had cautioned that it might not work.

The concept that software with trial periods might be designed to not
work in a VM environment had never crossed my mind - honest. I'm not
sure if that will create issues for me down the road. At present I'm
installing the software I used on my XP to either Windows 8.1 or to the
VM WinXP I made. I'm doing that piecemeal fashion, especially since
I'm not under any deadline to get things done.

Once I get that settled, I'll probably become adventuresome and try to
set up VMs to run some variant of Linux, Warp, AmigaDOS and BeOS and
maybe even one to play around and resume learning programming. I'll
see how any of that plays out. I remember coding a program for a class
one time that ended up barfing my pc :-) Using a VM would hopefully
keep that type of accident from spilling over to my real world set up
:-)

I have a learning curve ahead of me just to get used to how networks
and VM on my pc work and can be administered. It's a very big leap for
me. For years my pc and software were in use as a single user, single
pc, no network. Even my devices were connected using wire instead of
wireless. I never had any compelling reason to spend the bucks for
that type of overhaul of my equipment. I had Internet access of course
but that didn't really get involved learning, configuring and
administering a network much less two or more networks for that matter.

John

Windows 8.1 Pro - installed Hyper-V
 

Yes wrote:

Paul wrote:

Yes wrote:
As I reported yesterday, today I'd be working on getting Hyper-V
running and install a VM WinXP. Because I'd never done that
before, I was nervous and really wasn't sure what to expect.

FWIW, I found two articles that I found very useful. They provided
step by step instructions with screenshots to highlight the
instructions.

http://www.techrepublic.com/blog/win...-hyper-v/6690/

and

http://www.techrepublic.com/blog/win...-hyper-v/6732/

With one or two exceptions, things went smoothly. As far as I can
tell, Hyper-V and the VM WinXP are working as expected. I still
have a long way to go, but the biggest hurdle seems to be over.

John

Hyper-V requires SLAT. I could not install Hyper-V on my "pitiful"
hardware, because my processor doesn't have SLAT.

And it's handy to understand what happens when using a Hypervisor.
All OSes running on the computer are "Guest OSes". That means,
even Windows 8.1 is a Guest OS. And Windows 8.1 has the same status
as your WinXP does. The Hypervisor is the "boss", and everything else
runs underneath it.

SLAT (second level address translation) is part of enhancing
the performance of the graphics card. Since Windows 8.1 is
now a guest, it shares the video card with other OSes. It
doesn't have a privileged position, when playing a 3D game
on the computer. This could mean a reduced frame rate,
something you could have tested for, before installing
Hyper-V. (Do a before and after test, like run 3DMark
before and after, and see how much slower it is.)

So unlike other virtual machine environments, where the
"guests" go through some graphics emulation layer, the
model is a bit different when Hyper-V is involved. If
you don't notice anything, all is fine and dandy.

Note that some executables you download, they do a
check of the environment. As an example, when working
on an encrypted transport stream problem (.ts file),
I downloaded a program called TSDoctor, which has
a trial period. As is usual with programs of
unknown trust, I loaded it in a VM for testing.
It refused to run (presumably, to prevent a user like
me from using the trial period over and over again,
via throw-away VMs). If I wanted to use it, I would
be required to install it on my "main" OS.

When you load that program on your new Hyper-V setup,
it will run in no OS for trial purposes. Because the
status of all OSes, is they're all guests. You can test my
hypothesis if you want. If you purchase a license key
for the program, then you can run it where you want.
Or, so it's claimed.

http://www.videohelp.com/tools/TS-Doctor

So your new Hyper-V, does make a tiny difference
to programs wired up like that one. I'm sure the
author of that program, spent more lines of code
"arming and protecting it", than actually working
on transport streams.

Paul

Hi Paul,

I'm glad you saw my post my experience (all of one day so far LOL
:-) with Hyper-V. I remember you had cautioned that it might not work.

The concept that software with trial periods might be designed to not
[snip]

If Hyper-V becomes too problematical, you might consider VirtualBox. It
is a free virtualizer, but unlike Hyper-V actually runs as an app on
the host OS, in your case W8.1, and all VMs run as Guests on the Host.

https://www.virtualbox.org/

It works very well. Easy to set up.

Stef

Windows 8.1 Pro - installed Hyper-V
 

Stef wrote:

Yes wrote:

Paul wrote:

Yes wrote:
As I reported yesterday, today I'd be working on getting Hyper-V
running and install a VM WinXP. Because I'd never done that
before, I was nervous and really wasn't sure what to expect.

FWIW, I found two articles that I found very useful. They
provided step by step instructions with screenshots to highlight
the instructions.


http://www.techrepublic.com/blog/win...-hyper-v/6690/

and


http://www.techrepublic.com/blog/win...-hyper-v/6732/

With one or two exceptions, things went smoothly. As far as I
can tell, Hyper-V and the VM WinXP are working as expected. I
still have a long way to go, but the biggest hurdle seems to be
over.
John

Hyper-V requires SLAT. I could not install Hyper-V on my "pitiful"
hardware, because my processor doesn't have SLAT.

And it's handy to understand what happens when using a Hypervisor.
All OSes running on the computer are "Guest OSes". That means,
even Windows 8.1 is a Guest OS. And Windows 8.1 has the same
status as your WinXP does. The Hypervisor is the "boss", and
everything else runs underneath it.

SLAT (second level address translation) is part of enhancing
the performance of the graphics card. Since Windows 8.1 is
now a guest, it shares the video card with other OSes. It
doesn't have a privileged position, when playing a 3D game
on the computer. This could mean a reduced frame rate,
something you could have tested for, before installing
Hyper-V. (Do a before and after test, like run 3DMark
before and after, and see how much slower it is.)

So unlike other virtual machine environments, where the
"guests" go through some graphics emulation layer, the
model is a bit different when Hyper-V is involved. If
you don't notice anything, all is fine and dandy.

Note that some executables you download, they do a
check of the environment. As an example, when working
on an encrypted transport stream problem (.ts file),
I downloaded a program called TSDoctor, which has
a trial period. As is usual with programs of
unknown trust, I loaded it in a VM for testing.
It refused to run (presumably, to prevent a user like
me from using the trial period over and over again,
via throw-away VMs). If I wanted to use it, I would
be required to install it on my "main" OS.

When you load that program on your new Hyper-V setup,
it will run in no OS for trial purposes. Because the
status of all OSes, is they're all guests. You can test my
hypothesis if you want. If you purchase a license key
for the program, then you can run it where you want.
Or, so it's claimed.

http://www.videohelp.com/tools/TS-Doctor

So your new Hyper-V, does make a tiny difference
to programs wired up like that one. I'm sure the
author of that program, spent more lines of code
"arming and protecting it", than actually working
on transport streams.

Paul

Hi Paul,

I'm glad you saw my post my experience (all of one day so far
LOL :-) with Hyper-V. I remember you had cautioned that it might
not work.

The concept that software with trial periods might be designed to
not [snip]

If Hyper-V becomes too problematical, you might consider VirtualBox.
It is a free virtualizer, but unlike Hyper-V actually runs as an app
on the host OS, in your case W8.1, and all VMs run as Guests on the
Host.

https://www.virtualbox.org/

It works very well. Easy to set up.

Stef

Way too early for me to know, especially because I'm a newbie VM
and networks. I've tried virtual box before under WinXP. So far
Hyper-V seems to work; I just don't know enough to recognize if it
works and plays "well". The articles I posted links to gave what I
thought were very clear step by step instructions to install Hyper-V
and WinXP. No significant problem, just that now I have to learn to
use it :-)

John

Windows 8.1 Pro - installed Hyper-V
 

Yes wrote:

Stef wrote:
[big snip]
not [snip]

If Hyper-V becomes too problematical, you might consider VirtualBox.
It is a free virtualizer, but unlike Hyper-V actually runs as an app
on the host OS, in your case W8.1, and all VMs run as Guests on the
Host.

https://www.virtualbox.org/

It works very well. Easy to set up.

Stef

Way too early for me to know, especially because I'm a newbie VM
and networks. I've tried virtual box before under WinXP. So far
Hyper-V seems to work; I just don't know enough to recognize if it
works and plays "well". The articles I posted links to gave what I
thought were very clear step by step instructions to install Hyper-V
and WinXP. No significant problem, just that now I have to learn to
use it :-)

John

If it ain't broke, don't fix it, I always say. If you're not having any
problems, and Hyper-V is fulfilling your needs, why try something else?

Stef