Firefox 3 about:config hacks

Firefox 3 one of the maximum downloaded open source browser which has set a Guinness world record. Their were Over 8,000,000 downloads in 24 hours!. Along with Firefox 3 Spreadfirefox also got new cool look.

Firefox 3 about:config file is the core configuration file of Firefox. By editing about:config file we can get amazing hacks for Firefox 3. Firefox allows the users to change many preferences in the about:config file so it’s totally ethical to do it.Here is list of 21 Firefox 3 hacks & tweaks.

To get the Firefox 3 configuration file type “about:config” at address bar.
Firefox 3 about:config hacks

Here is List of about:config hacks for Firefox 3

1) Disable Extension Compatibility Checks
extensions.checkCompatibility = False
extensions.checkUpdateSecurity = False

2) Location Bar (Set number Auto Complete URL at Address Bar)

This is a good hack to trim down that huge auto-complete list on your URL bar. By default it displays maximum 12 URL

browser.urlbar.maxRichResults = #

Enter Number at # (3,10,12 etc)

3) Stop Displaying Website Icon (Favicon) in Address bar & On Tab

browser.chrome.site_icons = False

4) Disable Prefetch (Helpful for frequent Google searcher, low-speed internet connection or low RAM)

network.prefetch-next = False

5) Extend Spell check to forms

layout.spellcheckDefault = 2
Change Value from 1 to 2

6) Disable Blinking Text

browser.blink_allowed = False

7) Speed Tweaks

network.http.pipelining false to true
network.http.pipelining.maxrequests 30 to 8
network.http.max-connections 30 to 96
network.http.max-connections-per-server 15 to 32
network.http.max-persistent-connections-per-server 6 to 8
network.http.pipelining.ssl false to true
network.http.proxy.pipelining false to true

8 ) Disable Annoying Browser Behavior

dom.disable_window_open_feature.menubar
dom.disable_window_move_resize
dom.disable_window_open_feature.titlebar
dom.disable_window_open_feature.toolbar

Set all of above to value False

9) Remove Tab Close Button from all Tab and set A single Close Button at Right
Remove Tab Close Button
Remove Tab Close Button

browser.tabs.closeButtons = 3

Single Close Button to control all Firefox Opened Tabs. (value should be 3 and not 2 Thanks Andreas )

10) Disabler Browser Toolbar Tip

browser.chrome.toolbar_tips = False

11) Show More Tabs on Single Firefox Window before Scrolling

browser.tabs.tabMinWidth = 75

Setting lesser value with reduce Tab width

12) Past Copy Content with Middlemouse Click

middlemouse.paste = True

13) Scroll webpage in One Go

mousewheel.withaltkey.action=1

14) Disable Delay Time While Installing Firefox Add-on

security.dialog_enable_delay = 0

(Zero is number of seconds Firefox should wait while installing Add-on)

15) Increase History Undo Close Tab Limit ( Recently Closed Tabs )
Increase History Undo Close Tab Limit

browser.sessionstore.max_tabs_undo=15

By default you can undo 10 recently closed tabs inorder to increase your history closed tabs. Change number 13 to as per your choice.

16) Open Firefox Default Search Bar Result in New Tab

browser.search.openintab=True

17) Right Click View Source in Your Favorite Editor

view_source.editor.external=True
view_source.editor.path= Path of Editor

(e.g. path C:\Program Files\npp.4.8.2.bin\notepad++.exe)

18) Enable/Disable Single Click to Select Whole URL in Address bar
Single Click Select URL Select

To Enable Single Click Select URL of address bar use the below about:config Tweak

browser.urlbar.clickSelectsAll = True

To disable Single Click Select

browser.urlbar.clickSelectsAll = False

19) Emule/ed2k link association (Linux users)

network.protocol-handler.app.ed2k= /usr/bin/ed2k
network.protocol-handler.external.ed2k = true

20) Fast Scrolling Across Tabs
Fast Scrolling Across tabs

toolkit.scrollbox.scrollIncrement =75

( 75 is number of pixels to scroll at a time when scrolling the tab strip’s scrollbox. (Default: 20)

21) Auto Complete URL while You type at address Bar
Auto Complete URL

browser.urlbar.autoFill=True

