Skip to main content
GameDev.net gamedev.net
🔒 Locked

Runtime Error in SDL

Started by GamerDude27 Feb 28, 2007 at 4:53 PM 5 replies 1.1k views
Original Post
GamerDude27
GamerDude27
Alright I am running a simple image loading program and it compiles alright, but when it runs it gives me this error: The application or DLL C:\Dev-Cpp\Bin\tiff.dll is not a valid Windows image. Please check this against your installation diskette. I have no idea what this means seeing as I'm not trying to load an image called tiff.dll. Does anyone know what this means?
Kylotan
Kylotan
It means an executable image - ie. that file isn't a proper executable file. It's one of the dependencies for SDL_Image, and it sounds like you may have a corrupt version of it. Try re-downloading whatever package you're using.

Also consider upgrading from Dev-Cpp to something better supported such as Code::Blocks or a free version of Visual Studio, since Dev-CPP is not incredibly good and isn't well supported any more, and that may be a problem if you're trying to get DevPaks to work.
GamerDude27
GamerDude27
Hmm... Tried reinstalling devpacks and I get the same error. I kinda like Dev C++ and I've tried Visual Studio and switched back to Dev C++. Anyone have another idea?
GamerDude27
GamerDude27
Does anyone else have an idea or an opinion on changing compilers?
rip-off
rip-off
Quote:
Original post by GamerDude27
Does anyone else have an idea or an opinion on changing compilers?


I think its not a compiler issue, the dll is corrupt somehow. Why not go to the SDL_image homepage and download a fresh copy of the dlls. See if that works.
GamerDude27
GamerDude27
Ahh I got it to work. The thing was that I had a working dll under Dev-CPP/bin
but not in Windows/windows32. Thank you for all of your help.
Ravuya
Ravuya
You should not put SDL DLLs into the system32 folder; this has caused compatibility issues in the past where software you are compiling is built against a later version of SDL, but when the program is run, Windows retrieves the older version in system32 first and crashes in a rather embarassing fashion.

You should put the SDL DLLs with your executable file; this directory will always take precedence over the system32 folder.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.