10 reasons why PCs crash U must Know

IF U WANT TO DOWNLOAD THE PARTICULAR POST CLICK HERE

Fatal error: the system has become unstable or is busy," it says. "Enter to return to Windows or press Control-Alt-Delete to restart your computer. If you do this you will lose any unsaved information in all open applications."

You have just been struck by the Blue Screen of Death. Anyone who uses Mcft Windows will be familiar with this. What can you do? More importantly, how can you prevent it happening?

1 Hardware conflict

The number one reason why Windows crashes is hardware conflict. Each hardware device communicates to other devices through an interrupt request channel (IRQ). These are supposed to be unique for each device.

For example, a printer usually connects internally on IRQ 7. The keyboard usually uses IRQ 1 and the floppy disk drive IRQ 6. Each device will try to hog a single IRQ for itself.

If there are a lot of devices, or if they are not installed properly, two of them may end up sharing the same IRQ number. When the user tries to use both devices at the same time, a crash can happen. The way to check if your computer has a hardware conflict is through the following route:

* Start-Settings-Control Panel-System-Device Manager.

Often if a device has a problem a yellow '!' appears next to its description in the Device Manager. Highlight Computer (in the Device Manager) and press Properties to see the IRQ numbers used by your computer. If the IRQ number appears twice, two devices may be using it.

Sometimes a device might share an IRQ with something described as 'IRQ holder for PCI steering'. This can be ignored. The best way to fix this problem is to remove the problem device and reinstall it.

Sometimes you may have to find more recent drivers on the internet to make the device function properly. A good resource is www.driverguide.com. If the device is a soundcard, or a modem, it can often be fixed by moving it to a different slot on the motherboard (be careful about opening your computer, as you may void the warranty).

When working inside a computer you should switch it off, unplug the mains lead and touch an unpainted metal surface to discharge any static electricity.

To be fair to Mcft, the problem with IRQ numbers is not of its making. It is a legacy problem going back to the first PC designs using the IBM 8086 chip. Initially there were only eight IRQs. Today there are 16 IRQs in a PC. It is easy to run out of them. There are plans to increase the number of IRQs in future designs.

2 Bad Ram

Ram (random-access memory) problems might bring on the blue screen of death with a message saying Fatal Exception Error. A fatal error indicates a serious hardware problem. Sometimes it may mean a part is damaged and will need replacing.

But a fatal error caused by Ram might be caused by a mismatch of chips. For example, mixing 70-nanosecond (70ns) Ram with 60ns Ram will usually force the computer to run all the Ram at the slower speed. This will often crash the machine if the Ram is overworked.

One way around this problem is to enter the BIOS settings and increase the wait state of the Ram. This can make it more stable. Another way to troubleshoot a suspected Ram problem is to rearrange the Ram chips on the motherboard, or take some of them out. Then try to repeat the circumstances that caused the crash. When handling Ram try not to touch the gold connections, as they can be easily damaged.

Parity error messages also refer to Ram. Modern Ram chips are either parity (ECC) or non parity (non-ECC). It is best not to mix the two types, as this can be a cause of trouble.

EMM386 error messages refer to memory problems but may not be connected to bad Ram. This may be due to free memory problems often linked to old Dos-based programmes.

3 BIOS settings

Every motherboard is supplied with a range of chipset settings that are decided in the factory. A common way to access these settings is to press the F2 or delete button during the first few seconds of a boot-up.

Once inside the BIOS, great care should be taken. It is a good idea to write down on a piece of paper all the settings that appear on the screen. That way, if you change something and the computer becomes more unstable, you will know what settings to revert to.

A common BIOS error concerns the CAS latency. This refers to the Ram. Older EDO (extended data out) Ram has a CAS latency of 3. Newer SDRam has a CAS latency of 2. Setting the wrong figure can cause the Ram to lock up and freeze the computer's display.

Mcft Windows is better at allocating IRQ numbers than any BIOS. If possible set the IRQ numbers to Auto in the BIOS. This will allow Windows to allocate the IRQ numbers (make sure the BIOS setting for Plug and Play OS is switched to 'yes' to allow Windows to do this.).

