[Dyre Straits]

This is very weird to me.

I'm testing a new level for a game and the author is sending me updated files every few days. In order to start the new level quickly I've created a Desktop Shortcut to the file located in the map folder of where the game's installed.


When I receive a newer file it has the same name as the previous one. So, as I've been accustomed to doing in 98SE, I simply rename the current file to something like 'filename.old' and then copy the newer file into the folder. This has always worked like a charm for me in 98SE.

Now, here's what's happening in XP Home: I rename the file and copy the newer one into the folder where it's supposed to be. BUT, when I double click my Desktop Shortcut, it is linked to the renamed file instead of the properly named file. In order to make the shortcut work, I have to completely remove the previous shortcut and create a new one.

Even if I try to change the name in the 'target' option of the properties, it tells me it can't find the file ... even though it's right under its nose!

So, anyone have a clue how to correct this....or what's causing it to begin with?

[PangingJr]

if the program names.... 123.exe,
and you have its shortcut on desktop,
and if you've turned off the 'hide extensions for known file types',
then you'll see the shortcut as... "123.exe.lnk" (or 123.lnk, depending on how the shortcut was created) now let try this... rename the orginal file from 123.exe to 123_old.exe,
then delete it (the 123_0ld.exe is now in the Recycle bin),
Copy the new 123.exe into its place. make sure you'll not use the shortcut untill you've done the previous steps. and see if the shortcut still working.

[Dyre Straits]

Panging, Thanks for the reply and suggestion.

However, I don't have the extensions hidden. In this particular case the extension is .dsm and is a file that's run using a version of the Unreal Engine. What I'm doing is changing the .dsm to .old. Then I'm bringing in the new file that has the same prefixname.dsm. I would assume that my existing Desktop shortcut would then use the new .dsm file and run the program. But, instead, it's sticking with the file that I've renamed to .old.

If I rightclick on the shortcut and go to the Properties, the line in my Target box is showing it pointing to the .old file. When I try to change the .old to .dsm I get a popup telling me that there's no file there. Yet, it IS there. I just put it there.

So far, the only way I've been able to make things work is to just delete the existing shortcut, right click on the new file in the folder and Send it to the Desktop to create a new shortcut.

[PangingJr]

okay i understand,

its actually an advantage of the NTFS - Distributed link tracking,
it maintains the integrity of shortcuts, you can rename source files, move them to another NTFS volumes, etc , all without breaking the shortcut.

let see we can do it..
so if the source (original) file names.. "123.dsm"...
1st, delete the shortcut you've already created,
then create a new shortcut to the file,
make sure the shortcut works and then stop using it (do not edit the target line, rename, D-Click on it) until you've done with all next steps..

rename the 123.dsm to "123.old", then delete it.
and then put the new 123.dsm to its place. now D-click on the shortcut and see if it works.

-------------
edit--
and if it worked you can restore the old flie (123.old from the recycle bin) back in and the shortcut should remain on pointing to the new one.

[Dyre Straits]

So, the bottom line is that it really can't be done like I'd want to do it. That is, simply edit the Target line as long as the 'dynamically linked' file is present. Is that correct?

[PangingJr]

Yes, that is correct.

we just have to play a trick on XP on this...
Once you deleted the source file, the shortcut becomes broken, if you still using that shortcut XP'll use 2 NTFS's features.. 1) File ID tracking 2) Comprehensive search, and try to repair the broken shortcut. but before XP can do that we put on a new source file for the shortcut and XP picks it up from there...
if you move or rename the source file, XP'll use those features and do auto edit to the target line and the broken shortcut is repaired.

------------
and..
when renaming/moving the source file (the present file with new name/difference location) i'd say you can still edit the target line of the shortcut by hand and this also when the File ID tracking and the Comprehensive search features had been turned off in windows registry.

[Dyre Straits]

Well, at least I know now what's going on and why.

The reason for doing as I'd done before was to be able to revert quickly to a previous file if something was drastically wrong with a newer one. All it required was simply editing the extension of the file names.

[PangingJr]

i do that all the time myself for trying to keep the old file for later use and by renaming it... for the shortcut, it may look as a long steps but its about the same, just have to rename it /delate / then put it back. or delete the old shortcut, then create a new one.

[Vampyromaniac]

Dyre, see if this helps?

Disable shortcut updating in Win2k/WinXP

If you move a file and by that disable any shortcuts referring to it, then Win2k/WinXP will try to make the shortcuts correct by searching the HDD to find the file again.

This can be annoying if changing HDD letters back and forth. One can disable this feature in the registry with this DWORD :

[HKEY_CURRENT_USER \Software \Microsoft Windows \CurrentVersion \Policies \Explorer]
NoResolveTrack = 1

More Info MS KB Q299780

[Dyre Straits]

Thanks!! That just might do the trick. I'll let you know.

EDIT: I'm expecting a new map to try sometime after the weekend. I'll give this a try. I've already created the DWORD and settings.

[Dyre Straits]

UPDATE: That Registry change worked like a charm! Thanks for posting that.

[Vampyromaniac]

No problem, buddy glad to help you out