Information Blog

Showing posts with label fix. Show all posts

Tuesday, April 12, 2016

Fix the Problem Ejecting USB Mass Storage Device error

This must have happened to each of us many times that when we click the “Safely Remove Hardware” icon in the system tray to remove hardware, we get an error message saying “The device ‘Generic Volume’ cannot be stopped right now. Try stopping the device again later”.

One of the reason for this problem may be that the pen drive is still in use and some data is either being read from it or being written into it. That means some process is using the drive but we do not know what the processes are that are accessing the drive.

Steps to Fix the Problem Ejecting USB Mass Storage Device:
1. End the processes that are using the USB drive:
Download and install this software called as Unlocker, now open My Computer, right click on your USB drive icon, click on Unlocker.

Now click on Unlock All to kill all the processes using the Drive. Now the drive should get safely removed.

2. Clean the system infected by viruses:
If the first step fails that means the process that is accessing the pen drive is a virus for sure. So to clean the system just scan the computer with a good updated Anti Virus and delete the viruses that are found. The problem would certainly get solved.

Thursday, March 24, 2016

Fix Bugs in Windows Media Player using Fix WMP Utility

Windows Media Player is a default media player in windows and is used by most of the windows users. Its look and feel are good so even i prefer using WMP. But over a period of time, some bugs are created. A great utility is available to fix these bugs. "Fix WMP Utility v 1.0"

Its a free utility developed by The Windows Club. It re-registers all the concerned Windows Media dll files required for the smooth functioning of Windows Media Player.If you experience any problem or you get error messages while playing any audio or video in WMP you can run this utility to fix the issues. It re-registers over 40 dlls required for smooth functioning of Windows Media Player.

Please create a System Restore point before using this utility for safety. However this utility is tested and works fine in Windows Vista and Windows 7 and should work for

all versions of Windows and Windows Media Player.

Below are some screenshots of the software:

Download Fix WMP Utility v 1.0 here

Sunday, February 21, 2016

How to fix Raspberry Pi boot problems

If you have any problems with your SD card messing up or your Pi not booting, this is an attempt at documenting my issues with booting or SD card corruption and how I fixed them.

This can range from problems with rpi-update to changing the /boot/config.txt file to restoring the SD card superblocks from the superblock backup to Oh No my SD card is hosed and I need to recover files. Weve all been there so need to be embarrassed about messing something up. Things mess up a lot.

Boot Problems

First of all, this is a great reference that I use a lot.

Start by figuring out what changed.

Did you just change your /boot/config.txt?
Did you delete any important files?
Did you run rpi-update?
Did you add a new device?
Did you overclock too much?
Do you get a kbd prompt?
Did it run some weird commands on the shutdown about "device still open for writing"?

If you just changed your config.txt, you should change it back and then change line by line while rebooting until you see what option is causing the error.

If you deleted any files, restore them.

If you ran rpi-update and it wont reboot, try making your /boot/config.txt the default one. The cma_lwm and cma_hwm options sometimes cause the new firmware to break.
If that doesnt work or you have flashing light errors, restore the old boot files by copying the /boot.bak/ files into /boot/
sudo cp -ap /boot.bak/* /boot/

If you recently overclocked, try reducing it back down. I run 1100 MHz easily but 1200 MHz tends to be unstable for me.

If you get a kbd prompt or error, check your power supply to make sure its supplying enough voltage, then reduce any overclocking or overvolting in your config.txt, then (if the first two dont solve it) replace the boot files like described above.

If you have a kbd prompt that you couldnt fix, you get read/write or I/O errors on shutdown or startup, or

it cant find the ext4 partition, then you have been a victim of SD card corruption.
Dont worry though. There are still ways to recover your files.

The first thing you should do is make a copy of your SD card image.
Plug the card into another computer with linux and use dd to copy the image. Then you can try to fix the image file without further corrupting the data.
The first thing to try to do is replace your superblock with a backup. To do that click here.
If that doesnt work and all else fails, it is possible to use scalpel and custom recovery configuration to get your files. See here for how to do that.

Consider donating to further my tinkering