Tuesday, September 29, 2009

MOM.implementation or CCC.implementation Appear After Installing Catalyst Software Suite

This error message is caused by display drivers not being properly uninstalled or the latest driver version not being installed.

Symptoms:
MOM.implementation or CCC.implementation error message appears after installing Catalyst Software Suite

Resolution:

1.      Ensure the System BIOS is updated using the latest version.

2.      Uninstall the current display driver and Catalyst Control Center version from the System via Add/Remove Programs.

3.      Install the latest Catalyst Driver Suite.

Applicable Products:

Harware:
  • Desktop Radeon™ series

Operating Systems:

  • Windows Vista 32-bit Edition
  • Windows Vista 64-bit Edition
  • Windows XP Professional
  • Windows XP Home Edition
  • Windows XP Media Center Edition
  • Windows XP Professional x64 Edition

Communication failure or stop printing at certain percentage, print queue always stock

You've tried to uninstall and reinstall the printer driver of your printer. But still no luck. The printer still won't print. Or it would say printing but it won't finish printing.

You can try these steps:

1.Check if the firewall is blocking any printer services
 
2.Check what port the printer is using (reenable the bi-directional support) and if it's on online mode
 
3.Disable all the firewalls
 
4.Uninstall the printer driver and software
 
5.Delete any items under the ff keys:
 HKLM\System\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-2
 
 HKLM\System\CurrentControlSet\Control\Print\Environments\Windows NT  x86\Drivers\Version-3
 
 HKLM\System\CurrentControlSet001\Control\Print\Environments\Windows NT  x86\Drivers\Version-2
 
 HKLM\System\CurrentControlSet001\Control\Print\Environments\Windows NT  x86\Drivers\Version-3
 
Optional***
6.Delete any non default items under the ff keys:
Note: ONLY THE NON DEFAULT ITEMS SHOULD BE DELETED
 HKLM\System\CurrentControlSet\Control\Print\Monitors
 HKLM\System\CurrentControlSet001\Control\Print\Monitors
  Default items are as follows:
   AppleTalk Printing Devices
   BJ Language Monitor
   Local Port
   PJL Language Monitor
   Standard TCP/IP Port
   USB Monitor
   Windows NT FAx Monitor
*****
7.Delete any items under the ff keys:
 HKLM\System\CurrentControlSet\Control\Print\Printers
 
 HKLM\System\CurrentControlSet001\Control\Print\Printers
 
8.Completely remove drivers by doing the ff: (Option for comm failure because of the upgrade from xp to vista)
 Ensure there are no documents in queue.
 
 Disconnect printer’s USB cable.
 
 Click the Start pearl, then click All programs, Printers, Dell xxx (where  “xxx” is the printer model number) and then Uninstall.  Complete the  uninstall utility.
 
 From the start search box type spool and press .
 
 The spool folder located at c:\windows\system32\spool opens.
 
 Rename c:\windows\system32\spool\drivers\w32X86 to  c:\windows\system32\spool\drivers\backup.
 
 Rename c:\windows\system32\spool\prtprocs\W32X86 to   c:\windows\system32\spool\prtprocs\backup.
 
9.Restart the computer.
 
10.Check th services status
 
 Start-Run- Type Services.msc and Click on Open
 
 You will see long list of services
 
 You need to make sure following 4 Services are set to Automatically start
       
        Remote Procedure Call RPC
        Remote Procedure Call RPC Locater
        LexBce Server
        Print Spooler
 
11.Reinstall the latest printer driver

Errors in Printing using Internet Explorer 7

Problem Description

When printing using Internet Explorer 7, the error " Cannot find 'file://C:/TEMP/LOW/%filename%.htm' Make sure the path or Internet address is correct. " occurs.

Resolution

Execute in Command Console as Administrator: icacls C:\Users\Username\AppData\Local\Temp\Low /setintegritylevel (OI)(CI)low

Thursday, September 24, 2009

BSOD ISSUES AND SOLUTIONS

 

BSOD ISSUES AND SOLUTIONS

        - It all needs the Win XP OS CD and you have to be in Recovery Console. Listed are commands you have to type in after entering Recovery Console. Don't forget to hit ENTER every after command.


