Skip to main content

Brother DCP-110C Waste Ink Counter Reset

· One min read

Resetting the DCP-110C Printer Waste Ink Counter is easy, follow the instructions below:

  1. Press the Menu & Mono start keys next press the Up arrow key 4 times to make the machine enter the maintenance mode.
  2. Enter 8 & 0 by using the up arrow key & SET keys.
  3. Press the mono start key several times until the purge count appears on the LCD.
  4. Enter 2 7 8 & 3 by using the up arrow key & set keys to reset the purge count to zero
  5. Press the stop/exit key to return to the initial stage of the maintenance mode.
  6. Enter 9 twice by using the up arrow & set key’s to exit from maintenance mode
  7. Restart printer

Brother HL-140 Drum Light is on

· One min read

Trying to print with your HL-140 and the Drum light is on? Follow the instructions below.

Reset the Drum

  1. Press the cover release button and then open the front cover of the printer.
  2. Press & hold down the Go button until all 4 LEDs are lit. Once all 4 LEDs are lit, release the Go button.
  3. Close the front cover.
  4. Make sure that the Drum LED is now off.

Caution: Reset the drum counter only when you replaced the drum unit with a new one.

Brother HL-2040 Paper Light Blinking On/Off

· One min read

This problem usually occurs due to a Paper Jam in the printer or a faulty Drum unit in the printer. Follow any of the instructions below that matches your problems.

Printing

  1. In your word document/or document you are trying to print
  2. Go to File
  3. Page Setup
  4. Paper
  5. Make sure that your paper source is set to Tray 1 or what Tray the correct paper is in.

Reinstalling Toner

  1. Take off the front cover
  2. Pull the tabs on the side
  3. Pull out the big toner and cartridge
  4. Find the Blue tab
  5. Slide the tab from right to left
  6. Reinsert toner
  7. Close the toner door

 

If none of the above work, it is possible that your Drum unit is faulty and needs to be sent in to the manufacturer for repair.

 

c0000135 {Unable to Locate Component}

· One min read

The application has failed to start because CSRSRV.DLL was not found. Reinstalling the application may fix this problem.

First you need to access the recovery console. Following the instructions below

  1. Boot with your original Windows XP CD. You need one which will allow you to get into the Recovery Console.
  2. Once booted, choose to use the Recovery Console
  3. Choose which Windows installation you need to log into. if there’s only one on that machine, it will be “1?.
  4. Type in the Administrator password.
  5. You need to then copy a version of the file that isn’t corrupted, over the one that is. Type:** Copy d:i386csrsrv.dll c:windowssystem32csrsrv.dll**
  6. Restart the Computer

This command also may indicated Harddrive failure. Scan with a Hard Drive tool such as Spinrite or HDD Regenerator to make sure the drive is in good condition.

c000021a Fatal System Error

· 2 min read

“The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000026c”

Caused by a recently Windows Update

First you need to access the recovery console. Following the instructions below

  1. Boot with your original Windows XP CD. You need one which will allow you to get into the Recovery Console.
  2. Once booted, choose to use the Recovery Console
  3. Choose which Windows installation you need to log into. if there’s only one on that machine, it will be “1?.
  4. Type in the Administrator password.
  5. Change to the update folder by typing** cd WINDOWS$NtUninstallKB925902$spuninst**
  6. Run this command in the folder: batch spuninst.txt (If the command ran correctly, you should see a spuninst.tag file, using the “dir” command)
  7. Restart the Computer

At this point the computer should boot properly and you should install SP3 and other patches to prevent this problem from happening again.

If the spuninst.tag file doesn’t exist, you may have received a bunch of errors instead. There are a few reasons why this could happen, one of which is if your windows isn’t really installed on the c: drive, even if the Recovery Console always names it that way. To remove the patch manually type in these command in the Command Prompt (By going back using the Windows CD instructions above)

DEL “c:windows$hf_mig$kb925902mf3216.dll”

_ DEL “c:windows$hf_mig$kb925902gdi32.dll”_

_ DEL “c:windows$hf_mig$kb925902user32.dll”_

_ DEL “c:windows$hf_mig$kb925902win32k.sys”_

_ DEL “c:windowssystem32dllcachegdi32.dll”_

_ DEL “c:windowssystem32dllcachemf3216.dll”_

_ DEL “c:windowssystem32dllcacheuser32.dll”_

_ DEL “c:windowssystem32dllcachewin32k.sys”_

_ COPY “c:windows$NtUninstallKB925902$gdi32.dll” “c:windowssystem32gdi32.dll”_

_ COPY “c:windows$NtUninstallKB925902$mf3216.dll” “c:windowssystem32mf3216.dll”_

_ COPY “c:windows$NtUninstallKB925902$user32.dll” “c:windowssystem32user32.dll”_

_ COPY “c:windows$NtUninstallKB925902$win32k.sys” “c:windowssystem32win32k.sys”_

_ COPY “c:windows$NtUninstallKB925902$spuninstspuninst.txt” “c:windows$NtUninstallKB925902$spuninstspuninst.tag”_

Sources taken from TechForLunch