prelink breaks VMware 4.5.2 on FC2?

[D. D. Brierton]

I installed VMware Workstation 4.5.2 on FC2 yesterday, and it was
working fine. I got up today and went to start vmware and it wouldn't
start. I tried restarting the vmware service and then starting vmware
from a terminal and this was the output:

$ sudo /sbin/service vmware restart
Password:
Stopping VMware services:
   Virtual machine monitor                                 [  OK  ]
   Bridged networking on /dev/vmnet0                       [  OK  ]
   DHCP server on /dev/vmnet1                              [  OK  ]
   SMB share server on /dev/vmnet1                         [  OK  ]
   SMB name server on /dev/vmnet1                          [  OK  ]
   Host-only networking on /dev/vmnet1                     [  OK  ]
   DHCP server on /dev/vmnet8                              [  OK  ]
   NAT service on /dev/vmnet8                              [  OK  ]
   Host-only networking on /dev/vmnet8                     [  OK  ]
   Virtual ethernet                                        [  OK  ]
Starting VMware services:
   Virtual machine monitor                                 [  OK  ]
   Virtual ethernet                                        [  OK  ]
   Bridged networking on /dev/vmnet0                       [  OK  ]
   Host-only networking on /dev/vmnet1 (background)        [  OK  ]
   Host-only networking on /dev/vmnet8 (background)        [  OK  ]
   NAT service on /dev/vmnet8                              [  OK  ]

$ vmware
NOT_REACHED F(4518):390


VMware Workstation Error:
VMware Workstation unrecoverable error: (vmui)
NOT_REACHED F(4518):390
Please request support.  We will respond on the basis of your support
entitlement.

Press "Enter" to continue...Aborted

I searched through the archive and found this post:

http://www.redhat.com/archives/fedora-list/2004-June/msg01928.html

which never had any replies. Unfortunately, in my case running
vmware-config.pl doesn't help. However the only thing that happened to
my system between me using VMware last night and trying to use it this
morning was the running of the cron jobs. As I can't imaging that
updatedb or logrotate could have effected VMware I can only assume it
was prelink.

Any suggestions?

Best, Darren

-- 
=====================================================================
D. D. Brierton            darren at dzr-web.com          www.dzr-web.com
       Trying is the first step towards failure (Homer Simpson)
=====================================================================