Goole Wave – more like a drop!

26 10 2009

On Fri evening I got an Google Wave invite that has taken the internet discussion forums by tide. Everyone seem to have gone hyper over it. So naturally I was very excited and accepted the invite and logged in right away. I was greated with an empty three panel screen… The welcome wave arrived few min later.. Clicked on my contacts. Empty! Tried to send a mail … well’ I can’t. I can send it to only those in my Contact!

Later I learn that I can communicate only within the wave community. Thats a huge restriction. It would take ages for everyone to get the wave invite and even longer for every one to be sufficiently interested to start using it. Since Wave is all on the cloud, many folks who are not online all the time will find it very unusable.

I tried to send a mail from my work Id and GMail, but they never show up in my googlewave a/c. Later I learn that no outside communication is allowed for now. Hope google fixes that first thing.

So, I decieded to form my cummunity and sent invite to some of my tech savvy and must be family members, including  my 8 yr old daughter. Unlike the GMail invite, the wave invites are not sent right away. I don’t know if Google reviews the receipients for “wave worthyness”. So, two days into having wave a/c, I feel like an drop with no one to talk to. wired!


Tomorrow’s world

26 05 2009

Happen to catch this documentory on Discovery channel. Some of the techs covered ..

  • Realestate
    • air and sea
  • Smart Dust : tiny computing, communicating devices all over the city
  • Personal long/short distance travel
    • JetPack
    • Viper
    • Highways in Sky
    • Underwater flying
    • Squba car
  • Geo Browser
    • Google Earth, street view
  • Telepresense
    • Cisco Emerging technologies
    • Cisco Health Presense
    • Transporting presense
  • Alternate Power
    • Pizo electricity
  • Water Purifier
    • SlingShot
  • Alternate agriculture
    • Skyfarm
  • Planet killers (asteroids)
    • seed vault
  • Anti Aging
    • Gene


20 01 2009

While looking for some TB pluggins, stumbled on ScribeFire. Seem like a very promissing pluggin. I was able to connect to my tech blog within seconds and adding this post from ScribeFire.

Enabling Hibernate in Windows Vista

19 01 2009

Most popular tip seem to be to run powercfg /hibernate on from cmd (run as Admin). But this did n’t work for me.

However turning off the Hybrid mode worked.

Personalize -> Screen Saver -> Changer Power Settings -> Change when the computer sleeps -> Change advanced power settings -> Sleep ->Allow hytbrid sleep -> Settings [Off] .

Now did anyone say Vista was user friendly ?


Here is a blog with screen shots.


22 05 2008

300px-Keplers_supernovaNow thats some news … Sure we live in intersting times.

More on SuperNova at Wikipedia.

Putting the Sansa into Recovery Mode

25 03 2008
While updating mp3 tags with Linux (mp3info), I think I disconnected the device prematurely and it screwed the mp3 ID3 tags and possibly the file system. The player keeps rebooting while refreshing database.
While googling around found this useful (but unsafe) tip.
From time to time there may be a reason to put your Sansa into Recovery Mode. This is one of the four USB modes that the Sansa has, which is used for fixing most problems with the Sansa.
SANSA Sandisk
  • Turn the hold switch so that the orange is showing.
  • Hold the REC button on the side of the Sansa.
  • While holding the REC button, press the power button.
  • After the SanDisk logo appears, it should say “Welcome to Recovery Mode”.
  • After this appears, you may release the REC button. If the Sansa goes to the firmware, it is most likely because the REC button wasn’t held in far enough, and you must repeat these steps.

File Descriptions

  • Firmware file
    • Often called PP5022.MI4, this is the file that controls most of the Sansa, with the exception of when it turns on.
    • When using the Hebrew firmware, this file must be (re)named to firmware.mi4, which is case sensitive.
    • The latest firmware may be downloaded from the Manual Firmware Download thread
  • Bootloader File
    • Often called BL_SD_BOARDSUPPORTSD.ROM, this is the file that tells the Sansa to load the firmware file. The bootloader file also contains the Recovery Mode.
    • When using the Hebrew firmware, this file must be (re)named to pribootLoader.rom, which is also case sensitive.
    • The bootloader almost never needs to be replaced, and a bad or corrupt bootloader may result in the need to use e200tool, a very low level tool.
  • sansa.fmt
    • This file, though normally not used, can be placed on the Recovery Mode drive to format the main partition, which stores all of the music.
    • This file is often used to fix most problems that aren’t fixed by replacing the firmware, such as a music file that is corrupt, which occasionally causes the Refresh Database ‘window’ to freeze.
    • This file’s extension must be fmt. The full filename can not be sansa.fmt.txt or similar, and must only be sansa.fmt
  • Other files
    • Unless it is noted in the Manual Firmware Download thread that another file must be included for the firmware to work, do not add any other files to the Recovery Mode drive
    • Do not, under any circumstances, place a file ending in ‘.bin’ on the Recovery Mode drive.
    • If in doubt about placing any other files besides the firmware (and possibly bootloader) onto the Recovery Mode drive, PM a Sansa moderator, who should be able to help you.

“Load main image failed, switch to recovery mode” error
This error, the most common reason for using Recovery Mode, happens when the firmware is corrupt. Corrupt firmware can not harm your Sansa. In addition, it is fairly easy to fix:

  • Download a copy of the latest firmware, such as from theManual Firmware Download thread.
  • With the Sansa in Recovery Mode, save the mi4 file to the 16MB-FORMAT drive. Rename the mi4 file to PP5022.mi4, if it is not already.
  • Do not copy any other files over. The 16MB-FORMAT is not for storing music and other files. The only files that can be copied over are the bootloader, firmware, and sansa.fmt files
  • If you are using the Hebrew firmware, you may need to rename the firmware file to firmware.mi4 (case sensitive).
  • Disconnect your Sansa.

Sansa Freezes on Database Refresh
This problem is also fairly common, and usually occurs when an MP3 file is corrupt, and causes the database refresh to freeze. It also is fairly easy to fix:

  • Turn off your Sansa, if you haven’t already. If needed, hold the power button for 20 seconds to force it off.
  • Place your Sansa in recovery mode by following the steps above.
  • Place the sansa.fmt file in Recovery Mode. Please note placing this file in Recovery Mode will format your Sansa. That means it will delete all your music that is stored on it.
  • Remove your Sansa, and wait for it to format.
  • Turn off hold, restart Sansa (if needed) and
  • Done

Latest Sansa e200 firmware: (Sansa) Rockbox Build:
Site | Download | Old Builds | Thread
My PM box fills up too fast it seems – feel free to email me if you have any questions.

Resizing disk in Vista

6 01 2008

Control Panel->Computer Managament->Storege->Disk Management

Select the drive, right click and select Shrink/Expand Volume

 If Vista would n’t allow you to shrink C:, disable Snapshot (restore points).

Control Panel->System->System Protection

Uncheck C: and Apply

To resize/move Page file

Control Panel > System > Advanced system settings > Advanced tab | Performance Settings > Advanced tab | Virtual Memory Change > UNCHECK “Automatically manage paging file size for all drivers

Select the drive where you would like the new page file to go and either fill in “Custom Size” or “System managed size” and click on “Set”.


Select the drive where the present page file is (ie. C drive) and select “No paging file size” and click on “Set”.


ps. The quickest way to bring up the Advanced System Properties tab is
{Windows Key} > type “systempropertiesadvanced”