Uninstall Hotspot Shield Completely

Posted: Wednesday, 23 November 2011 by Unknown in Labels: , , , , ,
0


## Uninstall hotspot shield using revo uninstaller / advanced uninstaller pro.


## Create new  environment variable -


1. right click my computer --> properties --> advanced settings


2. click environment variables button --> click new button under system variables 


3. variable name = devmgr_show_nonpresent_devices, variable value = 1


4. click ok --> ok --> ok


## open device manager --> click view --> select show hidden devices


## right click on Hotspot Shield driver --> uninstall


## Uninstall hotspot shield miniport drivers -


1. right click on my network places/ go to network and sharing center (win7)


2. right click local area network  --> properties --> select hotspot shield miniport  --> uninstall


## Go to C:\Windows\System32\Driver --> delete "taphss.sys", "tapoas.sys"


## Go to C:\Windows\System32\DriverStore\FileRepository --> delete " nethss.inf_amd64_neutral_8028d194cee25616 "


To delete this -


1. take ownership of this folder and delete it.
2. restart in safe mode and try to delete it.
3. Boot pc with a live cd ( livexp, linux distros etc), navigate to the folder and delete it [ best way to delete ]

Enable/Disable File and Printer Sharing

Posted: Tuesday, 13 September 2011 by Unknown in Labels: , , , ,
0

Open Control Panel.

Click on Network And Internet --> Nework and Sharing Center.

Click on Change Adapter Settings on the left.

Right click on Local Area Network and Select Properties.

Now untick File and Printer Sharing for Microsoft Networks.

Click ok.

To enable it select File and Printer Sharing for Microsoft Networks  and click ok.

How To Fix Hal.dll Errors in Windows 7 and Windows Vista

Posted: Thursday, 21 July 2011 by Unknown in Labels: , , , , , ,
0

If you have Windows Vista or Windows 7 installed and you're seeing the hal.dll error, it most likely means that for whatever reason, your master boot record has been changed to the one only compatible with Windows XP... and it's looking for hal.dll.

Lucky, this problem is pretty easy to fix.

Resolution

1. Start System Recovery Options from the Windows Installation Disc.

2. Open Command Prompt from the System Recovery Options menu.

3. At the prompt, type the bootsect command as shown below and then press Enter:

bootsect /nt60 sys

The bootsect command as used above will overwrite the master boot record on the partition used to boot Windows to the one that's compatible with Windows Vista, Windows 7, and later Windows operating systems.

4. After running the bootsect command as shown in the last step, you should see a result that looks something like this:

C: (\\?\Volume{37a450c8-2331-11e0-9019-806e6f6e6963})

Successfully updated NTFS filesystem bootcode.

Bootcode was successfully updated on all targeted volumes.

Note: If you receive some kind of error, or this doesn't work after you try to start Windows normally again, try running "bootsect /nt60 all" instead. The only caveat here is that if you're running a dual-boot computer, you may inadvertently cause a similar, but opposite, problem with any older operating systems you boot to.

5. Close the Command Prompt window and then remove the Windows disc from your optical drive.

6. Click the Restart button from the System Recovery Options window.

7. Windows should start normally now.

8. If nothing works make a clean installation of windows.

Missing Or Corrupt Hal.dll Error Troubleshooting Windows XP

Posted: Wednesday, 20 July 2011 by Unknown in Labels: , , , , , ,
0

Hal.dll Error Message

There are few different ways that the "missing or corrupt hal.dll" error may present itself, with the first listing being the most common:

"Windows could not start because the following file is missing or corrupt:
\system32\hal.dll.
Please re-install a copy of the above file."

"\System32\Hal.dll missing or corrupt:
Please re-install a copy of the above file."

"Cannot find \Windows\System32\hal.dll"

"Cannot find hal.dll"

The "missing or corrupt hal.dll" error displays shortly after the computer is first started. Windows XP has not yet fully loaded when this error message appears.

Cause

Causes of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll DLL file or a hal.dll file that has been deleted or moved from its intended location.

Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged hard drive.

