Why is there "OpenAL32.dll" in the 64bit builds, this aught to be changed too OpenAL64.dll"
SDL2.dll is not needed anymore either.
SDL2.dll is not needed anymore either.
Removing Support for 32bit Windows?
|
Why is there "OpenAL32.dll" in the 64bit builds, this aught to be changed too OpenAL64.dll"
SDL2.dll is not needed anymore either.
Because the official name of that library is OpenAL32.dll even if it was 64bit.
From OpenAL Soft's readme.txt: (note: even the 64-bit DLL should be named OpenAL32.dll)
I liked the part where it worked, except there was no such part.
05-27-2014, 12:54 PM
That seems to be an LWJGL thing. Every result I get on google for OpenAL64.dll involves being stored in a natives or natives/windows folder along with lwjgl related things.
My guess is because all of lwjgl's natives get stored in one folder, and you couldn't have OpenAL32.dll and OpenAL32.dll because name clash.
I liked the part where it worked, except there was no such part.
05-28-2014, 07:04 AM
This is going to blow your mind; the System32 folder has the 64bit files and the SysWOW64 has the 32bit files.
05-28-2014, 07:08 AM
(This post was last modified: 05-28-2014, 07:11 AM by DJBarry004.)
Uh, no. The System32 folder has some X64 files and the rest is X86.
Add: There seems to be a mix of the DLLs of both versions (X64 & X86) on those two folders. Rig 1: Windows 10 Home | AMD A6-1450 @ 600/1000/1400 MHz | AMD Radeon HD Graphics 8250 | 4GB RAM | HP Pavilion TouchSmart 11.
Rig 2: Windows 10 Pro | Intel Core i7-2640M @ 780/2800/3500 MHz | Intel HD 3000 Mobile | 8GB RAM | Dell Latitude 6320.
05-28-2014, 09:48 AM
(05-28-2014, 07:08 AM)DJBarry004 Wrote: Uh, no. The System32 folder has some X64 files and the rest is X86. Wrong again. What lamedude said is right. System32 will have only x64 DLLs and SysWOW64 will have only x86. If a DLL has both a x86 and a x64 version, it'll be present in the two folders...
Avell A70 MOB: Core i7-11800H, GeForce RTX 3060, 32 GB DDR4-3200, Windows 11 (Insider Preview)
ASRock Z97M OC Formula: Pentium G3258, GeForce GT 440, 16 GB DDR3-1600, Windows 10 (22H2) 05-28-2014, 10:19 AM
The WOW64 is shorthand for Windows On Windows 64-bit, so it actually makes some sense that that's where all the backwards-compatibility files would be kept. Why System32 is still called System32, however, is unclear. Maybe they'd hardcoded it in so many places that they couldn't change it.
OS: Windows 10 64 bit Professional
CPU: AMD Ryzen 5900X RAM: 48GB GPU: Radeon 7800 XT 05-28-2014, 11:07 AM
Well, there used to be "System", back in the 16bit windows days. Then 32bit was an "addon" to windows 98, and the System32 folder was created or something in that process, and the trend just stuck for Windows XP...
...it's just crazy, don't look into it. AMD Threadripper Pro 5975WX PBO+200 | Asrock WRX80 Creator | NVIDIA GeForce RTX 4090 FE | 64GB DDR4-3600 Octo-Channel | Windows 11 23H1 | (details)
MacBook Pro 14in | M1 Max (32 GPU Cores) | 64GB LPDDR5 6400 | macOS 12
05-28-2014, 01:58 PM
Idiots like to hardcode. MS probably did it to avoid my program breaks on Win64 "Nothing’s wrong with it. It compiles" bug reports.
|
« Next Oldest | Next Newest »
|