Skip to main content

No IE7 for Windows 2000 ?

This news was published last year but I just like featuring here as a reminder for me and for other readers. For those who are still using Windows 2000, there is bad news. The much-awaited IE 7 will not be available for Windows 2000 users. But why? I hear you ask. Microsoft said that:

"the task is too complex due to security features not available in the older operating system. Company officials also noted that Windows 2000 is moving into the "Extended" support phase of Microsoft's product lifecycle as of June 30, 2005."

"It should be no surprise that we do not plan on releasing IE7 for Windows 2000," IE program manager Chris Wilson wrote on the Internet Explorer Web log.

The above phrase clearly stated that Windows 2000 is an old operating system and MS will not support in the future (till 2010). IMHO, I think Windows 2000 is one of the stable OS ever built by MS. It is also used in many mission-critical servers all over the world. I once took classes of MCSE and the instructor use Windows 2000. It is stable and rock-solid especially if use in corporate environment and has a large userbase. But why MS don't want to release IE7 for Windows 2000 users? Why not MS listen to Windows 2000 users? Upgrading to XP involves buying a new OS and many reluctant to do it and especially when they look at many security problem of XP before. You may think that this is one of MS tactic to dominate OS market.

I am one of Windows 2000 users and also a big fan of Firefox. If MS doesn't want to release it for Windows 2000, I have firefox. We as a user, have many better choices. We just need to choose the right tool for what we want to achieve. Thank god we have open source apps that are more reliable with better support for open standard to choose from.

Comments

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy

postfix - mailbox size limit and message size limit

postfix is my MTA of choice. I use it for my mailserver because its simplicity , security and sendmail-compatible (the widely used smtp in the world but not as secure). It is also extensible by plugging other servers for various purposes (antispam, antivirus,database etc).

I had one problem with file attachment larger than 10MB. Users couldn't send it although I have setup squirrelmail (SM) to be able to attach files summed up more than 20MB and I had modified php settings as per here. The problem was not in SM setting. It was postfix. By default, attachment size that can be sent by postfix is 10MB ~ 10240000 byte. How did I know it? I looked in log file (for my system it is in /var/log/mail/errors. For other system, the file to look is /var/log/maillog). The line looked like this:

Feb 26 16:30:53 webmail postfix/sendmail[30775]: fatal: me@mymailserver.org(74): Message file too big


Solution
Open /etc/postfix/main.cf with a text editor of choice and find message_size_limit directive an…