Monday, July 30, 2007

Future technology

I need to got ono of these ;p



Monday, July 23, 2007

Google e-books

More google e-books get it or regret it.I'm also still reading it, and here i share it with you

Google Adsense Secrets

Google Secrets How To Get A top 10 Ranking

How to Hacker

There is a community, a shared culture, of expert programmers and networking wizards that traces its history back through decades to the first time-sharing minicomputers and the earliest ARPAnet experiments. The members of this culture originated the term 'hacker'. Hackers built the Internet. Hackers made the Unix operating system what it is today. Hackers run Usenet. Hackers make the World Wide Web work. If you are part of this culture, if you have contributed to it and other people in it know who you are and call you a hacker, you're a hacker.

modern Zen poem has it:

To follow the path:
look to the master, follow the master, walk with the master, see through the master, become the master.

read this how to hacker e-book

Sunday, July 22, 2007

BIOS Beep Code


What is a BIOS Beep Code?

When you power on a computer the BIOS immediately takes control of the computer and performs the P.O.S.T (Power On Self Test). At the end of the POST the computer will play an audible 'BEEP' through either the PC's internal speaker of through speakers attached to the sound card (if you have a built-in sound chip). If the POST completed successfully without detecting any problems with then system will play a single short beep to let you know the test is complete and the computer will continue to startup and load the operating system.

If during the POST the BIOS detects a problem it will normally display a visual error message on the monitor explaining what the problem is. However, if a problem is detected before the BIOS initializes the video card, or a video card is not present or not detected then the BIOS will play several 'BEEPS' through the speaker to let you know there is a problem. Depending on the type of the BIOS you have the BIOS may play beeps in a specific pattern to indicate what the problem is, or play the same beep a number of times indicating the problem. It is very important that you pay close attention to the number and/or pattern of the beeps your computer plays on startup.

Below is a table of the most common AMI, Phoenix and Award BIOS beep codes.

AMI (American Megatrends International) BIOS Beep Codes.
AMI BIOS uses beeps of the same length and pitch. The error is displayed as a number of beeps. For example, 4 beeps indicated a timer failure.

BEEP CODE

MEANING

POSSIBLE CAUSE

1 Beep (No video)

Memory refresh failure

Bad memory

2 Beeps

Memory parity error

Bad memory

3 Beeps

Base 64K mem failure

Bad memory

4 Beeps

Timer not operational

Bad motherboard

5 Beeps

Processor error

Bad processor

6 Beeps

8042 Gate A20 failure

Bad CPU or Motherboard

7 Beeps

Processor exception

Bad processor

8 Beeps

Video memory error

Bad video card or memory

9 Beeps

ROM checksum error

Bad BIOS

10 Beeps

CMOS checksum error

Bad motherboard

11 Beeps

Cache memory bad

Bad CPU or motherboard


Award BIOS Beep Codes
Award BIOS uses beeps of varying duration. A long beep will typically last for 2 seconds while a short beep will last only 1 second. Award BIOS also uses beeps of different frequency to indicate critical errors. If an Award BIOS detects that the CPU is overheating it may play a high pitched repeating beep while the computer is running.

BEEP CODE

MEANING

POSSIBLE CAUSE

1 Long, 2 Short

Video adapter failure

Bad video adapter

Repeating (Endless loop)

Memory error

Bad memory or bad connection

1 Long, 3 Short

Video adapter failure

Bad video adapter or memory

High freq. beeps (while running)

CPU is overheating

CPU fan failure

Repeating High, Low beeps

CPU failure

Bad processor


Phoenix BIOS Beep Codes

Phoenix BIOS uses beep code patterns to indicate problems. In the table below the '-' indicates a brief pause between beeps.

Example: 1 - 1 - 2 would sound like BEEP BEEP BEEP BEEP

BEEP CODE

MEANING

POSSIBLE CAUSE

1 - 1 - 2

CPU / motherboard failure

Bad CPU / motherboard

1 - 1 - 3

CMOS read/write failure