Hal.dll Error Troubleshooting

1. Restart the PC. The hal.dll error could be a fluke.

2. Check for proper boot order in BIOS. You might see the hal.dll error if the boot order in BIOS is first looking at a hard drive other than your main hard drive.

Note: If you've recently changed your boot order or recently flashed your BIOS, this may be what's causing your problem.

3. Run Windows XP System Restore from a command prompt. If this doesn't work or you're receiving the hal.dll error message before you're able to complete this process, move on to the next step.

4. Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP's boot.ini file and not the hal.dll file, which is often times the case.

Note: If repairing the boot.ini does correct the hal.dll issue but the problem reappears after a reboot and you've recently installed Internet Explorer 8 in Windows XP, uninstall IE8. In this specific situation, IE8 could be the root cause of your hal.dll problem.

5. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the hal.dll error.

6. Recover data from any bad sectors on your hard drive. If the physical part of your hard drive that stores any part of the hal.dll file has been damaged, you're likely to see errors like this.

7. Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.

8. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.

9. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch.

Note: While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

Important: If you can't gain access to your files to back them up, you should understand that you will lose them all if you continue with a clean installation of Windows XP.

10. Test the hard drive. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive but you'll want to test it to be sure.

If the drive fails any of your tests, replace the hard drive and then complete a "new" installation of Windows XP.

Invalid Page Fault in Module Kernel32.dll Error Resolution

Posted: by Unknown in Labels: , , , ,
0

Kernel32.dll Error Messages

There are a number of different ways that the "invalid page fault in module kernel32.dll" error may show up on your computer. Many different software programs may generate the kernel32.dll error in Windows but here are some of the more common specific error messages you may see:

"Explorer caused an invalid page fault in module Kernel32.DLL"

"Iexplore caused an invalid page fault in module Kernel32.DLL"

"Commgr32 caused an invalid page fault in module Kernel32.dll"

"Error in Kernel32.dll"

"[PROGRAM NAME] has caused an error in Kernel32.dll"

Kernel32.dll error messages may appear when Windows starts, when a program is opened, when a program is running, when a program is closed or at nearly any time during a session of Windows.

Cause of Kernel32.dll Errors

The causes of the kernel32.dll error message are as varied as the messages themselves. The kernel32.dll file is involved with memory management in Windows.

When Windows is started, kernel32.dll is loaded into a protected memory space so other programs don't attempt to use the same space in memory to run their operations.

The frequently accompanying "invalid page fault" error means that another program (or many programs) are trying to access this same space in your computer's memory.

Resolution

1. Restart your computer. The kernel32.dll error could be a fluke.

2. Reinstall the program if the "invalid page fault in module kernel32.dll" error occurs only when you use a single software program.

Chances are, the software program is most likely to blame so uninstalling and reinstalling the program may do the trick.

Be sure to install any service packs or other patches available for the program. One of these may have resolved the kernel32.dll problem that the software is causing. If necessary, you may need to stop using a particular program if it's the only cause of the problem.

3. Repair potentially damaged password list files. Try this troubleshooting step only if you're running Windows 95 or Windows 98 and if the kernel32.dll page fault is caused by "Explorer", "Commgr32", "Mprexe", "Msgsrv32", or "Iexplore".

4. Repair corrupted thumbs.db files. Often times, the "Explorer caused an invalid page fault in module Kernel32.DLL" error is caused by a corrupted thumbs.dll file in a folder of subfolder that you're trying to access.

5. Do you have DLL files saved to your desktop? If so, remove them. This can sometimes cause kernel32.dll errors.

6. Run a virus scan. Some specific computer viruses cause kernel32.dll errors as part of their damage to your computer. Quarantining the virus may resolve your issue entirely.

7. Update drivers for any hardware that might be related to the kernel32.dll error. For example, if a kernel32.dll error appears when printing to your printer, try updating the drivers for your printer.

If you suspect that drivers need updated but aren't sure where to start, update your video card drivers. Outdated video card drivers sometimes cause kernel32.dll errors.