Many of above about:config hacks are available in Older Firefox Version, at the end if some thing goes wrong then feel free to restore your about:config to older setting see the below image of how to restore about:config
Restore Firefox about:config

Hope you guys like this Firefox 3 hacks, If you have any tips or hacks related to Firefox 3 about:config, hacks, tweaks do let me know I will include it in above list.

Check out 9 Fix for Firefox 3 Crashes and Hang Problem.

Posted by Sandip | June 22, 2008 .

Browse the Free Removal Tools

Bitdefender has very nice collection of dedicated free tools to remove specific viruses.

here is link

http://www.bitdefender.com/site/Downloads/browseFreeRemovalTool/

Travel without the laptop

Nice article highlighting apps that can be used to carry aps.

Coolest Firefox Tricks

Coolest Firefox Tricks

Everybody’s favorite open-source browser, Firefox, is great right out of the box. And by adding some of the awesome extensions available out there, the browser just gets better and better.
But look under the hood, and there are a bunch of hidden (and some not-so-secret) tips and tricks available that will crank Firefox up and pimp your browser. Make it faster, cooler, more efficient. Get to be a Jedi master with the following cool Firefox tricks.
1) More screen space. Make your icons small. Go to View - Toolbars - Customize and check the “Use small icons” box.
2) Smart keywords. If there’s a search you use a lot (let’s say IMDB.com’s people search), this is an awesome tool that not many people use. Right-click on the search box, select “Add a Keyword for this search”, give the keyword a name and an easy-to-type and easy-to-remember shortcut name (let’s say “actor”) and save it. Now, when you want to do an actor search, go to Firefox’s address bar, type “actor” and the name of the actor and press return. Instant search! You can do this with any search box.
3) Keyboard shortcuts. This is where you become a real Jedi. It just takes a little while to learn these, but once you do, your browsing will be super fast. Here are some of the most common (and my personal favs):

• Spacebar (page down)
• Shift-Spacebar (page up)
• Ctrl+F (find)
• Alt-N (find next)
• Ctrl+D (bookmark page)
• Ctrl+T (new tab)
• Ctrl+K (go to search box)
• Ctrl+L (go to address bar)
• Ctrl+= (increase text size)
• Ctrl+- (decrease text size)
• Ctrl-W (close tab)
• F5 (reload)
• Alt-Home (go to home page)

4) Auto-complete. This is another keyboard shortcut, but it’s not commonly known and very useful. Go to the address bar (Control-L) and type the name of the site without the “www” or the “.com”. Let’s say “google”. Then press Control-Enter, and it will automatically fill in the “www” and the “.com” and take you there - like magic! For .net addresses, press Shift-Enter, and for .org addresses, press Control-Shift-Enter.

5) Tab navigation. Instead of using the mouse to select different tabs that you have open, use the keyboard. Here are the shortcuts:

• Ctrl+Tab (rotate forward among tabs)
• Ctrl+Shft+Tab (rotate to the previous tab)
• Ctrl+1-9 (choose a number to jump to a specific tab)

6) Mouse shortcuts. Sometimes you’re already using your mouse and it’s easier to use a mouse shortcut than to go back to the keyboard. Master these cool ones:

• Middle click on link (opens in new tab)
• Shift-scroll down (previous page)
• Shift-scroll up (next page)
• Ctrl-scroll up (decrease text size)
• Ctrl-scroll down (increase text size)
• Middle click on a tab (closes tab)

7) Delete items from address bar history. Firefox’s ability to automatically show previous URLs you’ve visited, as you type, in the address bar’s drop-down history menu is very cool. But sometimes you just don’t want those URLs to show up (I won’t ask why). Go to the address bar (Ctrl-L), start typing an address, and the drop-down menu will appear with the URLs of pages you’ve visited with those letters in them. Use the down-arrow to go down to an address you want to delete, and press the Delete key to make it disappear.

8)User chrome. If you really want to trick out your Firefox, you’ll want to create a UserChrome.css file and customize your browser. It’s a bit complicated to get into here, but check out this tutorial.
9) Create a user.js file. Another way to customize Firefox, creating a user.js file can really speed up your browsing. You’ll need to create a text file named user.js in your profile folder (see this to find out where the profile folder is) and see this example user.js file that you can modify. Created by techlifeweb.com, this example explains some of the things you can do in its comments.
10) about:config. The true power user’s tool, about.config isn’t something to mess with if you don’t know what a setting does. You can get to the main configuration screen by putting about:config in the browser’s address bar. See Mozillazine’s about:config tips and screenshots.