Bad motherboard

1 - 1 - 4

BIOS ROM failure

Bad BIOS chip

1 - 2 - 1

Timer failure

Bad motherboard

1 - 2 - 2

DMA failure

Bad motherboard

1 - 2 - 3

DMA failure

Bad motherboard

1 - 3 - 1

Memory refresh failure

Bad memory

1 - 3 - 2

64K memory failure

Bad memory

1 - 3 - 3

64K memory failure

Bad memory

1 - 3 - 4

64K memory failure

Bad memory

1 - 4 - 1

Address line failure

Bad memory

1 - 4 - 2

Parity error

Bad memory

1 - 4 - 3

Timer failure

Bad motherboard

1 - 4 - 4

NMI port failure

Bad motherboard

2 - 1 - 1

64K memory failure

Bad memory

2 - 1 - 2

64K memory failure

Bad memory

2 - 1 - 3

64K memory failure

Bad memory

2 - 1 - 4

64K memory failure

Bad memory

2 - 2 - 1

64K memory failure

Bad memory

2 - 2 - 2

64K memory failure

Bad memory

2 - 2 - 3

64K memory failure

Bad memory

2 - 2 - 4

64K memory failure

Bad memory

2 - 3 - 1

64K memory failure

Bad memory

2 - 3 - 2

64K memory failure

Bad memory

2 - 3 - 3

64K memory failure

Bad memory

2 - 3 - 4

64K memory failure

Bad memory

2 - 4 - 1

64K memory failure

Bad memory

2 - 4 - 2

64K memory failure

Bad memory

2 - 4 - 4

64K memory failure

Bad memory

2 - 4 - 4

64K memory failure

Bad memory

3 - 1 - 1

Slave DMA failure

Bad motherboard

3 - 1 - 2

Master DMA failure

Bad motherboard

3 - 1 - 3

Interrupt controller failure

Bad motherboard

3 - 1 -4

Slave IC failure

Bad motherboard

3 - 2 -2

Interrupt Controller failure

Bad motherboard

3 - 2 - 4

Keyboard control failure

Bad motherboard

3 - 3 - 1

CMOS batter failure

Bad CMOS battery

3 - 3 - 2

CMOS configuration error

Incorrect setting

3 - 3 - 4

Video memory failure

Bad video card or memory

3 - 4 - 1

Video init failure

Bad video card or memory

4 - 2 - 1

Timer failure

Bad motherboard

4 - 2 - 2

CMOS shutdown failure

Bad motherboard

4 - 2 - 3

Gate A20 failure

Bad motherboard

4 - 2 - 4

Unexpected interrupt

Bad processor

4 - 3 - 1

RAM test failure

Bad memory

4 - 3 - 3

Timer failure

Bad motherboard

4 - 3 - 4

RTC failure

Bad motherboard

4 - 4 - 1

Serial port failure

Bad motherboard

4 - 4 - 2

Parallel port failure

Bad motherboard

4 - 4 - 3

Coprocessor failure

Bad motherboard or CPU.

9 - 2 - 1

Video adapter incompatibility

Use a different brand of video card

Saturday, July 21, 2007

Windows XP Myth

Myth Definition - "A fiction or half-truth, especially one that forms part of an ideology." There are numerous Myths floating around the Internet regarding Windows XP, especially relating to Optimizations and Security.

Myth - "Windows XP requires a high end PC to install and run."

Reality - "Windows XP can be installed on surprisingly low system requirements contrary to popular opinion. With the average life cycle of a regular PC being roughly 4-6 years, just about any PC being used today can run Windows XP. The following requirements are Microsoft's "official" minimum system requirements which I have tested to work fine with the exception of only 64 MB of RAM (performance is poor). Increasing your RAM to 128 MB would be the only upgrade I would strongly consider as my absolute minimum Windows XP system requirements."

233 MHz CPU (300 MHz Recommended) *
128 MB Recommended (64 MB of RAM minimum supported, limits performance and some features) *
1.5 GB of available hard disk space *
Super VGA (800 x 600) or higher-resolution video adapter and monitor
CD-ROM or DVD drive
Keyboard and Microsoft Mouse or compatible pointing device

