Amis du soir, bonsoir...je me permets de poster de nouveau parce que j'aimerais bien en avoir le coeur net...Pour suivre mon aventure dans l'émulation, voire les posts précédents ( entre nous soit dit: je trouve étonnant que personne n'ait les memes problèmes que moi...je me sens seul d'un seul coup...!!!!)
Donc....pour la énième fois j'ai tout éffacé de mon home...et recommencer en suivant le tuto sur la workstation. Je tiens à dire que j'ai fait les memes choses, j'ai suivi la meme procédure, mais cette fois avec un résultat différent. Le voici, ( c'est un peu long, mais, bon c'est ce qu'il y a sur ma console ) je saute les étapes pour vous donner la fin:
Do you accept? (yes/no) y
Thank you.
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the mime type icons?
[/usr/share/icons]
What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]
In which directory do you want to install the application's icon?
[/usr/share/pixmaps]
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes] y
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.15-23-386/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.15-23-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.15-23-386'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config0/vmmon-only/common/task.o
CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.15-23-386'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes] y
Extracting the sources of the vmnet module.
Building the vmnet module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.15-23-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.15-23-386'
CC [M] /tmp/vmware-config0/vmnet-only/driver.o
CC [M] /tmp/vmware-config0/vmnet-only/hub.o
CC [M] /tmp/vmware-config0/vmnet-only/userif.o
CC [M] /tmp/vmware-config0/vmnet-only/netif.o
CC [M] /tmp/vmware-config0/vmnet-only/bridge.o
CC [M] /tmp/vmware-config0/vmnet-only/procfs.o
CC [M] /tmp/vmware-config0/vmnet-only/smac_compat.o
SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
Warning: could not open /tmp/vmware-config0/vmnet-only/includeCheck.h: Invalid argument
CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.15-23-386'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The file /lib/modules/2.6.15-23-386/misc/vmnet.o that this program was about to
install already exists. Overwrite? [yes] y
The file /lib/modules/2.6.15-23-386/misc/vmnet.ko that this program was about toinstall already exists. Overwrite? [yes]
The module loads perfectly in the running kernel.
The file /etc/rc2.d/S90vmware that this program was about to install already
exists. Overwrite? [yes]
The file /etc/rc2.d/K08vmware that this program was about to install already
exists. Overwrite? [yes]
The file /etc/rc3.d/S90vmware that this program was about to install already
exists. Overwrite? [yes]
The file /etc/rc3.d/K08vmware that this program was about to install already
exists. Overwrite? [yes]
The file /etc/rc5.d/S90vmware that this program was about to install already
exists. Overwrite? [yes]
The file /etc/rc5.d/K08vmware that this program was about to install already
exists. Overwrite? [yes]
The file /etc/rc0.d/K08vmware that this program was about to install already
exists. Overwrite? [yes]
The file /etc/rc6.d/K08vmware that this program was about to install already
exists. Overwrite? [yes]
Starting VMware services:
Virtual machine monitor done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host-only networking on /dev/vmnet1 (background) done
Host-only networking on /dev/vmnet8 (background) done
NAT service on /dev/vmnet8 done
The configuration of VMware Workstation 5.5.1 build-19175 for Linux for this
running kernel completed successfully.
You can now run VMware Workstation by invoking the following command:
"/usr/bin/vmware".
Enjoy,
--the VMware team
Bon. J'y suis presque. Ma shell est encore "ouverte" et dans outils système je vois vmplayer et workstation. Tout comme hier, avec ma dapper toute fraiche...
Je fais quoi? Je donne du
/usr/bin/vmware
pour voir???:cool:
allez, je me lance, on verra bien.
( je ne sais absolument pas pourquoi j'en suis arrivé là, alors qu'hier, après réinstall de dapper, et de workstation, puis reboot, je n'ai plus réussi à lancer quoi que ce soit....)
Un coup de main pour éliminer windozzzzzz et ne le faire fonctionner qu'en virtuel??? J'demande de l'aide parce que je suis presque sur que ça va foirer, au moins aprés un reboot...
Merci d'avance, je fais savoir.
Amkoolgarst.😉
