Monday, December 31, 2007

Skype account management mess

Why is it so hard for the Skype folks to understand that a simple and consistent account management system is much better than a confusing, everchanging, "full of surprises" one?  Every time I log on to my Skype account (which I don't do very often, frankly) I find myself learning a new account management system.  Everything is not like it was the last time I logged on.  Everything's changed, reshuffled.  I only need to do a single simple thing: add some money to the family group account I manage.  And every time I wonder: where did they stick the group account this time around?  How did they call it this time around?  I consider myself lucky if I find what I want within the first ten minutes.  But sometimes I don't.  It's a mess.  A frustrating mess.

People, stop changing things!  Don't you understand that you might be losing customers because of this?  Keep it simple, stupid!

Sunday, December 16, 2007

Mac type 1 fonts in a web page

Lucida Grande

Lucida Grande Thick

Lucida Grande Bold

Lucida Grande size 10

Lucida Grande size 12

Lucida Grande size 14

Saturday, December 01, 2007

PCLinuxOS 2007

I wanted to try this OS on my computer over the weekend.  So I downloaded and burned a CD and shoveled it into the CD drive hoping for a quick and easy install.

I was wrong.  The installation was anything but quick and easy.  For starters it couldn't mount the CD drive.  So I was required to specify the following boot options: all-generic-ide irqpoll.  It was a typical problem with all linux disttors about a year ago on the Intel P965 chipset that I use.  But recent linux distributions finally managed to work around this problem.  Except for PCLinuxOS as it turns out.

Anyway, even with those boot options all the PCLinuxOS livecd could do is boot into a command prompt.  It couldn't start the X server.  I logged in with the root/root combination and examined the Xorg.0.log file, where I didn't find anything suspicious, only an innocently looking "fatal server error: cannot run in the framebuffer mode" message which I can't decipher (why does it want to use the framebuffer?  who knows).

Ironically the PCLinuxOS livecd splash screen says: "radically simple."  Nice joke IMO.

Naturally, I couldn't spend any more time with this OS.  Time to move on and try something more worthwhile.  PCBSD maybe?  The only thing I can't understand is how this OS keeps the first position in the distrowatch.org list of OS'es.

How to speedup Vista shutdown

Set the following registry value:

[HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control]
WaitToKillServiceTimeout = 1000

This will force all services to quit within 1 second (the default value is 20000 which means 20 seconds).  And if there is a service that can't do it, it will be killed, which is OK for a typical desktop system.

I also found a good article that describes this trick and a couple of more: http://www.mydigitallife.info/2006/10/31/fast-shutdown-faster-windows-2000-windows-xp-windows-2003-and-windows-vista/

Thursday, November 22, 2007

My old calculator I had in high school

citizen srp-175

I've been trying to find out which calculator model I used in school.  But I couldn't remember it.  After looking through pictures of hundreds old calculators I finally found it.  Citizen SRP-175.  It was a nice little device.  It's primarily a scientific calculator.  It's also possible to enter and execute small programs on it.  But I didn't use its programmability, because computers were available at that time.

Monday, June 25, 2007

Resolve Windows Update problems on Vista

Some of Windows Update errors on Vista can be solved by resetting the state of the Windows Update service on the machine.  The state is saved in the %SystemRoot%\SoftwareDistribution directory.  So all that needs to be done is deleting the contents of that directory.  When the update service is started next time, it will recreate this directory contents by downloading the data from the online update server.  Just follow these easy steps:

  1. Stop the "Windows Update" service.
  2. Delete %SystemRoot%\SoftwareDistribution directory.
  3. Restart the "Windows Update" service.

Friday, June 15, 2007

Thursday, April 19, 2007

Looking for perfect Linux distro: Mandriva 2007.1

I've been trying different Linux distros since I installed my first Linux in 1997.  My quest for the perfect Linux distro continues.  Today I tried Mandriva 2007.1.  It was release just recently.  2007.1 (aka 2007 Spring edition) is apparently an update for the 2007 version of Mandriva distro.  I had 2007 installed at some point.  It was OK, but had some problems with my hardware.  The hardware was pretty new for that time (late 2006).  I have Intel DP965LT motherboard and Core2Duo processor.  Back at that time surprisingly many Linux distros failed to install on this motherboard.  It generally required kernel 2.6.19 or later to work.

I read about Mandriva 2007.1 on slashdot.  Many people left favourable comments.  So I decided to give it another try.  I downloaded a free edition DVD, burned it, and started the installation.

The installer launched from the DVD and the installation generally went smoothly.  The installer informed me that it failed to load pata_marvell driver, but it didn't seem to have caused any problems.  The installation proceeded.

Mandriva partition manager is very good.  It was quite easy to choose a partition to install linux on.  By default it created an extended partition on my hard drive, so I had to switch into "expert mode" and force it to create a primary partition instead.  Then I proceeded to format and copy packages to the installation partition.

Mandriva gives you a choice to copy the whole content of the DVD to the hard drive first and then install from the hard drive.  I chose that option.  But I'm not sure whether it sped up the installation.  Just copying the DVD to the hard drive took at least 20 minutes.

Then goes the hardware configuration.  Mandriva detected most of my hardware correctly.  I have two sound cards, one onboard is Intel HD and another is SB Audigy.  It suggested driver modules for both sound cards.  I was mainly interested in the SB Audigy card, so I had to choose between snd_emu10k1 and some audigy driver.  I chose snd_emu10k1, since this was a driver I encountered before.  I turned out to be a bad choice.  The sound from the speakers was very noisy.  The installer doesn't offer to test the driver so I had no idea how it would work.

Then goes a video card.  My machine has a PCIE card, ATI Radeon X700.  The installer detected it as ATI card and suggested the ati driver.  There is an option to test the X server with that driver.  I tried it and the X server couldn't start for some reason.  Thinking that it will be resolved after the installation is complete I proceeded with that driver anyway.  Again, it was another mistake as I learned later.

Then it was the time to configure the wireless card.  I have a Ralink based PCI card.  The installer suggested two options: the native rt61 driver and the ndiswrapper over Windows driver.  I wanted to go with the rt61 driver, but it wasn't available in the free edition.  I got the error message, saying that the driver needs a firmware which is only provided in the paid edition.  Too bad.  Especially considering that the firmware is essentially free (maybe not GPL'ed though).  Now I had to install the ndiswrapper.  The installer asked for a CD with the Windows driver.  Unfortunately the CD drive was locked, because I had the Mandrive DVD disk in it.  There was no obvious way to unlock it, so I gave up on the wireless and opted for the wired connection.

The rest went smoothly.  But on the first boot X server didn't start.  Having checked the log file I found that it tries to find a PCI card which doesn't exist.  My video card is PCIE.  Alrighty then.  I've searched the internet using a text browser named lynx and found some mentioning of fglrx driver.  Unfortunately this driver didn't exist on the system.  Perhaps it's also availabe in the paid edition only.  Which I thought was a pity, because it severly limits my options.

At the end I checked the kernel version that comes with this distro.  It was 2.6.17-13mdv.  Quite a disappointment.  Why does Mandriva stay with that old kernel when others have kernel 2.6.20 already?  I have no idea.

After two hours of my experience with Mandriva I already had multiple problems to resolve.  This definitely wasn't something I was looking for.  Besides, another popular distro was just released - Ubuntu 7.04.  So I decided to erase Mandriva and try Ubuntu instead.  Hope it gives me less problems.