I'm running Slack 11.0 with kernel 2.6.20.1 and I got workstation 5.5.3, installing it using the vmware-any-any-update108 patch. I am able to create a virtual machine just fine, but when I go to power on the machine I get the following errors, one after another:


Is that patch acceptable for workstation or is only for player? I forced the vmwar-config.pl to compile against my kernel.

Have you tried it without the patch?

Yeah, and the vmware-config.pl bombs out. Tried re-installing twice now with the same results.

Can you post the output from the vmware-config script without the patch please

Ok,I got it running. I had to take the vmmon.tar and vmnet.tar that came with the vmware-any-any patch, extract them, run make and copy the .o and .ko files produced to the /lib/modules/2.6.20.1/misc directory, overwriting the files there.

My problem now is that I can't seem to get Windows XP Pro to connect to the internet through my ethernet adapter and running Fallout 2 causes the mouse to behave erratically.

So I've narrowed down the problem to vmnet0 not loading/running properly. When using bridged networking, it doesn't start and the eth0 starts in disconnected mode for guest OS Win XP. I'm not at my machine currently, but any ideas are welcome. I only the internet so I can update Windows etc.

But it sounds like you've not yet got the virtual network up? (sorry, not much help here). The next offerings focus on what I know *after* the virtual networking is at least on/activated.

Here's some stuff I know on virt network, most of which may not yet be relevant to your case. But, under certain circumstances (possibly other than yours at this time) these certainly may have relevancy.

I wonder if needs a running samba server in Slack.

Perhaps not (but for file sharing between the 2 OS, probably so).

I can't remember if I got it (networking) working in my Vmware Player.

I do have the networking works in my Qemu (Slack is host OS, Win 2K SP4 is guest OS in Qemu). Firefox and others in Win 2K access the internet superbly. (Qemu *may* not be as fast as Vmware (for internet gameing -- I do not game) But I remember it took me a lot to get it working (I'm probably near intermediate as far as my network admin skill level).

Your Slack internet access must work (of course). Then it goes from there (real NIC) through the virtualized NIC (it be the NIC shown in device manager in Win XP). But in order for data to travel this route, somehow it must know how to go that way. In Qemu, I think Qemu has a built in DHCP server that serves a relevant IP address to the MS Windows OS. I think Qemu might also do forwarding and NAT (Qemu uses something like 10.10.10.xx IP range -- my real LAN uses 192.168.1.xx IP range -- thus these two networks need a forwarding/NAT.

I'm less familiar with how Vmware handles this.

But you might peruse in Win XP the device manager look its NIC. Might also peruse the LAN/networking applet in control panel (for relevant gateway IP address, etc. etc.). The Win command: ipconfig

lists what your Win IP address is.

I've heard that the native Win XP firewall (on by default?) does not get along with arp. (*if* anything uses arp to achieve its means).

But it sounds like you've not yet got the virtual network up? This is the first order, before anything that I have herein.

--
Alan.

Here's what the error actually says:

inside code tags enclosed at first of next url's -- had same prob -- got it working -- did something by hand to the vmx file and reran the config. (With Vmware there's two ways to do it 1. NAT (like my Qemu) or 2. bridged (*supposedly* the Vmware default).

I too had probs with Vmware guest OS networking -- I don't know if I ever got back to it and got it fixed or not.

If you fix, please post back what you did so I can learn more (can't *ever* know too much about this sort of stuff).

--
Alan.

Ok, thanks I got the network working now. I ended up changing the permissions on /dev/vmnet0 to allow all users read/write access, and then re-running vmware-config.pl, and it cleared things up, though I'm not 100% on the permissions fixing anything. At least for a NAT configuration. Not sure why bridged still won't pull an ip from the ISP DHCP server, but at least it's working now.

The next problem to fix is the video. Trying to run some games, i.e. Civ II (which won't show wonder completion videos, herald videos or high council member videos), Fallout 2 (which has erratic mouse movement, so much so that I can't choose New Game on the main menu) and Civ IV which bombs when it tries to init engine, with an error of:

Looking at the adapter properties, it is shown as a 16mb VMware SVGA II. I have a NVIDIA 256mb FX5200 physical adapter, with the current Linux drivers installed.

So that's my next mission. I only wanted XP for the games anyways, so :shrug:

Ok, I got it figured out now. Everything works fine. I gotta run, but when I get back I'll post up the solution.

AFAIK, vmware *emulates* all/whatever hardware that you see in MS Win device manager.

As so, then it is not expected to see any corelation between *virtualized/emulated* hardware and what your *real* hardware is.

Doesn't the VM in vmware sort of stand for "virtual machine ware" <- there it is *virtual* or virtualized machine equates to "not real hardware, but, nonetheless, hardware.

For game, you may need to dual boot your box Linux and Win XP dual boot.

MS Win still has it over Linux for game. But I've heard that gaming software companies are porting to Linux due to gaining of Linux popularity/useage.

Maybe there's a gaming addon/plugin for vmware that ups the video (so called hardware but nontheless virtual or emulated variety thereof).

--
Alan.

Have you run vmware-config.pl with the --compile switch? I read somewhere sometime ago, that recompiling of modules is needed for slack. Also wine can run Fallout 1-2-Tactics just fine (with a bit quirky mouse, but still definiately playable)

OK, the problem was that VMware only has experimental 3d acceleration support, and it's not enabled by default. I had to go in and add these lines to the .vmx file to get it to work:

The first line changes the vram size to 128, which is the max currently supported in VMware. The second enables 3d support and the third makes the mouse more stable. So now I can run the games, but my machine isn't powerful enough to push Civ 4 in virtual XP on top of Slack. I can hear the music, but the video just won't come up. The solution to this is simple: get a machine more powerful than the current 1.4Ghz that I have right now.

Have you tried Cedega?

It works well for me for Battlefield 2 and Counterstrike.

I bet it would work MUCH better than vmware for your game... and if you are poor you can subscribe for 3 months (15 bux) and cancel your subscription right away. By doing so, you have the legal right to run the software, but you wont get any updates/support.