tantone
09-20-2006, 09:45 AM
On our latest Ghost image for the Dell D620, Explorer has a strange quirk that affects, like, 2 people, but it's something we need to address.
Here's how to reproduce it (on that image on that laptop model):
- create a shortcut to a network location on your desktop (mapped drive, UNC path, doesn't matter)
- open Windows Explorer (folder list visibile by default)
- in the folder list, go to your desktop
- double-click on the shortcut on the right
Instead of opening the location the shortcut points to, it opens the C: drive. You can put the shortcut anywhere you like on the computer, but the result is the same.
This only happens when you double-click with the folder list open. If you right-click and Open, it opens properly. If you double-click with the folder list closed, it works. If you double-click on the shortcut directly on the desktop (not through Windows Explorer), it works.
I've scoured the registry for something telling regards but the settings are identical to my other laptop.
Yes, this is an issue with the image that needs to be corrected--likely by recreating the image. But it seems there's something that we could fix. Any suggestions?
Here's how to reproduce it (on that image on that laptop model):
- create a shortcut to a network location on your desktop (mapped drive, UNC path, doesn't matter)
- open Windows Explorer (folder list visibile by default)
- in the folder list, go to your desktop
- double-click on the shortcut on the right
Instead of opening the location the shortcut points to, it opens the C: drive. You can put the shortcut anywhere you like on the computer, but the result is the same.
This only happens when you double-click with the folder list open. If you right-click and Open, it opens properly. If you double-click with the folder list closed, it works. If you double-click on the shortcut directly on the desktop (not through Windows Explorer), it works.
I've scoured the registry for something telling regards but the settings are identical to my other laptop.
Yes, this is an issue with the image that needs to be corrected--likely by recreating the image. But it seems there's something that we could fix. Any suggestions?