download this e-book to read more. Click here

Google Hacks!!




ever wonder how people works in google? watch this clip

download e-books on google hacks here.Worth a reading though!!

Macgyver



remember this series?..he's one of my childhood heroes!!
download the unofficial Macgyver How-To Handbook here

It's All About The Pentiums

Successful negotiations - 7 easy steps

Whether you covet a new job, a raise, a business deal, a new car, some new bling, or need to rectify a problem with a loved one, the ability to play ‘deal maker’ is your secret weapon to achieving the result you want. In my opinion, one of the greatest strengths of very successful business people is their ability to out negotiate with others to achieve their desired result. Negotiating doesn’t need to be back and forth, point-counterpoint banter. I’ve found that the most proficient negotiators manage these conversations in such a way that the other party likely does not even know they are engaged in a bargaining process. The bottom line is simple: if there is something you want that is in someone else’s control, knowing how to negotiate will stack the odds in your favor. The key is to be tough but fair.


1. First and foremost, be prepared to walk away. This is single most
important strategy to getting what you want out of life. If you aren’t prepared to
say, “No” and mean it; then you are likely to end up settling for a lesser
outcome. Before entering into the negotiation, know in advance exactly what you
are and are not willing to concede, so that you do not need to process this
information on-the-fly without adequate time to weigh the pros and cons of
each.

2. Know when to forego all together. A good deal comes together quickly – a
bad deal takes way too long. Take a clue from the amount of time it’s taking to
get what you want. If you have to “force it,” chances are it will come back to bite
you later on.

3. Deal at the right level. Nothing is more frustrating than trying to do a deal
with an individual who can’t make the final decision. It’s like negotiating against
yourself – you address an issue and try to come to a conclusion and then the
other person takes that to someone else “behind the scenes” only to come back
and say it can’t be done on those terms. It’s far more efficient and effective to
find the right person to negotiate with directly, “(wo)mano y (wo)mano.”

4. Due diligence to come prepared. The more information you have
surrounding the circumstances of your endeavor, the “marketplace,” for example,
the more likely you are to not only prevail, but also get the best deal possible.
While you may actually prevail by shooting in the dark, not knowing the extent of
the opportunity could result in your leaving a lot on the table. Whether it’s the
average pay for a given job, the price typically paid for a product or a service, or
who you are in competition with for a new position – knowledge is truly power.

5. Don’t take anything personally. To maintain objectivity, treat every
negotiation as if you are doing a deal for someone else who has hired you as the
professional “closer.” When you allow yourself to get emotionally involved,
rational thought often goes by the wayside and you’re far more likely to concede
to your later regret. Cool heads get the best, and most, out of what they are
seeking.

6. Anticipate objections. Prior to the negotiation, brainstorm all the reasons or
objections that may prevent you from getting what you want – and prepare a
thoughtful counterpoint for each, one at a time. During a negotiation, people
conjure all sorts of reasons why something can’t be done, many of which are
often bogus. Until you know the valid sticking point, you are just spinning your
wheels.

7. Don’t underestimate Karma. What goes around indeed comes around. The
best deal is one where both parties walk away feeling positive about the result of
the negotiation. The worst deal is that where one side leaves the table feeling

Wednesday, July 18, 2007

Monitoring Physical Threats in the Data Center

Traditional methodologies for monitoring the data center environment are no longer sufficient. With technologies such as blade servers driving up cooling demands and regulations such as Sarbanes-Oxley driving up data security requirements, the physical environment in the data center must be watched more closely. While well understood protocols exist for monitoring physical devices such as UPS systems, computer room air conditioners, and fire suppression systems, there is a class of distributed monitoring points that is often ignored. This paper describes this class of threats, suggests approaches to deploying monitoring devices, and provides best practices in leveraging the collected data to reduce downtime.

download this e-book to readmore

