Sign in with
Sign up | Sign in
Your question

Virtual Windows

Last response: in Windows XP
Share
March 1, 2005 2:45:32 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

I remember a while back seeing a setup where there was a way to have
'virtual' Windows installed... i.e., like having a multiple boot
configuration, but instead of multiple booting, once booted up, there was an
app that was run that would have other 'virtual systems' that you could
run...

This was used at a training facility... they had their system setup where
you were actually working on a 'virtual machine' on the system, so if you
deleted files, messed up network settings, etc... it didn't really matter,
because they could easily revert the virtual system.

I'm wanting this capability so I can have a separate 'system' in which I can
run beta software... so the beta software would actually be installed on a
virtual machine, not my production machine... you know, so the beta software
doesn't do something to mess my production up.

OK.. if you have any ideas what the heck I'm talking about... please reply
and let me know.

Thanks,
MS

More about : virtual windows

Anonymous
March 1, 2005 2:53:46 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

MJS wrote:
> I remember a while back seeing a setup where there was a way to have
> 'virtual' Windows installed... i.e., like having a multiple boot
> configuration, but instead of multiple booting, once booted up, there was an
> app that was run that would have other 'virtual systems' that you could
> run...
>
> This was used at a training facility... they had their system setup where
> you were actually working on a 'virtual machine' on the system, so if you
> deleted files, messed up network settings, etc... it didn't really matter,
> because they could easily revert the virtual system.
>
> I'm wanting this capability so I can have a separate 'system' in which I can
> run beta software... so the beta software would actually be installed on a
> virtual machine, not my production machine... you know, so the beta software
> doesn't do something to mess my production up.
>
> OK.. if you have any ideas what the heck I'm talking about... please reply
> and let me know.
>
> Thanks,
> MS
>
>
I think you're looking for Virtual PC.


http://www.microsoft.com/windows/virtualpc/default.mspx

gls858
Anonymous
March 1, 2005 2:55:49 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

Microsoft Virtual PC 2004
http://www.microsoft.com/windows/virtualpc/default.mspx

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/defaul...

------------------------------------------------------------------------------

"MJS" wrote:

| I remember a while back seeing a setup where there was a way to have
| 'virtual' Windows installed... i.e., like having a multiple boot
| configuration, but instead of multiple booting, once booted up, there was an
| app that was run that would have other 'virtual systems' that you could
| run...
|
| This was used at a training facility... they had their system setup where
| you were actually working on a 'virtual machine' on the system, so if you
| deleted files, messed up network settings, etc... it didn't really matter,
| because they could easily revert the virtual system.
|
| I'm wanting this capability so I can have a separate 'system' in which I can
| run beta software... so the beta software would actually be installed on a
| virtual machine, not my production machine... you know, so the beta software
| doesn't do something to mess my production up.
|
| OK.. if you have any ideas what the heck I'm talking about... please reply
| and let me know.
|
| Thanks,
| MS
Related resources
Anonymous
March 1, 2005 4:34:23 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

MJS wrote:

> I remember a while back seeing a setup where there was a way to have
> 'virtual' Windows installed... i.e., like having a multiple boot
> configuration, but instead of multiple booting, once booted up, there was an
> app that was run that would have other 'virtual systems' that you could
> run...
>
> This was used at a training facility... they had their system setup where
> you were actually working on a 'virtual machine' on the system, so if you
> deleted files, messed up network settings, etc... it didn't really matter,
> because they could easily revert the virtual system.
>
> I'm wanting this capability so I can have a separate 'system' in which I can
> run beta software... so the beta software would actually be installed on a
> virtual machine, not my production machine... you know, so the beta software
> doesn't do something to mess my production up.
>
> OK.. if you have any ideas what the heck I'm talking about... please reply
> and let me know.
>
> Thanks,
> MS
>
>
I was using a computer lab for a while that reloaded a default
installation from a network server each time a workstation was booted.
As I understand it, the Network Interface Cards (NICs) acted as the boot
drive and contained code that accessed the server over a LAN and copied
the Windows installation from an image on the server.
Anonymous
March 1, 2005 4:34:24 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

