How to Fix boot time difference between Windows and osx86 in a Dualboot setup

**RedZot** · 27-08-2011

The sequence of events that occur between the time you turn on your computer and the time it gets ready to accept commands called the process of starting. It is really tempting to have operating system like OSX in your own personal computer. Thanks to osx86 designed for non apple based system. To run OSX on your system you will need to patch the system first. You have to do that by a patched installation DVD. There are various projects you can found on internet about the mac operating system you can run on your hard drive. All you need to check the perfect system compatibility or else the operating system will crash. Check for the hardware compatibility list to run Mac on non-apple systems.

There are certain basic terms that you need to learn and understand to work with the boot process. This will not only help you to fix the boot time, but also help you to manage the other boot process.

Some Hardware support to fix boot time incase of other problems :
One of the most important components in a computer' is the RAM. It is an temporary memory that cannot any information when the computer is turned off. This is the

reason for which a system cannot rely on RAM to remember the basic features of how to communicate with other hardware. So for the boot process is designed. In general,

the boot process follows the following steps :

Turning on the system. Here when you press the button on the case, the power is on.
The microprocessor begins executing instructions stored in ROM
Self Test on or power-on self- test. In ths stage the computer performs a crucial diagnostic system and each component of the computer
Loading the OS. The operating system files are copied from the hard disk into RAM.
Check the system configuration. The microprocessor reads the data from the CMOS setup and run any routine specified for use.
Ready to accept data and commands.

Location to add plists scripts :

To fix the boot time preferences you will need to provide an appropriate location to load your plists file. Plists files are xml script which loads the preferences of services to load on the startup. One a Mac based system there are three directories that are available where you can usefully put your plists.

If these folders do not exist to you, you can create them yourself also :
/ Library / LaunchDaemons - In this folder you put your plist, if you want to create a user-independent daemon.
/ Library / LaunchAgents - In this folder you put your plist, if you want to create an agent that is active for all registered users.
~ / Library / LaunchAgents - In this folder you put your plist, if you want to create an agent that is active only for a specific user.

You can find a whole series of launchd.plists in the folder / System / Library / LaunchDaemons. Apple recommends that folder only for native use plists. But if you look at a few examples, you should definitely take a look into it since.

**RedZot** · 27-08-2011

Loading and testing your plist files :

To properly execute the plists file on your system you must first check that they are properly registered by launchd. Or else they will not be loaded. You could log out and back or to make a new start. The best thing to make this work by using the launchctl command. For example you have an script 2.plist file located in ~ / Library / LaunchAgents. And you want to load the file then you have to enter the following command into Terminal:

Code:

launchctl load ~ / Library / LaunchAgents / script 2.plist

And if you plan to turn this feature off then the command is below :

Code:

launchctl unload ~ / Library / LaunchAgents / script 2.plist

And the key to "Disabled" to remove:

Code:

launchctl load-w ~ / Library / LaunchAgents / script 2.plist

If you want to see which are loaded plists, type:

Code:

launchctl list

The boot time difference on Multiboot setup :

Many times you notice the time difference in a dual boot system is higher compare to regular. Especially when you are working two entirely different operating system which are based on different hardware architecture. For example using osx86. Many users face issue of getting Windows boot right after osx86 setup. There are certain fixes that can help you here to fix this problem. The setup and installation is easy with some updates you will need to download. The changes will lead to modification in Windows registry file. So have a backup of the same. Some entries located in Windows registry are quiet responsible for the boot time difference.

There is an reason behind this why does this happens. The common explanation is due to the different way of taking BIOS time is different in both operating system. In Windows the BIOS time that is your clock time is considered as the local bios time of your system. Sometime failed cmos lets to wrong time in your system. The scenarios for Mac is different. In this the UTC is which is called as Universal time is taken instead of the BIOS time. This results in boot time variation. This thing is needed to be fix to get an appropriate boot time. There are some bios udpates and patches for Mac DVD's which do the work.

**RedZot** · 27-08-2011

How to fix the boot time issue :

The problem can be resolves by an adjustment in the setup of osx86. There is no need to do major modification in your Windows. For this I found an script that runs on the installation of osx86. This manages the UTC with the regular bios time whenever you are using osx86. You have to take care that that script is properly initiated or else the problem will not be fixed. I had attached as script 1 & script 2 in the below attachment.

At first there is an script which you have to add in /sbin. Download script 1 and check. Do not rename just change the file extension. This script will toggle the utc time to local time.

Then download the second file and remove .txt from the end. You have to place the file /System/Library/LaunchDaemons. This file is necessary to initiate the above toggle script on startup. The file runs from launchd in Mac based operating system. This file is responsible to carry out the background process of the system. It also controls the background processes and other programs. This file leds to faster startup. Once the second script in placed in this location, launchd runs the first script where the UTC time is toggled with the local Windows time. This will reduce the boot time to very low, where the Mac system does not wait back to look for proper UTC update.

Once you done with script setup you will need to run some commands to execute the file properly. At first you will have to make the script executable. The command to run that file is - sudo chmod +x /sbin/ xxxxxxxx (the name of 1st script ). Once you are done with the first command then comes to execute the second script which is located in /System/Library/LaunchDaemons.
Commands :