尚未添加到任何已有项目中的内容:
疑点暂存
Win 3.11 for workgroups Hebrew RTM(the one version 3.11.050):
该版hebrew rtm比后发RTM（无050标识）出的更早，两者皆为RTM。
Win 3.11 for workgroups Russian 1993-10-14 version:
情况可能和win3.2 redchina一样，但因为语言不通找不出决定性的证据。
可能有用的key
部分过于难看的内容经过排版，key本身不动。
WindowsXP 2520 Pro 英文版－－60天免激活序列号：
RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
Windows XP 2505 RC1－－序列号：
DTWB2-VX8WY-FG8R3-X696T-66Y46
Q3R8Y-MP9KD-3M6KB-383YB-7PK9Q
411Y0-URB45-34R3B-310N6-70U51
F0R6R-347JU-57IC3-M0V34-11Z16
50M38-0DY53-7UPU5-7H380-M8111
Microsoft Whistler Professional Beta 2 2462繁体中文版
S/N：QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Microsoft Windows Millennium B2 V4.90.2438 98 第三版中文完整测试版
S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG
Microsoft Windows Whistler Pro CD-Key：
F6PGG-4YYDJ-3FF3T-R328P-3BXTG
...............................................
Windows 2000 Professional RC3
VXKC4-2B3YF-W9MFK-QB3DB-9Y7MB
Windows 2000 Server RC3
H6TWQ-TQQM8-HXJYG-D69F7-R84VM
..............................................
Windows 95 v4.00.950 R2 : 875-7215850
Windows 95 v4.00.950 R3/R6 : 975-4769754
Windows98 build 1708 and 1720 and maybe others -
Serial Number: HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Memphis (WIN 98): K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
Win98 Second Edition V 4.10.2174 A
Serial Number C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Microsoft Windows Whistler Build 2505RC1/2509postRC1
BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
Microsoft Windows Whistler Beta 2 Build 2502/2504
JJWKH-7M9R8-26VM4-FX8CC-GDPD8
Microsoft Windows Whistler Beta 2 Build 2486
BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
Microsoft Windows Whistler Beta 2 Build 2474-2499
DTWB2-VX8WY-FG8R3-X696T-66Y46
Microsoft Windows Whistler Beta 2 Build 2469
Q3R8Y-MP9KD-3M6KB-383YB-7PK9Q
Microsoft Windows Whistler Beta 1 Build 2462-2465
DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
Microsoft Windows Whistler Build 2296 & 2458
QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
VXKC4-2B3YF-W9MFK-QB3DB-9Y7MB
Windows 98 Build 1708/Build 1720:
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Windows 98 Build 1708:
BBH2G-D2VK9-QD4M9-F63XB-43C33
Windows 98 Build 1720:
HGBRM-RBK3V- M9FXV-YCXDK-V38J4
Windows 98 Build 1723:
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Windows 98 OSR Beta Refresh beta 2 and up to build 2150:C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 95(other build keys):
875-7215850
100-1208613
757-2573155
Windows 95 (build 490) : 100-1208613
Windows 98 OSR Beta Refresh - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 Beta 2 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 Build 2150 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 v4.10.2126 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 v4.10.2131 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 97 Code: 26495-OEM-0004791-53803
.............................................
Windows XP Home Build 2542-2600
s/n: 4C4DQ-323QV-XBWTX-CX8YQ-3KJKM
Microsoft Windows Vista Build 5308
S/N: Client_S/N: R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Server_S/N: WBVG8-4JPQB-6HJ6H-XH7YY-D2GQY
Windows Vista 5308
S/N: WGDJW-B8DYC-WVKX4-6MKF4-B8PK8
Windows Vista Beta 2 32bit
S/N: V4TYH-74MWQ-6VTBQ-XRD3V-9MMX2
Windows vista beta 2 build 5342
S/N: GKFV7-F2D9H-QKYXY-777P3-4M73W
TGX39-HB48W-R29DH-6BVKB-3XFDW
Q8WDJ-TR4KJ-X8WHM-GVGV3-H74C3
CKY24-Q8QRH-X3KMR-C6BCY-T847Y
C6RDR-7PC77-476GM-VYMGD-DDH2B
R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Windows Vista Beta 5259
S/N: TGX39-HB48W-R29DH-6BVKB-3XFDW
windows vista beta2
S/N: BV8W7-2Q9TX-KDHP9-9B98J-439WT
Windows Vista Beta2 Build 5384.4
S/N: PVYFQ-2JTBV-9KXQ2-FQHDY-MTBVH
Windows Vista build 5536
Name: Chris
S/N: 6BJ24-CGPHV-FKX6G-4RJ3C-T24FV
for any think ask me:) i am a webmaster
Windows Vista RC1 (build 5600)
S/N: BV8W7-2Q9TX-KDHP9-9B98J-439WT
Windows Vista RC2 5744
S/N: PVYFQ-2JTBV-9KXQ2-FQHDY-MTBVH
Windows Longhorn
s/n: WDRCM-DRVGY-T3YQY-V47YP-XMF9B or
s/n: WDRR9-TX2PH-R3633-6G882-KBKTM or
s/n: WDRYW-G682C-BCDFJ-FB2HJ-YCXTM or
s/n: WDTCJ-PQGH8-76CRJ-CCH4F-RYBPY or
s/n: WDTQ4-JTC3D-DQHD2-QBD2M-4DDGM or
s/n: WDV2M-H8QVB-JDV9X-HW7M4-HPCKB or
s/n: WDV47-MP3XD-D2MD6-7WDPX-X89TM or
s/n: WDVQX-KQRY7-9R6F4-W76K4-BJ9TM or
s/n: WDVRV-JHHYY-49893-HPGRB-78DGM
Windows Longhorn 40 CD-keys
Name: Windows Longhorn 40 CD-keys
S/N: DPTWG-M9PGK-2HT2J-JT9R9-6V8WM
WDYW9-4VJ63-RB8PW-46Q37-9M72Y
WF224-7QFP2-4H2H2-62DGW-KXFCY
WF2Q7-R9WJF-24JGX-G6CH8-VWYPY
WF3X4-8WV6F-G8XVK-QYP47-P92KB
WF4BF-QYRYM-TJMXP-BGMKP-CV4CY
WF4C4-29K22-RPTG6-WXW46-BVR9B
WF6BD-RHP7T-3BG4B-9PFH8-T3T6M
Windows Vista/Longhorn(Build 5308)
S/N: QGVK9-4Y2VT-6YXTH-74QJV-9G3GG
Got it as a beta tester
Windows 7 Beta 32-bit
S/N: GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
Windows 7 beta Nov. 08 build 6801
S/N: J7PYM-6X6FJ-QRKYT-TW4KF-BY7H9
D67PP-QBKVV-6FWDJ-4K2XB-D4684
HQDKC-F3P6D-C9YYM-HRB89-QDBB7
76DX2-7YMCQ-K2WCP-672K2-BK44W
2RG93-6XVFJ-RKHQ7-D2RTT-3FMQT
TT63R-8JGWP-WWT97-R6WQC-4CVWY
YQJX6-D6TRM-VWBM7-PHDJK-YPXJH
Q7J7F-GQHBT-Q42RQ-2F8XV-2WKKM
Windows 7 Build 7000
7XRCQ-RPY28-YY9P8-R6HD8-84GH3
RFFTV-J6K7W-MHBQJ-XYMMJ-Q8DCH
482XP-6J9WR-4JXT3-VBPP6-FQF4M
GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
TQ32R-WFBDM-GFHD2-QGVMH-3P9GC
8XPDH-PCKKG-6MPKT-FTM67-ZFMWG
4HJRK-X6Q28-HWRFY-WDYHJ-K8HDH
GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
QXV7B-K78W2-QGPR6-9FWH9-KGMM7
6JKV2-QPB8H-RQ893-FW7TM-PBJ73
RFFTV-J6K7W-M HBQJ-XYMMJ-Q8DCH
JYDV8-H8VXG-74RPT-6BJPB-X42V4
D9RHV-JG8XC-C 77H2-3YF6D-RYRJ9
Windows 7 RC
S/N: Q3VMJ-TMJ3M-99RF9-CVPJ3-Q7VF3
Windows XP Beta 2 Build 2428
RBDC9-VTRC8-D7972-J97JY-PRVMG
s/n: : QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
WINDOWS 97 BETA : MENPHIS
2859500057111-34276（这啥？）
Microsoft Office 2007 2007 (keine Beta)
S/N: KGFVY-7733B-8WCK9-KTG64-BC7D8
ist die Serial für die Verkaufsversion - nix Beta oder so
Microsoft Office 2007 beta
S/N: HGJH4-9W9FY-8C7B6-P2H6X-9DQ9T
Microsoft Office Professional 2010 Beta
Product Key: 49QGP-V2MRB-XYMYK-Y26V2-YVXYK
Microsoft Office Professional Plus 2007 2007 - Beta2
Name: anything
S/N: MTP6Q-D868F-448FG-B6MG7-3DBKT
Microsoft Windows Server 2008 Beta
<u>Enterprise Edition:</u>
S/N: TFGPQ-J9267-T3R9G-99P7B-HXG47
<u>Standard Edition:</u>
S/N: 2T88R-MBH2C-M7V97-9HVDW-VXTGF
<u>Datacenter Edition:</u>
S/N: GQJJW-4RPC9-VGW22-6VTKV-7MCC6
<u>Itanium Based Systems Edition:</u>
S/N: CQ936-9K2T8-6GPRX-3JR9T-JF4CJ
<u>Windows Web Server Edition:</u>
S/N: GT8BY-FRKHB-7PB8W-GQ7YF-3DXJ6
Note: Product Keys for Evaluation
Microsoft Windows Seven (7) Beta
S/N: Windows 7 Beta 32 Bit:
* 6JKV2-QPB8H-RQ893-FW7TM-PBJ73
* QXV7B-K78W2-QGPR6-9FWH9-KGMM7
* 4HJRK-X6Q28-HWRFY-WDYHJ-K8HDH
* GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
* TQ32R-WFBDM-GFHD2-QGVMH-3P9GC
Windows 7 Beta 64 Bit:（其他来源补足）
JYDV8-H8VXG-74RPT-6BJPB-X42V4
7XRCQ-RPY28-YY9P8-R6HD8-84GH3
D9RHV-JG8XC-C77H2-3YF6D-RYRJ9
RFFTV-J6K7W-MHBQJ-XYMMJ-Q8DCH
4HJRK-X6Q28-HWRFY-WDYHJ-K8HDH
office 2007 beta 2
Name: open lic key no nead to activate
S/N: RQCRJ-FCTYM-V3PDF-GRD46-9YHXQ
enjoy
Office Professional Plus 2007 Beta 2
S/N: MTP6Q-D868F-448FG-B6MG7-3DBKT
Windows Server 2003 Enterprise rc2 Beta2
S/N: s/n: VQ83Q-89DJ9-X9TG9-QF6MC-FRV2D
Windows .NET Server 2003 German
s/n: CKY24-Q8QRH-X3KMR-C6BCY-T847Y
Windows 2003 Candidated Release
s/n: HJYCJ-647BB-76FYQ-J76JT-P78XD
...........................................
Microsoft Windows 98 1720+
#/HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Microsoft Windows 98 Build 1723
#/HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Microsoft Windows 98 RC4
#/320DD-23GW3-2H9CJ-39FNE-3E3IS
Microsoft Windows 98 RC5
#/K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
MS Frontpage 98 3.01 Beta（几个标题都一样）
8067-4039161
8123-0123512
9978-3492547
MS IE Administration Kit 3.1 (IEAK)
Install code: 1234567792
MS Outlook 98 Final Beta
#/1112-1111111
Windows 95 (build 490)
100-1208613
Windows 95 950 r2
8757215850
Windows 95 950 r6
9754769754
Windows 95 v4.00.950 R2
875-7215850
Windows 95 v4.00.950 R3/R6
975-4769754
WINDOWS 98
RC5 CD KEY - K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
Windows 98 Build 1708
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Windows 98 SE RC3 Build 2222
C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 Second Edition RC3 Build 2222
C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows RC5
Possible key is K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
Memphis 1713 Released (Win98)
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Microsoft Money v2.01 beta for Windows
00-105-0200-99999979
...........................................
MicroSoft Windows 98 Second Edition RC1
C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
MicroSoft Windows 98 Second Edition RC2
FTBT6-96WDC-384FQ-WF482-Q3M73
...........................................
Windows 95 950 r2 - 875-7215850
Windows 95 950 r3 - 975-4769754
Windows 95 950 r6 - 975-4969754
...........................................
（这些看起来是被截断了）
Memphis 1410 beta 1 :09-A12345
Microsoft Money v2.01 beta (Win3) : #: 00-105-0200-99999979
Microsoft Office 97 Pro Beta : cdkey: 0701-0743365
Microsoft Works v4.0 beta : #: 33977-053-0111756
...........................................
Microsoft.Windows.Server.2003.RC2.3718.CHS.iso
SN : CKY24-Q8QRH-X3KMR-C6BCY-T847Y
SN : KRMXQ-BJDUW-J89MB-7767F-PVR8M
...........................................
windows vista rc2 中文版
FCDW7-QP4XD-R48GT-Q47Y3-HTR9P
...........................................
Windows Server 2008 R2 RC各版的测试产品序列号：
·Windows Server 2008 R2 Release Candidate Enterprise(标准版)
Product Code ： Q7Y83-W4FVQ-6MC6C-6QQTD-TPM88
·Windows Server 2008 R2 Release Candidate Standard(企业版)
Product Code ： V4KRB-QDWK2-GVT4X-BV4XG-34TV4
·Windows Server 2008 R2 Release Candidate Datacenter(数据中心版)
Product Code ： WXGKX-XXW8X-P8KTJ-PFX7T-DPYYW
·Windows Web Server 2008 R2 Release Candidate(WEB版)
Product Code： RBBKH-BVD6B-74FV9-RYPJ7-TCFXB
...................................................
Windows Server 2008 Enterprise RC1
产品密钥 1: HVFX4-C6DY3-M792V-DBXXG-8T24Q
产品密钥 2: 83XTG-V8DHP-TF73Y-G7MCX-4Q4XB
产品密钥 3: H6BXB-CQWDR-QRRJD-9HV7R-TMGKJ
产品密钥 4: CV3TD-JJ4G7-P2TJG-3MMXH-YXRWR
产品密钥 5: H6V9C-PJF42-H29WV-HW334-WYYM4
Windows Server 2008 Standard RC1
产品密钥 1: VWRJT-DJJYR-QG7YD-Q7X73-TQCHT
产品密钥 2: 87PC6-CTW7M-C3DVH-TYGGR-BRJPM
产品密钥 3: YKYMG-C68WD-4RCGB-3FMJT-FG637
产品密钥 4: TKGXB-G6PYQ-Q7F3M-G9HJW-TXCBT
产品密钥 5: Q642B-4WHQF-DPQT4-WCDJJ-J7RG2
Windows Server 2008 Datacenter RC1
产品密钥 1: QX9DX-DYXT8-G3CMF-G4F9F-Y9MPP
产品密钥 2: GDQRG-PX42M-YYYBK-7Y7XD-G76GP
产品密钥 3: RDPFX-8TPGR-3PMCX-P68W7-JTCWP
产品密钥 4: C2YRQ-4JVDJ-GCCTG-Y3JWB-GXTQJ
产品密钥 5: MXD74-82KC7-MV8MR-XRMK9-WVT7R
................................................
2000 RC-1/SP-1
K4CJ8-XHQMW-YF7HH-MYRGM-J3DRW
WINDOWS 7 Release Candidate 1:
C43GM-DWWV8-V6MGY-G834Y-Y8QH3
6JQ32-Y9CGY-3Y986-HDQKT-BPFPG
KBHBX-GP9P3-KH4H4-HKJP4-9VYKQ
GPRG6-H3WBB-WJK6G-XX2C7-QGWQ9
P72QK-2Y3B8-YDHDV-29DQB-QKWWM
Q3VMJ-TMJ3M-99RF9-CVPJ3-Q7VF3
BCGX7-P3XWP-PPPCV-Q2H7C-FCGFR
9JBBV-7Q7P7-CTDB7-KYBKG-X8HHC
KGMPT-GQ6XF-DM3VM-HW6PR-DX9G8
MT39G-9HYXX-J3V3Q-RPXJB-RQ6D7
MM7DF-G8XWM-J2VRG-4M3C4-GR27X
MVBCQ-B3VPW-CT369-VM9TB-YFGBP
MVYTY-QP8R7-6G6WG-87MGT-CRH2P
6F4BB-YCB3T-WK763-3P6YJ-BVH24
RGQ3V-MCMTC-6HP8R-98CDK-VP3FM
............................................
Microsoft Office 2000 Beta 2 :
s/n: BBH2G-D2VK9-QD4M9-F63XB-43C33 or
s/n: MP4F9-W6C8V-HTCCT-T7M7R-Y7K3Y
Microsoft SMS 2.0 beta2 For WindowsNT :
s/n: 11111-11111-11111-11111-11111
Microsoft SQL Server 7.0 Enterprise Edition Build 611 :
s/n: 111-1111111
Microsoft Windows 98 OEM Service Release 1 Beta 1 :
s/n: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
（此处合并）
Microsoft Windows 98 OSR Beta Refresh :
Microsoft Windows 98 OSR1 v4.10.2126 :
Microsoft Windows 98 OSR1 v4.10.2131 :
Microsoft Windows 98 OSR1 Build 2150 :
Microsoft Windows 98 OSR1 Beta 2 :
Microsoft Windows 98 Second edition Build 2162 :
CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
..................................................
Windows 95 (build 490) .........................................100-1208613
................................................................757-2573155
................................................................875-7215850
..................................................
Windows XP Build 2446, 2454 & 2458 CD-Key: QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Windows XP Beta 2 (2462)
CD-Key: DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
Windows XP Build 2469
CD-Key: Q3R8Y-MP9KD-3M6KB-383YB-7PK9Q
Windows XP Build 2474 - 2499
CD-Key: DTWB2-VX8WY-FG8R3-X696T-66Y46
Windows XP Build 2502-2505 (RC1)
CD-Key: BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
Windows XP 25xx/350x (60 Days)
CD-Key: RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
Windows XP 2542+ (30 Days) Home
CD-Key: BQJG2-2MJT7-H7F6K-XW98B-4HQRQ
Windows XP 2542+ (30 Days) Pro
CD-Key: BX6HT-MDJKW-H2J4X-BX67W-TVVFG
Windows XP PRE-RTM 2600
CD-Key: BX6HT-MDJKW-H2J4X-BX67W-TVVFG
BX6HT-MDJKW-H2J4X-BX67W-TVVFG (2542專業人員僅僅)[2600]
BQJG2-2MJT7-H7F6K-XW98B-4HQRQ (2542個人僅僅）
Microsoft Whistler Professional Beta 2 2462繁體中文版 S/N：QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Microsoft Windows Millennium B2 V4.90.2438 98 第三版中文完整測試版 S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG
Microsoft Windows Whistler Pro CD-Key：
F6PGG-4YYDJ-3FF3T-R328P-3BXTG
Microsoft Windows XP 2428 中文版
S/N：F6PGG-4YYDJ-3FF3T-R328P-3BXTG or
S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG or
S/N：QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Microsoft Windows XP Professional Beta2 build 2505) 中文繁體專業完整版
S/N：RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
..................................................
Windows Millennium Beta 2 Build 2419.5 S/N:RBDC9-VTRC8-D7972-J97JY-PRVMG
..................................................
Microsoft Whistler Person build 2410－－ SN：F6PGG-4YYDJ-3FF3T-R328P-3BXTG
Microsoft Windows Whistler Pro
CD-Key：F6PGG-4YYDJ-3FF3T-R328P-3BXTG
Microsoft Windows XP 2428 S/N：F6PGG-4YYDJ-3FF3T-R328P-3BXTG or
S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG
..................................................
Microsoft Windows 2003 .NET
版本: Enterprise Edition
网址: www.microsoft.com
s/n: G4GC3-PWBMF-36BH6-3RXK8-D9V23 AktivationKey: 119501-164671-893012-496996-208900-871600-717516
Microsoft Windows Server 2003
版本: Enterprise rc2 Beta2
网址: www.microsoft.com
s/n: VQ83Q-89DJ9-X9TG9-QF6MC-FRV2D
Microsoft Windows Vista
版本: Beta 2 Build 5270
网址: www.microsoft.com
S/N: R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Microsoft Windows Vista
版本: Build 5308
网址: www.microsoft.com
S/N: Client_S/N: R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Server_S/N: WBVG8-4JPQB-6HJ6H-XH7YY-D2GQY
Microsoft Windows Whistler
版本: RC1 and RC2
s/n: BFB47-3C7FY-WHR6H-G9X4D-7TTFJ or s/n: RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
Microsoft Windows Whistler
版本: 2542 Pro
s/n: BX6HT-MDJKW-H2J4X-BX67W-TVVFG
Microsoft Windows Whistler
版本: 2542 Personal
s/n: BQJG2-2MJT7-H7F6K-XW98B-4HQRQ
WINDOWS 97 BETA : MENPHIS
网址: www.microsoft.com
2859500057111-34276
Windows
版本: Whistler
网址: www.microsoft.com
s/n: F6PGG-4YYDJ-3FF3T-R328P-3BXTG or s/n: DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
Windows .NET Server 2003 German
版本: Enterprise RC2
网址: www.microsoft.com/windows.net
s/n: CKY24-Q8QRH-X3KMR-C6BCY-T847Y
Windows .Net Enterprise Server for itanium
网址: www.microsoft.com/
s/n: K74W7-WR4HR-H7P6B-4V9BF-XJD6Y
Windows 2003
版本: Candidated Release 2
网址: http://www.tcs.com
s/n: HJYCJ-647BB-76FYQ-J76JT-P78XD
Windows 2003
版本: Server.net
网址: http://www.tcs.com
s/n: K4RBR-F3K42-M9RXG-48TPR-H6BPB or s/n: C4C24-QDY9P-GQJ4F-2DB6G-PFQ9W
Windows 2003
版本: (.NET) German Retail
网址: http://www.tcs.com
s/n: C4C24-QDY9P-GQJ4F-2DB6G-PFQ9W
Windows 2003 Server
版本: .net
网址: www.microsoft.com
s/n: K4RBR-F3K42-M9RXG-48TPR-H6BPB or QW32K-48T2T-3D2PJ-DXBWY-C6WRJ or C4C24-QDY9P-GQJ4F-2DB6G-PFQ9W
microsoft windows xp home eidition
版本: sp2 built 2162
S/N: wwwjr-bx7cv-p32x2-c7vt3-qd6bp
Win95 Key计算
WINDOWS95 只要合於下述公式之序號，不必原告指定的「唯一」序號，仍可安裝。 ＡＢＣＤＥ-ＦＧＨ-ＩＪＫＬＭＮＯ-ＰＱＲＳＴ 1. ＡＢＣ 為 001 至 366 之間的三位數字。 2. Ｄ 為一固定數字 9 。 3. Ｅ為介於 5 至 9 之間的一位數字。 4. ＦＧＨ為英文字母 OEM 或 oem 皆可。 5. Ｉ為一固定數字 0。 6. ＪＫＬＭＮＯ 此六個數字之和為 7的倍數， 即Ｊ+Ｋ+Ｌ+Ｍ+Ｎ+Ｏ= 7×n ( n 為常整數 ) 7. ＰＱＲＳＴ 為介於 00000至99999之間的五位數字。 8. 此一公式，經測試，僅有一、二組無法使用。
Win3.2 doc
[Anonymous] 2020-01-18 23:05:01 3.2简体中文定制版那是微软中国专门定制的版本 [Anonymous] 2020-01-18 23:05:30 3.2的出现是被迫的。 [Anonymous] 2020-01-18 23:06:29 上次讨论的就是为什么明明有3.1，还要做3.2。 [Anonymous] 2020-01-18 23:08:06 3.2是中易宋体 [Anonymous] 2020-01-18 23:11:58 windows 3.2 之所以说是真正的官方定制版，是因为不仅仅系统深度汉化，而且系统中不支持中文的环境结构，也做了修改 [Anonymous] 23:12:39 让系统对于中文不再有“不兼容”的问题 [Anonymous] 23:13:21 而之前说的 3.1 的中文版，实际上只是个“浅显汉化版” [Anonymous] 23:14:59 3.1只是“UI”上汉化成了中文，然后加上了外挂式的中文显示环境 [Anonymous] 23:15:24 但实际上，3.1的内核，对于中文的支持是相当糟糕的 [Anonymous] 23:15:37 兼容性问题一大把 [Anonymous] 23:17:17 当时3.1刚出来时，只有“南极星”或者“中文之星”这样的“外挂汉字平台” [Anonymous] 2020-01-18 23:15:54 后来这件事还被传成了阴谋论，说微软发行3.2直接掐死了一些中文汉字软件 [Anonymous] 2020-01-18 23:16:46 所以我才说3.1和3.2背后的迷太多。 [Anonymous] 2020-01-18 23:17:22 说3.2是阴谋的也好，说3.2是我方强迫的也好， [Anonymous] 2020-01-18 23:22:55 7、8年前我专门给微软发过邮件，问过3.2这个版本是怎么来的时，微软有过粗略的解释 [Anonymous] 2020-01-18 23:33:42 当时微软回复的大概意思就是说： 3.2是为了适应市场需要，同时修复3.1版本对中文的核心兼容性问题，而专门定做和完善的版本，针对印刷和照排行业的需要，做了深度的改进 而且，3.2定制版的实践积累，为后来的朝鲜语、日语及其它东亚语言版本的完善，提供了宝贵的经验 [Anonymous] 2020-01-18 23:36:48 3.2这种东西有点类似于Windows 8 Chinese Language Edition吗 [Anonymous] 2020-01-18 23:37:47 实际上，3.2的重要性和意义，远超于你说的“单语言中文版” [Anonymous] 2020-01-18 23:38:21 3.2实际上是在积累东亚语言的定制经验 [Anonymous] 2020-01-18 23:39:36 也就是说，3.2中文版，是当时的“示例” [Anonymous] 2020-01-19 17:01:07 windows3.2+word6 几乎横扫所有非照排系统
Win95 RTM HellGod Warez(READNOW.TXT)
SuP all.... Well, here it is WINDOWS 95 GOLD.... this is the FINAL release that will be in stores on August 24th.... when you got to "System" to find out the version it'll say 4.00.950... DO NOT BE ALARMED.... you might say "duh, this is just 950!" WRONG.... the first version of 950 was 950 -r2 this is the GOLD version......the FINAL version This KICK ASS WaRe brought to you by the ONE AND ONLY: H e L L G o D Whenever ya see me in WaReZ or anywhere else, say, "SuP HeLL GoD!" This GREAT ware brought to you in accordance with swoop...... Greetz to aLL WaReZ gr00ps from HeLL GoD.....
其他细碎拮文
- 系统的启动问题！
我的机器装了Windows Whistler Advanced Server(5.00.2442)后，开始运行还能进系统，可差不多重启几次之后，就再也进不去了，老是定格在出现Logo之后，用Safe Mode也进不去，重装之后还是有问题，怎么办呢？万望赐教！
https://bbs.csdn.net/topics/10442785
- 关于在WindowsXP（ beta2 2442）下安装内猫的问题
我的内猫型号为TP—LINK的rockwell的11235芯片的5689HCF内猫，在WindowsXP（ beta2 2442）下安装TP—LINK公司的FOR WIN2000驱动，系统提示没有数字签名，继续安装系统自动重启，且显示为非正常关机。再次进入系统，能够找到猫但是驱动未安装，再次进行安装依然如此。但同样没有数字签名的NVIDIA的12.40驱动就能运行正常，请各位大虾赐教！
远古Windows 98 Beta版本列表
http://www.wintricks.it/faqlamer/win-ver.html
最迟的列表可能出现时间为2001年。仅供参考，列表中有错误信息！
- PAGINA 1/2
In questa tabella riassuntiva ho ritenuto utile inserire il semplice database di tutte le vers. di Windows 9x uscite sinora.....
da WINDOWS 95 a 98 VERSIONI + TABELLA
| RELEASE S.O. | VERSIONE | REVISIONE MS-DOS |
DATA + ORA | BUILD |
|---|---|---|---|---|
| Windows 95 final retail | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95 final OEM | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95a OSR1 final Update | 4.00.0950 a | 7.00 [4.00.0950] | 02-02-96 + 09:51:00 | 4.00.0951 |
| Windows 95B OSR 2.0 final OEM | 4.00.0950 B | 7.10 [4.00.1111] | 08-24-96 + 11:11:11 | 4.00.1111 |
| Windows 95B OSR 2.1 final Update | 4.00.0950 B | 7.10 [4.00.1111] | 04-10-97 + 12:14:00 | 4.03.1212 |
| Windows 95B OSR 2.1 final OEM | 4.01.0971 B | 7.10 [4.00.1111] | 06-25-97 + 09:07:10 | 4.01.0971 |
| Windows 95C OSR 2.5 final OEM | 4.00.0950 C | 7.10 [4.00.1111] | 11-26-97 + 12:16:00 | 4.03.1214 |
| Windows 98 Beta | ||||
| Windows 98 Beta pre-DR | 4.10.1351 | 7.10 [4.10.1351] | 12-16-96 + 13:51:00 | 4.10.1351 |
| Windows 98 Beta DR | 4.10.1358 | 7.10 [4.10.1358] | 12-20-96 + 13:58:00 | 4.10.1358 |
| Windows 98 pre Beta | 4.10.1378 | 7.10 [4.10.1378] | ? + ? | 4.10.1378 |
| Windows 98 pre Beta | 4.10.1410 | 7.10 [4.10.1410] | ? + ? | 4.10.1410 |
| Windows 98 pre Beta | 4.10.1423 | 7.10 [4.10.1423] | 04-08-97 + 04:23:00 | 4.10.1423 |
| Windows 98 Beta 1 | 4.10.1500 | 7.10 [4.10.1500] | ? + ? | 4.10.1500 |
| Windows 98 Beta 1 | 4.10.1508 | 7.10 [4.10.1508] | ? + ? | 4.10.1508 |
| Windows 98 Beta 1 | 4.10.1511 | 7.10 [4.10.1511] | ? + ? | 4.10.1511 |
| Windows 98 Beta 1 | 4.10.1525 | 7.10 [4.10.1525] | 06-18-97 + 10:09:00 | 4.10.1525 |
| Windows 98 Beta 1 | 4.10.1535 | 7.10 [4.10.1535] | 07-02-97 + 15:35:00 | 4.10.1535 |
| Windows 98 Beta 1 | 4.10.1538 | 7.10 [4.10.1538] | 07-12-97 + 15:38:00 | 4.10.1538 |
| Windows 98 Beta 1 | 4.10.1543 | 7.10 [4.10.1543] | ? + ? | 4.10.1543 |
| Windows 98 Beta 2 | 4.10.1544 | 7.10 [4.10.1544] | 07-31-97 + 15:44:00 | 4.10.1544 |
| Windows 98 Beta 2 | 4.10.1546 | 7.10 [4.10.1546] | 08-02-97 + 15:46:00 | 4.10.1546 |
| Windows 98 Beta 2 | 4.10.1550 | 7.10 [4.10.1550] | 08-10-97 + 17:21:00 | 4.10.1550 |
| Windows 98 Beta 2 | 4.10.1559 | 7.10 [4.10.1559] | 08-11-97 + 15:50:00 | 4.10.1559 |
| Windows 98 Beta 2 | 4.10.1564 | 7.10 [4.10.1564] | 08-14-97 + 15:50:00 | 4.10.1564 |
| Windows 98 Beta 2 | 4.10.1569 | 7.10 [4.10.1569] | 08-22-97 + 15:50:00 | 4.10.1569 |
| Windows 98 Beta 2 | 4.10.1577 | 7.10 [4.10.1577] | 09-04-97 + 15:50:00 | 4.10.1577 |
| Windows 98 Beta 2 | 4.10.1581 | 7.10 [4.10.1581] | 09-10-97 + 15:50:00 | 4.10.1581 |
| Windows 98 Beta 2 | 4.10.1593 | 7.10 [4.10.1593] | 09-25-97 + 15:50:00 | 4.10.1593 |
| Windows 98 Beta 2 | 4.10.1599 | 7.10 [4.10.1599] | 10-08-97 + 15:50:00 | 4.10.1599 |
| Windows 98 Beta 3 | 4.10.1602 | 7.10 [4.10.1602] | ? + ? | 4.10.1602 |
| Windows 98 Beta 3 | 4.10.1605 | 7.10 [4.10.1605] | ? + ? | 4.10.1605 |
| Windows 98 Beta 3 | 4.10.1614 | 7.10 [4.10.1614] | 10-24-97 + 16:14:00 | 4.10.1614 |
| Windows 98 Beta 3 | 4.10.1619 | 7.10 [4.10.1619] | 10-31-97 + 16:19:00 | 4.10.1619 |
| Windows 98 Beta 3 | 4.10.1624 | 7.10 [4.10.1624] | 11-06-97 + 16:24:00 | 4.10.1624 |
| Windows 98 Beta 3 | 4.10.1629 | 7.10 [4.10.1629] | 11-14-97 + 16:29:00 | 4.10.1629 |
| Windows 98 Beta 3 | 4.10.1633 | 7.10 [4.10.1633] | 11-18-97 + 16:33:00 | 4.10.1633 |
| Windows 98 Beta 3 | 4.10.1650 | 7.10 [4.10.1650] | 11-26-97 + 16:50:00 | 4.10.1650 |
| Windows 98 Beta 3 | 4.10.1650.3 | 7.10 [4.10.1653] | 12-03-97 + 16:50:03 | 4.10.1650.3 |
| Windows 98 Beta 3 | 4.10.1650.8 | 7.10 [4.10.1658] | 12-09-97 + 16:50:08 | 4.10.1650.8 |
| Windows 98 Beta 3 | 4.10.1666 | 7.10 [4.10.1666] | 01-14-98 + 16:06:06 | 4.10.1666 |
| Windows 98 Beta 3 | 4.10.1671 | 7.10 [4.10.1671] | 01-20-98 + 16:07:10 | 4.10.1671 |
| Windows 98 Beta 3 | 4.10.1677 | 7.10 [4.10.1677] | 01-30-98 + 16:07:07 | 4.10.1677 |
| Windows 98 Beta 3 | 4.10.1681 | 7.10 [4.10.1681] | 02-05-97 + 16:08:10 | 4.10.1681 |
| Windows 98 Beta 3 | 4.10.1687 | 7.10 [4.10.1687] | 02-12-98 + 16:08:07 | 4.10.1687 |
- PAGINA 2/2
Windows 98 a partire dalla vers. RC
WINDOWS 98 VERSIONI + TABELLA
| RELEASE S.O. | VERSIONE | REVISIONE MS-DOS |
DATA + ORA | BUILD |
|---|---|---|---|---|
| Windows 98 RC | ||||
| Windows 98 Beta RC0 | 4.10.1691 | 7.10 [4.10.1691] | 02-16-98 + 12:16:00 | 4.10.1691 |
| Windows 98 Beta RC0 | 4.10.1702 | 7.10 [4.10.1702] | 03-05-98 + 12:17:00 | 4.10.1702 |
| Windows 98 Beta RC0 | 4.10.1708 | 7.10 [4.10.1708] | 03-12-98 + 12:17:00 | 4.10.1708 |
| Windows 98 Beta RC0 | 4.10.1713 | 7.10 [4.10.1713] | 03-19-98 + 12:17:00 | 4.10.1713 |
| Windows 98 Beta RC1 | 4.10.1721.3 | 7.10 [4.10.1721] | 03-30-98 + 17:21:40 | 4.10.1721.3 |
| Windows 98 Beta RC2 | 4.10.1723.4 | 7.10 [4.10.1723] | 04-10-98 + 17:23:40 | 4.10.1723.4 |
| Windows 98 Beta RC2 | 4.10.1726 | 7.10 [4.10.1726] | 04-18-98 + 17:26:00 | 4.10.1726 |
| Windows 98 Beta RC3 | 4.10.1900.5 | 7.10 [4.10.1900] | 04-24-98 + 19:05:00 | 4.10.1900.5 |
| Windows 98 Beta RC4 | 4.10.1900.8 | 7.10 [4.10.1900] | 04-28-98 + 19:08:00 | 4.10.1900.8 |
| Windows 98 Beta RC5 | 4.10.1998 | 7.10 [4.10.1998] | 05-06-98 + 19:09:08 | 4.10.1998 |
| Windows 98 | ||||
| Windows 98 final retail | 4.10.1998.6 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 final OEM | 4.10.1998.6 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 OSR 1 Beta | ||||
| Windows 98 SP1 Beta 1 | 4.10.2088 | 7.10 [4.10.2088] | 10-01-98 + 20:08:08 | 4.10.2088 |
| Windows 98 OSR1 Beta 1 | 4.10.2106 | 7.10 [4.10.2106] | 11-18-98 + 21:06:00 | 4.10.2106 |
| Windows 98 OSR1 Beta 1 | 4.10.2120 | 7.10 [4.10.2120] | 12-20-98 + 21:20:00 | 4.10.2120 |
| Windows 98 OSR1 Beta 1 | 4.10.2126 | 7.10 [4.10.2126] | 01-08-99 + 21:26:00 | 4.10.2126 |
| Windows 98 OSR1 Beta 1 | 4.10.2131 | 7.10 [4.10.2131] | 01-21-99 + 21:31:00 | 4.10.2131 |
| Windows 98 SP1 Beta 2 | 4.10.2150.0 | 7.10 [4.10.2150] | 01-05-99 + 21:50:00 | 4.10.2150.0 |
| Windows 98 SP1 Beta 2 | 4.10.2150.4 | 7.10 [4.10.2150] | 02-25-99 + 21:50:04 | 4.10.2150.4 |
| Windows 98 SP1 final Update | 4.10.2000 | 7.10 [4.10.1998] | 05-26-99 + 08:00:00 | 4.10.2000 |
| Windows 98 OSR1 Beta 2 | 4.10.2174 | 7.10 [4.10.2174] | 03-21-99 + 21:07:40 | 4.10.2174 |
| Windows 98 SE Beta RC1 | 4.10.2183 | 7.10 [4.10.2183] | 04-11-99 + 21:08:30 | 4.10.2183 |
| Windows 98 SE Beta RC2 | 4.10.2185 | 7.10 [4.10.2185] | 04-18-99 + 21:08:50 | 4.10.2185 |
| Windows 98 SE Beta RC3 | 4.10.2222 | 7.10 [4.10.2222] | 04-20-99 + 22:22:00 | 4.10.2222 |
| Windows 98 Second edition | ||||
| Windows 98 SE final retail | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE final OEM | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE Updates final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
远古Windows 98 Beta版本列表 2
最迟的列表可能出现时间为2004年。仅供参考，列表中有错误信息！
| OS RELEASE | VERSION | MS-DOS REVISION | DATE + TIME | BUILD |
|---|---|---|---|---|
| Windows 95 retail final | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95 OEM final | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95 Upgrade final | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95a OSR1 Update final | 4.00.0950 a | 7.00 [4.00.0950] | 02-02-96 + 09:51:00 | 4.00.0951 |
| Windows 95B OSR 2.0 OEM final | 4.00.0950 B | 7.10 [4.00.1111] | 08-24-96 + 11:11:11 | 4.00.1111 |
| Windows 95B OSR 2.1 Update final | 4.00.0950 B | 7.10 [4.00.1111] | 04-10-97 + 12:14:00 | 4.03.1212 |
| Windows 95B OSR 2.1 OEM final | 4.01.0971 B | 7.10 [4.00.1111] | 06-25-97 + 09:07:10 | 4.01.0971 |
| Windows 95C OSR 2.5 OEM final | 4.00.0950 C | 7.10 [4.00.1111] | 11-26-97 + 12:16:00 | 4.03.1214 |
| Windows 98 Beta pre-DR | 4.10.1351 | 7.10 [4.10.1351] | 12-16-96 + 13:51:00 | 4.10.1351 |
| Windows 98 Beta DR | 4.10.1358 | 7.10 [4.10.1358] | 12-20-96 + 13:58:00 | 4.10.1358 |
| Windows 98 early Beta | 4.10.1378 | 7.10 [4.10.1378] | ? + ? | 4.10.1378 |
| Windows 98 early Beta | 4.10.1410 | 7.10 [4.10.1410] | ? + ? | 4.10.1410 |
| Windows 98 early Beta | 4.10.1423 | 7.10 [4.10.1423] | 04-08-97 + 04:23:00 | 4.10.1423 |
| Windows 98 Beta 1 | 4.10.1500 | 7.10 [4.10.1500] | ? + ? | 4.10.1500 |
| Windows 98 Beta 1 | 4.10.1508 | 7.10 [4.10.1508] | ? + ? | 4.10.1508 |
| Windows 98 Beta 1 | 4.10.1511 | 7.10 [4.10.1511] | ? + ? | 4.10.1511 |
| Windows 98 Beta 1 | 4.10.1525 | 7.10 [4.10.1525] | 06-18-97 + 10:09:00 | 4.10.1525 |
| Windows 98 Beta 1 | 4.10.1535 | 7.10 [4.10.1535] | 07-02-97 + 15:35:00 | 4.10.1535 |
| Windows 98 Beta 1 | 4.10.1538 | 7.10 [4.10.1538] | 07-12-97 + 15:38:00 | 4.10.1538 |
| Windows 98 Beta 1 | 4.10.1543 | 7.10 [4.10.1543] | ? + ? | 4.10.1543 |
| Windows 98 Beta 2 | 4.10.1544 | 7.10 [4.10.1544] | 07-31-97 + 15:44:00 | 4.10.1544 |
| Windows 98 Beta 2 | 4.10.1546 | 7.10 [4.10.1546] | 08-02-97 + 15:46:00 | 4.10.1546 |
| Windows 98 Beta 2 | 4.10.1550 | 7.10 [4.10.1550] | 08-10-97 + 17:21:00 | 4.10.1550 |
| Windows 98 Beta 2 | 4.10.1559 | 7.10 [4.10.1559] | 08-11-97 + 15:50:00 | 4.10.1559 |
| Windows 98 Beta 2 | 4.10.1564 | 7.10 [4.10.1564] | 08-14-97 + 15:50:00 | 4.10.1564 |
| Windows 98 Beta 2 | 4.10.1569 | 7.10 [4.10.1569] | 08-22-97 + 15:50:00 | 4.10.1569 |
| Windows 98 Beta 2 | 4.10.1577 | 7.10 [4.10.1577] | 09-04-97 + 15:50:00 | 4.10.1577 |
| Windows 98 Beta 2 | 4.10.1581 | 7.10 [4.10.1581] | 09-10-97 + 15:50:00 | 4.10.1581 |
| Windows 98 Beta 2 | 4.10.1593 | 7.10 [4.10.1593] | 09-25-97 + 15:50:00 | 4.10.1593 |
| Windows 98 Beta 2 | 4.10.1599 | 7.10 [4.10.1599] | 10-08-97 + 15:50:00 | 4.10.1599 |
| Windows 98 Beta 3 | 4.10.1602 | 7.10 [4.10.1602] | ? + ? | 4.10.1602 |
| Windows 98 Beta 3 | 4.10.1605 | 7.10 [4.10.1605] | ? + ? | 4.10.1605 |
| Windows 98 Beta 3 | 4.10.1614 | 7.10 [4.10.1614] | 10-24-97 + 16:14:00 | 4.10.1614 |
| Windows 98 Beta 3 | 4.10.1619 | 7.10 [4.10.1619] | 10-31-97 + 16:19:00 | 4.10.1619 |
| Windows 98 Beta 3 | 4.10.1624 | 7.10 [4.10.1624] | 11-06-97 + 16:24:00 | 4.10.1624 |
| Windows 98 Beta 3 | 4.10.1629 | 7.10 [4.10.1629] | 11-14-97 + 16:29:00 | 4.10.1629 |
| Windows 98 Beta 3 | 4.10.1633 | 7.10 [4.10.1633] | 11-18-97 + 16:33:00 | 4.10.1633 |
| Windows 98 Beta 3 | 4.10.1650 | 7.10 [4.10.1650] | 11-26-97 + 16:50:00 | 4.10.1650 |
| Windows 98 Beta 3 | 4.10.1650.3 | 7.10 [4.10.1653] | 12-03-97 + 16:50:03 | 4.10.1650.3 |
| Windows 98 Beta 3 | 4.10.1650.8 | 7.10 [4.10.1658] | 12-09-97 + 16:50:08 | 4.10.1650.8 |
| Windows 98 Beta 3 | 4.10.1666 | 7.10 [4.10.1666] | 01-14-98 + 16:06:06 | 4.10.1666 |
| Windows 98 Beta 3 | 4.10.1671 | 7.10 [4.10.1671] | 01-20-98 + 16:07:10 | 4.10.1671 |
| Windows 98 Beta 3 | 4.10.1677 | 7.10 [4.10.1677] | 01-30-98 + 16:07:07 | 4.10.1677 |
| Windows 98 Beta 3 | 4.10.1681 | 7.10 [4.10.1681] | 02-05-97 + 16:08:10 | 4.10.1681 |
| Windows 98 Beta 3 | 4.10.1687 | 7.10 [4.10.1687] | 02-12-98 + 16:08:07 | 4.10.1687 |
| Windows 98 RC0 | 4.10.1691 | 7.10 [4.10.1691] | 02-16-98 + 12:16:00 | 4.10.1691 |
| Windows 98 RC0 | 4.10.1702 | 7.10 [4.10.1702] | 03-05-98 + 12:17:00 | 4.10.1702 |
| Windows 98 RC0 | 4.10.1708 | 7.10 [4.10.1708] | 03-12-98 + 12:17:00 | 4.10.1708 |
| Windows 98 RC0 | 4.10.1713 | 7.10 [4.10.1713] | 03-19-98 + 12:17:00 | 4.10.1713 |
| Windows 98 RC1 | 4.10.1721.3 | 7.10 [4.10.1721] | 03-30-98 + 17:21:40 | 4.10.1721.3 |
| Windows 98 RC2 | 4.10.1723.4 | 7.10 [4.10.1723] | 04-10-98 + 17:23:40 | 4.10.1723.4 |
| Windows 98 RC2 | 4.10.1726 | 7.10 [4.10.1726] | 04-18-98 + 17:26:00 | 4.10.1726 |
| Windows 98 RC3 | 4.10.1900.5 | 7.10 [4.10.1900] | 04-24-98 + 19:05:00 | 4.10.1900.5 |
| Windows 98 RC4 | 4.10.1900.8 | 7.10 [4.10.1900] | 04-28-98 + 19:08:00 | 4.10.1900.8 |
| Windows 98 RC5 | 4.10.1998 | 7.10 [4.10.1998] | 05-06-98 + 19:09:08 | 4.10.1998 |
| Windows 98 retail final | 4.10.1998 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 OEM final | 4.10.1998 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 Upgrade final | 4.10.1998 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 SP1 Beta 1 | 4.10.2088 | 7.10 [4.10.2088] | 10-01-98 + 20:08:08 | 4.10.2088 |
| Windows 98 OSR1 Beta 1 | 4.10.2106 | 7.10 [4.10.2106] | 11-18-98 + 21:06:00 | 4.10.2106 |
| Windows 98 OSR1 Beta 1 | 4.10.2120 | 7.10 [4.10.2120] | 12-20-98 + 21:20:00 | 4.10.2120 |
| Windows 98 OSR1 Beta 1 | 4.10.2126 | 7.10 [4.10.2126] | 01-08-99 + 21:26:00 | 4.10.2126 |
| Windows 98 OSR1 Beta 1 | 4.10.2131 | 7.10 [4.10.2131] | 01-21-99 + 21:31:00 | 4.10.2131 |
| Windows 98 SP1 Beta 2 | 4.10.2150.0 | 7.10 [4.10.2150] | 01-05-99 + 21:50:00 | 4.10.2150.0 |
| Windows 98 SP1 Beta 2 | 4.10.2150.4 | 7.10 [4.10.2150] | 02-25-99 + 21:50:04 | 4.10.2150.4 |
| Windows 98 SP1 Update final | 4.10.2000 | 7.10 [4.10.1998] | 05-26-99 + 08:00:00 | 4.10.2000 |
| Windows 98 OSR1 Beta 2 | 4.10.2174 | 7.10 [4.10.2174] | 03-21-99 + 21:07:40 | 4.10.2174 |
| Windows 98 SE RC1 | 4.10.2183 | 7.10 [4.10.2183] | 04-11-99 + 21:08:30 | 4.10.2183 |
| Windows 98 SE RC2 | 4.10.2185 | 7.10 [4.10.2185] | 04-18-99 + 21:08:50 | 4.10.2185 |
| Windows 98 SE RC3 | 4.10.2222 | 7.10 [4.10.2222] | 04-20-99 + 22:22:00 | 4.10.2222 |
| Windows 98 SE retail final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE OEM final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE Upgrade final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE Updates final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows ME Beta DR1 | 4.90.2332 | 8.00 [4.90.2332] | 07-23-99 + 22:33:00 | 4.90.2332 |
| Windows ME Beta DR2 | 4.90.2348 | 8.00 [4.90.2348] | 08-06-99 + 23:48:00 | 4.90.2348 |
| Windows ME Beta DR3 | 4.90.2358 | 8.00 [4.90.2358] | 08-20-99 + 23:58:00 | 4.90.2358 |
| Windows ME Beta DR4 | 4.90.2363 | 8.00 [4.90.2363] | 08-27-99 + 23:06:03 | 4.90.2363 |
| Windows ME early Beta | 4.90.2368 | 8.00 [4.90.2368] | 09-03-99 + 23:06:08 | 4.90.2368 |
| Windows ME early Beta | 4.90.2374 | 8.00 [4.90.2374] | 09-13-99 + 23:07:04 | 4.90.2374 |
| Windows ME Beta 1 | 4.90.2380 | 8.00 [4.90.2380] | 09-24-99 + 23:08:00 | 4.90.2380 |
| Windows ME Beta 1 | 4.90.2394 | 8.00 [4.90.2394] | 10-13-99 + 23:09:04 | 4.90.2394 |
| Windows ME Beta 1 | 4.90.2399 | 8.00 [4.90.2399] | 10-22-99 + 23:09:09 | 4.90.2399 |
| Windows ME Beta 1 | 4.90.2404 | 8.00 [4.90.2404] | 10-29-99 + 00:44:00 | 4.90.2404 |
| Windows ME Beta 1 | 4.90.2410 | 8.00 [4.90.2410] | 11-05-99 + 00:11:00 | 4.90.2410 |
| Windows ME Beta 1 | 4.90.2416 | 8.00 [4.90.2416] | 11-15-99 + 00:16:00 | 4.90.2416 |
| Windows ME Beta 1 | 4.90.2419.4 | 8.00 [4.90.2419] | 11-19-99 + 00:19:04 | 4.90.2419.4 |
| Windows ME Beta 2 | 4.90.2429 | 8.00 [4.90.2429] | 12-10-99 + 00:29:00 | 4.90.2429 |
| Windows ME Beta 2 | 4.90.2434 | 8.00 [4.90.2434] | 12-20-99 + 00:34:00 | 4.90.2434 |
| Windows ME Beta 2 | 4.90.2443 | 8.00 [4.90.2443] | 01-07-00 + 00:43:00 | 4.90.2443 |
| Windows ME Beta 2 | 4.90.2447 | 8.00 [4.90.2447] | 01-14-00 + 00:47:00 | 4.90.2447 |
| Windows ME Beta 2 | 4.90.2455 | 8.00 [4.90.2455] | 01-31-00 + 00:55:00 | 4.90.2455 |
| Windows ME Beta 2 | 4.90.2460 | 8.00 [4.90.2460] | 02-04-00 + 00:06:00 | 4.90.2460 |
| Windows ME Beta 2 | 4.90.2465 | 8.00 [4.90.2465] | 02-11-00 + 00:06:05 | 4.90.2465 |
| Windows ME Beta 2 | 4.90.2470 | 8.00 [4.90.2470] | 02-18-00 + 00:07:00 | 4.90.2470 |
| Windows ME Beta 2 | 4.90.2474 | 8.00 [4.90.2474] | 02-25-00 + 00:07:04 | 4.90.2474 |
| Windows ME Beta 2 | 4.90.2481 | 8.00 [4.90.2481] | 03-03-00 + 00:08:01 | 4.90.2481 |
| Windows ME Beta 2 | 4.90.2487 | 8.00 [4.90.2487] | 03-10-00 + 00:08:07 | 4.90.2487 |
| Windows ME Beta 2 | 4.90.2491 | 8.00 [4.90.2491] | 03-17-00 + 00:09:01 | 4.90.2491 |
| Windows ME Beta 3 | 4.90.2499 | 8.00 [4.90.2499] | 03-27-00 + 00:09:09 | 4.90.2499 |
| Windows ME Beta 3 | 4.90.2499.3 | 8.00 [4.90.2499] | 03-30-00 + 00:09:09 | 4.90.2499.3 |
| Windows ME Beta 3 | 4.90.2509 | 8.00 [4.90.2509] | 04-18-00 + 00:25:09 | 4.90.2509 |
| Windows ME Beta 3 | 4.90.2513 | 8.00 [4.90.2513] | 04-21-00 + 00:25:13 | 4.90.2513 |
| Windows ME Beta 3 | 4.90.2516 | 8.00 [4.90.2516] | 04-28-00 + 00:25:16 | 4.90.2516 |
| Windows ME RC0 | 4.90.2525 | 8.00 [4.90.2525] | 05-08-00 + 00:25:25 | 4.90.2525 |
| Windows ME RC1 | 4.90.2525.6 | 8.00 [4.90.2525] | 05-17-00 + 00:25:25 | 4.90.2525.6 |
| Windows ME RC2 | 4.90.2535 | 8.00 [4.90.2535] | 06-05-00 + 00:25:35 | 4.90.2535 |
| Windows ME retail final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
| Windows ME OEM final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
| Windows ME Upgrade final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
| Windows ME Step-Up final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
来自defacto的Win98新闻
Tuesday 26th May (8:25pm GMT) It maybe beating a dead horse, but what the hey it fills space. If you remember about three weeks ago Krypto was very doubtful that Reality Check Network would be returning and claimed if it did return he would never rejoin. Well he has already contracted a famous scene coder to start work on a new Windows 95 interface for the magazine. The coder won't start until he has told by Krypto to begin. After two plus months of idling Scenelink has returned with a new look (again). This time around they have replaced the monthly features section with an articles area and added the famed Dupelink. Sunday 24th May (5:05pm GMT) Just incase you where wondering about those rumours of a PWA NFO being slipped onto a gold master of Windows98 before it went to press. Well they are completely false, as is the so-called modified code. There was also a webpage quoting a press release from Microsoft, and if you read it properly you could easily tell it was a fake. It contained lines that would never be used in a press release, like the one below. "Remember, if you are approached by one of these ex-employees, and they offer you source code to one of the many fine Microsoft releases, you are not entitled to use this code by law. Not even PWA is entitled to its use. Please return it. Please." Monday 18th May (6:42pm GMT) Game Over Online Magazine is now open for business. Read the previous days news for more information. Well the biggest os release since Windows 95 is now upon us, PWA brings you Windows 98 Retail Full Install at 21*5meg disks. Here is a note for people who require the other versiosn of Windows 98 from the PWA nfo. You need to download the CABS and the RETAIL SETUP and unzip/unrar everything into one directory. The reason for this is that as soon as I get install keys, I can release RETAIL UPGRADE, OEM FULL and OEM UPGRADE versions and they will only take 4 meg each (the CAB zips are generic thruout all these versions, I can just package up the differences in seperate zips to save everyone space and time). You just unzip whichever one you want into the same directory as the generic CAB zips.
另外单独的一则（这就是你ProductType辣么多的理由？）
Monday 15th December Nothing much happening today so I thought I might regurgitate some news that can be found in your local newspapers. After US District Court judge Thomas Jackson's decision to temporally stop Microsoft shipping Ie4 with Windows 95 there are now doubts that Windows 98 may ship in April. Though more realistic people say it will most likely ship in two different versions, one with Ie4 and one with out. So you may see six different versions (2 full and 4 upgrade) of Windows 95 on the selves by the time it comes out.
未泄露文件信息 随手一记
MS WinXP SP1 v1069 (OEM) usa_1069_csd_wxpsp1.iso 289.09 MB MSDN XP SP1 build 1050 (unk name) 235.55 MB XPSP1 v1073 (unk name) 121mb ............................................................ Windows XP Service Pack 2 build.2082 简体中文版 ed2k://|file|xpsp2_2082_chs_x86fre.iso|441059328|de08833a9597c991f25250e858d6bcd9|/ 简介: 现本网站发布最新的Windows.XP.SP2.RC1.2096 简体中文版补丁，望朋友们浏览下载。我这个已过时了，本人的任务也该完成了。请极个别没下完的朋友抓紧时间，我再做一天源。特鞠躬致谢下面回复的朋友！！！ 此次传输量: 软件简介： 微软终于释放了Windows XP Service Pack 2 build.2082 简体中文版,这个SP的第一个最终测试版,我们第一时间从BetaPlace找到了最新的版本提供给你 还等什么,快快下载尝鲜 测试表明：XP的安全性能大大加强，另外增加了网络防火墙。连ＩＥ６也一块升级到了ＳＰ２可以拦截广告和弹出窗口和一些脚本程序。安完后，多了安全中心。在OEM版本上测试升级成功,限于条件，其它版本未测试。 ISO格式。 注意：具体安装程序在update文件夹里，update.exe。 最好作备份！我已经安装完，现在没感觉有什么问题。欢迎喜欢尝鲜的朋友可不要埋怨我！ 关于此次升级包sp2太大的问题我认为可能是因为里面含有网络防火墙及防毒软件捆绑发售造成的（完全免费的啊！）我是从sp1升级的（当然用的是已激活的D版）已经两天了，程序正在自动升级，一切OK。 本人带宽有限（ADSL）请下完的朋友帮忙作源，我保证一星期内有效，请尽快！ 紧急告知！！！ 现已证明WINXP－SP2升级包已经把俄罗斯破解版给封杀了！！！在知道消息后便马上通知朋友们，其实上面写得很清楚这是SP的第一个最终测试版，请喜欢尝鲜的朋友们一定用GHOST作好备份，切记！！！ 再有从朋友们回复中我感觉SP2对国产防杀软件好象不支持，因为系统升级后已带有网络防火墙及防毒软件。我也是个菜鸟，解决不了任何问题。此次SP2升级包对我们大家都是个新鲜未知的东西，有什么埋怨骂微软，希望别算在我头上。 ............................................................................... Windows.XP.SP2.RC1.2096 简体中文版 ed2k://|file|xpsp2_2096_chs_x86fre_RC1.iso|367886336|e1faef49be1ff3905f707cc5e2b8ddfa|/ 简介: 最新的Windows.XP.SP2.RC1.2096 简体中文版,呵呵,很快SP2正式版就快出来了 听说到6月份出,呵呵 推荐算号激活和VOL版本的朋友更新,注意:破解激活的Xp将要求激活,无法登陆 『图文』Windows XP SP2 RC1 简体中文版初体验(转自ssite.org) 环境 host os: windows server 2003 enterprise guest os: vmware workstation 4.5.1.7568 vm conf: CPU: P4 2.2 RAM: 256M HDD: 4G(单分区) NIC: NAT .............................................................................. Windows XP SP2 RC2 Build 2149 简体版[crsky deadlink] http://file.mydrivers.com/others/XP_SP2_RC22149CHS.rar http://file2.mydrivers.com/others/XP_SP2_RC22149CHS.rar 软件大小： 293380K 软件更新： 2004-6-16 17:11:00 软件介绍： 微软官方已经公布了Windows XP RC2的下载地址，有需要的朋友赶快行动吧。这是简体中文版，安装请执行i386\update目录下的update.exe文件。 .............................................................................
某个WinBeta IRC文件列表记录
<Winbeta-XDCC-252> Kiri Online >> Sends: 0/1, Queues: 0/3 <Winbeta-XDCC-252> Bandwidth >> Current: 0KB/s, Record: 1258KB/s <Winbeta-XDCC-252> [#1] ��4Winxp SP2 RC2 2162�� (271.38MB, 11 Gets) <Winbeta-XDCC-252> [#2] ��1Longhorn Build 4074�� (724.9MB, 4 Gets) <Winbeta-XDCC-252> [#3] ��2Acronis Partition Expert 9 Build 485�� (37.95MB, 6 Gets) <Winbeta-XDCC-252> [#4] ��6Win XP Pro AMD 64 Build 1184�� (457.6MB, 2 Gets) <Winbeta-XDCC-252> [#5] ��4Windows Installer 3.0 RC2�� (6.93MB, 4 Gets) <Winbeta-XDCC-252> [#6] ��3Microsoft Command Shell Preview V2�� (24.04MB, 2 Gets) <Winbeta-XDCC-252> To request a file, type /msg Winbeta-XDCC-252 xdcc send #x <Winbeta-XDCC-252> For pack info, type /msg Winbeta-XDCC-252 xdcc info #x <Winbeta-XDCC-252> Total transferred: 13136.81MB in 29 files <Winbeta-XDCC-252> ** ***** Read The NFO'S w/Notepad ***** Brought to you by Carvensno and Winbeta ** <Winbeta-XDCC-302> #15 1x [271.38M] ��4Microsoft Windows XP SP2 Build 2162�� <Winbeta-XDCC-302> ** Brought to you by Winbeta and dm2k4. ** <Winbeta-XDCC-302> Total Transferred: 9036.74MB <eugrus> xdcc list <Winbeta-XDCC-302> ** 15 packs ** 0 of 1 slots open, Record: 22KB/s <Winbeta-XDCC-302> ** Bandwidth Usage ** Current: 16KB/s, Record: 22KB/s <Winbeta-XDCC-302> ** To request a file type: "/msg Winbeta-XDCC-302 xdcc send #x" ** <Winbeta-XDCC-302> #1 0x [18.36M] ��3Microsoft .NET Framework v1.1 SP1 and v1.0 SP3 Beta 2�� <Winbeta-XDCC-302> #2 1x [22.14M] ��3Microsoft .NET Framework v2.0.3113.31�� <Winbeta-XDCC-302> #3 1x [24.04M] ��3Microsoft Command Shell Preview v2.0�� <Winbeta-XDCC-302> #4 0x [94.44M] ��3Microsoft Host Integration Server 2004 Release Candidate�� <Winbeta-XDCC-302> #5 0x [99M] ��3Microsoft Office 2003 SP1 Beta Build 6353�� <Winbeta-XDCC-302> #6 0x [103.73M] ��3Microsoft Operations Manager 2005 Beta 3 Bundle�� <Winbeta-XDCC-302> #7 0x [356.24M] ��3Microsoft SQL Server Yukon PDC Build�� <Winbeta-XDCC-302> #8 0x [3697.12M] ��4Microsoft Visual Studio .NET 2005 Beta 1 DVD�� <Winbeta-XDCC-302> #9 0x [6.93M] ��3Microsoft Windows Installer v3.0 RC2�� <Winbeta-XDCC-302> #10 1x [724.9M] ��7Microsoft Windows Longhorn WinHEC Build 4074�� <Winbeta-XDCC-302> #11 0x [4013.15M] ��7Microsoft Windows Longhorn WinHEC Build 4074 AIO DVD�� <Winbeta-XDCC-302> #12 0x [342.89M] ��3Microsoft Windows Longhorn WinHEC Build 4074 LDK�� <Winbeta-XDCC-302> #13 1x [371.42M] ��4Microsoft Windows Server 2003 SP1 Build 1218�� <Winbeta-XDCC-302> #14 3x [468.42M] ��4Microsoft Windows XP Professional AMD64 Build 1218�� <Winbeta-XDCC-302> #15 1x [271.38M] ��4Microsoft Windows XP SP2 Build 2162�� <Winbeta-XDCC-302> ** Brought to you by Winbeta and dm2k4. ** <Winbeta-XDCC-302> Total Transferred: 9041.18MB <WinBeta-XDCC-22245> Kiri Online >> Sends: 1/1, Queues: 0/5 <WinBeta-XDCC-22245> Bandwidth >> Current: 20KB/s, Record: 22KB/s, Cap: 20KB/s <WinBeta-XDCC-22245> [#1] ��2Windows XP Pro AMD64 ��4Build: 1184�� (457.61MB, 0 Gets) <WinBeta-XDCC-22245> [#2] ��3Windows Longhorn WinHEC ��4Build:4074�� (724.9MB, 0 Gets) <WinBeta-XDCC-22245> [#3] ��6Virutal Server 2005 ��4Build: 1.1.445�� (17.26MB, 0 Gets) <WinBeta-XDCC-22245> [#4] ��7Windows Installer v3.0 ��4Build: RC2�� (6.93MB, 0 Gets) <WinBeta-XDCC-22245> [#5] ��8Windows XP SP2 ��4Build 2162�� (271.38MB, 0 Gets) <WinBeta-XDCC-22245> To request a file, type /msg WinBeta-XDCC-22245 xdcc send #x <WinBeta-XDCC-22245> For pack info, type /msg WinBeta-XDCC-22245 xdcc info #x <WinBeta-XDCC-22245> Total transferred: 70.69MB in 0 files <WinBeta-XDCC-22245> ** ]::[Always read the .nfo]::[Brought to you by WinBeta and $injed]::[ ** <WinBeta-XDCC-110> Kiri Online >> Sends: 0/1, Queues: 0/2, Min Speed: 1KB/s <WinBeta-XDCC-110> Bandwidth >> Current: 0KB/s, Record: 56KB/s <WinBeta-XDCC-110> [#1] ��2Acronis.Partition.Expert.9.build.485-WinBeta�� (37.95MB, 2 Gets) <WinBeta-XDCC-110> [#2] ��4Microsoft.Command.Shell.Preview.v2.0-WinBeta�� (24.04MB, 1 Gets) <WinBeta-XDCC-110> [#3] ��2Microsoft.ISA.Server.2004.RC1.WInbeta�� (46.47MB, 0 Gets) <WinBeta-XDCC-110> [#4] ��2Windows Code Name "Longhorn" - #4074�� (724.9MB, 0 Gets) <WinBeta-XDCC-110> [#5] ��5Office 2003 SP1 #6353�� (99MB, 0 Gets) <WinBeta-XDCC-110> [#6] ��2Host Integration Server 2004 RC�� (94.44MB, 0 Gets) <WinBeta-XDCC-110> [#7] ��4"Royale" - new official theme for XP/2003�� (0.17MB, 1 Gets) <WinBeta-XDCC-110> [#8] ��1LH #4074 LDK�� (342.89MB, 0 Gets) <WinBeta-XDCC-110> [#9] ��3Windows XP Service Pack 2, Build 2162 ENG Full�� (271.38MB, 0 Gets) <WinBeta-XDCC-110> [#10] ��2Windows Installer 3.0 RC2�� (6.93MB, 0 Gets) <WinBeta-XDCC-110> [#11] ��2Windows Server 2003 SP1 #1218�� (371.42MB, 1 Gets) <WinBeta-XDCC-110> [#12] ��4Windows Server 2003 Enterprise Edition, AMD64 build 1218�� (505.78MB, 0 Gets) <WinBeta-XDCC-110> [#13] ��6Windows XP Pro, AMD64 build 1218�� (468.42MB, 4 Gets) <WinBeta-XDCC-110> [#14] ��4Windows Server 2003 Standard Edition, AMD64 build 1218�� (502.92MB, 0 Gets) <WinBeta-XDCC-110> To request a file, type /msg WinBeta-XDCC-110 xdcc send #x <WinBeta-XDCC-110> For pack info, type /msg WinBeta-XDCC-110 xdcc info #x <WinBeta-XDCC-110> Total transferred: 3568.15MB in 9 files <WinBeta-XDCC-110> ** always here from the beginning.. ** <WinBeta-XDCC-256> Kiri Online >> Sends: 0/1, Queues: 0/10, Min Speed: 10KB/s <WinBeta-XDCC-256> Bandwidth >> Current: 0KB/s, Record: 90KB/s <WinBeta-XDCC-256> [#1] Acronis.Partition.Expert.9.build.485-WinBeta.rar (37.95MB, N/A Gets) <WinBeta-XDCC-256> [#2] Microsoft_Virtual_Server_2005_Build_1.1.455.rar (17.26MB, N/A Gets) <WinBeta-XDCC-256> [#3] WB-LH4074.rar (724.9MB, N/A Gets) <WinBeta-XDCC-256> [#4] wb-p-wxpsp2b2149.rar (266.71MB, N/A Gets) <WinBeta-XDCC-256> [#5] wb-royale-mce.rar (0.17MB, N/A Gets) <WinBeta-XDCC-256> [#6] Windows.XP.SP2.Build.2162-WinBeta.rar (271.38MB, N/A Gets) <WinBeta-XDCC-256> [#7] Windows.XPSP2.Build.2144.full-WinBeta.rar (274.67MB, N/A Gets) <WinBeta-XDCC-256> To request a file, type /msg WinBeta-XDCC-256 xdcc send #x <WinBeta-XDCC-256> For pack info, type /msg WinBeta-XDCC-256 xdcc info #x <WinBeta-XDCC-256> Total transferred: 776.41MB in 0 files <WinBeta-XDCC-256> ** Brought to you by WinBeta **
文件文本
OS2VSCHG.TXT
WARP VS CHICAGO: A Decision Maker's Guide to 32-bit Operating
System Technology
IBM Personal Software Marketing
October 1994
EXECUTIVE SUMMARY
=================
This document is designed to provide the corporate decision maker
with benefits of OS/2 and important information about critical
weaknesses in Microsoft's forthcoming Chicago operating system.
At the heart of the discussion are key architectural,
operational, and strategic flaws in the Chicago OS design and
strategy - flaws that Microsoft has either downplayed or ignored
in its efforts to market Chicago as the "next generation" Windows
desktop platform.
For example, you'll learn:
Why OS/2's ability to isolate individual 16-bit Windows
applications into their own separate VDMs provides a level of
inter-application protection that is unavailable under Windows
3.1 or Chicago.
How this same isolation also allows OS/2 to preemptively multitask
existing 16-bit Windows applications, with no impact on native
application performance
Why having a comprehensive System Object Model (SOM) is important,
and how OS/2's SOM implementation acts as the "glue" to the
WorkPlace Shell interface.
Ways in which OS/2's Virtual DOS Machine implementation is more
flexible than Chicago's.
Major topics include:
Architectural flaws that compromise Chicago's stability when
running 16-bit Windows applications.
How these same flaws also limit Chicago's multitasking
capabilities with a mixture of application types.
Why the lack of a System Object Model makes the Chicago interface
"fragile."
Ways in which Chicago's DOS heritage render the product inflexible
when dealing with 16-bit DOS device drivers.
At the end of each section, a direct comparison is made between
the Chicago implementation of a particular subsystem or
feature/function, and that of the leader in 32-bit desktop
operating systems, IBM's Operating System/2.
The material is based on an in-depth analysis of Microsoft's
public statements regarding Chicago's design characteristics and
various presentations given at trade shows by industry
consultants.
OS/2 - THE RIGHT SOLUTION
Choosing the right operating system. In many ways it's the most
important personal computer technology decision you'll make in
this century. Choose wisely and you'll reap the benefits for
years. Choose poorly and you may find yourself in a quagmire of
under-performing software and inadequate computing power.
So just what constitutes a wise choice in today's confusing PC
marketplace? Simple: the product that does the best job of
preserving your existing investments while opening the door to
the future. In a nutshell, the wise choice is Operating
System/2.
OS/2 - THE WORLD'S MOST POPULAR 32-BIT OPERATING SYSTEM FOR IBM
AND IBM COMPATIBLE PC's
Why OS/2? Because it represents the most logical upgrade path
for today's PC users. OS/2 preserves your investment in 16-bit
DOS and Windows applications while providing access to a new
world of 32-bit, object-oriented technology.
Upgrading to OS/2 is a win-win proposition. Just ask any of the
more than five-million OS/2 users - over 8 times as many users as
Microsoft's current 32-bit offering, Windows NT. These are
people just like you who have outgrown their existing DOS or
Windows environments and who are looking for more - more power,
more functionality, more stability.
With OS/2 they've found a powerful mix of backward-compatibility,
32-bit processing power, and ease of use, along with the kind of
rock-solid reliability that only a mature, established operating
system platform can deliver. With the release of V3, OS/2 is
entering in its 3rd generation, and the product's reputation for
reliability and price/performance is unmatched in the PC
industry.
BUT WHAT ABOUT CHICAGO?
This is the question that perplexes both corporate decision
makers and end users alike. With all of the media hype
surrounding this "next generation" of Microsoft Windows, many
customers feel paralyzed when making operating system purchasing
decisions. The fear of "missing-out" on Chicago is overwhelming
for some.
But as experience with the initial beta release of Chicago has
demonstrated, Microsoft's "next generation" of Windows is far
less compelling than they would lead you to believe. In fact,
the core of Windows 4.0 is probably running on a PC near you:
it's called Microsoft Windows 3.1.
ARCHITECTURE
============
CHICAGO - SAME CODE, DIFFERENT PACKAGING
"How can that be? It looks so different!"
Looks can be deceiving. While Chicago indeed sports a radically
different user interface (more on that later), as you peel-away
the layers of GUI and packaging you'll discover a product that
looks remarkably like Windows 3.1. In fact, Chicago retains so
much of its original DOS/Windows heritage that it retains the
latter's most notorious operational characteristic: instability.
For example, under Windows 3.1 all applications, as well as the
operating system code itself, share a single memory address
space. While such a memory management model breeds performance,
it also means that an error in any single application can
potentially crash the entire operating system.
This crashing phenomena is often referred to as a General
Protection Fault or "GPF," and has been the bane of Windows users
since version 3.0. It is because of this inherent architectural
weakness that Windows 3.1 has gained a well-deserved reputation
of being an unstable, unreliable operating environment.
Under Chicago, this same single address space model (referred to
as the "System Virtual Machine") is retained, along with the
inherent weakness of leaving key portions of the operating system
code exposed to potentially buggy applications. Thus the same
application failures that crashed Windows 3.1 can potentially
bring down the entire Chicago operating system.
To their credit Microsoft has made great strides in "cleaning-up"
many of the bugs in the original Windows 3.1 code while
preparing it for inclusion with Chicago. However they cannot
avoid the inherent architectural flaws that the Windows 3.1
single System VM model introduces. There will always remain the
possibility of an errant application causing a disastrous system
crash.
OS/2 - SAME CODE, BETTER IMPLEMENTATION
OS/2 eliminates the Single System VM stability problem by letting
you run Windows applications in their own separate sessions, or
"VDMs" (Virtual DOS Machines). Thus if an application fails
under OS/2, the effect of the failure is limited to the
individual session. Other applications, as well as the operating
system itself, remain unaffected.
And by retaining much of the original Windows 3.1 code base,
OS/2's environment remains highly backward compatible with
Windows 3.1 applications and device drivers.
MULTITASKING
============
CHICAGO - A "SEMI-PREEMPTIVE" TASK SWITCHER?
One of Microsoft's biggest selling points for Chicago has been
the promise of a new breed of 32-bit Windows applications. These
applications are to be preemptively multitasked by the Chicago
operating system, and will have access to advanced performance
enhancing techniques like multi- threading.
Let's define the difference between preemptive and cooperative
multitasking. Preemption is an involuntary loss of control which
the application must handle. Cooperative multitasking is where
the application is given control and it is the application's
responsibility to give up control so that other applications may
execute.
The move to a preemptive multitasking model represents a a
significant departure from Windows 3.1. Under that environment
applications must "cooperate" in order for multitasking to occur.
Each program "yields" to the operating system so that it can
switch control of the PC's CPU to a different application (this
is often referred to as "cooperative multitasking" or
"task-switching").
It is a well know fact that the Windows "cooperative
multitasking" model is inefficient. It also forces programmers to
code their applications in a way that adds complexity and hinders
performance. So it comes as no surprise that Microsoft's promise
of preemptive multitasking in Chicago has been heralded as one of
the new platform's most important features.
But the truth is that Microsoft isn't telling the whole story
when it comes to Chicago's multitasking architecture. In
reality, unless you work exclusively with 32-bit "Win32"
applications, you won't reap the benefits of true preemptive
multitasking.
Why? Because of Chicago's heavy reliance on 16-bit, Windows
3.1-era code. Under Chicago, both 16-bit and 32-bit applications
rely on 16-bit code structures that reside within the System VM -
code that has been brought over from Windows 3.1.
While the "bitness" of the code itself isn't significant, the
environment from which it hails is. Windows 3.1 was written as a
cooperative, not preemptive, multitasking environment. When you
introduce portions of its code into a preemptive setting, where
more than one task may be vying for its services at any given
time, the code breaks.
To safeguard against this sort of "code breakdown," Microsoft has
serialized access to key portions of the Chicago infrastructure -
most notably the USER (window management) and GDI (graphics
device interface) subsystems. In technical terms, this is
referred to as a "non-reentrant" design, meaning that only one
application may execute within these modules at any given time.
While such an approach works with Win32 applications - which can
be preempted at any point during their execution - it breaks down
once a 16-bit Windows (Win16) application begins to execute. As
it stands, currently shipping Win16 applications cannot be
reliably preempted during execution. Attempting to do so while
such an application is calling on a non-reentrant, 16-bit code
module can cause the entire operating system to crash.
To avoid this latter scenario, and thus retain some semblance of
multitasking, Microsoft has implemented a special locking
mechanism. Dubbed "Win16LOCK," this mechanism denies access to
the older code when a 16-bit application has called on its
services. Thus only the currently running Win16 application has
access to the 16-bit code - all other applications, including
Win32 applications, are "blocked" from executing until the 16-bit
application has finished and the environment has been made safe
for the next task.
In practice, the performance hit associated with this locking
phenomena is minimal when running 32-bit applications
exclusively. However, when you introduce a mixture of 16 and
32-bit applications - the most likely scenario given the
projected lack of available Win32 products - Win16LOCK becomes a
major problem.
Most 16-bit Windows applications are notorious for failing to
yield properly under Windows 3.1, and until they do so under
Chicago, all other applications will be blocked from accessing
USER and/or GDI (in reality, only 50% of GDI calls are affected -
but these are the most common functions so the net result is the
same).
Taken as a whole, these two compromises - the serialization of
subsystem access and Win16LOCK - create what would best be
described as a "semi-preemptive" multitasking environment. And
while the resulting "hourglass" is expected under a cooperatively
multitasked environment, it seems out of place in a "next
generation" Windows that supposedly "preemptively multitasks"
native Win32 applications.
OS/2 - TRUE PREEMPTION FOR BETTER PERFORMANCE
OS/2 has featured true preemptive multitasking of native
applications since day one. Regardless of the mixture of
application types, OS/2 can continue to smoothly multitask dozens
of concurrent programs, and its reentrant subsystems allow it to
service multiple concurrent requests without the overhead of a
"Win16LOCK" implementation.
And thanks to its ability to run them in separate VDMs, OS/2 can
also preemptively multitask existing 16-bit Windows applications
which Chicago can not. Thus you can have DOS, Windows, and OS/2
applications running concurrently, side-by-side, without any
performance penalties and all preemptively multitasked. This is
a feature that Chicago will be unable to match without underlying
architecture changes, and a welcome addition to any power-user's
arsenal.
INTERFACE
=========
CHICAGO - BEAUTY THAT'S ONLY SKIN-DEEP
Another major feature of Chicago, and one that has drawn
considerable attention from the industry press, is its new user
interface. Terms like "object-oriented" and "desktop metaphor"
are often used to describe this radically different Windows look.
But as with most of Chicago's underpinnings, the actual
foundation underneath the product's user interface is nothing
more than an extension to what already existed in Windows 3.1.
Unlike a true object-oriented environment - where links between
individual objects are "live" and updated automatically - the
Chicago GUI is static. "Objects" on the Chicago desktop are
merely pointers to files on the disk. "Properties" for these
objects are stored in .INI files (for Windows applications) or
.PIF files (for DOS applications), and links between them (called
"shortcuts" under Chicago) are equally static.
For example, if you create a shortcut to an executable file and
place it on the Chicago desktop, then rename the original
executable, the shortcut will essentially be severed. To
re-establish it you'll have to re-create the shortcut from
scratch.
In a true object-oriented environment, all shortcut-like links to
the executable would have been updated automatically by the
underlying object management model. Chicago has no such
underpinnings, so links are easily broken by novice users who are
unfamiliar with the crudeness of the Chicago interface.
Going hand-in-hand with Chicago's shortcut mechanism is the
product's support for long file and directory names on FAT
volumes. Microsoft is emphasizing Chicago's ability to
automatically convert long file/directory names into 8.3
character abbreviations for compatibility with existing DOS and
Windows applications. What they seem to be ignoring, however, is
the fact that promoting the use of long names can be disastrous
when there is no underlying object model.
Take, for example, the novice user who, upon discovering long
filenames, decides to "reorganize" their hard disk. They
gleefully rename directories at will, unaware that they are
severing shortcut after shortcut in the process. Suddenly none
of their applications work, and I/S is called in to undo the
damage (which in some cases may mean reinstalling both operating
system and applications).
The Chicago desktop itself is not an OLE 2.0 object. This
statement in itself has no ramifications until you start
understanding what type of integration is lost due to this lack
of object technology. This deficiency in the product, means that
an application is not well integrated with the desktop and does
not inherit any of the advantages like Drag 'n' Drop support.
Heralded by Microsoft as one of Chicago's key selling points, the
new Windows interface may in the end prove to be one of its
biggest flaws. Without an underlying system object model to tie
everything together, this new "shell" may prove to be an I/S
support nightmare.
OS/2 - TRUE OBJECT-ORIENTATION
OS/2's WorkPlace Shell is a true object-oriented interface. The
underlying System Object Model (SOM) provides complete
object-tracking so simple operations like dragging a directory to
another directory won't invalidate links and other interface
structures. Thus it's easier on both novices and IS support
staff alike.
SOM also allows applications to fully manipulate the WorkPlace
Shell interface. A good example is cc:Mail for OS/2, which uses
SOM to seamlessly integrate its in/outbox interfaces with the
WorkPlace Shell desktop. This level of integration isn't
possible under Chicago since its shell is itself not an object.
APPLICATION SUPPORT
===================
CHICAGO - STILL DOS AFTER ALL THESE YEARS
"Chicago eliminates the need for DOS. It is a true operating
system..."
This is one of the more colorful myths surrounding Microsoft's
Chicago operating environment. Microsoft claims that Chicago
eliminates the need for DOS - that DOS and Windows are now
completely integrated and that all the old restrictions that DOS
brought to the table have been eliminated.
While it is true that you will no longer have to purchase a
separate DOS product in order to install and use Chicago, this in
no way constitutes the eradication of DOS as a part of the
Windows operating system equation. DOS is still there, lurking
in the shadows. It's just been cleverly disguised by a different
Windows GUI. And though much of its functionality - including
file system access - has been replaced by 32-bit Chicago VxDs
(Virtual Device Drivers), there are still ways in which DOS can
hinder the Windows environment.
Take real-mode device drivers, for example. Under DOS/Windows
3.1 you were forced to load all DOS device drivers at DOS
boot-time via the CONFIG.SYS file. These drivers would then
occupy all DOS sessions under Windows' 386 Enhanced Mode,
impacting their available conventional memory and limiting the
overall configurability of the Windows VDM architecture.
Chicago suffers from this very same limitation. Any real-mode
DOS device drivers that you wish to access from within Chicago
must be loaded via CONFIG.SYS at boot-time. Thus, if you want
access to a particular resource, and this resource requires a DOS
device driver, you'll be forced to pay a penalty in terms of lost
conventional memory and potential compatibility problems across
all Chicago VDMs.
And what about troublesome applications like games? Chicago
features a special DOS session - the "Single MS-DOS Application
Mode" - that allows such applications to execute unencumbered by
the confines of a traditional Virtual DOS Machine (virtual I/O,
video memory, etc.). What Microsoft doesn't publicize, however,
is the fact that, in order to invoke this mode, you must
essentially shut-down Chicago. All running applications close,
and the Chicago GUI itself is paged to disk. This entire process
can take up to a minute depending on the speed of the hardware in
use and the number of open applications - quite a disruption,
especially when you're trying to finish that last minute memo or
download a large file from a host system.
OS/2 - A BETTER DOS THAN DOS (OR CHICAGO)
OS/2 really does eliminate the need for DOS. It's VDMs are
completely configurable, allowing you to create individual
CONFIG.SYS and AUTOEXEC.BAT files for each DOS session. This is
an important option in those situations where a single device
driver or TSR configuration for all VDMs would be inadequate.
OS/2's VDMs are also highly backward-compatible and can also be
configured to allow direct hardware access for applications that
require it. And if an application truly refuses to run under
OS/2 you can use the "dual-boot" option to run real DOS in about
the same amount of time it takes you to invoke Chicago's "Single
MS-DOS Application Mode."
INDEPENDENT SOFTWARE VENDOR COMMITMENTS
=======================================
CHICAGO: AN ISV HEADACHE
One area where Microsoft continues to be uncertain is on the
subject of API standards. Independent Software Vendors (ISVs)
have been fighting an uphill battle in their efforts to pin-down
Microsoft's overall API strategy. This is especially true of the
native Chicago API, Win32c, which is itself a subset of the full
Win32 API published nearly two years ago and implemented on
Windows NT.
Further exacerbating the situation is Microsoft's continual
updating of the Win32c specification. New APIs emerge almost
monthly, many of which extend Win32 in ways that tie applications
to the Chicago platform. This has aggravated ISVs who wish to
write cross-platform applications for Windows, Windows NT, and
Chicago. The only way these ISV's can write cross-platform
applications, because of the different APIs support, is to poll
the Kernel, determine which API is available and write dual or
triple path code. With the APIs still in a state of flux there is
no guarantee that the multiple path code will work.
What this means to the 32-bit operating system customer is a
potential delay in the release of Chicago-compatible Win32
applications. Given the architectural limitations of Chicago's
Win16 application support - especially when multitasking and
stability are major considerations - lack of Win32 applications
could represent a serious obstacle to the platform's widespread
adoption. Chicago needs Win32 applications before it even begins
to make sense as a replacement for Windows 3.1. But given the
confusion and frustration in the ISV community it may be some
time before we see a substantial selection of Win32 titles.
OS/2 - A CONSISTENT MESSAGE
In contrast to Microsoft's "API du jour" strategy, IBM has stood
firm on its promises to support open standards and honor ISV
commitments. There is one 32-bit OS/2 Presentation Manager API
for both client and server systems. Applications written to that
API will work across OS/2 versions running on Intel-based PC's,
and will be easily portable to more advanced implementations in
the future (including OS/2 for PowerPC).
OS/2 currently boasts over 2000 native applications, all of which
tap into the superior multitasking and performance of the world's
most popular 32-bit operating system.
SUMMARY
=======
OS/2: THE RIGHT ANSWER
As you can see, Microsoft's Chicago operating system is long on
hype and somewhat short on technology. But if you've followed
their product offerings over the past few years, this revelation
should really come as no surprise. Microsoft has a track record
of delivering "cosmetically advanced" operating systems while
ignoring the more important issues like robustness, capacity, and
true object-orientation.
In contrast, IBM has a very different track record, one that
speaks of commitment to open standards and listening to customer
needs. This is the same company that has been developing cutting
edge OS technology for mainframe and minicomputer systems since
the dawn of the information age. With OS/2, IBM has laid the
foundation for a truly robust, high-capacity computing
environment that preserves your existing investments while
opening the door to the future.
You can see the difference in areas like the OS/2 user interface.
The WorkPlace Shell, in conjunction with the System Object Model
(SOM), provide a truly object-oriented computing environment, one
that thinks for you and doesn't break-down when you try to tap
into its power. Likewise, OS/2's multitasking represents a
no-compromises approach to bringing this powerful capability to
the masses. From native OS/2 applications to its robust Win-OS2
VDMs, it is an operating system that can juggle your most complex
tasks with ease.
So in the end, the wise choice is obvious: OS/2 has the backward
compatibility you want, the stability and reliability you need,
and the kind of rock-solid commitment to excellence you've come
to expect from the world's number one software company, IBM.
Chicago looks more and more like a warmed-over version of
yesterday's technology, not the "next generation Windows"
platform that Microsoft is advertising it to be.
So what about Chicago? Good question! With one foot still
buried in the DOS/Windows grave, Chicago is yesterday's
technology dressed-up to look like tomorrow's 32-bit OS. Why
wait for an impostor? OS/2 is here today, and represents the
real future in personal computer operating systems.
APPENDIX A: FEATURES CHARTS FOR OS/2 AND CHICAGO
================================================
The following charts provide a summary of OS/2 and Chicago
features, including multitasking characteristics, application
environments, and bundled productivity tools.
OS/2 VS CHICAGO ON ARCHITECTURE
WARP LAN
FEATURE WARP CLIENT CHICAGO
32-bit Window Management Yes Yes No (1)
32-bit Graphics Subsystem Yes Yes No (2)
32-bit Printing Subsystem Yes Yes Yes
32-bit Multimedia Subsystem Yes Yes Yes
32-bit Kernel Yes Yes Yes
Demand Paged Virtual Memory Yes Yes Yes
HPFS Support Yes Yes No
Non-locking Input Queue (3) Yes Yes No
(Applications can keep running)
(1) USER is 16-bit, non-reentrant code
(2) 50% of GDI calls are serviced by 16-bit, non-reentrant code
(3) WARP, new version of OS/2, has an engine that will unlock
the input queue if it is locked
OS/2 VS. CHICAGO ON APPLICATION ENVIRONMENTS
WARP LAN
FEATURE WARP CLIENT CHICAGO
16-bit OS/2 PM Applications Yes Yes No
32-bit OS/2 PM Applications Yes Yes No
Win32s Applications (Ver 1.0 & 1.1) Yes Yes Yes
Preemptive Multitasking (4) Yes Yes No
Win16 Application Support Yes Yes Yes
Win16 Device Driver Support Yes Yes Some (5)
Number of 32-bit Applications 2000+ 2000+ 0 (6)
Available
(4) See chart on multitasking comparison
(5) Windows 3.x communications drivers need to be re-written
(6) Native Chicago applications
OS/2 VS. CHICAGO ON MULTITASKING CHARACTERISTICS
WARP LAN
FEATURE WARP CLIENT CHICAGO
Preemptive of 32-bit Applications Yes Yes Yes
Preemptive of DOS Applications Yes Yes Yes
Preemptive of Win16 Applications Yes Yes No
Preemptive of mixed 16/32-bit Yes Yes No (7)
Applications
Multiple, Protected Win16 VDMs Yes Yes No (8)
Crash Protection Yes Yes No (9)
Preemptive Multi-threading Yes Yes Yes
(7) Win16LOCK prohibits access to USER and portions of GDI
when a Win16 application is executing
(8) All 16-bit applications share a single address space - the
System Virtual Machine (VM)
(9) Key operating system code structures (USER and GDI) share
the System VM address space with 16-bit applications
OS/2 VS. CHICAGO ON USER INTERFACE
WARP LAN
FEATURE WARP CLIENT CHICAGO
Folder Work Areas Yes Yes No
Integration with operating SOM Yes Yes No (10)
Launch Pad Yes Yes Yes
Drag & Drop Deletion Yes Yes No
Drag & Drop Faxing Yes Yes Yes
Drag & Drop Access Paths (change Yes Yes No
execution paths it will still work)
Object Type Templates Yes Yes No
Parent Folder Closing Options Yes Yes No
(10) Chicago shell components are not OLE 2.01 objects"
OS/2 VS. CHICAGO ON MULTIMEDIA
WARP LAN
FEATURE WARP CLIENT CHICAGO
Image Viewer Yes Yes No
Photo CD Support Yes Yes No
Autodesk Animation Yes Yes No
Play any Audio File from Internet Yes Yes No
Audio/Video Synch Manager Yes Yes No
MPEG Support Yes Yes Yes
32-bit Audio/Video Playback Yes Yes Yes
OS/2 VS. CHICAGO ON BUNDLED APPLICATIONS
WARP LAN
FEATURE WARP CLIENT CHICAGO
Internet Access Tools Yes Yes No
FTP Yes Yes No
Telnet Yes Yes No
Gopher Yes Yes No
Newsreader Yes Yes No
WEB Explorer Yes Yes No
CompuServe Front-End Yes Yes No
Word Processor Yes Yes No (11)
Spreadsheet Yes Yes No
Database Yes Yes No
Charting Yes Yes No
Report Writer Yes Yes No
Electronic Mail Yes Yes Yes
Image Viewer Yes Yes No
FAX Yes Yes Yes
Phonebook Yes Yes No
Personal Information Mgr Yes Yes No
Sys Info Yes Yes No
VideoIn Yes Yes No
Video Conferencing Yes Yes No
(11) Chicago comes with a simple text editor, not a word processor
DISCLAIMER
==========
The information contained in this document represents the current view
of IBM Corporation on the issues discussed at the date of publication.
Because IBM must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of IBM, and IBM cannot
guarantee the accuracy of any information presented after the date of
publication.
This document is for informational purposes only. IBM makes NO
WARRANTIES, EXPRESSED OR IMPLIED, IN THIS SUMMARY.
1994 IBM Corporation. All Rights Reserved. Printed in the United
States of America.
OS/2 is a registered trademark of International Business Machines
Corporation.
Microsoft is a registered trademark and Windows is a trademark of
Microsoft, Inc.
NetWare is a registered trademark of Novell, Inc.