The OP is looking for Virtual PC 2004 or Virtual Server 2005 for running
Windows (all flavors) on an XP desktop as an alternative for setting up a
multiboot computer.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"RobertVA" <Robert_c72nospam@hottmail.com> wrote in message
news:%23g7uN1oHFHA.3484@TK2MSFTNGP12.phx.gbl...
> MJS wrote:
>
>> I remember a while back seeing a setup where there was a way to have
>> 'virtual' Windows installed... i.e., like having a multiple boot
>> configuration, but instead of multiple booting, once booted up, there was
>> an app that was run that would have other 'virtual systems' that you
>> could run...
>>
>> This was used at a training facility... they had their system setup where
>> you were actually working on a 'virtual machine' on the system, so if you
>> deleted files, messed up network settings, etc... it didn't really
>> matter, because they could easily revert the virtual system.
>>
>> I'm wanting this capability so I can have a separate 'system' in which I
>> can run beta software... so the beta software would actually be installed
>> on a virtual machine, not my production machine... you know, so the beta
>> software doesn't do something to mess my production up.
>>
>> OK.. if you have any ideas what the heck I'm talking about... please
>> reply and let me know.
>>
>> Thanks,
>> MS
>>
>>
> I was using a computer lab for a while that reloaded a default
> installation from a network server each time a workstation was booted. As
> I understand it, the Network Interface Cards (NICs) acted as the boot
> drive and contained code that accessed the server over a LAN and copied
> the Windows installation from an image on the server.
Anonymous
March 1, 2005 4:35:53 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

Can also be done with Alcohol 120
"MJS" <a@b.com> wrote in message
news:up2l4ZoHFHA.3336@TK2MSFTNGP10.phx.gbl...
>I remember a while back seeing a setup where there was a way to have
>'virtual' Windows installed... i.e., like having a multiple boot
>configuration, but instead of multiple booting, once booted up, there was
>an app that was run that would have other 'virtual systems' that you could
>run...
>
> This was used at a training facility... they had their system setup where
> you were actually working on a 'virtual machine' on the system, so if you
> deleted files, messed up network settings, etc... it didn't really matter,
> because they could easily revert the virtual system.
>
> I'm wanting this capability so I can have a separate 'system' in which I
> can run beta software... so the beta software would actually be installed
> on a virtual machine, not my production machine... you know, so the beta
> software doesn't do something to mess my production up.
>
> OK.. if you have any ideas what the heck I'm talking about... please reply
> and let me know.
>
> Thanks,
> MS
>
>
Anonymous
March 1, 2005 4:35:54 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

But Windows OS's run under VPC are supported by Microsoft PSS.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"Glenn Shumaker" <shoe1@charter.net> wrote in message
news:eB2Vd.2681$nZ6.1300@fe04.lga...
> Can also be done with Alcohol 120
> "MJS" <a@b.com> wrote in message
> news:up2l4ZoHFHA.3336@TK2MSFTNGP10.phx.gbl...
>>I remember a while back seeing a setup where there was a way to have
>>'virtual' Windows installed... i.e., like having a multiple boot
>>configuration, but instead of multiple booting, once booted up, there was
>>an app that was run that would have other 'virtual systems' that you could
>>run...
>>
>> This was used at a training facility... they had their system setup where
>> you were actually working on a 'virtual machine' on the system, so if you
>> deleted files, messed up network settings, etc... it didn't really
>> matter, because they could easily revert the virtual system.
>>
>> I'm wanting this capability so I can have a separate 'system' in which I
>> can run beta software... so the beta software would actually be installed
>> on a virtual machine, not my production machine... you know, so the beta
>> software doesn't do something to mess my production up.
>>
>> OK.. if you have any ideas what the heck I'm talking about... please
>> reply and let me know.
>>
>> Thanks,
>> MS
>>
>>
>
>
Anonymous
March 1, 2005 4:35:54 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