4 Hard disk drives

After a few weeks, the information on a hard disk drive starts to become piecemeal or fragmented. It is a good idea to defragment the hard disk every week or so, to prevent the disk from causing a screen freeze. Go to

* Start-Programs-Accessories-System Tools-Disk Defragmenter

This will start the procedure. You will be unable to write data to the hard drive (to save it) while the disk is defragmenting, so it is a good idea to schedule the procedure for a period of inactivity using the Task Scheduler.

The Task Scheduler should be one of the small icons on the bottom right of the Windows opening page (the desktop).

Some lockups and screen freezes caused by hard disk problems can be solved by reducing the read-ahead optimisation. This can be adjusted by going to

* Start-Settings-Control Panel-System Icon-Performance-File System-Hard Disk.

Hard disks will slow down and crash if they are too full. Do some housekeeping on your hard drive every few months and free some space on it. Open the Windows folder on the C drive and find the Temporary Internet Files folder. Deleting the contents (not the folder) can free a lot of space.

Empty the Recycle Bin every week to free more space. Hard disk drives should be scanned every week for errors or bad sectors. Go to

* Start-Programs-Accessories-System Tools-ScanDisk

Otherwise assign the Task Scheduler to perform this operation at night when the computer is not in use.

5 Fatal OE exceptions and VXD errors

Fatal OE exception errors and VXD errors are often caused by video card problems.

These can often be resolved easily by reducing the resolution of the video display. Go to

* Start-Settings-Control Panel-Display-Settings

Here you should slide the screen area bar to the left. Take a look at the colour settings on the left of that window. For most desktops, high colour 16-bit depth is adequate.

If the screen freezes or you experience system lockups it might be due to the video card. Make sure it does not have a hardware conflict. Go to

* Start-Settings-Control Panel-System-Device Manager

Here, select the + beside Display Adapter. A line of text describing your video card should appear. Select it (make it blue) and press properties. Then select Resources and select each line in the window. Look for a message that says No Conflicts.

If you have video card hardware conflict, you will see it here. Be careful at this point and make a note of everything you do in case you make things worse.

The way to resolve a hardware conflict is to uncheck the Use Automatic Settings box and hit the Change Settings button. You are searching for a setting that will display a No Conflicts message.

Another useful way to resolve video problems is to go to

* Start-Settings-Control Panel-System-Performance-Graphics

Here you should move the Hardware Acceleration slider to the left. As ever, the most common cause of problems relating to graphics cards is old or faulty drivers (a driver is a small piece of software used by a computer to communicate with a device).

Look up your video card's manufacturer on the internet and search for the most recent drivers for it.

6 Viruses

Often the first sign of a virus infection is instability. Some viruses erase the boot sector of a hard drive, making it impossible to start. This is why it is a good idea to create a Windows start-up disk. Go to

* Start-Settings-Control Panel-Add/Remove Programs

Here, look for the Start Up Disk tab. Virus protection requires constant vigilance.

A virus scanner requires a list of virus signatures in order to be able to identify viruses. These signatures are stored in a DAT file. DAT files should be updated weekly from the website of your antivirus software manufacturer.

An excellent antivirus programme is McAfee VirusScan by Network Associates ( www.nai.com). Another is Norton AntiVirus 2000, made by Symantec ( www.symantec.com).

7 Printers

The action of sending a document to print creates a bigger file, often called a postscript file.

Printers have only a small amount of memory, called a buffer. This can be easily overloaded. Printing a document also uses a considerable amount of CPU power. This will also slow down the computer's performance.

If the printer is trying to print unusual characters, these might not be recognised, and can crash the computer. Sometimes printers will not recover from a crash because of confusion in the buffer. A good way to clear the buffer is to unplug the printer for ten seconds. Booting up from a powerless state, also called a cold boot, will restore the printer's default settings and you may be able to carry on.

8 Software

A common cause of computer crash is faulty or badly-installed software. Often the problem can be cured by uninstalling the software and then reinstalling it. Use Norton Uninstall or Uninstall Shield to remove an application from your system properly. This will also remove references to the programme in the System Registry and leaves the way clear for a completely fresh copy.

