BASLQC / procfw

Automatically exported from code.google.com/p/procfw
1 stars 0 forks source link

Cannot launch Snes9xTYL/me on Pro-B10fix1/Cfix3 under 6.20/6.35 #511

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install Pro-B10fix1 or Cfix3 on either 6.20 or 6.35
2. Install Snes9xTYL or Snes9xTYLme
3. Launch Snes9xTYL and wait for it to fail to launch.

What is the expected output? What do you see instead?
It should run.

What version of the product are you using? On what operating system?
Tested Pro-B10fix1 and Pro-Cfix3 on a PSP-3000 at 6.35 and a PSP-1000 at 6.20

Please provide any additional information below.
On my PSP-2000 6.20 running Pro-B10fix1, it works!

There must be something rather simple I'm missing or some kind of VSH setting 
that breaks Snes9xTYL or something like that.

Original issue reported on code.google.com by IcySo...@gmail.com on 17 Oct 2012 at 11:11

GoogleCodeExporter commented 9 years ago
P.S. Resulting error code is 8002013C

Thank you.

Original comment by IcySo...@gmail.com on 17 Oct 2012 at 11:11

GoogleCodeExporter commented 9 years ago
Update: I have upgraded Snes9xTYL to "Snes9xTYLmecm 091127 fixed2" version 
available on the net and have tested it on the PSP-1000 running Pro-Cfix3 and 
it works!

I didn't yet have the opportunity to test it on the PSP-3000 but will report 
back when I do.

Original comment by maim...@gmail.com on 20 Oct 2012 at 1:21

GoogleCodeExporter commented 9 years ago
Update 2: I've tested this apparently new(er) version of Snex9x on the 3000 and 
it is working! However, if I'm not mistaken, I've used this new version 
previously on my own 3000 with Pro-B10 and it didn't work. If there was an 
issue before, Pro-C3 has corrected it! I will report back with my findings on 
this later on as well.

Original comment by IcySo...@gmail.com on 20 Oct 2012 at 12:35

GoogleCodeExporter commented 9 years ago
Update 3: Tested Snes9xTYLmecm fixed 2 on my PSP-3000 with Pro-B10 and it is 
working just fine. This issue can now be closed/archived.

Original comment by IcySo...@gmail.com on 23 Oct 2012 at 4:54