Sun 02 Apr 2006
Category : Commentary/LiveStrong.txt
I hate Windows and all that it stands for with a vengeance. But I resolved long ago that, if we want to be able to go on using our Macs in business, we've got to be able to handle all that Windows will throw at us without breaking into a sweat.
That's how we've been able to hang on to our PowerBooks through some bleak years working with Windows-centric client companies, some of whom were happily using Macs till some "consultant" or IT manager came to throw them out.
I've seen them all - Richard Ellis, AGF, among others, and most painful of all, Motorola - home of the PowerPC and 68000 chip. And IT managers gleefully selling off perfectly usable, even brand-new Macs for 20 bucks.
It's a question of attitude. I wouldn't do this - ethnic cleansing for the machines. Even if we could do it, "forward migration" as somebody calls it, and move a company from PCs to Macs, I would still find use for the PCs, and use them till they really die. It's about conservation, and cutting down on waste - not least about the waste of the human spirit.
That's why although I'll still work on Windows, it's all "aridity and disenchantment" - there's nothing noble behind that spirit.
WebDAV and Windows XP - A Solution
Category : Technology/WebDAVandWindowsXP.txt
We've found a solution for setting Windows XP to access a WebDAV folder. Thanks to Stephen Cranfill and Chiang Hai Hwee who sent me the solution within two hours of each other :
Now, a couple of other Windows notes :
This should also work for Windows 2000 clients, but Windows 2000 doesn't really need the port number. The WebDAV user name and password are entered the same way as for the Mac clients.
If you have SSL turned on at the server, you can enter the URL like this : https://domainName/dav (i.e., with https, you don't need to enter the port number - how inconsistent - there's not enough life times to keep all these straight.) The user name and password, plus all the subsequent WebDAV communications, will then be sent encrypted.
If you cannot access the server via https, you need to go to Internet Explorer's Tools/Internet Options menu, and under the Advaned tab, under the Security section, turn on "Use TLS 1.0".
Windows does really make you work. It's totally inconsistent and largely illogical. It doesn't try even one bit to conform to open, non-Microsoft, Internet standards - "embrace and extend" being more important than playing nice with the neighbours. It tries to be too smart, remembering URL, user name and password combinations when you don't want it to, even when they are wrong, and ends up tripping the user.
It reminds me of how corporate IT departments work - layers of managers and project leaders throwing ideas for features, often without a grasp of the issues or the trade-offs, hoping to impress the superiors or whoever is listening in to the project reviews, and passing all these to one little poorly-paid outsourced programmer to code everything but the kitchen sink.