8. Decrease the hardware acceleration on your video card. While uncommon, some computers do have problems when the hardware acceleration is set at it's default setting of full acceleration.

9. Have you overclocked your PC? If so, try resetting your hardware configuration to the default recommended by the manufacturer. Overclocking has been known to cause kernel32.dll issues.

10. Test your system memory for damage. Kernel32.dll error messages from random programs and activities in Windows could be a sign of a hardware failure with your computer's memory. One of these programs will clearly identify if you have a problem or give your memory a clean bill of health.

Replace the memory if it fails any of your tests.

11. Repair your Windows installation. If individual software reinstallations and hardware tests fail to resolve the problem, a repair installation of Windows should replace any damaged or missing files that may be causing kernel32.dll messages.

12. Perform a clean installation of Windows. This type of installation will completely remove Windows from your PC and install it again from scratch.

13. Finally, if all else has failed, including the clean installation from the last step, you're likely looking at a hardware issue with your hard drive or another piece of hardware.

If the hard drive is the likely culprit, replace the hard drive and then perform a new installation of Windows.

D3dx9_41.dll Not Found Error Resolution

Posted: by Unknown in Labels: , , , , ,
0

There are several ways that d3dx9_41.dll errors can show up on your computer. Several of the more common specific d3dx9_41.dll error messages are listed below:

"The file d3dx9_41.dll is missing"

"D3dx9_41.DLL Not Found"

"File d3dx9_41.dll not found"

Cause of D3dx9_41.dll Errors

D3dx9_41.dll issues are caused in one way or another by an issue with Microsoft DirectX.

The d3dx9_41.dll file is one of many files contained in the DirectX software collection. Since DirectX is utilized by most Windows based games and advanced graphics programs, d3dx9_41.dll errors usually show up only when using these programs.

Resolution

1. Restart your computer if you haven't yet.

The d3dx9_41.dll error might be a fluke and a simple restart could clear it up completely.

2. Install the latest version of Microsoft DirectX. Chances are, upgrading to the latest version of DirectX will fix the d3dx9_41.dll not found error.

3. Assuming the latest DirectX version from Microsoft doesn't fix the d3dx9_41.dll error you're receiving, look for a DirectX installation program on your game or application DVD or CD. Usually, if a game or other program utilizes DirectX, the software developers will include a copy of DirectX on the installation disc.

Sometimes, though not often, the DirectX version included on the disc is a better fit for the program than the latest version available online.

4. Uninstall the game or software program and then reinstall it again. Something might have happened to the files in the program that work with d3dx9_41.dll and a reinstall could do the trick.

5. Restore the d3dx9_41.dll file from the latest DirectX software package. If the above troubleshooting steps haven't worked to solve your d3dx9_41.dll error, try extracting the d3dx9_41.dll individually from the DirectX downloadable package.

6. Update the drivers for your video card. While it's not the most common solution, in some situations updating the drivers for the video card in your computer could correct this DirectX issue.

Important Registry Tricks For Security

Posted: Tuesday, 19 July 2011 by Unknown in Labels: , , , , , , ,
0

## Manually Disable Regedit Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.


HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System
NOTE: If you do not have System, right click on Polices, click on New and Key, then type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value. Type DisableRegistryTools and press Enter.

6. Right click on DisableRegistryTools and click on Modify.
7. To Disable Regedit and Allow Silent Mode: Type 1 and ok
8. To Disable Regedit and Prevent Silent Mode: Type 2 and ok

## Manually Disable CMD Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System

Note:If you do not have System in the left pane, then right click on Windows and click on New and Key, then type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value. Type DisableCMD and press Enter.

6. Right click on DisableCMD and click on Modify
7. To Disable Command Prompt Only and Allow Scripts: Type 2 and ok.
8. To Disable Command Prompt and Scripts: Type 1 and ok.

## Manually Disable TaskMgr Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System

NOTE: If you do not have System, then right click on Polices and click on New and Key. Type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value and type DisableTaskMgr and press Enter.