The OP is not talking about virtual cd/dvd drives, but about virtual
computers running a variety of operating systems in windows on his XP
desktop. For example, running Windows 98SE and Windows XP Pro on the same
computer simultaneously and being able to drag and drop beween the desktops,
and so on, without having to partition or reboot.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"Glenn Shumaker" <shoe1@charter.net> wrote in message
news:eB2Vd.2681$nZ6.1300@fe04.lga...
> Can also be done with Alcohol 120
> "MJS" <a@b.com> wrote in message
> news:up2l4ZoHFHA.3336@TK2MSFTNGP10.phx.gbl...
>>I remember a while back seeing a setup where there was a way to have
>>'virtual' Windows installed... i.e., like having a multiple boot
>>configuration, but instead of multiple booting, once booted up, there was
>>an app that was run that would have other 'virtual systems' that you could
>>run...
>>
>> This was used at a training facility... they had their system setup where
>> you were actually working on a 'virtual machine' on the system, so if you
>> deleted files, messed up network settings, etc... it didn't really
>> matter, because they could easily revert the virtual system.
>>
>> I'm wanting this capability so I can have a separate 'system' in which I
>> can run beta software... so the beta software would actually be installed
>> on a virtual machine, not my production machine... you know, so the beta
>> software doesn't do something to mess my production up.
>>
>> OK.. if you have any ideas what the heck I'm talking about... please
>> reply and let me know.
>>
>> Thanks,
>> MS
>>
>>
>
>
March 1, 2005 5:31:16 PM

Archived from groups: microsoft.public.windowsxp.basics (More info?)

"MJS" <a@b.com> wrote in message
news:up2l4ZoHFHA.3336@TK2MSFTNGP10.phx.gbl...
>I remember a while back seeing a setup where there was a way to have
>'virtual' Windows installed... i.e., like having a multiple boot
>configuration, but instead of multiple booting, once booted up, there
>was an app that was run that would have other 'virtual systems' that
>you could run...
>
> This was used at a training facility... they had their system setup
> where you were actually working on a 'virtual machine' on the system,
> so if you deleted files, messed up network settings, etc... it didn't
> really matter, because they could easily revert the virtual system.
>
> I'm wanting this capability so I can have a separate 'system' in which
> I can run beta software... so the beta software would actually be
> installed on a virtual machine, not my production machine... you know,
> so the beta software doesn't do something to mess my production up.
>
> OK.. if you have any ideas what the heck I'm talking about... please
> reply and let me know.
>
> Thanks,
> MS
>
>


For virtual machines running on the same host:
Microsoft's Virtual PC
VMware
As to which is the better product, that depends on what how you intend
to use it. VMware is the better performer for speed and also for
isolation of the VMs so it is the better choice for multiple concurrent
OS'es for programming activities but it is more expensive. Some reviews
were found at:
http://usuarios.lycos.es/hernandp/articles/vpcvs.html
http://www.osnews.com/story.php?news_id=1054 (a bit dated)
http://www.pcmag.com/article2/0,1759,1134681,00.asp
http://www.winsupersite.com/reviews/virtualpc2004.asp

Could be you were remotely accessing another PC from your host:
VNC, UltraVNC, RealVNC, or TightVNC
Symantec PCAnywhere

Some hosts lets you add a daughtercard which provides an entire hardware
platform on which to run the guest OS. Several years ago, we has some
Solaris boxes that had a daughtercard on which to run Windows (i.e., a
host within a host). You were running an actual and separate instance
of the guest OS on its own hardware. I wasn't involved in the
experiment so I have no experience on how well that worked.

--
____________________________________________________________
Post your replies to the newsgroup. Share with others.
E-mail reply: Remove "NIXTHIS" and add "#VS811" to Subject.
____________________________________________________________
!