pdftest

Windows Technology focus

Boot

Windows

Smooth out and speed up your PC boot process with Mike Williams’ expert guide

Covered in detail Applications ■ The BIOS p56 ■ Master Boot Record p56 ■ Drive troubleshooting p57 ■ Booting XP p57 ■ Booting Vista p58 ■ Boot Drivers p58 ■ Plug and Play p59 ■ Session Manager p59 ■ Log on p60 ■ Windows Services p60 ■ Loading Explorer p61

Technology focus ■ Booting in Safe Mode p59 ■ Startup troubleshooting p60 ■ Multi-core boot? p61

56

PCP275.feat5 Sec1:56

When your PC is running properly, you probably won’t spend a great deal of time thinking about the Windows boot process.

What would be the point? You turn your PC on in the morning, Windows starts and your desktop appears.

It happens automatically, and every time, so there will seem little need to worry about the technicalities.

This happy situation probably won’t last very long, though, as PC startup problems are annoyingly common.

Sooner or later you’ll find that your system boots slowly, displays odd error messages or in extreme cases won’t start at all. Many users live with boot problems or re-install Windows and start again, but there is a better way. If you learn what happens during the boot process then you’ll be able to diagnose and fix any issues that might arise.

The BIOS

T

he boot starts with your PC’s BIOS, which grabs its settings from CMOS RAM before initialising your video adaptor and any expansion cards. A Power On Self Test does basic hardware checks, tests your RAM if required and usually delivers a single beep to indicate that everything is working.

If there’s a problem at this point then the BIOS will display an error message or issue a number of beeps; check your motherboard manual to figure out what they might mean. If it’s accessible, launch your BIOS setup program to confirm that no settings have been changed. If they have, this could mean that your motherboard’s CMOS battery has failed, in which case you’ll need a replacement.

If you’ve installed an expansion card recently, try it in a different slot. Other new devices should be removed altogether to see if they are causing a problem. You can also check the support section of your motherboard or your PC manufacturer’s site for more advice.

These hardware problems are relatively uncommon, though. It’s likely that this first boot stage will be completed without incident and your PC will move smoothly into stage two, which is hard drive access.

Master Boot Record

T

he BIOS now attempts to load the first sector of the first drive specified in your boot order list (you’ll find this in the BIOS settings). If there’s nothing bootable in that device, the BIOS will work down the list until it encounters a hard drive.

The first sector of a hard drive normally contains the Volume Boot Record or Master Boot Record (MBR), a structure that includes a tiny program to launch the boot process and details of how your hard drive is partitioned.

The last two bytes of the sector now have a standard signature, which is ‘0x55AA’ (see www.multibooters. co.uk/mbr.html), so the BIOS checks for this to confirm that the drive is bootable. If those bytes aren’t present, it’ll skip this device and carry on down the boot order list, displaying an error message like ‘Operating system not found’ if it can’t find anything to boot.

If the signature is found, though, your BIOS will launch the MBR program. This scans each of your partitions, checking their boot indicator bytes. If these are all set to zero (not bootable), you’ll see an ‘Operating system not

1 Incorrect BIOS settings can extend your boot time, or prevent Windows starting altogether.

275 December 2008

29/9/08 7:23:57 pm

Technology focus Windows

faster found’ error message. If they’re anything other than zero or 0x80, you’ll see an ‘Invalid partition table’ message.

However, if it finds just one with a value of 0x80 (meaning bootable), then the MBR program will load the first sector in that partition, the Volume Boot Sector.

If the Volume Boot Sector can’t be read, the MBR program will say there’s an ‘Error loading the operating system’. If it can be read but doesn’t have the 0x55AA signature, then it’ll warn you that you have a ‘Missing operating system’. However, if both tests are passed then the program contained in the Volume Boot Sector will launch, and this leads to launching Windows itself.

Drive troubleshooting

B

oot problems might arise at this stage if your PC is trying to start from the wrong device.

Launch your BIOS setup program, look for the boot order list and change it so that your hard drive (or preferred boot device) comes first. This will also give the boot process a small speed boost.

It’s more likely that one of the boot structures on your hard drive has become corrupted, though, and Windows Vista can usually fix this automatically. Boot from your Windows installation disc, then work your way through the wizard, clicking the ‘Repair Your Computer’ option when you see it. Choose the operating system to repair, click ‘Next’, and select ‘Startup Repair’ to fix the problem.

