https://bugs.winehq.org/show_bug.cgi?id=43651
Bug ID: 43651 Summary: Engine Prime: can only add tracks if under C: drive Product: Wine Version: 2.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: smidge@xsco.net Distribution: ---
Created attachment 59077 --> https://bugs.winehq.org/attachment.cgi?id=59077 Log file adding a track via Z: drive (faulty)
Engine Prime is a music preparation application targeted at DJs who use Denon's latest hardware. It can be downloaded at http://www.denondj.com/engineprime
Engine Prime 1.0.0 starts up successfully if d3dcompiler_46.dll and d3dcompiler_47.dll are disabled. But a track can only be added to the collection via the Filesystem Browser if it is accessed via the C: drive. Trying to add a track via the Z: drive (mapped to root) silently fails to add the track to the collection.
Steps to reproduce:
* Clean wine prefix. * Install Engine Prime 1.0.0 (link above) * Copy an MP3 file of your choice to somewhere under drive_c. * Copy another MP3 file of your choice to somewhere else on your filesystem accessible via a drive mapped in Wine, e.g. the Z: drive * Start Engine Prime as follows: env WINEDLLOVERRIDES="d3dcompiler_46.dll=d;d3dcompiler_47.dll=d" wine ~/.wine/drive_c/Program\ Files\ (x86)/Engine\ Prime/EnginePrime.exe * Observe empty music collection (try clicking on "Collection")
"Good" route: * Select the Filesystem Browser * Navigate to the folder containing the 1st MP3 file from earlier (under C: drive) * Click the folder to show the file in the main pane to the right * Right-click the track, choose Add to Collection * Click on Crates, then click on Collection * Observe that the MP3 file has been added to the collection successfully
"Bad" route: * Select the Filesystem Browser * Navigate to the folder containing the 2nd MP3 file from earlier (under Z: drive) * Click the folder to show the file in the main pane to the right * Right-click the track, choose Add to Collection * Click on Crates, then click on Collection * Observe that the MP3 file has *NOT* been added to the collection successfully
Logs for the good and bad route attached.
https://bugs.winehq.org/show_bug.cgi?id=43651
--- Comment #1 from Adam Szmigin smidge@xsco.net --- Created attachment 59078 --> https://bugs.winehq.org/attachment.cgi?id=59078 Log file adding a track via C: drive (working)
https://bugs.winehq.org/show_bug.cgi?id=43651
--- Comment #2 from Adam Szmigin smidge@xsco.net --- The main difference I can see from the logs is that when loading a file from the Z: drive, the following lines appear in the log:
(the sample file I used is under /srv/media/music/unmixed/Acid House)
fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\" fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\" fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv" fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv" fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media" fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media" fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media\music" fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media\music" fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media\music\unmixed" fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media\music\unmixed" fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media\music\unmixed\Acid House" fixme:file:GetLongPathNameW UNC pathname L"\\?\Z:\srv\media\music\unmixed\Acid House" fixme:file:FindFirstFileExW flags not implemented 0x00000002
No such lines are logged when choosing a file from the C: drive. Perhaps looking at the Z: drive from Engine Prime is treated as a UNC path somehow?
Additionally, Engine Prime does not show any drive letters I have assigned besides C: and Z: - in my case I mapped M: to /srv/media. This may or may not be related.
https://bugs.winehq.org/show_bug.cgi?id=43651
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |43599
https://bugs.winehq.org/show_bug.cgi?id=43651
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download CC| |dark.shadow4@web.de
https://bugs.winehq.org/show_bug.cgi?id=43651
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.denondj.com/engi | |neprime
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- Filling in a few fields.
Sorry, can't really test it since it doesn't show anything but "C:" for me, and it doesn't run in my VM.
https://bugs.winehq.org/show_bug.cgi?id=43651
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |43652
https://bugs.winehq.org/show_bug.cgi?id=43651
--- Comment #4 from Adam Szmigin smidge@xsco.net --- Hi Fabian,
In case it helps, running the application as follows (relative path to exe) causes Z: to *not* be visible in the filesystem browser:
$ cd ~/.wine/drive_c/Program\ Files\ (x86)/Engine\ Prime/ $ WINEDLLOVERRIDES="d3dcompiler_46.dll=d;d3dcompiler_47.dll=d" wine EnginePrime.exe
... but running it with an absolute path *does* cause Z: to show up:
$ WINEDLLOVERRIDES="d3dcompiler_46.dll=d;d3dcompiler_47.dll=d" wine ~/.wine/drive_c/Program\ Files\ (x86)/Engine\ Prime/EnginePrime.exe
Hope this helps,
Adam
https://bugs.winehq.org/show_bug.cgi?id=43651
--- Comment #5 from Fabian Maurer dark.shadow4@web.de ---
... but running it with an absolute path *does* cause Z: to show up: $ WINEDLLOVERRIDES="d3dcompiler_46.dll=d;d3dcompiler_47.dll=d" wine ~/.wine/drive_c/Program\ Files\ (x86)/Engine\ Prime/EnginePrime.exe
Now I get it, it only shows up when starting the exe while the working directory is outside of "C:", but inside of "Z:". This way you can also make "F:" show up, just make the working directory in the folder that is mapped as "F:".
That by itself is very odd, does it behave like that on windows, too?
However, I can now reproduce the issue. But only for Z:, if I for example run it from F:\ (mapped as /home/fabian/Ramdisk) it works fine. Very odd, indeed.
https://bugs.winehq.org/show_bug.cgi?id=43651
--- Comment #6 from Adam Szmigin smidge@xsco.net --- Hi Fabian,
(In reply to Fabian Maurer from comment #5)
Now I get it, it only shows up when starting the exe while the working directory is outside of "C:", but inside of "Z:". This way you can also make "F:" show up, just make the working directory in the folder that is mapped as "F:".
That by itself is very odd, does it behave like that on windows, too?
I don't have access to a Windows machine to test, unfortunately.
I'll try this out with other drive mappings to confirm your findings too..
Regards, Adam
https://bugs.winehq.org/show_bug.cgi?id=43651
--- Comment #7 from Adam Szmigin smidge@xsco.net --- Possible hint from the Denon DJ FAQ: http://denondj.com/kb/article/2236#read_only
Why can’t I add songs from read-only media to my collection?
Engine Prime creates and stores the database on the same drive(s) that store the tracks. This means that drives/media must have write access enabled to work with Engine Prime. Typical read-only situations include locked SD cards, CDs or other ROM media, and 12” Vinyl Discs.
I'll test this out.
https://bugs.winehq.org/show_bug.cgi?id=43651 Bug 43651 depends on bug 43599, which changed state.
Bug 43599 Summary: Engine Prime 1.0.0 crashes due to HLSL compilation failure https://bugs.winehq.org/show_bug.cgi?id=43599
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
-
wine-bugs＠winehq.org -
WineHQ Bugzilla