https://bugs.winehq.org/show_bug.cgi?id=56886
Bug ID: 56886 Summary: Wincatalog can't scan folders Product: Wine Version: 9.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dark.shadow4@web.de Distribution: ---
Download at https://www.wincatalog.com/download/wincatalog_setup_2024_7_5_612_anycpu.exe Archived at https://web.archive.org/web/20240629011906/https://www.wincatalog.com/downlo...
On start of the program you get get a crash (bug 56885), ignore that.
To test: - Install the program all with default options - Create new catalog (just press save to put it in the default folder) - Click "Folder" in the toolbar (5th from left), select a folder.
It gives the error "Cannot open catalog file /path/to/file writing"
For best results use a clean WINEPREFIX and AFAIK it must be 64bit for the error to happen.
https://bugs.winehq.org/show_bug.cgi?id=56886
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://www.wincatalog.com/ | |download/wincatalog_setup_2 | |024_7_5_612_anycpu.exe
https://bugs.winehq.org/show_bug.cgi?id=56886
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- This program is pretty finicky for me, so I'm not really sure about most of my analysis here. Re-testing would be appreciated! FWIW, I'm using the new wow64, but it seems to affect normal biarch wine builds as well.
Bisected to commit 9dca2a707269dce7723e5a72204220560d3641d7 Author: Alexandre Julliard julliard@winehq.org Date: Tue May 14 12:28:51 2024 +0200
ntdll: Update PROCESSOR_ARCHITECTURE variable correctly for ARM platforms.
https://bugs.winehq.org/show_bug.cgi?id=56886
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- Created attachment 76705 --> https://bugs.winehq.org/attachment.cgi?id=76705 Logs
Attaching some logs where I made RtlSetEnvironmentVariable always output, this shows a difference in the detected architecture.
https://bugs.winehq.org/show_bug.cgi?id=56886
Michael R. michael@wincatalog.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |michael@wincatalog.com
--- Comment #3 from Michael R. michael@wincatalog.com --- The issue relates to .NET Framework 4.8. The main module of WinCatalog is a native MFC application, and it works without issues. The Scanning Module is a .NET Framework 4.8 (WinForms) app (.exe) and it doesn't work. To reproduce: Click Add Disk -> Select a Disk -> OK.
The Scanning Options is a .NET Framework 4.8 (WPF) app (.exe), and it doesn't work. To reproduce: Click the Scanning Options button on the toolbar.
Both modules worked well in WineHQ 9.0 (the last version they were tested).
https://bugs.winehq.org/show_bug.cgi?id=56886
--- Comment #4 from Michael R. michael@wincatalog.com --- (In reply to Michael R. from comment #3)
The scanning module: w3DiskScanner.exe The scanning options module: ScanningOptions.exe
https://bugs.winehq.org/show_bug.cgi?id=56886
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- If I click "Scanning Options" a new windows opens, seems to work. Let's make this issue about the "Cannot open catalog file /path/to/file writing" error.
From time to time I get a "Window class name is not valid" error, but that's different as well.
https://bugs.winehq.org/show_bug.cgi?id=56886
Sven Baars sven.wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |9dca2a707269dce7723e5a72204 | |220560d3641d7
--- Comment #6 from Sven Baars sven.wine@gmail.com --- Confirming the bug and the commit. The commit reverts cleanly. For me, in new wow64, it indeed changed behavior.
Before:
PROCESSOR_ARCHITECTURE: L"AMD64" PROCESSOR_ARCHITEW6432: L""
After:
PROCESSOR_ARCHITECTURE: L"x86" PROCESSOR_ARCHITEW6432: L"AMD64"
https://bugs.winehq.org/show_bug.cgi?id=56886
--- Comment #7 from Sven Baars sven.wine@gmail.com --- I still haven't figured out the exact implementation, but I found at least one issue with the current implementation.
if (CreateProcessA( "C:\windows\syswow64\msinfo32.exe", NULL, NULL, NULL, FALSE, 0, NULL, NULL, &si, &pi )) { [get the env from pi] query_env_var(env, L"PROCESSOR_ARCHITECTURE", is_win64 ? L"AMD64" : L"x86"); query_env_var(env, L"PROCESSOR_ARCHITEW6432", is_win64 ? NULL : L"AMD64"); }
The above test works for me on windows but fails for me on wine. The exact issue with this application is a bit different, but it's similar in the sense that the native machine is not reported where it should be.
Putting back the old code, but replacing
RtlInitUnicodeString( &nameW, L"x86" ); RtlSetEnvironmentVariable( env, &arch_strW, &nameW );
with RtlSetEnvironmentVariable( env, &arch_strW, get_machine_name( machine, &nameW ));
fixes the application and the above test.
https://bugs.winehq.org/show_bug.cgi?id=56886
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |2c61d236b177f18f409200c1a46 | |8720428a1ea16 Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- Hopefully fixed by 2c61d236b177f18f409200c1a468720428a1ea16.
https://bugs.winehq.org/show_bug.cgi?id=56886
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 10.0-rc5.
-
WineHQ Bugzilla