Worm in a fitter warzone2100-2.3_beta1.exe

[gigabyte502]

What does it mean? Why at fitters constantly there are worms?

[cybersphinx]

Please report it to your anti-virus maker as a false positive.

[i-NoD]

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.

[Zarel]

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.

Or we could just bundle the DLLs directly...

[i-NoD]

Even if we obtain all the necessary files (there is only the re-distributable package available with the latest SDK), we still have handle 32/64 version problem ourself instead of relying on Creative installer.
How about supplying the pack but instead of enabled-by-default silent installation we'll set it optional and provide an additional link in wz section of start menu.
Btw current package is somewhat outdated...

[Zarel]

afaik, the current devpkg has latest OpenAL. So if the installer doesn't, tell Buggy to update to the latest devpkg.

And wouldn't we just bundle the 32-bit DLL? Since Warzone is 32-bit and all?

[cybersphinx]

The current devpackage contains a static OpenAL Soft, that should solve the installer problem.

[i-NoD]

And wouldn't we just bundle the 32-bit DLL? Since Warzone is 32-bit and all?

Obviously, yes. But, if someone have an x64 Windows then logically Creative redist installs the x64 version of the library, doesn't it?

The current devpackage contains a static OpenAL Soft, that should solve the installer problem.

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).

Or we can use cybersphinx's sound patch and then supplying both libraries will give more available devices to select.

[cybersphinx]

Obviously, yes. But, if someone have an x64 Windows then logically Creative redist installs the x64 version of the library, doesn't it?

Does a 64 bit DLL work with a 32 bit binary? On Linux, you need 32 bit libraries to run 32 bit binaries.

It's a dynamic one.

Actually it contains both, bin/OpenAL32.dll and lib/libopenal32.a...

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.

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 I don't think you can use both libraries at once to get the devices from both.)

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.

[Zarel]

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?

I would be fine with this solution.

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.

warzone2100-2.3_beta1.exe is the Warzone 2.3b1 installer. It extracts into and executes the OpenAL installer in silent mode.

[i-NoD]

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.

warzone2100-2.3_beta1.exe is the Warzone 2.3b1 installer. It extracts into and executes the OpenAL installer in silent mode.

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.

[cybersphinx]

Ah, so the problem isn't the Openal-installer itself, but the fact that our installer executes it. That makes sense, yes. I'm not used to all the new-fangled Windows malware stuff...

[i-NoD]

Actually it contains both, bin/OpenAL32.dll and lib/libopenal32.a...

Isn't libopenal32.a a stub for .dll i.e. dynamic? If it's a static then why do we have a .dll anyway?

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 I don't think you can use both libraries at once to get the devices from both.)

Check this info from OpenAL Soft 1.10

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.

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.
Still a dev could use OpenAl Soft version alone.

[gigabyte502]

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.

Really, I clean a tick with "OpenAL libraries" such anti-virus message I have not found out.

uncheck OpenAL.PNG

However, after installation, during game start deduces this message. What would it mean?

error.PNG

On a note:
My configuration of the personal computer.
The processor: Intel Core 2 Duo E450, 2x2,40 Hz
Operative memory: 2 GB
Video card: NVIDIA GeForce 8500 GT, 512 MB
Operational system: Windows XP Pro x86 SP3

[i-NoD]

It's an issue with the new PhysFS. You can try to add a --configdir <some latin-chars-only path> to WZ link.
Check this #1066 ticket for details.