It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Fallout Series"Failure initializing input devices"(20 posts)(20 posts)
(20 posts)
Pages:
1
2
This is my favourite topic
Posted September 29, 2008
Recently bought fallout 2 and after installing and launching the game first time round it worked perfectly. However, when attempting to launch a second time the screen goes black then flicks back to the desktop instantly, followed by the error message:
"Failure initializing input devices"
Does anyone have any idea whats going on? I run windows vista 32 if that helps.
Thanks guys!
No posts in this topic were marked as the solution yet. If you can help, add your reply
Posted September 29, 2008
avatar
dbirchinall: Recently bought fallout 2 and after installing and launching the game first time round it worked perfectly. However, when attempting to launch a second time the screen goes black then flicks back to the desktop instantly, followed by the error message:
"Failure initializing input devices"
Does anyone have any idea whats going on? I run windows vista 32 if that helps.
Thanks guys!
Did you mod it in anyway? I got some errors like this after installing the mode to turn the game into a windowed mode.
Posted September 29, 2008
No ive not modded it in anyway. Ive tried running it windowed and not windowed and i still get the same message.
Posted September 30, 2008
Deleting the ddraw.dll fixes the issue.
Posted October 02, 2008
The ddraw.dll thing didnt work, fallout still wouldnt open after modifying the file. Launched fallout recently though and it worked perfectly. Now, a day later, and its failing to open again. I suspect its a problem with my pc, not the game.
Posted October 14, 2008
Same problem in Fallout 1, except it never ran properly.
Posted May 23, 2009
Hey, if you're still having trouble with this---I just had the same problem, and I solved it by running the game under Windows 95 mode. Just right click the game's icon, click Properties, click on the Compatibility tab, and set the mode to Windows 95.
Hope that helps!
Posted January 10, 2010
The Work-Around:
After first launch of Fallout 2 and configuring the game as desired, edit fallout2.cfg and change "times_run=1" (or whatever number is displayed) to "times_run=0". Save. Right click the file > properties > enable Read-Only. Now times_run won't count up and you can keep playing. Read-only needs to be disabled for any settings to save again.
The logic:
First off, deleting ddraw.dll is NOT a solution. It simply disables sfall.
Google was little help with this issue, but did everyone's experience did provide the necessary pieces to solve the puzzle.
Essential Clue: Launches properly on first run.
I noticed that the first run did not prompt for registration information, but every run after (the ones that received the driver initialization error) did. Checking the fallout.cfg I noticed that the times_run counter (located under [system]) was incrementing properly. Turn it back to 0, and what happens? The game launches. So I made the file read-only after changing the times_run to 0.
What I would like to see happen:
It seems that this error is tied to BlackIsle prompting you to register. If anyone knows the location of the file or registry key that contains that information, please post it here so that I might try it for an actual solution then this work-around that I've posted.
Posted June 22, 2010
http://sfall.sourceforge.net/FAQ.html
Posted November 07, 2010
avatar
dbirchinall: Recently bought fallout 2 and after installing and launching the game first time round it worked perfectly. However, when attempting to launch a second time the screen goes black then flicks back to the desktop instantly, followed by the error message:

"Failure initializing input devices"

Does anyone have any idea whats going on? I run windows vista 32 if that helps.

Thanks guys!
I had the exact same problem, here's how I got it fixed:

I downloaded Sfall from http://sourceforge.net/projects/sfall/
Extracted it and took the 2 ddraw files to my Fallout 2 game file.
Opened the ddraw.ini with notepad and changed the following parts:
BackgroundKeyboard=1 (it was 0)
BackgroundMouse=1 (it was 0)
-in [graphics] Mode=5 (for DirecX9 windowed, it was 0)
-GraphicsWidth=1280
-GraphicsHeight=1024 (or what ever your resolution is, check it by right clicking your desktop and choosing Personalize, from there Display Settings).
Saved the file and started the game.

If the game says that your trying to run it in comatibility mode right click the Fallout2.exe file and uncheck all the compatibility ticks.

Hope this helps someone. This is such an awesome game I would hate it for someone not being able to play it.

EDIT:
The mouse going outside the game box started to bug me so I changed BackgroundMouse back to 0 and the game still works. I think the biggest issues with me were the BackgroundKeyboard being 0 and the resolution. I have two displays so I get a lot of resolution errors with games.
Post edited November 07, 2010 by Toffotin
Posted March 01, 2011
avatar
mars0124: The Work-Around:
After first launch of Fallout 2 and configuring the game as desired, edit fallout2.cfg and change "times_run=1" (or whatever number is displayed) to "times_run=0". Save. Right click the file > properties > enable Read-Only. Now times_run won't count up and you can keep playing. Read-only needs to be disabled for any settings to save again.

The logic:

First off, deleting ddraw.dll is NOT a solution. It simply disables sfall.

Google was little help with this issue, but did everyone's experience did provide the necessary pieces to solve the puzzle.

Essential Clue: Launches properly on first run.

I noticed that the first run did not prompt for registration information, but every run after (the ones that received the driver initialization error) did. Checking the fallout.cfg I noticed that the times_run counter (located under [system]) was incrementing properly. Turn it back to 0, and what happens? The game launches. So I made the file read-only after changing the times_run to 0.

What I would like to see happen:

It seems that this error is tied to BlackIsle prompting you to register. If anyone knows the location of the file or registry key that contains that information, please post it here so that I might try it for an actual solution then this work-around that I've posted.
First, I know that this is a zombie thread but seeing as people are continuing to have the problem (I myself ran into it today), I went ahead and posted.

I decided to tinker a bit and take this a step further since I don't like having to mark a file as Read-Only (never know if you need to change options later, remember to unmark it, etc). After poking around, I found the eregui.ini file in the ereg folder. Setting Run=No under the various sections (the Register Function section at least) disabled the registration altogether and the games works perfectly. Thanks go to the above for realizing it was the registration that was causing the problem. This fix solves the pesky notice AND fixes the game so I consider it a double-win.

Hope this helps!
Posted October 05, 2013
Just to chip in as I was also experiencing this error message in Win 7 64-bit.

What work for me was right-clicking the game, and under properties selected Run in 640 x 480 screen resolution.


I also left the run as admin ticked.
Posted October 17, 2013
I was trying to play Fallout 1 on a tablet ... turns out all I needed to do was plug in a mouse ...
Posted June 07, 2015
avatar
LordPorker: Just to chip in as I was also experiencing this error message in Win 7 64-bit.

What work for me was right-clicking the game, and under properties selected Run in 640 x 480 screen resolution.


I also left the run as admin ticked.
YEAH!
that fixed it. Thanks a bunch!
Posted October 01, 2015
For anyone else that has this problem, the thing i had to do was to un-plug my 360 controler
Pages:
1
2
This is my favourite topic
Community
Fallout Series"Failure initializing input devices"(20 posts)(20 posts)
(20 posts)