I've tried several times to install X11-Basic and I keep the following error message:
C:\WINDOWS\system32\SDL.dll Unable to register the DLL/OCX: RegSvr32 failed with exit code 0x4.
I'm running Windows 8.1
You seem to have CSS turned off. Please don't fill out this field.
I get the same error on Windows 7. I had to use the .zip install package for an older version.
same error under W10 64bits
Happened same on Win7 32bit and 64bit also... My installer made by Inno Setup recent version. This X11 can have the same.
Yes, the X11-Basic installer is made with Inno-Setup. I dont know what might be wrong there. Has anybody any good idea?
I can confirm - have same problem (Win 10)
I have analyzed this problem: It can safely be ignored. Simply press the ignore button on that message.
However this should be fixed in the new release 1.25-47.
Log in to post a comment.
View and moderate all "MS WINDOWS version of X11-Basic" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I've tried several times to install X11-Basic and I keep the following error message:
C:\WINDOWS\system32\SDL.dll
Unable to register the DLL/OCX: RegSvr32 failed with exit code 0x4.
I'm running Windows 8.1
View and moderate all "MS WINDOWS version of X11-Basic" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I get the same error on Windows 7.
I had to use the .zip install package for an older version.
View and moderate all "MS WINDOWS version of X11-Basic" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
same error under W10 64bits
View and moderate all "MS WINDOWS version of X11-Basic" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Happened same on Win7 32bit and 64bit also...
My installer made by Inno Setup recent version. This X11 can have the same.
Yes, the X11-Basic installer is made with Inno-Setup. I dont know what might be wrong there. Has anybody any good idea?
I can confirm - have same problem (Win 10)
I have analyzed this problem: It can safely be ignored. Simply press the ignore button on that message.
However this should be fixed in the new release 1.25-47.
Last edit: Markus Hoffmann 2017-03-09