Alternatively, use the tool ‘bootrec.exe’ to do it for yourself (see www.support.microsoft.com/kb/927392).

XP users have more manual work to do. You’ll need to boot from your Windows installation disc, launch the Recovery Console and try the ‘FIXMBR’ or ‘FIXBOOT’ commands to fix the Master Boot Record or Boot Sector (see www.support.microsoft.com/kb/314058).

However, FIXBOOT is risky if you’ve got more than one partition, as it may overwrite the current partition table.

The free tool Parted Magic (www.partedmagic.com) may be useful here, as it creates a bootable CD that can fix the MBR and Boot Sector, repair a broken partition table,

1 ‘Operating system not found’ error message? One or more of your basic hard drive structures has been corrupted.

recover a deleted partition and more. Just be careful.

This is a very low-level tool: make a mistake and you could create more issues than you solve.

Fact file

Booting XP

Windows XP loads many system components into a fixed memory location.

This is poor security practice as it gives malware a known point of attack. Windows Vista fixes this by loading its components into one of 256 random memory blocks, so it’s much less vulnerable to hackers (see www.tinyurl.com/6q6tl6).

T

he Windows XP Volume Boot Sector starts by launching the program ‘NTLDR’. You’ll see an error if this is missing, but otherwise NTLDR will start and check the root directory for a valid hibernation file (‘hiberfil.sys’). If found, NTLDR will restore it to memory so you carry on where you left off.

If you’re not waking up a hibernating PC, NTLDR will read the settings held in ‘boot.ini’ instead, displaying a boot menu when you’ve got more than one operating system installed. If only XP is installed (or you chose it from the menu), NTLDR will carry on loading Windows.

This process is quite resilient, so if, for example, boot.ini is deleted, the boot can probably continue with default settings (after displaying an error). However, this isn’t guaranteed and if NTLDR can’t be found then you’ll definitely be in trouble. Fortunately there’s a very easy way to insure yourself against such problems.

Take a CD, DVD, floppy or spare USB drive, and copy boot.ini, NTLDR and ‘Ntdetect.com’ across from the root folder of your hard drive. If one of these files becomes corrupted and Windows won’t start, boot from this emergency disc instead. Assuming there’s no other damage, Windows should start, and you can copy your system files back from the boot device to the hard drive.

If you didn’t make any preparations, you can also boot from your Windows CD, launch the Recovery Console and

3

275 December 2008 57

PCP275.feat5 Sec1:57

29/9/08 7:24:1 pm

Windows Technology focus

3 copy NTLDR from the CD to your hard drive (use a command like ‘COPY D:\i386\NTLDR C:\’, where ‘D:’ is replaced by the letter for your DVD drive). Or, if a missing boot.ini is the problem, enter the command ‘BOOTCFG / REBUILD’ to recreate it. (There’s more about Recovery Console at www.support.microsoft.com/kb/314058).

Booting Vista

U

1 Enable hibernation for the fastest possible Windows boot time.

Fact file Windows Vista stores its boot settings in the Boot Configuration Data file (BCD). This appears on your hard drive (\Boot\ BCD) and Registry (HKLM\ Bcd00000000), but must be edited using Vista’s command line BCDEdit (www.tinyurl. com/5n2ff2) or a simpler graphical tool like VistaBoot PRO (www. vistabootpro.org).

nder Windows Vista there is no NTLDR, and instead the Volume Boot Sector locates and launches the Vista Boot Manager, ‘bootmgr.exe’. This reads your startup settings from their new location, the Boot Configuration Data file (BCD). You’ll then see a boot menu if there’s more tthan one operating system installed.

If you y only have Vista installed, or have chosen Vista ffrom the menu, then Boot Manager will transfer transfe control to either Windows Resume when you’re rresuming from hibernation, or the Windows Loader if you’re starting from scratch.

The most common problem here is a missing or corrupted corrup BCD, resulting in error messages like ‘Windows ‘Windo Boot Configuration Data file is missing’.

These errors can usually be fixed by the Startup Repair tool that we discussed earlier, but you can re also restore the BCD manually.

Boo from your Windows Vista DVD and work Boot w to the System Recovery Options dialog as your way previou previously.

