By using this site, you agree to our Privacy Policy and our Terms of Use. Close

Forums - Sony - DO NOT TURN ON YOUR FAT PS3 - date bug is majorly screwing up systems

That's an hour of gaming I'll never get back. :P

... oh well.



Hmm, pie.

Around the Network

the was many news on n4g with Statements "Sony gains RROD sized issue as PS3 stops “doing everything”"and after that xbox fanboys say's that press is not biased to ps3.Lolololo



And here i thought it was Sony's "kill switch"

But i kinda feel left out coze my phat PS3 didn't have any problems :(



Vote to Localize — SEGA and Konami Polls

Vote Today To Help Get A Konami & SEGA Game Localized.This Will Only Work If Lots Of People Vote.

Click on the Image to Head to the Voting Page (A vote for Yakuza is a vote to save gaming)

So are there no implications of the affected PS3's thinking that it's the 1st of March when it's the 2nd (i.e. always a day behind the real date)? Which is what was presumably going to happen and appears to be what has happened.



kowenicki said:
Skeeuk said:
lol at certain fanboys who wanted this to fail, how miserable they are, i feel sorry for them.


I think you are out of order there... totally uncalled for.

The 360 community in here did not jump on this at all... and fair play to them for that.

Unlike the news story on the front page about this being sorted.. which is full of RROD references from sony fans... again totally uncalled for.

 

To be fair there are like... 10 times as many sony fans on this site... so it's 10 times the fanboys.

It takes way less effort on the sony fanboys part.

The site is so bereft of 360 fanboys that I somehow got called a 360 fanboy once or twice.



Around the Network
drpunk said:

So are there no implications of the affected PS3's thinking that it's the 1st of March when it's the 2nd (i.e. always a day behind the real date)? Which is what was presumably going to happen and appears to be what has happened.

My PS3 this morning after a day of not being on thought it was the 1st of March, or at least it said 01/03 (UK format) on the date bit at the top.

 

Kasz216 said:

To be fair there are like... 10 times as many sony fans on this site... so it's 10 times the fanboys.

It takes way less effort on the sony fanboys part.

The site is so bereft of 360 fanboys that I somehow got called a 360 fanboy once or twice.

Only a 360 fanboy would say that.

 



Hmm, pie.

This clock error wins hands down as the biggest stink over nothing.

About the only thing lost by anyone yesterday was about a half day of gaming on PSN.

But it's still pretty disturbing to think something as elementary as a clock error can literally lock out many games (and ALL DL content) from functioning at all.



The Fury said:
drpunk said:

So are there no implications of the affected PS3's thinking that it's the 1st of March when it's the 2nd (i.e. always a day behind the real date)? Which is what was presumably going to happen and appears to be what has happened.

My PS3 this morning after a day of not being on thought it was the 1st of March, or at least it said 01/03 (UK format) on the date bit at the top.

Yeah, seemed the obvious thing that was gonna happen, that if it thought yesterday was 29th of Feb then it would think that today is 1st March.

So it's obviously not "fixed" and I'm just wondering what possible implications there are of it always being a day behind. Hopefully there are none.



not let turn into a mud slinging contest in either direction)))
Sony Stock Up In The Midst Of Global Crisis
http://www.n4g.com/NewsCom-484204.aspx?CT=1&Page=1&Page2=1#C3391847



drpunk said:
The Fury said:
drpunk said:

So are there no implications of the affected PS3's thinking that it's the 1st of March when it's the 2nd (i.e. always a day behind the real date)? Which is what was presumably going to happen and appears to be what has happened.

My PS3 this morning after a day of not being on thought it was the 1st of March, or at least it said 01/03 (UK format) on the date bit at the top.

Yeah, seemed the obvious thing that was gonna happen, that if it thought yesterday was 29th of Feb then it would think that today is 1st March.

So it's obviously not "fixed" and I'm just wondering what possible implications there are of it always being a day behind. Hopefully there are none.

Or I can just set the date 1 day forward, the issue was the system's confusion and the 2 days not matching and one not existing, now the days exist so the system just thinks it's yesterday instead of today. I presume me setting the date to today won't do anything but change the date that displays on main screen and as the 29th has now passed as far as the internal clock is concerned, it cannot be go back to it and so no error will be found (I cannot set the calendar date as 29th as it doesn't exist).

Surely there would be the same issue if I manually set the date to 13th April 2013, the dates differ but the internal clock will always be behind. It doesn't harm the console at all, it's just a date.

 

.... this is confusing.



Hmm, pie.