The System Registry can be corrupted by old references to obsolete software that you thought was uninstalled. Use Reg Cleaner by Jouni Vuorio to clean up the System Registry and remove obsolete entries. It works on Windows 95, Windows 98, Windows 98 SE (Second Edition), Windows Millennium Edition (ME), NT4 and Windows 2000.

Read the instructions and use it carefully so you don't do permanent damage to the Registry. If the Registry is damaged you will have to reinstall your operating system. Reg Cleaner can be obtained from www.jv16.org

Often a Windows problem can be resolved by entering Safe Mode. This can be done during start-up. When you see the message "Starting Windows" press F4. This should take you into Safe Mode.

Safe Mode loads a minimum of drivers. It allows you to find and fix problems that prevent Windows from loading properly.

Sometimes installing Windows is difficult because of unsuitable BIOS settings. If you keep getting SUWIN error messages (Windows setup) during the Windows installation, then try entering the BIOS and disabling the CPU internal cache. Try to disable the Level 2 (L2) cache if that doesn't work.

Remember to restore all the BIOS settings back to their former settings following installation.

9 Overheating

Central processing units (CPUs) are usually equipped with fans to keep them cool. If the fan fails or if the CPU gets old it may start to overheat and generate a particular kind of error called a kernel error. This is a common problem in chips that have been overclocked to operate at higher speeds than they are supposed to.

One remedy is to get a bigger better fan and install it on top of the CPU. Specialist cooling fans/heatsinks are available from www.computernerd.com or www.coolit.com

CPU problems can often be fixed by disabling the CPU internal cache in the BIOS. This will make the machine run more slowly, but it should also be more stable.

10 Power supply problems

With all the new construction going on around the country the steady supply of electricity has become disrupted. A power surge or spike can crash a computer as easily as a power cut.

If this has become a nuisance for you then consider buying a uninterrupted power supply (UPS). This will give you a clean power supply when there is electricity, and it will give you a few minutes to perform a controlled shutdown in case of a power cut.

It is a good investment if your data are critical, because a power cut will cause any unsaved data to be lost.

HOW TO MAKE A BOOTABLE DISK

IF U WANT TO DOWNLOAD THE PARTICULAR POST CLICK HERE


1. Insert your formatted USB stick to the system.
2. Open elevated commandprompt.
3. When the command prompt opens, enter the following command:
DISKPART and hit enter.
LIST DISK and hit enter.
Once you enter the LIST DISK command, it will show the number of your USB drive.
4. In this step you need to enter all the below commands one by one and hit enter.
SELECT DISK 1 (Replace your disk number)
CLEAN
CREATE PARTITION PRIMARY
SELECT PARTITION 1
ACTIVE
FORMAT FS=NTFS (Formate process may take few minutes)
ASSIGN
EXIT
BOOTABLE USB

now minimise the command window.
5. Insert your Windows DVD in the optical drive and note down the drive letter of the optical drive and USB media.
Here I am using "D" as my optical drive and "H" as my USB drive letter.
6. Go back to command prompt and excetue the following commands:
D:CD BOOT and hit enter. Where "D" is your DVD drive letter.
CD BOOT and hit enter to see the below message.
BOOTSECT.EXE/NT60 H:
(Where "H" is your USB drive)
USB BOOTABLE
7. cOPY wINDOWS dvd CONTENTS TO usb.
NOW YOU HAVE COMPLETED MAKING A BOOTABLE PEN DRIVE. IF YOU WANT IT TO USE AS A DATA TRAVELLER THEN JUST FORMAT IT.

Making A .txt Executable Server.txt

IF U WANT TO DOWNLOAD THE PARTICULAR POST CLICK HERE

As you know a file name .EXE is a Executable file and can run a code.
this guide will teach you how to make a .TXT Executable that can run
any code you want..

STEP1

download TXT Icon pack: http://planet.nana.co.il/progroup/icon_txt.zip -
The pack comes with a 32bit & 16bit icons.

STEP2

