My Sansa Clip+ has been freezing more than once. Luckily there a simple solution, see: http://kb.sandisk.com/app/answers/detail/a_id/188/~/resetting-a-sansa-player.
This service is added during the installation of Lexmark printers. However if you uninstall the Lexmark printerdriver, the Lexbce Server service remains active. You cannot just disable it, because the Print Spooler service depends on this service.
Here is one method (which worked for me) to remove the service:
1. Remove the dependency by running the following command:
sc config spooler depend= RPCSS
2. Remove the Lexbce Server serices:
Download and run SysInternals AutoRuns. Go to the “Services” tab and rightclick the “Lexmark Lexbce Server service”. Now click “Delete”.
Given the number of hits after Googling for this issue, apparently a lot of people have problems with HP LaserJet P2055 and LaserJet 2015 printers.
The problem: after some time these printers can lose their network connection, and it not possible to connect to the printer in any way. The only thing you can do is restart the printer. Afterwards it will work again … for some time 😦
This HP link describes this issue and a possible solution.
In case the link would disappear for some reason, here’s the content:
When a printer is connected to a network switch and it has not been used for a period of time, users may no longer be able to print. When in this condition, usually the printer also cannot be accessed through TELNET, FTP, or even through the Embedded Web Server. The printer even fails to respond to ping requests.This issue is caused by the network switch disabling the port to which the printer is connected because it believes that the printer is no longer connected, due to a lack of traffic on that port. Most managed enterprise switches automatically disable a port if no network traffic has been generated on that port for a period of time, and will remove the MAC address of the device on the port from the switch’s MAC table. This process is commonly referred to as Aging .SOLUTION:The following solutions can be utilized to address the issue depending on the customers environment and business needs.1. SLP Keep Alive – The Jetdirect can be configured to generate an SLP (Service Locater Protocol) multicast packet at specified intervals through a telnet session. At the telnet prompt, enter the command slp-keep-alive:x where x is the numeric value of the specified time interval (in minutes) which is less than the switchs aging value. For example, if the switchs aging value is 10 minutes, then an SLP Keep Alive value of 8 could be used. In this case the telnet command would be slp-keep-alive:8. A value of zero will disable the SLP Keep Alive option.2. Static MAC Table Entry – A static entry of the printers MAC address can be placed in the switchs MAC table for the port that the printer is connected to. A static entry will not be aged since aging only applies to dynamic entries that are created automatically when the switch senses a device on a port.I
I succesfully applied solution 1 using TELNET and fixed 2 P2055 printers like that. It was pretty simple:
slp-keep-alive:8 (depending of the number of minutes you would like to configure; I used 8 since I did not know the switches aging value and it worked for me)
(you can get help with “?” and see the current configuration using “/”)
Unfortunately the P2015 printers don’t support TELNET, so for this does not apply to these printers. I have not tested this, but I guess if you have P2015 printers, solution 2 will probably be the best way to fix the issue for P2015 printers.
A possible solution as suggested by HP support is to configure the printer directly on each workstation instead of configuring it on the print server. I don’t agree with HP that this is a good solution (you lose central administration, you have to install the driver on each PC, …), but it seems to work.
According to what I can find on the net this issue is often caused by formatter PCB problems, and replacing this can also solve the issue.
It’s relatively easy to find how to create a multiboot USB stick. On www.Pendrivelinux.com you can find a straight forward procedure to do this (http://www.pendrivelinux.com/boot-multiple-iso-from-usb-multiboot-usb/).
This is a very neat way to make a multiboot USB stick, because it’s pretty simple, and basically just involves formatting the USB stick, running the MultiBootISOs.exe file (which you can download using the link above). Then you’ll only have to follow the links to the Linux distros ISO files, download and copy them to the USB sticks’ root (with some exceptions, described on the site).
It would be fun adding some kind of Windows based image as well. I tried creating an UBCD4WIN (Ultimate Boot CD for Windows) ISO file and adding this to the menu. Unfortunately this did not work (UBCD4WIN did not start, and displayed some error message).
After some troubleshooting, Googling, … I decided to take another approach. This one is not as nice as just adding another ISO, but at least it works.
In brief this is how you can make it work:
– Create a bootable USB stick with UBCD4WIN (using UBUSB; see http://pctechtips.org/dual-booting-bartpe-and-backtrack3-from-usb-flash-drive/ for more details) and test if it boots normally (IMPORTANT: always create a UBCD4WIN from a Win XP PC – or virtual Win XP client system; for example using VirtualBox ! If you use Windows Vista or W7 you’ll end up with a stick which does not boot !)
– Delete (or rename) the Syslinux folder on the USB stick
– Make a backup of the menu.lst file (from the root of the USB stick)
– Run MultiBootISO.exe, WITHOUT formatting the USB stick
– Add the following section (source: menu.lst from the UBCD4WIN you backed up earlier) to the menu.lst on the USB stick (see below)
title “Ultimate Boot CD for Windows”
find –set-root /ntldr
That’s it: your multiboot combined Windows (UBC4Win) – Linux USB stick is ready !
Some more tips:
A cool way to test your bootable USB stick, without having to reboot your PC each time you want to test can be found here: http://www.pendrivelinux.com/boot-a-usb-flash-drive-in-virtualbox/#more-3606. This describes how you can boot your stick form VirtualBox.
On http://computer-forum.2960126.n2.nabble.com/USB-Multi-Boot-Drive-Grub4Dos-td3506580.html you can find even more stuff you can add to your USB boot stick.
With one of my old USB sticks (2GB Dane-Elec Z-Mate), something strange happened.
Each time when clicking on the “Safely Remove Hardware and Eject Media” (on Windows 7), it displayed “Eject Open … 4GB-Windows 7 …” (see below).
After searching on Google I found a solution:
In Windows Explorer go to C:\Users\USERNAME\AppData\Local\Microsoft\Device Metadata\dmrccache\en-US.
You should find the following folder there: \d42472c3-a173-455f-8fc5-640e344597b1\.
Delete this directory (folder) d42472c3-a173-455f-8fc5-640e344597b1 with the offending USB drive still attached to the computer.
Now use the “Safely Remove Hardware and Eject Media” and remove the offending USB Device.
Reinsert the offending USB Device and all it will be displayed normally.
Indeed, after doing the operation above, the USB stick would show up as below:
I just bought a SanDisk Cruzer 4GB U3, but did not need the U3 functionality. Click here to find how to remove the U3 Launchpad.
If you’d like to compare the shutter lag of some digital camera’s, here is a handy comparison table, with links to reviews of the camera’s as well (by Cameras.co.uk).