2016년 11월 15일 화요일

Microsoft Windows 3.x

Microsoft Windows 3.x

Microsoft > Microsoft Windows > Microsoft Windows 3.x
Windows 3.x
Microsoft Windows family
Developer
Microsoft
Website [1]
Release information
Release day 1990May 22 [info]
Latest stability version A Japanese edition: 3.1 (May, 1993)
English version: 3.11 - 1993December [info]
Source model Closed Source
License Microsoft EULA
Kernel type (3.0) / (3.1) which there is no ?
Support state
The support end: December 31, 2001 (the American date and time)
The license publication end: November 1, 2008 (the American date and time) [1] [2]

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.

A solitaire mine sweeper is attached by Windows 3.1 リバーシ solitaire in Windows3.0.

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.

Change of the shipment number

  • Windows3.0 (the whole world)
    • -400,000 June 22, 1990
    • -1,000,000 December 30, 1990
    • More than -3,000,000 May, 1991 [4]
  • Windows 3.1 (the whole world)
    • 1 million April 6, 1992 - orders [5]
    • 1 million opening shipment [6]
    • I sell 1 million of them in -1 week on April 12, 1992 [7]
    • -25,000,000 May, 1993 [8]
    • -40,000,000 end of January, 1994
    • -60,000,000 January, 1995
    • -100,000,000 August, 1995 [9]
  • Windows 3.1 (North America)
    • I sell 1 million of them from - release in 50 days on May 26, 1995 [10]
  • Windows 3.1 (Japan)
    • May 14, 1993 - Japan electroplate, order 65,000 [8]
    • -1,460,000 May 17, 1994 [11]
    • February, 1995 -3,000,000 of them breakthrough [12]
    • -4,020,000 end of May, 1995 [12]

Support model

  • 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)
  • The EPSON PC series (Seiko Epson)
  • The FMR series (Fujitsu)
  • FM TOWNS (Fujitsu)
  • The J-3100 series (TOSHIBA)
    • 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.
In addition, I was able to call a screen similar to the Task Manager by double-clicking a desktop background.
Window
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 3.0、3.1では、標準でネットワーク (LAN) 機能自体が搭載されておらず、LAN Manager ClientなどDOSベースのネットワーク機能に頼っていた。LAN Manager ClientはWindows NT ServerのCD-ROMなどに収録され、TCP/IPやNetBEUI、NetWare互換プロトコルなどのプロトコルが使えた。また、Windows for Workgroups (WfW) 3.1はWindows 3.1にWindowsベースでのネットワーク機能を付加するアドオンとして発表、販売された。ただし、この段階ではネットワークプロトコルとしてNetBEUIかNetWare互換プロトコルしか選択できなかった。その後、WfW 3.11が完全なWindows製品として発売され、後にこのWfW3.11向けにTCP/IPプロトコル用ドライバも提供された。なお、WfWは日本語版は開発されていない。

インターネットが普及してくると、Windows 3.1およびWfW 3.11向けにInternet Explorer（16bit版）が公開され、これにはOutlook Express（16ビット版）や電話回線経由でインターネットに接続（ダイヤルアップ）するためのダイヤラーなどが添付されていた。インターネットの閲覧やメールの送受信はInternet Explorer添付のダイヤラーを使ったダイヤルアップの他、LAN Manager Clientをインストールしてある場合やWfWではLAN経由でも可能である。

ちなみに、Internet Explorer標準添付のダイヤラーはPC/AT互換機用だったため、PC-9800シリーズやPC-9821シリーズなどでダイヤルアップ接続する場合は市販ソフトなどを別途用意する必要があった。

その他、サードパーティ数社（Trumpet等）もPC-9800シリーズなどでもダイヤルアップ可能なインターネット接続ソフトを提供し、TCP/IP機能やウェブブラウザ（MOSAIC等）などを発売した。

プロテクトモードのサポート

Windowsは3.0のスタンダード・モードおよびエンハンスト・モードからプロテクトモードのサポートが始まった。

厳密には、WindowsはWindows/386 2.xからプロテクトモードを利用しているが、このバージョンでは内部的に80386で導入された機能をプロテクトモードで使用し、アプリケーションには仮想86モードを提供するというものであり、アプリケーションからはプロテクトモードの導入に伴うメリットは非常に限定的だった。 これがWindows 3.xのスタンダードモードとエンハンストモードは、Windowsの大半のモジュールがプロテクトモードで動作する16ビットのコードで構成され、アプリケーション（WIN16アプリケーション）もプロテクトモードで動作する16ビットのコードで構成されるように変更された。 さらにエンハンストモードでは、80386で導入されたメモリ管理機能をプロテクトモードで動作するシステムのコードに実装し、IA-32のページングを利用した仮想記憶もサポートし、実メモリ以上のメモリをアプリケーションが確保できるようになった。 また Windows 用のデバイスドライバとして、80386で導入された機能をプロテクトモードで活用した VxD デバイスドライバもサポートされた。 従来のWindowsは常にメモリが不足気味だったが、3.0からのプロテクトモードをサポートした結果、Windows自身とそのアプリケーションは、（コンベンショナルメモリ）+（EMS）よりも高速で大量のメモリを使用可能なプロテクトメモリを利用可能になった。 そのため、MS-DOSではメモリ不足から実現不可能だった大型アプリケーションも、Windows用に開発されるようになった。