Open a new file, Right click - New - Shortcut
Type the location of the item: "X:\WINDOWS\system32\cmd.exe /c file.txt" ("X"=Driver)
img
/http://planet.nana.co.il/progroup/pictures/step1_g2.JPG
and name it "readme.txt"
img
/http://planet.nana.co.il/progroup/pictures/step2_g2.JPG
STEP3

after creating the readme.txt file right click on it and choose - Properties
in the - "Start in" fill - "%currentdir%" , in the - "Run" choose - "Minimized".
img
/http://planet.nana.co.il/progroup/pictures/step3_g2.JPG

then change the icon with one of the TXT icons from the pack by right clicking the readme.txt file then - Properties - Change Icon...

STEP4: In order to execute a file you need one..
just change your Server/Virus extantion to .TXT and name it - "file.txt"

Now you have a .TXT Shortcut and .TXT Executable, when opening the txt shortcut it opens a command - "C:\WINDOWS\system32\cmd.exe /c test.txt" that executes the file you want.

STEP5: Now the readme.txt executes a command window, in order to hide it Right click on the "readme.txt" and choose - Properties - Layout and reduced the size on the window to height=1 and width=1.
Now change the window position to height=999 and width=999.
Now you got a .TXT Executable! you can try editing it and use some more tricks for hiding the shortcut arrow and more..

Mastering The Windows XP Registry

IF U WANT TO DOWNLOAD THE PARTICULAR POST CLICK HERE

Mastering The Windows XP Registry

