Google Chrome has now eclipsed Mozilla Firefox in the speed category. However, I still use Firefox as my main web browser because it is still better than Chrome in certain areas.
But just recently, I tried a few tweaks that significantly improved the speed of Firefox making it a little bit snappier than the latest version of Google Chrome when loading webpages.
Here are some of the things that I did that helps make Firefox somewhat faster than Chrome:
1. Type about:config into the Firefox URL/address bar and hit ENTER. You will be warned that you might void your warranty if you change some advanced settings, but just go on and trust me 
2. Inside the Firefox configuration page, scroll down and look for the following entries: network.http.pipelining network.http.proxy.pipelining Set their values to “true” by double-clicking each one of them.
3. Next up, find this entry: network.http.pipelining.maxrequests Double-click and set the value to 8.
4. Right-click anywhere inside the config page and select New –> Integer. Name it nglayout.initialpaint.delay and set the value to “0″. Continued…
Posted in Support Tips.
Tagged with firefox, firefox speed.
By Vinanth, Practice Lead
– May 18, 2010
HandsFree Networks with its small footprint and automated support features offer various ways for a user to perform asset and site management. All information are stored in SQL databases and through the use of the Dashboard, Query module and Notifications many tasks are performed by accessing the databases.
HandsFree Networks helps Managed Service Providers and other Infrastructure management companies to perform asset change monitoring through its asset change module. It enables a user to understand the hardware and software changes that take place. The Software Provisioning and Metering module helps to keep track of the number of times and amount of times a software application has been used. Continued…
Posted in Product Features.
Tagged with IT Business Solution, Managed Services, Support Automation.
By Kavita Sarma
– May 11, 2010
The growing demand and need for IT infrastructure manged services has also seen a rise in the demand for secured communication between components of the infrastructure. Companies, both SMBs or Enterprise ITs, are now much more concerned and inclined on security of data and systems while delivering services. These companies also look forward for a tool that can give them a comprehensive management or monitoring of changes to a device.
HandsFree Networks support automation tool provides secured data communication and ensures that there is no unauthorized access to the end-user’s system. HandsFree Networks uses state-of art mechanisms such as MD5 Hashing for event logging, DART configuration & execution. Continued…
Posted in Product Features.
Tagged with Managed Services, Restricting logon access, secured communication.
By Kavita Sarma
– April 22, 2010
HFN is highly scalable because it has a peer-to-peer architecture and relies on technologies such as distributed databases and TCP/IP networking that is highly scalable.
HFN management applications are built around distributed SQL database technology. Event log records are stored in account tables. The definition of account is highly flexible. Any subset of IP addresses can be defined as an account. In addition, the ReSOFT server has a multi-tier account structure that lets you define accounts that mirror an organization’s physical and organizational structure. These mechanisms, combined with distributed SQL database technology, make the HFN server a highly scalable facility.
The HFN client has a peer-to-peer architecture. Initially, inter-client awareness is limited to a single sub-net corresponding to a class C sub-net. The only operation that involves all HFN clients on a sub-net is when the HFN clients check on each other. This activity takes place when the clients first start. Some DART/Scrip go through the list of HFN clients, and when they do that, the underlying routine actually makes sure the HFN client is still there (one at a time). The first operation (startup) is the only broadcast operation.
Execution of symptom detection, diagnosis and resolution, and system management and maintenance activities does not depend on a central location. A copy of the HFN client that performs all of these activities resides on every supported device and the DART /Scrip (automated procedures) database is replicated on every device.
Resolution of the vast majority of symptoms that occur on a network involves at most a handful of devices. Because the HFN client has a peer-to-peer architecture, clients can co-operate to resolve multi-device symptoms efficiently. For example, symptoms involving print server failures whose diagnosis is performed by the HFN client on the print server and then communicated to the HFN client on the device where the failure was detected.
At the same time, resolution of a symptom on a shared resource takes place only once. The first HFN client that detects the symptom initiates the diagnosis, and executes the resolution. In this way, HFN clients on other devices will either not detect the symptom at all or will be limited to detecting it.
HFN is highly scalable because it has a peer-to-peer architecture and relies on technologies such as distributed databases and TCP/IP networking that is highly scalable.
HFN management applications are built around distributed SQL database technology. Event log records are stored in account tables. The definition of account is highly flexible. Any subset of IP addresses can be defined as an account. In addition, the ReSOFT server has a multi-tier account structure that lets you define accounts that mirror an organization’s physical and organizational structure. These mechanisms, combined with distributed SQL database technology, make the HFN server a highly scalable facility.
- The HFN client has a peer-to-peer architecture. Initially, inter-client awareness is limited to a single sub-net corresponding to a class C sub-net. The only operation that involves all HFN clients on a sub-net is when the HFN clients check on each other. This activity takes place when the clients first start. Some DART/Scrip go through the list of HFN clients, and when they do that, the underlying routine actually makes sure the HFN client is still there (one at a time). The first operation (startup) is the only broadcast operation. Continued…
Posted in Product Features.
Tagged with scalability.
By Santanu Das, Pre-Sales Consultant
– April 13, 2010
Ever wondered taking a system backup would be easy and without user intervention. Currently the trend which is being followed by a technician would be a huge task to accomplish a complete system Backup.Taking a system backup is important these days as the desktop are prone to viruses, trojans, malware or BSOD which could actually crash a system where all the important data’s are lost and the only way to get them back is by periodic backup. Continued…
Posted in Best Practices, Support Tips.
Tagged with BackUp, Desktop Backup.
By Tharun Kumar, Tipster
– March 20, 2010
Recent Comments