I take software engineering this term, and for some suspicious reason the instructor wants us to develop for the iPhone. Now, as if that wasn't bad enough, we must develop for it in Objective C, which can only be compiled on a mac system.
Quite redundant, considering a java application would work just as well and can be developed over any platform, meaning i don't have to buy or steal a mac to do so.
Nevertheless, our instructor, in his infinite wisdom argues that in real life one does not always have the luxury of choosing one's target application language, and often must learn new languages for new platforms.
True enough, however, one also has time, energy, and resources to handle the task, not to mention one gets paid for it.
Long story short, it has to be an iPhone app, and it has to be in Objective C.
So after 4 gruesome days, i've managed to get OSX running with some limited functionality on my PC. Problem is OSX changes the BIOS clock to match my selected regional timezone, while Windows reads it once and then compensates accordingly. Switching back and forth results in my time being advanced artificially over and over again. Evidently there is a fix for it, by setting my BIOS time to UTC time, (universal time something that starts with c) and adding a registry 32 bit DWORD :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal and setting it to 1.
This however causes linux (I have 4 operating systems now) to push my time forward, which means i have to find another solution. Annoying.
Subscribe to:
Post Comments (Atom)
linux will be very happy that your system clock is on UTC; you just have to let it know. I've never had to deal with *not* having a UTC clock, so I can't remember how to set that, but it's probably best to ask your distro.
ReplyDeletethat's a good point. linux probably has a setting somewhere for UTC time.
ReplyDeleteI'll look for it next time i log into Ubuntu.
This comment has been removed by the author.
ReplyDeleteok, in ubuntu dealing with UTC is easy, and the current default is for localtime or UTC=no in the RC file.
ReplyDeletewindows uses localtime by default
so the only problem now is osx, which as i just noticed increments my bios clock by 8 hours after every boot no matter what i do. not sure what's causing it but i a simple fix would be a script that decrements the system clock by 8 hours on shutdown. i still don't understand what kind of a standard has an OS CHANGING my bios clock. that's like none of their business. what happens in bios should stay in bios.