HKPrince

Quote: I was hoping I could try and get W98 to appear in the Loader before I boot into XP. Dual booting of Windows XP with another Windows OS such as 98 or ME (NT, I don't know), you will need the ntdetect.com, ntldr, boot.ini (you should have them), another pagefile.sys on the Windows OS root directory (I don't know why there is another) etc, and most important, bootsect.dos, the boot sector image of another Windows OS. Without it, even you write the boot option of the Windows OS in boot.ini, Windows XP doesn't know how to do. Whenever Windows XP or Windows 2000 is installed with an existing Windows OS, it modifies the master boot record of the harddisk and add its own boot sector to it, then move the boot sector of the OS to bootsect.dos. When the computer boots, it reads the boot sector and calls up ntldr (NT loader). NT loader allows you to select OS which is written in boot.ini. If you select another OS, NT loader then call the bootsect.dos to boot another OS. I hope I am writing the right thing because I have tried to do the same thing but I search in the net and find out it is quite difficult.

I get an email from PowerVR Technologies about 10 minutes after I send them an email about the crashing after quit from 3D games to the desktop. And I use the driver verifier manager to locate the problem causing driver.

There is an utilty called driver verifer manager in Windows XP and Windows 2000, it is used to verify whether a driver is OK or not. You can use this utility to find out which driver causes the problem, though you can't do anything to solve it if it is the only driver you have. Maybe uninstall the problematic hardware, looking for a newer driver or write to the hardware company and tell them to solve the problem. Below is information from Microsoft: Driver Verifier is a tool that can monitor one or more kernel-mode drivers to verify that they are not making illegal function calls or causing system corruption. Driver Verifier performs extensive tests and checks on the target drivers. For example, if the driver uses memory at an improper IRQL, improperly calls or releases spin locks and memory allocations, or frees memory pool without first removing any timers, Driver Verifier will issue the appropriate bug check.