このことは、Windowsが次世代アプリケーションの実行環境としてMS-DOSの後継の地位を築く理由の一つになった。

なお、ここで言うメモリの速度とは、ハードウェアの速度のことでは無く、EMSはバンク切り替えがあるためにその切り替えのオーバーヘッド分低速であるということである。実際、プログラムをEMSにロードすることにより、リアルモードでも実行可能な大規模アプリケーションも存在したが、ほぼ常時バンク切り替えを繰り返すために低速だった。

32ビット時代へ

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 3.1から新しいバージョンへのアップグレード / アンインストール

Windows 3.1からは、Windows 95かWindows 98(Second Editionも含む)にのみアップグレードできる。その後継であるWindows Meや、Windows 2000にできない。また、Windows 95かWindows 98のどちらにアップグレードしても、後にそのバージョンをアンインストールしてWindows 3.1に戻せる。

その他

個々のプログラムの設定は、それぞれのプログラムが持つiniという拡張子が付けられたファイル、もしくはwin.iniやsystem.iniなどのWindowsのシステムファイルで行っていた。Windowsそのものの設定もwin.iniとsystem.iniで行っていた。これらはテキストファイルであり、テキストエディタで編集を行うことができたため、何かしらの設定変更の後Windowsが立ち上がらなくなっても、MS-DOS環境などからwin.iniやsystem.iniの中身を修正して復旧することができた。Windows 3.1で採用された頃のレジストリは、ファイルの関連付けなどに使用される程度だった。

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等の日本語パッチを当てるということも出来た。

本OSの起動音「tada.wav」は、以降のWindows OSの全てに搭載されている。

脚注

[ヘルプ]
  1. ^ The end of an era - Windows 3.x
  2. ^ 18年以上の歴史を築いた「Windows 3.x」がついに終了 - Gigazine 2008年11月6日
  3. ^ 『日経産業新聞』 1991年3月14日、6面
  4. ^ 『日経産業新聞』1991年5月8日付
  5. ^ 『日経産業新聞』1992年4月7日付
  6. ^ 脇英世『Windows入門』岩波書店、1995年12月20日第1刷、1996年1月6日第3刷、ISBN 4-00-430420-2、74頁。
  7. ^ 『日経産業新聞』1992年5月18日付
  8. ^ a b 『日経産業新聞』1993年5月17日付
  9. ^ 脇英世、前掲書v頁。
  10. ^ 『日本経済新聞』1995年8月30日付夕刊
  11. ^ 『日経産業新聞』1994年6月9日付
  12. ^ a b 『日経産業新聞』1995年6月20日付
  13. ^ ソフマップタイムス1992年1月号News flash「快適なWindows 3.0を目指して」
  14. ^ なお、NEC版では「IMEかな漢字変換」という名前だったほか、これとは別にNEC独自のIMEも付属した。IBM版ではMS-IMEとIASインタフェースかな漢字変換プログラムが切替可能だった。
  15. ^ 岩淵明男『マイクロソフト・ウインドウズ戦略のすべて』TBSブリタニカ、1993年10月7日初版、ISBN 4484932288、44-45頁。
  16. ^ 戸内順一『Windows3.1マスターマニュアル』HBJ出版局、1994年3月29日初版、ISBN 4-8337-4501-1、96ページ
  17. ^ 海老原浩之、川俣晶共著『Windows3.1スペシャル』技術評論社、1993年9月15日初版、ISBN 4-87408-573-3、120ページ
  18. ^ 高橋良明『すぐに使えるWindows3.1』ソフトバンク、1993年10月15日初版、ISBN 4-89052-455-X、138ページ
  19. ^ 「98は本当にMacに追いついたか？」、月刊ソフマップワールド1994年4月号（Vol.56）、p11。
  20. ^ PC-9800シリーズ用英語版は486SX（25MHz）以上でないと動作しない。
「https://ja.wikipedia.org/w/index.php?title=Microsoft_Windows_3.x&oldid=61794112」から取得

This article is taken from the Japanese Wikipedia Microsoft Windows 3.x

This article is distributed by cc-by-sa or GFDL license in accordance with the provisions of Wikipedia.

Wikipedia and Tranpedia does not guarantee the accuracy of this document. See our disclaimer for more information.

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.

0 개의 댓글:

댓글 쓰기

피드 구독하기: 댓글 (Atom)