In Tiger I used to use the rc.local/shutdown.local scripts to adjust the dates between mac os and windows os.

See link for instructions: http://forum.insanelymac.com/index.php?sho...=shutdown.local

Now, it seems that apple has disabled the rc scripts for Leopard. This was the best working method and don't have a working solution anymore.

I think apple said they replaced the rc scripts with launchd. I used Lingon to create a startup script to do the rc.local part of the script; however, I can't seem to find a way to use launchd to issue the shutdown command.

Anyone a launchd expert or have a better way to deal with the date/time differences between windows and mac?

I've already tried several things in windows (registry change, startup script, etc..) but they aren't perfect.


Thanks

swag01

Okay, new thing with Leopard. If you don't specify a password when creating your account, you can't use sudo.

I was having problems creating directories and all in the environment and found this little problem.

Sucks, because I never have put a password on the system before. Maybe it is for better security.

Okay;

I created a script to deal with the local time problem between osx and windows.

You should be able to use this script in either Tiger or Leopard.

I took the original idea about adjusting the date, but put it in a startup item.

One Issue (but minor): If you don't shut Tiger/Leopard cleanly, you'll need to manually change the clock to the correct time (for that time).


Steps to Install:

-- copy FixLocalTime to /Library/StartupItems:
Ex: sudo cp -rf ~/Desktop/FixLocalTime /Library/StartupItems

-- make sure root is the owner of the directory and files:
Ex: sudo chown /Library/StartupItems/FixLocalTime

Reboot... And it should be working. If the date isn't correct, adjust it in either windows or osx.


To confirm that it is working, look in the system log and search for FixLocalTime.

Also, if your clock was off when you copied the files, osx will think the files were added after boot time and won't run the script. (look in the log for the error).

If this occurs, then issue the "touch" command on the files where the date isn't correct.

Thanks worked perfectly!