Date: Tue, 9 Jan 2001 11:03:43 -0700 (MST) From: John Reynolds~ <jreynold@sedona.ch.intel.com> To: "Will Mitayai Keeso Rowe" <mit@mitayai.net> Cc: "Vladimir N. Silyaev" <vsilyaev@mindspring.com>, "Will Mitayai Keeso Rowe" <mitayai@home.mitayai.net>, <freebsd-emulation@freebsd.org> Subject: RE: VMWare2.0 on FreBSD 4.2 Message-ID: <14939.21120.5431.896647@hip186.ch.intel.com> In-Reply-To: <NEBBIEGPMLMKDBMMICFNAEHKEAAA.mit@mitayai.net> References: <20010109092617.B337@jupiter.delta.ny.us> <NEBBIEGPMLMKDBMMICFNAEHKEAAA.mit@mitayai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[ On Tuesday, January 9, Will Mitayai Keeso Rowe wrote: ] > > :You have try to use some FreeBSD related readme files coming together > :with vmware port, and try to make you existing partiotions works using > :plain disks. > > What readme files...? > > :P.S. If you lookign to use WinXXX XXX Don't forget to boot in safe > :mode and > :create different hardware profile, at other case you can easily screwed up > :you existing setup. > : > > Ouch! Thanks for that tip ;-) if you are using Win98 (SE or not) for the client, don't bother creating the second hardware profile. In fact, don't bother with anything in general (IMHO). Regardless of the "separate hardware profile" things get screwed up between the two if you try to boot the same partition under VMware and natively. If you have things setup natively and use VMware's procedure to install the VMware tools (with the better SVGA driver, etc.) it will hose your drivers for native (put you back in 640x480 mode). If you go fix native drivers (painstakingly) it will hose the VMware setup. Repeat this ad nauseum if you like. AFAICT, it isn't a "FreeBSD problem" either because VMware's news server's lists were flooded with the same complaints I had with people running it under "real linux." There was never any "real" resolution. My advice would be to install win98 in a virtual disk and just use it like that. I had NOTHING but frustration trying to use the same FAT disk under VMware and native boot mode. VMware's "help" site claims they have work-arounds but they absolutely do not work. This information is 3 months old (and coming from my warped memory). If it is out dated and better procedures/work-arounds exist for doing the above, please share them! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14939.21120.5431.896647>