6. Right click on DisableTaskMgr and click on Modify.
7. Type 1 and click on OK.

## Manually Disable Autoplay Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\No​DriveTypeAutorun

NOTE: If you do not have System, then right click on Polices and click on New and Key. Type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value and
type No​DriveTypeAutorun and press Enter.

6. Right-click NoDriveTypeAutorun, and then click Modify.
7. In the Value data box, type 0xFF to disable all types of drives.
8. Click OK, and then exit Registry Editor.
9. Restart the computer.

## Manually Disable Run Command in Start Menu Using Registry Editor

1. Open the Start Menu.
2. Click run, type regedit and press Enter.
3. If prompted by UAC, then click on the Continue (Vista) or Yes (Windows 7).
4. In regedit, navigate to the location below.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\No​Run

NOTE: If you do not have System, then right click on Polices and click on New and Key. Type System and press Enter.

5. In the right pane, right click on a empty area and click on New and DWORD (32-bit) Value and
type No​Run and press Enter.

6. Right-click NoRun, and then click Modify.
7. In the Value data box, type 0 to disable run / 1 to eanble run.
8. Click OK, and then exit Registry Editor.
9. Restart the computer.

Note: Other DWORD values: DisableLocalMachineRun, DisableLocalMachineRunOnce, DisableCurrentUserRun, DisableCurrentUserRunOnce.

ATI Catalyst Control Centre error / MOM.exe error

Posted: Tuesday, 21 June 2011 by Unknown in Labels: , , , , , ,
0

Do you see this error when you startup you pc/laptop ??


" Catalyst Control Centre: Command-Line has stopped working " or
" Mom.exe application error. Failed to initialize properly ".


Now there are 2 possible reasons for this error:
1. corrupted video driver/software in this case ATI Catalyst Control Centre.
2. virus/malware


First we try to reinstall ATI Catalyst Control Centre.


Steps to do that:


1. Best way to uninstall ATI Catalyst Control Centre is to run the setup file used to install the software and select unistall to completely unistall the software.


2. Next run ccleaner and clean the pc. Then use the registry cleaner option of ccleaner to remove the software leftover.


3. Now go to program files and delete all related folders.


4. Next click Start --> run and type in regedit and press enter.
Registry Editor will open.
Now go to - HKEY_CURRENT_USER --> Software -->Delete ATI / ATI Technologies entry.
Then go to - HKEY_LOCAL_MACHINE -->Software --> Delete ATI / ATI Technology entry.


5. Now restart the pc.


6. Then run the setup file again to install ATI Catalyst Control Centre.


This should sove the problem ( atleast it worked for me ).


Now if this does not help, then may be this is because of virus.
Run full pc scan with a good antivirus ( Nod32 / Kaspersky ).


If this does not solve your problem, then run sytem diagnostics with HijackThis and ask for
help from experts in forums.


Hope this helps you.

Double Click Always Opens Search or OpenWith in Windows Explorer

Posted: Thursday, 26 May 2011 by Unknown in
0


If you mess around in the registry, or install some different software packages that add things to the right-click menu, you can end up with a problem where the default action on a folder is always "Search…" or "Open With", even though you set it to something else.


There's a quick and easy fix for this problem. Open up regedit.exe by using Start\Run and then browse down to this registry key:
HKEY_CLASSES_ROOT\Directory\shell
Double-click on the default value and set it to "none" without the quotes, as seen here:
This will restore the normal behavior.


If you are also experiencing this problem when you try to click on a drive, you can run this command from the run box or command prompt:
regsvr32 /i shell32.dll
This should restore the normal behavior.


If you are getting a message that says "Windows cannot find 'PET32.exe'" or anu other error messages, then at some point you had a virus, or still have a virus. First, make sure that you run a virus scanner to get rid of the virus. Then run the regsvr32 command above, which should fix the problem.


To remove the virus-


1. Use SDFix
2. Use ComboFix


This will clean your pc. 