11) Add a keyword for a bookmark. Go to your bookmarks much faster by giving them keywords. Right-click the bookmark and then select Properties. Put a short keyword in the keyword field, save it, and now you can type that keyword in the address bar and it will go to that bookmark.
12) Speed up Firefox. If you have a broadband connection (and most of us do), you can use pipelining to speed up your page loads. This allows Firefox to load multiple things on a page at once, instead of one at a time (by default, it’s optimized for dialup connections). Here’s how:

• Type “about:config” into the address bar and hit return. Type “network.http” in the filter field, and change the following settings (double-click on them to change them):
• Set “network.http.pipelining” to “true”
• Set “network.http.proxy.pipelining” to “true”
• Set “network.http.pipelining.maxrequests” to a number like 30. This will allow it to make 30 requests at once.
• Also, right-click anywhere and select New-> Integer. Name it “nglayout.initialpaint.delay” and set its value to “0″. This value is the amount of time the browser waits before it acts on information it receives.

13) Limit RAM usage. If Firefox takes up too much memory on your computer, you can limit the amount of RAM it is allowed to us. Again, go to about:config, filter “browser.cache” and select “browser.cache.disk.capacity”. It’s set to 50000, but you can lower it, depending on how much memory you have. Try 15000 if you have between 512MB and 1GB ram.
14) Reduce RAM usage further for when Firefox is minimized. This setting will move Firefox to your hard drive when you minimize it, taking up much less memory. And there is no noticeable difference in speed when you restore Firefox, so it’s definitely worth a go. Again, go to about:config, right-click anywhere and select New-> Boolean. Name it “config.trim_on_minimize” and set it to TRUE. You have to restart Firefox for these settings to take effect.
15) Move or remove the close tab button. Do you accidentally click on the close button of Firefox’s tabs? You can move them or remove them, again through about:config. Edit the preference for “browser.tabs.closeButtons”. Here are the meanings of each value:

• 0: Display a close button on the active tab only
• 1:(Default) Display close buttons on all tabs
• 2:Don’t display any close buttons
• 3:Display a single close button at the end of the tab bar (Firefox 1.x behavior)

thanks to W5A

Douwe Osinga Blog

One of very interesting blogs that I like. Check the Google Hacks section.

http://douweosinga.com/

Make ur Internet n Bandwidth Rapid - Rapid Speeds 100%

1.Increase bandwidth by tweaking QoS in Windows XP Pro

The following tweak applies only to Windows XP Professional edition.

The default system behavior is that all 100% bandwidth is available, however, if there is a running application that indicates to the OS it needs to send high priority/real time data, then as long as it has the socket open, Windows XP will restrict “best effort” traffic to 80% of the bandwidth so that high priority traffic can be accommodated. Basically, applications can make this request to the operating system for QoS support using the QoS application programming interfaces (APIs) in Windows and this only applies if a specific app is requesting QoS.

If you'd like to change how much bandwidth is reserved for QoS (the default is 20% of the total bandwidth), do the following:

1. Make sure you're logged in as "Administrator" (not just any account with admin privileges).
2. Navigate to START>Run and type: gpedit.msc
3. Navigate to Local Computer Policy > Administrative Templates > Network > QOS Packet Scheduler
4. In the right window, double-click the limit reservable bandwidth setting
5. On the setting tab, check the enabled setting.
6. Where it says "Bandwidth limit %", change it to read 0 (or whatever percentage you want to reserve for high priority QoS data)
7. Click OK, close gpedit.msc

Under START > My Computer > My Network Connections > View Network Connections, right-click on your connection and under Properties (where it lists your protocols), make sure QOS Packet Scheduler is enabled.



The tweak desribed below helps boost priority for DNS & hostname resolution in general. What this means is, it helps web pages load faster, and has negligible effect on downloads (not counting the couple of ms gain with the host resolution at connect-time).

Applying this tweak assumes some proficiency in editing the Windows Registry using Regedit (Start > Run > type: regedit). As always, backup your Registry before making any changes so you can revert to the previous state if you don't like the results.


