Re: multiple os on single pc. was When is a Windows network not a Windows network

--
[ Picked text/plain from multipart/alternative ]
NT and W2K crash as well  - only marginally more stable that W9x. My
experience shows that it depends how new the PC is. Windows 'seems' to
get less reliable as it, and the hardware, get older. Is this just me,
or is this rather suspicious.

Back to the subject of  multiple OS on a single PC. I have found that a
base OS of Linux with Windows in VMWare sessions is more stable than
Windows as the base OS. Win NT4 server and W2K run perfectly well in a
VMWare shell under Linux.

For a stable system I would recommend a base OS of Linux, then add the
Windows OSs. If one of the Windows sessions crashes, it can be restarted
without rebooting the entire PC.

Syd Nicholson


Walden H. Leverich wrote:

>What version of windows? If it's not W2K (and _maybe_ XP Pro) then all bets
>are off. The rest stink.
>
>The biggest disservice MS did to themselves was naming their P.O.S.
>operating systems (9x and ME) the same as their good ones (NT, W2K and XP
>Pro). I often hear that "windows" crashes all the time and then I hear that
>it's 9x or ME.
>
>
>-Walden
>
>------------
>Walden H Leverich III
>President
>Tech Software
>(516) 627-3800 x11
>(208) 692-3308 eFax
>WaldenL@TechSoftInc.com
>http://www.TechSoftInc.com
>
>Quiquid latine dictum sit altum viditur.
>(Whatever is said in Latin seems profound.)
>
>
>
>-----Original Message-----
>From: Weatherly, Howard [mailto:hweatherly@dlis.dla.mil]
>Sent: Tuesday, May 14, 2002 08:10
>To: 'midrange-l@midrange.com'
>Subject: RE: multiple os on single pc. was When is a Windows network not a
>Windows network
>
>
>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
>--
>[ Picked text/plain from multipart/alternative ]
>I wish I had the reported up time with any Windows product that I hear
>reports about, always seems like something is broken or won't work! maybe
>it's those darn IBM computers I use that the OS finds fault with, or maybe I
>just ask the OS to do the far to complex task of simply managing hardware
>and providing a decent user interface, yup that must be it, I am far too
>demanding ...
>
>-----Original Message-----
>From: Walden H. Leverich [mailto:WaldenL@TechSoftInc.com]
>Sent: Monday, May 13, 2002 4:28 PM
>To: 'midrange-l@midrange.com'
>Subject: RE: multiple os on single pc. was When is a Windows network not a
>Windows network
>
>
>Along the lines of my analogy to LPAR, what happens when the controlling
>LPAR goes down? When the host OS goes south the entire machine (including
>VMs) go south. However, I find that doesn't happen to often (W2K).
>
>-Walden
>
>------------
>Walden H Leverich III
>President
>Tech Software
>(516) 627-3800 x11
>(208) 692-3308 eFax
>WaldenL@TechSoftInc.com
>http://www.TechSoftInc.com
>
>Quiquid latine dictum sit altum viditur.
>(Whatever is said in Latin seems profound.)
>
>
>
>-----Original Message-----
>From: Weatherly, Howard [mailto:hweatherly@dlis.dla.mil]
>Sent: Monday, May 13, 2002 16:21
>To: 'midrange-l@midrange.com'
>Subject: RE: multiple os on single pc. was When is a Windows network not a
>Windows network
>
>
>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
>--
>[ Picked text/plain from multipart/alternative ]
>What happens when the host system has a problem, are the virtual machines
>preserved or is a major catastrophe?
>
>-----Original Message-----
>From: Walden H. Leverich [mailto:WaldenL@TechSoftInc.com]
>Sent: Monday, May 13, 2002 3:47 PM
>To: 'midrange-l@midrange.com'
>Subject: RE: multiple os on single pc. was When is a Windows network not a
>Windows network
>
>
>It actually keeps the state of the OS in memory. I can run W2K as my base OS
>with a WinNT and a Linux VM. The important thing to stress here is that
>there is no reboot involved. The guest OS's run in a window under W2K. Think
>of it as LPAR for windows. (Um, maybe you should think of LPAR as vmware for
>OS/400 <G>).
>
>When we moved to W2K (several years ago now) the payroll software that we
>run wouldn't work under W2K. Normally that would necessitate either a
>dual-boot system or a second box, however with VMWare I would simply boot
>the NT VM when I needed to access the software. As a funny aside, the
>payroll software was Java based, you know the write once run anywhere
>software <G>
>
>On final place VMWare is really cool is demos and the lab. Want to test or
>demo 2 Exchange servers with a client. No problem, just boot two W2K server
>VMs, start exchange in each and then run the client in the host os. Don't
>expect this to be fast, but it does work.
>
>-Walden
>
>------------
>Walden H Leverich III
>President
>Tech Software
>(516) 627-3800 x11
>(208) 692-3308 eFax
>WaldenL@TechSoftInc.com
>http://www.TechSoftInc.com
>
>Quiquid latine dictum sit altum viditur.
>(Whatever is said in Latin seems profound.)
>
>
>
>-----Original Message-----
>From: Vernon Hamberg [mailto:vhamberg@attbi.com]
>Sent: Sunday, May 12, 2002 17:32
>To: midrange-l@midrange.com
>Subject: RE: multiple os on single pc. was When is a Windows network not a
>Windows network
>
>
>I've heard some neat things about this. Does it keep a disk copy of the
>state of each OS when switching, or something like that? Are there limits on
>memory and disk resources per OS? There'd certainly need to be more disk,
>I'd think, and some more CPU memory to keep everything going - kinda like a
>hypervisor?
>
>At 03:59 PM 5/12/02 -0500, you wrote:
>
>>PS:  If you need very good performance out of the vm, then partition
>>magic would be better.
>>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
>or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
>or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
>or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
>or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
>or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>

--