Description Logo for Microsoft Windows from 1992 to 1999.
Source This vector image was created by converting the Encapsulated PostScript file available at brandsoftheworld.com - to see it there, click here. If it is not free content, remember to only render it at web resolution to comply with our fair-use policy.
Article [[{{{Article}}}]]
Portion used The entire work illustrated is covered by this rationale
Low resolution? SVG
Purpose of use The Classic Microsoft Windows logo - used in the main article and in other articles about the software itself
Replaceable? Not replaceable.
Other information This image is only being used in Wikipedia articles for informational and educational purposes.
The image's inclusion here will not result in financial loss to the creator of the original drawing or Microsoft.
A logo is very safe territory
Wikipedia is a non-profit organisation, downstream providers who are not non-profit will need to consider whether they will take the risk in using this image
Windows/386 introduced a 32-bit protected mode kernel and virtual machine monitor. For the duration of a Windows session, it created one or more virtual 8086 environments and provided device virtualization for the video card, keyboard, mouse, timer and interrupt controller inside each of them. The user-visible consequence was that it became possible to preemptively multitask multiple MS-DOS environments in separate Windows (graphical applications required switching the window to full screen mode). Windows applications were still multi-tasked cooperatively inside one of such real-mode environments.
Windows 3.0 (1990) and Windows 3.1 (1992) improved the design, mostly because of virtual memory and loadable virtual device drivers (VxDs) which allowed them to share arbitrary devices between multitasked DOS windows.[citation needed] Because of this, Windows applications could now run in 16-bit protected mode (when Windows was running in Standard or 386 Enhanced Mode), which gave them access to several megabytes of memory and removed the obligation to participate in the software virtual memory scheme. They still ran inside the same address space, where the segmented memory provided a degree of protection, and multi-tasked cooperatively. For Windows 3.0, Microsoft also rewrote critical operations from C into assembly, making this release faster and less memory-hungry than its predecessors.
No comments:
Post a Comment