Warning: Please read how to use guides before using these software. 


After problem is resolved remove SDFix and ComboFix from your system and run a full system virus scan before doing anything.


Use a good antivirus and antispyware to keep your pc clean.

How To Repair or Replace Boot.ini in Windows XP

Posted: Sunday, 22 May 2011 by Unknown in
0

When you start your computer after you upgrade to Microsoft Windows XP, you may receive one or both of the following error messages:

Invalid Boot.ini

Windows could not start because the following file is missing or corrupt: 
Windows\System32\Hal.dll
This issue may occur if the Boot.ini file is missing, damaged, or contains incorrect entries.

To resolve this issue, start the computer from the Windows XP CD, start the Recovery Console, and then use the Bootcfg.exe tool to rebuild the Boot.ini file. To do this, follow these steps:
  1. Configure the computer to start from the CD-ROM or DVD-ROM drive. For information about how to do this, see your computer documentation, or contact your computer manufacturer.
  2. Insert the Windows XP CD-ROM into your CD-ROM or DVD-ROM drive, and then restart your computer.
  3. When you receive the "Press any key to boot from CD" message, press a key to start your computer from the Windows XP CD-ROM.
  4. When you receive the "Welcome to Setup" message, press R to start the Recovery Console.
  5. If you have a dual-boot or multiple-boot computer, select the installation that you have to use from the Recovery Console.
  6. When you are prompted, type the administrator password, and then press ENTER.
  7. At the command prompt, type bootcfg /list, and then press ENTER. The entries in your current Boot.ini file appear on the screen.
  8. At the command prompt, type bootcfg /rebuild, and then press ENTER. This command scans the hard disks of the computer for Windows XP, Microsoft Windows 2000, or Microsoft Windows NT installations, and then displays the results. Follow the instructions that appear on the screen to add the Windows installations to the Boot.ini file. For example, follow these steps to add a Windows XP installation to the Boot.ini file:
    1. When you receive a message that is similar to the following message, press Y:
      Total Identified Windows Installs: 1

      [1] C:\Windows 
      Add installation to boot list? (Yes/No/All)
    2. You receive a message that is similar to the following message:
      Enter Load Identifier
      This is the name of the operating system. When you receive this message, type the name of your operating system, and then press ENTER. This is eitherMicrosoft Windows XP Professional or Microsoft Windows XP Home Edition.
    3. You receive a message that is similar to the following:
      Enter OS Load options
      When you receive this message, type /fastdetect, and then press ENTER. 

      Note The instructions that appear on your screen may be different, depending on the configuration of your computer.
  9. Type exit, and then press ENTER to quit Recovery Console. Your computer will reboot.

Partition and format your USB drive and make it bootable with RMPrepUSB (a Windows utility)

Posted: Saturday, 14 May 2011 by Unknown in Labels: , , , ,
0


RMPrepUSB is similar to the HP Format utility, but much more flexible and should be better at creating a USB Flash memory drive that will boot on most systems successfully.
RMPrepUSB is a Windows utility that can be used to format any USB storage device, e.g. USB Flash drive (UFD) or USB hard disk as a bootable device. It can be used to partition, format, write a Master Boot Record,  partition table and/or Volume Boot Record (sometimes called a Partition Boot Record) and operating system boot code to any USB storage device (e.g. USB flash memory drive or USB hard disk).
RMPrepUSB makes a single user partition of any size and is primarily intended for USB Flash Drive (UFD) memory sticks although it can be used on USB hard drives to create a single partition.
The utility also places boot code on the USB device for either XP/WinPEv1 (ntldr), Vista/WinPEv2/Win7 (bootmgr), MS-DOS (io.sys) or FreeDos (kernel.sys).
RMPrepUSB does not place any files on the UFD – you must copy these over yourself or set the option in RMPrepUSB to copy over the contents of a folder of your choice.