2.Host Resolution Priority Tweak
host name resolution priority
Windows 2k/XP

First, open the Windows Registry using Regedit, and (after backing up) navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ServiceProvider



Note the following lines (all hex dwords):
Class = 008 (8) - indicates that TCP/IP is a name service provider, don't change.

LocalPriority = 1f3 (499) - local names cache
HostsPriority = 1f4 (500) - the HOSTS file
DnsPriority = 7d0 (2000) - DNS
NetbtPriority = 7d1 (2001) - NetBT name-resolution, including WINS

What we're aiming to do is increase the priority of the last 4 settings, while keeping their order. The valid range is from -32768 to +32767 and lower numbers mean higher priority compared to other services. What we're aiming at is lower numbers without going to extremes, something like what's shown below should work well:

Change the "Priority" lines to:
LocalPriority = 005 (5) - local names cache
HostsPriority = 006 (6) - the HOSTS file
DnsPriority = 007 (7) - DNS
NetbtPriority = 008 (8) - NetBT name-resolution, including WINS

Windows 9x/ME

The tweak is essentialy the same as in Windows 2000/XP, just the location in the Registry is slightly different. For a more detailed description see the Windows 2000/XP section above.

Open the Windows Registry using Regedit, and (after backing up) navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\ServiceProvider

You should see the following settings:
Class=hex:08,00,00,00

LocalPriority=hex:f3,01,00,00
HostsPriority=hex:f4,01,00,00
DnsPriority=hex:d0,07,00,00
NetbtPriority=hex:d1,07,00,00

The "priority" lines should be changed to:
LocalPriority=hex:05,00,00,00
HostsPriority=hex:06,00,00,00
DnsPriority=hex:07,00,00,00
NetbtPriority=hex:08,00,00,00

Reboot for changes to take effect.


In addition to the tweaks already covered in Win 2k/XP Registry Tweaks and More Win 2k/XP Tweaks, the Windows XP Service Pack 2 introduces a few new issues covered in the article below. Please make sure you understand what you are doing before making any changes to your Operating System. Note the information below only applies to Windows XP Service Pack 2.



3.Remove the limit on TCP connection attempts

Windws XP SP2 introduces a few new twists to TCP/IP in order to babysit users and "reduce the threat" of worms spreading fast without control. In one such attempt, the devs seem to have limited the number of possible TCP connection attempts per second to 10 (from unlimited in SP1). This argumentative feature can possibly affect server and P2P programs that need to open many outbound connections at the same time.

Rant: The forward thinking of Microsoft developers here is that you can only infect 10 new systems per second via TCP/IP ?!?... If you also consider that each of those infected computers will infect 10 others at the same rate:
second 1: 1+10 computers
second 2: 10+10*10 computers (110 new ones)
second 3: 10+100*10 computers ( 1110 new ones)
second 4: 10+1000*10 computers (11110 new ones)
....
all the way to 10*60 + 10^60 computers in a single minute (that's a number with 60 digits, or it would far exceed Earth's population). Even if we consider that 90% of those computers are unreachable/protected, one would still reach ALL of them within a minute.

In other words, even though it is not going to stop worm spreading, it's going to delay it a few seconds, limit possible network congestion a bit, and limit the use of your PC to 10 connection attempts per second in the process ! I have no problem with the new default setting limiting outbound connection attempts. Still, users should have the option to easily disable or change this setting. I might be going out on a limb here, but ever since the introduction of Windows XP I can't help thinking that I dislike all the bult-in Windows "wisardry" in a sense that the system also limits user access. That irritating trend to ease the mental load on end users is somewhat insulting, considering that Windows is to make the more "intelligent" choice instead of the end user, as well as limit their access to tuning such settings...
End of rant.

With the new implementation, if a P2P or some other network program attempts to connect to 100 sites at once, it would only be able to connect to 10 per second, so it would take it 10 seconds to reach all 100. In addition, even though the setting was registry editable in XP SP1, it is now only possible to edit by changing it directly in the system file tcpip.sys. To make matters worse, that file is in use, so you also need to be in Safe mode in order to edit it.

