Dolphin 3.0 does not start...

[Apache Thunder]

Dolphin 2.0 worked great for me. So I saw that 3.0 was released a few weeks ago so I went and upgraded to it. Now I can't use Dolphin at all.

When I try to start Dolphin nothing happens. As in absolutely nothing. No error, no window comes up, nothing. If a process even appears in Task Manager, it will vanish to quick to even see it.

The only other thread I could see regarding this issue was made back in 2009 and obviously is not relevent to my problem because v2.0 worked fine for me.

I have Windows XP 64-bit Edition. Both the 32bit and 64 bit versions of Dolphin 2.0 worked fine.

I did not try the 32bit version of 3.0 and will not bother with it since I have 6GB of ram and wish to use the 64 bit version for obvious reasons. No I will NOT use Windows Vista/7 just to run this emulator. Also, Service Pack 3 does not exist for Windows XP 64-bit, so don't suggest that either.

I just love how the makers of this great program have decided to throw us Xp64bit users out to pasture. Because it seems like they did something to majorly screw it up for my OS.

I have tried Lectrode's SVN build of v3.0 and it has the same issue. So I'm sure all the SVN builds out there won't work for me either unless someone made a SVN build that specifically addresses this issue, then please do point me in the right direction.

I have tried

[neobrain]

Windows XP x64 is not supported, unless you're compiling Dolphin yourself.

EDIT: Complain to Billiard

[Apache Thunder]

Any specific reason why it's not supported?

[neobrain]

Billiard decided we need to make use of some post Windows Vista only threading function on x64 for zero benefit if I recall correctly.

See http://code.google.com/p/dolphin-emu/source/detail?r=7294 .

[Anti-Ultimate]

Who uses Windows XP 64-Bit these days anyway ?

It's too old, has more bugs then the x86 Version and it's slower than 7...

What i wanted to say:

There are like only 100 People on the world that use XP 64-Bit nowadays...
Please upgrade.

[Apache Thunder]

(07-21-2011, 06:46 AM)Anti-Ultimate Wrote: Who uses Windows XP 64-Bit these days anyway ?

It's too old, has more bugs then the x86 Version and it's slower than 7...

What i wanted to say:

There are like only 100 People on the world that use XP 64-Bit nowadays...
Please upgrade.

Uhm no thanks. One big reason I won't upgrade is that there is no upgrade path to Windows 7 from a XP installation. It would have to be a full reinstall and I would lose setting and stuff to all my installed applications. (don't even try to suggest using the Transfer wizard, it transfer the important registry settings for installed applications so that they would still work. I would still have to reinstall all my apps! Plus it's a piece of crap... )(I have like 4 or 5 different versions of 3DS Max installed right now. I don't want to have to go through reinstalling them or finding out one or more versions of them don't work in Win7 + I have literally at least 40-50 other applications installed right now). I have a lot of stuff configured and WinXP 64 bit has worked like a champ for me for a good 1 and half years straight without any major issues. (the main reason for switching to it was a major hardware upgrade. So perhaps on my next hardware upgrade I might get Windows 7 for once)

As such, I will NOT go through another reinstall to get to Windows 7 just to use one or two new programs. I do have Win7 installed as a secondary OS, but switching to it is a pain and it lacks 90% of all the stuff I have installed on my XP OS.

The main reason I don't like Win7 right now is that Microsoft can't make up their dam mind when it comes to where certain features are located and how to get to them. For example in XP, I could right click my network connection icon in my taskbar to get my connection status dialog which I could retrieve IP info and such. No such luck doing this in Win7, you have to open My networks and go through a maze of links and clicks to get to it...

I also despise how the icons are presented. Setting the icon views to medium gives them some semblance on how they looked in XP, but there is no classic view in that since. Sure Win7 does have a classic theme that makes it look more like XP, but it still has all the GUI issues that Win7 has. Mainly the bloated nature of it. There's just too many new crap added in. I liked the features I had with XP, I don't want a new amped up search bar or a redesign in the address bar or other important GUI feature I use a lot. Microsoft needs to relearn how to create new OS without adding so much new crap that the previous GUI/system of doing things is completely unrecognizable in the new OS. Case in point, the transition to Win9x to XP wasn't that hard. The only main differences was the NT system and change in how DOS programs run. I didn't have too much trouble figuring out the new stuff in XP, because a lot of it still resembled what Windows 98 had.