INFORMATION ON VIRUS

1. How to create a sample file virus file ?

This particular codes is taken from www.eicar.org. It is meant for virus test file BUT it doesn't have any effect on your computer.

STEP 1
You can type this code below : X5O!P%@AP[4PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

STEP 2
Save it into eicar.com.txt using notepad.

STEP 3
Rename this file to eicar.com, and your antivirus will detect this as a virus.

2. How to test this code HEURISTICALLY ?

You can change some of the codes as below :

Smith1.Txt
X5O!P%@AP[4PZX54(P^)7CC)7}$EICAR-STANDING-ANTIVIRUS-TEST-FILE!$H+H*
(Changed STANDARD to STANDING)

Smith2.Txt
X5O!P%@AP[4PZX54(P^)7CC)7}$EICON-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*
(Changed Eicar to Eicon)

Smith3.Txt
X5O!P%@AP[4PZX54(P^)7CC)7}$EICON-STANDING-ANTIVIRUS-TEST-FILE!$H+H*
(Changed EICAR to EICON, and STANDARD to STANDING)

Smith4.Txt
X5O!P%@AP[4PZX54(P^)7CC)7}$BALLZ-STINDORK-ANTISACKS-TEST-FORK!$H+H*
(Random Words)

Smith5.Txt
X5O!P%@AP[4PZX54(P^)7CC)7}$!$H+H*
(Completely removed text string)

Smith6.Txt
X5O!P%@AP[42233PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*
(Additional Numbers added to binary)

Smith7.Txt
X5O!P%@AP[42233PZX54(P^)7CC)7}$RAIC-TARNDARD-ILIKESMOKE-TUST-FULE!$H+H*
(Inserted Random letters with addition numbers added into binary)

Smith8.Txt
X5O22!P%@AP[4PZX5422(P^)7CC)7}$!$H+H*
(Removed text string, inserted 22 twice into string to break up signature)

Command AV 4.90.4 Results:
Started scan: 6/14/2004 4:33:03 PM

C:DownloadsSmithTestSmith1.txt Infection: EICAR_Test_File.unknown?
C:DownloadsSmithTestSmith2.txt Infection: EICAR_Test_File (exact)
C:DownloadsSmithTestSmith3.txt Infection: EICAR_Test_File.unknown?
C:DownloadsSmithTestSmith4.txt Infection: EICAR_Test_File.unknown?
C:DownloadsSmithTestSmith5.txt Infection: New or modified variant of Trivial
C:DownloadsSmithTestSmith6.txt Infection: New or modified variant of Trivial
C:DownloadsSmithTestSmith7.txt Infection: New or modified variant of Trivial
C:DownloadsSmithTestSmith8.txt Infection: New or modified variant of Trivial

3. How antivirus works?

Antivirus scans all files (executables and non-executrable files) looking for a pattern or virus signature. If the pattern is found, then the file will be cleaned. The pattern is in HEX form e.g EA779078... (I juz make this one out for example sake).

Actual example of hex codes or sometimes known as footprint codes are listed below (NOTE: Ox means the number is in HEX format; so if 0x57 means 57 in hex)
(1) Stoned virus [stoned]
 0x00 0x53 0x41 0x52 0x06 0x56 0x57 0xbe
(2) Ping Pong virus - version B [Ping]
&nbsp0xa1 0xf5 0x81 0xa3 0xf5 0x7d 0x8b 0x36 0xf9 0x81
(3) Friday 13th virus [Fri13]
&nbsp0xb4 0x4f 0xcd 0x21 0x73 0xf7 0x58

Actually, a binary file (executable file) or document (e.g. MS Word document) can be read easily by opening the file with the flag 'rb' (read binary). You can see the content in HEX. You can try do a project to simulate the output like in Ethereal. If you read MS Word document, you can see it in ASCII or HEX, but if the file is already secured with a PASSWORD, then you cannot see anything that can be understood.

You can also see the content of a file easily by downloading a free software called FileAnalyzer, very easy to use and I recommend that u try it.