You only need to worry about the number of connection attempts per second if you have noticed a slowdown in network programs requiring a number of connections opened at once. You can check if you're hitting this limit from the Event Viewer, under System - look for TCP/IP Warnings saying: "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". Keep in mind this is a cap only on incomplete outbound connect attempts per second, not total connections. Still, running servers and P2P programs can definitely be affected by this new limitation. Use the fix as you see fit.

To change or remove the limit, you can use the following program:

Event ID 4226 Patcher v2.11

Code:

http://www.speedguide.net/files/xp_sp2/EvID4226Patch211a-en.zip

- A patching program for removing or changing the limit imposed on connection attempts in SP2. The patcher has the ability to restore tcpip.sys back to the original... Still, you might want to back up tcpip.sys, use it at your own risk. The author of this patch can be reached @ http://www.lvllord.de/

4. Recommended settings for Windows 2000 / XP
Windows 2000 & XP, unlike NT supports large windows as described in RFC1323 ( the 'RcvWindow' has a maximum value of 2**30 rather than 64K), and includes some other improvements over its predecessors you can use to speed up any TCP/IP transfers. , the descriptions and other options are added to provide you with better understanding and enable you to customize your settings.

All the following entries, unless otherwise noted should be placed in the Windows 2000/XP Registry under the key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

TCPWindowSize

The value of TCP Window in the Windows 2000 Registry is DWORD, representing number of bytes, with range from 0 to 2^30. The recommended values (in red) optimize TCP for any high speed Internet connection and work best in most cases, however if you'd like to use a custom value follow these guidelines:

For best results, the TCPWindow should be a multiple of MSS (Maximum Segment Size). MSS is generally MTU - 40, where MTU (Maximum Transmission Unit) is the largest packet size that can be transmitted. MTU is usually 1500 (1492 for PPPoE connections). To determine the MTU value of your ISP, check out the Advanced Registry Editing section of our site.

There are three places in the Windows 2000 Registry where you can add the TCP Window parameter.

HKLM/SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
GlobalMaxTcpWindowSize="256960" (DWORD, number of bytes) Valid range is from MSS to 2^30. Add the value as a decimal. Note: For best results RWIN has to be a multiple of MSS lower than 65535 times a scale factor that's a power of 2, i.e. 44 x 1460 = 64240 x 2^2 = 256960. If you choose to use a RWIN lower than 65535, you can simply make it multiple of MSS and turn scaling off (Tcp1323Opts=0)

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
TcpWindowSize="256960" (DWORD, number of bytes) Valid range is from MSS to 2^30. Add the value as a decimal. TcpWindowSize can also exist under TcpipParametersInterface - if added at this location, it overrides the global setting for this particular . Note (10/20/00): Seems MS has found another bug in Windows 2000, the TCPWindowSize should be configured with the global setting (GlobalMaxTcpWindowsSize) rather than this one - Q263088

Note: For best results RWIN has to be a multiple of MSS lower than 65535 times a scale factor that's a power of 2, i.e. 44 x 1460 = 64240 x 2^2 = 256960. If you choose to use a RWIN lower than 65535, you can simply make it multiple of MSS and turn scaling off (Tcp1323Opts=0)

Tcp1323Opts

Tcp1323Opts is a necessary setting in order to enable Large TCPWindow support as described in RFC 1323. Without this parameter, the TCPWindow is limited to 64K.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Tcp1323Opts="1" (DWORD, recommended setting is 1. The possible settings are 0 - Disable RFC 1323 options, 1 - Window scaling but no Timestamp options, 3 - Window scaling and Time stamp options.)

Note: Tcp1323Opts="3" might help in some cases where there is increased packet loss, however generally you'll achieve better throughput with Tcp1323Opts="1", since Timestamps add 12 bytes to the header of each packet.

DefaultTTL

DefaultTTL determines the time in seconds and the number of hops a packet lives. While it does not directly affect speed, a larger value increases the amount of time it takes for a packet to be considered lost, discarded and retransmitted. A value that's too small can cause packets to be unable to reach distant servers at all.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
DefaultTTL="64" (DWORD, recommended setting is 64. Other settings that are widely used are 128 and 32)

EnablePMTUDiscovery

