And? What happened?
Just the same thing Leo. It shows on Drive "I" right into the "~Images~~ folder, but when I click into the Icons folder, it changes into Drive"C".
I posted both the the True Launch board (Creates the Images folder) and on the Windows Secrets lounge to see if there are any hints.
Regards,
Chuck Billow
Sorry but it's really difficult to follow this thread and make suggestions when the answers/descriptions are vague and/or contain errors/typos which change their meanings. It's already an unusual and hard to understand issue without us having to second-guess the details.
Please give the full paths (not just drive letters) in descriptions, and please explain (for example) which folder you renamed, what you renamed it to, and exactly what you did and what happened as a result, making sure the drive letters and folder names are all correct. (Or just use more before & after screenshots.)
Guys, I'm sorry, I found it.
I copied all the ICO files to another folder, and then deleted the Icons folder, set up a new one, putting just the ICO files back, and now it's fine.
There (obviously) had to be some type of file there issuing some sort of directive that I wasn't catching.
Thanks,
Chuck
What non-icon files were in the folder which didn't get copied this time?
They're probably the key to what happened and it'd be good to understand in case it happens again.
[quote="leo"]What non-icon files were in the folder which didn't get copied this time?
They're probably the key to what happened and it'd be good to understand in case it happens again.[/quote]
Leo, I had deleted everything from the "bad" folder, but I went back to an image of the drive from a couple days ago, and the attached list of (non-ico) files were in the folder.
Even to my novice eye, it seems that the key here was/is the target.lnk file. But I have no idea where that came from at all, or for what purpose. It was just sitting there buried among the hundreds of icon files...
Again, apologize, for I should have caught this in the first pass...
Regards,
Chuck
list.txt (933 Bytes)
Or at least in the pass where I specifically told you to look for it...
Leo, the part that totally confounds me is why Total Commander and Explorer both walked right past any problem, giving me the "correct" drive. That was in part why I never suspected having missed something. I only (finally) created the new folder more out of frustration than anything else. And I sure wouldn't have been looking for a shortcut! Why did that "automatically" execute?
I'm just sorry to have wasted your time on this blunder...
Chuck
You keep saying Leo in reply to Jon. 
Explorer requires a few more things to be in place before it will follow a target.lnk; Jon & I are looking into that at the moment with the aim of making Opus consistent with Explorer.
I don't have Total Commander installed so I'm not sure if it uses the same rules as Explorer or if it follows target.lnk files at all.
Good thing I'm not trying to be a demolitions expert, huh?
Chuck