Today bought a Brother DCP-7020 Multi-function Laser Printer from CanadaComputers, the price is $132 (cash price $130) plus tax, the same printer sold at bestbuy is $162 after discount(original price $235). when I tried to buy it 2 days ago when it was on sale, no store in GTA has in stock and I don't want to pay $10 for shipping:-). after spend more time searching on google, I found a nice web site http://www.pricecanada.com/, from there it shows several stores and compares the prices. great web site.
Next step would be to buy a toner (TN350?) from costco.ca, it's about $50.
Now need to spend time to figure out how to use all the features of this great bargin printer....
Wednesday, February 27, 2008
Monday, February 18, 2008
Description of the Windows Installer CleanUp Utility
View products that this article applies to.
Article ID : 290301
Last Review : May 7, 2007
Revision : 5.6
This article was previously published under Q290301
Warning The Windows Installer CleanUp Utility is provided "as is" to help resolve installation problems for programs that use Microsoft Windows Installer. If you use this utility, you may have to reinstall other programs. Caution is advised. We recommend that you do not use this utility with 2007 Office system products.
On This Page
SUMMARY
MORE INFORMATION
Contents of the Readme.txt file
SUMMARY
Microsoft has updated the Windows Installer CleanUp Utility. With the Windows Installer CleanUp Utility, you can remove a program's Windows Installer configuration information. You may want to remove the Windows Installer configuration information for your program if you experience installation (Setup) problems. For example, you may have to remove a program's Windows Installer configuration information if you have installation problems when you try to add (or remove) a component of your program that was not included when you first installed your program.
The Windows Installer CleanUp Utility does not perform the following functions: • Remove Windows Installer
• Remove files of any programs that are installed by Windows Installer, such as Microsoft Office 2003
The Windows Installer CleanUp Utility does perform the following functions: • Provides a dialog box in which you can select one or more programs that were installed by Windows Installer
To do this, select the programs that you want in the Installed Products list in the Windows Installer CleanUp dialog box. After you make this selection, the utility removes only the Windows Installer configuration information that is related to those programs.
• Removes the files and registry settings that make up the Windows Installer configuration information for programs that you select
If you use this utility to remove the Windows Installer configuration information for your program and you plan to reinstall the program, you should reinstall the program in the same folder where you originally installed it. This prevents duplication of files on your hard disk or disks.
Back to the top
MORE INFORMATION
This version of the Windows Installer CleanUp Utility works correctly in all 32-bit versions of Microsoft Windows. The 32-bit versions of Microsoft Windows are as follows: • Microsoft Windows Vista
• Microsoft Windows Server 2003
• Microsoft Windows XP
• Microsoft Windows Millennium Edition
• Microsoft Windows 2000
• Microsoft Windows NT 4.0 with Service Pack 3 or later
• Microsoft Windows 98
• Microsoft Windows 95
This version of the Windows Installer CleanUp Utility works correctly in all 64-bit versions of Microsoft Windows. The 64-bit versions of Microsoft Windows are as follows:• Microsoft Windows Server 2003
• Microsoft Windows XP
• Microsoft Windows Vista
The following file is available for download from the Microsoft Download Center:
Download the Windows Installer Cleanup Utility package now.
Back to the top
Contents of the Readme.txt file
README FOR WINDOWS INSTALLER CLEAN UP UTILITY version 3
SEPTEMBER, 2006
WHAT IS THE WINDOWS INSTALLER CLEAN UP UTILITY?
The Windows Installer Clean Up Utility is a tool that can be used to remove Windows Installer configuration management information if a problem occurs.
*** NOTE: The Windows Installer Clean Up Utility should not be used to remove the 2007 Microsoft Office System installation information. ***
The Windows Installer configuration management information can become damaged if any of the following issues occur:
- The computer's registry becomes corrupted.
- A registry setting that is used by the Windows Installer is
inadvertently changed, and this change results in a problem.
- The installation of a program that uses Windows Installer (for
example, Microsoft Office 2003) is interrupted.
- There are multiple instances of a setup program running at the same time, or
an instance of a setup program is "blocked."
WHAT HAPPENED TO MSICU.EXE?
In the original release, there were two versions of the Windows Installer Clean Up Utility: Msicu.exe (for use in Microsoft Windows 95, Windows 98 and Windows ME), and Msicuu.exe (for use in Windows NT, Windows 2000, Windows XP, and Windows Server 2003). Msicu.exe was removed because Msicuu.exe now works with all 32-bit versions of Microsoft Windows.
WHAT IS MSIZAP.EXE?
The Windows Installer Clean Up Utility uses the Msizap.exe program file to perform cleanup operations on the Windows Installer configuration management information. Microsoft does not recommend that you run Msizap.exe manually, because Msizap.exe uses a command-line interface. Msizap.exe does not provide the same ease of use or level of protection as the Windows Installer Clean Up Utility.
WHY IS THERE NO MSIZAP.EXE IN THE EXTRACTED FILES?
There are two versions of MSIZAP.EXE: MsiZapA.exe (for use in Windows 95, Windows 98 and Windows ME), and MsiZapU.exe (for use in Windows NT, Windows 2000, Windows XP, and Windows Server 2003). The appropriate executable must be renamed MsiZap.exe in order for the Windows Installer Clean Up Utility to work correctly. The installation process renames and installs the correct version automatically.
HOW DO I INSTALL THE WINDOWS INSTALLER CLEAN UP UTILITY?
When you download the utility, choose either Install or Save (if you choose Save then run the downloaded executable from the folder in which you saved the executable). By default, the setup program installs the Windows Installer Clean Up Utility files to a folder beneath the Program Files folder. This folder is called "Windows Installer Clean Up."
All the files that are used by the utility (Msicuu.exe, Msizap.exe, and this Readme file) are copied into this folder, and a shortcut is created on the Programs menu under the Start menu.
The files may also be extracted manually from the downloaded file. However, after you do this, you must rename the appropriate MsiZap*.exe file "MsiZap.exe." (NOTE: If you use the utility on Windows 95/98/98SE/ME, rename MsiZapA.exe. Otherwise, rename MsiZapU.exe.)
HOW DO I RUN THE WINDOWS INSTALLER CLEAN UP UTILITY?
To run the Windows Installer Clean Up Utility, use either of the following methods:
- Click 'Start', click 'All Programs' (or 'Programs' on some operating systems), and then click the shortcut for the
Windows Installer Clean Up Utility.
- Find and run the Msicuu.exe file.
A dialog box will be displayed that contains a message, a list of installed products, and four buttons.
The message that is displayed is as follows:
Continuing further will make permanent changes to your system. You may
need to reinstall some or all applications on your system that used the
Windows Installer technology to be installed. If you do not want to
proceed, please press the 'Exit' button now. Choosing 'Remove' will
make the permanent changes.
The list contains the titles of all the installed programs that are registered with Windows Installer. Because the Windows Installer Clean Up Utility installation also uses Windows Installer, the Windows Installer Clean Up Utility should be included in the list. Select the programs that you wish to remove. (To select multiple items in the list, hold down the SHIFT key or the CTRL key as you select the items.)
The four buttons in the dialog box are as follows:
[Select All] - Selects all the programs in the list.
[Clear All] - Clears the selection of all the programs in the list.
[Remove] - Removes the Windows Installer installation information for
the selected program or programs.
[Exit] - Exits the Windows Installer Clean Up Utility.
If you click 'Remove,' the following prompt is displayed:
Warning - All items selected will be removed from the Windows Installer
database. In order for the items to work properly, you must individually
re-install all items selected. Select OK to continue removing product,
Cancel to abort.
If you click 'OK,' all the Windows Installer information that is associated with the selected programs is removed. This includes the entries for the programs in the Add/Remove Programs tool in Control Panel. If you remove the installation information for an installed program, the program is prevented from being able to add or remove components or to repair itself. NOTE: If you remove the installation information, files or shortcuts for the programs themselves are not removed. You should reinstall the programs before you try to use them.
WHAT IF I RECEIVE AN ERROR MESSAGE?
The following table lists the Windows Installer Clean Up Utility error messages that you may receive and the cause for each message.
Error message:
This utility requires that Msizap.exe version 2 or greater reside in the same folder.
Cause:
Msizap.exe version 2 or a later version of Msizap.exe cannot be found in the same folder as Msicuu.exe.
---------------------------------------------------------------------------
Error message:
You must have Administrator rights to run this utility.
Cause:
To run Msicuu.exe, you must be logged on with administrator rights.
---------------------------------------------------------------------------
Error message:
This utility requires that the Windows Installer be installed and properly registered.
Cause:
Msicuu.exe uses the Windows Installer object model to identify the installed products.
To correct the problem, try reregistering Msi.dll.
HOW DO I REMOVE THE WINDOWS INSTALLER CLEAN UP UTILITY?
When the Windows Installer Clean Up Utility is installed, an entry for the utility is created in the Add/Remove Programs tool in Control Panel. To remove the Windows Installer Clean Up Utility, click the entry in the list of installed programs, and then click 'Remove.'
Article ID : 290301
Last Review : May 7, 2007
Revision : 5.6
This article was previously published under Q290301
Warning The Windows Installer CleanUp Utility is provided "as is" to help resolve installation problems for programs that use Microsoft Windows Installer. If you use this utility, you may have to reinstall other programs. Caution is advised. We recommend that you do not use this utility with 2007 Office system products.
On This Page
SUMMARY
MORE INFORMATION
Contents of the Readme.txt file
SUMMARY
Microsoft has updated the Windows Installer CleanUp Utility. With the Windows Installer CleanUp Utility, you can remove a program's Windows Installer configuration information. You may want to remove the Windows Installer configuration information for your program if you experience installation (Setup) problems. For example, you may have to remove a program's Windows Installer configuration information if you have installation problems when you try to add (or remove) a component of your program that was not included when you first installed your program.
The Windows Installer CleanUp Utility does not perform the following functions: • Remove Windows Installer
• Remove files of any programs that are installed by Windows Installer, such as Microsoft Office 2003
The Windows Installer CleanUp Utility does perform the following functions: • Provides a dialog box in which you can select one or more programs that were installed by Windows Installer
To do this, select the programs that you want in the Installed Products list in the Windows Installer CleanUp dialog box. After you make this selection, the utility removes only the Windows Installer configuration information that is related to those programs.
• Removes the files and registry settings that make up the Windows Installer configuration information for programs that you select
If you use this utility to remove the Windows Installer configuration information for your program and you plan to reinstall the program, you should reinstall the program in the same folder where you originally installed it. This prevents duplication of files on your hard disk or disks.
Back to the top
MORE INFORMATION
This version of the Windows Installer CleanUp Utility works correctly in all 32-bit versions of Microsoft Windows. The 32-bit versions of Microsoft Windows are as follows: • Microsoft Windows Vista
• Microsoft Windows Server 2003
• Microsoft Windows XP
• Microsoft Windows Millennium Edition
• Microsoft Windows 2000
• Microsoft Windows NT 4.0 with Service Pack 3 or later
• Microsoft Windows 98
• Microsoft Windows 95
This version of the Windows Installer CleanUp Utility works correctly in all 64-bit versions of Microsoft Windows. The 64-bit versions of Microsoft Windows are as follows:• Microsoft Windows Server 2003
• Microsoft Windows XP
• Microsoft Windows Vista
The following file is available for download from the Microsoft Download Center:
Download the Windows Installer Cleanup Utility package now.
Back to the top
Contents of the Readme.txt file
README FOR WINDOWS INSTALLER CLEAN UP UTILITY version 3
SEPTEMBER, 2006
WHAT IS THE WINDOWS INSTALLER CLEAN UP UTILITY?
The Windows Installer Clean Up Utility is a tool that can be used to remove Windows Installer configuration management information if a problem occurs.
*** NOTE: The Windows Installer Clean Up Utility should not be used to remove the 2007 Microsoft Office System installation information. ***
The Windows Installer configuration management information can become damaged if any of the following issues occur:
- The computer's registry becomes corrupted.
- A registry setting that is used by the Windows Installer is
inadvertently changed, and this change results in a problem.
- The installation of a program that uses Windows Installer (for
example, Microsoft Office 2003) is interrupted.
- There are multiple instances of a setup program running at the same time, or
an instance of a setup program is "blocked."
WHAT HAPPENED TO MSICU.EXE?
In the original release, there were two versions of the Windows Installer Clean Up Utility: Msicu.exe (for use in Microsoft Windows 95, Windows 98 and Windows ME), and Msicuu.exe (for use in Windows NT, Windows 2000, Windows XP, and Windows Server 2003). Msicu.exe was removed because Msicuu.exe now works with all 32-bit versions of Microsoft Windows.
WHAT IS MSIZAP.EXE?
The Windows Installer Clean Up Utility uses the Msizap.exe program file to perform cleanup operations on the Windows Installer configuration management information. Microsoft does not recommend that you run Msizap.exe manually, because Msizap.exe uses a command-line interface. Msizap.exe does not provide the same ease of use or level of protection as the Windows Installer Clean Up Utility.
WHY IS THERE NO MSIZAP.EXE IN THE EXTRACTED FILES?
There are two versions of MSIZAP.EXE: MsiZapA.exe (for use in Windows 95, Windows 98 and Windows ME), and MsiZapU.exe (for use in Windows NT, Windows 2000, Windows XP, and Windows Server 2003). The appropriate executable must be renamed MsiZap.exe in order for the Windows Installer Clean Up Utility to work correctly. The installation process renames and installs the correct version automatically.
HOW DO I INSTALL THE WINDOWS INSTALLER CLEAN UP UTILITY?
When you download the utility, choose either Install or Save (if you choose Save then run the downloaded executable from the folder in which you saved the executable). By default, the setup program installs the Windows Installer Clean Up Utility files to a folder beneath the Program Files folder. This folder is called "Windows Installer Clean Up."
All the files that are used by the utility (Msicuu.exe, Msizap.exe, and this Readme file) are copied into this folder, and a shortcut is created on the Programs menu under the Start menu.
The files may also be extracted manually from the downloaded file. However, after you do this, you must rename the appropriate MsiZap*.exe file "MsiZap.exe." (NOTE: If you use the utility on Windows 95/98/98SE/ME, rename MsiZapA.exe. Otherwise, rename MsiZapU.exe.)
HOW DO I RUN THE WINDOWS INSTALLER CLEAN UP UTILITY?
To run the Windows Installer Clean Up Utility, use either of the following methods:
- Click 'Start', click 'All Programs' (or 'Programs' on some operating systems), and then click the shortcut for the
Windows Installer Clean Up Utility.
- Find and run the Msicuu.exe file.
A dialog box will be displayed that contains a message, a list of installed products, and four buttons.
The message that is displayed is as follows:
Continuing further will make permanent changes to your system. You may
need to reinstall some or all applications on your system that used the
Windows Installer technology to be installed. If you do not want to
proceed, please press the 'Exit' button now. Choosing 'Remove' will
make the permanent changes.
The list contains the titles of all the installed programs that are registered with Windows Installer. Because the Windows Installer Clean Up Utility installation also uses Windows Installer, the Windows Installer Clean Up Utility should be included in the list. Select the programs that you wish to remove. (To select multiple items in the list, hold down the SHIFT key or the CTRL key as you select the items.)
The four buttons in the dialog box are as follows:
[Select All] - Selects all the programs in the list.
[Clear All] - Clears the selection of all the programs in the list.
[Remove] - Removes the Windows Installer installation information for
the selected program or programs.
[Exit] - Exits the Windows Installer Clean Up Utility.
If you click 'Remove,' the following prompt is displayed:
Warning - All items selected will be removed from the Windows Installer
database. In order for the items to work properly, you must individually
re-install all items selected. Select OK to continue removing product,
Cancel to abort.
If you click 'OK,' all the Windows Installer information that is associated with the selected programs is removed. This includes the entries for the programs in the Add/Remove Programs tool in Control Panel. If you remove the installation information for an installed program, the program is prevented from being able to add or remove components or to repair itself. NOTE: If you remove the installation information, files or shortcuts for the programs themselves are not removed. You should reinstall the programs before you try to use them.
WHAT IF I RECEIVE AN ERROR MESSAGE?
The following table lists the Windows Installer Clean Up Utility error messages that you may receive and the cause for each message.
Error message:
This utility requires that Msizap.exe version 2 or greater reside in the same folder.
Cause:
Msizap.exe version 2 or a later version of Msizap.exe cannot be found in the same folder as Msicuu.exe.
---------------------------------------------------------------------------
Error message:
You must have Administrator rights to run this utility.
Cause:
To run Msicuu.exe, you must be logged on with administrator rights.
---------------------------------------------------------------------------
Error message:
This utility requires that the Windows Installer be installed and properly registered.
Cause:
Msicuu.exe uses the Windows Installer object model to identify the installed products.
To correct the problem, try reregistering Msi.dll.
HOW DO I REMOVE THE WINDOWS INSTALLER CLEAN UP UTILITY?
When the Windows Installer Clean Up Utility is installed, an entry for the utility is created in the Add/Remove Programs tool in Control Panel. To remove the Windows Installer Clean Up Utility, click the entry in the list of installed programs, and then click 'Remove.'
Thursday, February 7, 2008
Windows Vista - Intermittent mouse/cursor misalignment
Symptom 1: sometime when hovering the mouse cursor over a box that I wanted to click and nothing would happen. Not only would it not "click," the box wouldn't even highlight. then I had to place the arrowhead (sometimes) about 1/4 inch higher than the spot I wanted to click. Then, for no apparent reason, the arrowhead's mathematical position would become synched with it's visual position and it would come back into alignment with the check boxes and dialog boxes and such.
Symptom 2: when resizing a windows, I move the mouse cursor to the border, at this moment, the mouse cursor consistantly jumping the position back and forth. after using vista for 1 week I am able to resize the windows size anyway but it still give me a lot of trouble.
Solution: download the lastest driver from amd.com web site for the Raedon ATI 2400 video card, after install the new driver (system shows driver date 12/20/07, version 8.451.0.0, ALL WORKS.
Symptom 2: when resizing a windows, I move the mouse cursor to the border, at this moment, the mouse cursor consistantly jumping the position back and forth. after using vista for 1 week I am able to resize the windows size anyway but it still give me a lot of trouble.
Solution: download the lastest driver from amd.com web site for the Raedon ATI 2400 video card, after install the new driver (system shows driver date 12/20/07, version 8.451.0.0, ALL WORKS.
Saturday, February 2, 2008
Installing SQL Server 2005 on Vista
Here is the on the internet on how to install SQL Server 2005 on Vista, following by my notes:
I sent this to our local user group when I installed Vista Ultimate on my new laptop a few months ago. Yesterday, I did a quick search to see if this information was readily available and found that it still was not (at least not in one place), so I decided to post it here. I hope it helps!
· You must install SQL Server 2005 SP2. I was able to successfully install RTM, then followed by SP2, but an attendee at our last user group meeting had no such luck. One of our local Microsofties mentioned there is an SQL install that combines the core install of SQL with SP2.
· OWC 11 component install fails. This has a domino effect on the installation of most of the other SQL components. You know, the important ones, like database services, SSIS, SSAS and SSRS. The newsgroup solution was to uninstall OWC 11 through Add/Remove Programs. This solution worked for me, as well.
· IIS is required for Reporting Services. Nothing new here, but the configuration of IIS was not as simple as I recall it on XP. Be sure the following options are selected (Start --> Control Panel --> Programs and Features --> Turn Windows features on or off):
o Web management tools
§ IIS 6 Management Compatibility
· IIS 6 WMI Compatibility
· IIS Metabase and IIS 6 configuration compatibility
o World Wide Web Services
§ Application Development Features
· ASP.NET
· ISAPI Extensions
· ISAPI Filters
§ Common Http Features
· Default Document
· Directory Browsing
· HTTP Redirection
· Static Content
§ Security
· Windows Authentication
· You must install Visual Studio SP1, then another patch for Vista. I initially tried installing the patch for Vista first but it wanted SP1. I was unable to run BIDS until I installed these. Here are the download files (available for download at Microsoft.com):
o VS80sp1-KB926601-X86-ENU (VS SP1)
o VS80sp1-KB932232-X86-ENU (patch for Vista)
There was mention of having to turn off UAC at one of our user group meetings. I did not have this issue. During the install, I was asked if I wanted to be added to the sysadmin role during the SQL SP2 setup, because Builtin\Administrators is not automatically added to sysadmin like it used to be.
Notes:
I sent this to our local user group when I installed Vista Ultimate on my new laptop a few months ago. Yesterday, I did a quick search to see if this information was readily available and found that it still was not (at least not in one place), so I decided to post it here. I hope it helps!
· You must install SQL Server 2005 SP2. I was able to successfully install RTM, then followed by SP2, but an attendee at our last user group meeting had no such luck. One of our local Microsofties mentioned there is an SQL install that combines the core install of SQL with SP2.
· OWC 11 component install fails. This has a domino effect on the installation of most of the other SQL components. You know, the important ones, like database services, SSIS, SSAS and SSRS. The newsgroup solution was to uninstall OWC 11 through Add/Remove Programs. This solution worked for me, as well.
· IIS is required for Reporting Services. Nothing new here, but the configuration of IIS was not as simple as I recall it on XP. Be sure the following options are selected (Start --> Control Panel --> Programs and Features --> Turn Windows features on or off):
o Web management tools
§ IIS 6 Management Compatibility
· IIS 6 WMI Compatibility
· IIS Metabase and IIS 6 configuration compatibility
o World Wide Web Services
§ Application Development Features
· ASP.NET
· ISAPI Extensions
· ISAPI Filters
§ Common Http Features
· Default Document
· Directory Browsing
· HTTP Redirection
· Static Content
§ Security
· Windows Authentication
· You must install Visual Studio SP1, then another patch for Vista. I initially tried installing the patch for Vista first but it wanted SP1. I was unable to run BIDS until I installed these. Here are the download files (available for download at Microsoft.com):
o VS80sp1-KB926601-X86-ENU (VS SP1)
o VS80sp1-KB932232-X86-ENU (patch for Vista)
There was mention of having to turn off UAC at one of our user group meetings. I did not have this issue. During the install, I was asked if I wanted to be added to the sysadmin role during the SQL SP2 setup, because Builtin\Administrators is not automatically added to sysadmin like it used to be.
Notes:
- Might need to download newer version of SQL Server 2005
- Refer to previous post on how to uninstall SQL Server 2005 on vista machine
How to uninstall an instance of SQL Server 2005 manually
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry
On This Page
INTRODUCTION
MORE INFORMATION
Before you uninstall SQL Server 2005
Back up the data
Delete the local security groups
Save or rename the SQL Server Reporting Services folders
Stop all SQL Server services
Use an account that has the required rights
How to uninstall a stand-alone instance of SQL Server 2005 manually
Step 1: Make sure that the Microsoft SQL Server Setup Support Files component is installed
Step 2: Run the command to uninstall the SQL Server components
Delete the Reporting Services virtual directories
Delete the ReportServer application pool
If you experience problems
Step 3: Uninstall the support components
Step 4: Uninstall the Microsoft SQL Server Native Client component
Step 5: Uninstall the Microsoft SQL Server Setup Support Files component
If these steps did not uninstall all the components
INTRODUCTION
This article describes how to uninstall a stand-alone instance of Microsoft SQL Server 2005 manually. If you follow the steps in this article, you prepare the system so that you can reinstall SQL Server.For more information about how to uninstall a SQL Server 2005 failover cluster manually, see the "How to manually uninstall a SQL Server 2005 failover cluster" topic in SQL Server 2005 Books Online, or visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms180973(SQL.90).aspx
For more information about how to uninstall an instance of SQL Server 2000 manually, click the following article number to view the article in the Microsoft Knowledge Base:
290991 How to manually remove SQL Server 2000 default, named, or virtual instance
Important On a computer that is running SQL Server 2005 together with earlier versions of SQL Server, SQL Server Enterprise Manager and other programs that depend on SQL-DMO may be disabled when you uninstall the instance of SQL Server 2005.
This issue may occur when you have side-by-side installations of SQL Server 2005, SQL Server 2000, and SQL Server 7.0 and when you uninstall any one of the versions. This issue may also occur when you have side-by-side installations of SQL Server 2000 and SQL Server 2005 and when you installed SQL Server 2000 after you installed SQL Server 2005.
This issue occurs because the registration for the SQL Server 2005 SQL-DMO COM library was deleted. To re-enable SQL Server Enterprise Manager and other programs that depend on SQL-DMO, register SQL-DMO. To do this, run the following command at a command prompt:
regsvr32.exe sqldmo.dll
MORE INFORMATION
We recommend that you use Add or Remove Programs to uninstall SQL Server 2005. However, if an installation fails or if Add or Remove Programs does not uninstall the instance of SQL Server 2005, follow the steps in this article to uninstall the instance manually.
If you receive the following error message during the SQL Server 2005 Setup process, a SQL Server 2005 component was not uninstalled from the computer:
A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.
Before you uninstall SQL Server 2005
Back up the data
You may have databases that you want to save in the present state. You may also want to save changes that were made to the default databases. If either case is true, make sure that you have a good backup of the data before you follow the steps in this article. Alternatively, save a copy of all the data and of all the log files. Save these copies in a folder other than the MSSQL folder. The MSSQL folder is deleted as part of the uninstallation process.The files that you must save include the following database files.
These files are installed as part of SQL Server 2005:
• Distmdl.*
• Master.*
• Mastlog.*
• Model.*
• Modellog.*
• Msdbdata.*
• Msdblog.*
• Mssqlsystemresource.*
• Northwnd.* (This database is an optional installation.)
• Pubs.*
• Pubs_log.*
• Tempdb.*
• Templog.*
• ReportServer[$InstanceName] (This is the Report Server default database.)
• ReportServer[$InstanceName]TempDB (This is the Report Server default temporary database.)
Delete the local security groups
As part of the uninstallation process, delete the local security groups for the SQL Server 2005 components. For more information, see the "Setting up Windows service accounts" topic in SQL Server 2005 Books Online, or visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms143504.aspx
Save or rename the SQL Server Reporting Services folders
If you use the SQL Server installation together with SQL Server Reporting Services, save or rename the following folders and subfolders:
• Default path\Reporting Services
• Default path\MSSQL\Reporting Services
• Default path\SQL Server instance name\Reporting Services
• Default path\90\Tools\Reporting Services
Note Default path is a placeholder for %ProgramFiles%\Microsoft SQL Server. If you used the Reporting Services Configuration tool to configure the installation, the names may differ from the names in this list. Additionally, the databases may be located on a remote computer that is running SQL Server.
Stop all SQL Server services
We recommend that you stop all SQL Server services before you uninstall the SQL Server 2005 components. Active connections may prevent the uninstallation process from finishing successfully.
Use an account that has the required rights
Log on to the server by using the SQL Server 2005 service account or by using an account that has equivalent rights. For example, log on to the server by using an account that is a member of the local Administrators group.
How to uninstall a stand-alone instance of SQL Server 2005 manually
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Step 1: Make sure that the Microsoft SQL Server Setup Support Files component is installed
In Add or Remove Programs, make sure that Microsoft SQL Server Setup Support Files appears in the list of installed programs. If Microsoft SQL Server Setup Support Files appears in the list, go to the "Step 2: Run the command to uninstall the SQL Server components" section.
If Microsoft SQL Server Setup Support Files does not appear in the list, install this component before you continue. To install this component, follow these steps:
1. Locate the original SQL Server 2005 installation media.
2. To install the support files, double-click the Servers\setup\sqlsupport.msi file.
Note In the "Step 5: Uninstall the Microsoft SQL Server Setup Support Files component" section, you uninstall this component.
Step 2: Run the command to uninstall the SQL Server components
At a command prompt, run the following command:
"%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /Remove"
Uninstall the SQL Server components one at a time until all the SQL Server components are uninstalled.
Note Add or Remove Programs also runs the ARPWrapper.exe program by using the /Remove option. However, the reference to the ARPWrapper.exe program may have been deleted.
The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams.
256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry
On This Page
INTRODUCTION
MORE INFORMATION
Before you uninstall SQL Server 2005
Back up the data
Delete the local security groups
Save or rename the SQL Server Reporting Services folders
Stop all SQL Server services
Use an account that has the required rights
How to uninstall a stand-alone instance of SQL Server 2005 manually
Step 1: Make sure that the Microsoft SQL Server Setup Support Files component is installed
Step 2: Run the command to uninstall the SQL Server components
Delete the Reporting Services virtual directories
Delete the ReportServer application pool
If you experience problems
Step 3: Uninstall the support components
Step 4: Uninstall the Microsoft SQL Server Native Client component
Step 5: Uninstall the Microsoft SQL Server Setup Support Files component
If these steps did not uninstall all the components
INTRODUCTION
This article describes how to uninstall a stand-alone instance of Microsoft SQL Server 2005 manually. If you follow the steps in this article, you prepare the system so that you can reinstall SQL Server.For more information about how to uninstall a SQL Server 2005 failover cluster manually, see the "How to manually uninstall a SQL Server 2005 failover cluster" topic in SQL Server 2005 Books Online, or visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms180973(SQL.90).aspx
For more information about how to uninstall an instance of SQL Server 2000 manually, click the following article number to view the article in the Microsoft Knowledge Base:
290991 How to manually remove SQL Server 2000 default, named, or virtual instance
Important On a computer that is running SQL Server 2005 together with earlier versions of SQL Server, SQL Server Enterprise Manager and other programs that depend on SQL-DMO may be disabled when you uninstall the instance of SQL Server 2005.
This issue may occur when you have side-by-side installations of SQL Server 2005, SQL Server 2000, and SQL Server 7.0 and when you uninstall any one of the versions. This issue may also occur when you have side-by-side installations of SQL Server 2000 and SQL Server 2005 and when you installed SQL Server 2000 after you installed SQL Server 2005.
This issue occurs because the registration for the SQL Server 2005 SQL-DMO COM library was deleted. To re-enable SQL Server Enterprise Manager and other programs that depend on SQL-DMO, register SQL-DMO. To do this, run the following command at a command prompt:
regsvr32.exe sqldmo.dll
MORE INFORMATION
We recommend that you use Add or Remove Programs to uninstall SQL Server 2005. However, if an installation fails or if Add or Remove Programs does not uninstall the instance of SQL Server 2005, follow the steps in this article to uninstall the instance manually.
If you receive the following error message during the SQL Server 2005 Setup process, a SQL Server 2005 component was not uninstalled from the computer:
A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.
Before you uninstall SQL Server 2005
Back up the data
You may have databases that you want to save in the present state. You may also want to save changes that were made to the default databases. If either case is true, make sure that you have a good backup of the data before you follow the steps in this article. Alternatively, save a copy of all the data and of all the log files. Save these copies in a folder other than the MSSQL folder. The MSSQL folder is deleted as part of the uninstallation process.The files that you must save include the following database files.
These files are installed as part of SQL Server 2005:
• Distmdl.*
• Master.*
• Mastlog.*
• Model.*
• Modellog.*
• Msdbdata.*
• Msdblog.*
• Mssqlsystemresource.*
• Northwnd.* (This database is an optional installation.)
• Pubs.*
• Pubs_log.*
• Tempdb.*
• Templog.*
• ReportServer[$InstanceName] (This is the Report Server default database.)
• ReportServer[$InstanceName]TempDB (This is the Report Server default temporary database.)
Delete the local security groups
As part of the uninstallation process, delete the local security groups for the SQL Server 2005 components. For more information, see the "Setting up Windows service accounts" topic in SQL Server 2005 Books Online, or visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms143504.aspx
Save or rename the SQL Server Reporting Services folders
If you use the SQL Server installation together with SQL Server Reporting Services, save or rename the following folders and subfolders:
• Default path\Reporting Services
• Default path\MSSQL\Reporting Services
• Default path\SQL Server instance name\Reporting Services
• Default path\90\Tools\Reporting Services
Note Default path is a placeholder for %ProgramFiles%\Microsoft SQL Server. If you used the Reporting Services Configuration tool to configure the installation, the names may differ from the names in this list. Additionally, the databases may be located on a remote computer that is running SQL Server.
Stop all SQL Server services
We recommend that you stop all SQL Server services before you uninstall the SQL Server 2005 components. Active connections may prevent the uninstallation process from finishing successfully.
Use an account that has the required rights
Log on to the server by using the SQL Server 2005 service account or by using an account that has equivalent rights. For example, log on to the server by using an account that is a member of the local Administrators group.
How to uninstall a stand-alone instance of SQL Server 2005 manually
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Step 1: Make sure that the Microsoft SQL Server Setup Support Files component is installed
In Add or Remove Programs, make sure that Microsoft SQL Server Setup Support Files appears in the list of installed programs. If Microsoft SQL Server Setup Support Files appears in the list, go to the "Step 2: Run the command to uninstall the SQL Server components" section.
If Microsoft SQL Server Setup Support Files does not appear in the list, install this component before you continue. To install this component, follow these steps:
1. Locate the original SQL Server 2005 installation media.
2. To install the support files, double-click the Servers\setup\sqlsupport.msi file.
Note In the "Step 5: Uninstall the Microsoft SQL Server Setup Support Files component" section, you uninstall this component.
Step 2: Run the command to uninstall the SQL Server components
At a command prompt, run the following command:
"%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /Remove"
Uninstall the SQL Server components one at a time until all the SQL Server components are uninstalled.
Note Add or Remove Programs also runs the ARPWrapper.exe program by using the /Remove option. However, the reference to the ARPWrapper.exe program may have been deleted.
If you have uninstalled SQL Server Reporting Services, you must perform the following tasks:
• Delete the Reporting Services virtual directories
Use Microsoft Internet Information Services (IIS) Manager to delete the following virtual directories:
• ReportServer[$InstanceName
• Reports[$InstanceName
• Delete the ReportServer application pool
• Delete the Reporting Services virtual directories
Use Microsoft Internet Information Services (IIS) Manager to delete the following virtual directories:
• ReportServer[$InstanceName
• Reports[$InstanceName
• Delete the ReportServer application pool
Use IIS Manager to delete the ReportServer application pool.
If you receive the following error message, go to the "If you experience problems" section to uninstall the SQL Server redistributed files and the SQL Server support files:
Registry Enumeration Failed
You may have an instance that has more than one server. For example, you may have an instance that has SQL Server 2005 Database Engine, SQL Server 2005 Analysis Services, and SQL Server 2005 Reporting Services. If you have an instance that has more than one server, the Setup program fails, and you receive the following error message:
The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams.
This error is expected because of refcounting. A refcount is used to track how many programs use the same .dll file or the same .msi file. When a program is uninstalled, the program decrements the refcount for an .msi file by one. When the last program is uninstalled, the .msi file is deleted. In this case, the .msi file is the Microsoft SQL Server Setup Support Files component (SqlSupport.msi). If you receive this error message, use one of the following methods to resolve this error:
• Reinstall the Microsoft SQL Server Setup Support Files component (SqlSupport.msi) before you uninstall each component in the instance.
• Temporarily refcount the SqlSupport.msi file to itself. To do this, follow these steps:
1.Obtain the GUID for the Microsoft SQL Server Setup Support Files component. To obtain the GUID, follow steps 1 and 2 from the "If you experience problems" section.
2. Use Registry Editor to create or to modify the following registry key with these values:
• Temporarily refcount the SqlSupport.msi file to itself. To do this, follow these steps:
1.Obtain the GUID for the Microsoft SQL Server Setup Support Files component. To obtain the GUID, follow steps 1 and 2 from the "If you experience problems" section.
2. Use Registry Editor to create or to modify the following registry key with these values:
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
Value: Uninstall
Type: REG_SZ
Data: {11111111-1111-1111-1111-111111111111},{GUID}
Note GUID is a placeholder for the GUID of the SQL Server support files. For example, the GUID of the English x86 SQL Server support files is as follows:
Data: {11111111-1111-1111-1111-111111111111},{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
Data: {11111111-1111-1111-1111-111111111111},{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
If you experience problems
If you experience problems when you try to uninstall the SQL Server components, follow these steps:
1. Start Registry Editor, and then locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
2. In the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that includes "Microsoft SQL Server 2005." For example, look for the following names:
• Microsoft SQL Server 2005
• Microsoft SQL Server 2005 Analysis Services
• Microsoft SQL Server 2005 Reporting Services
• Microsoft SQL Server 2005 Notification Services
• Microsoft SQL Server 2005 Integration Services
• Microsoft SQL Server 2005 Tools
• Microsoft SQL Server 2005 Books OnlineWhen you see a display name that includes "Microsoft SQL Server 2005," note the GUID that you clicked in the left pane.
3. For each GUID that you noted in step 2, run the following command at a command prompt:
If you experience problems when you try to uninstall the SQL Server components, follow these steps:
1. Start Registry Editor, and then locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
2. In the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that includes "Microsoft SQL Server 2005." For example, look for the following names:
• Microsoft SQL Server 2005
• Microsoft SQL Server 2005 Analysis Services
• Microsoft SQL Server 2005 Reporting Services
• Microsoft SQL Server 2005 Notification Services
• Microsoft SQL Server 2005 Integration Services
• Microsoft SQL Server 2005 Tools
• Microsoft SQL Server 2005 Books OnlineWhen you see a display name that includes "Microsoft SQL Server 2005," note the GUID that you clicked in the left pane.
3. For each GUID that you noted in step 2, run the following command at a command prompt:
start /wait msiexec /x {GUID} /l*v c:\sql_uninstall.log
Notes
• In this command, replace GUID with the GUID that you noted in step 2.
• If you receive the following error message, contact Microsoft Customer Support Services:
• In this command, replace GUID with the GUID that you noted in step 2.
• If you receive the following error message, contact Microsoft Customer Support Services:
The setup has encountered an unexpected error in datastore.
For a complete list of Microsoft Product Support Services telephone numbers and for information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
http://support.microsoft.com/contactus/?ws=support
4. Open the following file:
C:\Sql_uninstall.log
C:\Sql_uninstall.log
Approximately 15 lines from the bottom of the file, locate a line that resembles the following line: MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Tools -- Removal completed successfully.
If the uninstallation process was not successful, note the component name and the GUID, and then save the Sql_uninstall.log file.
Step 3: Uninstall the support components
Use Add or Remove Programs to uninstall the support components in the following order:
• MSXML 6.0 Parser
• SQLXML4
• Microsoft SQL Server VSS Writer
• Microsoft SQL Server 2005 Backward Compatibility
• Anything else that is related to SQL Server 2005, except for the Microsoft SQL Server Native Client component and for the Microsoft SQL Server Setup Support Files component
Use Add or Remove Programs to uninstall the support components in the following order:
• MSXML 6.0 Parser
• SQLXML4
• Microsoft SQL Server VSS Writer
• Microsoft SQL Server 2005 Backward Compatibility
• Anything else that is related to SQL Server 2005, except for the Microsoft SQL Server Native Client component and for the Microsoft SQL Server Setup Support Files component
If the uninstallation process fails for any one of the support components, you may receive the following error message:
Setup failed due to missing prerequisites
If you receive this error message, follow these steps:
1. Start Registry Editor, and then locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
2. In the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches the name of the redistributable file. When you see a display name that matches the name of the redistributable file, note the GUID that you clicked in the left pane.
3. For each GUID that you noted in step 2, run the following command at a command prompt:
1. Start Registry Editor, and then locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
2. In the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches the name of the redistributable file. When you see a display name that matches the name of the redistributable file, note the GUID that you clicked in the left pane.
3. For each GUID that you noted in step 2, run the following command at a command prompt:
start /wait msiexec /x {GUID} SKIPREDISTPREREQS=1 /l*v c:\sqlredist_uninstall.log
Note In this command, replace GUID with the GUID that you noted in step 2.
4. Open the following file:
C:\Sqlredist_uninstall.log
4. Open the following file:
C:\Sqlredist_uninstall.log
At the bottom of the file, locate a line that resembles the following line:
MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Backward compatibility -- Removal completed successfully.
If the uninstallation process was not successful, note the component name and the GUID, and then save the Sqlredist_uninstall.log file.
Step 4: Uninstall the Microsoft SQL Server Native Client component
If all the other steps were successful, uninstall the Microsoft SQL Server Native Client component by using Add or Remove Programs.
Note Do not uninstall the Microsoft SQL Server Native Client component if you have SQL Server 2000 components installed.
Step 5: Uninstall the Microsoft SQL Server Setup Support Files component
If all the other steps were successful, uninstall the Microsoft SQL Server Setup Support Files component by using Add or Remove Programs.
If these steps did not uninstall all the components
If the previous steps did not uninstall all the components, follow these steps:
1. Perform Step 1 in the "How to uninstall a stand-alone instance of SQL Server 2005 manually" section.
2. In Add or Remove Programs, uninstall all SQL Server 2005 components in the following order:
• SQL Server 2005
• SQL Server 2005 Analysis Services
• SQL Server 2005 Reporting Services
• SQL Server 2005 Notification Services
• SQL Server 2005 Integration Services
• SQL Server 2005 Tools
• SQL Server 2005 Books Online
• MSXML 6.0 Parser
• SQLXML4
• SQL Server VSS Writer
• SQL Server 2005 Backward Compatibility
• Anything else that is related to SQL Server 2005
• SQL Server Native Client
• SQL Server setup support files
3. Download and then install the Windows Installer CleanUp Utility. For more information about this utility, click the following article number to view the article in the Microsoft Knowledge Base:
290301 Description of the Windows Installer CleanUp Utility
4. Start the Windows Installer CleanUp Utility.
5. If any of the components in step 2 are listed, follow these steps:
a. Select the components, and then click Remove. You can use the CTRL key to select multiple components.
b. When you receive the following warning message, click OK:
All products selected will be removed from the Windows Installer database. In order for the products to work properly, you must individually re-install all products selected.Note Before you click OK, verify that the components that you selected are correct. These components will be permanently removed after you click OK.
c. In Add or Remove Programs, uninstall the Windows Installer Cleanup Utility.
1. Perform Step 1 in the "How to uninstall a stand-alone instance of SQL Server 2005 manually" section.
2. In Add or Remove Programs, uninstall all SQL Server 2005 components in the following order:
• SQL Server 2005
• SQL Server 2005 Analysis Services
• SQL Server 2005 Reporting Services
• SQL Server 2005 Notification Services
• SQL Server 2005 Integration Services
• SQL Server 2005 Tools
• SQL Server 2005 Books Online
• MSXML 6.0 Parser
• SQLXML4
• SQL Server VSS Writer
• SQL Server 2005 Backward Compatibility
• Anything else that is related to SQL Server 2005
• SQL Server Native Client
• SQL Server setup support files
3. Download and then install the Windows Installer CleanUp Utility. For more information about this utility, click the following article number to view the article in the Microsoft Knowledge Base:
290301 Description of the Windows Installer CleanUp Utility
4. Start the Windows Installer CleanUp Utility.
5. If any of the components in step 2 are listed, follow these steps:
a. Select the components, and then click Remove. You can use the CTRL key to select multiple components.
b. When you receive the following warning message, click OK:
All products selected will be removed from the Windows Installer database. In order for the products to work properly, you must individually re-install all products selected.Note Before you click OK, verify that the components that you selected are correct. These components will be permanently removed after you click OK.
c. In Add or Remove Programs, uninstall the Windows Installer Cleanup Utility.
If these steps did not uninstall all the components and all the files that are related to the instance of SQL Server 2005, contact Microsoft Customer Support Services.
Friday, February 1, 2008
Outlook 2000 on Vista
here is a post from Internet, it does help me to solve the problem
For all of you out there that hate Microsoft’s activation and want to run your copy of Office 2000, including Outlook, on you new Windows Vista machine or those that are upgrading a computer to Vista I have developed a step-by-step guide to getting Outlook 2000 working on Windows Vista. This is not perfect, so be sure to read the issues at the end. Let’s get started. Pull out your Office install disk (you’ll need it) and follow these steps:
For all of you out there that hate Microsoft’s activation and want to run your copy of Office 2000, including Outlook, on you new Windows Vista machine or those that are upgrading a computer to Vista I have developed a step-by-step guide to getting Outlook 2000 working on Windows Vista. This is not perfect, so be sure to read the issues at the end. Let’s get started. Pull out your Office install disk (you’ll need it) and follow these steps:
- Install Office 2000 normally on Windows Vista (if you are installing Office on a clean copy of Vista then skip to step #12).
- If you are upgrading a computer that already has Office installed you will need to reinstall Outlook.
- Insert your Office 2000 CD.
- Do not run setup from the pop up when inserting the CD.
- Go to the Control Panel and click the Uninstall a program link in the Programs section.
- Highlight Office and click on Change in the options above.
- Click the button by Add or Remove Features.
- Set Outlook to Not Available and click Update Now.
- Again, Highlight Office and click on Change.
- Click the Add or Remove Features button again.
- Now set Outlook to Run from My Computer and click Update now.
- Is everyone with us now. You have Outlook Installed or reinstalled and are ready to configure it.
- Run Outlook. If this is a clean install follow the wizard to setup your e-mail account. If you did the reinstall of Outlook you will probably have to manually setup your account.
- If you try to create an e-mail message and click the To: button you should get a WAB error.
- Shutdown Outlook.
- Run Windows Explorer.
- Navigate to C:\Program Files\Common Files\System.
- Copy wab32.dll and wab32res.dll to C:\Windows\System32.
- Start Outlook.
- This could be enough for most, but if you continue to be prompted that Outlook is not their default e-mail program you have a little further to go.
- Open Explorer and find your Outlook.exe (usually C:\Program Files\Microsoft Office\Office\Outlook.exe).
- Right click Outlook.exe and choose properties.
- Click the Compatibility Tab.
- Change the options to run in compatibility mode for Windows XP SP2, and check the box to Run this program as an administrator.
- Now click on Show settings for all users.
- Set the compatibility to Win XP SP2 and check Run this program as an administrator on this page too.
- Run Outlook again, and answer Yes if asked to make it the default e-mail program. You might want to exit and run Outlook again until it starts without asking.
- Exit Outlook.
- Go back to the properties for Outlook.exe and remove all the checks from both properties pages.
- Your finished! Congratulations!
Issue:
Just in case you thought you were finished, there are two problems, and they effect people differently depending on whether you upgrade a computer to Vista or you installed Office 2000 on a clean install of Vista.
The first problem has to do with your contacts. When you cop the WAB (Windows Address Book) files above you are getting Outlook to use the Windows Contacts… not the Outlook Contact. You will have to learn to live with this. When you click the To: button in an e-mail the Windows Contacts is listed, so it is easy to do your contact maintenance. But you cannot use the Contacts in Outlook.
The second problem with with clicking on e-mail links on web pages. If you install Office on a clean copy of Vista it will try to launch Windows Mail. I have not been able to change this behavior. However, if you upgraded your computer to Vista them you will get Outlook as the default e-mail provider for the MAILTO protocol.
That’s all I have for you. Please feel free to contact me (mailto:scott@satx.rr.com?subject=Outlook) and let me know if this helped you, or just post a comment. If anyone know how to get around the MAILTO protocol issue I would love for you to send me the steps to fix it. I will test it and add it to this page.
Enjoy!
Bought a new DELL computer
Bought a dell Inpiron 530 from dell.ca web site last week, get it 6 days later, here is the setting
Intel® Core™2 Processor Q6600 (2.40GHz,1066 FSB) w/Quad Core Technology and 8MB cacheGenuine
Windows Vista® Ultimate 32-bit Edition English
4GB DDR2 SDRAM at 667MHz
Dell Optical Mouse
Dell USB Keyboard
Integrated Audio
56K PCI Data Fax Modem
16X DVD+/-RW Drive
Dell Resource DVD with Application Backup
ATI Theater 650 PRO Combo TV Tuner with Remote Control
128MB Radeon ATI HD 2400 PRO
500GB Serial ATA Hard Drive (7200RPM)
22 inch SP2208WFP widescreen Flat Panel Monitor
1 Year Next Business Day Onsite/In Home Service and Tech Support Dell
AS501 10W Flat Panel Attached Spkrs for UltraSharp™ Flat Panels
Integrated 10/100 Ethernet
Cost: $1429 plus tax
Intel® Core™2 Processor Q6600 (2.40GHz,1066 FSB) w/Quad Core Technology and 8MB cacheGenuine
Windows Vista® Ultimate 32-bit Edition English
4GB DDR2 SDRAM at 667MHz
Dell Optical Mouse
Dell USB Keyboard
Integrated Audio
56K PCI Data Fax Modem
16X DVD+/-RW Drive
Dell Resource DVD with Application Backup
ATI Theater 650 PRO Combo TV Tuner with Remote Control
128MB Radeon ATI HD 2400 PRO
500GB Serial ATA Hard Drive (7200RPM)
22 inch SP2208WFP widescreen Flat Panel Monitor
1 Year Next Business Day Onsite/In Home Service and Tech Support Dell
AS501 10W Flat Panel Attached Spkrs for UltraSharp™ Flat Panels
Integrated 10/100 Ethernet
Cost: $1429 plus tax
Subscribe to:
Posts (Atom)