I may be crazy, nut I think I know what the problem is.
VMWare is installed and configured via perl scripts. These scripts assume SysVInit. Slackware uses it's own BSD style init.
In your post, you note the output of vmware-config.pl (condensed for easy reading):
Code:
This program previously created the file /etc/init.d/rc2.d/K08vmware, and was
about to remove it. Somebody else apparently did it already.
This program previously created the file /etc/init.d/rc3.d/S90vmware, and was
about to remove it. Somebody else apparently did it already.
This program previously created the file /etc/init.d/rc3.d/K08vmware, and was
about to remove it. Somebody else apparently did it already.
This program previously created the file /etc/init.d/rc5.d/S90vmware, and was
about to remove it. Somebody else apparently did it already.
This program previously created the file /etc/init.d/rc5.d/K08vmware, and was
about to remove it. Somebody else apparently did it already.
This program previously created the file /etc/init.d/rc0.d/K08vmware, and was
about to remove it. Somebody else apparently did it already.
This program previously created the file /etc/init.d/rc6.d/K08vmware, and was
about to remove it. Somebody else apparently did it already.
I'm going to wager a whacky guess that the correct files were never created.
No I don't know how much this will help you, but I have installed vmware-player on my system and had it work, so....
You should know that Slackware uses a BSD-style init system by default, BUT it also recognizes SysVInit init systems (what VMWare install script is expecting).
I created a directory, /etc/rc.d/init.d
Inside the /etc/rc.d/init.d directory is one lonely file, vmware (maybe this is different for VMWare vs. VMWare-Player, but I doubt it).
I created a bunch more directories, /etc/rc.d/rc0.d /etc/rc.d/rc1.d /etc/rc.d/rc2.d /etc/rc.d/rc3.d /etc/rc.d/rc4.d /etc/rc.d/rc5.d /etc/rc.d/rc6.d
Now when I installed VMWare-Player, I pointed stuff in the right direction (I haven't bothered reading your link, so maybe you did, but I'll bet you didn't).
Anyway the next important note is that runlevel 5 is the GUI runlevel for everybody but Slackware. So you will want to make /etc/rc.d/rc4.d and /etc/rc.d/rc5.d look the same.
Each of the directories (/etc/rc.d/rc?.d) is refering to a specific runlevel.
When your all done, remember that the /etc/rc.d/rc?.d files are just symlinks (they all should point to /etc/rc.d/init.d/vmware or eq., regardless of name)
/etc/rc.d/rc0.d - K08vwmare
/etc/rc.d/rc1.d - Nothing
/etc/rc.d/rc2.d - K08vwmare and S90vmware
/etc/rc.d/rc3.d - K08vwmare and S90vmware
/etc/rc.d/rc4.d - K08vwmare and S90vmware
/etc/rc.d/rc5.d - K08vwmare and S90vmware
/etc/rc.d/rc6.d - K08vwmare
It's late so I hope this all makes sense. Alternatively, I believe Jong has a post on using a SlackBuild to convert the perl installation over to use the native Slackware init system. If you search the forum, it shouldn;t be hard to find (search "vmware slackware", there aren't that many entries, as I recall).