Showing posts with label boot. Show all posts
Showing posts with label boot. Show all posts

Tuesday, March 30, 2010

Clean Windows virus without booting into windows



At times, the Windows operating system may be severely affected by malware, spyware and virus to the extent that it is not possible to install an anti-virus, anti-malware or anti-spyware tool within the Windows operating system.

Nowadays, intelligent malware,spyware and virus are able to block out disinfectant tools and softwares that may be used to detect and eliminate the problems.

So how is it possible to clean up the operating system without booting into Windows?

2 known tools are available from renown anti-virus software companies.

1. Kaspersky Rescue Disk
2. F-Secure Rescue-CD

These are Live CDs which boots to a native environment that is independent of the operating system installed in the hard disk. And since they boot up using the files in the CD and not the hard-disk, malwares/spywares/virus in the hard-disk is unable to impair its operations.

Here are 2 very useful guides on how to use these CDs to remove the malwares, spywares and virus in your operating system.


An easier way to download the CD images and install directly onto a USB drive instead of using CDs would be to use "Unetbootin". Just select the desired image [ F-secure or Kaspersky ] from the dropdown list of distributions and choose the USB drive to use. The "Unetbootin" application will automatically download the latest version of the Live CDs and install it onto the USB drive in one step.

A quick guide to using "Unetbootin" can be found here at PendriveLinux.com.
Unetbootin is available on operating systems such as Windows and Linux.

Bookmark and Share

Friday, January 15, 2010

Speed up Windows Vista performance! Tips really work!



Vistax64 has a very good guide for speeding up Vista performance!

From boot up speed to application speed to managing services and registry optimization..

For all tech and non-tech users.

Choose which one to try.
Bookmark and Share

Wednesday, April 1, 2009

Testing your PC's RAM for defects the better way!



Very often, the computer's memory aka RAM might be the cause of the PC not responding or the infamous Windows BSOD.

It's not something easy to troubleshoot as it is not possible to know which byte within the PC's RAM is having some problems. And the way most OS handles memory for application and cache storage is not something that is physically shown on a map.

One way is to create an application that will try to write all 0's(zeros) to each byte and verify that it is zero by reading the same byte again and repeat again writing and verifying all the 1's. But with the operating system taking up so much memory in the first place after bootup, it may not be possible to do this accurately.

A good way is to use a linux distribution CD.
Most distribution CDs come with a memory checker before it fully loads up the Linux OS.
This is so that very little memory is used to ensure most, if not, all the bytes of the memory is tested.
An Ubuntu distribution CD is recommended here.

Set the bios so that you boot from the CD/DVD drive first.
This is usually set by pressing the "DEL" or the "F2" key when the PC is booting up.
Choose the boot order such that the PC will boot from the CD/DVD drive.

Once the Ubuntu CD boots up, you should be able to see this screen.


Select "Test Memory"

This will allow the Linux CD to test for any defects on your PC RAM hardware.

This method will be better than booting from your own OS [Windows XP/Vista/etc] because the current Windows OS on your hard disk may already have some files which are corrupted due to bad RAM. Faulty RAM causes erronous writes to files and if these files are Windows drivers required to manage the memory, then it'd be inaccurate to do any testing using the same OS.

Below are some guides to set your bios to boot from CD
http://www.hiren.info/pages/bios-boot-cdrom
http://www.lockergnome.com/windows/2005/12/21/configure-your-bios-to-boot-from-cd/
http://pcsupport.about.com/od/tipstricks/ht/bootcddvd.htm



Today is 1st April 2009
Time now is 13:14hrs

It is recommended to have a Linux Live CD installed into a USB thumbdrive and use it for testing purposes. A Linux Live CD is able to boot up into a Graphical User Interface [GUI] without affecting the original Windows OS installed on the same PC. Having a bootable USB is also a great way to be able to use someone else's PC safely and doesn't leave any traces on that PC. Moreover, USB stick is easier to carry around that a CD/DVD.

