Archive

Archive for January, 2010

Error Installing Windows XP

January 16, 2010 Leave a comment

Description – When installing Windows XP you receive a BSOD that says, PCI.SYS address f9a380bf base at f9a31000, date stamp 3b7d8ssc”

Solution – Use a Windows XP installation disc that has at least SP2 slipstreamed.

Advertisements
Categories: Computers Tags: ,

Dictionary Error Sending Email

January 16, 2010 2 comments

Description – When sending an email in Outlook you receive a message that says, “No custom dictionary exists. Would you like to create one?” When you click Yes you receive an error that says, “An error occurred while creating the custom dictionary.”

Cause – The user’s custom dictionary setting in Word is incorrect.

Solution – Open Word. Click Tools>Options>Spelling & Grammar. Click Dictionaries. Click Add. Select CUSTOM.DIC & click OK. Click OK through all other windows. Now try to send the email again.

Note – The default path for the custom.dic file is C:\Documents and Settings\username\Application Data\Microsoft\Proof.

Categories: Computers Tags: , ,

Error Running an Executable

January 16, 2010 Leave a comment

Description – When running an executable you receive an error that says, “Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.”

Solution – Right click the file & select Properties. On the General tab towards the bottom by there is a security section that says, “This file came from another computer and might be blocked to help protect this computer”. Click Unblock. Now run the file again.

Categories: Computers Tags:

Error Installing Software on a Terminal Server

January 16, 2010 2 comments

Description – When installing software on a Terminal Server you receive an error that says, “Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator.” You receive this error even if you are a local administrator.

Solution 1 – Log in to the console or RDP to the Console/Admin session. Use “mstsc /console” on Windows Server 2003 or “mstsc /admin” on Windows Server 2008.

Solution 2 – Browse to HKLM\Software\Policies\Microsoft\Windows\Installer. Create a DWORD value called EnableAdminTSRemote & set it to 1

Categories: Computers Tags: ,
%d bloggers like this: