strunge said:
greenmedic88 said:
Wagram said:
ShadowSnake said:
if the ps3 (160 phatty) hasn't been plugged in at all for the past couple of days, will there be a problem if i were to wait for all this to blow over? |
Honestly I don't think being online at all affects this. I believe that even if your console is off atm you still may be prone to this issue.
|
Actually, I think it was stated that if you were already logged on before the clock rolled over to 2/29, you'd be fine.
It's only if you turned your system on after the clock rolled that you'd be experiencing all the related date error problems. I can vouch for this personally.
I'm not turning my other system on until the fix is announced.
|
being logged on before it occured isn't the sme thing as the system itself being off, and thus not logged on, so I'm not sure how you are disp[uting his position. if the requirement for this to occur is that you are not logged on when it happened, than a system that is off, and thus not logged on, would also be affected, regardless of whether you turn it on or not because it meets the criteria -- not logged on when the calendar rolled back, and the calendar rolled back even if the system is off.
|
It has nothing to do with PSN or being logged on at all. The problem is related to the internal clock attempting to calculate the date as a non-existent 2/29/2010.
If someone had their console turned on when the clock turned, they're probably fine. If it was off, probably not.
Although if you were logged on, it generally (always) means your console was powered on.
