Anderton

Hello Rippie, Unfortunately the only software that I tested was "Boot Log XP". I don't have Windows 7 or even Vista, so I won't test any other "Boot Logger" too soon… Meanwhile this program only works for Windows XP, but they intend release a version that works in 64-bit, Vista/Seven: http://www.greatis.com/utilities/bootlogxp/bootvis_replacement.htm Kind regards.

There is an option: Boot Log XP http://www.greatis.com/utilities/bootlogxp/index.html You can look for "Microsoft Bootvis": http://www.greatis.com/utilities/bootlogxp/bootvis_replacement.htm Good luck.

You can try this: Fix the ugly menu bar after applying a custom theme http://windowsxp.mvps.org/uglymenubar.htm Do not change your registry without a backup. Good luck.

Last month (April), after one year (it takes ages to HP fixes this problem) HP finally begins to release a hotfix to this problem. This was the worst support case that I have ever seen in my life. After install all the new updates displayed in the HP page for my printer all my problems and errors with the Word 2007 are gone now. Even using HP as my default printer (no changing was necessary anymore). Good luck.

Yes. You are right. The "Microsoft .NET Framework 3.5 Service Pack 1" is the full updated package for v2.0 SP2, v3.0 SP2 and v3.5 SP1. You don't need to install " .NET 2.0 SP2" first. Microsoft .NET Framework 3.5 Service Pack 1 Full Package To download the full package, rather than the bootstrapper, click on the link below: .NET Framework 3.5 Service Pack 1 (Full Package) IMPORTANT: After installing the .NET Framework 3.5 SP1 package (either the bootstrapper or the full package) you should immediately install the update KB959209 to address a set of known application compatibility issues. If you still have problems with these .NET versions you can try also the updates below (post v2.0 SP2, v3.0 SP2 and v3.5 SP1): The best thing to do is to wait for a new update rollup package with the above mentioned patchs. Regards.

Try this: cdimage -e -b<bootsector> -l<label> -h -n -d -m -x -o -w1 "<source folder>" "<destiny folder\NAME.ISO" And see if it works for you. Good luck.

Hello, In the previous versions of "win32k.sys" in Portuguese Brazilian language (PTB) this bug appears in QFE brand. The bug was fixed in the new version of the file: MS09-006: Vulnerabilities in Windows Kernel could allow remote code execution http://support.microsoft.com/kb/958690/ The error doesn't appear anymore in QFE PTB version; the translation was fixed. Best regards, Anderton.