Hello SDL,
I searched Google for this but found nothing so I assume it’s a new
question.
I had an interesting adventure here on the old windows 2000 machine.
All of the sudden for no reason that I can determine, any SDL
application I ran gave me this error:
Couldn’t initialize SDL: DirectInputDevice::SetDataFormat: Invalid parameter
I recompiled, rebooted, nothing helped. Then it seemed to fix itself,
and now all the programs work again. I have zero ideas why this
happened. Can anyone provide advice? Thanks for any insight.
System: win2000 will all patches, AthlonXP, via KT133A chipset,
GeForce4ti running latest drivers from nVidia.
-ray
Ray Skoog wrote:
Hello SDL,
I searched Google for this but found nothing so I assume it’s a new
question.
I had an interesting adventure here on the old windows 2000 machine.
All of the sudden for no reason that I can determine, any SDL
application I ran gave me this error:
Couldn’t initialize SDL: DirectInputDevice::SetDataFormat: Invalid
parameter
I recompiled, rebooted, nothing helped. Then it seemed to fix itself,
and now all the programs work again. I have zero ideas why this
happened. Can anyone provide advice? Thanks for any insight.
System: win2000 will all patches, AthlonXP, via KT133A chipset,
GeForce4ti running latest drivers from nVidia.
I had some more thoughts on this… this is caused by my choice of
mouse, isn’t it? I actually hot-swap my Mac’s USB mouse and keyboard
back and forth between Mac and PC, and I have randomly determined that
this error occurs only when I do not have a multi-button mouse plugged
in as well. Is this a bug?
-ray
Hello SDL,
I searched Google for this but found nothing so I assume it’s a new
question.
I had an interesting adventure here on the old windows 2000 machine.
All of the sudden for no reason that I can determine, any SDL
application I ran gave me this error:
Couldn’t initialize SDL: DirectInputDevice::SetDataFormat: Invalid parameter
I recompiled, rebooted, nothing helped. Then it seemed to fix itself,
and now all the programs work again. I have zero ideas why this
happened. Can anyone provide advice? Thanks for any insight.
Is it possible that Windows didn’t think that a mouse was attached?
See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment
Is it possible that Windows didn’t think that a mouse was attached?
See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment
Nope, I was using that one-button mouse to double-click the .exe.
Windows knew it was there. I could then just plug in the multi-button
one, it would work, unplug, it would not work, back and forth as many
times as I liked. I could even use the one-button mouse to launch and
operate the app if the multi-button one was plugged in.
Oh well, since I found my problem this is more of a “for you
information” than a “must fix,” as far as I am concerned.
-ray