On Sat, Apr 08, 2000 at 09:00:40PM +0100, Tony Boom wrote:
>  OK  chaps...  Any  chance of a complete idiots step by step guide as to
>  Howto  please. Whenever I've installed VMWare it refused to boot till I
>  installed an OS. I'm using Red Hat 6.1.

    OK, it is somewhat simple.  Mind you I don't have VMWare installed
anywhere at the moment so forgive any inconsistancies.  Also, I did this
before VMWare 2.0 was released.

    I am making the assumption that you're using IDE devices.  OK, let's set
the ground rules.  Assume lilo is installed in the boot sector to provide a
boot loader to either Windows98 or Linux.  VMWare will be installed on Linux.
Finally, make it a simple setup.  Single IDE drive with Linux on /dev/hda2 and
windows on /dev/hda1.

    IIRC there is an option to boot a raw device.  In this case the raw device
is /dev/hda.  

brw-rw----    1 root     disk       3,   0 Dec  9 14:21 /dev/hda

    If you tell it to boot that device you'll end up booting right back to the
lilo prompt.  From there, choose Windows98 instead of Linux and you're now
booting the same Windows partition as you would natively.  Same programs, same
registry, same drive letters, etc.

    Now, what you'll want to do is install hardware profiles into Windows98
(95 has them as well).  You'll need one for a native boot and one for a
virtual boot.  When booting it will ask which one you want to boot to.  When
booting in VMWare, tell it the virtual one and install all the VMWare drivers
there.  The trick is to disable any drivers in each profile that is not
needed.  IE, disable the VMWare drivers in the native boot, and the native
drivers in the VMWare boot.

    The end result is a booting process like this:

lilo --> Windows98 --> Native profile
     |
     +-> Linux --> X --> VMWare
                         |
                         +-> lilo --> Windows98 --> VMWare profile
                                  |
                                  +-> Linux (if you so choose, not
                                             advised.)

    Yes, you could, in theory, boot one copy of Linux inside the other copy,
access the same drives in the same manner.  Or Linux inside Linux insude
Linux, etc.  I don't advise it since I dunno what problems might arise from
it.

>  Personal email obviously, not to the list.

    Nah, just marked it off topic in case someone else wanted to know. 

-- 
         Steve C. Lamb         | I'm your priest, I'm your shrink, I'm your
         ICQ: 5107343          | main connection to the switchboard of souls.
-------------------------------+---------------------------------------------
-- 
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
   <mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
   <mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------

You are subscribed as : [email protected]


Reply via email to