This time, select ‘Command Prompt’ rather than ‘System Repair’, then type ‘Bootrec / RebuildBcd’ an and press [Enter]. Type ‘Yes’ to confirm your Windows insta installation path and look for a confirmation message telling you that all is well.

Occasionally this will fail if bootrec.exe can’t find a Windows installation. You could try removing and recreating the BCD by entering the commands ‘Bcdedit /export C:\BCD_Backup’, ‘ren c:\boot\bcd bcd.old’ or ‘Bootrec /rebuildbcd’.

If that doesn’t work, then rebuild the file manually, see www.support. microsoft.com/kb/927391.

Boot drivers

W

hen you’re not restoring a hibernating PC, Windows uses the BIOS to collect very basic information on your PC buses, hard drives, video adaptors and so on.

This is extremely limited, but there’s really no alternative because Windows’ own, more sophisticated tools can’t be run yet. If the BIOS returns incorrect

1 The Windows Vista installation DVD includes some very useful troubleshooting tools.

information then this can cause odd problems, but you can check its report for yourself by browsing the Registry at HKLM\Hardware\Description.

NTLDR (or ‘winload.exe’) then loads core files like the Windows kernel (‘Windows\system32\ntoskrnl.exe’) and Hardware Abstraction Layer (‘Windows\system32\hal.dll’).

Next to be loaded is the System section of the Registry (Windows\system32\config\system). Windows then reads all the drivers listed under HKLM\System\CurrentControl Set\Services, loading anything with a Start value of 0. This marks them as boot drivers that deliver such a core service that they must be loaded before anything else. In fact, they’re loaded even in Safe Mode, so buggy third-party boot drivers can stop your PC starting altogether. To view the boot drivers on your system, run ‘msinfo32.exe’, click ‘Software Environment | System Drivers’ and the ‘Start Mode’ column header, then scroll down, looking for everything with a Start Mode of ‘boot’.

Everything loaded is checked against a security catalogue that holds the digital signatures for the original files (‘Windows\System32\catroot\{F750E6C3-38EE11D1-85E5-00C04FC295EE}\nt5.cat’). That’s good for security, but a problem if the catalogue becomes corrupted, as the boot stops if the signatures don’t match.

NTLDR/winload.exe’s final task is to launch the Windows kernel. This really gets things moving by initialising your processors, then its memory process manager, Plug and Play manager, manage process manager and just about core service it provides. every other ot There should also be a visual Ther indicator of progress about now, indicato loads the boot video as the kernel k driver. This T isn’t your actual video driver: it’s just a generic Windows file that knows just enough to display simple images and progress information. progres The kernel carries on initialising various low-level structures until it 1 VistaBootPRO is the easiest way reaches one of the most important to tweak your BCD settings. stages sso far: the I/O Manager starts

If your PC locks up during a normal startup, but can boot in Safe Mode then that’s a good indication of driver issues 58

PCP275.feat5 Sec1:58

275 December 2008

29/9/08 7:24:5 pm

Technology focus Windows

Booting in Safe Mode Recover from many startup problems with this invaluable boot We’ve discussed regular boots, but if you press [F8] as your PC starts and choose ‘Safe Mode’ from the menu, the process works differently.

The aim of Safe Mode is to use only the minimal set of core Windows drivers that will allow your PC to boot. This means that if a buggy third-party driver is preventing your system from starting, you should be able to boot into Safe Mode and investigate the problem. To ensure that this happens, the I/O Manager doesn’t load drivers from the standard Registry list, instead it browses the Registry keys list at HKLM\SYSTEM\ CurrentControlSet\Control\SafeBoot. This

contains keys called ‘Minimal’ for standard Safe Mode and ‘Network’ for Safe Mode plus networking. Beneath each of these keys are lists of the drivers that Windows will load. And the Safe Mode key also contains a value called ‘AlternateShell’, defaulting to ‘cmd.exe’. This tells Windows what to launch if you select ‘Safe mode with command prompt’.

If you really want to get into advanced tweaking then you could try customising this list. Could Safe Mode do without the Windows Defender service, maybe? You could delete it and find out. Perhaps you’d like to run one of your apps in Safe Mode, but it needs its own

up Plug and Play (PnP) and begins the process of loading your remaining device drivers.

