… in Explorer < 7.0 (old IE's do not understand CSS "position: fixed" ).

• It’s a scratch pad after all!
• will fix it sooner or later if I have time ;-)

Use Firefox! ;-)

How to enable, disable displaying by page and change the number of lines by page in various OS’es

[read more…]

2L (Lindberg Lyd Ltd) is about to hammer another nail into the CD’s coffin. You can buy and download albums (not many at that time)  in DSD64, FLAC 24/96 and FLAC 24/96 multichannel formats  from their website. Or test taste the HiRez for free here.

The picture shows sono- and spectrogram of W.A.Mozart: Violin concerto in D major (KV 218) - Allegro
Marianne Thorsen / TrondheimSolistene / Øyvind Gimse (Stereo WAV 24bit/96kHz). And it sounds accordingly ;-)

What a difference from the crap like this recording!

More info:

• Avsforum discussion.
• Audioasylum duscussion

After hitting this bug (yes, again and again) I had to unmount the broken file system and run fsck (twice). But then I apparently hit anoter bug (or a feature?) - I could not mount the file system back.

Neither pwdx not lsof showed any processes using /export/docs. The solution was to recreate the directory:

Snv_92 has been entertaining me since I upgraded from quite stable snv_88. I’m hitting a bug after a bug. (See here).

This is the latest - unkillable process, which can’t be killed with kill -9 or zone reboot. Reboot just hangs. Truss ends up with:

dtrace shows nothing. The only workaround is to reboot the entire system.

See also:

Revenge of the unkillable process
Unkillable process
Bug ID 6455727

What to choose for a home server? The most important difference is not the accelerometers or MTBF but whether the disks will be used in RAID’s.

An excerpt from Western-Digital FAQ:

When an error is found on a desktop edition hard drive, the drive will enter into a deep recovery cycle to attempt to repair the error, recover the data from the problematic area, and then reallocate a dedicated area to replace the problematic area. This process can take up to 2 minutes depending on the severity of the issue. Most RAID controllers allow a very short amount of time for a hard drive to recover from an error. If a hard drive takes too long to complete this process, the drive will be dropped from the RAID array. Most RAID controllers allow from 7 to 15 seconds for error recovery before dropping a hard drive from an array. Western Digital does not recommend installing desktop edition hard drives in an enterprise environment (on a RAID controller).

Western Digital RAID edition hard drives have a feature called TLER (Time Limited Error Recovery) which stops the hard drive from entering into a deep recovery cycle. The hard drive will only spend 7 seconds to attempt to recover. This means that the hard drive will not be dropped from a RAID array.

If you install a RAID edition hard drive in a desktop computer, the computer system may report more errors than a normal desktop hard drive (due to the TLER feature). Western Digital does not recommend installing RAID edition hard drives into a desktop computer environment.

Source: What is the difference between Desktop edition and RAID (Enterprise) edition hard drives?

This is the second track from Porcupine Tree “Deadwing” called “Shallow”.

WYSIWYG… It sounds just like the graph in SND.  Especially if upsampled without decreasing the volume - like badly scratched disk. And yes, loud. Can it be any worse?

After upgrading from snv_88 to snv_92 (Solaris 11 or Nevada b92) my home server started spewing  the following errors:

[read more…]

In order to upsample 16/44.1 stream to, for example, 24/96 and play it on the Transporter you need:
[read more…]

Who could have thought that Eva Cassidy’s album “Time after time” (one of my favourites, BTW) would have been recorded with such clippings?

See an excerpt from “The Letter”  on the left.