So why the f*** fix something that isn't broke? The only other program I have that doesn't work with my current OS is Battlefield Bad Company 2 and I don't really like that game too much. If Battlefield 3 comes out and turns out to not work with XP 64bit version, I MIGHT upgrade to Windows 7, but only via the upgrade to Vista, then to Windows 7 path. But right now I can't justify risking that as two OS upgrades in a row doesn't sound like it would go down well. Dude it took me a good 4+ years after XP was first released to actually upgrade to it.

Back in the old days of Windows 98, I had a lot of stuff that didn't work in XP. But after awhile I eventually got enough programs+interest to finally upgrade. Perhaps one day I will see my self upgrading to Windows 7, 8, 9, Ultra 10 Premium, or whatever the f*** Microsoft decides to call their next OS. I go by my own clock in terms of the lifespan of my OS, not the screwed up idea of OS lifespan that Microsoft wants to impose on us.

So please, don't turn this into a "upgrade your OS/machine or else" thread. I have to work with what I got and when a new program/game comes out that really peaks my interest that only works in Win7, then perhaps maybe then I may upgrade to it. I also refute your claim that only 100 users have WinXP 64-bit....come on really? I won't even dignify that with a response. XP maybe an really old OS, but it still has plenty of relevance today with the many things available out there and still works really well with new hardware, so as long as it continues to work great on the new computers being put out there, I will continue using it. Plain and simple.

Back on topic, how complicated is the coding that they added for this threading function? Is there any one working on a SVN build that removes this and possibly adds XP 64 support? I guess I can stick with 2.0 for now. If 3.0 doesn't really provide a big boost/stability boost over 2.0, then I guess I will have to be stuck with an outdated emulator. God help me if a future version adds WFC support. Perhaps then I might have enough interest in this program to justify an OS switch.

[HawaiianPunch]

I believe you can get XP64 support if you compile yourself with certain settings.

[Apache Thunder]

That's one possibility. I would have to research what code language it uses, hope the program used to compile it doesn't cost money to use, and also hope that the process isn't too complicated to learn.

The last time I did anything code related was an old Turbo Pascal open source Mario side scrolling game that ran in DOS. I managed to add new levels and sprites to the game and I didn't even learn 2% of all the what the coding language can do.

[HawaiianPunch]

Dolphin is written in C++ and compilation instructions can be found at http://code.google.com/p/dolphin-emu/wiki/Windows_Build . As for modifying the code for XP64, ask Neo, Daco or NaturalViolence.

[Dimitri]

(07-21-2011, 12:41 PM)HawaiianPunch Wrote: As for modifying the code for XP64, ask Neo, Daco or NaturalViolence.

The USE_SRWLOCKS and USE_CONDITION_VARIABLES defines (those that affect XP x64 support) are defined through #if conditional tests in two different files.

To manually force these defines not to be defined, falsify the tests with "&& 0" as done by the attached patch. Apply this patch once you've set up a local repository for Dolphin using TortoiseSVN (as described by the above wiki page). Hopefully this works.

EDIT: Dunno if this patch still is valid with GIT (instead of SVN), but I'll post the contents of this patch (which I think references Common) for those who have trouble downloading attachments (to get around that I'd advise refreshing the page with F5 or Ctrl+F5 and/or using Firefox...) :

Code:

Index: StdMutex.h
===================================================================
--- StdMutex.h    (revision 7683)
+++ StdMutex.h    (working copy)
@@ -29,7 +29,7 @@
#define USE_RVALUE_REFERENCES
#endif

-#if defined(_WIN32) && defined(_M_X64)
+#if defined(_WIN32) && defined(_M_X64) && 0
#define USE_SRWLOCKS
#endif

Index: StdConditionVariable.h
===================================================================
--- StdConditionVariable.h    (revision 7683)
+++ StdConditionVariable.h    (working copy)
@@ -18,7 +18,7 @@
#define USE_RVALUE_REFERENCES
#endif

-#if defined(_WIN32) && defined(_M_X64)
+#if defined(_WIN32) && defined(_M_X64) && 0
#define USE_CONDITION_VARIABLES
#elif defined(_WIN32)
#define USE_EVENTS