Gaming Upgrading from 5.00 M33-3

  • Thread starter Thread starter jy2
  • Start date Start date
  • Views Views 6,652
  • Replies Replies 36
Saken said:
Hey, i just tried playing on my 2GB stick, and it hanged just like the 16gb stick. I'm beginning to think it's the ROM or the firmware, will try now on a pc emu to see if it's the ROM.
I don't really wanna downgrade from Prom-2, cause i wanna play BBS and other new release games
What can be done?

Waiting for that apology....
closedeyes.gif


Edit....oh and chuck one in for saken too.
 
xist said:
Saken said:
Hey, i just tried playing on my 2GB stick, and it hanged just like the 16gb stick. I'm beginning to think it's the ROM or the firmware, will try now on a pc emu to see if it's the ROM.
I don't really wanna downgrade from Prom-2, cause i wanna play BBS and other new release games
What can be done?

Waiting for that apology....
closedeyes.gif


Edit....oh and chuck one in for saken too.

Source? and you'd be so lucky! I haven't got anything to apologize for! You seem rather power mad or a troll...
 
WOW. This is just a Trolling War. Go fight somewhere else. If people think GEN is shit. Then let them think GEN is shit. Doesn't matter. As long as people can play ISOs.

Anyway, I have a question that is actually related to the Topic.

I have M33-6 and was wondering if I should stay where I am at and wait for patches or get prometheus for M33-6?

Thx
 
Grab prometheus for M33 if you like. I still tend to see newer titles patched to work on whatever. As for Rydian's questions, the only one I can answer effectively is the first one. The MS speedup on M33 allows games to run at full speed from the mem stick. .Iso formats tend to work fine on Gen, but if compressed to .Cso format they stall out and lag. This is not the case on M33 as the mem speedup allows for these file types to run at full speed. That said, most modern homebrew runs fine on Gen. The Mem card speedup however has been enough to keep me on M33.
 
GreatCrippler said:
Grab prometheus for M33 if you like. I still tend to see newer titles patched to work on whatever. As for Rydian's questions, the only one I can answer effectively is the first one. The MS speedup on M33 allows games to run at full speed from the mem stick. .Iso formats tend to work fine on Gen, but if compressed to .Cso format they stall out and lag. This is not the case on M33 as the mem speedup allows for these file types to run at full speed. That said, most modern homebrew runs fine on Gen. The Mem card speedup however has been enough to keep me on M33.

Does Prometheus for M33 allow you to run games that require 5.50 or 5.55 without manual patching, such as Persona 1 (either a clean dump or even from UMD)? If the Prometheus plugin does that (as opposed to the 620 plugin which doesn't) I might switch back to M33.
 
sprogurt said:
xist said:
saken tried on two different Memory Sticks and with different ROM's and still ran into this problem.

QUOTE(Saken @ Sep 18 2010, 04:35 PM) It seems to work fine on my other mem stick..
It works well on my 2GB Sony, but on my 16GB sandisk it doesn't.

'-_- This tells us that it is infact a memory stick problem and not a firmware problem, and the fact that even when you acknowledged that it was working and still claim it hang just so you can argue is beyond me. Why? What do you get out of it?

Here's some photos to prove that it works fine on my genuine 2GB sandisk pro duo:

pic3.jpg

pic1.jpg

pic2.jpg

pic4.jpg

pic5.jpg

Here's some more proof that it works fine

Yeh uh sprogurt, I said it worked fine because i got past ONE stage without it hanging.
However, I played on and the same stuff happened that was mentioned on the 16GB mem stick. I PMed this to xist, seeing as he seemed to know what he was talking about and seemed willing to help. That's the source..

Why don't you then, install prometheus-2 and tell me whether the emulator works?
If you get past naming yourself without hanging, try and catch your first pokemon without it hanging. If you can do all that you will be the winner.
 
nl255 said:
Does Prometheus for M33 allow you to run games that require 5.50 or 5.55 without manual patching, such as Persona 1 (either a clean dump or even from UMD)? If the Prometheus plugin does that (as opposed to the 620 plugin which doesn't) I might switch back to M33.

Using ISO Tool all patching entails is a few button presses...if you don't want to go "fully manual" then there's no need. However, there's never any reason not to be at the end of a CFW chain. Why 5.00M33-3 over 5.00M33-6 when you lose out on the additional incorporated features?
 
Saken said:
Why don't you then, install prometheus-2 and tell me whether the emulator works?
If you get past naming yourself without hanging, try and catch your first pokemon without it hanging.

The previous photos are with prometheus-2 installed, as are
pic6.png

pic7.png

pic8.png
 
Last edited by sprogurt,
sprogurt said:
Saken said:
Why don't you then, install prometheus-2 and tell me whether the emulator works?
If you get past naming yourself without hanging, try and catch your first pokemon without it hanging.

The previous photos are with prometheus-2 installed, as are these.
pic6.png

pic7.png

pic8.png

5.50 Prometheus-2 you say?
Then what's this:
durpb.jpg

Also, I meant to actually rename the pokemon.. You didn't.. It was after nicknaming the pokemon that it hanged, and your not even on Prom-2.
If you were it would say 5.50 Prom-2 for your firmware, not 5.00 M33-6
 
Saken said:
5.50 Prometheus-2 you say?

Nope, I didn't say that. I said Prometheus-2. This is 5.00 M33-6 prometheus-2. I tried it on GEN first then took pictures after I downgraded it.

Saken said:
Also, I meant to actually rename the pokemon.. You didn't.. It was after nicknaming the pokemon that it hanged

Well you actually wrote:
Saken said:
try and catch your first pokemon without it hanging.

They're two different things...You didn't ask me to rename them, so I didn't. It's like asking for the salt and then complaining because someone didn't get you pepper aswell. Also I'm pretty sure if many people had problems with naming they would just avoid it, try that...

QUOTE(Saken @ Sep 22 2010, 10:00 AM)
and your not even on Prom-2. If you were it would say 5.50 Prom-2 for your firmware, not 5.00 M33-6

Actually 5.00 M33-6 prometheus-2 doesn't rename the firmware name...Hence it's 5.00 M33-6, not 5.50 Prom-2.
 
But that's not Prometheus-2 Firmware. That's a modified M33 frankensteined with modules from Prometheus. Essentially you're just saying it runs on M33.
 
xist said:
But that's not Prometheus-2 Firmware. That's a modified M33 frankensteined with modules from Prometheus.

I used 5.00 M33-6 prometheus-2 because it's more widely known within the scene as "5.00 M33-6 prometheus-2" instead of "a modified M33 frankensteined with modules from Prometheus".
 
sprogurt said:
xist said:
But that's not Prometheus-2 Firmware. That's a modified M33 frankensteined with modules from Prometheus.

I used 5.00 M33-6 prometheus-2 because it's more widely known within the scene as "5.00 M33-6 prometheus-2" instead of "a modified M33 frankensteined with modules from Prometheus".

Well the glitches are with 5.50 Prome-2, that's what i experienced.
Technically speaking, you are on Prometheus-2, but you aren't on 5.50 which is the version i experienced the incompatibilities. Therefore your "evidence" doesn't apply.
 
Saken said:
Well the glitches are with 5.50 Prome-2, that's what i experienced.
Technically speaking, you are on Prometheus-2, but you aren't on 5.50 which is the version i experienced the incompatibilities.

QUOTE(sprogurt @ Sep 22 2010, 06:16 PM) I tried it on GEN first then took pictures after I downgraded it.
 

Site & Scene News

Popular threads in this forum