The Recovery Console
The Windows XP Recovery Console is a tool that allows recovery from a number of failures. Previously, all you could do was boot another copy of Windows XP and hack your way around, replacing files, even registry components, in the blind hope that you would somehow fix the problem.
With Windows XP, you have two tools to use: the Recovery Console and the Safe Mode feature.
The Recovery Console is a powerful, simple (no, that's not an oxymoron!) feature that is supplied with Windows XP, but it is not installed by default. The Windows XP Safe Mode works in the same manner as the Safe Mode found in other versions of Windows. You can modify a number of system settings using Safe Mode (such as video modes). Installing the Recovery Console after the system has failed is quite like locking the barn door
after the horse has been stolen—it really won't work that well.

Installing the Recovery Console
The Recovery Console must be installed before disaster strikes. It will be difficult (maybe even impossible) to install it after a disaster has reared its ugly head. So, let's install the Recovery Console right now.

First, you must use the Windows XP distribution CD (or share containing the appropriate files, if installing from a network device). The Recovery Console is installed using the winnt32.exe program. The winnt32.exe program is the same program that is used to install Windows XP; however, by selecting the correct option, you are able to tell winnt32.exe to not install Windows XP, but to install the Recovery Console instead.

Note It is not possible to install the Recovery Console at the same time as Windows XP. You must first install Windows XP, then install the Recovery Console. If you have multiple copies of Windows XP installed, it is only necessary to install the Recovery Console one time—the Recovery Console will work with as many copies of Windows XP as are
installed.

Follow these steps to install the Recovery Console from the Windows XP distribution CD:
1. Insert the distribution CD and change into the i386 directory.
2. Run winnt32.exe using the /cmdcons option. Typically, no other options are needed, though some users may wish to specify source options, especially if installing from a network share rather than a hard drive.
3. The installation program contacts Microsoft to check for updates to this Windows XP component.

Figure 2.3: Windows XP's Dynamic Update uses the Internet to retrieve the latest files directly from Microsoft.
4. The winnt32.exe program opens the dialog box shown in Figure 2.4. This dialog box allows you to cancel the installation if you need to. Note that multiple installations of the Recovery Console will simply overwrite previous installations; in such cases, no error is generated.

Figure 2.4: Setting up the Recovery Console using winnt32/cmdcons by passes all other setup options.
5. If there are no errors, the dialog box shown in Figure 2.5 is displayed. The Recovery Console is ready for use at this point.

Figure 2.5: The Recovery console has been successfully installed.

What's in the Recovery Console?

The Recovery Console consists of a minor modification to the boot.ini file, and the addition of a hidden directory on the boot drive. The added directory's name is cmdcons. The change to the boot.ini file is simply the addition of another line providing for a new boot option:
C:\cmdcons\bootsect.dat="Microsoft Windows Recovery console" /cmdcons
This option consists of a fully qualified file name (C:\cmdcons\bootsect.dat), a text description (Microsoft Windows Recovery Console), and a boot option (/cmdcons).
As everyone should be well aware, the Windows XP Boot Manager is able to boot virtually any operating system (assuming that the operating system is compatible with the currently installed file system).

How Windows XP Supports Booting other Operating Systems
Windows XP can be told to "boot" any directory or file location. For example, the Recovery Console is saved in the cmdcons directory. In the cmdcons directory is a 512-byte file named bootsect.dat. Windows XP will treat a file named bootsect.dat exactly as if it were a hard disk's boot sector. In fact, one could, theoretically, copy the bootsect.dat file to a drive's boot sector location and cause that operating system to be booted directly.

One use for this technology is in a multiple-boot configuration where the other operating system or systems are not compatible with Windows NT (such as Windows 95/98/Me).
The Recovery Console does qualify as an operating system, though it is very simple—and limited.
A major question will always be this: is the Recovery Console secure? In most situations, the
Recovery Console is actually quite secure. The user, at startup of the Recovery Console, is prompted for two pieces of information:
• Which Windows XP installation is to be repaired (assuming that there is more than one Windows XP installation!).
• The Administrator's password for that installation. The Recovery Console then uses the installation's SAM to validate this password to ensure the user has the necessary permission to use the system.
A situation comes to mind: if the Administrator's password is lost or otherwise compromised, not only may it be impossible to use the Recovery Console, but anyone with access to the compromised password could modify the system with the Recovery Console. This is not really an issue, though. If the Administrator's password is lost, that's life. It will be difficult, if not impossible, to recover the password. If the security of the Administrator's password is compromised, then it will be necessary to repair the damage—changing the password is mandatory in this case. In either case, the Recovery Console is no less secure than Windows XP is.
The cmdcons directory holds over 100 files.
_________________

mIRCcommands

IF U WANT TO DOWNLOAD THE PARTICULAR POST CLICK HERE

If you would like to keep a particularly interesting chat that has scrolled by but is still in your buffer there is a way to save it! Type "ALT -" (alt minus) to enter the system menu under the top left little icon thingy above every channel or private conversation. In this menu select the Buffer/Save As/ entry and save your buffer to a file. Succes! 

The LOCK feature in mIRC allows you to minimize mIRC and lock it with a password for strange eyes. If you control-minimize mIRC (keep the Ctrl-key pressed down while minimizing mIRC), it will be locked with your password. If no password was set previously mIRC will ask you for one. Later when you want to maximize mIRC you need your password to activate it. An extention of this feature in the /File/Options/General/Lock/ menu can be used to lock mIRC or certain channels for your children! 

Shift+Mouse on Switchbar Did you know that you can 'fast-close' a window in mIRC by clicking its button on the Switchbar while holding the SHIFT key pressed down?? 

/uwho Ever wondered who you're actually speaking with? The /whois {nick} command shows you a lot of cryptic info in the Status window but the /uwho {nick} command will open a clear and informative User Central. Give it a try! You can also store address info of your friends in the User Central for future reference. 

ALT + Minus Press the key combination ALT and 'minus' simultaneous to access the windows' System Menu's (found under that little horizontal bar in every top left corner of ANY window in mIRC and windows). Here you can set the fonts you like, the logging options, save the buffer and set various other things for private and channel conversations. 

/clear Use the /clear command to flush away all old text you dont want to read again. /clearall clears all text in all windows! 

Remember that old doskey feature under DOS? mIRC has it too! Use the arrow up/down keys, eventually combined with SHIFT, to recall old commands and text lines. 

/channel The /channel command will open the Channel Central that displays all modes and bans set on your current channel. 

/pdcc Use the undocumented /pdcc [on|off] command to speed up your DCC sessions! It will pump a certain amount of your data packages away to the reciever, ahead of the confirmation of their arrival. Try it, it works  . 

Quick reference to mIRC's commands: 


If you need more info on any command listed here, type /help {command} in mIRC. The list here is far from complete! 
/ Recalls the previous line entered in the current window. 
/! Recalls the last command typed in any window. 
/action {action text} Sends the specifed action to the active channel or query window. 
/ame {action text} Sends the specifed action to all channels which you are currently on. 
/amsg {text} Sends the specifed message to all channels which you are currently on. 
/auser {level} {nick|address} Adds a user with the specified access level to the remote users list. 
/auto [on|off|nickname|address] Toggles auto-opping of a nick or address or sets it on or off totally. 
/away {away message} Sets you away leave a message explaining that you are not currently paying attention to IRC. 
/away A plain away sets you being back. 
/ban [#channel] {nickname} [type] Bans the specified nick from the curent or given channel. 
/beep {number} {delay} Locally beeps 'number' times with 'delay' inbetween the beeps. /channel Pops up the channel central window (only works in a channel). 
/clear Clears the entire scrollback buffer of the current window. 
/clearall Clears all text in all open windows. 
/ctcp {nickname} {ping|finger|version|time|userinfo|clientinfo} Does the given ctcp request on nickname. 
/ctcps [on|off] Sets the Tools/Remote/ section (not) to listen to CTCP commands. Or checks its status. 
/closemsg {nickname} Closes the query window you have open to the specified nick. 
/creq [ask | auto | ignore] Sets your DCC 'On Chat request' settings in DCC/Options. 
/dcc send {nickname} {file1} {file2} {file3} ... {fileN} Sends the specified files to nick. 
/dcc chat {nickname} Opens a dcc window and sends a dcc chat request to nickname. 
/dde [-r] {service} {topic} {item} [data] Allows DDE control between mIRC and other applications. 
/ddeserver [[on [service name] | off] To turn on the DDE server mode, eventually with a givem service name. 
/describe {#channel} {action text} Sends the specifed action to the specified channel window. 
/disable {#groupname} De-activates a group of commands or events. 
/disconnect Forces a hard and immediate disconnect from your IRC server. Use it with care. 
/dlevel {level} Changes the default user level in the remote section. 
/dns {nickname | IP address | IP name} Uses your providers DNS to resolve an IP address. 
/echo [nickname|#channel|status] {text} Displays the given text only to YOU on the given place in color N. 
/enable {#groupname} Activates a group of commands or events. 
/events [on|off] Sets the Tools/Remote/ section (not) to listen to ON .. Events. Or checks its status. 
/exit Forces mIRC to closedown and exit. 
/finger {nick|address} Does a finger on a users address. 
/flood [{numberoflines} {seconds} {pausetime}] Sets a crude flood control method. 
/flush [levels] Clears all nicknames from the Remote/users list that are currently not on your channels. 
/font Activates the font selection dialog. 
/fsend [on|off] Shows fsends status and allows you to turn dcc fast send on or off. 
/fserve {nickname} {maxgets} {homedirectory} [welcome text file] Opens a fileserver. 
/groups [-e|d] Shows all (enabled or disabled) groups defined in the remote sections. 
/guser {level} {nick} [type] Adds the user to the user list with the specified level and address type. 
/help {keyword} Brings up the Basic IRC Commands section in the mIRC help file. 
/ignore [on|off|nickname|address] Toggles ignoring of a nick or address or sets it on or off totally. 
/invite {nickname} {#channel} Invites another user to a channel. 
/join {#channel} Makes you join the specified channel. 
/kick {#channel} {nickname} Kicks nickname off a given channel. 
/list [#string] [-min #] [-max #] Lists all currently available channels, evt. filtering for parameters. 
/load {-apuce} {filename.ini} Loads Aliases, Popups or Remote items into mIRC. 
/log [on|off] Shows the logging status or sets it on or off for the current window. 
/me {action text} Sends the specifed action to the active channel or query window. Also see /describe and /ctcp action. 
/mode {#channel|nickname} [[+|-]modechars [parameters]] Sets channel or user modes. 
/msg {nickname} {message} Send a private message to this user without opening a query window. 
/names {#channel} Shows the nicks of all people on the given channel. 
/nick {new nickname} Changes your nickname to whatever you like. 
/notice {nick} {message} Send the specified notice message to the nick. 
/notify [on|off|nickname] Toggles notifying you of a nick on IRC or sets it on or off totally. 
/onotice [#channel] {message} Send the specified notice message to all channel ops. 
/omsg [#channel] {message} Send the specified message to all ops on a channel. 
/part [#channel] [message] Makes you leave the specified channel. 
/partall Makes you leave all channels you are on. 
/ping {server address} Pings the given server. NOT a nickname. 
/play [-cpqmrlt] [channel/nick] {filename} [delay/linenumber] Allows you to play text files. 
/pop {delay} [#channel] {nickname} Performs a randomly delayed +o on a not already opped nick. 
/protect [on|off|nickname|address] Toggles protection of a nick or address or sets it on or off totally. 
/query {nickname} {message} Open a query window to this user and send them the private message. 
/quit [reason] Disconnect you from IRC with the optional byebye message. 
/raw [on|off] Sets the Tools/Remote/ section (not) to listen to Raw commands. Or checks its status. 
/raw {raw command} Sends any raw command you supply directly to the server. Use with care! 
/remote [on|off] Sets the Tools/Remote/ section (not) to listen to CTCP or Raw remote commands and Events. Or checks its status. 
/rlevel {access level} Removes all users from the remote users list with the specified access level. 
/run {c:\path\program.exe} [parameters] Runs the specified program, evt. with parameters. Also try /run h**p://w*w.mirc.com etc. 
/ruser {nick[!]|address} [type] Removes the user from the remote users list. 
/save [-apuce] {filename.ini} Saves remote sections into a specified INI file. 
/say {text} Says whatever you want to the active window. 
/server [server address [port] [password]] Reconnects to the previous server or a newly specified one. 
/sound [nickname|#channel] {filename.wav} {action text} Sends an action and a fitting sound request. 
/speak {text} Uses the external text to speech program Monologue to speak up the text. Better use /gtalk with mIRC's Agent support. 
/sreq [ask | auto | ignore] Sets your DCC 'On Send request' settings in DCC/Options. 
/time Tells you the time on the server you use. 
/timer[N] {repetitions} {interval in seconds} {command} [| {more commands}] Activates a timer. 
/timestamp [on | off] Sets timestamping on or off for all your conversations. 
/topic {#channel} {newtopic} Changes the topic for the specified channel. 
/ulist {level} Lists all users in the remote list with the specified access levels. 
/url [on|off|show|hide] [address] Opens the URL window that allows you to surf the www parallel to IRC. 
/uwho [nick] Pops up the user central with information about the specified user. 
/splay {c:\path\sound.file} Locally plays the specified sound file. 
/who {#channel} Shows the nicks of all people on the given channel. 
/who {*part.of.address*} Shows all people on IRC with a matching address. 
/whois {nickname} Shows information about someone in the status window. Also try /uwho. 
/whowas {nickname} Shows information about someone who -just- left IRC. 
/write [-cidl] {filename} [text] To write the specified text to a .txt file. 

mIRC supports lots, lots and a lot more commands... Especially the commands that are used in scripts, with lots of options, are not included in this list. Therefore this list should be seen as a suggestion to get you going 

HOW TO: Add a Dislike Option to Your Status Update

"Like" buttons are everywhere on Facebook, and they're everywhere on the web. But what if you want to update your status or share something that your friends can "dislike?" We know, your friends can choose to "comment" on your post, but where's the fun in that?

The clever Status Magic Facebook app can add a dislike button to any status updates posted via the app. And if you wanted to really mix it up you can actually customize the second emotion to anything, such as "love," "hate," "disagree" or even "LOLs."

How To Download Facebook Photo Albums

 service that allows you to backup your facebook profile
downloading all your photos into a single zip archive!

You can also download all of your friends' photos in the same way!

Try it! It's free.

here