Hi all,

I've got a problem which I hope someone can help with as I can't find it in the forums.

I've got a trial version of VMware Workstation 4.5.2 build-8848 installed on Mandrake 10.1 linux, kernel 2.6.8.1

The problem is the common one about the kernel modules. I run the vmware-config.pl and everything is fine. However, this happy state of affairs lasts only til the next reboot. Once I restart the pc and log in again, what hey,here's the same message about the kernel modules once more, and I have to run the config again. This is driving me insane ! How can I make it remember that it's already been configured ?

pls help me ....

isnt there any answer ? pls help me ?

???????????????*

I had the same problem but my trial ran out before I could solve it Its wierd because it worked happily in Mandrake 9.1:s
Sorry i couldnt be of help.

who knows the answer of this question?

I'm not sure how Mandrakes start up scripts work, wether they use /etc/init.d or /etc/rc.d style scripts, but the problem is not that your vmware config dies after every reboot, bot the module vmmon has not been loaded into the kernel again.

By default vmware installs the appropriate files in /etc/rcX.d and /etc/init.d, so you can either get this working from startup.
The command to specifically start this service is:
/etc/init.d/vmware start|restart|stop

Give it a go.

thanks but it didnt work

I'm having the same problem: did you get a fix?

I experienced the same issue and (If it is the same problem) it appears to be a "not-configured" flag that VMWare creates during execution of the /etc/init.d/vmware startup script.

Deep in the heart of the vmware script there is a section containing the following:

if [ "$exitcode" -gt 0 ]; then
# Set the 'not configured' flag
...
exit 1

When you run the init.d script, the body f the statement creates/updates a not-configured file in the /etc/vmware directory. This file causes the system to say you haven't configured it and forces you to rerun the config.

Simply cutting the body of this does not fix the problem 100%. It eliminates the message, but it still doesn't guarantee your networking will be running properly after a reboot. I'm still working on that problem...

..same problem.. :-((((

I had the same problem (Mandrake 10.1) until I updated my vmware with the most current "any-updates" from this page:

http://platan.vc.cvut.cz/ftp/pub/vmware/

Hope this helps!

it works.. it works.. :-))))) Thanks scottlinux!

I have read on the vmware site, that you need configure your kernel to lad vmware modules by the command : vmware-config.pl --compile