VMware scripts are created twice and is a real pain

Hello, I've installed VMware 3.0 on a computer where important work is done. Every time SuSEconfig or vmware-config.pl are run, separate symlinks of vmware are created in rc5.d. One ends up with two sets of start/kill links. The result causes the virtual machine to not start and no work can be done. The user of the machine is a non technical person, needless to say I get a phone call every time this person can't get the program to run and hints that it would better to ditch linux and go back to MS Windows. The culprit seems to be vmware-config.pl, since it creates the symlinks without using "innsserv". I would really appreciate if SuSE and VMware worked out this problem. -- Rafael