Boot problems here are often caused by corrupt or missing Registry files, resulting in a message complaining that the ‘\windows\system32\config\system’ file is ‘Missing or corrupt’. If you’re using Vista, you should be able to fix this by using System Restore or booting from the Last Known Good Configuration (press [F8] when you boot, select ‘Advanced Boot Options’), but XP users may find they’re stuck with just the Recovery Console.

Fortunately, Microsoft detail a procedure that lets you recover a Registry backup copy from the command line (see www.support.microsoft.com/kb/307545).

Plug and Play

T

1 Safe Mode might just be the best disaster recovery feature ever introduced into Windows.

service to be running? It can be added here. Be sure to save the original list, though. Remember, this is complicated stuff – tweaking for grownups. Don’t blame us if anything goes wrong. ■

your hardware has been detected and the appropriate drivers loaded.

Hardware problems, driver faults or conflicts here can result in a very slow boot or your PC hanging altogether. If your PC locks up, but can boot in Safe Mode then that’s a good indication of driver issues. Launch the Event Viewer (‘eventvwr.msc’) and look for recent errors that might offer clues. The Windows Vista Event Viewer also records details of performance problems during the boot process.

You can also ask Windows to record the drivers loaded during boot (run msconfig.exe, select the Boot tab, enable a Boot Log Log, restart and check ‘\Windows\Ntbtlog.txt’). Remove or re-install hardware you’ve added recently and update other drivers, in particular for your motherboard.

he PnP manager initially knows of just one virtual device on your PC, and it’s named ‘root’. This is used by the Hardware Abstraction Layer to detect your main bus and everything directly connected to the motherboard. Any discovered hardware returns a vendor ID representing the manufacturer and a product ID that tells Windows what ventually, the kernel continues the boot process it is. The PnP Manager then looks in the Registry under by launching Session Manager (‘smss.exe’).

HKLM\System\CurrentControlSet\Enum to find a key This use the Registry keys at or below HKLM\ where the hardware type, vendor and product ID match System\CurrentControlSet\Session Manager to the device. The key should contain a value called ‘Driver’ call functions. It’ll run any programs defined at the which points to a particular Registry key under HKLM\ BootExecute Registry Key, for instance. Normally this just SYSTEM\ControlSet001\Control\ launches ‘autochk.exe’ aut (the boot Class and a value called ‘infpath’ version of ‘ch ‘chkdsk.exe’), but other that points to the driver INF file in programs – aand some viruses – \Windows\Inf. This finally tells will add them themselves to the list.

Windows where to load the driver.

Session M Manager is also Alternatively, it’ll discover that you responsible fo for delayed file rename don’t have a driver installed for or delete oper operations. If an this device at all, in which case uninstall pro program can’t remove you’ll be prompted to add it later, a file because it’s in use, for once Explorer has started. example, it’ll add its details to its As the process goes on, ‘FileRenameO ‘FileRenameOperations’ key.

Windows will find different buses Session Man Manager will follow its (PCI, USB and so on). It’ll load instructions aat the next boot. their drivers, which will go on to Session M Manager reads the discover everything attached to 1 The Microsoft System Information tool list of Known DLLs from the them, and this continues until all can display your boot drivers.

‘KnownDLLs ‘KnownDLLs’ Registry key. It

1 Click ‘View | Devices by Connection’ to see the order in which devices were detected.

Session Manager

E

Fact file By default, Windows plays a sound every time it boots, which is potentially alarming if you turned the speakers up extra loud the night before. For quieter mornings, launch the ‘Control Panel Sounds’ applet, select the Sounds tab and disable the Windows Startup and Windows Logon sounds.

275 December 2008 59

PCP275.feat5 Sec1:59

29/9/08 7:24:7 pm

Windows Technology focus

1 Blue screen error messages can be useful. The file, basic error message and stop code will help you to diagnose them.

Fact file For more information on PC boots, read the XP troubleshooting guide (www.tinyurl.com/ ywcvec) and guide to new Vista kernel features (www.tinyurl. com/5urf7a). A blog post covers How Windows Starts Up (www.tinyurl. com/5rwwwu), and Jonathan de Boyne Pollard has technical Vista details (www. tinyurl.com/6cvmg7).

3 creates your paging files according to the Registry settings at Memory Management\Paging Files, loads the remaining Registry files from the \Windows\ System32\Config folder and creates the system environment variables you’ll find at HKLM\System\ CurrentControlSet\Session Manager\Environment.

