Jump to content
5 posts in this topic

Recommended Posts

In some cases, discrepancies between OS X's interpretation of a computer's BIOS-set internal clock can lead to modifications of the interpreted time in Windows XP. This is because OS X seems to interpret the time initially configured as GMT only, so if you live in another time zone, OS X changes the clock.

When you boot back into Windows, the clock will display a different time than what it actually is.

 

This leads to issues with the infernal DRMs that seem to be plaguing the media consumer forum. Janus DRM, AKA DRM WMP10, or the DRM compatible with "PlaysForSure" content is dependent on a clock that counts down to 30 days, in most cases. When that time elapses, content must have its license renewed, or they will not play.

 

However, when Windows reads that the clock has changed in a strange manner since the previous boot, it seems that the DRM becomes invalid. Any music that has a DRM security 'feature' may lose it's access privileges.

 

This has been happening to me recently. Since it can be irritating to renew licenses, due to faulty coding on the part of whatever company you receive the DRMed content from, or the like, be careful that you watch your clock changes. As such, I've left my clock in OS X on GMT, so that it doesn't conflict with Windows, or my DRM.

 

If anyone has any other insights on this issue, let me know.

What's the point of having different time zones anyway?

 

Believe me, poor users get awfully confused when their server tells them files have been created with GMT0 timestamps when they live in Arizona. Or more seriously, creating Cron jobs or other OS time/date critical functions becomes a nightmare if you have to factor in time differences. Best to have a TZ which reflects the real world. Of course, when you work for a company which has servers in every time zone, the problem bites you the other way.

 

DRM sucks anyway. If the b*st**d companies didn't tie up your legitimate rights in code which is useless to you, we wouldn't have this problem.

 

(OK, I know they have a duty to protect their income and foil pirates etc., I just hate the fact that even when you pay for something and play the game you get screwed. That's just not fair.)

When you boot back into Windows, the clock will display a different time than what it actually is.

 

Simplest solution (and what I do) is to use network time protocol to sync your clock everytime windows boots. This is free software downloadable from here.

http://ntp.isc.org/bin/view/Main/SoftwareDownloads

 

It sets your computer clock to navy time in the time zone you specify. Even without OS X its helpful as computer clocks aren't all that accurate.

×
×
  • Create New...