Directional Speaker Cables

Can a speaker cable has a direction?

QED representative answered:

I've just found this:-

Quote-----

From the horses mouth :-

Dear David,
unfortunately our marketing department doesn't like to offend people who
believe in the "burn in" and directionality theory of speaker cables. If
you subscribe to these theories, you may choose to arrange the QED Original
cable so that the writing points from the amplifier, towards the the
speaker.

If, like me, you don't believe a piece of copper can behave like a diode,
you may safely ignore the advice!
Sorry to have worried you for the sake of political correctness,
Yours sincerely
XXXXXX XXXXXXX
xxxx@qed.co.uk
QED AUDIO PRODUCTS LTD,
(ARMOUR HOME ELECTRONICS)
Unit B3
Kinsgswey Business Park,
Forsyth Road
WOKING,
Surrey UK
GU21 5SA
www.qed.co.uk
Tel: +44 (0)1483 747474
Fax: +44 (0)1483 545600

--- Quote

However, monster cable faq says:

Quote ---

Will I notice a difference if I hook up my cables in the wrong direction?
You probably will not, but if you think that you are experiencing noise problems, check that they are. Cables are directional for shielding purposes only. Should you not see these arrows, remember that the signal flow should go in the same direction of the print on the cable jacket, reading left to right away from the source (source to destination)

--- Quote

So go figures.

[Disclosures: The above entries come from a discussion in an (unreachable) discussion in AVForum which was cached in google.

SqueezeCenter conflicts with CheckPoint's Secure Client

I tried to run SqueezeCenter on my macbook.

It did not start.

Apparently, there is a known problem with apple security updates etc.

I followed the suggested solution, i.e., installed OnyX, and now it did not work.

I tried the CPAN trick I found here, did not work either.

Finally, I looked into /etc/services looking for usages of port 9000 (the port that SqueezeCenter listens to).

I found that I had a service called cslistener listening to this port.

After some googling, I discovered that it is the secure client of checkpoint.

I stopped the secure client; started SqueezeCenter, and all worked perfectly ...