Next, Session Manager loads ‘win32k.sys’, a component that provides core Windows GUI services. This switches your display from the boot driver’s basic VGA resolution to whatever you’ve got set up, so when this happens you’ll know that the Session Manager is almost finished.

The most likely problem to occur here is that of a missing Registry. You can replace it using the same techniques that we used earlier in the Boot Drivers section.

Blue screen crashes naming win32k.sys are also common, but this file is rarely the culprit. Enter the stop code (it’ll be something like ‘0x0000008e’) and ‘Win32k. sys’ at www.support.microsoft.com for more advice.

Log on

T

he Windows Session Manager now creates a session that will allow programs to be run.

Under Vista, session 0 is reserved for Windows services, and Session Manager creates a second session for programs. It then launches another core Windows component, the Windows Client-Server Runtime SubSystem (‘\windows\system32\csrss.exe’).

Startup troubleshooting Track the Windows startup process to help diagnose boot problems If you’re still having boot problems despite our recommendations, checking exactly what happens during the Windows startup process might help.

To display driver names as they’re loaded, launch msconfig.exe, select the Boot tab and check ‘/SOS’ (in XP) or ‘OS Boot Information’ (in Vista). If you check the ‘Boot Log’ option then Windows will save this data to ‘\Windows\Ntbtlog.txt’.

You can also check the Event Viewer (launch ‘eventvwr.msc’) and look for error messages relating to recent boots.

For completeness, though, nothing beats Process Monitor (www.tinyurl. com/2okfn9). Click ‘Options | Enable Boot Logging’, restart your PC and it will record all file and Registry accesses from

60

PCP275.feat5 Sec1:60

the moment that the Windows Session Manager starts. You may have literally millions of events listed, but if you’ve got persistent boot issues that can’t be fixed in any other way, perusing the Process Monitor report just might help. ■

1 AutoRuns (www.tinyurl.com/39338j) shows you exactly which programs are launched when Windows starts.

Session Manager’s final initialisation step under XP is to launch the log-on process. This does much more than just logging on, though, starting a security process (‘\Windows \System32\Lsass.exe’) and launching the Service Control Manager (‘\Windows\System\Services.exe’). Finally it checks HKKLM\Software\Microsoft\WindowsNT\ CurrentVersion\WinLogon\GinaDLL, using that DLL to log you on if one is specified or otherwise launching the default \Windows\System32\MSGINA.DLL. Under Vista this changes a little. A new process called ‘WinInit.exe’ handles the security and Service Control Manager work, while the logon uses a much more flexible Credential Provider system. There can be more than one of these, and Session Manager checks the HKLM\Software\ Microsoft\Windows NT\Currentversion\Authentication\ Credential Providers to find out what it must launch.

Most problems that occur here will be down to missing files, although there’s always the possibility that malware will try to replace one of these Windows components. If you’re experiencing difficulties, check the Registry keys we’ve mentioned for unusual entries.

Windows Services

T

he log-on process may not prompt you for a password if it’s been configured that way (run ‘CONTROL USERPASSWORDS2’, select the account to automatically log in to and uncheck ‘Users must enter a user name and password...’). However, otherwise it will display the log-on screen, then wait for you to enter your account details. This isn’t entirely wasted time, though, as in the background the Service Control Manager (SCM) will be loading your Windows Services.

The SCM starts by browsing the Registry at HKLM\ System\CurrentControlSet\Control\ServiceGroupOrder\ List. This lists service groups in the order in which they should be loaded, so ‘Primary Disk’ comes before ‘Boot File System’, for instance (the PC can’t manipulate a file system until it can access a disk). The SCM then scans your list of services (HKLM\SYSTEM\CurrentControlSet\Services), looking for ‘DependOnGroup’ and ‘DependOnService’ keys.

A network-related service might have a DependOn Service entry of ‘TcpIp’, say, as the TCP/IP service must be loaded first. The SCM uses this data to determine the order in which services must be loaded, then initialises all services with a startup type of Automatic (that’s a Start value of 2).

Not all services are immediately essential, though, and so Vista tries to speed up the boot process with a new tweak. Non-critical services like Windows Media Player Network Sharing are assigned a startup value of ‘Automatic (Delayed Start)’, which means that the SCM starts it after everything else, with a very low initial

1 The boot process continues even while the logon screen is displayed, as Windows Services are loaded in the background.

275 December 2008

29/9/08 7:24:11 pm

