when you run sage you get the following error
'serial and activation key combo are not valid. and you cannot change them'
solution:
I have had this problem numerous times in the past where the installation proceeds then ends with the messages:
During the installation of the device.
The system cannot find the file specified
and it goes into a detection loop
HERE is the solution:
Windows 2000/XP has a bug that it cannot properly detect new hardware by *.inf files, if the RunOnce registry key is missing for the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
This key is often used by installers to execute post-reboot programs, but sometimes they accidentally delete this key.
IMPORTANT: This article contains information about modifying the registry. Make sure that you understand how to backup and restore the registry, in case a problem occurs. Please read the linked Microsoft Knowledge Base article prior to editing the registry.
Go to Start » Run and enter "regedit."
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
With CurrentVersion Highlighted, go to the Edit menu and select New » Key
Name the key RunOnce, leaving everything else about the key alone.
The RunOnce key should now exist underneath the CurrentVersion key.
Once the key exists, Windows 2000/XP stops redetecting the Hardware
see also this article, Driver Install Error - "Class installer"
Note : Before trying the step below please run startup repair first
Solution :
1. Boot the computer from Vista OS DVD.
Click on Repair Your Computer.
Click on Command prompt.
At the X:\Sources prompt, type bcdedit /export C:\BCD_Backup and press <Enter>
Type c: and press <Enter>.
At the C:\ prompt, type cd boot and press <Enter>.
At the C:\Boot prompt, type attrib bcd -s -h -r and press <Enter>.
At the C:\Boot prompt, type ren c:\boot\bcd bcd.old and press <Enter>.
At the C:\Boot prompt, type bootrec /rebuildbcd and press <Enter>.
The Boot Configuration File will be rebuilt at this point. Once it finishes, type exit and press <Enter>. Click the Restart button
Here are some other commands
bootrec /RebuildBcd - Use this option when you must completely rebuild the BCD
bootrec /FixMbr - writes a Windows Vista-compatible MBR to the system partition
bootrec /FixBoot - writes a new boot sector to the system partition by using a boot sector that is compatible with Windows Vista
If the automated startup repair doesn't do it - even after a few goes , as Prasath says,
I would try this first
bootrec /fixmbr
your dvdrom drive letter:\boot\bootsect.exe /nt60 all /force
del C:\boot\bcd
bootrec /rebuildbcd
Close cmd prompt
remove dvd, Reboot.
Fingers crossed.
You'll need to delete the registry folders for DivX from the machine (be sure to get both the local and user level folders).
To do this go to start > type 'regedit' in the run box > delete the software/divx folders from the registry of the local machine and relevant user accounts.
Once this is done run the installer file again (you do not need to uninstall first) and it will offer you the option to select an install language again. Select the correct language and complete the install as normal.
Reboot and you should find the problem corrected
The boot.ini file is a hidden file that is used to identify in what folder on which partition and on which hard drive Windows XP is located. Boot.ini can become damaged, corrupted or deleted for a number of reasons and is usually brought to your attention by an error message.
Follow these easy steps to repair the damaged/corrupted boot.ini file or replace it if it has been deleted.
Enter Windows XP Recovery Console. The Recovery Console is an advanced diagnostic mode of Windows XP with special tools that will allow you to restore the boot.ini file.
When you reach the command line (detailed in Step 6 in the link above), type the following command and then press Enter.
bootcfg /rebuild
The bootcfg utility will scan your hard drives for any Windows XP installations and then display the results. Follow the remaining steps to add your Windows XP installation to the boot.ini file.
The first prompt asks Add installation to boot list? (Yes/No/All).
Type Y in response to this question and press Enter.
The next prompt asks you to Enter Load Identifier:.
This is the name of the operating system. For example, type Windows XP Professional or Windows XP Home Edition and press Enter.
The final prompt asks you to Enter OS Load options:.
Type /Fastdetect here and press Enter.
Take out the Windows XP CD, type exit and then press Enter to restart your PC.
Assuming that a missing or corrupt boot.ini file was your only issue, Windows XP should now start normally.
If like me you want to have all your email PST files in one easy place to backup (ie on your D: drive) you might need to move your PST Files. POP3 PST easily enough but the IMAP PST are always created in the default PST location and if you try and move them like normal POP3 PST files the file will respawn with a different name in the default location redering the moved IMAP PST useless.
How IMAP PST files are handled changes from version to version of out look and I recommen you read the article below before doing anything else. You should also consider that when you recreate an IMAP profile all of the items will re-sync anyway so the only thing you would need to do is change the default location. The articles below go into more detail about this process.
Links
Moving POP3 PST files is really easy.
POP3 Send and Receive Error 0x8004010F
Occasionally you will get an error 0x8004010F which is caused by internal PST links not working. The links below show you how to fix the broken links.
Microsoft Word bullets help organize information into an easy-to-read format, but if the bullets aren't spaced correctly it can throw off the look of your document. Microsoft Word 2010 has two different ways to alter the spacing of bullet points. The first way changes the indent between the edge of the paper and the bullet point, along with the bullet point and the text, while the second way changes the distance between separate bullet points.
Instructions
Does any one know what the differences are between PCL5, PCL5E and PCL6? Are there any differences in the commands supported?
PCL (Printer Control Language) is a printing language developed by HP and PCL drivers is a language (a set of command codes) that enable application programs to control Hewlett-Packard DeskJet (some models), LaserJet (all models), and other HP printers. Many personal computer users find themselves in need of PCL drivers after purchasing a new HP or HP-compatible printer and attaching it to their existing PC and operating system. PCL5 allows you to download macros, fonts and forms to the printer memory (RAM or HD), so you can store unvariable data in the printer and minimize the size of the file you'll print. The fonts, macros and forms are "called" and merged into the printout via PCL commands embedded in the file body.
PostScript is a programming language developed by Adobe and transformed into a printing language. It describes the appearance of a printed page, mantaining its formatting, color and print quality settings. Because of that, print files generated with PS drivers can be portable among different printers without the file that will be printed lose quality, color definitions or formatting. The printer must have a PS module that translates the PostScript commands. Macintosh computers and applications working inside an Windows network environment uses PS drivers (PostScript has born in Mac world - Windows world used PS later).
Both driver types groups the print commands and settings into the whole page, so if there's an error when processing the file, the whole page will be lost and you have to reprint the page you lost, or all the file, depending on the error. They're different of the PCL3 (print language for most DeskJet printers), which separates the file in swaths - this is the reason why DeskJet printer don't need much memory; it has only the necessary to store the swath it's printing now. Resulting: PCL3 always prints. The tradeoff is that PCL3 generates much more data than PCL5,6 or PS files (the PC process all the job and the print file size is large, so PCL3 is most used in parallel connections.
Unlike PCL3 (DeskJet) printers, Laser printers that make use of PCL5, PCL6 or PS must have powerful processors and much more built memory because they have to process the whole page (or the whole print job). By this reason, PCL and PostScript drivers tranfers all the processing charge to the printer and the PC doesn't suffer with performance issues - the "Return to application" time is smaller. The PC "closes" the file and send to the printer, so the print file size is much smaller. By this reason, PCL5,6 and PS are most used in network environments.
Choosing PCL or PS drivers depends on the applications you're using. For example, if you're using graphic applications like PhotoShop, Corel or similars, the best choice is the PS driver. By other hand, if you're using desktop applications (Excel, Word, PowerPoint and so on), the best choice is the PCl drivers. If you want to make use of downloading forms and fonts to the printer, you must use PCL drivers because PS drivers doesn't do that.
This tip could be applied to any kind of Windows Update on windows XP be it manual update or automatic update.
A failure in updating could happen when you suddenly get disconnected or downloaded corrupted data which happens a lot. And it seems that there is no local check to ensure that the file is actually complete. It just attempts to install the downloaded material even if its not complete. The stupid thing is that even though you try to update again, it just checks the cache, see that its there and won't bother redownloading the files.
Therefore when you face such a scenario, you could take these steps to solve your problems:
Thats all. Its simple right? Good luck.
Solution 1:
Try to remove it from Installed Updates:
1. Click on “Control Panel” in “Start menu”
2. Go to “Uninstall a program” in “Control Panel”
3. Click on “View installed updates” in “Programs and Features”
4. Right click on Update which reads Powershell and uninstall it.
Solution 2:
PowerShell is not present in the add/remove programs. I thought I had PowerShell deleted in Add/Remove Programs - but apparently it is still there and I cannot complete the In-Place upgrade on my Windows Vista.
Solution 3:
I had the same problem. It was not showing up as an installed program or update, it was still there though! I even tried to install it and then uninstall it, nothing seemed to work.
After playing around I decided to manually remove the files but even after trying to change the permissions, it would not let me delete them. What a pain.
Here is my quick fix:
OR
If your feeling spunky, you can rename the folder back to WindowsPowerShell, after the upgrade, despite it being incompatible...but I wouldn't recommend it.