1) NTLDR is missing or corrupt

        Solution:

                1. ~Recovery Console

                2. cd \

                3. map (to know the drive name where XP CD is)

                4. copy d:\i386\ntldr (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

2. Continuous Restart

        Solution:

                1. ~Recovery Console

                2. cd \

                3. map (to know the drive name where XP CD is)

                4. copy d:\i386\ntdetect.com (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

3. Stop: C0000135 - kernel32.dll missing or corrupt

        Solution:

                1. ~Recovery Console

                2. cd system32

                3. map

                4. expand d:\i386\kernel32.dl_ (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

4. windows\system32\config missing or corrupt

        Solution:

                1. ~Recovery Console

                2. cd \

                3. dir (Look for System Volume Information. If it's there, proceed to Step 5, if not, continue with Step 4)

                4. attrib -h -s "system volume information" (this will unhide the System Volume Information.)

                5. cd "system volume information"

                6. cd _resto~1

                7. dir (Look for the RP numbers and what date it corresponds to for restoring it back to a working date, i.e.RP158 - 08/25/2006)

                8. cd RP# (i.e. RP158)

                9. cd snapshot

                10. dir (Look for the presence of entries like _registry_machine_software c:\windows\system32\config\system and others)

                11. copy _registry_machine_system c:\windows\system32\config\system

                12. exit

               

                ***Note: If you want to fully restore not only the system file, you can also do the SAM, SECURITY and SOFTWARE by typing:

                copy _registry_machine_sam c:\windows\system32\config\sam

                copy _registry_machine_security c:\windows\system32\config\security

                copy _registry_machine_software c:\windows\system32\config\software - (this can be useful if error has been caused by a software installed/changed)

5. hal.dll missing or corrupt

        Solution 1 (try first):

                1. ~Recovery Console

                2. bootcfg /rebuild

                3. Press y

                4. ms home /fastdetect (name the OS)

                5. exit

        Solution 2 (if first one doesn't work):

                1. ~Recovery Console

                2. cd system32 (to go to c:\windows\system32)

                3. map

                4. expand d:\i386\hal.dl_ (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

6. boot.ini / could not read from the selected boot disk / check boot path

        Solution is the same with the hal.dll error's Solution 1.

7. black screen after the Windows XP splash screen

        Solution:

                1. ~Recovery Console

                2. cd \

                3. dir (Look for System Volume Information. If it's there, proceed to Step 5, if not, continue with Step 4)

                4. attrib -h -s "system volume information" (this will unhide the System Volume Information.)

                5. cd "system volume information"

                6. cd _resto~1

                7. dir (Look for the RP numbers and what date it corresponds to for restoring it back to a working date, i.e.RP158 - 08/25/2006)

                8. cd RP# (i.e. RP158)

                9. cd snapshot

                10. dir (Look for the presence of entries like _registry_machine_software c:\windows\system32\config\software and others)

                11. copy _registry_machine_software c:\windows\system32\config\software

                12. exit

 

Tuesday, September 22, 2009

Your computer won't turn on, it's just giving you a beeping sound

One weekend morning, you woke up with a smile in your face ready to play your favorite game, since it's your day off or no school works to do. Then suddenly when you turn on your computer you hear a beeping sound.

 

You tried to check where the sound is coming from, then you found out that it’s from the inside of your computer. Don’t know what to do. You tried to phone the manufacturer of your computer, but it’s taking ages for them to answer.

 

You can try these simple steps:

 

Make sure that you remove your static first before handling any components of the computer. To remove your static, make sure that you’re in bare foot then hold any grounded object like your faucet. Hold it for about 3 minutes and you’re good to go.

 

1.       Try to remember if you installed new hardware or software to the system, if not, try to remember if you moved your computer from one place to another.

2.      Try to remove all the cables from the back of your system then try to plug the keyboard, mouse monitor and power cable.

3.      Try to turn on the computer. If still same, we need to open up the computer.

4.      If you don’t have the knowledge on how to open the tower of your computer, you can visit the support site of the manufacturer of your computer using a different computer to check for the manual.

5.      Make sure that when you open the tower of your computer all the cables from the back are unplugged.

6.      After opening the cover of the tower, look immediately to the memory modules of your computer. It looks like a 6” ruler that’s inserted in a black slot with either black or white clips at both ends.

7.      We’re going to reseat the connection of your memory module. To do that all you need to do is to push the clips outwards, then the memory modules will simply pop-out.

8.     After reseating the memory modules (if you have four, make sure you reseat all four). Connect the keyboard, mouse, monitor and power.

9.      Turn on the system and check if it will post up. If not.

10.  We will try each memory modules in each slots.

11.   If you isolate one memory module to be faulty. That memory module is causing the issue.

12.  If you isolate on slot that is causing the issue. Then it’s the motherboard that is causing the issue.

13.  But is none of the memory modules or the memory slot is causing the issue, try to remove all the memory module turn on the system, and check if the computer will make a beeping sound. If yes, then the mother board is still not detecting any memory modules.

14.  If you have an add-on video card, we need to reseat that as well.

15.   If all these steps won’t fix the issue, the first main cause of this issue would be the memory modules. Either you haven’t isolated which module is causing the issue or worst all of them are already busted but it’s a rare case. Another point of failure would be the motherboard.

You might be wondering why I asked you to immediately look for the memory modules and not the other components inside the computer.

 

The post process of the computer is:

 

A.     The computer checks for the processor if it’s okay.

B.     The computer checks for the memory if it’s okay. If not, it will create a beeping sound.

Wondering why it’s not creating a beeping sound for the processor? The computer will create a beeping sound as well for the processor. BUT it’s very rare for a processor to malfunction unless it was overclocked or not installed properly.

 

C.     The computer will check for video memory

D.    The computer will check for input devices

E.     The computer will check for bootable devices.

 

There you go, that’s why on the previous steps, I asked you to check the memory modules, then the video card.

 

There are several reasons why memory modules fail.

 

1.       Because of static electricity build up inside the computer.

2.      Age of the memory module

3.      Heat

 

 

And another thing, if you were able to isolate the root cause of the problem, make sure that you have the warranty card or the invoice of your computer so that you can have a replacement for that part.

 

 

Hope that these steps would help you.