Worm in a fitter warzone2100-2.3_beta1.exe
Posted: 17 Nov 2009, 12:35
What does it mean? Why at fitters constantly there are worms?
Strategy by Design
https://forums.wz2100.net/
Or we could just bundle the DLLs directly...i-NoD wrote:It's definitely not a worm, but rather a KIS heuristics reaction on silent sub-install. Just uncheck 'OpenAL libraries' during components selection and try again, there will be no warning this time. Btw KIS has reacted this way on any WZ install for ages.
Obviously, yes. But, if someone have an x64 Windows then logically Creative redist installs the x64 version of the library, doesn't it?Zarel wrote:And wouldn't we just bundle the 32-bit DLL? Since Warzone is 32-bit and all?
It's a dynamic one. And we could use dynamic version to supply both a OpenAL Soft (should be default one due to 5.1 capability) and a Creative libraries (fallback version due to Generic Sofware compatibility device).cybersphinx wrote:The current devpackage contains a static OpenAL Soft, that should solve the installer problem.
Does a 64 bit DLL work with a 32 bit binary? On Linux, you need 32 bit libraries to run 32 bit binaries.i-NoD wrote:Obviously, yes. But, if someone have an x64 Windows then logically Creative redist installs the x64 version of the library, doesn't it?
Actually it contains both, bin/OpenAL32.dll and lib/libopenal32.a...i-NoD wrote:It's a dynamic one.
Is there any reason not to just use OpenAL Soft always? If I understood the Windows hack correctly, it was done because the Creative OpenAL doesn't support many channels with its default device (and no 5.1 with the other one...). Doesn't OpenAL Soft fix that?And we could use dynamic version to supply both a OpenAL Soft (should be default one due to 5.1 capability) and a Creative libraries (fallback version due to Generic Sofware compatibility device).
Or we can use cybersphinx's sound patch and then supplying both libraries will give more available devices to select.
I would be fine with this solution.cybersphinx wrote:Is there any reason not to just use OpenAL Soft always? If I understood the Windows hack correctly, it was done because the Creative OpenAL doesn't support many channels with its default device (and no 5.1 with the other one...). Doesn't OpenAL Soft fix that?
warzone2100-2.3_beta1.exe is the Warzone 2.3b1 installer. It extracts into and executes the OpenAL installer in silent mode.cybersphinx wrote:Edit: Why are we talking about OpenAL in this worm thread anyway? The screenshot shows a complaint about warzone2100-2.3_beta1.exe, not any Openal-installer.
And this action is usually classified as suspicious by AntiVirus software. I saw this before, but usually I'm not installing an outdated OpenAL, so my AV is not producing such warning.Zarel wrote:warzone2100-2.3_beta1.exe is the Warzone 2.3b1 installer. It extracts into and executes the OpenAL installer in silent mode.cybersphinx wrote:Edit: Why are we talking about OpenAL in this worm thread anyway? The screenshot shows a complaint about warzone2100-2.3_beta1.exe, not any Openal-installer.
Isn't libopenal32.a a stub for .dll i.e. dynamic? If it's a static then why do we have a .dll anyway?cybersphinx wrote:Actually it contains both, bin/OpenAL32.dll and lib/libopenal32.a...
cybersphinx wrote:Is there any reason not to just use OpenAL Soft always? If I understood the Windows hack correctly, it was done because the Creative OpenAL doesn't support many channels with its default device (and no 5.1 with the other one...). Doesn't OpenAL Soft fix that?
Check this info from OpenAL Soft 1.10cybersphinx wrote:(And I don't think you can use both libraries at once to get the devices from both.)
It's expected that end-user will install Creative bullet-proof OpenAl32.dll plus router/wrapper which will gather additional devices from all native/additional OpenAL implementations. So, OpenAL Soft library default name is 'soft_oal.dll' since it's additional to Creative one. And yes it gives more devices that Creative library by itself.Note that it is still expected to install the OpenAL redistributable provided by Creative Labs (at http://openal.org/), as that will provide the "router" OpenAL32.dll that applications talk to, and may provide extra drivers for the user's hardware. It will also provide 64-bit DLLs. The DLL provided here will simply add additional devices for applications to select from. If you do not wish to use the redistributable, then simply rename soft_oal.dll to OpenAL32.dll.. just be aware this will prevent other system-installed OpenAL implementations from working.
To use it, copy the DLL from the Win32 folder to the folder OpenAL32.dll is installed in.
For 32-bit Windows, the Win32 DLL will typically go into the system32 folder.
For 64-bit Windows, the Win32 DLL will typically go into the SysWOW64 folder. There is no Win64 DLL provided at this time.
Really, I clean a tick with "OpenAL libraries" such anti-virus message I have not found out.i-NoD wrote:It's definitely not a worm, but rather a KIS heuristics reaction on silent sub-install. Just uncheck 'OpenAL libraries' during components selection and try again, there will be no warning this time. Btw KIS has reacted this way on any WZ install for ages.