Misplaced Pages

MSI Wind Netbook

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

The MSI Wind Netbook was a family of subnotebooks / netbooks designed by Micro-Star International (MSI). Wind stands for "Wi-Fi Network Device". The first model was announced at CeBIT 2008, and first listed for pre-orders on May 9, 2008. While initially 8.9- and 10.1-inch screen versions existed, as of 2010 only the 10.1" remained, with a resolution of 1024 × 600. While most models had 1 GB of RAM, some had 2 GB, and hard disks ranged from 80 GB on the oldest to 250 GB on the newest models. Also featured were Bluetooth , WLAN and a 1.3 megapixel camera. The Wind PC was MSI's response to the successful Asus Eee PC . The keyboard was 92% of full-size.

#74925

32-748: Now available by MSI are 10-inch and 7-inch Wind Pad tablets using the Android operating system. When the original Wind U100 was released, many original equipment manufacturer versions of the Wind were also released, under different names. Some OEM versions are offered in different colors to the original MSI Wind, apart from the Tsunami Moover (white only), the Mobo White and the Ahtec LUG N011 (white only). The MSI Wind netbooks (specifically

64-449: A Chromebook is also a common customization. Original equipment manufacturer An original equipment manufacturer ( OEM ) generally refers to a company that produces parts and equipment that may be marketed by another manufacturer. However, the term is ambiguous, with several other common meanings. It sometimes means the maker of a system that includes other companies' subsystems, an end-product producer, an automotive part that

96-618: A message-based protocol for communicating with their devices—as user-mode drivers. If such drivers malfunction, they do not cause system instability. The Kernel-Mode Driver Framework (KMDF) model continues to allow development of kernel-mode device drivers, but attempts to provide standard implementations of functions that are known to cause problems, including cancellation of I/O operations, power management, and plug and play device support. Apple has an open-source framework for developing drivers on macOS , called I/O Kit. In Linux environments, programmers can build device drivers as parts of

128-498: A different requirement regarding installation media from Direct OEMs. While a clean retail media of Windows can be installed and activated on these devices with OEM keys (most commonly using the SLP key that's embedded in to the system firmware already), actual OEM recovery media that was created by the PC manufacturer (not system-builder, nor retail Windows versions) typically only works on

160-487: A high-level application for interacting with a serial port may simply have two functions for "send data" and "receive data". At a lower level, a device driver implementing these functions would communicate to the particular serial port controller installed on a user's computer. The commands needed to control a 16550 UART are much different from the commands needed to control an FTDI serial port converter, but each hardware-specific device driver abstracts these details into

192-437: A target for exploits . Bring Your Own Vulnerable Driver (BYOVD) uses signed, old drivers that contain flaws that allow hackers to insert malicious code into the kernel. Drivers that may be vulnerable include those for WiFi and Bluetooth, gaming/graphics drivers, and drivers for printers. There is a lack of effective kernel vulnerability detection tools, especially for closed-source OSes such as Microsoft Windows where

224-435: A variety of manufacturers ( Dell , HP , ASUS , Acer , Lenovo , Wistron , Inventec , Supermicro , Compal Electronics , Quanta Computer , Foxconn , Pegatron , Jabil , Flex , etc.). These OEMs commonly use a procedure known as System Locked Pre-installation , which pre-activates Windows on PCs that are to be sold via mass distribution. These OEMs also commonly bundle software that is not installed on stock Windows on

256-471: Is a popular example of a company that issues its Windows operating systems for use by OEM computer manufacturers via the bundling of Microsoft Windows . OEM product keys are priced lower than their retail counterparts, especially as they are purchased in bulk quantities, although they use the same software as retail versions of Windows. They are primarily for PC manufacturer OEMs and system builders, and as such are typically sold in volume licensing deals to

288-563: Is important that the hardware manufacturer provide information on how the device communicates. Although this information can instead be learned by reverse engineering , this is much more difficult with hardware than it is with software. Microsoft has attempted to reduce system instability due to poorly written device drivers by creating a new framework for driver development, called Windows Driver Frameworks (WDF). This includes User-Mode Driver Framework (UMDF) that encourages development of certain types of drivers—primarily those that implement

320-407: Is improved stability, since a poorly written user-mode device driver cannot crash the system by overwriting kernel memory. Because of the diversity of modern hardware and operating systems, drivers operate in many different environments. Drivers may interface with: Common levels of abstraction for device drivers include: So choosing and installing the correct device drivers for given hardware

352-418: Is manufactured by the same company that produced the original part used in the automobile's assembly, or a value-added reseller . When referring to auto parts, OEM typically refers to the manufacturer of the original equipment, that is, the parts which are then subsequently assembled and installed during the construction of a new vehicle. In contrast, aftermarket parts are those made by companies other than

SECTION 10

#1732801034075

384-472: Is often a key component of computer system configuration. Virtual device drivers represent a particular variant of device drivers. They are used to emulate a hardware device, particularly in virtualization environments, for example when a DOS program is run on a Microsoft Windows computer or when a guest operating system is run on, for example, a Xen host. Instead of enabling the guest operating system to dialog with hardware, virtual device drivers take

416-508: Is that they can be loaded only when necessary and then unloaded, thus saving kernel memory. Depending on the operating system, device drivers may be permitted to run at various different privilege levels . The choice of which level of privilege the drivers are in is largely decided by the type of kernel an operating system uses. An operating system which uses a monolithic kernel , such as the Linux kernel , will typically run device drivers with

448-473: Is tied to the PC motherboard which it is initially installed on, and there is typically no transferring the key between PCs afterward. This is in contrast to retail keys, which may be transferred, provided they are only activated on one PC at a time. A significant hardware change will trigger a reactivation notice, just as with retail. Direct OEMs are officially held liable for things such as installation/recovery media, and as such were commonly provided until

480-400: Is via protection rings . On many systems, such as those with x86 and ARM processors, switching between rings imposes a performance penalty, a factor that operating system developers and embedded software engineers consider when creating drivers for devices which are preferred to be run with low latency, such as network interface cards . The primary benefit of running a driver in user mode

512-612: The PCI bus or USB is identified by two IDs which consist of two bytes each. The vendor ID identifies the vendor of the device. The device ID identifies a specific device from that manufacturer/vendor. A PCI device has often an ID pair for the main chip of the device, and also a subsystem ID pair that identifies the vendor, which may be different from the chip manufacturer. Computers often have many diverse and customized device drivers running in their operating system (OS) kernel which often contain various bugs and vulnerabilities , making them

544-405: The interrupt handling required for any necessary asynchronous time-dependent hardware interface. The main purpose of device drivers is to provide abstraction by acting as a translator between a hardware device and the applications or operating systems that use it. Programmers can write higher-level application code independently of whatever specific hardware the end-user is using. For example,

576-529: The kernel , separately as loadable modules , or as user-mode drivers (for certain types of devices where kernel interfaces exist, such as for USB devices). Makedev includes a list of the devices in Linux, including ttyS (terminal), lp ( parallel port ), hd (disk), loop, and sound (these include mixer , sequencer , dsp , and audio). Microsoft Windows .sys files and Linux .ko files can contain loadable device drivers. The advantage of loadable device drivers

608-620: The MSI Wind U100) have been subject to customization; especially as Hackintoshes . Though many other netbooks can also be installed with Mac OS X, the MSI Wind is one of the most popular mainly because of its ideally large keyboard, simple design, and wide availability of options. The MSI Wind (specifically the U100) can be installed with Mac OS X Snow Leopard 10.6.8 with a modified bootloader and kernel. Installing ChromeOS and turning it into

640-916: The OEM, which might be installed as replacements or enhancements after the car comes out of the factory. For example, if Ford used Autolite spark plugs , Exide batteries, Bosch fuel injectors , and Ford's own engine blocks and heads when building a car, then car restorers and collectors consider those to be the OEM parts. Other-brand parts would be considered aftermarket, such as Champion spark plugs, DieHard batteries, Kinsler fuel injectors, and BMP engine blocks and heads. Many auto parts manufacturers sell parts through multiple channels, for example to car makers for installation during new-vehicle construction, to car makers for resale as automaker-branded replacement parts, and through general merchandising supply chains. Any given brand of part can be OEM on some vehicle models and aftermarket on others. Microsoft

672-416: The PC model line that was designed for it. For example, a recovery disc/USB for a Toshiba Satellite P50-B will only work on that model, and not a Satellite S55T. OEMs rely on their ability to drive down the cost of production through economies of scale . Using an OEM also allows the purchasing company to obtain needed components or products without owning and operating a factory. Device driver In

SECTION 20

#1732801034075

704-435: The context of an operating system , a device driver is a computer program that operates or controls a particular type of device that is attached to a computer or automaton . A driver provides a software interface to hardware devices, enabling operating systems and other computer programs to access hardware functions without needing to know precise details about the hardware being used. A driver communicates with

736-681: The design of their hardware. Moreover, it was traditionally considered in the hardware manufacturer 's interest to guarantee that their clients can use their hardware in an optimal way. Typically, the Logical Device Driver (LDD) is written by the operating system vendor, while the Physical Device Driver (PDD) is implemented by the device vendor. However, in recent years, non-vendors have written numerous device drivers for proprietary devices, mainly for use with free and open source operating systems . In such cases, it

768-407: The device through the computer bus or communications subsystem to which the hardware connects. When a calling program invokes a routine in the driver, the driver issues commands to the device (drives it). Once the device sends data back to the driver, the driver may invoke routines in the original calling program. Drivers are hardware dependent and operating-system-specific. They usually provide

800-406: The images of Windows that will be deployed with their PCs (appropriate hardware drivers , anti-malware and maintenance software, various apps, etc.). Individuals may also purchase OEM "system-builder" licenses for personal use (to include virtual hardware ), or for sale/resale on PCs which they build. Per Microsoft's EULA regarding PC manufacturers and system-builder OEM licenses, the product key

832-412: The late-2000s. These were phased out in favor of recovery partitions located on the primary storage drive of the PC (and available for order from the manufacturer upon request) for the user to repair or restore their systems to the factory state. This not only cut down on costs, but was also a consequence of the gradual obsolescence and phasing out of optical media from 2010 onward. System builders also have

864-446: The opposite role and emulates a piece of hardware, so that the guest operating system and its drivers running inside a virtual machine can have the illusion of accessing real hardware. Attempts by the guest operating system to access the hardware are routed to the virtual device driver in the host operating system as e.g.,  function calls . The virtual device driver can also send simulated processor-level events like interrupts into

896-410: The rest of the system. Even drivers executing in user mode can crash a system if the device is erroneously programmed . These factors make it more difficult and dangerous to diagnose problems. The task of writing drivers thus usually falls to software engineers or computer engineers who work for hardware-development companies. This is because they have better information than most outsiders about

928-499: The same (or similar) software interface. Writing a device driver requires an in-depth understanding of how the hardware and the software works for a given platform function. Because drivers require low-level access to hardware functions in order to operate, drivers typically operate in a highly privileged environment and can cause system operational issues if something goes wrong. In contrast, most user-level software on modern operating systems can be stopped without greatly affecting

960-509: The same privilege as all other kernel objects. By contrast, a system designed around microkernel , such as Minix , will place drivers as processes independent from the kernel but that use it for essential input-output functionalities and to pass messages between user programs and each other. On Windows NT , a system with a hybrid kernel , it is common for device drivers to run in either kernel-mode or user-mode . The most common mechanism for segregating memory into various privilege levels

992-452: The source code of the device drivers is mostly not public (open source) and drivers often have many privileges. A group of security researchers considers the lack of isolation as one of the main factors undermining kernel security , and published an isolation framework to protect operating system kernels, primarily the monolithic Linux kernel whose drivers they say get ~80,000 commits per year. An important consideration in

MSI Wind Netbook - Misplaced Pages Continue

1024-451: The virtual machine. Virtual devices may also operate in a non-virtualized environment. For example, a virtual network adapter is used with a virtual private network , while a virtual disk device is used with iSCSI . A good example for virtual device drivers can be Daemon Tools . There are several variants of virtual device drivers, such as VxDs , VLMs , and VDDs. Solaris descriptions of commonly used device drivers: A device on

#74925