[LINK] Question: How do you protect Windows?

[Adam Todd]

>>>I'll not be revisiting Windows in the foreseeable
>>>future (even if it is seen as a career limiting move!)
>>
>>Career limiting - questionable, but that is improving anyway.
>>Hypertension limiting - definitely.
>
>That is a very good point. There may be tangible financial
>losses I experience turning down ASP/C# contracts (cringe).

Totally agree, but I don't so ASP :)

>But the intangible benefits of working on systems that
>never crash, never suffer virii/worms/adware/spyware
>and that do what they are told when programmed in such and
>such a way far outweight any perceived lost contracts.

I charge more for MS processes, if I do any at all these days.  It's rare, 
remember I retired from IT&T, but occasionally someone makes me an offer I 
just can't refuse.   And if it's MS based, the offers are very UNrefusable!

Unix Offers aren't as exciting, but the projects tend to be more doable and 
more long term sustainable.  I don't get a lot of "repeat" or "recall" work 
on unix systems.  I try and avoid recall on MS and teach the consumer to 
look after it :)


"Power off and on" tends to work in most cases :)

Or "reinstall and reload the Backup or Master CD or DVD" works too :)

>My current project work is being done on Linux and OS X. It
>is basic C stuff, and can be run on practically any platform.

That's pretty sad.  You've done yourself out of a lot of "coding for 
platform X and Y and Z" work now :)

>A few sorry sods on our project have to use an SDK that only
>runs on Win XP. I'll say little more than that I hear them
>cussing and swearing at Mickeysoft ....

I have to admit, the last time I did ANY low level coding for windows was 
about 12 years ago.  I gave up on C and API's a long long time ago.