Re: How will PatchGuard change kernel programming?

An API documentation is a contract between the API vendor (Microsoft) and
the user (ISV). As such, only those functions are documented which are
guaranteed to stay and won't break compatibility with previous OS versions.
This is not always the case, though; there's been breaking changes in
Windows API sometimes, and not always for good.

Things that's never been documented are not guaranteed to stay in OS or
always continue working the same way. It's silly to rely on undocumented
API, because it will cause compatibility problems in the future.

"smerf" <smerf@xxxxxxxxxx> wrote in message
news:FtYXg.44703$8s6.18853@xxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your response.

IMHO, this is just another way that Microsoft is increasing its monopoly
of the desktop. First, they don't release all of the OS APIs - except to
thier internal applications developers and "select" Microsoft Partners.
Now, they are locking people out of 3rd party methods that help to protect
us (like Spysweeper and AVG). They are also blocking graphics hooks that
make apps like VNC a viable alternative to the Windows-only Remote Desktop
(which is not on all versions of Windows).

I think this move (until it is hacked) will force more software vendors
out of business and increase Microsoft's stranglehold on the desktop.

I'm starting to think that we need to revisit the notion of breaking
Microsoft into an applications company and an OS company. We probably
should have done that in the original anti-trust suits.

I really don't see the problem with giving developers the ENTIRE API to
work with. Will they find flaws? Sure they will, and some will even abuse
them. But, Microsoft would be aware of flaws even sooner than they are now
and could actually take a decent stab at making the OS secure from
malicious hacking instead of from developers and users.

REALbasic + Linux is looking better and better.


"Don Burn" <burn@xxxxxxxxxxxxxxxx> wrote in message
news:uQuguay7GHA.4568@xxxxxxxxxxxxxxxxxxxxxxx
It is a good thing, since it forces people to develop properly and not
use kludgy hooking, which exposes the system to threats. For any decent
developer it will not impact them at all.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply



"smerf" <smerf@xxxxxxxxxx> wrote in message
news:NiUXg.10022$nn6.4289@xxxxxxxxxxxxxxxxxxxxxxxxx
How will Vista's PatchGurad change the ability of coders to extend the
OS?







.

Relevant Pages

  • Re: Penetration of ASP.NET - Developers continue to use VB6 & ASP
    ... i thought the article was saying that the Windows API was dead and you're a good example of why. ... he's saying that Microsoft lost the app war with the web. ...
    (microsoft.public.inetserver.asp.general)
  • Re: Penetration of ASP.NET - Developers continue to use VB6 & ASP
    ... i thought the article was saying that the Windows API was dead and you're a good example of why. ... he's saying that Microsoft lost the app war with the web. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cost of the M$ monopoly-$10BIllion/year.
    ... and how little investment Microsoft has made to it since bundling ... >> towards producing a low cost yet powerful machine, which is what Apple ... >the late 80s when Windows was a steaming pile of crap by comparison. ... >And apps depend on API, and Apple has a much better API than Windows, ...
    (comp.sys.mac.advocacy)
  • Re: DFS Client NetDfs API in MSDN - NetDfsSetClientInfo
    ... trying to make a simple API call work because the Microsoft documentation ... flat out wrong in MSDN library, MSDN online, and every other site that ... the NetDfsSetClientInfo and NetDfsGetClientInfo API calls both ... This is not the first MSDN documentation error I have dealt with, ...
    (microsoft.public.win32.programmer.networks)
  • Re: Why Lisp is too hard for me to use
    ... and eventually the legacy Win32 api may ... Of course Windows has sharp edges. ... I noticed a Mac dev complaining about Apple's ... whereas Microsoft seems to have the problem that they bend over ...
    (comp.lang.lisp)