https://bugs.winehq.org/show_bug.cgi?id=50586
--- Comment #34 from Erich E. Hoover erich.e.hoover@gmail.com --- Created attachment 69360 --> https://bugs.winehq.org/attachment.cgi?id=69360 report unrecognized tag
(In reply to Arnaud Dovi from comment #33)
Created attachment 69353 [details] steps to reproduce
Hope it helps
That reproduces the error on startup really effectively, thanks. However, I don't know how to tell if I've fixed the (In reply to Arnaud Dovi from comment #33)
Created attachment 69353 [details] steps to reproduce
Hope it helps
Yes, thank you. I removed the internal uses where we get the link target, so I can confirm that this application is aware of reparse tags and that it is effectively responsible for the "problem": === 0168:fixme:file:FILE_GetSymlink MAGIC /home/ehoover/staging-50586/pfx/dosdevices/c:/Program Files/Black Tree Gaming Ltd/Vortex /home/ehoover/staging-50586/Vortex Mod Manager 0168:fixme:file:unix_to_nt_file_name /home/ehoover/staging-50586/Vortex Mod Manager: /Vortex Mod Manager (X:) ===
So, given that I can: 1) Fix this so that it "works" (reports the target properly) but gives you problems in terms of not properly finding everything. This is likely closest to what would happen on Windows if you set up the same situation with mklink. Is there any chance that you have a Windows box where you can verify that? 2) Report an unrecognized tag for unix symlinks (see hacky attachment, if you want to give that a try) 3) Hide the symlinks completely
Zeb, do you have thoughts?