CamTron Posted September 1, 2015 Share Posted September 1, 2015 Does that SDL.DLL error happen right when you start Dolphin, or when you try to start the game? If it happens right when you start Dolphin, you might try opening it first and then attaching FineSSE to the process. It's possible that FineSSE might be interfering when it tries to load the DLL. As for PCSX2, you're getting the same exact exception, but FineSSE is catching it and shutting down the program rather than Windows. I've never used FineSSE at all, but I'd think there's a way to make it ignore that exception. There's no reason why the developers of both of those applications should be including code that throws those exceptions in a release version that's not meant to be debugged anyway. Link to comment Share on other sites More sharing options...
rloew Posted September 1, 2015 Share Posted September 1, 2015 I downloaded Dolphin 3.0 from the link in Post #1.To remove the 406D1388 RaiseException, Patch DOLPHIN.EXE:16B1E0 55 -> C3 3 Link to comment Share on other sites More sharing options...
junior600 Posted September 2, 2015 Author Share Posted September 2, 2015 (edited) I downloaded Dolphin 3.0 from the link in Post #1.To remove the 406D1388 RaiseException, Patch DOLPHIN.EXE:16B1E0 55 -> C3Thanks for your reply. How can I patch it? Do I need to use a hex editor? Edited September 2, 2015 by junior600 Link to comment Share on other sites More sharing options...
rloew Posted September 2, 2015 Share Posted September 2, 2015 Yes. Link to comment Share on other sites More sharing options...
junior600 Posted September 3, 2015 Author Share Posted September 3, 2015 Yes.Sorry to bother you, but have tried to do that with HxD .... I can't find that line... "Impossible to find 16B1E0 55" If I search "RaiseException"? Link to comment Share on other sites More sharing options...
loblo Posted September 3, 2015 Share Posted September 3, 2015 (edited) 16B1E0 55 -> C3 means go to address 16B1E0 and replace 55 by C3. Edited September 3, 2015 by loblo Link to comment Share on other sites More sharing options...
MiKl Posted September 3, 2015 Share Posted September 3, 2015 Yes.Sorry to bother you, but have tried to do that with HxD .... I can't find that line... "Impossible to find 16B1E0 55" You need to find 16B1E0 and change the value at this address from 55 to C3.Did a quick check with the xvi32 resource hacker and it was immediately found. Link to comment Share on other sites More sharing options...
halohalo Posted September 5, 2015 Share Posted September 5, 2015 (edited) Does this gamecube emulator (dolphin 3.00) work on windows 98+kernelex 2015? I have tried to run it, but it says me that it is missing a function in "imagehlp.dll" xD You can find the file exe therehttp://www.dolphin-emulator.com/download.html?rev=v30&arch=win32I hope someone can find a solution.Hardware acceleration needed for D3D 9.0c and OpenGL is not available on Windows 98 with KernelEx. So I think it is impossible to run Dolphin on 98. In fact, Dolphin doesn't work on Windows 2000 if you don't install KEP and other utilities made by BWC. Although gCube 0.3(gCube_nodebug.exe) emulator works on 98, it is too immature and outdated. Old PCSX2 0.94 should work on 98 with KernelEx. Maybe someday old Dolphin 2.0 will run on 98 with KernelEx, but expecting latest Dolphin and PCSX2 to run on 98 is impractical. Edited September 6, 2015 by halohalo Link to comment Share on other sites More sharing options...
junior600 Posted June 3, 2016 Author Share Posted June 3, 2016 On giovedì 3 settembre 2015 at 4:48 PM, MiKl said: You need to find 16B1E0 and change the value at this address from 55 to C3. Did a quick check with the xvi32 resource hacker and it was immediately found. I'm sorry to reply after a year xD I have replaced the value from 55 to C3... But now the emulator shows me another different error as soon as I launch a game... "Dolphin caused an Invalid Page Fault in Module <unknown> in 0000:0940018d. Registers: EAX=00000005 CS=0167 EIP=0940018d EFLGS=00010202 EBX=00000000 SS=016f ESP=0fb0ff04 EBP=bfa4a4ff ECX=68330080 DS=016f ESI=80003368 FS=500f EDX=0040048c ES=016f EDI=834b5ae4 GS=0000 Byte all'indirizzo CS:EIP: 89 8a 00 00 04 00 8b 15 44 67 35 04 8b 0d 44 67 Immagine dello stack: 834b5ae4 04d1e800 00000000 bfa4a4ff 0072105a 834b5ae4 04d1e800 0fb0ff4c 834a3040 7d010efd 00000020 0fb0ff7c 007a946a ffffffff 00523e7e 04d27108 I don't know what does it mean... Is there a guide which explains what I have to edit? For example how did Rleow understand that I had to Patch the value in DOLPHIN.exe in order to remove the 406D1388 RaiseException? How did he know which address it was? Another thing.... I'm trying to run pcsx2 too (version 0.9.4 or 0.9.5) The pcsx2.exe showed me this error "The Pcsx2.exe file is linked to missing export KERNEL32.DLL:MapUserPhysicalPages", so I have seen with importpatcher.41 how many functions are missing in kernel32. MapUserPhysicalPages AllocateUserPhysicalPages FreeUserPhysicalPages I added these functions in stubs.ini (Kstub822) and now the pcsx2.exe file shows me: "Cannot allocate mem addresses 15000000-5500000, err:8" I think I'm in the right track to load it. Sorry for my english, I know it is very poor. Link to comment Share on other sites More sharing options...
CamTron Posted June 7, 2016 Share Posted June 7, 2016 I'm pretty sure he used Ollydbg or a similar program to disassemble and debug the code, search for a specific function call, and from there you can change some opcodes and know what offset and bytes to patch. Link to comment Share on other sites More sharing options...
junior600 Posted June 8, 2016 Author Share Posted June 8, 2016 19 hours ago, CamTron said: I'm pretty sure he used Ollydbg or a similar program to disassemble and debug the code, search for a specific function call, and from there you can change some opcodes and know what offset and bytes to patch. Oh, I see... I have tried to use Ollydbg and I have found where dolphin.exe calls "raise exception". Now, what should I edit? (this is a old version of dolphin). This is a screen of ollydbg Spoiler Link to comment Share on other sites More sharing options...
rloew Posted June 8, 2016 Share Posted June 8, 2016 I used tools I wrote myself to find the location to patch. I have never used Ollydbg. First I used a binary search program to locate the Exception Code. Then I used a disassembler to identify the enclosing subroutine. Analysis showed that no return code was needed and the calling convention. Dropping a return instruction on the top of the subroutine was the appropriate thing to do. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now