Oldest Mk2, Newest Mk1


Goity said:
Isn't gonna help, but MK1 2006.02.01 - GP2xV127 - 00001651
Now this doesn't make sense to me - mine is 10 days later

Model GP2X - F100

S/N 2006.02.11 - GP2XV001 - 00000018
 
Last edited by a moderator:
reeced said:
Goity said:
Isn't gonna help, but MK1 2006.02.01 - GP2xV127 - 00001651
Now this doesn't make sense to me - mine is 10 days later

Model GP2X - F100

S/N 2006.02.11 - GP2XV001 - 00000018

Well, don't try to make sense out of the "GP2XV001" part, whose meaning is one of the the Great Mysteries. And the final number appears likely to be the sequence number within a particular production run or something like that.
 
Last edited by a moderator:
Dzz said:
Thanks everybody for making the effort to type in your data. All we really need at this point is info about serial numbers in this range:

2006.03.09 - 2006.05.22
2006.05.19 - GP2XV127 - 00004899
Mk2

I didn't preorder, so I'd expect there must be Mk2's at least a little older than this.
 
Last edited by a moderator:
rabidcow said:
2006.05.19 - GP2XV127 - 00004899
Mk2

I didn't preorder, so I'd expect there must be Mk2's at least a little older than this.
Thanks! Okay, the mystery range is now:

2006.03.09 - 2006.05.19
 
Last edited by a moderator:
While I understand the convenience of an automatic detection, is it really that unreasonable to have the user specify what kind of unit they have?

If some sort of agreement could be reached, GP2X developers could implement it so that once the information is entered the first time, it's stored in /etc/mark or what-have-you, accessible for future use. Sounds like an excellent project for the GP2X standards guy(s). In any event, it would be a viable solution until this detection thingy is done. I'd even argue it's the most elegant solution if date is all we have to go on.
 
Back
Top