When set to 1 (True), TCP attempts to discover MTU automatically over the path to a remote host. Setting this parameter to 0 causes MTU to default to 576 which reduces overall performance over high speed connections. Note that this setting is different than our Windows 9x recommendation.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
EnablePMTUDiscovery="1" (DWORD - boolean, valid settings are 0-->False and 1-->True. Many connections perform better with this entry at 1, however, if you prefer to set your upstream to send fixed 1500 packets, you might want to use 0 instead). When set at 1, establishing connections and initial transfer speed might slow down a bit, however you will get better throughput if somewhere in the path large packets need to be fragmented.

EnablePMTUBHDetect

Setting this parameter to 1 (True) enables "black hole" routers to be detected, however it also increases the maximum number of retransmissions for a given segment. In most cases you'd want to keep BHDetect to 0 (False).

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
EnablePMTUBHDetect="0" (DWORD - boolean, valid settings are 0-->False and 1-->True. Recommended setting is 0)

SackOpts

This parameter controls whether or not SACK (Selective Acknowledgement) support is enabled, as specified in RFC 2018. SACK is especially important for connections using large TCP Window sizes.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
SackOpts="1" (DWORD - boolean, recommended setting is 1. Possible settings are 0 - No Sack options or 1 - Sack Option enabled).

TcpMaxDupAcks

This parameter determines the number of duplicate ACKs that must be received for the same sequence number of sent data before "fast retransmit" is triggered to resend the segment that has been dropped in transit.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
TcpMaxDupAcks="2" (DWORD - range 1-3, recommended setting is 2).



Patches


This Includes

1. sguide_tweak_2k.zip
Description: Generic patch for Windows XP and Windows 2000 (all versions). This patch will optimize your TCP/IP Registry settings for high speed Internet connections. To install, extract the .inf file first, then double-click (or right-click on filename and choose install from the pull-down menu) and reboot for changes to take effect.

Code:

http://www.speedguide.net/files/sguide_tweak_2k.zip

2.sguide_tweak_2k_pppoe.zip

Description: Generic patch for Windows XP/2000 and DSL connections using PPPoE. This patch will optimize your TCP/IP Registry settings for high speed Internet connections. It is specifically designed for PPPoE DSL connections. To install, extract the .inf file first, then double-click (or right-click on filename and choose install from the pull-down menu) and reboot for changes to take effect.

Code:

http://www.speedguide.net/files/sguide_tweak_2k_pppoe.zip

3. winxp_dnscache.zip

Description: Patch Windows 2k/XP not to cache failed DNS entries. By default, when a DNS lookup fails (due to temporary DNS problems), Windows still caches the unsuccessful DNS query, and in turn fails to connect to a host regardless of the fact that the DNS server might be able to handle your lookup seconds later. This patch fixes the problem by configuring the DNS client to continue sending queries to an unresponsive network. To install, save to your HD, unzip the .reg file, then double-click the filename.

Web Patches - faster loading of Web Pages

The following patch increases Web page loading speed, by doubling the number of possible concurrent open connections. For example, imagine a web page has 20 images and some text - in order for your browser to get all these files, it opens 2 or 4 concurrent connections, depending on the Web server. Increasing the number of open connections allows for faster retrieving of the data. Please note that the patch sets some values outside of the HTML specs. If you decide to install it, backup your Registry first. Changes will take effect after you reboot. Download the patch appropriate for your OS:

OS: Windows 9x/ME

Code:

http://www.speedguide.net/files/sg_webtweak_9x.zip

OS: Windows 2K/XP/2k3

Code:

http://www.speedguide.net/files/sg_webtweak_2k.zip

TCP OPTIMISER

Please reupload this image to another image host:

http://img414.imageshack.us/img414/31/tcpoptimizer12es.png

Description: The TCP Optimizer is a free, easy Windows program that provides an intuitive interface for tuning and optimizing your Internet connection. Just download and run, there is no installaion required. The program makes it easy to find the best MTU and RWIN values, test latency and tweak all the important broadband related registry parameters. The Optimizer can be helpful with tuning any Internet connection type, from dialup to Gigabit+

Code:

URL http://www.speedguide.net/files/TCPOptimizer.exe

ENJOY !!!!!!!!!!

Thanks to Warez-BB.org

CRUSH

rIP is a reverse IP tool. It takes a hostname or IP address as input and returns all the vhosts running on the same IP address.

http://crushmachine.com/rip.php