RMPrepUSB has many different uses, including:
  1. Partition, format and make bootable a USB drive
  2. Clean (erase/wipe) a USB drive
  3. Backup a USB drive (or parts of a USB drive) to an image file
  4. Restore an image file (or part of an image file) to a USB drive
  5. Install the Grub bootloader onto a USB drive
  6. Test a USB drive (useful for testing fake USB flash memory drives
  7. Eject a USB drive (for safe removal)
  8. Display the partition structure of a USB drive (or image file)
  9. Use after PEBuilder to install your XP PE files to a bootable USB drive.
Six steps to make your USB drive bootable
  1. Select the USB drive in the listbox if more than one is present and either leavethe size as MAX or change it (e.g. type 512 for a partition size of 512MiB).
  2. Change the volume label text if you want to.
  3. Set the type boot loader that you want installed onto the new partition after ithas been formatted.
  4. Change the Filesystem and Overrides. You may need to experiment with these before you can find a combination that works. Different models of PCs or Noteboooks may require different settings.
  5. If you want to, you can copy the contents of a folder to the new empty partition after it has been formatted. Tick the COPY OS FILES box if you want this. Note: RMPrepUSB will not place any boot files on the USB drive and it will not be bootable unless you copy the boot files onto it.
  6. Click on the blue Prepare drive button.

Creating Multiboot USB/ISO for Troubleshooting PC

Posted: by Unknown in Labels: , , , ,
0


1. XBoot- A utility for creating Multiboot USB/ISO


XBoot is a easy-to-use utility for creating Multiboot USB/ISO.You may have seen many bootable ISO files like Linux live CDs , Antivirus rescue CDs etc. XBoot can combine these ISO files in to oneMultiboot ISO file or create Multiboot USB in just few clicks.

Simply Drag and drop ISO files in to XBoot and click Create ISO or Create USB button.

Support for some ISO files have been added , support for some other ISO files will be added later on the request of users.

Official website of Xboot: http://sites.google.com/site/shamurxboot

2. Sardu


SARDU (short for Shardana Antivirus Rescue Disk Utility) is a free software application that can produce a CD / DVD or a USB device with multiboot support.

The CD/DVD/USB device may include comprehensive collections of antivirus rescue cds, collections of utilities, popular distributions of Linux Live, and the best known Windows PE © , recovery disks and Install of Windows XP © and Windows Seven ©.

Official website of Xboot: http://www.sarducd.it/

Error Loading Operating System

Posted: Sunday, 8 May 2011 by Unknown in Labels: , , , , , ,
0



" Error Loading Operating System "

This one is a classic problem. It shows up when one is booting up the pc.

Now there are 2 different scenarios  in which this error may crop up.

1. You are booting your computer and this error comes up.
2. You are tring to install a new OS and during the first reboot in the process this error comes up.

According to microsoft : 

This issue may occur if your computer BIOS does not correctly manage or support the capacity of the hard disk on which you are installing Windows XP.

To resolve this issue, use one of the following methods:

1. Make sure that you are using the latest BIOS revision for your computer. Contact the computer manufacturer to inquire about how to obtain and install the latest BIOS update that is available for the computer.

2. If you are using an IBM computer with an AWARD BIOS version 4.5x, visit the following IBM Web site: http://www.ibm.com

This issue is caused by any of the below reasons.
  1. The computer's BIOS does not support the computer hard disk drive's size or settings.
  2. Computer Hard disk drive is not properly setup in CMOS.
  3. Issue with drive's partitions ( corrupt partition table in mbr )
Solution:

1. This issue is often caused when the BIOS does not properly detect the hard disk drive. To resolve this issue, update the computer motherboard's BIOS.

2. Verify that the computer's hard disk drive is properly setup in CMOS setup.Once in CMOS, verify the below hard disk drive settings.
  1. Verify the hard disk drive is detected.
  2. Try changing the "Access mode" on the hard disk drive to Large or LBA. This setting may vary depending on the BIOS.
3. This issue can be cause if the disk drives are not properly setup or have been changed by another program, such as a utility that comes with a Linux distribution. To resolve this issue, delete and recreate all the partitions before running the Windows XP setup.

Warning: Before deleting partition backup your data as you will lose all you data. There are free programs out there with which you can backup your data.Do not backup partitions as after you try to restore the partitions it will corrupt the mbr and you will end up with the same error.

To backup your data use any free live cd distributions eg. partedmagic, damn small linux, puppy linux etc. Download the iso file, write it to cd and boot from the cd. browse the partitions and copy your data to an external HDD.

If simply deleting and recreating partition does not solve your problem, then write zeros to the entire drive which is nuking your drive. You can use " Dariks Boot and Nuke " software for this purpose. You can download it from the download section.

** Before deleting your partition, try and fix your boot/mbr which is also one of the reason for this error.

1. boot from your windows xp installation cd.
2. after loading is done, press r to repair installation.
3. now you will see a command prompt like screen - select the harddisk on which you wish to repair installation by pressing 1 or as shown in the prompt.
4. type fixboot and press enter
5. typr fixmbr and press enter
6. type exit and press enter

Your pc will restart and if your problem is still not solved then follow the above methods of deleting and recreating partitions.

PC hangs and shutsdown while viewing online videos ( black screen )

Posted: by Unknown in Labels: , , ,
0


I faced this annoying little problem. Whenever i view online videos, the pc hangs after a few seconds  and shutsdown ( black screen). I have to do a hard reset to operate my pc again.

Well i searched a lot but could not get any idea as to what was causing this problem. Found out later that this issue was of adobe flash player.

1. While viewing online videos right click on the video, deselect enable hardware acceleration.  This option was causing the problem. Enable hardware acceleration is used for webcam.

2. If the above does not solve your problem then -
  • uninstall flash player, java.
  • restart pc.
  • download new version of flash player and java.
  • now first install java and then flash player.
  • restart pc.

Warning 0251-System CMOS checksum bad - default configuration used

Posted: by Unknown in Labels: , , , , ,
0


0251-System CMOS checksum bad - default configuration used.

This error creeps up during computer startup.

The main reason for this error are -

1. CMOS battery is discharged/faulty. 
In this case the CMOS battery needs to be replaced. This is the reason 99% of the time  for this error.

2. CMOS battery connector in motherboard is faulty.
In this case motherboard needs to be replaced or repaired.  This is rare and is mostly caused by voltage fluctuation.

Take ownership of folders/drives and grant permissions !!

Posted: by Unknown in Labels: , , , , ,
0


Has it ever happened to you that you doubleclicked a folder or drive and a message sprang up saying " Access Denied ".

Well it means you don't  have the required permissions to access that particular drive or folder. In order to access it you have to take ownership of that drive or folder. You need  to have administrator priviledges to make changes to permissions.

Now there are 2  ways to do so -- 

A. Through Windows GUI

1. Right click on the folder/drive and select properties.

2. Click on advanced button at the button and now click on owner tab. Under current owner you will see the current owner of the folder/drive. By default it is the administrators group. Do not change it. If it has been changed to some other account change it to administrators group. Click on edit and select administrators under " change owner to ". Select the tickbox below which says " replace owner on subcontainers and objects ".  Now click ok.

3. Now go  to security tab and check if your username is present under " Groups or usernames: ". 

4. If yes, then select your username and look if you have fullcontrol under " Permissions for usernamename ". If fullcontrol is not selected then click edit button and select your username. Now select the tickbox next to fullcontrol under allow and click ok.

5. If no, then click edit button and then click add button in the window that opens. Now a window opens  " Select users or groups ". Click on advanced.  Now click on findnow button in the window that opens up. Select your username from the search results  and click ok and again ok. Now you can see your username under " Groups or usernames ". Select your username and select allow fullcontrol under " Permissions for username ". Click ok and then click apply.

B. Through Command Prompt

Click on start, then run. Now type cmd and press enter to start command prompt.

1. takeown /F D:\foldername /A /R
2. cacls D:\foldername  /T /P username:F
3. icacls D:\foldername  /grant username:F /T  ( use if cacls is not supported )