Skip to main content

Easy Green way to Cool a Laptop using a Bath Towel or Tissue paper.

Laptops get hot after long use. As they old, they get hotter; and sooner. Sometimes, working in a room with AC running doesn't even help. What makes the situation worse, they shutdown after getting extremely hot. Buying a USB laptop cooler pad is one solution. But here is a simple DIY, that can save you money and your laptop those extra amps.

Here is a simple yet powerful solution to it. No – not the "cleaning the processor fan fins" tip.

image image
  • Take a Tissue Paper / Bath towel.
  • Dampen it with cold water. Make sure you remove all of the excess water.
  • Take a flat board to support your laptop's bottom. If your laptop is an "always on desktop replacement", you can use the table it is resting on.
  • Keep the dampened paper/towel on it.
  • Make two or three bars of cardboard (about 1/2 inch wide, length to cover your laptop, considerable height)
  • Keep the laptop on the dampened towel using the bars to elevate it a little.

The fans running on the laptop use the moisture to cool the temperature by staying close to it. Depending upon the dampness and the volume of moisture, the laptop will stay cool for a long time, before it starts to get hot. Just re-dampen when the cloth becomes hot.

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour...

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value> ...