We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

I recall there being a discussion about how none of the primary SDL developers had access to Vista for testing, yet.

At any rate, a blue screen means a kernel panic or driver bug, so it's possible that SDL isn't doing anything wrong here. We'll have to wait until someone gets Vista or someone debugs this, I guess.  :/

(Flagging this as ASSIGNED, since it'll be me that debugs it if a copy of Vista ever becomes available to me.)

--ryan.

Ryan,


thanks for your reply! :D
I don't know, if you have already read my other reply here:

http://www.libsdl.org/pipermail/sdl/2006-December/077553.html

?

In this reply I wrote, that Windows Vista Release Candidate 2 has already shown the same bug! Windows Vista Release Candidate 2 was released by Microsoft free to the public. So I think it would be enough, to get a copy of this from a bittorrent source and start debugging my example programm with this version of Vista.
For more details concerning build number and installation just read my link given above.

And yes, the released SDL version does something wrong, because the SDL-version
from the author of "Rocks'n'Diamonds" is slightly changed and with this Rocks'n'Diamonds doesn't crash Vista!
But I can't find the sources of the changed SDL on the homepage of Rocks'n'Diamonds, otherwise we could search for the change(s) the author (Holger Schemel) has made in his SDL-sources.


Alex

RC2 isn't available from Microsoft anymore, which means it would be considered pirating to get it from BitTorrent.

That being said, the most likely reason that one SDL works while another doesn't is that one is using DirectX and the other is using WinDib for 2D graphics, which would go down radically different paths in the OS video drivers.

(Or perhaps one is using waveout for audio instead of directsound? One is using 2D graphics and the other wants OpenGL? I'm just trying to think of places where we touch hardware...)

Anyhow, we _will_ fix this eventually.

--ryan.

Ok, I'll look forward for a fix / new version of SDL.
If I can be of any help for you in this process, just email me.

Alex

Hi Ryan,


I just found a temporary workaround for the problem, that the newest SDL-Version creates a bluescreen when called from a MinGW compiled programm under Vista, when calling SDL_Init()!

Of course you should better inspect the SDL-code, configure script or makefile, because my solution only works, when the coder of the programm which needs the SDL has a computer with Vista, where he / she can compile the SDL.dll for himself / herself!

O.K., now how did I fix my problem?
I just found out, that when compiling the SDL.dll under Vista with MinGW, then the MinGW-programm which needs the SDL.dll runs fine with no bluescreen! But it will create a bluescreen again, when the SDL.dll is compiled with MinGW under XP!
Both SDL-versions differ in size and I don't know why! The version compiled under XP has a size of 2634 KByte and the version compiled under Vista has a size of 1641 KByte!
When I look at both sizes I wonder why these are so big, when compared with the one on the official SDL-donwload page? I think your makefile has no strip-parameter for the MinGW-compiler in it(?), but this is only an assumption!


Greetings
  Alex

Bumping a bunch of bugs to Priority 1 for consideration for the 1.2.12 release.

--ryan.

Updated the URL for the original issue:
http://lists.libsdl.org/pipermail/sdl-libsdl.org/2006-December/058893.html

I just ran an SDL program that I built under cygwin on Vista and it worked fine for me.  I tried downloading your example zip file and I couldn't get it.  Can you attach it to this bug so I can try again?

I just tried the latest SDL 1.2 snapshot cross-compiled with the latest cross-compiler tools and also had no problems.

Maybe your XP machine is running an old release of the build environment?

I'm marking this bug invalid for now, pending new information.