![](https://seccdn.libravatar.org/avatar/3e1352bfef10435f2311e11bd44ba060.jpg?s=120&d=mm&r=g)
Theoretically, http://volker.orcon.net.nz/linux/vmware/ should be all you need to know to get vmware express going on a freshly installed SuSE 7.3. At least it worked for me. As for your other endless mucking around, the following 3 commands as root will get rid of any package + its running daemons (not the recommended way for experienced admins, but it will work): rpm -e --nodeps --noscripts --force VMware SuSEconfig reboot Actually, I take that back. The --noscripts will not always tidy up during rpm -e, depending on the individual package. Esp commercial software is chronic, but VMware will be fine. Volker PS Make sure you install VMware by using an rpm of it.
![](https://seccdn.libravatar.org/avatar/6ecea25fec0d8a8e1c0f921aa80ebea8.jpg?s=120&d=mm&r=g)
On Monday 26 November 2001 03:03, Volker Kuhlmann wrote:
Theoretically,
http://volker.orcon.net.nz/linux/vmware/
should be all you need to know to get vmware express going on a freshly installed SuSE 7.3. At least it worked for me.
Hi Volker. Thank you for your reply.
As for your other endless mucking around, the following 3 commands as root will get rid of any package + its running daemons (not the recommended way for experienced admins, but it will work):
OK.
rpm -e --nodeps --noscripts --force VMware SuSEconfig reboot
Fine, but cannot be run form neither Yast nor Yast2, but hope rpm -e VMware will uninstall in case :-)
Actually, I take that back. The --noscripts will not always tidy up during rpm -e, depending on the individual package. Esp commercial software is chronic, but VMware will be fine.
What are you taking back Volker ??.
Volker
PS Make sure you install VMware by using an rpm of it.
Yes and once more thanks for the nice info. The .txt files has now been written out :-) -- Med venlig hilsen / Best regards Erik Jakobsen - erik@urbakken.dk Powered by SuSE 7.3
![](https://seccdn.libravatar.org/avatar/6ecea25fec0d8a8e1c0f921aa80ebea8.jpg?s=120&d=mm&r=g)
On Monday 26 November 2001 03:03, Volker Kuhlmann wrote: Hi again Volker. I have as metioned downloaded your .txt file: Is the below necessary as I run the kernel 2.4.10-4GB ??. I have installed the missing kernel sources fro the DVD. Create the missing header files before compiling the vmware kernel modules. 1) Install package kernel-source-2.4.10.SuSE (I used kernel-source-2.4.10.SuSE-8.i386.rpm from CD 2.) Make sure the running kernel fits this source. Boot the correct kernel if not. 2) Create header files cd /usr/src/linux make mrproper make cloneconfig Turn on module versions. Make no other change to the kernel configuration, and leave the maximum suported memory at 4GB (vmware won't work with 64GB). There are several ways to do this: make xconfig Enter "Loadable module support" (2nd down on the left), and set "set version information on all module symbols" to yes. Save and exit. make menuconfig ... make config ... make dep This has created the missing header files. DO NOT COMPILE MODULES (waste of time) or INSTALL THE KERNEL OR MODULES (warranty/support void if done)! -- Med venlig hilsen / Best regards Erik Jakobsen - erik@urbakken.dk Powered by SuSE 7.3
participants (2)
-
Erik Jakobsen
-
Volker Kuhlmann