Technology focus Windows

Multicore boot?

There are lots of boot tweaks online, but be careful – they don’t all work

1 The he new Delayed Start services option in Vista can shave ve a few seconds off your boot time.

priority. Any delayed start services get very few CPU or disc resources during their startup phase, which means they’ll take a while to initialise, but Explorer and everything else should load more quickly by comparison.

If you’re running Vista then you can probably extend the same trick to other, third-party services, and perhaps further improve your boot time. Launch ‘services.msc’ and browse the list. To change the Startup Type to ‘Automatic (Delayed Start)’ double-click the program entry. Repeat with non-essential services from applications you’ve installed, but be careful – apply the technique to more critical components, like antivirus tools, and you could crash your PC on the next boot. Don’t experiment at all unless you have the backups to recover from any situation.

Once the SCM finishes loading your services, it waits for a signal from the Windows logon component to tell it that you’ve successfully logged on. If this happens, and all your autostart services have loaded without errors, then the current copy of HKLM\SYSTEM\CurrentControlSet is saved as the last known good configuration, and will be used if you choose that option from the boot menu. Check the Registry key HKEY_LOCAL_MACHINE\SYSTEM\ Select to see the ‘CurrentControlSet’ copy you’re using right now, and the one that’s labelled as ‘LastKnownGood’.

Loading Explorer

A

fter loading the HKEY_CURRENT_USER Registry hive from this user account, it’s finally time to load the Windows shell. This process begins by loading any executables listed at HKLM\SOFTWARE\Microsoft\Windows NT\ CurrentVersion\Winlogon\UserInit, which by default points to ‘\Windows\System32\UserInit.exe’.

The UserInit program runs any log-on scripts named in HKCU\Software\Policies\Microsoft\Windows\System\ Scripts, and the equivalent HKLM Registry key. It finally locates the program stored in HKCU\SOFTWARE\ Microsoft\Windows NT\CurrentVersion\Winlogon\Shell (or the HKLM equivalent if that doesn’t exist), which by default is ‘explorer.exe’. The desktop is initialised, the

A new boot tip you’ll find online says that Windows boots slowly because it only uses one CPU. Enable all the cores (launch msconfig.exe, select the Boot tab, click ‘Advanced Options’ and increase the Number of Processors), they say, and you’ll get better performance.

It’s true that initially the boot process only uses one core, but there’s no alternative: the Windows code that creates threads and schedules them hasn’t been loaded yet. The Msconfig setting does nothing to change this and is actually used to disable CPU cores – for example, if you’re running ancient software that misbehaves when it’s

running on more than one processor.

If you do this, just remember to restore normal operations when you’re done. ■

1 Sadly, this Msconfig tweak won’t make any difference to your boot performance.

taskbar appears, startup programs are launched and you’re finally able to use the PC. At least, that’s what should happen.

Boot problems here may be caused by missing or corrupt data. There may be a problem with the Registry hive for your user account, for instance. If the Registry pointers to ‘UserInit.exe’ or explorer.exe are missing then the boot won’t complete. Use System Restore or use the Last Known Good Configuration to fix the problem.

The most likely issues arise from thirdparty conflicts, though, either apps you’ve installed or malware that’s infected your PC. In extreme cases the Windows desktop won’t appear correctly and you’ll receive an error or message saying that explorer.exe ‘failed to initialise properly’.

You may be able to work around an explorer.exe initialisation problem by closing and relaunching the current process. That is, press [CTRL]+[Shift]+[ESC] to launch Task Manager, select the Processes tab, right-click ‘explorer.exe’ and select ‘End Process Tree’. Then click ‘File | New Task’, type ‘explorer.exe’ and press [Enter].

If that fails, try booting into Safe Mode, use System Restore or boot from the Last Known Good Configuration.

If you’ve just installed something that might have caused the problem, remove it. Otherwise, see the ‘Startup Troubleshooting’ box for tools that should soon have your system running smoothly again. ■

1 Explorer won’t start?

You may be able to launch it manually from Task Manager.

Mike Williams learned about the PC boot process in the days of DOS, when he wrote tools to fix startup problems. feedback@pcplus.co.uk

The most likely boot issues arise from third-party conflicts – either programs you’ve installed or malware infections 275 December 2008 61

PCP275.feat5 Sec1:61

29/9/08 7:24:13 pm