 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / General / General / May 2008time difference
My university gave me a mac book pro that is boot camp dual boot with vista and leopard. I am loving it so far, i just have a few problems that i cant seem to work out. for my personal needs i use vista more than leopard but to avoid an argument i see both operating systems to be very solid and usefull. having said that my problems are in windows but i didnt know which forum to post in since it is an apple system but a microsoft os. I have boot camp set to automatically boot to the windows partition, which bypasses boot picker. if i ever need to go to leopard i just hold down the option key when i boot and then i can select leopard. in windows my clock goes crazy. i haved tried various setups to make it stay on the right time but it always seems to find a way to go 5 hours fast. the it guys at my university sent me a registry edit that they said would fix the problem but i think it isnt working. here are the changes that it made: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control \TimeZoneInformation] "Bias"=dword:00000168 "StandardName"="@tzres.dll,-162" "StandardBias"=dword:00000000 "StandardStart"=hex:00,00,0b,00,01,00,02,00,00,00,00,00,00,00,00,00 "DaylightName"="@tzres.dll,-161" "DaylightBias"=dword:ffffffc4 "DaylightStart"=hex:00,00,03,00,02,00,02,00,00,00,00,00,00,00,00,00 "TimeZoneKeyName"="Central Standard Time" "DynamicDaylightTimeDisabled"=dword:00000000 "ActiveTimeBias"=dword:0000012c "RealTimeIsUniversal"=dword:00000001 should this make my clock work? btw: my timezone is central standard time In article <ef62f7e7-7012-426c-9cb9-e6669d6cc07f@d1g2000hsg.googlegroups.com>, > My university gave me a mac book pro that is boot camp dual boot with > vista and leopard. I am loving it so far, i just have a few problems [quoted text clipped - 3 lines] > but i didnt know which forum to post in since it is an apple system > but a microsoft os. Windows doesn't even know it's running on a Mac. And why should it? Macs have Intel motherboards, processors, and other standard PC components. What you are experincing a Windows Vista software glitch. The comp.sys.mac.* news groups are for Mac hardware and Mac software issues. > I have boot camp set to automatically boot to the > windows partition, which bypasses boot picker. if i ever need to go to [quoted text clipped - 20 lines] > should this make my clock work? btw: my timezone is central standard > time Ask in a Windows news group.  SignaturePlease send all responses to the relevant news group. E-mail sent to this address may be devoured by my very hungry SPAM filter. I do not read posts from Google Groups. Use a real news reader if you want me to see your posts. JR > In article > <ef62f7e7-7012-426c-9cb9-e6669d6cc07f@d1g2000hsg.googlegroups.com>, [quoted text clipped - 12 lines] > The comp.sys.mac.* news groups are for Mac hardware and Mac software > issues. Not so fast - the issue is in the use of the "standard PC" components. Apple's apparently using UTC time in the hardware clock, and MS apparently is not. Other OSes on Intel boxes work use UTC time too, so solutions that work for them may apply here too. Perhaps a better approach in general would be to run Windows inside a VM (Parallels, VMware, VirtualBox) in Leopard. Cheers, Chris > > In article > > <ef62f7e7-7012-426c-9cb9-e6669d6cc07f@d1g2000hsg.googlegroups.com>, [quoted text clipped - 19 lines] > Other OSes on Intel boxes work use UTC time too, so solutions that work > for them may apply here too. Right. The fact that the Mac uses UTC time is inconsequential. It's not a Mac-specific issue as much as it is a Windows XP/Vista hardware clock issue: <http://preview.tinyurl.com/2yedaf> SignaturePlease send all responses to the relevant news group. E-mail sent to this address may be devoured by my very hungry SPAM filter. I do not read posts from Google Groups. Use a real news reader if you want me to see your posts. JR > In article <68vculF2q480...@mid.individual.net>, > [quoted text clipped - 36 lines] > > JR Sorry, Jolly Roger, but the OP is right on this one... even if it is a Windows issue, it is caused by the Apple hardware (I have the same problem myself). A Windows group would be of much less help, most likely... I recall that Apple officially acknowledged this issue a while back, but I can't find the page. Google "boot camp time difference" and there are some quick-and-dirty fixes there. > Sorry, Jolly Roger, but the OP is right on this one... even if it is a > Windows issue, it is caused by the Apple hardware (I have the same > problem myself). A Windows group would be of much less help, most Honestly, no it isn't an Apple hardware problem. The link JR gave had a link to this more technical page: <http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html> Basically all standard OSes have a convention of storing a UTC value in the hardware clock. Windows follows a different convention, which is wrong for the reasons stated in the above page. But ultimately all the OSes are just following *conventions* on what to store in the hardware. The hardware does what it is told :-) Since Windows can't be persuaded to work correctly, either move to somewhere where localtime is UTC (perhaps infeasible) or run Windows inside of something that can lie to it about the clock, like VMware. Cheers, Chris > > Sorry, Jolly Roger, but the OP is right on this one... even if it is a > > Windows issue, it is caused by the Apple hardware (I have the same [quoted text clipped - 17 lines] > > Chris sorry i havent responded sooner. i had already tried the registry edit that was linked by JR, but i think that it might be my problem since i am completely bypassing os x for the majority of my boots. i am going to remove that entry and see if it has any effect. if not then what if i set my time to be purposely wrong in os x? thanks to those of you that have been polite and helpful so far, guitardude > sorry i havent responded sooner. i had already tried the registry > edit that was linked by JR, but i think that it might be my problem > since i am completely bypassing os x for the majority of my boots. i AFAIK, booting is handled by the firmware (think "BIOS", though it is called EFI) and not OS X. > am going to remove that entry and see if it has any effect. if not > then what if i set my time to be purposely wrong in os x? thanks to > those of you that have been polite and helpful so far, > guitardude Anyway, there are strong suggestions that Windows simply cannot cope reliably with UTC hardware clocks, so the registry hack can't be trusted. Other OSes that run on x86, like Solaris and Linux, can be told that the hardware clock doesn't use UTC. Perhaps there's a way to make OS X do the same, though I somewhat doubt it. I still think VMware's the best way to solve the problem. Cheers, Chris > > sorry i havent responded sooner. i had already tried the registry > > edit that was linked by JR, but i think that it might be my problem [quoted text clipped - 17 lines] > > I still think VMware's the best way to solve the problem. Or get over your Windows addiction and learn to use Mac OS X - you'll live happier as a bonus. ; ) SignatureNote: Please send all responses to the relevant news group. If you must contact me through e-mail, let me know when you send email to this address so that your email doesn't get eaten by my SPAM filter. JR |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.