Should We Get Mad At Gamepark?

Should We...

  • Beg Gamepark (mass e-mailing) to switch back to Samsung

    Votes: 0 0.0%
  • Do the above, and boycott new BLU's

    Votes: 0 0.0%
  • Fix all our software

    Votes: 0 0.0%
  • Make a "faulty" fix mod (LCD replace)

    Votes: 0 0.0%
  • Do something else. Post your ideas.

    Votes: 0 0.0%

  • Total voters
    0

Blah

Wanna Be Programmer
Joined
Dec 18, 2003
Messages
3,253
Age
34
Location
Oregon, USA
Website
Visit site
We all know about the new ones with the "faulty" Taiwanese LCD's.
It doesn't really effect me because mine was from just before that shipment.
But as a GP32 user, I'm concerned.
 
What would be the point in getting mad at them. I'm sure the distrubuters are sending word back to them that they have faulty product coming out of their factory and they will evnetually fix it other wise they;re wasting money.
 
i have a gp32
but i'm still pretty pissed about this

and i wouldn't count on an lcd replacement
that sounds expensive and dangerous
i haven't voted
because i can't decided
i'm stuck between mass emailing and boycotting the new flus
 
If Gamepark fixes the problem, they should also fix the ones people send in (via their dealer, of course).
 
it's a shity situation. they can't really even say 'oh, but it works on all the commercial games' because they know the commercial games are shit.


hopefully a new BIOS that fixes it will come out.



this is a disaster for gamepark, and the new BLU buyers...
 
1. The fault lies with Samsung.
2. Gamepark do not officially support homebrew software so they can get away with taking no action.
3. They switched LCD suppliers for a reason - probably cost. So they are unlikely to switch back.
4. Petitioning them will not help the dozens/hundreds of users with 'faulty' units out there now.

Best bet is to find some way of fixing it on our end. Hopefully it's possible without having access to the source code (changing one argument of a function...) much like the clock speeds can be hacked wthout source. Or better yet, a firmware mod.
 
And nobody said that Samsung doesn't make them anymore.
And according to Gamepark, the price is not what they cared about.

Edit: The sticky said that it was because the largest manufacturer of LCD screen glass folded and Samsung is trying to find glass. :blink: Why would the largest LCD screen glass manufacturer fold?
 
I dont think begging them to switch back to samsung is going to have any effect.


I think gamepark needs to work with devs or coders or just all gp owners to find a solution, preferably one that doesn't involve having to send your GP off anywhere.


It would be great if gamepark looked at, found and sovled the problem thru the firmware or bios and just provided a new file to everyone to download and fix it just like that. After everything I've read on the subject this seems to be very possible and the easiest solution.
 
Firmware wouldn't fix programs that init the lcd screen with their own code.
I.E Osnes9x and Frodo. And the Gp's already come with special official fireware
installed. The fix on the source code of programs looks easy enough, but some
programs that are unsupported by their coders and not open source can't be fixed
that way.
 
it'd be good if gamepark released info about exactly what the differences were...


and rico, gamepark know about the homebrew/emu community...(see the logo for the german GP32 launch)... they know that they'd be shooting themselves in the foot if they destroyed that market with the new batch...
 
IntenseWage posted on Dec 11 2004 at 05:19 AM said:
I'm still rocking the non-lit unit. Hahaha, booyah.

Oh yeah, well you'll be shit outta luck if the sun blows up. Didn't think of that now did you??
 
Last edited by a moderator:
If the effect on Homebrew would be felt even if it has nothing to do with emmulators then they have to do something about it. They only have like 10 consumer games, 98% of their usage comes from people making homebrew games.

Still getting mad dosent help, sending email will probably be ignored unless you speak korean, and there's probably a very good reason that they had to switch screens like a lack of stock for the first screen or that the new ones were cheaper. Which ever it'd probably be easier to code around it if it's a driver problem (this is assuming someone can understand why it happens to be able to do this)

I hope for the sake of the community this dosent continue for long.
 
Phew, this isn't good for the community. Not at all.

I don't know what could be done. Hopefully something like a firmware that patches the file or something so that it will display correctly on the new units. Apparently, Mr. Spiv has an idea, and if anyone can solve this problem, it's Spiv.

I don't know enough to say that I'm mad at GamePark... but I think there's a very good chance I would be mad if I did know the whole story.
 
Memnoch posted on Dec 11 2004 at 07:35 AM said:
Gamepark have always been a bunch of chimps. Nothing they do surprises me anymore.


agreed. unfortunately.
 
Last edited by a moderator:
shinneri posted on Dec 11 2004 at 05:30 AM said:
Phew, this isn't good for the community.  Not at all.

I don't know what could be done.  Hopefully something like a firmware that patches the file or something so that it will display correctly on the new units.  Apparently, Mr. Spiv has an idea, and if anyone can solve this problem, it's Spiv.

I don't know enough to say that I'm mad at GamePark...  but I think there's a very good chance I would be mad if I did know the whole story.

Yeah this sucks. How the hell are stores, websites etc going to explain to their customers that it is "normal" that half of the programs that they run will have the screen all corrupted? No one will buy the GP32 anymore and the ones that do will end up returning them so much that most places will stop selling them as it is not worth the hassle. It is only then when everyone drops them that Gamepark will say "oops, I guess changing suppliers to save 98 cents per screen wasn't such a good idea" but by then it will already be too late.

And all of the knuckleheads that suggest changing the code to work on the new units are forgetting one minor problem with that. Many of these programs and emus have been abandoned long ago. There is no source to be found and no way to change the stuff, so it is forever fucked on new units. Also if it means that you have to use the official SDK and not the ones that bang the metal what will that mean? The reason they bang the metal is to get speed out of the stuff. So will all emus that are developed with the new units and official SDK run dog slow now? What a mess.

It is quite ironic. The GP32 survived the launch of the Zodiac, braved the DS storm, but in the end it will die because its own company Gamepark had to shoot itself in the foot and self destruct by fucking around with something that they shouldn't have.

My hope is that the backlash is so severe for this that GP will have no choice but to go back to the working version soon. There may be a period of a month or so where they try to peddle these dodgy units, and when that don't work they will go back.
 
Last edited by a moderator:
TelcoLou posted on Dec 11 2004 at 04:26 AM said:
IntenseWage posted on Dec 11 2004 at 05:19 AM said:
I'm still rocking the non-lit unit. Hahaha, booyah.

Oh yeah, well you'll be shit outta luck if the sun blows up. Didn't think of that now did you??


and if the sun blows up we all die , infact we die before thesun blows up , so while the sun is getting bigger , we get a nice amount of warmth and light for our non lit units XD
 
Last edited by a moderator:
Back
Top