Zitat von "Jochen Roderburg" <[EMAIL PROTECTED]>: > Yes, correctly, the problem appeared after a Windows guest additions > upgrade from 1.6.0 to 1.6.2. > > AFter several ups and downs I am currently at VBox 1.6.2, but with > Windows guest additions 1.5.7, because I did not want to repeat that > upgrade experience. ;-)
Hi Andreas, I had some time now and dared to do some more experiments. As I knew now where to look I was able to repair the damages manually immediately. What I found: There is no problem when the mentioned Windows registry keys do not yet contain a VBoxSF entry before the install. E.g. an existing string "LanmanWorkstation" is correctly changed to "VBoxSF,LanmanWorkstation" If, however, the key does already contain "VBoxSF,LanmanWorkstation", this is corrupted to VBoxSF,anmanWorkstation", invalidating the second part. This happens on all installation sequences of Guest Additions 1.6.x, because these just install on top of each other. On 1.6.x installations over an 1.5.x the older version is first uninstalled and the "VBoxSF" part in the registry is correctly deleted, so the problem does not show up in these cases. Jochen Roderburg ZAIK/RRZK University of Cologne Robert-Koch-Str. 10 Tel.: +49-221/478-7024 D-50931 Koeln E-Mail: [EMAIL PROTECTED] Germany ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
