॥ स्वक्ष ॥

To content | To menu | To search

Tag - Kvetch

Entries feed - Comments feed

2011 July 13 [Wednesday]

E-filing IncomeTax returns in india

The Indian government agency that runs the Income-Tax portal  "incometaxindiaefiling.gov.in" has very thoughtfully provided an electronic filing facility for its citizens which enables all tax-payers to file their Tax returns without a trip to the local Income Tax Office. However, their thoughtfulness only extends to Windows users as they have provided the e-forms only in the MSOffice .xls format which will not run any macros on a non-Windows platform. Now, I have not used Windows for many years now and having been forced to pay for a half-baked edition pre-installed on my laptop, I could not wait for my warranty to finish and free up that disk space.

Last week, I found two Open-Office hacks for the ITR forms 1 and 2 at:

However, the Open-Office  supported ITR-2 form from KSEB is borked -- has locked cells which will not work nor retrieve macros in Open-Office and many fields and cells are protected, making it impossible to enter data so that the Tax macros work properly. The ITR-2 form (available from the above link) has some errors in the conversion for Open Office --In Part B - TI in Computation of total income. It does not allow you to enter any figures in the following fields:

1. Salaries (6 of Schedule S)
2. Income from house property (C of Schedule-HP) (Enter nil if loss)
3. Capital gains
4. Income from other sources
This prevents the macro from tabulating the Total (Example: A + B +Total of (I) for all fields), due to which its not possible to tabulate the final tax payable.

Does anyone know how to get locked cell macros to work in Open-Office? All help and pointers to get these hacks working on Open-Office would be a big help. TIA.

PS: FWIW, I had asked this question on the local LUG list, which was a waste as one list member, who didnt read the question, chose to focus his undivided attention on the terrible mistake I made -- used the word  'company'. Thereafter, it was a fun exercise in "I-am-the-loudest-jerk-and-bully-here" ad hominem and logical fallacies. Yeah, total WIN on the technical help scale. The smartz knocked my socks off! 

2011 April 4 [Monday]

b0rked Broadcom bcm43xx drivers

Dear Broadcom, Despite your late gesture of opensourcing the bcm43xx wireless drivers, I continue to have issues -- Last week a kernel upgrade from lucid not only broke the driver but managed to kill the nvidia drivers for good measure -- it was easier to take a data backup and do a clean re-installation of Lucid than waste a lot of time figuring out how your bcm43xx driver broke the nvidia drivers killing my graphics display totally. 

However, I was mistaken about it being a kernel upgrade (to 2.6.35) issue as the peace lasted for hardly 3 days -- since I am blessed with having to start my monday morning troubleshooting your broken hardware drivers (on 2.6.32-21 generic kernel version) instead of getting actual work done.
 
lucid@ubuntu:~$ dpkg --list |grep b43
ii  b43-fwcutter             1:012-1build1          Utility for extracting Broadcom 43xx firmwar

lucid@ubuntu:~$ dpkg --list |grep bcmwl
ii  bcmwl-modaliases       5.60.48.36+bdcom-0ubuntu3       Modaliases for the Broadcom 802.11 Linux STA

So the "b43-fwcutter" utility package exists on my system (as I had installed and activated the drivers) but something between each reboot was blocking the drivers as the link would suddenly be hard blocked. This despite me taking the trouble to NOT upgrade from the 2.6.32-21 generic kernel version.

Then, I checked the B43 blacklisted file:

lucid@ubuntu:~$ cat /etc/modprobe.d/* | egrep '8180|acx|at76|ath|b43|bcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|witch|wl'
# which ath5k cannot recover. To prevent this condition, stop
blacklist ath_pci
blacklist eth1394
# replaced by p54pci
blacklist prism54
# replaced by b43 and ssb.
blacklist bcm43xx
blacklist uart6850
blacklist twl4030_wdt

and sure enough, "bcm43xx" was indeed on the blacklist.....nice, girdle up for more yakshaving!

Next, I paid a visit to the "blacklist.conf" file and commented out the line "blacklist bcm43xx".

Rebooted for it to take effect. Nada, Zilch, still no wifi.

lucid@ubuntu:/lib/firmware/b43$ ls
a0g0bsinitvals5.fw  a0g1bsinitvals13.fw  a0g1initvals5.fw     b0g0bsinitvals9.fw  lp0bsinitvals13.fw  lp0initvals14.fw    n0initvals11.fw  ucode14.fw
a0g0bsinitvals9.fw  a0g1bsinitvals5.fw   a0g1initvals9.fw     b0g0initvals13.fw   lp0bsinitvals14.fw  lp0initvals15.fw    pcm5.fw          ucode15.fw
a0g0initvals5.fw    a0g1bsinitvals9.fw   b0g0bsinitvals13.fw  b0g0initvals5.fw    lp0bsinitvals15.fw  n0absinitvals11.fw  ucode11.fw       ucode5.fw
a0g0initvals9.fw    a0g1initvals13.fw    b0g0bsinitvals5.fw   b0g0initvals9.fw    lp0initvals13.fw    n0bsinitvals11.fw   ucode13.fw       ucode9.fw

lucid@ubuntu:~$ cd /lib/firmware/brcm
bash: cd: /lib/firmware/brcm: No such file or directory


Then, a sudo ln -s bcm43xx-0-610-809-0.fw bcm43xx-0.fw and sudo ln -s bcm43xx_hdr-0-610-809-0.fw bcm43xx_hdr-0.fw should have loaded and activated the drivers after a reboot. It did not, forcing me to switch to a wired connection on a laptop. WTF!

Broadcom, fiddling with "bcm43xx" is a sure-fire way to kill time. Thankyou very much for the Yak-shaving experience --it serves as a constant reminder to me, why I will never (unknowingly) buy another Broadcom driven product in future, ever! KTHXBAI.

UPDATE:: Its a "networking disabled on boot" bug in Ubuntu-Lucid and Maverick that has a fix (but not yet committed for Maverick):
[0] http://ubuntuforums.org/showthread.php?t=1594577
[1] https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/524454
[2] https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#Installing%20b43%20drivers
[3] http://www.qc4blog.com/?p=857

I've tried everything mentioned in the above threads to no avail. Wifi is out cold!

2011 February 22 [Tuesday]

beware of spammers asking for your account password

If you've got a mail with the subject line "Account System Update", asking for your "Passvvord" (gee, atleast spell it right :/), because they are shutting down your account, .... Simply delete it.

Notice the headers, its not from Google or Gmail and you would be safer not responding to them. I'm not sure if google has a feedback system where I can submit this so I thought its better to blog and tell the whole world.

Delivered-To: s***@gmail.com
Received: by 10.236.95.41 with SMTP id o29cs221272yhf;
Mon, 21 Feb 2011 16:29:35 -0800 (PST)
Received: by 10.224.28.66 with SMTP id l2mr1663334qac.68.1298334565437;
Mon, 21 Feb 2011 16:29:25 -0800 (PST)
Return-Path: <nobody@alexander.ourhostingservers.com>
Received: from alexander.ourhostingservers.com (alexander.ourhostingservers.com [75.126.65.69])
by mx.google.com with ESMTPS id m15si11781389qck.51.2011.02.21.16.29.25
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 21 Feb 2011 16:29:25 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of nobody@alexander.ourhostingservers.com designates 75.126.65.69 as permitted sender) client-ip=75.126.65.69;
Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of nobody@alexander.ourhostingservers.com designates 75.126.65.69 as permitted sender) smtp.mail=nobody@alexander.ourhostingservers.com
Received: from nobody by alexander.ourhostingservers.com with local (Exim 4.69)
(envelope-from <nobody@alexander.ourhostingservers.com>)
id 1PrfGY-0000BR-P5
for s***@gmail.com; Mon, 21 Feb 2011 17:34:06 -0600
To: s***@gmail.com
Subject: Account System Update
X-PHP-Script: ex-dn.com/e107_themes/inbox.php for 41.31.241.220
From: Gmail <verifyscevsces@gmail.com>
Reply-To: verifyscevsces@gmail.com
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
Message-Id: <E1PrfGY-0000BR-P5@alexander.ourhostingservers.com>
Date: Mon, 21 Feb 2011 17:34:06 -0600
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - alexander.ourhostingservers.com
X-AntiAbuse: Original Domain - gmail.com
X-AntiAbuse: Originator/Caller UID/GID - [99 32002] / [47 12]
X-AntiAbuse: Sender Address Domain - alexander.ourhostingservers.com
X-Source:
X-Source-Args:
X-Source-Dir:

We are shutting down some accounts due to congestion in our database system and your account was chosen to be deleted automatically. To avoid permanent lockup, kindly click reply and fill in the space below for verification purpose:-

Account ID
Passvvord
Registered Year (MM/YYYY)
Designation Field:
Direct Phone:

Note: This email is only for Gmail users (Users should reply within 48 hours to avoid "Permanently Lockup" Account)

Thank you for using Gmail !

- page 1 of 7