Howtogeek.com's guide to creating a USB bootable Linux Live CD from Windows
Bookmark and Share

Monday, March 9, 2009

POST Beep Codes



Usually if there is a hardware problem with the PC, it refuses to boot up normally. The common tell-tale signs would be the output screen stays blank.

But such tell-tale signs tell nothing but just an indicator of something is wrong inside the PC.
If your PC is able to power up but unable to show any display on the screen, do look out for another indicator which is audible instead of a visual indicator.

Most mainboard have a boot sequence even before it allows the harddisk to start booting the installed operating system. This boot sequence is controlled by something called the BIOS. The boot sequence itself is known as the POST [ Power On Self Test ].

So the BIOS will check for all installed hardware on the mainboard and ensure that critical components such as RAM,Video display and CPU are installed before going on to check other devices which are of lesser priority [ ie not absolutely necessary for PC to startup ].

Since the BIOS is able to detect the presence of critical and non-critical components, sensing that if there is any critical components missing, the boot sequence will be incomplete. Thus resulting in what most of us experience when the PC cannot boot up. Besides stopping the PC from booting up, the BIOS will also present a set of audible signals to the user. These audible signals come in the form of beeps generated by the internal PC speaker [ usually embedded in the PC casing ].

Though some newer PCs don't come with these internal PC speakers nowadays, most still do have this little speaker that does nothing but generate beeps. To find out if there is such a speaker in the PC, just listen for quick beep whenever a PC is turned on. If you can hear such a beep, it means the PC is equipped with such an internal speaker.

So, the BIOS upon detecting missing critical components it'll generate a sequence of beeps upon completing the POST. For each detected problem, it will generate the beeps in different sequence. The PC owner, knowing the issue faced, can then proceed to troubleshoot the PC in the specific hardware/region as the POST beeps codes has already narrowed down the possible causes to a fewer causes. This then help saves time for troubleshooting whereby the user have to test each and every hardware for problems.

Below is a set of standard beep codes and its detected errors.

If your mainboard is using AMI BIOS[ America Megatrends ]
  • 1 Beep - Memory Refresh Failure (check memory)
  • 2 Beeps - Memory Parity Error in first 64KB block (check memory)
  • 3 Beeps - Memory Read/Write Error in first 64KB block (check memory)
  • 4 Beeps - Motherboard timer not functioning (possible motherboard replacement)
  • 5 Beeps - Processor Error (may need replacement Processor)
  • 6 Beeps - Gate A20/keyboard controller failure (possible motherboard replacement)
  • 7 Beeps - Processor Exception Interrupt Error (may need replacement Processor)
  • 8 Beeps - Display Memory Read/Write Failure (reseat or replace video card)
  • 9 Beeps - ROM checksum Error (replace BIOS chip or motherboard)
  • 10 Beeps - CMOS shutdown Read/Write error (possible motherboard replacement)
  • 11 Beeps - Bad Cache Memory - test failed (replace cache memory)

If your mainboard is using Phoenix BIOS
eg. 1-1-4-1 means the beeping sequence will be *----*----****----*
  • 1-1-4-1 - Cache Error (level 2)
  • 1-2-2-3 - BIOS ROM Checksum
  • 1-3-1-1 - DRAM Refresh Test
  • 1-3-1-3 - Keyboard controller test
  • 1-3-4-1 - RAM Failure on address line xxxx (check memory)
  • 1-3-4-3 - RAM Failure on data bits xxxx of low byte of memory bus
  • 1-4-1-1 - RAM Failure on data bits xxxx of high byte of memory bus
  • 2-1-2-3 - ROM copyright notice
  • 2-2-3-1 - Test for unexpected interrupts
To know if your mainboard is AMI or Phoenix BIOS, it's usually shown on the display as the PC boots before it starts loading the OS.

For more reading, visit Wikipedia page on POST

Today is 9th March 2009
Time now is 08:56 hrs

Free Windows Vista/XP/2000/NT registry scan to optimize your system to top speed
Bookmark and Share

Live Traffic Map