Archive for category Boot
>Boot Block Recovery
>
You don’t need to pay a measly sum of dollars just to recover from a boot block mode. Here it is folks:
AWARD Bootblock recovery:
That shorting trick should work if the boot block code is not corrupted, and it should not be if /sb switch is used when flashing the bios (instead of /wb switch).
The 2 pins to short to force a checksum error varies from chip to chip. But these are usually the highest-numbered address pins (A10 and above).
These are the pins used by the system to read the System BIOS (original.bin for award v6), calculate the ROM checksum and see if it’s valid before decompressing it into memory, and subsequently allow Bootblock POST to pass control over to the System BIOS.
You just have to fool the system into believing that the System BIOS is corrupt. This you do by giving your system a hard time reading the System BIOS by shorting the 2 high address pins. And when it could not read the System BIOS properly, ROM Checksum Error is detected “so to speak” and Bootblock recovery is activated.
Sometimes, any combination of the high address pins won’t work to force a checksum error in some chips, like my Winbond W49F002U. But shorting the #WE pin with the highest-numbered address pin (A17) worked for this chip. You just have to be experimentative if you’re not comfortable with “hot flashing” or “replacement BIOS”.
But to avoid further damage to your chip if you’re not sure which are the correct pins to short, measure the potential between the 2 pins by a voltmeter while the system is on. If the voltage reading is zero (or no potential at all), it is safe to short these pins.
But do not short the pins while the system is on. Instead, power down then do the short, then power up while still shorting. And as soon as you hear 3 beeps (1 long, 2 short), remove the short at once so that automatic reflashing from Drive A can proceed without errors (assuming you had autoexec.bat in it).
About how to do the shorting, the tip of a screwdriver would do. But with such minute pins on the PLCC chip, I’m pretty comfortable doing it with the tip of my multi-tester or voltmeter probe. Short the pins at the point where they come out of the chip.
AMIBIOS Recovery bootblock:
1. Copy a known working BIOS image for your board to a floppy and rename it to AMIBOOT.ROM.
2. Insert the floppy in your system’s floppydrive.
3. Power on the system while holding CTRL+Home keys. Release the keys when you hear a beep and/or see the floppy light coming on.
4 . Just wait until you hear 4 beeps. When 4 beeps are heard the reprogramming of the System Block BIOS went succesfull, so then you may restart your system.
Some alternative keys that can be used to force BIOS update (only the System Block will be updated so it’s quite safe):
CTRL+Home= restore missing code into system block and clear CMOS when programming went ok.
CTRL+Page Up= restore missing code into system block and clear CMOS or DMI when programming went ok.
CTRL+Page Down= restore missing code into system block and do not clear CMOS and DMI area when programming went ok
Btw: the alternative keys work only with AMIBIOS 7 or higher (so for example an AMI 6.26 BIOS can be only recovered by using CTRL+Home keys).
Boot Block Recovery for FREE
************************************************
BLACKOUT Flashing
*************************************************
Recovering a Corrupt AMI BIOS chip
With motherboards that use BOOT BLOCK BIOS it is possible to recover a corrupted BIOS because the BOOT BLOCK section of the BIOS, which is responsible for booting the computer remains unmodified. When an AMI BIOS becomes corrupt the system will appear to start, but nothing will appear on the screen, the floppy drive light will come on and the system will access the floppy drive repeatedly. If your motherboard has an ISA slot and you have an old ISA video card lying around, put the ISA video card in your system and connect the monitor. The BOOT BLOCK section of the BIOS only supports ISA video cards, so if you do not have an ISA video card or your motherboard does not have ISA slots, you will have to restore your BIOS blind, with no monitor to show you what’s going on.
AMI has integrated a recovery routine into the BOOT BLOCK of the BIOS, which in the event the BIOS becomes corrupt can be used to restore the BIOS to a working state. The routine is called when the SYSTEM BLOCK of the BIOS is empty. The restore routine will access the floppy drive looking for a BIOS file names AMIBOOT.ROM, this is why the floppy drive light comes on and the drive spins. If the file is found it is loaded into the SYSTEM BLOCK of the BIOS to replace the missing information. To restore your BIOS simply copy a working BIOS file to a floppy diskette and rename it AMIBOOT.ROM, then insert it into the computer while the power is on. The diskette does not need to be bootable or contain a flash utility. After about four minutes the system will beep four times. Remove the floppy diskette from the drive and reboot the computer. The BIOS should now be restored.
Recovering a Corrupt AWARD BIOS
With AWARD BIOS the process is similar but still a bit different. To recover an AWARD BIOS you will need to create a floppy diskette with a working BIOS file in .BIN format, an AWARD flash utility and an AUTOEXEC.BAT file. AWARD BIOS will not automatically restore the BIOS information to the SYSTEM BLOCK for this reason you will need to add the commands necessary to flash the BIOS in the AUTOEXEC.BAT file. The system will run the AUTOEXE.BAT file, which will in turn flash the BIOS. This is fairly easy. Here are the steps you need to take.
· Create a bootable floppy diskette
· Copy the BIOS file and flash utility to the diskette
· Create an text file with any standard text editor and add the following lines
@ECHO OFF
FLASH763 BIOSFILE.BIN /py
In the above example I am assuming that you are using the FLASH763.EXE flash utility. You will need to replace the FLASH763 with the name of whatever flash utility you are using, and replace the BIOSFILE.BIN with the name of the BIOS file you are using. You will also need to change the ‘/py’ to whatever the command is for your flash utility to automatically program the BIOS without user intervention. If you do not know the command to automatically flash your BIOS type the name of the flash utility with a space and then /? to display the utility’s help screen. The help screen should pecify the command switch to automatically flash your BIOS. If you are using the FLASH763.EXE utility then the switch to automatically flash your BIOS is ‘/py’.
>Boot Block Recovery
>
You don’t need to pay a measly sum of dollars just to recover from a boot block mode. Here it is folks:
AWARD Bootblock recovery:
That shorting trick should work if the boot block code is not corrupted, and it should not be if /sb switch is used when flashing the bios (instead of /wb switch).
The 2 pins to short to force a checksum error varies from chip to chip. But these are usually the highest-numbered address pins (A10 and above).
These are the pins used by the system to read the System BIOS (original.bin for award v6), calculate the ROM checksum and see if it’s valid before decompressing it into memory, and subsequently allow Bootblock POST to pass control over to the System BIOS.
You just have to fool the system into believing that the System BIOS is corrupt. This you do by giving your system a hard time reading the System BIOS by shorting the 2 high address pins. And when it could not read the System BIOS properly, ROM Checksum Error is detected “so to speak” and Bootblock recovery is activated.
Sometimes, any combination of the high address pins won’t work to force a checksum error in some chips, like my Winbond W49F002U. But shorting the #WE pin with the highest-numbered address pin (A17) worked for this chip. You just have to be experimentative if you’re not comfortable with “hot flashing” or “replacement BIOS”.
But to avoid further damage to your chip if you’re not sure which are the correct pins to short, measure the potential between the 2 pins by a voltmeter while the system is on. If the voltage reading is zero (or no potential at all), it is safe to short these pins.
But do not short the pins while the system is on. Instead, power down then do the short, then power up while still shorting. And as soon as you hear 3 beeps (1 long, 2 short), remove the short at once so that automatic reflashing from Drive A can proceed without errors (assuming you had autoexec.bat in it).
About how to do the shorting, the tip of a screwdriver would do. But with such minute pins on the PLCC chip, I’m pretty comfortable doing it with the tip of my multi-tester or voltmeter probe. Short the pins at the point where they come out of the chip.
AMIBIOS Recovery bootblock:
1. Copy a known working BIOS image for your board to a floppy and rename it to AMIBOOT.ROM.
2. Insert the floppy in your system’s floppydrive.
3. Power on the system while holding CTRL+Home keys. Release the keys when you hear a beep and/or see the floppy light coming on.
4 . Just wait until you hear 4 beeps. When 4 beeps are heard the reprogramming of the System Block BIOS went succesfull, so then you may restart your system.
Some alternative keys that can be used to force BIOS update (only the System Block will be updated so it’s quite safe):
CTRL+Home= restore missing code into system block and clear CMOS when programming went ok.
CTRL+Page Up= restore missing code into system block and clear CMOS or DMI when programming went ok.
CTRL+Page Down= restore missing code into system block and do not clear CMOS and DMI area when programming went ok
Btw: the alternative keys work only with AMIBIOS 7 or higher (so for example an AMI 6.26 BIOS can be only recovered by using CTRL+Home keys).
Boot Block Recovery for FREE
************************************************
BLACKOUT Flashing
*************************************************
Recovering a Corrupt AMI BIOS chip
With motherboards that use BOOT BLOCK BIOS it is possible to recover a corrupted BIOS because the BOOT BLOCK section of the BIOS, which is responsible for booting the computer remains unmodified. When an AMI BIOS becomes corrupt the system will appear to start, but nothing will appear on the screen, the floppy drive light will come on and the system will access the floppy drive repeatedly. If your motherboard has an ISA slot and you have an old ISA video card lying around, put the ISA video card in your system and connect the monitor. The BOOT BLOCK section of the BIOS only supports ISA video cards, so if you do not have an ISA video card or your motherboard does not have ISA slots, you will have to restore your BIOS blind, with no monitor to show you what’s going on.
AMI has integrated a recovery routine into the BOOT BLOCK of the BIOS, which in the event the BIOS becomes corrupt can be used to restore the BIOS to a working state. The routine is called when the SYSTEM BLOCK of the BIOS is empty. The restore routine will access the floppy drive looking for a BIOS file names AMIBOOT.ROM, this is why the floppy drive light comes on and the drive spins. If the file is found it is loaded into the SYSTEM BLOCK of the BIOS to replace the missing information. To restore your BIOS simply copy a working BIOS file to a floppy diskette and rename it AMIBOOT.ROM, then insert it into the computer while the power is on. The diskette does not need to be bootable or contain a flash utility. After about four minutes the system will beep four times. Remove the floppy diskette from the drive and reboot the computer. The BIOS should now be restored.
Recovering a Corrupt AWARD BIOS
With AWARD BIOS the process is similar but still a bit different. To recover an AWARD BIOS you will need to create a floppy diskette with a working BIOS file in .BIN format, an AWARD flash utility and an AUTOEXEC.BAT file. AWARD BIOS will not automatically restore the BIOS information to the SYSTEM BLOCK for this reason you will need to add the commands necessary to flash the BIOS in the AUTOEXEC.BAT file. The system will run the AUTOEXE.BAT file, which will in turn flash the BIOS. This is fairly easy. Here are the steps you need to take.
· Create a bootable floppy diskette
· Copy the BIOS file and flash utility to the diskette
· Create an text file with any standard text editor and add the following lines
@ECHO OFF
FLASH763 BIOSFILE.BIN /py
In the above example I am assuming that you are using the FLASH763.EXE flash utility. You will need to replace the FLASH763 with the name of whatever flash utility you are using, and replace the BIOSFILE.BIN with the name of the BIOS file you are using. You will also need to change the ‘/py’ to whatever the command is for your flash utility to automatically program the BIOS without user intervention. If you do not know the command to automatically flash your BIOS type the name of the flash utility with a space and then /? to display the utility’s help screen. The help screen should pecify the command switch to automatically flash your BIOS. If you are using the FLASH763.EXE utility then the switch to automatically flash your BIOS is ‘/py’.
Viruses
Posted by nck12 in Boot, boot virus, macro virus, Viruses on December 11, 2010
Viruses or virii are self-replicating pieces of software that, similar to a biological virus, attach
themselves to another program, or, in the case of “macro viruses”, to another file. The virus is
only run when the program or the file is run or opened. It is this which differentiates viruses from
worms. If the program or file is not accessed in any way, then the virus will not run and will not
copy itself further.
There are a number of types of viruses, although, significantly, the most common form today is
the macro virus, and others, such as the boot sector virus are now only found “in captivity
Boot Sector Viruses
The boot sector virus was the first type of virus created. It hides itself in the executable
code at the beginning of bootable disks. This meant that in order to infect a machine, you
needed to boot from an infected floppy disk. A long time ago, ( 15 years or so ) booting
from floppy was a relatively regular occurrence, meaning that such viruses were actually
quite well spread by the time that people figured out what was happening. This virus ( and
all other types ) should leave a signature which subsequent infection attempts detect, so
as not to repeatedly infect the same target. It is this signature that allows other software
( such as Anti-Virus-software ) to detect the infection
The Executable File Virus
would specifically look for programs which were a part of the operating system, and thus
were most likely to be run each time the computer was turned on, increasing their
chances of successful propagation. There were a few ways of adding a virus to an
subtle ) was to overwrite the first part of the executable file with the virus code. This meant
that the virus executed, but that the program would subsequently crash, leaving it quite
obvious that there was an infection – especially if the file was an important system file.
remain there in the background, allowing the computer to run as normal in the
foreground. The more complex of these viruses would intercept system calls that would
expose them and return false results – others would attach themselves to the ‘dir’
command, and then infect every application in the directory that was listed – a few even
stopped ( or deleted ) Anti-Virus software installed onto the systems
The Polymorphic Virus
Early viruses were easy enough to detect. They had a certain signature to identify them,
either within themselves as a method to prevent re-infection, or simply that they had a
specific structure which it was possible to detect. Then along came the polymorphic virus.
Poly – meaning multiple and morphic – meaning shape. These viruses change themselves
each time they replicate, rearranging their code, changing encryption and generally
making themselves look totally different. This created a huge problem, as instantly there
were much smaller signatures that remained the same – some of the “better” viruses were
reduced to a detection signature of a few bytes. The problem was increased with the
release of a number of polymorphic kits into the virus writing community which allowed
any virus to be recreated as a polymorph.
The Macro Virus The
Macro Virus makes use of the built-in ability of a number of programs to execute
code. Programs such as Word and Excel have limited, but very powerful, versions of the
Visual Basic programming language. This allows for the automation of repetitive tasks, and
the automatic configuration of specific settings. These macro languages are misused to
attach viral code to documents which will automatically copy itself on to other
documents, and propagate. Although Microsoft has turned off the feature by default now
on new installations, it used to be that Outlook would automatically execute certain code
attached to e-mails as soon as they were read. This meant that viruses were propagating
very quickly by sending themselves to all of the e-mail addresses that were stored on the
infected machine.
Worms
Worms are older than viruses. The first worm was created many years before the first virus.
This worm made use of a flaw in the UNIX finger command to quickly bring down most of
the Internet.A worm is a program that, after it has been started, replicates without any need for
human intervention. It will propagate from host to host, taking advantage of an
unprotected service or services. It will traverse a network without the need for a user to
send an infected file or e-mail. Most of the large incidents in the press recently have been
worms rather than viruses.
Earn money with AlertPay
Trojans and Spyware
The first Trojan Horse was created by the Greeks several thousand years ago.The basic concept is that you sneak something nasty into an
otherwise secure computer in the guise of something nicer. This can range from a
downloaded game trailer to an e-mail promising naked pictures of your favorite celebrity. This
section covers Trojans and spy ware.
Trojans are pieces of malware which masquerade as something either useful or
desirable in order to get you to run them. At this point they may well do something unpleasant
to your computer such as install a backdoor or rootkit or – even worse – dial a
premium rate phone number that will cost you money.
Spyware is software that installs itself surreptitiously, often from websites that you might
visit. Once it is installed it will look for information that it considers valuable. This may be usage
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Horse As a Virus |
The Movie Troy,You can Imagine that horse as a Trojan Virus.
Time bomb programming is used to allow you to download and try a program for a period of time – usually 30 days. At the end of the trial period, the program ceases to function, unless a registration code is
provided.Logic bombs and Time bombs are programs which have no replication ability and no
ability to create an access method, but are applications or parts of applications that will
cause damage to data should they become active. They can be stand-alone, or part of
worms or viruses.
More About Computer Security
>Viruses
Posted by nck12 in Boot, boot virus, macro virus, Viruses on December 11, 2010
>Viruses or virii are self-replicating pieces of software that, similar to a biological virus, attach
themselves to another program, or, in the case of “macro viruses”, to another file. The virus is
only run when the program or the file is run or opened. It is this which differentiates viruses from
worms. If the program or file is not accessed in any way, then the virus will not run and will not
copy itself further.
There are a number of types of viruses, although, significantly, the most common form today is
the macro virus, and others, such as the boot sector virus are now only found “in captivity
Boot Sector Viruses
The boot sector virus was the first type of virus created. It hides itself in the executable
code at the beginning of bootable disks. This meant that in order to infect a machine, you
needed to boot from an infected floppy disk. A long time ago, ( 15 years or so ) booting
from floppy was a relatively regular occurrence, meaning that such viruses were actually
quite well spread by the time that people figured out what was happening. This virus ( and
all other types ) should leave a signature which subsequent infection attempts detect, so
as not to repeatedly infect the same target. It is this signature that allows other software
( such as Anti-Virus-software ) to detect the infection
The Executable File Virus
would specifically look for programs which were a part of the operating system, and thus
were most likely to be run each time the computer was turned on, increasing their
chances of successful propagation. There were a few ways of adding a virus to an
subtle ) was to overwrite the first part of the executable file with the virus code. This meant
that the virus executed, but that the program would subsequently crash, leaving it quite
obvious that there was an infection – especially if the file was an important system file.
remain there in the background, allowing the computer to run as normal in the
foreground. The more complex of these viruses would intercept system calls that would
expose them and return false results – others would attach themselves to the ‘dir’
command, and then infect every application in the directory that was listed – a few even
stopped ( or deleted ) Anti-Virus software installed onto the systems
The Polymorphic Virus
Early viruses were easy enough to detect. They had a certain signature to identify them,
either within themselves as a method to prevent re-infection, or simply that they had a
specific structure which it was possible to detect. Then along came the polymorphic virus.
Poly – meaning multiple and morphic – meaning shape. These viruses change themselves
each time they replicate, rearranging their code, changing encryption and generally
making themselves look totally different. This created a huge problem, as instantly there
were much smaller signatures that remained the same – some of the “better” viruses were
reduced to a detection signature of a few bytes. The problem was increased with the
release of a number of polymorphic kits into the virus writing community which allowed
any virus to be recreated as a polymorph.
The Macro Virus The
Macro Virus makes use of the built-in ability of a number of programs to execute
code. Programs such as Word and Excel have limited, but very powerful, versions of the
Visual Basic programming language. This allows for the automation of repetitive tasks, and
the automatic configuration of specific settings. These macro languages are misused to
attach viral code to documents which will automatically copy itself on to other
documents, and propagate. Although Microsoft has turned off the feature by default now
on new installations, it used to be that Outlook would automatically execute certain code
attached to e-mails as soon as they were read. This meant that viruses were propagating
very quickly by sending themselves to all of the e-mail addresses that were stored on the
infected machine.
Worms
Worms are older than viruses. The first worm was created many years before the first virus.
This worm made use of a flaw in the UNIX finger command to quickly bring down most of
the Internet.A worm is a program that, after it has been started, replicates without any need for
human intervention. It will propagate from host to host, taking advantage of an
unprotected service or services. It will traverse a network without the need for a user to
send an infected file or e-mail. Most of the large incidents in the press recently have been
worms rather than viruses.
Earn money with AlertPay
Trojans and Spyware
The first Trojan Horse was created by the Greeks several thousand years ago.The basic concept is that you sneak something nasty into an
otherwise secure computer in the guise of something nicer. This can range from a
downloaded game trailer to an e-mail promising naked pictures of your favorite celebrity. This
section covers Trojans and spy ware.
Trojans are pieces of malware which masquerade as something either useful or
desirable in order to get you to run them. At this point they may well do something unpleasant
to your computer such as install a backdoor or rootkit or – even worse – dial a
premium rate phone number that will cost you money.
Spyware is software that installs itself surreptitiously, often from websites that you might
visit. Once it is installed it will look for information that it considers valuable. This may be usage
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Horse As a Virus |
The Movie Troy,You can Imagine that horse as a Trojan Virus.
Time bomb programming is used to allow you to download and try a program for a period of time – usually 30 days. At the end of the trial period, the program ceases to function, unless a registration code is
provided.Logic bombs and Time bombs are programs which have no replication ability and no
ability to create an access method, but are applications or parts of applications that will
cause damage to data should they become active. They can be stand-alone, or part of
worms or viruses.
More About Computer Security
Hacking,Secure Your Web Experiance,How to Create Password ?
How To Boot Xp Fast ?
Boot Xp Fast
-
Follow the following steps
1. Open notepad.exe, type “del c:\windows\prefetch\ntosboot-*.* /q” (without the quotes) & save as “ntosboot.bat” in c:\
- 2. From the Start menu, select “Run…” & type “gpedit.msc”.
- 3. Double click “Windows Settings” under “Computer Configuration” and double click again on”Shutdown” in the right window.
- 4. In the new window, click “add”, “Browse”, locate your “ntosboot.bat” file & click “Open”.
- 5. Click “OK”, “Apply” & “OK” once again to exit.
- 6. From the Start menu, select “Run…” & type “devmgmt.msc”.
- 7. Double click on “IDE ATA/ATAPI controllers”
- 8. Right click on “Primary IDE Channel” and select “Properties”.
- 9. Select the “Advanced Settings” tab then on the device or 1 that doesn’t have ‘device type’ greyed out select ‘none’ instead of ‘autodetect’ & click “OK”.
- 10. Right click on “Secondary IDE channel”, select “Properties” and repeat step 9.
- 11. Reboot your computer.
>How To Boot Xp Fast ?
>Boot Xp Fast
-
Follow the following steps
1. Open notepad.exe, type “del c:\windows\prefetch\ntosboot-*.* /q” (without the quotes) & save as “ntosboot.bat” in c:\
- 2. From the Start menu, select “Run…” & type “gpedit.msc”.
- 3. Double click “Windows Settings” under “Computer Configuration” and double click again on”Shutdown” in the right window.
- 4. In the new window, click “add”, “Browse”, locate your “ntosboot.bat” file & click “Open”.
- 5. Click “OK”, “Apply” & “OK” once again to exit.
- 6. From the Start menu, select “Run…” & type “devmgmt.msc”.
- 7. Double click on “IDE ATA/ATAPI controllers”
- 8. Right click on “Primary IDE Channel” and select “Properties”.
- 9. Select the “Advanced Settings” tab then on the device or 1 that doesn’t have ‘device type’ greyed out select ‘none’ instead of ‘autodetect’ & click “OK”.
- 10. Right click on “Secondary IDE channel”, select “Properties” and repeat step 9.
- 11. Reboot your computer.
-
You are currently browsing the archives for the Boot category.
Something New 