M$ windows is NOT an operating system, its a user application

thanx for paying attention to this post. You must be, one of the few, that really worry about you system(s).
Getting straight to the point, that m$ windows its just an application, I'd like to point out the following.
A. Its designed from a user P.O.V. making certain that the user has total control over the system (is an administrator). There are simple tasks that must be done, and cannot be done unless you switch -listen to this- the user account to be an admin, perform the task, switch back the user to plain. Logging in as admin and do the stuff, is not enough in many occasions. That, holds true, after -at least- win2k.
B. There are files that the system does not allow you to access. Even if you are the admin, there are files hidden and cannot be accessed. Some system files are even protected in 'safe mode' and the only way to look at them is booting with a live cd (eg ubuntu, best boot cd etc).
C. Functionality is restricted not by design, but using software flags in the code or the registry setup during installation. You can find examples of this maybe since NT but definitively since w2k (workstation vs server) .
D. There is -at least for me- a debate for the implementation of ACLs and file security in general. If they had just implemented the VMS approach it would be so straight forward and simple. Doing a clopyright from other systems, and not even implementing it right, bugs the hell out of me. (<- ok, that is just a personal insight)
E. Embedding /Binding the drivers, the way its done, for any hardware that you plug in, its so DOS, or may I say win95. There is really no user space in their configs. You must have an admin next to you or you dont have a pc. That is the reason really, that everybody logs in as admins at all times.
F. At vista they claim full control of the MBR. Whats this? Just to avoid dual boots? To follow the instructions on setting up a second OS, you'll need to get a PhD. (exaggerated, I agree, just to point out the complexity)
G. Too many hidden secrets. Starting the validation, h/w signature, kernel, APIs etc etc. That alone makes it a simple and plain commercial application.
H. What would be the difference if we were using cp/m.... Soooory for that, I meant DOS. We had an application over dos, named WINDOWS 1, then 2, the 3 then whatsoever then VMS ... eeerrr sorry, WinNT, that did not boot dos, and everybody used it as a single user system. I was using concurrent dos and concurrent cp/m and had more frills years before. At least I had an operating system, crummy graphics but a real os, with timings, user access, memory handles and everything. Where are those in vista? A system that you must ask an application for resources that'll be squeezed in an provided by passing info to a subsystem that controls the application. They like to call it a kernel. They wished.

From an administration point of view, its so time consuming, that all of my friends switched to virtual. I converted all installations to Virtual machines under GPL. I install an enterprize server at about 10 minutes (to copy the machine from usb). Yes, I pay for the license. I treat it an an applications, thats what it is and all needed services are coming from linux servers. At some places, users are on linux too. It was hard for them, but its company policy --- lol, oooh yeah! +grim

Leave the gamers on m$. Get the business on operating systems like OpenVMS - Unix - Linux - AIX and whatever flavors. Not wonnabe(s). Lets also price support contracts at what it is worth. M$ systems X 2 VS an operating system. I already watch the ROV as it is today. Imagine what would happen if we double support prices for those time consuming, limited functionality application systems? did I mention antivirus ???