Quote:
Originally Posted by abror
is there a way to get rid of the popup at the start of this install?
Attachment 32723 |
Comment out lines 4219 and 4220 of the script with
//
Code:
//if (FailWinEleven = '') and (MessageBox(WizardForm.Handle, 'Some of the methods used in this compression may not be supported by Windows 11.' + #13#10 + #13#10 + 'Would you like to continue anyway?', SetupMessage(msgSetupAppTitle), MB_ICONQUESTION or MB_YESNO or MB_TASKMODAL) <> IDYES) then
// Exit;
But be aware that this is a warning and that installation errors may occur because one of the methods is not supported by Windows 11.
Quote:
Originally Posted by Masquerade
QuickSFV will display this error if there are spaces in the file path where the MD5 checksum is stored. The string needs wrapping in quotation marks.
|
Try changing line 5231 of the script as shown below:
Code:
ShellExec('open', ExpandConstant('{app}\QuickSFV.exe'), AddQuotes(ExpandConstant('{app}\{#QuickSFVFile}')), '', SW_SHOWNORMAL, ewWaitUntilTerminated, ResultCode);
Quote:
Originally Posted by Masquerade
Seconding this, which methods are supposedly not working on Windows 11? I have been making my repacks under Windows 11 for months now and have not encountered any such problems. If there's anything you would like testing, just ask.
|
From what I've understood so far they are: xt_zlib (xzlib), xt_lzo (xlzo), xtool:manvil:lzo, xtool:mfc3, xtool:mfc4, lzorec
For the xt_zlib method (from the old xtool) the old DLL zlibwapi.dll (102 Kb) was replaced by the DLL used with the new XTool (523 Kb) and the problem was fixed (I hope it has the same compression gain).
For errors in the other methods above the incompatible library is lzo2.dll (103 Kb) which does not work with Windows 11.
You can blacklist the DiskSpan GUI new methods that occur extraction errors in windows 11, for this include in the FailWinEleven= key of the [SETTINGS] section of DSG_Methods.ini.
The methods listed if used will show a warning to the user before compression and also during installation.
For errors of this type to occur, it is necessary to compress it on Windows 10 or lower and install it on Windows 11.
Compressing on windows 11 will not show errors even during installation because the libraries will be ignored and there will be no precompression (Ratio 100%).