*That's* a common myth encouraged by Microsoft. Little code is left, I'll
grant, but the basic behavior is much the same; any experienced OS/2 user
can recognize BASEDEVs in NT's refusal to deal with changing devices at
runtime, for example. Likewise, its handling of IFSes is quite familiart
once you get past the use of the registry instead of CONFIG.SYS. And Win32
is the OS/2 API with functions and structures renamed, structure contents
slightly rearranged, and the not-so-occasional flag with an inverted sense
(often for no discernable reason IMHO).
Someone who hasn't had significant experience with both would likely believe
the tale that NT has no relationship to OS/2. Someone who has experience
with both knows differently; if you can see past the glitz, the behavior
tells the story. (I discount Microsoft's claims that NT is not related to
OS/2, for the simple reason that they felt they had more to lose by
acknowledging it than by trying to claim that OS/2 was entirely IBM's fault
and that they had the "real" OS.)
-- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering KF8NH Kiss my bits, Billy-boy.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/