OpenSolaris (open Solaris) is a name of the operating system (the OS) released by the open source project that Sun Microsystems on the basis of the Solaris Operating Environment technology began and a project. For distinction, "OpenSolaris project" refers the latter to "OpenSolaris" in the former afterward.
Table of contents
Process
The OpenSolaris project is aimed for open source development of "Solaris", and user group, user community move into action for a user and developers of Solaris(SunOS) mainly in all parts of the world.
However, information from a document circulated in the Oracle inside with the expression with "OpenSolaris is officially now dead." on August 13, 2010 was sold, and confusion produced it. Oracle makes clear that open-sourcing in itself cancels the exhibition of so-called knight Lee cord although I maintain it later.
The establishment of the OpenIndiana project was announced as folk music of OpenSolaris on September 14, 2010. The purpose of OpenIndiana becomes a successor of OpenSolaris and is to develop the free OS that is compatible with Solaris [1]. In addition, the Illumos project that almost aimed at the complete open-sourcing of Solaris (closely SunOS kernel and ユーティリティティ concerned namely OS/Net) for the same period starts. OpenIndiana uses these works in the future.
OpenIndiana does not get the support of the Oracle. This resembles to it with Red Hat Enterprise Linux and relations of CentOS (I speak so even FAQ of OpenIndiana oneself). It is with "Spork" not project reason, "Fork" (spork).
In addition, it is confusing, but "Indiana" is a development name of OpenSolaris. This leads to a result to accelerate confusion of late 2010.
Chronological table
On January 25, 2005, I establish OpenSolaris project. Sun Microsystems announces that I open-source 1,670 patents that the company has.
In February, 2005, Sun Microsystems released a source code of DTrace.
On June 14, 2005, Sun Microsystems released a source code of Solaris10.
On November 16, 2005, I released a source code of file system "ZFS" [2].
On May 5, 2008, I release Solaris "OpenSolaris 2008.05" for first open source [3].
On December 11, 2008, I release OpenSolaris 2008.11.
On June 1, 2009, I release OpenSolaris 2009.06. It supported SPARC platform, and Project Crossbow was added as others, a new feature corresponding to SSD ZFS.
On April 16, 2010, a CD distribution program is abolished than Oracle and after that becomes only the downloading [4].
As of April, 2010, the latest build is under development, but there is not the announcement from Oracle, and the OpenSolaris board of directors and communication are in condition not to be produced [5].
On August 13, 2010, a contribution titled "OpenSolaris cancelled, to be replaced with Solaris 11 Express" is done in the discussion area of the OpenSolaris official site. I am performed Oracle with information from a document circulated inside and am expressed with "OpenSolaris is officially now dead.".
When it is talked about to Oracle but return it, on August 23, 2010, "will return control of the community to Oracle" and administration of the community are expressed with the minutes of the OpenSolaris governing board [6]; [7].
On September 14, 2010, I became a successor of OpenSolaris, and the establishment of the OpenIndiana project for the purpose of developing the free OS that was compatible with Solaris was announced [1].
License
I use CDDL(Common Development and Distribution License) of the OSI approval. This is the open source license that Sun Microsystems revised MPL(Mozilla Public License) in consideration of patent suit measures.
In addition, Tranpedia is simply not responsible for any show is only by translating the writings of foreign licenses that are compatible with CC-BY-SA license information.
References and the source which I can inspect are not shown at all, or this article is insufficient. You add the source, and please cooperate with the reliability improvement of the article. (July, 2013)
16 bits operating environment (Operating Environment, a note gave their operating system from 3.1) that Microsoft Windows 3.x (Microsoft Windows 3.x) expands MS-DOS. With improved version "Windows 3.1" released in "Windows 3.0" released as a version in 1991 and 1993 (the release year of each Japanese edition).
In addition, I develop "Windows 3.0 with Multimedia Extensions" (Windows MME) corresponding to the multimedia with some models, and minor version up of several degrees is carried out. "Windows for Workgroup" (Windows 3.1 base) supporting a network is released with the English version. In addition, "Win32s to operate 32-bit application as an additional module," there are Internet and "Internet Explorer" (16 bits version) to e-mail it "LAN Manager" for "Video for Windows" to play the animation of the AVI form to connect it to LAN "WinG" to speed up a raster display.
It is necessary to operate MS-DOS system on a computer beforehand to start it from MS-DOS environment. However, it is necessary to purchase MS-DOS separately because each was sold as an expansion product of MS-DOS before Windows 3.1 separately.
Table of contents
Summary
Microsoft Windows 3.x changed completely with Microsoft Windows 2.x which was for real mode and accomplished development to the OS to utilize protect mode with GUI of the new design. The division according to the CPU which there was in Microsoft Windows 2.x is abolished, but it is less than 80286, and there is a limit for a usable function because I plan function improvement in 80286 or less by using 386 enhanced modes which is not available positively. But movement got heavy, and machine power more than 486 was slightly necessary for 386 enhanced modes practically.
There were real mode (I use the function of 8086 equivalency CPU's), standard mode (I use the function of 80286 equivalency CPU's), 386 enhanced modes (I use the function of the i386 equivalency CPU) in Windows 3.0, but cut off real mode while I speeded up movement speed than 3.0 in Windows 3.1 (Microsoft announces this as good news in conference for developers in the United States, and it is said that I was welcomed ardently by a developer). It is only 16-bit application of 286 protect mode equivalency basically to work with 386 enhanced modes (of course, it can use 386 orders on the application side if a CPU is higher than i386). In addition, it is for Microsoft, and, in Japanese edition Windows 3.1, 80286 is excluded from correspondence with the NEC version, too, and after i386 becomes essential in the standard mode. In addition, it is for IBM, and 80286 is supported, too and can operate at standard. [the source required] the OS had come to already utilize 386 functions at the time of Windows/386 placed as a version for exclusive use of 80386 of Windows 2.x, but the application remained a limit called the real mode. However, the application became the protect mode movement of 286 equivalency in higher than standard mode in Windows3.x, too and came to be able to use protect memory freely. But the limit that the memory must use by 64KB for remains for a limit called the protect mode of 16 bits even if CPU's are more than 386.
It was an advantage that the multi task that could execute plural tasks with graphical user interface (GUI) function at the same time was possible, but one Windows program occupied a CPU, and other programs might stop (nonpreemptive). It was similar, and it was necessary to call an order to leave a task open from all over the program moderately even if I used Visual BASIC which was an interpreter-shaped development environment.
When I put it between the plural MS-DOS based program in 386 enhanced modes, I realized complete multi task. I do not cope with the graphic screen operation with the MS-DOS console.
In addition, because it was based on memory management of MS-DOS, knowledge about the securing of conventional memory was necessary, and constant knowledge was required to add a peripheral device, and to manage it. Particularly, it is necessary for a user to renew config.sys by manual operation in the middle of installation in Windows 3.0, and a hurdle is expensive.
The following existed as the thing which was not localized for Japan.
Windows 3.11
A package of (service pack application version of the place to say in now) Windows 3.1 for update of Windows 3.1 was released in the form that I changed the small of.
Windows for Workgroups 3.1
The thing which supported a network function in Windows 3.1 by default in October, 1992. It was an adding on package to Windows 3.1.
Windows for Workgroups 3.11
In December, 1993, 32 bits file access implements part of planned thing implemented by Windows 95 by taking in advance. It is released as the full package which is different from Windows 3.1/3.11.
Windows 3.2
The thing which localized Windows 3.11 to simplified Chinese character Chinese (product for People's Republic of China) in 1994. In addition, I released English version till then to the simplified Chinese character Chinese market.
PC/AT compatibles (with an IBM JAPAN version and the Microsoft version)
The PC-9800 series (there were an NEC version and a Microsoft version and, as for the English version, only as for the NEC version, was released a few)
If a PC/AT compatibles version and the PC-9800 series version were made in Microsoft, there was a product made in each hardware maker (as for the former as for IBM JAPAN, the latter NEC). These were different from a product made in Microsoft in a part including the Japanese input system. In addition, the product made in IBM JAPAN varied in screen font slightly.
As for the TOSHIBA J-3100 series version, general Windows version "ATOK7" which was not sold was carried.
PC/AT compatibles market in Japan
I had had the DOS/V boom that release time happened between an appearance and enthusiasts of DOS/V and doing it coming at the same time in an occasion and contributed to the formation of the IBM PC/AT compatibles market in Japan very much.
The personal computer (PC) market in Japan almost monopolized a market in those days in a domestic maker. Furthermore, I was in the oligopoly state in the PC-9800 series of NEC if I said. Because I was sold all over the world, the development cost could not compare with a product for exclusive use of the country that I could sell only in a Japanese market, and the PC/AT compatibles was cheap, but was in condition not to be able to enter it for a wall called Japanese. The product development of NEC was left unredeemed from the good balance with office computers (office computer) of the company by the performance level that was lower than the PC/AT compatibles of the same period, and the price was not reduced, too. However, Japanese handle it with cheap and high-performance PC/AT compatibles and will suddenly enlarge the PC/AT compatibles market in the country by virtual completion of Windows that common application is available with the domestic PC. NEC provided Windows for a PC of the company, but it followed that superiority of the application that existed in MS-DOS environment was lost.
640*480/16-colored indication was possible and, in Windows 3.0 for Japanese DOS/V, exceeded a 640*400/16 color of the PC-9800 series of main force machine NEC at the time in standard VGA and was able to use 800*600 high definition from Windows by a commercial driver by having comprised an SVGA mode with the already in those days most DOS/V machine (or a graphic circuit became independent as an expansion board, and exchange was easy) [13]. DDD (Display Dispatch Driver) which displayed Japanese by a patch file and an English version driver to display GUI of high definition, many colors (640*480/256 color, 800*600/256 color, 1024*768/16 color) more was sold by some English version indication board drivers, and cases for the PC/AT compatibles which a hardware price was cheaper than the PC-9800 series, and was high-performance increased led by an upper grade user, and a market has begun to stand up.
There comes to be polychromatic GUI indication high definition even if I use much English version indication board drivers in next Japanese Windows 3.1 directly. In addition, of the impact that TVCM is televised to release, and Masahiro Motoki calls "Windows!" repeatedly users not to be necessary who were particular about the PC-9800 series increased by there being it, and having shown the name of Windows to widely in the country. Input method editor Microsoft IME was adopted as a standard in the outline font TrueType and Microsoft version by Japanese Windows 3.1 [14] and planned unification of the Japanese input and output environment where a difference was in a product for each architecture. [15][16] [17] the new entries by this combination by the assembling PC with the PC parts shop and the foreign PC maker occur successively more [18], and market needs is a chance to shift to PC/AT compatibles.
However, the PC-9800 series was still strong at this stage, too. I needed the OADG standard now having one unification of the standard and the derivation product for the use of these optional kinds between PC-98 series twisters because it was open. Naturally the Japanese PC peripheral device maker released the peripheral device for Windows 3.1 of the PC-9821 series and dropped in price by volume sales effect immediately. In a company use and the game market, the needs of the MS-DOS based application still existed in a considerable number, too. Furthermore, there were the countermeasures such as price reductions by Seiko Epson which was NEC and the PC-98 compatible machine maker which were a manufacturer and continued finding a constant share. It is Windows after 95 that absorbed the difference in apparatus on the OS side by methods such as the device virtualization that this flow gets into full swing.
User interface
It was hard to say, and it should have been said that GUI in the true meaning was realized by the following circumstances in the desktop environment that worked on MS-DOS. The look & feel was renovated by Windows 2.x, but, in this respect, there is not the big change.
Shell
The standard shell was the program launcher which had a function equivalent to menu software called the later Program Manager in Windows 3.x. In addition, a shell can appoint specific application of (shell software made in Command Prompt and the third party) other than File Manager and it by changing setting.
In addition, (MDI) where Program Manager File Manager was able to found plural child screens in a pro-screen together.
Program Manager
As a general rule, I came to perform the start of the program from "Program Manager". Program Manager was a program to show a screen "a group" to classify "the icon" which expressed a program and icons in and was able to start a program by double-clicking an icon. However, there was not correspondency between an icon (and a group) in the Program Manager and the file (and a directory) on the disk, and it was impossible to do file operation on Program Manager. The Program Manager was, so to speak, equivalent to the Start Menu as a place for short cut to say with after 95.
File Manager
I came to perform the file operation by a program called "the File Manager" similar to "the MS-DOS window" which was a shell of previous Windows (1.0 and 2.x). I can execute a program by the double click of the file directly and can perform the linkage of the application by the extension on File Manager, too. The icon smaller than the MS-DOS window that a file name is only enumerated comes to be displayed and, if anything, has appearance similar to the Explorer after Windows 95. But there was not the function to display "a big icon" unlike the task (later description) of Program Manager and the desktop and was able to display only several kinds of icons which oneself had by the File Manager.
That age indication more than 2,000 years is garbled for File Manager again; was defective, but a Y2K-response version was distributed later by Microsoft.
Desktop
I cannot put a file and short cut considerable icon about the domain of so-called desktop. An icon displayed here was a task icon, and the desktop before Windows 3.x was a place equivalent to task bar to say with after 95. But I was able to give glory to wall paper and a design as a background.
There is not a button equivalent to [X] to close the window with after 95 in the title bar of the window in the top right corner. A button [▲] of the top right corner is a button of the maximization (screenful indication), and a button ([◆]-formed button that ▼ equalled ▲ up and down) to return to window indication when I have already maximized it is displayed most. The next button [▼] is a button of the minimization (a task icon). It is possible for the end from a pull-down menu from a[-]button and menubar of the title bar leaning to the left, but it is finished even to double-click left upper [-] itself. I cannot but input in Command Prompt with EXIT without being able to terminate it from menubar and title bar in the case of MS-DOS box. In addition, I can perform the forced end of the active window in [ctrl+alt+delete].
Pointing
The mouse was recommended and was not yet essential in those days. I could choose (I do not use it) which there was no mouse in at the time of setup, and main system in itself of Windows became able to operate even a keyboard. But there is a lot of application that was made with a mouse premise since it is really GUI, and a mouse becomes essential to Windows after 95.
The operation by the right-click was effective, and it still less had special implication only when I coped on the application side in operating Windows. A paint brush and a mine sweeper can utilize a right-click for the application attached to the Windows standard.
Multimedia
Windows 3.0 was not able to handle an animation and a sound at first. But, as for what became able to use those multimedia features for the first time, this was sold separately with the Windows body after Windows 3.0 with Multimedia Extensions was released. A multimedia feature was equipped with in Windows 3.1 by default afterwards.
An MPC (English version) standard was devised by Microsoft, but it was impossible with the PC of the smallest constitution in the first version virtually to use multimedia. I was late very much in comparison with Mac OS or TownsOS at this point in time, but it is the computer for originally duties for offices, and a function for entertainment is a standard, and it may be said even if there was no help for it for the OS to get on IBM PC/AT and the compatible machine that it is not prepared. In Japan, the PC which existed of Windows to be able to use the multimedia feature for by default was FM TOWNS degree in those days. But it was the PC-9800 series, but a model at the time came to be able to regenerate music in standard-based media players to tell the careful thing by there being a lot of FM sound source deployment machines (the thing that sound quality decreases the MIDI reproduction by the FM sound source), and choosing Windows 3.1 as the OS when I prepared for software separately [19].
An effect as the environmental improvement of the DOS is bigger than environmental improvement of Windows with the PC/AT compatibles, and the version up of the MPC standard will push up the PC/AT compatibles which, as a result, was the lowest environment for a game play to a PC gaming standard machine at a stretch. But it became the cause that this delayed a shift to Windows of the game environment and became the strong motive that Microsoft developed WinG and DirectX.
Video for Windows is announced in the times of Windows 3.1, too. Just [when?] から was the thing of the specifications that the resolution was usable only in toy degree low when I saw it, but multimedia CD-ROM software came to be released for Windows 3.1 to come to be able to regenerate AVI. 当時VFWの動画が入ったCD-ROMを日本国外で購入したものの、国内に持ち込む際に税関で止められ没収されたという話がある。 「Video」の文字からアダルトビデオが連想されたらしいのだが、税関にはCD-ROMドライブのあるパソコンすらなく何の問題もない単なる風景映像であることを証明することもできなかったという。 それが当時のマルチメディア環境の現状だった[要出典]。
Windows NTの登場による32ビットOSへの移行を促す意味もあり、Win32sというドライバ/APIがマイクロソフトから供給された。これはWindows 3.1の386エンハンストモード上で動作する32bitプログラムのためのドライバ/APIであり（WinNTのAPIであるWin32のサブセットなのでWin32s）、これにより初期の32ビットアプリケーションの開発を多少容易にした。
また、ファイルシステムにおいてはBIOSを介した16ビットディスクアクセスが基本的に用いられていたものの、Windows 3.1の386エンハンストモードでは常設スワップファイルに対してのみ32ビットでのアクセスが可能となった。さらに、Windows for Workgroups 3.11では完全な32ビットディスクアクセスが実現された。
Windows 95以降、レジストリを中心にWindowsのコンフィグレーションがブラックボックス化されてしまったのに対し、Windows 3.1以前のWindowsは比較的中身の理解しやすいシステムだったと言える。
Windows 3.1時代のシステムの柔軟性を生かして、日本で未発売のWindows for Workgroupsの差分のシステムファイルを日本語版Windows3.1（DOS/V版）に移植をしたり、i286で動作する英語版Windows 3.1[20]や日本未発売のWindows for WorkgroupsにWin/V等の日本語パッチを当てるということも出来た。
In addition, Tranpedia is simply not responsible for any show is only by translating the writings of foreign licenses that are compatible with CC-BY-SA license information.
It becomes CrossFireX which is available for parallel movement now in up to four GPU (as for the dual GPU card of the GPU2 unit deployment, accessible to the again normal single GPU card to four pieces to two pieces).
CrossFire (the first generation) - September 27, 2005 [1]
Software CrossFire (the second generation)
CrossFireX (the third generation) - September 19, 2007
Connection method
At first I need a motherboard having the expansion slot which I can only insert several of graphics cards and them in and the latest device driver and, in constitution of the multi-GPU environment by CrossFire, must be all a thing corresponding to CrossFire.
Procedure
I prepare a motherboard equipped with a CrossFire-adaptive chipset and two graphics cards of the same model corresponding to CrossFire (or more than two).
According to a manual, I connect a graphics card to PCI Express connector and connect each card with a bridge cable (Native CrossFire). I perform connection (mostly I connect "CrossFire Edition" to one near a CPU) of both to PCI Express connector according to a manual and, in the case of a model released before 1950XTX, turn on an exclusive output cord.
I start a PC and validate CrossFire setting in utility software "AMD Catalyst".
Construction is possible, but, as for the Radeon 1000 series released before it, structure is complicated, and, as for Radeon 2000, HD 3000, HD 4000, the HD 5000 series, it is necessary to prepare for a model (e.g.,: in "RadeonX1900 CrossFire Edition" "RadeonX1900XTX/XT/PRO") same as thing (I may call this "a master" or "a master board") and it of "CrossFire Edition" if I prepare the same model. In addition, the lineup called "CrossFire Edition" did not exist after 2007 and was unified by a lineup that it supported ATI CrossFire or ATI CrossFireX.
In addition, in Radeon R9 290X, XDMA where the connection with the bridge cable becomes needless is implemented [2].
Because the CrossFire standard is made open, it is made in ATI and can build even product made in other companies chip set such as not only the motherboard mounted with a chipset made in AMD but also Intel. If it is Intel, after intel P965 Express, I can build it if it is a motherboard equipped with PCI Express *16 slot more than two (975X, P35, P45, P55, H55, H57, X58). It is said that I have the superiority over the third party including Intel which is a rival on competition with NVIDIA as a reason throwing the CrossFire architecture open [the source required]. On the other hand, NVIDIA refused the SLI correspondence with the motherboard which was not equipped with a chipset (tip such as the PCI Express switch made in or NVIDIA) made in the company, but announced that I provided a license of SLI in a part of the chip set "AMD 9" series in the next term of AMD in April, 2011 in intel X58 chip set in August, 2009 [3]. It is a part, but "the limit by the difference in platform chip set" will be in this way taken away by CrossFire, SLI.
It is difficult to increase the number of PCI Express lanes, and there are many things changing number of the lanes 8 with two. In correspondence with CrossFire, number of the lanes 16 includes ATI CrossFire Xpress 3200, AMD 790FX, intel X38, X48, X58 to two things.
"The rendering of the alternation frame" and "rendering of top and bottom or the right and left division" are common in the multi-GPU environment, but I divide 32 pixels of whole into a block of every direction in CrossFire, and method "SuperTiling mode" [4] doing rendering (to put it simply, rendering doing the part between white trouts of a field of the chess namely the checkerboard or black trouts at a time) supports the block of one tobashi.
Because mirroring of the memory is performed in CrossFire (CrossFireX), as for the available memory gross weight, it is really 4GB or thereunder by application even if, for example, I use two pieces of cards equipped with a 4GB graphics memory without it being to 8GB of 4GB *2.
When I perform GPGPU distributed processing using OpenCL in AMD multi-GPU environment, it is recommended that I turn off CrossFire (CrossFireX) [5].
In addition, confirmation is necessary for the specifications such as total electricity, 12V1, 12V2 of the power supply unit on the occasion of enlargement. There is the risk such as the motherboard damage, and attention is necessary in one [the source required] of when I make CrossFire constitution with a power supply unit of inferior quality when it is the worst.
Derivation standard
Hybrid CrossFire (Hybrid CrossFireX)
A technique [6] to let GPU on the graphics card and GPU with a built-in AMD chipset cost parallel computation [7] [8].
In addition, Tranpedia is simply not responsible for any show is only by translating the writings of foreign licenses that are compatible with CC-BY-SA license information.
