尚未添加到任何已有项目中的内容:
疑点暂存
Win 3.11 for workgroups Hebrew RTM(the one version 3.11.050):
该版hebrew rtm比后发RTM（无050标识）出的更早，两者皆为RTM。
泰语版wfw3.11rtm版本3.11.0
Win 3.11 for workgroups Russian 1993-10-14 version:
情况可能和win3.2 redchina一样，但因为语言不通找不出决定性的证据。
待写内容
Win3.0 MME待加OEM版: IBM OEM, Creative Labs OEM, NEC OEM(PC98)
MS Team Manager 97 Beta 3
Microsoft Mini Manager build 034
OS2 J2.1 Beta: https://archive.org/download/OS2J21_Beta
mess 0.235开始pc9821ce2 os2安装界面会分出不完整4屏
fmtowns: win3.0 L17+mme V1.0 L20; win3.0 L14+mme V1.0 L10(redump released); win3.1 L10/L11/L12
OS2 Warp 3(Internal revision 8.200 (w207-39)0, 95/04/21) https://archive.org/download/IBMOS2Warp3Collection
Office 97 SR1 CHS特征，WINWORD.EXE SHA1:1891b82f68af0a5c5dea6d93a3fb0305
可能有用的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 vista
版本: Beta2 /560
网址: www.microsoft.com/de/
S/N: GKFV7-F2D9H-QKYXY-777P3-4M73W
PVYFQ-2JTBV-9KXQ2-FQHDY-MTBVH
Gild für die Aktuell gültige deutsche Downloadversion unter:
http://download.windowsvista.com/preview/rc1/de/download.htm
Windows Longhorn 40 CD-keys
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
WF6QT-42PG6-62966-CFPR4-6JPKB
WF7CM-VGQ2G-638TF-MGGG9-K966M
WDHPT-W2688-D8YCG-MXVMD-QFV2Y
WDJ7X-KJWW7-VY4TP-4XVJ8-3KQGM
WDKK4-D8PVY-82P2D-FRJCH-KKQGM
WDMCX-VV2JX-DPYQP-DWJJR-7BKTM
WDMVM-J3FTT-PXQTX-F62HW-8QH2Y
WDPQX-7W72Y-W7KXV-M32Q3-H672Y
WDPTH-H44HD-3PKGG-QVGY8-HWPKB
WDQ23-28KM8-MYCR6-JGKF3-DXJXB
WDQ48-V8QKY-2GB9V-FPDH8-7KV2Y
WDQJQ-RVHQ3-7TYCG-JQDKH-YWYPY
WDRCM-DRVGY-T3YQY-V47YP-XMF9B
WDRR9-TX2PH-R3633-6G882-KBKTM
WDRYW-G682C-BCDFJ-FB2HJ-YCXTM
WDTCJ-PQGH8-76CRJ-CCH4F-RYBPY
WDTQ4-JTC3D-DQHD2-QBD2M-4DDGM
WDV2M-H8QVB-JDV9X-HW7M4-HPCKB
WDV47-MP3XD-D2MD6-7WDPX-X89TM
WDVQX-KQRY7-9R6F4-W76K4-BJ9TM
WDVRV-JHHYY-49893-HPGRB-78DGM
WDWQT-GTWBK-3PG86-3Q7MT-FKQGM
WDX6J-TKPKP-KXRX3-XK8RB-T89TM
WDXHK-8HTXQ-38BVY-HMRRX-TVCKB
WDY7J-VH676-6W6GJ-3XDGD-B2MPY
WDYJD-P9KWP-FF623-J4GF6-7WYPY
WDYMT-9J8DR-737MH-KC2Q4-JRV2Y
WDYPX-JCTPH-6T6X9-Y9BW2-YWT6M
WDYR9-8W7FJ-MBVDK-8P7X8-D4JXB
WD3B4-8FP2F-HG32G-2TKMJ-HM3GM
WD3K9-Y8JT8-XM6HY-6GPF3-3RQGM
WD3RY-GJD27-PXW6X-FVHX6-7466M
WD46W-G43JC-4RG9H-HB9PP-X3H2Y
WD4JJ-XPXKJ-87976-J7VHP-DBRCY
WD78W-DPJ8G-VB3CM-42T2F-73YPY
WD7RD-K96P7-VBPC7-9J8C7-JMBPY
WD7W4-37XP7-Y2CKW-CBR67-Q9FCY
WD7YP-8CV4R-PKPXJ-M3D4H-V24CY
WD84B-X22FW-J73T4-79BVM-GVXTM
WD86P-7KF33-CQ3GQ-VHCBW-R2MPY
WD86P-XK3DX-4437D-CJJWW-BBWXB
WD8FY-8XYBJ-KKDKB-89T3R-RGKTM
WD8TG-V9FKV-3TJ2M-H83CQ-29V2Y
WD933-G4XVY-YXGYM-BHV3T-89JXB
WD94K-W98PY-T8G66-MYYPF-QGWXB
WD9RT-MPRMB-Q222M-MJC9V-QPG6M
WDB43-R8H38-GG786-4672Y-Y28XB
WDB8R-99G7K-XCP8V-B29CB-DWYPY
WDBHQ-H3QDK-94D78-MYQTD-XRV2Y
WDBHY-G8H69-6P2RT-48HP8-VQYPY
WDC69-H38QC-V942H-K4G3J-2M3GM
WDCX9-J4HDH-8JJR3-QMR4B-MF66M
WDD9T-WGV3D-288R7-64QT2-BXQGM
WDDKH-VV469-KV8BX-6WB8V-PGBPY
WDF72-G3BBF-XY3CY-D8673-3KV2Y
WDFVT-QRDR4-VWWG9-KBKMC-WCR9B
WDG28-JJXKY-F68BM-W3PY3-CBKTM
WDG8H-4R4M3-KPH2F-62JB4-KB72Y
WT7B9-R4R28-WXTWV-J74X7-2W9TM
WT8M7-BCR9K-M46HF-CD22C-X9QGM
WT8XB-B6PJB-YKX7B-MKQRT-8RQGM
WT97G-F23H4-VDXFX-KXRFJ-C4JXB
WTBT9-M24W3-CF92M-33CX7-9KJXB
WTBTB-WGXGQ-PC7DX-77GVJ-63T6M
WTBXH-GR3F7-33BPK-6D6JR-K8H2Y
WTC84-4RFX4-BDFX6-3GFF7-BT3GM
WT7B9-R4R28-WXTWV-J74X7-2W9TM
WT8M7-BCR9K-M46HF-CD22C-X9QGM
WT8XB-B6PJB-YKX7B-MKQRT-8RQGM
WT97G-F23H4-VDXFX-KXRFJ-C4JXB
WTBT9-M24W3-CF92M-33CX7-9KJXB
WTCQX-DVXGV-GY6RW-PGDVR-BWPKB
WTDVV-CDPJD-V4VV9-GBHDM-QKV2Y
WTFPG-K797G-XVH8R-J8K7Q-4D9TM
WTGBG-BBDDT-FBCD4-KMY7V-JJH2Y
WTGWT-2YT9B-4RVY8-GKT36-FX2KB
WTH4M-HBTGH-BQHG2-DYVDC-44QGM
WTH7K-F2V9D-FBXD2-C6JWH-6V8XB
WTJ9D-MP8C4-XWMQ7-VH77T-CBWXB
WTKMP-2VY64-7M7RP-GMVWQ-28YPY
WTKXJ-YFQH9-7PWCP-QWDKT-JKJXB
WTKYR-4HT6D-MQ7WC-BRXVF-VY3GM
WTP6B-V37BV-DM7WK-HVKM9-YT3GM
WTPQK-T4TKD-HG94F-9XG34-M6RCY
WTQJ6-QM6CJ-MKR73-R3FTR-KK2KB
WTQPH-383F2-KB2TP-BHY8T-J2R9B
WTRB8-Q632D-RJ2YQ-PJBQY-6WH2Y
WTRDK-TD2GC-Q2WK9-JY68T-DQ49B
WTT7X-48FDM-3FMM4-9HDPQ-C9FCY
WTVVF-XXC4B-JWKJV-FVTRV-36KTM
WTWJR-76DGP-2226Q-6DC9H-TPG6M
WTWWW-M79FR-CRMRW-JMJBW-6T3GM
WTX2X-3TGXR-9YFMX-CTW47-GGBPY
WTY3H-88DGV-TM22T-8XPJ4-XQYPY
WTYM3-9GK9D-H48BY-WGW2P-3WT6M
WTYQF-HBRKH-RM9JK-67HB9-DMBPY
WV27G-D697P-VHBH4-RKJD3-VDDGM
WV2WH-3WMFB-QKXPM-DVYH8-6P8XB
DPTWG-M9PGK-2HT2J-JT9R9-6V8WM
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
.......................................................
Microsoft Windows XP Home Edition build 2462
S/N: QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
S/N: VQGJ8-4T8GB-83M2Y-GFBYX-T22MP
Microsoft windows XP Pro Corp SP2 RC2
M69KY-RGJCB-XK478-RXRC8-4RR78
HRT3W-JXFYD-VT7GC-3XJRY-TPXYQ
Q2FFM-97RHX-YHMDC-Q2DJM-8M9DW
C8KJ8-6CXYG-WQ8KM-WG3Y4-W98T3
FFQP3-HC26G-R98XJ-FHHR9-TT86D
H8846-2FCG7-MDBGT-8VP7K-63XVT
Microsoft Windows.net Server Family
GP99K-BVTDC-M8PTB-T37PJ-7JH2B
Microsoft Windows Longhorn all
S/N: WT7B9-R4R28-WXTWV-J74X7-2W9TM
S/N: WT8M7-BCR9K-M46HF-CD22C-X9QGM
S/N: WT8XB-B6PJB-YKX7B-MKQRT-8RQGM
S/N: WT97G-F23H4-VDXFX-KXRFJ-C4JXB
S/N: WTBT9-M24W3-CF92M-33CX7-9KJXB
S/N: WTQPH-383F2-KB2TP-BHY8T-J2R9B
S/N: WTWWW-M79FR-CRMRW-JMJBW-6T3GM
S/N: KR2X8-M8MGV-FQBRR-322YQ-QPM2Y
S/N: FGQQD-FDFWC-P276Q-GXHGW-4JPJM
Microsoft Windows Longhorn Alpha Build 3683
CKY24-Q8QRH-X3KMR-C6BCY-T847Y
Microsoft Windows Longhorn build 4015 alfa
S/N: CKY24-Q8QRH-X3KMR-C6BCY-T847Y
Microsoft Windows Longhorn Build 4074
s/n: TCP8W-T8PQJ-WWRRH-QH76C-99FBW
Microsoft Windows Longhorn build 4074 beta
S/N: TCP8W-T8PQJ-WWRRH-QH76C-99FBW
Microsoft Windows 2003 .NET Server RC
S/N: HK4GF-RFKKT-C9H7X-3D748-TYF8M
S/N: HDRF9-P7XGM-V23YT-WDMR8-CTBPB
Microsoft Windows 2003 Enterprise Server RC2
S/N: fcdcf-md7gt-tj4fg-qtjw7-d2xr3
Microsoft Windows 2003 RC2
S/N: HJYCJ-647BB-76FYQ-J76JT-P78XD
Microsoft Windows XP 60 day 2509-2532
S/N: RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
Microsoft Windows XP build 2419/2428
S/N: RBDC9-VTRC8-D7972-J97JY-PRVMG
Microsoft Windows XP build 2428/2419
S/N: RBDC9-VTRC8-D7972-J97JY-PRVMG
Microsoft Windows XP build 2469
S/N: Q3R8Y-MP9KD-3M6KB-383YB-7PK9Q
Microsoft Windows XP build 2474/2475
S/N: DTWB2-VX8WY-FG8R3-X696T-66Y46
Microsoft Windows XP build 2481
S/N: QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Microsoft Windows XP build 2502/2505
S/N: JJWKH-7M9R8-26VM4-FX8CC-GDPD8
Microsoft Windows XP build 2505 RC1
S/N: BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
S/N: 411Y0-URB45-34R3B-310N6-70U51
S/N: F0R6R-347JU-57IC3-M0V34-11Z16
S/N: 50M38-0DY53-7UPU5-7H380-M8111
Microsoft Windows XP build 266
S/N: RK7J8-2PGYQ-4P7VL-V6PMB-F6XPQ
OFFICE 2003 Beta2 : DM8R3-3VBXF-F7JRX-FJ7P4-YD3HM
ALL APPS EXCEPT OFFICE : CXDH9-4QMFJ-K482C-49XYF-QTH3Y
FRONTPAGE
INFOPATH
ONENOTE
OUTLOOK WITH BCM
Microsoft Office XP Release Candidate 1 (RC1)
MQPD6-C748R-FMRV6-8C3QK-79THJ
Windows "Longhorn" Client Preview DQ948-7C7YT-W79CT-X38MQ-XXV2Y
Windows .NET Server (Release Candidates) VWB7G-HJY3D-JYDXC-DCGR8-4BBP3
Microsoft Office Pro 2003 Beta 2 Suite DM8R3-3VBXF-F7JRX-FJ7P4-YD3HM
Microsoft Office System 2003 Beta 2 Apps CXDH9-4QMFJ-K482C-49XYF-QTH3Y
Windows Vista Build5365 English DVD ISO
32bit版
PVYFQ-2JTBV-9KXQ2-FQHDY-MTBVH
2J4JT-P34KF-YMGH8-FKDRQ-JP8M9
之前版本的?
TCP8W-T8PQJ-WWRRH-QH76C-99FBW(似乎是5408版)
WBVG8-4JPQB-6HJ6H-XH7YY-D2GQY (Server)
R4HB8-QGQK4-79X38-QH3HK-Q3PJ6 (Client)
64bit版
WGDJW-B8DYC-WVKX4-6MKF4-B8PK8
Microsoft Windows XP Vista Vista BETA Build RC1 S/N: P2B8T-KRHJW-B7KMH-3KM29-Y3XBY
Microsoft Windows XP Service Pack 2 Build 2162 Home Integrated SN:WWWJR-BX7CV-P32X2-C7VT3-QD6BP
MS Windows XP Professional SP2 RC2 beta build 2149 Intergrated SN:XP8BF-F8HPF-PY6BX-K24PJ-TWT6M
Microsoft Windows XP Professional SP2 RC1 Integrated REPACK 15 389 SN:XP8BF-F8HPF-PY6BX-K24PJ-TWT6M
.......................................................
LH 3683 till LH 4029(main) = CKY24-Q8QRH-X3KMR-C6BCY-T847Y
LH 4029(Lab06n) till LH 5112 = TCP8W-T8PQJ-WWRRH-QH76C-99FBW
LH 5212(winmain) till LH 5231= GKFV7-F2D9H-QKYXY-777P3-4M73W
LH 5259 = TGX39-HB48W-R29DH-6BVKB-3XFDW
LH 5270 =
Starter = R93TJ-7R9P9-B9GXM-HPYJM-VDH3W
Home Basic= KJ89T-MF23J-XD9X9-WHDF3-DV8X8
Home Basic N= CDV26-DG6DG-7DY4J-GHXPR-W8YMT
Home Premium = RK83M-X2CQ4-6K2CW-W7HKF-TPTBW
Professional Standard= WHPY8-M92RQ-2KMD9-QWQMK-8KV4M
Professional Standard N= KFBH3-BX3DC-9YFWJ-Y9D7V-TPCJY
Professional Enterprise= MFKHB-RYT8V-443HR-DC64T-T8YRD
Ultimate= R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
LH 5308.17 = 7KYMQ-R788Q-4RF69-KTWKM-92PFJ (All Sku's)
LH 5308.6 =
Ultimate: WGDJW-B8DYC-WVKX4-6MKF4-B8PK8
LH 5310 =
Ultimate: WGDJW-B8DYC-WVKX4-6MKF4-B8PK8
LH 5355 =
Starter= 6GHT4-62PKK-H3274-4YHC4-7FGPY
Home Basic= PY2RB-BQRKG-9TQ3P-GVJ43-VFGR6
Home Basic N= 6J8RT-947JQ-XDGV4-4FCTV-QRRXV
Home Premium = 7KKWR-978CY-8GMWD-X2RF9-PJ6BB
Business= YVT36-YVCP2-J97GQ-7T22R-RWV8P
Business N= 7K8QY-WRC42-QCRDJ-QK968-XFJCJ
Enterprise= MF9PG-RQK7R-26BPJ-TWFYK-RHXCM
Ultimate= 7YJ76-6WJF4-D3PH9-P2Q6W-Y9Q38
LH 5384.4 = PVYFQ-2JTBV-9KXQ2-FQHDY-MTBVH (all Sku's)
Lh 5435 =
Starter 6GHT4-62PKK-H3274-4YHC4-7FGPY
Home Basic PY2RB-BQRKG-9TQ3P-GVJ43-VFGR6
Home Basic N 6J8RT-947JQ-XDGV4-4FCTV-QRRXV
Home Premium 7KKWR-978CY-8GMWD-X2RF9-PJ6BB
Business YVT36-YVCP2-J97GQ-7T22R-RWV8P
Business N 7K8QY-WRC42-QCRDJ-QK968-XFJCJ
Enterprise MF9PG-RQK7R-26BPJ-TWFYK-RHXCM
Ultimate 7YJ76-6WJF4-D3PH9-P2Q6W-Y9Q38
Lh 5466 =
Starter 6GHT4-62PKK-H3274-4YHC4-7FGPY
Home Basic PY2RB-BQRKG-9TQ3P-GVJ43-VFGR6
Home Basic N 6J8RT-947JQ-XDGV4-4FCTV-QRRXV
Home Premium 7KKWR-978CY-8GMWD-X2RF9-PJ6BB
Business YVT36-YVCP2-J97GQ-7T22R-RWV8P
Business N 7K8QY-WRC42-QCRDJ-QK968-XFJCJ
Enterprise MF9PG-RQK7R-26BPJ-TWFYK-RHXCM
Ultimate 7YJ76-6WJF4-D3PH9-P2Q6W-Y9Q38
LH 5491 =
Starter 6GHT4-62PKK-H3274-4YHC4-7FGPY
Home Basic PY2RB-BQRKG-9TQ3P-GVJ43-VFGR6
Home Basic N 6J8RT-947JQ-XDGV4-4FCTV-QRRXV
Home Premium 7KKWR-978CY-8GMWD-X2RF9-PJ6BB
Business YVT36-YVCP2-J97GQ-7T22R-RWV8P
Business N 7K8QY-WRC42-QCRDJ-QK968-XFJCJ
Enterprise MF9PG-RQK7R-26BPJ-TWFYK-RHXCM
Ultimate 7YJ76-6WJF4-D3PH9-P2Q6W-Y9Q38
LH 5723 =
Starter 6GHT4-62PKK-H3274-4YHC4-7FGPY
Home Basic PY2RB-BQRKG-9TQ3P-GVJ43-VFGR6
Home Basic N 6J8RT-947JQ-XDGV4-4FCTV-QRRXV
Home Premium 7KKWR-978CY-8GMWD-X2RF9-PJ6BB
Business YVT36-YVCP2-J97GQ-7T22R-RWV8P
Business N 7K8QY-WRC42-QCRDJ-QK968-XFJCJ
Enterprise MF9PG-RQK7R-26BPJ-TWFYK-RHXCM
Ultimate 7YJ76-6WJF4-D3PH9-P2Q6W-Y9Q38
LH 5728 =
Starter 6GHT4-62PKK-H3274-4YHC4-7FGPY
Home Basic PY2RB-BQRKG-9TQ3P-GVJ43-VFGR6
Home Basic N 6J8RT-947JQ-XDGV4-4FCTV-QRRXV
Home Premium 7KKWR-978CY-8GMWD-
X2RF9-PJ6BB
Business YVT36-YVCP2-J97GQ-7T22R-RWV8P
Business N 7K8QY-WRC42-QCRDJ-QK968-XFJCJ
Enterprise MF9PG-RQK7R-26BPJ-TWFYK-RHXCM
Ultimate 7YJ76-6WJF4-D3PH9-P2Q6W-Y9Q38
LH 5744 =
Starter 6GHT4-62PKK-H3274-4YHC4-7FGPY
Home Basic KHHM6-HC47Q-2JWBW-WYCX4-FWT3B
Home Basic N 6J8RT-947JQ-XDGV4-4FCTV-QRRXV
Home Premium 7T6DF-PJF8R-2DVRB-9CXP9-G2MXG
Business 9C4TD-CPPRV-B7HVB-4976C-H6VW8
Business N 7K8QY-WRC42-QCRDJ-QK968-XFJCJ
Enterprise MF9PG-RQK7R-26BPJ-TWFYK-RHXCM
Ultimate 3YFJ7-3486F-7488V-3VDMF-2PJMW
LH 5758 till 5920.16387 = Use Windows Vista Retail keys
Windows Server Longhorn February 2007 CTP (IA64) —–9JB9R-HV9F2-9TQRG-372M3-DWH6H
Windows Server Longhorn February 2007 CTP (x86 and x64) —- RGVDW-V3J3C-6CD3P-2CQJV-GF4PG
Office System Beta 2 2007 ——— RQCRJ-FCTYM-V3PDF-GRD46-9YHXQ
Office System Groove Server 2007 Beta 2 — WCMWF-H7DD9-3R2Q6-QM863-G7XD6
Office System Project Server 2007 Beta 2 — CYGH3-KVXBH-JDQV3-FFYPP-XGKD3
Office System SharePoint Server 2007 Beta 2 — C39KH-VHBKR-KT62D-Q4FVG-4PB76
.......................................................
: Windows 2000 RC3(2183) CD-Key:
: ========================
: FGWDX-XRVRH-3MG7J-HWQ9W-Q9T2Y
: VXKC4-2B3YF-W9MFK-QB3DB-9Y7MB
: Windows 2000 RC3(2183) Server CD-Key:
: ========================
: WY6PG-M2YPT-KGT4H-CPY6T-GRDCY
: H6TWQ-TQQM8-HXJYG-D69F7-R84VM
: Windows 2000 RC3(2183) Adv. Server CD-Key:
: ========================
: WY6PG-M2YPT-KGT4H-CPY6T-GRDCY
: H6TWQ-TQQM8-HXJYG-D69F7-R84VM
.......................................................
Microsoft Windows Vista Beta 2 Build 5384.4 x86 - Serial.txt
9HBX9-X6VPV-VFG3W-4XJR4-BPHHF
product key windows 7 ultimate rc build 7100(1).txt
Product key: RGQ3V-MCMTC-6HP8R-98CDK-VP3FM
236TW-X778T-8MV9F-937GT-QVKBB
可能有用的MS注册机
- Windows 9X
文件:MEMBETA-Crack for Win98 Beta,~Beta2？-.ZIP
文件:MSCRACK-Unprotect MS Setup installer-.ZIP
文件:MSKEYGEN-MS CD-Key Gen,xxx-xxxxxxx-.ZIP
文件:Pc win98-Crack for Win98 RC3~RTM-.zip
文件:CHIBCRK-Chicago Beta-1M6 Password Crack-.ZIP
文件:Win98 Build 1423 crack(repack).7z
文件:Win95-98-sp1 hackit(repack).7z
文件:PC MEMFX-Memphis 1XXX Shutdown & Text Fix-.ZIP
文件:GL98UREG-Windows98 Build 1998 REG Crack for Windows Update-.ZIP
文件:CHICAFIX-Win95 73g crack-.ZIP
文件:Pc w1559-Win98 1559 Crack-.zip
- Windows NT
文件:Windows Server 2003 Build 3607 CHS Crack.7z
文件:Windows Whistler 2416 Patches.zip
文件:Windows Whistler Beta 2 Build 2428 Logon Fix.zip
文件:Windows Whistler Beta 2 Build 2462.zip
文件:Windows Whistler Xp Beta 2 Build 2462.zip
文件:Windows Xp Beta 2 Build 2469 And 2474 Crack And Serial.zip
文件:Windows Xp Beta 2 Build 2481.zip
文件:Windows Xp Build 2474 2475.zip
文件:Windows Xp Build 2486 2493ad.zip
文件:Windows Xp Build 2505 Rc1 Full With Serial And Crack.zip
Fake随记
MICROSOFT.WINDOWS.8.RC1-LZ0 实际上是Win8 8102.101 x86原iso。
en_winnt_3.1_1xx_oct1991_devkit_x86_en-US.iso 该版本为基于Dec 1991（239）镜像覆盖Oct 1991文件所得产物而不存在属于297的文件。
Beta相关PreDB记录
PreDB 横杠分隔不同来源
MICROSOFT.LONGHORN.ALPHA.BUILD.3683-BETAZ Microsoft.Longhorn.Build.4029-RERLS Microsoft.Windows.Longhorn.4074.Driver.Kit-BetasIRC Microsoft.Windows.Longhorn.WinHEC.Build.4074-BetasIRC Longhorn.4074.Activation.Crack-BetasIRC Microsoft.BizTalk.Server.2004.Service.Pack.2.Beta.SUB100.READ.NFO-BetaInsiders Microsoft.BizTalk.Server.2006.Beta.1-WinBeta Microsoft.BizTalk.Server.2006.Enterprise.Edition.CTP-WinBeta Microsoft.BizTalk.Server.2006.R2.EDI.CTP3-BetaInsiders Microsoft.Certificate.Lifecycle.Manager.Beta.1.SUB100.iNTERNAL-BetaInsiders Microsoft.Commerce.Server.2006.Beta1.SUB100-BetaInsiders Microsoft.Commerce.Server.2007.Beta.R.C.-SKULLZ Microsoft.Exchange.Server.2007.Beta2.x64.DE.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.Beta2.x64.EN.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.Beta2.x86.DE.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.Beta2.x86.EN.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.SP1.Beta.1.64Bit.DVD-WinBeta Microsoft.Host.Integration.Server.2004.Beta.3-BetasIRC Microsoft.ISA.Server.2007.Enterprise.Edition.Beta1.READ.NFO-WinBeta Microsoft.Internet.Explorer.8.32Bit.Build.6001.18343.SUB100-WinBeta Microsoft.Internet.Explorer.8.32Bit.Build.6001.18344.SUB100-WinBeta Microsoft.Internet.Explorer.8.64Bit.Build.6001.18343.SUB100-WinBeta Microsoft.Internet.Explorer.8.64Bit.Build.6001.18344.SUB100-WinBeta Microsoft.Media.Center.SDK.Build.5381.for.Windows.Vista.SUB100-BetaInsiders Microsoft.Media.Center.SDK.Build.5472.for.Windows.Vista.SUB100-BetaInsiders Microsoft.Office.12.Beta.DVD-LH Microsoft.Office.12.Build.3111-COLABLiKJE Microsoft.Office.12.OneNote.Beta.1.READ.NFO-WinBeta Microsoft.Office.12.PRE-RELEASE.Build.3417.Enterprise.Edition-GRAVEDiGGER Microsoft.Office.12.Professional.Beta.1-WinBeta Microsoft.Office.12.Project.Professional.Beta.1.READ.NFO-WinBeta Microsoft.Office.12.Server.Beta.1-WinBeta Microsoft.Office.12.Visio.Professional.Beta.1.READ.NFO-WinBeta Microsoft.Office.2007.Beta.1.Refresh.READ.NFO-PUBLiCBETA Microsoft.Office.2007.Beta2.SPANISH-inD Microsoft.Office.2007.Professional.Beta2.German.AIO-BetaInsiders Microsoft.Office.2007.Professional.Plus.BETA.SPANiSH-iND Microsoft.Office.InfoPath.2003.Toolkit.for.Visual.Studio.2005.Beta2-BetaInsiders Microsoft.Office.Professional.Plus.2007.Beta.1TR-WinBeta Microsoft.Office.Select.2007.DVD.Beta.1.Refresh-PUBLiCBETA Microsoft.SQL.Server.2005.32Bit.WorkGroup.Edition.June.CTP.Build.2000.090.1187.00-WinBeta Microsoft.SQL.Server.2005.64Bit.Standard.Edition.June.CTP.Build.2000.090.1187.00.DVD-WinBeta Microsoft.Speech.Server.2007.Beta.Developer.Edition.for.Windows.XP-WinBeta Microsoft.Speech.Server.2007.Beta.Enterprise.Edition.for.Windows.Server.2003-WinBeta Microsoft.System.Center.Virtual.Machine.Manager.Beta1-LH Microsoft.VSIP.Extras.SDK.2003.Beta.Refresh-BetasIRC Microsoft.Virtual.PC.2004.French.RETAIL-RESET Microsoft.Virtual.PC.2004.Incl.SP1.French.RETAIL-RESET Microsoft.Virtual.PC.2004.SPANiSH-EiTheL Microsoft.Virtual.PC.2007.Beta.x64.SUB100-BetaInsiders Microsoft.Virtual.PC.2007.Beta.x86.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.Enterprise.SP1.Beta.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.R2.SP1.Beta.1-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.1.SUB100.DIRFIX-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.1.x64-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.1.x64.SUB100.DIRFIX-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.2.SUB100-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.2.x64.SUB100-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta2.x64.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.R2.SP1.Beta2.x86.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.v1.1.465.Enterprise.Edition-TBE Microsoft.Visual.Studio.2005.Beta.2.Team.Suite.Edition.DVD-WinBeta Microsoft.Visual.Studio.2005.Workshop.2364-ExAuST Microsoft.Visual.Studio.6.SP6.Beta.Refresh-BetasIRC Microsoft.Visual.Studio.Integration.Package.2003.Beta-BetasIRC Microsoft.WindoFS.Longhorn.Server.32Bit.Build.6001.16497.April.CTP.DVD-WinBeta Microsoft.Windows..Beta..Build.000.x.DVD-WinBeta Microsoft.Windows.2003.Datacenter.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2003.Datacenter.With.SP2.Beta.Refresh.2.Itanium.DVD-LH Microsoft.Windows.2003.Datacenter.With.SP2.Beta.Refresh.2.x64-LH Microsoft.Windows.2003.Enterprise.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2003.SP2.Beta.2786.PROPER-LH Microsoft.Windows.2003.SP2.Beta.2786.x64.PROPER-LH Microsoft.Windows.2003.Server.R2.Enterprise.SP2.RC.Integrated.VOL.Edition-ETH0 Microsoft.Windows.2003.Server.R2.Enterprise.x64.SP2.RC.Integrated.MULTI.IMAGE-ETH0 Microsoft.Windows.2003.Server.R2.SP1.32Bit.RC0-WinBeta Microsoft.Windows.2003.Server.R2.SP1.64Bit.RC1.2038.iNTERNAL.READ.NFO-BetaInsiders Microsoft.Windows.2003.Server.R2.Standard.SP2.RC.Integrated.VOL.Edition-ETH0 Microsoft.Windows.2003.Server.R2.Standard.x64.SP2.RC.Integrated.MULTI.IMAGE-ETH0 Microsoft.Windows.2003.Standard.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2003.Standard.With.SP2.Beta.Refresh.2.x64-LH Microsoft.Windows.2003.Web.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2004.BETA-TSZiSO Microsoft.Windows.7.32Bit.Build.6801.DVD-WinBeta Microsoft.Windows.7.64Bit.Build.6801.DVD-WinBeta Microsoft.Windows.7.Beta.1.Build.7000.x86.DVD-WinBeta Microsoft.Windows.7.Beta.1.Build.7000.x86.DVD.REPACK-WinBeta Microsoft.Windows.Driver.Kit.for.Windows.Vista.Build.5456.DVD-BetaInsiders Microsoft.Windows.Driver.Kit.for.Windows.Vista.Build.5728.DVD-BetaInsiders Microsoft.Windows.Home.Server.Beta.2.DVD-WinBeta Microsoft.Windows.Live.Mobile.10.7.Refresh.Beta.SUB100.READ.NFO-BetaInsiders Microsoft.Windows.Longhorn.4074.Driver.Kit-BetasIRC Microsoft.Windows.Longhorn.4074.SDK-BetasIRC Microsoft.Windows.Longhorn.Alpha.M5.Build.4015-MNP Microsoft.Windows.Longhorn.Build.4074.iNTERNAL.DVD-BuRN Microsoft.Windows.Longhorn.Pro.Corp.FiNAL-BETASIRC Microsoft.Windows.Longhorn.Server.32Bit.Build.5600.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.5744.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.5757.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.6001.16461.February.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.6001.16497.April.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.6001.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.build.5384.4.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.5757.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.6001.16461.February.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.6001.16497.April.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.6001.DVD-WinBeta Microsoft.Windows.Longhorn.Server.Beta2.Build.5384.x64.GERMAN.DVD-BetaInsiders Microsoft.Windows.Longhorn.Server.Beta2.Build.5384.x86.GERMAN.DVD-BetaInsiders Microsoft.Windows.Longhorn.WinHEC.Build.4074.IA64-BetasIRC Microsoft.Windows.Longhorn.WinHEC.Build.4074.Repack-WinBeta Microsoft.Windows.Longhorn.build.4083.AMD64-WinBeta Microsoft.Windows.Media.Player.11.Beta.Build.5358.For.Windows.XP.SUB100-BetaInsiders Microsoft.Windows.Media.Player.11.Beta.Build.5358.For.Windows.XP.UNGENUINE.SUB100-BetaInsiders Microsoft.Windows.Media.Player.v11.GENUINE.CRACK-ETH0 Microsoft.Windows.SDK.for.Windows.Vista.Build.5456.DVD-BetaInsiders Microsoft.Windows.SDK.for.Windows.Vista.Build.5728.DVD-BetaInsiders Microsoft.Windows.Server.2003.32Bit.Standalone.SP1.GERMAN.Build.1812-WinBeta Microsoft.Windows.Server.2003.64Bit.Enterprise.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.Enterprise.Edition.SP2.English.RC-LH Microsoft.Windows.Server.2003.Enterprise.Edition.SP2.English.Volume.Licensing.Customers.RC-LH Microsoft.Windows.Server.2003.Service.Pack.2.Build.2725.JP.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2725.JP.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2786.EN.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2805.DE.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2805.EN.x64-BetaInsiders Microsoft.Windows.Server.2008.32Bit.Build.6001.16606.June.CTP.DVD-WinBeta Microsoft.Windows.Server.2008.32Bit.Build.6001.17042.DVD-WinBeta Microsoft.Windows.Server.2008.SP2.64Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5270.DVD.iNTERNAL-WinBeta Microsoft.Windows.Vista.32Bit.Build.5365.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5381.1.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5536.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Vista.32Bit.b5384.4.DVD-WinBeta Microsoft.Windows.Vista.5472.Language.Pack.English.for.Vista.x64-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.English.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.German.for.Vista.x64-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.German.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.Japanese.for.Vista.x64-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.Japanese.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5536.Language.Pack.English.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5536.Language.Pack.German.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5536.Language.Pack.Japanese.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.64Bit.Build.5365.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5381.1.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5384.4.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5744.DVD-WinBeta Microsoft.Windows.Vista.Automated.Install.Kit.RC2.WAIK.DVD-WinBeta Microsoft.Windows.Vista.Build.5259.TAP.Build.x86.DVD.READNFO-BetaInsiders Microsoft.Windows.Vista.Build.5270.Driver.Kit.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.Build.5308.x86.German.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5456.x64.DVD.iNTERNAL-BetaInsiders Microsoft.Windows.Vista.Build.5456.x64.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5456.x86.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.Symbols.amd64fre-BetaInsiders Microsoft.Windows.Vista.Build.5728.Automated.Installation.Kit.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5840.x86.DVD-BetaInsiders Microsoft.Windows.Vista.SP1.32Bit.Build.6001.16549.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.32Bit.Build.6001.16659.Beta.1.DVD-WinBeta Microsoft.Windows.Vista.SP1.Update.32Bit.Build.6001.16633.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.32Bit.Build.6001.16659.Beta.1.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.32Bit.Build.6001.17128.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.64Bit.Build.6001.16633.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.64Bit.Build.6001.16659.Beta.1.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.SP2.32Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Vista.SP2.64Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Vista.x64.Build.5456.DVD-WinBeta Microsoft.Windows.Vista.x64.Build.5456.DVD.NFOFix-WinBeta Microsoft.Windows.XP.Embedded.SP2.Feature.Pack.2007.CTP.Build.1-LH Microsoft.Windows.XP.Embedded.SP2.Feature.Pack.2007.CTP.Build.2-LH Microsoft.Windows.XP.Pro.x64.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.XP.Professional.SP2.Build.2138.Beta.Integrated-ETH0 Microsoft.Windows.XP.Professional.SP2.RC2.Integrated-ETH0 Microsoft.Windows.XP.SP3.Build.3180.READ.NFO-WinBeta Microsoft.Windows.XP.SP3.Build.3205.Beta.1.READ.NFO-WinBeta Microsoft.Windows.XP.SP3.Build.3300.RC2.READ.NFO-WinBeta Microsoft.Windows.XP.Tablet.PC.Edition.2004.Alpha.Upgrade-BetasIRC Microsoft.Windows.XP.x64.Professional.Corporate.SP2.RC.Integrated.MULTI.IMAGE-ETH0 Microsoft.XImage.Build.5270.SUB100-BetaInsiders Microsoft.XImage.Build.5270.ia64.SUB100-BetaInsiders Microsoft.XImage.Build.5270.x64.SUB100-BetaInsiders Windows.7.RC1.build.7048.x64.SPANiSH-RABO Windows.7.RC1.build.7048.x86.32bits.SPANiSH-RABO Windows.7.ServerEnterprise.Build.7260.x64-OMGWTF Windows.7.ULTIMATE.German.Build.7600.RTM.incl.Toolkit.x64-NOTRADE Windows.Driver.Kit.EDW.Build.5456-LH Windows.Georgia.Build.2380-MDWF Windows.Vista.Build.5231-LH Windows.Vista.Build.5259.x86.DVD-IND Windows.Vista.Build.5308.x86.German.DVD-BetaInsiders Windows.Vista.Build.6000.SDK.v0.0.RTM.DVD-NLN Windows.Vista.CTP.Build.5231-LH Windows.Vista.CTP.Build.5231.CD.Version.READ.NFO-LH Windows.Vista.CTP.Build.5231.x64-LH Windows.Vista.CTP.Build.5231.x64.CD.Version.READ.NFO-LH Windows.Vista.CTP.Build.5270-LH Windows.Vista.CTP.Build.5270.x64-LH Windows.Vista.CTP.Build.5308-LH Windows.Vista.CTP.Build.5308.x64-LH Windows.Vista.Ultimate.Build.5308.60-LH Windows.Vista.Ultimate.Build.5308.60.x64-LH longhorn.4051.PDC.WINBETA.iso-bootable windows.longhorn.build.4008-mnp MICROSOFT.WINDOWS.2000.AND.NT4.SOURCE.CODE-SCENELEADER --------------------------------------- MICROSOFT.COMMAND.SHELL.V.2.PREVIEW.PACKAGE-BETASIRC MICROSOFT.EXCHANGE.SERVER.2000.RELEASE.CANDIDATE.1-RiSE MICROSOFT.HOST.INTEGRATION.SERVER.2000.BETA.2-RiSE MICROSOFT.LCS.2005.ENTERPRISE.BETA.SUB100-BRiCK MICROSOFT.LCS.2005.ENTERPRISE.EDITION.RC.SUB100-BRiCK MICROSOFT.LCS.2005.STANDARD.BETA.SUB100-BRiCK MICROSOFT.LCS.2005.STANDARD.EDITION.RC.SUB100-BRiCK MICROSOFT.MONEY.2005.BETA.1-BRiCK MICROSOFT.OFFICE.2010.v14.0.4302.1000.BETA.1.VOLUME.X86-64.ENGLISH-WZT MICROSOFT.OFFICIAL.BETA.CURRICULUM.WINDOWS.2000.MANAGING.A.NETWORK.ENVIRONMENT.COURSE.2126A-JGT MICROSOFT.OPERATIONS.MANAGER.2005.EXPRESS.RC2.SUB100-BRiCK MICROSOFT.OPERATIONS.MANAGER.2005.FULL.RC2.SUB100-BRiCK MICROSOFT.SMALL.BUSINESS.ACCOUNTING.2006.BETA.2.INTERNAL-BRiCK MICROSOFT.SMS.2003.DMFP.BETA.2.SUB100-BRiCK MICROSOFT.SMS.2003.SP1.RC1.UPGRADE-BRiCK MICROSOFT.SQL.SERVER.2005.BETA.2.RESOURCE.DVD-BRiCK MICROSOFT.SQL.SERVER.2005.DEVELOPER.POST.BETA.2-BRiCK MICROSOFT.VIRTUAL.SERVER.2005.ENTERPRISE.RC.SUB100-BRiCK MICROSOFT.WINDOWS.2003.SP1.1247.BETA-BRiCK MICROSOFT.WINDOWS.2003.SP1.1260.BETA-BRiCK MICROSOFT.WINDOWS.8.RC1.ISO-LZ0 MICROSOFT.WINDOWS.DRIVER.FOUNDATION.INTERNAL.SUB100-BRiCK MICROSOFT.WINDOWS.MILLENIUM.RC1-GLoW MICROSOFT.WINDOWS.XP.SP2.SOURCE-CODE.Hacked-EXPLOiT Microsoft.BizTalk.Server.2004.Service.Pack.2.Beta.SUB100.READ.NFO-BetaInsiders Microsoft.BizTalk.Server.2006.Beta.1-WinBeta Microsoft.BizTalk.Server.2006.R2.EDI.CTP3-BetaInsiders Microsoft.Biztalk.Server.2004.BETA-HUiSO Microsoft.Certificate.Lifecycle.Manager.Beta.1.SUB100.iNTERNAL-BetaInsiders Microsoft.Codename.Avalon.and.Indigo.Beta1.RC.iNTERNAL-BetaInsiders Microsoft.Codename.Avalon.and.Indigo.Community.Technology.Preview.March.2005-WinBeta Microsoft.Codename.Istanbul.Enterprise.Build.1168-WinBeta Microsoft.Codename.Istanbul.Enterprise.Build.1168-WinBeta2 Microsoft.Codename.Istanbul.Standard.Build.1168-WinBeta Microsoft.Command.Shell.Beta1.ia64-BetaInsiders Microsoft.Command.Shell.Beta1.x64-BetaInsiders Microsoft.Command.Shell.Beta1.x86-BetaInsiders Microsoft.Command.Shell.Preview.v2.0-WinBeta Microsoft.Commerce.Server.2006.Beta1.SUB100-BetaInsiders Microsoft.Commerce.Server.2007.Beta.R.C.-SKULLZ Microsoft.Dashboard.Retail.4627.XBOX-COMPLEX Microsoft.DirectX.8.Win2K.BETA-KAMEL Microsoft.DirectX.8.Win9XME.BETA-KAMEL Microsoft.English.Query.v7.5.Beta.2-uFo Microsoft.Enterprise.Desktop.Virtualization.Beta.1.0.66.SUB100-WinBeta Microsoft.Exchange.Server.2007.Beta2.x64.DE.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.Beta2.x64.EN.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.Beta2.x86.DE.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.Beta2.x86.EN.iNTERNAL-BetaInsiders Microsoft.Exchange.Server.2007.SP1.Beta.1.64Bit.DVD-WinBeta Microsoft.Groove.Server.2010.Beta.Build.4006.x64-WinBeta Microsoft.Host.Integration.Server.2004.Beta.3-BetasIRC Microsoft.Host.Integration.Server.2004.Beta2-BetasIRC Microsoft.Host.Integration.Server.2004.RC1-BetasIRC Microsoft.Hyper-V.Server.2008.R2.RC.x64.DVD-WinBeta Microsoft.Hyper-V.Server.2008.R2.x64-ZWTiSO Microsoft.ISA.Server.2007.Enterprise.Edition.Beta1.READ.NFO-WinBeta Microsoft.Internet.Explorer.7.0.5296.0.Beta.2.Validation.Patch.FREE.FROM.WEB-iND Microsoft.Internet.Explorer.7.0.Build.5346.5.Beta.2.x86.German-PDC Microsoft.Internet.Explorer.7.0.Build.5358.SUB100-BetaInsiders Microsoft.Internet.Explorer.7.Beta.1-WinBeta Microsoft.Internet.Explorer.8.32Bit.Build.6001.18343.SUB100-WinBeta Microsoft.Internet.Explorer.8.32Bit.Build.6001.18344.SUB100-WinBeta Microsoft.Internet.Explorer.8.64Bit.Build.6001.18343.SUB100-WinBeta Microsoft.Internet.Explorer.8.64Bit.Build.6001.18344.SUB100-WinBeta Microsoft.Kodu.Beta.1.0.0.104-WinBeta Microsoft.Kodu.Beta.1.0.22.0.Academic.Version-WinBeta Microsoft.Kodu.Beta.1.0.22.0.General.Version-WinBeta Microsoft.Kodu.Beta.1.0.23.0.Academic.Version-WinBeta Microsoft.Kodu.Beta.1.0.23.0.General.Version-WinBeta Microsoft.Kodu.Beta.1.0.7.0-WinBeta Microsoft.Limit.Login.Beta-BetasIRC Microsoft.MSN.Messenger.7.5.0160.Beta-BetaInsiders Microsoft.MSN.Messenger.7.5.0162.Beta-BetaInsiders Microsoft.MSN.Messenger.v6.2.0137.Multiaccount.and.Ads.Remover.WinALL.iNTERNAL.Patch-NGEN Microsoft.Management.Console.2.1.Beta2-BetaInsiders Microsoft.Management.Console.2.1.Beta2.SDK-BetaInsiders Microsoft.Media.Center.SDK.Build.5381.for.Windows.Vista.SUB100-BetaInsiders Microsoft.Media.Center.SDK.Build.5384.for.Windows.Vista.SUB100-BetaInsiders Microsoft.Media.Center.SDK.Build.5456.for.Windows.Vista.SUB100-BetaInsiders Microsoft.Media.Center.SDK.Build.5472.for.Windows.Vista.SUB100-BetaInsiders Microsoft.Office.12.Beta.1.AIO.DVD.READ.NFO-WinBeta Microsoft.Office.12.Beta.DVD-LH Microsoft.Office.12.Build.3111-COLABLiKJE Microsoft.Office.12.FrontPage.Beta.1.READ.NFO-WinBeta Microsoft.Office.12.OneNote.Beta.1.READ.NFO-WinBeta Microsoft.Office.12.PRE-RELEASE.Build.3417.Enterprise.Edition-GRAVEDiGGER Microsoft.Office.12.PRE.RELEASE.Build.3417.Enterprise.Edition-GRAVEDiGGER Microsoft.Office.12.Professional.Beta.1-WinBeta Microsoft.Office.12.Project.Professional.Beta.1.READ.NFO-WinBeta Microsoft.Office.12.Server.Beta.1-WinBeta Microsoft.Office.12.Visio.Professional.Beta.1.READ.NFO-WinBeta Microsoft.Office.2003.SP1.Build.6353-WinBeta Microsoft.Office.2007.Beta.1.Refresh.READ.NFO-PUBLiCBETA Microsoft.Office.2007.Beta.2.iNTERNAL.French.WinALL.Cracked-ENGiNE Microsoft.Office.2007.Beta2.SPANISH-inD Microsoft.Office.2007.Professional.Beta2.German.AIO-BetaInsiders Microsoft.Office.2007.Professional.Plus.BETA.SPANiSH-iND Microsoft.Office.2010.BETA.1.Build.4417.x64-UP2DATE Microsoft.Office.2010.BETA.1.Build.4417.x86-UP2DATE Microsoft.Office.2010.Build.4536.NFOFiX-WinBeta Microsoft.Office.2010.Build.4536.x64-WinBeta Microsoft.Office.2010.Build.4536.x86-WinBeta Microsoft.Office.2010.PRE.RTM.Build.4730.x64-UP2DATE Microsoft.Office.2010.PRE.RTM.Build.4730.x86-UP2DATE Microsoft.Office.2010.Professional.Plus.RC0.Build.4734-WinBeta Microsoft.Office.2010.Professional.Plus.RC0.x64.Build.4734-WinBeta Microsoft.Office.2010.SP1.Beta1-WinBeta Microsoft.Office.2010.Web.Applications.Beta.1-WinBeta Microsoft.Office.B2.Refresh.AIO-WinBeta Microsoft.Office.InfoPath.2003.Toolkit.for.Visual.Studio.2005.Beta2-BetaInsider Microsoft.Office.Professional.Plus.2007.Beta.1TR-WinBeta Microsoft.Office.Professional.Plus.2010.Techical.Preview.x64.DVD-iND Microsoft.Office.Professional.Plus.2010.Techical.Preview.x86-iND Microsoft.Office.Select.2007.DVD.Beta.1.Refresh-PUBLiCBETA Microsoft.Office.System.2003.Beta.2.Kit.MULTILINGUAL-LCDiSO Microsoft.Operations.Manager.2005.Beta.3.Bundle-WinBeta Microsoft.Operations.Manager.2005.Beta3.Express.SUB100-BetasIRC Microsoft.Operations.Manager.2005.Beta3.Full.SUB100-BetasIRC Microsoft.PURE.A.U.T.O.v5442154.5b-ZWTiSO Microsoft.Plus.Digital.Media.Edition.ENGLiSH-NLiSO Microsoft.Plus.for.WindowsXP.GERMAN.INTERNAL.iSO-MATRIX Microsoft.Project.Professional.2010.Beta.1.x64-WinBeta Microsoft.Project.Professional.2010.Beta.1.x86-WinBeta Microsoft.Project.Professional.2010.Build.4536.x64-WinBeta Microsoft.Project.Professional.2010.Build.4536.x86-WinBeta Microsoft.Project.Server.2010.Beta.Build.4006.x64-WinBeta Microsoft.Proxy.3.Comet.beta2-PWA Microsoft.SMS.2003.Inventory.Tool.for.Dell.Updates.Beta.iNTERNAL-BRiCK Microsoft.SMS.2003.SP1.Beta-BetasIRC Microsoft.SQL.Server.2005.32Bit.April.Community.Technology.Preview.Build.2000.090.1116.00.DVD-WinBet Microsoft.SQL.Server.2005.32Bit.April.Community.Technology.Preview.Build.2000.090.1116.00.DVD-WinBeta Microsoft.SQL.Server.2005.32Bit.CTP-WinBeta Microsoft.SQL.Server.2005.32Bit.Devel.Edi.Edition.June.CTP.Build.2000.090.1187.00.DVD-WinBeta Microsoft.SQL.Server.2005.32Bit.Developer.Edition.June.CTP.Build.2000.090.1187.00.DVD-WinBeta Microsoft.SQL.Server.2005.32Bit.Enterprise.Edition.June.CTP.Build.2000.090.1187.00.DVD.READ.NFO-WinB Microsoft.SQL.Server.2005.32Bit.Enterprise.Edition.June.CTP.Build.2000.090.1187.00.DVD.READ.NFO-WinBeta Microsoft.SQL.Server.2005.32Bit.Express.Edition.June.CTP.Build.2000.090.1187.00-WinBeta Microsoft.SQL.Server.2005.32Bit.Exss.Edition.June.CTP.Build.2000.090.1187.00-WinBeta Microsoft.SQL.Server.2005.32Bit.Standard.Edition.June.CTP.Build.2000.090.1187.00.DVD-WinBeta Microsoft.SQL.Server.2005.32Bit.WorkGroup.Edition.June.CTP.Build.2000.090.1187.00-WinBeta Microsoft.SQL.Server.2005.64Bit.Developer.Edition.June.CTP.Build.2000.090.1187.00.DVD-WinBeta Microsoft.SQL.Server.2005.64Bit.Standard.Edition.June.CTP.Build.2000.090.1187.00.DVD-WinBeta Microsoft.SQL.Server.2005.AMD64.December04.CTP-WinBeta Microsoft.SQL.Server.2005.AMD64Bit.Build.9.00.852-WinBeta Microsoft.SQL.Server.2005.Build.9.00.852-WinBeta Microsoft.SQL.Server.2005.December04.CTP-WinBeta Microsoft.SQL.Server.2005.Developer.Edition.Beta2-YUM Microsoft.SQL.Server.2005.Enterprise.July.CTP-ARNISO Microsoft.SQL.Server.2008.R2.Enterprise.Evaluation.November.CTP.DVD-LiBiSO Microsoft.SQL.Server.2008.R2.Enterprise.Evaluation.November.CTP.REPACK.DVD-LiBiSO Microsoft.SQL.Server.2008.R2.Express.Edition.CTP.v10.50.1092-Lz0 Microsoft.SQL.Server.2008.R2.Express.Edition.CTP.v10.50.1092.WIN64-Lz0 Microsoft.SQL.Server.2008.R2.Express.Edition.November.CTP.v10.50.1352.12.FRENCH-iND Microsoft.SQL.Server.2008.R2.Express.Edition.November.CTP.x64.v10.50.1352.12.FRENCH-iND Microsoft.SQL.Server.2008.R2.RC1-WinBeta Microsoft.Search.Server.2010.Beta.Build.4006.x64-WinBeta Microsoft.SharePoint.Designer.2010.RC1.Build.4730.1010-WinBeta Microsoft.SharePoint.Designer.Technical.Preview.2010-Lz0 Microsoft.SharePoint.Designer.Technical.Preview.2010.x64-Lz0 Microsoft.SharePoint.Foundation.2010.RC1.Build.4730.1010-WinBeta Microsoft.SharePoint.Server.2010.RC1.Build.4730.1010-WinBeta Microsoft.Sharepoint.Designer.2010.Build.4536.x64-WinBeta Microsoft.Sharepoint.Designer.2010.Build.4536.x86-WinBeta Microsoft.Sharepoint.Foundation.2010.Build.4536.x64-WinBeta Microsoft.Sharepoint.Server.2010.Beta.Build.4006.x64-WinBeta Microsoft.Sharepoint.Server.2010.Build.4536.x64-WinBeta Microsoft.Sharepoint.Workspace.2010.Build.4536.x64-WinBeta Microsoft.Sharepoint.Workspace.2010.Build.4536.x86-WinBeta Microsoft.Small.Business.Accounting.2006.b1.0.2601-WinBeta Microsoft.Speech.Server.2007.Beta.Developer.Edition.for.Windows.XP-WinBeta Microsoft.Speech.Server.2007.Beta.Enterprise.Edition.for.Windows.Server.2003-WinBeta Microsoft.Sql.Server.2005.Beta.2.Developer.ISO-BetasIRC Microsoft.Student.Graphing.Calculator.2006.Beta2-BetaInsiders Microsoft.Student.Graphing.Calculator.2006.Beta3-BetaInsiders Microsoft.System.Center.Operations.Manager.2007.MP.Authoring.Console.SP1.RC.amd64.x86.SUB100-BetaInsiders Microsoft.System.Center.Operations.Manager.2007.SP1.RC-BetaInsiders Microsoft.System.Center.Operations.Manager.2007.SP1.RC.Upgrade-BetaInsiders Microsoft.Systems.Management.Server.2003.RC1.Japanese-GiSO Microsoft.TrainingBase.Disk.Base09A.RC.DVD-iRONiSO Microsoft.VSIP.Extras.SDK.2003.Beta.Refresh-BetasIRC Microsoft.Virtual.PC.2007.Beta.x64.SUB100-BetaInsiders Microsoft.Virtual.PC.2007.Beta.x86.SUB100-BetaInsiders Microsoft.Virtual.PC.2007.RC.x64.SUB100-BetaInsiders Microsoft.Virtual.PC.2007.RC.x86.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.Enterprise.SP1.Beta.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.R2.SP1.Beta.1-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.1.SUB100.DIRFIX-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.1.x64-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.1.x64.SUB100.DIRFIX-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.2.SUB100-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta.2.x64.SUB100-LH Microsoft.Virtual.Server.2005.R2.SP1.Beta2.x64.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.R2.SP1.Beta2.x86.SUB100-BetaInsiders Microsoft.Virtual.Server.2005.build.1.1.445-WinBeta Microsoft.Virtual.Server.2005.v1.1.465.Enterprise.Edition-TBE Microsoft.Visio.2010.Build.4536.x64-WinBeta Microsoft.Visio.2010.Build.4536.x86-WinBeta Microsoft.Visual.Studio.2005.Beta.2-WinBeta Microsoft.Visual.Studio.2005.Beta.2.Standard.Edition.DVD-WinBeta Microsoft.Visual.Studio.2005.Beta.2.Team.Suite.Edition.DVD-WinBeta Microsoft.Visual.Studio.2005.July.CTP.Build.8.00.50630.0.Professional.Edition.DVD-WinBeta Microsoft.Visual.Studio.2005.July.CTP.Build.8.00.50630.0.Standard.Edition.DVD-WinBeta Microsoft.Visual.Studio.2005.June.CTP.Build.8.00.50601.0.Professional.Edition.DVD.READ.NFO-WinBeta Microsoft.Visual.Studio.2005.June.CTP.Build.8.00.50601.0.Team.Foundation.Server.Edition.READ.NFO-Win Microsoft.Visual.Studio.2005.June.CTP.Build.8.00.50601.0.Team.Foundation.Server.Edition.READ.NFO-WinBeta Microsoft.Visual.Studio.2005.June.CTP.Build.8.00.50601.0.Team.Suite.Edition.DVD.READ.NFO-WinBeta Microsoft.Visual.Studio.2005.Workshop.2364-ExAuST Microsoft.Visual.Studio.2008.Beta2.Professional.DVD.iNTERNAL-BetaInsiders Microsoft.Visual.Studio.2008.Beta2.Team.Suite.DVD.iNTERNAL-BetaInsiders Microsoft.Visual.Studio.2010.Integrated.Shell.Beta.2-WinBeta Microsoft.Visual.Studio.2010.Isolated.Shell.Beta.2-WinBeta Microsoft.Visual.Studio.2010.Service.Pack.1.Only.Beta.READNFO.MULTI-KOPiE Microsoft.Visual.Studio.2010.Ultimate.x86.Beta.2-WinBeta Microsoft.Visual.Studio.6.SP6.Beta.Refresh-BetasIRC Microsoft.Visual.Studio.CTP.December.DVD-WinBeta Microsoft.Visual.Studio.Integration.Package.2003.Beta-BetasIRC Microsoft.Visual.Studio.Lightswitch.Beta1.READNFO.x86-KOPiE Microsoft.WinFS.Beta.1-WinBeta Microsoft.WinFX.SDK.Avalon.CTP-WinBeta Microsoft.WindoFS.Longhorn.Server.32Bit.Build.6001.16497.April.CTP.DVD-WinBeta Microsoft.Windows.2000.Advanced.Server.SP4.and.RU1.Build.1.032.Beta.Integrated-ETH0 Microsoft.Windows.2000.Advanced.Server.SP4.and.RU1.Build.1.038.Beta.Integrated-ETH0 Microsoft.Windows.2000.Professional.SP4.and.RU1.Build.1.021.Beta.Integrated-ETH0 Microsoft.Windows.2000.Professional.SP4.and.RU1.Build.1.028.Beta.Integrated-ETH0 Microsoft.Windows.2000.Professional.SP4.and.RU1.Build.1.032.Beta.Integrated-ETH0 Microsoft.Windows.2000.Professional.SP4.and.RU1.Build.1.038.Beta.Integrated-ETH0 Microsoft.Windows.2000.Server.SP4.and.RU1.Build.1.028.Beta.Integrated-ETH0 Microsoft.Windows.2000.Server.SP4.and.RU1.Build.1.032.Beta.Integrated-ETH0 Microsoft.Windows.2000.Server.SP4.and.RU1.Build.1.038.Beta.Integrated-ETH0 Microsoft.Windows.2000.Update.Rollup.1.Beta1.Build.1.028.German-BetaInsiders Microsoft.Windows.2000.Update.Rollup.1.Build.1.038.English.SUB100-BetaInsiders Microsoft.Windows.2000.Update.Rollup.1.Build.1.038.German.SUB100-BetaInsiders Microsoft.Windows.2000.Update.Rollup.1.Build.1.038.Japanese.SUB100-BetaInsiders Microsoft.Windows.2003.Datacenter.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2003.Datacenter.With.SP2.Beta.Refresh.2.Itanium.DVD-LH Microsoft.Windows.2003.Datacenter.With.SP2.Beta.Refresh.2.x64-LH Microsoft.Windows.2003.Enterprise.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2003.SP1.1184.Interim.Update.CD-BetasIRC Microsoft.Windows.2003.SP1.Beta.1173.SDK-BetasIRC Microsoft.Windows.2003.SP2.Beta.2786.PROPER-LH Microsoft.Windows.2003.SP2.Beta.2786.ia64-LH Microsoft.Windows.2003.SP2.Beta.2786.x64.PROPER-LH Microsoft.Windows.2003.Server.R2.Enterprise.SP2.RC.Integrated.VOL.Edition-ETH0 Microsoft.Windows.2003.Server.R2.Enterprise.x64.SP2.RC.Integrated.MULTI.IMAGE-ETH0 Microsoft.Windows.2003.Server.R2.SP1.32Bit.RC0-WinBeta Microsoft.Windows.2003.Server.R2.SP1.32Bit.RC1.2038.German-BetaInsiders Microsoft.Windows.2003.Server.R2.SP1.32Bit.RC1.2038.iNTERNAL.READ.NFO-BetaInsiders Microsoft.Windows.2003.Server.R2.SP1.64Bit.RC1.2038.iNTERNAL.READ.NFO-BetaInsiders Microsoft.Windows.2003.Server.R2.Standard.x64.SP2.RC.Integrated.MULTI.IMAGE-ETH0 Microsoft.Windows.2003.Server.SP1.Build.1260.32Bit-WinBeta Microsoft.Windows.2003.Service.Pack.1.Build.1159.Update-BetasIRC Microsoft.Windows.2003.Service.Pack.2.Build.2805.ia64-LH Microsoft.Windows.2003.Standard.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2003.Standard.With.SP2.Beta.Refresh.2.x64-LH Microsoft.Windows.2003.Web.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.2004.BETA-TSZiSO Microsoft.Windows.7.32Bit.Build.6801.DVD-WinBeta Microsoft.Windows.7.64Bit.Build.6801.DVD-WinBeta Microsoft.Windows.7.7260.RTM.BRANCH.32BIT-BBYERSR Microsoft.Windows.7.Beta.1.Build.7000.x64.DVD-WinBeta Microsoft.Windows.7.Beta.1.Build.7000.x86.DVD-WinBeta Microsoft.Windows.7.Beta.1.Build.7000.x86.DVD.REPACK-WinBeta Microsoft.Windows.7.Build.6519.M1.DVD-MSBP Microsoft.Windows.7.Build.6956.x86.DVD-MSBP Microsoft.Windows.7.Build.7000.x64.German.DVD-MSBP Microsoft.Windows.7.Build.7000.x86.German.DVD-MSBP Microsoft.Windows.7.Build.7022.x86.DVD-WinBeta Microsoft.Windows.7.Build.7057.x64.READ.NFO.DVD-iND Microsoft.Windows.7.Build.7057.x86.DVD-iND Microsoft.Windows.7.Build.7068.DIRFiX.NFOFiX.x86.DVD-iND Microsoft.Windows.7.Build.7068.x64.DVD-iND Microsoft.Windows.7.Build.7077.x64.iNTERNAL.DVD-iND Microsoft.Windows.7.Build.7077.x86.iNTERNAL.DVD-iND Microsoft.Windows.7.Build.7086.x86.DVD-iND Microsoft.Windows.7.Build.7100.RC1.x64.iNTERNAL-UP2DATE Microsoft.Windows.7.Build.7100.RC1.x86.iNTERNAL-UP2DATE Microsoft.Windows.7.Build.7127.PRE-RTM.GERMAN.x64.iNTERNAL-UP2DATE Microsoft.Windows.7.Build.7127.PRE-RTM.GERMAN.x86.iNTERNAL-UP2DATE Microsoft.Windows.7.Build.7127.x64.DVD-iND Microsoft.Windows.7.Build.7127.x86.DVD-iND Microsoft.Windows.7.Build.7201.x64.DVD-iND Microsoft.Windows.7.Build.7201.x64.iNTERNAL-UP2DATE Microsoft.Windows.7.Build.7201.x86-UP2DATE Microsoft.Windows.7.Build.7227.PRE-SP1.x86-UP2DATE Microsoft.Windows.7.Build.7229.x64.DVD-iND Microsoft.Windows.7.Build.7229.x86.DVD-iND Microsoft.Windows.7.Build.7264.x64-Win7 Microsoft.Windows.7.Build.7264.x86-Win7 Microsoft.Windows.7.RC.Build.7100.x64.MSDN-ISO Microsoft.Windows.7.RC.b7100.x64.DVD-SheepNET Microsoft.Windows.7.RC.b7100.x64.DVD-ZoneNetGay Microsoft.Windows.7.RC.b7100.x64.DVD-oneNEThomosexuAL Microsoft.Windows.7.RC.b7100.x86.DVD-LocalNet Microsoft.Windows.7.RC1.Build.7100.x64.DVD-iND Microsoft.Windows.7.RC1.Build.7100.x86.DVD-iND Microsoft.Windows.7.RC1.Language.Pack.x64.DVD-iND Microsoft.Windows.7.RC1.Language.Pack.x86.DVD-iND Microsoft.Windows.7.Ultimate.7601.16537.100327.PreSp1-SITES_INT Microsoft.Windows.7.beta.7137.0.090521.1745.X64.DVD-iND Microsoft.Windows.7.beta.7137.0.090521.1745.X86.DVD-iND Microsoft.Windows.7.x64.Build.7264-iND Microsoft.Windows.8.1.Build.6.3.9369.x64.DVD-iND Microsoft.Windows.8.BETA.BLUID.7850.M1.x86.PC-FRANCO_Int Microsoft.Windows.99.ENGLISH.RARE.BETA.BOOTABLE.ISO-NAKENHUND Microsoft.Windows.Application.Compatibility.Toolkit.4.0.Beta.WiNXP-BRiCK Microsoft.Windows.Automated.Installation.Kit.Vista.SP1.Build.16659-BetaInsiders Microsoft.Windows.Automated.Installation.Kit.Vista.SP1.Build.16659.German-BetaInsiders Microsoft.Windows.Automated.Installation.Kit.Vista.SP1.Build.16659.Japanese-BetaInsiders Microsoft.Windows.Automated.Installation.Kit.for.Windows.7.Build.7100.DVD-WinBeta Microsoft.Windows.Centro.Beta1.3DVD.READ.NFO-BetaInsiders Microsoft.Windows.Centro.CTP.3DVD.READ.NFO.iNTERNAL-BetaInsiders Microsoft.Windows.Codename.Longhorn.4066.Enterprise.Edition.x86-MSBP Microsoft.Windows.Command.Shell.Preview.V.3.WiNXP2K3-BRiCK Microsoft.Windows.DCT.5.2.Beta2.REPACK-BetasIRC Microsoft.Windows.Defender.Beta.2.Build.1.1.1051.0-BRD Microsoft.Windows.Defender.Beta.2.Build.1.1.1347.0-iND Microsoft.Windows.Defender.Beta.2.Build.v1.1.1347.0-ECU Microsoft.Windows.Defender.Beta.2.Build.v1.1.1347.0.German-ECU Microsoft.Windows.Defender.v1.1.1593.0-ECU Microsoft.Windows.Defender.x64.v1.1.1593.0-ECU Microsoft.Windows.Driver.Kit.Build.6001.16549-BetaInsiders Microsoft.Windows.Driver.Kit.EDW.Build.5483.DVD-BetaInsiders Microsoft.Windows.Driver.Kit.For.Windows.Vista.Build.5840.DVD.PRE.RTM-LH Microsoft.Windows.Driver.Kit.for.Windows.7.Build.7100-WinBeta Microsoft.Windows.Driver.Kit.for.Windows.Vista.Beta2.Build.5384.DVD-BetaInsiders Microsoft.Windows.Driver.Kit.for.Windows.Vista.Build.5456.DVD-BetaInsiders Microsoft.Windows.Driver.Kit.for.Windows.Vista.Build.5472.DVD-BetaInsiders Microsoft.Windows.Driver.Kit.for.Windows.Vista.Build.5600.DVD-BetaInsiders Microsoft.Windows.Driver.Kit.for.Windows.Vista.Build.5728.DVD-BetaInsiders Microsoft.Windows.Embedded.Standard.CTP.DVD-MSBP Microsoft.Windows.Essential.Business.Server.Beta2.3DVD.READ.NFO-BetaInsiders Microsoft.Windows.Essential.Business.Server.RC1.4DVD.READ.NFO-MSBP Microsoft.Windows.HCT.12.0.Beta-BetasIRC Microsoft.Windows.HCT.v11.2-TBE Microsoft.Windows.HPC.Pack.2008.Beta2-MSBP Microsoft.Windows.HPC.Server.2008.Beta.1-BetaInsiders Microsoft.Windows.HPC.Server.2008.R2.RC-WinBeta Microsoft.Windows.HPC.Server.2008.RC2-MSBP Microsoft.Windows.HPC.Server.2008.RC2.SDK.x64-MSBP Microsoft.Windows.HPC.Server.2008.RC2.SDK.x86-MSBP Microsoft.Windows.Home.Server.2010.Build.7360-WinBeta Microsoft.Windows.Home.Server.Beta.2.DVD-WinBeta Microsoft.Windows.Home.Server.CTP.DVD-SWARE Microsoft.Windows.Journal.WinALL-FTS Microsoft.Windows.Live.Mail.Desktop.8.0.Build.0624.SUB100-BetaInsiders Microsoft.Windows.Live.Messenger.8.0.Build.0863.SUB100-BetaInsiders Microsoft.Windows.Live.Mobile.10.7.Beta1.SUB100.READ.NFO-BetaInsiders Microsoft.Windows.Live.Mobile.10.7.Beta1.for.Windows.Vista.Testers.SUB100.READ.NFO-BetaInsiders Microsoft.Windows.Live.Mobile.10.7.PocketPC.Refresh.Beta.for.Windows.Vista.Testers.SUB100.READ.NFO-BetaInsiders Microsoft.Windows.Live.Mobile.10.7.Refresh.Beta.SUB100.READ.NFO-BetaInsiders Microsoft.Windows.Live.Mobile.10.7.Smartphone.Refresh.Beta.for.Windows.Vista.Testers.SUB100.READ.NFO-BetaInsiders Microsoft.Windows.Logo.Kit.1.1.Build.6475.DVD-BetaInsiders Microsoft.Windows.Longhorn.4074.Driver.Kit-BetasIRC Microsoft.Windows.Longhorn.4074.SDK-BetasIRC Microsoft.Windows.Longhorn.Alpha.Build.4053-STOLEN Microsoft.Windows.Longhorn.Alpha.M5.Build.4015-MNP Microsoft.Windows.Longhorn.Alpha.M6.Build.4008-Sjabby Microsoft.Windows.Longhorn.Beta.1.SDK-BetasIRC Microsoft.Windows.Longhorn.Build.4074.iNTERNAL.DVD-BuRN Microsoft.Windows.Longhorn.Pro.Corp.FiNAL-BETASIRC Microsoft.Windows.Longhorn.Reloaded.M1TR-iND Microsoft.Windows.Longhorn.Server.32Bit.Build.5600.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.5744.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.5757.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.6001.16461.February.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.6001.16497.April.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.Build.6001.DVD-WinBeta Microsoft.Windows.Longhorn.Server.32Bit.build.5384.4.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.5600.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.5744.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.5757.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.6001.16461.February.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.6001.16497.April.CTP.DVD-WinBeta Microsoft.Windows.Longhorn.Server.64Bit.Build.6001.DVD-WinBeta Microsoft.Windows.Longhorn.Server.Beta2.Build.5384.x64.GERMAN.DVD-BetaInsiders Microsoft.Windows.Longhorn.Server.Beta2.Build.5384.x86.GERMAN.DVD-BetaInsiders Microsoft.Windows.Longhorn.Server.Build.5600-LH Microsoft.Windows.Longhorn.Server.Build.5600.x64-LH Microsoft.Windows.Longhorn.Server.x64.build.5384.4.DVD-WinBeta Microsoft.Windows.Longhorn.WinHEC.Build.4074-BetasIRC Microsoft.Windows.Longhorn.WinHEC.Build.4074.AMD64-BetasIRC Microsoft.Windows.Longhorn.WinHEC.Build.4074.IA64-BetasIRC Microsoft.Windows.Longhorn.WinHEC.Build.4074.Repack-WinBeta Microsoft.Windows.Longhorn.b5048.32bit.WinHec.DVD-WinBeta Microsoft.Windows.Longhorn.build.4083.AMD64-WinBeta Microsoft.Windows.Longhorn.build.4083.AMD64.NFOFix-WinBeta Microsoft.Windows.Longhorn.soon-BetaInsiders Microsoft.Windows.Media.Player.11.Beta.Build.5358.For.Windows.XP.SUB100-BetaInsiders Microsoft.Windows.Media.Player.11.Beta.Build.5358.For.Windows.XP.UNGENUINE.SUB100-BetaInsiders Microsoft.Windows.Media.Player.11.Beta.Build.5358.German.For.Windows.XP.UNGENUINE.SUB100-BetaInsiders Microsoft.Windows.Media.Player.9.0.0.3133-BetasIRC Microsoft.Windows.Media.Player.v11.Beta.WinXP.Cracked-CRD Microsoft.Windows.Millennium.Build.2460-CORPGODS Microsoft.Windows.Mobile.2005.Codename.Magneto.5.1.1700.Build.14326.0.0.0-Betas Microsoft.Windows.SDK.for.Windows.Vista.Beta2.Build.5384.DVD-BetaInsiders Microsoft.Windows.SDK.for.Windows.Vista.Build.5456.DVD-BetaInsiders Microsoft.Windows.SDK.for.Windows.Vista.Build.5472.DVD-BetaInsiders Microsoft.Windows.SDK.for.Windows.Vista.Build.5600.DVD-BetaInsiders Microsoft.Windows.SDK.for.Windows.Vista.Build.5728.DVD-BetaInsiders Microsoft.Windows.Server.2003.32Bit.Blade.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.32Bit.Blade.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.32Bit.Blade.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.32Bit.Datacenter.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.32Bit.Datacenter.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.32Bit.Datacenter.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.32Bit.Enterprise.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.32Bit.Enterprise.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.32Bit.Standalone.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.32Bit.Standalone.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.32Bit.Standalone.SP1.Build.1812-WinBeta Microsoft.Windows.Server.2003.32Bit.Standalone.SP1.GERMAN.Build.1812-WinBeta Microsoft.Windows.Server.2003.32Bit.Standard.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.32Bit.Standard.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.32bit.Enterprise.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.32bit.Standard.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.64Bit.Datacenter.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.64Bit.Enterprise.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.64Bit.Standard.SP1.Integrated.Build.1812-WinBeta Microsoft.Windows.Server.2003.AMD64.Enterprise.SP1.Build.1218-WinBeta Microsoft.Windows.Server.2003.AMD64.Standard.SP1.Build.1218-WinBeta Microsoft.Windows.Server.2003.Build.1184-WinBeta Microsoft.Windows.Server.2003.Enterprise.Edition.SP2.English.RC-LH Microsoft.Windows.Server.2003.Enterprise.Edition.SP2.English.Volume.Licensing.Customers.RC-LH Microsoft.Windows.Server.2003.Enterprise.Edition.with.Service.Pack.2.Beta.Build.2175.German.ia64-BetaInsiders Microsoft.Windows.Server.2003.Enterprise.Edition.with.Service.Pack.2.Beta.Build.2175.German.x86-BetaInsiders Microsoft.Windows.Server.2003.Integrated.ENT.AMD64.Build.1184-WinBeta Microsoft.Windows.Server.2003.R2.Beta.IDS.Build.1970-BetaInsiders Microsoft.Windows.Server.2003.R2.Beta.IDS.Build.1970.1.German-BetaInsiders Microsoft.Windows.Server.2003.R2.Beta2.English.iNTERNAL-BetaInsiders Microsoft.Windows.Server.2003.R2.Beta2.German.iNTERNAL-BetaInsiders Microsoft.Windows.Server.2003.R2.Beta2.Japanese.iNTERNAL-BetaInsiders Microsoft.Windows.Server.2003.R2.Beta2.SDK-BetaInsiders Microsoft.Windows.Server.2003.R2.Enterprise.Edition.with.Service.Pack.2.Beta.Build.2175.German.x86.READ.NFO-BetaInsiders Microsoft.Windows.Server.2003.R2.Standard.Edition.with.Service.Pack.2.Beta.Build.2175.German.x86.READ.NFO-BetaInsiders Microsoft.Windows.Server.2003.SP1.1023-WinBeta Microsoft.Windows.Server.2003.SP2.Build.2175.8in1.DVD-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.DE.IA64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.DE.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.EN.IA64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.EN.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.EN.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.JP.IA64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.JP.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2721.JP.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2725.DE.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2725.EN.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2725.EN.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2725.JP.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2725.JP.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2786.EN.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2786.EN.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2805.DE.x86-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2805.EN.x64-BetaInsiders Microsoft.Windows.Server.2003.Service.Pack.2.Build.2805.EN.x86-BetaInsiders Microsoft.Windows.Server.2003.Standard.Edition.with.Service.Pack.2.Beta.Build.2175.German.x86-BetaInsiders Microsoft.Windows.Server.2003.ia64Bit.Standalone.SP1.Build.1812-WinBeta Microsoft.Windows.Server.2003.ia64Bit.Standalone.SP1.GERMAN.Build.1812-WinBeta Microsoft.Windows.Server.2003.x64.Datacenter.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.x64.Datacenter.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.x64.Enterprise.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.x64.Enterprise.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.x64.Standard.SP1.Build.1421-WinBeta Microsoft.Windows.Server.2003.x64.Standard.SP1.Build.1433-WinBeta Microsoft.Windows.Server.2003.x86.Build.1184-WinBeta Microsoft.Windows.Server.2008.32Bit.Build.6001.16606.June.CTP.DVD-WinBeta Microsoft.Windows.Server.2008.32Bit.Build.6001.16648.September.CTP.DVD-WinBeta Microsoft.Windows.Server.2008.32Bit.Build.6001.17042.DVD-WinBeta Microsoft.Windows.Server.2008.64Bit.Build.6001.16606.June.CTP.DVD-WinBeta Microsoft.Windows.Server.2008.R2.64Bit.Build.6801.DVD-WinBeta Microsoft.Windows.Server.2008.R2.64Bit.Build.7000.DVD-WinBeta Microsoft.Windows.Server.2008.R2.64Bit.Build.7100.DVD-WinBeta Microsoft.Windows.Server.2008.SP2.32Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Server.2008.SP2.32Bit.Build.6002.16659.DVD-WinBeta Microsoft.Windows.Server.2008.SP2.64Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Server.2008.SP2.64Bit.Build.6002.16659.DVD-WinBeta Microsoft.Windows.Server.2008.WDK.RC0-BetaInsiders Microsoft.Windows.Server.2008.WDK.RC1.Escrow.Build.6001.17048-BetaInsiders Microsoft.Windows.Server.2008.x64.RC1.Build.6001.17051.DVD-BetaInsiders Microsoft.Windows.Server.2008.x86.RC1.Build.6001.17051.DVD-BetaInsiders Microsoft.Windows.Server.Update.Services.3.0.SP1.RC.X64-BetaInsiders Microsoft.Windows.Server.Update.Services.3.0.SP1.RC.X86-BetaInsiders Microsoft.Windows.Sticky.Notes.WinAll-FTS Microsoft.Windows.Storage.Server.2008.R2.Beta.1-WinBeta Microsoft.Windows.User.State.Migration.Tool.2.6.RC0.WiNALL-BRiCK Microsoft.Windows.V1.1985-dANISHgOLD Microsoft.Windows.Virtual.PC.and.Windows.XP.Mode.for.Windows.7.Build.7100.x64-WinBeta Microsoft.Windows.Virtual.PC.and.Windows.XP.Mode.for.Windows.7.Build.7100.x86-WinBeta Microsoft.Windows.Vista.32Bit.Build.5270.DVD.iNTERNAL-WinBeta Microsoft.Windows.Vista.32Bit.Build.5342.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5365.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5365.DVD-WinBeta. Microsoft.Windows.Vista.32Bit.Build.5381.1.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5384.4.DVD.DIRFIX-WinBeta Microsoft.Windows.Vista.32Bit.Build.5456.DVD.iNTERNAL-WinBeta Microsoft.Windows.Vista.32Bit.Build.5456.DVD.iNTERNAL.NFOFix-WinBeta Microsoft.Windows.Vista.32Bit.Build.5536.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5536.DVD.NFOFiX-WinBeta Microsoft.Windows.Vista.32Bit.Build.5600.RC1.DVD.iNTERNAL-WinBeta Microsoft.Windows.Vista.32Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Vista.32Bit.Build.5744.DVD.iNTERNAL-WinBeta Microsoft.Windows.Vista.32Bit.Server.Core.Build.5270-WinBeta Microsoft.Windows.Vista.32Bit.b5384.4.DVD-WinBeta Microsoft.Windows.Vista.5472.Language.Pack.English.for.Vista.x64-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.English.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.German.for.Vista.x64-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.German.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.Japanese.for.Vista.x64-BetaInsiders Microsoft.Windows.Vista.5472.Language.Pack.Japanese.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5536.Language.Pack.English.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5536.Language.Pack.German.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.5536.Language.Pack.Japanese.for.Vista.x86-BetaInsiders Microsoft.Windows.Vista.64Bit.Build.5270.DVD.iNTERNAL-WinBeta Microsoft.Windows.Vista.64Bit.Build.5342.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5365.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5381.1.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5384.4.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5600.RC1.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5728.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Build.5744.DVD-WinBeta Microsoft.Windows.Vista.64Bit.Server.Core.Build.5270-WinBeta Microsoft.Windows.Vista.Automated.Install.Kit.RC2.WAIK.DVD-WinBeta Microsoft.Windows.Vista.Beta2.Build.5384.x64.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Beta2.Build.5384.x86.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5259.TAP.Build.x86.DVD.READNFO-BetaInsiders Microsoft.Windows.Vista.Build.5259.x86.DVD.READNFO-BetaInsiders Microsoft.Windows.Vista.Build.5270.Driver.Kit.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.Build.5270.x86.German.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5308.x64.German.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5308.x86.German.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5456.x64.DVD.iNTERNAL-BetaInsiders Microsoft.Windows.Vista.Build.5456.x64.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5456.x86.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5456.x86.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.Automated.Installation.Kit.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.Symbols.amd64chk-BetaInsiPREREPORT Microsoft.Windows.Vista.Build.5472.Symbols.amd64chk-BetaInsiders Microsoft.Windows.Vista.Build.5472.Symbols.amd64fre-BetaInsiders Microsoft.Windows.Vista.Build.5472.Symbols.x86chk-BetaInsiders Microsoft.Windows.Vista.Build.5472.Symbols.x86fre-BetaInsiders Microsoft.Windows.Vista.Build.5472.x64.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.x64.German.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.x64.Japanese.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.x86.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.x86.German.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5472.x86.Japanese.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5536.Symbols.x86fre-BetaInsiders Microsoft.Windows.Vista.Build.5536.x86.DVD.iNTERNAL-BetaInsiders Microsoft.Windows.Vista.Build.5536.x86.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5536.x86.JAPANESE.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5552.x86.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5600.Automated.Installation.Kit.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x64.DVD.iNTERNAL-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x64.FRENCH.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x64.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x86.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x86.FRENCH.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x86.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x86.READ.NFO-BetaInsiders Microsoft.Windows.Vista.Build.5600.RC1.x86.SPANISH.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5728.Automated.Installation.Kit.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5728.x64.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5728.x86.GERMAN.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5744.CD.Version.READ.NFO-LH Microsoft.Windows.Vista.Build.5744.RC2.x64.DVD.iNTERNAL-BetaInsiders Microsoft.Windows.Vista.Build.5744.RC2.x86.DVD-BetaInsiders Microsoft.Windows.Vista.Build.5840.x86.DVD-BetaInsiders Microsoft.Windows.Vista.Codename.LIV3D.Beta.1.32Bit.DVD.READ.NFO-WinSeta Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.32Bit.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.64Bit.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.64Bit.Server.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.Developers.Kit-WinBeta Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.FIX-ANTIWPA Microsoft.Windows.Vista.Final.Build.6.0.6000.RTM.SPANISH-BoRrasS Microsoft.Windows.Vista.SP1.32Bit.Build.6001.16549.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.32Bit.Build.6001.16659.Beta.1.DVD-WinBeta Microsoft.Windows.Vista.SP1.Update.32Bit.Build.6001.16633.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.32Bit.Build.6001.16659.Beta.1.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.32Bit.Build.6001.17128.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.64Bit.Build.6001.16633.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.SP1.Update.64Bit.Build.6001.16659.Beta.1.DVD.READ.NFO-WinBeta Microsoft.Windows.Vista.SP2.32Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Vista.SP2.32Bit.Build.6002.16659.DVD-WinBeta Microsoft.Windows.Vista.SP2.64Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Vista.SP2.64Bit.Build.6002.16659.DVD-WinBeta Microsoft.Windows.Vista.SP2.RC.Update.32Bit.Build.6002.16670-WinBeta Microsoft.Windows.Vista.SP2.RC.Update.64Bit.Build.6002.16670-WinBeta Microsoft.Windows.Vista.SP2.Update.32Bit.Build.6002.16497-WinBeta Microsoft.Windows.Vista.SP2.Update.32Bit.Build.6002.16659-WinBeta Microsoft.Windows.Vista.SP2.Update.32Bit.Build.6002.17043-WinBeta Microsoft.Windows.Vista.SP2.Update.64Bit.Build.6002.16497-WinBeta Microsoft.Windows.Vista.SP2.Update.64Bit.Build.6002.16659-WinBeta Microsoft.Windows.Vista.SP2.Update.64Bit.Build.6002.17043-WinBeta Microsoft.Windows.Vista.Service.Pack.1.amd64.Build.6001.16659.DVD-BetaInsiders Microsoft.Windows.Vista.Service.Pack.1.amd64.Build.6001.16659.German.DVD-BetaInsiders Microsoft.Windows.Vista.Service.Pack.1.x64.Build.6001.17042.DVD-BetaInsiders Microsoft.Windows.Vista.Service.Pack.1.x86.Build.6001.16659.DVD.iNTERNAL-BetaInsiders Microsoft.Windows.Vista.Service.Pack.1.x86.Build.6001.16659.German.DVD-BetaInsiders Microsoft.Windows.Vista.Service.Pack.1.x86.Build.6001.17042.DVD-BetaInsiders Microsoft.Windows.Vista.Symbols.Build.5381.amd64-BetaInsiders Microsoft.Windows.Vista.Symbols.Build.5381.x86-BetaInsiders Microsoft.Windows.Vista.x32.Final.Build.6.0.6000.RTM.MSDN.SPANISH-FastSCeNe Microsoft.Windows.Vista.x32.RETAIL.SPANISH-IND Microsoft.Windows.Vista.x64.Build.5456.DVD-WinBeta Microsoft.Windows.Vista.x64.Build.5456.DVD.NFOFix-WinBeta Microsoft.Windows.Vista.x64.Final.Build.6.0.6000.RTM.MSDN.SPANISH-FastSCeNe Microsoft.Windows.Web.Server.2008.R2.64Bit.Build.7000.DVD-WinBeta Microsoft.Windows.Web.Server.2008.SP2.32Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Web.Server.2008.SP2.32Bit.Build.6002.16659.DVD-WinBeta Microsoft.Windows.Web.Server.2008.SP2.64Bit.Build.6002.16497.DVD-WinBeta Microsoft.Windows.Web.Server.2008.SP2.64Bit.Build.6002.16659.DVD-WinBeta Microsoft.Windows.Whistler.Professional.Beta.1.ISO-RiSE Microsoft.Windows.XP.2003.Enterprise.Server.Keygen-YAG Microsoft.Windows.XP.64-Bit.Edition.For.64-bit.Extended.Systems-TBE Microsoft.Windows.XP.64.Bit.SP1.Integrated.For.64.Bit.Ext.Systems-TBE Microsoft.Windows.XP.Embedded.Feature.Preview.2008.CTP-BetaInsiders Microsoft.Windows.XP.Embedded.SP2.Feature.Pack.2007.CTP.Build.1-LH Microsoft.Windows.XP.Embedded.SP2.Feature.Pack.2007.CTP.Build.1.iNTERNAL-BetaInsiders Microsoft.Windows.XP.Embedded.SP2.Feature.Pack.2007.CTP.Build.2-LH Microsoft.Windows.XP.Home.OEM.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.Home.Retail.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.Home.Upgrade.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.PRO.AMD64.Build.1184-WinBeta Microsoft.Windows.XP.Pro.64bit.Build.1812-WinBeta Microsoft.Windows.XP.Pro.AMD64.Build.1218-WinBeta Microsoft.Windows.XP.Pro.x64.Build.1421-WinBeta Microsoft.Windows.XP.Pro.x64.Build.1433-WinBeta Microsoft.Windows.XP.Pro.x64.With.SP2.Beta.Refresh.2-LH Microsoft.Windows.XP.Prof.Corp.SP2.Integr.RC.2.2-LCDiSO Microsoft.Windows.XP.Professional.Corporate.SP2.Integrated.RC.2.2-LCDiSO Microsoft.Windows.XP.Professional.Corporate.SP3.RC1.Build.3244.Integrated-ETH0 Microsoft.Windows.XP.Professional.Corporate.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.Professional.N.Corporate.SP3.RC1.Build.3244.Integrated-ETH0 Microsoft.Windows.XP.Professional.OEM.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.Professional.Retail.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.Professional.SP2.BETA.04.01-TDA Microsoft.Windows.XP.Professional.SP2.Build.2082.Beta.Integrated-ETH0 Microsoft.Windows.XP.Professional.SP2.Build.2138.Beta.Integrated-ETH0 Microsoft.Windows.XP.Professional.SP2.RC1.Integrated-ETH0 Microsoft.Windows.XP.Professional.SP2.RC1.Integrated.REPACK-ETH0 Microsoft.Windows.XP.Professional.SP2.RC2.Integrated-ETH0 Microsoft.Windows.XP.Professional.Student.Edition.SP3.RC1.Build.3244.Integrated-ETH0 Microsoft.Windows.XP.Professional.Student.Edition.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.Professional.Upgrade.SP3.RC2.Build.3300.Integrated-ETH0 Microsoft.Windows.XP.Professional.x64.Edition.Service.Pack.2.Beta.Build.2175-BetaInsiders Microsoft.Windows.XP.Professionnelle.beta.2.FRENCH.ISO-Ulysse Microsoft.Windows.XP.SP1.v1065.WinXP-LUCiD Microsoft.Windows.XP.SP2.2111.2in1-BetasIRC Microsoft.Windows.XP.SP2.2111.Interim.Update.ISO-BetasIRC Microsoft.Windows.XP.SP2.2120.2in1.ISO-BetasIRC Microsoft.Windows.XP.SP2.2126.2in1-BetasIRC Microsoft.Windows.XP.SP2.2142.Express.Installer-BetasIRC Microsoft.Windows.XP.SP2.Beta.2082.Express-BetasIRC Microsoft.Windows.XP.SP2.Beta.2082.Express.REPACK-BetasIRC Microsoft.Windows.XP.SP2.Beta.2082.Full-BetasIRC Microsoft.Windows.XP.SP2.Beta.Build.2120-BetasIRC Microsoft.Windows.XP.SP2.Build.2055.UxTheme.Patch-BetasIRC Microsoft.Windows.XP.SP2.Build.2126-BetasIRC Microsoft.Windows.XP.SP2.Build.2138-BetasIRC Microsoft.Windows.XP.SP2.Build.2142-BetasIRC Microsoft.Windows.XP.SP2.RC1.2096.2in1-BetasIRC Microsoft.Windows.XP.SP2.RC2.Build.2149-WinBeta Microsoft.Windows.XP.SP3.Build.3180.READ.NFO-WinBeta Microsoft.Windows.XP.SP3.Build.3205.Beta.1.READ.NFO-WinBeta Microsoft.Windows.XP.SP3.Build.3300.RC2.READ.NFO-WinBeta Microsoft.Windows.XP.Service.Pack.3.Build.3205.Beta.1.German-BetaInsiders Microsoft.Windows.XP.Service.Pack.3.Build.3205.Beta.1.Japanese-BetaInsiders Microsoft.Windows.XP.Service.Pack.3.Build.3244.RC1-BetaInsiders Microsoft.Windows.XP.Service.Pack.3.Build.3300.RC2.German-BetaInsiders Microsoft.Windows.XP.TPCE.2004.Developer.Kit.1.7-BetasIRC Microsoft.Windows.XP.Tablet.PC.Edition.2004.Alpha.Upgrade-BetasIRC Microsoft.Windows.XP.x64.Professional.Corporate.SP2.RC.Integrated.MULTI.IMAGE-ETH0 Microsoft.XImage.Build.5270.SUB100-BetaInsiders Microsoft.XImage.Build.5270.ia64.SUB100-BetaInsiders Microsoft.XImage.Build.5270.x64.SUB100-BetaInsiders Microsoft_Operations_Manager_2004_Beta2-Winbeta Microsoft_Windows_7_Rc1_Build_7100_x64_FRENCH-DEFEAT Microsoft_Windows_95_950C_OSR2.5_beta-PWA Microsoft_Windows_Server_2003_64Bit_Datacenter_SP1_Integrated_Build_1812-WinBeta Microsoft_Windows_XP_Pro_64bit_Build_1812-WinBeta microsoft.office.2003.one.note.beta-winbeta
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. 此一公式，經測試，僅有一、二組無法使用。
Win98 setupx.dll和ProductType引用
100 - Clean install using Microsoft Internal 101 - Clean install using Full CD 102 - Clean install using CD 103 - Clean install using Full Floppy 104 - Clean install using Floppy 105 - Clean install using Web 110 - Clean install using Select CD 111 - Clean install using MSDN CD 112 - Clean install using WIN98 Upgrade (Windows 98 SE only) 115 - Clean install using Full OEM CD 116 - Clean install using OEM CD 120 - Clean install using OEM Preinstall Kit 121 - Microsoft Windows ME 4.90.3000 ??? 1 2 - Retail CD Upgrade (full too?) 3 - Floppy Upgrade 4 - 5 - 6 - 7 - Floppy 8 - Floppy 9 - OEM CD Full
Win95:
1: Microsoft internal - doesn't require a product key of any kind 2: Retail CD upgrade - requires a 10-digit product key and a qualifying product (MS-DOS, OS/2 or an earlier version of Windows) for upgrade 3: Retail floppy upgrade - requires a 10-digit product key and a qualifying product for upgrade, will check for user information in the bootsector of disk 2 and write it there 4: Retail floppy full - requires a 10-digit product key, will check for user information in the bootsector of disk 2 and write it there 5: Unknown - requires a 10-digit product key. This behaves the same way as type 6, and I've never seen it used on actual installation media of any kind, which leads me to suspect it's entirely unused or was possibly reserved for future use. Maybe this product type was to be used by a planned full retail CD release, but as said, no media has been found so far that actually uses it. 6: Unknown - see type 5 above. 7: OEM Preinstallation Kit floppy - This does not seem to ask for any product key, but will check for user information in the bootsector of disk 2 and write it there. This is a rare media type that was used by OEMs to preinstall Windows 95 onto their computers, the product type is also often overriden with a different one on actual media (see below for how this works). 8: OEM floppy full - requires an OEM product key, will check for user information in the bootsector of disk 2 and write it there. 9: OEM CD full - requires an OEM product key.
关于Win98SE Stepup和Full版的主CAB差别
- 在检查Build 2183A时发现，Full版主CAB相比Stepup版多出以下文件：
dibeng.dll gdi32.dll iosclass.dll krnl386.exe ntdll.dll systhunk.dll vfd.vxd
2222A正式版同样有这些文件差异，待写。
水木清华（newsmth）帖子随记
正式中文版WINDOWS98鉴别方法!
发信人: phn (阿潘), 信区: NewSoftware 标 题: 正式中文版WINDOWS98鉴别方法! 发信站: BBS 水木清华站 (Mon Aug 31 17:12:16 1998) 这是一位网友(和微软有业务联系)告诉我的: if you want to know which is Simplified Chinese Windows 98 final release version CD you can see: 3xxM, autorun, all files' date is 1998-06-19 20:01 don't see version, all version is 4.10.1998 from RC0-RC5, final release is same version. So RC=release candidate. Windows 98 english and chinese SP1 is on schedule. English SP1 will release on Sep. BTW: 我可不是为盗版商推销积压货哦, 嘻嘻 ;o) -- ※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.102.13.24]
关于PWin98SE(2222A)之我见
发信人: cybergene (活泼的基因), 信区: NewSoftware
标 题: 关于PWin98SE(2222A)之我见
发信站: BBS 水木清华站 (Mon Aug 23 13:13:44 1999)
作为一个喜欢尝试各种新软件或软件新版本的Software-Fun，我老早就把自己的
机器升成了Win98SE。见到前面有许多关于询问PWin98SE的情况，下面就把俺的感受
和大家交流交流：
1、过程：
我是先装的PWin98正式版，然后升级到IE5.0，尔后又升级到2184版，最后升级到
2222A的。到现在已经有半年多了，一直也没有重新装过。
2、感受：
从上98后就觉得比原来的97好用多了。我的机器配置是P200MMX+64M+5.1GHDD，在现在
也只能算是低等水平吧，但是就我机器平时的工作量来说，Win98的确很令我满意：
我一般在做主页时需要同时运行如下软件：
Netscape 4.6(one or more)、
IE5.0(one or more)、
Photoshop 5.0CS、
Word 97、
Dreamweaver 2.0、
Apache 1.3.6 for Win32、
Ultraedit6.0、
CuteFTP2.8、
ACDSee32 2.4等
在这种情况下系统只是稍稍有些慢而已，并没有出现不稳定的现象（这一点我要
解释一下：不是从未出过问题，但是半年多来出GPF的次数真的是屈指可数）。
3、一些问题的解释：
a.关于Win98中安装时不拷贝某些文件的问题，我个人的感觉是差别不是非常大，
不过如果自己拷贝了那些文件，在关机时似乎的确会少出现几次不能“安全关机”的
现象。
b.关于IE5容易“死”的问题，是IE5对浏览FTP站点时的处理的确做得不好，我对此
的办法是：凡是ftp://开头的URL我一律复制后用CuteFTP来打开，不用IE5直接点击。
4、一点声明：
俺写上面这些的意思并不是想夸奖98有多么多么的好，仅仅是就事论事而已。
如果Linux下可以方便的处理中文，可能我就不懂98了。：-）
p.s. 关于直接装98se之后IE5没有繁体语言包的问题，我个人认为还是线装98，
然后升级IE5（这时安装语言包），再升成98SE的好。--其实多用不了多少时间的。
--
Talking the way you are talking now. There are things that
have to be done and you do them and you never talk about them.
You don't try to justify them, they can't be justified. You just
do them, then you forget it...
Welcome to DNA Studio: http://202.112.87.24/main.html
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.112.87.24]
Windows 千年盛世 sc beta2 感觉
发信人: kxn (身体恢复中~20%), 信区: NewSoftware 标 题: Windows 千年盛世 sc beta2 感觉 发信站: BBS 水木清华站 (Sun Feb 27 22:02:45 2000) 比较爱死, :( 还挺慢 安装的时候出了一个非法操作，但是居然进行下去了 我是从 98 升级的，所以硬件兼容性不知道，用的都是 98 的 driver 升级以后发现比 98 改变了的有, CD 播放器和 2K 的一样花了 游戏里面多了一些, NT 里的游戏都有了，还多了个蜘蛛牌 自带的是 IE 5.5, 暴不稳定，我用它看小说经常失去响应,而且不知为什么 txt 文件默认用的是楷体字，就更慢了 其他我还真没有看出什么新鲜的，试一试以前的 98 游戏倒是都能玩 于是很快就删掉重装 97 了 Over. -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.136.178]
Q: What is Windows "Whistler"?
发信人: hammer (小棰子), 信区: NewSoftware 标 题: Q: What is Windows "Whistler"? 发信站: BBS 水木清华站 (Mon May 1 12:25:18 2000) business/consumer version of Windows classed as Windows 2001. Q: What will be new in Windows "Whistler"? A: Little is really known, but if it heads the way that Whistler was going to then it will be much more HTML based than any other operating system. Q: Will Windows "Whistler" have a new Graphic User Interface (GUI)? A: Yes, the beginnings are already in place - and internal releases have already done away with the start bar. Q: Has testing of Windows "Whistler" begun? A: Only internally Q: When is Windows "Whistler" due to be finally released? A: No date has been announced but it is expected sometime at the end of 2001. Q: If I am a games player, should I go for Windows 2000 or wait for "Whistler"? A: Defiantly wait for Windows "Whistler" for the simple reason that it is designed for both the business & consumer thus is more adept at games playing. -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.136.246]
Re: WinXP2458下网卡怎么装？NE2000，ISA
发信人: iMEMS (少保九千岁), 信区: NewSoftware 标 题: Re: WinXP2458下网卡怎么装？NE2000，ISA 发信站: BBS 水木清华站 (Fri Mar 23 01:07:12 2001) easy 1. manual install a new device from harddisk from the inf dir in win2k 2. unzip the ne*.* from the drivers.cab in whistler i386 to a temp dir. 3. choose this temp dir when whistler require the dir for these ne2000 compatible sys files. 4. ignore the digital assighment warning, but go on to an end. 5. set the irq and io. 6. restart 7. network tcp/ip setting 【 在 denggang (邓邓) 的大作中提到: 】 : 安装了Win Whistler2458，怎么网卡驱动那么少？我的网卡是旧点， : 但2000也支持的，不识别，也找不到驱动，据说2000的驱动可以用， : 哪里可以找到？ -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.117.51.70]
Re: 谁能在贴一遍xp 2462 sev版，15天的破解方法？
发信人: yern (金黄色), 信区: NewSoftware
标 题: Re: 谁能在贴一遍xp 2462 sev版，15天的破解方法？
发信站: BBS 水木清华站 (Fri Apr 13 20:24:37 2001)
2464a - Beta 2
Product-Key
QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
(I) Pre-Installation Perperations if you didn't download my ISO:
-Extract the .ISO with ISObuster or any other iso extracter
1. Delete idwlog.exe and sysparse.exe from the i386 folder of the
installation folder
2. Replace winlogon.ex_, setupreg.hiv and setupp.ini (i386 folder
also) with those provided in the
files provided in the PreInstall folder.
(II) Post Installation After 100% and final reboot (Safe Mode):
1. Boot into Safe Mode - F8 at startup
2. Start -> Control Panel -> Admin Tools -> CPU Management -> Local
Users
-Delete Microsoft Account and Help Account
-Change guest password
-Rename Administrator
3. Now U need to edit the Registery which is Really easy to do
-Start -> Run
-regedit
-HKEY\Software\Microsoft\WindowsNT\CurrentVersion\
-Modify "RegDone" to 1
-HKEY\Software\Microsoft\WindowsNT\CurrentVersion\WinLogon
-Modify "Activation Required" to 0
-HKEY\Software\Microsoft\WindowsNT\CurrentVersion\WinLogon
-Modify "SFCDisable" to 1
-Close Regedit
4. The final step:
-Start -> Run
*Copy and past these commands one at a time in the run box.
- regsvr32.exe -u regwizc.dll
- regsvr32.exe -u licdll.dll
【 在 mitdreaming (I Love MCSB) 的大作中提到: 】
: 不好意思，谢谢了县!
--
金&黄色
※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.174.17]
Windows XP 2465 crack
发信人: kodey (砍刀), 信区: NewSoftware 标 题: Windows XP 2465 crack 发信站: BBS 水木清华站 (Sun Apr 29 22:52:41 2001) Windows XP 2465 crack by BaTMaN 2465 - Interim Build 2465 Ver. 2002 Product-Key QB2BW-8PJ2D-9X7JK-BCCRT-D233Y (I) Pre-Installation: -Extract the .ISO with ISObuster or any other iso extracter 1. Delete idwlog.exe and sysparse.exe from the i386 folder of the installation folder 2. Replace winlogon.ex_, setupreg.hiv and setupp.ini (i386 folder also) with those provided in the files provided in the PreInstall folder. (II) Post Installation After 100% and final reboot (Safe Mode): 1. Boot into Safe Mode - F8 at startup 2. Start -> Control Panel -> Admin Tools -> Computer Management -> Local Users -Delete Microsoft Account and Help Account -Rename Administrator 3. The final step: -Start -> Run *Copy and past these commands one at a time in the run box. - regsvr32.exe -u regwizc.dll - regsvr32.exe -u licdll.dll (III) Windows XP Remove XP Build From Desktop 1. Right-Click Your Desktop And Press "PrWperties" 2. Goto The "Desktop" Tab 3. Press "Customize Desktop" 4. Move To The "Web" Tab 5. Enable The "Lock Desktop Items Option" 6. Press Ok In The "Customize Desktop" Window And Then In The "Properties" Window There, Your All Done, No More Build No. On Desktop, Even Though A Couple More Annoying Things Were Added Now. -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.200.43.170]
关于xp2480和2491(转载)
发信人: gladglad (lori), 信区: NewSoftware 标 题: 关于xp2480和2491(转载) 发信站: BBS 水木清华站 (Wed May 23 16:01:30 2001) leaboard 论坛出现了一张２４９１的截图，很多人都深信２４91已经发 。可惜的是微软历史还没有在一周之内发布２个内部测试版的先例。再 次说明一下，到目前为止，网络上可供下载的 最新的ＷｉｎＸＰ测试版的版本号是２４７４，英文版，任何更高版本都是假的。 另外那张２４９１的截图制作人Photoshop用的还是蛮不错的． 可惜的是他没有注意到，从２４７４版本开始， 微软在about信息中就已经放弃了"Build 版本号.idx序号.xxxxxx-xxxx"的版本 表示格式，而是采用"Build版本号.main.xxxxxx-xxxx"的格式。 单凭这点，就足以说明那张图是假的了，另外还能说明的是， 作图人自己连２４７４都没有安装上，因此不知道这点小更改，真是百密一疏。 请大家不要再浪费时间讨论２４８０和２４９１的事情了。记住，微软发布内部测试版的时间最短周期是一周！！若真的有新版出来了，我会及时通知大家。 -- 找一个ppmm来告别单身 ※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.169.200]
Re: 请问，xp2774有什么改进，我好决定是否重装
发信人: fiend (紫虹~开阔的心世界不会小), 信区: NewSoftware 标 题: Re: 请问，xp2774有什么改进，我好决定是否重装 发信站: BBS 水木清华站 (Fri May 25 00:02:13 2001) 从我由2465升级后使用8个小时的经验来看 task bar bug没有了 系统启动很快，比2465稍快（我没有安装其他新软件） 关机开始出现无法关闭的情形，后来在一次关机前主动卸载了AVP monitor后 关机正常，也很快，AVP也不用先unload 而且没有turn off实际为restart的bug D3D问题解决，播放mpeg，rm，divx，dvd均无问题 界面方面的改进，抛砖引玉先说几个： 1、开机启动画面，原来的彩色进度条变成了闪烁的loading字样 出现了2002字样 2、IE和explorer的logo从小的转动的地球变成飘动的windowsxp logo 3、开机检查磁盘时的界面变成彩色，和欢迎画面的色彩和结构相仿 4、txt默认图标变漂亮了 5、My Documents下多了一个My Video目录 6、Network Connections的图标有小变化，而且New Connection Wizard 放到左边的Tasks窗口里了 初步印象，改进不大，用2465的倒不需要升级，2469的升升级可以 解决D3D的问题，当然，打那个补丁也可以，不过据说效果不大好 【 在 yuyi99 (ruyi) 的大作中提到: 】 : 到底有什么改进，哪位装了，不妨说说，看了前面的文章，好像毛病很多 : 我刚下载，还没决定是否装，我现在用的是2462 -- へ︿︿ㄟ ┏┳┳━━┳━━━━━━━━━━━━━━━━━━━━━┓ ( p ︶ˇ﹋ˇ︶ o ) ┣╋┫ ↘ ┃ 欢迎访问fiend.dhs.org fiendftp.dhs.org ┃ ╰ ▂▂ ▂▂ ╯ ┣♀╋┳┳┫ 超过6G的mp3 MTV删除中 还有实用软件 ┃ ( 【 ★ ▉ ★ 】 ) ┣┻┻╋♂┫春花秋月┃ ≡≡ ﹌ ● ﹌ ≡≡ ┃ ↖ ┣╋┫㊣≡能不能优雅的走着钢索≡㊣┃ ╰db╯ ┗━━┻┻┻━━━━━━━━━━━━━━━━━━━━━┛ ※ 修改:·fiend 於 May 25 00:03:42 修改本文·[FROM: 166.111.145.231] ※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.145.231]
Re: 请问，xp2774有什么改进，我好决定是否重装
发信人: LiveMotion (LiveMotion@dhxy.pku), 信区: NewSoftware 标 题: Re: 请问，xp2774有什么改进，我好决定是否重装 发信站: BBS 水木清华站 (Thu May 24 23:59:57 2001) 呵呵,要照你这么说,那到rtm出了的时候,不知道有多少bug了 其实xp基本已经定型了,如果不再捆绑什么小东东,现在主要就是 在修正bug了,所以应该是越高的版本越好的说 我觉得2474是不错的,但是由于大家太过着急得到它了,结果在传 播的过程中出了不少意外,但是现在能够得到的最终版本还是很 棒的. 要说比2463,其实改进的地方不是很大,但是2463似乎有工具栏的 bug吧,2474是没有了,而且个人感觉速度比2463有不少提升,不仅 是启动还是应用程序的打开执行什么的.界面作了若干修改,但是 大体保持了一贯的whistler风格,值得一提的是,对于搜索界面作 了美化,左边的链接选择frame加上了蓝色的背景,做成了列表链接 的形势,风格和以前完全不同了,下面还有一只可爱的小狗,挺逗的 反正. 不过如果你怕麻烦或者没有把握能弄清楚哪些是必须的补丁的话, 还是等吧,2480应该就是rc1了 【 在 stid (不需要) 的大作中提到: 】 : 我觉得还是不要装 : 我现在用的2463还可以，不过有一点小毛病，但是可以忍受 : 2474有什么毛病就难说了 -- ※ 修改:·LiveMotion 於 May 25 00:00:47 修改本文·[FROM: 162.105.99.78] ※ 来源:·BBS 水木清华站 smth.org·[FROM: 162.105.99.78]
What's new about winxp2485
发信人: lml (升级中...), 信区: NewSoftware
标 题: What's new about winxp2485
发信站: BBS 水木清华站 (Fri Jun 8 11:11:59 2001)
Anyone who is fooled into thinking that this (build 2485 of Windows XP) is in
fact Release Candidate 1 (RC1) will not be far off the mark. Many people are
already calling this the most stable, fast and complete build to date, not
that it come's a
surprise when you think that every new build "should" be better than the
last anyway.
The reasons for this are among the following:
Internet Explorer bug's are fixed (ie: display window borders works)
Taskbar now flashes orange when in the background (instead of orange "lines")
Start Menu display's correctly (not overlapped by underlying menu)
Direct3D and OpenGL works properly (finally!)
Build number is no longer displayed in "System Properties" tab
Version changes:
Windows Messenger updated to build 4.0.0142
DirectX updated to 8.1 (4.08.01.0810)
Internet Explorer & Outlook Express 6 @ 6.0.2485
Stability is much better giving users a feeling that XP is "ready" just a
week or 2 away from RC1 we wonder if there is much more to improve on!
Downside's to this build are still the Outlook Express icons that need
looking at, these were not displayed correctly on my machine (black
boxes underneath all icons) this may be a sign that they are being worked
on. The Desktop icon still looks sucky
(IMHO) but given that XP is now feature frozen I guess its something we
will have to live with =o(
--
On the Stork Tower
The sun along the mountain bows;
The Yellow River seawards flows.
You will enjoy a grander sight
By climbing to a greater height.
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.200.43.170]
Re: 请教xp2485瘦身方法
发信人: cluck (永久归宿清寒小屋), 信区: NewSoftware
标 题: Re: 请教xp2485瘦身方法
发信站: BBS 水木清华站 (Mon Jun 11 10:07:30 2001)
windows\system32\dllcache
windows\drivercache
windows\help
【 在 Shaggy (摇头虫子) 的大作中提到: 】
: 到底都可以删除什么东西
: 我的C盘之装了xp和offic还有proe，再加上不到500M的My Document
: 4.8G的空间就只剩下1.5G多点了，proe用了不到500M，offic英文和中文补丁一共
: 也就900M吧，就是说xp和他的组件用了1.3个G呢，到底都可以删除什么东西让它
: 减减肥啊。。。。。
--
红酥手，黄滕酒，满城春色宫墙柳；东风恶，欢情薄，一怀愁绪，几年离索，错错错。
春如旧，人空瘦，泪痕红邑鲛绡透；桃花落，闲池阁，山盟虽在，锦书难托，莫莫莫。
－陆 游·钗头凤－
世情薄，人情恶，雨送黄昏花易落；晓风乾，泪痕残，欲笺心事，读语斜阑，难难难。
人成各，今非昨，病魂尝似秋千索；角声寒，夜阑珊，怕人寻问，咽泪妆欢，瞒瞒瞒。
－唐蕙仙·钗头凤－
※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.160.57]
[转载]★★WindowsXP RC1★★
发信人: MarchRain (^_^), 信区: NewSoftware
标 题: [转载]★★WindowsXP RC1★★
发信站: BBS 水木清华站 (Wed Jun 13 23:04:22 2001)
发信人: wiky (★悲情Wiky★), 信区: Newsoftware
标 题: ★★WindowsXP RC1★★
发信站: 荔园晨风BBS站 (Wed Jun 13 22:35:36 2001), 转信
Windows XP「新瓶」不是「舊酒」
令人矚目的Windows XP Professional RC1終於發表了。根據微軟的一貫做法，到
了RC版本的階段，無論是用戶界面或功能都與最終的正式版本相差不遠，因此我們
可以從這RC1 版先睹正式版本的風采。
任重而道遠
微軟希望以XP實現Windows統一作業系統天下的目標，而這重任其實也是兩三年前
曾經賦予Windows 2000的使命。但Windows 2000的如意算盤始終未能打響，否則也
不會有Windows Me的出現了。因此，XP Professional仍然是定位於個人用家，而
Server等其他版本則針對專業用家。雖然我們是次測試的Professional版本只是針
對個人用家，但其安裝 光碟的淨容量竟然多達478MB，微軟對XP的祈望可見一斑。
IE逐漸引退
XP RC1內置的瀏覽器是IE6，但新系統默認的瀏覽器卻換成了多功能的MSN，而IE作
為瀏覽器的地位逐漸下降並且內化，其內核被進一步嵌入了系統 的核心。MSN會依
照使用者的所在國家和城市，為個人度身訂做的單一瀏覽器。用家只需要透過一個
MSN瀏覽器便可以享受娛樂、新聞、購物、聊天室等所有互聯網 內容。就連多媒體
的播放控制界面及Hotmail電郵都包括在同一版面內，表現出微軟企圖獨霸網上多
媒體和相關服務的野心。
翻版從此絕跡
XP的安裝速度十分快，無論從Win 98、Me或Win 2000上都可以直接安裝，安裝過程
十分簡單，相信不會難倒慣於使用微軟產品的用家，在此略過不提。但在安裝的過
程中有一先決條件，就是要求用家原來的作業 系統必須是正版。微軟決心打擊翻
版，所以從XP開始便加入了網上認證的環節。未經認證的XP就只能生存14日，如果
閣下使用的是翻版就自然不可能通過 認證。
萬能檔案總管
這個不顯眼的檔案總管，在不斷演進至今已不只局限在管理文件﹔而是集管理，處
理和瀏覽於一身的萬能總管。XP的檔案總管可以對圖像文件檔 進行更方便的瀏覽
和管理，例如將圖像旋轉，以幻燈換片方式顯示所有圖檔，以及支援播放更多類型
媒體檔案等。XP之檔案總管甚至可以用文件夾 中的文件圖像作為文件夾自身的圖
示。如果需要顯示檔案的細節，檔案總管甚至可以顯示影音文件的作者和版權持有
人等﹔對圖像文件，更可以顯 示出該圖像使用何種牌子型號的數碼相機所拍攝。
功能體貼入微
除了大的改進之外，XP就連一些細微的地方也沒有放過。好像附屬應用程式組中的
小畫家，以前只能支援DIB和BMP這兩種最老套的無壓縮 並體積巨大的格式﹔而
XP Pro中的小畫家現在已經支援JPEG，TIFF，GIF等多種格式。關機的畫面就更加
吸引，當選擇了關機後，桌面的牆紙便由彩色逐漸褪成黑白﹔ 而關機、重新啟動
及睡眠功能則變成了可以選擇的按鈕。
在人機界面方面，XP新增加了人工語音合成引擎，以及熒幕鍵盤，方便輸入工作。
而XP Pro使用的Clear Type技術令到文字的顯示效果更加平滑，尤其是中文的顯示
完全沒有了以前Windows經常見到的筆畫不均勻和文字變形的情。遠程控制功能
則 容許電腦間互相傳送文件，並且由一部電腦操控另外的多部電腦。
作為家用的個人作業系統，XP Pro保留了Win Me受歡迎的系統還原功能，對那些一
知半解又喜歡胡亂嘗試新軟件的玩家就最有用。此外，XP Pro還內置了上網分享和
簡單的防火牆功能。為方便用家管理自己的網頁，XP Pro還有網頁同步功能，並且
可以設定自動排程進行網頁同步更新。此外，XP Pro讓用家可透過互聯網與專門的
標準時間基準進行校正，令電腦的內部時間保持準確。
結論
結論
把Windows XP與之前的版本相比，可見其進步是深層次的，再不只是簡單的改進使
用界面或增加新功能，而是向著Microsoft.net這概念踏出第一步。其中的P ro版
本將會成為家庭用家和遊戲玩家的平台，並徹底取代Win Me。就以RC1中已經內置
了最新的DirectX 8.1版本及顯示卡驅動程式為例，它能夠支援所有新遊戲，
3DMark 2001的測試得分更大幅度超越Win Me，亦改善了以前Win 2000在OpenGL表
現較好而3D成績落後的情。
Microsoft Windows XP涉獵的範圍似乎愈來愈廣，從視窗外觀及介面、互聯網功能
如內置防火牆以至多媒體播放和製作等等，微軟都想納入其王國之內。當驚 嘆
Windows XP功能的同時，也不禁聯想起那些依靠微軟的小型軟件公司的生存空間又
被壓縮了一截。
--
Ｗｅｌｃｏｍｅ Ｔｏ Ｗｉｋｙ ＤＯＤ Ｓｔｕｄｉｏ
ｈｔｔｐ：//１９２．１６８．０．１７７
※ 来源:·荔园晨风BBS站 bbs.szu.edu.cn·[FROM: 192.168.0.177]
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 210.39.3.50]
Re: xp.net和winxp到底有什么区别啊？
发信人: yingfuchen (绝剑), 信区: NewSoftware 标 题: Re: xp.net和winxp到底有什么区别啊？ 发信站: BBS 水木清华站 (Wed Jul 25 00:11:27 2001) .net是server ,advanced server,date center xp是personal,professional 【 在 dailyface (每天新感觉) 的大作中提到: 】 : rt. -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 162.105.52.129]
autopatch for xp2520
发信人: MarchRain (“心软”), 信区: NewSoftware 标 题: autopatch for xp2520 发信站: BBS 水木清华站 (Fri Jul 27 04:29:20 2001) http://perso.chello.fr/lf/autopatch2520.rar This is a modified Windows XP CD. It has an integrated patch that resets the 60 day activation grace period every time the machine reboots. Installation: Any one of the following approaches 1.Boot from CD; 2.Under Windows 9x/ME/NT/2000/XP, run “INSTALL.BAT” to clean install or “UPGRADE.BAT” to upgrade; 3.Under Windows 9x/ME/NT/2000/XP, run setup.exe or winnt32.exe (important: do not select “Dynamic Updates”); 4.Under DOS, run winnt.exe; For 3 and 4, use this key when asked RK7J8 - 2PGYQ - P47VV - V6PMB - F6XPQ Features: No CD key input (if boot from CD or use the .BAT files) No 180 day time limit 60 day grace period (new), which is reset at every reboot No “Comment?” button Pre-installed Tweak UI Pre-installed DirectX manager Pre-installed “Sachs Aquarium” screen saver (new version 0.99L with a starfish) User account “HelpAssistant” and “SUPPORT_388945a0” deleted Built-in “Guest” account disabled Updated XP_XTRAS directory Notes: The activation dialog has been disabled. If you need to open it (to activate XP with a valid key or to see how it looks*), do the following: Open a command window; Type the commands: Regsvr32 /s licdll.dll Regsvr32 /s regwizc.dll %systemroot%\system32\oobe\msoobe.exe /a To disable the dialog again, type the following commands Regsvr32 /s /u licdll.dll Regsvr32 /s /u regwizc.dll -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 210.39.3.50]
Windows XP sn s/n cdkey cd-key
寄信人: windtear (死亡线上的挣扎!) 标 题: Windows XP sn s/n cdkey cd-key 发信站: BBS 水木清华站 (Mon Jul 30 21:11:33 2001) 来 源: 166.111.176.248 2600 BX6HT-MDJKW-H2J4X-BX67W-TVVFG 2542 RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ pro:BX6HT-MDJKW-H2J4X-BX67W-TVVFG home:BQJG2-2MJT7-H7F6K-XW98B-4HQRQ 2535 CH6BH-G7PCX-KTM8K-WRKBD-HC7TW 2526(xp rc2) XB88B-9B96V-CRJPG-64882-GQBDD 60day(also for 3505) RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ 180day internet(telephone) 已经不能用了 用烂了:P 后证明确实不能用了 留作纪念 CXGDD-GP2B2-RKWWD-HG3HY-VDJ7J 2480 cn 再来增加 2464a QB2BW-8PJ2D-9X7JK-BCCRT-D233Y 2462 DW3CF-D7KYR-KMR6C-3X7FX-T8CVM DW87C-76RXP-LLK6C-3FJ2J-2908F 203KR-234TJ-389H8-3F2HU-1W187 2458 2446 QB2BW-8PJ2D-9X7JK-BCCRT-D233Y 2428 F6PGG-4YYDJ-3FF3T-R328P-3BXTG RBDC9-VTRC8-D7972-J97JY-PRVMG
xp2542 cracked!!!
发信人: yingfuchen (绝剑), 信区: NewSoftware 标 题: xp2542 cracked!!! 发信站: BBS 水木清华站 (Fri Aug 17 10:58:41 2001) 终于搞定2542， 下面是crack和我安装成功的shotcut ftp://com.pku.edu.cn/incoming/2542_crack/ 安装说明： 将压缩包中i386下文件解出，覆盖安装文件中i386下文件， 然后用sn:RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ (别的我没试过，出问题我可不负责：） 装完，就可以使用，期限60天，当然，你可以激活，或者接着crack （进safemode，运行reset3.exe 和 pop-up.bat) enjoy it:) -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 162.105.52.129]
Windows XP中发现跟踪码
发信人: ever (流星), 信区: NewSoftware 标 题: Windows XP中发现跟踪码 发信站: BBS 水木清华站 (Wed Aug 29 21:00:29 2001) 发信人: ssun (explorer), 信区: TechNews 标 题: Windows XP中发现跟踪码 发信站: 南京大学小百合站 (Wed Aug 29 15:22:55 2001), 站内信件 (www.pcnews.com.cn 专稿 张永刚)微软位打击盗版真是不遗余力，近日，有人发 现在微软发布的Windows XP本中隐藏有“拷贝标识码”（universally unique identifier）。也就是说，每一份从微软站点下载的拷贝或从微软处得来的CD版 Windows XP都有一个加了密的唯一标识码。由于微软对每一个参与测试Windows XP的用户都进行了详细的登记，所以通过这一标识码可以唯一确定使用这一拷贝的 用户信息。通过这种方式，微软可以跟踪每一份Windows XP的拷贝。如果有谁胆敢 把Windows XP非法拷贝给他人或协助盗版，微软根据盗版Windows XP中的标识码就 可以顺藤摸瓜，找到元凶。 这一标识码由于通过MD5加密算法进行加密所以一直以来都没有被人发现。网 上现在已经有了解码程序，只要下载这一程序，运行“md5 *.iso”就可以得到如 下标识码信息（因拷贝不同会有所不同）： D:\WinXP>md5 *.iso 0227f25ed04d54488b5f52fb4239ba46 *usa_2600__x86fre.per_whistler.iso d1f3716dce6233ab353032c6b67ef40e *usa_2600_x86eval.pro_whistler.iso 36c7fe8b9d9b0d14296d1a380e907867 *usa_2600__x86chk.pro_whistler.iso b3c25315840fdf440760401e95022c35 *usa_2600__symcd2.sym_whistler.iso 所以，使用正版Windows XP的人现在要注意了，不要轻易把自己的拷贝借给他 人安装或复制，因为你的一举一动都被微软看在眼里。 -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.119.60.168]
微软正式承认Windows XP使用跟踪技术（转载）
发信人: Erratic (漂砾), 信区: NewSoftware 标 题: 微软正式承认Windows XP使用跟踪技术（转载） 发信站: BBS 水木清华站 (Mon Sep 3 20:26:44 2001) From : CSDN 微软正式承认Windows XP使用跟踪技术 2001-9-1 17:20:51，阅读次数： 1661 新闻内容： (北京青年报)微软正式承认，在其发布给测试者的Windows XP中确实使用了跟踪技术 ，监视那些泄漏Windows XP的测试人员。 微软在信中写道: 我们真希望你当初能够私下里跟我联系此事。确实，我们使用了跟踪技术监视那些泄 漏Windows XP的人。通过这项技术，我们现在已经发现了大量测试人员，在未经允许的情 况下蓄意泄漏Windows XP给他人，这些人已经被从测试者名单上除名了。你的文章泄漏了 这一隐藏在Windows XP中的秘密，把它公之于众，使我们再也不能像以前那样轻易的发现这些不法之徒，给我 们带来了诸多不便。 大量的Beta版测试网站向我们一次次反应，有很多家伙通过不法手段得到了Windows XP的测试版本。我们的跟踪技术正是为了有效的阻止这一趋势的蔓延。同时，我想你保证 ，这一技术只是一些标记而已，对系统的安装和激活不会产生任何作用。 这一跟踪技术并不涉及任何个人隐私问题： ·它只是一个产品标签，不涉及到任何个人安全和隐私信息。 ·为什么不涉及个人隐私呢？因为得到这一跟踪码的是你，而不是我们。除非你把包 含此跟踪码的私有拷贝四处分发，否则，这一跟踪码只会保存在你的机器当中。 ·我们并不是使用这一技术跟踪什么人下载了，下载了多少次，因为这些信息都已经 被服务器记录在了LOG文件当中，需要时随时可以得到。我们只是使用这一技术跟踪那些 泄漏XP的人，使他们的账号不能再使用。 看来微软也是满肚子苦水，好不容易想出来的妙招就这么泡汤了。 -- 一剑走天下 两樽论春秋 ※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.214.7]
NT5.0 试用报告
发信人: chxliu (chxliu), 信区: NewSoftware
感觉很不错,画面非常漂亮,IIS也升级到了5.0 .而且是全版,什么语言都
有.
唯一的缺陷的对中文支持还是不够好,有些中文无法显示.另外安装过程很
漫长,几乎让我无法忍受.
测试结果:
因为对中文数据库支持有问题,我现在不得不使用.......win98,呵呵.
希望各位高手们放过我们,别老来黑咱们.
现在 NT5.0 已经放到化云坊上,欢迎试试.
发信人: chxliu (chxliu), 信区: NewSoftware
【 在 Jonny (识时务者为俊杰.寻梦中回首) 的大作中提到: 】
: 嘿嘿，我取那东西，让你们服务器不正常了一段时间呢，竟然是 Serv-U
: 的服务器，那东西不理想。
没办法啊，用 IIS 不支持断点续传，而 WardFTP 又存在响应方面的
问题，所以只好用 Serv-U 了。有什么好的解决办法，还请赐教。
Win2K Beta3 在 4.80/incoming
发信人: gloria (深蓝), 信区: NewSoftware
【 在 Jonny (识时务者为俊杰.寻梦中回首) 的大作中提到: 】
: Win2000.Beta3.By.Jonny 目录。
: 是压缩文件，解开后有 8000 多个文件，小心哦。
我昨天装了一个晚上
唯一的感觉就是: 累!
先是我的硬盘几乎要折腾不开
这可能不是M$的毛病, 是作这些东西的大侠们太有耐心了
340M的东西, 先unzip, 再unrar, 最后要cabinet, 前后解三遍
前两遍时间>20m, 最后一遍时间>30m
出来8000多个文件, 我只好边解边删
好不容易开始安装了, 刚开始看到有bootdisk, 以为非要做盘
结果做完四张盘启动后冲俺要CD!(这四张盘启动足有15分钟)
只好放弃软盘, 还是按NT的老方法安装, 装个DOS, 然后winnt
下面的过程与NT4没啥差别, 开始又狂拷一遍文件到硬盘(我一直不能理解NT为啥要这样)
然后启动, 安装时发现我有傻了眼
原来这个东西至少需要630M空间, 而我分给它的900M分区由于临时文件占了300多M不够了
这个分区原来装的NT4 Server, 是肯定够的
只好暂时放弃, 进win98用PM4搬来移去将分区凑成1.9G(再不够我就砸了这鬼东西)
这下倒没问题, 安装时间虽说长点, 除了有些检测程序出了crash外倒没出大问题
安装选项里多了很多东西, 比如smtp server, index server, IIS5, certificate server
感觉好象是要像Linux一样将基本的网络服务都包括进来
我装了一些常用的服务(其实也没啥用, 主要是看看)
最后空间用了大约800M
我不得不痛骂M$简直是硬盘猪
包括这些服务器的Linux装上不会超过300M(要知道Win2000里不包括编译器啊)
起来后看着还比较花梢, 支持的硬件很多(连我的Creative DVD解压卡都能识别)
可是偶然的机会我看了看Task Manager, 哇赛, 用了90多M内存(幸亏俺是128M)
其它用起来感觉还凑合, 不过觉得没啥新东西, 就是NT4+Win98
目前要用中文是个大大的问题, 安装俺看见有Simlified Chinese就是不让人选
能用的中文系统基本上没有(俺的第一步要求很简单, 能看BBS)
最后只好翻出NJWin1.6, 用里面的NJWin for Win3/NT勉强可用
但是屏幕刷新超级之慢, 而且要狂读硬盘, 字还经常有重叠
其它的中文系统基本上连字都出不来
好了, 先写这么多
总之, 微软的东西个个都是垃圾!!!!
这个Win2000 Server除了界面花哨外连给Linux提鞋都不配
发信人: chxliu (chxliu), 信区: NewSoftware
看来 Beta3 对中文的支持还是有问题。原来我们也花了一晚上在装
Beta2 ，感觉还可以，倒不象你说的那么难受，呵呵。不过因为它对中文的
支持存在问题，中文数据库根本打不开，所以最后又放弃了。
【 在 gloria (深蓝) 的大作中提到: 】
: 我昨天装了一个晚上
: 唯一的感觉就是: 累!
: 先是我的硬盘几乎要折腾不开
: 这可能不是M$的毛病, 是作这些东西的大侠们太有耐心了
: 340M的东西, 先unzip, 再unrar, 最后要cabinet, 前后解三遍
: 前两遍时间>20m, 最后一遍时间>30m
: 出来8000多个文件, 我只好边解边删
: 好不容易开始安装了, 刚开始看到有bootdisk, 以为非要做盘
: 结果做完四张盘启动后冲俺要CD!(这四张盘启动足有15分钟)
: 只好放弃软盘, 还是按NT的老方法安装, 装个DOS, 然后winnt
: 下面的过程与NT4没啥差别, 开始又狂拷一遍文件到硬盘(我一直不能理解NT为啥要这样)
: 然后启动, 安装时发现我有傻了眼
: 原来这个东西至少需要630M空间, 而我分给它的900M分区由于临时文件占了300多M不够了
: 这个分区原来装的NT4 Server, 是肯定够的
: 只好暂时放弃, 进win98用PM4搬来移去将分区凑成1.9G(再不够我就砸了这鬼东西)
: 这下倒没问题, 安装时间虽说长点, 除了有些检测程序出了crash外倒没出大问题
: 安装选项里多了很多东西, 比如smtp server, index server, IIS5, certificate server
: 感觉好象是要像Linux一样将基本的网络服务都包括进来
: 我装了一些常用的服务(其实也没啥用, 主要是看看)
: 最后空间用了大约800M
: 我不得不痛骂M$简直是硬盘猪
: 包括这些服务器的Linux装上不会超过300M(要知道Win2000里不包括编译器啊)
: 起来后看着还比较花梢, 支持的硬件很多(连我的Creative DVD解压卡都能识别)
: 可是偶然的机会我看了看Task Manager, 哇赛, 用了90多M内存(幸亏俺是128M)
: 其它用起来感觉还凑合, 不过觉得没啥新东西, 就是NT4+Win98
: 目前要用中文是个大大的问题, 安装俺看见有Simlified Chinese就是不让人选
: 能用的中文系统基本上没有(俺的第一步要求很简单, 能看BBS)
: 最后只好翻出NJWin1.6, 用里面的NJWin for Win3/NT勉强可用
: 但是屏幕刷新超级之慢, 而且要狂读硬盘, 字还经常有重叠
: 其它的中文系统基本上连字都出不来
: 好了, 先写这么多
: 总之, 微软的东西个个都是垃圾!!!!
: 这个Win2000 Server除了界面花哨外连给Linux提鞋都不配
发信人: DanielWJ (daniel), 信区: NewSoftware
haha
This version can use Chinese, and you can download Microsoft PinYin to input
Chinese. Pls go to Control Panel ->regional setting, to set country
And it's not same as NT4 + Win98. It changes a lot.
You'd better use it well, then say it. It so magic product.
【 在 gloria (深蓝) 的大作中提到: 】
: 我昨天装了一个晚上
: 唯一的感觉就是: 累!
: 先是我的硬盘几乎要折腾不开
: 这可能不是M$的毛病, 是作这些东西的大侠们太有耐心了
: 340M的东西, 先unzip, 再unrar, 最后要cabinet, 前后解三遍
: 前两遍时间>20m, 最后一遍时间>30m
: 出来8000多个文件, 我只好边解边删
: 好不容易开始安装了, 刚开始看到有bootdisk, 以为非要做盘
: 结果做完四张盘启动后冲俺要CD!(这四张盘启动足有15分钟)
: 只好放弃软盘, 还是按NT的老方法安装, 装个DOS, 然后winnt
: 下面的过程与NT4没啥差别, 开始又狂拷一遍文件到硬盘(我一直不能理解NT为啥要这样)
: 然后启动, 安装时发现我有傻了眼
: 原来这个东西至少需要630M空间, 而我分给它的900M分区由于临时文件占了300多M不够了
: 这个分区原来装的NT4 Server, 是肯定够的
: 只好暂时放弃, 进win98用PM4搬来移去将分区凑成1.9G(再不够我就砸了这鬼东西)
: 这下倒没问题, 安装时间虽说长点, 除了有些检测程序出了crash外倒没出大问题
: 安装选项里多了很多东西, 比如smtp server, index server, IIS5, certificate server
: 感觉好象是要像Linux一样将基本的网络服务都包括进来
: 我装了一些常用的服务(其实也没啥用, 主要是看看)
: 最后空间用了大约800M
: 我不得不痛骂M$简直是硬盘猪
: 包括这些服务器的Linux装上不会超过300M(要知道Win2000里不包括编译器啊)
: 起来后看着还比较花梢, 支持的硬件很多(连我的Creative DVD解压卡都能识别)
: 可是偶然的机会我看了看Task Manager, 哇赛, 用了90多M内存(幸亏俺是128M)
: 其它用起来感觉还凑合, 不过觉得没啥新东西, 就是NT4+Win98
: 目前要用中文是个大大的问题, 安装俺看见有Simlified Chinese就是不让人选
: 能用的中文系统基本上没有(俺的第一步要求很简单, 能看BBS)
: 最后只好翻出NJWin1.6, 用里面的NJWin for Win3/NT勉强可用
: 但是屏幕刷新超级之慢, 而且要狂读硬盘, 字还经常有重叠
: 其它的中文系统基本上连字都出不来
: 好了, 先写这么多
: 总之, 微软的东西个个都是垃圾!!!!
: 这个Win2000 Server除了界面花哨外连给Linux提鞋都不配
Re: 有谁用过NT5。0BETA2
发信人: boyalone (不笑), 信区: NewSoftware
标 题: Re: 有谁用过NT5。0BETA2
发信站: BBS 水木清华站 (Sun Nov 15 15:03:49 1998)
【 在 waterheart (好人好梦) 的大作中提到: 】
: 有没有可以在里面处理汉字的
--
我用的版本盗的不好
中文部分没盗下来
但我用nt4的也很稳定
具体做法
装完nt5后
在控制面板里将regional settings
中的地区改为China
default language改为simplified chinese
然后会问你很多文件在哪
反正就在nt4和nt5的目录下，耐心的找
就行了
但有一个关于输入法的exe找不到
但我那有一个外挂的输入法（mspyxxx.exe)
装上就可以了
还有一个chxxx.dll不知干吗使，反正没找到
也不碍事
作完以上步骤后
你重启起来发觉外观没变
但连一下bbs试试，汉字终于出来了
richwin nt 不知怎样，不过既然nt5内核
支持chinese倒也不碍事\ /
\ o --> <-- o /
\++++++++++++++++++++++++++++++++++++++++/
两小球何时相撞？
解：
F=Ma
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 166.111.6.32]
win2k vs. linux
发信人: oldfat (我是老肥), 信区: NewSoftware
标 题: Re: 请问什么东西解压.ace，不要winace(null)
发信站: BBS 水木清华站 (Sun Sep 26 18:21:09 1999)
【 在 figer (我) 的大作中提到: 】
: 第一个给我啊，版主，多谢了，上到哪里准备？
: hero 3在win2k下确实能用，而且速度比98下要快，主要是进城的时候
: 一闪而过，没有任何延迟，呵呵，估计是win2k的dma比较好的原因
我有种感觉，win2k是一个划时代的产品，那天和ivan讨论，
他说2000和nt4、98相比就像3.1和95的区别，这个产品
是我用过的ms产品中最稳定、最快、最好用的产品，
真怕ms一统江湖,但是没办法，人家的产品就是好用，
sigh
--
◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎
◎ 哲平： ◎
◎ 『喜欢。喜欢。喜欢。喜欢。 ◎
◎ 喜欢。喜欢。喜欢。喜欢。』 ◎
◎ 你的理子 ◎
◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 210.39.3.50]
发信人: figer (我), 信区: NewSoftware
标 题: Re: 请问什么东西解压.ace，不要winace(null)
发信站: BBS 水木清华站 (Sun Sep 26 18:31:27 1999)
【 在 oldfat (我是老肥) 的大作中提到: 】
: 我有种感觉，win2k是一个划时代的产品，那天和ivan讨论，
: 他说2000和nt4、98相比就像3.1和95的区别，这个产品
: 是我用过的ms产品中最稳定、最快、最好用的产品，
: 真怕ms一统江湖,但是没办法，人家的产品就是好用，
: sigh
是啊，我现在感觉win2k rc2和所有的操作系统（微软的〕绝对是本质
区别，包括它以前的那个win2k build 2114，速度快，极其稳定，
安全性也好，解决了winnt4.0中的好多问题，不知道正式版是什么样子，
不过我认为现在的rc2其实完全能当成正式版卖了，我这些天一直用
各种变态的方法折腾我的win2k rc2，但是它就是不死机，除非你用一个
前台独占的程序（游戏：P〕，否则要象它死确实有点困难，
对于应用程序的优化简直就是极点，office系列一点即入，photoshop5.5
启动只要3秒，这种速度在9x下是不可想象的。而且内存释放的极为干净，
除了今天发现的那个winace，看来微软的赌注压对了，呜呜，什么时候
中国才能有一个象95一样的操作系统，我肯定支持，linux的中文版买了
好多张，实在是失望了。希望我们这一代能出个好的操作系统和m$竞争。
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 166.111.177.131]
发信人: xsz (勇哥~~让心和思想一同腐蚀), 信区: NewSoftware
标 题: Re: 请问什么东西解压.ace，不要winace(null)
发信站: BBS 水木清华站 (Sun Sep 26 19:35:26 1999)
【 在 oldfat (我是老肥) 的大作中提到: 】
: 我有种感觉，win2k是一个划时代的产品，那天和ivan讨论，
: 他说2000和nt4、98相比就像3.1和95的区别，这个产品
: 是我用过的ms产品中最稳定、最快、最好用的产品，
: 真怕ms一统江湖,但是没办法，人家的产品就是好用，
: sigh
呵呵,我也有这种感觉,其实GUI绝对是有优势的,这点不容质疑,关键
是它稳定与否,随着硬件价格的降低,一个定位合适的图形界面绝对会
比字符界面来得招人喜欢,在这我并不否认linux的发展潜力很大,但
如果用它来做个人平台的话总觉得支持太少了,而X的硬件消耗和Win
似乎也是一个量级的东东,并没有绝对优势可言.
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: thermdyn.chemen]
发信人: figer (我), 信区: NewSoftware
标 题: Re: 请问什么东西解压.ace，不要winace(null)
发信站: BBS 水木清华站 (Sun Sep 26 19:48:01 1999)
【 在 xsz (勇哥~~让心和思想一同腐蚀) 的大作中提到: 】
: 呵呵,我也有这种感觉,其实GUI绝对是有优势的,这点不容质疑,关键
: 是它稳定与否,随着硬件价格的降低,一个定位合适的图形界面绝对会
: 比字符界面来得招人喜欢,在这我并不否认linux的发展潜力很大,但
: 如果用它来做个人平台的话总觉得支持太少了,而X的硬件消耗和Win
: 似乎也是一个量级的东东,并没有绝对优势可言.
看来两位版主的意见倒是相同了，我认为linux应该和winnt的server竞争，
而不是和workstatinon竞争，因为不是一个东西，就象拿汽车和馒头对比
一样，没有可比性
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 166.111.177.131]
发信人: xsz (勇哥~~让心和思想一同腐蚀), 信区: NewSoftware
标 题: Re: 请问什么东西解压.ace，不要winace(null)
发信站: BBS 水木清华站 (Sun Sep 26 19:52:14 1999)
【 在 figer (我) 的大作中提到: 】
: 看来两位版主的意见倒是相同了，我认为linux应该和winnt的server竞争，
: 而不是和workstatinon竞争，因为不是一个东西，就象拿汽车和馒头对比
: 一样，没有可比性
就比较性来说当然应该unix和winnt server比较,可是如果linux如果也是
和winnt server比较的话就有点不太公平了,因为linux的发展方向并不是
单纯的服务器环境,它还是更希望能成为一个个人操作平台的吧,否则它也
不会起点那么低了,可以探讨,可以探讨,因为我对linux的认识还在初级阶
段,所以可能有不对的地方,欢迎给我指正:)
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: thermdyn.chemen]
发信人: figer (我), 信区: NewSoftware
标 题: Re: 请问什么东西解压.ace，不要winace(null)
发信站: BBS 水木清华站 (Sun Sep 26 20:17:26 1999)
【 在 xsz (勇哥~~让心和思想一同腐蚀) 的大作中提到: 】
: 就比较性来说当然应该unix和winnt server比较,可是如果linux如果也是
: 和winnt server比较的话就有点不太公平了,因为linux的发展方向并不是
: 单纯的服务器环境,它还是更希望能成为一个个人操作平台的吧,否则它也
: 不会起点那么低了,可以探讨,可以探讨,因为我对linux的认识还在初级阶
: 段,所以可能有不对的地方,欢迎给我指正:)
有道理，不过我并不看好linux的个人平台，因为个人平台需要的是简单实用，
而linux的发展好象有点象mac os我感觉就是技术至上那种东西，
可惜的是没有考虑兼容性的问题，而且闲杂linux的优势我认为是在于网络，
换言之，就是它对网络服务的支持远远比它对现在常用软件的支持好，
我认为这是它发展的一个失误，微软的成功就在于兼容并包，别人的东西好，
我先把你拿过来，最后为我所用，这样才会使自己越来越强大，我用过一段时间
的linux，后来就是因为兼容性问题才不得已回到了ms，不过现在win2k的发展
已经让我很吃惊了，非常成熟的一个作品，没有白白浪费gates的几十亿美元，
看来下一代的操作系统非它莫属了
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 166.111.177.131]
Re: 这些软件还可以用么?
发信人: hwdz (把酒临风), 信区: NewSoftware
标 题: Re: 这些软件还可以用么?
发信站: BBS 水木清华站 (Wed Oct 13 14:14:29 1999)
【 在 truebasic (忙着复习准备考G的小鸭~~焦头烂额) 的大作中提到: 】
从科大转的一篇文章，参考一下吧
超级解霸可以用现在的sthdvd测试版代替
发 表 人：Xing_Yun(星云) 版面名称：WindowsNT[4168]
文章提要：Win 2000尝鲜记
源 发 站：中国科大BBS站(Wed, 13 Oct 1999 08:23:01)
71%
从10.10开始使用Win2000，到现在反映良好，这之间仅出现2次
运行程序执行错误而重起，几次IE Error，关闭之外，不象98下经常死机。
我装了原来Win98下的所有软件，除了Latex找不到DPMI设备无法运行
其他都正常，下面列一下我所用的软件：
Nav 2000 for nt workstation
winzip 7.0 ACDSee 2.41 NJStar 2.1
Calypso 3.0.0.14 Foxmail 3.0 Beta2 Realplayer
Adobe Acrobatreader Photoshop 5.5 Illustrator8.0
Macromedia Dreamweaver Authorware 4.03 Director 7.02
Flash 4.0 Ulead Webrazor 2.0 Edit plus 1.25
NetTerm 2.42a VC 6.0 Maple
Winamp 2.03 Absolute ftp 1.60 Audio Catalyst 2.1
Ghost View 2.65 超级解霸dvd测试版 Net Ants 2.67
Teleport 1.29b1107 Cool edit pro 1.2 Personal Avi editor
Maya 2.5 Softimage 3.8 |extreme 考拉输入法
未测试的为mathematica 4.0,matlab,spss 9.0,
我刚安装完时，C盘占了700多兆，现在是0.99GB，我把系统上的Temp目录
改到D:\temp下（有1G的剩余空间），似乎运行速度会快了点。
现在感到不爽的就一个——网上邻居运行速度慢，其他都感觉非常满意！！！
我的配置是PII 233, 64MBRAM, 10G, 安装的是Win 2K RC 2.
希望过一个月之后，我还是非常满意。 ^_^
--
※ 来源: 中国科大BBS站 [bbs.ustc.edu.cn]
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 210.45.208.1]
win2k下必须的service
发信人: figer (某人), 信区: NewSoftware
标 题: win2k下必须的service
发信站: BBS 水木清华站 (Mon Nov 29 12:19:53 1999)
event log
local disk manager
plug and play
remote procedure call
remote registry service
run as service
security count manager
windows managment instrumentation driver extensions
workstaion
有了这些就可以最小启动了，
我在英文的2183下只启动这些service的时候内存占用是43M
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 166.111.162.131]
Win2k Pro Final ISO
发信人: zzzzzh (来去匆匆), 信区: NewSoftware
标 题: Win2k Pro Final ISO
发信站: BBS 水木清华站 (Sun Dec 19 13:21:16 1999)
预发行版的Win2000 Pro英文版2195实际就是最终发行版，只不过有3个安装文件不同。
其中最关键的是setupreg.hiv，这个好像是个安装流程文件，Time Bomb就在这里，
CDROM和BOOTDISK里各有一个.另外,setupup.ini和eula.txt文件都影响不大。
作天搞了一个Build2195 ISO的补丁，把这3个文件给重写了一下，
放在lib.pku/incoming/Win2kProPatch里面了，原来的ISO还有，有兴趣的可以试试。
我用WinImage展开这3个文件都没问题。
--
自己动手,丰衣足食
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.204.85.6]
关于win2k的几个问题的说明
发信人: oldfat (老肥也), 信区: NewSoftware
标 题: 关于win2k的几个问题的说明
发信站: BBS 水木清华站 (Sun Dec 19 22:08:26 1999)
看来大家有很多问题，就我所知，为了帮主大家更好的
安装好win2k,就几个问题根据我的经验回答如下：
1.硬件配置：
win2k相比起以前的ms操作系统来说，这次的驱动程序是带
的最全的，大部分主流的硬件，在driver.cab中都有驱动
程序，不过有些杂牌的硬件不一定保证。
不过注意一点，由于win2k正式发售日期在2000年2月17日
所以很多硬件产商可能到那时才会出正式的驱动程序，而现在
在driver.cab中所带驱动程序大多是beta版的，只能满足
基本功能要求。像我的sblive，就不支持eax和multi-speaker
根据我的经验，要跑win2k，对你的系统要求最高的不是cpu,
而是内存，p516mmx跑win2k绝对没问题，但内存如果低于
64m，你就最好不要装，否则会很辛苦的。
2.build问题
win2k从开发到成品一共经历了差不多3年，中间经历了很多
过程。windows系列从98开始就引进了build这一区分版本
的概念。比如说，win98 final的build就是1998，98se的
build就是2222，而win2k最后的build是2195（应该是的）
我很奇怪，这一次的build为什么不是2000，不过要注意，
在之前也有个2195,那个版本是以iso的形式放在lib的，
那个版本有444天的限制，而且在屏幕的右下角有
“evaluation version"字样，注意，不要装这个版本。
现在在lib的是没有限制的，请赶快下载。
3.版本问题
win2k一共有4个版本，现在面世的有三个版本，pro,
srv,adsrv,大概过一段时间后，会有个datacenter
server的版。那么对于我们来说，装哪个版本更适合呢？
如果你不开发server/client程序，或者不拿来做网站，
pro就绝对足够了，虽然说现在很多游戏不支持2k,
但我相信，以后的游戏会主要以2k作为游戏平台，
pro就足够能满足大部分人的需求。至于srv,adsrv等
作服务器的版本，对内存需求太大，不装也罢。
4.对中文的支持。
从2k开始，（包括o2k and win2k)，ms使用了unicode
技术，这使到在英文下处理中文变成了现实，大家只需
安装不同语言的字符集即可。具体在win2k下实现的过程
如下，进control panel,选regional setting,先装入
simplified chinese的字符集，然后将所有的默认选项
选成chinese(prc)即可，记得，一定要先装字符集，
否则不能选chinese(prc).
5.对软件的支持
大部分在98/nt4下运行的软件都能在2k下运行，除了些游戏，
因为这些游戏在安装前会判断你的os,因为2k is base on
nt technology,所以游戏的安装程序判断你的操作系统是
nt，就不会继续安装下去，解决方法，你可以在98下装一次，
然后将注册表中改变部分导入到2k下，应该就是没有问题的。
但由于现在部分硬件2k还不支持，像tnt, diamond s90等，
所以就算安装成功，也玩不了。
6.新功能
由于2k是基于nt4基础上的，所以有很多9x下没有的功能，
对那些不熟悉nt4的同志们来说，你最好找几本书看看，
否则会手忙脚乱的，而装一次2k耗时很长，所以不清楚你在
干什么就不要乱干，否则谁后果很严重，尤其是你用了ntfs
格式的话，注意，ntfs有它的优点，也有很大的缺点。
希望大家都能更好的使用2k这一划时代的ms产品，
--
◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎
◎ 哲平： ◎
◎ 『喜欢。喜欢。喜欢。喜欢。 ◎
◎ 喜欢。喜欢。喜欢。喜欢。』 ◎
◎ 你的理子 ◎
◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎◎
※ 来源:·BBS 水木清华站 smth.org·[FROM: 210.39.3.50]
win2kpro下能用的和不能用的软件
发信人: cybergene (活泼的基因), 信区: NewSoftware
标 题: Re: 什么FTP软件能使用WWW的代理？
发信站: BBS 水木清华站 (Mon Dec 6 10:27:09 1999)
【 在 sevenup (方鸿渐) 的大作中提到: 】
: 就象浏览器那样的。
NetAnts
--
Windows: 32 bit extensions and a graphical shell for a 16 bit patch to
an 8 bit operating system originally coded for a 4 bit microprocessor,
written by a 2 bit company, that can't stand 1 bit of competition.
Welcome to DNA Studio: http://dnastudio.dhs.org
new software, navupdate, wallpapers, mp3z, linux, forums......
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.112.85.250]
发信人: xsz (勇哥~~努力!~~奋斗!), 信区: NewSoftware
标 题: Re: 什么FTP软件能使用WWW的代理？
发信站: BBS 水木清华站 (Mon Dec 6 10:27:31 1999)
【 在 sevenup (方鸿渐) 的大作中提到: 】
: 就象浏览器那样的。
估计只有netants,jetcar这样的东东了
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: thermdyn.chemen]
发信人: cybergene (活泼的基因), 信区: NewSoftware
标 题: Re: 什么FTP软件能使用WWW的代理？
发信站: BBS 水木清华站 (Mon Dec 6 10:28:01 1999)
【 在 sevenup (方鸿渐) 的大作中提到: 】
: 就象浏览器那样的。
刚试了一下，Leech也可以。
--
Windows: 32 bit extensions and a graphical shell for a 16 bit patch to
an 8 bit operating system originally coded for a 4 bit microprocessor,
written by a 2 bit company, that can't stand 1 bit of competition.
Welcome to DNA Studio: http://dnastudio.dhs.org
new software, navupdate, wallpapers, mp3z, linux, forums......
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.112.85.250]
发信人: kxn (好好学习！), 信区: NewSoftware
标 题: Re: 什么FTP软件能使用WWW的代理？
发信站: BBS 水木清华站 (Mon Dec 6 12:15:05 1999)
【 在 cybergene (活泼的基因) 的大作中提到: 】
: NetAnts
ReGet 可以
cute 似乎可以, 不敢肯定
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 166.111.163.178]
发信人: heiheihei (嘿嘿嘿), 信区: NewSoftware
标 题: 紫光输入法，faint
发信站: BBS 水木清华站 (Sun Dec 12 09:54:56 1999)
期望挺高，太失望了。
如果你敲一个字母w, 会出现"为"字， 再敲w,会出现"我"，再敲w,又变成了"为"，
莫名其妙！
加了个背景图，倒是挺cool,但是那个输入框却不支持中文，输入汉字是乱码，faint.
NT4+SP4
--
************************************************
牵牵心理热线--http://psyonline.com.cn
我们一直在努力，做中国最专业的心理学网站！
************************************************
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.112.83.182]
发信人: mwgjh (萧秋雨), 信区: NewSoftware
标 题: Re: 紫光输入法，faint
发信站: BBS 水木清华站 (Sun Dec 12 13:42:21 1999)
【 在 heiheihei (嘿嘿嘿) 的大作中提到: 】
: 期望挺高，太失望了。
: 如果你敲一个字母w, 会出现"为"字， 再敲w,会出现"我"，再敲w,又变成了"为"，
: 莫名其妙！
: 加了个背景图，倒是挺cool,但是那个输入框却不支持中文，输入汉字是乱码，faint.
: NT4+SP4
最要命的是敲d的时候，有时候是"的"，有时候是"大"，还有可能是"打"。
不过它的词库比新拼音大多了，我觉得还不错。
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 202.114.208.160]
发信人: stny (Tony), 信区: NewSoftware
标 题: Re: 紫光输入法，faint
发信站: BBS 水木清华站 (Sun Dec 12 16:00:42 1999)
【 在 mwgjh (萧秋雨) 的大作中提到: 】
: 敲第一个d是"的"，紧接着敲第二个d是"大"，再敲第三个d又成了"的"...
: 有这样调整字序的吗？
帮助里是这样解释的：
动态调整字序
紫光拼音输入法对字词输入具有最近输入记忆和联想的能力，使用动态调整字序选
项时，输入法将根据前次输入情况调整候选字词的顺序。
调整的依据是将最可能出现的字优先提供选择。其中对前次输入情况的判断包括了
对字的判断和标点符号的判断。
例如，如果您刚输入了句号，输入“z”时（假设这时使用模糊音设置“z=zh”）
，优先显示的字是“在”；如果您刚刚输入了“筷”，则输入“z”时，将优先提
示“子”。
也就是说，它是上下文相关来动态调整的，而不是根据使用频率来调整的。
--
※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 210.34.11.61]
发信人: CHh5945 (痴), 信区: NewSoftware
标 题: 我的Win2kPro下能用的软件 与 不能用的软件
发信站: BBS 水木清华站 (Mon Dec 20 14:19:31 1999)
Microsoft Windows 2000 Professional Release Candidate 3 中文版下能使用
ACDSee2.42 + 汉化 + 注册 个人认为比3.0小巧好用
Acrobat Reader 4.0 0528 01:01 中文版
Advanced Dialer 2.2 + 汉化 + 注册 2k下用不着了，但可用
CTerm 1999金秋版
DLExpert0.83 很少用但可用
DynaDoc Free Reader 3.50中文版
FoxMail 3.0β2
CnShare 1.0 中国共享软件屏保
CuteFTP 3.5.4 + 汉化 + 注册 等3.5.6的汉化注册
HySnapDX 3.52.00 + 汉化 + 注册
LeapFTP 2.61 + 汉化 + 注册
MagicSet 2.94A for Windows 2000 改注册表的好东东，等2.95 for Win2k
Microsoft Office 2000 (9.0.2812)
Norton Antivirus 2000 for NT 安装前后有些小问题，不影响使用
NetAnts 2.75
NetInfo 3.5 + 注册
Opera 3.60.0.286 + 汉化 + 注册
ReadBOOK 1.21 界面部分英文，不影响使用
RealPlayer Plus 6.0.7.362 就是Plus 7.0
RealJukebox 1.0.0.439
SthSvcd 5.5 1999.3.8 豪杰超级DVD（试用）
UltraEdit 7.00a + 汉化 + 注册
Winamp 2.5e汉化版
WinImage中文版 5.00.5000 + 注册
WinRAR 2.60汉化版 + 注册
WinZip 7.0 SR-1 (1285) + 汉化 + 注册
Microsoft Windows 2000 Professional Release Candidate 3 中文版下不能使用
NetHacker II Beta(测试版)
NetXRay 3.03
Remote Administrator 1.11 个人认为比PcAnywhere小巧、快不少
STerm 0.917 下的 Sniffer 可惜0.918开始Sniffer没了
微软拼音输入法2.0 7M左右的单安装版，有一些问题
大家多提一些吧。
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.114.208.160]
发信人: figer (某人), 信区: NewSoftware
标 题: Re: 我的Win2kPro下能用的软件 与 不能用的软件
发信站: BBS 水木清华站 (Mon Dec 20 14:34:47 1999)
【 在 CHh5945 (痴) 的大作中提到: 】
: Microsoft Windows 2000 Professional Release Candidate 3 中文版下能使用
: ACDSee2.42 + 汉化 + 注册 个人认为比3.0小巧好用
感觉3.0的画面更清晰一些，没有2.x的那种模糊了。
: Acrobat Reader 4.0 0528 01:01 中文版
: Advanced Dialer 2.2 + 汉化 + 注册 2k下用不着了，但可用
: CTerm 1999金秋版
: DLExpert0.83 很少用但可用
: DynaDoc Free Reader 3.50中文版
: FoxMail 3.0β2
: CnShare 1.0 中国共享软件屏保
: CuteFTP 3.5.4 + 汉化 + 注册 等3.5.6的汉化注册
: HySnapDX 3.52.00 + 汉化 + 注册
: LeapFTP 2.61 + 汉化 + 注册
: MagicSet 2.94A for Windows 2000 改注册表的好东东，等2.95 for Win2k
: Microsoft Office 2000 (9.0.2812)
: Norton Antivirus 2000 for NT 安装前后有些小问题，不影响使用
: NetAnts 2.75
: NetInfo 3.5 + 注册
: Opera 3.60.0.286 + 汉化 + 注册
: ReadBOOK 1.21 界面部分英文，不影响使用
: RealPlayer Plus 6.0.7.362 就是Plus 7.0
: RealJukebox 1.0.0.439
: SthSvcd 5.5 1999.3.8 豪杰超级DVD（试用）
: UltraEdit 7.00a + 汉化 + 注册
: Winamp 2.5e汉化版
: WinImage中文版 5.00.5000 + 注册
: WinRAR 2.60汉化版 + 注册
: WinZip 7.0 SR-1 (1285) + 汉化 + 注册
: Microsoft Windows 2000 Professional Release Candidate 3 中文版下不能使用
: NetHacker II Beta(测试版)
: NetXRay 3.03
这个我的用不了，网卡不行:(，每次可以安装，但是没法驱动网卡
: Remote Administrator 1.11 个人认为比PcAnywhere小巧、快不少
: STerm 0.917 下的 Sniffer 可惜0.918开始Sniffer没了
你在2K下能监听？呵呵，好象那个东西不行的，因为2K是NT啊:P
: 微软拼音输入法2.0 7M左右的单安装版，有一些问题
: 大家多提一些吧。
自由拼音3.0 没有任何问题，嘻嘻。
jetcar0.74b 没问题，完全通过
the bat!1.38e 没问题
serv-U 2.5 没问题
hero3 没问题
quake2 没问题
game expert 没问题（好容易找了一个可以在2K下改游戏的东西）
winace1.0 没问题
wincmd 4.01 没问题
大家把自己用的写出来就可以了，呵呵。不过我的一般不用汉化的，
因为汉化the bat!136之后就发现注册码失效了，呵呵，而且
用的习惯了，都知道怎么用了，用不用汉化都可以。
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.162.3]
发信人: CHh5945 (痴), 信区: NewSoftware
标 题: Re: 我的Win2kPro下能用的软件 与 不能用的软件
发信站: BBS 水木清华站 (Mon Dec 20 14:46:55 1999)
figer兄没看清呀。
NetXRay 3.03和Sniffer都是不行的。
补充：
Serv-U 2.5a、2.5b都可以。
SthVcd 5.5 + 十全大补不行。
【 在 figer (某人) 的大作中提到: 】
: 感觉3.0的画面更清晰一些，没有2.x的那种模糊了。
: 这个我的用不了，网卡不行:(，每次可以安装，但是没法驱动网卡
: 你在2K下能监听？呵呵，好象那个东西不行的，因为2K是NT啊:P
: 自由拼音3.0 没有任何问题，嘻嘻。
: jetcar0.74b 没问题，完全通过
: the bat!1.38e 没问题
: serv-U 2.5 没问题
: hero3 没问题
: quake2 没问题
: game expert 没问题（好容易找了一个可以在2K下改游戏的东西）
: winace1.0 没问题
: wincmd 4.01 没问题
: 大家把自己用的写出来就可以了，呵呵。不过我的一般不用汉化的，
: 因为汉化the bat!136之后就发现注册码失效了，呵呵，而且
: 用的习惯了，都知道怎么用了，用不用汉化都可以。
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.114.208.160]
发信人: chenccc (chenxian), 信区: NewSoftware
标 题: Re: 我的Win2kPro下能用的软件 与 不能用的软件
发信站: BBS 水木清华站 (Tue Dec 21 16:08:47 1999)
【 在 CHh5945 (痴) 的大作中提到: 】
: Microsoft Windows 2000 Professional Release Candidate 3 中文版下能使用
: ACDSee2.42 + 汉化 + 注册 个人认为比3.0小巧好用
: Microsoft Office 2000 (9.0.2812)
^^^^^中文Office97能不能用？不想用O2k的说
: Norton Antivirus 2000 for NT 安装前后有些小问题，不影响使用
: NetAnts 2.75
: NetInfo 3.5 + 注册
: Opera 3.60.0.286 + 汉化 + 注册
: ReadBOOK 1.21 界面部分英文，不影响使用
: RealPlayer Plus 6.0.7.362 就是Plus 7.0
: RealJukebox 1.0.0.439
: SthSvcd 5.5 1999.3.8 豪杰超级DVD（试用）
: UltraEdit 7.00a + 汉化 + 注册
: Winamp 2.5e汉化版
: WinImage中文版 5.00.5000 + 注册
: WinRAR 2.60汉化版 + 注册
: WinZip 7.0 SR-1 (1285) + 汉化 + 注册
: Microsoft Windows 2000 Professional Release Candidate 3 中文版下不能使用
: NetHacker II Beta(测试版)
: NetXRay 3.03
: Remote Administrator 1.11 个人认为比PcAnywhere小巧、快不少
: STerm 0.917 下的 Sniffer 可惜0.918开始Sniffer没了
: 微软拼音输入法2.0 7M左右的单安装版，有一些问题
: 大家多提一些吧。
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.38.207.123]
发信人: Atlas (觉今是而昨非), 信区: NewSoftware
标 题: Re: 我的Win2kPro下能用的软件 与 不能用的软件
发信站: BBS 水木清华站 (Tue Dec 21 21:01:16 1999)
NO PROBLEM.
I use it now.
【 在 chenccc (chenxian) 的大作中提到: 】
: ^^^^^中文Office97能不能用？不想用O2k的说
--
栋宇存而弗毁兮，
形神逝其焉如。
※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.144.48]
发信人: yuanjingli (环顾四方), 信区: NewSoftware
标 题: Re: 我的Win2kPro下能用的软件 与 不能用的软件
发信站: BBS 水木清华站 (Tue Dec 21 22:48:53 1999)
为什么不用，比office97好用的多,例如，有12次copy&paste
【 在 chenccc (chenxian) 的大作中提到: 】
: ^^^^^中文Office97能不能用？不想用O2k的说
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.52.95]
win2k adv srv使用印象
发信人: figer (某人), 信区: NewSoftware 标 题: win2k adv srv使用印象 发信站: BBS 水木清华站 (Mon Jan 3 21:56:24 2000) 自从11月花了两周时间下载了WIN2000 Adv.Srv(RC3.2183)后, 我的主操作系统就改成了WIN2K. PS: 现在谁在-CD市场上可以找到RC2以后的版本吗? 据我所知, -CD中一般都是不能再烂的Beta3(213x). 另外现在已有了RC3.2195 了, 但我也懒得再去下了, 2183已经很稳定, 驱动程序至少对我 来说也已足够, 直接用着2183等正式版吧---除非再发现哪个版本 有什么重大突破. 安装程序330M, 从南平下载, 因为种种原因, 共花了我30多小时, 前后两周时间才下下来. 一安装, 居然还失败了, 真要把我给气疯掉. 跑到新闻组上去问, 才知道HIVESYS.INF确实是有问题. 更新之后再装, 一切顺利. 虽然是英文版, 但对中文的支持真是 没得说---除了操作系统界面是英文的外, 一切中文软件和中文内容全部 正常. 很多人说起W2K, 重头都是在冬眠, TS/TSC和华丽的界面, 操作等方面, 但我因职业触觉, 首先注意到的则是它的网络管理. W2K仍然有域控制器(DC)的概念, 但和NT4整合得好象就不是很紧密. 在 W2K的服务器上, 我不能用W2K的工具来管理域, 却得用NT4的Server Tools 来做这些工作. 不知是我没做对, 还是W2K确实如此? 在W2K的网络管理中, 我认为最有意义的一个方面是W2K引入了象Novell的 NDS一样的目录树概念: Active Directory, 可以把整个网络中的共享目录 集中管理. 相对于它的重要对手--NOVELL来说, 这方面终于不再逊色. 在我的目光中, 最有意义的第二个方面就是Quota了. 这也一直是NT网络 最重要的缺陷之一, 现在在NT5中也终于得到了弥补. 第三个方面自然就是大家都很感兴趣的TS/TSC了, 象UNIX的X终端, NT揖都可以利用服务 器? 大的处理器和海量内存来进行工作, 使终端的成本得以最大限度的降低, 从来都是网络的重要方面. 经过无盘95 的风风雨雨之后, 我本已对共享应用程序这个模式非常失望. 但TS的出现, 使我也再次关注共享--服务器端运行. 虽然向来保守的我现在对TS最看好的 方面主要还是在远程管理. 但我也认为通过对它的熟悉掌握, 通过应用程序 厂商对它的进一步支持, 它的前途不可限量---可能因此改变NT现有的一切 网络工作模式. 最后一个不得不讲的方面应该是冬眠了, 虽然我从不认为这对服务器有 什么实质上的意义, 但W2K毕竟也是包含了工作站版本的. 由于W2K不象W98, 很少会需要重启, 而冬眠不但能缩短70%以上的启动时间, 更加可以保存关 正常. 软件也都可以在W2K下用. 象我用的OFFICE97/2K, FOXMAIL, AGENT(一个著名 的新闻组阅读软件), NJWIN, MS-PROXY CLIENT等都运行正常. 而运行不正常 的软件却只发现有RICHVIEW和NW client32. 最后, 也应该说是真正的缺点恐怕还是我前面提到过的: 与NT4整合得不够 紧密. 不管怎么说, 在NT5下不能通过NT4域管理方式来管理NT4的域, 都应该 算是一个严重的错误. 这将导致许多用户升级困难. 只是不知道这是不是我还 没有掌握W2K的管理方式才有这样的看法. 说来可笑, 我说的W2K的缺点时似乎都是在为它歌功诵德. 其实, NW的高效 率文件打印服务, UNIX的许多方面都是W2K望尘莫及的. 但我这里主要是把它 和W9x/NT在相比较. 应该可以说: 相对于9x/NT来说, W2K确实是很好的东西, 除非是P5级CPU与32M以下内存的组合, 否则我就推荐W2K. 一直以来, 我都自称"反M$阵营中的坚定分子", 可是各种不可抗拒因素使我 在事实上却越来越倒向微软的怀抱了. 可贺乎? 可怜乎? -!- 不敢再称 -- ※ 修改:·jpg 於 Jan 4 08:36:28 修改本文·[FROM: argo.zsu.edu.cn] ※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.162.3]
WIN2000安装前/后应该做的几件事
发信人: figer (某人), 信区: NewSoftware 标 题: WIN2000安装前/后应该做的几件事 发信站: BBS 水木清华站 (Mon Jan 3 21:58:33 2000) 最近本组讨论WIN2K的文章非常多（废话，W2K组嘛），不过有 很大一部分问题是重复的，或是具有类似的解决方法，尤其是关于安 装和初始设置。所以我想把这些问题集中起来放在一起，在万千的网 站上也会存放一份，希望有安装上的问题的朋友能先浏览一下，看看 你的问题是不是已经有解决办法了，如果没有再问不迟。为了不使这 篇文章太罗嗦，我不会写得太详细，而有很多的问题只是提一下解决 方法，具体步骤可以参考组内/网站上的WIN2000区文章。另外，这 里只谈PRO版，且以RC3为例。不过其它版本不会差太远。 文中提到的其它文档，都可以在组里面的老贴中找到，或到这里 看看： http://www.webking.com.cn/goodnews/syssoft/windows2000/index.htm 本文主要目的是为不太熟悉WIN2K的朋友作个介绍与指南，如果 您很熟悉W2K，当然也欢迎您来信或把您的经验/技巧/意见发到组 上，我将视情况定期整理。请寄Su99 安装前应做的事 1、想想，值得装W2K么？ 要看干什么了。如果一般用来上网，写文章，搞开发，那么 WIN2000很适合，它的稳定性是9X无法相比的。如果主要玩游戏， 那么还是考虑WIN9X吧。当然你也可以装9X/2000双启动，但请一定 安在不同的分区，否则会有很多麻烦。 2、我的机器跑得动W2K么？ 最好是PII/CELERON级的CPU，MMX200左右也差不太多，最重要 是内存大。64M是基本，128M就很舒服了。如果只有32M，千万不要 装，会死人的 :-) 服务器版就更恐怖了，一般不要考虑。 另外是硬盘。准备用来装W2K的那个分区请至少留1G的空间。 怎么会这么大？算算吧： ..刚安好的winnt+program files+documents and setting三个 目录共=600M ..交换文件pagefile.sys大概100M（会变化） ..如果用冬眠，还要一个和内存大小相同的hiberfil.sys 加起来就已经800M了，总要为以后留点空间吧。所以1G是最基 本的。 3、升级主板BIOS 这一步差不多是最重要的，有很多问题都是由它引起的。如果不 升级到最新的BIOS，有可能会安装失败，就算成功也可能无法使用 最新的ACPI支持，还可能有其它一些小问题。以下列出了几种笔者 见过的，非升级不可的板子： ..华硕P2L97：1008会造成COM口不认，1009就OK ..华硕P2B/P2B-F：1010以前的可能会造成COM口问题， 1010/1011没问题 ..GIGA 6ZXC/6BXC：1.0的BIOS会造成安装兰屏，如果用F7跳 过则无法使用ACPI。升级到1.3一切搞定 当然还有其它很多，无法列举。最近组上在征集各种主板对ACPI 和电源管理的情况，等积累到一定数量可能会列个表出来。 总之要记得，一定要先升级BIOS再安装，否则，就算安装好后 再升级，也可能无法开启一些功能。 4、准备驱动程序 W2K的驱动程序采用了WDM规范，和NT/9X都有点不一样，所以， 如果2000无法正确识别你的硬件，而你又没有厂家提供的WIN2K专 用驱动的话，一般来说就没指望在W2K下用它了。有很少的硬件可以 使用NT4的驱动程序来安装。 不过也不用太担心，只要是比较大路的货色，象S3，TRIDENT， MATROX之类的显卡，ESS，CRYSTAL的声卡，NE2000兼容网卡，PCI 网卡，一般都不会有任何问题。出问题的一般是特别新的显卡和特别 好的声卡。如果装不上可以试一下NT的驱动。相信随着W2K的普及， 厂家会逐渐开始提供W2K驱动。到网上找找。 5、开始安装 首先建议你把文件复制到硬盘再安装。W2K有几千个小文件，会 造成光驱光头的频繁定位而降低速度、增加磨损。如果硬盘空间不紧 张的话，就把安装目录留着吧，免得到时候放光盘。 你的W2K安装盘应该有一个I386目录，有两个文件可以开始安 装：winnt.exe和winnt32.exe。前者用于DOS下的安装，后者用于 从已有的WINDOWS升级。不过，现在流行的RC1/2/3虽然可以从中文 9X（SE2222A不行）下开始安装，但不能升级，而是安装成双启动。 如果从DOS下安装，请一定先加载SMARTDRV，否则你会后悔的。 WIN2K完全支持FAT/FAT32/NTFS。所以，如果你用9X/2000双启 动的话，完全可以把所有分区转成FAT32。 安装后应该做的事 1、改注册表 不会吧，一来就改注册表。其实这一步不必要，但是改了之后有 个好处，就是以后安装组件/驱动程序不会要你插光盘，而是直接进 行。如果你根本没有光盘的话，最好进行这一步，否则一些程序如 SFC（系统文件修复）只会让你插光盘，根本不给你选目录的机会。 前提是你把安装程序留在硬盘上。 我们假设你是从c:\w2k\i386开始安装的，现在进入注册表编辑 器regedit，前往： HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup 会看到右边后三个都是跟目录有关的设置。哪怕你是从C盘安装 的，W2K也会自作聪明地把它们设为光盘的相应目录(真不知道它怎 么想的），比如f:\w2k\i386（假设F是光驱）。现在把它们全部改回 来。其中有一个是用的UNICODE，每个英文占两个字节，不用怕，小 心点，只需要把F改成C即可，不用动其它的。 改好就行了，包括下一步的中文支持安装都不会再提任何“盘在 哪里”的傻问题。 改注册表还可以打开《WIN NT/2000命令行隐藏设置》，允许使 用TAB键进行命令行的目录/文件名补全。 2、安装中文支持 这一步很重要，所以专门写了一篇《WIN2K的中文支持》，里面 对安装智能ABC/五笔有详细的叙述，就不在这里罗嗦了。总之W2K 的中文支持是很好的。 3、设置电源管理 W2K的电源管理是一个亮点，包括让电脑向家电“即开即用”方 向迈近一大步的“冬眠”，所以也专门在《WIN2K的电源管理简介》 中有详述。 4、关掉调试器Dr. Watson 运行drwtsn32，把除了visual notification之外的全都去掉。 否则一旦有程序出错，硬盘会响很久，而且会占用很多空间 如果你以前遇到过这种情况，请查找user.dmp文件并删掉，可 能会省掉几十M的空间。这是出错程序的现场，对我们没用。 关于Dr. Watson的问题，在《关于DR WATSON》中有叙述。 5、删掉不需要的组件 WIN2K的添加/删除程序看不到写字板/画图这些东西。按照《在 WIN2000中删掉不需要的组件》中的办法，可以控制这些组件的去留。 6、拨号上网 请看星矢写的《win2000设置internet拨号上网》，有详细的步骤。 另外有一个极短的《WIN2000 ICS（INTERNET连接共享）介绍》。 7、如果崩溃 如果崩溃了，请你一定试一下Recovery Console，在《RECOVERY CONSOLE介绍》中有叙述。这个功能还很不完善，可能不会 有很大的意义 8、其它问题 诸如某种具体硬件的兼容性，双启动等问题，请参考《WIN2000 常见问答》 整理：su99 (su99@webking.com.cn) 供稿人：万千WIN2000组 -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.162.3]
Microsoft 许可协议——供Win2kPro预发行代码
发信人: CHh5945 (痴痴), 信区: NewSoftware 标 题: Microsoft 许可协议——供Win2kPro预发行代码 发信站: BBS 水木清华站 (Fri Feb 18 19:02:27 2000) 这是一份您（个人或单一实体），作为最终用户（“受 方”），与 Microsoft Corporation（“Microsoft”） 之间的法律协议。您一旦安装、复制或以其它方式使 用（如下所述）本软件，即表示您同意接收这份 Microsoft 许可协议和保密协议。如果您不同意本协议 中的条款，请不要安装、复制或使用本软件。 Microsoft 许可协议 供 Microsoft Windows 2000 Professional 预发行代码 1． 许可证的授予。 （a） Microsoft 授予 “受方”一份有限的、非独家 的、不可转让的、无版税的许可证，在您处的最多数目 至五（5）台的 CPU 上安装和使用随附本协议的软 件(“产品")，仅供您内部测试之用。Microsoft 保留 一切其它权利。受方不得出租、租赁、出售、分许可、 转让或以其他方式转移本产品或任何随附的印刷材 料（“文件”）。受方不得对产品进行反向工程和反向 编译，但如果当地适用法律明示禁止前述限制，则不在 此限。受方不得将本产品用于实际操作环境中，要求本 产品在该环境中具有与商业发行的产品一样的性能远 行，或者在数据没有充分备份的情况下使用。受方不得 将本产品用于基准或性能测试。Microsoft 及其供应商 将保留本产品的所有权和一切产权，除本协议明文规定 外，本协议不得被视为转移本产品或其内含的特征或资 料的任何所有权或许可权。 （b） 当 Microsoft 要求时，受方同意向 Microsoft 提供合理的反馈，包括但不限于有关本产品的测试的使 用性、故障汇报及测试结果。另外，如果 Microsoft 要 求时，受方将作合理的努力查阅和注释一切所提供的文 件。受方提供的所有的故障汇报、测试结果及其它反馈 均为 Microsoft 所有并可以由 Microsoft 自行决定其 用途。由于开发工作的性质，Microsoft 不能确定本产 品的错误或差异何时可以得到解决。 （c） 受方对产品的使用仅限于受方之处。在未获得 Microsoft 书面同意的情况下，受方不得将产品向第 三方演示或展示。 （d）本“产品”可能包含 Windows NetMeeting 这种使 应用程序即使只安装在其中一台计算机上也能够在两台 或多台计算机上共享的技术。您可以结合 Microsoft 所 有的应用程序产品使用此项技术（根据上述 1(a) 节的允 许），以用于召开多方会议。至于非 Microsoft 应用程 序的共享情况，受方应该参阅随附的许可协议或与许可证 发行方联系以确定许可证发行方是否允许共享其应用程 序。 2．协议期限。本协议期限自接受复制, 安装和使用本产 品之日开始至 Microsoft 在任何时间给受方书面终止为 止，无论有无起因本协议在 Microsoft 为本产品进行商 业发行时无需通知而终止。在本协议终止后，受方应停 止使用本产品，并且在要求时，立即将所有全部或部分本 产品副本及 Microsoft 提供的有关材料退还 Microsoft 或证明其已被销毁。 3．支持。Microsoft 没有义务为本产品提供技术支持或 其他支持。但是，有限的技术支持如果在 Microsoft 提 供给受方的材料中提及，则可能提供这类的支持，支持 的使用受“联机”文档和/或其他 Microsoft 提供的材料 中所述的各项 Microsoft 政策和计划的制约。作为支持 的一部分而提供给受方的任何附加软件代码应被视为本产 品的一部分，并受本协议中的各项条款和条件约束。至 于受方作为支持的一部分而提供给 Microsoft 的技术资 料，Microsoft 可将该资料用于其商业用途，包括产品 支持和开发。Microsoft 在使用该技术资料时不会以个 人形式提及受方。该有限支持可能不会在美国境外的所 有国家（地区）提供，并且将在本产品开始商业发行后 中止。 4．产品维护。Microsoft 没有义务为本协议项下所授予 的产品向受方提供维护、技术支持或更新版本。无论在 任何情况下 Microsoft 都没有义务因受方参加测试计划 而免费为受方提供本产品的一份商业发行版本。 Microsoft 没有义务对本产品进行商业发行。 5．保证否认。在适用法律所允许的最大范围内， Microsoft 及其供应商以“即此”形式包含其中所有错 误并没有任何种保证的形式提供本产品及其（如果有的 话）支持服务。在适用法律所允许的最大范围内， Microsoft 进一步否认任何明示的或暗示的担保（如果 有的话），包括但不限于适销性、适用性、无病毒、响 应的准确性和完整性、疏忽或工作质量问题造成的问题、 所有有关本产品以及提供或未能提供支持服务并且不保 障宁静使用、符合描述、无侵权的行为的默认保证。有 关使用或运行本产品和文件的所有风险由受方承担。 6．无意外、因果性和某些其它损失责任。在适用法律 所允许的最大范围内，在任何情况下，Microsoft 或 其供应商绝不就因使用或不能使用本产品或提供或未能 提供支持服务或提供或不能提供协议其它条款所引起的 任何特别的、意外的、间接的或因果性损害（包括，但 不限于营业利益损失、营业中断、人身伤害、隐私暴露、 无法履行任何义务包括名誉或合理义务、营业信息遗失、 金钱上的或其他任何损失）承担赔偿责任，即使是由于 Microsoft 及其提供商出错、疏忽（包括大意）、有限 责任、违反合同和违反担保时均不负责，即使 Microsoft 事先被告知该损害发生的可能性。 7．有限责任和补偿。无论发生的损失是由于什么原因 造成（包括但不局限于以上所述所有损失以及一切直 接的或一般性的损失），Microsoft 及其任何提供商 在这份协议下的全部责任以及您所有的赔偿将局限于 您所支付的产品价格或五美元。上述排除和限制否认 书在相关法律允许的范围内生效，即使赔偿并未达到 原有意义。 8.管辖法律；律师费用。本协议受华盛顿州法管辖并且 受方同意接收华盛顿州的州级和联邦级法院管辖。受方 自动放弃缺乏法律保护和地点不方便的保护辞。如相关 法律或法院规定允许，开庭费可能由任何一方支付。如 果 Microsoft 或受方聘用律师执行任何本协议项下授 予的或有关的权利，那么胜方应有权收回合理的律师 费用。 9．出口限制。受方确认就本产品和文件而言，不会将 其直接或间接地出口或转口于（i）任何受美国出口限 制的国家（目前包括但不一定限于古巴、苏丹、伊朗、 伊拉克、利比亚、朝鲜和叙利亚）以及这些国家（地 区）的国民无论居住在世界何地计划将本产品和文件 传输或运送回这些国家（地区）内；（ii）任何受方 知道或应知道会将本产品用于设计、开发或生产核、 化工或生物类的武器的任何个人或实体，或（iii）任 何被美国的任何联邦机构禁止参于美国出口交易项目 的任何个人或实体。 如果您就本协议有任何疑问，或如果您因任何原因想与 Microsoft 接洽，请写信给：Microsoft Corporation, WWPG Beta Team,One Microsoft Way, Redmond, WA 98052-6399。 -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.114.208.160]
win2k_SC零售版本特征
发信人: jobss (Ning Ge), 信区: NewSoftware
标 题: win2k_SC零售版本特征
发信站: BBS 水木清华站 (Mon Mar 13 19:49:56 2000)
2000-01-10 版本号是2195.1 or 2195.3
点setup.exe按鼠标右键--->属性,可以知道版本号.
xixi..
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.112.169.6]
关于windows 2000的答问，不可不看！！！(oldfat)
发信人: kouzh (寇仲【少泡网，练刀法，破天魔】), 信区: NewSoftware
标 题: 关于windows 2000的答问，不可不看！！！(oldfat)
发信站: BBS 水木清华站 (Sat Mar 18 01:28:56 2000)
作者: 主题: 关于windows 2000的答问，不可不看！！！
oldfat
成员
Posts: 9
Registered: Mar 2000 发表于 03-18-2000 12:22 AM
本来我不打算写这篇文章的，但实在是气愤不过某些人的言语，就写下这篇
一点综述吧。
本篇文章里面的内容主要来自于以下网址： http://corob.net/win2000/ ，
英语好的朋友请直接访问。我只不过是将部分内容翻译成中文并加上自己
的体会而已（括号内的内容）。
问：我应该使用哪个版本的windows 2000?
答：Build 2195是windows 2000的最终版本号（最终Build）。2195是在
1999年12月15日发布的最终版本RTM（Release To Manufacturing，也就
是制造版本。微软这次除了用年份、build命名版本号之外，还多了个新
名次－－－RTM，具体情况请参看
http://www.microsoft.com/presspass/press/1999/Dec99/W2KrtmPR.asp）。
问：2195.3是什么？是最终版本吗？
答：错！根本就不存在2195.3，只有2195。但是2195有两个版本，一个是
有120天时间限制的试用版，另外一个是没有时间限制的版本。这两个版本
都是最终版本。
（oldfat注1：2195就是最终的build号，根本就不存在什么2195.3。英文版
的windows 2000最终版是1999-12-15就出来了，没有几天，CORE就Release
了硬盘版和ISO版，这是最早出现的warez版的windows 2000。没有几天，
某个组织release了所谓的2195.3，结果马上就被nuked掉了。又过了几天
PWA release了OEM版，在他们的NFO中讲到：“恭喜CORE，因为他们是最早
Release正式版的windows 2000。微软在Release最终版时，一共出了两个
版本，一个是没有时间限制的，一个是有120天时间限制的。而那个没有时间
限制的版本，保密性极高，一般的微软职员都没权使用，只能使用120天限制
版的。”所以PWA就比CORE晚了几天才release。）
（注2：我不相信微软同一个产品的build是不一样的，不可能说英文版的是
2195，而中文版是2196，这个根本不可能。中文版只是将英文版所有英文版
的东西汉化成中文版的，内核没有任何区别，所以build号也应该一样）。
问：如何辨别我的windows 2000是否有时间限制？
答：运行“winver"（开始-->运行，然后输入winver）。在"Copyright (C)
1981-1999 Microsoft Corp." （这是英文版的提示，中文版应该是“版权
所有（C） 1981－1999 Microsoft Corp”）下面有"Evaluation copy.
Expires ," （“评估版本，将于<某天后到期>”）
之类的字样。
问：很不幸，我装得是有时间限制的版本，我该怎么办？
答：唯一的解决方法就是重新安装没有时间限制的版本，除此之外，没有任何
解决方案。
问：那我从哪能够得到没有限制的版本？难道我要重新全部DOWN过？
答：很高兴告诉你，你不用那样做。实际上，有120天时间限制的版本和没有时间
限制的版本只有一个文件是不同的－－－－在i386目录下的setupreg.hiv，你只需
将没有时间限制的版本中的那个文件覆盖掉有时间限制的就行了。另外，你可以
通过http://corob.net/win2000/setupreg.asp 上面所说的方法手动修改该文件
也可以达到同样的目的。
问：怎样去处掉安装过程中需要输入注册号这个过程？
答：打开i386目录下的setupp.ini，将PID后面的数字改成51873270，那么在
整个安装过程中就不会再问你输入序列号了。
问：怎么做windows 2000启动光盘？
答：你可以参照http://corob.net/win2000/bootcd.asp 上面所说的方法进行
制作。
（oldfat注：windows 2000的原版光盘是可以直接启动安装的，这样既省掉了
要预先分区的这个步骤，其次，用启动光盘安装windows 2000要比从硬盘安装
少启动机器一次。）
oldfat: 我记得好像《软件》杂志第三期随刊附送windows 2000简体中文版最终
测试版，我估计就是有时间限制的2195，不知那个无量D版商将这个版本做成D
版，然后冒充正式版的windows 2000简体中文版。
注1：多谢EFNET中win2000中的朋友们！！！
注2：虽然MS说要到3月20日才正是发售windows 2000简体中文版，但实际上，
连邦和中赫早在13号就到货了，所以很多人就买了。我的一个朋友刚好久买了
一套professional的，1999元，我看过，的确是2195。
注3：guest，请你说话文明点，不要出口伤人。我很不like你这种说话方式，
而且你好像不懂装懂，自以为是。希望你注意点，不过没有你，我也不会浪费
时间来写这篇帖子。主啊！饶恕这些无知的人吧。
--
就让它尘归尘，
土归土，
网络归网络，
现实归现实吧。
飞吧，自我
※ 来源:·BBS 水木清华站 smth.org·[FROM: 162.105.39.231]
Whislter 2267使用感受（一）
发信人: CHh5945 (痴痴), 信区: NewSoftware
标 题: Whislter 2267使用感受（一）
发信站: BBS 水木清华站 (Tue Oct 31 07:49:08 2000)
发信人: sq (写Whislter使用感受中……), 信区: NewSoftware WWW-POST
标 题: Whislter 2267使用感受（一）
发信站: 武汉白云黄鹤站 (Mon Oct 30 14:17:19 2000) , 站内信件
周末抽空把Whislter Pro 2267从蓝皮鼠上拉了下来,装上后用了几天。从这
几天的使用感受来看，whislter确实算的上一个架构相当成熟的操作系统了， 一
些试用感受，不吐不快。本想写成FAQ形式，但自己也刚刚用了没有几天，所以还
是从安装开始，结合自己遇到的问题写一下了。
我一共在两套不同的配置上安装了Whislter，分别耗时35分钟和50分钟。
第一套配置：C333 oc C665（133×5，2.2v）
TNT2标准版/16MB （核心125 oc 155 ; 显存150 oc 175）
IBM 30G＋WD 6.4G （均为2M缓存，WD为5400转）
MSI 6199NA主板
128MB×2 KingMax
……
……
第二套配置：C366 oc C550 (100×5.5 ，2.0v)
Permedia2 /8MB SGRAM
酷鱼II 13.6G
杂牌VIA 133A
64MB KingMax
……
……
硬盘全部采用NTFS分为两个区,在C盘上事先安装2K SERVER以及常用软件作对
比参照。将Whislter安装在D盘上。第一套配置中把系统安装在IBM盘上,Whislter
所有的安装文件均放在WD盘上。要说明的是,写出的基本上都是我自己的主观感受
，时间和条件所限，没有跑任何一款测试软件来量化系统的表现,所以态度和观点
可能会失于严谨，请各位多担待了。
--
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.114.208.160]
Whislter 2267使用感受（二）
发信人: CHh5945 (痴痴), 信区: NewSoftware
标 题: Whislter 2267使用感受（二）
发信站: BBS 水木清华站 (Tue Oct 31 07:49:35 2000)
发信人: sq (写Whislter使用感受中……), 信区: NewSoftware WWW-POST
标 题: Whislter 2267使用感受（二）
发信站: 武汉白云黄鹤站 (Mon Oct 30 14:18:50 2000) , 站内信件
整个安装向导可以说是windows 2k安装向导和windows 9X安装向导的结合，整
个安装界面和9X非常相似，同为采用的step by step主题式安装，但是所有的安装
步骤几乎和2K相同。本想采用全新安装，但带有smartdev的9X启动盘不在手头，只
得作罢，所以选择了在2K中安装。
整个安装过程几乎没有什么组件可以定制选择，第一次重启后，安装程序便会
用自带的OS-Loader改写引导区，因为语言版本的冲突,引导菜单中会局部出现乱码
。虽然曾在ChinaByte上看到过Whislter的介绍,但安装完成后，还是被它漂亮的登
录画面所打动。
在256MB的系统上，Whislter的表现应该可以用酣畅淋漓来形容,因为有大容量
内存的保证，运行速度和2K SERVER版没有什么明显的区别.但是有一个有趣的现象
不可不提，在两套内存相差很大的系统中，启动速度几乎相同！！到登录过程完成
，系统不再读盘之后，查看了任务管理器，所耗内存为78MB左右，和2KSERVER的71
MB(默认安装，没有再另行打开获关闭任何附加服务）相差不大,也从侧面证明了运
行速度大致相同。界面比2K又漂亮了很多，尤其是开始菜单可以说是一种全新的体
系，但是我还是喜欢传统的开始菜单，这些都可以在任务栏属性中选择。
--
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.114.208.160]
Whislter 2267使用感受（三）
发信人: CHh5945 (痴痴), 信区: NewSoftware
标 题: Whislter 2267使用感受（三）
发信站: BBS 水木清华站 (Tue Oct 31 07:50:04 2000)
发信人: sq (写Whislter使用感受中……), 信区: NewSoftware WWW-POST
标 题: Whislter 2267使用感受（三）
发信站: 武汉白云黄鹤站 (Mon Oct 30 14:19:37 2000) , 站内信件
就我使用的这两套系统来看，应该说Whislter的硬件兼容性是相当好的，所
有的硬件都可以识别出来，包括一块杂牌内猫和两块不知名的PCI杂牌网卡,并且
使用完全正常！
得益于系统良好的磁盘管理能力,我在2K SERVER中安装的绝大多数软件都可
以直接正常运行,包括Photoshop5.5，3DMAX R2/R3，AutoCAD R14/2000等等。因
为手头没有什么游戏，所以测试游戏的兼容性只得作罢。
虽然系统是英文版本，但是对中文的支持除去我发现的个别现象外，可以用
优秀来评价，要注意的是，想系统能完整的支持中文显示，在安装过程中就设置
好地域和语种是事半功倍的.我到现在唯一发现的不足只有两个：1）当用系统自
带的写字板来编辑中文文档时，字体横向压缩的比较厉害,和在UltraEdit中显示
出的效果差不多。但是当采用其他的中文文档编辑器（如Sunny SmartNote 或者
Dreamedit）后，又会显示出标准的宋体。2）上白云时，无论是直接telnet还是
用Cterm，出来的效果就和没有打开ansi控制一样.如果说上个问题没有什么大碍
的话，这个问题我自己还没有找到行之有效的解决办法。
--
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.114.208.160]
Whislter 2267使用感受（四）
发信人: CHh5945 (痴痴), 信区: NewSoftware
标 题: Whislter 2267使用感受（四）
发信站: BBS 水木清华站 (Tue Oct 31 07:50:32 2000)
发信人: sq (写Whislter使用感受中……), 信区: NewSoftware WWW-POST
标 题: Whislter 2267使用感受（四）
发信站: 武汉白云黄鹤站 (Mon Oct 30 14:20:30 2000) , 站内信件
IE的版本号是5.6，并且还是直接128位加密的，不需要打补丁。不知道到正
式发行时，中文版系统的IE是否还是56位加密.Outlook Express的版本号同样是
5.6，不过没有感受到和5.0/5版的差别在什么地方。IIS没有来得及安装,所以是
否和以前有什么改进，也下不了结论。Web页面的浏览速度和2K持平。
在9X和2K中，活动桌面都是可以选择是否打开的，但是到了Whislter，却没
有了关闭活动桌面的选项，根据经验,活动桌面是要占据8～10MB内存空间的！是
否可以通过修改注册表来关闭活动桌面，我没有去细看，又兴趣的朋友，可以研
究一下。
整个系统的运行效率还是相当高的，在9X和2K设置Cterm属性时都会出现中文
显示不完全的现象，但是在Whislter下就没有这个问题.其他的软件也都运行正常
，只是除了3D MAX R3——渲染速度明显赶不上2K，相信这只是显卡驱动程序的问
题。
连续运行了这几天，系统十分稳定，没有死过机。因为CPU被我超到了665Mhz
的频率，显卡也在88的AGP外频下超负荷运转，应该说整个系统的稳定性还是给我
留下了非常深刻的印象（这块极品C333的CPU我一般都是在112×5，降压到1.8v来
使用的）。不过占用的内存确实太大，那套64MB的系统只能说是可以完成安装.速
度感和使用486/16MB来跑95的感受差不多。128MB是正常运行Whislter的最低要求
经过了这几天的试用，没有发现什么大的BUG，就像我的签名档说的那样，我
被彻底征服了。虽然现在的Whislter还只是在测试阶段,但我还是把原来的系统由
2k Pro＋RH Lniux改便成了Whislter Pro 2267＋RH Linux。
注：还有一点忘记说了，2250和2257我不知道，但是2267有使用时间的上限限制，
我把系统时钟调到2000年2月份时，居然拒绝安装，faint。
--
--
※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.114.208.160]
Office2K3B2五笔解决方法（不知old否）
发信人: sd2345678 (caniggia), 信区: Lesbian
发信人: cygwin (人生如梦), 信区: NewSoftware
标 题: Re: Office2K3B2五笔解决方法（不知old否）
发信站: BBS 水木清华站 (Sat Jul 12 00:10:42 2003), 转信
用86版。
chinese版很多人都说受害了
我也用过一段98
后来又改回86了
【 在 bigfatcat (http://huzhenghui.51.net/) 的大作中提到: 】
: 为什么不要用？
__..
.' /__
-- . __ ..`..'-.'
\.-.-..-' '---._.---' a `-'|
`-' ( . .'
` ) `. `-'
\ . . .'
`. . : .'
`. )"""--""\ |/ \
| / \\ : ( `\\
_/ ^ \_\ ^
※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.168.186]
Windows XP SP2 build 1224 download
发信人: fifanwc (国际足联), 信区: NewSoftware 标 题: Windows XP SP2 build 1224 download 发信站: BBS 水木清华站 (Sat Aug 9 03:21:20 2003), 转信 http://www.techconnect.ws/modules.php?name=News&file=article&sid=1849&mode=&order=0&thold=0 Together with xBetas we present to you a new Windows XP Service Pack 2 build 1224. This one has been released yesterday and includes some of the newest fixes from the previous version. Update: just updated the files... Read on for the download... Download Windows XP SP2 build 1224 Note: Not supported by Microsoft! -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.120.224.18]
Longhorn PDC 4051
发信人: pythias00 (Mp3), 信区: NewSoftware 标 题: Longhorn PDC 4051 发信站: BBS 水木清华站 (Sun Oct 26 00:42:56 2003), 转信 Longhorn PDC Build 4051 Includes New Slate Theme Posted by DoubleDoom on 22nd October 2003 05:46 PM - no comments When Longhorn debuts this october 26th at the Professional Developers Conference in LA it will debut with a whole new theme code-named "Slate". The Longhorn PDC build (4051) was decided around two weeks ago. Since then lucky company employees have had the chance to use the OS or take a look at it but are under strict orders not to talk to anyone about the PDC build. Two pictures (which are confirmed to be real) have leaked onto the internet showing the new theme. Although they're not the best pictures they do however highlight the new theme very well. The leakers known as "ABSO1ut3 1nfin!ty & B3y0nD" leaked the well documented 4029 screenshots around 2 months ago. Included in the package is a set of Q and A's making people aware that build 4051 is the PDC build, aero isn't included in the PDC build and will only be demo'd and also that plex is no longer the theme, "slate" has replaced it. Also included is a note to Robert Scoble (http://longhornblogs.com/scobleizer/) documenting how these pictures belong to him. Robert is an MS Employee who has helped manage PDC. According to internal sources at Microsoft the PDC build is "amazing" and very stable. Roll on 26th October -- [XP1800+][ASUS K7V266C][Ramos DDR333 512M][Leadtek Winfast A170 DDR] [LaJi 17'][Logitech USB Wheel Mouse][Logitech keyboard] [Realtek RTL8139][Logitech USB Camera][WDC WD400BB-00DEA0][ST3120022A] [ATAPI CDROM 44X][IOMEGA ZIPCD 4X/4X/24X][刚弄到一块蓝色布垫] ※ 修改:·pythias00 于 Oct 26 00:45:10 修改本文·[FROM: 219.224.187.201] ※ 来源:·BBS 水木清华站 smth.org·[FROM: 219.224.187.201]
Chinese Support for Longhorn 4051(转载)
发信人: stenve (男生), 信区: NewSoftware 标 题: Chinese Support for Longhorn 4051(转载) 发信站: BBS 水木清华站 (Mon Oct 27 22:42:08 2003), 转信 I use Windows XP Pro ENU for many days, so I know how to tune a ENU version of Windows XP into a good Chinese-savvy OS. The same method works in Longhorn now. Steps: 1.Prepare your Longhorn Install medium (Such as CD-ROM) now. 2.Choose Control Panel->Regional and Language Options. 3.Select the 2nd page, Languages, and check (click) the checkbox before "Install files for East Asian languages". Press OK, and OK again :=) 4.While all files are copied, don't restart immediatery, choose Cancel or No. 5.In Regional and Language Options Dialogbox, choose the 3rd page, Advanced. 6.You can see a combobox (the text field with a down arrow:-) saying "English (Un*S*)". Click on the down arrow and choose "Chinese (RPC)" 7.Press OK ,and OK in the popup dialogbox. 8.When Windows tells you to restart, just do it. 9.After a working restart, now Longhorn supports Chinese . -- -- ※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.192.157.41]
Longhorn Tweaks-Build 4051
发信人: pythias00 (Mp3), 信区: NewSoftware 标 题: Longhorn Tweaks-Build 4051 发信站: BBS 水木清华站 (Wed Oct 29 02:26:03 2003), 转信 Changes Over Build 4029 Welcome screen is similar to 4029 but now sports black as the color of choice to match the new Slate theme. The setup routine has been redone for this build and is much nicer than previous builds. New Slate theme included in this build, Plex is gone for good. Carousel view in Hardware and Devices has been removed. New sidebar clock design yet again. Preview pane polished but still somewhat slow. Download manager in Internet Explorer works intermittently (reported by numorous people that it works on and off or not at all) Popup blocker in Internet Explorer improved, works very nicely. New boot screen (Looks a bit weird). Bugs and Known Issues in 4051 Explorer is still leaky with the sidebar on (see below). In Outlook 2003 when you click Personal Folders it displays the html code instead of Outlook Today. Network Browsing is broken by default. See "Repair Longhorns Networking " later on in this guide. Internet Explorer's download manager is flakey. Sometimes it work, sometimes it doesn't. If a menu overlaps the sidebar, it may remove the sidebar gredient from the overlapped area. To fix this, just resize another tile over the missing gredient area and things should return to normal. If Windows Explorer or Internet Explorer lock up, you will get a glimpse of where the original titlebar (from previous windows versions) is in Explorer . Frequently Asked Questions (F.A.Q.) Q: Why is my Longhorn CD not bootable? A: Because the original release was missing its boot record. You will need to obtain a fixed ISO or find a patch to make the CD bootable. Q: Does the memory leak still exist in Explorer? Unfortunatly, it does, but there are two solutions to repair the leak or stop it completely. Read the rest of the guide for more information. Performance Tweaks Here's where the fun begins. This build has a lot to be tweaked to speed it up so here we go! Uninstalling un-needed components: First open SYSOC.INF. You can do this by clicking the Windows flag (Start ), and then clicking Run. Type "notepad C:\WINDOWS\INF\SYSOC.INF" (without the quotes. Then delete all instances of the word HIDE and save. Now navigate to Add/Remove Programs in the Control Panel Go to Add/Remove Windows Components Uninstall the following: %avalon_desc% %mfDesc% %mygames_desc% %sidebar_desc% TabletPCRuntime_desc% oc_biologon Windows File System Services (WinFS) Windows Storage Full-text Index NOTE: There is a leak in the Windows Explorer process when you have the sidebar on. Make absolutely sure you uninstall %avalon_desc% and %sidebar_desc%, this will either stop the leak or slow it down, depends on your system configuration . Disabling Unnecessary Services: Go to Start --> Run and type Services.msc Now set the following services to DISABLED Automatic Updates AvRtSvr Base Firewall Engine Biometric Resource Manager Castle Service Certificate Propogation Computer Data Synchronization Manager Digital ID Management Service Error Reporting Service Font Cache Service FontCacheService Fusion Isolation Service ICF/ICS - Firewall and connection sharing IPSEC Services NS$ShellSubscriptions Offline Files Service Parental Control Auditing Remote Registry Secondary Logon Software Licensing Service SSDP Discovery Service System Maintenance Service System Restore Service Universal Plug and Play Device Host WindowsEventForwardingService WinFSSync Performance Options: Now go to Computer properties --> Advanced Tab, under Performance options click the Settings button. Uncheck the following: Animate Windows when Minimizing and Maximizing Fade or slide menus into view Fade or slide tool tips into view Fade out menu items after clicking Show preview and filters in folders (VERY IMPORTANT) Show shadows under menus Show translucent selection rectangle Slide open combo boxes Slide taskbar buttons Smooth edges of screen fonts Smooth-scroll list boxes Use a background image for each folder type Now open Computer and go to Tools --> Folder Options and click View Tab and uncheck the following: Automatically search for network folders and printers Choose smart icons when opening new windows Display file size information in folder tips Display simple folder view in explorer's folder list Hide extenstions for known file types Use Domain folder sharing wizard Use simple file sharing The Infamous Explorer Memory Leak Everyone remember the explorer.exe memory leak that was present in 4015 and 4029? Well suprise! Its still here! Good news is it can be capped off for good with a few simple steps. Start by disabling the sidebar (right click sidebar --> properties uncheck Enable Sidebar) Go into Computer, go to tools --> Folder Options and check "Run Explorer windows in a seperate process" Right click Computer and go to properties, Advanced tab, under performance hit settings and uncheck "Show preview and filters in folder" Now reboot and there will be no more memory leak. The sidebar has pretty much been turned into a waste of space in this build, and filters are sort of broken in places, so theres no real need to have them turned on. Repair Longhorns Networking In terms of Networking, build 4051 is sort of.. well.. messed up. You may not be able to browse some computers' network shares or even the entire network itself. To fix this, follow the instructions below. Make sure that your workgroup is set the same as all of your other machines . You can change this by clicking the Windows flag (Start), right-clicking on My Computer, and selecting Properties. Click the Computer Name tab, and then click the Change button. Change the workgroup name and press OK. Don 't reboot if asked. Next, you will need to change a setting for the Client for Microsoft Networks . To change this setting, click the Windows flag (Start), and then click Control Panel. Double-click Network Connections. Next, right-click on "Local Area Connection" and click Properties. Select "Client for Microsoft Networks " and then click "Properties". Click the arrow next to the first drop-down box in the Properties dialog and select "Windows Locator". Press OK, and close the Properties window. Restart your computer. After performing the above steps you should be able to browse through network shares and other network related items without any problems. Components Of the Sidebar This is one of the disappointments of build 4051 if you ask me. Microsoft seriously downsized the amount of tiles available, theres only 5 tiles in this build. Clock Tile - The analog clock that we've seen in 4029, although its been redesigned slightly. It looks alot better and now has the "digital time" (EG: 5:23PM) and the date below it. Quick Launch - Displays the items in your Quick Launch. Slightly redesigned , no longer has the names by the items. Classic Tray Tile - Displays the System Tray. Some icons may not appear correctly or at all. You can access them by clicking on the tile itself, which will display a list of the tray icons. (Note: It doesn't seem to refresh well ) Slide Show Tile - display a picture slideshow on the sidebar, cool if you 're bored and need something to stare at. Seems to only display the contents of My Pictures and is not customizable in this build. Sync - Used for file syncronization. Requires WinFS -- [XP1800+][ASUS K7V266C][Ramos DDR333 512M][Leadtek Winfast A170 DDR] [LaJi 17'][Logitech USB Wheel Mouse][Logitech keyboard] [Realtek RTL8139][Logitech USB Camera][WDC WD400BB-00DEA0][ST3120022A] [ATAPI CDROM 44X][IOMEGA ZIPCD 4X/4X/24X][刚弄到一块蓝色布垫] ※ 来源:·BBS 水木清华站 smth.org·[FROM: 219.224.187.201]
Windows Longhorn新特性一览
发信人: pythias00 (Mp3), 信区: NewSoftware 标 题: Windows Longhorn新特性一览 发信站: BBS 水木清华站 (Thu Oct 30 01:57:11 2003), 转信 Windows Longhorn新特性一览 访问次数：4320 Longhorn是微软下一代技术和平台的软件开发代号，这一代软件将包括Windows，Windows Server，.NET和Microsoft Office软件的 新版本。Windows "Longhorn"是下一代主要的Windows桌面操作系统，它很象Windiws XP，但包括了许多新的特性，如：基于任务（或者 智能）的用户界面，可扩展、可停靠的开始面板，和一个基于SQL Server 2003的、被称为WinFS的文件系统。Windows Longhorn也将和 Windows XP一样，将会发布Home版，Professional版，Tablet PC版，MEdia Center版，64位版和其它版本，但这些版本名字如何确定还 没有最终明确。 Windows Longhorn将有哪些新功能？ 1.Windows Longhorn将会倡导基于任务的界面，这个功能将远远超过现在在 Windows XP中见到的界面。这一新的用户界面代码名称 位Aero，是基于被称之为Avalon的、基于.NET的新的API。 2.Windows Longhorn的开始菜单和任务栏将用一个新的Sidebar组件所代替，这个组件可以根据用户的喜好选择是否停靠在桌面的一 边。Sidebar是基于XML 的，可以链接倒本地资源，也可以链接倒远程资源。 3.Windows Longhorn将要求计算机安装具有3D效果的视频硬件展示许多特殊的效果，以使屏幕更栩栩如生。但这并不意味着基本的窗口和鼠标界面将会被取代，而是让它们看上去更美观。 4.Windows Longhorn将可选择地采用微软和Intel，AMD共同开发的Palladium安全技术。 5.Windows Longhorn将采用类似数据库的文件系统，称之为Windows Future Storage (WinFS)，它基于SQL Server2003的技术（代码名字位Yukon）。这种文件系统提取物理文件位置，允许用户进行复杂的数据检索和排序，这在今天是不可能实现的。例如：目前的文件 象电子邮件，联系人，Word文档，音乐文件等都是完全分开的，在Windows Longhorn中将不再是这样。WinFS不是一个全新的文件系统， 而是对NFTS的扩展，它仍然需要NFTS。微软正在努力使我们在日益增长的硬件设备中查找我们所需要的数据更加容易。通过为文件系统增加关系数据库的功能，检索数据和文档将更加迅速。正如微软一位执行官所说疑问的那样：“为什么我们在因特网上找我们想要的东西只需要几秒钟，而在我们自己的机器上却需要花费更多的时间呢？”。除了采用WinFS技术之外，微软还新增加一个文件系统概念：库，它 将象集合那样组织数据，而不管它们系统中的实际物理存储位置。例如：照片和电影库将搜集呢系统中所有的电子照片和数码影像的链接。 6.Windows Longhorn将包含许多反病毒（AV）的API，它将会帮助开发人员更容易地把他们的软件继承进基本的操作系统中。微软也 将会向Longhorn用户提供反病毒的自动更新的订阅，以确保用户的系统保持最新的反病毒功能。 7.Windows Longhorn将包含集成的可刻录DVD功能，它可以识别任何一种可刻录DVD格式。数字媒体狂热者们能够直接从摄像机直接拷贝倒可刻录的DVD上，而不用再复制到硬盘上。 8.Windows Longhorn将包含一种更高级的错误报告工具Error Reporting Tool (ERT)，它允许用户向微软报告Bug，并且可以自动修 复这些Bug 。 9.Windows Longhorn采用一种新的安装机制，将会在20分钟之内安装Windows Longhorn。 10.Windows Longhorn将包含许多新的API，以提供对系统的新功能的访问。 11.Windows Longhorn的编程机制将发生很大的变化，将统一Web和Windows编程模型，同时提供连线和离线的用户体验。在生成 Longhorn的技术中，微软已经完全转移到基于.NET的可管理代码环境。Longhorn生成器最终将明确与以前的Win32 API进行分离，也就是 说，Win32将会处于维护的状态，所有的开发都是以可管理的.NET API展开的。一个被成为Avalon的API形成Desktop Compositing Engine (DCE)（桌面创作引擎）的基本元素，DCE将替代以前的GDI和GDI+。另外一个被成为Aero的API，为新的用户界面提供API。这些全新的所有 API将采用XML应用程序标记语言，XML Application markup language (XAML)，对开发人员提供比以前方便的多的访问能力。 这种思想极大地减少了API的数量，并且使API更加标准化。目前，已经有超过76000个Wi n32 API和无数的包装。在Longhorn里，微软希 望把这些API减少到8000到10000个。另外一个重要的变化涉及到硬件驱动，在过去，微软允许消费者使用非签名(non-signed)的驱动程序以实现兼容性的需求，但这样经常导致稳定性的问题。在Longhorn中，用户只能使用经过签名的驱动程序了。 开发人员比较关心的是Visual Studio .NET "Whidbey"的发布，Whidbey是Windows Longhorn的IDE编程环境，目前处于Beta版的状态。Whidbey包括XAML的可视化设计器。在10月23号洛杉矶的PDC大会上，微软将向开发人员提供第一个Longhorn Software Developer Kit (SDK)的公开发布版本。Longhorn Software Developer Kit将包含开发人员可访问的UI组件和行为。 -- [XP1800+][ASUS K7V266C][Ramos DDR333 512M][Leadtek Winfast A170 DDR] [LaJi 17'][Logitech USB Wheel Mouse][Logitech keyboard] [Realtek RTL8139][Logitech USB Camera][WDC WD400BB-00DEA0][ST3120022A] [ATAPI CDROM 44X][IOMEGA ZIPCD 4X/4X/24X][刚弄到一块蓝色布垫] ※ 来源:·BBS 水木清华站 smth.org·[FROM: 219.224.187.201]
Re: xp.sp2 & 2003.sp1
发信人: Lord (小地主◎喜欢老婆的大眼睛), 信区: NewSoftware
标 题: Re: xp.sp2 & 2003.sp1
发信站: BBS 水木清华站 (Sat Dec 20 23:38:51 2003), 转信
转贴的。你可以试一下
＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝
Windows XP Service Pack 2 beta 2055 本地安装法
首先大家去下载一个Windows XP Service Pack 2 beta 2055
下载完成后把下载回来的xpsp2-express.exe解压到一个临时目录，如：xpsp2-express，接下来打开update下的update.url，可以看到一个URL链接：http://wxpsp2.windowsupdate.micr ... x86fre-USA-2055.psf，去下载吧，这个就是我们本地安装的文件，有300多M之巨 ，接着修改update.url，把这个链接修改为你下载的本地安装文件的地址，如：file:///C:/WindowsXP-SP2-x86fre-USA-2055.psf。接下来等文件下载完了运行update下的update.exe，呵呵，已经是本地安装了哦。
＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝
【 在 lyyq (lyyq) 的大作中提到: 】
: SP2好像是网络安装得啊
: 没有硬盘安装得吗
--
●
┃┿ ┿ .˙ │ ┿┑ 路请┄┅阅━读◆最即时的信息◆━x┅┄ .·¨‥. . ·˙
┿ ━┿ ┃┿ ┿┷ ·…’'; ┄┅ ━ ◆最热烈的讨论◆━ ┅┄ '¨* ●
·˙│ ·│ │ / ﹨ 版 ˙·˙‥. ┄┅ ━ ◆最旺的人气◆━ ┅┄
.·. THUExpress
新手上路请先阅读精华区治版方针 x-2-1-1
※ 来源:·BBS 水木清华站 smth.org·[FROM: 211.96.233.1]
xp.en.vlk.sp2b2082试用 ：)
发信人: li0nBc (dRag0nMa), 信区: NewSoftware
标 题: xp.en.vlk.sp2b2082试用 ：)
发信站: BBS 水木清华站 (Thu Feb 26 08:54:51 2004), 转信
1>正如大家所预料的,sp2又ban了很多key,呵呵,所以,推荐refresh install.
这几个key是我检验可以用来安装的,当然,肯定还有其它的:
QVJ2P-2HY64-TX2TJ-R6XXD-QP646
2Q8XT-MMFHR-KTK32-RCYJ6-YCTJY
MT2MV-WBFV4-8FJP4-DCT6X-8383D
2>ie的版本是6.0.2900.2082 update version:sp2
dX 的版本是9.0b 4.09.0000.0903
3>内建的firewall的界面又很大的改善,可以选择exceptions了,但是,好像不能不接收有程序链接的警告.
性能还没有测试.
4>windows的update界面有所改观,正在测试(现在的网络有些慢),scan的时候error,后边会再测试.
5>在b2055上集成的,依然缺少3个文件:nmoldwb.dll,nmwb.dll,nmwhiteb.chm,不过不影响使用
6>装完系统后,第一个装的是alcohol 120%(1.4.7b1005),应为要装ibm的驱动.一切正常
后边又装了java vm
7>tweak的时候发现以前通过修改注册表来取消系统文件保护功能的做法失效,还是会弹出对话框
不知道是不是要crack:)
8>区域设置没有看到设置默认语言的地方,我装的时候是选择装亚洲语言支持,这样装了很多垃圾(日文等)
所有,以后会再winnt.sif里面设置,装简体跟繁体.地区设置成china (prc)后,语言自动默认简体.
9>多了个security center,包括firewall,av跟windows update的提醒.
10>first logon 的配置中,要选择是否自动update,我选择否,结果hang了,按电源键关掉,希望final里面会改.
11>暂时这么多了,还在测试,有新感受会及时分享
--
滚滚长江东逝水，浪花淘尽英雄。是非成败转头空，青山依旧在，几度夕阳红。
白发渔樵江渚上，惯看秋月春风。一壶浊酒喜相逢，古今多少事，都付笑谈中。
明·杨慎
※ 来源:·BBS 水木清华站 smth.org·[FROM: 61.170.175.*]
Re: xp.en.vlk.sp2b2082试用 ：)
发信人: RonLiang (俩零), 信区: NewSoftware 标 题: Re: xp.en.vlk.sp2b2082试用 ：) 发信站: BBS 水木清华站 (Thu Feb 26 09:12:42 2004), 转信 【 在 li0nBc (dRag0nMa) 的大作中提到: 】 : 标 题: xp.en.vlk.sp2b2082试用 ：) : 发信站: BBS 水木清华站 (Thu Feb 26 08:54:51 2004), 转信 : : 1>正如大家所预料的,sp2又ban了很多key,呵呵,所以,推荐refresh install. : 这几个key是我检验可以用来安装的,当然,肯定还有其它的: : QVJ2P-2HY64-TX2TJ-R6XXD-QP646 : 2Q8XT-MMFHR-KTK32-RCYJ6-YCTJY : MT2MV-WBFV4-8FJP4-DCT6X-8383D : : 2>ie的版本是6.0.2900.2082 update version:sp2 IE下载文件时的弹出框变化不小。hoho : dX 的版本是9.0b 4.09.0000.0903 MediaPlayer 9.00.00.3124 XP的多系统选单的名字都是Windows XP Media Center Edition了。 : : 3>内建的firewall的界面又很大的改善,可以选择exceptions了,但是,好像不能不接收有程序链接的警告. : 性能还没有测试. 奇差无比。极不稳定 : : 4>windows的update界面有所改观,正在测试(现在的网络有些慢),scan的时候error,后边会再测试. 的确，和2055beta的还有进步。 我的没有报错。不过有19.2M的升级文件可选。。 : : 5>在b2055上集成的,依然缺少3个文件:nmoldwb.dll,nmwb.dll,nmwhiteb.chm,不过不影响使用 : : 6>装完系统后,第一个装的是alcohol 120%(1.4.7b1005),应为要装ibm的驱动.一切正常 : 后边又装了java vm 偶直接装的sun java : : 7>tweak的时候发现以前通过修改注册表来取消系统文件保护功能的做法失效,还是会弹出对话框 : 不知道是不是要crack:) : : 8>区域设置没有看到设置默认语言的地方,我装的时候是选择装亚洲语言支持,这样装了很多垃圾(日文等) : 所有,以后会再winnt.sif里面设置,装简体跟繁体.地区设置成china (prc)后,语言自动默认简体. : : 9>多了个security center,包括firewall,av跟windows update的提醒. 这个可以在服务中禁用 : : 10>first logon 的配置中,要选择是否自动update,我选择否,结果hang了,按电源键关掉,希望final里面会改. 我比较幸运。我选了yes : : : 11>暂时这么多了,还在测试,有新感受会及时分享 : : -- : 滚滚长江东逝水，浪花淘尽英雄。是非成败转头空，青山依旧在，几度夕阳红。 : 白发渔樵江渚上，惯看秋月春风。一壶浊酒喜相逢，古今多少事，都付笑谈中。 : 明·杨慎 : : : ※ 来源:·BBS 水木清华站 smth.org·[FROM: 61.170.175.*] -- 当你的电脑被病毒或者木马侵害的时候，请到virus版。 如果你受益于virus版，那么今后就请你帮助你的病友们，因为你深知他们所处的境地。 如果virus版未能如你所愿，那么也请你为了他们，将后来跟病毒斗争的经验告诉他们。 当你对病毒反病毒技术感兴趣的时候，请到virus版。共同提高、共同关心计算机安全。 virus版需要每一位网友的支持！ ※ 来源:·BBS 水木清华站 smth.org·[FROM: 219.224.138.*]
Winxp sp2 2082 一些截图
发信人: archon (Just DO it), 信区: NewSoftware 标 题: Winxp sp2 2082 一些截图 发信站: BBS 水木清华站 (Thu Feb 26 09:51:21 2004) 1. 系统 2. Security Center 3. Windows firewall - General 4. Windows firewall - Exceptions 5. Windows firewall - Advanced 6. Internat Options (Prompt-windows management) 7. IE Popup blocked bar 8. IE About -- ┈╆─╮┈┈╋───╋┈┊┈╬──┼┈┈┈┈┼┼┈┈╬──╋┈┈┈p数据库[ACCESS][十进制数据] │ │ 我 │ 的 ┼─ Feb█2┈┤ 世 ├──╬┼┼┼╭─┼╮美│xtEditor的优缺 ┈ █7─┼┈┈roge█z───┼ │ ╚──┤ 界 │┼合集] 以下几█款─╢不│┗─哪个更█好─╮些 │ │ │ ╬─╯ ┈╩──╯ │ │再│ │丽│zz from 乌鸦的日 ┈┗─┼┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈│┈┼─╬┈┈╬─╯┈ecky!经典使用问题集（0516版）zz f ※ 来源:·BBS 水木清华站 http://smth.org·[FROM: 159.226.21.*]
XP SP2 Beta v2096试用
发信人: RonLiang (俩零), 信区: NewSoftware 标 题: XP SP2 Beta v2096试用 发信站: BBS 水木清华站 (Thu Mar 18 14:10:11 2004), 转信 安装完重启之后先进入了安装系统时才有的“请稍候”那个黑屏幕。:) 估计重新设定了不少东西。 IE版本是6.0.2900.2096，谈出广告屏蔽一如既往的好。 Media Player版本9.0.0.3133。解决了2082里面MediaPlayer的SRS功能不佳的Bug 以前最受诟病的ICF的兼容性稳定性问题现在已经很好了。 DCOM服务和别的SP2版本一样，不可或缺了。禁用这个会很麻烦。 和所有XP SP2一样，现在的windows autoupdate如果被禁用之后，连手动的在线更新都没法进行。 总的来说，现在的SP2暂时没有发现不稳定的地方。 比以前的SP2进步了不少。甚至感觉速度比2082快多了，无论是启动还是运行速度。 现在XP Sp1为了防Welchia要打的补丁太多了。 SP2的推出是越早越好。 不过这个版本现在还要在线打一个补丁：March Security Beta (7) 新装的SP2之后原来的微软拼音2003被打回3.0了。。。 Office之外没法用体验版了。现在修复一次Office就好了。^_^ -- 当你的电脑被病毒或者木马侵害的时候，请到virus版。 如果你受益于virus版，那么今后就请你帮助你的病友们，因为你深知他们所处的境地。 如果virus版未能如你所愿，那么也请你为了他们，将后来跟病毒斗争的经验告诉他们。 当你对病毒反病毒技术感兴趣的时候，请到virus版。共同提高、共同关心计算机安全。 virus版需要每一位网友的支持！ ※ 修改:·RonLiang 于 Mar 18 14:29:56 修改本文·[FROM: 219.224.138.*] ※ 来源:·BBS 水木清华站 smth.org·[FROM: 219.224.138.*]
体验longhorn build 5048
发信人: nikilee (niki), 信区: NewSoftware
标 题: 体验longhorn build 5048
发信站: 水木社区 (Wed Apr 27 12:46:41 2005), 站内
昨天晚上从eea上把longhorn拖回来之后就迫不及待的
开始尝试，本人机器配置不是很好，没有体验到什么东西，
就简单写一点吧，回到新家了，呵呵。
整个系统安装大概耗费了40分钟，安装完成之后，声卡
驱动自动安装了，我的显卡是unichrome集成的，没有驱动，
下载了for XP的驱动安装一切正常，4074的时候怎么都不能
安装:(。
最郁闷的事情是安装完成之后安装了一下daemon，结果
系统开始频繁自动重启，到保护模式下不能卸载，说是windows
installer在保护模式下不能启动，在启动的时候按F8出现的选
项中多了一个在遇到错误的时候不重启机器，选择之后发现直接
死机，什么反应都没有，进入保护模式之后想system restore告
诉我系统中有一个硬件设备故障，不能restore，郁闷坏了，干脆
重新安装。
测试了一下一些基本的软件，都能够比较正常的运行，不过
MyIE2在显示器的左上角一块白色，看不见输入的地址，IE很耗系
统资源，一个进程大概要35M。
系统安装完成之后大概只需要200M内存，没有WinFS，有一个
mssearch服务，搜索的速度挺快的，还可以设置多个filter，应该
以后还会有较大改进。
AERO的开始菜单按钮很酷，鼠标放上去之后那盏灯会变亮。
Norton Anti-virus 企业办ver10安装完成之后不能正常启动
自动防护。
回头安装一下office和VS2005beta尝试一下。
其他的还在体验中，慢慢汇报。
--
※ 来源:·水木社区 newsmth.net·[FROM: 218.104.71.*]
Re: 体验longhorn build 5048
发信人: Vela (快乐的小帆船), 信区: NewSoftware 标 题: Re: 体验longhorn build 5048 发信站: 水木社区 (Sat Apr 30 09:11:09 2005), 站内 俺的机器是sp2200+512+radeon9000 on asus board 重新分了个区后就装了，都还顺利。 只是貌似和以前的多系统启动略有区别，longhorn自己整了个用来boot的咚咚，俺的启动菜单要选两层；启动挺慢的。 longhorn把自己安装所在盘作为了系统盘C，其他的顺推，因此盘符有了变化，害得我有若干软件无法执行；默认好像不显示盘符，只有 名称，甚不习惯；6G的盘装完剩了不到2G。 longhorn的系统盘上不只document、windows、program三个文件夹，还有个build、InstalledRepository文件夹，还没弄清楚。 装完系统看设备管理器，发现网卡没装上，只好重新找了驱动手动安装，管他认不认，还行，装完可用；声卡貌似装上了，但死活没有声音，最后也是手动安装，装完也可用了；显卡认不出来，手动装了一下，显示型号就对上了；几个驱动直接运行setup（for xp版）都不 好使，声卡那个还提示说不支持目前系统，呵呵；不过到现在。还有个咚咚不知是啥，还有个？挂在那里。 俺用的GB看新闻，而且习惯大图标，但在longhorn上，GB的大图标也太大了点，主要是图标周围的空白太多了，占了很多空间，不知怎么弄的。 其他还没有来得及试，只是看了盖子的演讲，觉得那个glass挺有意思，查了查弄了一下。只是开了dwm以后，感觉机子从586变回286了，窗口透明有了，最大、最小化的时候有那个animations and transition效果，按钮也变样了，可惜阿，太费劲了，跑不起来。 觉得要是不提dwm的话，眼下的状况还可以，当然很大型的软件还没有试，但就一些常用的看还行，弄起来和xp有些相似，lh自带了xp主 题，选了以后基本上就是个xp拉，除了那些改进。 大体就这些先，其他的再补充。 【 在 nikilee (niki) 的大作中提到: 】 : 昨天晚上从eea上把longhorn拖回来之后就迫不及待的 : 开始尝试，本人机器配置不是很好，没有体验到什么东西， : 就简单写一点吧，回到新家了，呵呵。 : ................... -- 凡属不可避免的就是理所当然的 ※ 来源: ·BBS 水木清华站 smth.org·[FROM: Phoenix City]
Vista.5231.PROPER.软件试用手记 [1]
发信人: withinsea (沐海|呵呵……呵呵呵……呵呵呵呵……), 信区: NewSoftware
标 题: Vista.5231.PROPER.软件试用手记 [1]
发信站: 水木社区 (Thu Oct 13 01:39:17 2005), 站内
装好了系统下一步就该上软件了吧……也不知能用的还有多少
p.s. 以下仅限于平时我用到的软件
[1] copy and use
1. CTerm (3.23 build 050514)
正常啊正常，huhu^^。所以现在在这里贴得很高兴
2. TM (2005)
启动后界面上一片空白……像一个 VB 里新建立的空窗口
虽然貌似是在运行着但实际上等于没法用。只能等下一个版本了……
(MSN 我没试。不是有 www 版本了么……那东西好强)
3. ACDSee32 (2.44)
正常。这才叫好软件哪……多少年头了……
4. LeapFTP (2.7.5.610)
正常。继 ACDSee32 之后再次印证简单即美……
5. MPlayer (20050717-KK)
正常。虽然因为没有声卡驱动没法出声，图像确实是好的
6. FlashPlayerMX
唔……正常。没啥可说的……
--
あの空を回る風車の羽根達は ...,,,..
いつまでも同じ夢見る .::::::::::::::::...
届かない場所をずっと見つめてる ::::::'''' _ ,- -""-.
願いを秘めた鳥の夢を :'' ,,- ' ` 「AIR」
." ``'- -'' .... the 1000th summer
※ 修改:·withinsea 于 Oct 13 01:39:28 修改本文·[FROM: 221.221.207.*]
※ 来源:·水木社区 newsmth.net·[FROM: 221.221.207.*]
Vista.5231.PROPER.软件试用手记 [2]
发信人: withinsea (沐海|呵呵……呵呵呵……呵呵呵呵……), 信区: NewSoftware
标 题: Vista.5231.PROPER.软件试用手记 [2]
发信站: 水木社区 (Thu Oct 13 02:33:07 2005), 站内
下面是……就算是常用软件吧。虽然依各人的习惯会有很大不同……
[2] 搞些大软件之前手头必备的东西
1. WinRAR (3.5rc)
正常。啊哈……这个要是没法用就要命了……
2. Daemon Tools (3.47)
大家都知道这个没法用了哈。虽然我不死心还是试了一下……
终于发现把大软件都存成 .iso 的做法是会有麻烦的 - -b
对了前两天说到哪个虚拟光驱现在在 Vista 可以用来着？
注：Daemon 3.11 可用 - -b
3. foobar & lyricII (0.8.2)
应该是正常的。不过声卡问题……没法验证了
(其它的多媒体相关的软件我就都没试了)
4. FlashGet (1.71chs)
正常。终于下定决心换这个了。没广告是重要原因……
5. BitSpirit (3.0.1.077 似乎是……)
运行是正常的。但是界面有错位的现象出现，字号也变小了。
国产软件在 UI 上还是没有太多的注意力阿……
6. Firefox (0.9.2)
正常。虽然我本来以为它会出毛病的……名家风范说。
7. TT (2)
er....也不能指责吧，毕竟 IE 变了很多对不……
安装起动都正常，选好插件开始打开窗口的时候出错推出。
不兼容新版 IE 的缘故……估计 IE inside 的浏览器多多少少都会有类似的问题
等新版。
8. Editplus (2.12)
正常。我果然是离不了这个呢^^ 就是觉得它的 UI 比 UE 要协调
p.s. Vista 下面的字体有不少有变化了。
宋体字库是新的(所以 Term 下文字那么平滑？还是因为全部字号都直接走矢量字？)
我喜欢用的编程字体 Courier New 8px 看起来也不大一样了
9. Adobe Acrobat Reader (7 chs)
正常。松一口大气……
10. Kaspersky Anti-Virus (4.5) & Anit-Hacker (1.8.180)
安装不能。Pro 和 Personal 全都不认识这个系统…… - -b
11. Symantec Antivirus Corporate (10.0.0.359)
蓝屏!安装到70%左右出现，需要进安全模式把它卸掉才会正常
但也许是因为 Daemon 3.11 的问题……总之请小心
嗯，也就是说，一般的使用应该是没什么大问题说。
只是杀毒部分……唔。
--
あの空を回る風車の羽根達は ...,,,..
いつまでも同じ夢見る .::::::::::::::::...
届かない場所をずっと見つめてる ::::::'''' _ ,- -""-.
願いを秘めた鳥の夢を :'' ,,- ' ` 「AIR」
." ``'- -'' .... the 1000th summer
※ 修改:·withinsea 于 Oct 13 13:25:03 修改本文·[FROM: 221.221.207.*]
※ 来源:·水木社区 newsmth.net·[FROM: 221.221.207.*]
Vista.5231.PROPER.软件试用手记 [2补]
发信人: withinsea (沐海|呵呵……呵呵呵……呵呵呵呵……), 信区: NewSoftware
标 题: Vista.5231.PROPER.软件试用手记 [2补]
发信站: 水木社区 (Thu Oct 13 13:32:24 2005), 站内
用了 daemon 3.11，有些东西能装了。另外再加上之前忘了的。补充几个……
首先！我用 daemon 装 Symentac 时候蓝屏！卸载才恢复。
不知是因为 Symentac 本身还是因为 daemon，总之请小心。
12. MS Apploc
正常。常需要用各种语言的软件的朋友们可以放心了。
别忘了修改 /windows/AppPath/AppLoc.tmp 为空并置为 Read-only
13. MS Office (2003)
正常。安装过程中曾有几个注册表键写不进去，忽略掉了
不过貌似不影响使用。怀疑是语音组件碰上了没驱动的声卡闹的
14. 金山词霸 (2005)
正常。局域网里很多人装的话，在防火墙里面把它访问网络的权限禁掉。
【 在 withinsea (沐海|呵呵……呵呵呵……呵呵呵呵……) 的大作中提到: 】
: 下面是……就算是常用软件吧。虽然依各人的习惯会有很大不同……
: [2] 搞些大软件之前手头必备的东西
: 1. WinRAR (3.5rc)
: ...................
--
あの空を回る風車の羽根達は ...,,,..
いつまでも同じ夢見る .::::::::::::::::...
届かない場所をずっと見つめてる ::::::'''' _ ,- -""-.
願いを秘めた鳥の夢を :'' ,,- ' ` 「AIR」
." ``'- -'' .... the 1000th summer
※ 来源:·水木社区 newsmth.net·[FROM: 221.221.207.*]
Vista.5231.PROPER.软件试用手记 [3]
发信人: withinsea (沐海|呵呵……呵呵呵……呵呵呵呵……), 信区: NewSoftware
标 题: Vista.5231.PROPER.软件试用手记 [3]
发信站: 水木社区 (Thu Oct 13 13:43:47 2005), 站内
[3] 开发工具。Java 适用。
1. jdk (1.5.0_04)
正常。呼……
2. Eclipse (3.1) & MyEclipse (4GA)
正常。不正常就见鬼了，jvm 上面跑的东西。
3. Tomcat (5.5.9)
正常。同上，java 的优势啊……
4. MySQL (5.0rc)
正常。这样基本的应用已经可以跑起来了……
顺便说一句，MySQL 的三个官方客户端 Administrator,
Query Browser, Migration Toolkit 都是拷过来就可以用
5. MS SQL Server (2000)
安装不能……因为有项目在用所以试了一下，不出所料地没法用。
只能等新版本了吧……
嗯，最主要的几个工具都还可以用
cvs 不一定要装在本机所以无所谓了……
晚上再试 Photoshop 之类的东西
【 在 withinsea (沐海|呵呵……呵呵呵……呵呵呵呵……) 的大作中提到: 】
: 用了 daemon 3.11，有些东西能装了。另外再加上之前忘了的。补充几个……
: 首先！我用 daemon 装 Symentac 时候蓝屏！卸载才恢复。
: 不知是因为 Symentac 本身还是因为 daemon，总之请小心。
: ...................
--
あの空を回る風車の羽根達は ...,,,..
いつまでも同じ夢見る .::::::::::::::::...
届かない場所をずっと見つめてる ::::::'''' _ ,- -""-.
願いを秘めた鳥の夢を :'' ,,- ' ` 「AIR」
." ``'- -'' .... the 1000th summer
※ 修改:·withinsea 于 Oct 13 13:57:36 修改本文·[FROM: 221.221.207.*]
※ 来源:·水木社区 newsmth.net·[FROM: 221.221.207.*]
Office12体验感想
发信人: OneMoreTouch (放弃幻想，未必能成就现实！), 信区: NewSoftware 标 题: Office12体验感想 发信站: 水木社区 (Thu Oct 27 21:43:51 2005), 站内 在今晚9：00以前，我认为今天是个不错的日子（对于我这个新软迷来说只要有软件更新 就会顿时精神气爽，典型的新软综合症），因为今天一下子冒出了两个新软：OFFICE12 和QQ2005,尤其是前者，自从上次看了微软出的演示视频后我就对OFFICE12一见钟情了 ，天天盼着早日目睹其芳容，而对于后者，虽然也挺让人激动，但用后觉得较之前几个 Beta版，基本没什么改变，所以兴奋劲还没起来就冷了。 现在只说OFFICE12，虽然还只是Pre-release版，但我还是一狠心把原来的OFFICE2003完 全卸掉了，心想着这东西一定更好用。安装过程还算顺利，但也发现了不少问题：采用 Custom方式，很多可选项旁边都没有文字，改变安装路径也做得挺次的，也不给个参考 路径，另外如果已经安了OFFICE12,再安装Visio等其他东西时，程序不会自动检测OFFI CE12的安装路径，而是仍然安装在默认位置，整个安装过程不算太慢。 装安后，我迫不及待的挨个运行，首先是Word：如果没有卸载原有的老版OFFICE，它可 能会在启动的时候报一些宏加载错误，主要是语言问题引起的，全新安装不会有问题， 启动速度不慢，只比2003慢一点，但完全可以接受（我的本本是P4m1.4,512MB内存，Ge force4go420），这个的确让我挺兴奋的；运行的界面和以前介绍过的一样，第一次用这 种形式的界面的确要适应一段时间，再加上全是英文的，难度的确不小。我打开了几个 原来的Word文档，可以轻松加载（包括我120页的毕设论文），只是会提示该文档使用了 一些老版的功能，问要不要启用这些功能，启用后没发现什么不同，其它的一些精彩功 能就不说了，单说一下一些缺陷吧：首先没找到关闭当前文档的按钮，要关只能整个Wo rd程序一起关（也可能是我真的没有找到），这个让我很FT；一些常用的按钮，比如打 开，新建等默认为有快捷按钮，需要自定义出来，默认的只有保存和返回上一步；界面 上的一上的一些大图标显示比较粗糙。Word默认保存的格式已经改成了.docx，所以要想 和现在的老版兼容的话，可能还得另存为.doc，但这个也可以设置。 Word的表现其实还是另我挺满意的，用Office12来代替2003的决心已经下了1／3了，接 下来试了试PowerPoint，这个让我很郁闷，找开程序没有问题，速度也还可能接受，但 当我打开原来的PPT文档时，居然没打开，程序死掉了，我确定这个文档用2003是可以打 开的，后来又试了几个，有一些可以打开，但当PPT里包含一些直接从Autocad或者Prot el里拷过来的图时，速度会爆慢，近乎于死机，而且整个放映过程也显得一顿一顿的； 默认的模板只有4个，而且很丑；另外一个很低极的Bug是在2003里如果一行没有内容， 其前面的行标是会自动隐掉的，但在12里居然都显示出来了，这让ppt怎么看呀。其它像 实时预览的功能我没看到，可能是我机器配置还是太低了的缘故。 在遭受了PowerPoint的沉重打击之后，我抱着卸载OFFICE12前最后欣赏一下的心情，试 了试Excel，相比之下，Excel做得是比较完美的，打开了几个文件都没有问题，但我并 没有深入测试，只是大概看了看。 其它像Outlook，frontpage和Visio，前两个平时不怎么用，不知道有些什么改进，感觉 变化不大，Visio的界面变化也不大，但模板好像进行了重新的整理归类，在操作上增加 了一些像自动连接相邻线的功能，其它的没有多试了。 晚上9：00回来后，终于下定决心还是把Office12卸掉了，虽然它的确带给了我不少的惊 喜，尤其是它的运行速度并不像想像的那样慢，但它还是带了太多的Bug，毕竟还是Pre -release版嘛。我像等beta版出来的时候我肯定还会义无反顾地会去当一回小白鼠的， 嗯！ -- ※ 来源:·水木社区 newsmth.net·[FROM: 59.66.100.*]
Windows Vista 5231.051004安装报告
发信人: Hakkk (我爱老婆), 信区: NewSoftware
标 题: Windows Vista 5231.051004安装报告
发信站: 水木社区 (Sat Oct 29 20:13:56 2005), 站内
前段日子下了好久下下来的5231.051004 版，前几天终于有空安装了，之后断断续续折
腾好几天，到现在为止告一段落。
【软硬件环境】
CPU： AMD Athlon XP 1800+ (11.5*133超频至166)
主板： FIC AU13, nVidia nForce2 Ultra 400
内存： 512MB DDR333
显卡： nVidia GeForce4 MX 440 with AGP8x
声卡： (板载)nVidia MCP2
网卡： (板载)3Com 3C920B-EMB Integrated Fast Ethernet
(PCI)Macronix MX98715-Based Ethernet Adapter
(PCI)Realtek RTL8139 Family PCI Fast Ethlernet NIC
OS： Windows XP Pro SP2 VOL CHS (On C:\Windows)
【安装】
只有镜像，没有DVD刻录，所以就从XP里安装了。
用Daemon mount 上安装盘镜像，从虚拟光盘运行setup，安装流程自动开始。基本没有
什么可以干预的部分，只有选择安装方式、填序列号、选择分区需要动动鼠标键盘。在
选择安装方式的一步，因为XP和Vista的语言不符，所以升级是无效的，只有全新安装，
这也正是我需要的。选择分区的时候选了一个专门空着的分区F:，然后就开始淅沥哗啦
的拷文件。
【启动】
经过无所事事的等待，系统安装完毕。启动的时候发现，boot菜单已经完全更新了，界
面与2k/xp/2k3时代的菜单完全不一样，显示两项分别为Legacy pre-longhorn windows
和Microsoft Windows，默认为后者。猜测第一项应该是启动XP用的，于是选了第一个，
结果出乎意料的是又到了另一个boot菜单，这个是旧风格的XP的boot菜单，里面也是两
项，Windows XP和Windows Longhorn。尝试选第二项，结果黑屏后就此死掉，说明这一
项根本是无效的。重启后选Legacy，然后Windows XP，重新回到XP下，然后用msconfig
检查Boot.ini，发现这个文件只反映了上面说的第二层boot菜单，并且用检查启动路径
后发现longhorn这项确实无效，于是干脆删掉，并且把显示菜单时间改为0，这样Vista
的新boot菜单中的两项就相当于直接对应了XP和Vista。
后来看看C盘和F盘，下面都多了一个Boot目录，估计是Vista 的新boot菜单用的，没有
找到编辑方法，在Vista的系统属性－高级－启动设置里面也没有类似XP 编辑菜单的地
方，只能改变默认选项以及等待时间而已。
【登陆】
再重启，选Microsoft Windows，这回看到Vista 的欢迎界面了，除了Administrator，
还有一个用其他用户登陆的选项，能够直接输入用户名和密码。后来证明这一设计还是
不错，因为如果系统新建了其他Administrators组的帐号，欢迎界面上的Admin 就隐藏
了，对于XP来说需要登陆时ctrl+alt+del两次调出传统登陆框才能登陆，而Vista 选择
其他帐户的话直接就可以输入帐户名和密码。
【用户权限】
新建了一个Admins 组的帐号，然而进去之后发现其权限仍然低于系统内置Admin帐号。
在执行一些程序的时候，会弹出窗口询问是否授权运行，类似linux 要求输入root密码
那样，只不过因为这个帐号也确实是Admins组的，所以没问我密码，只是确认授权就行
了。在开始菜单里可以看到有一个Turn On/Off UAP 的快捷方式，用来关闭这个授权询
问。不过就算关了，在执行一些服务、驱动方面的设置时，自建的Admins组的帐号还是
权限不够。于是最后干脆删除了自建帐号，回Administrator做后面的事情了。
【中文支持】
系统自身一切正常。进到区域语言选项，把位置、单位格式、非Unicode 程序默认语言
都设置到中文或者中国，重启，然后发现对中文的支持非常好。安装自己最习惯的紫光
拼音3，完全正常。
【驱动】
打开设备管理器，发现一砣未知设备，是那种类型都没识别出来的未知设备。已经识别
出来的主要硬件包括那块MX440的显卡和Realtek的网卡，其他两块网卡、板载声卡都嗝
了。为了安装驱动，先得分清哪个？号对应哪个设备。幸好事先在XP的设备管理器中做
了记录，例如3Com的板载网卡是PCI总线2、设备1、功能0，Macronix的网卡是PCI总线1、
设备11、功能0等等，接下来就可以折腾驱动了。
声卡：从nVidia的网站里找到了for vista的驱动：
http://www.nvidia.com/object/winvista_32bit_beta1.html
那堆问号设备中有两个是声音相关的，一个是nVidia nForce Audio Codec Interface，
另一个是nVidia nForce MCP Audio Processing Unit。每一个都执行一遍Reinstall，
选择自己查找设备，然后类型中选声音控制器，之后have disk ，定位到解压驱动的地
方，系统都能认出来对应设备。安装成功，有声音了～不过毕竟是beta版驱动程序，主
音量调节居然无效……我是指左右滑动滑杆音量是不变的……（Vista 的音量调节不是
上下滑而使是左右滑）。幸好Media Player的音量调节是有效的，不然就总要旋音箱旋
钮……
网卡：上面那个网页里也有网卡驱动，不过是nForce3 之后主板的，用不了。找到当初
买主板时候给的驱动盘，把for 2k/xp 的驱动程序目录拷出来，然后选代表板载3Com网
卡的那个问号设备，同样步骤，类型选为网络适配器，定位到驱动目录，又认出来了，
安装，成功。
不过另一块Macronix的网卡就折腾死我了。在XP中它是自动识别的，Vista 中却没带它
的驱动。尝试用XP系统的驱动程序，在安装时定位到C:\Windows\inf，也就是XP存放所
有设备inf文件的地方，能顺利找到Macronix MX98715-Based Ethernet Adapter的驱动，
但是点下一步安装的时候总是出错，看来这个从Win2k到XP都能用的驱动终于死在Vista
了。网上找这块网卡的驱动，都是比XP里带的还老的，安装统统出错。最后的希望是用
Win2k3的驱动了，这个刚刚才弄到，版本号确实比XP的高，如果这个还不行，那就忍了。
剩下的一个设备是nVidia nForce PCI System Management ，这个本来就没有驱动，只
是Vista不知道是什么东西而已，人工选择分类为系统设备，然后在list 里面就能找到
一模一样的名字，确认即可（也不知道究竟有什么用）。
【上网】
本地连接正常，登陆tunet我用的是MyTunet程序，兼容性很好，安装服务也成功了。只
是接下来建立VPN连接的时候头又大了。新建连接－拨号或者VPN连接，这些还和XP一样，
然后下一个页面，选择拨号还是VPN的时候……居然两个都是灰色的……想到 Internet
选项中也有一个连接页面可以建立拨号和VPN连接，于是去那里看看，结果New按钮虽然
不是灰色的，但是死按都没有效果……
看来Vista是没有加入这个功能？试试看能不能用XP的代替。XP 中其实有一个拨号电话
簿文件，在C:\Documents and Settings\All Users\Application Data\Microsoft\
Network\Connections\Pbk\这个目录下，文件名是rasphone.pbk。双击运行，居然成了，
下拉框里赫然有XP中建立的VPN连接，属性也能修改，只是新建还是不能工作。点连接，
输入帐号密码，经过认证后窗口消失了，右下角也没有出现那个网络连接的小电脑标志，
不过通过ipconfig来看，连接确实建立起来了！
折腾累了，今天先不弄了。应用程序前面withinsea 测试了很多，我懒得动了。下次有
空重点再试试那块没起来的网卡，以及一个最大的问题……Activation……
--
表与里的存在……
阴影外的阳光……
光明的力量……
来自人心灵的正面……
不要忘记——
我就是你！！
※ 来源:·水木社区 newsmth.net·[FROM: 59.66.114.*]
Windows Vista 5231.051004安装报告（后续1）
发信人: Hakkk (我爱老婆), 信区: NewSoftware 标 题: Windows Vista 5231.051004安装报告（后续1） 发信站: 水木社区 (Sun Oct 30 13:42:05 2005), 站内 【网卡驱动】 最终那块网卡的驱动搞定了，还是用的XP的驱动，只不过原来我提取出来的文件有问题。 从XP的windows\inf提出来的自带安装配置文件是没有路径信息的，只指明了一个layout .ini文件，里面记录了驱动程序在driver.cab的什么地方，文件名是什么。Vista 下的 driver.cab里没有那个文件，所以安装出错说找不到文件。 在net713.inf文件中加入 [SourceDisksFiles] mxnic.sys = 1,,.\ 安装顺利成功！ 【显卡驱动】 因为想自定义刷新率（现在1280×960，85Hz，其实可以上到 90Hz，但没选项），所以 试着安装了nVidia的for 2k/xp的Geforce通用显卡驱动。解开文件后，运行.exe文件安 装失败，于是从设备管理器手动安装，定位到解压目录，成功。重启后nVidia的配置选 项工作正常，现在刷新率改到90 了。看来Vista虽然带的驱动少，但是对现有硬件和驱 动的支持还是不错的。关键是很多设备得从零开始装（即类型都没有识别，显示为未知 PCI设备），如果测试者不知道怎么识别分类就没办法了。 【AntiVirus】 安全中心也嘟嘟了半天，装个杀毒软件吧。我一向用NAV的，不过猜测Vista装不上，一 试，果然……于是改装SAV10企业版，完全没问题，自动防护、更新病毒库都和在win2k3 下没有区别。 【AnitSpyware】 安全中心里新加了这一项状态检查，并且查看时发现推荐打开微软的那个AntiVirus 软 件。不过似乎还只是一个壳，并没有把软件集成到 Vista，每次尝试打开都失败，最后 干脆关了这一项。期待下一个测试版了。 【桌面外观】 还是没有恢复Sidebar。我的MX440是DirectX7显卡，Aero Glass的D9特效自然是看不全 的，不过改了改注册表，也算强开了，强扭的瓜，嗯……果然不甜，因为不是毛玻璃而 是透明玻璃，有时候就找不到想点的窗口标题栏了……还有音量图标打开后什么都看不 见，当然摸索着位置还是能拖动那个滑杆的…… 【几个软件程序】 Fterm，太正常了； QQ，我在XP下装的新鲜出炉的珊瑚虫3.2.1，在Vista 下直接能用。 CCProxy，无论是XP下装的还是Vista重装的，根本不能运行，错都不报一个。 PES5，强开了D9特效运行就报错，不开的话正常的一塌糊涂，XP下装的，Vista 下导入 一个注册表就能爽了。 MSN Messenger 7.5，居然这个东西在XP下装的在Vista也能直接用，只不过进行选项设 置时候会报错，仅此而已……也不是啥大东西，重装就重装。 暂时就试了这么多，先歇会儿 最后一个大问题，还是关于激活的……看来找不到能用的号或者算号器了。希望那个破 解程序还是有效的，嗯。 【 在 Hakkk (我爱老婆) 的大作中提到: 】 : 前段日子下了好久下下来的5231.051004 版，前几天终于有空安装了，之后断断续续折 : 腾好几天，到现在为止告一段落。 : 【软硬件环境】 : ................... -- Darkness from twilight, crimson from blood that flows; buried in the flow of time; in Thy great name, I pledge myself to darkness! Those who oppose us shall be destroyed by the power you and I possess! DRAGU SLAVE!! ※ 来源:·水木社区 newsmth.net·[FROM: 59.66.114.*]
Vista 5308感受
发信人: luckyangle (听烟), 信区: NewSoftware
标 题: Vista 5308感受
发信站: 水木社区 (Mon Mar 6 08:55:22 2006), 站内
年前的5270也感受了，这个周末在家又鼓捣了一下5308
发现5308确实稳定了很多
基本上从登陆到界面都定型了
而且Vista的桌面图片一版比一版漂亮
5308的好俺就不说了，就说说不好
1）我的主板是865PE的板子，声卡驱动搞不定
2）显卡驱动用内置的不行，会提示你驱动不兼容，不知
道微软搞什么名堂，内嵌的驱动都不兼容，后来换了
Nvida提供的5308专用驱动，搞定
3）网卡一直捕获不到DHCP分配的地址，也没搞明白怎么
回事，只好切换到XP下捕获地址，抄下来，手工设置，
上网搞定，IE7果然比IE6强，但是多页面似乎有点假，
点击超链接，新打开一个页面，居然重新开了一个IE7
大窗口，而不是在当前窗口开一个新的页面
4）Windows Defender无法更新
5）Symantec Antivirus Corporate Edition v10与5308不
兼容，装不成功，直接蓝屏，再次启动，再次蓝屏，只
能用上一次好的配置重新启动，卸载，手工清理注册表
后换趋势的Internet Security最新版，搞定，可升级
因为声卡到现在都没有搞定，所以还没来得及试MediaPlay
，哪位老大知道如何搞定声卡么？我的芯片是Reltek AC97的。
如果哪位老大有可用的驱动，请发到我的邮箱：
liuhuiyu@vip.sina.com
谢了阿！下次再报告实验进度！
--
※ 来源:·水木社区 newsmth.net·[FROM: 211.69.196.*]
Office 2007 beta1 感受
发信人: mikky (笑嘻嘻), 信区: NewSoftware
标 题: Office 2007 beta1 感受
发信站: 水木社区 (Sun Mar 19 00:52:08 2006), 站内
Office 2007 beta1 感受
1 操作比pre-beta近了一步，更趋于合理一些，但是的确需要换很大的思维才能习惯新的操作风格
2 从界面上来说，更漂亮了，outlook显示效果更好，但是带来的结果是大量的内存占用
3 在使用过的很多应用来看，word和outlook还不是很令人满意，（下面相细说明），但是其他程序，如excel, access, publisher, infopath从速度和稳定性来讲都已经到了可用的程度，picture organizer已经明显标明不是beta版本。很不错。
3 各组件似乎过多地用到了word的很多功能，而word开发不够成熟可能导致其余的部件，特别是outlook不稳定
4 word的感觉
- 不能很好地和2003兼容，原先的normal.dot会导致每次启动word都提示错误
- word占用内存太大.且操作硬盘频繁。在使用word过程中对于硬盘的喀拉喀拉声很明显。同时，也导致操作相应非常慢。
- 一些操作优化不好，比如显示字体列表延时很明显，输入的时候也觉得有一点慢，不知道是不是心里原因。
- 一些功能尚未完善，比如auto correction，比2003差很多，也多次出现该插件错误，而其他组件将其禁用现象
- 极端不稳定，有的时候切换窗口都会导致word退出
-
word优点：
- 新的操作，使得使用更加傻瓜化，但是需要时间适应
- 对ink tools 支持加强，对于我这样tablet使用狂人来说，还是很爽的
5 outlook的感觉
- 占用内存太大了。最小化以后居然占用了45M,不知道是用来干吗的。[第二次启动后，最小化，正常，越占用6M内存。看起来还是有点不稳定]，正常约占用50~60M。
- 操作速度慢了不少，不够流畅
outlook的优点
- 日历视图漂亮了不少，
- 在某些显示上优化了一些，如联系人窗口，多了一个名片显示，看起来比较漂亮，搜索联系人的时候，搜索到的结果中，搜索关 键字也会高亮显示
- 邮件视图中多了todo bar, 相当于原来的today window, 感觉好一点。
6 其他组件
其他组件主要使用了publisher, ppt, excel, 感觉到占用内存比原来多了一点，稳定性要比outlook和word好很多。另外主要看中他们的是，做表或者ppt,可以轻松地做出专业的效果，比原先的效果要好很多了。这一点可以让人花更多的精力在内容上。赞一个。推荐使用这几个。
Infopath 和 access以前用得不多，手头也没有对应的库和工程，所以没有试。但是通过打开程序和随便点击的情况来看，稳定性还是不错的。
7 总结和展望
看了这些，比较当初从XP到2003， 不管从功能，用户操作还是稳定性上，都是一个大的跨步。甚至在我的直觉里面，2003占用的资 源甚至都比XP少。 但是2007没有给我这种感觉，哪怕是将来出现的正式版，我也不抱太大的希望。因为比较2003的测试版，2007有一点 让人失望了。这些失望主要来自于最常使用的outlook和word.希望正是版本出来的时候，对资源和稳定性能够有一个很好的控制。
不过从做出文档的精美程度上，2007能够轻易地做出很专业的文档，即使是对于配色和布局很没有感觉的人，都能轻松应对，这个的确是一个很大的进步。在excel和ppt上，这一点体会尤其明显。
这次的测试版本中没有visio,很失望。想到visio2003的巨大进步，以及2007几个部件所体现出来的精美特效，不仅让我浮想联翩，实际 上visio2007才是我最梦寐以求的……不知到会做成什么样子。期待啊。同样还有惊艳一时的onenote, 不知到在2007中会以什么样的面目示人。不过可别占资源太大了，要不光刷新就等半天，谁还有心情做note啊。
简单的测试结束。比起pre-beta来，的确有一点失望，因为最想要改进的内存和稳定性，都没有提高，甚至已开始我都有一点怀疑我是不是下错版本了。所以对于正是版本，也不要抱太大的希望。只是如果和2003交叉使用能够用得住的话，outlook,word用2003,其他版本适 当选择使用，也未必不是一个好的选择。
附注：
1 我的硬件配置
PM 1.5G, 1.24G mem, 4200转的硬盘。
2 本来截了不少图，但是考虑到昨天为了上传附件居然发文等了快两个小时经验，还是节约时间，不传了。
--
※ 来源:·水木社区 http://newsmth.net·[FROM: 202.7.166.*]
Office 2007 Volume License Key
发信人: soff (荣升新软版版霸), 信区: NewSoftware
标 题: Office 2007 Volume License Key
发信站: 水木社区 (Sat Nov 11 16:27:38 2006), 站内
Office 2007 Suites
DBXYD-TF477-46YM4-W74MH-6YDQ8
Office 2007 Applications
W2JJW-4KYDP-2YMKW-FX36H-QYVD8
--
偶本 bt, 躬耕於 bit, 苟全性命於 bbs, 不求聞達於 mm...
一般来说，教师的幸福感主要由学生的对其的爱戴程度、自身对教学的胜任感、
探究的新鲜感、成功的愉悦感组成。
－－《理解教育论》熊川武，江玲 教育科学出版社2005
※ 来源:·水木社区 newsmth.net·[FROM: 222.131.58.*]
IE8 Beta2初体验
发信人: alwaysmylove (Your wish is my command), 信区: NewSoftware
标 题: IE8 Beta2初体验
发信站: 水木社区 (Thu Aug 28 11:46:41 2008), 站内
1. Inprivate browsing很好很强大，很黄很暴力，恩
2. 地址栏会出现类似Firefox的推荐网址功能，以前浏览的历史记录很明显
3. 查看源代码用了自带的查看器，有代码高亮功能，超级赞
4. 貌似找不到 模拟IE7 的按钮了,不过多了一个兼容性视图按钮，在地址栏旁边。而且，可以设置哪些网址用兼容性浏览。不过不是每 个网站都会出现这个按钮……很奇怪
5. 一堆什么加速器功能，直接关了，没用
6. 可以打开以前关闭的标签列表
7. 还没假死过……以前IE7经常死，估计是RP
8. 检查钓鱼网站那个东西，改名叫Smartscreen了
9. 管理加载项的功能人性化了很多，自动分类了
10. 标签浏览功能大大加强了。增加了选项卡组功能，在一个页面打开的新选项卡和该页面属于同一分组，不同组的选项卡用颜色区分开。关闭的时候可以直接关闭一个分组。关闭选项卡的速度很明显快了很多。
11. 在网页内查找功能强大了，跟fx很像
--
=== http://blog.alwaysmylove.net ===
Everything that has a beginning has an end
___ ___ ___ ___ _____ ___
| \/ | / _ \ |_ ||_ _|/ _ \
| . . |/ /_\ \ | | | | / /_\ \
我是 | |\/| || _ | | | | | | _ |
| | | || | | |/\__/ / _| |_| | | |
\_| |_/\_| |_/\____/ \___/\_| |_/
office2010 beta2不激活的使用方法(zz)
发信人: timepp (时间调色板), 信区: NewSoftware 标 题: office2010 beta2不激活的使用方法(zz) 发信站: 水木社区 (Sun Oct 18 11:29:48 2009), 站内 2009-10-18 12:03:59 (PS 我的方法不如littleboy的方法好，所以修改为littleboy的方法)方法： 1、把x:\Program Files\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPC.dll改名，如ossppc.dll.bak 2、将x:\Program Files\Common Files\microsoft shared\OFFICE14\Office Setup Controller\setup.exe改名,如改成setup.exe.bak 3、在注册表中查找 X:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPC.DLL，找到的值应 该在类似以下位置： HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserD ata\S-1-5-18\Components\ED417E2A8BA189D4C8741500D3BAD4A3 将上面的位置中ED417E2A8BA189D4C8741500D3BAD4A3改为 ED417E2A8BA189D4C8741500D3BAD4A3-bak -- 有我胡媚在，皇上怎么会看得上你呢~~ 勾引皇上的事情，还是交给我吧 ※ 修改:·timepp 于 Oct 18 12:05:58 2009 修改本文·[FROM: 119.40.25.*] ※ 来源:·水木社区 newsmth.net·[FROM: 119.40.25.*]
Microsoft Windows Vista Beta 1 Fact Sheet
发信人: Rydia (暖如地血，寒比天风), 信区: NewSoftware 标 题: Microsoft Windows Vista Beta 1 Fact Sheet 发信站: 水木社区 (Thu Jul 28 07:34:37 2005), 站内 Microsoft Windows Vista Beta 1 Fact Sheet Windows Vista? beta 1 is an important milestone on Microsoft Corp.’s path to releasing the final version of Windows Vista. Beta 1 will provide developers, IT professionals and Windows? enthusiasts with an opportunity to test the operating system’s infrastructure and provide Microsoft with valuable feedback. Beta 1 is being delivered to more than 10,000 beta testers via the Windows Vista Technical Beta Program, and thousands more people will receive beta 1 through the MSDN? developer program and Microsoft? TechNet. Fundamental Improvements for Computing With More Confidence Windows Vista beta 1 focuses on greatly improving the Windows’ fundamentals — security, deployment, manageability and performance — so developers, IT professionals and end users can have more confidence in their PCs. Enhancements have been made in the following areas: * Security. Windows Vista will deliver many new or improved security features that provide a usable, consistent and manageable experience in corporate, mobile and roaming environments, as well as in the home. Some examples of new security features in Windows Vista beta 1 include these: * User Account Protection features enable administrators to deploy PCs set up to give end users only the privileges they need to perform their tasks. This bridges the gap between user and administrative privileges by running applications with limited permissions. * Windows Service Hardening monitors critical Windows services for abnormal activity in the file system, registry and network that could be used to allow malware to persist on a machine or propagate to other machines. * Anti-malware features detect and remove worms, viruses and other types of malicious software from the computer during an upgrade. * Advanced data protection technologies reduce the risk that data on laptops or on other computers will be viewed by unauthorized users, even if the computer is lost or stolen. Windows Vista supports full-volume encryption to help prevent disk access to files by other operating systems. It also stores encryption keys in a Trusted Platform Model (TPM) v1.2 chip. The entire system partition is encrypted in both the hibernation file and the user data. * Microsoft Internet Explorer 7 in Windows Vista Beta 1 includes many features to help protect against malicious Web sites and malware. To help protect against phishing and spoofing attacks, Internet Explorer also does the following: * Highlights the address bar when users visit a secure sockets layer-protected site and lets users easily check the validity of a site’s security certificate * Allows users to clear all cached data with a single click * Network Access Protection. Viruses and worms can attack a protected internal network through mobile computers that do not have the latest updates, security configuration settings or virus signatures downloaded. Mobile users may connect to unprotected networks at hotels, airports or coffee shops, where their computers can become infected by malware or a virus. Windows Vista has Network Access Protection to help prevent security-compromised computers from connecting to a user’s internal network until security criteria are met. * Firewall. Windows Vista provides outgoing as well as incoming filtering, which can be centrally managed via Group Policy. This lets administrators control which applications are allowed to communicate or are blocked from communicating on the network. Controlling network access is one of the most important ways to mitigate security risks. * Deployment. Windows Vista will help make desktop deployment dramatically faster and easier. Deployment features included in Windows Vista Beta 1 include the following: * The Windows Imaging (WIM) format provides a single file that contains one or more complete Windows Vista installation images. To conserve space, Windows Vista compresses the file and stores only a single copy of files that more than one image share. As a result, Windows Vista images help eliminate redundancy, decrease file size, and reduce installation or migration time. Image-based setup also is less error-prone than a scripted installation process. * Windows Pre-installation Environment (PE) enables administrators to configure Windows offline as well as diagnose and troubleshoot hardware problems before launching the setup process. * The Application Compatibility Toolkit (ACT) helps administrators quickly identify, analyze and resolve any issues with non-standard applications being migrated to Windows Vista. * Manageability. Windows Vista will help reduce total cost of ownership (TCO) of PCs through simplified management, increased automation of tasks and improved diagnostics. Improvements in Windows Vista beta 1 include these: * Better diagnostics implementation, including auto-diagnosis and auto-correction of common error conditions, fixes for known crashes and “hangs,” and new technology to minimize reboots when installing software, are included. * An improved Task Scheduler schedules tasks to launch when a specific event occurs, such as when disk space becomes insufficient. * Web Services for Management (WS-Management) makes it easier to run scripts remotely and to perform other management tasks. Communication can be both encrypted and authenticated, helping limit security risks. * Microsoft Management Console 3.0 (MMC 3.0) provides a common framework for management tools, making them easier to find and use. MMC 3.0 supports richer, more functional graphical user interfaces for management and allows administrators to run multiple tasks in parallel, keeping administrative tools responsive even after launching a complex or slow management task. * Performance. Windows Vista will help improve PC performance in key areas, including starting up, waking up and responding to user actions. Performance features included in Windows Vista beta 1 include the following: * Quick startup. Login scripts and startup applications and services process in the background while users perform their desired tasks. * Sleep state. The new Sleep state in Windows Vista combines the speed of Standby mode with data protection features and low-power consumption of Hibernate. The Sleep state also allows users to change or remove a battery with little risk to open applications and data, since memory is safely written to the hard disk. Startup from the Sleep state requires just seconds, meaning fewer shutdowns and restarts are necessary, which helps improve power management. * Superior memory management and improved input/output (I/O) management makes Windows Vista more responsive than previous versions of Windows, especially in the most noticeable tasks, such as opening the Start menu or right-clicking a file in Windows Explorer to display a shortcut menu. Clear and Connected Many of the innovative end-user features and user-interface (UI) changes for Windows Vista will not be included until the release of Windows Vista beta 2. However, Windows Vista beta 1 does include an early look at the new UI design, and showcases some of the features that will give users clear ways to organize and use their information and seamlessly connect to people and devices, including these: * Searching and finding information.Windows Vista will introduce a new organization concept called a Virtual Folder, which is a saved search that is automatically and instantly run when a user opens the folder. In addition, every new Explorer in the operating system, including Internet Explorer, includes a new Quick Search box that enables customers to quickly search through large amounts of content being viewed or to initiate wider content searches across the PC. * Glass and new Window animation. The Windows Vista desktop experience will deliver a new visual identity — translucent glass with more animation. Because it is visually intuitive, the glass helps users focus on the task at hand, whether reading a document, viewing a Web page or editing a photo. * Redesigned Start menu with application search. The Windows Vista redesigned Start menu will make it faster and easier for users to find specific applications and to browse through all programs. * Sync Manager. Windows Vista will unify the synchronization with the Sync Manager, a new interface that enables users to initiate a manual sync, stop an in-progress sync, see the status of current sync activities and receive notifications to resolve conflicts across all devices and data sources with the click of a single button. * Networked projection for mobile PCs. Windows Vista will make it easier for users to connect a mobile PC to a projector over a network to display a presentation, or to share a presentation with nearby PCs. The networked projection feature allows a Windows Vista-based computer to detect nearby PCs or projectors and establish a connection through a network, regardless of whether the network is wired or wireless, ad hoc or part of a corporate infrastructure. Internet Explorer 7 for Windows Vista Beta 1 In addition to the security features mentioned above, Internet Explorer 7 in Windows Vista beta 1 includes new capabilities that make everyday tasks easier, including support for tabbed browsing, a toolbar search box that includes AOL search, Ask Jeeves, Google, MSN? Search and Yahoo! Search, as well as shrink-to-fit printing of Web pages to automatically resize the page to print properly. Also, with new integrated support for emerging technologies such as Web feeds (RSS), users of Internet Explorer 7 in Windows Vista will get personalized news, sports, shopping information and blogs delivered directly to their PCs. Internet Explorer 7 in Windows Vista beta 2 will continue to build on the security enhancements with support for anti-phishing, which will help warn and protect users against fraudulent Web sites and personal data theft in the browser. It will also add a Protected Mode to give Internet Explorer sufficient rights to browse the Web, but not enough rights to modify user settings or data. Many of these new browser features will also be available to users of Windows XP through Internet Explorer 7 for Windows XP Service Pack 2. Internet Explorer 7 beta 1 for Windows XP is now available to IT administrators, developers and enthusiasts for testing and evaluation through the Technical Beta Program and MSDN. Windows Server, Code-Named “Longhorn” The first beta of Windows Server?, code-named “Longhorn,” also is now available to a limited number of participants in the Technical Beta Program, including hardware manufacturers, original equipment manufacturers, independent hardware vendors, system builders, independent software vendors and developers. The next version of Windows Server, code-named “Longhorn” is designed to provide a secure and reliable server platform, helping customers reduce IT complexity, increase end-user productivity and deliver rich new applications. The new server operating system is slated for final release in 2007. “Avalon” and “Indigo” Windows Vista beta 1 also includes the first beta of Windows Presentation Foundation (formerly known by the code name “Avalon”) and Windows Communication Foundation (formerly known by the code name “Indigo”), which are part of the WinFX? programming model. WinFX extends the Microsoft .NET Framework with classes for building new user interface experiences and advanced Web services. Together, they enable developers to build connected systems that take advantage of the processing power of the smart client, incorporate cutting-edge media and graphics, and communicate with other applications with improved security and reliability. System Requirements Minimum system requirements will not be known until summer 2006 at the earliest. However, these guidelines provide useful estimates: * 512 megabytes (MB) or more of RAM * A dedicated graphics card with DirectX? 9.0 support * A modern, Intel Pentium- or AMD Athlon-based PC. -- 33333331 Rydia Mar 20. ● 还有地球人在吗? 33333332 SYSOP Mar 20. Re: 还有地球人在吗？ > 33333333 Rydia Mar 20. ● 80岁生日，抢个大整^_^ 33333334 SYSOP Mar 20. ● Rydia被取消在Earth版的发文权限 ※ 来源:·水木社区 newsmth.net·[FROM: 218.13.28.*]
Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.32Bit.DVD.
发信人: KingoM (Spy of Blizzard), 信区: NewSoftware
标 题: Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.32Bit.DVD.
发信站: 水木社区 (Thu Jul 28 08:14:43 2005), 站内
Release Date.....: July 27th, 2005
Directory Name...: Microsoft.Windows.Vista.Codename.Longhorn.Beta.1.
Supplier.........: Microsoft DVD.READ.NFO WinBeta
Type.............: OS
Format.......... : DVD ISO (as supplied by MS)
Number of Discs..: 1
Archives.........: 54 x 50 MB (2% rar recovery record)
Files............: wb winvlhb132bitdvd.rxx
Protection.......: key/wpa
Requirements.....: CPU: 1.5GHz+ / RAM: 512MB+ / HDD: 6gb+
Link.............: http://www.microsoft.com/windowsvista/default.mspx _
Release Notes
__________________________________________________________________
Windows Vista codename Longhorn, the next generation OS from Microsoft
This is Beta 1. Build 5112 for those inclined to such information.
There is 30 day activation protection. The key below works to install
We were offered the antiwpa workaround which we declined as we do not
provide cracks. The folks that offered antiwpa said they will make
it available at the same time as this release in order to allow people
the opportunity to enjoy Windows Vista codename Longhorn Beta 1 for
more than 30 days. Look out for their release if you wish to use it
We recommend you enter the beta program or join MSDN to get your own
legit key which you will be able to activate.
Nukers This must remain an iso or it will not extract or boot.
Enjoy Beta 1. This is an original untouched iso.
--
http://wc3x.3322.org
※ 来源:·水木社区 newsmth.net·[FROM: 218.4.223.*]
my Amateur Windows Vista beta 1 review
发信人: sghaha (不要吧), 信区: NewSoftware 标 题: my Amateur Windows Vista beta 1 review 发信站: 水木社区 (Thu Jul 28 16:42:01 2005), 站内 ZT Well.. before I start.. I have to say.. I obtained the software legally, so please do not post here asking where to download it etc. And.. yes this is my very first review... so its probably lacking lots of things and most of the review is just my rant. Installation: Installing was a breeze, you only need to type in your product key, choose some hard drive partition settings and that's basically it. However, I have to say it took a long time to install, I don't know if its because I'm installing it on my super old hard drive, or if it really is a pain... I waited almost 2 hours for Windows Vista to completely finish installing. The install process was very boring, maybe its because this is the beta version, there's nothing for you to read or look at while its installing, just a green bar on the bottom with its fake progress.. the reason i say its fake its because it keeps filling itself up and empties itself.. basically you can't tell how much is left by looking at the progress bar. First Starting Up Experience.. The first thing I saw when Vista finally started up was a very nice logging on screen, now, there are some things I find really funny, when Vista is logging on, it saids, "Waiting for xxx Service", almost as if Vista is a person himself? I just found it kinda weird for it to say Waiting instead of Loading.. Anyhow, looking at the UI was a shock.. because first of all, I did not expect a completely BLACK taskbar and very ugly large desktop icons.. they honestly look like they were copied from some 12 yeard old that played with photoshop. The first thing I did was obviously open up Internet Explorer 7 which I must say is not bad at all, its a completely new experience.... Internet Explorer 7 I should say, I downloaded IE7 for XP as well but I haven't even ran it yet, after switching my HD back to XP I'll give it a shot and see if its the same as the Vista one. The best thing about IE7 is tabbed browsing which I think is a complete copy from FireFox, there's also a search bar on the right of the address bar which is ALSO a copy from FireFox. Open a new tab from middle mous click on a link is also another copy. Basically, IE7 is what FireFox users wanted in Internet Explorer. I managed to crash IE 7 lots of times by installing the snagit plugin, so I had to uninstall that or I wasn't even able to run IE 7 at all. Definitely worth the upgrade from IE 6, or whatever version Microsoft is on right now. No more "My" If you've noticed.. there's no more, My Documents, My computer, My pictures, etc. They are all just, Documents, Pictures, Computer, Videos, etc. Good move? I don't know.. i've gotten so use to MY everything, its really weird to see just Documents, Pictures, etc. Especially Computer, I keep clicking on Games which is right on top of it, because GAMES was never in the startmenu, which I think is VERY pointless. Who really plays that much of the games that Windows came with anyways? I don't think it needs to be pinned on the start menu. Start Menu The start menu looks really clogged up and too big for my liking, it takes up too much of the screen's space when you open it, and the WORST part is, clicking on ALL PROGRAMS, no longer extends another menu, its crammed into a small box that's inside the start menu itself and it makes finding things REALLY hard and difficult, that's probably why Microsoft included a very ugly search box on the start menu to search for things in the start menu (whats the point?!?! you can't use the search for ANYTHING ELSE!! jUST THE FREAKIN START MENU!) *check screenshots.. it looks REALLY UGLY!!!* Windows Explorer, or "Computer" Well, the visual appeal is awesome! It makes me like Windows all over, well not really, but the re-designed graphics and the famous XP green progress bar looks a LOT better, its animated now and just looks more.. modern. It sorta feels like you're on a mac, and I like that.. although some mac fanboys may hate me for saying this.. but Microsoft actually did a good job in copying apple. Navigating through the folders are really easy (if you get use to it), and once again, looks VERY visually appealing. New Features The new feature that caught me most was Windows Search Indexing "thing" that they had on XP, for Windows XP, the default is off.. but on Vista the default was on.. which I really don't like, I think they are trying to copy Tiger's Spotlight feature and have indexing on all the time so finding files would be really easy, but if you have a loud hard drive like the one I am on now, it really gets on your nerves, so I decided to turn that off. Another new feature is PARENTAL CONTROLS, yes.. parents can now limit the games their kids play by setting the MSRB rating their kids can install/open, so if their kids try installing San Andreas, it will probably give them a nasty error, I haven't tried this feature because I didn't feel like making another account and installing San Andreas on it. The Control Panel has all new re-designed icons.. basically the entire OS has new re-designed icons that look a LOT better on the eyes and just work better. Another thing about the CP is that its now split into so many fricken categories its REALLY hard to find something especially since most of the time you're on the computer, you're not in the control panel, but thankfully, they still have the classic view avaibale for those like me. Added Thoughts.. (keeps growing Added July 28th: Right when I was going to shut down lovely Vista, and use my Windows XP again, I noticed Vista now has a shutdown counter, just like the mac does.. but the counter only counts for 30 seconds where as the mac is 100+ seconds. Great job copying.. I never knew why you needed to wait 100+ seconds till your mac shuts down. Added July 28th: RANT, Why on earth does Windows Media Player need 3 album art pictures?! I think we get the point the song is by Mozart after the first big picture. Overall thoughts Windows Vista is very visually appealing, I will probably not buy the OS for anything over $125, because there really isn't that big of a change.. almost forgot! YES! It is a lot faster than Windows XP, but maybe that's because I haven't clogged it up with junk yet, but from what I remember on my clean Windows XP, it does work a little faster, things seem to be more responsive and images/stuff seem to render a little quicker than Windows XP, plus all the visual effects.. its amazing how microsoft can get the speed it does in Vista. I would recommend people buying it only if they like things that are very visually attractive, or just wait till you get a new computer and have a preloaded. OR.. you can do it the bad way.. which I won't even go into. Enjoy some screenshots! -- ※ 来源:·水木社区 newsmth.net·[FROM: 202.120.3.*]
Windows.Genuine.Advantage.and.Javascript.Workaround.REPACK.
发信人: seu (向阳花木), 信区: NewSoftware
标 题: Windows.Genuine.Advantage.and.Javascript.Workaround.REPACK.
发信站: 水木社区 (Tue Aug 2 10:16:11 2005), 站内
� [ D E E P S P A C E 9 ] �
- ---+-----------------------+---------------- -
Windows Genuine Advantage and Javascript Workaround REPACK iNTERNAL
- <+- --------+----------------------+-------- -+> -
...... | Type : Tool Language ..: Multi? | ......
: | OS ..: XP Crack/SN ..: none | :
. | Date : 31.07.05 Protection : none | .
� PRODUCT iNFORMATiON �
- <-- --------+----------------------+-------- --> -
This is an automated WGA deactivator for all the ppl who use Win XP
and can磘 do Windows Update or MS Security Downloads any longer.
What it does : It simply closes all iexplorer windows, installs the
Program "Trixie" and installs the JavaScript to the Trixie-Folder t
deactivate the WGA-Checks.
You can do this steps manually if you want... You just have to look
on this page (where i got the files and informations)
http://www.extended64.com/blogs/rafael/
I did this iNTERNAL Release because i磎 to lazy to do the steps
manually on each PC... You can decide if you want to use my
silent-script or do yourself manually... It磗 up to you !
This Package has been tested with German Windows XP Pro Corporate,
but it should also work with english or other languages I think.
� REPACK iNFORMATiON �
- <-- --------+----------------------+-------- --> -
Damn, i hate this Fuck ! There was a ; missing in the script...
thats why it didnt run on some machines... So here磗 the fix !
And by the way : Now Installer gives a InfoBox when it磗 done...
� iNSTALL iNFORMATiON �
- <-- --------+----------------------+-------- --> -
Unpack, Read this .nfo and start the .exe
� GROUP iNFO �
- <-- --------+----------------------+-------- --> -
. .
We want to greet all GRPs who know us ;)
. .
: :
:.... <================================================> ....:
. DS9iSO STiLL ROCKiNG LiKE HELL iN 2005 .
:.... . . ........:
--
红 红 专专专 并并并并 进进进
红 红 专 并 进
红 红 专专专 并 进
红 红 专 并 进
红红红 专专专 并 进进进
※ 来源:·水木社区 newsmth.net·[FROM: 202.127.23.*]
Windows.Genuine.Advantage.Validation.Tool.Patch-TWK
发信人: LeonTang (The Blue Danube), 信区: NewSoftware
标 题: Windows.Genuine.Advantage.Validation.Tool.Patch-TWK
发信站: 水木社区 (Tue Aug 2 09:15:59 2005), 站内
░░░░░░░░░░ ░░░░░░░░
░░░░░░░░░░░░░░░░░░░░ ░░ ░░░░░░ ░░░░░░░░░ ░░░░░░░░░░ ░░░░░░░░
░░ ░░ ░░░░░░░ ░░ ░░ ░░ ░░░ ░░░░░░
░░░░░░░░░░░░░░░░░░░ ░░░░░░ ░░░░░░░ ░░░░░░░░ ░░░░░
░░░░░░░░░░░░░░░░░ ░░░░░ ░░░░░ ░░░░░ ░░░░░
░░░░░ ░░░░░ ░░ ░░░░░ ░░░░░ ░░░░
░░░░░ ░░░░░ ░░░░ ░░░░░ ░░░░░ ░░░░░
░░░░░ ░░░░░ ░░░░░ ░░░░░ ░░░░░ ░░░░░
░░░░░ ░░░░░ ░░░░░░ ░░░░░ ░░░░░░ ░░░░░░
░░░░░░░ ░░░░░ ░░░░░░░░ ░░░░░ ░░ ░░░░░░░░░░░░
░░░░░░ ░░ ░░░░░ ░░░░░░░░░░░ ░░░░░ ░░░░░░░░░░░░░░░
░░░░░░░░ ░░░░░░░░░░░░░░░░░ ░░░░░ ░░ ░░░ ░░░░
░░░░░░ ░░░░░░░░░░░░░░░░░░░░░░░ ░░░░░░░░░░░░░░░░
░░░░░ ░░░░░░░░░░░░░░░░░░░░░░░ ░░░░░ ░░░░░░░
░░░░ ░░░░░░░░░ ░░ ░░░░░░░░░░ ░░░░░ ░░░░░
░░░░░ ░░░░░░░░░ ░░░░░░░░ ░░░░░ ░░░░░░
░░░░░ ░░░░░░░░ ░░░░░░░░░ ░░░░░ ░░░░░░░
░░░░ ░░░░░░░░ ░░░░░░░░ ░░░░░░ ░░░░░░░░░
░░░░░ ░░░░░░░░ ░░░░░░░ ░░░░░ ░░░░░░░░░
░░░░░ ░░░░░
░░░░░ ░░░░░░
░░░░░░░ ░░░░░░░░
░░░░ ░░ ░░░░ ░░░
░░░░░░░░ ░░░░░░░░░
TWK PROUDLY PRESENTS:
┌──────────────────────── ------------------------- ────────────────────────┐
│ │
│ Windows Genuine Advantage Validation Tool(KB892130) PATCH │
│ │
├─────────────────────────────────────┬─────────────────────────────────────┤
│ │ │
│ Release Date :01.08.2005 │ TUPE : PATCH │
│ Release Size :01xXXMB │ Protection :CRAP │
│ │ │
└─────────────────────────────────────┴─────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│--- - RELEASE NOTES - ---│
└───────────────────────────────────────────────────────────────────────────┘
Windows Genuine Advantage Validation Tool use Windows XP and can't do
Windows Update or MS Security Downloads any longer winout legit serial key.
┌───────────────────────────────────────────────────────────────────────────┐
│--- - RELEASE iNFO - ---│
└───────────────────────────────────────────────────────────────────────────┘
1. Unzip, Unrar.
2. Locate \WINDOWS\system32\LegitCheckControl.dll
3. Close all iexplorer windows, run twk-winupdatepatch.exe .
4. Enj
--
※ 来源:·水木社区 newsmth.net·[FROM: 218.193.190.*]
Windows XP SP1 ISO 版安装心得
发信人: soff (今年大四明年大三), 信区: NewSoftware
标 题: Windows XP SP1 ISO 版安装心得
发信站: BBS 水木清华站 (Sat Jun 8 14:29:35 2002)
其实没有想象中那么恐怖，我用的是英文 XP 2600 corp
1、运行 deactivate.reg 文件来取消掉原有的激活信息；
2、运行 %systemroot%\system32\oobe\msoobe.exe /a 进入激活画面，选择第二项电话
激活；
3、在接下来的窗口中，选择 change product key 来修改序列号，新的序列号是
K2KB2-BDBGV-KP686-D8T7X-HDMQ8，输入完毕，点击 update 进行更新，完成之后再点击
remind me later，之后重起机器；
4、机器启动完毕以后，再次运行 %systemroot%\system32\oobe\msoobe.exe /a 进入激
活画面，现在应该显示已经激活的信息，到这里基本上成功了；
5、接下来就是升级了，运行光盘中的 update 目录下的 update.exe 执行安装程序，安
装程序首先会检查序列号是否合法，接下去就开始安装了，包括检查系统、备份文件、
停止服务、安装文件以及完成安装，安装完毕以后，需要重新启动机器；
6、机器启动完毕以后，首先告诉我 StyleXP 不能用在这个版本的 Windows XP，实在是
分特呀，别的 Visual Style 也都不能用了，系统的 shellstyle.dll 版本号没变，但
是大小变了，试着用其覆盖 Visual Style 下的相同文件，但还是不管用，看来只有期待
更新了；
7、查看 About Windows 窗口，显示的版本是 Version 5.1(Build 2600.xpsp 1.020529
-1810: Service Pack 1, v.1050)；IE 的版本号为 Version: 6.0.2800.1050.xpsp 1.
020529-1810，别的就没看了，总体感觉还是挺爽的 :P
--
____ ____ __
_____ ____ / __// __/ ____ ___ / /_
/ ___// __ \ / /_ / /_ / __ \ / _ \ / __/
(__ )/ /_/ // __// __/ _ / / / // __// /_
/____/ \____//_/ /_/ (_)/_/ /_/ \___/ \__/ 珊瑚虫工作室[Coral Studio]
※ 来源:·BBS 水木清华站 smth.edu.cn·[FROM: 211.68.9.136]
Windows Longhorn，图形功能大幅加强
Windows Longhorn，图形功能大幅加强 http://xml.sz.luohuedu.net http://www.erp800.com/net_lover/ Longhorn强化了图形功能。新图形画面与现有版本Windows截然不同，看起来非 常漂亮。在WinHEC的演示中，使用早期测试版本演示了高级动画效果，流畅地放大和 缩小窗口尺寸，以及显示半透明窗口等。 现有版本的Windows都是在单独的桌面界面上显示Windows桌面。因此，每个窗口 分别使用单独的界面，以确保自己的显示区域。另外，各窗口只能在没有被隐藏于其 他窗口的“自己的区域”中显示。 而Longhorn则是各窗口均确保固有的界面。各窗口完全独立，不管有没有其他窗 口，都可随时显示整个窗口。同样在桌面画面中，所有打开的窗口在1秒钟里多次同 时连续显示。 当然，这样变更后的Longhorn与现有版本的Windows相比，必须具有性能极高的 图形资源。但是，微软解释说：“由于目前几乎所有的PC均支持3D图形功能，因此没 有任何问题”。不支持3D图形功能的PC尽管无法完全利用Longhorn的全新图形功能， 但微软表示可以通过在图形功能中设置多种模式来解决。 模式有3种。“标准模式（baseline mode）”只能使用与Windows 2000相同的功 能。此时只使用软件显示功能。更高一级的为“一级体验（tier 1 experience）” 模式。提供部分Longhorn的全新图形功能。所要求的3D图形硬件配置基本与“DirectX 7”所要求的配置相同。一级体验中还包括面向笔记本电脑的“低耗电模式”。“二 级体验（tier 2 experience）”模式能够使用Longhorn的全部功能。二级体验需要 最高级的硬件配置，与“DirectX 9”所要求的配置相同。 此次演示使用的是“Longhorn build 4015 desktop”。该版本Longhorn在窗口 切换时，各窗口如同迎风飘扬的旗帜，一边飘荡、一边在画面中显示出来。窗口的透 明度包括多种等级，其表现力应该是现有Windows中效果最好的。 另一个重要之处是，放大和缩小窗口尺寸后，其显示特性不会受到任何影响。也 就是说，现有版本的Windows需利用任务栏中的按钮选择最小化画面，而Longhorn即 便将画面最小化以后，仍能直接在最小化状态下准确地判断其画面上显示的内容。 现有应用程序不需任何改进，即可利用Longhorn的全新图形功能，这一点也尤为 重要。也就是在Longhorn上运行的所有现有应用程序均能够自动地使用全新动画功能 和透明功能等画面效果。此次演示所用的应用程序都能够在Windows XP上运行。包括 记事本、命令行和任务管理器。 另外，播放“星战前传II”动态图像的演示也意义非凡。这是因为即使一边实时 播放动态图像一边起动其他应用程序，动态图像的播放速度和显示质量也没有受到任 何影响。另外，演示所用的是硬件配置较低的电脑，采用工作频率1.5GHz的Pentium 4处理器，384MB内存，显卡为“ATI Radeon 9700”。这一点令人非常吃惊。
微软安全架构——Palladium
微软安全架构——Palladium http://xml.sz.luohuedu.net http://www.erp800.com/net_lover/ 保存在计算机中的信息总是面临着外泄的危险，有时连机密文件或是信用卡号码 等价值很高的信息也不能幸免。守护机密信息的保护功能会因安全漏洞的发现而变得 不堪一击，阻止外泄信息造成危害的数据加密功能有时也会徒有其表。比如，保存在 内存及硬盘中的密码数据一旦被盗，加密也就没有任何意义了。 因此，人们希望能从软硬件两方面着手来打造安全的个人电脑。美国微软2002年 7月刚刚公开了开发概要的新安全架构“Palladium（帕拉斯女神，开发代号）”。帕 拉斯女神指的是因特洛伊木马而闻名的古代城市特洛伊城的守护神。正如开发代号的 含义一样，其目标是建立一个可以起到防止数据非法泄漏的防火墙作用的安全架构。 制造机密数据的“保险柜” 在Palladium构想中，把用于认证和加密的加密密钥的基本信息作为硬件预先嵌 入个人电脑。购买支持Palladium的个人电脑时，个人电脑独有的加密密钥就会被写 入到这枚硬件芯片上。通过这个加密密钥，支持Palladium的OS可对运行于其上的程 序进行认证，并加密保存机密数据。具体而言，也就是说支持Palladium的OS将会设 置一个只有已经得到认证的程序才可以访问的保护区域。而保存在保护区域中的数据 都是经过加密的，即使被拷贝到其他电脑上，也无法还原。 关于基于硬件的安全功能，微软目前没有公开详细架构。不过，按照该公司持有 的于2001年12月得到批准的、被公认为Palladium基本专利的“Digital rights management Operation Sytem”（美国专利号：6330670）来推断，有可能是在CPU中嵌入加密密 钥的基本信息。也有可能不是在物理上将其集成到一个CPU上，而是嵌入到由CPU和专 用接口组成的专用芯片中。 作为选项标准，还准备有与外设进行数据交换的加密功能。键盘和显示器也是机 密数据被盗的途径。如果将支持Palladium的个人电脑和外设配合起来，那么就可以 通过对击键和图像数据进行加密，来追加防止信息泄漏的功能。 除硬件和OS外，应用程序的支持也不可或缺。要编辑Palladium生成的保护区域 ，就必须经由名为“Trusted Operation Root(TOR)”的Palladium管理程序（使用Palladiu 的API）。而不支持Palladium的现有应用程序则无法访问保护区域。在运行不支持Palladiu 的应用程序时，TOR会把内存中的保护区域数据隐藏起来。 将集成到Longhorn中！？ 如上所述，要想实现Palladium构想，就必须在硬件和软件两个方面同时具有支 持Palladium的产品。如果Palladium构想得不到第三方的信任，那么就将无从实现。 要想得到对Palladium构想的支持，方法有两个。一个是通过目前该公司向合作 企业提供的源代码公开计划“Shared Source Initiative”，公开Palladium核心程 序——TOR的源代码。另一个方法是在第三方机构的监督下对Palladium架构进行试验 。在硬件方面，微软目前已经开始分别与美国英特尔和美国AMD联合制定支持Palladium 的硬件规格。 实际上具有Palladium功能的OS最早也要到2004年才能亮相。微软已经将Palladium 定位于用于普及.NET的安全强化策略“To trust.NET”的核心技术。关于To trust. NET，由于微软已经表示“力争在未来3年内实现这一策略”（微软公司负责平台策略 部门的副总裁Sanjay Parthasarathy），因此定于2004年下半年开始供货的Windows 下一版本“Longhorn（开发代号）”极有可能成为支持Palladium的OS。 同时支持Windows外其它OS的标准已先行亮相 除了Palladium以外，业界还在尝试利用硬件标准来构筑安全架构。这就是由制 定电脑标准的安全架构的业界团体“TCPA（值得依赖的计算平台联盟）”所制定的安 全的个人电脑标准。 TCPA是于1999年10月由美国康柏、美国惠普、美国IBM、英特尔及微软共同发起 成立的。截止2002年7月，已经有180多家硬件及软件制造商加入TCPA。尽管微软已经 作为TCPA的一员加入TCPA，但却采取了推进Palladium构想的立场。 TCPA所制定的“TCPA Main Specification”是用于确立名为“Trusted Platform Module(TPM)”的硬件级安全架构的标准。在IBM开发的安全技术的基础上，TCPA于 2001年10月公布了该标准的1.0版本。除具有生成加密密钥的功能外，TPM还可以高速 进行数据加密和还原。另外，还可以作为用于保护BIOS和OS不被修改的辅助处理器来 使用。在这方面IBM已经先行一步，该公司已经将集成有密钥数据和加密处理功能的 、符合TCPA标准的TPM芯片，作为“安全芯片”集成到了该公司的个人电脑中，并且 已经开始供货。 TCPA与Palladium的区别主要有如下两点：（1）TCPA制定的标准保证电脑在OS起 动前的安全，而Palladium的保护重点在于OS的起动过程和起动后的工作过程；（2） TCPA同时支持Windows之外的其它OS。 目前，TCPA尚未制定以TPM为前提的OS和应用程序的安全标准。目前正在制定中 的TCPA Main Specification V1.2将追加与软件有关的规定。 关于TCPA，微软表示：“Palladium并不是与TCPA相对立的标准，而是对TCPA的 补充”（微软Palladium业务部门总经理John Manferdelli）。 Palladium--彻底修改PC架构 为了实现Palladium计划，需要得到很多硬件及软件的支持。如果可能的话，它 将作为预定于2004年供货的下一代Windows--Longhorn的一部分嵌入。微软产品经理 Mario Juarez称：“Palladium不仅可以解决问题，还可以扩展人们在生活及工作使 用计算机的范围”。 微软将按照如下的方针设计Palladium： （1）通过Palladium，可以确认用户正在使用其应该使用的PC。另外，用户在使用网 上获得的信息之前也要通过确认。 （2）Palladium为了防止数据被窃听或窃用，将对经过签名的数据进行加密保护。为 了防止文档在用户不知情的情况下被篡改，系统将维持文档的完整性。 （3）Palladium能够防止病毒及蠕虫的入侵。由于不会执行未经系统承认的程序，因 而可以防止病毒破坏系统。 关于TCPA，微软表示：“Palladium并不是与TCPA相对立的标准，而是对TCPA的 补充”（微软Palladium业务部门总经理John Manferdelli）。 Palladium--彻底修改PC架构 为了实现Palladium计划，需要得到很多硬件及软件的支持。如果可能的话，它 将作为预定于2004年供货的下一代Windows--Longhorn的一部分嵌入。微软产品经理 Mario Juarez称：“Palladium不仅可以解决问题，还可以扩展人们在生活及工作使 用计算机的范围”。 微软将按照如下的方针设计Palladium： （1）通过Palladium，可以确认用户正在使用其应该使用的PC。另外，用户在使用网 上获得的信息之前也要通过确认。 （2）Palladium为了防止数据被窃听或窃用，将对经过签名的数据进行加密保护。为 了防止文档在用户不知情的情况下被篡改，系统将维持文档的完整性。 （3）Palladium能够防止病毒及蠕虫的入侵。由于不会执行未经系统承认的程序，因 而可以防止病毒破坏系统。 （4）Palladium可以阻截垃圾邮件。在垃圾邮件进入邮箱之前采取防御措施。如果持 有符合用户设置标准的证书，则未经申请发送来的邮件也可以被接受。 （5）Palladium可以保护个人隐私。除可以在PC上给数据添加签名外的功能外，还可 以使用确保数据只传送给指定用户的被称为Agent（代理程序）的软件，给经由因特 网发送的数据添加签名。《新闻周刊》给Agent软件起了个绰号，叫做“My Man”。 （6）在信息由PC发送之后，Palladium仍可以对信息进行控制。使用被称为“Digital Rights Management”（DRM）的技术，可以经由因特网安全地发送音乐、图像以及 其它的知识财产等。比如，电影公司及音乐行业可以使用此技术使顾客在不侵害音乐 CD及电影的著作权的范围内进行复制。另外，还可以保证个人的电子邮件不会被其他 人任意复制及转发。据《新闻周刊》报道，“用户也可以设置为制作出Word文件后， 在下周之前别人无法读取。不管在什么场合下，设置的主动权都掌握在用户手中，而 不是由微软来控制”。 Palladium提出的这些设想并不是新概念。如果要说这个系统有什么特别之处的 话，那么唯一的新东西就是微软将业界统一到其技术的周围、并一直坚持到实现为止 的能力。 芯片制造商--美国英特尔及美国AMD已经决定支持Palladium。另外，虽然未公布 名称，但在安全成为最受关心的问题的金融服务及健康管理、政府等领域，微软的主 要合作伙伴已经同意支持Palladium。 但是，Palladium能否成功还没有任何保证。由于旷日持久微软案以及日渐增大 的对安全问题的担心，反对微软的呼声日渐高涨。而且由于Palladium是Windows独有 的技术，毫无疑问这将进一步扩大微软对OS的支配地位。 对此，微软认为Palladium可以方便地移植到其它的平台上，并以此回击外界的 指责。Palladium 的软件设计师Willman Presumably表示：“Palladium可以嵌入Palm 、电话和手表中使用，这一优势不可忽视。另外，我们还正在考虑向Linux及Macintosh 移植的问题”。 微软将发布新一代安全技术Palladium的SDK 美国微软有可能会在今年10月份提供旨在彻底改善Windows机器安全性的“新一 代安全运算基础（Next Generation Secure Computing Base ，NGSCB ）”（开发代 号：Palladium）的有关信息。微软将于10月份在该公司面向开发者的会议“微软专 业开发者会议（Microsoft Professional Developers Conference，PDC）”上，公 开NGSCB最初的软件开发工具包（Software Development Kit，SDK）。该SDK将成为 面向程序员的NGSCB代码的首次公开展示，运行时可编写具有特殊功能的程序及服务 。 NGSCB不光对OS等软件，在硬件上也安装专用技术，可实现更加强大的安全及保 密功能。可对文件及数据进行自动加密，防止非法复制及篡改。按计划，NGSCB将于 2005年底作为Longhorn的选项功能亮相。不过，必须使用符合NGSCB规格要求的PC。
Longhorn_4051_PDC_WINBETA.iso@eea
发信人: cubehead (方腦殼), 信区: NewSoftware
标 题: Longhorn_4051_PDC_WINBETA.iso@eea
发信站: BBS 水木清华站 (Mon Oct 27 16:10:44 2003), 转信
nfo
#####
#############
#############
############# ### ###
############# ###############
############# ##############
############# ##############
############# ##############
### ### ##############
###### ##############
############# ##############
############# #######
############## ### ###
############# ##############
############# ##############
############# ##############
############# ##############
## ## ##############
# ##############
#############
#######
_ ___ ____ __
| | / (_)___ / __ )___ / /_____ _
| | /| / / / __ \/ __ / _ \/ __/ __ `/
| |/ |/ / / / / / /_/ / __/ /_/ /_/ /
|__/|__/_/_/ /_/_____/\___/\__/\__,_/
/-----------------------------------------------------------------------------------\
| Microsoft Windows Longhorn PDC build #4051 |
<----------------------------------------------------------------------------------->
| - Source: Microsoft - Type: Operating System |
| - Packaged By: winbeta - Image Format: ISO |
<---------------------------------------------------------------------------------->
| - Files: Longhorn_4051_PDC_WINBETA.part15.rxx |
| - Number of CD's: 1 - Protection: WPA |
| - Archives: 45 x 15 MB - Release Date: 10/25/03 |
<----------------------------------------------------------------------------------->
| - Review: http://msdn.microsoft.com/events/pdc/ |
<----------------------------------------------------------------------------------->
| - Hardware Requirements: 600+ Mhz CPU, 128 MB RAM, 1.5 GB HD Space |
<----------------------------------------------------------------------------------->
<---------------------------- R E L E A S E N O T E S ----------------------------->
PDC 2003 is being widely heralded by the development community as a "must-attend"
event for enterprise developers, software architects, software engineers, Web
developers, and Web development managers wanting to stay in sync with Microsoft's
platform roadmap.
Be one of the first to look under the hood of "Longhorn."
"Longhorn" is the code name for the next major release of Microsoft Windows畻and
the innovation runs deep. At PDC 2003, you can be the first to get information on
how to build your applications to take advantage of "Longhorn," and be ready for
the future.
Get up to speed on the next-generation database capabilities of "Yukon." With deep
XML support and Common Language Runtime integration, the next release of Microsoft
SQL Server, code named "Yukon," will take programmability, scalability,
availability,and business intelligence to the next level.
Experience the future of application development with Visual Studio "Whidbey."
Extend your power and productivity with upcoming versions of Microsoft Visual
Studio�. Unleash the power of advanced Web services, harness business processes,
and transform database programming with "Yukon." See the latest innovation in
Visual C#�, Visual C++�, Visual Basic�, and other programming languages.
Take Web services to the next level with Microsoft .NET connected software. Web
services have become the industry choice for connecting systems. At PDC 2003,
you'll see where Web services are going next, with new capabilities, advanced
infrastructure tools, and new opportunities.
Get early code
PDC attendees have always been the first to get developer previews of important
future products. The tradition continues with PDC 2003梘et early, and in some cases,
exclusive code for Windows "Longhorn," SQL Server "Yukon," Visual Studio "Whidbey,"
and other technologies.
A great value.
Your PDC 2003 ID gets you into a keynote address on the next generation of computing
from Chairman and Chief Software Architect Bill Gates, as well as break-out sessions,
exclusive parties, interactive labs, a full-service food court, and much, much more.
<----------------------------- I N S T A L L N O T E S ---------------------------->
1.) Unpack.
2.) Burn to CD.
3.) Install.
4.) Use this CD-Key:
4.) Enjoy!
<------------------------ ENJOY ANOTHER FINE RELEASE BY WiNBETA --------------------->
| Do More for less |
\------------------------------------------------------------------------------------/
Contact us at winbeta@winbeta.org
--
かつて、純潔な愛が俺の前に置いていたが、大切にしていなかった。あの愛を失った
時、どんなに後悔したか、分かってきた！世の中に一番つらいことは、これしかない
と思う。お前の剣が、俺の喉から切ってくれよ！もう猶予しないぞ！もし、神様から
、もう一度やらせる機会がくれれば、俺は、あの女の子にそう言うのが決まっている
――愛してる！もし、この愛に期限を付けなければならなかったら、俺の希望は：一
万年だ！
※ 来源:·BBS 水木清华站 smth.org·[FROM: 211.66.31.197]
longhorn4051cdkey
发信人: woshishuaige (帅哥), 信区: NewSoftware
标 题: longhorn4051cdkey
发信站: BBS 水木清华站 (Sun Nov 30 09:52:49 2003), 转信
CD-KEY:
RYXQH-P87BC-6223X-CFCGW-PP28Y
WJ66G-DCFVX-YMHWT-VCDBP-PYKR4
WJJ6M-XD26K-WJQY7-DVC3R-3CC44
PDW2X-JYPRK-PTBHY-TCV4Q-JMVJP
XJWPD-7GTB6-DJG7K-D8FR4-DCWKM
67FQF-WWY62-TRGT2-H3Q2W-2B8KG
8CD6H-BXYMB-R4TGD-2JWGF-TXQQM
8GB3T-4GXPQ-F433T-PF48C-TRQD2
PFGYH-P328R-F4YXY-6QC2K-Y22VY
3DFQT-CCV6T-HBGC3-MX8KK-MW7VK
7QYRX-G7VWX-6TKTK-T6P7C-WRBB9
XGBP3-FDMC6-MGFD6-HMKBW-JWJD7
RW6K6-3H2KT-GPTTR-GBDHQ-2366M
H4FT2-7X7JX-T78MB-847CR-3BJK4
KMFVH-7W78D-WM36T-V2DQH-J28MY
MJHG3-MJX7V-XGXM7-W343X-V779D
7FRPK-WVC2Y-DYMGD-BCCJ7-3934J
V4WQM-BXDCW-M3Y8C-Q4M3T-WP8X2
BDT2X-WWPKR-FKW82-DCW8F-VQRFR
K24GK-M8XX8-R6MTG-2QGK6-B293D
FTD8T-MM2P8-8RC86-R3H3J-FKK4W
C4FP2-TW4QP-CPDCM-F6XWG-THFC2
WXJMG-KD8TY-Y6D8F-XBW6J-FJ833
CWRKT-YQGBR-T8YY8-W643V-DYYFR
PHTKD-CM2HG-J77P8-CKBBJ-78XMB
HG8TC-8PGVH-YB4DY-RVRTQ-V4926
WVQ6X-CWRXH-PQCDP-XQPQD-764YC
77WBF-FP28Y-PJT4B-PHWCT-VDGHG
J2QV2-RX7YY-F8RX2-DXXV6-28HVM
V8DV6-QVKGB-X8P36-D6BHP-HPD7X
HKWKM-4K3M6-YWVJ8-WYDRG-BYDMT
HKWKM-4K3M6-YWVJ8-WYDRG-BYDMT
6K6WB-WVX77-WCD34-XQWDR-BGD8Y
6K6WB-WVX77-WCD34-XQWDR-BGD8Y
T3KRQ-WBT32-JP4RM-RJXGF-CYVBX
7R2HX-7H2PJ-VBD73-XTGJM-MQ36T
R6YD2-DV2CW-VCFR8-QMCQW-GKJFH
BBKBK-KXRFP-HCT7G-82WJ4-TJXHQ
6XVH3-RC264-P2T3M-7DW3Y-CR7BF
CQ42R-3TBGW-364Q2-Y4RCP-4R23X
VGXJH-G2JDC-XTFDB-GMJGM-WCG27
CG7MR-XGTX7-RTPCK-CXT6W-86BRX
Q8CTQ-82K6F-MCF87-47V47-MPPFR
W64C6-78YCB-H7CPR-6PCFR-X66VP
22B33-2RFM2-38J27-PC666-2VYG3
MRPVT-MQKKW-FMRGJ-7PGVW-9CVDD
QMC4H-H2TDF-DMPM4-4Y8PQ-GDFG4
8787G-TTK8K-Y4R4G-T763P-H4QGT
HTGBX-MQD6V-KK27R-7GFT4-W9XD6
KJT2M-YK8XF-CW4DW-HRG4C-VCFTC
26PRY-RVVCF-VC63V-CRWJW-3Q8XJ
6K288-7Y3GW-27BGC-HT646-48RM6
RRG8Y-QD3VT-X8KD2-FKY8G-HDGWK
CV4WQ-WRW2B-HR26C-7HV2D-WRCKC
2CQBW-J8X86-K6JG7-2MMDB-F4YBV
7V7VV-JD3QJ-FB2DG-TWMTB-3WCXC
HJ8JT-DDWC7-HMKWV-TJXKX-BJV4H
C83Y2-GKKFY-HRD4X-KC7TJ-YY6F3
HVFY4-2MMBX-KWK26-HYF2M-7KYHC
M63BW-CF4PD-QVR3H-4KR3W-BW329
HFHMX-BW6PH-Q727H-RFYHY-2M4V7
H6BDC-88J6W-8TMBH-W7RJP-W8K3G
M6BDX-VJ7MG-V3TWJ-P8WXC-C7KHJ
PPYJC-FFHDQ-M7CRR-H4F66-J9RRF
MC83G-RWCJW-33MFB-YF4D3-YKPV8
PP83Q-3PP24-PVMK4-4W6DP-GMRHR
R6T4Q-XYD4Q-YRPDG-62GQP-YVHWY
PFXMH-GQWRJ-34FHR-FHRMR-VCCKV
BYMMK-74BH8-D4KHH-J2TQ4-C68Q3
3X7TG-YWCYP-7KY3P-RTRYK-TW23D
P8GKH-KD6XC-VRWTY-KD4VP-7837H
8PBVM-DD46V-TVQFC-YHDJC-M4X33
B2QM8-RKYYG-2KF2T-PDPVH-MYD2Q
GG82Y-6GTTC-XDCH2-WW7BG-C87TF
CGXDD-2V46G-J2GK7-TPCXY-F66HF
WKMJK-4JR28-VJ23C-474JF-BPPJB
G6HD4-FWTJJ-XPMPQ-HPMWD-GG4F2
W6FW3-Y7MR8-YFW4H-7TQ4J-MDV47
BM3PD-H8FP3-C4FRY-TDJ8Y-WDK8T
72R3X-BCYXM-47DFH-7JKKR-MGP7F
H4VVC-XQT79-J4YM6-FWH4X-HYRPY
764KR-MBPC6-2FGYC-2F7FJ-CJT9Y
6TDKX-WFFYJ-MC8RM-WHGCW-D2PHW
MJP6G-67XYV-WG8DW-D78PK-H94BQ
HQMRJ-GG46R-P8H6C-HCBQG-MG2PC
7Y3P2-74TF6-X38MD-TQ3FY-WCHBX
D3KCP-QXTRH-PDFXW-YF78H-8D4HM
8X73K-DTMXX-WBDM3-MYKRT-WVG87
CK8TC-CR72D-67BQ6-TFWKW-J9RVW
CCFDF-GPVFY-DD6GT-C2TX3-V43QG
7WX4K-2QMX8-Q6XJ6-XGBMT-DPH9V
47FRH-6PR26-688F8-4VFFF-P87BK
6KMDM-MCPGY-KJF8B-TG63C-VXXKP
KMDBT-T424V-VH43M-6CXJH-R6W29
848VR-VW3KD-YC423-YDWVK-DQM22
XMDW2-433F4-X3V6P-23QQK-V9THQ
PMHKJ-MFWHR-BY6GF-C6HB7-BVPPW
838CP-KVDYX-BH3HB-MDMHX-7C7XH
4V3BY-CVH3G-GGPRV-PTFQJ-JBVWK
4DFXW-X7BDK-BT6QY-JXGB3-Q8R96
XYRG6-YYFG2-8BC66-RDKB4-4447K
RWXGF-8HG38-DMB73-QGQXC-PHDMX
43K7D-DD3Q3-GD6KM-Q43GM-RD9TR
44GVV-WCYCF-WD3H2-PMQRG-JM7KR
8M4T6-BP66W-MFGQV-36JMT-37CGF
C76T6-YH34G-787HC-DQKVR-7YYJ2
JJ834-T3BYV-JV836-YD6XP-F4VB6
R463C-XQGTY-XYJ7W-PRP66-86WXW
8CJRG-FH7JY-2K864-FBMYM-WX88M
6PHPW-WBQWQ-XDXX6-QVQRQ-CP6DX
D82XB-HQ8DB-C77RJ-2BTM4-MB7VB
RGW6G-GX8YJ-RY8CP-R2BKP-HGYBX
B32Y6-RBW88-DKRGQ-GQBWK-XJ3XK
RQWKK-G8HGH-6KTYF-KMKMY-M7PMP
YVFQ3-6Q3CK-4T2GP-X2JCC-2WDYT
CF4RV-682GP-TM2QV-WRBKH-XPMY9
6V283-F67TB-7WJ2P-Y3FR6-QG2QQ
BRR6D-88XDC-BBCYG-R8K7V-24RYM
7D4VF-CGJV8-XD7RJ-7KGFV-VF92T
TRCT7-DCGXJ-2GPTB-Q26KC-C9P8K
K7RPB-CDPQC-GG6CK-48BP2-CRFM2
HHK4Y-MYJ47-3F6KH-3Q26X-DTXMX
--
●˙ 呵呵，累并且快乐着。
˙●
˙● ╭──┄┄┄┄┄┄┄┄┄
●˙╭╮ 让 自 己 快 乐 ╰────────╮
╭╮┣╯╯ 让 自 己 飞 ╰╮
╰╰┫ ←─────────────────────────╯
※ 来源:·BBS 水木清华站 smth.org·[FROM: 218.75.124.146]
激活 Microsoft Longhorn 4029<zz>
发信人: mrzhu (小色一狼), 信区: NewSoftware 标 题: 激活 Microsoft Longhorn 4029<zz> 发信站: BBS 水木清华站 (Tue Sep 16 11:22:02 2003), 转信 This should work to crack activation for Longhorn beta 4029 1) Boot into safemode using the F8 Key 开机用f8进安全模式 2) Use the File TweakNT.exe and make sure Remove Timebomb is checked and click on covert to: and click Home Edition. Then Click Apply. You will Get a few Prompts after that, just hit ok. 运行TweakNT.exe 并且确保“Remove Timebomb ”是打勾的，选转换到Home Edition，点“应 用”，然后直接点“OK” 3) Use the File Win XP Activator.exe you may get a error..ignore it. 运行Win XP Activator.exe ，忽略错误 4) go to start,run and type in cmd 点“开始”－> "运行"->CMD（命令行界面） 5) type in "net user <makeup a username> <Password> /add" Example: net user Long Horn /add 创建一个用户，照这个输入命令就行了 6) after that it should say command complete succesfully, now type in "net localgroup administrators <username u entered above> /add" For example: net localgroup administrators Long /add 给这个用户加上管理员权限 7) Reboot and let windows boot up normally, now u should see a promt to enter a password for the username you put in, do that and you should be in If it worked allright u should get in ok without any problems! CONGRATS! 重启就行了 -- 忍看朋辈成新郎， 怒向……觅小妞！ ※ 来源:·BBS 水木清华站 smth.org·[FROM: 219.245.42.160]
说说关于Longhorn 4029 的问题
发信人: sghaha (阿笨), 信区: NewSoftware 标 题: 说说关于Longhorn 4029 的问题 发信站: BBS 水木清华站 (Sun Sep 21 11:53:31 2003), 转信 当你们装好Longhorn 4029，然后按照CRACK的提示， 在F8安全模式下，利用tweaknt顺利绕过激活验证，进入桌面。 然后再想连接网络用CPP KEY 进行激活时，是不是总是失败？提示你KEY错误？ 为什么呢？现在leaked out 出来的这个Longhorn 4029版本其实早给做了手脚了。 大家可以比较一下ISO安装目录\sources\与系统目录\windows\system32\ 的两个pidgen.dll有什么不同？ 1、日期不对。 ISO安装目录\sources\pidgen.dll是9月13日， 分明去其他文件有太大区别。别的都是7月16日 而系统目录\windows\system32\pidgen.dll是6月25日，和其他系统文件一样。 2、内容不同。 我用compare软件比较过。差的太多。 2、算法不同。 ISO安装目录\sources\pidgen.dll是.net算法， 因此支持所有.net3763以下、longhorn 4015以下的KEY，包括可激活的CPPKEY。 系统目录里\windows\system32\pidgen.dll是什么算法呢？我不知道。但是所有.net3763以 下、longhorn 4015以下的KEY：比如CKY24-Q8QRH-X3KMR-C6BCY-T847Y什么的都通不过验证 。 呵呵，但是我告诉你们一个真正可以用的KEY，（当然它的激活次数已经超过了） PP6PW-38JHD-DR2WB-XFJXF-DJ9RJ PID=55034-103-0000365-58670 看到这个PID是不是很熟悉？ 其实和你装的Longhorn 4029里的一样。 无论是用CKY24-Q8QRH-X3KMR-C6BCY-T847Y还是其他的CPP KEY来安装， 最后的结果就是生成唯一一样的PID：PID=55034-103-0000365-58670 为什么？因为LONGHORN采用的是WINPE预安装模式，其\source\install.wim安装文件 就相当于一个ghost的镜像。其安装过程是： 1、把安装文件复制到C盘（以$开头的那几个目录） 2、重新启动，开始WINPE预安装模式，把安装文件复制到目标硬盘。 并在目标硬盘的根目录生成sysprep目录，里面有sysprep模式的选项。 如果你在这一步结束后，下一步开始前，进入另一个系统，如XP 看看这个sysprep目录里面的unattend.txt，就可以找到 [UserData] FullName = "Preinstall" OrgName = "Preinstall" ComputerName = * ProductId = "PP6PW-38JHD-DR2WB-XFJXF-DJ9RJ" 这样的信息，大家看到真正的KEY了吧？ 3、重新启动，开始以sysprep的工厂模式安装：硬件检测和安装组件、保存设置等等。 4、安装完毕，重新启动，进入WINDOWS。 也就是说，无论你们采用什么KEY来装，最后还是会变成原本这个ISO预置的KEY： PP6PW-38JHD-DR2WB-XFJXF-DJ9RJ 而之所以这个4029的longhorn安装完毕如果直接在正常模式下进入系统，就要你激活 那是因为制作这个ISO时没有重新设置激活期限，以至成了一个副本。嘿嘿！ 如果你已经用Win XP Activator.exeCARCK 过 LONGHORN 4029，想激活，就要先把 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents的值 去掉最后两个字节，然后再运行 oobe/msoobe /a 这个LONGHORN 4029的SETUP.INI和4015是一样的： [Pid] ExtraData=65796D7176796A7A6D616191E8B8EF Pid=55034270 可以想象吧？ -- http://www.xk76.org ※ 来源:·BBS 水木清华站 smth.org·[FROM: 218.186.177.90]
常见WIN OS@MSDN SHA1/CRC
发信人: CNote (I'm a PC), 信区: NewSoftware
标 题: 常见WIN OS@MSDN SHA1/CRC
发信站: 水木社区 (Fri Jan 9 05:45:10 2009), 站内
常用 MS OS filename/SHA/CRC @MSDN
主要用于方便检查下载正确/完整性。
win2k 的由于 java 的授权问题早就不能下载了，订阅的光盘倒是还有，
却也就用不着列出来了。
win2k3 由于版本太多，选了个有代表意义的ent版，应该也是用的最多的。
其他相对小众版本OS，用的人估计也根本用不着看本文。。。表bs我
下文 RTL 表示 retail 版本，VL/VOL 表示 Volume License
========================
Non Final
-Vista w/ SP2 beta
-Windows 7 beta
-Windows 2008 R2 beta
========================
Windows Vista with Service Pack 2 Beta (x64) - DVD (English)
Home Basic; Home Premium; Business-Retail; Enterprise; Ultimate;
File Name:
en_windows_vista_with_service_pack_2_beta_x64_dvd_288193.iso
Date Posted (UTC): 11/10/2008 11:16:58 AM
SHA1: D320A3FFEE027DB12E7E4F4C35C2AD1FBB455934
ISO/CRC: 06695F47
Windows Vista with Service Pack 2 Beta (x86) - DVD (English)
Home Basic; Home Premium; Business-Retail; Ultimate;
File Name:
en_windows_vista_with_service_pack_2_beta_x86_287906.iso
Date Posted (UTC): 11/21/2008 8:19:33 PM
SHA1: AB59B14A418F7672395D9B89279B30DC89E6ED92
ISO/CRC: 12287431
Windows Vista Enterprise with Service Pack 2 Beta (x64) - DVD (English)
File Name:
en_windows_vista_enterprise_with_sp2_beta_x64_288254.iso
Date Posted (UTC): 11/12/2008 7:54:16 PM
SHA1: 052716F4E535850C41B5A90E6D81EE3189D630D3
ISO/CRC: FD4C18D1
Windows Vista Enterprise with Service Pack 2 Beta (x86) - DVD (English)
File Name:
en_windows_vista_enterprise_with_service_pack_2_beta_x86_288250.iso
Date Posted (UTC): 11/21/2008 10:06:51 PM
SHA1: AB7997E1A0181FF458DC68E86926ED7AAD989814
ISO/CRC: EC5C65F5
Windows 7 Beta (x64) - DVD (English)
File Name:
en_windows_7_beta_dvd_x64_x15-29074.iso
Date Posted (UTC): 12/30/2008 4:26:48 PM
SHA1: E09FDBC1CB3A92CF6CC872040FDAF65553AB62A5
ISO/CRC: 8E2FAD39
Windows 7 Beta (x86) - DVD (English)
File Name:
en_windows_7_beta_dvd_x86_x15-29073.iso
Date Posted (UTC): 12/22/2008 2:41:15 PM
SHA1: 6071184282B2156FF61CDC5260545C078CCA31EE
ISO/CRC: AABA5A48
Windows Server 2008 R2 Datacenter, Enterprise, and Standard Beta (x64) DVD (ENG)
File Name:
en_windows_server_2008_r2_datacenter_enterprise_standard_beta_dvd_x64_x15-29167.iso
Date Posted (UTC): 12/29/2008 8:52:33 PM
SHA1: D6E920581DC1E4FB647F4C60145988A0C4B162A0
ISO/CRC: 6AD35D7F
Windows Server 2008 R2 Beta for Itanium Based Systems (ia64) - DVD (English)
File Name:
en_windows_server_2008_r2_beta_for_itanium_based_systems_dvd_ia64_x15-29173.iso
Date Posted (UTC): 12/30/2008 4:57:21 PM
SHA1: CD57C68F8EABF4DB81FD51CFBE076C6A69582328
ISO/CRC: 51A21CEC
===============================
WinXP with SP3 ENG+CHS RTL+VOL
===============================
Windows XP Professional with Service Pack 3 (x86) - CD (CHS) VOL
File Name:
zh-hans_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-74070.iso
Date Posted (UTC): 5/2/2008 12:05:18 AM
SHA1: D142469D0C3953D8E4A6A490A58052EF52837F0F
ISO/CRC: N/A
Windows XP Professional with Service Pack 3 (x86) - CD (CHS) RTL
File Name:
zh-hans_windows_xp_professional_with_service_pack_3_x86_cd_x14-80404.iso
Date Posted (UTC): 5/1/2008 11:01:59 PM
SHA1: 69DBF131116760932DCF132ADE111D6B45778098
ISO/CRC: N/A
Windows XP Professional with Service Pack 3 (x86) - CD (English)
File Name:
en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso
Date Posted (UTC): 5/1/2008 11:01:59 PM
SHA1: 1C735B38931BF57FB14EBD9A9BA253CEB443D459
ISO/CRC: N/A
Windows XP Professional with Service Pack 3 - VL (x86) - CD (English)
File Name:
en_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-73974.iso
Date Posted (UTC): 5/2/2008 12:05:18 AM
SHA1: 66AC289AE27724C5AE17139227CBE78C01EEFE40
ISO/CRC: N/A
=======================
WinXP X64 ENG RTL+VOL
=======================
Windows XP Professional x64 Edition with SP2 - VL (English)
File Name:
en_win_xp_pro_x64_with_sp2_vl_X13-41611.iso
Date Posted (UTC): 5/4/2007 4:00:03 PM
SHA1: CD9479E1DBAD7F26B8BDCF97E4AA71CBB8DE932B
ISO/CRC: N/A
Windows XP Professional x64 Edition - VL (English)
File Name:
en_win_xp_pro_x64_vl.iso
Date Posted (UTC): 4/7/2005 9:45:00 PM
SHA1: A70B118316A9A451B966A082E7C1DD0E8018718D
ISO/CRC: N/A
Windows XP Professional x64 Edition (English)
File Name:
en_windows_xp_professional_x64.iso
Date Posted (UTC): 3/29/2005 9:13:00 PM
SHA1: 8E914F652DFF0AA8FD16F41B583817C7E107BBA5
ISO/CRC: N/A
==================================
Vista with SP1 ENG+CHS X86+X64 RTL
==================================
Windows Vista with Service Pack 1 (x64) - DVD (English)
Home Basic; Home Premium; Business-Retail; Ultimate;
File Name:
en_windows_vista_with_service_pack_1_x64_dvd_x14-29595.iso
Date Posted (UTC): 2/28/2008 6:01:56 PM
SHA1: BDADC46A263A7BF67EB38609770E4FDBD05247CB
ISO/CRC: 5CC5BE14
Windows Vista with Service Pack 1 (x86) - DVD (English)
Home Basic; Home Premium; Business-Retail; Ultimate;
File Name:
en_windows_vista_with_service_pack_1_x86_dvd_x14-29594.iso
Date Posted (UTC): 2/25/2008 6:26:09 PM
SHA1: BCD715A02739809E477C726AE4B5CAA914156429
ISO/CRC: CE4CB528
Windows Vista Enterprise with Service Pack 1 (x64) - DVD (English)
File Name:
en_windows_vista_enterprise_with_service_pack_1_x64_dvd_x14-55934.iso
Date Posted (UTC): 3/4/2008 12:01:32 AM
SHA1: 149D6E02DE20FA80A7A8ABBC7432C8006E8C1F7E
ISO/CRC: DB73C366
Windows Vista Enterprise with Service Pack 1 (x86) - DVD (English)
File Name:
en_windows_vista_enterprise_with_service_pack_1_x86_dvd_x14-55954.iso
Date Posted (UTC): 2/29/2008 10:56:24 PM
SHA1: A06608EDA6F20F4D1FADF7946EFA09C7DE65AD7F
ISO/CRC: 601F6B43
Windows Vista with Service Pack 1 (x64) - DVD (CHS)
Home Basic; Home Premium; Business-Retail; Ultimate;
File Name:
zh-hans_windows_vista_with_service_pack_1_x64_dvd_x14-30733.iso
Date Posted (UTC): 4/14/2008 9:46:02 PM
SHA1: 65A9AB26AD5A82E5C2F52E0EA976F033E386EBE2
ISO/CRC: 698BAD8E
Windows Vista with Service Pack 1 (x86) - DVD (CHS)
File Name:
zh-hans_windows_vista_with_service_pack_1_x86_dvd_x14-30732.iso
Date Posted (UTC): 4/14/2008 9:46:02 PM
SHA1: E2898C28A31D38D064C999CE5C92156C6A4DAE05
ISO/CRC: 8720447A
Windows Vista Enterprise with Service Pack 1 (x64) - DVD (CHS)
File Name:
zh-hans_windows_vista_enterprise_with_service_pack_1_x64_dvd_x14-55848.iso
Date Posted (UTC): 4/14/2008 10:38:48 PM
SHA1: CFE6ADA55C88F8A6552174C02618D5CE12F8C033
ISO/CRC: 3ABC9150
Windows Vista Enterprise with Service Pack 1 (x86) - DVD (CHS)
File Name:
zh-hans_windows_vista_enterprise_with_service_pack_1_x86_dvd_x14-55727.iso
Date Posted (UTC): 4/14/2008 10:38:48 PM
SHA1: 3AD7F4B7ECFEB905FD779142EA7500C8394DB5CB
ISO/CRC: 89336A90
===========================================
Vista Business with SP1 ENG+CHS X86+X64 VOL
===========================================
Windows Vista Business with Service Pack 1 (x64) - DVD (English)
Business-Volume License;
File Name:
en_windows_vista_business_with_service_pack_1_x64_dvd_x14-56048.iso
Date Posted (UTC): 3/6/2008 10:13:26 PM
SHA1: 9324CB4EC463EE73DF820C689CD4B73340860CB2
ISO/CRC: 95FC2F77
Windows Vista Business with Service Pack 1 (x86) - DVD (English)
Business-Volume License;
File Name:
en_windows_vista_business_with_service_pack_1_x86_dvd_x14-56028.iso
Date Posted (UTC): 3/6/2008 10:13:26 PM
SHA1: 7E6A387E53E1CF77244E637B28A37D529BB85D39
ISO/CRC: CBD8E31C
Windows Vista Business with Service Pack 1 (x64) - DVD (CHS)
File Name:
zh-hans_windows_vista_business_with_service_pack_1_x64_dvd_x14-56298.iso
Date Posted (UTC): 4/14/2008 11:18:53 PM
SHA1: FF4536BF2CD8509F64D36A5247C863F5525C042F
ISO/CRC: 5B46B34F
Windows Vista Business with Service Pack 1 (x86) - DVD (CHS)
File Name:
zh-hans_windows_vista_business_with_service_pack_1_x86_dvd_x14-56119.iso
Date Posted (UTC): 4/14/2008 11:18:53 PM
SHA1: A0DA9A2ECB8AAF89E1DD4C1269AF153EF4FE9320
ISO/CRC: 68D804D7
======================================
Win2003 R2 with SP2 ENG+CHS VOL+RTL
======================================
Windows Server 2003 R2, Enterprise Edition with SP2 - Disc 1 (English)
File Name:
en_win_srv_2003_r2_enterprise_with_sp2_cd1_X13-05460.iso
Date Posted (UTC): 4/26/2007 8:11:40 PM
SHA1: EE11CC735C695501874D2FA123F7D78449B3DE7C
ISO/CRC: N/A
Windows Server 2003 R2, Enterprise Edition with SP2 - Disc 2 (English)
File Name:
en_win_srv_2003_r2_enterprise_with_sp2_cd2_X13-68584.iso
Date Posted (UTC): 4/26/2007 8:11:40 PM
SHA1: A0BE7279E8692DD2EA718BDF54844E4A17ACFEF1
ISO/CRC: CDF77EDB
Windows Server 2003 R2, Enterprise x64 Edition with SP2 - Disc 1 (English)
File Name:
en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso
Date Posted (UTC): 4/26/2007 8:11:40 PM
SHA1: D04C8F304047397BE486C38A6B769F16993D4B39
ISO/CRC: N/A
Windows Server 2003 R2, Enterprise x64 Edition with SP2 - Disc 2 (English)
File Name:
en_win_srv_2003_r2_enterprise_x64_with_sp2_cd2_X13-68588.iso
Date Posted (UTC): 4/26/2007 8:11:40 PM
SHA1: 54B845F1E4C27C9C96AACEF59B9AB19CEFE1C8BC
ISO/CRC: BADD5028
Windows Server 2003 R2, Enterprise x64 Edition with SP2 - Disc 1 - VL (English)
File Name:
en_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-48614.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: A747E66B5206A8A5A4904B93A273FA0DF8130CA1
ISO/CRC: N/A
Windows Server 2003 R2, Enterprise x64 Edition with SP2 - Disc 2 - VL (English)
File Name:
en_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd2_X13-68588.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: 54B845F1E4C27C9C96AACEF59B9AB19CEFE1C8BC
ISO/CRC: BADD5028
Windows Server 2003 R2, Enterprise Edition with SP2 - Disc 1 - VL (English)
File Name:
en_win_srv_2003_r2_enterprise_with_sp2_vl_cd1_X13-48610.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: 0D0CDDD29FCF8FF7456A4BE8CE15698EBA90D1DC
ISO/CRC: N/A
Windows Server 2003 R2, Enterprise Edition with SP2 - Disc 2 - VL (English)
File Name:
en_win_srv_2003_r2_enterprise_with_sp2_vl_cd2_X13-68584.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: A0BE7279E8692DD2EA718BDF54844E4A17ACFEF1
ISO/CRC: CDF77EDB
Windows Server 2003 R2, Enterprise Edition with SP2 - Disc 1 - VL (CHS)
File Name:
cn_win_srv_2003_r2_enterprise_with_sp2_vl_cd1_X13-46432.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: D0DD2782E9387328EBFA45D8804B6850ACABF520
ISO/CRC: N/A
Windows Server 2003 R2, Enterprise Edition with SP2 - Disc 2 - VL (CHS)
File Name:
cn_win_srv_2003_r2_enterprise_with_sp2_vl_cd2_X13-13895.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: 4B364E848FCC59762DDDCED1493248E2896EE033
ISO/CRC: A9488E36
Windows Server 2003 R2, Enterprise x64 Edition with SP2 - Disc 1 - VL (CHS)
File Name:
cn_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-47314.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: FDA1A0401CA610F6E3A7780D6DB004DA2F944138
ISO/CRC: N/A
Windows Server 2003 R2, Enterprise x64 Edition with SP2 - Disc 2 - VL (CHS)
File Name:
cn_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd2_X13-35321.iso
Date Posted (UTC): 4/27/2007 11:06:15 PM
SHA1: 42CB2508F37B7B3331B8EB7A04D58DB508248821
ISO/CRC: 42B94FC6
==========================
Win2008 ENG+CHS X86+X64
==========================
Windows Server 2008 Datacenter, Enterprise and Standard (x64) - DVD (English)
Datacenter, Enterprise and Standard;
File Name:
en_windows_server_2008_datacenter_enterprise_standard_x64_dvd_X14-26714.iso
Date Posted (UTC): 2/4/2008 1:33:22 PM
SHA1: BD000374709F67E9358814DB6EC8F0DDAAA16F70
ISO/CRC: 8F7090D5
Windows Server 2008 Datacenter, Enterprise and Standard (x86) - DVD (English)
Datacenter, Enterprise and Standard;
File Name:
en_windows_server_2008_datacenter_enterprise_standard_x86_dvd_X14-26710.iso
Date Posted (UTC): 2/6/2008 8:10:09 PM
SHA1: 6CA018FF96F1E9B2B310A36546B6FDED99A421E6
ISO/CRC: D20A8F20
Windows Server 2008 Datacenter, Enterprise and Standard without Hyper-V (x64) - DVD (English)
Editions without Hyper -V;
File Name:
en_windows_server_2008_datacenter_enterprise_standard_without_hyperv_x64_dvd_X14-27010.iso
Date Posted (UTC): 2/13/2008 10:14:32 PM
SHA1: F2B05BCF9A89DC8CB2BABC0BA860890F66BD994A
ISO/CRC: 3D29F611
Windows Server 2008 Datacenter, Enterprise and Standard without Hyper-V (x86) - DVD (English)
Editions without Hyper -V;
File Name:
en_windows_server_2008_datacenter_enterprise_standard_without_hyperv_x86_dvd_X14-27006.iso
Date Posted (UTC): 2/13/2008 10:14:32 PM
SHA1: D28929BBEC09CD5A624740B9B2ADB08F165DD473
ISO/CRC: 6798261B
Windows Server 2008 Datacenter, Enterprise and Standard (x64) - DVD (CHS)
File Name:
cn_windows_server_2008_datacenter_enterprise_standard_x64_dvd_x14-26746.iso
Date Posted (UTC): 3/18/2008 1:29:18 AM
SHA1: 1400F7A5CA11E81B49FDB80A25F856DED84ACEC8
ISO/CRC: 8147A1E7
Windows Server 2008 Datacenter, Enterprise and Standard (x86) - DVD (CHS)
File Name:
zh-Hans_windows_server_2008_datacenter_enterprise_standard_x86_dvd_x14-26742.iso
Date Posted (UTC): 3/10/2008 10:28:25 PM
SHA1: 4C1BC3739C13D3CE122C9B4BED4BB2BB2DC708C1
ISO/CRC: 1E0671F1
Windows Server 2008 Datacenter, Enterprise and Standard without Hyper-V (x64) - DVD (CHS)
Editions without Hyper -V;
File Name:
zh-Hans_windows_server_2008_datacenter_enterprise_standard_without_hyper-v_x64_dvd_x14-26958.iso
Date Posted (UTC): 3/21/2008 9:19:43 PM
SHA1: 8D9D7275F571670582DC097BC42AE43719AAC276
ISO/CRC: 43F856E2
Windows Server 2008 Datacenter, Enterprise and Standard without Hyper-V (x86) - DVD (CHS)
Editions without Hyper -V;
File Name:
zh-Hans_windows_server_2008_datacenter_enterprise_standard_without_hyper-v_x86_dvd_x14-26876.iso
Date Posted (UTC): 3/21/2008 9:19:43 PM
SHA1: B47A6F9573F5B2529A2183ACC13150EA93DEBC14
ISO/CRC: 0D11895F
==========================
--
项少龙沙哑着声音，缓缓道：“有个旅客在沙漠里走着，忽然后面出现了一群饿狼，追着他来要群起而噬。他大吃一惊，拚命狂奔，为生命而奋斗。”郭秀儿“啊”一声叫了起来道：“在沙漠怎跑得快过饿狼，他定要死啦！”
项少龙微微一笑道：“不用慌！就在饿狼快追上他时，他见到前面有口不知有多深的井，不顾一切跳了进去。” 赵雅松了一口气道：“那口井定是有水的，是吗？”
项少龙望往下面的小溪流，摇头道：“不但没有水，还有很多毒蛇，见到有食物送上门来，昂首吐舌，热切引项以待。他大惊失神下，胡乱伸手想去抓到点甚么可以救命的东西，想不到竟天从人愿，给他抓到了一棵在井中间横伸出来的小树，把他稳在半空处。于是乎上有饿狼，下有毒蛇，不过那人虽陷身在进退两难的绝境，但暂时总仍是安全的。就在他松了一口气的时刻，奇怪的异响传入他的耳内。他骇然循声望去，魂飞魄散地发觉有一群大老鼠正以尖利的牙齿咬着树根，这救命的树已是时日无多了。就在这生死一瞬的时刻，他看到了眼前树叶上有一滴蜜糖，于是他忘记了上面的饿狼，下面的毒蛇，也忘掉了快要给老鼠咬断的小树，闭上眼睛，伸出舌头，全心全意去舐尝那滴蜜糖。”
项少龙伸了个懒腰道：“对老子来说，那滴蜜糖就是生命的意义！”
※ 来源:·水木社区 newsmth.net·[FROM: 211.99.222.*]
台湾中文化软件联盟 旧faq档案 部分邮件记录
IE5 Beta 2 使用心得
* updated by Kii Ali, 12-11-2001
ftp://ftp.nsysu.edu.tw/cpatch/faq/other_ie5.txt
Subject: 其他_IE5 Beta 2 使用心得
------------------------------------------------------------------------------------------
From: "小叮噹" <sa8528039@scc3.scc.edu.tw>
To: <patch-author@cpatch.org>
Subject: Microsoft IE5 Beta 2 中文版使用心得
Date: Sat, 16 Jan 1999 01:52:29 +0800
您好,弟是小叮噹,
以下是小弟的測試環境:
測試環境: ASUS P5A & Intel Pentium MMX 233 & 128MB SDRAM -8
作業系統: Microsoft Windows 98
以下是這兩個多月來執行 IE5 的一些心得:
重大缺點-> 記憶體怪獸:
安裝 IE5 後的 WIN98 開機情況:
首先 要安裝 IE5 的人注意了,這一個版本吃記憶體超凶的>_<
開完機約耗掉 4X MB ~ 6X MB, 裝了以後有一種中了" 石頭病毒"的感覺,然後, 開幾個
視窗, 您就會發現您的記憶體就快被那記憶體怪獸耗盡了,尤其用 IE 上網時,感覺更是
明顯,不是普通的慢啊...
當然還是有優點...(不然 M$ 不用活了 ^_^)
1. 多重 代理伺服器的設定:
IE5 把 Proxy Server 的設定移到 連線設定的部分了,
也就是說不同的 ISP 連線設定 可以各至設定各至的 Proxy Server
2. 多重帳號連線選擇:
開啟 IE 連上 Internet 時,可選擇 由那一個連線帳號去連網路...
3. 多語系顯示&和解決西歐字母亂碼的問題:
IE 5 還有一個很不錯的優點,其實主要也是改正 IE4 的缺點,那就是
多語系的顯示部分, 以前只要該網站的網頁有設定 charset 時,不管
使用者想用 Big 5 碼來看,卻發現怎麼轉也轉換不過來...導致一堆
海外華人所設立的網站呈現出亂碼
(PS:明明是 BIG5 碼啊,IE4就是秀不出來,只好用 Netscape 來瀏覽)
原因和西歐字母 和 Charset 有關... IE5 把這個 IE4 的大 BUG 解決
了,IE5 在檢視下的編碼功能裡面還多了自動選擇的部分,使用者可以設定個人常用的字
集,如果 IE 5 還是秀出亂碼,可選擇想顯示的字集(語系)來強迫 IE 5 顯示出來...
4.解決 Outlook Express 的亂碼問題:
在 IE5 Preview 1中,這部分還是英文版的ㄅ,到 Beta2 已經是中文版了
當還有 Outlook Express 5.0 beta 2 中的西歐字母的亂碼以解決了,不像
前一版的 Outlook Express 4 要改 Register or 改 Outlook 相關的 DLL 檔
裡的 Charset 設定,強迫改成 Big5 才能正常顯示那些 Big 5 信件
(PS: 當第一次收到西歐字母的亂碼信時,開啟那封郵件, 設定它的編碼
為 BIG5, Outlook Express 5 就會問您要不要將此類郵件用 BIG 5 碼來
瀏覽...選是,就會在 該軟體的字組的設定中出現轉換的對應設定...
之後就不會再發生顯示一堆西歐字母亂碼的問題
PS: 要更改設定可到 Oullook Express 5 中 工具->選項->閱讀->國別設
定中新增或移除原來的設定
PS:以上暫時想到比較重要的就這麼多了,給大家一些想玩 IE5 的先看
看本篇文章再來決定要不要安裝 IE5...^_^
------------------------------------------------------------------------------------------
From: "小叮噹" <sa8528039@scc3.scc.edu.tw>
To: <patch-author@cpatch.org>
Subject: Microsoft IE5 Beta 2 中文版使用心得補遺(二)
Date: Sat, 16 Jan 1999 02:17:45 +0800
您好,弟是小叮噹,
以下是另一個 IE5 Beta2 中文版的大問題:
裝了 IE5 之後,繁體中文字有顯示上的問題:
安裝了 IE5 之後,會有些繁體中文字有顯示上的問題存在,這點在IE5裡的注意事項有提
到這一點,所以想安裝 IE5 的 USER , 要有心理準備
還有在安裝前先把說明文件看過一遍再決定要不要安裝,會比較好喔
------------------------------------------------------------------------------------------
From: "小叮噹" <sa8528039@scc3.scc.edu.tw>
To: <patch-author@cpatch.org>
Subject: Microsoft IE5 Beta 2 中文版使用心得補遺
Date: Sat, 16 Jan 1999 03:19:10 +0800
您好,弟是小叮噹,
以下是小弟突然想到的東西:
1.IE5 不相容 IE4 PowerToys:
小弟想起來 IE4 PowerToys 中文版某些功能無法安裝在 IE5 Beta2 中
文版之上,如 GB 碼 的文件想轉 GB 碼, 會發生問題,無法轉換,至於是不是全部 IE4
PowerToys 的功能都不能用,這小弟就不得而知了...
PS: 小弟是在安裝完 IE5 才想把 IE4 PowerToys 給裝上去...
如果先裝 IE4 PowerToys 再裝上 IE5 呢? 小弟也沒試過,所以小弟
自已也不知道會發生什麼怪事...
2. 以前一些 英文軟體,那些以前對話框或字會被截掉(也就是那些英文軟體在英文
WIN95/98 上執行和在中文版的 WIN95/98上畫面會不一致) 在安裝了 IE5 之後(完全安
裝),那些軟體的畫面就正常了...
小弟猜測可能是和 那些Uni-code 字集和本身 IE5就是採用Uni-code的
關係, 而 IE 又是 WIN98 的核心... 看來 WIN98 本身的核心也朝向和
WIN 2000 一樣 萬國碼化了...^_^ 當然和 WIN 2000 比還差的遠了...
那以後各位中文化作者就不用讓費大量的時間再調整對話框和字體
上面了...^_^
------------------------------------------------------------------------------------------
Reply-To: "Jason Wang" <tojason@bigfoot.com>
From: "Jason Wang" <tojason@bigfoot.com>
To: "Kii Ali" <kiiali@cpatch.org>
Subject: =?big5?B?UmU6ICh1c2VyKUlFNSBCZXRhIDIgqM+lzqTfsW8=?=
Date: Thu, 21 Jan 1999 19:31:05 -0500
Hi :
小弟有些使用IE5 的心得。關於先裝 IE4 PowerToys 再裝上 IE5 的話，小弟試
過一切正常且非常好用。雖然IE5有點吃RAM，但是有一個很大的改變點就是，當以
前的IE4當掉時，有關IE4的程式都會難逃一死(Like : Explorer.exe)，然後連工作列
右邊的小Icon都會消失(相信大家一定都曾經有過此經驗)。但在IE5，他似乎把程式架
構重新寫過，當電腦因IE5停止回應時，只需按"Ctrl+Alt+Del"，然後只要關閉停止回
應的那個IE視窗即可，假使你有一次開啟許多IE視窗，通常也只會關掉停止回應的
那一個IE視窗而已，對其他的沒影響。還有，IE5瀏覽器中的"說明-->修復"也滿好
用的喔...!
Windows2000 B1978
* updated by Kii Ali, 12-11-2001 From: "JAZZ" <jchih@ficnet.net> To: "JQJQ" <jqjq@ms21.url.com.tw> Cc: "KiiAli" <kiiali@cpatch.org > Subject: Windows2000 B1978 Date: Tue, 23 Feb 1999 04:27:03 +0800 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-MDaemon-Deliver-To: kiiali@mail.maiowoo.com X-Return-Path: jchih@ficnet.net 您好, 弟是 JAZZ, 首先當然是得感謝 JQJQ 兄的 Windows2000 B1978, 省去了弟下載 的時間, 之前下載 1946 及 1974 都耗盡了弟不少時間, 弟只是用 56K Modem 苦苦下載的, 並沒有專線可用. 星期日早上便收到了, 但是下來的測試及安裝卻也耗費相當的時間, 從 Win9x, Dos 下都逐一安裝過來驗證. 結果弟發覺幾個盲點.... JQJQ 兄的 1978 並沒有附加多國語系檔, 所以選用時會找不到 , 幸好 弟之前有下載過 1946 裡面有, 將它餵給 1978 吃當然是可以, 只要自行 建立一個 Lang 的目錄就行了. 這個檔案在勤益的 Upload 還有, 但有 78 MB 之多. 如果安裝時未曾選用語系, 安裝後便永遠無法再安裝了??這是第一個 盲點所在, 真不曉得 Microsoft 在搞什麼?? The God said : This is Beta.... 第二個盲點便是如果是在 Dos 模式下安裝, 也就是執行 Winnt.exe 安裝, 那更慘....根本沒有語系挑選視窗, 想當然爾安裝後更本也就純英文版了. 而且如果 Dos 下開機時未曾載入 Smartdrv.exe (先要 Himem.sys) 它會警告 您, 弟不鳥它...結果死的很慘, 光是複製檔案就超過一小時了....! 您一定會疑惑?? 一定要複製到硬碟安裝嗎 ? 直接燒成光碟不就可以指定 光碟安裝了嗎 ?? 您注意一下, 未安裝的原始檔有約 40 個左右包含 "~" 的 檔名, 這是長檔名在 Dos 的樣子, 但是燒成 ISO 時, ISO9660 是不允許這個 字符的, 它會轉換成 "_" 字元. 安裝時便會找不到檔案, 弟這邊的經驗是一 直忽略仍能可裝完, 但是如遇到中文檔名的檔案一律無法開啟 (指安裝 1946 時的經驗). 弟的疑惑是, 那微軟當初是用什麼格式燒成光碟的?? 因為 ISO9660 的 Joliet 在 Dos 下是可看到但進不去的 , 而標準 ISO9660 Level 1 檔名又不允許 "~" 字元存在, 弟試過燒錄 UDF, UDF/ISO , ISO9660 Level 2 (Joliet), 都無法在 Dos 下正常使用的 . 弟找出 Nt4 的原版光碟, 那是標準 ISO9660 開機型光碟, 但仍有 "~" 字元的檔 名存在, 弟想或許是燒錄程式的 ISO 的字元定義及控制不同的詫異吧?? 找時 間弟再以 EasyCD 系列及 WinOnCD 試試看吧!!目前弟都用 " 尼祿 -- 火燒羅馬 城 " 而已...想起了微軟 AOE 的羅馬興起的外包裝, 差點以為是賣 Nero... :P 雖說弟是用 CD-RW 可以反覆測試, 不過也燒壞過三片 CD-RW 過, 兩片 Ricoh 一片 Yamaha, 而且就算新買的 Yamaha 4416, 弟也只能用 2X 燒 , 因為 "尼祿" 這個暴君就是只能讓我用 2X , 不讓我用 4X 的寫錄 CD-RW. 光是燒壞的三片 CD-RW 價錢就可以買一筒 CDR 了, 而且三片總次數不超過 90 次....讓弟有時 候很疑惑 CD-RW 的價值. 不過弟強調...我絕不是補帖商!! 只是電腦狂罷了!! 因此至此為止, 弟要能安裝無誤就是一定要先複製一份在硬碟, 然後安裝時 Windows2000 自動再複製一份 (目錄為 $Winnt$ 安裝完後就自動砍掉了, 這是 弟刻意用強制關機, 重跑 BIOS 開機序回 Win9X 下看的), 如果您只有一顆硬 碟, 容量沒約 1 GB (因為共要 350MB*3 份 ) 時不就甭安裝了?? 當然為了語系問題, 您最好還是先安裝一個陽春 Win95 , 然後執行 Winnt32.exe 安裝, 也不用煩惱 Smartdrv.exe 的事, 也可以從光碟安裝 (Win9X 認得 Joliet) , 下不複製到硬碟的指令就一切 OK 不是嗎?? 第四個盲點就是能不能做 Setup Disk ?? NT4.0 可以(印象中做出來好像不能用) 5.0 不知道能不能 ?? 難道每次都得重新安裝, 沒有如 NT4 修復功能嗎??這是為 了搬移 NT 時重做開機區的重要功能耶... 第五個是 Nt5.0 的 FAT32 好像跟 Win95 OSR2 之後及 Win98 不同 ?? 因為 Nt5 的 Scandisk 及 Defragement 並沒錯誤訊息, 但弟切換 BIOS 開機至 Win9X 想重 整 NT5 的硬碟(安裝 FAT32 , 非 NTFS ) 時, 都說含有必須修復的磁區 ?? 弟曾 看過一份微軟的文件說這是加強型的 Fat32 (V2.0), 好像在 Nt4Sp4 也有, 但是 弟也曾在 Nt4 安裝過 Nt4Sp4 但沒這個現象過啊?? 總之目前 Windows2000 畢竟是測試版, 出任何錯都是名之言順的, 但是美美的 介面真是讓人愛不釋手, 驅動程式也支援到 Voodoo3 及 Banshee了, 不過 Voodoo2 是子卡, 不是顯示卡所以反而不支援, 那麼到底用 Nt4 還是用 Win9X 的 Driver ? 弟就懶得去試了.
(beta)WinNT 5 beta2 1877 測試報告
* updated by Kii Ali, 12-11-2001 X-Sender: kiiali@cpatch.org Date: Mon, 26 Oct 1998 21:31:58 +0800 To: Patch-Beta <patch-beta@cpatch.org>, VIP <vippiv@ftp1.gep.ncu.edu.tw> From: Kii Ali <kiiali@cpatch.org> Subject: (beta)WinNT 5 beta2 1877 測試報告 Sender: vippiv-request@ftp1.gep.ncu.edu.tw Resent-Message-Id: <B0000029081@ftp1.gep.ncu.edu.tw> Resent-From: vippiv@ftp1.gep.ncu.edu.tw X-Unsub: To leave, send text 'LEAVE' to <vippiv-request@ftp1.gep.ncu.edu.tw> 您好，弟是_Kii_Ali 其實在發這個測試報告之前，是滿戒慎恐懼的。 接觸 NT 的時間不過暑假幾個月，而且是為了接 cpatch 管理者所需， 才逼迫自己去弄懂 NT，相信比在座各位短許多。弟只不過是在海邊撿 石頭的人，對大海的奧秘，可以說是一無所知。只能說，把手上的石頭 現給大家看看罷了。裡面的許多觀點都是沿襲以前測試 Win98 觀念， 或許沒有測到和騷到各位所要的癢處吧。還請各位方家，不吝指正。 本文歡迎轉載，唯請註明出處。 0.目錄 ====== 1.記憶體需求 2.安裝過程 3.歡迎畫面 4.PNP 功能 1.音效卡 2.顯示卡 3.網路卡，scsi，modem 4.滑鼠 5.硬體新增精靈 6.控制臺/安裝移除程式 7.控制臺/鍵盤(輸入法) 8.控制臺/顯示器 9.控制臺/DirectX 10.控制臺/Tweak UI 11.控制臺 /系統/硬體管理 12.控制臺 /字形 13.一般對話窗 14.關機 15.IE5/Outlook 5 16.總評 17.感謝 1.記憶體需求 ============ 64MB 是最基本的記憶體需求。如果您只跑 NT5 工作站版本，那麼還可以 。如果是跑伺服器版本，那是「一定不夠」。是動得很難看，swap 的相 當厲害，硬碟卡哩卡哩亂叫的聲音讓你回到在 286 用 1.2 MB 磁碟片抽 換執行 dbase4 的時代。我是直接跳到 128MB，記憶體的瓶頸一下子舒解 不少。 這些記憶體的需求，隨著您所要求的服務數量多少而上昇。如果你在 NT4塞進了 IIS4, IE4 Outlook4 這些東西，所佔的記憶體需求要多少 ？如果弟沒有測錯，NT5 包含了 IIS5 , IE5, Outlook 5 等一卡車免 費強迫贈送的元件，在 task manager 看來也得要 8xMB ，蠻可怕的 數字。 2.安裝過程 ========== Win98 在安裝時，有個 batch98 的公用程式可以取代所有繁瑣的過程 ，包括序號和安裝選項等等一堆。不過 NT5 好像還沒有？如果朋友知 道簡化安裝它的方式，請告訴弟一聲。 從 dos 下開始安裝，WinNT /b 執行，還算蠻順利的。不能在 98 底 下安裝。在裡面的文件提到這版的 beta 不能與Win95/98 共存，不 過我倒是沒有問題。而且還是「直接安裝」在 fat32 上。享受了4k小 磁區的優點，雖然速度也比 ntfs 慢了不少，但這似乎是讓 Win98 與 NT 共存不得不為的做法。 如果你是從光碟下安裝，建議在 dos 先執行 smartdrv.exe ，在拷貝 其原始檔到硬碟的 dos part 時間會少一些。我的經驗是，至少要一 個小時。如果沒有 smartdrv.exe ，就會聽到你的硬碟和光碟機一前 一後琴瑟和鳴的怪叫起來。1500 個以上的檔案，要有耐心一點。如果 是灌了4dos ，dir 該 /i386 目錄都會出問題，想來是 environment 設得不夠大。 跟 NT5 1735 的安裝畫面一樣，蠻漂亮而專業的畫面。在 1735 安裝 時出現是工作站版本的畫面，安裝完卻是伺服器版的錯誤，這版已經 不復出現。 安裝的時候，如果您的記憶體才64MB，建議您「不要做怪」。怎麼說 ？就是在安裝時儘可能不要去開啟那些 option 選項，尤其是 server 版本。輸入法、網路服務設定等等，800x600 解析度都可以在灌完 NT 後再去選擇，那將遠比安裝時選擇來得快， 1735 1877 兩版在安 裝時的選項回應速度，實在慢到讓人吐血，會讓你以為機器停了三分 鐘，當掉了，沒有想到很久之後居然又動起來了。 輸入法的安裝，簡直是非常不人性化。在 NT4 或是 Win98 裡面輸入 法都是獨立的項目，在 NT5 的觀念則是歸併到「鍵盤」，於是安裝 就出現倉頡大易新注音，跟一堆西班牙文、法文、美式英文等番邦文 字並列在一起的奇特景象，不過還是稱為「輸入法」。剛開始找的確 會在觀念上搞混。在安裝輸入法時我自己雞婆把「大易」設定成我的 預設值，結果引起以後無限的麻煩，最後還是把預設值改回美式英文 。建議大家不要自己找麻煩。 3.歡迎畫面 ========== Welcome 的部分還沒有完工，而且還是英文的，看來也醜，內容也不 多。算了，還是自己測程式吧。本來是想看看 welcome 裡面有什麼 新東西說。 4.PnP 功能 ========== 據說 NT5 有 hot-plug 的功能？這正是我最擔心的功能之一。如果你 的機器是有許多非「標準配備」的人，最好要有一些心理準備。總體 而言，NT5 的 pnp 功能，的確比 NT4 + pnpisa.sys 要強得多。 1.音效卡 -------- 弟所使用的音效卡是 cmi8330 ，明致主機版內建的那塊 (晶片上還印 了Sound Pro 1869+，倒足胃口的名稱)，號稱有3d 環場音效，我是覺 得不怎麼樣啦。前一版 1735 和 NT4 server, workstation 都可以安 裝，只是會有連續振盪的高頻嘯音，讓人煩到極點，弄到後來去買一 塊 ess1868 的爛卡總算解決問題。沒想到1877 版居然正常了，真是 該放鞭炮慶賀。不過 pnp 的配置仍不順利。仍然有個 device 亮起黃 色驚嘆號。 2.顯示卡 -------- 弟使用過 SiS 6326 , S3 Virge ，在 1735 跟 1877 都沒有問題。當 然由於 NT 本身的限制，SiS 6326 在98 底下一堆花俏的功能，在 NT 就沒有了。當然，SiS 6326 得到灌完 NT後才再安裝上去。NT 在這 裡會「誤判」多出一張 vga 相容顯示卡 (唉)，不要理它，沒事就好。 3.網路卡，scsi，modem --------------------- 都沒有問題，安裝完NT就直接抓到，不用再另外麻煩。 使用的網路卡是 D-Link 530ct PCI, Win98 抓成 DEC21040 ，這倒沒 錯，晶片的名稱，NT 1735 也沒抓錯，NT 1877 卻抓成了 Intel 21040 ，唉，可以動就算了。在 98 底下如不信邪硬要裝上 D-Link 530ct， 必死。 :( 另外的網路卡是 Accton 166x ISA ，「非常建議」不要買。裝雖然沒 有什麼問題，不過該廠商的網站跟 dlink 都一樣有夠慢速，抓下來其 肥大 driver解開後只有幾個字 " Win95 內建其 driver" ，真想把這 塊卡扔進垃圾桶裡。而且這些廠商的美國網站居然都比臺灣網站快， 真是怪事？ SCSI 用過 AdvanSys, Tekram 都沒有問題。 modem 用過台康的，gvc 的也沒有問題。 4.滑鼠 ------ 這不該有問題的，結果出問題了。用羅技滑鼠抓不到，開完機之後沒 有滑鼠簡直不能動。結果換了三鍵式普通兩百塊的滑鼠才解決。勉強 裝上羅技滑鼠一定會亮出黃色驚嘆號。 別懷疑，剛剛說的是1877 版的，在1735 版結果是普通滑鼠沒有用， 羅技滑鼠反而正確抓到了。 :( 除了懷疑自己的滑鼠有鬼，實在沒有第二個理由安慰自己。 滑鼠在控制臺有「自動移至」的功能，NT5 新小功能，滿好的，九八 的未來 SERVICE PACK應該把這個放進去吧？微軟並非做不到，只是 要不要把這小功能做上去罷了。 5.硬體新增精靈 ============== 「硬體新增精靈」跟 Win98 的很像，看來似乎比 NT4 的人性化一些？ 但仍是煩人居多。配合 PNP 的部分，在理想與現實似乎有一段差距。 在新增時總要開上一堆視窗，說明文字的過於囉嗦，反而讓使用者不曉 得該選那一個。 如果 NT5 的目錄是致力於跟 98 的介面統一 (其實已經統一的滿像了)， 這個部分像 98 一樣簡潔會比較好。 那個精靈，真的不太 wizard 。 6.控制臺/安裝移除程式 ===================== 1877 這部分沒有中文化完全，而且不能以手動鍵盤操作。畫面的構成 在底下的部分雖然有漂亮的底色，離實用的階段還很遠。 7.控制臺/鍵盤(輸入法) ===================== 如前所言，NT5 的觀念把這兩個合而為一，這對中文版的使用者來說， 真是「找麻煩」。外掛輸入法的相容性，和對外字集 (比如中國海等) 的支援，讓使用者在轉換平臺時沒有困擾，才是臺灣微軟應該努力的 目錄。統一在 NT5 的 unicode 底下？恐怕還要有一段時間。 而且我也不想那麼快被微軟統一。 8.控制臺/顯示器 =============== NT5 內定值顯示紫色畫面，還蠻好看的。一樣有 Active Desktop， 一樣有內建 plus 的功能，只可惜還是不能在 systray 直接控制解 析度的切換。 9.控制臺/DirectX ================ NT5 無法得知他的 directX 版本，如果你用 ka 修改的 directx.cpl 或是用原英文版的，都無法得到 directx 5 或 6 的版號。版本都是 5.00.xxxx 。部分選項使用，還會使 directx.cpl 當掉。 看來這個 directx.cpl 似乎只能用於 95/98 ，跟 NT5 是可以相處， 但相處的並不愉快。這裡可以找到相關檔案 ftp://ftp.nsysu.edu.tw/cpatch/system/directx/cdirectx.zip ftp://ftp.nsysu.edu.tw/cpatch/system/directx/cdxinfo.zip (25KB) ftp://ftp.nsysu.edu.tw/cpatch/system/directx/cdxdiag.zip (29KB) 10.控制臺/Tweak UI ================== 非常建議安裝，尤其是您的 NT5 只有一個人使用，沒有安全顧慮時 ，把自動登入的功能打開吧，那會讓你少煩很多事情的。server 版 從登入畫面到完全執行完還得花上一段時間，特別是你的 ram 特別 少，或是非 NTfs ，或是服務太多的時候。 Win98 內附的 tweakui 1.25 就可以使用。也有孫小毛和 ynk的中 文化版本。 ftp://ftp.nsysu.edu.tw/cpatch/system/tweakui/tweakui98_1.exe 11.控制臺 /系統/硬體管理 ======================== 如果弟沒想錯，控制臺 /系統 底下執行後，結果跑出 mmc (Microsoft Managemant Console) 之類的東西出來？對 NT4 的管理者而言，似乎 是必須重新適應的觀念。是比較好懂沒有錯啦。 好不好用？其實我比較喜歡 Win95/98 那種控制系統硬體的方式， 簡明。用獨立的程式，然後分成兩個 viewer pane ，並不是很好使 用，特別是用鍵盤而不用滑鼠操作的時候。 12.控制臺 /字形 =============== 字形多了一種 OpenType ，跟以前 倚天的「開放字型規格」(還有人 記得這種東西嗎？)應該沒什麼關係。只可惜看不出來有什麼不同，副 檔名一樣是 *.ttf ，只有部分英文字型會顯示 OpenType 。妙的是， 去檢查 Win98的 font 目錄，一樣有一堆是 OpenType。似乎是 nt5 的 fontview.exe 判斷上有點問題。 13.一般對話窗 ============= NT4 的使用者，很容易看這個部分在 NT5 發生重大改變。在一般開啟 檔案的對話窗，左側 有一串 recent, favorite ，我的電腦，網路上 的芳鄰等等「物件」，做得很像frontpage 98 或是 Outlook 98 左側 一串東西的風格。右上側的按鈕也統一成 office 97 式浮動式按鈕。 左側大型按鈕部分，也沒有翻譯完。而這卻是一般使用者最常用到的 dll 檔。 好或不好？ 個人看法是，吃 gdi 而不實用的大 icon 怪物。不過看樣子微軟是不 可能改這個地方了。1735 版這個部分沒有中文化，且因為字型關係導 致顯示重疊而完全錯誤，是非常失敗的部分。1877 則已經改正。如果 微軟不弄這種花招，使用者會感謝它。如果微軟真想在一般對話窗搞 花樣，那麼把 file-ex 之類的東西買下來，或是功能照抄嘛，也比這 種只能好看的東西來得強。 或許以後我們所有的軟體都得像 frontpage98, Outlook 98 看齊，做 出左側沒啥用的垃圾大圖示軟體出來？弟私下很不喜歡這樣，自從 ie3 改為浮動式按鈕(還無聊的按鈕底色花紋)，office 97 , IE4 IE5 也變 成浮動式按鈕，然後市面上一堆軟體全部跟進變成浮動式按鈕(偶爾會 加上底色花紋)...包括 netscape 4.0, powerdesk 203, cuteftp 2.0 ,psp4 ,ultraedit 5 的以上版本在內 :( 軟體的流行風潮？ 看來，我們只好等著準備接受這種，左側沒啥用的垃圾大圖示軟體吧。 早晚有天要流行起來的。你只要想到，連開個 ultraedit 編個小文字 檔，becky 寫封小信，左側都得出來左側那種呆瓜圖示，就覺得噁心 到極點。創造流行的死微軟？ 算了，不過是弟的嘮叨兼無聊偏見。 14.關機 ======= 之前舊版的畫面 關閉電腦/重新啟動電腦/登入另外的使用者一堆有的 沒的...是用 Radio Button ，單選題，當然你可以用 hotkey 直接 指定，也可以用滑鼠按選擇。畫面看起來也很順眼，每個人都看得懂。 1877 做了一些小修改，這些選項變成下拉式選單。差點沒有昏倒。 敗筆。 兼欠人罵。改到沒什麼好改，也不用去動這種東西吧？ 15.IE5/Outlook 5 ================ IE5 我沒有仔細測，把體力放在玩 netscape 4.5 正式版了，有點想 開刀把 netscape 4.5 中文化解決丟掉。微軟已經表明 IE5 不會支援 XML? Outlook 5 則改進了不少，至少不會中文化導致邊框不正確而 完全不能寫信了。當然，還是不建議用 Outlook 5 來寫信。 有關 email 設定問題，您可以參考這裡的訊息 ftp://ftp.nsysu.edu.tw/cpatch/faq/setup_email.txt 16.總評 ======= 雖然弟挑了很多毛病，比起上一個版本 1735 ，其實已經好很多了， 也可以拿來做實際的工作平臺。在一般對話窗已經沒有前一版的重大 錯誤，選擇和開啟檔案也沒有問題，你可以說它的確很穩，這也是一 般人選擇 NT 的最大理由，我則是只考慮拿來當中文化平臺。當然測 試的風險是一定有的。 不過在系統負荷仍重的情形下，用 NT5 1877 的確要有些心理準備。朋 友跟我要去說要當筆記型電腦的作業系統，那未免太辛苦了一些。 若要兼顧穩定，和眾多軟體相容性，甚至多媒體的考慮，想玩個 game， 甚至像我一樣變態，把 .dat 檔拷進硬碟，一邊四倍速燒片一邊看vcd (把新世紀福音戰士vcd看完，真爽)，我寧可選擇 Win98。NT 5 的確有 些小功能做得很醒目，不過還是留個系統管理員吧。要不然，就選 NT4 workstation 吧，它的確也夠穩的了，雖然還是有辦法把它當掉。 如果您是測試狂，想要用新的作業系統，這版已經可以用了。只等它更 完美。 17.感謝 ======= 感謝住臺中在雲技唸書的 Richard Liu <czliu@tcts.seed.net.tw> ， 提供 NT5 beta2 1877 版本，此篇測試報告即是應他之要求所做。 此篇寫掉五個小時。 -- Eudora Pro 2.2 (patch) 中文化軟體的訊息與評論，將用電子信件每天下午定期發出。 請告訴你的朋友訂閱 Patch-News ，以便獲取最新中文化檔案訊息。 請到 http://cpatch.hort.ntu.edu.tw/ 訂閱或取消信件。如果你是 使用智邦生活館電子報服務的朋友，請到這裡訂閱及取消電子報。 http://scorpio.url.com.tw/ENews/login.asp 黃國書(Kii Ali)，地理老師，電腦測試狂。 ICQ#5107476
有關 NT5 的進一步測試
* updated by Kii Ali, 12-11-2001
ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_nt51877_1.txt
Subject: 有關 NT5 的進一步測試
---
有關 NT5 的進一步測試
updated by Kii Ali, 11-18-98
不曉得上次丟出來給大家的 NT5 測試報告，還滿意否？希望這篇
又臭又長，卻得讓您從頭到尾好好看完的文章，還不至於看到頭腦
爆掉。
還是很誠心的期待，能有人給弟批評，指出那些地方有測試錯誤或
觀點偏差的地方。據說微軟這個作業號稱 Windows 2000 ，不過沒
兩天就說這名稱早有人註冊了，天曉得以後還會改成什麼名字。網
路上的消息總是流傳的特別快而不切實際，或許 Windows 2000 就
像 et2000, ez2000 一樣都將會是個失敗的末代產品？然後變成
Doors 2001, Gates 2002 ? 把它當成一個全新作業系統而非更新
版本的角度來看，操作觀念在那裡產生轉變，這是我感興趣的地方
，而非單純的只以 NT 或 Windows 的下一代繼氶者來看。
必須明說的是，我對 NT server 及網路管理的經驗不足，機器未
在有 loading 的網際網路上操作，以致於像 NT5 號稱重大改進的
Quota 控制等觀念不能實作。在報告上觀念無可避免有許多偏差，
還請您指正。
歡迎自由引用，唯請註明出處。如果您引用時能 email 知會弟，那
是再好不過。
目錄
====
1.Outlook Express 5
2.有關 NT5 的地名翻譯
3.系統/光碟自動播放
4.PIO/DMA 模式
5.多媒體-豪華cd 播放機
6.多媒體-Microsoft Media Player
7.多媒體-Netshow
8.MMC 微軟管理主控台
9.再談 nt 下的輸入法
10.Win98/NT5 並存的問題
11.尋找/檔案或資料夾
12.新增/移除程式
13.系統列內「拔出硬體」圖示
14.捷徑
15.字形-OpenType
16.字形-數位認證
17.字形- TTFEXT 的相容性解決
1.Outlook Express 5
===================
此次包括在 NT5 裡面的 Outlook Express 5 (beta1) ，版號為
5.00.0707.2700 ，完全還沒有中文化。以後的正式版本應該也跟
這個差不多。或許我們過幾天就可以看到隨著微軟放出來的 ie5
測試中文化版本？
要注意的是，這版的 Outlook Express 並不能在 win98 裡面使用
。只適用於 NT。
以下是常見的 Outlook Express 中文相容性設定問題。整理如下。
這版的 Outlook Express 跟 win98 內附的相同，沒有好好設定，
極易造成別人收信困擾。
1. 造成麻煩的 HTML 發信
>Tools/Options/Send/Mail Sending Format/
在「郵件」內容中，請選 "Plain Text" , 而非 HTML 格式。
html 格式大小，通常是「普通文字」格式的四到八倍。
>Tools/Options/Send/News Sending Format/Plain Text
在「新聞」內容中，請選 "Plain Text" , 而非 HTML 格式。
html 格式大小，通常是「普通文字」格式的四到八倍。
2. 郵件內容的設定，皆在如下路徑。
>Tools/Options/Send/Mail Sending Format/Plain Text/Settings
2.1 信件格式
Message format
請選擇 "MIME" 而不要選 UUdecode。
2.2 信件編碼問題
>.../MIME /encode text with
請選 "None", 如果選 "Quote-Printable" 將會造成「國內」使
用者極大困擾，信件會增大原來三至八倍，如果對方使用 Eudora
將很容易當機。
2.3 標題亂碼解決，只要選「準備八位元」就可以了。
8 bit character
>.../MIME /Allow 8-bit character in headers
2.4 自動轉折文字
不建議設定，而改以手動在 65 字元左右按 Enter 斷行，否則
你的信件到別人手中反而會「自動重排」得亂七八糟。請在底下
"xxx"填入 132，也就是這個值的最大值。
Automatically wrap text at "xxx" characters, when sending.
3. 新聞內容的設定，皆在如下路徑。大部分照著 mail 的設定即可。
>Tools/Options/Send/News Sending Format/Plain Text/Settings
2.有關 NT5 的地名翻譯
=====================
說實在，這是雞蛋裡挑骨頭，不過這方面的翻譯應該盡量參考國內
譯的標準名詞，而非自己自創名詞。這部分的錯誤大部分出自於「
時區」和「電話語音」這兩樣。
雖然時區的部分大家很少會去設定 (想想看，你在裝完 NT5 後，有
沒有可能帶著自己的筆記型電腦，到烏干達或是沙烏地阿拉伯出差
？)，不過這個也驗證了翻譯人員的水準，和微軟中文化品管的不良
。
沒辦法嘛，誰叫 Kii Ali 是唸地理的。隨便也看到一堆笑話般的錯
誤。另外在時區地球議內的「高亮度顯示」似乎也不見了。
以下是在 registry 裡面找到的錯誤舉例。
1."Display"="(GMT+07:00) 曼谷，漢諾義，亞加達"
"Dlt"="東南亞日光節約時間"
"Std"="東南亞標準時間"
這個錯誤不曉得是幹的。只能說，實在是很離譜。
「曼谷，河內，雅加達」才對。
2."Display"="(GMT+04:00)巴古，塔布理斯"
"Dlt"="高加索日光節約時間"
"Std"="高加索標準時間"
這個是裡海西岸，高加索山東側的「巴庫」油田，和「提比里斯」，
這樣子翻譯恐怕大家要以為「古巴」打錯變成「巴古」了。
3."Display"="(GMT+03:00) 巴格達，科威特，里雅德"
"里雅德"應該是 "利雅德"，沙烏地阿拉伯首都。
4."Display"="(GMT+10:00) 坎培拉， 墨爾本，席德尼"
大家都會搞不清楚"席德尼" 是啥子東西，澳洲兩千年奧運「雪梨」
啦。
5."Display"="(GMT+10:00) 布里斯本"
"Dlt"="澳洲東部日光節約時間"
說是「布里斯班」大家會比較熟稔吧？
3.系統/光碟自動播放
===================
找了半天，還是沒有找到控制「光碟自動播放」 autorun 的設定。
跟 nt4 是完全一樣。除了自己安裝 Tweakui 可以達到這個功能之
外，其他簡直無可選擇。幸好 win95/win98 還找得到，雖然是個不
太好找的地方。
除非使用者熟 registry ，否則根本無法在 NT5 裡面關掉它。而這
對燒錄作業的危害是眾所皆知的。
4.PIO/DMA 模式
==============
NT5 內建使用 DMA 模式，溝通 IDE 通道。(相信一定有人覺得奇怪
，nt底下使用 dma 模式？)
但某些機器使用 DMA 模式時，燒錄光碟反而出現問題。您找看看底
下這個地方，可以設定和切換 PIO/DMA 模式。
>控制臺/系統/硬體/裝置管理員/裝置/IDE ATAPI 控制卡/主要 IDE
通道找到後，按兩下出現
>內容/進階設定/轉送模式
好累，居然藏在這麼裡面 :(
5.多媒體-豪華cd 播放機
======================
這個軟體蠻不似微軟的傳統多媒體軟體，「堪用就好」的軟體設計
哲學。只能說，太漂亮了。
只能說，看起來很像跟 Creative 買來的 cd 播放軟體，抄得未免
有點「太像」。再說一次，太漂亮了。(很少微軟的東西可以得到
ka 這種評價) 。支援 tunes.com , Music Boulevard 這兩站的
「網路專輯下載」，還可以設定「批次下載」。除了沒辦法在播
cd 音樂時出現像 winamp 的波型器之外，簡直沒有什麼好挑。
缺點：
1.中文化字型「太醜」，包括程式的「標題列」在內。是選用
MS Sans Serif 8 沒有改而出現的結果。
2.畫面還可以再酷一點。比其他牌仍稍嫌不夠，比起之前，包括
win98 內附版本則已經好太多。
6.多媒體-Microsoft Media Player
===============================
直譯為「媒體播放程式」，不過微軟把它中文化後，唯一沒有翻譯
的卻是這個名稱。想來是要跟原始版本的「媒體播放程式」相較不
同吧。
這和我們在 win95/win98 裡面所看到的「媒體播放程式」，有很明
顯的不同。如果各位有拿過「純潔」中文化的 media player 5.20
中文化，對這個應該有點印象。NT5 把這個列入標準配備，拿到的
版號是 6.00.01.0628，已經完全中文化，但跟之前的 5.20 有什麼
分別，說實在比不出來，甚至在內部版號內也是一樣稱 5.20。在
NT5 裡面常常以 media player2 來稱呼這個軟體。我在想「純潔」
那版的中文化大概可以踼出硬碟，沒有用了吧？
在 NT5 裡面，舊版的執行檔名稱為 mplay32.exe ，新版的則為
mplayer2.exe。為區分起見，弟在此也仿照 NT5 的暱稱，直接稱
此為 mplayer2。微軟在這版的 NT5 一樣放上舊版的 MPALY32.EXE。
即便我不喜歡微軟的 Active Movie / Direct Show ，但是用
MPlayer2 來放「空軍一號」，仍不免為它的效果而吃驚。畫面流暢
度和音效品質都和 Xing MPeg player 不相上下，甚至有過之而無
不及。當然你可以嫌微軟的軟體那種，稍嫌「醜畢了的華麗」那種
感覺，而不想把 xing 換掉，不過 xing 的地位已經受到威脅則是
事實。
缺點：除了 mplayer2 沒有辦法直接放 VCD 外 (倒是可以選擇
*.dat 來放)，調整螢幕大小 50%, 100%, 200%, full screen 等實
在有夠煩之外，其他似乎沒有什麼好挑。
優點：mplayer2 支援多語言 (比如說你拿到成龍主演[我是誰] vcd
，如果支援的話，在英文 NT5 成龍就說英語，在中文 NT5 成龍就
講中文，多好)。不過弟手上的500 片vcd 好像還沒有找到支援，
試不出來。:) 甚至也支援「字幕」。當然我手上的片子還是沒有
半片支援的。當然囉，它也支援 mp3 。
mplayer2 支援網路 , UDP, proxy 一拖拉庫有的沒有的。不過弟還
是對在網路上的媒體播放沒有興趣。臺灣網路速度太慢了。是否微軟
想拿這個肥軟體來取代 (順便幹掉) quicktime, Realaudio 等等多
媒體播放程式？在網路上已經可以單獨拿到這個版本，當然也會隨
著 ie5和 NT5 一併出貨。而底下提到的 netshow 將是 mplayer2 的
元件之一。
內定的網路連結地點在此。
http://www.microsoft.com/isapi/redir.dll?prd=mediaplayer&pver=5.2&ar=home
7.多媒體-NetShow
================
您可以在 NT5 安裝完的目錄找到，微軟免費贈送的，卻必須由使用
者自行安裝。這兩個檔案都是「限nt使用」。而且都仍是「英文版」
。在安裝完的 NT5 server ，只有簡單的稱呼「Netshow 伺服器」
「Netshow 工具」。連 server 端的 netshow 工具都準備吃下來了
，
NetShow 3.0 Server and Administration components
C:\Program Files\Netshow 服務\nssrvNT5.exe (6.0M)
號稱提供了 Multicast Streaming , unicast Streaming 的
能力。也可以經由 proxies 讓伺服器與伺服器之間對傳。
Netshow 3.0 Tool service
C:\Program Files\Netshow 服務\nstlsNT5.exe (3.6M)
手上沒有網路，倒是不曉得這有沒有比「純潔」上次中文化的來得新
？這版包含了 Advanced Streaming Format (ASF) content for
NetShow 3.0 *.asf 的規格弟尚未來得及測試。包含了三個主要元件
，NetShow T.A.G. Author、 NetShow Encoder、 NetShow ASF
Indexer。
8.MMC 微軟管理主控台
====================
如果您稍後有接觸過 NT4+IIS4 ，應該有聽過 Microsft Management
Control , MMC 這個東西。
最明顯的是， MMC 版本是 1.1 (廢話)。
我們知道在 mmc 的觀念底下，管制的選硬體相當多 (說實在，我還
是不太喜歡 mmc 的管理觀念與作法)。mmc 原先內附的元件，除了
硬體管理部分有中文化之外，其他像 Transcation server,
Certificate server 都還沒有中文化。另外，如果您使用 NT5
resource kit (附在 beta 光碟裡面)，這個當然也沒有中文化。其
實蠻可惜的，這部分只要把 .inf 改一改就好了。
mmc 管理主控台檔案 (*.msc ，沒打錯字) ，找到的如下，蠻多的
。NT5 的測試光碟裡提到 MSC 只有英文的 help 檔，其他大部分則
是語帶不詳著為多。當然囉，在底下還是有一堆弟不知道功能的。
如果那位大哥熟稔 NT4+IE4+IIS4 的管理方式，有可能的話，還麻
煩說明。NT5+IE5+IIS5 可說是轉換新觀念了。這部分也是弟限於能
力，沒有全力測試的地方。找出來底下那堆就偷笑了。
c:\progra~1\common~1\micros~1\msinfo\*.msc
MSINFO32.MSC 系統資訊
c:\progra~1\resour~1\*.msc
SIDWALK.MSC ?
c:\progra~1\resour~1\tmc\*.msc
RKTMC.MSC NT5 resouce Kit
c:\winnt\system32\*.msc
ACSSNAP.MSC ?
CERTMGR.MSC Cert 伺服器管理
CERTSRV.MSC Cert 伺服器
CIADMIN.MSC Index Server
COMPMGMT.MSC 電腦管理
DEVMGMT.MSC 硬體裝置
DEVTREE.MSC ?
DFRG.MSC ?
DFSGUI.MSC 分散式檔案系統管理員
DISKMGMT.MSC 磁碟管理
DNSMGMT.MSC dns管理
DOMAIN.MSC 網域樹管理
DSA.MSC 目錄管理
DSSITE.MSC Active Directory 站台及服務管理員
EVENTVWR.MSC 事件管理
FAXSERV.MSC 傳真管理
FSMGMT.MSC 檔案伺服器
GPEDIT.MSC ?
IAS.MSC ?
IPSEC.MSC ip 安全管理
IPSECDS.MSC ?
NETMGMT.MSC 網路服務管理
NTMSMGR.MSC 卸除式存放管理
NTMSOPRQ.MSC ?
RRASMGMT.MSC 路由及遠端存取管理員
SVCMGMT.MSC ?
SYSMON.MSC 系統監視
TAPIMGMT.MSC 電話語音
c:\winnt\system32\inetsrv\*.msc
IIS.MSC 網際網路服務管理
c:\winnt\system32\mts\*.msc
MTXEXP.MSC Transcation Server
9.再談 nt 下的輸入法
====================
我們上次提過，在 nt 下的輸入法設定是在 控制臺/鍵盤/輸入法
裡面，實在相當不合理。registry 的技術資料上則有些差別。
底下以大易輸入法在 nt 安裝為例。
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Keyboard Layouts\E0060404]
"layout file"="kbdus.dll"
"layout text"="大易"
"IME file"="DAYI.IME"
如果把大易裝在 win95/Win98 ，則是如此
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Keyboard Layouts\E0060404]
"layout file"="kbdus.kbd"
"layout text"="大易"
"IME file"="DAYI.IME"
看出來了嗎？kbdus.kbd 和 kbdus.dll 的差別。兩邊的 registry
不能混用。
10.Win98/NT5 並存的問題
=======================
無論是 NT5 工作站 或 伺服器 版本，皆可以與 win98 共存安裝。
也不必動到 Boot Manager 這種東西。安裝後可以使所有硬碟的
空間最揮到最高效益。當然我知道有些朋友是用「抽取式硬碟」來
達到所謂 Dual-Boot 的功能，這顆硬碟裝 Win98 ，那顆裝 nt4，
甚至還有人這顆硬碟是「燒錄專用」，那顆是「上網路專用」，第
三顆是「多媒體專用」，真的無須如此。
多花上幾顆硬碟的代價，能否換來系統的穩定？如果問我，答案是
否定的。曾在號稱不當機的 nt4 server ，照樣硬體當機，照樣燒
出一堆飛盤。關鍵不在 nt 本身是否「比較不會當機」，而在使用
者對nt 運作模式瞭解的多寡吧。
Win98/NT5 並存的安裝方式是：
1.第一個分割區，必須使用 fat/fat32 分割磁碟。
2.只能從 dos 開始安裝，不能從 win98 裡面安裝。
3. c:\Program Files 裡面，有些檔案會被 nt 安裝程式取代，比
如 Outlook Express, Netmeeting, Common Files/Microsoft
Shared，這部分並不能在 Win98/NT5 混用。要小心。
如果你的系統已經有 win98，在第一次安裝完後，或是系統在開始
PnP 抓新增硬體裝置時，通常會出現
-------------------------------------------------------
imm32.dll 錯誤，這不是正確的 nt 影像，請檢查你的安裝程式。
-------------------------------------------------------
原因很簡單，它檢查到 c:\windows\system\imm32.dll 了，不
要理它。或許你試看看把 path 環境變數拔掉，可能有點用。
錯誤訊息會一直警告，不過 PnP 裝置仍然可以正常安裝上去。
11.尋找/檔案或資料夾
====================
這是 Win95/Win98/NT4 皆有的功能。NT5 也不例外。
不過，NT5 利用 ie5 來完成這項功能。 :( 你可以看到它啟動了
ie5 後出現了「檔案搜尋」的功能。試找看看吧，打入 imm32 後
search ，哇，居然找不到 :(
其爛無比的設計。欠罵。 :(
12.新增/移除程式
================
這是 Win95/Win98/NT4 皆有的功能。NT5 也不例外。
不過，NT5 利用 ie5 來完成這項功能。 :(
在舊版的 beta 1733 裡面是新舊兩版並列，beta 1877 則只留一個。
不諱言說，除了提供了解除安裝的「提示句」之外，以及拖慢速度
之外，似乎看不到什麼好處。弟寧可比較喜歡舊版的方式。
在每一個解除安裝的「浮動列示」之下，按了之後會出現「請按此處
，取得支援資訊」，立意還算不錯，不過按了「支援資訊」的 link
後，出現了「版本」「線上支援」「連絡人」... 一堆之類的東西 (
一樣是利用 ie5 來開啟)，裡面的內容通通都是 unknown 。包括微
軟自己的軟體在內。甚至 NT5 裡面附的 Netshow tool 3.0 一樣沒有
支援這種功能。
看來這要軟體界的配合，還有很長很長的路要走。微軟想用 ie5 來
當這樣的平臺，未免野心也太大了。
在 新增移除程式/設定 Windows ，還得多按一下「元件」按鈕才會
出現想要的功能，蠻笨的而相當不直觀的設計方式。結果是呼叫另
外一個 dll 來完成設定 nt 自身的工作。
弟不欣賞這樣的設計，對使用者界面 (user interface) 毫無幫助
，對程式本身來說，也不可能因此就會移除的比較乾淨。
13.系統列內「拔出硬體」圖示
===========================
NT5 跑出這個東西，代表你可以在開機時拔離任何的週邊，想拔就拔，
豈不很好？不過弟試了，能拔的不過是滑鼠和 modem 而已 :( 頂多
再加上個 usb device :(
那個圖示怎麼把它消掉？沒什麼用處啊，如下步驟..
>控制臺/硬體精靈/拔除或退出硬體/按下一步/拔除或退出/在工作列上顯示圖示。
除非你確定你有很多東西 (比如 pcmcia 卡)可以這樣拔來拔去的，
要不然這玩意兒真的沒有用處。
抽取式硬碟可不可以這樣拔 ？當然不行。當然，我拔毀一顆的經驗。
14.捷徑
=======
捷徑觀念的處理，在 NT5 稍有改變。
每個捷徑 在選取後，按右鍵/內容/一般 已經可以直接改變捷徑名稱。
而 在選取後，按右鍵/內容/捷徑/說明 則可以讓使用者自行填入說明
，這些說明會直接變成捷徑的「黃色小標籤」tooltips ，算是相當
重要的「人性化」改進。
以往的 win98 則只能微軟內定的系統程式才享有這種殊榮，而且必
須在 registry 裡面動手腳才成。
除了捷徑，一般的檔案 在選取後，按右鍵/內容/變更 則可以直接變
更檔案開啟的關連程式。
15.字形-OpenType
=================
上次的報告裡簡略的提到了 OpenType ，這個跟倚天原先的「開放
字型規格」沒有關係，看來似乎是包含在 ttf 的一個 extension 功
能？請先到網路上找這個軟體 TrueType Font Properties ，微軟出
的 Shell Extension ，可裝在 Win95/98/NT 底下。我拿到的檔案版
本為 2.00.05 ，或許微軟那裡會有更新的檔案才對。先放在這裡。
英文版 (for Win95/98/NT)
ftp://ftp.nsysu.edu.tw/cpatch/system/ttfext/source/ttfext.exe (345K)
中文化版本 (for Win95/98/NT)
ftp://ftp.nsysu.edu.tw/cpatch/system/ttfext/cttfext.zip
這個工具安裝完後，在這裡留下檔案，當您選擇任何一個 *.TTF 字
型，按滑鼠右鍵/內容，依作業系統的不動，啟動下列 DLL功能。
c:\WINDOWS\SYSTEM\SHELLEXT\TTFEXT.DLL (for Win95/98, 260k)
c:\WINNT\SYSTEM32\SHELLEXT\TTFEXTNT.DLL (for WinNT, 268k)
如果沒有這個檔案，是很難判斷 ttf 字型的內部規格，更不要說對
OpenType 有什麼樣的瞭解了。
底下以 Arial, Courie 字型會例，做有無 OpenType 的比較。
我們可以看出帶 OpenType 屬性的字型體積都比較大？不過即使
在 win98或nt5 ，有沒有帶 OpenType 屬性都可以正常列印字型。
有趣的是，在 win98 裡面分別顯示 2.00 , 2.45 兩個版本(皆為
TrueType)，在NT5 裡面顯示的卻都是 2.60 (OpenType)，看
來 NT5 的字形 fontview 似乎有點小問題？
os fontfile ver OpenType size
----------------------------------------------
win98 arial.ttf 2.00 N 72,476
win98 arialbd.ttf 2.00 N 144,404
win98 arialbi.ttf 2.00 N 74,000
win98 ariali.ttf 2.00 N 80,548
win98 cour.ttf 2.00 N 105,308
win98 courbd.ttf 2.00 N 174,596
win98 courbi.ttf 2.00 N 90,704
win98 couri.ttf 2.00 N 90,988
NT5 arial.ttf 2.45 Y 253,760
NT5 arialbd.ttf 2.45 Y 265,656
NT5 arialbi.ttf 2.45 Y 206,744
NT5 ariali.ttf 2.45 Y 186,336
NT5 cour.ttf 2.45 Y 284.572
NT5 courbd.ttf 2.45 Y 292,168
NT5 courbi.ttf 2.45 Y 213,420
NT5 couri.ttf 2.45 Y 222,236
中文字的問題則比較大一些。這次提供的 mingliu.ttc, kaiu.ttf
都是 2.10 版，在 win98亦為 2.10 版，卻稍有不同。 win98 版
內沒有 OpenType 屬性，nt5 則有。字型的編碼都是使用 Unicode
(ISO 10646-2) ，造字的方面據說似乎是有所補齊了，但我們所需
求的「日文」則沒有看到，或許認為當年倚天中文所造日文字非
big5 標準，加以需考量CJK 的雙位元內碼，而未列入吧。
os fontfile ver OpenType size
----------------------------------------------
win98 mingliu.ttc 2.10 N 4,279,576
win98 kaiu.ttf 2.10 N 7,067,244
NT5 mingliu.ttc 2.10 Y 5,161,604
NT5 kaiu.ttf 2.10 Y 8,632,328
不過如果您有用 ttfext 去看這兩個字型，竟會發覺它們的
編碼規則是 PRC (People's Republic of China) ，也就是
中華人民共和國，而非使用 Taiwan。不曉得是華康科技在
製造 ttf 字形時參數搞錯了，還是我們的 ttfext 弄錯了？
有關 OpenType 的問題，您可以參考這個說明。
http://www.microsoft.com/typography/property/help.htm
16.字形-數位認證
================
不管您有沒有安裝 ttfext ，在 nt 環境底下，選擇任何一個 ttf 字型，
按滑鼠右鍵皆可出現「數位認證」的標籤。
「數位認證」原始目的，是要確保程式本身由原始發行公司所提供。包
括 crc 及fingerprint 等，都做了詳細的檢查與驗算。認證單位都是由
VeriSign 所做。但奇怪的是，只有 *.ttf 方有提供此種認證，其他程式
檔則沒有？
蠻值得一看的，雖然還不曉得它在實際用途上能有什麼用。Win98 及NT4
都沒有提供這個功能。
這部分微軟倒是已經中文化完成。
17.字形- TTFEXT 的相容性解決
============================
其實很希望微軟把這個 ttfext 加入 win98/NT5 的標準配備裡，畢竟這是
該有的資訊檔案。單純的 msinfo.exe 當然不能滿足使用者需要。當然囉，
也該把它中文化。
ttfext 本身安裝後，並沒有設定中文字集常用到的 *.ttc (TrueType
集合體)，麻煩您手動把底下內容存成存文字檔 ttc.reg ，點兩下執行，把
它匯入您的 registry 裡面。
---
REGEDIT4
[HKEY_CLASSES_ROOT\ttcfile\ShellEx]
[HKEY_CLASSES_ROOT\ttcfile\ShellEx\PropertySheetHandlers]
[HKEY_CLASSES_ROOT\ttcfile\ShellEx\PropertySheetHandlers\MSTrueTypeProperties]
@="{afc638f0-e8a4-11ce-9ade-00aa00a42d2e}"
---
NT5 beta3 b1978 測試報告
* updated by Kii Ali, 12-11-2001
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt5b1978.txt
Subject: NT5 beta3 b1978 測試報告
------------------------------------------------------------------------------------------
NT5 beta3 b1978 測試報告
updated by Kii Ali, 02-28-99
■目錄
1.寫在前頭
2.必也正名乎？
3.安裝 - dos
4.安裝 - win98
5.安裝 - 建議硬體配置
6.安裝 - NT5 減肥記
7.華麗的視窗 UI
8.語系 - Regional Options
9.語系 - Language Setting for the System
10.語系 - Setting for Current User
11.語系 - 目前使用者設定的 reg 檔
12.語系 - NT5 已有的實作
13.語系 - Input Locales
14.字型 - 書同文
15.字型 - 細明 3 的缺點
16.硬體 - 硬體精靈 & 裝置管理員
17.硬體 - 支援的儲存方式
18.硬體 - 列印支援的增強
19.硬體 - 共用 MODEM
20.硬體 - 不相容列表
21.多媒體 - Win32 Driver Model(WDM)
22.多媒體 - DirectX
23.管理工具 - Darwin
24.管理工具 - Group Policy Editor
25.檔案 - 尋找檔案
26.檔案 - NT 的檔案系統
27.檔案 - 開啟檔案對話方塊
28.控制臺元件
29.捷徑觀念
30.登錄程式 regedit.exe
31.使用者設定檔路徑
32.結論與建議
33.版權
■1.寫在前頭
* 在您看這篇時，建議調整信件軟體的顯示字形為 細明體 12 或 System 12
* 。否則部分表格與文字，會無法對齊或是發生移位。
寫測試報告是很痛苦的事，很耗時間和精力。但寫完測試報告，則是極其快樂
的事，那代表又玩爛了一個軟體。
我不敢說能夠把 NT5 玩爛，或是能把 NT5 架構上的觀念與實作都全部測試完
，一方面是配備太差，另一方面是在市面沒有任何相關書籍的情形下，這樣子
不免瞎子摸象之嫌。網路上 NT 的高手比比皆是，在 NT4 都不夠爛熟的情形
下，我只不過是在海邊玩耍的小朋友，面對遼闊的大海只能撿幾顆小石頭，跟
大家分享經驗罷了。錯誤的地方一定很多，還請指正。
先前已經有幾位朋友寫過的測試報告，包括 Kii Ali (還是我啦 )對 1877 的
兩篇報告，以及 JAZZ 對 1978 安裝過程的一些質疑。因此請您先看過這些，
對 NT5 的架構和測試理念有個基本的瞭解。所有在舊版測試過的項目和理念
，將儘可能不再重覆。如下。
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt5b1877.txt
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt5b1877_1.txt
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/b_nt5b1978.txt
另外，這篇是「測試報告」，而不是「功能簡介」。因此無可避免會摻雜了筆
者個人的觀感、意見、甚至牢騷。KA 的意見不一定是正確，甚至有可能是錯
誤的。如果您希望能全盤瞭解 NT5 的架構，請直接看光碟裡面的 Release
Notes，300 k 左右的英文，這樣會比較快，也應該不會太難讀才對。弟是希
望能把實作的情形提出來探討，而不是陷在生硬專有名詞和廣告詞句一堆的
Release Notes 來打轉。
如果部分提及的內容太難，看不懂或是看得頭痛，建議您直接跳過，裝完 NT5
有實作經驗後，再回來看。
在 1978 的測試報告中，由於取得光碟的缺陷，語系元件支援則是取自 1948
的內容 (這些元件包括 ara 阿拉伯文、chs 中文簡體、cht 中文繁體、heb
希伯來文、ind 印度、tha 泰國、jpn 日本、kor 韓國 )。所幸這個部分大部
分是字形和輸入法的軟體，再更新的機會已經不大。我是 1948 1978 兩個版
本都安裝過了。
NT5 的新增功能很簡單，IE5 + IIS5 + Outlook Express 5 + 多語系支援 +
FAT32 + quota + NTFS5 + 網際網路印表.. 大概就這樣子，您可以很單純的
這樣認為。底下就不用再看 ka 廢話下去囉。
■2.必也正名乎？
NT5 已經正式改名。
包括的登入畫面、程式的 about 部分，ntldr 和一些大大小小的地方都換成
windows 2000 的名稱。當然有些小地方微軟沒有用心測試及換完 (比如 NT5
reskit 的部分 )。有些則是名稱不是很統一，比如登入畫面是 Windows 2000
Professional，在 about 畫面則是稱 Windows Version 5.0。至於是否為有
版權爭議把 windows 2000 多弄個 Professional (專業版?) 字樣，就不得而
知。
比起 beta2 在使用者介面改了很多，最明顯的是淡藍色的窗子改成橘子色的
窗子。只是由於過於強調 Windows 2000，以致所有的 Windows 內建程式的
about 畫面都強迫掛上了 Windows 2000 的橘子色視窗 banner，看來未免過
於華麗而「大而無當」。如果您在 NT5 內檢視以前 win98 的內建程式，會很
驚異的發現，他們的 about 畫面和版次全部都換成 5.0 build 1978，然後也
掛上了 Windows 2000 橘子色視窗畫面。顯示的版次是完全不對的。
換句話說，微軟連自己軟體的 about 畫面顯示都要「強姦」了。這實在是非
常不好的習慣。:(
必須承認，beta 3 版本的 Windows 2000 使用者介面外表上，愈來愈不像傳
統 NT，但 Windows 2000 在核心運作上仍完全是 NT 的觀念。
所以，本文仍將以 NT5 做為主要的稱呼。
■3.安裝 - dos
一般都是從 dos 底下用光碟安裝。安裝的參數如下。我們最熟悉的 winnt /b
參數已經不見了。
Installs Windows NT.
WINNT [/S[:]sourcepath] [/T[:]tempdrive] [/I[:]inffile]
[[/U[:scriptfile]]
[/R[x]:directory] [/E:command] [/A]
/A Enable accessibility options.
/E Specifies command to be executed at the end of GUI setup.
/I[:]inffile
Specifies the filename (no path) of the setup information file.
The default is DOSNET.INF.
/R Specifies optional directory to be installed.
/Rx Specifies optional directory to be copied.
/S[:]sourcepath
Specifies the source location of Windows NT files.
Must be a full path of the form x:\[path] or
\\server\share[\path].
The default is the current directory.
/T[:]tempdrive
Specifies a drive to contain temporary setup files.
If not specified, Setup will attempt to locate a drive for you.
/U Unattended operation and optional script file (requires /s).
如果您用了參數 /a，可以多了三個選項，選擇「放大鏡」「聲音鍵」等在安
裝過程方便聽力視力不便人士的措施。同樣，在 Win98 情形安裝時一樣可以
選擇。
安裝時記得加上 smartdrv 快取程式，否則 dos portion 安裝部分，光是複
製到硬碟的時間就得一個半小時。而這只不過是把光碟裡面的 5600 個檔案全
部 copy 到硬碟的暫存目錄。之後才會載入 ntldr 進行真正的安裝。檔案實
在太多，在複製的過程中很容易漏失掉，建議您先複製到硬碟上，比較快，也
沒有檔案漏掉的問題。只是要先多佔 380mb 的空間，對硬碟小的朋友很傷腦
筋。
微軟應該用 win98 的 *.cab 檔的方式，否則 1978 版 5407 個檔案 (1948
版則是 7300 個檔案 )，對安裝者而言困擾極大，dir 都要老半天。如果掛了
4dos 而 environment 設定不夠大，dir 還會出現 out of environment
space 的訊息。
(這是廢話，不過在一個目錄下 5407 個小檔案，對燒片子來說，實在是很可
怕的事情。燒掛了三片又降速才燒好。新防拷措施？)
■4.安裝 - win98
不得不承認，靠著微軟的廣告功力所賜，在 Win98 底下安裝的畫面很令人耳
目一新。 1948 的畫面不過如舊版的 nt4 autorun，1978 是真的漂亮。但是
1978 在進入時則會告訴你 winnt32.exe 找不到，所以把你踼出來了。1948
無此問題。原來 1948 把 winnt.exe, winnt32.exe 放在同一個目錄下，1978
則在 nt5\winnt32 裡面。
安裝的第一個畫面是英文的 (有點失望 )，可以選 Locale 語系的定義，當然
我們會很興奮的去翻，咦，怎麼有了 Catalan，就是沒有 Chinese (Taiwan)
？好吧，在 Language Setting for system 可以選 Traditional Chinese，
將就著選吧。如果你有要做中文化的需求，請記得多勾一個 Simplified
Chinese。
然後第二個問題，安裝程式會告訴你語系不同，所以不能 upgrade，或是乾脆
將你踼出。
如果安裝程式已經開始複製，別太高興，等一下還是要進 dos 模式作業，所
以如果你的光碟是燒 Romeo 格式，在純 dos 底下 mscdex 無法進入 Romeo
格式的目錄，到時候就要跳腳。
所以弟還是建議從 DOS 模式開始裝。在 win98 底下如果犯錯誤，花掉的時間
恐怕不會 dos 模式少。
■5.安裝 - 建議軟硬體配置
1.記憶體：
記憶體將是玩 NT5 的最大限制。
在弟這裡的情形，1978 只開了 UltraEdit 6.0, Powerdesk 2.04, 這樣就要
吃掉 62M。遠比 NT5 beta 2 (差不多 43M)，NT4 還要兇。如果您像弟一樣只
有 64M 的記憶體，玩起來會有點累，程式一多就可以聽到 swap 動作時硬碟
的聲音。硬碟上的 pagefile 已經到 100M 之多。
如果記憶體不夠多，又只想在 fat32 上跑 NT5 方便做中文化，NT5 1877 或
許是比較好的選擇。
2.CPU:
至少要 p200 以上才有能看的效率。
3.VGA
PCI 顯示卡已經是最基本的要求，以前的舊式 ISA 卡在驅動程式清單上已
經找不到了，如同 Jazz 所說，支援了 Banshee ，有巫毒卡的傢伙不妨拿
來在 NT5 上操看看。
4.Reg 檔
1978 匯出來的 reg 檔高達 6mb，這是很沈重的負擔，要有一些心理準備。
如果只是純想玩 nt5 本身，可以把 IE5 相當的 reg 設定砍掉一些。
5.shell 介面
我們拿到的 1978 1948 其 shell 裡面都只有英文版的 resource，顯示全部
都是英文的，雖然可以輸入和處理中文，但總是有一些不便。至少，看起來就
比較沒有那麼順眼。
如果只是要一個可裝在 FAT32 的 NT 系統，1877 會是比較好的選擇。
6.建議一定要裝的小程式
6-1.TweakUI cpl ，控制臺元件，可以讓你省一些無聊的登入手續及時間。
6-2.DirectX cpl ，控制臺元件，讓你看一些 DirectX 的資訊。
6-3.TTFext ，Shell Extension，取得 True Type 字型的資訊。
ftp://ftp.nsysu.edu.tw/cpatch/system/tweakui/ctweakui125_4.zip
ftp://ftp.nsysu.edu.tw/cpatch/system/directx/cdx6cpl.zip
ftp://ftp.nsysu.edu.tw/cpatch/system/ttfext/cttfext.exe
■6.安裝 - NT5 減肥記
請執行這個批次檔，馬上減肥。這個批次檔在 win98 一樣可以通用。只要把
c:\winnt\ 換成 c:\windows\ 即可。
記得這個原則，在同一個目錄下的檔案數愈少，尋找起來愈快。整合後的批次
檔如下。您可以把不需要的部分 rem 掉。我儘可能把說明寫詳細。
DELTRASH.BAT
: 1.解決一輩子也不會看的垃圾檔
DEL /Y C:\WINNT\*.TXT
DEL /Y C:\WINNT\*.BMP
DEL /Y C:\WINNT\*.GIF
DEL /Y C:\WINNT\*.HTT
DEL /Y C:\WINNT\*.HTZ
DEL /Y C:\WINNT\*.ICO
DEL /Y C:\WINNT\*.---
DEL /Y C:\WINNT\*.LOG
DEL /Y C:\WINNT\DISCOVER*.*
DEL /Y C:\WINNT\README*.*
DEL /Y C:\WINNT\WELCOME*.*
DEL /Y C:\WINNT\TOUR*.*
: 2.想要速度快，把那些花俏的東西，包括螢幕保護程式弄掉。
: 音效只要留 Musica 的就可以 (因為最小)，甚至連 Musica
: 都可以不留。
: 2-1. 把多餘的游標砍掉。
copy C:\WINNT\CURSORS\APPSTART.ANI c:\temp
copy C:\WINNT\CURSORS\GLOBE.ANI c:\temp
copy C:\WINNT\CURSORS\HOURGLAS.ANI c:\temp
DEL /Y C:\WINNT\CURSORS\*.*
copy c:\temp\APPSTART.ANI C:\WINNT\CURSORS
copy c:\temp\GLOBE.ANI C:\WINNT\CURSORS
copy c:\temp\HOURGLAS.ANI C:\WINNT\CURSORS
: 2-2. 把螢幕保護程式弄掉。
DEL /Y C:\WINNT\*.SCR
: 2-3. 把音效 wav, mid, rmi 弄掉。只留 Musica 和基本音效。
copy C:\WINNT\MEDIA\CHIMES.WAV c:\temp
copy C:\WINNT\MEDIA\CHORD.WAV c:\temp
copy C:\WINNT\MEDIA\DING.WAV c:\temp
copy C:\WINNT\MEDIA\Musica*.WAV c:\temp
copy C:\WINNT\MEDIA\NOTIFY.WAV c:\temp
copy C:\WINNT\MEDIA\RECYCLE.WAV c:\temp
copy C:\WINNT\MEDIA\TADA.WAV c:\temp
DEL /Y C:\WINNT\MEDIA\*.*
copy C:\TEMP\CHIMES.WAV C:\WINNT\MEDIA
copy C:\TEMP\CHORD.WAV C:\WINNT\MEDIA
copy C:\TEMP\DING.WAV C:\WINNT\MEDIA
copy C:\TEMP\Musica*.WAV C:\WINNT\MEDIA
copy C:\TEMP\NOTIFY.WAV C:\WINNT\MEDIA
copy C:\TEMP\RECYCLE.WAV C:\WINNT\MEDIA
copy C:\TEMP\TADA.WAV C:\WINNT\MEDIA
: 3.可以不用的英文 ttf 字形檔。一般使用都是 Times New Roman。
DEL /Y C:\WINNT\FONTS\VERDANA*.TTF
DEL /Y C:\WINNT\FONTS\TREBUC*.TTF
DEL /Y C:\WINNT\FONTS\GEORGIA*.TTF
DEL /Y C:\WINNT\FONTS\PALA*.TTF
: 4.pnf 檔是編譯後的 inf 檔，當然可以砍。Winnt 安裝時會自動產生。
DEL /Y C:\WINNT\INF\*.PNF
: 5.如果你不使用 winnt 內定的 modem ，或是你已經有 modem 的安裝 inf 檔，
: 還可以把 mdm*.* 全砍。
DEL /Y C:\WINNT\INF\MDM*.*
: 6.網路卡驅動程式定義 inf 也可以砍。但由於由於網路卡驅動程式，網
: 路服務和協定程式都使用 NET*.INF 開頭，因此要保留底下這幾個。其他
: 一百五十幾個全部都可以砍掉。批次檔如下。
copy C:\WINNT\INF\NET21X4.INF C:\TEMP
copy C:\WINNT\INF\NETDLC.INF C:\TEMP
copy C:\WINNT\INF\NETIPRIP.INF C:\TEMP
copy C:\WINNT\INF\NETLPD.INF C:\TEMP
copy C:\WINNT\INF\NETMSCLI.INF C:\TEMP
copy C:\WINNT\INF\NETNB.INF C:\TEMP
copy C:\WINNT\INF\NETNBF.INF C:\TEMP
copy C:\WINNT\INF\NETNM.INF C:\TEMP
copy C:\WINNT\INF\NETNWCLI.INF C:\TEMP
copy C:\WINNT\INF\NETNWLNK.INF C:\TEMP
copy C:\WINNT\INF\NETPSA.INF C:\TEMP
copy C:\WINNT\INF\NETPSCHD.INF C:\TEMP
copy C:\WINNT\INF\NETRASA.INF C:\TEMP
copy C:\WINNT\INF\NETRASS.INF C:\TEMP
copy C:\WINNT\INF\NETRAST.INF C:\TEMP
copy C:\WINNT\INF\NETRWAN.INF C:\TEMP
copy C:\WINNT\INF\NETSAP.INF C:\TEMP
copy C:\WINNT\INF\NETSERV.INF C:\TEMP
copy C:\WINNT\INF\NETSNMP.INF C:\TEMP
copy C:\WINNT\INF\NETSTRM.INF C:\TEMP
copy C:\WINNT\INF\NETTCPIP.INF C:\TEMP
copy C:\WINNT\INF\NETTPSMP.INF C:\TEMP
copy C:\WINNT\INF\NETUPGRD.INF C:\TEMP
DEL /Y C:\WINNT\INF\NET*.INF
copy C:\TEMP\NET21X4.INF C:\WINNT\INF
copy C:\TEMP\NETDLC.INF C:\WINNT\INF
copy C:\TEMP\NETIPRIP.INF C:\WINNT\INF
copy C:\TEMP\NETLPD.INF C:\WINNT\INF
copy C:\TEMP\NETMSCLI.INF C:\WINNT\INF
copy C:\TEMP\NETNB.INF C:\WINNT\INF
copy C:\TEMP\NETNBF.INF C:\WINNT\INF
copy C:\TEMP\NETNM.INF C:\WINNT\INF
copy C:\TEMP\NETNWCLI.INF C:\WINNT\INF
copy C:\TEMP\NETNWLNK.INF C:\WINNT\INF
copy C:\TEMP\NETPSA.INF C:\WINNT\INF
copy C:\TEMP\NETPSCHD.INF C:\WINNT\INF
copy C:\TEMP\NETRASA.INF C:\WINNT\INF
copy C:\TEMP\NETRASS.INF C:\WINNT\INF
copy C:\TEMP\NETRAST.INF C:\WINNT\INF
copy C:\TEMP\NETRWAN.INF C:\WINNT\INF
copy C:\TEMP\NETSAP.INF C:\WINNT\INF
copy C:\TEMP\NETSERV.INF C:\WINNT\INF
copy C:\TEMP\NETSNMP.INF C:\WINNT\INF
copy C:\TEMP\NETSTRM.INF C:\WINNT\INF
copy C:\TEMP\NETTCPIP.INF C:\WINNT\INF
copy C:\TEMP\NETTPSMP.INF C:\WINNT\INF
copy C:\TEMP\NETUPGRD.INF C:\WINNT\INF
: 7.如果螢幕不是「非常有名的」，通常 NT 抓不到。連我的 Sampo 521
: 都找不到了，全砍可也。
DEL /Y C:\WINNT\INF\MONITOR*.*
: 8. 如果英文的 help 八百年看不到一次，全砍可也。就算是中文的 help
: 其實我也很懶得看。
DEL /Y C:\WINNT\HELP\*.*
: 9. 一卡車微軟垃圾程式，包括 MSAGENT, SPEECH, WEB, VCM,
: 注意：這裡為方便起見，直接使用 deltree 指令。如果不管
: ie5，再把 java 幹掉。即使沒有 java 目錄一樣可以執行ie5。
DELTREE /Y C:\WINNT\MSAGENT
DELTREE /Y C:\WINNT\SPEECH
DELTREE /Y C:\WINNT\WEB
DELTREE /Y C:\WINNT\VCM
DELTREE /Y C:\WINNT\DRWATSON
DELTREE /Y "C:\WINNT\Downloaded Programs Files"
DELTREE /Y C:\WINNT\JAVA
DELTREE /Y "C:\WINNT\Offline Pages"
: 10.最大的垃圾檔，41.8mb
DELTREE /Y "C:\WINNT\Driver Cache"
: 11.inf 目錄中的 exe 程式，mplayer2，1.0MB。
DEL /Y C:\WINNT\INF\UNREGMP2.EXE
DEL /Y C:\WINNT\INF\UNREGPN.EXE
: 12.如果可以不管無聊的 ie5 安全性，還可以再減 7.5MB。
DELTREE /Y C:\WINNT\SECURITY
: 13.再狠一點，把用不到的個人設定檔砍掉。只留單一使用者的設定檔便可。
: 只有 "All Users (WINNT)" 不能刪掉。
DELTREE /Y "C:\Documents and Settings\All Users"
DELTREE /Y "C:\Documents and Settings\Default User"
DELTREE /Y "C:\Documents and Settings\Default User (WINNT)"
■7.華麗的視窗 UI
任何人一安裝完，都不免要為 NT5 1978 華麗的 icon 著迷。包括「我的電腦
」、「網路上的芳鄰」、「資源回收筒」。甚至連「 Internet 連線精靈」都
硬是好看起來。即使是在 256 色不驅動 Plus! 的情形下，仍然要說其 icon
的確好看。
配色與字形方面，把 Win98 的水泥灰轉成特別的象牙白，畫面柔和許多。字
型的標題與螢幕字體改採用 Tahoma 8 Bold，雖然只是小變化，視窗卻呈現了
特異的風格與景致，尤其是英文字母，這要歸功於 Tahoma 字形的特殊質感。
對於一般繁體中文 Win98 的使用者，初見之下不免稍不習慣，卻很舒服。如
果是難看的簡體中文 win98，使用感簡直差別太大了。很難得看到微軟對內定
值肯下這種功夫。
能不能把我的 Win98 顏色與視窗風格，抄得跟 NT5 配置很像？當然可以的，
不過 NT5 的細明體 3.0 跟 Tahoma 8 搭配起來沒有問題，Win98 內建的細明
體 2.1 就不那麼好看。另外，Win98 附的 Tahoma 2.25 版，而 NT5 是
Tahoma 2.30 版本。您試看看。
各項參數如下。H:Hue彩度 , S:Sat飽合, L:Lum亮度, R:Red, G:Green, B:Blue
Desktop(桌面) H:141 S:115 L:105 R: 58 G:110 B:165 靛藍
Active Title Bar(使用中視窗), 18
Color1 H:149 S:199 L: 55 R: 10 G: 36 B:106 深藍
Color2 H:141 S:171 L:191 R:166 G:202 B:240 淺藍
Font Tahoma 8 , Bold, 白
Menu (功能表) H: 27 S: 29 L:194 R:212 G:208 B:200 象牙白
Font Tahoma 8, 黑
Message Box, (訊息方塊)
Font Tahoma 8, 黑
3D Objects(物件) H: 27 S: 29 L:194 R:212 G:208 B:200 象牙白
Inactive Title Bar(非現用視窗), 18
Color1 H:160 S: 0 L:120 R:128 G:128 B:128 灰
Color2 H:160 S: 0 L:181 R:192 G:192 B:192 淺灰
Font Tahoma 8 , Bold
字型顏色 H: 27 S: 29 L:194 R:212 G:208 B:200 象牙白
ToolTip(工具提示) H: 40 S:240 L:246 R:255 G:255 B:225 淡淺黃
當然也有一些小問題。BC++ 5.02 使用者，會因 Tahoma Bold 字體過大而導
致操作不便。
■8.語系 - Regional Options
這是 1978 最重要的改進。
Jazz 之前的報告提到，如果在安裝時沒有選擇語系時，便會一路英文版到底
。如果在 DOS 安裝也是只出現英文版。其實，1978 已經有實作方式出來了，
只不過我們拿到的 1948 1978 都只有美式英文 (0409) 的 resource 而已，
畫面只能看到英文。但內部已經可以支援簡體繁體中文字顯示，和中文輸入法
。
在控制臺裡有個 Regional Options，Win98 裡面翻譯成「國別設定」，包括
貨幣、數字、時間、日期等設定，好像沒什麼用，我們在 Win98 也很少管它
做什麼。在 Win98 只要一動到國別設定，就必須重新開機。
NT5 不同，不用重新開機，立即生效。
NT5 的 Regional Options 多增了兩樣。而這兩樣底下又一堆東西。
1.General 1.(一般)
Setting for Current User (目前使用者設定)
Language Setting for the System (系統語言設定)
2.Input Locale 2.(輸入法)
Install Input Locales (安裝輸入法)
Input Language (輸入語言)
Layout/IME (鍵盤配置/輸入法)
Hot Keys for Input Locales (快速鍵設定)
其中 Input Locale 在 Win98 是獨立的「輸入法」，在 NT5 則可分別在「國
別設定」和「鍵盤」這兩項中找到。
■9.語系 - Language Setting for the System
必需先設定這個「系統語言」，才能設定「使用者語系」和其後的「輸入法」
。目前表列支援的有以下語言，當然，很多語系微軟並沒有實做。根據前面所
提的，語系元件取自 1948 的內容 (這些元件包括 ara 阿拉伯文、chs 中文
簡體、cht 中文繁體、heb 希伯來文、ind 印度、tha 泰國、 jpn 日本、kor
韓國 )，因此恐怕有部分元件無法進行設定。
阿拉伯 Arabic
亞美尼亞 Armenian
波羅的海 Baltic
中歐 Central Europe
斯拉夫語 Cyrillic
喬治亞 Georgian
希臘 Greek
希伯來語 Hebrew
印度 Indic
日本 Japanese
韓國 Korean
中文簡體 Simplified Chinese
泰國 Thai
中文繁體 Traditional Chinese
土耳其 Turkic
越南 Vietnamese
西歐美國 Western Europe and United States
一般說來，第一次安裝後的 [default] 都出現在美國。請把簡體中文和繁體
中文打勾，並把繁體中文設成 [default]。如果你把 [ 中文繁體 ] 設定成預
設值，所有內部運作的語系，甚至包括填寫在 registry 的內容將以 BIG5 為
主。相同的，如果你把 [ 中文簡體 ] 設定成默認值，那麼內部運行的語系都
會是 GB2312。
且由於 MagicWin 之類的軟體無法在 NT5 上面正常運作，加入中文簡體和日
文便成為必要動作。不過日文語系的支援要 35mb 左右，實在也太大了一些。
加入新增的語系之後，會到光碟的 lang 目錄去找字形與輸入法檔案。然後重
新開機。
這跟上面的「目前使用者設定」是無關的。你甚至可以把內部語系設定成簡體
，目前使用者設定為 Chinese (Taiwan)。如此你的文件以 gb2312 做為內碼
標準，但看的程式界面都是繁體中文。而且還可以隨時切換。
這在中文化非常有用。
■10.語系 - Setting for Current User
微軟的官方說法是「設定貨幣、數字、日期、時間」等等。更重要的，如果程
式支援多語系，出現的將是那一個語系。
比如說，你想要看到繁體中文的「光碟、滑鼠、游標」，還是看到簡體中文的
「光盤、鼠標、光標」，還是英文 cdrom, mouse, cursor？這還可以線上切
換。前提是，必須安裝前述的「系統語系設定」。否則， c 開頭的一定只有
Catalan，就是沒有 Chinese。
有趣的是，只有在中文才會出現 Sorting Order (排序方式)。
1.Chinese (Taiwan)
排序方式包括 Stroke Count (筆劃 ), Unicode Order (Unicode 排序 ),
Bopomofo (看不懂？ㄅㄆㄇㄈ啦 )。第一項為內定值。臺灣慣用筆劃來排序
的，而 big5 碼編碼也是用筆劃排序，實在比較不科學。連中華郵政的三加
二郵遞區號軟體，也已經捨棄筆劃而就拼音法。
2.Chinese (PRC, Singapore, Hong Kong, Macau)
排序方式包括 Pronunciation (發音 ), Unicode Order (Unicode 排序 ),
Stroke Count (筆劃)。以第一項發音為內定值。
ps. 我們在實作的過程中發現，其實系統還是會以 reg 檔內定的 0409 語系
(美式英文) 做顯示。只有在程式不含英文語系時，才會自動切換簡體或繁體
。但對中文化來說，已經相當夠用了。原因在這這裡，在變更 locale 時不會
動到這個 registry ，所以程式仍維持英文狀態。
[HKEY_USERS\.DEFAULT\Control Panel\International]
"iCountry"="1"
"iCurrDigits"="2"
"iCurrency"="0"
"iDate"="0"
"iDigits"="2"
"iLZero"="1"
"iMeasure"="1"
"iNegCurr"="0"
"iTime"="0"
"iTLZero"="0"
"Locale"="00000409"
"s1159"="AM"
"s2359"="PM"
"sCountry"="United States"
"sCurrency"="$"
"sDate"="/"
"sDecimal"="."
"sLanguage"="ENU"
"sList"=","
"sLongDate"="dddd, MMMM dd, yyyy"
"sShortDate"="M/d/yy"
"sThousand"=","
"sTime"=":"
■11.語系 - 目前使用者設定的 reg 檔
線上切換的內定值註冊登錄檔在這裡。跟 Win98 的位置有很大不同。主要的
變更包括 "Locale" 語系編號、"sLanguage" 語系名稱等等。
[HKEY_USERS\S-1-5-21-1202660629-813497703-1957994488-1000\Control Panel\International]
"iCountry"="886"
"iCurrDigits"="2"
"iCurrency"="0"
"iDate"="2"
"iDigits"="2"
"iLZero"="1"
"iMeasure"="0"
"iNegCurr"="1"
"iTime"="0"
"iTLZero"="1"
"Locale"="00000404"
"s1159"="上午"
"s2359"="下午"
"sCountry"="Taiwan"
"sCurrency"="NT$"
"sDate"="/"
"sDecimal"="."
"sLanguage"="CHT"
"sList"=","
"sLongDate"="yyyy'年'M'月'd'日'"
"sShortDate"="yyyy/M/d"
"sThousand"=","
"sTime"=":"
"sTimeFormat"="tt hh:mm:ss"
"iTimePrefix"="1"
"sMonDecimalSep"="."
"sMonThousandSep"=","
"iNegNumber"="1"
"sNativeDigits"="0123456789"
"NumShape"="1"
"iCalendarType"="1"
"iFirstDayOfWeek"="6"
"iFirstWeekOfYear"="0"
"sGrouping"="3;0"
"sMonGrouping"="3;0"
"sPositiveSign"=""
"sNegativeSign"="-"
■12.語系 - NT5 已有的實作
這是根據 1978 的 agt*.dll 所查出來的。所以 NT5 雖然定義了許多新語系
，包括許多民族方言與地方語系，市場上的接受度還是比較重要。以英語為例
，只有美式英文一個版本，沒有英國版，因為沒有必要。
"00000401"="Arabic (Arabic)" ;阿拉伯
"00000404"="Chinese (Traditional)" ;繁體中文
"00000405"="Czech" ;捷克
"00000406"="Danish" ;丹麥
"00000405"="Czech" ;捷克
"00000406"="Danish" ;丹麥
"00000407"="German (Standard)" ;德國
"00000408"="Greek" ;希臘
"00000409"="English (United States)" ;美國
"0000040B"="Finnish" ;芬蘭
"0000040C"="French (Standard)" ;法國
"0000040D"="Hebrew" ;希伯來
"0000040E"="Hungarian" ;匈牙利
"00000410"="Italian (Standard)" ;義大利
"00000411"="Japanese" ;日本
"00000412"="Korean (Standard)" ;韓國
"00000413"="Dutch (Standard)" ;荷蘭
"00000414"="Norwegian (Bokmal)" ;挪威
"00000415"="Polish" ;波蘭
"00000416"="Portuguese (Brazilian)" ;巴西
"00000419"="Russian" ;俄文
"0000041D"="Swedish" ;瑞典
"0000041E"="Thai" ;泰國
"0000041F"="Turkish" ;土耳其
"00000804"="Chinese (Simpilified)" ;簡體中文
"00000816"="Portuguese (Standard)" ;葡萄牙
"00000C0A"="Spanish (Modern Sort)" ;西班牙(現代腔?)
有關語系定義的相關資料，您可以參考這裡。
ftp://ftp.nsysu.edu.tw/cpatch/faq/tech/tech_nls98.txt
ftp://ftp.nsysu.edu.tw/cpatch/faq/tech/tech_nlsnt.txt
■13.語系 - Input Locales
輸入法的加入方式跟 win98 有很大不同。加入時必需先選定 Input Locales
為 Chinese (Taiwan) 才能選擇到正常的中文輸入法，包括
Chinese (Traditional) - Alphanumenic 字母排序？
Chinese (Traditional) - Array 行列
Chinese (Traditional) - Big5 Code 內碼
Chinese (Traditional) - ChangJie 倉頡
Chinese (Traditional) - Quick 快碼
Chinese (Traditional) - Unicode Unicode
大易 大易
新注音 新注音
新倉頡 新倉頡
如果是選定 Chinese (PRC) ，則有
Chinese (Simpilified) - NeiMa 內碼
Chinese (Simpilified) - QuanPin 快拼
Chinese (Simpilified) - ShuangPin 雙拼
Chinese (Simpilified) - ZhengMa 鄭碼
微軟新拼音輸入法 微軟新拼音輸入法
另外這些輸入法支援了雙語系。亦即你若切換系統為簡體，仍然可以用注音來
輸入 GB 2312 編碼的字，習慣完全不用改變，很類似 Global IME 的觀念。
但某些非微軟內建的舊輸入法就沒這麼好運了，比如我手上用的大易九萬詞庫
(K 某人所做版本 )，換到簡體中文下就無用武之地。
某些未加 "Chinese (Traditional) - " 開頭的輸入法，像「新注音」「新倉
頡」「大易」「微軟新拼音」等能不能支援 Unicode？弟不能肯定。
■14.字型 - 書同文
有關字型的部分，您可以參考這裡，說的比較詳細。除了華康細明體 Mingilu
3.0 內含字型數改為 22550 (原本 1877 內 Mingliu 3.0 的字數為 22535 )
之外，其他沒有變。據說這篇也是 K 某人所寫的。
ftp://ftp.nsysu.edu.tw/cpatch/faq/tech/tech_nls0.txt
Mingliu 3.0 跟 Win98 所附 2.1 版不同點，在於 3.0 版支援了 1252 及
950 兩種語系 (英文及繁體中文 )，而 2.1 版只有 950 語系 (繁體中文 )。
3.0 版可以顯示「簡體中文」，而 2.1 版不行。同樣的，簡體的新宋體」和
「黑體」一樣可以顯示繁體中文。有沒有搞錯？新細明體可以顯示簡體中文，
宋體可以顯示繁體中文？
我們做個實驗。
把這篇文章丟到 UltraEdit，調整顯示字體為 SimSun 12，能不能顯示？不行
。不過把 Script (Win98 譯為指令檔 )從 Chinese_GB2312 換成 Western 再
看看，可不可以？
於是我們看到了繁體中文，只是這種繁體中文不太習慣，實在沒有華康字漂亮
。至少比起實在不好看的簡體 Win98 好多了。同樣在簡體環境下，一樣可以
用華康，把 Chinese_Big5 換成 Western 就可以看到簡體中文。
這樣的好處是，秦始皇在兩千多年前所提出的「書同文」，統一中國文字，或
許在 NT5 上就可以付諸實現？
不過扯到秦始皇，也扯太遠了 (笑 )。政治姑不論，文字不統一，卻實在是後
人的悲哀，還要讓老外拿個 Unicode 來統一，怪誰？(苦笑 )。
■15.字型 - 細明 3 的缺點
字型的數目增多了，字型的使用習慣卻走回頭路。全形的句號、全形的逗號都
縮小到左下角，橫寫還勉強可以看，若是直印出來，真是讓人倒足胃口。大陸
的宋體包括逗號，也是縮小在左下角，看起來就像民國二十年左右印出來的徐
志摩小說。日文的 Mincho 字體也是如此。
難看。中日台三地字型商的腦袋和審美觀，不曉得跑到那裡了？
字型方面，非常推薦使用 NT5 1877 測試版的細明體 Mingliu 3.0 版，雖然
少了 15 個字，但是標點符號的位置都對。再不行，就用 Win98 內附的 2.1
版。
■16.硬體 - 硬體精靈 & 裝置管理員
Release notes 把這裡寫的跟廣告詞差不多。包括 Plug and Play，Attach
Hardware more easily than ever 等等。NT5 官方說法最稱道的包括其「硬
體精靈」，和套在 MMC 1.2 架構底下的「裝置管理員」。
比起沒有 PnP 觀念的 NT4，「硬體精靈」的觀念的確是進步了不少。但坦白
說，測過了 17xx, 1877, 1948, 1978，感覺是「都很難用」。「硬體精靈」
和「裝置管理員」所開的太多視窗與耗掉的 gdi，都使 NT5 愈來愈像怪獸。
圖示很多，畫面操作起來比起 Win98 繁瑣，用起來很難跟 "Attach Hardware
more easily than ever" 聯想在一起。
另外，對硬體的支援包括了 WDM, 多媒體方面。
有人一定要懷疑，在 beta2 才 mmc 1.1 而已，現在就換到 1.2 版？要麻煩
你自行去用手動安裝了。在這裡。1978 對 mmc 的安裝並不正常。
E:\NT5\FIX\*.*
把這個目錄底下的所有檔案，全部複製到 C:\WINNT\SYSTEM32\ 底下。
■17.硬體 - 支援的儲存方式
1.Windows 95 升級支援
文件上是這麼說，不過顯然只限於英文版 Win95。是否支援 Win98 升級？
文件上並沒有明顯提示。在對 NT5 1948, 1978 的實作結果，都不能在中文
Win98 底下升級。都會告訴你語系不同而建議你另外安裝。
2.NTbackup
我沒有測試。文件上是提及了「類似檔案總管的操作方式」，支援排程和
Windows NT Media Services (NTMS)，當然也支援了 NTFS, FAT, FAT32 ，
易於操作的使用介面等。
3.支援 FAT32
4.NTFS 的增強功能
提供了一卡車的新功能。包含 per-user disk quotas, file encryption,
and the ability to add disk space to an NTFS volume without
rebooting.
英文專有名詞很多，請參看「NT 的檔案系統」。
5.UDF
NT5 支援 UDF (Universal Disk Format，通用磁碟格式 )v1.5。UDF 是用
來設計給 dvd 和 cd 的檔案交換格式，意圖取代 cdfs。
6.Encrypting File System
在 ntfs 分割區上，提供了通透性的檔案加密。
■18.硬體 - 列印支援的增強
底下選譯自 NT5 Release Notes 的廣告詞。NT5 使用 *.gpd 的驅動程式，所
以舊版的驅動程式以不相容者為多。ICM 2.0 的功能，弟未能測試。
1.Internet Printing
可存取 Internet 上的網路印表機。比如列印到某個 URL 印表機，瀏覽
HTML 印表機狀態。甚至經由 http 跨過 Internet 列印到 nt5 印表機。
http://<server>/printers
2.簡化使用者介面
3.Active Directory Integration
動態目錄整合。容易找到網路印表機。
4.Image Color Management 2.0 API
支援了 ICM 2.0 ，比起以前更快更一致。
■19.硬體 - 共用 MODEM
總算 nt5 支援共用 modem，早該支援了。應該一堆人等了很久。至於比起
modem share, ishare, wingate 之類，倒很難有個定論。驅動程式目錄如下
。
E:\NT5\WINNT32\WINNTUPG\MS\MODEMSHR\NETMSHR.INF
■20.硬體 - 不相容列表
這份列表整理自如下目錄，總共 99 個檔案說明，弟儘可能的把它簡化。我想
孫小毛要失望了，因為不支援 Wacom 數位版。連 LapLink, pcanywhere,
Iomega ZIP, ALS 120 音效卡，羅技滑鼠都上榜了。看來大家準備大搬風，至
少有遠程遙控需求的 (pcanywhere) 就不太能考慮，要不然就要重做驅動程式
了。整理自如下目錄
E:\NT5\WINNT32\COMPDATA\
硬體相容性列表要看 Windows 2000 Hardware Compatibility List，如下地
方。
http://www.microsoft.com/hwtest/hcl/
Adaptec AAA 或 ARO 系列 RAID 控制卡
Avance Logic ALS120 音效卡晶片
Backup Domain Controller
CIC Handwriter 手寫版軟體 2.0
Calcomp 數位版
Compaq Survey Tool
Crystalware audio device
Dell 電腦的自動關機服務(Auto-Shutdown Service)
Dell 電腦的過熱關機服務(Thermal Shutdown Service)
Dell's "OpenManage Client"
DeskOff which is part of DeskView by Siemens
DeskOn which is part of DeskView by Siemens
DeskView System Monitoring which is part of DeskView by Siemens
DeskWOL which is part of DeskView by Siemens
Digital 的某些電腦
HP 1150c 掃描器軟體
HP C4734 擴充式鍵盤驅動程式
HP Lock
HP TopTools Device Manager
IBM 9397 Video Capture 驅動程式
IBM IRDA 紅外線驅動程式
IBM MPEG-2 Decoder 驅動程式
IBM ServeRAID II SCSI Host Adapter
IBM TrackPoint 驅動程式
Imation Parallel Port SuperDisk Drive
Initio INI-910 chip (SCSI)
InocuLAN by Cheyenne
Intel LANDesk Client Manager
Interphase 光纖驅動程式
Iomega Parallel Port ZIP
Laplink
Logitech 部分產品
Message Queuing 1.0 Information Store
Phoenix PC Card 控制驅動程式
Phoenix Power Management
Powerdesk Utilities (是 matrox 的顯示程式啦，可不是 mijenix)
STB video adapter
Siig application titled "CYBER PCI"
Symantec PCAnywhere
Toshiba Power Management System
UMAX VistaScan version 2.40
Wacom Digital Writing device
某些 parallel port storage device (行動式硬碟)
某些電源管理驅動程式
■21.多媒體 - Win32 Driver Model(WDM)
原先是設計可給 Windows, WinNT 皆可使用的 driver 介面。包括了 IEEE
1394 和 usb 介面等。不過我們在 Win98 上面看到的實作，多指在音效卡的
driver。
wdm 的音效驅動程式，對 NT5 而言是一個新的嘗試。微軟在這裡加入了 Ro-
land GM (General Midi) DLS (Download Sound 可下載聲音元件 )的功能，
聽起來相當不錯。對 win98 好是不好？或許您可以參考這篇一年前對 S3
SonicVibes 測試報告，再做定奪。在 K 某人的另外非正式報告中，則是嫌
wdm 的聲音聽起來「比較沈」。
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_s3sonic.txt
至於 WDM 和一般音效驅動程式，那一種效果比較好？真的很難說，畢竟音效
處理不是 cpu 超頻，速度愈快可能愈難聽。在消耗的記憶體上，明顯的是以
wdm 為多。
■22.多媒體 - DirectX
這裡跟 win98 的支援幾乎一樣。包括對多個顯示器，usb, agp (含 Gart 和
2x agp), dvd 等等的支援。另外在 NT5 的 release notes 清楚的提及，完
整支援 DirectX 5.0。令人疑惑的是，最新的 DirectX 6.1 到底有沒有支援
？
如果是用微軟自己出的 DirectX.cpl 去觀看 NT5 的 DirectX，只會看到「已
安裝 DirectX -1 」的字樣。:( 這顯示了 NT5 跟 Win98 的 DirectX 似乎是
兩回事。同樣的硬體，裝在 NT5 上也可能不支援 DirectX，雖然在 Win98 底
下有支援。
有關 DirectX，建議您抓取這個回來閱讀及測試。它同時支援繁體中文簡體中
文環境，據說也是 K 某人所做的。
ftp://ftp.nsysu.edu.tw/cpatch/system/directx/cdxcpl6.txt
ftp://ftp.nsysu.edu.tw/cpatch/system/directx/cdxcpl6.zip
1978 顯示的 DirectX 版本如下
已安裝 DirectX -1
Direct3D 5.00.1975.0001
DirectDraw 5.00.1978.0001
DirectInput 5.00.1976.0001
DirectPlay 5.00.1975.0001
DirectSound 5.00.1975.0001
■23.管理工具 - Darwin
上次的報告中提到了 Microsoft Management Console (MMC)，此處不再贅述
。這次的達爾文 (Darwin) 則是 Application Installation Management。
簡單的說，達爾文是用來管理安裝程式的架構。希望能做到 Zero Administra
-tion 的程度。早期版本固不用說，即使對 1978 的實測中，達到與配合的程
度是「零」，包括微軟 NT5 所附上的程式在內。微軟顯然還有很長的路要走
。我們且來看看微軟的廣告詞是如何說的。
1.Standard package format & installation service.
達爾文可處理安裝、修理、移除，和追蹤元件的軌跡。
2.Resiliency
可協助程式的維持管理。
3.Just in time (JIT) installations
應用程式可設計成給達爾文的管理 api 來安裝元件。
4.Policy-based Management.
達爾文可支援應用程式的廣告(啥東西？應用程式也有廣告？)可跟 ZAW feature
緊密結合，可讓機器顯示安裝的過程，而不必真正的安裝應用程式。
5.Support for lockdown.
達爾文是內建於 NT 的一項服務，准許應用程式可安裝完其廣告，即使登入
的使用者沒有足夠的權限可以安裝該應用程式。
6.Management & package API.
達爾文提供了一組功能，可供應用程式從達爾文管理架構中獲得利益。包括
重新組態、修理、定位、強迫安裝程式元件。因此，程式可以用來發展
標準的 達爾文 packages 。
翻譯的相當生硬，而且怎麼看都跟小標題配不起來？(原文就是如此，ka 也沒
辦法，苦笑中 )。似乎我們可以看出，微軟意欲在安裝工具上一統介面的野心
？
■24.管理工具 - Group Policy Editor
群組政策編輯器，這是包含在 MMC 架構下的使用者介面程式。可管理包括
given site, domain, organization 的設定。也可以用來管理.adm 檔案。微
軟並未如宣稱的實作完全。在 beta 版當中，只能管理「應用程式指定」和「
登入 script 」的部分。
■25.檔案 - 尋找檔案
還是一樣，套在 IE5 架構底下來找檔案。1978 的檔案尋找，總算比 1877 的
笨拙尋找方式來的聰明一些了。
■26.檔案 - NT 的檔案系統
底下取自 NT5 release notes 。原件如下。
E:\NT5\DUMP\DATALOGS\RELNOTES.HTM
---------------------------------------------------------------------------
功能 NTFS4 NTFS5 FAT FAT32
---------------------------------------------------------------------------
安全性 Y, 支援完整的 Y(同左) N N
NT安全控管
---------------------------------------------------------------------------
加密功能 N Y 支援 N N
---------------------------------------------------------------------------
動作記錄 Y, 可保留斷電時 Y(同左) N N
或其他問題的動
作紀錄
---------------------------------------------------------------------------
檔案大小 最大理論值可達 Y(同左) 最大到2GB 最大到2GB
16 exabytes=
2^63-1 bytes
(2的63次方)
---------------------------------------------------------------------------
磁碟大小 磁碟或檔案的最 Y(同左) (文件上此處) FAT32 支援
大建議值 2TB (空白) 2GB 到 2TB。
---------------------------------------------------------------------------
檔案壓縮 支援對檔個別壓 Y(同左) N N
壓。磁簇最大值
不超過 4kB。
---------------------------------------------------------------------------
作業系統相容度 NT NT Windows Win95 OSR2
(NT4 有支援?) MS/DOS Win98
(文件上未提) NT NT5
OS/2 (dos 7.1 也
支援吧？)
---------------------------------------------------------------------------
容錯相容性 simpled N N
spanned
mirrored mirrored
RAID-5 RAID-5
---------------------------------------------------------------------------
線上更換磁碟 N Y N N
不用重新開機
---------------------------------------------------------------------------
磁碟容量管制 N Y N N
(Quota)
---------------------------------------------------------------------------
麥金塔系統的 Y Y 不支援，然而若 不支援，然而若
檔案與列印服 你的os 在 fat 你的os 在 fat32
務 分割區時，可在 分割區時，可在
ntfs 使用這項 ntfs 使用這項
服務 服務
---------------------------------------------------------------------------
MS/DOS, N N Y N
win31 支援
---------------------------------------------------------------------------
Win95 N N Y N
---------------------------------------------------------------------------
OSR2, Win98 N N Y Y
---------------------------------------------------------------------------
NT351, NT4 Y N Y Y (存疑?)
---------------------------------------------------------------------------
NT5 Y Y Y Y
---------------------------------------------------------------------------
■27.檔案 - 開啟檔案對話方塊
多個智慧型的尋找檔案，有點像在使用 web 瀏覽器，打個一兩個字，就會自
動在底下列出一排近似檔名的下拉式選單，讓你找檔案。用意不錯，不過使用
起來的經驗實在不方便。
一般我們會直接輸入檔名時，通常是對檔案很熟悉才可能，否則都是直接用滑
鼠點選就好了。這時用鍵盤選，反而檔名很容易跑掉而浪費時間，如果用滑鼠
選，還要把手移過去，那乾脆直接選檔不是更快？
如果不理它，當然可以。很煩的畫面跳來跳去而已。 :(
■28.控制臺元件
NT5 在觀念上，把部分元件從「我的電腦」中移走，移到「控制臺」中當做特
殊資料夾。包括 Win98 裡大家熟知的「印表機」「排程工作」「撥號網路」
，另外「管理工具」和「資料夾選項」也都一併進到了控制臺。
在硬體管理部分，沿續了 1877 的風格，幾個重要的管理反而得繞很多路，或
是要開一大堆視窗。包括
硬體精靈 /Control Panel/System/Hardware/Hardware Wizard
裝置管理員 /Control Panel/System/Hardware/Device Manager
硬體設定檔 /Control Panel/System/Hardware/Hardware Profiles
服務 /Control Panel/Administration Tool/Component Services/System Tools/Service
服務 /Control Panel/Administration Tool/Computer Managerment/System Tools/Service
■29.捷徑觀念
上次 1877 的報告裡已提過了捷徑觀念的改變。這次新增的項目包括
1.Run as different User
同一個程式可以設定給兩個不一樣的人用，甚至可以設定密碼。再度使用時
必需輸入 id 和密碼，否則只能是當成同一個人使用。
2. Run In separatedly space
這我無法測試。
3.Run:
設定執行視窗最大化、最小化、或是一般視窗。
4.尋找捷徑目標的方式
原本要直接找檔案定位，改成樹枝狀架構瀏覽，找起來比以前更加直觀。
■30.登錄程式 regedit.exe
這個應該沒有問題，操作方式很類似，功能也沒有增加。問題是 NT5 登錄程
式 regedit.exe 匯出的格式竟然不是純文字檔，而是有點類似 Unicode 的文
件，裡面填的全是 20 而非 00。這在整理 registry 起來會造成相當大的不
便。
改用 Win98 內建的 regedit 即可解決。匯入、匯出都沒有問題。REGEDIT4
的檔頭一樣可以使用。
■31.使用者設定檔路徑
NT5 的要求是讓每個登入工作站的使用者，有獨立的使用空間。這裡的設定跟
1877 有重大差別。使用者設定獨立出 WINNT 系統目錄外，也不跟 Win98 "My
Documents" 搶同一個實體位置 (雖然名稱還是一樣 )。以弟為例，至少有五
個目錄。
C:\Documents and Settings\All Users
C:\Documents and Settings\All Users (WINNT)
C:\Documents and Settings\Default User
C:\Documents and Settings\Default User (WINNT)
C:\Documents and Settings\kiiali
如果以正在使用的 kiiali 為例，每個目錄下都有如此複雜的子目錄。您可以
看到，Local Setting 底下又存了一分。IE5 的個別設定又佔得相當多。扣掉
IE5 和 Local Setting 的部分，真正屬於個人所用的並不太多。可別嚇到了
，Win98 其實也差不多，只是沒有這麼肥大罷了。
Documents and Settings
+--kiiali
+--Application Data
| +--Microsoft
| | +--SystemCertificates
| | | \--My
| | | +--Keys
| | | +--CTLs
| | | +--CRLs
| | | \--Certificates
| | +--Protect
| | | \--S-1-5-21-1202660629-813497703-1957994488-1000
| | +--Internet Explorer
| | | \--Quick Launch
| | +--Installer
| | | \--{90150409-78E1-11D2-B60F-006097C998E7}
| | +--HTML Help
| | +--Crypto
| | | \--RSA
| | | \--S-1-5-21-1202660629-813497703-1957994488-1000
| | \--Address Book
| \--Identities
| \--{C5B76F52-CD04-11D2-B79B-0080C80D13F5}
+--Cookies
+--Desktop
+--Favorites
| +--Media
| \--Links
+--Local Settings
| +--Temporary Internet Files
| | \--Content.IE5
| | +--WXHP0SBP
| | +--T0SW3GJF
| | +--O36FA3IL
| | \--4RQ3658Z
| +--Temp
| +--History
| | \--History.IE5
| | +--MSHist011999022619990227
| | \--MSHist011999022819990301
| +--Application Data
| | \--Microsoft
| | \--Windows
| +--My Documents
| | \--My Pictures
| +--NetHood
| +--PrintHood
| +--Recent
| +--SendTo
| +--Start Menu
| | \--Programs
| | +--Startup
| | \--Accessories
| | +--System Tools
| | +--Entertainment
| | +--Communications
| | \--Accessibility
| \--Templates
+--My Documents
| \--My Pictures
|--NetHood
|--PrintHood
|--Recent
|--SendTo
+--Start Menu
| \--Programs
| +--Startup
| \--Accessories
| +--System Tools
| +--Entertainment
| +--Communication
| \--Accessibility
\--Templates
■32.結論與建議
其實我沒有做很深的測試。不過 1978 適合以下幾種人玩。
1.沒有中文 UI，因此要忍受英文，適合能忍受英文的傢伙來玩。
2.多語系的正式支援。(重要！) 很適合中文化雙語平臺，程式設計等等。
3.想在 FAT32 上裝 NT 。
4.想測試作業系統新功能。
5.硬體配備好，想把功能發揮到極致。
ps1.如果你會用 vc 中文化，那麼把舊版 1877 的 shell32 資源檔貼過來就
可以有中文介面了。
ps2.如果可能，把 ie5 拔掉。吃資源吃太兇了。
■33.版權
本文作者為 Kii Ali <kiiali@cpatch.org> 所寫。非常歡迎您引用
。引用時可能碰到的版權問題，麻煩您遵守如下：
1.個人可以免費引用和傳播一部分或全部文章，唯請註明文章出處，包括作者
姓名和原取得的 URL 等等。在這種情形下，您通常無須通知作者。不過您
若願意通知作者，我會很高興的。
2.網站引用請註明文章出處，亦請通知作者。商業出版的報紙、書籍、與謀利
場合，為免誤會紛爭，務請取得作者授權。
3.本文將放置於如下的 URL 。
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt5b1978.txt
NT5 beta3 b2012 測試報告
* updated by Kii Ali, 12-11-2001
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt52012.txt
Subject: NT5 beta3 b2012 測試報告
------------------------------------------------------------------------------------------
NT5 beta3 b2012 測試報告
updated by Kii Ali, 04-23-99
■目錄
1.寫在前頭
2.安裝 - dos
3.安裝 FAQ
4.硬體
5.GUI 介面
6.輸入法
7.內建程式
8.tanliwu 的報告
■1.寫在前頭
應某 J 網友所托，也蒙他照顧，寫了 2012 的測試報告，算是回饋吧。
弟盡可能只指出和先前版本的不同之處。當然有很多朋友老是喜歡問我
這種呆問題：「卡哩，那你認為 NT5 到底值不值得裝？」唉，明知道
我會有什麼答案，都不乖乖的看 KA 牌測試報告嗎？ (笑)
在寫的時候， NT5 已經又出了 2020 的版本了，委實換版換得很累，
卻也是測試狂操作檔案，那些變態的快樂吧。我不敢說對 NT 的系統和
架構瞭解多少，畢竟在識者眼光中，可能只摸著皮毛。IIS5 的觀念一
直未能實做，這是我所欠缺的。這版我沒有測的很詳細，原因是，版號
相異不大，跟前版的差異自然不大。裝的過程費時費力，的確讓人望之
卻步。
先前已經有幾位朋友寫過的測試報告，包括 Kii Ali (還是我啦 )對
1877 的兩篇報告，以及 JAZZ 對 1978 安裝過程的一些質疑。因此請
您先看過這些，對 NT5 的架構和測試理念有個基本的瞭解。所有在舊
版測試過的項目和理念，將儘可能不再重覆。如下。
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt51877.txt
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt51877_1.txt
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/ka_nt51978.txt
ftp://ftp.nsysu.edu.tw/cpatch/faq/betareport/b_nt5b1978.txt
■2.安裝 - dos
一般都是從 dos 底下用光碟安裝。安裝的參數如下。我們最熟悉的
winnt /b 參數早已在 beta3 不見了。當然它的安裝方式跟 build 1978
又不太一樣。弟試譯如下。建議您還是要看看原文，安裝時可不會出現
中文的。
Sets up Windows 2000 Server or Windows 2000 Professional.
裝置 W2k 伺服器版或專業版。
WINNT [/s[:sourcepath]] [/t[:tempdrive]]
[/u[:answer file]] [/udf:id[,UDF_file]]
[/r:folder] [/r[x]:folder] [/e:command] [/a]
/s[:sourcepath]
Specifies the source location of the Windows 2000 files.
The location must be a full path of the form x:[path] or
\servershare[path].
/s[:來源路徑]
指定 w2k 檔案的來源處。來源地必須使用完整的路徑名稱，或是
指定 \servershare[path]. 這種路徑。
/t[:tempdrive]
Directs Setup to place temporary files on the specified
drive and to install Windows 2000 on that drive. If you do
do not specify a location, Setup attempts to locate a drive
for you.
/t[:暫存路徑]
指定 Setup 使用特定的暫存磁碟來安裝 w2k。如果你不指定，
Setup 會替你自動指定。
(通常會指定在 c: ，所以 c: 必須要留下至少 475MB x2 的容
量大小。不要小看 NT5 會塞爆你硬碟的能力。)
/u[:answer file]
Performs an unattended Setup using an answer file (requires
/s). The answer file provides answers to some or all of the
prompts that the end user normally responds to during Setup.
/u[:預答檔案]
指定 Setup 使用的預答檔案。此預答檔案可預先提供在 Setup
過程中會碰到的對話提示，來代替使用者回答。
(有這個預答檔案，換句話說，你就可以按下 Setup ，人就閃
去睡覺，隔天就有 NT5 可用。)
/udf:id[,UDF_file]
Indicates an identifier (id) that Setup uses to specify how
a Uniqueness Database File (UDF) modifies an answer file
(see /u).The /udf parameter overrides values in the answer
file, and the identifier determines which values in the UDF
file are used. If no UDF_file is specified, Setup prompts
you to insert a disk that contains the $Unique$.udb file.
/udf:id[,UDF_檔]
指定一個確認 id ，Setup 將用來指定單一資料檔 (UDF) 如何
修正預答檔案。 /udf 的參數效力將超過預答檔案，確認 id
亦將決定其值在 UDF 中如何使用。如果沒有指定 UDF 檔，
Setup 將提示你插入包含 $Unique$.udb 的磁片。
/r[:folder]
Specifies an optional folder to be installed. The folder
remains after Setup finishes.
/rx[:folder]
Specifies an optional folder to be copied. The folder is
deleted after Setup finishes.
/r[:資料夾名稱]
指定安裝的資料夾。資料夾將保存到 Setup 結束後。
/rx[:資料夾名稱]
指定要複製的資料夾。資料夾將在 Setup 結束後刪除。
/e Specifies a command to be executed at the end of GUI-mode Setup.
/a Enables accessibility options.
/e 指定圖形介面安裝完後，第一個要執行的指令。
/a 啟動存取性選項。可以多了三個選項，選擇「放大鏡」「聲音
鍵」等在安裝過程方便聽力視力不便人士的措施。
■3.安裝 FAQ
1.smartdrv
仍然建議您在 DOS 安裝時，一定要掛 smartdrv.exe ，這樣子硬碟存
取速度可以加快。否則 7600 個小檔複製到硬碟，再開始正式的安裝程
序，包準沒有人可以受得了。如果要安裝得更順，把光碟的 7600 個檔
案全部複製到硬碟會比較好。
2.bootfont
所有舊版相關的 bootfont 相關檔案要移除掉。附上雖然可以在開機時
就顯示中文，但其中的 ↑↓ 箭頭因為是半形的，會跟中文相衝。如果
你一定要在 NT5 開機時顯示中文，建議你用舊版的 ntldr 來做。
3.會跟 Win98 使用同名檔案
包括 Netmeeting, wordpad (Accessories), Outlook Express 和 IE
主程式等，建議您如果常常要在 Win98/NT5 使用，這幾個最好備分，
或著只要用 Win98 版本。Win98 並不能執行部分 NT5 的內建程式。
■4.硬體
1.記憶體：
同 1978 的測試報告，記憶體將是玩 NT5 的最大限制。
奇怪的情形是，2012 所使用的記憶體居然會比 1978 還要少？我這裡
開了 powerdesk 204, ultraedit 610a ，所使用的記憶體只有51M
(1978 為 62M) ，新版的記憶體使用量居然比較少？
2.支援的硬體增多
這似乎是廢話。不過看到 2012 總算支援了 SiS 6326 ，的確有些驚喜。
3.軟碟問題
這版已不像 1977 會一直 Search 軟碟的動作，使用起來順多了。
3.硬體管理
/Control Panel/System/Hardware (控制臺/系統/硬體) 多了這項。
Device Manager/ Driver Signing (裝置管理/驅動程式簽名)
這項管制每個驅動程式，使用微軟的數位簽名 (Digital Signing)，在
安裝新軟體時，也將管制 File signature verication。
4.虛擬記憶體
/Control Panel/System/Advanced/Performanced Option/
這裡控制了虛擬記憶體 paging file size ，甚至令人驚奇的是，還可
以設定 registry 的大小？只是這版的 registry 又大到 8MB 了，運
作起來必定拖慢。
page file 除了可以設定在 c: ，還可以設定在其他硬碟一起並行，也
就是說，pagefile 可以不止一個。
■5.GUI 介面
IE5 版號是 5.00.2516.1900 56-bit 版本，比在 7-11 買的還要新。
1.Smooth Scrolling
不過這一版的 smooth scrolling 頗為徹底，每一下下拉視窗或是下拉
選單，都出現了漸層的陰影。使用上的 GUI 感覺相當不錯。但拿來實
際作業時，就不免嫌拖慢速度。你可以在這裡設定。
/Control Panel/Display/Effect/Visual Effect/
[] Use transition effect for menus and tooltips [Fade Effect]
[Scroll Effect]
選單和工具提示的轉變效果。這裡有個 combobox 下拉式視窗，喜歡淡
入淡出，還是要用捲動？當然這個功能可以完全關閉。要不要使用這個
功能？我的建議：關掉。 (笑)
2.滑鼠陰影
在這裡可以指定
/Control Panel/Mouse/Pointers/Enable Pointer Shadow
滑鼠一樣具有「立體陰影」，讀者可以仔細比看看，的確有差，滑鼠的
游標看來像「浮在桌面」上，很立體的感覺。
3.檔案尋找
雖然仍然是用 ie5 來做尋找介面，不過已經比前一版聰明也成熟多了。
至少，可以用了。
■6.輸入法
有點不同的是，這版的輸入法 hotkey 並沒有預先指定。你可以在這裡
指定。
/Control Panel/Regional/Input Locales/Hotkeys for Input Locales
只是每一個設定都需要有 Shift ，並且只能指定 0-9 ，唉。
■7.內建程式
1.同步化 (syncronized)
這版的 NT5 提供了 Desktop & Laptop 的同步程式。其理念可以說脫胎
於傳統的「公事包」，但更加的視覺化。
相對於傳統的 LapLink 這類傳檔程式，弟還是建議，傳統的比較好用。
2.Performance
這次不是獨立程式了，而是整合在 MMC 1.2 的架構裡面。在這裡可以找
到。
/Coltrol Pancel/Adminitration/Performance
其實這是 System Monitor 的子元件，整合程度不佳。System Monitor
仍然是傳統的灰色介面而非象牙白，動起來並不能每一段時間自動去
Monitor ，有些失望。
3.Service
Service 當然還是同以前的版本，一樣架構在 MMC 1.2 架構上。部分
的元件可以看到微軟相當活潑化設計，元件改用可動式的 gif 的設計
，所以可以看到一個滾動的 COM+ 元件，球狀物體在盒子內滾動。這
裡可以看到。
/Console Root/Componect Service/Computers/My Computer/COM+ Application
4.磁碟重組
該死的，這樣一樣架構在 MMC 1.2 的架構底下。
/Computer Managerment/Storage/Disk Defragment
用過這個人，會很驚異的發現，微軟抄 Norton Diskeeper ，抄得真像。
■8.tanliwu 的報告
參考一下 tanliwu 的報告。
Date: Sun, 11 Apr 1999 18:32:56 +0800
From: Henry Wu <tanliwu@ms1.url.com.tw>
前後安裝過build 1979 及 build 2010，有數點向各位報告，
1.在1979的電腦管理有一項不錯的選項，記得是有關群組及使用者
有好幾十個選項，類似於Tweak UI，可以做一些設定，但2010版
卻已找不到。
2.Win2000 的撥號網路可以多線號碼循環撥號，但另外安裝的撥號
軟體例如NetBar或是Advanced Dialer 卻無法自動重撥〔使用這
些軟體，主要是為了計算上線時間及費用，免得玩過頭，而且讓
它在上線時主動開啟一些程式，斷線時自動關閉程式〕
NetBar或Advanced Dialer 在Win98 都可以正常運作。
3.在2010版的Dos 視窗，一開啟都是中文模式，找不到按鍵可以讓
它開啟為英文模式。有些dos 下的程式線條會成為亂碼，在1979
版，可能是中文Shell 的關係，印象中沒這個問題。
4.在1979及2010都無法安裝 @Guard v3.1
5.2010的IE版本比在7-11買的IE還新，用後者無法在2010安裝。
Win98 b3的一些問題
* updated by Kii Ali, 12-11-2001 ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_win98b3.txt Subject: KA_Win98 b3的一些問題 --- X-Sender: kiiali@ms1.accmail.com.tw (Unverified) Date: Mon, 16 Feb 1998 16:06:36 +0800 To: VIP <vippiv@ftp1.gep.ncu.edu.tw> From: Kii Ali <kiiali@cpatch.org> Subject: [vip$c47] 有關 win98b3 的一些問題 Sender: vippiv-request@ftp1.gep.ncu.edu.tw Resent-Message-Id: <B0000003515@ftp1.gep.ncu.edu.tw> Resent-From: vippiv@ftp1.gep.ncu.edu.tw X-Unsub: To leave, send text 'LEAVE' to <vippiv-request@ftp1.gep.ncu.edu.tw> 您好，弟是_Kii_Ali 真是可喜可賀，弟手上還在用的爛486-133 ，總算把 b3 裝起來 了。真是好，不用再按一下 Enter 把 b2 的IE4 過期提示關掉。 進控制臺，看看系統，音效卡的 ESS1868 變成 1688 :( 然後聲音 變得更難聽。仍然採用 WDM 的架構，多了個 SW synthesis 軟體 MIDI 實在是不太難聽。連帶的連正常 WAVE 檔都聽起來沉沉 的。幸好在B3 的音效裏沒有 CD 輸出太小的問題。B21 版本不但在 SB16 的驅動程式上，有 CD 輸出的問題，在 ESS 一樣也有 。 如果不信邪，把裝錯的 1688 要換成 1868，那麼必定沒有聲音。驅動 程式不能驅動，不管是微軟版本或是ESS 原廠都有問題。那麼，再把 驅動程式換回 ESS1688 吧，答案還是不行。最後因為音效問題，只好 重裝 win98 了事。 不曉得這是那個門子的 PNP，在 B2 版本裏，並不太囉嗦這種事情。 那個先裝，那個後裝，那個拔掉都可以很明顯簡潔的偵測出來。或許 該是主機版跟 B3 打架？ 網路卡部分，指定 Dlink DE-530 也是不行，結果讓它自己抓成 DEC 21040 (反正他本來就是使用 21040 晶片)反而就可以動了，真奇怪。 顯示卡的部分，同樣是 S3 virge 晶片，跑起 xing 的數值也是明顯落 差？這點就我相關懷疑，應該是不會差那麼多才對。不曉得各位的 xing 在這兩個版本裏跑起來如何？ 我要強調的是，不是說 win98b3 不好，而是在某些方面或 某些機器上， 似乎選擇 B2 會有比較好的相容性？ 就算是以我而言，仍然免不了有那種障礙。想從 B3 換回 B2 的確有點強人 所難。一方面要自己「降級」很奇怪，另一方面降級勢必要付出 整個作業系統重裝的代價，相對而言好像可以就好了，不是嗎？ -------------- 廣告：誠徵 B2 IE4 到期的破解方式。 -------------- 另外，要請 HYSK 音效大師來說明一下，在 win98b3 控制臺/多媒體/音效 似乎有進階音效的東西。有桌上型喇叭，螢幕兩側喇叭，鍵盤喇叭，四聲 道，環場音效，甚至還有筆記型電腦的音效等等，這些在驅動程式上或 是在實際聽起來的效果上，有沒有什麼差別？ 我聽起來實在是「沒有」差別。 :( 各位可以告訴我，差別在那裏嗎？如果 沒有差別，實在寧可把它拔掉。 控制臺的音效控制實在是做得很「炫」，不過還是寧可要求較實際的音效品質。 :( --- 黃國書 (Kii Ali)，師大地理碩三，目前兼任私立復興國中地理老師。 ICQ:5107476 信箱測試完成，麻煩您把寄信 default 轉到 gep 這個地方。
Win98 b21測試報告
* updated by Kii Ali, 12-11-2001
ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_win98b21.txt
Subject: KA_Win98 b21測試報告
---
To: vip
From: Kii Ali <kiiali@cpatch.org>
Subject: [vip$c47] win98 b2,b21,b3測試報告
Cc:
Bcc:
X-Attachments:
At 03:04 PM 1998/1/21 +0800, you wrote:
您好，弟是_Kii_Ali
>【大地】的 Win98Beta3 應該可以測試使用了？以下是個人的測試心得﹕
看到 HYSK 的測試，真是於吾心有戚戚焉，以弟在 WIN98 上的慘痛
經驗(昨天測試 winoncd 3.5 ，裝上 PacketCD 組件，結果把 registry
毀掉，win98 重裝)，或許也可以提出一些不同看法。
測試環境
--------
主機 486-adm5x86133, 586-Cyrix6x86133，
RAM 32M ,48M
音效卡 ESS1868，AD1816
網路卡 DE220 (ISA PNP) ，頂尖 (使用 winbond chip,PCI)，
DE220 (早期版本)
SCSI卡 Symbios 810a (PCI), DTCxxxx (scanner 附)
VGA9卡 S3 Virge 325
CDR Sony 924s
1.0 整體環境
------------
當機的機制。改變了不少，比起 win95 來說更不容易當機，執行
速度「似乎」在開機關機都比 win95 好許多。
>1.速度降低﹐原本 32MB 改為 64MB 後﹐才覺得系統反應速度與原本的
>95OSR2 差不多﹐頗令人感到悲哀！
以上是 HYSK 的說法，弟覺得還好。至少486-133 操 160 跑起來
的感覺，前後不會差很多，甚至有好一些耶。B3 和B21 是稍慢了
一些，B2 則沒有。
整體來說，這三個版本玩過的感覺是，b2 最穩定，次為 B3，B2.1
有問題。B2 版的唯一缺點是：IE4 到期，每次開機總要多按一次。
雖然我也實在不用(不想用)IE4 和 channels。有誰可以破IE4 搶
鮮版的期限破解？啥，要我去灌 IE401 ？試過了，但是它要求要
先解除 IE4 的安裝(天曉得怎麼解除)。那麼，把 IE4 的幾個
shell extension 拔掉，把 registry 拔掉吧？或是把系統的
shell.dll shell32.dll 換成 IE4 的版本，包準不能執行。
然後，出這個餿主意的人，registry 又毀了，重裝 win98 吧。
2.0 網路分享
------------
首先請有裝網路卡的同學打開「控制臺/網路/檔案及列印分享」
看看裏面的選項有兩個或三個？
b2 多了「我想讓其他人透過 internet 使用我的檔案」。這一項在
B21 和 B3的版本圴無，不曉得這是微軟的顧慮？新版弄掉了。 :(
2.1 網路卡
----------
網路卡 Dlink DE220 相容的程度，B2 最好，進去就正確抓到。
B21 根本找不到PNP 網路卡，分配到的 IRQ 是這衝那衝，B3
正確抓到 DE220，但是無法正確運作，連不上網路芳鄰。
或許是 486 版子比較舊，Award PNP bios 比較沒有那麼先進
，但是在同樣機器不同的作業系統下，win95, osr2, win98b2
都正常，而b21 b3都不正常。如果您的機器是屬於比較早期，
建議您使用 b2 版本。
不過弟記得 Award PnP Bios 似乎也只出到 1.0a版而已，
該不會差那麼多吧？
3.音效卡
--------
B2 版對音效卡沒有問題。B21 對音效卡有極為嚴重的問題。因為
B21 在音效卡上的組態多了 WDM driver ，天曉得這是什麼東西。
您可以在 system32 的目錄底下看到一堆 redbook.sys 等很大的
東西。如果是用 PNP 安裝方式的音效卡，在 b21 必定會自動幫您
選到 WDM driver ，要拔掉還很難，因為拔掉會自動去找到音效卡，
然後再自動裝上 WDM driver 。最後去動 *.inf 等等東西才可以
順利換掉。
以同樣是 ESS 音效卡來說，WDM driver 聲音未免太沉，不喜歡。
在 486 上裝 B21，ESS 卡是抓到了，結果開始嘯叫，怎麼調都
沒有用。
某些人的報告(使用 SB16) 指出，B2.1 在CD 輸出「超級小聲」，
連耳機插孔也有問題。但是使用 midi, wave 反而都沒有問題。
我手上已有有三個例子這樣了。
怎麼可能有這種事情，連光碟機前的耳機插孔也有問題？同樣的
機器，換到 DOS 下，音量可以大到吵死你。進 win98b21 就有
問題。
B3 沒有問題，不過會把1868 抓成1688 :( 唉，算了。B3 的音效
卡驅動程式是稍新一點，但似乎有些不一樣？仔細聽看看，
還是比較喜歡聽 ESS 出的 driver ，似乎好一點？
4.其他部分
-----------
4.1 輸入法
----------
相信各位眼尖的都看到了，B2 多了「新注音」，B21 多了「新注音」
「新倉頡」「新速成」，B3 居然把這些都取消，沒有了。 :(
不曉得微軟在想什麼？很有被當白老鼠耍的感覺。就像以前
我們在醫學院裏做白老鼠的免疫實驗，這次灌這種藥，下次灌
另一種藥，灌到胃鼓脹起來 (想必唸文化生技的一抹淺藍常常
幹這種事 :) 最後通通剖開肚子，「榨汁」算一算 WBC count
白血球計數 :(
4.2 控制臺物件
--------------
搖桿部分，B21 居然是英文版的，實在也太離譜了。
電源管理是 B2 版本稍差的地方，B21 和B3 基本上都是使用
同樣的電源管理程式。看起來比較不會那麼「拙」。
Desktop Themes 似乎我在 B2 沒有找到(反正也是佔硬碟空間
和拖慢速度的東西)，B21 要進安裝程式才有辦法找到。B3 則是
自動出現，多了幾個「水世界」等等主題。
4.3 安裝程式
------------
B2 版本的安裝程式，從頭到尾都出現同一個人，B21 B3
則邊按裝邊換人：:) 大概花俏一些吧？B3 會多出現要選擇
那一個國家 channels ，算是比較顧慮到使用者。不過，
這有什麼差別？我裝的結果，channels 只有 channel guide ，
別無它物。
4.4 升級或降級？
-----------------
升級容易降級難。如果您之前已裝到 B3 ，想回頭換回B2，
答案是不行。registry 部分老是會出現 invalid number，無法
解決，最後是 protection error :(
所以，重裝吧。
不過，如果在 msdos.sys 裏面版本號碼故意填不一樣，您猜猜
會發生什麼事情？ :)
4.5 簡潔的驅動程式
------------------
原廠所出的是比較好，或是比較功能缺乏？不過比起微軟所附上的
出的，還是新了一些。像 Symbios 810a 目前拿到最新版本是 404，
微軟的是 402 ，大家可以試看。
Xing 的數據， S3 卡方面反而是微軟內建比較快？
建議
----
如果您的機器很先進，很穩定，組態很簡單，B3 可以用。只
等別人破解。
如果您的機器跟我一樣，還在用 486，或是插了太多卡(像我
插了兩張SCSI 卡，一台燒錄器，一台掃描器)，組態太複雜，比較
喜歡簡單又有效率的東西，或是對IE4 新版實在沒有興趣的，或
是要找一個 SWAP 比較不兇的，ICON 看起來比較古老一點的 (像
B2 的桌面ICON 就設計的比B3 的還要拙)，那麼B2 可以考慮。
只除了要多按個「您的IE4 搶鮮版已經過期，請去更換正式版」
這種令人吐血的東西。
如果您就是喜歡用 B21....那麼也沒有什麼不好，不是嗎？
Win98 b1546測試報告
* updated by Kii Ali, 12-11-2001 ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_win981546.txt Subject: KA_Win98 b1546測試報告 --- To: vip From: Kii Ali <kiiali@teacher.fhjh.tp.edu.tw> Subject: Re: Win98 beta 2 期限破解 Cc: Bcc: X-Attachments: At 04:24 AM 1997/10/18 +0800, you wrote: >沒有抓到該 patch 檔的就如此改 > >filename: io.sys 219014 >find: 3f 24 4d >edit: 00 00 -- 太好了，雖然大小沒有一樣，卻一樣可以改，不會再提示您BETA TEST 到期。 不過卻 IE4 在叫。只要是11月15日之後，在每次進去WINDOWS 之後，總是會 叫說過期。雖然弟一點也沒有想去用IE4 :( 弟想提出幾個笨問題，大家討論看看。 1.Quickview 在 win95 時正常，在 win98 時看中文 DOC 檔卻出現亂碼。英文 和數字沒有問題，很明顯是內碼錯誤。但是，看中文 TXT 或其他檔案卻沒有 問題。您那裏也有嗎？先試看看再說。原本是以為 word 8 檔案的問題，後來 看了別人用 word 7 格式儲存，仍然是有些錯誤。 若用Quickview Plus 不曉得能不能解決這個問題？我想不出出錯的理由在那裏。 2.安裝正式版 IE4 就可以解決 windows IE 介面到期的問題。但我實在不喜歡 IE4，有沒有可能把完整 IE4 相關 DLL 拔乾淨， registry 也清乾淨，留下 比較「純正」的 win98 ? 說是盲目擁戴 Netscape 也對，不喜歡系統裏面塞 了一堆莫名其妙的東西倒是真的。 win98 安裝完的垃圾實在太多，3MB 的 welcome.AVI，用不到的 TXT GIF 等等。不曉得在幹什麼，能有什麼實用。比 win95 多個 cabview.dll ，還算是 勉強有些進步。可是也只能 view 而已，沒有太多稀奇。 3.大家試的 compiled HTML 對 HELP 介面有沒有什麼差別？比較好用或是編寫 比較容易？或著您像我一樣，也會覺得傳統的 help 檔格式還比較順眼且實際？ 所以弟把那些同樣的 compiled HTML 全給拔了，反正都是英文，對操作也沒有 什麼影響。甚至連IE4 好像也不能看這些東西？ 4.該死的「平滑捲動」功能，實在是中看不中用(借用 pank 的話)，拖慢速度， 不爽，常常按錯滑鼠 :( 看來似乎可以在以下的地方改.. 控制台/internet/option/進階/螢幕平滑捲動 有點用，但不是所有地方都有用。 :( 不曉得 more properties 什麼時候才有 WIN98 版本。 :( 5.即使花了 99 元，去 7-11 買了 IE4 正式版光碟，好爽快哦。結果 連上 微軟 WIN98 update ，居然會 javascript error :( 就這些囉，請大家看看了。
Win98 b1708測試報告
* updated by Kii Ali, 12-11-2001 ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_win981708.txt Subject: KA_Win98 b1708測試報告 --- To: vip From: Kii Ali <kiiali@cpatch.org> Subject: win98 1708 Cc: Bcc: X-Attachments: 您好，弟是_Kii_Ali 這個版本，不曉得換過之後，各位有沒有看出來什麼新的特色？ 很抱歉，好像除了 driver 換換，其他的，顯然有點像是個失敗的 作品。除了浪費精神與體力的測試員，想試試 IE 新版跟 舊版的什麼地方有不同，對 IE 的更新恐怕也是極為有限的 minor bug fix ，對我們這種不太用到IE 的人實在沒有啥用處。 弟不太建議換這個版本。 從 1650 到 1676 ，您有發現什麼變化？再到 1691 ，似乎除了 右上欄從轉動的地球變成窗戶，開始的灰色欄位變成藍色欄位， 有什麼不同？ 這一版有些不同了。窗戶的樣子變稍小，窗戶的樣子弄得「更醜」，醜的樣子 就好像從 64K 色降到 256 色，害我還跑去看顏色數目是不是調錯了？ 如果這樣就叫做改版，號稱GUI 界面的「大幅改進」，那我還是等 改進更多一點再進吧。窗戶在「飛」的樣子，換版的傢伙們，你不會 覺得奇怪嗎？好像不太對。原來是變得更醜了啦。 看來號稱這兩天就要出現的 1715 ，或許可以先觀望一下。
Win98 b1721測試報告
* updated by Kii Ali, 12-11-2001 ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_win981721.txt Subject: KA_Win98 b1721測試報告 --- X-Sender: kiiali@ms1.accmail.com.tw (Unverified) Date: Wed, 29 Apr 1998 14:56:56 +0800 To: VIP <vippiv@ftp1.gep.ncu.edu.tw> From: Kii Ali <kiiali@cpatch.org> Subject: win98 b1721 Cc: wei-an@i-manila.com.ph Sender: vippiv-request@ftp1.gep.ncu.edu.tw Resent-Message-Id: <B0000011717@ftp1.gep.ncu.edu.tw> Resent-From: vippiv@ftp1.gep.ncu.edu.tw X-Unsub: To leave, send text 'LEAVE' to <vippiv-request@ftp1.gep.ncu.edu.tw> 您好，弟是_Kii_Ali 看了老半天， 沒有人寫這個測試報告，我就來寫寫囉。 難得看這個版本這麼順眼，我想雄哥可以把 1708 這個版本刪了吧？ 或許您要等六月多的正式版或是搶鮮版，馬路消息是，搶新鮮白老鼠 版大概會是b1650？或是名列 Release Candidate 的1676 版？ 只是我看到連 7-11 都已經擺出 win98的書，想來有一些好笑。 對系統影響重大的軟體，我想沒有太多的理由對其害怕或著是 不用，裝過的包括 486slc (有夠烏龜的機器) , 486-133 操160 ,586 impp 操頻, 586-133 , PPro 200 等等。安裝的方式包括 win95 upgrade , win98 upgrade, DOS install 等等。除了 win31 沒有去試之外。 當然囉，我還有cdr 和pci 音效卡， scanner等等亂七八糟的設備， 所以環境是比較複雜一些。之前有人提到在win98 底下燒片不穩， 我想應該是毫無關係吧？四倍燒的時候再給他上網多工下去 然後 看看會不會有壞片跳出來，實在是很爽快的事情。 :) 新增功能改進方式如下 1.多了Real Audio 4.0 中文版，免費授權的 ，當然，我們可以用更肥的5.0。 2.右上角的窗戶，總算跟1691 一樣好看。當然，對ie4 的改進 可以「感覺」出又進步不少，雖然我實在不喜歡肥肥的ie4 (你只要 想想在 486-slc 用上ie4 有什麼後果就好了 。 ) 3.總算看到help的中文，當然，還有一堆沒有完全翻完。 4.pnp 的功能的確不錯，對scsi 卡等都是裝上後馬上就可以用， driver 都更新的相當新，除了稍略於原廠的版本外，實在沒有太多好 挑的。對 vga 卡方面，曾有朋友提到他換了 ms win98的 驅動程式 之後 ， 音效卡就乖乖的沒有爆音？ 5.之前提到1708 的物件問題，是我不小心多刪了 registry 所致。 當然，也不是沒有缺點。 1.Quick View 還是不能跟powerdesk 搭配，或許是出於微軟的惡意 或是 powerdesk 公司抓不到新版 QuickView 方式 。 不過即使 新版的 QuickView 還是跟所有beta3版本的情形一樣。改進了一些 ， 不用調就可以顯示中文了，可是還是難用。又醜又難用。 安裝完後，換回 win95的quickview 或是直接用 powerdesk 3 都是解決方式。記得，一定是要安裝完 QuickView 換掉檔案(取其寫入的registry ) 而不是不裝 ，這樣 registry 就沒有了。 2.internet connetion wizard ，立意很好，卻是其笨無比。包括 微軟的ie4 & outlook express 都會乖乖的去呼叫 icw ， 如果您 像我一樣，手賤的話，包準 icw 刪掉後，要讓這些軟體動起來， 就得傷一些腦筋了。 3.win98 在registry 裏面多了非常多的功能，當然也多了一卡車的垃圾。 如果好好花心思去清一清裏面 registry ，你會發覺win98 其實很輕快。 包含 advanced INF ,這些要刪的陷井不少。 你可以把win98 調得更輕更穩更快，不過，得花一些心思在registry 。 還要麻煩雄哥在win98 做幾個事情。 0.1708 應該是可以踼出去了。 1.裏面的 zip 檔麻煩解開。裏面都是 cab 檔，實在是不用再壓了。 差點沒有解到吐血。 2.Channel 沒有用 ie4的可以刪掉，要不然就解在channels 底下。 解開來也是一堆*.cab 檔案。至於 win98tour 就不用了，用搶鮮 版的傢伙應該不用這種無聊東西。 ----- (patch) 中文化軟體的訊息與評論，將用電子信件每天下午定期發出。 請告訴你的朋友訂閱 Patch-News ，以便獲取最新中文化檔案訊息。 請到 http://miau.cs.ccu.edu.tw/cpatch/ 訂閱或取消信件。 常見問題請看 http://miau.cs.ccu.edu.tw/cgi-bin/cpatch/note.iis 黃國書(Kii Ali)，私立復興國中地理老師，電腦測試狂。 ICQ#5107476
Win98 b1900測試報告
* updated by Kii Ali, 12-11-2001 ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_win981900.txt Subject: KA_Win98 b1900測試報告 --- To: vip From: Kii Ali <kiiali@cpatch.org> Subject: win98 b1900 Cc: pu Bcc: X-Attachments: 您好，弟是_Kii_Ali 大概已經有一些電腦測試狂，拿到這個版本安裝完了吧？或許早有人 發完了這一版的測試報告，弟只能算是野人獻曝，出來曬曬太陽了。 微軟的許多測試版，在 win98 b1676 之後就已經達到不錯的穩定性 和可用程度。但對於許多「自作聰明」的地方則是不太敢領教。在 版本號碼上從 1721 直接跳 1900 ，其實我深感懷疑。而且還號稱 RC 版本，但是這個 RC3 版本是否真的如 Release Candidate 3？ 瀏覽器的外殼 ------------ 首先，我們來看win98裏面 msie4 的版本號碼，您可以對看看您手上 所用的 ie4 或是 ie401 版本號碼是否比這個舊(好像是廢話) MSIE 4.72.3110.1;SP1 當然囉，您可以在任何地方看到這個新式右上角的窗戶─可真夠酷的。 跟前一個 1721 一樣，這個窗戶沒有 tooltips 黃色小標籤，飄忽在 白色框框黑色底裡的晦澀窗戶，然後轉過來是俗不可耐的金色地球(還非洲 大陸的形狀)沈在黑色裡，兩個一直替換。我不禁聯想到窗戶王國的世界 沈淪在黑色的陰暗裡。 這是我個人的偏見。這也是我最不喜歡這個版本的地方，每一個 beta 老是讓弟覺得是在替 ie4 做 beta ，而非 win98 做 beta 。微軟的 自作主張實在令人倒足胃口。 如果是調成256色，右上角的變化顏色簡直不能看。 不曉得微軟是否有美國司法部的陰影，老是要在這上面的圖案做手腳。無論是 傳統的 ie4 的 e 字小寫圖樣，或是ie3的更老地球傳統，或是 win98 b1691 的 窗戶版本，至少都比這個好一百倍。winamp 在換皮 (skins) 也不過如此。 或許微軟可以考慮把這處開放給 plus theme 之類的東西，做個連戰和李登輝 交互轉動的頭如何？要不然再加個陳水扁或是 Kii Ali 之類的也可以。這樣 至少好玩多了。 不過，換個方式來看，這版的 win98 不再強迫使用者一定要用 ie4 做為內定 的 *.htm browser ，網景的使用者至少不用費心到 registry 再改來改去了。 對於較舊版本的 win98 安裝者，這版也不會免費贈送ie4 和「快速向外看」， 「頻道」的圖示到 taskbar 上面，或許也有一些好處吧？ 安裝需求 -------- 以下剪自 readme.txt Typical Windows 95 upgrade: requires approximately 195 MB of free hard disk space, but may range between 120 MB to 295 MB, depending on your system configuration and the options you choose to install. Full install of Windows 98 on a FAT16 drive: requires 225 MB of free hard disk space, but may range between 165-355 MB depending on system configuration and options selected. Full install of Windows 98 on a FAT32 driver: requires 175 MB of free hard disk space, but may range between 140 MB - 255 MB, depending on system configuration and options selected. 如果你的 ram 夠多，hd 也大，cpu 也快，不用像我一樣用 notebook 安裝 win98 ，那麼 win98 是一直可以考慮的作業系統。如果你用 notebook ，而這些條件都不足，建議 osr2 即可。曾經透過網路硬在 250mb 的486 筆記型電腦，勉強從 win95 塞進win98，跑起來的確有 一些辛苦，光是安裝便得 75分鐘，或者更久，決定在網路的速度。 如果是光碟上安裝到一般桌上型，30分內是絕對有餘的。 有那一些好玩的？ ---------------- 這版的問題跟前些版本的一樣，中文化仍嫌不夠。 當然，「控制臺」絕對不是像這版的 web 畫面所說：「請使用控制臺， 讓電腦展現個人的風格」，如果的附庸風雅。 雖然總算勉強有了中文化的 windows 說明，不過win98線上版本仍是 英文。 在新增/移除 程式內容，不曉得是因為用了雄哥的破解關係，還是 mem24.zip 有問題被蓋掉，出來的竟然是英文的。某些中文字則因為 跟英文的大小不相容而被遮到了。 kernal 雖然更新了不少，驅動程式換得是還好，並不太多，以 s3 virge 來看看版本，一個是 1685，一個是 1696，都是嫌稍稍舊一些。話說回來， s3 的站上有一個顯示卡的 beta 版本，不曉得各位有沒有去拿？一般的評價 ，似乎是微軟 Certified 的驅動程式比較穩？ 這個版本有沒有像以前一樣支援 powerdesk 2.0 ? 好像還是沒有。又要 去拿 osr2 版本的東西了。 控制臺中的某些物件，新增軟硬體時都會有某種風格的實物照片，比如 新增 modem ，新增印表機，新增網路設定等等，但這部分的風格雖然沒有 完全統一。 增加 win98 的速度 ----------------- win98 需要更多的記憶體，更好的 cpu 及更大的硬碟，用來準備愈來愈的 的 gdi 消耗。我想，這是大家公認的。 讓 win98 動起來可以又輕又快，有幾個方式 1.把 windows 目錄裡的 *.bmp *.txt *.bmp *.gif *.jpg *.htm *.htt 全部 踼掉，目錄裏面檔案愈少，找到檔案的速度就愈快。這些都是 win98 免費 附送的垃圾。如果可以不嫌難看 (反正要求效率)，*.SCR 也可以踼掉。您總 不希望在燒片子時，冒出鐵達尼的 screen saver 吧？ 2.新增加的 plus 選項裡，全部不要設定。在慢的電腦上，這個改變是相當 明顯的。 3.registry (1)在這個區段裡，有極多的垃圾，如果你不用 msie4 ，你會發覺可以砍的 東西極多。當然，Advanced setup 要小心一點，砍了 web 顯示畫面就 沒有得玩了 (雖然也是浪費 gdi 的東西)。 REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Microsoft] (2)底下這一段就更多東西可以砍了。 win98 免費附送了自動執行的 RunOnce， 您可以到這裡來砍。 REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion] (3)如果不太敢玩 registry ，那麼「小小工具箱」是弟推薦的。一樣有部分 可以動 registry 的功能，在這裡 ftp://miau.cs.ccu.edu.tw/cpatch/x-setup/ 另外，如果不需要多餘的 dll ，可以考慮這個 ftp://miau.cs.ccu.edu.tw/cpatch/clnsys (4)底下這段的 Boot Count 不曉得是幹啥用的？啟動100 次就要叫我們付錢，否則 不能用了嗎？ :) REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion] "InstallType"=hex:01,00 "SetupFlags"=hex:02,05,00,00 "DevicePath"="C:\\WINDOWS\\INF" "ProductType"="100" "RegisteredOwner"="黃國書" "RegisteredOrganization"="師大地理所" "ProductId"="" "LicensingInfo"="" "DVD_Region"="3" "BPC_Region"="0" "OldWinVer"=hex:00,04 "ProductKey"="HGBRM-RBK3V-M9FXV-YCXDK-V38J4" "DigitalProductId"=hex:a4,00,00,00,03,00,00,00,37,39,38,37,38,2d,30,30,30,2d,\ 30,31,30,30,30,31,35,2d,30,37,34,32,35,00,00,00,00,00,37,33,30,2d,30,30,30,\ 30,31,00,00,00,00,00,00,00,23,4e,00,80,5a,63,34,3a,40,51,1c,12,ce,53,01,00,\ 00,00,00,00,eb,a2,3d,35,12,22,01,00,01,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,30,35,31,30,30,00,00,00,00,00,00,00,00,00,\ 00,00,fc,7b,16,07,40,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,e6,de,2a,8d "SubVersionNumber"="" "ProgramFilesDir"="C:\\Program Files" "CommonFilesDir"="C:\\Program Files\\Common Files" "Plus! VersionNumber"="IE 4.0 4.72.3110.1" "WallPaperDir"="C:\\WINDOWS\\Web\\Wallpaper" "MediaPath"="C:\\WINDOWS\\media" "ConfigPath"="C:\\WINDOWS\\config" "SystemRoot"="C:\\WINDOWS" "OldWinDir"="C:\\WINDOWS" "ProductName"="Microsoft Windows 98" "RegistrationExtDLL"="OEMREG.DLL" "RegDone"="" "FirstInstallDateTime"=hex:e1,b1,5a,24 "Version"="Windows 98" "VersionNumber"="4.10.1900" "ProgramFilesPath"="C:\\Program Files" "SM_AccessoriesName"="附屬應用程式" "PF_AccessoriesName"="Accessories" "OtherDevicePath"="C:\\WINDOWS\\INF\\OTHER" "SecureProductId"="12356-74987-98423-16521-34461" "BootCount"="3" (5) registry 裏面的 Vxd 這是可以動手腳的地方，特別是當你不需要 ie4 的時候。 至於完全把 ie4拔掉嘛..我沒有把握。前一陣子是有人提出 ie4 的完全反安裝方式，不過實在不太徹底。您可以用 verslist 去尋找 版號 4.72.xxxxx 的軟體，包括所有的 dll 等。 整體評價 -------- 這一版的我是覺得還好，沒有像上次拿到 1708 那般的問題。可是，好 在那裏，說不上來，總是有著徒勞測試的感覺。改進那些地方？增強那些 地方？一直找不太出來。 這次微軟總算比較人性化的，尊重之前安裝的 registry ，不會自做 聰明的硬塞給 ie4 和 outlook ，這是值得肯定的地方。 不太鼓勵裝這版 1900 rc3，繼續用用 1723 吧。 當然，裝了拿來練習自己的beta 功力，也不是壞事，也不會損失什麼。每 beta 一次，雖然要浪費一些時間，卻得強迫自己對整個作業系統更加瞭解。 我不會考慮要等 win98 正式版這類的話，對事物的瞭解硬是比別人快，每個 beta 就像個賭注一樣，或許可以換取更高的穩定性及實用性，這就是 beta ， 把自己當白老鼠的樂趣。那種心態就跟以前追83外頻100外頻的人，沒有什麼兩樣。 網路總是瞬息萬變的，三四年前還在用 Trumpet winsock + Netscape 1.20 ，爭論著 win95 os/2 熟僾熟劣，以學術網路為主的我們，實在很難想像 現今的網路世界有這麼大的變化。主流標準改變，我們在短短時間被就 得被強迫牽著鼻子走。如今還用 trumpet 來建立網路環境翱人恐怕極少， Netscape 被打的搖搖欲墜，學術網路還是主力，卻不再是網路上唯一獨大 的團體了。我們的恐龍思考方式可能也要改變改變，誰曉得 win98 的下 一個世代會是什麼樣子？會不會微軟帝國 (Age of Empire ??)，就像 麥當 勞，visa 卡，可口可樂一樣，成為另一種必備的生活方式？ 至於右上角的窗戶，拜託，真是被微軟打敗了。 希望能很快聽到你對這一版 win98 的評價，希望您反駁弟的看法。 廢話 murmur ----------- 這個評論是應雄哥的要求而寫的。如果您覺得這個評論信寫的不太爛的話， 寫封信來鼓勵打氣，或是反駁。弟有點累了。 您可以自由引用、轉送、剽竊本文的部分或全部。只要您高興。
Win98 b1910測試報告
* updated by Kii Ali, 12-11-2001 ftp://ftp.nsysu.edu.tw/cpatch/faq/ka_win981910.txt Subject: KA_Win98 b1910測試報告 --- X-MAILFROM: vip_error@ftp1.gep.ncu.edu.tw X-Sender: kiiali@ms1.accmail.com.tw (Unverified) Date: Tue, 09 Jun 1998 02:06:56 +0800 To: Patch-user <patch-user@miau.cs.ccu.edu.tw> From: Kii Ali <kiiali@cpatch.org> Subject: win98 1910 測試報告 Cc: Jonson <jonson@ms5.accmail.com.tw>,fwtn2@vot.net Sender: vippiv-request@ftp1.gep.ncu.edu.tw Resent-Message-Id: <B0000015564@ftp1.gep.ncu.edu.tw> Resent-From: vippiv@ftp1.gep.ncu.edu.tw X-Unsub: To leave, send text 'LEAVE' to <vippiv-request@ftp1.gep.ncu.edu.tw> 您好，弟是_Kii_Ali 經過了前幾天的 CIH 病毒事件，我想大家都怕到了 win98 這種東西 吧？尤其是證明了假版本的 win98 sp1 ，真是害人不淺，正如那個 ID縮寫是什麼 K 什麼 A 的傢伙在說的，大家一起雞飛狗跳了，難得 大家一起做「格式化」硬碟運動，再度證明了死雞和哀必閹等牌的硬 碟耐操性，好不熱鬧。才不過是 1900 rc3 版本，這下子在許多地下 站又看到 1910 rc4 ，不免令人懷疑，不過又是另一個假版本罷？ 總算抓下來使用了。以下的測試，純屬個人偏見。 不過，這是值得您使用的軟體。 安裝 ---- 在學校的 PII 機器上安裝時，結果無法順利的從所使用的 win98 1900 版 本升級。這似乎是有點反常，不曉得其他人有沒有碰到這種情形？ 以前的 win98 beta 版本，在 win98 底下安裝都是執行 windows 版本的 scandisk ，這一版居然跑去執行 dos 版的 scandisk 了，然後告訴您 「磁碟鎖住，請結束部分的公用程式」，安裝程式偵測到您同步使用 MS-DOS 程式，所以就不讓你繼續安裝了。即使把所有的程式全部退掉， 安裝程式仍然會出現 su03 的訊息，而不讓你再繼續安裝下去。 還有這種事情啊？ 如果是在 win98 dos box 安裝倒是有一些改進。至少打了 setup /? 會出現所有安裝的參數，而不會像前一版直接跳入安裝畫面。填密碼 畫面也較 1723 好多了，在之前的版本，填密碼時因為是英文字，而會出現 字底下一半被吃掉的情形，在1910 已經大為改善。只是還是要填密碼 有點煩。固然是可以拿之前的舊 beta 版本，從 precopy2.cab 解出 setupx.dll 套進去繼續使用，密碼連問都不問就可以過，安裝完再把真正 版本的弄回來。但畢竟麻煩，一般人也不會這麼做。算了，找找密碼吧？ 密碼同 1900 版本。 CWin98 1900 S/N K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3 我是直接在純 dos 下執行安裝，把所有的參數都設上去，至少安裝較 不煩人。 軟體更新部分 ------------ 這版跟 1900 沒有明顯差別。只是當您進「控制臺/系統/裝置管理員」 時，檢查每一個微軟內附的驅動程式，都是 4.10.1998 ，而非原先我們 設想的 1910 。從滑鼠驅動程式到 S3 顯示卡網路卡等無一例外，有些 明明檔案一樣，沒有改版，卻也冠上個 1998 的 build no. 。該是確定 版本了吧？而且由於倉促出新版，看起來像是只改版本號碼的工作而已， 有些驅動程式微軟仍沒有更新到最新，還是要到原公司的網路站上去抓。 不過這點恐怕是不能苛求了。 在ie4 的部分如同 1900 裝起來的，版號是 4.72.3110.1;sp1 ，您可以 對照看看您手上的版本是不是跟這個一樣。很難得看到 win98 出的 beta 中，沒有對 ie4 做更新。 :) 這版如同1900，不會「強姦」使用者原來的 netscape 設定，如果您預設的 瀏覽器是 netscape 它不會雞婆的推薦您使用 ie4，不過前幾個 beta 倒是 會有點雞婆的順便幫您把 netscape 的書籤順便轉成ie使用的書籤形資料夾， 然後就會發現 favorite 目錄底下一長串的東西在佔硬碟空間。在工具 列的「快速啟動」裡塞了 netscape ，它也不會硬要送個 ie4 的 link 給你。 當然囉，頻道列還是要免費送上的。 只是如果您使用「我的電腦/檢視/資料夾選項/檔案類型」時，就可以發現 在 url 的部分，還是有一些被改掉了。雖然仍然是使用 netscape 來看 web，或是指定了cuteftp 來抓檔，顯示的 icon 和執行的方式都還是以 ie4 的內定方式居多。雖然使用者可以改，但是要一般使用者去改這個 未免強人所難。在「控制臺/Internet/程式」雖然可以指定部分協定 所要使用的程式，但仍屬極為不足。 幾個建議 -------- 雖然這些建議，微軟大概也聽不到... 1.url 的控制和程式指定 要微軟弄個比較好一點的界面，讓使用者很方便的更改這些協定使用 的程式，好像有點難。微軟的 powertoy 有改這種東西嗎？在「控制 臺/Internet/程式」雖然可以指定部分協定所要使用的程式，但仍屬 極為不足。 Jonson[藏雲]兄，你要不要建議 X-setup 的 作者把這部分指定特定 winsock 程式的功能，包含在下一版內？ 雖然使用者改這些東西還「不太難」，很煩倒是真的。這些協定 我全找出來了，包括以下.. URL:Gopher 通訊協定 URL:HyperText 傳輸通訊協定 URL:HyperText 傳輸通訊協定附加保密 URL:MailTo 通訊協定 URL:News 通訊協定 URL:RLogin 通訊協定 URL:Telnet 通訊協定 URL:TN3270 通訊協定 URL:檔案通訊協定 URL:檔案傳輸通訊協定 2.DirectX5 DirectX5 已經是 win98 的正式規格，這次附上的版本號碼當然沒有例外的 通通改成4.05.01.1998 。其實微軟是可以在控制臺裡加入 DirectX 的控 制臺元件，都已經有了，就該讓它正大光明的顯示出來。安裝完英文版的 DirectX5 也一樣可以出現 DirectX 的控制臺元件 ，使用上沒什麼問題， 只是是英文版的看起來有一些不爽，也要忍受某些字元被吃掉的不舒服。 把它當成內建之後，至少在控制臺多個藍紫色底十字架型的東西，看起來 有點中古味道。 其實 bgr 出的 TweakIT 就可以一起設定，但是微軟怎麼沒有想到把 Directx.cpl ,Directx info, Ddirectx tool 全部整合在一起呢？分開 那麼多，對 end user 而言好像都差不多，不過是一堆垃圾工具。 如果微軟不想放正式中文的 directx.cpl ，要不然就只好麻煩國內的 中文化作者，給它來個「中文化」一下了。順便把 Vramdir.cpl 等也 中文化，對中文化作者這個應該都算是牛刀小試了。 又，在703巷有擺出 DirectX 5.2 中英文版，不曉得有什麼差別？在這裡。 http://703.cdpa.nsysu.edu.tw/download/dx5eng.exe http://703.cdpa.nsysu.edu.tw/download/dx5cht_tw.exe 在弟的經驗，即使是安了 tw 版本的 DirectX 5.2 ，控制臺內一樣 不會出現中文化的控制臺，而英文版本的卻有。我先把它上傳到這裡 好了，有興趣而又裝了 win98 的朋友，直接把這個檔案 copy directx.cpl c:\windows\system 就可以使用了。順便問一下上次 做 Final Reality 1.01 的中文化作者 Feather , fwtn2@vot.net ， Directx.cpl 中文化要不要試試？檔案很小，應該是牛刀小試，專有名 詞多了些倒是真的。 檔案我先丟在這裡 ftp://miau.cs.ccu.edu.tw/cpatch/directx/source/directx.cpl 旅遊和求助？ ------------ 這次的 Tour 和 Help 的部分已經做得更完全了，雖然還是有部分的缺損。 如果你像我一樣，要教完全不懂電腦的媽媽來學鍵盤怎麼用，滑鼠怎麼按， 這個部分其實是做得不錯。「探查 Windows 98」雖然唸起來有點直譯感， 內容建議您不妨全跑一遍看看，總共有四課，大家也可以複習一下什麼是 「中央處理單元」等等繞舌的東西。觀念還蠻新的，wave 使用 *.mpa 格式， 可以用 Xing 來播放，也減少了這些 demo 所佔的龐大體積。 又，錄 *.mpa 這個女聲是中文的，聲音還不錯，不過令我聯想到訓練「超級 耳朵」的辨視率，所幸聲音不會很機械化。我在想，不曉得是微軟請了那個 廣播員來講的？題外話，這類的白痴 cai 開頭部分，如果裏面先播個了一段 Bill Gates 或是 Kii Ali 的 *.avi 或 *.mpg 檔，應該會有點比較「活」 的吸引力和說服力。當然，塞了「飯島愛」或是 'Hitomi" 的原聲錄音，眾 男士們應該會更有興趣才對。 總共有四課，「電腦基本常織」「windows 98 概覽」「最新消息」「 Windows 98 相關資源」。按第二課檔案有所缺損，進去就卡在那裡不能動 了。 第三課連結到的反而有點像第二課的內容，裏面的雖然是廣告詞不少， 總也是微軟在 win98 的賣點，「非常」建議您去複習一下裏面 win98 的廣告 詞，至少知道 win98 有什麼新的好玩的地方，比看那個id 是什麼 k 什麼 a 的測試報告，實在多了。只是不免覺得 Active Desktop 和 ie4 功能灌水的 未免太多(頑固反微軟msie4 傢伙的一貫說詞)，不過自己褒自己不用錢，算了。 第四課有蠻重的廣告嫌疑，賣 Microsoft Windows 98 Starts Here 和 Microsoft Press ，不曉得臺灣要不要賣這個的中文版啊？倒不如用 心把這個 demo 做好比較實在。 結語 ---- 正式版會再改太多嗎？我想不會了，有點像是 final beta 的感覺。 當然囉，有的站在放出 win98 同時，還放出 vismwa.exe 這類的東西， 號稱可以把 win98 的日期限制和螢幕底下的 beta 版號去掉。事實上， 已經不用這種東西了，螢幕底下的版號，如果您是從舊 beta 一路裝上 來就會出現，但也無妨，如果您是直接裝 1900 rc3，已經不會出現這 個東西了。 對於不心急的朋友，應該是沒有差。要不然就再等到七月底正式中文 版吧？ 麻煩一下 -------- 您「不用」寫信問我 1910 到那裏去抓。很多地方有擺出來。寫了我也 不會回。 廢話 murmur ----------- 這個評論是應雄哥的要求而寫的。如果您覺得這個評論信寫的不太爛的話， 寫封信來鼓勵打氣，或是反駁。弟有點累了。 您可以自由引用、轉送、剽竊本文的部分或全部。只要您高興。 Outlook Express 的使用者請勿使用 HTML (請改用一般純文字模式) 和 Quote-Printable 選項(國內不須使用)，使用者資訊名稱儘量使用 英文ID，以免造成收信人亂碼困擾。 黃國書(Kii Ali)，私立復興國中地理老師，電腦測試狂。 ICQ#5107476
去除 CWin98 Service Pack 1 開機時過期提示
* updated by Kii Ali, 12-11-2001 Date: Sun, 07 Mar 1999 03:26:35 +0800 To: VIP <vippiv@ftp1.gep.ncu.edu.tw> From: Henry Pan <pank@ms12.hinet.net> Subject: 去除 CWin98 Service Pack 1 開機時過期提示 Cc: patch-author@cpatch.org 去除 CWin98 Service Pack 1 開機時過期提示 File IO.SYS Find 61 26 81 Edit 00 00 00 -- Henry Pan BBS ID:pank PGP Key ID:ECD8C249 Tale.net http://www.tale.net LemonTree ftp://ftp.tale.net AppleTree ftp://apple.tale.net BBS telnet://bbs.te.fcu.edu.tw
Window 98 中文版修正檔 Pack 1 (Build 912)
Window 98 中文版修正檔 Pack 1 (Build 912) 此版本修正了 Windows 98 中文版中的已知錯誤
CFido 北京Paradise BBS天堂资讯站 帖子随记
- 没有顺序，帖子本身没有标题。
Windows 95 , Windows NT 4.0 , Memphis(Beta 2)比较
============================================================================= * Forwarded by Searching Autumn (6:653/1018) * Area : WINDOWS.CHINA ([晕倒死区.中国FIDO网]) * From : Clement Huang, 6:650/2 (Thursday March 26 1998 17:07) * To : All * Subj : 95,NT,Memphis ============================================================================= Windows 95 , Windows NT 4.0 , Memphis(Beta 2)比较: +-------+---------------+-----------------------+-----------------------+ | | Windows 95 | Windows NT 4.0 | Memphis(Beta 2) | +-------+---------------+-----------------------+-----------------------+ | 内核 | 16位+32位 | 32位 | 32位+16位 | +-------+---------------+-----------------------+-----------------------+ | 用户 | Explorer | Explorer | IE 4.0 | | 界面 | | | | +-------+---------------+-----------------------+-----------------------+ | 16位程| DLL | VDM(虚拟DOS机) | DLL | | 序接口| | | | +-------+---------------+-----------------------+-----------------------+ | 设备驱| 32位+16位 | 32位 | 32位+16位 | | 动程序| | | | +-------+---------------+-----------------------+-----------------------+ | 物理内| 无 | 完全 | 不完全 | | 存保护| | | | +-------+---------------+-----------------------+-----------------------+ | 32位程| | | | | 序相对| 100 | 160-180 | 140-160 | | 运行速| | | | | 度 | | | | +-------+---------------+-----------------------+-----------------------+ | 稳定性| 差 | 非常好 | 一般 | +-------+---------------+-----------------------+-----------------------+ | 文件 | VFAT(2G), | NTFS, | FAT32 | | 系统 | FAT32 | FastFAT | | +-------+---------------+-----------------------+-----------------------+ | 注册表| 无 | 管理员设定 | 无 | | 保护 | | | | +-------+---------------+-----------------------+-----------------------+ | 网络 | 一般 | 好 | 较好 | | 性能 | | | | +-------+---------------+-----------------------+-----------------------+ | 应用程| DOS :98% | DOS :90% | DOS :95% | | 序兼容| Win3.x:99% | Win3.x:95% | Win3.x:95% | | 性 | WinNT :60% | Win95 :95% | Win95 :99% | | | | | WinNT :80% | +-------+---------------+-----------------------+-----------------------+ | 实际最| | | | | 低硬件| | | | | 配置 | 486DX2/ | P54C-100MHz/ | P55C-166MHz/ | | (CPU/ | 8M / | 24M / | 24M / | | 内存/ | 300M / | 540M / | 800M / | | 硬盘/ | 1M | 1M | 2M | | 显存 | | | | +-------+---------------+-----------------------+-----------------------+ | 使用 | 一般 | 较难 | 较易 | | 难度 | | | | +-------+---------------+-----------------------+-----------------------+ | 价格 | RMB 900+ | RMB 4000(Workstation) | ??? | |(正版) | | RMB 12000(Server) | | +-------+---------------+-----------------------+-----------------------+ | 特点 | 兼容性好 | 安全性高 | 界面友好 | +-------+---------------+-----------------------+-----------------------+ 上表是我使用这三种操作系统的体会,仅供参考. -+- 天堂总站向您问好! + Origin: 欢迎光临北京天堂资讯总站 TEL:68188622/68169730/68169731 (6:650/2)
WIN98的时间限制如何取消
WJJ> WIN98的时间限制如何取消?
YZQ> PWin98 beta2 解除时间限制的办法 (cRACK bY cTRLd)
YZQ> (理论上适用于 Win98 的任何一个 beta 版本)
YZQ> 1. 打开 IO.SYS
YZQ> 2. 寻找 2D BC 07
YZQ> 3. 换为 2D BD 07
YZQ> 注: 将 BC 换为 BC + n 即可获取多 n 年的使用时间,
BL> 这个我也在光盘上见过,你试过了吗?能说说BC换成BC+n
` 俺^^是从光盘上摘下的,俺也没试过.
BL> 将样换吗?除了用pctools9.0寻找此地址,还能用什么工具
` ^^成BD加一年,换成D0可延长20年!
BL> 来查找(windows98是32位的,低版本的pctools不能用)
BL> 请指教,谢谢!
...> _____网内存知已___
... 杨 智 清 0311—7062636 ；127—1167148
...> 天崖若比邻
... 欢迎使用蓝波车明汉化版!
--- 蓝波车明汉化版 v2.31
* Origin: Hebei Info Bank BBS (86-311)3031617 (6:652/1)
Ewin98beta2如何去除时间限制
-=> 听 Tony Yang 向 All 说得正热闹，我也来插一嘴：
TY> * 多区投递 来自:9
TY> 各位:
TY> Ewin98beta2如何去除时间限制,是不是先用软盘dos(是否6.22?)启动,
TY> 然后用pctools修改IO.sys的某些字节(甚么字节请明示).希望能从你
TY> 们那里能找到答案.
b4 2a cd 21 91 2d bc 07
改为：b9 11 00 ba 01 01 91 90
>>>> ---- 一个新网友 --------
... (北京）魏志新 010--65082333
>>>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@
... 好东西自然受欢迎！
--- 蓝波快信/DOS v2.20
* Origin: -* Beijing Naturel BBS 大自然信息台 010-6423-7461 *- (6:650/25)
Windows NT 5.0 周其力 杨 波 编译
——Windows NT 5.0 周其力 杨 波 编译 现在许多IS部门都把应用程序从大型机上移走， 建立起了基于适合于工作组的软件的大规模分布式应用程 序，牺牲了大型机的可比性、可靠性、可管理性和安全 性。微软瞄准这一点，推出Windows NT 5.0，向用户展示 出X500型的目录服务，Kerberos安全体系和增强型 DCOM。结合微软交互服务器，这一新浪潮将形成对企业计 算机世界的强大冲击。 目录服务 新的NT50的中心特征就是它的目录服务功能。 这种目录被称为活动目录，用来解决NT没有能适用于企业 的目录系统的问题。和活动目录的X500相比较，原NT 40 中使用的网络目录服务(NDS)所提供的目录服务真是相形 见绌。但微软并没有创造任何新的东西，这一举措完全是 围绕着DNS和LDAP而展开的。 DNS的层次型应答式命名服务已为我们所熟知。尽 管作为Internet网的中枢目录协议，但对于单个企业来说， 它仍缺乏足够的灵活性。一个完备的目录服务应该能够把 任意对象名(如机器或应用程序)映象到相关的任意信息上。 但DNS基本上还是一种从机器名到IP地址的映象服务。 X500能提供从系统到服务的任何定位。但由于 其极度复杂性，数载经营之后仍未能广泛推广。此时，X500 DAP的简易版本LDAP获得了若干目录经销商的支持承诺。 活动目录是建立在DNS和LDAP的共同基础之上的。 它把机器分组为称为域的管理单元，并给每一单元赋与诸 如acme.com的DNS域名。每个域都必须有一个运行活动目 录服务器的NT机器作为域控制器。 就像域控制器操纵NT服务器一样，拥有DNS和LDAP 软件的用户也应该访问控制器的目录数据库。DNS已成为 (LDAP也即将成为)广泛推广的工业标准。及此，Unix，Mac 和OS/2的用户都能以Windows和NT用户的相同方式访问活动 目录服务器。 活动目录数据库可以存储各类信息，这意味着它 可以作为通用目录在不同网络上使用。例如，它允许存储 和检索联系一个运行在网络Unix服务器上的服务的必要信 息。很奇怪微软这回在关键技术上倒采取了世界通用的态 度。 由于增进了容错能力的性能，域可以有多个域控 制器，且每个域控制器都拥有一个域目录数据库的完整复 本。在这种多控制应答的情况下，任何域控制器复本中的 项目改变，都可以最终渗透到其余复本中去。 为完成这种应答，微软创建了一个域控制器之间 的通信协议。为与外界进行可互相操作的应答，活动目录 也支持X500定义的目录信息影像协议(DISP)，但有效与 否尚未可知。要获得有效的应答，需基于一个共同协议和 对应答什么的共识(例如共同的目录数据库模式)。只有解 决了模式问题，标准应答协议才会充分有用。 微软为活动目录的用户提供了不同的应用程序接 口，其中最好的选择是活动目录服务接口(ADSI)。它是一 般的基于COM的接口，可以用以活动目录、NDS和其它目录 服务。其余选择还有微软的MAPI，LDAP的CAPI和OLE数据 库。软件开发者可择需而用之。 活动目录最明显的竞争者毫无疑问是NDS。基于 X500的NDS功能强大、灵活、技术复杂。由于发展得早， 不能像DNS和LDAP那样集成化而成为关键目录标准。但它仍 拥有大批追随者，占有相当市场份额。很难说活动目录与 NDS在技术上谁优于谁，微软的竞争点应放在提高活动目 录的简易性和其与标准的一致性上。 分布式对象 活动目录包括一个类别存储，作为Windows登记 的分布式版本。应用程序可使用活动目录寻找目标代码。 你可以编写能够存在于系统而不仅仅是调用处的程序。从 NT40开始，微软扩充了COM使之成为DCOM。 COM定义了软件间提供服务的语言无关的标准途 径。一个COM对象包括一个或多个方法，用户可经由接口 访问方法。使用这种对象的用户可以获得每个接口的指针 并请求该接口的方法。 COM自身允许用户不去理会对象的使用是在动态 链库中还是在同一机器的其它过程中。DCOM对COM对象扩 展了这种简易性。当用户请求一个远程对象的方法时， DCOM在网络上定位对象，给目标系统发送RPC。远程对象 的定位可由用户提供，存储在用户登记上，或是存储在NT 50活动目录里。这种操作就象是在局部环境中进行的 一样。当然，两种情况下的代码是相同的。 DCOM依赖于由DCE定义的微软实现的远程过程调 用。其被命名为微软PC，在Windows和NT中有广泛应用(虽 然DCE本身并不流行)。由于它提供了这些操作系统的各种 复本，几乎已成为今日最广泛使用的RPC协议。微软称 DCOM的这一变种为对象RPC(ORPC)。 另外加入DCOM的是集成了微软交互服务器。MTS应 用程序必须以COM对象描述。至少是现在，对于这些对象的 直接远程访问只能经由DCOM。独立软件经销商可以创建与 MTS标准一致的应用程序，交给用户去结合建立完整解决方 案。这一结果形成了类似于已存在ActiveX客户端部件市场 的服务器端市场。虽然有包括IBM和Oracle在内的若干经销 商也试图做出尝试，但还没有别的交互服务器能做到这一 点。 DCOM在1996年成为NT40的标准组成。以AG软件 为主要来源，微软1月份推出Windows95版，其余的对 Solaris，HP－UNIX，Linux，MVS及其它操作系统的版本 的推出预计在年底完成。那时的DCOM将不再是 Windows/NT的独享物。 但DCERPC也非访问远程方法的唯一协议标准。 OMG也在CORBA中定义了一个替代品ⅡOP。它所提供的重 定向功能使用户能了解到移动了的对象。这比RPC协议略 胜一筹。但两者的基本问题是一致的。据称，OMG的CORBA 和OMA的其余部分已得到了更多经销商的支持，而且比包 括DCOM/ActiveX在内的其余任何中间软件都更适用于多种 平台。OMG规范力图于从始至终的大众化，平台中性和语 言中性，支持分布式而非将这些特性逐个加入。 虽然在目录和安全服务上有多样性是糟糕的事， 但在RPC协议上的多样性却并不见得坏。Netscape就采用 了ⅡOP作为标准协议并把它加入到Navigator的每个复本 中去。但反微软的力量并没有结成单一的对DCOM的ORPC 的竞争者。Sun就为Java对象之间的通信另开发了一个称 之为RMI的替代协议。虽然谁最有用尚需拭目以待，但微 软似乎已成为这场竞争中最大受益者。凭借着公司的实 力，微软将自己的协议推行到了现行的两个最为通用的 操作系统中，并加入了DCERPC——这也是——不容忽视 的强大力量。 安全服务 目录服务让你找到所需的东西，通信协议使你 能与其交互访问。但并非每个人都能在网络上进行任意 的查找与交互访问。NT50也为这里所需的分布式安全 服务的访问控制提供了新的工具。 有效的分布式安全体系需要几方面因素。首先 也是最重要的一点就是鉴别途径，也就是用户向服务器 证明身份。其次是用户提供授权信息给服务器，由它决 定用户所拥有的是哪种访问权限。再次是数据的完整 性。密码校验包括了所有的传输数据，让接收者能检测 出数据传输中遭受到的任何攻击性变化。数据的私有可 通过加密传输数据而获得。 这回微软在分布式安全体系上采用的是主流工 业标准。NT有一段时间曾支持SSL。但这种基于公共密钥 的安全体系有时并不完善，而且对于某些应用程序的加 密也相当缓慢。基于这些原因，NTLAN管理器(NTLM)开始 成为今日的局部NT中分布式安全的主要协议。它提供鉴 别、数据完整性和数据私有，对单个域来说是比较理想 的。但它也仍存在欠缺，在非微软环境下也不流行。 与增强和提高现行的协议相反，微软正准备将 NTLM降级为传代物。在NT50中，微软将开始采用MIT 的Kerberos。它在NTLM上增加了新的功能，即相互鉴 别。也就是服务器也需向用户提供身份证明。微软的 Kerberos具有标准Kerberos5.0的功能。微软环境下每 个域都有自己的Kerberos服务器，分享活动目录使用的 数据库。从而Kerberos服务器必须在域控制器上执行， 且能在域中应答。 希望安全访问远程服务的用户必先登录Kerberos 服务器。成功登录后给用户返回TGT。然后用户再将之传 给Kerberos服务器去申请具体的应用程序服务器口令。 如果Kerberos服务器认为用户提供的TGT无效，则将请求 口令返还用户且不提问。用户可将该TGT发送给远程应用 程序服务器，由它来鉴别用户身份。这些口令都用不同 密钥以不同方法加密。提供分布式安全并非易事，所以 Kerberos是相当复杂的。 微软选择去标准化安全协议的做法好得几乎令 人难以置信，但事实就是如此。然而即将实现的标准 Kerberos50协议并没有确切定义发送什么去鉴别用 户。Kerberos的不同实现发送的是不同的授权信息。所 以微软版本发送特殊NT安全标识符就不足为奇了。这样 的话，与其余Kerberos实现的完全互动性就成了问题。 由于在这一领域还没有广泛认同的销售标准，所以很难 对这一问题找到好的解决途径。 NT无处不在吗? 就即将来临的NT新增功能来看，用户们可以得 出两个主要结论。一是微软在尽最大努力使NT在分布式 环境中更为有效。虽然活动目录和安全服务的性能还需 操作系统的长期考验。二是微软通过在分布式服务中实 施标准协议而试图让NT适合多销售的环境，其中包括 Unix，Mac，甚至大型机。但是诸如目录应答，Kerberos 授权信息甚至一些尚未发现的问题依然存在。微软此时 买入几乎所有的多销售商中间软件的标准，把这场长期 竞争的未来面貌已经澄清。其它任何公司都无能力创建 一个适宜的中间软件解决方案，使之成为广泛应用的标 准。而令人奇怪的是，微软也没有这么做，它紧抱标 准，给自己保了个险。 ... Fe Tiger 9800-393074 >>> fstiger@pub.foshan.gd.cn ... 风情犹拍古人肩 -- 宋/黄庭坚/定风波 --- 蓝波车明汉化版 v2.30 * Origin: Homeboy Club 阳光灿烂的日子 86-757-3387141～3387144 佛山 (6:655/501)
显示方式的新潮流——体验Win98的多重显示技术
显示方式的新潮流——体验Win98的多重显示技术 Win 98的多重显示技术（Mutiple Display）是近来人们谈论的 热点，但由于仅处于“谈”的阶段，大多数人对它并没有多少感性认 识。为此，笔者在Win 98 Beta2简体中文版上同时使用两个显示卡，分 别挂接两台显示器，对Win 98的多重显示功能进行了实际体验,感受了这 种显示方式带来的方便与乐趣。就个人体会而言，正如微软宣称的一 样，用过多显示器后，再也无法忍受单显示器那狭窄的视野。或许多重 显示将真的成为PC显示方式的明天，甚至引起一场革命。下面我们就结 合实际深入了解一下Win 98的多重显示技术。 一、Win 98多重显示技术简介 一台PC挂接两个显示器，这在过去主要通过高档显示卡提供两 个视频口来实现，仅在少数高端图形工作站使用。随着Win 98的出现， 现在普通的PC用户也可享受到多重显示带来的好处。目前Win 98 Beta2 可同时支持4套PCI显示系统，到正式版推出时将可支持9套，以3x3的矩 阵形式显示电视墙效果。因此，这种多重显示技术将进一步拓宽PC的应 用领域。当前显示器的屏幕尺寸每增大一级，价格就翻一倍，比如15寸 显示器的价格不到17寸的一半，而两台15寸的屏幕面积则远大于一台17 寸。从经济的角度看，用多台小屏幕代替一台大屏幕无疑是合算的。对 于个人PC用户而言，只需把淘汰了的低档PCI显示卡和14寸显示器利用起 来，就会得到一个全新的PC视野，尤其是游戏发烧友和电脑图形工作 者，可以最小的投资获得最大的收益。 利用Win 98的多重显示支持可以实现的功能包括：1扩展 Windows桌面，相当于扩大了屏幕面积。2进行图形设计时，一个显示 器显示图形全局，另一个进行局部放大显示。3一个显示器显示视频动 画，另一个显示文字说明。4运行多视点游戏，比如用四台显示器显示 战机游戏的前、后、左、右四个方向的视野。5多个显示器分别显示不 同的Web页面。6以电视墙效果显示大画面。目前的For Win 95应用程 序只能实现第一个功能，即扩展桌面。要实现后几个功能必须使用Win 98提供的新应用编程接口（API），也就是只有For Win 98的应用软件才 有可能提供这些功能，相信98年新推出的游戏和图形软件会支持多重显 示。 Win 98提供的多重显示功能非常易于控制，不过显示卡必须是 PCI插口的。当多个显示卡安装在系统上后，其中一个为主卡，即系统启 动时使用的缺省显示卡，其余为副卡，在Win 98中分别标记为显示器1、 显示器2、…。通常靠近电源的第一个卡为主卡，为显示器1，之后按序 递推。各个显示卡分别挂接不同的显示器，用户可为各个显示子系统设 置完全不同的分辨率、颜色数和刷新率等显示参数。 二、在Win 98中安装多显示系统的方法 在这里以安装两个显示卡为例，原系统为Winfast 280V2显示卡 加Philips 14B显示器，然后将S3 765卡和另一早期的14寸显示器同时挂 接上去。具体操作步骤如下： 1在280卡下正常安装Win 98 Beta2，并安装好显示驱动程 序，设置合理的显示参数。 2正常关机。将765卡插入PCI插槽，插时注意与280卡的位置 关系。在笔者使用的系统中靠近电源的一边为主卡，启动时Win 98自动 使用主卡作为显示器1。 3.重新启动。使用主卡的显示器正常进入Windows图形界面，而 挂接副卡的显示器以字符方式显示一段英文，大意是：如果要使用该显 示器，请在控制面板中将它设置为桌面的一部分。 4.在主显示器中进入控制面板，打开“显示”，此时在单显示 系统下的“设置”选项卡变为“显示器”选项卡(如图)，可使用的显示 子系统列在表内。选择第二个显示系统，并使“将此设备当成桌面的一 部分”复选框有效，选项卡的主画面显示当前系统使用两台显示器(如 图)。此时单击“设置”按钮，可以更改当前选中显示系统的显示参数。 完成前述操作后，按“确定”，副显示器即进入Windows的图形界面，成 为桌面的一部分。 当副显示器成为桌面的一部分后，桌面面积增大一倍，桌面的 扩展方向为主显示器的左边，其横坐标范围为－640（或－800，－102 4，…）到0，主显示器的坐标范围为0到640（或800，1024，…）。用 PrintScreen抓取的全屏图如图所示，可以看到两个显示器的显示范围略 有错位。 由于当前的应用软件没有使用Win 98提供的新API，故无法以电 视墙效果显示大画面，当对窗口进行最大化时，只能将显示范围扩大到 一个屏幕范围，如图所示。不过，可以把一个窗口置于两个屏幕的交界 处，如果两个屏幕的设置不同，所抓取的图像区别很显著。如图所示， 一边是64K色，另一边是256色。 在安装多显示系统时应注意以下问题： 1主板内置显示卡。在安装Win 98时要确保系统只有一个显示 卡，如果主板有内置显示卡，应先拔掉外插卡。在插上外卡重新启动 后，外卡成为主卡，内置卡成为副卡，如果再添加显卡，内置卡成为第3 个副卡，总之内置卡的优先级最低。这是由主板上的BIOS控制的，而非 由Win 98控制。 2用作主卡或副卡的条件。所有带Win 95 驱动程序的PCI图形 显示卡都可作为主卡，如果主卡使用Win 3.x的驱动程序，副卡将无法使 用。而副卡需要由Win 98提供的专用驱动程序。目前Win 98 Beta2支持 的副卡包括：ATI Mach64 GX、S3 764V＋(765)、S3 Trio 64V2、S3 ViRGE、S3 Aurora (S3M65)、Cirrus 5436,7548,5446、 ET6000、ATI Rage 1 ＆ 2 (VT ＆ greater)。此外，对ATI Mach64和S3 ViRGE支持 DirectDraw，对S3 ViRGE支持Direct3D。 随着15寸显示器的普及，不少朋友想对现有的显示系统进行升 级，但又觉得将原有系统闲置实在可惜，Win 98多重显示技术的出现彻 底解决了这一问题。手上有多余显示器和显示卡的朋友，现在就动手 吧，宽广的屏幕视野将带给你全新的感受。 < ＼ 王 ／ ～ ～ 铁老虎 9800-393074 > ⊙ ⊙ ～ ～ ～ ～ fstiger@pub.foshan.gd.cn < /ω\ ～ ～ ... All的一句温柔的娇音入耳,韦小宝脑中登时天旋地转,喜欢得全身如欲炸裂. --- 蓝波车明汉化版 v2.30 * Origin: Homeboy Club 阳光灿烂的日子 86-757-3387141～3387144 佛山 (6:655/501)
试 用 Windows98中文测试版
试 用 Windows98中文测试版
Windows98 测试版开始测试至今以近9个月，尽管Windows98
是迄今为止桌面Windows的最佳版本，但业界对它的评价仍是贬
过于褒。
笔者认为win98与win95相比较,性能是有所提高,特别是对
高配置的计算机用户来说。由于是测试版,部分功能有待改进，
且安装没有win95顺利。
一.关于安装
1.安装注意事项
1>电脑配置最好在P133，32M以上，应有400M以上的硬盘空间。
2>应当制作启动盘,保留原操作系统的备份,不必急着作FAT32
的转化，这样可以很方便地删除Windows98(即使安装未成功)。
3>最好将文件复制到硬盘，从配置好驱动程序的Windows95中
安装Windows98。
4>部分硬件必须手动配置,在系统设置中同一设备可能出现两次。
2.个人安装经历
去年9月在朋友处第一次看到pwin98，借回光盘花了半天时间
安装完毕。由于机器速度太慢，过几天就卸载了。当时的机器配置
为P100、8M,1.0G,T9680。
后来将电脑升级到6x86L-PR200+(超至83.3*2),32MEDO,金鹰
s3-375(4M),安装pwin98时速度明显加快,除声卡(OPL3)手动安装,
其余一切正常。而一些游戏（如八一战鹰）的效果明显好于pwin95b,
可能是显卡的驱动程序较新的原因。但一些应用程序(如word97,
photoshop4.0)的启动速度要比win95稍慢。
今年组装了一台电脑,由于用AGP显卡,因为Pwin95b(OSR2.0)不支
持AGP,所以只有装Pwin98-b2版(当时市面上还无b3版)。安装很顺利,
使用一些应用程序(如office97)也正常,古墓丽影Ⅱ效果很好。可是
玩另外一些游时(如摩托英豪,云霄飞车等),启动游戏时弹出对话框显
示direct draw fail,无法运行，重新安装问题依旧。换上另外一块显
卡(金鹰s3-375),一切正常。将电脑搬到电脑公司,四、五个人搞了一天,
最后只有卸载PWin98了事(win95b中一切正常)。
机器配置为:pⅡ233,华硕P2L97主板,华硕AGP -3000TV显卡(驱动程
序版本是1.04),启亨PCI声卡。
后来有了pwin98-b3版,复制文件是很顺利,到配置系统文件时出现
"SETUP发现.CAB文件损坏,并试图从此状态恢复",确定后依旧。取出光
盘提示driver16.cab错误。退出安装,将光盘上文件拷到硬盘,再次安
装问题依旧。重新用光盘安装，出错时换上pwin98(b2)光盘,可继续,
依提示再换上pwin98(b3)光盘,文件复制完毕安装程序重新启动,安装
程序设置好"控制面板"等,到系统配置又死机。冷启动问题依旧。
重新启动到安全模式,打开"系统",发现有几十个同样的显卡.将其删除
仅剩一个,并将驱动程序改为VGA,重新启动成功,进入"控制面板",将显卡改
为pwin98自带的"华硕AGP-3000"驱动程序,重新启动成功,可是无声。进入系
统设置,发现声卡上有黄色!。删除后重装,出现driver16.cab错,无法安装。
安装声卡自带驱动程序,重新启动,出现链接错误,死机。进入安全模式依
旧,无法解决,又找不到声卡新的驱动程序只有运行A盘上的uninstall,回
到win95.
将硬盘Fdisk,Format,再次安装,问题依旧无法解决。
后来将driver16.cab 解压到硬盘,删除driver16.cab,在pwin95b中
从硬盘安装,依提示操作，一切顺利。只是声卡无SRS,将驱动程序更改
为声卡自带的驱动程序,一切变为正常.运行至今，感觉良好。
由于硬件配置不同，安装时会遇到不同的问题。就上述“.CAB”的
问题，解决方法很简单。如安装时碰到相同问题，可少走弯路。
二.Windows98的新特性
1.任务栏中的“显示桌面”，可以在运行应用程序时，很方便地使用桌
面上常用程序的快捷方式启动另一程序，而不必到“开始”菜单中一层
层去寻找了。
2.系统工具中新增"磁盘清理程序"可很方便地清除 Internet 临时文件，
已下载的程序文件，回收站和临时文件。
3.“系统文件检查”能检查系统文件是否都正确，可从验证数据文件中
删除或更新文件，也可从安装盘提取系统文件。
4.控制面板中新增的“桌面主题”,可非常方便地将外观改为习惯了的
桌面。
5.Windows98的磁盘碎片整理程序可以把磁盘上的文档归并到连续区域，
还可以重新安排程序文件以使程序启动得更快。
6.“系统信息”可以详细列出各种系统信息，当用 Internet 寻求技术支
持时，这些信息可是非常重要的。
7.“Windows 调整”，可对系统进行调整，加速经常使用的程序。
8.“计划任务”可安排适当的时间自动维护系统，以便使系统设置成最
佳性能。
9.“Windows 更新” 可通过 Internet 完成对系统的更新。
10. “Windows 帮助”，本地帮助文件未汉化。也可通过 Internet 获
得帮助。
三.Pwin98部分性能
1.原来在Pwin95b能双启动,Pwin98不需作任何修改,仍能双启动。由于
不显示“Starting Windows98...”，必须在自检按键不放。
2.取消除pwin98必须以外的内存驻留程序,系统资源可达96%。
3.Internet Explorer 能有效地管理系统和随时从网上获得最新信息。
4.b3版对AGP显卡的支持，较b2版有较大改进。
5.硬件驱动程序齐全，版本也比较新。
6.支持USB和IEEE 1394端口,提高了计算机使用的方便性。
上述几点仅仅是本人使用PWindows98的经历和体会，我用 Windows98
这段时间，死机率明显底于Windows95。我个人认为 Windows98 不管是
从系统性能，还是从方便实用来说，都比 Windows95 有所提高。不过
它对系统硬件的要求也越来越高，这也可能是 Wintel 的一个阴谋吧。
3.12
☆☆☆☆☆☆☆☆☆☆☆
☆ 姓名: 罗卫平 ☆ Ｌ Ｗ Ｐ
☆ ID:Luo weiping ☆
... 月明星稀,乌鹊南飞.绕树三匝,何枝可依?
--- 群星中心邮局
* Origin: 群星荟萃站希望您能成为一星! (0571)5113934 (6:660/106)
今天在D版光碟点见到有一张WIN98的简体中文正式版
... Windows 2000,DUNE 2000,BWAVE 2000... ... 人的欲望真是无止境啊... RT> 今天在D版光碟点见到有一张WIN98的简体中文正式版, 不知道 RT> 大家有否用过? 其内容是否当真? 请注意一下光盘封面的logo，有beta 3字样的编号Win-1的是实用工具集合， 有不少好东东，其中包括Windows 98 简体中文beta-3测试版。如果没有beta 3字样， 且编号为“简中W98”则为Windows 98英文beta 2 CD版，内有中文beta 2的安装版。 --- ＣＲＵＥＬ ＫＩＬＬＥＲ ☆┃HAMMER┃★ --- 因为我的病就是感情太多 ★┃OF GOD┃☆ ... 京工附中现象二十：男生不会玩《美少女梦工厂》，女生精通《ＹＥＳ！ＨＧ》 --- 神锤帮专用蓝波 vip版 * Origin: 欢迎光临北京天堂资讯总站 TEL:68188622/68169730/68169731 (6:650/2)
我已经用了WIN98 Beta3一个多月了
-=>原信是 Zhang Mole 给 Eagle Lin 的<=-
EL> 我已经用了WIN98 Beta3一个多月了,很稳定,速度也快. ;))
ZM> 你的是什么鸡? 俺看到的是K5-133. 8M内存的鸡. 太慢:(((
ZM> 是不是有优化的方法?
EL> 我用的是INTEL 200MMX,32M SDRAM,火球5代2.1G,创宏TX主板.
EL> 我看这东东是没有什么办法能很好的优化了,硬件是有点老火. ;(
ZM> 俺认为, WINDOW系列太吃RAM, 那天在朋友那看到16M的内存装了
ZM> 98还是难以忍受呢;& 更别说那8M的鸡了:(( 你太幸福拉:)
我还有一台133,16M,SEAGATE 850M,中凌2000HX,也装了WIN98,还可以
用起来非常的方便. ;)
>>> 荆棘鸟 Eagle Lin
>>> eagle.lin@usa.net ICQ: 5782873
>>> http://www.nease.net/~hlyufeng
... 每一个来到世界的生命在期待,因为我们改变的世界将是他们的未来... 罗大佑
--- 荆棘鸟综合加工厂
* Origin: 贵阳荆棘鸟信息资讯站 * 0851-3833577 * 欢 迎 光 临 (6:662/51)
* 多区投递, 来自: 『CHAT.China [神州神聊]』
究竟WIN98正式版几时会出?
-=>原信是 Robin Tan 给 Dannil Hong 的 "WIN98几时出?" <=- RT> RT> WIN98的BETA2已经出了这么久了, 究竟WIN98正式版几时会出? DH> 3.19在德国首发 RT> RT> 今天已经是4月4号了, 不知到现在有否WIN98的消息呢? 现在又没有消息了:( 俺好不容易找到一个ewin98 beta3,还是坏的:(( 等不到win98只好用beta了 >>> http://www.nease.net/~dannil CBP:(010)288c33599 ... 〖品〗Dannil Hong 〓 ☆ ☆ 〓 UIN:2077478〖品〗 >>> E-mail: dannil.hong@usa.net 舒克营长 ... 从蝙蝠的羽来,到夜魔的青爪去,契约的失效...青爪邪核诅咒!! --- 蓝波95 v2.53 [NR] * Origin: West-Point Programmer's BBS * 86-10-6252-4869 (6:650/27)
上星期天的,我正用着,没了beta 3的标记
-=>原信是 Mark Xu 给 Robin Tan 的<=-
MX> 上星期天的,我正用着,没了beta 3的标记,是1691
正是WRC0的,我在Winbeta拉时,它的目录就是如此,不过还有个Upgare :)
MX> 我想是可能是WC0版本.但1713中文版也出来了.internet上有,不过太大.
在哪有1713的版本?是否可以Uninstall IE4? :)
MX> Bate 3 1676 1691,我感觉bug少了,但前题是64M下,32M明显跟不上.
我觉得使用1602的稳定性不错 :)我使用486/20RAM照样跑的欢? :)
MX> 正式中文版我想要8月份以后.
应该是6.25同时发表 :)
--> 立冰山之巅,观赤热炎焰 Yours Friend
... 世界上本没有路,走的人多了也就成了路.
--- 请到菁华资讯来
* Origin: -* Elite BBS 菁华资讯 *- Tel:0597-752-1998 (6:657/701) (6:657/701)
上星期天的,我正用着,没了beta 3的标记
於 Friday April 10 1998，19:26，
在「SOFTWARE.CHINA [运用软件]」信区中 Janson Yang 发给 Mark Xu 的，信中提到......
Dear Janson Yang ， 您好：
-=>> 原信是 Mark Xu 给 Robin Tan 的<=-
MX>> 上星期天的,我正用着,没了beta 3的标记,是1691
JY> 正是WRC0的,我在Winbeta拉时,它的目录就是如此,不过还有个Upgare :)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
好象此www要密码的,给个能入的密码给我,我很想看看
我申请了N次参加win98 beta测试都不批,可怜!
MX>> 我想是可能是WC0版本.但1713中文版也出来了.internet上有,不过太大.
JY> 在哪有1713的版本?是否可以Uninstall IE4? :)
没试过,6:654/1008 站台有WRC1 1718,您可文件直索,不过134M小心电话费.
┌─ 人生何处不相逢 葵乡小苑 Ｍａｒｋ Ｘｕ──────────┐
│E-Mail:jmxuguo@pub.jiangmen.gd.cn BB:0750-996833791 ICQ:3002087 │
└─────────────────────────────────┘
--- GoldED 2.50+
* Origin: SunFlower BBS 葵乡小苑 TEL:750-6600557 广东新会 (6:656/111)
我装了一个Frontpage98
... 听得Gary Liu和Liu Jin正唱起＜frontpage98＞的拉网小调，我抓起麦克风 ...
LJ> 我装了一个Frontpage98,还没有用,他就提示我
LJ> 使用期限已到.:(
LJ> 请问大家该如何搞定?
GL> 你用的是BETA版,如果改系统时间不行的话?就只有用正式的了.
谢谢大家对此事给我的回信.
我用的是BETA版,但我已经在老信包中,找到了破除时间
限制的方法.
如下:
----------------------cut-----------------------------------
寻找一个名为fp30cutl.dll的文件,然后找57 75 0B 89这几个
字节,找到后将75 0B改为40 48就一切OK了,
我下载的FP98测试版就是这样解决的.
> ┏━━━ | email:flying@iname.com
... ︽︽︽︽︽︽︽ | http://www.nease.net/~flying
> ━━━┛ShaoFei | http://flysun.home.ml.org
-------------------- CUT --------------------------------------
谢谢大家的关心!
在此向所有给我回信的站友表示感谢!同时也向所有帮助过我的站友
表示感谢!
BTW:这个BATE版好像不能汉化,请大家注意!
∥∥∥ ┏━━━━━━━━━━━━━� ━━┓
... ⅹбб ┃LIU JIN ★傻傻 的 歌谣★ LIU JIN┃ - 武汉 -
～ ρ ┗━━━━━━━━━━━━━━━━┛
... 释伽在此，释伽不在此／释伽恒躲在碑的反面
--- ～平静如水～ v毕生缘
* Origin: Jingle BBS武汉劲捷电子信息站(027)3648668,3636678,3692889 (6:663/2)
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 几乎横扫所有非照排系统
远古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.
6002.16489 下载地址
Direct Download Links: KB955430 ============================ http://www.download.windowsupdate.com/msdownload/update/software/crup/2008/10/windows6.0-kb955430-x86_47e7f7bb056bf205a013c3b688725f15686736db.msu Build 16489 [KB948465] ============================== http://www.download.windowsupdate.com/msdownload/update/software/svpk/2008/10/prereqtool_033b26b3dbcf60aa698669cafe328b9c902e02a6.exe http://www.download.windowsupdate.com/msdownload/update/software/svpk/2008/10/windows6.0-kb948465-x86-express_a96b7203b8364041ca7a4ba56954f0d271e11eb5.cab http://www.download.windowsupdate.com/msdownload/update/software/svpk/2008/10/windows6.0-kb948465-x86-neutral_baba6ab4f6755a8c80b618674f6ec7a15648ea59.psf http://www.download.windowsupdate.com/msdownload/update/software/svpk/2008/10/windows6.0-kb948465-x86-en-us_b3aa612c435c67e8826dd3547aa1ac54feb5dbe1.psf
未泄露文件信息 随手一记
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文件。 ............................................................................. Windows XP SP2 RTM (xpsp2_chs_2179) ed2k://|file|win_xpsp2_chs_2179.FLiCHiNeLa.exe|299702272|10921124ae05c8b01f823f56a0cbd206|/ 简介： 经过长久的等待，终于等到了版本号为2179的Windows XP Service Pack 2，虽然今天就是8月5日了，但由于微软并没有正式公布，所以谁也不敢确定2179就是真正的RTM。 现在提供中文版本的2179下载，有兴趣试试的朋友就下载来看看吧。 如果您的WinXP是非法拷贝，请谨慎安装。 PS：（8月6日） 最新坏消息, xpsp2再次推迟, RTM将于8月6日发布, PST时间. 据传是因为2179/2180均出现错误, 具体原因自然外人是不知道的... 官方已完成xpsp2的多语言页面, RTM交付日期仍未变, PST 8月6日, 也就是中国时间推后16小时, 至少要今天晚上. Windows XP Service Pack 2 官方简体中文页面 ............................................................................. 《长角牛》(Longhorn)5060 ed2k://|file|[长角牛].longhorn_5060.rar|685441024|1966516d54bd7ff36a09a49e7c95f94d|/ 简介： 中文名: 长角牛 英文名: Longhorn 版本: 5060 制作发行: Microsoft 地区: 美国 简介: Longhorn 5060 我是从其它网站上找到的下载连接。是个RAR压缩包。(大家先暂时不要下，因为下到58.8%就没源了。对给大家带来的不便深表歉意。)
某个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.
�
- OS2BETA.ZIP [COMMENTS FROM OS2 BETA TESTERS]
OS2RPRTS.TXT
Customer Experiences
OS/2 Version 2.0
"An odd thing happened when I loaded OS/2 2.0 on my PS/2 at work. The rains
stopped. Clouds parted. The sun came out. Birds began to chirp. And yes,
I even believe I heard the sound of small, happy children playing in a park.
I was converted....... I am sold. I want OS/2..... I'm nuts about OS /2 2.0.
It's everything that IBM has promised. I find it easy, intelligent, and yes,
even fun.... Here at work, myself and the other analysts are continually
amazed at what OS/2 2.0 can do. I've been recommending it to almost every
new department I service. I love telling people what it does.... Thanks for
letting me be a part of the Early Experience." PUGET SOUND BANK IN TACOMA,
WASHINGTON - ROBERT A. PIRNIE
"I've long looked for a way to integrate my workaday computing. OS/2 is the
answer...... My day begins calling various on-line services via modem,
opening numerous documents on my word processor, and starting a DOS-based
database I use for my students grades. Before OS/2 this took quite a bit of
time. But now I have these programs set to open on startup, and my overall
productivity has increased three-fold. I can answer a student's grade
queries as I confidently print a lecture I must give, compile some utility I
wrote in C++, download from the EEP BBS, all the while backing up the
directory containing my book to a floppy disk---try that with DOS or
Windows!...... I'm not a Big Iron guy, just a dedicated theology teacher and
scholar, but OS/2 is a God-send for my productivity and for the stability of
my work environment--which is precious to me, if to no one else. OS/2 is man
made, I know, and my jaded fellow theologians may find this heresy, but day
by day OS/2 seems to me to be a flat-out miracle." SAINT JOSEPHS COLLEGE IN
RENSSELAR, INDIANA - MARK JOHNSON, ASSISTANT PROFESSOR, DEPARTMENT OF
PHILOSOPHY & RELIGION
"My job requires that I continually juggle my time between a variety of
ongoing tasks. Furthermore, I must deal with frequent interruptions to
service customer telephone calls. In the past, my PC was a less than
adequate aid in helping me accomplish these work tasks in an efficient
manner...... OS/2 2.0 has finally elevated my PC from the level of aid to
that of a true tool in my work environment. Using the WPS, I have created a
PC environment that is the ideal best of all worlds. The various programs,
system connections (multiple terminal sessions to various systems, as well as
PC servers), and other productivity tools that I need to execute on my PC,
can now be executed (automatically) as soon as I turn on my PC in the
morning. I finally am able to have hot connections to all of these
facilities simultaneously. No longer do I suffer through the syndrome of
having to terminate one facility, and initiate a new one, due to the normal
interruptions of my daily environment. I simply hide and surface the old and
new activities, respectively, all with a few simple mouse clicks on my OS/2
WPS desktop. And when I return to a precious activity, it's just as I left
it..... We are a small, service oriented company. Our small size demands
that we achieve the maximum productivity among the few employees that we
have. The desktop environment available with OS/2 2.0 will finally allow us
to obtain the productivity multiplier promises, that have so long been used
as a selling point for PCs on every desktop..... It truly is a superior
product." ALLINSON-ROSS IN GOLDEN, COLORADO - MARVIN NIPPER, PRESIDENT
"To me, only three major breakthroughs in technology equal this product;
those being the invention of the light bulb, the invention of the wheel, and
the discovery of fire. I am truly impressed! Furthermore I find this system
so convenient and uncomplicated to use that most of my time is spent fighting
my SEVEN-YEAR-OLD son for control of my computer. I feel that IBM has once
again proven that it is not only the front runner of microcomputer
technology, but also the trail blazer of times to come!" SECURITY PACIFIC
AUTOMATION COMPANY, INC. IN SEATTLE, WA - DONALD K. CHAMPINE, TECHNICAL
CONSULTANT, SPAC-NW TECHNICAL SUPPORT
"OS/2 2.0 provides the best of all worlds....Additionally, IBM has scored a
major hit in the new powerful GUI Workplace Shell..... Not only is the base
operating system stable, but the LAN Program, Host Communications, and
Database are all rock solid. OS/2 2.0 provides stability for both the
standalone user as well as a user in a complex networked environment....
OS/2 2.0 performance is better than any DOS based multitasking system I have
used..... Power users need the features of OS/2 2.0 but so do new
users...... Some words for OS/2 2.0 -- Great, Excellent, Magnificent,
Superb, Extraordinary, Impressive, Noteworthy, Outstanding, Smashing,
Wonderful, Fabulous, Fantastic, Fine, Good, Marvelous, Super, Terrific,
Tremendous, Stupendous, Amazing, Premier, Glorious, Splendid, Distinguished,
and Number one.....you've given us what I've wanted for years.... Thank you
IBM." MISSOURI HIGHWAY & TRANSPORTATION DEPARTMENT - BOB HITT, PROGRAMMER
ANALYST
"OS/2 2.0 is for both the power user and the average user. In fact, I
suspect we will see a new breed of power users. These people will be able to
harness the power of their machines because OS/2 makes it easy. One does not
need to spend hours poring over manuals. You simply do what you want.
Quickly, they will be just as capable as today's power users. That is one of
the beauties of OS/2, making the today's power available to today's user.....
Perhaps it is unfair to compare Windows 3.0, a fully released product, to
OS/2 2.0, a beta still a month and a half away from general availability, but
I must say that under OS/2 I am able to get more done faster and more
reliably than I was ever able to under Windows. Ironic, isn't it? I can't
wait for general availability!" UNIVERSITY OF CALIFORNIA IN SANTA BARBARA,
CA - KEVIN W. LAIRD, MICROSYSTEMS GROUP COORDINATOR
"I think OS/2 is a real winner even for single workstations....the real
reason is that it's simply more productive.... True preemptive multitasking
is wonderful....and formatting disks, downloading or faxing in the background
really saves time.... I think one reason this product has improved so
dramatically is that IBM listened carefully to it's customers....... it's a
phenomenal product. I'm happy to say that your performance claims are real,
not just hype. The improved DOS & Windows support is ABSOLUTELY PHENOMENAL!
Your team has done a first rate customer-oriented job developing this
product. We are delighted with it's capabilities. I wanted to let you know
how much we appreciate the leadership role IBM has taken with this new OS/2.
Keep up the good work." MAYER BRYSON INVESTMENTS IN SAN FRANCISCO - ROBERT
MAYER, PRESIDENT
"The PC had a glorious birth, followed by some trying formulative years, but
now I see the PC on the edge of taking it's place as a productive member of
the DP society. I believe that OS/2 will make the PC the premier member of
this future DP Society..... OS/2 is finally moving the PC into a mature stage
of life....... When we evaluate a product (application software) the
evaluation can be solely based on the business need rather than limited by
the operating platform." MASS MUTUAL INSURANCE COMPANY - DENNIS AIROLDI
"It's like having a graphics workstation built into a mainframe as friendly
as a Macintosh.... With OS/2 and the Workplace Shell, we can, for the first
time, deliver the mainframe processing power and connectivity needed for our
complex applications with the flexibility and ease of use of a fourth
generation GUI....... OS/2 and the Workplace Shell gives our complex software
the processing power our users demand, combined with the ease of use needed
for first time users..... The Shell....far surpasses the Windows environment
(a DOS Extender) and other GUIs in performance/price, ease of integration,
utility, and program-manipulating and executing power." MANUFACTURING
INTEGRATED SYSTEMS, AN INDEPENDENT SOFTWARE VENDOR USING OS/2 2.0 FOR
MANUFACTURING APPLICATIONS - NORM HARRIS, PRESIDENT, (SAN YNEZ, CA)
"OS/2 2.0 has great affinity with my large system background. For example, I
appreciate the 4K demand paging, multi-threading, CUA compliance, and other
features that I first became acquainted with in the large systems
environment. Having struggled to obtain connectivity to both 5250 and 3270
hosts in the same DOS machine, I truly appreciate OS/2s ability to
communicate...... What do I run on my machine? Has OS/2 2.0 displaced MS
DOS and Windows as my operating environment? ABSOLUTELY!" DRESSER RAND IN
PAINTED POST NY -JAMES R. SMITH, SR. SYSTEMS PROGRAMMER
"OS/2 Version 2.0 is exactly what I need to perform my job, an industrial
strength personal computer operating system. In five months of heavy daily
use I have not experienced a single operating system crash..... In the final
analysis when you're finished playing games and ready to get to work, OS/2
version 2.0 is the product for you." LUCKY STORES IN DUBLIN, CA - BOB
GAUTHIER
"OS/2 has finally surpassed my expectations.... OS/2 definitely proved to me
that it is better Windows than Windows! I would not have believed it if I
had not experienced it myself!!! IBM has convinced me that if anything has
been done right, it is OS/2!" VAN WILLIAMS, ADVANCED TECHNOLOGY RESEARCHER
IN SAN ANTONIO TX
"OS/2 simply revolutionizes the desktop.... Designing and developing
applications for OS/2 is a dream come true. The machine works for the
developer now rather than being a recalcitrant hunk of iron to be man-handled
through it's paces." TEXAS INSTRUMENTS IN PLANO TX - RICHARD BROOKS,
OPERATOR WORKSTATION DEVELOPER
"I am looking forward to moving everyone to OS/2 just as quickly as possible
since it runs all of our applications while giving them full resource
availability and protecting them from interfering with each other. From the
support perspective, this is a dream come true. Instead of five
environments, I can see the day rapidly approaching when I'll only have to
support and train in one - OS/2..... The stability and reliability of the
platform means that I will get fewer service calls and increased client
satisfaction..... With OS/2 safe multitasking has finally arrived allowing
me to recover machine power that would otherwise have been wasted..... With
all of the applets that come with OS/2, a person can actually do productive
work without purchasing other products." CAJUN ELECTRIC POWER IN BATON ROUGE
- DON BABCOCK
"Multiple sessions is an absolute must in my job, and I can print mainframe
reports in the background!!!!.... Running OS/2 2.0 at work, at home, at the
unit, in a tent under fire, out on the runway, in a foxhole.....
anywhere...... everywhere!!!!!!!! What sets me apart from others is that I
am elated about OS/2 from maybe a different point of view from the rest, I am
a user!" MARC C. JONES AT CAJUN ELECTRIC POWER IN BATON ROUGE
"You have already proven to be a better Windows than Windows!..... I
consider myself a winner being in on the testing of the Operating System of
the '90's - OS/2 2.0" WASHINGTON PUBLIC POWER SUPPLY SYSTEM IN RICHLAND
WASHINGTON - PAT MURPHY
"OS/2 2.0 to a PC user is what a ratchet is to a mechanic. How did we ever
get along without it...?" TARGET STORES IN MINNEAPOLIS - CRAIG ANDERSON ,
MANAGER, END USER COMPUTING
"The years of waiting for the right operating system are over. Furthermore
our professionals can use PCs in their area of expertise without having to
become experts in the underlying operating system because of the friendly
interface known as the Workplace Shell! Power and Productivity without the
frustration PC users have known until now....hats off to IBM!" NORTHWEST
PIPELINE CORPORATION IN SALT LAKE CITY - LEE TORNOW, STAFF ANALYST
INFORMATION SYSTEMS
"The actual installation was completely painless and a pleasant surprise....
It is reassuring to know that I will not have to abandon existing software
when we migrate to a new operating system..... Cutting and pasting between
DOS application windows will allow the creating of new reports and visual
presentation aids...... I will be running V 2.0 on my home system as well as
in the office because once you get accustomed to the power and versatility in
one environment, it's hard to go back to something less at home." LOCKHEED
SPACE OPERATIONS IN TITUSVILLE, FLORIDA - RICHARD CLINTON NETWORK
ADMINISTRATOR
"Sort of like a good book, you just can't put it down or stay away from
it........ The use of preemptive multitasking along with the memory
protection provided by OS/2 makes those UAE's (Unrecoverable Application
Errors) nearly a thing of the past. However if it does occur, simply close
and then reopen the application. All other programs running on the system
are unaffected..... The system performs several operations, overlapping many
of the longer running functions without any fuss or muss on your part.....
The Workplace Shell (WPS) is the hottest thing to come down the PC pipeline
since the original PC.... OS/2 also includes a collection of bells and
whistles IBM call applets.... OS/2 2.0 has more applications available for
it (not tomorrow, not next week, but today) than any operating system in
history. It can run your DOS, Windows, and OS/2 applications
unmodified...... A today's operating system for today's hardware, that's
IBM's OS/2 Version 2.0" SHERRILL FURNITURE COMPANY IN HICKORY NC - DAVID
ELLER
"Any application plus OS/2 plus any machine should equal productivity. I
believe the Workplace Shell is one of the smartest features of OS/2."
AMERICAN AIRLINES IN TULSA OKLAHOMA - DENNIS P HAYES, SR. EDP SYSTEMS
ENGINEER
"OS/2 lets you do what YOU want to, because it does what you want!" CHASE
MANHATTAN BANK IN NEW YORK - DAVID GROSS, STAFF CONSULTANT
"OS/2 2.0 allows us to more effectively utilize our existing hardware by
supporting the simultaneous execution of OS/2 1.3, Windows, and DOS
applications on a single PC...... My 9 year old son messed around with
OS/2...and five minutes later I came back downstairs to find him changing
screen colors, moving folders, playing games, and working with various
applications that come with the system." AN OS /2 APPLICATION DEVELOPER -
WAYNE HOLMES IN BELLEVUE, WASHINGTON
"OS/2 is a truly empowering operating system for application developers. It
easily supplants AIX as the ideal development platform.... OS/2 is a
mainframe on the desktop..... While the advanced hardware has been there for
some time, it took OS/2 to finally make the promise of mainframes on the
desktop come true.... Whether you are a developer, a systems integrator, a
big iron MIS Professional, or an end user, OS/2 is the operating system of
choice for the desktop...and it's a lot of fun too. I'm having the time of
my life." HILBERT COMPUTING IN OLATHE, KANSAS - GARY MURPHY, SR. PROGRAMMER
"At home my 12 year old daughter finds no difficulty installing her game
software and using the system for recreation...... The system is a
programmer's dream.... OS/2 shines in the support area.... One technical
support staff person can support many technical workstations because of the
workplace shell and networking software installations. No other product can
make that claim. It is truly a open software..... OS/2 is affordable,
maintainable, and powerful. I do not believe it will have a competitor for a
long time to come. It is better business to use it to develop new user
applications than to redevelop it." ASHLAND OIL IN ASHLAND KY. - CHARLES
DUCK, PROJECT DIRECTOR OPERATIONS PLANNING
"OS/2 allows the marriage of tools that were better left divorced from one
another." BLUE CROSS & BLUE SHIELD IN CHICAGO - JONATHON HANDLER, SR.
CONSULTANT
"The reason I like OS/2 is simple. I get more work done when I use it....and
that's why I bought a computer in the first place." NATIONWIDE INSURANCE IN
CARROLL, OHIO - TERRANCE CROW.
"With the new folders, I can very easily arrange my computer work in a way
that is very convenient for me.... The Drag & Drop concept is also a real
time-saver. With it, doing things like discarding old items becomes
trivial.... The Workplace shell certainly gives me new freedoms to do things
the way I like, thus improving my work. The ability to run any software I
need gives me a real performance boost." TEXACO IN HOUSTON TEXAS - JIM
WILLIS, INFORMATION TECHNOLOGY DEPARTMENT
"Maximum Flexibility - that's OS/2 2.0..... Flexibility no other operating
system can provide. OS/2 2.0 has significantly improved my personal
productivity and flexibility." MCKESSON CORPORATION IN RANCHO CORDOVA, CA -
BUS S. SWINE, DIRECTOR, DATA CENTER SERVICES
"Mere mortals don't have the words to describe how impressed I am with what
OS/2 2.0 can do for me.... still to me the best part of all is the way the
Workplace shell ties it all together. The power of the new shell is amazing.
By changing the way I look at the system I am now much more efficient at what
I do... dragging and dropping confounds my co-workers who are used to the
endless sequence of keystrokes used for deleting, printing, and just about
everything else.... I must admit, though, that I did have to give up a lot.
A lot of frustration; a lot of headaches; and a lot of lost time that
is!..... The Windows-OS/2 battle from a technical standpoint was over long
ago and Windows never stood a chance." LEONARD'S METALS IN ST. CHARLES, MO -
DAVID BLAIR, PROGRAMMER, NETWORK SYSTEMS ADMINISTRATOR, CONNECTIVITY
SPECIALIST
"...and those from the land of Boca delivered on their promise and the child
was christened OS/2 2.0, and it was good!..... Freedom of choice is the
hallmark of OS/2..... OS/2 raises your level of expectation and fulfills
that expectation. This is the standard against which all operating systems
will be judged, and this is a very tough act to follow because users are
finding quietly, unobtrusively, OS/2 opens the doors to vistas that you've
only been able to dream of through Windows." PHILLIPS 66 IN BARTLESVILLE,
OKLAHOMA - BOB WESNESKI, ANALYST & POET
"OS/2 2.0's ability to multitask DOS applications, Microsoft Windows 3.0, and
all OS/2 applications in a protected environment is an incredible boon to my
productivity...... You can install OS/2 2.0 and begin work immediately.....
Workplace Shell is a new, extremely easy and powerful object-oriented
desktop... After using the Workplace shell for a while, I find the Macintosh
OS kind of klunky.... There is no equivalent on any other system.... I
finally have access to a stable, fast operating system that has tremendous
potential to carry me into the 21st century and beyond...... I currently
have OS/2 running on a non-IBM machine, and I haven't had a single problem
with incompatibility.....I know what operating system will be on ALL my
machines, and it's OS/2 2.0." SECURE MICRO SYSTEMS IN LAFAYETTE IN - GARRY
ADKINS, PRESIDENT & OWNER
"OS/2 can help! OS/2 can help! OS/2 can help! It does not matter what
business you are in or whether or not you are new in business.... It
WORKS!!!!! IBM and OS/2 are going to make my next professional 15 years the
best of my life in whatever environment I find myself..... It will be the
standard operating system for all of our personal computers worldwide. I
know that my company's investment in computer hardware and software are
secure now that IBM OS/2 is on the job.... Future developments in the
Ultimedia (Multimedia) market prove the value of OS/2 as the most viable
personal computer operating system to ever hit the market. The ability to
use touch screen technology in conjunction with audio visual systems for the
purpose of person-to-person communications in manufacturing and educational
environments can only help America regain her economic leadership
status....... IBM and OS/2 2.0 are America's best business partners and are
helping to make our best resource, our people, more productive!" TITLEIST &
FOOT JOY WORLDWIDE IN NEW BEDFORD, MA. - CARL S. NORMAN, SUPERVISOR, END
USER SERVICES.
"I would like to share my enthusiasm over your new product: OS/2 V 2.0. I am
currently going to college, and it is an excellent tool. It is a vast
improvement over any DOS version (I own 5.0) and while it makes the desktop
appear similar to Apple's MAC it is superior because it is compatible with
several different formats of applications and is a true multi-tasking
system.... OS/2 is also a much stable platform than Windows..... I also
won't have to listen to Mac users talk about how unfriendly IBM's are (GUIs).
I like mine just fine with OS/2 V 2.0." CHRIS NOLEN, COLLEGE STUDENT
"The OS/2 2.0 Workplace Shell's object-oriented environment makes the
computer desktop intuitive and flexible. It is a greater leap from 1.X than
1.X was from DOS..... The addition of multitasking DOS and Windows
applications makes 2.0 the most powerful desktop operating system ever ---by
far." JOEL POOLE IN CORTE MADERA, CA
"I was looking forward to the convenience of integrating the running of OS/2,
DOS, and Windows programs. This feature turned out to be great - better than
I had hoped. But it was OS/2's full use of extended memory which changed my
way of doing things. I feel like I've grown an extra pair of hands..... The
primary reason for my surprise at the way OS/2 has transformed office routine
into office dynamic is the manner in which mutitasking saves time; and this
must be experienced to be completely assessed. The result is phenomenal! So
what you are offering here is, among many other good things, the
computational equivalent of open stacks in the library, the sine qua non of
Search & Discover..." CHANDO ENTERPRISES IN COLUMBIA, MD - WM A. DONNELLY,
PH.D ANALYST
"The Workplace Shell certainly enables a sophisticated, function-rich
operating system, for use by many a user, whether they are computer people or
not.... The new OS/2 has the potential to become the development platform
for many a mainframe shop, at a substantial cost savings in cost per CPU
cycle. It will also improve the efficiency of the programming staffs and of
migrating code to larger platforms because of it's thirty two bit
architecture.... The new OS/2 removes any reason any one might have to go to
Windows. It also removes any excuse any one might have for staying with DOS
because anything else is too sophisticated.... The SAA features of OS/2 2.0
make it a connectivity platform for anyone needing to participate in a
mainframe dominated environment.... In conclusion, OS /2 2.0 has something
to offer the largest segment of users since the first coming of DOS." FORD
MOTOR IN LORAIN ASSEMBLY PLANT - NEIL PATTERSON, CIM COORDINATOR AT LORAIN
ASSEMBLY.
"The technology used to integrate these environments (DOS, Windows and the
Workplace Shell) is very impressive." STATE FARM INSURANCE IN BLOOMINGTON,
IL - JIM BETHMANN, SR. ANALYST FOR DP OFFICE SERVICES
"Basic Services installs easily as was promised. Great job!..... I'm
convinced that EVERY DOS PROGRAM out there can run..... OS/2 V. 2.0
certainly runs the widest base of PC applications of any PC operating
system..... I was on the team that reviewed PC operating systems to
determine which would be the operating system(s) that we would recommend in
Texaco LA/WA. The one we picked was OS/2 Version 2.0." TEXACO IN CORAL
GABLES, FLORIDA - CARL HERRERA, SYSTEMS ANALYST
"OS/2.... It's the greatest! I just wanted to express my enthusiasm for the
significant improvements in OS/2.... I believe this is truly the operating
system of the future--almost all things for all users!" UCAR EMULSION SYSTEMS
IN CARY, NC. - B.F. COLE
"As a programmer, I love being able to run a compiler in the background while
editing a file in the foreground." ALAN LAU, AN INDEPENDENT PROGRAMMER IN
WINDSOR CT
Object Oriented Interface
Plenty of Power
Excellent Development Platform
Robust API Services
All in One Solution
True Multitasking
Intuitive Help
No more segmentation
Great Flexibility
Sound Investment
Yours for the asking
Simplified Set Up
Truly Mature
Extraordinary Support
Most Reliable
Operating
System Around
/
2 good to be true!
THE TRAVELERS INSURANCE IN HARTFORD, CT - RON CALEBRESE, TECHNICAL DIRECTOR,
COMPUTER SCIENCE
"Thank you for following through on a promise to create what I believe will
be the small systems operating system of the future.... I have found that
IBM is delivering much more that was originally expected. The look and feel
of the new graphical interface is a pleasure to work with, and extremely easy
to use and understand. I am very pleased with all of the drag and drop
features that have been added and look forward to being able to use some of
the other newer features such as tear off menus. As a developer of software,
I can appreciate the effort that has been put into this project. It appears
to me that many of the best things out in the marketplace have been
incorporated into this environment and as a result, a most exciting product
has emerged. Even the installation process is to be commended.... Some of
the aspects of the environment that I was most impressed with were the speed
of the system once loaded, and the amount of work that was done to get the
Windows interface to run it's applications flawlessly and with great
speed.... This new 32 bit version takes the cake." DUN & BRADSTREET
CORPORATION IN PARSIPPANY NJ - ANTHONY PALASCIANO, SR. SYSTEMS ANALYST
"OS/2 is definitely for me and for you! We have had OS/2 in production since
Version 1.2 with tremendous success...... OS/2 2.0 is also the reason for
many support/development groups to centrally focus efforts to deploy common
services.... IBM enterprises can now expand to the desktop without fear of
disabling user productivity. The magnitude of this expansion can not be
covered entirely here. OS/2 2.0 is bringing added dimension to enterprise
computing.... Yes, I'm impressed! " USAA IN SAN ANTONIO, TEXAS - JOHN R.
MIRANDA, SR. SYSTEMS PROGRAMMER, COOPERATIVE PROCESSING
"OS/2 Version 2.0 is great! The level of functionality and versatility built
into this product is incredible.... OS/2 is a great value. Of course, OS/2
runs DOS and Windows software. But, it goes well beyond them by providing a
level of reliability and fault isolation unmatched by either of those
environments on their own..... This is really a bargain, OS/2 is an
incredible value!!! OS/2 is also a platform for improving productivity...a
user can manage the entities inhabiting his or her computer in a more natural
and intuitive way..... The WPS goes beyond that by allowing a user to
directly manipulate those beasties in the box in a consistent manner..... I
congratulate IBM on being bold enough to provide a major enhancement over the
standard GUI.... One aspect of OS/2 which hasn't been discussed much is how
easy OS/2 is to administer and run. There is a good deal of tinkering that
has to be done to use many of the DOS tools that expand the standard DOS
environment; for example, PIF tuning files may have to be established and
areas of memory usually have to be carefully managed for those tools to
work.... These problems melt away with OS/2. I also hope people realize
that, in all the talk about OS/2 and how it represents the new IBM, it also
represents one of the most admirable traits of the old IBM. IBM has always
been a company with integrity, it hasn't reneged on promises made to it's
customers...... OS/2 in all its versions continues that tradition..... a
user's original software investment is protected while also providing
considerably advanced functionality in the overall system.... Good luck on
the roll out of OS/2. I'll be using it here and pushing for its success where
I can... " PAUL FIRGENS IN WHITE PLAINS
"OS/2 2.0 is head and shoulders above anything PC users have seen to date.
OS/2's power yields a simplicity that is unheard of. PC users have never had
it this easy. I really feel that as soon as the computing public learns how
easy OS/2 is to use and how many of the nightmares of DOS it eliminates, the
demand for OS/2 and OS/2 applications will go through the roof.... OS/2
frees you to concentrate on using our computers rather than fighting with
them to get the job done. Personal Computer users no longer have to worry
about whether a program is for DOS, Windows, or OS/2. You simply install it
and run it. Nothing could be easier than that." PETER NORLOFF IN FAIRFAX,
VA
"I think OS/2 2.0 is a fantastic product with a very bright future....
Workplace shell has resolved the conflict (speed vs. quality) between pretty
and productive.....it makes my VGA screen seem to have better resolution than
before, and the speed is excellent.... OS/2 2.0 does an excellent job of
performing several background tasks while providing superb responsiveness to
the task at hand.... Not just having several applications open at once, but
actually having them all work productively without a performance impact. I
finally feel that my computer system is being used to it's fullest
potential.... I believe that IBM's MVS has been the most reliable operating
system in the world for many years, and now the PC industry will benefit from
IBM's vast experience in virtual memory and protected operating systems with
OS/2 2.0.... One of the most important features of OS/2 2.0 is that it
protects users investment in hardware, software, and training.... OS/2 is
running flawlessly on a wide variety of systems.... I don't have to buy any
new applications in order to start taking immediate advantage of many of the
benefits of OS /2 2.0. I can gradually migrate to native OS/2 applications at
my own pace as new versions and features warrant. The protection of my
investment in application programs and of my knowledge of using them allows a
smooth transition to a more powerful operating system.... I can safely run
several of my existing DOS & Windows programs simultaneously without any
interference between them. No more fighting with limited memory for TSR
(terminate and stay resident) programs either. I simply run each in it's own
DOS window!......and I can cut and paste data between DOS, Windows, and OS/2
programs easily. I'm glad that this manual memory management is a thing of
the past..... OS/2 2.0 is definitely a better DOS than DOS, and a better
Windows than Windows.... All in all IBM has ensured that users can upgrade
to OS/2 2.0 with a minimum of cost and pain that so often accompanies
significant changes in software.... I was especially pleased to find that I
could upgrade an old copy of PC DOS to OS/2 1.3 for $99...that in itself was
an outstanding value. Best of all, IBM will give me a free upgrade to
version 2.0 when it becomes generally available! I have to say that this is
absolutely the best software value I've ever seen! I have seen the future of
desktop computing, and it is OS/2." UNIVERSITY OF MICHIGAN HOSPITALS IN ANN
ARBOR, MI - EUGENE T. MANGUM, SYSTEMS PROGRAMMER AT TAUBMAN CENTER
"After using OS/2 for the last four months I feel very confident that OS/2
2.0 will be a major success for IBM and a substantial advance for
productivity for workstation users.... OS/2 2.0 is proving to be a well
crafted and a well designed operating system.... Especially noteworthy is the
dynamic data exchange feature between programs running in Microsoft Windows
and OS/2.... I am looking forward to rolling out the general availability of
OS/2 2.0 to both our system developers and end user communities." BLUE CROSS
& BLUE SHIELD IN JACKSONVILLE - FLORIDA OTIS J. GARBER, SYSTEMS DEVELOPMENT
PROJECT MANAGER
"Users finally get what they have been asking for.... So far with very
little tuning I am able to run the following programs simultaneously:
DOS-Professional Write 2.22, DOS-PC Tools 6.0 Desktop, DOS-Harvard Graphics,
OS/2-Communications Manager for 3270 session, 3270 print control,
Windows-Lotus 123 for Windows. I know that whatever the scenario a user
brings to the table OS/2 2.0 will solve it." LUTHERAN HOSPITAL IN FORT WAYNE,
IN - BRETT TAYLOR, NETWORK ADMINISTRATOR
"OS/2 was designed with business in mind.... with it's enhanced DOS
compatibility, OS/2 offers us a migration path which protects our heavy
investment in DOS software while giving us the additional capacity we need to
support future growth on our branch workstations.... IBM has taken a major
step in fulfilling the strategic plan mapped out in 1987 for Operating
System/2. I would encourage business users who have not seen OS/2 in a while
to take another look." NATIONS BANK IN NORFOLK, VA - FRED JACOBS, LEAD
SYSTEMS ANALYST
"Anyone who isn't excited about OS/2 V. 2.0 either hasn't seen it or they
simply aren't big enough to admit they were wrong. You've done it again
IBM!" TEXAS TECH UNIVERSITY IN LUBBOCK, TX - DONNA CHAFIN, ADMINISTRATIVE
INFORMATION SYSTEMS
"I write to you now as a last resort. You see, I have lost my boyfriend to
OS/2. For the last two weeks he has been locked in the computer room as if he
was a mad scientist on the verge of a momentous discovery. I knock, I pound,
I whimper into the keyhole, I slide notes under the door; all to no avail....
I could hear him cackling with glee and often I heard awe in his voice that
sounded as if he were witnessing the second coming.... I must go in after
him. Clearly this man of mine cannot help himself. The temptation of OS/2
is too great. He is hooked and I am the only chance he has left.... If you
can't beat em, join em! letter from the boyfriend: I became convinced only
when OS/2 2.0 was demonstrated with ENTHUSIASM, by IBM. Because of this I
cannot help but demonstrate OS/2 2.0, with ENTHUSIASM, to others. You have
succeeded!
You have given me something that I did not possess before: a choice, and a
chance to be better." UNIVERSITY OF CA AT BERKELEY, L CHRISTIAN CANDELMIRE
AND JOHN SCHULBERT
"The King is dead, long live the King!... It has been said throughout
history and it shall be said again...this time OS/2 is King. After 10 years
the PC has finally arrived. IBM has drawn another sharp dividing line in the
history of personal computing with OS/2 2.0. An operating system that works
with me - not against me. An operating system that lets me fully realize the
personal in personal computer. An operating system that lets me use the
strengths of the mainframe while utilizing the flexibility and the power of
the PC..... Finally, let me paraphrase from an old review by Robert Schumann
in reference to a little known composer of the day named Frederick Chopin:
Hats off Ladies and Gentlemen, a winner! Just as Chopin forever changed the
way people would play, listen, and compose music for the piano, OS/2 2.0 will
forever change the way people use and interact with a PC." INFORMATION
RETRIEVAL COMPANIES, INC.
"Without OS/2 2.0, I frequently found myself interrupting one PC application
to start up another. Often I had to reboot the machine to get a different
configuration to match a specific application's need. No more! Those days
are over, OS/2 can do it all.... No more wasted time saving files and
retrieving files. No more stopping and starting applications. No more
telling people: I can't do it right now, come back later. I can just
smoothly transition my PC along with my thinking from one task to another. I
can do my own job better and faster.... OS/2 has fulfilled it's promise. It
truly handles multiple applications in multiple environments and does it
well. OS/2, Windows, DOS ---OS/2 can do it all!" LOYOLA UNIVERSITY IN
CHICAGO - WALTER M. SLAZYK, LEAD SYSTEMS PROGRAMMER
"The idea of packaging OS/2 2.0 with all the tools necessary to do everything
from spreadsheet analysis to personal time management is a big incentive
where time and money is concerned..... Some people may not use two programs
at the same time but once they see what can be accomplished with multitasking
from within a single program I doubt they will see an advantage to DOS
afterwards.... I believe that OS/2 2.0 is a strong robust operating system
that does not only need to installed on file servers or the highest power
computers that corporate America has. The home computer is becoming 32 bit
and with the utilities, games, and editors that are available under OS/2 2.0
the home user could easily take advantage of the installed features. The
information age is upon us and OS/2 2.0 is a strong base upon which to
build." UNIVERSITY OF CA AT SANTA BARBARA - BRUCE WALLACE, DEVELOPMENT
ENGINEER
"Workplace Shell is fabulous. I'm constantly amazed at the number of
powerful, easy to use features you've incorporated.... I also think your
implementation of DOS and Windows is excellent. Both are fast, stable and
complete. Windows applications work great and DOS applications definitely
run better on OS/2 than on Windows.... I think IBM has got a winner here.
2.0 is fast, stable, flexible and easy to use. It runs great on my 1988 16
MHz clone despite the old BIOS. And you've incorporated a lot of good
customer suggestions. I'm definitely sold. Keep up the good work!" MAYER
BRYSON INVESTMENTS IN SAN FRANCISCO - ROBERT MAYER, PRESIDENT.
"The freedom provided by being able to pop open a new session, grab the
needed information and act upon it without disturbing my previous work is
invaluable. With OS/2 2.0 it does not matter if the data is on my local hard
disk, on the mainframe, or on one of our UNIX servers... OS/2 2.0 truly
integrates all of these disparate information sources into the PC on my
desktop.... No more wasted time getting in and out of applications. No more
worries about the system crashing when one more application is loaded.
Office visits are shorter, more productive and spawn fewer drop by later, I
can't get to that now results. Overall it's just a better way to work."
DAVID MATOCHA IN RICHMOND, TX
"I have to say that it (OS/2 2.0) is the only serious multitasking operating
system choice for desktop. The new Workplace Shell is powerful and
configurable, and icons stay where you put them. The system runs DOS better
than DOS itself, allows for fast 32 bit programs and even runs uncooperative
DOS shells (such as Windows) with no problem. I can leave my workstation on
for days without rebooting, and can debug large programs using DOS protected
mode interface. Nothing else even comes close. It's a real operating system
for everybody, not just servers, as some have claimed, and not just users who
have only perfect applications, as all the task switching DOS shells
require.... Thanks for sticking with OS/2 and with all of us who believe in
it." MICRO MAGIC SYSTEMS IN BOLIVAR, MO - JERRY L. MCKITTRICK, SR. SYSTEMS
PROGRAMMER
"The workplace shell ends the frustration of PC users who feel helpless with
technology. After a short introduction to the environment, a few examples of
the context sensitive help feature, and the simplified logic of the workplace
shell, I am certain empowered users are right around the corner. I am
actually looking forward to introducing people to a streamlined version of
the already powerful desktop.... The icing on the cake for your product (is
that) the documentation is clear and concise. You have made OS/2 2.0
accessible to people that are not techies. The casual home user market will
love it's simplicity and it makes it an all-around great and well thought-out
product.... Everything to gain and nothing to lose. I thought there was no
such thing as a free lunch. I do not know how you did it but I want to thank
you for the revolution of the PC world. I guess if you want something done
right you have to do it yourself. Now all you need to do is let everyone
know, then they will feel the same way as I do - I can't live without it!"
CIGNA INSURANCE IN HARTFORD, CT - CHRISTINE MONARCHIE, LAN ADMINISTRATOR
"OS/2 2.0 is a fantastic product and a much needed tool for knowledge workers
everywhere.... The Workplace Shell is exceptional.... OS/2 provides real
value.... A few more pluses for OS/2 2.0: the product documentation, both
online and hardcopy is superb....includes a 3 frame Super person cartoon
depicting OS/2 2.0 vs. Windows Unrecoverable Application Error." CIGNA
INSURANCE, BLOOMFIELD, CT - DAVID A. PINARD, LEAD SYSTEMS DESIGNER
"Compared to the dedicated single user software products that have become so
popular under Windows, major new enterprise applications will all require an
entirely new level of operating system support.... Multithreading is a key
OS/2 feature, and one that may impress more than a few individual users
because it increases the performance of application software..... The most
likeable feature of OS/2 2.0 for the individual user is the ability to keep
what that user has now (DOS with Windows) while adding some new benefits,
such as performance, and the ability to try some new OS/2 specific software.
Gain without taking a loss...easy to accept. OS/2 is perceived as a
potential cure to many ills that exist in the DOS Windows third party
communications and database software solutions being attempted today.... I
would like to suggest that you fight to characterize OS/2 as more than just a
better DOS than DOS, etc. Rather this is really a new generation operating
system that goes far beyond DOS. It is like the automobile compared to the
horse and buggy. They both get you there, but can you really compare them?
Although when the automobile first came out there were no interstate
highways, there are today. And we all know the value of the automobile.
OS/2 is for the computing equivalent of the interstate highway. We can't
live without it, but that vision has not occurred to everyone." CITIBANK
(PRIVATE BANK DIVISION) IN VALHALLA, NY - DAVID H. JANSON
"In a nutshell, it is Great! Flexibility that will be available for support
and testing functions by being able to boot different configurations of DOS
Windows concurrently......of great importance is the ability to have an
advanced level LAN Server with a Ring O Implementation. That ability with
the new cache optimization of 386HPFS and the ability to create layers of
administrators with specific function really will give your network operating
system some of the enhancements that have been severely lacking..... Most
everyone who walks by and sees my desktop becomes very interested in when
they can have this release on their machines." GULF STATES UTILITIES COMPANY
IN OCAUMONI, TX - DR. KAREN S. MCCONNELL, SCD., LAN TECHNICAL COORDINATOR
"When asked what my impressions are with OS/2 2.0 I would have to say three
things: Power, Reliability, and Support.... People now have choices...
Choices in not only what people may run, but also how they run. At last,
there is an operating system in which power complements flexibility....
Never have I been in a program in which the company was so concerned about
the product, not the release date. Never have I been in a program that was
designed to enhance and evolve as opposed to patch and move on. Support does
not just come after a product is released; it should start as soon as it is
designed. Intuitive interfaces (such as the WPS), compatibility with
existing standards (DOS, Windows, etc.) and knowledgeable help desk staff all
contribute to a well supported product. IBM's OS/2 2.0 has all of these
features and more with a complement of services such as Prodigy, IBM Link,
National Support, and those great SEs..... OS/2 2.0 is not an operating
system of exceptions; it is an exceptional operating system. Power,
Reliability, and Support---I say Push the Power! Thank you for an operating
system well done. " CA POLITECH STATE UNIVERSITY IN SAN LUIS OBISPO, CA -
DAVID B, MASON, ASSISTANT SYSTEMS ANALYST
"It was amazing to see IBMCAD, several host login sessions, X-Windows, and a
couple of PC DOS prompts all running at the same time.... It was a pleasant
surprise to find that nearly every DOS application I use works under OS/2
without any fuss. The Windows applications I tried under OS/2 worked without
a hitch and ran as fast as they would under Microsoft Windows. Even though
this is beta code, performance is quite good. In particular, switching
between multiple DOS applications is much faster under OS/2 than with
Microsoft Windows.... I finally realized I was hooked on OS/2 when I went
back to PC-DOS and found myself saying, 'If I only had OS/2 I could open
another DOS session and...' or '...if I had OS/2 running I could open a
window to the RS/6000 or DEC VAX and....' Congratulations on a fine product.
It has the potential to make the personal computer platform more usable than
ever." SMITH METER, INC. (A MOORCO CO.) IN ERIE, PA - BRAD HARRISON, SYSTEMS
SOFTWARE ADMINISTRATOR
"In my opinion IBM has successfully and aggressively addressed every issue
concerning the operating environment choice. It is competitively priced,
runs 32-bit applications, it can also run DOS, Windows, and existing OS/2
programs. It is fault-tolerant, and the only true multitasking environment
on the market. I have seen no other product that can make those claims. In
my opinion, I would have to say IBM has lived up to their promise of offering
a better DOS than DOS, better Windows than Windows, and yes, believe it or
not, a better OS/2 than OS/2." WILLIAM STEPHENS IN SAN ANTONIO, TX.
"There comes a time when a company should get excited about a new product
that it has created. Well, OS/2 2.0 is the product and 1992 will be the year
to be remembered. IBM and OS/2 will the standard of the computer industry,
the same as DOS was when it was introduced to personal computers many years
ago.... OS/2 is a true state of the art technology and nothing like it exists
on the market today. Anyone who is planning to purchase an operating system
should, without hesitation, make OS/2 a viable solution to their computer
needs. OS/2 has the power and flexibility to fit into any environment from
the base operating system to connectivity to a mainframe. The platforms that
it crosses with transparency are unbelievable. I can't imagine what would be
next from IBM." CITY OF RICHMOND, PUBLIC SAFETY DEPARTMENT IN RICHMOND, VA -
PATROLMAN BRIAN KATZ, NETWORK ADMINISTRATOR
"I refuse to read lengthy documentation - I installed OS/2 along with Windows
and Communications Manager without reading a single book --no kidding--the
on-line documentation is all you need! ...best of all, I could finally
utilize the big model 57PC I bought, running multiple applications
concurrently, DOS, OS/2, and Windows together --- I deleted DOS and haven't
used it since!" STAR BANC CORPORATION IN CINCINNATI, OHIO - ROBERT W.
ELBERFELD, VICE PRESIDENT, SERVICES.
"Since installing OS/2, I have been able to significantly increase my
productivity by taking advantage of the multitasking and multithreading
capabilities of this new operating system technology. The transition from
the 'other guys' operating system to OS/2 was a very smooth and cost
effective because OS/2 allowed me to continue to run applications which were
designed to run in the 'other guys' operating system... I have already made
the choice to use OS/2. OS/2 gives me the necessary platform to conduct the
work which needs to be done today and also gives me room to grow in the
future. Release your computers processing potential, free your machine,
embrace the future today with the operating system which will grow with you.
OS/2 breaks the rules and makes up new ones." MICHIGAN CONSOLIDATED GAS -
ROGER G. VINCENT
"We expect our applications to run on a variety of hardware and software
platforms. I am very impressed with the overall function of OS/2 2.0. The
support of the DOS and Windows environments is also very good, almost every
one of the programs running under those systems came up immediately. My
overall impression with OS/2 2.0 is excellent. It is a good product with
several very nice features. I would recommend it without reservation."
FROSYTH MEMORIAL HOSPITAL IN WINSTON SALEM, NC. - KENNETH WISEMAN,
APPLICATIONS MANAGER
"Once you let go of past systems and begin to concentrate on what you wish to
accomplish and not on how to do it, the beauty of the Workplace Shell begins
to show through.... The multitasking performance of OS/2 2.0 is excellent...
The multitasking capabilities of OS/2 allows a person to work with their PC
in interrupt mode much the same way they normally work in todays business
environment. The developers of OS/2 2.0 have created the operating system
that we have been needing for a number of years. They have done an excellent
job and are to be commended." GULFSTREAM AEROSPACE CORPORATION IN SAVANNAH,
GEORGIA - GREG CANADY, MANAGER OF TECHNICAL SUPPORT.
"Why be content to run when you can fly?... How could I ever clip my wings
once I have experienced flight?...Well I cannot afford to be content to run
in the DOS world. I must fly, otherwise I will never finish the race, never
get my job done. OS/2 2.0 seems to be the only way to fly..... Finally I
will add that OS/2 2.0 is exciting; it lives up to it's promises and delivers
even more." JEFF LANGR IN WASHINGTON DC
"OS/2 2.0 makes two significant changes in the way we interact with the
computer. First, the Workplace Shell removes many of the anxieties of the
end user who is uncomfortable with command lines and file structures.... The
second, and more significant change is OS/2's true multitasking ability...
Perhaps in a few years multitasking under OS/2 will be like the microwave
oven; people will wonder how they ever got along without it. Let's hope
so.... My job of integrating applications and devices into a useful
environment just got a lot easier. Most of all, OS/2 2.0 provides the
stability and reliability for use in the corporate marketplace. Trying to
describe in words something as rich, complex, and unique as OS/2 2.0, I'll
paraphrase an old saying: To those who have never experienced 2.0, no words
will suffice; to those who have, no words are necessary." GARY RAGAN IN
MERRITT ISLAND, FLORIDA
"For the last several years the PC industry's hottest keyword has been
WYSIWYG... With IBM's release of OS/2 2.0 the new key word is HYCAEIT: Have
your cake and eat it too!.... The real beauty of the operating system is the
ability to utilize all my existing DOS and Windows applications....
Congratulations on an excellent achievement. If Dr. Martin Luther King
hadn't already said, 'Free at last...I'm free at last,' I'd be shouting it
right now." LEN WINKLER AT PLACERVILLE, CALIF.
"I started pushing OS/2 last year because I knew that DOS was too tired to
handle what we needed. I wanted to be able to format a disk while I worked
on a spreadsheet or a document. Now, I have a 32 bit operating system that
works small miracles every time I open a folder. If I am forced to use a DOS
machine now, I am constantly thinking of what also I could be doing at the
same time with 2.0.... By the way, do you guys giggle like I do when you
hear someone yet again telling their woeful tale of setting up another DOS
LAN requester? " HALLIBURTON SERVICES IN HARVEY, LA. - NICHOLAS H.
GARDINER, DISTRICT ENGINEER
"Now, WOW!!!!, it is better than ever. The new Workplace Shell is
terrific!... I also like the ability of running Windows applications without
the need of purchasing Windows.....once again, Hooray for OS/2. No more
failures because some vendor didn't write clean code, and it crashed the
system....to sum it up, I guess I really have to say that it looks like
you've got yourselves a winner with OS/2 2.0. I can't wait to see what
wonderful things you put into the next release." SOUTHLAND LIFE OF GEORGIA -
STEVEN T. FRANCIS
"One of the key benefits that OS/2 has shown me so far is the ability to
enable access to these various platforms on a single workstation. Our
application support folks often need simultaneous access to 3270 and 5250
emulation sessions, as well as their PC based applications. No other
operating system or environment currently supports this need.... The
combination of OS/2 base code and extended services provides unique
possibilities that weren't even considered before with DOS-based
systems....there are two crucial factors in the acceptance of OS/2... First,
and rightly so is stability. The second key factor which is a smooth
migration path from the previous operating system.... OS/2 2.0 is an
excellent step in the right direction. I now feel comfortable in suggesting
this product to my end users. This product does not waste our previous
investment in DOS software, yet it offers an exceptionally better future with
GUI and multithreaded applications. The SEs who service my account are truly
impressed with this product and believe in it's capabilities. That
enthusiasm certainly helps me feel comfortable with my own purchasing
decisions.... It's been quite a while since I experienced the joy of
exploring my computer as a new toy. OS/2 is a technical marvel, and I can
truly appreciate the skills required to write such code. My hat is off to
your developers, and my thumb is waving at those who have said IBM can't
write good code. " SUNTRUST SERVICE CORPORATION IN ORLANDO, FLORIDA -
WILLIAM R. BEEM, PC SUPPORT MANAGER
"OS/2 2.0 is an incredibly innovative operating system for 80386 based
personal computer systems. To paraphrase an old television commercial, 'Try
It...you'll like it,' is how I tell folks to try the new OS/2 2.0 Workplace
Shell. Everyone I've demonstrated the Workplace Shell to has been just as
impressed with it as I am.... What's really great about OS/2 2.0 is that I
can be developing a Windows database application with Objectvision for
Windows, indexing the new documentation for the application with DeScribe for
OS/2 and communicating with the company mainframe with IRMA for DOS. And I'm
doing all of this real work and communicating at the same time. This is
great!.... OS/2 2.0 creates a more productive desktop at my office and makes
my work at home more productive and fun too! OS/2 2.0 really puts incredible
power at your command at home and in the office. I'm looking forward to
getting my shrink wrapped GA copy ASAP..... I would like to see OS/2 2.0
installed on every personal computer system that IBM sells!" HIGH PLAINS
BAPTIST HOSPITAL IN AMARILLO, TEXAS - GLENN R. BOUDREAUX, SR. SYSTEMS
PROGRAMMER
"I love OS/2..... I love OS/2.... I love OS/2.... I am walking around
saying I love OS/2 and now I really mean it!" US NAVY AT CAPE CANAVERAL, FL -
SR. CHIEF WILLIAM NEAL PORTER III, NAVAL ORDINANCE TEST UNIT
"OS/2 2.0 is like a shade tree in a thirsty land. What's the difference
between OS/2 2.0 and Windows? OS/2 2.0 is software and windows is shelfware.
Keep Windows 3.0. Use the documentation as bookends and the diskettes for
scratch diskettes. " BURLINGTON NORTHERN RAILROAD, PAUL MARTIN
"I find myself unconsciously adopting an air of smug superiority whenever I
talk to DOS or Windows users containing our different OS Platforms... OS/2
provides preemptive multitasking even on the 80286 platforms.... under OS/2,
programs can be interrupted by the system, under Windows a program has to
release it's control so other programs can run..... For software developers
in a PC environment, OS/2 is almost a necessity. Some people have
recommended OS/2 for only server applications, but it's value is much more
pronounced in a user environment. I now depend on the ability to easily and
conveniently interrupt what I'm doing without losing the context of my
work...... Compared to Windows 3.x, OS/2 offers better performance,
integrity, and reliability. It more fully exploits the capabilities of
modern hardware and provides an advanced operating system with the most
compatibility to DOS in the marketplace. Our group of testers cannot wait to
get their hands on the generally available product and all share my
enthusiasm for the system." MARTIN MARIETTA ENERGY SYSTEMS, INC. IN OAK
RIDGE, TN - BROOKS MCNEELY, DATABASE & SYSTEMS INTEGRATION SPECIALIST.
"I have come to the conclusion that OS/2 2.0 is like a McDonalds Combo Value
Meal.... A McDonalds Combo Value Meal is made up of three Great American
fast food staples: a Big Mac, large fries, and a medium Coke. All for just
$ 2.99; great food for a great price. OS/2 2.0 is made up of three great
products from every PC users wish list; a powerful 32 bit, non-preemptive,
multi-tasking operating system (Big Mac), a desktop shell/manager that has
the best of Mac and Windows (Large Fries), and full upward compatibility to
run anything ever written for DOS, Windows, and OS/2 1.X (Medium Coke). All
for just $99.00; great operating system for a great price. With OS/2 2.0 you
don't have to buy any extras and actually the desktop manager is even better
than large fries or Norton Desktop for Windows or a Mac(intosh)... Many fast
food chains have tried to imitate McDonalds, but McDonalds' commitment to
giving the customer what they want, a quality product for a fair price, has
kept them number one. You have the chance to be number one with OS/2 2.0. Go
for it!" UNIVERSITY OF MICHIGAN IN ANN ARBOR - KURT RICHARDSON OF UNIVERSITY
INFORMATION SYSTEMS
"I was able to install the OS/2 2.0 operating system, the developers kit, my
favorite DOS applications, and a 10-megabyte swap partition on an 89 megabyte
hard drive, with enough disk space left for my program development work. Try
doing that with UNIX! I believe OS/2 2.0 will define the current state of
the art in operating systems and overall computing capabilities for users
running 386/486 class computers.... I believe that OS/2 is destined to
become one of the most, if not the most, successful operating systems of the
90s. It is good to see operating system software take a step forward and get
into sync with current hardware." JEFFREY S. KILGORE, COMPUTER USER IN
GEORGETOWN, TEXAS.
"I can run my favorite PM applications and my favorite Window applications,
as well as those special character-based DOS and OS/2 applications I can't do
without....all at the same time. I have found OS/2 2.0 fulfills every need I
have in an operating system and then some. It is truly my window into our
enterprise computing environment." CITY OF TACOMA, TACOMA, WASHINGTON -
BRIAN M. DAVELAAR, SR. TECHNICAL ANALYST
"I can build a personal platform from which I can use the appropriate tool
for the appropriate task. Most of all, being able to run a DOS task in the
background will free me from having to give my PC entirely over to one of
those tasks. I'll now be able to continue working on something else, while
the DOS task executes on it's Virtual Machine. I love it! Other substantial
improvements include the master help index, the ease of installation,
selection of print drivers, the Seek and Scan files, and the ability to
create folders for organizing objects. Even the improved ability to control
screen colors and backgrounds helps make the environment one in which I feel
most comfortable and (most of all) productive. I feel like I'm living in the
future." NORTHWESTERN NATIONAL LIFE INSURANCE IN MINNEAPOLIS - WALT CYGAN
"I'm sold! I didn't think I'd be saying this, but I'm a believer. I have
become so callous towards the empty claims of software vendors that I flat
out refuse to even hope for a feature until I've tried it myself....
Congratulations for doing it right.... We believe this type of environment
improves productivity and lowers training costs, so we began the move to GUIs
almost two years ago... You have delivered on your promise, given us a
migration path that makes sense, and because of it the entire computing world
will come knocking at your door (not window). Thanks!" NORTHWESTERN
NATIONAL LIFE INSURANCE - JERRY WALKER, SENIOR ANALYST
"The features of OS/2 2.0 make it a real winner for use at home as well as in
my department... At the office the multitasking features make it a great
tool for our operators and technical support personnel, since they are always
being interrupted and keep many things going at once. With Extended Services
they keep active sessions to the ES/9000, AS/400, and the RS/6000 going all
the time..... For home use, OS/2 2.0 has the wonderful dual personality of
being more powerful than DOS or Windows, but at the same time being easier to
use. The backward compatibility is a tremendous benefit, allowing use of
virtually all the programs we have now with the potential for enhanced
applications that take advantage of the advanced features of the new system.
I'm already looking forward to replacing Word for Windows with DeScribe as my
word processor." SCHOOL BOARD OF ALACHUA COUNTY, GAINESVILLE, FLORIDA -
DANIEL H. CROMER, JR., MANAGER OF SYSTEMS & PROGRAMMING
"OS/2 2.0 provides the most user-friendly environment for the PC platform.
OS/2 2.0 gives the DOS and/or Windows user a no-loss upgrade to a friendlier
and more powerful system with minimal pain. Within an hour or two of first
sitting down with OS/2 2.0, he/she can be significantly more productive...
OS/2's excellent support of DOS, Windows and existing OS/2 applications, with
protection of the system and each process from each other, makes OS/2 the
most integrating operating system available on any computer platform. It is
an excellent choice for the novice end user, the power user, and the
DOS/Windows/OS/2 programmer." PSI COMP SOFTWARE, INC. IN SALT LAKE CITY,
UTAH - BILL HARRIS (CONSULTING AT UTAH DEPARTMENT OF ENVIRONMENTAL QUALITY.)
"OS/2 will bridge the chasm between PCs and TRUE individual exploitation of
the power of information technology. Up until now, we've only been led to
believe that it's been done...... OS/2 has demonstrated how my investment in
textual applications can be stretched further and at the same time, it has
also let me experience the thrill of new graphical tools. My palette of
tools is now much broader than I had ever imagined and my productivity is
greater than ever. OS/2 will remove existing constraints and bring new and
even more powerful tools to my desktop... What excitement the future holds
for us with a new foundation of OS/2! I'm thrilled with the opportunity to
explore OS/2 and guide my company into the future with OS/2 as the catalyst."
TALBOTS IN TAMPA, FLORIDA - DAVID A. NAGY, DIRECTOR, TECHNICAL SERVICES
- OS2-2DOC.ZIP [OS2 Beta 6.167 Docs]
6167DOCS.LST
This is a listing of the documents that can be found on this diskette.
OVER6167.DOC Overview of the 6.167 version of IBM 32 Bit OS/2
INST6167.DOC Installation instructions and list of restrictions for
IBM 32 Bit OS/2 internal driver level 6.167
READ6167.DOC Read me first file for IBM 32 Bit OS/2 driver 6.167
VMBOOT.DOC Paper discussing the Virtual Machine boot function of
IBM 32 Bit OS/2
V2-WIN.DOC Information on running Windows applications under IBM 32
Bit OS/2.
ESLS6167.DOC Installation instructions and list of restrictions when using
Extended Services/2 (version 246) and LAN Services 2.0 (version
281) with IBM 32 Bit OS/2 driver 6.167.
INDBC167.DOC Installation instructions and restrictions for use with IBM
Extended Services/2 Database Manager Client feature. �
ESLS6167.DOC
Restrictions and Installation Instructions for
IBM Extended Services for OS/2 (Driver Level S1A246)
and
IBM OS/2 LAN Server V2.0 (Driver Level 281)
on
IBM OS/2 Standard Edition V2.0 (Driver Level 6.167)
October 18, 1991 2:16 p.m.
IBM CONFIDENTIAL Extended Services Driver S1A246 & OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver
6.167
This document contains information of a proprietary nature. ALL INFORMATION CONTAINED
HEREIN SHALL BE KEPT IN CONFIDENCE. None of this information herein shall be divulged to
persons other than IBM employees authorized by the nature of their duties to receive such information, or
individuals or organizations who are authorized in writing in accordance with existing policy regarding release
of company information. This material, if exported from the United States, is shipped under General
License GTDR.
Restrictions and Installation Instructions for
IBM Extended Services for OS/2 (Driver Level S1A246)
and
IBM OS/2 LAN Server V2.0 (Driver Level 281)
on
IBM OS/2 Standard Edition V2.0 (Driver Level 6.167)
October 18, 1991 2:16 p.m.
IBM CONFIDENTIAL Extended Services Driver S1A246 & OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver
6.167
IBM CONFIDENTIAL Extended Services Driver S1A246 ii OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.0 System Requirements and Performance ............... . . . . . . . 3
2.1 Memory and Fixed-Disk.Requirements . . . . . . . ............. 3
2.2 Extended Services.Performance. ........... . . . . . . . . . . . . . 4
2.3 LAN Server/Requester.Performance. ........... . . . . . . . . . . 4
3.0 New and Enhanced.Function ... . . . . . . . . . ......... . . . . . . 6
3.1 New and Enhanced Function in Communications Manager .. . . . . . . . . 6
3.2 New and Enhanced Function in Database Manager ............ . . 7
3.3 New and Enhanced Function in.LAN.Server 2.0 . . ........... . 8
4.0 Quick Glance - Fixes in this.Driver ....... . . . . . . . . . . . . . . . 10
4.1 Fixes in Communications.Manager. . . ....... . . . . . . . . . .. . 10
4.2 Fixes in Database Manager ............. . . . . . . . . . . . . . . 16
4.3 Fixes in LAN Services. . . . . . ........... . . . . . . . . . . . . . 19
5.0 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1 General Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2 Extended Services Restrictions. . . . . . . ............. . . . . . . 20
5.3 Communications Manager.Restrictions . ............. . . . . . . 21
5.4 Database Manager Restrictions. . . . . . . ............. . . . . . 25
5.5 LAN Server Version 2.0 Hardware.Restrictions ... . . . . . . . . . . . . 28
5.6 LAN Server Version 2.0 Server.Restrictions ... . . . . . . . . . . . . . . 29
5.7 LAN Server Version 2.0 Requester Restrictions. . . . . . . . . . . . . . . . 34
5.8 LAN Server Version 2.0 Publications Restrictions. . . . . . . . . . . . . . 37
6.0 Extended Services Installation. . . . . . . ............. . . . . . . 38
6.1 Before You Install Extended.Services ..... . . . . . ......... . . 38
6.2 Extended Services Installation Concepts. . . . . . . . .......... . . 40
6.3 Basic Configuration Services (BCS) ............... . . . . . . . . 41
6.4 Advanced Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.5 Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.6 Applying Patches to the Installed System. . . . . . . . ........ . . . 44
7.0 Installing Communications Manager ............... . . . . . . . . 47
7.1 Before You Install Communications Manager ................. 47
7.2 Installation Instructions for Communications Manager .... . . . . . . . 49
7.3 Re-installation of Communications Manager ................. 52
7.4 Communications Manager Installation Notes ................. 52
7.5 ROP Service and SPA Router Installation.Instructions .... . . . . . . 53
8.0 Installing Database Manager ............. . . . . . . . . . . . . . . 55
8.1 Before You Install Database Manager ............... . . . . . . 55
8.2 Database Manager Installation Examples. . . . . . . . ........ . . . 56
9.0 Installing OS/2 LAN.Requester. . ......... . . . ... . . . . . . . 65
9.1 Basic Installation for OS/2 LAN Requester ................. . 65
Contents ii
IBM CONFIDENTIAL Extended Services Driver S1A246 iii OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
9.2 Advanced Installation for OS/2 LAN Requester .............. . 65
9.3 Reinstalling, Reconfiguring.or Removing. . ........... . . . . . 65
10.0 Installing OS/2.LAN.Server . . ....... . . . . . . ... . . . . . . . 66
10.1 Basic Installation for OS/2 LAN Server. . . . . . . . .......... . . 66
10.2 Advanced Installation for OS/2.LAN.Server ..... . ....... . . 66
10.3 LAN Server 1.3 Migration Utility ............... . . . . . . . . 66
11.0 Installing IBM LAN Support Program and.DOS.LAN.Requester . . 67
11.1 Installing the IBM LAN Support.Program, V.1.21. ........ . . . 67
11.2 Installing DOS LAN.Requester. . ......... . . . ... . . . . . . 67
Appendix A. SNA Advanced Configuration . . . . . . . . ............ . 69
A.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A.2 Advanced Configuration for 5250. ............. . . . . . . . . . . 70
A.3 Advanced Configuration for 3270.Over Token-Ring. ........ . . . 76
A.4 Advanced Configuration for 3270.Gateway. . . . ....... . . . . . . 79
Appendix B. EHLLAPI Virtual Device.Driver (VDD) ... . . . . . . . . . . 83
B.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
B.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
B.3 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
B.4 Compatability (With Personal Communications 3270.2.0) . . . . . . . . 84
Appendix C. Communications Manager Stop.API. ........... . . . . 89
C.1 Overview and Usage ........... . . . . . . . . . . . . . . . . . . . . 89
Contents iii
IBM CONFIDENTIAL Extended Services Driver S1A246 1 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
1.0 Introduction
This document provides the basic installation instructions for the IBM Extended
Services for OS/2 (Extended Services) and LAN Server (LS) V2.0 driver. For
additional information on installing these products, please refer to the Workstation
Install Guide publication for Extended Services and the LAN 2.0 Network
Administrator Reference Volume 1 publication for LS.
The Extended Services and LAN Server V2.0 driver consists of: ( 3 1/2" format):
- 8 Extended Services diskettes
- 2 patch diskettes
- 2 OS/2 LAN Server V2.0 diskettes
- 3 OS/2 LAN Requester V2.0 diskettes
- 1 OS/2 LAN Network Device Drivers diskette
- 1 OS/2 LAN Migration Utility V1.3 diskette
- 3 DOS LAN Requester diskettes
- 1 PC LAN Support Program diskette
The patch diskettes contain patches for Extended Services.
# Note:
# OS/2 LAN Server driver 281 and Alternate Diskette 1 for Extended Services driver
# S1A246 are required for use with SE 2.0 driver 6.167. The Alternate Diskette 1 for
# Extended Services must be used as a replacement for the Diskette 1 in the original
# Extended Services driver S1A246. This Alternate Diskette 1 must be used during
# initial Extended Services installation.
The entire Extended Services installation procedure starts with Diskette 1 of the
Extended Services diskettes. You will be guided to insert program diskettes 1
through n, depending on your system requirements. The CONFIG.SYS file is
updated automatically during the Extended Services installation process.
The installation of OS/2 Communications Manager, OS/2 Database Manager and
OS/2 LAN Server assumes that you have already installed the appropriate OS/2
base operating system, or that you already have EE 1.30.1 installed.
For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required. For a 32-bit
base, SE V2.0 driver level 6.167 is required.
# NOTE
# Although, these drivers will run on either a SE 16-bit base or a 32-bit base, this
# document was primarily written from a 32-bit installation and execution
# perspective. Thus, there may be slight differences when running in a 16-bit
# environment.
# Throughout this document, a revision code of # in the left margin denotes changes
# from the previous Restrictions and Installation document for Extended Services and
# OS/2 LAN Server running on SE 2.0 level 6.605.
Introduction 1
IBM CONFIDENTIAL Extended Services Driver S1A246 2 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Introduction 2
IBM CONFIDENTIAL Extended Services Driver S1A246 3 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
2.0 System Requirements and Performance
The following sections identify performance characteristics of these drivers.
2.1 Memory and Fixed-Disk Requirements
NOTE: THIS INFORMATION ONLY PERTAINS TO THESE DRIVERS, AND
IS SUBJECT TO SIGNIFICANT CHANGE IN THE FUTURE!
For OS/2 Standard Edition V 1.30.1, a base partition of 20MB is needed. This
partition must hold this SE base, swappper.dat file, and the Extended Services and
LAN Server V2.0 files that are installed in the boot partition.
# For OS/2 Standard Edition 2.0, the base partition should be no smaller than 40MB.
# This is to contain both the SE base and the common files used by Extended
# Services and LAN Server (files that are always installed in the boot partition), and
# to give some room for future expansion.
# In addition to the disk space required for the appropriate Standard Edition base, the
# minimum disk space used by Extended Services or LAN Server is 12MB. However,
# depending on the Extended Services and LAN Server features that are actually
# configured and installed, up to 32MB of disk space may be used by Extended
# Services and LS.
The memory requirements of the OS/2 base operating system depend upon which
version of the operating system is used and which features of the OS/2 base system
are concurrently used. The MINIMUM memory requirement for the OS/2 SE
Version 1.30.1 product is 2 MB. The MINIMUM memory requirement for OS/2
SE Version 2.0 is 4 MB.
For these drivers, the minimum RAM for Extended Services or LAN Server, in
ADDITION to the base operating system requirement, is 1MB.
In addition to the memory required by the base operating system, Extended Services
and LAN Server, the user should allow additional memory to be used by whatever
user applications that are concurrently executed. In general terms, small OS/2
applications (for example, WordPerfect or Excel) typically require about 1 MB of
memory while large OS/2 applications (for example, DeScribe or Lotus 123/G) need
2-3 MB of memory.
We continue to work to improve the disk and memory usage of the SE, Extended
Services, and LS products. The numbers above may not reflect the actual disk and
memory requirements of the final product.
These drivers are NOT suitable to be used as a benchmarking platform.
Performance improvements continue to be made and the performance of this early
code may not represent the performance of the final product.
System Requirements and Performance 3
IBM CONFIDENTIAL Extended Services Driver S1A246 4 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
More complete information regarding the disk and memory requirements for
Extended Services, LAN Server, and OS/2 SE Version 2.0 will be made available at
general availability.
2.2 Extended Services Performance
Performance evaluation is ongoing; and performance is expected to improve over
time. This level of code, however, may not accurately represent, in your
environment, the performance of the final product. It is therefore
RECOMMENDED that this level of code NOT be used for performance
benchmarking and evaluation.
2.3 LAN Server/Requester Performance
2.3.1 Performance Considerations
When using this driver of LS 2.0, you may notice very significant improvements or
some degradation from LS 1.3 depending on your particular environment and/or
application. Some of these situations are described below. For the environments in
which OS/2 1.3 requesters are upgraded to OS/2 2.0, the descriptions assume
sufficient memory in the requesters to avoid swapping during application execution.
Note: We recommend that you do not use this driver level of code for performance
benchmarking or evaluation.
Environment 1
Upgrading LS 1.3 servers to LS 2.0 but not upgrading the requester's operating
system from OS/2 1.3 to 2.0. Also includes DLR requesters with or without upgrade
to DLR 2.0.
LS 2.0 Advanced Version
? LS 2.0 Advanced performs up to 2 times faster than LS 1.3 for most HPFS file
I/O operations, including application loading, for both DLR and OS/2
requesters. The result is both shorter response times seen by the user and greater
throughput capacity of the server.
LS 2.0 Entry Version
? The performance will be about the same as LS 1.3.
Environment 2
Upgrading OS/2 requesters to OS/2 2.0 but not upgrading the server to LS 2.0 from
LS 1.3.
Application Loading Across LAN: Currently, OS/2 2.0 application load times
across the LAN are slower than when using OS/2 1.3 as the requester operating
system. This is related to OS/2 2.0 loader performance. Application loading from
the DOS session is about the same as OS/2 1.3.
System Requirements and Performance 4
IBM CONFIDENTIAL Extended Services Driver S1A246 5 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
File I/O Performance Across LAN: OS/2 file I/O performance is slightly slower
with OS/2 2.0 than 1.3 but is not perceivable in many environments. This is a
known problem and improvements will be made. DOS session I/O performance of
OS/2 2.0 has noticeably improved performance over 1.3 for many types of I/O
operations.
Environment 3
Upgrading OS/2 requesters with OS/2 2.0 and also upgrading LS 1.3 servers with LS
2.0.
LS 2.0 Advanced Version
? Performance will be similar to that of the Environment 1 Advanced version but
OS/2 application loading will be somewhat slower.
LS 2.0 Entry Version
? The performance will be about the same as LS 1.3.
System Requirements and Performance 5
IBM CONFIDENTIAL Extended Services Driver S1A246 6 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
3.0 New and Enhanced Function
The following sections identify the function available in this driver.
3.1 New and Enhanced Function in Communications Manager
Following is a list of the new or enhanced functions that will be available in this
driver for Extended Services Communications Manager. This list is NOT intended
to include ALL functions that will be available in the final product.
Note
Please be aware that there may be restrictions/limitations that apply to some of
these functions for this driver. Please BE SURE to refer to 5.3,
﨏ommunications Manager Restrictions?on page 21 for information about
these restrictions.
?
Advanced Peer-to-Peer Networking (APPN) Support
? Modification of the LAN Transport layer to improve performance across
supported LANS
? Enabling support for industry standard NDIS interface
? Programmable Configuration allowing REXX interface to the configuration file
? 3174 Peer Communication enabling
? EHLLAPI extensions including multiple simultaneous application access and
support for structured fields low level verbs
? ACDI extension allowing API to re-direct ACDI output (in addition to
command line)
? 370 Netview Remote Operations allow OS/2 commands from the Netview
operator, REXX, and CLIST
?
New LU pooling algorithm to allocate session when requested, not as
configured
? Persistent Verification: reduced ID exchanges for LU6.2 (W/S to host)
? File Transfer support for long file names
? 3270 Jump key
? Optionally installable Communications Manager Utilities
? Configuration File Manager to simplify the administration of configuration files
? Increased number of workstations for SNA Gateway support
? 5250 in a PM text window as default
? Migration path from EE 1.30.1
New and Enhanced Function 6
IBM CONFIDENTIAL Extended Services Driver S1A246 7 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? Auto-reactivate DLC after adapter failure
? REXX EHLLAPI interface (for information, see RXHLLAPI.DOC in
\CMLIB)
?
DOS session interface to EHLLAPI (for information, see Appendix)
? CM Stop API (for information, see Appendix)
? Command line upgrade function for upgrading configuration files
3.2 New and Enhanced Function in Database Manager
Following is a list of the new or enhanced functions for Extended Services for OS/2
Database Manager that are available in this driver. The list is NOT intended to
include ALL functions that will be available in the final product.
Note
Please be aware that there may be restrictions/limitations that apply to some of
these functions for this driver. Please BE SURE to refer to 5.4, 﨑atabase
Manager Restrictions?on page 25 for information about these restrictions.
? Roll Forward Recovery (except for User Exits)
?
DOS Windows Client Support
?
Database Manageability Tools
?Configuration Tool
?Recovery Tool
?Directory Tool
? Database Manager Command Line Interface
? Protocols for Extended Services
?Database server support for Extended Services clients using NETBIOS,
APPC and APPN protocols
?Database server support for EE 1.2/1.3 OS/2 clients using SQLLOO
? Reliability, Availability, Serviceability and Trace
?Independent Trace Facility (ITF)
?First Failure Support Technology/2 (FFST/2) support
? Translate Function
? SQLSTATE
? User Defined Collate Sequence
? Database Client with Local Databases
? Standards Compliance: SAA and MIA
?SQL Date/Time/Timestamp Arithmetic
New and Enhanced Function 7
IBM CONFIDENTIAL Extended Services Driver S1A246 8 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
?Packages
?Multivendor Integration Architecture (MIA) Version 1 implementation
3.2.1 Design Changes from Previous Database Manager Releases
Please note that the following design changes have been made to Database Manager
in IBM Extended Services for OS/2
? You cannot create a database on a diskette, except on a Standalone Database
Manager workstation.
? APPC/APPN will NOT issue a STARTDBM (as APPC formerly did with EE
1.3). You must issue a STARTDBM at the database server before any database
clients can connect to a database.
3.3 New and Enhanced Function in LAN Server 2.0
Following is a list of the new or enhanced functions for OS/2 LAN Server 2.0 that
are available in this driver. The list is NOT intended to include ALL functions that
will be available in the final product.
Note
Please be aware that there may be restrictions/limitations that apply to some of
these functions for this driver. Please BE SURE to refer to 5.6, 﨤AN Server
Version 2.0 Server Restrictions?on page 29 and 5.7, 﨤AN Server Version 2.0
Requester Restrictions?on page 34 for information about these restrictions.
Reorganized/Improved Publications
PM Hypertext Based OnLine Reference
PM Based Graphical Install
386 High-Performance File System
Local Security for 386 HPFS
Fault Tolerance
? UPS Support
? Disk Mirroring and Duplexing
Support for Multiple LAN Adapters
NDIS Support - (Network Device Interface Specifications)
IBM Token Ring Busmaster/A Support
Remote IPL Enhancements
New and Enhanced Function 8
IBM CONFIDENTIAL Extended Services Driver S1A246 9 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? Remote IPL of DOS or 1.3 OS/2 Workstations
? Ethernet (DOS and OS/2 1.3 Requesters)
DOS LAN Requester Enhancements
? Enhanced Windows 3.0 Support
?
DBCS Command Line Support
? DBCS Printer Support
? DOS 5.0 Compatibilty
Operator Priveleges
Time Source Service
Logon Enhancements
?
Fault Tolerant Logon Capability
? Backup Logon
? Logon From Multiple Workstations
Generic Alerter Service
First Failure Support Technology/2 (FFST/2)
LAN Over Coax
New and Enhanced Function 9
IBM CONFIDENTIAL Extended Services Driver S1A246 10 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
4.0 Quick Glance - Fixes in this Driver
The following sections identify fixes (to previous driver restrictions) that have been
incorporated into this driver.
4.1 Fixes in Communications Manager
? INSTALLATION AND CONFIGURATION
FIXED
If you are installing IBM Extended Services for OS/2 with the SE 2.0
operating system, you must take the following step after installing SE 2.0
and before installing IBM Extended Services for OS/2. You should copy the
file ABIOS.SYS from the \OS2 directory to the root directory of the logical
drive on which OS/2 is installed.
FIXED
If you plan to install Communications Manager through Advanced
Installation with the default configuration file ACSCFG.CFG, you MUST
select BOTH ACSCFG and ACSCFGUS from the Default Configuration
File menu during initial installation. If you select only ACSCFG,
installation will fail.
FIXED
If you have the Networking Services/2 product installed on your workstation
and you are planning to install IBM Extended Services for OS/2 on that
workstation with Standard Edition version 1.3 at the refresh level 1.30.1, you
should reformat your partition during the installation of Standard Edition.
FIXED
Basic Configuration Services should not be used to create a 5250 WSF
configuration file during initial installation. Instead, Advanced Installation
should be used to install a User Defined 5250 configuration file.
FIXED
The Install/Remove function to Remove Communications Manager (CM)
may not remove all the Communications Manager files from the system.
RESTRICTION
An initial IBM Extended Services for OS/2 installation using A:ESINST
cannot be followed by a second A:ESINST without reformatting and
reinstalling the base operating system. If additional features need to be
installed after the initial installation, the REINST command should be used.
Quick Glance - Fixes in this Driver 10
IBM CONFIDENTIAL Extended Services Driver S1A246 11 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
After verifying a configuration file, you may see the following message in the
message log even though the configuration file verified without errors. This
message should be ignored.
The Communications Manager configuration does not start the SNA
support. Change and re-verify the Communications Manager configuration.
RESTRICTION
After you complete steps for installation of Communications Manager, you
are instructed to stop active features and press CTRL-ALT-DEL to reboot
the system. Instead of pressing CTRL-ALT-DEL, you should use the
DESKTOP Shutdown to stop the system if you have formatted your
hardfile using the High Performance File System (HPFS).
? INSTALLATION AND OPERATION OF CM WITH LAN SERVER (LS)
RESTRICTION
If you are planning to use both IBM Extended Services for OS/2 and LS,
you should install IBM Extended Services for OS/2 FIRST. When you
install Extended Services, you should select to install the LAN Adapter and
Protocol Support from Additional Features in Communications Manager
Advanced Installation (if it is not already installed based on a configuration
file you have selected).
FIXED
A NET START REQUESTER may fail if a NETBIOS application is
started at the same time. If this occurs, you should restart the requester.
? CUSTOM BUILD AND CUSTOM INSTALLATION
FIXED
Limited testing has been done with the Custom build and custom
installation feature.
FIXED
Custom build and custom installation should not be used for a configuration
file containing ACDI parameters.
FIXED
Custom build and custom installation should not be used for configurations
containing APPC/APPN parameters.
Quick Glance - Fixes in this Driver 11
IBM CONFIDENTIAL Extended Services Driver S1A246 12 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
Custom build and custom installation does not function correctly to install
LAN for a configuration file with ACDI redirection.
After a custom build and custom installation, the Basic Configuratio n
Services (ESCFG command) is not accessible.
? PROGRAMMABLE CONFIGURATION
FIXED
The APPN feature of Programmable Configuration is not functioning in this
driver and should not be used.
? CONFIGURATION UPGRADE
FIXED
Limited testing has been done with the Configuration Upgrade and
installation with pre-existing Extended Edition configuration files to be
upgraded. Upgrade of Extended Edition 1.2 or 1.3 configuration files for
3270 or ASYNC should work correctly. You should not attempt to upgrade
a configuration file which contains combinations of other features with 3270
or ASYNC.
FIXED
Configuration Upgrade should not be used to upgrade EE 1.0 and EE 1.1
configuration files. For this first driver, advanced configuration should be
used to build the files rather than upgrading from the old EE 1.0 or 1.1 file.
FIXED
Communications Manager configuration files containing Database Remote
Data Services features cannot be upgraded.
FIXED
Communications Manager configuration files containing LAN Requester
cannot be upgraded.
FIXED
An Extended Edition 1.2 or 1.3 level configuration file cannot be upgraded if
it contains 3270 DFT and 3270 non-DFT with more than one session for
DFT or non-DFT.
FIXED
EE 1.2 and 1.3 configuration files containing only NETBIOS parameters
cannot be upgraded in this first driver.
Quick Glance - Fixes in this Driver 12
IBM CONFIDENTIAL Extended Services Driver S1A246 13 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
EE 1.2 and 1.3 configuration files with APPC Transaction Program
parameters should not be upgraded in this first driver.
FIXED
Configuration upgrade should not be used to upgrade more than one EE 1.2
or EE 1.3 configuration file during installation.
FIXED
5250 WSF configuration files do not upgrade correctly.
FIXED
REINST should not be used to install an upgraded configuration file which
is stored in \CMLIB.
? SDLC CONNECTIVITY
FIXED
Intermittent TRAP D errors may occur with the SDLC connectivity.
? 3270 TERMINAL EMULATION
FIXED
The 3270 terminal emulator should not be restarted after selecting to stop
specific emulator sessions or a software error will occur. You should be able
to stop 3270 emulation and restart it without problems if you select to stop
ALL sessions.
? 3270 HOST GRAPHICS
FIXED
When running on the OS/2 2.0 operating system, host graphics files can be
printed or plotted only when using the PR option from the GDDM
directory panel.
RESTRICTION
When running on the OS/2 2.0 operating system, the PF5=SAVE PIF
option under the GDDM output function is not working correctly.
? SNA GATEWAY
Quick Glance - Fixes in this Driver 13
IBM CONFIDENTIAL Extended Services Driver S1A246 14 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
If the SNA Gateway has a LAN connection to the host or to its attached
workstations, the gateway may hang when logging off the last workstation.
To avoid this problem, the FREE UNUSED LINKS parameter in the DLC
profile (accessed from CM Advanced Configuration SNA Feature Profiles)
should be set to NO on your SNA Gateway.
? DMA ASYNC
RESTRICTION
The DMA Async support for line speeds up to 64Kbps is not functioning
correctly on the PS/2 Model 90 and Model 95. If you are using a PS/2
Model 90 or 95 with ASCII emulation or ACDI redirection, you can still
use line speeds up to 19.2 Kbps. You should add a REM statement to your
CONFIG.SYS as follows. In this statement, d is the logical drive on which
Communications Manager is installed.
REM DEVICE=d:\CMLIB\ASYNCDDC.SYS
?
5250 WORKSTATION FEATURE (WSF)
FIXED
Basic Configuration Services (ESCFG command) should not be used to
create a 5250 WSF configuration file. Instead Advanced Configuration
should be used.
FIXED
When configuring 5250 WSF session assignments, red warning panels will be
displayed indicating that the APPC partner LU alias and the APPC mode
name do not exist. You will be asked if you want to continue. Select YES.
If you have configured these parameters, they do exist even though the
warning indicates that they do not.
FIXED
To use 5250 WSF with the auto sign-on feature, the LU name and the LU
alias name should be configured to match.
FIXED
The F4=LIST function from the 5250 Session profiles does not provide a
list of the mode and partner LU profiles.
FIXED
When using the twinax connectivity for 5250 Workstation Feature, only one
twinax attached workstation can access the AS/400 at a time. This occurs
because every twinax workstation connects to the AS/400 with a PU name
of PU00000.
Quick Glance - Fixes in this Driver 14
IBM CONFIDENTIAL Extended Services Driver S1A246 15 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
Using the SE 2.0 operating system, 5250 fails to stop when it is selected to
be stopped from Communications Manager main menu. You should not
attempt to stop 5250 WSF if there are other Communications Manager
features running on the system. If you do attempt to stop 5250 WSF, you
should not attempt to restart 5250, or the other features running on the
system will be brought down. Your host line may need to be varied off and
back on after this scenario.
? LAN ADAPTER AND PROTOCOL SUPPORT
RESTRICTION
When using the IBM Token Ring 16/4 Adapter or the IBM Token Ring
16/4 adapter /A, and the adapter is set for 64K paged, a user application
cannot take advantage of the 64K.
FIXED
"Universally administered address reversed" is now a configuration option for
NETBIOS in the NETBEUI section of PROTOCOL.INI. For this first
driver, this option will not be operational.
FIXED
If you are writing NETBIOS applications, you may find that the return code
from NETBIOS in the AX register is not always correct. For this first
driver, you should rely on the NETBIOS return code in the NCB rather
than that in AX.
FIXED
The following statement should be added to the bottom of the CONFIG.
SYS to start the service required for LAN Adapter and Protocol Support
error handling. In this statement, d is the logical drive on which the OS2
operating system is installed.
RUN=d:\OS2\EPW.EXE
?
APPN
FIXED
The APPN function of routing traffic through an intermediate node is not
functioning correctly.
FIXED
The APPN messages in this driver are in a format such that the message
itself contains both the message and the help text. Therefore, if you choose
to view the help, you will get an indication that the help is not available. All
the information needed is contained in the message text itself.
Quick Glance - Fixes in this Driver 15
IBM CONFIDENTIAL Extended Services Driver S1A246 16 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? ACDI REDIRECTION API
FIXED
The MASM API data structure for ACDI Redirection API is incorrectly
named as REDIRECT.INT. You should rename this file to
REDIRECT.INC. This file is found in \CMLIB if you have selected to
install the API Data Structures.
? EHLLAPI
FIXED
The 5250 EHLLAPI TWAIT option on Set Session Parameters acts like an
LWAIT. It does not time out after the first minute.
?
REMOTE OPERATIONS (ROP) SERVICE
FIXED
For Remote Operations, an extra unwanted ICON and entry in the Task
List for ROP KERNEL is displayed. Neither the ICON nor the Task List
entry should be accessed.
FIXED
The ROP Service may not always start after initially starting the system or
after CTRL-ALT-DEL to reboot the system. If this problem occurs on
your system, you should select to start ROP Service again. It should start
correctly the second time.
FIXED FOR SE 2.0 ONLY
Occasionally the CTRL-ALT-DEL and Desktop shutdown may fail to
work after running ROP Service for an extended period of time. In this
case, the PC must be powered off. This can cause a significant delay in
startup when the PC is restarted.
? SUBSYSTEM MANAGEMENT
FIXED
The subsystem management functions to display class of service and
topology for the active configuration file are not working correctly.
4.2 Fixes in Database Manager
The following table shows what has been fixed and what has not been fixed since
the previous driver.
Quick Glance - Fixes in this Driver 16
IBM CONFIDENTIAL Extended Services Driver S1A246 17 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Table 1 (Page 1 of 2). Database Manager Fixes Since Previous Driver
Problem SE 1.30.1 or SE Status
2.0
Install SE 2.0 only Fixed
Musical notes may appear on screen during
the 'Transferring files...' message. No impact
to install.
Install SE 2.0 only Fixed
After Database Manager is installed, during
IPL the system message SYS1195 appears on
the screen. The message reads "The command
"SYSLOG" on line xx of the CONFIG.SYS
file is not recognized. Line xx is ignored."
Install Both Fixed
Database Manager messages are properly
installed, but no entry exists in Group Main.
(This applies to Standalone DBM only)
Create Database Both Fixed
After creating a new database with Extended
Services, change the following database
configuration parameters for that database:
? Log file size (# of 4K pages): change from
32 to 50
? Auto-restart: change from 'YES' to 'NO'
Backup/Restore SE 2.0 only Fixed
You can backup the 'Entire database' ONLY
(you CANNOT do a 'Changes Only'
backup).
Reinstallation (REINST) SE 2.0 only Fixed
Removal/reinstallation of Database Manager
components is unpredictable. If the user must
remove or reinstall components with this
driver, a disk format and a full install of the
operating system and Extended Services may
be required.
Reinstallation (REINST) Both Fixed
During a reinstallation, the system may
erroneously detect that a previous version of
Database Manager is installed. If you get the
Remove Previous Version of Selected
Component screen, select 'Remove Previous
Version' and the install should complete
normally.
Quick Glance - Fixes in this Driver 17
IBM CONFIDENTIAL Extended Services Driver S1A246 18 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Table 1 (Page 2 of 2). Database Manager Fixes Since Previous Driver
Problem SE 1.30.1 or SE Status
2.0
Command Line Interface does NOT work SE 2.0 only Fixed
Command Line Interface SE 1.30.1 only Fixed
? Cannot be run from the Desktop
? AUTOCOMMIT (the default) is not
working. The user will need to perform
commits ('dbm commit') manually.
? REORGCHK is not working.
? Message 'DBM.MSG file can't be found'
appears after normal completion
Install is failing to add x:\sqllib to
DPATH= statement of config.sys (where
x is the drive DBM is installed on).
Workaround is to add x:\sqllib to
DPATH= statement of config.sys
manually.
REXX Interfaces to Database Manager SE 2.0 only Fixed
If the user experiences difficulty with a REXX
application, the application should be
re-tokenized.
Independent Trace Facility (ITF) Both Fixed
The mask (-m) option is not working. If the
mask is used, the trace buffer will be empty.
Be aware that the mask option is invoked in
two ways. Neither one of these is working:
1. By starting trace using 'trc on
<options>' where one of the options is
-m (mask).
2. By starting trace with simply 'trc'.
This method of starting trace gives you a
full-screen menu of selectable options. If
you select any of the Products, Events or
Components this will also set a mask, and
the trace buffer will be empty.
Log Full Condition (SQL0964)Both Fixed
SQL0964 (DBM log full condition) received,
even though periodic 'commits' are being
done.
Quick Glance - Fixes in this Driver 18
IBM CONFIDENTIAL Extended Services Driver S1A246 19 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
4.3 Fixes in LAN Services
# NOTE TO OUR CUSTOMERS
# Since this is a new driver for LAN Server, it is highly recommended that you
# upgrade your system from the 274 LS driver to the 281 LS driver.
# Please note that the following are NO longer restrictions in the 281 LS driver:
#
FIXED
# Under Restrictions and Special Considerations for API's: The new 32 bit
# DosFindFirst() /DosFindNext() calls will not work properly on a network drive
#
FIXED
# Under Install/Config for the Server:
?
# If the requester is already installed on a workstation, the server cannot be
# installed. To install a server, remove the requester first.
# ? LAN Services cannot be moved to another drive, if already installed on a
# different fixed disk drive.
# FIXED
# Under Install/Config for the Requester:
# ? LAN Services cannot be moved to another drive, if already installed on a
# different fixed disk drive.
# ? Do not install the Loop Back Driver support.
#
FIXED
# Under Generic Alerter Services for the Server: The problem of the
# SYSLEVEL.SRV file not always being located in the :\IBMLAN subdirectory.
Quick Glance - Fixes in this Driver 19
IBM CONFIDENTIAL Extended Services Driver S1A246 20 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.0 Restrictions
The following sections identify inconsistencies, restrictions, and problems that we
are aware of in this driver. Our development groups are currently addressing these.
5.1 General Restrictions
You must install Extended Services before you install any components of LAN
Server V2.0. In addition, you must apply any Extended Services patches prior to
any installation of LAN Server V2.0 components.
Note
If you plan to install both Extended Services Database Manager and any
components of LAN Server V2.0, please BE SURE to read the Database
Manager restriction in 5.4.2, estrictions for Functions/Features Available in
this Driver?on page 25 under "Database Copy Protection".
5.2 Extended Services Restrictions
? INSTALLATION AND CONFIGURATION
?If you are planning to install this driver over the SE 1.30.1 or SE 2.0 base
operating system, you must reformat your boot partition and re-install your
base operating system. You must also follow the directions to remove
Extended Services code from any previous driver by following the
instructions in 6.1, 﨎efore You Install Extended Services?on page 38.
?After following instructions in 6.1, 﨎efore You Install Extended Services?
on page 38, the first installation of this driver is initiated with the
A:ESINST. The initial A:ESINST to install this driver cannot be followed
by a second A:ESINST without reformatting and reinstalling the base
operating system. If your initial installation fails for some reason, and you
must issue another A:ESINST, you may be able to perform the A:ESINST
again by taking the following steps.
? For the following files, issue ATTRIB filename -R, and then erase the
file.
? in the root directory of the boot drive, IBMLVL.INI
? in \MUGLIB, SYSLEVEL.MUG
? in \OS2\INSTALL, ESINST.HST
?COPY x:\OS2\INSTALL\CONFIG.ES x:\CONFIG.SYS, where x is
the logical drive letter for the boot drive
?Press CTRL-ALT-DEL to reboot the PC
?After you complete steps for installation of Communications Manager, you
are instructed to stop active features and press CTRL-ALT-DEL to reboot
Restrictions 20
IBM CONFIDENTIAL Extended Services Driver S1A246 21 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
the system. Instead of pressing CTRL-ALT-DEL, you should use
Shutdown to stop the system. To do so, bring up a menu by pressing the
right mouse button while the pointer is not on any object (i.e on blank
space) on the workplace desktop. Then select Shutdown from the menu to
stop the system and reboot again.
? If you have installed Communications Manager with a feature that requires
APPC/APPN support and you receive the following message, you should
use the REINST command to re-install the Communications Manager
configuration file for the feature. The re-installation will cause your
CONFIG.SYS to be updated correctly.
ACS0112C - Communications Manager - Originator APPC - Critical file
CONFIG.SYS(DEVICE=C:\CMLIB\APPN\CMKFMDD.SYS) was not
found or was modified or damaged: error type 0002.
# ?Multiple Communications Manager ICONs will be installed on the
# workplace desktop with this OS/2 2.0 driver. Duplicates can be ignored.
# ?With this OS/2 2.0 driver, the ICONs in the Communications Manager
# group, Database Manager group, and Extended Services group will run
# together. To arrange them so that the lettering is legible, you can click with
# the right mouse button on a blank area of the grouping and select Arrange
# from the menu which displays.
? REQUIREMENT TO EXIT CM BEFORE STOPPING THE SYSTEM
?If you have entered the Communications Manager Subsystem Management
or Advanced Configuration panels you MUST always select to Exit
Communications Manager before attempting a Desktop Shutdown or
CTRL-ALT-DEL. If you do not exit Communications Manager,
CTRL-ALT-DEL and Shutdown may be disabled.
In some cases, you may experience a trap d when exiting Communications
Manager with either the Exit when Complete or Exit Immediately options.
If the CSLIM is 1bffffff, this is a known problem. You can hit enter to
continue the exit process.
5.3 Communications Manager Restrictions
# ? COMMUNICATIONS MANAGER PANELS AND OPERATION WITH
# A MOUSE
# ?With the OS/2 2.0 operating system, the mouse may be inoperable on some
# of the Communications Manager panels. The keyboard may be used to
# select options. For example, to go to the CM Configuration panels, press
# F10 from the CM main menu and select Advanced and then select
# Configuration.
? PROGRAMMABLE CONFIGURATION
?If you plan to use the APPN functions of Programmable Configuration,
you MUST install the patches as described in 6.0, 﨓xtended Services
Installation?on page 38.
?If you plan to use Programmable Configuration, you should always change
the directory to \CMLIB prior to executing your Programmable
Restrictions 21
IBM CONFIDENTIAL Extended Services Driver S1A246 22 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Configuration program. If you do not change to the \CMLIB directory,
your configuration file may not verify correctly, or you may receive errors
for files not found.
?The APPN feature of Programmable Configuration should not be used to
perform LIST and GET, but may be used to perform ADD and PUT.
? FUNCTIONS INVOLVING APPC/APPN SUPPORT
?If you plan to use a Communications Manager function which requires
APPC/APPN support (e.g. 5250 WSF, 3270 emulation over SDLC or
Token ring, APPC, CPI-C, SNA Gateway), you MUST install the patches
as described in 6.0, 﨓xtended Services Installation?on page 38.
?MIGRATION WARNING. If you you plan to use a Communications
Manager function which requires APPC/APPN support (e.g. 3270
non-DFT, 5250 WSF, APPC, CPI-C, SNA Gateway), you must ensure
that your machine is configured with a unique Fully Qualified CP Name.
This name is created under-the-cover during Extended Services
installation/configuration upgrade based on the Network Name and PU
name in your current configuration file. Be aware that a naming collision
means that you may not be able to establish a 3270 session through an
Extended Services SNA Gateway to a host, be able to establish a 5250
session to an AS/400, or be able to activate a link to another APPN node.
If you encounter these problems after installation, use Advanced
Configuration/SNA Feature Profiles/SNA network definitions/ Local Node
Characteristics to change the Local Node Name to a unique name.
? 5250 WORKSTATION FEATURE
?In order to use the 5250 Workstation Feature in this driver, you MUST
install the patches as described in 6.0, 﨓xtended Services Installation?on
page 38.
? 3270 DFT CONNECTIVITY FOR A PC AT
?In order to use the 3270 DFT connectivity on a PC AT in this driver, you
MUST install the patch for 3270 DFT as described in 6.0, 﨓xtended
Services Installation?on page 38. This patch is NOT required if you are
running on a PS/2.
# ? 3270 EMULATION ON MODEL 95 WITH MULTIPLE ADAPTERS
# ?On OS/2 2.0, when running 3270 emulation, BOTH DFT and non-DFT
# connectivities on a PS/2 Model 95, selecting to stop and restart the
# non-DFT sessions will cause all sessions to go away.
? CONFIGURATION FILE MANAGER
?If you plan to use the Configuration File Manager, you MUST install the
patches required as described in 6.0, 﨓xtended Services Installation?on
page 38.
? 3270 HOST GRAPHICS
?In order to use 3270 Host Graphics with Extended Services, your host
system must have the following PTFs applied. If they are not applied you
may experience problems with clipping, printing and plotting.
Restrictions 22
IBM CONFIDENTIAL Extended Services Driver S1A246 23 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
?For MVS, PTFs UL89380, UN04644
?For VM/SP, PTFs UL89381, UN04645
?For VM/XA SP, PTFs UL89382, UN03715
?For DOS/VSE, PTFs UL89383, UN04646
?When running on the OS/2 2.0 operating system, the PF5=SAVE PIF
option under the GDDM output function is not working correctly. To
work around this problem, you should take the following steps.
?From the OS/2 full screen prompt, type GQFTRACE.
?From the window displayed, select Output from the Action bar and
select File (rather than screen).
?From that same window, select Options and select File Close/Open
mode.
?From your host session, type ADMCHART. You'll receive a pop up,
and you should select All Set.
?At this point, you should be able to select PF5=SAVE PIF.
?
DMA ASYNC
?The DMA Async support for line speeds up to 64Kbps is not functioning
correctly on the PS/2 Model 90 and Model 95. If you are using a PS/2
Model 90 or 95 with ASCII emulation or ACDI, you can still use line
speeds up to 19.2 Kbps. You should add a REM statement to your
CONFIG.SYS as follows.
?REM DEVICE=x:\CMLIB\ASYNCDDC.SYS (where x is the logical
drive on which Communications Manager is installed)
?
LAN ADAPTER AND PROTOCOL SUPPORT
?When using the IBM Token Ring 16/4 Adapter or the IBM Token Ring
16/4 adapter /A, and the adapter is set for 64K paged, a user application
cannot take advantage of the 64K.
? REMOTE OPERATIONS (ROP) SERVICE
?Occasionally the CTRL-ALT-DEL and Desktop shutdown may fail to
work after running ROP Service for an extended period of time on a system
formatted with HPFS running OS/2 SE 1.0. In this case, the PC must be
powered off. This can cause a significant delay in startup when the PC is
restarted.
# ?On OS/2 2.0, ROP service cannot be started by clicking on the Remote
# Operations Icon. Instead, the following steps must be followed to start the
# router and ROP service:
# From an OS/2 full screen command prompt, type the following
# rtr /desktop
# roppm /fullscreen /nologo
# ? EHLLAPI VIRTUAL DEVICE DRIVER (VDD)
Restrictions 23
IBM CONFIDENTIAL Extended Services Driver S1A246 24 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
# ?With this OS/2 2.0 driver, the EHLLAPI Virtual Device Driver MUST not
# be used. Inclusion of the EHLLAPI VDD statement in CONFIG.SYS will
# result in the inability to start any DOS sessions. If the EHLLAPI VDD is
# to be used, it should be used with the OS/2 2.0 driver level 6.605.
# ? ACDI REDIRECTION
# ?With this OS/2 2.0 driver, ACDI Redirection does not function correctly. If
# you are planning to use ACDI redirection, you should use OS/2 2.0 level
# 6.605.
5.3.1 Communication Manager Publications Restrictions
Workstation Installation Guide
The following APPN information is missing:
?
a description of the NS/2 files which may need to be backed-up before you
format your fixed disk at installation;
? installation and upgrade considerations for NS/2;
? the SNA networking defaults used by BCS.
Communication Manager Host Connect Reference
? incomplete APPN (NS/2) examples for the AS/400 chapter
Example Scenarios
? no APPN (NS/2) information.
? 5250 Emulation steps have had minimal testing.
? X.25 steps have had minimal testing.
Network Administrator's Guide
?
There is missing conceptual information and product description.
? The naming conventions are missing several names and details about the names.
? Operating system features are missing from the Operating System steps.
? Several of the Communication Manager steps are missing blanks for recording
information.
? Database steps are missing planning information for Remote Data Services
(RDS) and Distributed Database Connection Services (DDCS).
? The LAN step is missing cross-references to the LAN planning guides.
? The summary Worksheets at the back of the book are incomplete. Please refer
to the full worksheets found in the Workstation Installation Guide, the
Communication Manager Configuration Guide, and the LAN Network
Administrator's Reference Volume 1: Planning and Installation.
Restrictions 24
IBM CONFIDENTIAL Extended Services Driver S1A246 25 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.4 Database Manager Restrictions
5.4.1 Functions/Features NOT Available in this Driver
? Advanced Backup/Restore (Backup to non-standard devices)
5.4.2 Restrictions for Functions/Features Available in this Driver
The following restrictions/limitations apply to Database Manager for this driver.
These restrictions will be corrected in future drivers unless otherwise noted.
Migration of EE 1.1, 1.2 and 1.3 Databases
Migration of EE 1.1, 1.2 and 1.3 Databases
Migration of existing EE 1.1, EE 1.2 and EE 1.3 databases IS SUPPORTED in
this driver. Please refer to 8.1.1, 﨧igration of Databases?on page 55 for
information about migration of these databases. Be SURE to backup all
databases BEFORE you install this driver.
Migration of existing Extended Services databases, however, IS NOT
SUPPORTED in this driver. See below, under "Migration of Extended Services
Databases" for information about how to preserve these databases for use with
this driver.
Migration of Extended Services Databases (from previous driver)
Restrictions 25
IBM CONFIDENTIAL Extended Services Driver S1A246 26 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
WARNING
Migration of existing Extended Services databases (from the previous
Extended Services driver) is NOT SUPPORTED in this driver!
BEFORE YOU INSTALL THIS DRIVER, do the following steps if you want
to use existing Extended Services databases:
1. Export all tables and QM objects.
2. Save any view definitions that you will want to use with the new
version of the database.
3. Drop the database.
AFTER YOU INSTALL THIS DRIVER, do the following:
1. Create a new Extended Services database.
2. Import the tables and QM objects.
3. Redefine any views that you want to use.
4. Re-bind any existing access plans that you intend to use.
You will need to export all objects and drop the databases before you install each
new driver. Any updates you make to the databases using early driver code will
be lost unless you export your objects before installing each driver.
Database Copy Protection
If you plan to install any of the LAN Server V2.0 components on the same machine
on which Extended Services is installed, it is STRONGLY URGED that you install
the LAN Server V2.0 component(s) BEFORE you create or migrate any databases
using this Database Manager driver.
If you do create or migrate databases using this driver, and you then want to install
LAN Server V2.0, you MUST turn "Copy Protection" off for these databases
BEFORE you install the LAN component(s). If you do not, you will receive an
SQL5122N error ("Machine Dependent Check") when issuing a Start Using
Database, and the database will be unusable.
You can change this database parameter by using Database Tools, if installed, or the
Command Line Interface.
General Restrictions
? A message indicating a code page conversion error occurs sometimes when a
Start Using Database is issued. This may happen if database has been used
several times. Reboot the system if this occurs.
? If you do a Control-Break during a REORG, a Trap D will occur.
? REXX stored procedures do not work.
Restrictions 26
IBM CONFIDENTIAL Extended Services Driver S1A246 27 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? Using the DBM Alter Table command may cause a looping situation that will
appear as a hang.
? If a process is killed from a client/server, a Trap D will occur.
?
There is no support on a LAN server for redirected disk drives.
? If you get an SQL1084 error, use the message text for message SQL0956.
NETBIOS Restrictions
? When Extended Services and LAN Server are both installed and both running
concurrently, the value set for "maximum names" is lower than needed. Edit the
PROTOCOL.INI file NETBEUI section which will contain the "maximum
names" value. Or select "LAN Adapter and Protocol Support" from the
Communications Manager Advanced Configuration menu. The value should
be changed from 17 to 21. Then reboot.
Remote Data Services Restrictions
# ? Bind problem with EE 1.2/1.3 Database clients using Query Manager
# EE 1.2/1.3 database clients using Query Manager to remotely access a database
# on an Extended Services database server will fail with an SQL0040N error ("An
# error occurred on one or more bind files in list 'QRWSBND4.LST'. The
# following files were not found: "3,3".), the first time the database is accessed.
# Subsequent attempts to open the same database from a 1.2/1.3 client will
# receive an SQL0805N error ("NULLID.QRWS2B" is not found.).
? Remote Data Services heap size on the server is too low. Increase the value
from 2 to at least 3.
? You must issue a STARTDBM at the database server before any database
clients can connect to a database. If you do not, the database client will hang
when attempting to connect to a database.
DOS Database Client/DOS Windows Database Client Restrictions
# ? You CANNOT run any DOS Database client or DOS Windows Database client
# applications in OS/2 's 'DOS Windows Full Screen', 'DOS Window' or 'DOS
# Full Screen' command prompt environments.
? Terminating an application program on a client workstation without issuing a
COMMIT and Stop Using Database may cause the client to hang.
Roll Forward Recovery Restrictions
Roll Forward Recovery has not had sufficient testing at this time to withstand
extensive usage. It is included so that users may get familiar with the interfaces and
function capabilities. If used, please remain within the restrictions below. These
items will be corrected in future drivers.
? In order to do a ROLLFORWARD STOP you must have the log files
available that existed when the backup was taken.
? In most cases, a ROLLFORWARD to a point-in-time will not work correctly.
The ROLLFORWARD should be run to the end of the logs ( time =
9999/12/31-23:59:59)
? The USER EXIT option is not supported.
Restrictions 27
IBM CONFIDENTIAL Extended Services Driver S1A246 28 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? When using the LOG RETAIN option, it is recommended that you increase
the size of the log files (logfilsiz) and the number of log files (logprimary) as
much as possible. A TRAP D may occur after multiple log files have been used.
? BEFORE installing the operating system and Extended Services, the databases
must be backed up. If MIGRATE database fails, the database cannot be used
and will require a RESTORE of your backed up database.
? The logpath cannot be changed after turning the LOG RETAIN option 'ON'.
If a new logpath is desired, change to the new logpath, perform a START
USING DATABASE to activate the configuration change, perform a STOP
USING DATABASE, and then turn the RETAIN option 'ON'.
? You cannot ROLLFORWARD through a CREATE INDEX, DROP
INDEX, CREATE INDEX. It is recommended that no indexes exist when
using ROLLFORWARD.
5.5 LAN Server Version 2.0 Hardware Restrictions
5.5.1 Bridge Considerations
If you intend to run a bridge program on a slow workstation (i.e. IBM PC AT,
Family I), ensure that the parameter server value in the bridge configuration
program is set to No. If the parameter server value is set to Yes, a slow or
congested bridge machine will be unable to respond quickly enough to workstations
on the network, preventing the workstations' adapters from opening. Workstations
that cannot enter the LAN will display an message. error opening
adapter
5.5.2 Adapter Considerations
If you have an IBM Token-Ring Network 16/4 Adapter or IBM Token-Ring
Network 16/4 Adapter /A with a microcode level of C24550, your
sessions may be disconnected due to insufficient adapter transmit
buffers. To correct this problem you may do one of the following:
? Replace your adapter with Engineering Change (EC) level ECA066.
? Use the LAN Adapter and Protocol Support full-screen interface
to change the Number of adapter transmit buffers parameter
for your network adapter card from the default of 1 to 2.
5.5.3 Multiple Adapter Considerations
? IBM PC Network adapters cannot share interrupt levels, therefore, you must
ensure that other adapters on the workstation do not have the same interrupt
levels as your IBM PC Network adapters. The valid interrupt levels for an
IBM PC Network adapter are 2 and 3. Remember that in Micro Channel
workstations, interrupt level 9 is treated the same as an interrupt level of 2. If
Restrictions 28
IBM CONFIDENTIAL Extended Services Driver S1A246 29 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
required, use a Reference diskette to view or change interrupt levels for your
adapters.
? The 3270 Connection Adapter for 3174 Peer Communications can only use an
interrupt level of 2. To avoid conflict with an IBM PC Network adapter, you
must change the default interrupt level on the IBM PC Network adapter from 2
to 3.
? An important consideration with multiple adapters is the amount
of total RAM used by the various adapters. The total RAM used by
your adapter cards, including other hardware adapters (for example,
displays or SCSI drives) must not exceed 128KB. If this limit is
exceeded, the network may not be able to start. To calculate your
RAM usage, see the IBM OS/2 LAN Server Version 2.0 Network Administrator
Reference Volume 1: Planning and Installation for RAM requirements on
supported adapters. To this total, add any RAM used by other hardware as
indicated by the manufacturer's documentation.
? When installing either a IBM Token-Ring Network Adapter /A or an
IBM PC Network Adapter/A concurrently with a 3270 Connection
Adapter in a Micro Channel workstation, it should be located in a
higher numbered slot than the 3270 Connection Adapter.
?
Do not mix 8-bit and 16-bit adapters in the same workstation unless
they are at least 128KB apart in address range.
5.5.4 Remote IPL Adapter Considerations
The following adapter restrictions apply to the Remote IPL service:
? If multiple LAN adapters are installed in a remote IPL requester, only one of
the adapters can be configured for the Remote IPL service.
5.6 LAN Server Version 2.0 Server Restrictions
5.6.1 General System Caveats
If installing both extended services and LAN Server, you must install Extended
Services before installing LAN Server.
This release of LAN Server 2.0 may be installed under SE Manufacturing level
# 1.30.1, (16 BIT). The server may also be installed under OS/2 driver level 6.167, (32
# BIT). We recommend running the server on SE 2.0 for evaluation purposes only.
5.6.2 Restrictions and Special Considerations for Functional Components
Restrictions 29
IBM CONFIDENTIAL Extended Services Driver S1A246 30 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Install/Config
? If installing both ES and LS, ES must be installed first.
? If you select to install DOS 5.0 you must create the DOS 5.0 diskettes before
they can be copied by the LAN Services installation/ configuration program.
Follow the instructions on the boot diskette for DOS 5.0 to create the diskettes.
?
When the server is chosen to be removed, if Local Security for 386 HPFS is
installed, the RUNPRIV.EXE command is not removed from
STARTUP.CMD. Edit the file and remove the RUNPRIV.EXE command.
# ? Do not install both the Loop Back Driver support and the LAN adapter and
# Protocol support together.
# ? The 386 HPFS will not run on OS/2 Version 2.0. When installing the LAN
# Server on an OS/2 2.0 Operating System, do not use the basic path to install;
# use the advanced path and do not install the 386 HPFS support. On the Install
# screen select "DO NOT INSTALL" the 386 HPFS. Because Local Security for
# 386 HPFS and Fault Tolerance for Fixed Disk both require 386 HPFS, you will
# not be able to install them either.
# ? When using OS/2 2.0, always take the advanced path.
# ? Anytime you do a re-install or a re-configure, you must select "Replace" for the
# LAN adapter and the protocol support.
Command Line Interface
Changes have been made to the definitions of the /PASSWORDCHG and
/PASSWORDREQ parameters of the NET USER command. These parameters
are now defined as follows:
/PASSWORDCHG:{YES | NO} Specifies whether users can change their
own password. The default is YES.
/PASSWORDREQ:{YES | NO} Specifies whether a password is required for
this user account.
YES means that a password is required.
NO means that a password is not required, but
may be used. The password restriction of
MINPWLEN is applied to any password that is
used.
NO also means that other password restrictions
such as MINPWAGE, MAXPWAGE, UNIQUEPW, and
PASSWORDCHG will not be applied to this
account.
Restrictions 30
IBM CONFIDENTIAL Extended Services Driver S1A246 31 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Full Screen Interface
? On the IBM OS/2 LAN Requester, when you select (Definitions + Users
Logon Details + Program starters) for a user, the Manage Program Starter
panel lists all applications the user may access. It highlights applications
assigned to the user except DOS public applications added to that user ID at
IBM DOS LAN Requesters. From the Manage Program Starter panel, pressing
Enter without selecting these DOS public applications will automatically
deselect them for the user. Subsequently the DOS public applications will be
removed from the user's Served Applications panel the next time the user logs
on at an IBM DOS LAN Requester.
# ? From the OS/2 LAN Requester Full Screen Interface, if the number of users
# defined in the domain is more than 875, selecting one of the following actions
# will display the NET9808E error panel:
# 1. Select Definitions + Access Control + User List to manage Access
# Control Profile User List.
# 2. Select Definitions + Applications + Program Starters + Add to Add
# Applications to Program Starters.
# 3. Select Definitions + Applications + Program Starters + Delete to Delete
# Applications from Program Starters.
# Bring up User Profile Management Services (UPM) and reduce the list to fewer
# than 875 users by deleting users you no longer need and try the action again.
?
# If your base system is OS/2 Version 2.0, the Online Reference is not available
# from the LAN Requester Full Screen Interface at this time. However, you can
# view the Online Reference by issuing "view A3ALANOR.INF" from the OS/2
# prompt.
# Please do not select Utilities + Reference information, or press F5=Reference
# on any help panel.
# Selecting Utilities + Reference information, or pressing F5=Reference on a
# help panel will cause the following error panel to appear:
# "ROIVIEW.EXE
# SYS2070: The system could not demand load the application's
# segment. ROIVIEW -> HELPMGR.30 is in error. For additional
# detailed information also see SYS182.
# End program/command/operation
# Display help"
# Press Enter to End program/command/operation and select LAN Requester
# from the Task List panel to return to the LAN Requester Full Screen Interface.
# ? Copying files from one drive to another using the Drives folder is not
# functioning. Use the OS/2 and DOS command prompts instead.
# ? To make new files show up, select refresh on a folder.
Restrictions 31
IBM CONFIDENTIAL Extended Services Driver S1A246 32 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
HPFS/386
Local Security
? The 386 HPFS local security essentially supersedes Print Manager's local
security. When a workstation with the 386 HPFS local security is started, one
must log on as either an administrator or a print operator in order for the Print
Manager window to come up and for the Spooler to be enabled. If an
administrator or a print operator is not logged on at startup time, the Print
Manager can be started with one of the following ways:
?Make sure that the C:\PRIVINIT.CMD file (or the file specified by the
PROTSHELL= line of the CONFIG.SYS file) contains the line:
SPOOL.EXE. In this case, the Print Manager will come up and will be
enabled at every workstation restart.
?After the workstation is started, perform the following steps:
?log on locally an an administrator
?enter "PRIV SPOOL" at the command prompt
? If you do not log on with sufficient privilege or with sufficient access
permission, some applications may return error messages that do not indicate
access denied as a cause for the error. Try logging on as an administrator to see
if you have insufficient access permission or insufficient privilege for that action.
Access Control Profiles: Drive level access control profiles cannot be created on
HPFS/386 drives.
# Remote IPL (RIPL): The 32 bit remote IPL of OS/2 2.0 is not currently available
# for Token Ring, PC NET, or ETHERNET.
DOS LAN Requester / Windows
Windows: MS Windows without network support installed will always print to a
local printer, even if the LPT port is "net used" to a remote printer.
Maximizing Memory Utilization with DOS 5.0: (This is not in the PUBS for this
driver.) DOS 5.0 can make more memory available to applications than earlier
DOS versions. One way this is accomplished is by DOS being loaded in the first
64KB of extended memory, called the high memory area (HMA). HMA is
available on workstations with a 286 (or greater) processor with at least 1MB of
memory. Most systems also have 384KB of space called the upper memory area.
DOS can store information in this upper memory area on workstations with 386 (or
greater) processors and extended memory. DOS 5.0 can take advantage of available
memory by installing various memory managers, such as HIMEM and EMM386.
Refer to your DOS 5.0 documentation for more information about memory and
memory managers.
# DOS LAN Requester can take advantage of the high memory area (HMA) and
# upper memory blocks (UMB) by using the NET START command or the
# DOSLAN.INI file to have DOS 5.0 load the network components into UMBs.
# The NET START parameter in /UMB. This parameter is Extended Memory
# Adapter (XMA) card and a memory manager that supports upper UMBs.
/UMB can be used in combination with /EMS or /HIM. If /UMB is used in
combination with either of these parameters, the network first tries to load all code
Restrictions 32
IBM CONFIDENTIAL Extended Services Driver S1A246 33 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
into the UMB area. If all network components do not fit, then components are
loaded into other available memory specified by /HIM or /EMS. Conventional
memory may be reduced if all network components do not fit into the UMB area.
External Interface
Disk Fault Tolerance:
? Most data corruption problems have been fixed in this driver. The potential for
data corruption in high stress environments still exists.
? Do not attempt to command line "FORMAT" a currently mirrored drive to the
FAT file system.
? Do not create more than 24 disk partitions (including mirrors).
? In a system with SCSI drives, if it appears that your system is "hanging" forever
on reads/writes or you have excessive errors on SCSI drives, please be sure your
SCSI adapters are terminated properly. The following information will help you
do so:
?A SCSI card has one bus, which extends internally and externally. Each
end must be terminated exactly once. The different drives terminate
differently.
?If no drives are attached to a card internally, then a card edge terminator is
installed on the gold tabs at the top of the card. If no drives are attached
externally, then on the IBM SCSI adapter with cache an external
pin-in-socket terminator is used. On an IBM SCSI adapter with no cache
EITHER that terminator is used OR the on-board terminator near the
external connector is inserted.
?When drives are attached (internally, externally, or both), each cable must
be terminated at the end. The black drives (60, 80, 120, 160) have
terminators on the underside of the drive and usually have white slips of
paper attached to them. The gold (>300 MB) drives have a terminator
that gets inserted between the cable and the connector on the drive.
Generic Alerter Service
User Note:
# The error log entry in the SYSLOG is not readable; however, the alert entry is
# readable. This is not a Generica Alerter Service restriction as the alerts can be sent
# to NETVIEW.
Messages
# ? The filename "NETWKSTA.SYS" in messages is the incorrect name. The
# name should be "NETWKSTA.200".
5.6.3 Restrictions and Special Considerations for Device Drivers
? When using PCNET, the default in the IBMCOM\ PROTOCOL.INI in the
MAC section for IBMNETA_NIF needs to be changed as follows:
RECEIVEBUFFERS = 6 should be RECEIVEBUFFERS = 8
Restrictions 33
IBM CONFIDENTIAL Extended Services Driver S1A246 34 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.6.4 Restrictions and Special Considerations for Commands
? NETCOPY or any other type of copy command (i.e. Xcopy) will trap after a
long period of repeated use.
5.7 LAN Server Version 2.0 Requester Restrictions
5.7.1 General System Caveats
If installing both extended services and LAN Server, you must install Extended
Services before installing LAN Server.
# This release of LAN Requester can be run under SE driver manufacturing level
# 1.30.1,(16 BIT), or SE 2.0 driver level 6.167, (32 BIT).
Please log on before attempting LAN functions.
Install/Config
? If installing both ES and LS, ES must be installed first.
# ? When using OS/2 2.0, always take the advanced path.
# ? Anytime you do a re-install or a re-configure, you must select "Replace" for the
# LAN adapter and the protocol support.
Command Line Interface
Changes have been made to the definitions of the /PASSWORDCHG and
/PASSWORDREQ parameters of the NET USER command. These parameters
are now defined as follows:
/PASSWORDCHG:{YES | NO} Specifies whether users can change their
own password. The default is YES.
/PASSWORDREQ:{YES | NO} Specifies whether a password is required for
this user account.
YES means that a password is required.
NO means that a password is not required, but
may be used. The password restriction of
MINPWLEN is applied to any password that is
used.
NO also means that other password restrictions
such as MINPWAGE, MAXPWAGE, UNIQUEPW, and
PASSWORDCHG will not be applied to this
account.
Restrictions 34
IBM CONFIDENTIAL Extended Services Driver S1A246 35 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Full Screen Interface
? On the IBM OS/2 LAN Requester, when you select (Definitions + Users +
Logon Details + Program starters) for a user, the Manage Program Starter
panel lists all applications the user may access. It highlights applications
assigned to the user except DOS public applications added to that user ID at
IBM DOS LAN Requesters. From the Manage Program Starter panel, pressing
Enter without selecting these DOS public applications will automatically
deselect them for the user. Subsequently the DOS public applications will be
removed from the user's Served Applications panel the next time the user logs
on at an IBM DOS LAN Requester.
# ? From the OS/2 LAN Requester Full Screen Interface, if the number of users
# defined in the domain is more than 875, selecting one of the following actions
# will display the NET9808E error panel:
# 1. Select Definitions + Access Control + User List to manage Access
# Control Profile User List.
# 2. Select Definitions + Applications + Program Starters + Add to Add
# Applications to Program Starters.
# 3. Select Definitions + Applications + Program Starters + Delete to Delete
# Applications from Program Starters.
# Bring up User Profile Management Services (UPM) and reduce the list to fewer
# than 875 users by deleting users you no longer need and try the action again.
# ? If your base system is OS/2 Version 2.0, the Online Reference is not available
# from the LAN Requester Full Screen Interface at this time. However, you can
# view the Online Reference by issuing "view A3ALANOR.INF" from the OS/2
# prompt.
# Please do not select Utilities + Reference information, or press F5=Reference
# on any help panel.
# Selecting Utilities + Reference information, or pressing F5=Reference on a
# help panel will cause the following error panel to appear:
# "ROIVIEW.EXE
# SYS2070: The system could not demand load the application's
# segment. ROIVIEW -> HELPMGR.30 is in error. For additional
# detailed information also see SYS182.
# End program/command/operation
# Display help"
# Press Enter to End program/command/operation and select LAN Requester
# from the Task List panel to return to the LAN Requester Full Screen Interface.
# ? Copying files from one drive to another using the Drives folder is not
# functioning. Use the OS/2 and DOS command prompts instead.
# ? To make new files show up, you must select refresh on a folder.
Restrictions 35
IBM CONFIDENTIAL Extended Services Driver S1A246 36 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
External Interface
? In a system with SCSI drives, if it appears that your system is "hanging" forever
on reads/writes or you have excessive errors on SCSI drives, please be sure your
SCSI adapters are terminated properly. The following information will help you
do so:
?A SCSI card has one bus, which extends internally and externally. Each
end must be terminated exactly once. The different drives terminate
differently.
?If no drives are attached to a card internally, then a card edge terminator is
installed on the gold tabs at the top of the card. If no drives are attached
externally, then on the IBM SCSI adapter with cache an external
pin-in-socket terminator is used. On an IBM SCSI adapter with no cache
EITHER that terminator is used OR the on-board terminator near the
external connector is inserted.
?When drives are attached (internally, externally, or both), each cable must
be terminated at the end. The black drives (60, 80, 120, 160) have
terminators on the underside of the drive and usually have white slips of
paper attached to them. The gold (>300 MB) drives have a terminator
that gets inserted between the cable and the connector on the drive.
DOS LAN Requester / Windows
Windows: MS Windows without network support installed will always print to a
local printer, even if the LPT port is "net used" to a remote printer.
Maximizing Memory Utilization with DOS 5.0: (This is not in the PUBS for this
driver.) DOS 5.0 can make more memory available to applications than earlier
DOS versions. One way this is accomplished is by DOS being loaded in the first
64KB of extended memory, called the high memory area (HMA). HMA is
available on workstations with a 286 (or greater) processor with at least 1MB of
memory. Most systems also have 384KB of space called the upper memory area.
DOS can store information in this upper memory area on workstations with 386 (or
greater) processors and extended memory. DOS 5.0 can take advantage of available
memory by installing various memory managers, such as HIMEM and EMM386.
Refer to your DOS 5.0 documentation for more information about memory and
memory managers.
# DOS LAN Requester can take advantage of the high memory area (HMA) and
# upper memory blocks (UMB) by using the NET START command or the
# DOSLAN.INI file to have DOS 5.0 load the network components into UMBs.
# The NET START parameter in /UMB. This parameter is Extended Memory
# Adapter (XMA) card and a memory manager that supports upper UMBs.
/UMB can be used in combination with /EMS or /HIM. If /UMB is used in
combination with either of these parameters, the network first tries to load all code
into the UMB area. If all network components do not fit, then components are
loaded into other available memory specified by /HIM or /EMS. Conventional
memory may be reduced if all network components do not fit into the UMB area.
Restrictions 36
IBM CONFIDENTIAL Extended Services Driver S1A246 37 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.7.2 Restrictions and Special Considerations for Device Drivers
? When using PCNET, change the \IBMCOM|PROTOCOL.INI in the MAC
section for IBMNETA_NIF as follows:
RECEIVE BUFFERS = 6 should be RECEIVEBUFFERS = 8
5.7.3 Restrictions and Special Considerations for Commands
? NETCOPY or any other type of copy command (i.e Xcopy) will trap after a
long period of repeated use.
5.8 LAN Server Version 2.0 Publications Restrictions
? Pagination may not be final for some of the publications.
? Memory and fixed-disk requirements in the "Network Administrator Reference
Volume 1: Planning and Installation" will be available in the final version.
? On page 13-3 of the "Network Administrator Reference Volume 3: Network
Administrator Tasks", the discussion on multiple adapter support for Remote
IPL is not relevant to this release and will be removed in the final version.
? The information in the "LAN Server V 2.0 Quick Reference" is for 16-bit only.
Restrictions 37
IBM CONFIDENTIAL Extended Services Driver S1A246 38 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
6.0 Extended Services Installation
During the installation of the IBM Extended Services for OS/2, pressing F1=HELP
on menus and pop-ups will provide additional information to guide you through the
process.
Installation Notice
This driver has a known problem which causes the installation to flip back and
forth between screens while files are being transferred from diskette to the hard
disk. Do not let this confuse you; you will eventually receive the correct prompt,
panel or menu.
6.1 Before You Install Extended Services
? Before you install Extended Services, consider the following three cases:
1. If you have a previously installed version of Extended Edition version 1.30.1
(EE 1.30.1), you can install Extended Services over it.
If you install over EE 1.30.1, you may also select to install with an EE
1.30.1 configuration file, and the file will be upgraded automatically during
the installation process.
If you install a Database Client over an existing EE 1.30.1 Database Client:
?NETBIOS will be installed
?SQLLOO definitions will be removed from the configuration file
(assuming you are installing using Advanced Install and specify the EE
1.30.1 XXX.CFG file), NETBIOS will be defined (if not already
present), and a default NETBIOS configuration will be created in
XXX.INI (the LAN configuration file associated with the XXX.CFG
file).
?Database Manager Workstation (Node) Directory entries will be
converted from SQLLOO to NETBIOS.
2. If you have a previously installed version of Extended Services (earlier
driver), you MUST do the following:
a. If Database Manager is currently installed, and you wish to preserve
existing databases for use with this driver, follow the procedure in 5.4.2,
estrictions for Functions/Features Available in this Driver?on
page 25 under "Database Migration" before continuing to the next step.
b. Copy all files on the boot drive that you wish to preserve
c. Re-install one of the following base operating systems (and re-format
the boot drive during the installation):
?For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required.
# ?For a 32-bit base, SE V2.0 driver level 6.167 is required.
Extended Services Installation 38
IBM CONFIDENTIAL Extended Services Driver S1A246 39 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
d. Re-boot and bring up your newly installed operating system
e. Remove all Extended Services components that were previously
installed on other drives, by doing one of the following:
1) Reformat the partition(s) where Extended Services components are
currently installed (after copying any files you wish to keep)
--- or ---
2) Manually (or by using File Manager) erase all files (including
"read-only" files) in the following directories, their subdirectories,
AND the directories themselves:
?\sqllib
?\cmlib
?\dbdrqlib
3. If neither of the above cases apply, you must install one of the following
operating systems as your base (and reformat the boot drive during the
installation):
?For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required.
# ?For a 32-bit base, SE V2.0 driver level 6.167 is required.
? If you are installing Extended Services with the OS/2 SE 2.0 base operating
system you MUST select to INSTALL ALL FEATURES of the base operating
system.
? Before you install Extended Services, refer to section 5.0, estrictions?on
page 20 for the limitations on Communications Manager and Database
Manager.
?
If you have Database Manager databases from EE 1.1, EE 1.2 or EE 1.3 that
you wish to use with this driver, you will be able to migrate them for use with
Extended Services. Refer to 8.1.1, 﨧igration of Databases?on page 55 for
more information about database migration. Make SURE you backup all
databases BEFORE installing this driver.
# ? At the end of the installation process, if you wish to view the installation history
# file, the file can be browsed/printed by entering "VIEWLOG" at the OS/2
# command line. You can also select "View Install History File" from the
# Extended Services group on workplace desktop. (see 6.2.4, 蘒nstallation Tools?
# on page 41 for more information on this group).
? The use of certain mouse device drivers may not be compatible with the
Communications Manager SDLC or Async device drivers, particularly on the
PC AT and PC XT/286. This is due to hardware interrupt conflicts. For PS/2's
mouse device drivers which support interrupt sharing can work simultaneously
with the SDLC and/or Async device drivers.
The following is a table of the interrupt levels used for the most common
communications adapters. You should also insure that the interrupt level used
by an installed mouse device does not conflict with the levels used by your
communications adapters. For an interrupt level to be sharable, both device
drivers using the interrupt must be designed for interrupt sharing. Interrupt
sharing is supported on PS/2's only.
Extended Services Installation 39
IBM CONFIDENTIAL Extended Services Driver S1A246 40 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Table 2. Communication Adapter Interrupt Levels
Adapter Interrupt Levels Comments
DFT 2 Sharable on PS/2s
SDLC 3 and 4 Sharable on PS/2s (if selected)
ASYNC 3 or 4 Sharable on PS/2s
TRN 2, 3, or 7 XT/286 or AT
TRN 2, 3, 10, or 11Sharable on PS/2s
PCN 2 or 3 Sharable on PS/2s
6.2 Extended Services Installation Concepts
6.2.1 Initial Installation
ESINST
For an initial install (first time), Extended Services installation is started by inserting
the Extended Services diskette 1 and typing "A:ESINST" at the OS/2 Command
prompt, which will then display the "Extended Services Copyright Panel". This
invocation should only be used for your initial installation of Extended Services.
During initial install (ESINST), you may choose to install using one of three
installation options:
? Basic Configuration Services
? Advanced Installation
? Custom Installation (requires a Custom Build diskette)
6.2.2 Follow-on Installation
REINST
# After initially installing, Extended Services features can be added/removed through
# reinstall (REINST) from command line, or by selecting "Add or Remove Features"
# from the Extended Services group on workplace desktop. (see 6.2.4, 蘒nstallation
# Tools?on page 41 for more information on this group).
REINST is invoked at the OS/2 command prompt which will then display the
"Extended Services Install/Remove Menu". Reinstall should be used to install any
configuration file that was created/modified through Advanced Configuration, or to
install any additional feature or any new components after initial installation.
Extended Services Installation 40
IBM CONFIDENTIAL Extended Services Driver S1A246 41 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
ESCFG
# After initially installing, if you need to modify an existing Basic Configuration
# Services file or need to create one for yourself or another user, you may use ESCFG
# or select "Basic Configuration and Installation" from the Extended Services group
# on workplace desktop. (see 6.2.4, 蘒nstallation Tools?for more information on this
# group).
ESCFG is invoked at the OS/2 command prompt which will then display the
"Extended Services Basic Configuration Services Panel". You will get the option to
install the Basic Configuration Services files you have created/changed at the end of
the processing. You can also choose not to install, but to install at a later time
using REINST.
6.2.3 Custom Build
CUSTBLD
This command is used to invoke Custom Build. Custom Build creates a Custom
diskette with the selections that you have selected. This diskette will then be used
to install Extended Services on another workstation, by selecting Custom
Installation on the "IBM Extended Services Installation Options" menu during
initial install on that workstation.
6.2.4 Installation Tools
After initial installation of Extended Services, you may access installation tools by
selecting the Extended Services group from workplace desktop. You will be able to
select from the following options.
? Basic Configuration and Installation (ESCFG)
? Add or Remove Features (REINST)
? View Install History File (VIEWLOG)
? Create Custom Install Diskette (CUSTBLD)
? View Custom Build History File
? Extended Services Command Reference
6.3 Basic Configuration Services (BCS)
6.3.1 BCS Overview
BCS is designed to aid the user in doing a quick, simple installation by providing
easy-to-use Configuration Services at install time. You can use BCS to configure
and install the following features:
? 3270 Terminal Emulation
? ASCII Terminal Emulation to single host
Extended Services Installation 41
IBM CONFIDENTIAL Extended Services Driver S1A246 42 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? 5250 Work Station Feature (AS/400 or S/36)
? Database Manager using Remote Data Services
Each component has a section listing the steps to take for the BCS path. The order
you see for your prompted steps may not correspond to what is listed in this
documentation. You will be prompted to enter information unique to your
workstation during BCS configuration. Commonly used default values are provided
for other configuration parameters. Some defaults used by BCS may not be
appropriate for your particular environment, for example, the Token Ring adapter
type. However, BCS is highly recommended as a quick way to create a
configuration file at install time and to customize it with the appropriate parameter
values later via advanced configuration services.
For more information on the features supported by Basic Configuration Services,
please refer to the Extended Services Workstation Installation Guide.
Note
The configuration file created by the BCS is called a Basic Configuration File.
To modify the basic configuration file, you can either use the Basic
Configuration Services via ESCFG command OR the Communications
Manager advanced configuration services. Please note that once the Basic
Configuration File is modified by the Communications Manager advanced
configuration services, it CANNOT be used by BCS. Both basic and regular
configuration files can be used to bring up Communications Manager.
6.3.2 Steps for Using BCS During Initial Install
The steps below show you how to create a Basic Configuration file and to install
from this file. Make sure you have installed the base operating system first or have
Extended Edition version 1.30.1 installed.
1. Insert the Extended Services diskette 1 in drive A: and type A:ESINST from an
OS/2 full screen command prompt.
2. Press enter on Extended Services Installation Version 1 Copyright panel.
3. Press enter on the Welcome panel.
4. Press enter on the Introduction panel.
5. Select "Basic Configuration and Installation" from the IBM Extended Services
Installation Options menu. Insert diskettes as prompted.
6. Enter a name and an optional comment for the Basic Configuration file.
7. You will see the Basic Configuration Services main menu.
8. Install Communications Manager and/or Database Manager
? Refer to section 7.2.1, 蘒nstalling Communications Manager Using Basic
Configuration Services?on page 49
? Refer to section 8.2.1, 蘒nstalling Database Manager Using Basic
Configuration Services?on page 56
Extended Services Installation 42
IBM CONFIDENTIAL Extended Services Driver S1A246 43 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
9. Apply Patches
Appropriate Patches must be applied at this time. Refer to section 6.6,
嗀pplying Patches to the Installed System?on page 44 for information on the
patch process. This patch process must be followed to ensure you have a
working environment.
6.3.3 Using BCS After Initial Install
For information on modifying your Extended Services installation using Basic
Configuration Services, please refer to the Extended Services Workstation
Installation Guide.
6.4 Advanced Installation
Advanced Installation can be selected on an initial installation or on a follow-on
installation. It allows installation with a user defined configuration file from this or a
previous release, installation of a default configuration file, and selective installation
of additional features.
If you choose to install a user defined configuration file from a previous release, the
configuration information is automatically upgraded when you install Extended
Services.
6.4.1 Steps for Using Advanced Install During Initial Install
The steps below show you how to use Advanced Install. Make sure you have
installed the base operating system first or have Extended Edition version 1.30.1
installed.
1. Place the Extended Services diskette 1, in drive A: and type A:ESINST from an
OS/2 full screen command prompt.
2. Press enter on Extended Services Installation Version 1 Copyright panel.
3. Press enter on the Welcome panel.
4. Press enter on the Introduction panel.
5. Select "Advanced Installation" from the IBM Extended Services Installation
Options menu.
6. You will see the IBM Extended Services Install/Remove menu.
7. Install Communications Manager and/or Database Manager
? Refer to section 7.2.2, 蘒nstalling Communications Manager Using
Advanced Installation?on page 50
? Refer to section 8.2.2, 蘒nstalling Database Manager Using Advanced
Installation?on page 61
8. Apply Patches
Appropriate Patches must be applied at this time. Refer to section 6.6,
嗀pplying Patches to the Installed System?on page 44 for information on the
Extended Services Installation 43
IBM CONFIDENTIAL Extended Services Driver S1A246 44 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
patch process. This patch process must be followed to ensure you have a
working environment.
6.4.2 Using Advanced Install After Initial Install
After an initial installation, Advanced Installation can be invoked by using the
REINST command or by selecting the Add or Remove Features option from the
Extended Services Group on workplace desktop. For information on modifying
your Extended Services installation through a follow-on installation, please refer to
the Extended Services Workstation Installation Guide.
6.5 Custom Installation
For information on using Custom Installation, please refer to the Extended Services
Workstation Installation Guide.
6.6 Applying Patches to the Installed System
After your Extended Services system is installed, you must apply the necessary
patches.
6.6.1 Description of Extended Services Patches
Communications Manager Patches
? 5250 Workstation Feature
The ACS5ACS.DLL patch is required if you are planning on using the 5250
Workstation Feature in this driver. Without this patch 5250 WSF will not
function.
? LAN Adapter and Protocol Support
The NETBEUI.NIF and NETBEUI.OS2 patches are required if you are
planning on using the LAN Adapter and Protocol support in Extended Services
along with the LAN Server driver.
? Configuration File Manager
The following patches are required if you are planning to use the Configuration
File Manager in this driver. Without these patches, the CTRL-ESC key will
not function, you may experience traps, some garbled text, and problems with
help text when using the Configuration File Manager.
?COPYCFG.EXE, COPYCFG.HLP, CCF.MSG, CCFH.MSG
? Programmable Configuration
The patches below are required if you are planning to use Programmable
Configuration. Without the patches the APPN feature of Programmable
Configuration does not function correctly.
Extended Services Installation 44
IBM CONFIDENTIAL Extended Services Driver S1A246 45 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
?RCBMTD1.DLL, RCBMTD2.DLL, RCBMTD3.DLL, MAPPER.DLL,
GATEWAY.TDF, SRPI.TDF, APPN.TDF, RCBUPG.CMD
? APPC/APPN Support
The APPC.DLL patch is required if you plan to use Communications Manager
functions which require APPC/APPN support. Without this patch, you may
experience problems starting Communications Manager using a configuration
file involving APPC/APPN, or you may experience unpredictable results after
starting Communications Manager.
? 3270 DFT Support on SE 1.30.1 for the PC AT
The ACS3EIAC.DLL patch is required if you plan to use Communications
Manager 3270 DFT connectivity with the SE 1.30.1 operating system on a PC
AT. Without this patch, the 3270 DFT connectivity will not function on a PC
AT.
? SQLLOO
The RDSLAN.DLL patch is required if you plan to configure more than 50
NETBIOS sessions; or if you plan to have EE 1.2/1.3 Database clients using
SQLLOO, connecting to an Extended Services Database server.
Database Manager Patches
If you have Database Manager installed, you must also install the Database
Manager patches.
6.6.2 Instructions for Applying Extended Services Patches
*** NOTEs: ***
1. In order for the patches to be applied correctly, you MUST take the steps
below after Extended Services installation is complete.
2. You MUST NOT start Communications Manager or Database Manager
before applying the patches.
3. These patches for IBM Extended Services for OS/2 MUST be installed prior
to installing LAN Server if you plan to install the LAN Server product.
4. If you need to re-install any of the Extended Services components, the patch
process MUST be repeated after the re-installation.
1. Insert the patch diskette #1 in drive A:
2. From the OS/2 command prompt, enter the following commands.
Note: The replace command will replace files based upon the features you have
installed on your PC. If you have installed features which do not require any
patches, then the replace command may not replace any files.
? REPLACE A:\CMPATCH\*.* x:\CMLIB /S
where x is the logical drive on which Communications Manager for
Extended Services is installed.
Extended Services Installation 45
IBM CONFIDENTIAL Extended Services Driver S1A246 46 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? REPLACE A:\CMPATCH\*.* z:\IBMCOM /S
where z is the logical drive on which OS/2 is installed.
3. If you have installed the Communications Manager Configuration File Manager
utility, you MUST enter the following command to install the correct help text
file.
COPY A:\CMPATCH\COPYCFG.HLP z:\OS2\HELP\
(where z is the logical drive (boot drive) on which OS/2 is installed)
4. If you are planning to use Communications Manager, 3270 emulation with the
DFT connectivity on a PC AT with the SE 1.30.1 operating system, you should
enter the following to apply a patch for DFT.
COPY A:\ATPATCH\ACS3EIAC.DLL x:\CMLIB\DLL\
(where x is the logical drive on which Communications Manager for Extended
Services is installed)
5. If you have NOT installed Database Manager on your workstation, you can
skip this step. Otherwise, perform one of the following, depending on what you
have installed. If you are not sure what you have installed, you can use
VIEWLOG to look at your install history. In the steps below, specify the drive
letter that indicates the drive on which Database Manager is installed. Make
sure you have inserted patch diskette #2 in drive A:, and
? If you have a Database Server or Database Client/Server or Database
Standalone installed, type
a:dbserver x:
(where x is the drive on which Database Manager is installed) and press
Enter.
? If you have a Database Client with Local Databases installed, type
a:dbclocal x:
(where x is the drive on which Database Manager is installed) and press
Enter.
? If you have a Database Client installed, type
a:dbclient x:
(where x is the drive on which Database Manager is installed) and press
Enter.
6. Remove the patch diskette.
# 7. Bring up a menu by pressing the right mouse button while the pointer is not
# over any object (i.e. blank space) on the workplace desktop.
# 8. Select shutdown from the menu to stop the system and then reboot the system.
Extended Services Installation 46
IBM CONFIDENTIAL Extended Services Driver S1A246 47 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.0 Installing Communications Manager
7.1 Before You Install Communications Manager
Before installing IBM Extended Services for OS/2 (Extended Services), please be
sure that you have read and understood all of the restrictions and limitations. Refer
to 5.3, 﨏ommunications Manager Restrictions?on page 21 that apply to this
driver.
# After installation of Extended Services, "Communications Manager" group and
# "Extended Services" group will be added to the workplace desktop. The contents
# (i.e. options) of "Communications Manager" group depends on which features are
# installed. The following is a complete list of available options.
? Communications Manager
? SNA Network Definitions Configuration
? Verify SNA Network Definitions
? Manage SNA Logical Links
? Display Active SNA Configuration
? Display SNA Configuration Log
?
Configuration File Manager
? Start/Stop CM Trace
? Format SNA Trace information
Selecting the Extended Services group will display the following options to select
from:
? Basic Configuration and Installation
? Add or Remove Features
? View Install History File
? Create Custom Install Diskette
? Veiw Custom Build History File
? Extended Services Command Reference
You will note that Communications Manager Advanced Configuration profiles have
changed for SNA configuration, and for LAN Adapter and Protocol configuration.
We recommend that you read the APPENDIX section provided in this document,
before using the Advanced Configuration Services for SNA configuration. In the
APPENDIX section we have provided examples of configuration steps for SNA
advanced configuration. For further information, refer to the "Communications
Manager Configuration Guide" Volume 1.
Installing Communications Manager 47
IBM CONFIDENTIAL Extended Services Driver S1A246 48 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
For LAN Adapter and Protocol configuration, refer to the "LAN Adapter and
Protocol Support Configuration Guide".
Communications Manager can be installed on any fixed disk and all changes to the
CONFIG.SYS will be updated during the installation. Communications Manager
will be installed into the \CMLIB directory and CMLIB sub-directories.
The contents of the configuration file determines which program files will be
installed on your workstation. To have appropriate program files installed on your
system, you need to "install" the configuration file through the install process. To
save DASD space, only the files you need for the connectivities and features that
have been configured will be installed. For example, if your "installed" configuration
file(s) contains no X.25 configuration information, X:\CMLIB and CMLIB
subdirectories will not be loaded with any of the code which supports X.25 (X.25
DLC, X.25 device driver, etc.). *** WARNING: *** Merely copying or creating a
configuration file in the X:\CMLIB will not install the proper feature files and
update the CONFIG.SYS on your workstation.
*** IMPORTANT NOTES: ***
? If you plan to configure a new configuration file and copy to other
workstations, we RECOMMEND that the "Configuration File Manager" utility
be used, please refer to the "IBM Extended Services for OS/2 Network
Administration Guide. With APPN integrated into Extended Services, there are
APPN related files that MUST be copied with each .CFG file.
? If your configuration file has been modified to add new features (for example:
adding SRPI and 3270 features to the default ACSCFGUS.CFG via advanced
configuration services, or adding the 5250 WSF feature to your basic
configuration file via ESCFG.CMD), you will be required to go through the
REINST process to have the new feature files installed and CONFIG.SYS
updated on your system. If your configuration file has been customized via
advanced configuration services to include new features, type "REINST" at the
OS/2 command line, and be sure to select the "User Configuration File" option
on the Communications Manager Install Menu during the re-installation
process.
? If you have a new configuration file (by copying one from another workstation
or creating one via advanced configuration services), and it contains additional
connectivities and features other than what you have on your workstation,
re-installation is necessary to bring up Communications Manager with the new
configuration file. Type "REINST" at the OS/2 command prompt; select the
"User Configuration File" option on the Communications Manager Install
Menu, and follow the prompts to install the new program files.
7.1.1 Compiler Support
Following is a list of the current compiler support for Communications Manager.
?
Support for the PASCAL language has been removed.
? The Microsoft C Compiler V6.0 is the currently supported C compiler.
** The IBM C/2 compiler is no longer supported **.
Installing Communications Manager 48
IBM CONFIDENTIAL Extended Services Driver S1A246 49 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? The Microfocus COBOL/2 Compiler is the currently supported COBOL
compiler.
** The IBM COBOL/2 compiler is no longer supported **.
?
The IBM FORTRAN/2 compiler is the currently supported FORTRAN
compiler.
? The IBM MACRO ASSEMBLER/2 compiler is supported.
7.2 Installation Instructions for Communications Manager
7.2.1 Installing Communications Manager Using Basic Configuration Services
The steps below use default parameter values to create a basic configuration file with
3270 terminal emulation using Token Ring.
1. Select "3270 terminal emulation" from the BCS Main menu.
2. Select the "LAN" option for the Connection Type, and take the defaults for the
other options in the 3270 Terminal Emulation Defaults.
3. Select "IBM Token-Ring Network" for Network Type.
4. Select "IBM Token-Ring Adapter " from the Select Token Ring Network
Adapter menu. (Select the appropriate adapter for your environment if it is
different from the IBM Token-Ring Adapter.)
5. Specify a "locally administered address" from the Select LAN Address Type
menu.
6. Specify the 12 digit hex address for the Local Adapter Address.
7. On the 3270 Terminal Emulation LAN Defaults menu, specify the 12 digit hex
address for the LAN Destination Address.
8. Specify Local Node Name, Network Name, and Local Node ID on the
Configuration Network Defaults menu to suit your environment.
9. BCS Main Menu is displayed.
10. If you are selecting to install Database Manager, refer to 8.2.1, 蘒nstalling
Database Manager Using Basic Configuration Services?on page 56.
11. If no more features are to be configured, press F3 to exit BCS.
12. The target Drive Specification menu is displayed to specify the drive ID.
13. Press F3 to exit the IBM Extended Services for OS/2 Install/Remove menu if
you are done.
14. Stop all active processes.
# 15. Bring up a menu by pressing the right mouse button while pointer is not over
# any object (i.e on blank space) on workplace desktop.
# 16. Select Shutdown from the menu to stop the system and then reboot the system.
17. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on
page 44).
Installing Communications Manager 49
IBM CONFIDENTIAL Extended Services Driver S1A246 50 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.2.2 Installing Communications Manager Using Advanced Installation
1. Select the "Install Communications Manager" option from the IBM Extended
Services Install/Remove menu.
2. The target Drive Specification menu is displayed to specify the drive ID for
Communications Manager. You may install Communications Manager on any
fixed disk or partition.
3. Select "Configuration Files" from the Communications Manager Install menu.
4. Select "Default Configuration Files" from the Communications Manager
Configuration File menu.
Note: At this point, you could also have selected to install "User configuration
files." This would be the option that you would use to install a configuration file
from this release or a previous release. If you select a configuration file from a
previous release, the configuration information is automatically updated.
5. Select one or both of the following IBM supplied Default Configuration files
from the menu.
? ACSCFG.CFG
(This is a skeleton configuration file included with all model profiles and
NLS keyboard profiles.)
? ACSCFGUS.CFG
(This is a skeleton configuration file included with all model profiles and US
keyboard profiles.)
After selecting the configuration file, you will be returned to the
Communications Manager Install menu.
6. To install any additional features, select "Additional Features" from the
Communications Manager Install menu.
7. Press spacebar to select each individual feature to install from the Additional
Features menu. For example, if you are going to program to the
Communications Manager API using the provided language interface, you need
to install the API Data Structure files. Press enter when your are finished
selecting features.
8. Press F3 to exit the Communications Manager Install menu. Please note that
when Exit (F3) is pressed, installation of your feature selections are being
performed. Insert diskettes as required.
9. If you installed more than one configuration file, the Select Configuration File
to Update CONFIG.SYS File menu is displayed. By selecting the configuration
file(s) you wish to activate, the CONFIG.SYS is automatically updated with
DEVICE= and RUN= statements.
10. Refer to 8.2.2, 蘒nstalling Database Manager Using Advanced Installation?on
page 61 if you also need to install Database Manager.
11. Press F3 to exit the Extended Services Install/Remove menu if you are done
with Extended Services installation.
12. Stop all active processes.
Installing Communications Manager 50
IBM CONFIDENTIAL Extended Services Driver S1A246 51 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
# 13. Bring up a menu by pressing the right mouse button while mouse pointer is not
# over any object (i.e on blank space) on workplace desktop.
# 14. Select Shutdown from the menu to stop the system and then reboot the system.
15. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on
page 44).
7.2.3 Reconfiguring and Reinstalling Communications Manager
1. Start Communications Manager by selecting Communications Manager from
Communication Manager Group icon.
2. Enter the appropriate configuration file name for starting the Communications
Manager.
3. Select "Configuration Services" from the Action Bar to configure your desired
feature(s), for example: the SRPI, APPC, SNA Gateway, LUA, and X.25.
4. When the user-defined configuration file(s) are built and verified, exit the
Communications Manager.
5. Type "REINST" at the OS/2 command prompt to re-install your configuration
file(s) and the related feature files.
6. Select "Install Communications Manager" option from the IBM Extended
Services Install/Remove menu.
7. Select "Configuration Files" from the Communications Manager Install menu.
8. Select "User Configuration files" from the Communications Manager
Configuration file menu.
9. The Source Location menu is displayed. Specify the drive and path to your user
configuration file.
10. Select your desired configuration file(s) from the Select Configuration Files
panel.
11. Select the "Additional Features" option from the Communications Manager
Install menu if so desired.
12. Press F3 to exit the Communications Manager Install menu. Insert diskettes as
required.
13. Select the appropriate configuration file to update the CONFIG.SYS file.
14. Press F3 to exit the Extended Services Install/Remove menu.
15. Stop all active processes.
# 16. Bring up a menu by pressing the right mouse button while pointer is not over
# any object (i.e on blank space) on workplace desktop.
# 17. Select Shutdown from the menu to stop the system and then reboot the system.
18. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on
page 44).
Installing Communications Manager 51
IBM CONFIDENTIAL Extended Services Driver S1A246 52 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.3 Re-installation of Communications Manager
Re-installation is the process whereby the Communications Manager component,
Communications Manager configuration file(s) with added NEW features and/or
Additional Features are to be installed on a workstation that has previously been
through the Extended Services installation process. The requisite Communications
Manager program files are installed along with your configuration file. Enter
"REINST" from the OS/2 command prompt line, and follow the prompts for
installation instructions and inserting diskettes
7.4 Communications Manager Installation Notes
This section describes some specific notes that are related to installing the
Communications Manager from this driver:
? There are three types of configuration files that can be installed for
Communications Manager:
?Basic configuration file
?Default (IBM-supplied) configuration file
?User-defined configuration file.
The basic configuration file is generated by the fast-path Basic Configuration
Services. Please refer to 6.3, 﨎asic Configuration Services (BCS)?on page 41
for more detailed information. If the communication features cannot be
configured using the BCS, most users will want to go to the Install Additional
Features panel to select ACSCFG.CFG or ACSCFGUS.CFG from the Default
Configuration Files option. The ACSCFGUS.CFG file is a general-purpose
configuration file shipped with the system and contains all model profiles along
with US-only keyboard support. It will require tailoring for your specific
configuration before you can begin communicating. If you plan to make
extensive changes, you may want to copy ACSCFG.CFG or ACSCFGUS.CFG
to your own file, (e.g. MYCFG.CFG) and start the Communications Manager
using MYCFG.
Once ACSCFG.CFG or ACSCFGUS.CFG has been installed, you have the
flexibility to customize your own features in the configuration file by utilizing
the Communications Manager advanced configuration services function. After
you build your own configuration file, you need to type "REINST" at the OS/2
command line, and select the "Configuration Files" and "Addition Features"
options on the Communications Manager Install menu during the re-installation
process. Refer to sections 7.2.2, 蘒nstalling Communications Manager Using
Advanced Installation?on page 50 and 7.2.3, econfiguring and Reinstalling
Communications Manager?on page 51 for more information.
Installing Communications Manager 52
IBM CONFIDENTIAL Extended Services Driver S1A246 53 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.5 ROP Service and SPA Router Installation Instructions
Remote Operations Service (ROP Service) and Service Point Application Router
(SPA Router) can be installed on any fixed disk, and all changes to CONFIG.SYS
will be updated during installation. SPA Router and ROP Service are installed in
the \ROP directory of the drive you specify. Follow the steps below to install ROP
Service and SPA Router.
1. Place the IBM Extended Services for OS/2 diskette 1 in drive A.
2. At the command prompt type:
A:ROPS
3. Press Enter.
4. Follow instructions on the menus and insert diskettes as prompted.
5. You will be asked to enter the drive where you want to install the SPA Router
and ROP Service. Enter any valid drive letter of your choice. The SPA Router
and ROP Service are installed in the \ROP directory of the drive you choose.
6. On the "Remote Operations Installation Complete" menu, remove the diskette
from drive A: and press enter.
7. On the "Installation Complete" panel, select to "Return."
8. You will return to the OS/2 command prompt. At this point, you should use
Shutdown to stop and reboot the system so that the CONFIG.SYS changes
take effect.
*** NOTES: ***
Before you can use the SPA Router and ROP Service, you will need to do the
following.
1. In your Communications Manager SNA Profile ensure that the Maximum RU
Size is set to 512 or greater. ROP Service will only work with a value of 512 or
greater.
2. Configure and start a 3270 terminal emulation session (other than a 3270 DFT
session) or configure Advanced Program-to-Program Communications (APPC)
with session start in order to establish an SSCP-PU session.
3. If you are going to use the User Profile Management (UPM) operator checking
option, ensure that the operator ID of the NetView operator using ROP Service
is defined to the UPM tables. To do this, define a new ID using an UPM
administrator account. The password is optional. If the system is not security
critical, it is recommended that the password not be set because use of a
password requires sending the password with every RUNCMD.
4. Start the Communications Manager before using the SPA Router and ROP
Service.
Installing Communications Manager 53
IBM CONFIDENTIAL Extended Services Driver S1A246 54 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5. Open the Remote Operations group from the Desktop Manager group of OS/2
Presentation Manager. Start "Service Point Application Router" and then
"Remote Operations Service".
6. You are now ready to issue commands from NetView to this workstation.
Installing Communications Manager 54
IBM CONFIDENTIAL Extended Services Driver S1A246 55 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
8.0 Installing Database Manager
8.1 Before You Install Database Manager
Before installing Database Manager, please be sure that you have read and
understood all of the restrictions/limitations that apply to this driver. See 6.1,
﨎efore You Install Extended Services?on page 38 and 5.4, 﨑atabase Manager
Restrictions?on page 25.
Database Manager can be installed on any fixed disk, and all changes to
CONFIG.SYS will be updated during the installation. Database Manager will be
installed into the \SQLLIB and \SQLLIB\DLL directories.
8.1.1 Migration of Databases
Extended Services databases (databases created using the previously shipped
Extended Services driver), CANNOT BE MIGRATED FOR USE WITH THIS
DRIVER. Please refer to 5.4, 﨑atabase Manager Restrictions?on page 25 for
detailed instructions for using existing Extended Services databases with this driver.
Existing databases from EE 1.1, EE 1.2 and EE 1.3 CAN BE MIGRATED for use
with Extended Services. Currently, the only supported form of migration is
Backup/Restore. Refer to Appendix A of the IBM Extended Services for OS/2
Guide to Database Manager for instructions on migrating databases. Be SURE to
backup all databases BEFORE you install this driver.
Corrections
Appendix A of the IBM Extended Services for OS/2 Guide to Database Manager
has some incorrect information. The references to migration of Version 1.0
databases is wrong: EE 1.0 databases can NOT be migrated. Also, there are no
references to EE 1.2 or EE 1.3 databases in this appendix; however, migration
DOES WORK for these databases.
8.1.2 Compiler Support
Following is a list of the current compiler support for Database Manager.
? Support for the PASCAL language has been removed.
?
The Microsoft C Compiler V6.0 is the currently supported C compiler.
** The IBM C/2 compiler is no longer supported **.
? The Microfocus COBOL/2 Compiler V2.5 is the currently supported COBOL
compiler.
** The IBM COBOL/2 compiler is no longer supported **.
Installing Database Manager 55
IBM CONFIDENTIAL Extended Services Driver S1A246 56 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? The IBM FORTRAN/2 compiler is the currently supported FORTRAN
compiler.
8.2 Database Manager Installation Examples
Note
The following installation examples assume that you will be using IBM
Token-Ring as your LAN network type. If you choose other network types,
there will be some differences in the panels/menus that are displayed.
Also, due to variables such as the sequence of component installation, all steps
may not appear in the exact sequence listed in the examples. Additionally, if a
connection type of "LAN" was previously configured (such as during 3270
Terminal Emulation configuration), some menus/panels may not appear at all.
These are EXAMPLES only. Please refer to the IBM Extended Services for
OS/2 Start Here and the IBM Extended Services for OS/2 Workstation
Installation Guide for detailed installation instructions.
8.2.1 Installing Database Manager Using Basic Configuration Services
You can use Basic Configuration Services (BCS) to install any Database Manager
configuration (Database Client, Database Server, Database Client/Server, Database
Client with Local Databases, or Standalone). However, it is most commonly used to
install those configurations which use Remote Data Services (RDS); this includes all
configurations except Standalone.
If you use Basic Configuration Services, and if you plan to use X.25 or SDLC for
Remote Data Services, you will need to supplement your install with the
Communications Manager Advanced Configuration services and re-installation
process to configure and install them. Refer to the IBM Extended Services for OS/2
Configuration Guide for Communications for more information.
The instructions that follow assume you will be installing Database Services, Query
Manager, and Database Tools. Query Manager and Database Tools should be
installed with Database Services if other application programs are not available to
use when working with database information.
If you choose not to install either Query Manager or Database Tools, then do not
select those options from the Database Manager Install menu. In addition, you will
be able to select DOS Database Client support and/or Windows Database Client
support. This support can be installed on ANY configuration (see the IBM
Extended Services for OS/2 Guide to Database Manager for additional information
about DOS/Windows Database Clients).
You may install Database Manager on any fixed disk or partition.
Installing Database Manager 56
IBM CONFIDENTIAL Extended Services Driver S1A246 57 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Installing as a Database Client or Client with Local Databases
1. At the Basic Configuration Services Main Menu:
? Select "Database Manager using Remote Data Services"
2. At the Specify Database Manager Communications menu:
? Select "Database Client"
3. At the Databases on Your Workstation pop-up:
? Select "No"
Note
You can select "Yes", if you also want to create databases on this
workstation. If you do, you will actually be installing as a Database
Client with Local Databases. This is a new Database Manager
configuration with Extended Services.
4. If the Select LAN Network Type menu displays:
? Select "IBM Token-Ring Network..."
5. If the Select Token-Ring Network Adapter menu displays:
? Select the appropriate adapter (e.g., Token-Ring adapter /A, Token-Ring
adapter 16/4 /A, etc.)
6. If the Select LAN Address Type menu displays:
? Select "Use Universal address" if you want to use the unique address of the
adapter card itself (and proceed to Step 7)
-- or --
? Select "Specify a locally adminstered address" if you want to provide your
own unique local adapter address.
?At the Local LAN Adapter Address panel:
?Enter a UNIQUE 12-digit adapter address, such as 400000000015.
7. You will now be returned to the Basic Configuration Services Main Menu
? Select another feature that you wish to install (i.e., 3270 Terminal
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation
Instructions for Communications Manager?on page 49 for information
about installing these CM features.
-- or --
? Select F3=Exit if you have made your last selection
8. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
If the Target Drive Specification panel displays (for Communications Manager),
specify the target drive where you want CM installed.
9. At the Target Drive Specification panel for Database Manager
? Enter the target drive where you want Database Manager installed
Installing Database Manager 57
IBM CONFIDENTIAL Extended Services Driver S1A246 58 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
10. At the Database Manager Install Menu:
? Select "Database Services", "Query Manager" and "Database Tools" (note
that this is now a multi-select menu)
11. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that BCS now
defaults to the NETBIOS protocol for OS/2 clients. This requires that
workstation names on a LAN be unique).
12. Follow the prompts to insert diskettes for installation of Database Manager
Installing as a Database Server
1. At the Basic Configuration Services Main Menu:
? Select "Database Manager using Remote Data Services"
2. At the Specify Database Manager Communications menu:
? Select "Database Server"
3. At the Database Manager Target Drive Specification panel:
? Enter the target drive where you want Database Manager installed
4. If the Select LAN Network Type menu displays:
? Select "IBM Token-Ring Network..."
5. If the Select Token-Ring Network Adapter menu displays:
?
Select the appropriate adapter (i.e., Token-Ring adapter /A, Token-Ring
adapter 16/4 /A, etc.)
6. If the Select LAN Address Type menu displays:
? Select "Use Universal address" if you want to use the unique address of the
adapter card itself (and proceed to Step 7)
-- or --
?
Select "Specify a locally adminstered address" if you want to provide your
own unique local adapter address.
?At the Local LAN Adapter Address panel:
?Enter a UNIQUE 12-digit adapter address, such as 400000000020.
7. You will now be returned to the Basic Configuration Services Main Menu
? Select another feature that you wish to install (i.e., 3270 Terminal
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation
Instructions for Communications Manager?on page 49 for information
about installing these CM features.
-- or --
? Select F3=Exit if you have made your last selection
8. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
Installing Database Manager 58
IBM CONFIDENTIAL Extended Services Driver S1A246 59 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
If the Target Drive Specification panel displays (for Communications Manager),
specify the target drive where you want CM installed.
9. At the Database Manager Install Menu:
?
Select "Database Services", "Query Manager" and "Database Tools" (note
that this is now a multi-select menu)
10. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that BCS now
defaults to the NETBIOS protocol for OS/2 clients. This requires that
workstation names on a LAN be unique).
11. Follow the prompts to insert diskettes for installation of Database Manager
Installing as a Database Client/Server
1. At the Basic Configuration Services Main Menu:
? Select "Database Manager using Remote Data Services"
2. At the Specify Database Manager Communications menu:
?
Select "Database Client/Server"
3. At the Database Manager Target Drive Specification panel:
? Enter the target drive where you want Database Manager installed
4. If the Select LAN Network Type menu displays:
? Select "IBM Token-Ring Network..."
5. If the Select Token-Ring Network Adapter menu displays:
? Select the appropriate adapter (i.e., Token-Ring adapter /A, Token-Ring
adapter 16/4 /A, etc.)
6. If the Select LAN Address Type menu displays:
? Select "Use Universal address" if you want to use the unique address of the
adapter card itself (and proceed to Step 7)
-- or --
? Select "Specify a locally adminstered address" if you want to provide your
own unique local adapter address.
?At the Local LAN Adapter Address panel:
?Enter a UNIQUE 12-digit adapter address, such as 400000000025.
7. You will now be returned to the Basic Configuration Services Main Menu
?
Select another feature that you wish to install (i.e., 3270 Terminal
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation
Instructions for Communications Manager?on page 49 for information
about installing these CM features.
-- or --
? Select F3=Exit if you have made your last selection
Installing Database Manager 59
IBM CONFIDENTIAL Extended Services Driver S1A246 60 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
8. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
If the Target Drive Specification panel displays (for Communications Manager),
specify the target drive where you want CM installed.
9. At the Database Manager Install Menu:
? Select "Database Services", "Query Manager" and "Database Tools" (note
that this is now a multi-select menu)
10. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that BCS now
defaults to the NETBIOS protocol for OS/2 clients. This requires that
workstation names on a LAN be unique).
11. Follow the prompts to insert diskettes for installation of Database Manager
Installing as a Standalone
Note
Standalone DBM is usually installed using Advanced Installation, not BCS;
however, if you want to install one or more of the Communications Manager
features (3270 Terminal Emulation, ASCII Terminal Emulation or 5250 WSF)
AND you want Standalone DBM, this procedure will work.
1. At the Basic Configuration Services Main Menu:
? Select one of the Communications Manager options ("3270 Terminal
Emulation, ASCII Terminal Emulation, or 5250 Workstation Feature")
2. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
3. At the Target Drive Specification panel:
? Specify the target drive where you want Communications Manager installed
4. You will now be returned to the Basic Configuration Services Main Menu
?
Select F3=Exit
5. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
6. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
7. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
8. At the Database Manager Install menu:
9. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
Installing Database Manager 60
IBM CONFIDENTIAL Extended Services Driver S1A246 61 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
10. At the Database Remote Data Services menu:
? Select "No"
11. Follow the prompts to insert diskettes.
12. When you have finished installing Database Manager, select exit (F3), and
follow the instructions.
8.2.2 Installing Database Manager Using Advanced Installation
You can use Advanced Installation to install any Database Manager configuration
(Database Client, Database Server, Database Client/Server, Database Client with
Local Databases, or Standalone); however, it is most commonly used to install
Standalone. Those configurations which use Remote Data Services (RDS) are more
commonly installed using Basic Configuration Services (BCS).
The instructions that follow assume you will be installing Database Services, Query
Manager, and Database Tools. Query Manager and Database Tools should be
installed with Database Services if other application programs are not available to
use when working with database information.
If you choose not to install either Query Manager or Database Tools, then do not
select those options from the Database Manager Install menu. In addition, you will
be able to select DOS Database Client support and/or Windows Database Client
support. This support can be installed on ANY configuration (see the IBM
Extended Services for OS/2 Guide to Database Manager for additional information
about DOS/Windows Database Clients).
You may install Database Manager on any fixed disk or partition.
Installing as a Standalone
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
? Select "No"
7. Follow the prompts to insert diskettes.
8. When you have finished installing Database Manager, select exit (F3), and
follow the instructions.
Installing Database Manager 61
IBM CONFIDENTIAL Extended Services Driver S1A246 62 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Installing as a Database Client or Client with Local Databases
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
? Select "Yes"
7. At the Specify Database Manager Communications menu:
? Select "Database Client"
8. At the Databases on Your Workstation pop-up:
?
Select "No"
Note
You can select "Yes", if you also want to create databases on this
workstation. If you do, you will actually be installing as a Database
Client with Local Databases. This is a new Database Manager
configuration with Extended Services.
9. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that if you plan to
use NETBIOS as the protocol for this client, this name MUST be unique
on the LAN).
10. Follow the prompts to insert diskettes.
11. If LAN Adapter and Protocol Support (LAPS) has not been installed, the
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will
display.
12. At the IBM Extended Services/2 Install/Removemenu:
? Select "Install Communications Manager" to configure and install the
necessary CM features to support your configuration, if you have not
already done so. You will need to configure and install the necessary
communications adapter and protocol support in order to use Remote Data
Services.
-- or --
?
Select F3=Exit to complete the Database Manager installation
Installing Database Manager 62
IBM CONFIDENTIAL Extended Services Driver S1A246 63 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Installing as a Database Server
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
? Select "Yes"
7. At the Specify Database Manager Communications menu:
? Select "Database Server"
8. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that if you plan to
use the NETBIOS protocol for client communications, this name MUST
be unique on the LAN).
9. Follow the prompts to insert diskettes.
10. If LAN Adapter and Protocol Support (LAPS) has not been installed, the
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will
display.
11. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Communications Manager" to configure and install the
necessary CM features to support your configuration, if you have not
already done so. You will need to configure and install the necessary
communications adapter and protocol support in order to use Remote Data
Services.
-- or --
?
Select F3=Exit to complete the Database Manager installation
Installing as a Database Client/Server
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
Installing Database Manager 63
IBM CONFIDENTIAL Extended Services Driver S1A246 64 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
?
Select "Yes"
7. At the Specify Database Manager Communications menu:
? Select "Database Client/Server"
8. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that if you plan to
use the NETBIOS protocol for communications, this name MUST be
unique on the LAN).
9. Follow the prompts to insert diskettes.
10. If LAN Adapter and Protocol Support (LAPS) has not been installed, the
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will
display.
11. At the IBM Extended Services/2 Install/Remove menu:
?
Select "Install Communications Manager" to configure and install the
necessary CM features to support your configuration, if you have not
already done so. You will need to configure and install the necessary
communications adapter and protocol support in order to use Remote Data
Services.
-- or --
? Select F3=Exit to complete the Database Manager installation
Installing Database Manager 64
IBM CONFIDENTIAL Extended Services Driver S1A246 65 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
9.0 Installing OS/2 LAN Requester
Please read section 5.7, 﨤AN Server Version 2.0 Requester Restrictions?on
page 34 before installing.
*** PLEASE NOTE ***
# For a 16-bit base IBM OS/2 LAN Requester, Version 2.0, driver level 281 will
# run on SE manufacturing level 1.30.1. For a 32-bit base, IBM OS/2 LAN
# requester will run on SE V.2.0 driver level 6.167.
9.1 Basic Installation for OS/2 LAN Requester
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 31.
9.2 Advanced Installation for OS/2 LAN Requester
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 33.
9.3 Reinstalling, Reconfiguring or Removing
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 43.
Installing OS/2 LAN Requester 65
IBM CONFIDENTIAL Extended Services Driver S1A246 66 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
10.0 Installing OS/2 LAN Server
Please read section 5.6, 﨤AN Server Version 2.0 Server Restrictions?on page 29
before installing.
***PLEASE NOTE***
# The OS/2 LAN Server, V2.0, driver level 281, will run on the 16-bit based SE
# manufacturing level 1.30.1, and on the 32-bit based SE driver level 6.167
10.1 Basic Installation for OS/2 LAN Server
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 12.
10.2 Advanced Installation for OS/2 LAN Server
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 15.
10.3 LAN Server 1.3 Migration Utility
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 1,
page 20, and chapter 3, page 8. Also, please see the IBM OS/2 LAN Server V2.0
Migration Handbook .
Installing OS/2 LAN Server 66
IBM CONFIDENTIAL Extended Services Driver S1A246 67 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
11.0 Installing IBM LAN Support Program and DOS LAN
Requester
Please read section 5.6, 﨤AN Server Version 2.0 Server Restrictions?on page 29
and 5.7, 﨤AN Server Version 2.0 Requester Restrictions?on page 34 before
installing.
11.1 Installing the IBM LAN Support Program, V.1.21
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 5
and the IBM LAN Support Program User's Guide.
11.2 Installing DOS LAN Requester
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 5.
Installing IBM LAN Support Program and DOS LAN Requester 67
IBM CONFIDENTIAL Extended Services Driver S1A246 68 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix
Appendix 68
IBM CONFIDENTIAL Extended Services Driver S1A246 69 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix A. SNA Advanced Configuration
A.1 Overview
Earlier this year, IBM introduced a software program product called Networking
Services/2. This product was designed to enhance the performance of computers
operating in OS/2 Extended Edition network environments. Networking Services/2
provides both APPN end node and network node support to workstations, allowing
them greater flexibility when communicating with other workstations in the
network. Networking Services/2 also offers the SAA Common Programming
Interface (CPI) for communications, and an enhanced version of the Advanced
Program to Program Communications (APPC) Application Programming Interface
(API). Networking Services/2 greatly improved APPC throughput in
performance-critical LAN environments. In addition, Networking Services/2 offers
configuration and management services that provide both ease-of-use and improved
function for network users.
In this offering of Extended Services/2, the function provided by Networking
Services/2 is incorporated into the Communications Manager product. This
addition further enhances the usability and performance of APPN and
Communications Manager, as well as the networking capability of your OS/2 EE
system environment. With this added function, a workstation using Extended
Services can participate in an APPN network as a low-entry networking (LEN)
node, end node, or network node.
A.1.1 The Configuration Process
When you perform Advanced Configuration for SNA, Communications Manager
builds a particular set of configuration files. All of these files have the same name as
the configuration file you specify but different extensions. These files contain
different information, based on the extension. The following list provides
descriptions of the configuration files:
.CFG Communications Manager binary configuration file, which contains DLC,
SNA Gateway, X.25, 3270 LU, and LUA information.
This file is updated following Verify and is placed in the \CMLIB directory.
.NDF Node definitions configuration file, which contains an ASCII representation
of the verbs used to configure APPN at startup time. You can use the .NDF
file to perform additional SNA configuration by editing the file with any type
of ASCII editor.
This file is created following completion of the SNA Feature Configuration
panel during configuration and is placed in the \CMLIB\APPN directory.
.CF2 APPN binary configuration file, which contains a binary representation of
the verbs used to configure APPN at startup time. This file must exist and
cannot be empty to start APPN function.
This file is created following Verify and is placed in the \CMLIB\APPN
directory.
Appendix A. SNA Advanced Configuration 69
IBM CONFIDENTIAL Extended Services Driver S1A246 70 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
.SEC Binary security configuration.
This file is created following completion of the SNA Feature Configuration
panel during configuration and is placed in the \CMLIB\APPN directory.
.INI This file supports LAN adapter and protocol functions and is stored in the
\IBMCOM directory. PROTOCOL.INI is the name of the .INI file for the
active configuration on your workstation.
The node definitions (.NDF) and .INI files can be modified using a text editor.
You can modify the other configuration files using the Communications Manager
configuration panels.
Three scenarios for SNA Advanced Configuration are presented in this section:
?
5250 Advanced Configuration
? 3270 over Token-Ring
? 3270 over SDLC via Gateway.
Sample Node Definitions files (NDF) for each of the scenarios are also included.
A.2 Advanced Configuration for 5250
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory to create
your new configuration file.
(example: ) C>copy acscfgus.cfg 5250adv.cfg
2. Restart Communications Manager using this file.
(example: ) C>cm 5250adv
3. Switch to the task list to access the Communications Manager Main Menu.
4. Select the Advanced action bar item and then select the Configuration pulldown
choice. Press Enter.
A message box appears displaying the name of the configuration file.
5. Press Enter. The Specify Configuration Usage panel appears.
6. Select the first option if you intend to use this configuration on this workstation
and press Enter.
The Communication Configuration Menu appears.
7. Select option 4, SNA feature profiles, and press Enter.
The SNA Feature Configuration panel appears.
8. Select Data Link Control (DLC) Profiles and press Enter.
A message box appears showing the DLC types.
9. Select option 3, Token-Ring or Other LAN type... and press Enter.
The DLC Adapters and Operations panel appears.
10. Select the two options Adapter 0 and Create and press Enter.
The Create/Change IBM Token-Ring Network DLC Profile panel appears.
Appendix A. SNA Advanced Configuration 70
IBM CONFIDENTIAL Extended Services Driver S1A246 71 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
11. Use all of the default values displayed for the fields on this panel, except for the
C&SM LAN ID, where you must provide a value. Press Enter.
The SNA Feature Configuration panel appears.
12. Select SNA network definitions and press Enter.
The SNA Definitions Options panel appears.
13. Select Create/Change and press Enter. An informational message box appears.
Press Enter.
The Local Node Characteristics panel appears.
14. For the Required Features, specify the following:
Network ID
The network ID is the same as that supplied in the SNA base of previous
versions of Communications Manager. WARNING: The network ID
CANNOT be blanks.
Local node name
The local node name is the same as that as that supplied for the PU or Control
Point in previous versions of Communications Manager.
Node type
Accept the default node type of end node - no network node server.
For the optional features:
? Use the default supplied for the Local Node ID.
? Use the same name you supplied for Local Node Name for the Local Node
Alias Name, except enter the name in all caps.
? Use the default supplied for the Activate Attach Manager at startup
(selected).
Select the OK push button and press Enter. The Basic SNA information
message panel appears. Press Enter. The SNA Network Definitions Selection
panel appears.
15. Select Connections and select the Configure push button.
The CM SNA Connections panel appears.
16. Select To Primary Host and press Enter.
The Adapter List panel appears.
17. Select IBMTRNET and press Enter.
The "Creating a Connection to a To Primary Host" panel appears.
18. Use the default value supplied for the Link Name.
Supply values for the Partner Network ID, Partner Node Name, and LAN
Destination Address fields.
Select the Define Partner LUs... push button.
The "Creating Partner LU " panel appears.
19. .Supply values for the LU name, and Alias fields (the Alias value must be in all
caps) and then select the Add pushbutton.
Appendix A. SNA Advanced Configuration 71
IBM CONFIDENTIAL Extended Services Driver S1A246 72 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
The LU name and alias you selected are added to the list box.
Select the OK push button.
The Creating a Connection to a To Primary Host panel appears.
20. Select the OK push button to exit from this panel.
The CM SNA Connections panel appears.
21. Select the Configuration action bar choice and then select the Additional SNA
Features... pulldown choice.
The CM Additional SNA Features panel appears.
22. Create a mode profile by selecting the Modes choice and pressing Enter.
The Creating a Mode Definition panel appears.
23. Supply the following values for the fields shown:
Mode name: (supply a mode name)
Class of service: #CONNECT (the default)
Mode session limit: 64
Minimum contention winners: 32
Receive pacing window: 7
Select Default RU size.
Select the OK push button.
The CM Additional SNA Features panel appears.
24. Select the File action bar choice and then select the Save and exit pulldown
choice.
The SNA Network Definitions Selection panel appears.
25. Select the Exit push button.
The SNA Feature Configuration panel appears.
26. Press F3 to exit from the SNA Feature Configuration panel.
The Communication Configuration Menu appears.
27. Select option 6, LAN Adapter and Protocol Support and press Enter.
The Options panel appears.
28. Select Configure workstation (the default) and then select the OK pushbutton.
A message appears stating that the configuration file is being read, and then the
Configure Workstation panel appears.
29. Select the OK pushbutton to use all of the defaults shown on this panel.
The Options panel appears.
30. Select Configuration complete (the default) and then select the OK pushbutton.
The Communication Configuration Menu appears.
Appendix A. SNA Advanced Configuration 72
IBM CONFIDENTIAL Extended Services Driver S1A246 73 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
31. Select option 7, 5250 workstation feature profiles and press Enter.
The 5250 Workstation Feature Configuration panel appears.
32. Select option 1, Terminal profiles... and press Enter.
The Profile Operations panel appears.
33. Select option 3, Create... and press Enter. The Specify Terminal Profile Names
panel appears.
34. Use the default supplied for the Model name (M1) and enter TERM in the
Profile Name field. Press Enter.
The Create/Change Terminal Options panel appears.
35. Select option 1, Common terminal options and press Enter.
The Common Terminal Options panel appears.
36. Accept all the default values for the terminal options and press Enter.
The Specify Workstation ID panel appears.
Accept the defaults and leave the Workstation ID field blank. Press Enter.
The Create/Change Terminal Options panel appears.
37. Press F3 to exit from the Create/Change Terminal Options panel.
The 5250 Workstation Features Configuration panel appears.
38. Select option 3, Specify APPC LU alias... and press Enter.
The Specify APPC LU Alias panel appears.
39. Type the LU alias in the "APPC LU alias" field and press Enter. (This is the
same value as the one supplied for the Local Node Name in step 14 on
page 71.)
40. The 5250 Workstation Features Configuration panel appears.
41. Select option 4, Session assignments and press Enter.
The 5250 Session Selection panel appears.
42. Select Session Number 1 and press Enter.
The 5250 Terminal/Printer Session Assignments panel appears.
43. Supply the values for the following fields and press Enter.
5250 Workstation Feature profile name
Use the profile value "TERM", as shown in step 34.
APPC partner LU alias
Use the same value you used for supplying an alias in step 19 on page 71.
APPC mode name
Use the same value you used for supplying a mode name in step 23 on page 72.
Short session ID
Accept the default value for the short session ID (A).
The 5250 Session Selection panel appears.
Appendix A. SNA Advanced Configuration 73
IBM CONFIDENTIAL Extended Services Driver S1A246 74 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
44. Press F3 to exit the 5250 Session Selection panel.
The 5250 Workstation Feature Configuration panel appears.
45. Press F3 to exit the 5250 Workstation Feature Configuration panel.
The Communication Configuration Menu panel appears.
46. To verify your configuration file, press F10 and select the Verify action bar
choice. Then select option 1, Run verify from the pulldown.
A message box appears stating that the verification of the configuration file is in
process. After the configuration file is verified, a message box appears that
states the options for restarting and using the new configuration.
47. Press Enter. Another message box appears stating that Communications
Manager must be restarted to use the new configuration.
48. Press Enter. The Communication Configuration Menu panel appears.
49. Press F3 to exit from the Communication Configuration Menu. The
Communications Manager Main Menu" panel appears.
50. Press F3 to exit from the Communications Manager.
A message box appears notifying that you are exiting from Communications
Manager and asks you if you are sure.
51. Select option 1, Yes and press Enter.
Another message panel appears stating that the Communications Manager
features have ended successfully.
52. Press F3 to exit the Communications Manager.
53. Restart Communications Manager using the new configuration file.
(example: C>start cm 5250adv)
Switch to the task list to access the Communications Manager Main Menu.
54. Select option 1, Start emulators and press Enter.
The Start Communications panel appears.
55. Select option 4, 5250 Work Station Feature and press Enter.
The Select 5250 Work Station Feature Sessions to Start panel appears.
56. Select ALL and press enter.
The Logon panel appears.
57. Type the UPM user ID and password in the appropriate fields and press Enter.
The 5250 host sign on screen appears for the active 5250 session.
Appendix A. SNA Advanced Configuration 74
IBM CONFIDENTIAL Extended Services Driver S1A246 75 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
A.2.1 5250ADV .NDF File Example
DEFINE_LOCAL_CP FQ_CP_NAME(NETNAME.NODENAME )
CP_ALIAS(ALIASNAM)
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'00000')
HOST_FP_SUPPORT(YES)
HOST_FP_LINK_NAME(LINK0001);
DEFINE_LOGICAL_LINK LINK_NAME(LINK0001)
FQ_ADJACENT_CP_NAME(USIBMTH.AUSHATT )
ADJACENT_NODE_TYPE(LEN)
DLC_NAME(IBMTRNET)
ADAPTER_NUMBER(0)
DESTINATION_ADDRESS(X'400033345678')
CP_CP_SESSION_SUPPORT(NO)
ACTIVATE_AT_STARTUP(YES)
LIMITED_RESOURCE(USE_ADAPTER_DEFINITION)
LINK_STATION_ROLE(USE_ADAPTER_DEFINITION)
SOLICIT_SSCP_SESSION(YES)
EFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION)
COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION)
COST_PER_BYTE(USE_ADAPTER_DEFINITION)
SECURITY(USE_ADAPTER_DEFINITION)
PROPAGATION_DELAY(USE_ADAPTER_DEFINITION)
USER_DEFINED_1(USE_ADAPTER_DEFINITION)
USER_DEFINED_2(USE_ADAPTER_DEFINITION)
USER_DEFINED_3(USE_ADAPTER_DEFINITION);
DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(USIBMTH.AUSHATT )
PARTNER_LU_ALIAS(AUSHATT)
MAX_MC_LL_SEND_SIZE(32767)
CONV_SECURITY_VERIFICATION(NO)
PARALLEL_SESSION_SUPPORT(YES);
DEFINE_PARTNER_LU_LOCATION FQ_PARTNER_LU_NAME(USIBMTH.AUSHATT )
WILDCARD_ENTRY(NO)
FQ_OWNING_CP_NAME(USIBMTH.AUSHATT )
LOCAL_NODE_NN_SERVER(NO);
DEFINE_MODE MODE_NAME(QPCSUPP )
COS_NAME(#CONNECT)
DEFAULT_RU_SIZE(YES)
RECEIVE_PACING_WINDOW(7)
MAX_NEGOTIABLE_SESSION_LIMIT(32767)
PLU_MODE_SESSION_LIMIT(64)
MIN_CONWINNERS_SOURCE(32);
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)
DEFAULT_MODE_NAME(BLANK)
MAX_MC_LL_SEND_SIZE(32767)
DIRECTORY_FOR_INBOUND_ATTACHES(*)
Appendix A. SNA Advanced Configuration 75
IBM CONFIDENTIAL Extended Services Driver S1A246 76 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)
DEFAULT_TP_CONV_SECURITY_RQD(NO)
MAX_HELD_ALERTS(10);
START_ATTACH_MANAGER;
A.3 Advanced Configuration for 3270 Over Token-Ring
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory to create
your new configuration file.
(example: C>copy acscfgus.cfg 3270tr.cfg)
2. Restart Communications Manager using this file.
(example: C>start cm 3270tr)
3. Switch to the task list to access the Communications Manager Main Menu.
The Communications Manager Main Menu appears.
4. Select the Advanced action bar item and then select the Configuration pulldown
choice. Press Enter.
A message box appears displaying the name of the configuration file.
5. Press Enter. The Specify Configuration Usage panel appears.
6. Select the first option if you intend to use this configuration on this workstation..
The Communication Configuration Menu appears.
7. Select option 3, 3270 feature profiles and press Enter. The 3270 Feature
Configuration panel appears.
8. Select option 3, IBM Token-Ring or Other LAN type... and press Enter. The
Profile Operations panel appears.
9. Select option 2, Create/Change and press Enter.
The Create/Change 3270 Profile panel appears.
10. Select option 1, Connection.
The Specify Link Information panel appears.
11. Select Adapter 0 (the default) for the Adapter number field and supply the
destination address in the Destination Address field and press Enter.
The Create/Change 3270 Profile panel re-appears.
12. Select sessions to configure for a terminal.
The Create/Change 3270 Logical Terminal Profile panel appears.
Use the default values supplied for all of the fields on this panel and supply a
session ID and LU Local Address.
Press F3 two times to return to the Communication Configuration Menu. You
will receive a warning that the DLC must be configured; press Enter. Select
option 4, SNA Feature Profiles and press Enter.
Appendix A. SNA Advanced Configuration 76
IBM CONFIDENTIAL Extended Services Driver S1A246 77 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
The SNA Feature Configuration panel appears.
13. Select Data Link Control (DLC) Profiles and press Enter.
A message box appears showing the DLC types.
14. Select option 3, Token-Ring or Other LAN type.. and press Enter.
The DLC Adapters and Operations panel appears.
15. Select the two options Adapter 0 and Create and press Enter.
The Create/Change IBM Token-Ring Network DLC Profile panel appears.
16. Use all of the default values displayed for the fields on this panel, except for the
C&SM LAN ID, where you must provide a value. Press Enter.
The SNA Feature Configuration panel appears.
17. Select SNA network definitions and press Enter.
The SNA network definitions options panel appears. Select Create/Change, and
press enter.
The "Creating Basic SNA Node Information" panel appears.
18. Select OK.
The Local Node Characteristics panel appears.
19. For the Required Features, specify the following:
Network ID
The network ID is the same as that supplied in the SNA base of previous
versions in Communications Manager. WARNING: The Network ID cannot
be blanks.
Local node name
The local node name is the same as that as that supplied for the PU or Control
Point in previous versions of Communications Manager.
Node type
Accept the default node type of end node - no network node server.
For the optional features:
? Use the default supplied for the Local Node ID.
? Use the same name you supplied for Local Node Name for the Local Node
Alias Name, except enter the name in all caps.
? Select Activate Attach Manager at startup.
Select the OK push button and press Enter.
You will receive an informational message on the Basic SNA Node Information
Created. Press the OK push button.
You will see the SNA Network Definitions Selection. Select the Exit push
button.
The SNA Feature Configuration panel appears.
20. Select F3 to exit from this panel.
The Communication Configuration Menu appears.
Appendix A. SNA Advanced Configuration 77
IBM CONFIDENTIAL Extended Services Driver S1A246 78 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
21. Select option 6, LAN Adapter and Protocol Support and press Enter.
The Options screen appears.
22. Select Configure Workstation and press Enter.
The Configure Workstation panel appears.
23. Select the following on this panel:
? Select IBM Token-ring Adapters from Network Adapters.
A pop-up screen appears showing the adapters in the current configuration.
?
Select IBM IEEE 802.2 from Protocols.
A pop-up screen appears showing the current configuration for this item.
At this point, you can either:
? Select OK to complete configuration (and use the supplied defaults).
Note: If you choose this action, you can bypass step 24.
? Highlight the IBM Token-ring Adapters choice in the Current
Configuration box and select the Edit push button to edit the parameters
you created.
24. Use the edit box to edit the parameters for the token-ring adapters or the IBM
IEEE 802.2 entries.
Select OK when you are finished editing.
25. Select OK to exit the Configure Workstation panel.
The Options panel appears.
26. Select Configuration complete (the default).
The Communication Configuration panel appears.
27. Select the Verify action bar choice and then select the Run Verify pulldown
choice to verify the configuration file.
Note: A screen may appear stating that inconsistencies were found. If this occurs,
access the message log to view the messages and perform the following steps. For
example, you may be asked to do a REINST if the features you configured are not
installed yet.
1. Stop Communications Manager and type the command at the command REINST
prompt. This action restarts Communications Manager using the configuration
file you created.
2. On the REINST screen, select Install Additional Features and press Enter.
3. Select LAN Adapter and Protocol Support, for example, if this is the feature
which needs to be installed.
Appendix A. SNA Advanced Configuration 78
IBM CONFIDENTIAL Extended Services Driver S1A246 79 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
A.3.1 3270TR .NDF File Example
DEFINE_LOCAL_CP FQ_CP_NAME(NETNAME.NODENAME )
CP_ALIAS(ALIASNAM)
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'00000')
HOST_FP_SUPPORT(NO);
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)
DEFAULT_MODE_NAME(BLANK)
MAX_MC_LL_SEND_SIZE(32767)
DIRECTORY_FOR_INBOUND_ATTACHES(*)
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)
DEFAULT_TP_CONV_SECURITY_RQD(NO)
MAX_HELD_ALERTS(10);
START_ATTACH_MANAGER;
A.4 Advanced Configuration for 3270 Gateway
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory.
(example: ) C>copy acscfgus.cfg 3270gw.cfg
2. Restart Communications Manager using this file.
(example: ) C>start cm 3270gw
3. Switch to the task list to access the Communications Manager Main Menu.
4. Select the Advanced action bar item and then select the Configuration pulldown
choice. Press Enter.
A message box appears displaying the name of the configuration file.
5. Press Enter.
The Specify Configuration Usage panel appears.
6. Select the first option if you intend to use this configuration on this workstation.
The Communication Configuration Menu appears.
7. Select option 3, 3270 feature profiles, and press Enter. The 3270 Feature
Configuration panel appears.
8. Select option 2, SDLC... and press Enter.
The Profile Operations panel appears.
9. Select option 2, Create/Change and press Enter.
The Create/Change 3270 Profile panel appears.
10. Select option 1, Connection, and press Enter. The Select SDLC Adapter panel
appears.
11. Select option 1, Adapter 0 and press Enter. The Create/Change 3270 Profile
panel re-appears.
Appendix A. SNA Advanced Configuration 79
IBM CONFIDENTIAL Extended Services Driver S1A246 80 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
12. Select the sessions to configure for the terminal. The Create/Change 3270
Logical Terminal Profile panel appears. Select Profile type panel appears.
Select Option 1, Terminal and press Enter.
13. Use the default values supplied for all of the fields on this panel and supply the
values for the following fields:
? Session ID/LU name
? LU local address.
14. Press Enter to return to the Create/Change 3270 Profile.
15. Press F3 two times to return to the Communication Configuration Menu.
A warning message appears stating that an appropriate DLC must be configured
before 3270 emulation can be used.
16. Press Enter to return to the Communication Configuration Menu.
17. Select option 4, SNA Feature Profiles and press Enter. The SNA feature
configuration panel appears.
18. Select Data Link Control (DLC) profiles... and press Enter. A message box
appears showing the DLC types.
19. Select option 1, SDLC... and press Enter. The DLC Adapters and Operations
panel appears.
20. Select the two options Adapter 0 and Create and then press Enter. The
Create/Change SDLC DLC Adapter Profile panel appears.
21. Use all of the default values displayed for the fields on this panel, except for the
Free unused link field. Select No for this field and press Enter. The Specify
Data Set Ready Timeout panel appears.
22. Accept the default value of 5 minutes and press Enter. The Specify Negotiable
Link Station Data panel appears.
23. Accept the defaults for the fields on this panel and press Enter.
The SNA Feature Configuration panel re-appears.
24. Select SNA network definitions and press Enter.
The SNA network definitions options panel appears. Select Create/Change, and
press Enter.
An informational message appears on Creating basic SNA node information.
25. Select the OK pushbutton to proceed to the Local Node Characteristics
configuration panel.
26. For the Required Features, specify the following:
Network ID
The network ID is the same as that supplied in the SNA base of previous
versions of Communications Manager. WARNING: The Network ID cannot
be blanks.
Local node name
The local node name is the same as that as that supplied for the PU or Control
Point in previous versions of Communications Manager.
Appendix A. SNA Advanced Configuration 80
IBM CONFIDENTIAL Extended Services Driver S1A246 81 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Node type
Accept the default node type of End Node - No Network Node Server.
For the Optional Features:
?
Use the default supplied for the Local Node ID.
? Use the same name you supplied for Local Node Name for the Local Node
Alias Name, except enter the name in all caps.
27. Select the OK push button and press Enter.
An informational message appears on the Basic SNA information created. Select
the OK push button and press enter.
The SNA Network Definition Selection panel appears. Select the Exit push
button and press Enter.
The SNA Feature Configuration panel appears.
28. Select SNA gateway profiles... and press Enter. The Select Gateway Profile
Type panel appears.
29. Select option 1, Host Connection... and press Enter. The Profile Operations
panel appears.
30. Select option 3, Create and press Enter. The Create/Change SNA Gateway
Host Connection Profile (1 of 2) panel appears.
31. Set the values for the following fields and press Enter:
DLC type SDLC (default)
Permanent connection Yes
Auto-logoff timeout (minutes) 61
The Select Adapter panel appears.
32. Select option 1, Adapter 0 and press Enter. The Create/Change SNA Gateway
Host Connection Profile (2 of 2) panel appears.
33. Leave this panel blank and press Enter. The SNA Feature Configuration panel
returns.
34. Select SNA gateway profiles... again and press Enter. The Select Gateway
Profile Type panel appears.
35. Select option 2, Workstation LU... and press Enter. The Profile Operations
panel appears.
36. Select option 3, Create and press Enter. The Specify Profile Names panel
appears.
37. Accept the default for the Model profile name field (M6) and type ALICEWS1
in the profile name field. Press Enter. The Create/Change SNA Gateway
Workstation LU Profile panel appears.
38. Set the values for the following fields and press Enter:
Appendix A. SNA Advanced Configuration 81
IBM CONFIDENTIAL Extended Services Driver S1A246 82 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
LU name at workstation ALICEWS1
Comment (Optional)
PU name of workstation ALICEPU1
LU pooling Dedicated
LU local address at workstation (hex) *
Note: Enter the LU local address entered on the
Create/Change 3270 Logical Terminal Profile.
See 13 on page 80 for the
LU local address field.
DLC type SDLC
The Specify Dedicated LU Parameters panel appears.
39. Supply a value for the LU local address at host field and accept the default value
for the Auto-logoff field (NO). Press Enter. The Select Adapter panel appears.
40. Select option 1, Adapter 0 and press Enter.
The SNA Feature Configuration panel re-appears.
41. Press F3 to return to the Communication Configuration Menu.
42. Verify the configuration and re-start the Communications Manager to use the
new configuration.
Verify from action bar, and press enter.
Select Option 1, Run Verify and press enter.
A.4.1 3270GW .NDF File Example
A node definition file is built for you with the following set of default verbs:
DEFINE_LOCAL_CP FQ_CP_NAME(APPN.ATIG )
CP_ALIAS(atig )
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'00000')
HOST_FP_SUPPORT(NO);
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)
DEFAULT_MODE_NAME(BLANK)
MAX_MC_LL_SEND_SIZE(32767)
DIRECTORY_FOR_INBOUND_ATTACHES(*)
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)
DEFAULT_TP_CONV_SECURITY_RQD(NO)
MAX_HELD_ALERTS(10);
Appendix A. SNA Advanced Configuration 82
IBM CONFIDENTIAL Extended Services Driver S1A246 83 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix B. EHLLAPI Virtual Device Driver (VDD)
# *** NOTE ***
# The EHLLAPI VDD does not function correctly with the OS/2 SE 2.0 driver
# level 6.167. To use the EHLLAPI VDD, OS/2 2.0 level 6.605 must be used.
B.1 Overview
This IBM Extended Services for OS/2 driver contains a new EHLLAPI Virtual
Device Driver (VDD) to allow existing DOS HLLAPI applications to run in the
Virtual DOS Machine on the OS/2 2.0 operating system. This appendix gives the
information on how to use the EHLLAPI VDD.
The EHLLAPI Virtual Device Driver support is installed when you install
Communications Manager with a 3270 configuration file. The Installation of the
EHLLAPI VDD will enable the user to run existing DOS HLLAPI applications in
the OS/2 2.0 Virtual DOS Machine (VDM) environment using Extended Services
EHLLAPI with the Communications Manager.
Although an effort was made to be compatable with the Personal Communications
3270 EHLLAPI 2.0, some differences exist and are noted below.
It is recommended the DOS application be recompiled and linked to be executed in
the OS/2 environment if possible. This will enhance the overall performance of the
system and allow for inclusion of the many enhancements available in the
Communications Manager EHLLAPI.
B.2 Installation
The following statement should be added to the end of the CONFIG.SYS file (it
must follow the loading of physical device drivers):
? DEVICE=x:\CMLIB\VHAPI.OS2
(where x is the logical drive on which Communications Manager is installed)
Note: Machine must be restarted after making changes to CONFIG.SYS.
Appendix B. EHLLAPI Virtual Device Driver (VDD) 83
IBM CONFIDENTIAL Extended Services Driver S1A246 84 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
B.3 Usage
Bring up the Communications Manager and start 3270 communications. Establish
the same conditions in the host session window as are required in the DOS
emulator session by the DOS HLLAPI application. Create an OS/2 2.0 VDM
Window and start the DOS HLLAPI application.
B.4 Compatability (With Personal Communications 3270 2.0)
Appendix B. EHLLAPI Virtual Device Driver (VDD) 84
IBM CONFIDENTIAL Extended Services Driver S1A246 85 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Deviations:
Because of existing differences between the Per Com and OS/2 3270
emulators there are some differences in the EHLLAPI support:
1. ASCII mnemonic differences
- The following mnemonics are not supported by PER COM 3270 2.0.
However, since the OS/2 emulator generates them they may be
received by EHLLAPI applications running in the DOS box under OS/2 2.0)
1. @q End
2. @A@D Word Delete
3. @A@L Cursor Left fast
4. @A@N Get Cursor
5. @A@O Locate Cursor
6. @A@Z Cursor Fast Right
7. @A@9 Reverse Video
8. @A@b Underscore
9. @A@c Reset Reverse video
10. @A@d Red
11. @A@e Pink
12. @A@f Green
13. @A@g Yellow
14. @A@h Blue
15. @A@i Turquoise
16. @A@j White
17. @A@l Reset Host colors
18. @/ Overrun of queue (get key function only)
19. @S@T Jump to Task Mgr (Extended Services 1.0)
- The following lists differences between mnemonics supported by
both EHLLAPIs
1. @< Backspace
- Per Com treats this as a destructive backspace
- OS2 treats this as a non destructive backspace
note: When received by an EHLLAPI application running in the
DOS box under OS/2 2.0 this mnemonic should be treated as
a non destructive backspace.
- The following mnemonics are not supported by EHLLAPI on a 3270
session
1. @S@A Erase EOL
2. @S@B Field Advance
3. @S@C Field Backspace
4. @S@D Valid Backspace character
5. @r@t Pause
2. Copy OIA content
1. Column 21
- Per Com returns value of 0xF6
- OS2 returns value of 0x20
note: The value of 0x20 will be returned in the OS/2 2.0
DOS box.
2. Columns 61-63
Appendix B. EHLLAPI Virtual Device Driver (VDD) 85
IBM CONFIDENTIAL Extended Services Driver S1A246 86 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
- Per Com will not return printer information
note: Values in these columns may be returned in the OS/2
2.0 DOS box.
3. Group 3 Shift State
- bit 2 CAPS is not returned by OS2
(bit 0 set for both upper case and CAPSLOCK in OS2 with
bit 2 reversed)
note: Bit 2 will continue to be reserved in the OS/2 2.0
DOS box.
4. Group 8 byte 1 Input Inhibited
- bit 6 Device not working not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
5. Group 8 byte 2
- bit 1 OS2 Terminal Wait not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
6. Group 8 byte 3
- bit 1 Operation unauthorized not returned by Per Com.
- bit 2 Operation unauthorized minus function not
returned by Per Com.
note: These bits may be set in the OS/2 2.0 DOS box.
7. Group 10 Highlight #2
- bit 0 Selected not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
8. Group 11 Color #2
- bit 0 Selected not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
9. Group 13 Printer Status
- This group is reserved in Per Com
note: This group may be set in the OS/2 2.0 DOS box.
10. Group 14 Graphics
- bit 0 Graphics cursor not returned by OS2
note: This bit will not be returned in the OS/2 2.0 DOS
box.
3. Presentation Space character/field attributes translated under
the XLATE parm do not match (both are supposed to be CGA format).
Note: The purpose of this function is to provide a
Char/Attribute buffer to be displayed on the applications
Appendix B. EHLLAPI Virtual Device Driver (VDD) 86
IBM CONFIDENTIAL Extended Services Driver S1A246 87 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
screen that reflects exactly the text and colors of the
host presentation space. Since the Per Com implementation
performs this function incorrectly, the attributes
returned under OS/2 will be returned without alteration.
4. Host PS null characters (0x00) are translated to blanks (0x20)
under Per Com. They are not translated under OS/2. This may
affect searches (in Per Com EHLLAPI appls) for character strings
that include blanks that are null characters under OS/2.
5. Host Presentation Space sizes supported are different between the
two emulators. A user running a Per Comm EHLLAPI application
under OS/2 2.0 must make sure that he doesn't configure a PS mod
type that is larger than the Per Com application can handle. PS
sizes for Per Com are between 1920 (24x80) and 3564 (27x132).
Sizes for OS/2 are between 1920 and 7446 (146x51).
note: OS/2 2.0 DOS will support up the the maximum OS/2 size if
the application can handle it.
6. Storage Manager is different between the APIs.
Note: Setup of Storage Manager during configuration is not
required under OS/2. The maximum of 10 K bytes is
automatically preallocated outside of the DOS heap.
7. Considerations for using functions 90 & 91 in PER COM pub do not
apply.
8. PERCOM EHLLAPI messages are not generated under OS/2.
9. In OS/2 Trace is sent to file. In PER COM it is sent to screen.
Note: Under OS/2 2.0 OS/2 trace rules will be applied.
10. Send/Receive: PM window will be created to display status
messages (non Quiet mode).
11. Send/Receive: PS Position parameter specification of 0 for
Current directory is not supported in PERCOM.
Note: Under OS/2 2.0 a specification of 0 will be supported if
received.
12. As in Per Com, the DOS EHLLAPI application running under OS/2
2.0 will run on the interrupt thread. This means that hitting
Ctrl-C and Ctrl-Break, will have no effect when the thread is
suspended, waiting for an EHLLAPI function to complete.
However, under OS/2 2.0 the user may optionally close the DOS
window running the EHLLAPI application even when the thread is
suspended waiting for a function to complete (Warning: in this
case the 3270 emulation resources remain allocated until the
pending EHLLAPI function issued by the departed DOS application
is complete).
Appendix B. EHLLAPI Virtual Device Driver (VDD) 87
IBM CONFIDENTIAL Extended Services Driver S1A246 88 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
13. Functions 41-43 (Close Click Intercept) and 101-106 (Windowing)
are not supported under Per Com.
note: These functions will not be supported under OS/2 2.0.
Appendix B. EHLLAPI Virtual Device Driver (VDD) 88
IBM CONFIDENTIAL Extended Services Driver S1A246 89 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix C. Communications Manager Stop API
C.1 Overview and Usage
Included in this driver of Communications Manager is a new API to stop the
Communications Manager. The following description is written using the same
format as the OS/2 Control Program, Programming Reference. For additional
information, see the OS/2 Control Program Programming Reference which is a
volume of the IBM OS/2 Programmer's Toolkit version 1.2.
CmkDeactivateService -
Request to Stop the Communication Manager
This call will have the Communications Manager start exit processing
when the Main Menu is displayed.
CmkDeactivateService (StopType, Service, Reserved_1, Reserved_2, rc)
PARAMETERS
StopType(USHORT) - input
Type of stop process requested.
StopType codes:
* CMK_SOFT 0 - Exit when Complete
* CMK_HARD 1 - Exit Immediate
Service(ULONG) - input
Service number of Communication Manager
* CMK_ALL_FEATURES 1 - Stop Communications Manager
Reserved_1(ULONG) - input
Reserved and should be set to 0
Reserved_2(USHORT) - input
Reserved and should be set to 0
rc(USHORT) - return
Return code descriptions are:
0 CMK_SUCCESSFUL
22 CMK_ERR_INVALID_SERVICE
23 CMK_ERR_SYSTEM_ERROR
REMARKS
This call will request the Communications Manager to start exit
processing. The CMK_SOFT stop is the equivalent of selecting
"Exit when Complete" from the EXIT pulldown on the Communications
Manager Main Menu. The CMK_HARD stop corresponds to the "Exit
immediately" option.
Processing of the stop request will only occur when the Main Panel
is being displayed, or when a user returns to the Main Panel after
preforming some action like configuration.
Appendix C. Communications Manager Stop API 89
�
INDBC167.DOC
Restrictions and Installation Instructions for
IBM Extended Services for OS/2
Database Manager Clients Feature (Driver S1A246)
October 18, 1991 2:45 p.m.
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
This document contains information of a proprietary nature. ALL INFORMATION CONTAINED
HEREIN SHALL BE KEPT IN CONFIDENCE. None of this information herein shall be divulged to
persons other than IBM employees authorized by the nature of their duties to receive such information, or
individuals or organizations who are authorized in writing in accordance with existing policy regarding release
of company information. This material, if exported from the United States, is shipped under General
License GTDR.
Restrictions and Installation Instructions for
IBM Extended Services for OS/2
Database Manager Clients Feature (Driver S1A246)
October 18, 1991 2:45 p.m.
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Database Manager Clients Restrictions/Limitations ............ . . . 2
3.0 Installation Instructions ............. . . . . . . . . . . . . . . . . . . 5
4.0 Applying Patches to the OS/2.NETBIOS.Client . . . . ....... . . . . 6
4.1 Instructions for Applying Database Manager Client.Patches . . . . . . . . 6
Contents ii
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
1.0 Introduction
This document provides the driver restrictions and installation instructions for the
Database Manager Clients feature of the IBM Extended Services for OS/2 program.
The feature consists of the following code and publications:
1. Diskettes (3 1/2" format):
? 2 OS/2 NETBIOS Database Client diskettes
? 2 DOS Database Client/DOS Windows Database Client diskettes
? 1 PC LAN Support Program diskette (** shipped with the LAN Server
V2.0 program)
2. Publications
? Guide to Database Manager Clients
? Network Administrator's Guide (** part of Extended Services
Administrator's Ship group)
? LAN Adapter and Protocol Support Configuration Guide (** part of
Extended Services Administrator's Ship group)
? PC LAN Support Program User's Guide (** part of LS V2.0 ship group
sent with previous Extended Services/LAN Server driver)
Introduction 1
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
2.0 Database Manager Clients Restrictions/Limitations
The following restrictions/limitations apply to the Database Manager Clients feature
for this driver.
?
OS/2 NETBIOS Client Installation/Custom Diskette Creation:
?You must have at least 500K Bytes available on the C: drive for use by the
OS/2 NETBIOS Client install program. If OS/2 is booted from a drive
other than C:, the C: drive is still used for temporary working space for the
install program.
# ?If OS/2 is booted from a drive other than C:, the installation of the OS/2
# NETBIOS Client will not work. CONFIG.SYS is incorrectly updated
# (causing multiple error messages during IPL) and several files do NOT get
# installed.
# The workaround, if you plan to install the client from an OS/2 system
# which has been booted from a drive other than C:, is as follows:
# ?Edit the INSTALL.CMD file on the OS/2 NETBIOS Database Client
# Installation Diskette #1:
# Change the designated drive in line PKUNZIP2 REQINSTR.ZIP C:\
# -o -d 1>NUL 2>NUL to the drive you have booted your system
# from.
?If you are attempting to install the OS/2 NETBIOS Client on top of a
previous version of Extended Services, you must first erase the file
x:\IBMLVL.INI (where x: is the drive which OS/2 is booted from).
?During Install, the ONLY valid network adapters are the ones currently
listed in the Guide to Database Manager Clients under "Software and
Hardware Requirements. The menu that comes up during Install to allow
you to select your network adapter incorrectly lists more adapters than can
validly be selected.
?You CANNOT create a Custom Build Diskette for an OS/2 SE V2.0
workstation. The diskette that gets created will ONLY work on OS/2 SE
V1.30.1 workstations.
?After creating a custom diskette, you are told to remove the diskette. If you
do so BEFORE you press 'enter', you will get a "drive not ready" message.
Leave the custom diskette in drive a: until after pressing 'enter'.
?During Install, after selection of the network adapter, the "percentage of
installation complete" indicator is not correctly displayed. (** OS/2 SE V2.0
Level 6.605 ONLY)
?During Install and/or Custom Diskette creation, 'HELP' does not work
from the following panels/menus:
?Incompatible Versions
?File Backup
?Source Drive
Database Manager Clients Restrictions/Limitations 2
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
?On the panel asking you to check the terms and conditions of the licensing
agreement, there is a 'HELP' pushbutton, but it has no effect.
?On the Custom Diskette Panel, 'HELP' states that you will need a second
diskette, however you do not always need one.
? DOS Database Client/DOS Windows Database Client:
?You CANNOT run any DOS Database client or DOS Windows Database
client applications in OS/2's DOS Compatibility mode (i.e., from the DOS
box)
? There are NO online helps for Database Manager. You will need to refer to the
Extended Services for OS/2 Messages and Error Recovery Guide, Database Only
for the explanation of error messages.
? Corrections to Guide to Database Manager Clients
1. Pages 4-3, and 4-4:
?Steps 1 and 2 should be replaced by:
Type the following at the command prompt and press Enter: INSTDB
2. Page 3-7
?In step 8 the Workstaion Name Panel is displayed instead of the
Installation and Configuration Panel.
?Step 9 should be replaced with:
Type in the name of your workstation and select OK or press enter.
The "Copying files - Please wait" popup is displayed. While the system
copies files, the percentage of the diskette that is copied and the amount
of time elasped is continually updated on this panel. The Options panel
is displayed next.
?Step 10 should be removed.
?In steps 13 and 14 the cursor will not automatically move; it must be
tabbed or selected via a mouse.
?Step 14 should be replaced with:
Select Add to accept IBM OS/2 NETBIOS. Your selection (IBM OS/2
NETBIOS) is displayed in the current configuration field (beneath the
Network Adapters field). When all options are complete move to OK
and press enter. The Options panel is now displayed.
?Step 15 should be replaced with:
When all configuring is complete, press Configuration Complete. A
warning panel asking you to check the terms and conditions
information to verify that you can copy the network driver information
is displayed.
3. Appendix B, page B-3, "DBM Catalog NETBIOS Node"
?The syntax diagram has an error. You need to precede the adapter
number (0 or 1) with the keyword 'ADAPTER' or you will get an
error.
Database Manager Clients Restrictions/Limitations 3
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
Database Manager Clients Restrictions/Limitations 4
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
3.0 Installation Instructions
The installation instructions for this feature are included in the Guide to Database
Manager Clients publication which has been included with this driver shipment.
Once you have read and understood ALL restrictions and limitations that apply to
this driver, please refer to the above-mentioned publication for all details of
installing and configuring your client workstations.
Important Installation Note
If you are installing an OS/2 NETBIOS Client, you MUST apply some patches
after you complete the installation. After you have completed the installation
steps in the Guide to Database Manager Clients, return to this document and
follow the instructions in 4.0, 嗀pplying Patches to the OS/2 NETBIOS Client?
on page 6
Installation Instructions 5
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
4.0 Applying Patches to the OS/2 NETBIOS Client
After your OS/2 NETBIOS Client is installed, you must apply the necessary
patches.
Note
This applies ONLY to OS/2 NETBIOS Clients; it DOES NOT apply to DOS
Database Client or DOS Windows Database Client.
4.1 Instructions for Applying Database Manager Client Patches
*** NOTEs: ***
1. In order for the patches to be applied correctly, you MUST take the steps
below after Database Manager Client installation is complete.
2. If you need to re-install the Database Manager Client, the patch process
MUST be repeated after the re-installation.
1. Insert the patch diskette #1 in drive A:
2. From the OS/2 command prompt, enter the following command.
Note: The replace command will replace files based upon the features you have
installed on your PC. If you have installed features which do not require any
patches, then the replace command may not replace any files.
? REPLACE A:\CMPATCH\*.* z:\IBMCOM /S
where z is the logical drive on which OS/2 is installed.
3. Insert patch diskette #2 in driver A:, and type the following:
a:dbclient x:
(where x is the drive on which the Database Manager client is installed) and
press Enter.
4. Remove the patch diskette.
# 5. Use the Desktop Manager Shutdown feature to stop and reboot your system, if
# you are using OS/2 SE V1.3 with Manufacturing Refresh 1.30.1. If you are
# using OS/2 SE V2.0 Level 6.167, you should move the mouse to a blank area of
# the workplace desktop (i.e., not on an object or folder) and press mouse button
# #2. From the pull-down that appears, select "Shutdown" and follow the
# directions.
Applying Patches to the OS/2 NETBIOS Client 6
�
INST6167.DOC
OS/2 32-Bit Operating System
Installation Guide
PRE-RELEASE COPY
October 10, 1991
First Edition October 1991 < *
The following paragraph does not apply to the United Kingdom or any
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION 嗀S IS?WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not apply
to you.
This publication could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services
that are not announced in your country. Such references or information
must not be construed to mean that IBM intends to announce such IBM
products, programming, or services in your country.
Requests for technical information about IBM products should be made to
your IBM Authorized Dealer or your IBM Marketing Representative.
+ Copyright International Business Machines Corporation 1991. All rights
reserved.
Note to U.S. Government Users ?Documentation related to restricted
rights ?Use, duplication or disclosure is subject to restrictions set forth
in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
About This Book ..... . . . . . . . . . . . . . . . . . . . . . . . ix
How This Book is Organized. ....... . . . . . . . . . . . . . ix
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 1. Choosing an Installation.Procedure. ........ 1
Basic Installation. ..... . . . . . . . . . . . . . . . . . . . . . . . 3
Advanced Installation Choices. . . . ....... . . . . . . . . . 4
Running OS/2 2.0 and DOS on the Same System. . . . . . . . 4
Multiple Operating System Installation ........... . . . 6
Alternative Ways to Install. . . . ....... . . . . . . . . . . 6
Choosing an Advanced Installation.Procedure. ...... . 6
Special Note about Reconfigurable Diskette.Drives . . . . . 7
Chapter 2. Installing OS/2 2.0 as the Only Operating System . . 9
Setting Up Your Hard Disk. . . . ....... . . . . . . . . . . . . 9
Selecting the Operating System.Features . . . . . ...... . 12
Configuring the System ....... . . . . . . . . . . . . . . . . . 14
Viewing the Tutorial ....... . . . . . . . . . . . . . . . . . . . 16
Chapter 3. Adding OS/2 2.0 to a DOS System. . . . . . . . . . 17
Dual Boot Requirements ....... . . . . . . . . . . . . . . . . 18
Setting Up Your System for Dual Boot. . . . . ......... . 19
Making Sure Your DOS Directory Structure Is.Correct . . . 19
Creating or Modifying the AUTOEXEC.BAT and CONFIG.SYS
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Installing the OS/2 Version 2.0 Operating.System .... . . . 22
Viewing the OS/2 Tutorial. . . . ....... . . . . . . . . . . . 24
Starting the Dual Boot Feature ......... . . . . . . . . . . 24
Chapter 4. Installing Multiple Operating Systems .... . . . . 25
How This Chapter is Organized ......... . . . . . . . . . . 25
An Overview of the Boot Manager ......... . . . . . . . . 26
Hard Disk Management . . . . ....... . . . . . . . . . . . . . 27
Planning for a Boot Manager.Setup. . ..... . . ... . . 31
Sample FDISK Screen. . . ..... . . . . . . . . . . . . . . . 33
Getting Ready for Installation ......... . . . . . . . . . 35
+ Copyright IBM Corp. 1991 iii
Starting the OS/2 2.0 Installation ......... . . . . . . . . . 36
Installing OS/2 2.0 on a New System. . . . . ......... 36
Installing OS/2 2.0 on an Existing System. . . . . . . . . . . 37
Setting Up Your Hard.Disk . . . ..... . . . . . . . . . . . . . 39
Deleting Existing Partitions ......... . . . . . . . . . . . 39
Creating the Boot Manager Partition. . . . . ......... 41
Creating Partitions for Operating Systems Other than OS/2
2.0 and for Logical Drives. . . . ....... . . . . . . . . . 42
Options Menu Choices ....... . . . . . . . . . . . . . . 44
Specifying Options . . . . . . . . . . . . . . . . . . . . . . . 46
Creating the Partition or Logical Drive for OS/2.2.0 . . . . 47
Specifying Options for the OS/2 2.0 Partition or Logical Drive 48
Saving Your Changes. . . ..... . . . . . . . . . . . . . . . 52
Continuing with OS/2 2.0 Installation. . . . . ......... . . 53
Selecting the Operating System.Features . . . . . .. . . . 53
Formatting Logical Drives. . . . ....... . . . . . . . . . . 53
Viewing the Tutorial. . . ..... . . . . . . . . . . . . . . . . . . 53
Installing Other Operating Systems ......... . . . . . . . 54
Chapter 5. Alternative Ways to.Install. ....... . . . . . . 59
Understanding the Response File Installation .......... 59
Modifying the Response File. . . . ....... . . . . . . . . . . 60
Installing OS/2 2.0 from a Source Other than Drive A . . . . . . 63
Redirecting the Installation ......... . . . . . . . . . . . 63
Setting Up an Alternative Installation.Source ..... . . . 64
Installing from a CD-ROM.Device . . . . ....... . . . . 64
Appendix A. Customizing the Operating.System ... . . . . 67
Features that You Can Change.or Add . ....... . . . . . . 67
Changing Your Setup or Adding Features. . . . . ........ 69
Appendix B. Diagnosing System Problems. . . . . ...... . 71
Recovering the CONFIG.SYS File. . . . ....... . . . . . . . 71
Recovering User and System INI.Files. . ..... . . ... . . 72
Recovering from Errors on the Hard Disk. . . . . ........ 74
Responding to Installation.Errors . . . . ....... . . . . . . 75
Making the Boot Manager Active. . . . ....... . . . . . . . 76
Appendix C. Examples of Installing OS/2 2.0 and Partitioning
Your Hard Disk ..... . . . . . . . . . . . . . . . . . . . . . . . 77
ivOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Example 1: Creating a Primary Partition and a Logical Drive for
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Example 2: Installing the Boot Manager, OS/2 2.0, and One
Additional Operating.System . . . . ....... . . . . . . . . 80
Example 3: Installing the Boot Manager, OS/2 2.0, and Two
Additional Operating Systems ......... . . . . . . . . . . 82
Example 4: Installing Boot Manager without Repartitioning the
Entire Hard Disk. . . ..... . . . . . . . . . . . . . . . . . . . 85
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Contents v
viOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Notices
References in this publication to IBM products, programs, or
services do not imply that IBM intends to make these available in
all countries in which IBM operates. Any reference to an IBM
product, program or service is not intended to state or imply that
only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not
infringe any of IBM's intellectual property rights or other legally
protectible rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in
conjunction with other products, programs, or services, except
those expressly designated by IBM, are the user's responsibility.
IBM may have patents or pending patent applications covering
subject matter in this document. The furnishing of this document
does not give you any license to these patents. You can send
license inquiries, in writing, to the IBM Director of Commercial
Relations, IBM Corporation, Purchase, NY 10577.
The following terms, denoted by a single asterisk (*), used in this
publication, are trademarks or service marks of the IBM
Corporation in the United States or other countries:
AIX IBM Operating System/2
OS/2 Personal System/2 Presentation Manager
PS/2 SAA Systems Application
Architecture
The following terms, denoted by a double asterisk (**), used in this
publication, are trademarks of other companies as follows:
Adobe Adobe Systems Incorporated
Adobe Type Adobe Systems Incorporated
Manager
Helvetica Linotype Company
Microsoft Microsoft Corporation
PostScript Adobe Systems Incorporated
Windows Microsoft Corporation
+ Copyright IBM Corp. 1991 vii
viii OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
About This Book
This book provides detailed instructions on installing the IBM *
*OS/2 operating system.
How This Book is Organized
This book has the following chapters and appendixes:
Chapter 1 provides you with an overview of the various
installation options.
Chapter 2 describes a basic installation procedure that installs
the OS/2 operating system as the only operating system on
your hard disk.
Chapter 3 describes the procedure for adding OS/2 2.0 to an
existing DOS system, so that you can switch between the
operating systems.
Chapter 4 describes how to partition your hard disk during
installation, so that you can install multiple operating systems.
Chapter 5 describes alternatives to the typical installation
procedure, such as using the same installation choices for
multiple computers.
Appendix A briefly describes ways to customize your system
after installation.
Appendix B describes how to recover from errors.
Appendix C provides four examples of partitioning the hard
disk during installation.
* Trademark of the IBM Corporation.
+ Copyright IBM Corp. 1991 ix
Related Information
Overview This book contains general information about the OS/2
operating system. It also shows you which
combinations of keys to use to perform specific actions.
Quick Reference
This card provides you with a very brief set of
instructions on how to start the installation of the OS/2
operating system. It is intended primarily for those who
want to accept most or all of the preselected choices
during installation. Note that the card provides only
limited instructions to get you started. If you want more
detailed information about installing the operating
system, use this book.
The following publication will be available and can be ordered
separately:
OS/2 Version 2.0 Remote Installation and Maintenance (GG24-3780).
This book provides detailed information about setting
up remote installations (such as installations across a
local area network).
xOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 1. Choosing an Installation Procedure
This book describes how*to install the IBM * OS/2 Version 2.0
operating system. It describes the basic installation procedure,
which installs OS/2 2.0 as the only operating system on your hard
disk. It also describes advanced installation procedures, for those
who have unique system requirements (such as the need to install
multiple operating systems).
If you follow the basic installation procedure, you will be able to
**
run programs written for DOS and Microsoft Windows as well as
OS/2 programs--all under OS/2 2.0.
* Trademark of the IBM Corporation
** Trademark of the Microsoft Corporation.
+ Copyright IBM Corp. 1991 1
+----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+----------------------------+
2OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Basic Installation
This book describes the basic installation procedure as well as
more advanced procedures. Most people will find that the basic
installation procedure works best for them because their programs
written to run under DOS, Microsoft Windows, and the OS/2
operating system will run under OS/2 2.0.
The installation procedure begins when you insert the Installation
Diskette and restart the system. From that point on, most of the
information you need to help you install the system can be found
on the screens.
During the installation, you will be asked to make choices about
how you want your system set up. Each time you are asked to
make a choice, a default (preselected) choice will be provided. If
you want to accept these default choices, you can go now to the
Quick Reference card, which will give you instructions on how to
start the installation.
However, if you want more information about the choices you can
make during installation, or if you want assistance in completing
the installation, you can refer to Chapter 2, 蘒nstalling OS/2 2.0 as
the Only Operating System?on page 9.
To complete the basic installation procedure and set up OS/2 2.0
as the only operating system, choose one of these:
?
�葺葺葺莨葺葺葺葙
�葺葺馆葺葙 �葺葺馆葺葙
�Quick � � Chapter �
�Reference� � 2 �
�card � � �
� � � �
�葺葺葺葺? �葺葺葺葺?
If, instead, you want to install the OS/2 Version 2.0 operating
system according to one of the more advanced procedures (for
example, if you want to keep a version of DOS on the same system
with OS/2 2.0), continue to 嗀dvanced Installation Choices?on
page 4.
Chapter 1. Choosing an Installation Procedure 3
Advanced Installation Choices
Although installing OS/2 2.0 by itself is the procedure that will be
best for most people, you might have specific requirements to
install more than one operating system or to keep a version of
DOS on your system when you install OS/2 2.0.
Running OS/2 2.0 and DOS on the Same System
The OS/2 Version 2.0 operating system is designed to run
programs written for DOS and Microsoft Windows. These
programs run in a version of DOS that is optimized for the OS/2
environment. However, some programs will run only under a
specific version of DOS. If you have such a program, you might
want to consider running a specific version of DOS with OS/2 2.0.
There are three ways that you can set up your system to
accomplish this.
? You can load a version of DOS into a DOS session of OS/2 2.0.
The version of DOS can exist on another partition on the hard
disk or it can be on diskette.
?
You can install OS/2 2.0 on a system that already contains
DOS and then use the BOOT command to switch between the
operating systems. (This is called the Dual Boot feature.)
? You can install multiple operating systems on the hard disk of
your computer. Then, each time you start your computer, you
can select which operating system you want to be active. (You
use the Boot Manager feature to manage the startup of the
operating system.)
The following is a brief summary to help you decide which of these
choices is right for you.
4OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Run a version of Add OS/2 2.0 to a Install DOS and
DOS from within DOS partition (Dual OS/2 in their own
OS/2 2.0. Boot). partitions (Boot
Manager).
? You can either ? You do not have ? You must
partition your to partition your partition the
hard disk (and hard disk. hard disk during
install DOS in its installation.
own partition),
or you can start
DOS from a
diskette.
? You start DOS in ? You use the ? When you start
a DOS session BOOT command the computer,
of OS/2 to switch you select which
whenever you between DOS operating
need it. and OS/2 2.0. system to use.
? DOS can run in ? OS/2 2.0 and ? OS/2 2.0 and
a window while DOS do not DOS do not
OS/2 2.0 operate at the operate at the
continues to run. same time. same time.
You do not have
to shut down
OS/2 2.0 and all
OS/2 programs
to run a specific
version of DOS.
? You must modify ? You might have ? You do not have
DOS system to modify DOS to modify any
files after you system files or DOS system
install OS/2 2.0 change the files.
and DOS. directory
structure before
you install OS/2
2.0.
As you can see, each of the choices has certain advantages. For
example, if you start a version of DOS from within the OS/2
operating system, you can run the DOS version while continuing to
take advantage of the multitasking features of OS/2 2.0.
Chapter 1. Choosing an Installation Procedure 5
Multiple Operating System Installation
With the Boot Manager feature of OS/2 2.0, you can have multiple
operating systems installed in separate partitions of your hard
disk. Once the operating systems are installed, you use the Boot
Manager to select which one you want to start. As mentioned in
the previous section, you can install OS/2 2.0 and a version of DOS
in their own partitions, and then use the Boot Manager to select
one at startup time. You can install other operating systems (such
as AIX * ) as well.
Alternative Ways to Install
You can install OS/2 2.0 using a response file, which contains
information the installation program uses to set up a system.
When a response file is used, the installation program does not
prompt for decisions. This type of installation is typically used in
multi-workstation environments, where many computers are being
set up. You can also redirect the installation of OS/2 2.0 to a
source other than the diskette in drive A.
Choosing an Advanced Installation Procedure
If you have chosen to do something other than the basic
installation, select one of these advanced installation procedures:
?
�葺葺葺葺葺葺葺葺葺葺篙葺葺葺葺葺葺葺葺葺葙
�葺葺馆葺葙 �葺葺馆葺葙 �葺葺馆葺葙
� Chapter � � Chapter � � Chapter �
� 3 � � 4 � � 5 �
� � � � � �
� � � � � �
�葺葺葺葺? �葺葺葺葺? �葺葺葺葺?
Add OS/2 2.0 to Install OS/2 2.0 Install using a
a DOS system and other response file or
(Dual Boot). operating systems install from a
(Boot Manager). source other than
drive A.
* Trademark of the IBM Corporation.
6OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
The procedure for starting a version of DOS from diskette is
described in the online information, which is available on your
screen after you install the OS/2 Version 2.0 operating system.
Special Note about Reconfigurable Diskette Drives
Some systems that contain multiple diskette drives provide the
capability to read a self-starting diskette (such as the Installation
Diskette) from a drive other than A.
For example, suppose you have two diskette drives: A (for 3.5-inch
diskettes) and B (for 5.25 diskettes). If you load a self-starting
diskette in drive B and restart the system, the diskette in drive B
will be loaded.
If you have a system with multiple diskette drives and you want to
load the installation diskettes from a drive other than A, you will
need to reassign that other drive to make it the primary drive in
the startup sequence. See the documentation that came with your
computer for information on making a drive other than A the
primary drive.
Chapter 1. Choosing an Installation Procedure 7
8OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 2. Installing OS/2 2.0 as the Only
Operating System
This chapter describes how to install OS/2 2.0 as the only
operating system on your computer. It also provides information
to help you make choices about which features of the operating
system you want to install.
You can use the procedure in this chapter whether you are
installing on a new system or on a system that already contains
data. For example, if you already have OS/2 Version 1.3 on your
hard disk, you can use the procedure in this chapter to replace it
with OS/2 Version 2.0.
You can also use the procedure in this chapter to replace a DOS
system with OS/2 2.0. However, if you want to keep a version of
DOS on your system, see Chapter 3, 嗀dding OS/2 2.0 to a DOS
System?on page 17.
Note: If an error message is displayed while you are installing the
operating system, see esponding to Installation Errors?
on page 75 for an explanation of the message and the
corrective action.
In the first part of the installation, you will make choices about how
the hard disk on your system should be set up.
Setting Up Your Hard Disk
To begin the installation of the operating system, do the following:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt and
press Del to restart the system. The following screen appears:
+ Copyright IBM Corp. 1991 9
+---------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+---------------------------+
3. Remove the Installation Diskette, insert Diskette 1, and press
Enter.
You will be prompted at various points during installation to
remove the diskette in drive A and to insert another diskette.
Be sure to leave the diskette in drive A until the instructions
direct you to replace it. You will replace diskettes several
times before the operating system finishes copying information
from the diskettes to the hard disk of your computer.
4. As information is displayed, either accept it or change it. If
you want to set up a default system that works best for most
people, you can accept the preselected choice on each screen
by pressing Enter.
During this part of the installation, you will be asked whether
you want to accept the default installation partition or to
specify your own partition. A partition is a fixed-sized area on
the hard disk. If you are installing on a disk that contains no
data and you accept the default installation partition, the
installation program installs the operating system in one
partition that takes up the entire hard disk. If you are installing
on a system that already contains partitions, the installation
10OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
program indicates which partition it will use to install OS/2 2.0.
You can either accept this default choice or select another
partition.
Accepting the default partition works well for most people. If
you want to install the operating system in the default partition,
simply accept the preselected choices.
If you are not sure of a choice, press F1 for help.
A note about partitioning
If you want to create more than one partition on your hard disk,
or if you receive a message stating that an existing partition is
not large enough to hold OS/2 2.0, you will need to specify
information about partitions. When you select other than the
default partition, you see the FDISK utility screen. On this
screen, you use the Options menu to create the partitions.
(The Options menu is displayed when you highlight an entry on
the FDISK screen and press Enter.)
An example of creating more than one partition on the hard
disk is included in Appendix C, 﨓xamples of Installing OS/2
2.0 and Partitioning Your Hard Disk?on page 77. You might
want to follow that example now if you are setting up more
than one partition on the hard disk.
At a certain point in the installation process, you will be notified
that the hard disk setup is complete. You will then be asked to
restart your system by removing the diskette and pressing Enter.
Chapter 2. Installing OS/2 2.0 as the Only Operating System 11
Selecting the Operating System Features
Once the hard disk of your computer is set up, you see the OS/2
Setup and Installation screen. In this part of installation, you make
choices about which features of the operating system you want to
install.
+---------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+---------------+
The default choice on this screen is Learn how to use a mouse. If
your system has a mouse attached, but you are unfamiliar with
using the mouse, press Enter to select this choice. The Learn how
to use a mouse program teaches you how to use the mouse to
make selections from the screen.
The Install preselected features choice copies the most commonly
used features of the OS/2 operating system to your hard disk. It
does not copy all the features of OS/2 2.0 to your hard disk. (For
example, Install preselected features does not copy such features
as the Command Reference or REXX Information online documents
or the games that are provided with OS/2 2.0.) This choice is
useful if you want to save hard disk space.
The Install all features choice copies the entire OS/2 operating
system to your hard disk.
The Select features and install choice gives you the opportunity to
indicate which features of the operating system you want to install.
This choice is similar to Install preselected features because, by
installing only certain features, you can save hard disk space.
With this choice, however, you decide which features you want to
12OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
install. Also, if you partitioned your hard disk during the first part
of installation, you can format any logical drives that you
previously set up.
To select a choice, do one of the following:
? Use the Down Arrow ( ? ) key to highlight the choice, and then
press Enter.
? Move the mouse pointer until it is on the choice, and quickly
press mouse button one twice.
You next see the System Configuration screen, which lists your
country configuration and device support (for example, mouse,
keyboard, and display). You can change any of the items by
selecting the item and then selecting the OK push button.
If you chose Select features and install, you see a screen on which
you indicate which features you do not want to install. +-----------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------------+
If there is a feature that you will not need, you can choose not to
install it by removing the | next to the feature. To remove the |,
do one of the following:
? Move the mouse pointer to the feature and click once with the
mouse.
? Move the cursor to the feature and press the Spacebar.
Chapter 2. Installing OS/2 2.0 as the Only Operating System 13
If a More push button is displayed next to a feature, select the
push button to view more choices.
For example, if you decide you want to install only some of the
documentation, you select the More push button to the right of
Documentation to display a list of the documentation. Then, you
remove the | that is next to any documentation you do not want to
install.
Notice the number that is shown to the right of each feature. The
number signifies the amount of hard-disk space required to install
that feature.
For a description of the features, press F1, or see 﨔eatures that
You Can Change or Add?on page 67 for a description of all the
features.
The OS/2 Setup and Installation screen also contains a choice that
lets you format any logical drives you might have set up earlier in
the installation. If you partitioned your hard disk and set up logical
drives for data, you can format them now. To do so, select the
Options menu bar choice, and then select Format. Indicate which
file system (High Performance File System or File Allocation Table)
you want to use to format the logical drive.
Configuring the System
When most of the system files have been transferred, you will see
the Advanced Options screen. Some of the choices on this screen
are available only if you are installing on a hard disk that
contained an existing operating system. For example, if you had a
previous version of the OS/2 operating system on the hard disk,
the Migrate CONFIG.SYS/AUTOEXEC.BAT choice is available. You
use this choice to copy customization information from your
existing operating system to OS/2 2.0.
14OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Special note about migrating the CONFIG.SYS file
If you select Automatically update CONFIG.SYS amd
AUTOEXEC.BAT, you will notice that some device driver
statements from the existing CONFIG.SYS file are copied to the
new file but are preceded with a comment statement. These
statements are commented out because some device drivers
that were designed to operate with previous versions of DOS or
the OS/2 operating system might not operate with OS/2 2.0.
Such device drivers could cause problems with OS/2 2.0.
You can edit the CONFIG.SYS file after installation and remove
the comment statements from the lines that you want to be
active. Save a copy of the CONFIG.SYS file before you modify
it. In the event that a device driver causes problems, you can
use the procedures described later in this book to recover the
file.
If you have existing DOS or Microsoft Windows programs on your
hard disk, you will be asked whether you want to move these
programs into your OS/2 system.
On this screen, you will also indicate which printer should be used
as your default printer.
For specific information about these choices and for help using the
choices, press F1.
Chapter 2. Installing OS/2 2.0 as the Only Operating System 15
Viewing the Tutorial
After the operating system is installed and you have restarted the
system, the OS/2 Tutorial is displayed: +--------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------+
The tutorial shows you how to use the features of the OS/2
operating system. View the tutorial now. When you have finished,
explore the features of the operating system, and enjoy!
16OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 3. Adding OS/2 2.0 to a DOS System
This chapter describes how to install the OS/2 Version 2.0
operating system on a hard disk that already has DOS installed so
that you can use both operating systems. The OS/2 Version 2.0
operating system is installed along with DOS in the primary
partition of your hard disk.
By following the procedures in this chapter, you set up your
system to use Dual Boot. With Dual Boot, you can switch back and
forth between the DOS and OS/2 operating systems. For example,
if you have a DOS program that runs only under the DOS operating
system, you could switch to DOS and run the program.
Note: It is assumed that DOS is already installed on your system
and that you are familiar with using DOS.
You will add OS/2 2.0 to the same partition in which DOS resides.
Keep in mind that the DOS and OS/2 operating systems cannot
operate at the same time. You switch between the operating
systems using the BOOT command.
Another way to use DOS:
With Version 2.0 of the OS/2 operating system, you can run a
specific version of DOS (for example, DOS Version 5.0) from a
DOS session within OS/2 2.0. You can run DOS Version 5.0, for
example, while your other programs continue to run under
OS/2 2.0. So, if you want to be able to run a version of DOS
while OS/2 2.0 is running, you can set up DOS in its own
partition on the hard disk (which is explained in Chapter 4,
蘒nstalling Multiple Operating Systems?on page 25.) Or, you
can run a version of DOS from a DOS diskette. For information
on running a version of DOS from a DOS diskette, see the
online information, which is displayed on your screen after you
install the operating system.
+ Copyright IBM Corp. 1991 17
Dual Boot Requirements
Before you begin the procedures in this chapter, you should be
aware of the following:
?
DOS Version 3.2 or higher must be installed on your hard disk.
OS/2 2.0 will work with DOS Version 3.2; however, to take full
advantage of OS/2 capabilities, use DOS Version 3.3 or higher.
? The DOS operating system must exist on drive C before the
OS/2 operating system is installed. The Dual Boot feature is
operable only after OS/2 2.0 is installed.
? You can start either DOS or the OS/2 operating system from
the same partition on your hard disk. Note, however, that you
cannot use this feature with the High Performance File System.
The DOS operating system will not recognize or be able to use
anything within a High Performance File System partition.
? If you already have a previous version of the OS/2 operating
system with the Dual Boot feature or DOS installed on the
target hard drive, the existing operating systems must be
startable for the Dual Boot feature to work correctly. (Use the
FDISK utility program of DOS if you want to check whether the
version of DOS is startable.) Be sure that the DOS operating
system installed is the version you wish to use with the Dual
Boot feature.
? Your primary partition must be at least 24MB (MB equals 1 048
576 bytes) for the DOS and OS/2 operating systems to exist on
drive C. You should consider the size of both operating
systems and also leave room for the growth of a swap file. (A
swap file contains segments of a program or data temporarily
moved out of main storage.) A typical swap file is between 4
and 8MB. If your existing primary partition is not large
enough, use the DOS FDISK command to change your hard
disk setup. Follow the instructions in your DOS documentation.
QUESTION
Do you have OS/2 Version 1.2 or 1.3 with the Dual Boot feature
currently installed on your hard disk? If so, go to 蘒nstalling
the OS/2 Version 2.0 Operating System?on page 22.
18OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Setting Up Your System for Dual Boot
Before you install OS/2 Version 2.0, you will check to see that your
DOS system is set up correctly.
? All DOS commands and utility programs must be located in a
subdirectory, such as C:\DOS, and not in the root directory.
? You must create or modify the DOS operating system
CONFIG.SYS and AUTOEXEC.BAT files on your system and put
them in the root directory of your hard disk before the OS/2
operating system is installed. This includes setting the SHELL,
COMSPEC, PATH, and APPEND statements to find the DOS
command files in the appropriate subdirectory.
In the next section of this chapter, you will check to see that your
setup meets these conditions.
Making Sure Your DOS Directory Structure Is Correct
1. Start your computer using the DOS operating system that is on
your hard disk, and go to the DOS command prompt.
2. For the Dual Boot feature to work correctly, your CONFIG.SYS
and AUTOEXEC.BAT files must remain in your root directory.
All other DOS system files, including the COMMAND.COM file,
must exist in a subdirectory.
? If your DOS system files and the COMMAND.COM file
already exist in a subdirectory, go directly to 﨏reating or
Modifying the AUTOEXEC.BAT and CONFIG.SYS Files?on
page 21.
? If your DOS system files and COMMAND.COM do not
already exist in a subdirectory, continue to step 3.
3. Type the following command to create a DOS subdirectory on
your C drive:
MD C:\DOS
and press Enter.
Chapter 3. Adding OS/2 2.0 to a DOS System 19
4. To make sure your root directory and DOS subdirectory are set
up properly, follow these steps:
a. Copy all the files from the root directory of the hard disk to
the DOS subdirectory by typing:
COPY C:\*.* C:\DOS
Then press Enter.
Note: Although this step copies your CONFIG.SYS and
AUTOEXEC.BAT files to the DOS subdirectory, step
4c returns the files to where they properly belong.
b. Delete all of your files from the root directory of the hard
disk.
Warning: Be sure to type the command correctly. When
you enter the command, all files will be deleted, and you
will not be able to recover the data. You will be asked if
you are sure you want to use this command.
Type:
DEL C:\*.*
Then press Enter.
c. Place your existing AUTOEXEC.BAT file in the root
directory by typing:
COPY C:\DOS\AUTOEXEC.BAT C:\
Then press Enter.
Place your existing CONFIG.SYS file back in the root
directory by typing:
COPY C:\DOS\CONFIG.SYS C:\
Then press Enter.
d. Continue with 﨏reating or Modifying the AUTOEXEC.BAT
and CONFIG.SYS Files?on page 21.
20OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Creating or Modifying the AUTOEXEC.BAT and
CONFIG.SYS Files
Before installing the OS/2 operating system, you must create or
modify the DOS CONFIG.SYS and AUTOEXEC.BAT files on your
hard disk. This includes setting the SHELL, COMSPEC, PATH, and
APPEND statements to find the DOS command files in the
appropriate subdirectory.
To create or modify the DOS AUTOEXEC.BAT and CONFIG.SYS
files, do the following:
1. Using any editor (for example, EDLIN), add the following
statements, if they do not already exist, to the AUTOEXEC.BAT
file:
SET COMSPEC=C:\DOS\COMMAND.COM
PATH C:\DOS
APPEND=C:\DOS
COPY C:\DOS\COMMAND.COM C:\ >NUL
To the CONFIG.SYS file, add:
SHELL=C:\DOS\COMMAND.COM /P
Note: These statements include the minimum required
parameters. You can specify additional parameters if
you wish, but be sure that the DOS directory is specified
as indicated.
During OS/2 installation, OS/2 CONFIG.SYS and
AUTOEXEC.BAT files are created. The OS/2 operating system
places any existing DOS CONFIG.SYS and AUTOEXEC.BAT
files in the C:\OS2\SYSTEM subdirectory with a .DOS
extension. This is to make sure that the OS/2 operating
system uses the correct AUTOEXEC.BAT and CONFIG.SYS files
during system restart.
Note: If you are using DOS Version 4.0 and you want to use
the DOS shell, you must change the directory specified
in DOSSHELL.BAT from CD to CD\DOS. If this change
is not made, you will receive the message, Mouse file
. missing or unreadable
2. Remove any diskette from drive A.
3. Press and hold Ctrl+Alt; then press Del to restart the system.
Chapter 3. Adding OS/2 2.0 to a DOS System 21
If the system does not operate, review the previous steps to
make sure you have completed all of them. Remember, you
must have a working copy of DOS installed and it must not be
in the root directory.
Continue with 蘒nstalling the OS/2 Version 2.0 Operating System.?
Remember, do not select the FORMAT option while installing the
OS/2 operating system. After the operating system is installed,
you can start the Dual Boot feature. (See tarting the Dual Boot
Feature?on page 24.)
Installing the OS/2 Version 2.0 Operating System
If you have DOS or Microsoft Windows programs that you want to
install, install them before you install the OS/2 operating system.
Note: If an error message is displayed while you are installing the
operating system, see esponding to Installation Errors?
on page 75 for an explanation of the message and the
corrective action.
To install the operating system, do the following:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
then press Del to restart the system. The following screen
appears:
22OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
+-----------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------------+
3. Remove the Installation Diskette, insert Diskette 1, and press
Enter.
You will be prompted at various points during installation to
remove the diskette in drive A and to insert another diskette.
Be sure to leave the diskette in drive A until the instructions
direct you to replace it. You will replace diskettes several
times before the operating system finishes copying information
from the diskettes to the hard disk of your computer.
4. As information is displayed, either accept it or change it.
Remember that you should not format your hard disk during
installation.
If you are not sure of a choice, press F1 for help. (Or, you can
refer to Chapter 2, 蘒nstalling OS/2 2.0 as the Only Operating
System?on page 9, which provides additional information
about installing the operating system.)
Chapter 3. Adding OS/2 2.0 to a DOS System 23
Viewing the OS/2 Tutorial
When the operating system is installed and you have restarted the
system, the OS/2 Tutorial is displayed. The tutorial shows you
how to use the features of the OS/2 operating system. View the
tutorial now, and enjoy the new world of OS/2 2.0.
Starting the Dual Boot Feature
After you have installed the OS/2 operating system, you use the
BOOT command to switch from one operating system to another:
? If you are running the OS/2 operating system and want to
switch to DOS, display an OS/2 command prompt and type:
BOOT /DOS
Then press Enter.
?
If you are running DOS and want to switch to the OS/2
operating system, type:
C:\OS2\BOOT /OS2
Then press Enter.
For additional information about the BOOT command, refer to
the OS/2 Command Reference.
Each time the system is shut down and restarted, it starts in
whichever operating system was last being used. For example, if
you shut down the system while DOS is running, your system will
start in DOS the next time you turn on the system. Remember,
however, that the OS/2 operating system and DOS do not operate
at the same time.
24OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 4. Installing Multiple Operating Systems
This chapter describes how you can install multiple operating
systems on the hard disk of your computer. To install multiple
operating systems, you will set up multiple partitions on the hard
disk during the installation of the OS/2 operating system. You will
also install the Boot Manager feature.
After the Boot Manager is installed and all the operating systems
are installed in their own partitions, you use the Boot Manager
startup menu to select one of the operating systems. Each time
you start your system, then, you decide which operating system
you want to be active.
How This Chapter is Organized
This chapter is separated into three major sections. It is
recommended that you read the entire chapter. In addition,
examples of installing multiple operating systems are provided in
Appendix C, 﨓xamples of Installing OS/2 2.0 and Partitioning Your
Hard Disk?on page 77. For example, if you want to see a brief,
step-by-step example of installing DOS and OS/2 2.0, see Appendix
C.
Section Page Number
An overview of the Boot Manager 26
Hard disk management 27
Instructions for installing OS/2 2.0 and 34
partitioning the hard disk
+ Copyright IBM Corp. 1991 25
An Overview of the Boot Manager
If you are going to install multiple operating systems, you can use
the Boot Manager feature to manage the selective startup of those
systems. From the Boot Manager startup menu, you can select
which operating system you want to use each time you start your
system.
The following is an example of a Boot Manager startup menu that
includes three operating systems. +-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
You use the FDISK utility program during the installation of OS/2
2.0 to install the Boot Manager feature. The following is a brief list
of the steps you follow to set up your hard disk for multiple
operating systems. These steps are described in detail later in
this chapter. Examples are provided in Appendix C, 﨓xamples of
Installing OS/2 2.0 and Partitioning Your Hard Disk?on page 77.
? First, you install the Boot Manager in its own partition (1MB in
size).
? You then create partitions for the other operating systems you
are going to install.
? Next, you install the OS/2 Version 2.0 operating system.
? Finally, you install the other operating systems in the partitions
you created for them.
26OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Important: You should understand how a hard disk is partitioned
before you begin your installation. Make sure you read the
following section on hard disk management.
Hard Disk Management
During installation, you have the option of installing the OS/2
operating system in one partition that takes up the entire hard
disk. If, however, you choose to separate your hard disk into
multiple partitions, you see the FDISK screen.
From the FDISK screen, you specify the number and type of
partitions that you want created. You can create primary
partitions, which are typically used for operating systems. You can
also create logical drives in an area of the hard disk that is outside
the primary partitions. This area is known as the extended
partition. The logical drives within the extended partition are
typically used to hold programs and data.
Your hard disk can be separated into a maximum of four partitions.
You can have four primary partitions or three primary partitions
and the extended partition. If you are going to install multiple
operating systems on your hard disk, you must create one primary
partition to contain the programs that manage the startup of
multiple operating systems. (This partition is referred to as the
Boot Manager partition.)
After the Boot Manager partition is created, you can create up to
three additional primary partitions (to hold three operating
systems), as in the following example:
Chapter 4. Installing Multiple Operating Systems 27
�葺葺葺葺葺葺葺葺葺葺?
� Boot Manager �
谳葺葺葺葺葺葺葺葺葺莼
� DOS 5.0 �
谳葺葺葺葺葺葺葺葺葺莼
� OS/2 1.3 �
� �
谳葺葺葺葺葺葺葺葺葺莼
� OS/2 2.0 �
� �
� �
�葺葺葺葺葺葺葺葺葺葺�
Figure 1. Hard Disk with Four Primary Partitions
Another way of subdividing your hard disk is to create logical
drives within an extended partition. Logical drives are typically
used to hold programs and data. However, you can also install
OS/2 2.0 in a logical drive, as in the following example:
�葺葺葺葺葺葺葺葺葺葺葺葙
� Boot Manager � 葺葺葺?Primary Partition
谳葺葺葺葺葺葺葺葺葺葺葺?
� DOS 5.0 � 葺葺葺?Primary Partition
谳葺葺葺葺葺葺葺葺葺葺葺?
� OS/2 1.3 � 葺葺葺?Primary Partition
� �
谳葺葺葺葺葺葺葺葺葺葺葺?
� OS/2 2.0 � 葺?Logical Drive 葺葙
� � �
谳葺葺葺葺葺葺葺葺葺葺葺? � 葺葸 Extended
� Data � 葺?Logical Drive � Partition
谳葺葺葺葺葺葺葺葺葺葺葺? �
� Data � 葺?Logical Drive �
�葺葺葺葺葺葺葺葺葺葺葺? 葺?
Figure 2. Hard Disk with Primary Partitions and Logical Drives
The extended partition takes the place of one of the primary
partitions on your hard disk. In other words, if you create logical
drives within an extended partition, your hard disk can contain
only three primary partitions. Note that you must have one
primary partition in addition to the Boot Manager partition.
In Figure 2, notice that two logical drives have been set aside for
data. That data can be shared by all the operating systems
(provided the file system formats of the logical drives are
compatible with the operating systems).
28OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
All of the logical drives exist within one partitionhe extended
partition. You don't explicitly create the extended partition. The
extended partition is created the first time you create a logical
(non-primary) drive.
One of the differences between a logical drive and a primary
partition is that each logical drive is assigned a unique drive letter.
However, all primary partitions on a hard disk share the same
drive letter. (On the first hard disk in your system, the primary
partitions share drive C). This means that only one primary
partition on a hard disk can be accessed at one time. (Note that
the Boot Manager partition is different from other primary
partitions because it is never assigned a drive letter.)
�葺葺葺葺葺葺葺葺葺葺葺葙
� Primary (Boot Manager)� 葺葺葺葺葺?No drive letter.
谳葺葺葺葺葺葺葺葺葺葺葺? 葙
� Primary (DOS 5.0) � �葺葺葺葺?These partitions share C:
谳葺葺葺葺葺葺葺葺葺葺葺? � (Only one can be active)
� Primary (OS/2 1.3) � �
� � �
谳葺葺葺葺葺葺葺葺葺葺葺? ?
� Logical Drive � 葺葺葺葺葺? D:
� (OS/2 2.0) �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive (Data) � 葺葺葺葺葺? E:
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive (Data) � 葺葺葺葺葺? F:
�葺葺葺葺葺葺葺葺葺葺葺?
Figure 3. Drive Letter Assignment Example
Notice the drive letter assignments in this illustration. The
operating system that is active when you start the system
performs a process known as drive mapping, in which partitions
and logical drives are assigned drive letters. All the primary
partitions are mapped first and all logical drives within extended
partitions are assigned subsequent drive letters (up through Z).
Only one primary partition per hard disk can be active at a time.
So, only one primary partition is actually assigned the letter C at
any one time. The other primary partitions are not mapped.
An operating system maps only those drives with a format type
that it supports. For example, DOS does not support the
Chapter 4. Installing Multiple Operating Systems 29
installable file system (IFS) format. (The High Performance File
System is an example of an IFS format.) Therefore, any partition
or logical drive that is formatted with IFS is not mapped by DOS
and is not assigned a drive letter.
In the following figure, DOS is active in a primary partition. (The
other primary partitions are not mapped.) Drive D is formatted for
the File Allocation Table (FAT) file system, which DOS recognizes.
However, the next drive is formatted with a file system that DOS
does not recognize. Therefore, DOS ignores this drive. Some
versions of DOS (such as DOS Version 5.0) will recognize the last
partition on the hard disk and assign it the letter E. In other
versions of DOS, no drives beyond the HPFS drive are recognized.
Therefore, no data in those partitions can be used by DOS.
�葺葺葺葺葺葺葺葺葺葺葺葙
� Primary (Boot Manager)� 葺葺葺葺葺?No drive letter.
谳葺葺葺葺葺葺葺葺葺葺葺?
� Primary (DOS) � 葺葺葺葺葺? C:
谳葺葺葺葺葺葺葺葺葺葺葺?
� Primary (OS/2 2.0) �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical (Data) � 葺葺葺葺葺? D:
� FAT format �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical (Data) � 葺葺葺葺葺? DOS does not recognize this
� HPFS format �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical (Data) � 葺葺葺葺葺? E:
� FAT format �
�葺葺葺葺葺葺葺葺葺葺葺?
Figure 4. Example of Drive Mapping. This example illustrates the
problem that can result when the operating system does not recognize a
file format. You can avoid such a problem by placing the logical drive
formatted for the High Performance File System at the end of the hard
disk.
Because of the problems that can result when drives are
remapped, you should avoid deleting logical drives that exist in the
middle of your hard disk. For example, if you were to delete a
logical drive from the middle of your disk, the subsequent drives
would be remapped. (Drive F would become drive E, and so on.)
Problems would result if any programs refer to the former drive
letter.
30OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
The following figure is an example of how drives are mapped in a
system that has two hard disks.
Hard Disk #1 Hard Disk #2
�葺葺葺葺葺葺葺葺葺葺葺葙 �? �葺葺葺葺葺葺葺葺葺葺葺葙
� Boot Manager � 葺葺?No drive � � Primary �
谳葺葺葺葺葺葺葺葺葺葺葺? 葙 letter � 谳葺葺葺葺葺葺葺葺葺葺葺?
� Primary � � � � Primary �
� � �葺葺 C: D: 葺葺� 谳葺葺葺葺葺葺葺葺葺葺葺?
谳葺葺葺葺葺葺葺葺葺葺葺? � � � �
� Primary � � � � Primary �
谳葺葺葺葺葺葺葺葺葺葺葺? ? �? 谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive � 葺葺葸 E: H:
葺葺? � Logical Drive �
� � � �
谳葺葺葺葺葺葺葺葺葺葺葺? 谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive � 葺葺葸 F: I:
葺葺? � Logical Drive �
谳葺葺葺葺葺葺葺葺葺葺葺? 谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive � 葺葺葸 G: J:
葺葺? � Logical Drive �
�葺葺葺葺葺葺葺葺葺葺葺? �葺葺葺葺葺葺葺葺葺葺葺?
Figure 5. Example of Drive Mapping in a System with Two Hard Disks
The important thing to remember when you are setting up your
system is that only one primary partition can be accessible (active)
on each hard disk at any system startup. On the other hand, all
the logical drives within the extended partition are accessible
(provided their file system formats are compatible with the starting
operating system).
Planning for a Boot Manager Setup
When you are planning your Boot Manager setup, be aware of the
following:
?
If you want to preserve existing partitions on your hard disk,
you can install the Boot Manager partition at the end of the
hard disk. Otherwise, create the Boot Manager partition at the
beginning of the hard disk.
? Use primary partitions for DOS systems or previous releases
of the OS/2 operating system.
? To prevent hard disk fragmentation and loss of usable disk
space, create all primary partitions contiguously, at the
beginning or end of the disk free space area.
Chapter 4. Installing Multiple Operating Systems 31
? Put all installable file systems (such as the High Performance
File System) at the end of the disk configuration. As
mentioned earlier, some operating systems do not recognize
installable file systems. By placing all installable file systems
at the end of the disk, you can prevent the problem that results
when drives are remapped.
?
Be aware of specific operating-system restrictions on the hard
disk. For example, to run properly, DOS 3.3 must be installed
in a primary partition that is within the first 32MB of the hard
disk.
? If you are installing a primary partition for DOS and you intend
to load that version of DOS into a DOS session of OS/2 2.0, you
will need to change the DOS CONFIG.SYS and AUTOEXEC.BAT
files. (You do this after you finish installing the operating
systems.) Refer to the online information, which is displayed
on your screen after the OS/2 operating system is installed.
? You can install both DOS and a version of the OS/2 operating
system in the same primary partition if you want to use the
Dual Boot feature within your Boot Manager setup.
? If you are using the IBM DOS 5.00 Upgrade to update your DOS
3.3 or DOS 4.0 system, you should be aware that some
versions of the upgrade will not recognize the DOS partition
unless it is the only partition on the hard disk. You might have
to do the following:
1. Make sure that the DOS partition is the only primary
partition on your hard disk.
2. Install the DOS 5.00 Upgrade.
3. Add the Boot Manager partition and install OS/2 2.0.
Note that an example of adding the Boot Manager to an
existing system (without repartitioning the entire hard disk) is
outlined in Appendix C, 﨓xamples of Installing OS/2 2.0 and
Partitioning Your Hard Disk?on page 77.
32OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Sample FDISK Screen
The following FDISK screen represents a typical hard disk layout of
a 120MB hard disk with three operating systems installed. +--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
In the previous screen, note the following:
? The Boot Manager partition is marked Startable. When you
start your system, the Boot Manager will be in control. You
can then choose which operating system you want to run.
? DOS 3.3 and DOS 5.0 are set up in primary partitions.
However, only DOS Version 3.3 is accessible. Notice that the
drive letter (C) is displayed on the line that contains
information about the DOS 3.3 partition. The placement of the
drive letter indicates which of the primary partitions is active.
DOS and previous versions of the OS/2 operating system can
reside only in a primary partition. They cannot reside in a
logical drive within the extended partition.
? OS/2 2.0 resides in a logical drive in the extended partition
(drive D in this example). Remember that OS/2 2.0 can reside
in either a primary partition or in a logical drive within the
extended partition.
? The logical drive labeled E is set aside for common tools or
programs that can be shared by the operating systems.
Chapter 4. Installing Multiple Operating Systems 33
? 55MB of free space is available. This area can be set aside for
future use. For example, you could later add logical drives at
the end of the free space without disturbing any currently
installed partitions.
34OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Getting Ready for Installation
To partition your hard disk and install multiple operating systems,
you will follow the steps that are described in detail in the next
section. An overview of the steps is provided in the following list.
Examples of setting up your hard disk for multiple operating
systems are provided in Appendix C, 﨓xamples of Installing OS/2
2.0 and Partitioning Your Hard Disk?on page 77.
1. Begin the installation of OS/2 2.0.
2. Set up a partition for the Boot Manager.
3. Set up any primary partitions on the first hard disk that you
want to use to install other operating systems.
Note: At this point, you can also set up logical drives within
the extended partition for data or programs.
4. Set up the primary partition or logical drive for the OS/2
Version 2.0 operating system.
5. Install the OS/2 Version 2.0 operating system in that primary
partition or logical drive.
After you have installed OS/2 2.0, you can install the other
operating systems in the primary partitions that you set up in step
3.
Note that OS/2 installation does not control the installation of the
other operating systems. Each operating system must be installed
with its own installation package.
Back up your files!
If you are going to change an existing partition on your hard
disk, you must back up the data or programs in that partition
before you begin installation.
Chapter 4. Installing Multiple Operating Systems 35
Starting the OS/2 2.0 Installation
1. Insert the OS/2 Installation Diskette into drive A.
2. Turn on the computer. If the computer is already on, press
and hold Ctrl+Alt, and press Del to restart the system.
3. When prompted to do so, remove the Installation Diskette,
insert Diskette 1, and press Enter.
4. If you are installing OS/2 2.0 on a new system (on a hard disk
that does not currently contain an operating system), follow the
instructions listed below under 蘒nstalling OS/2 2.0 on a New
System.?Otherwise, go to 蘒nstalling OS/2 2.0 on an Existing
System?on page 37.
Installing OS/2 2.0 on a New System
If you are installing OS/2 2.0 on a new system (on a hard disk that
does not currently contain an operating system), you see several
introductory screens, followed by this screen:
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
To install the Boot Manager, do the following:
1. Select option 2 to display the FDISK screen.
2. Go to 﨏reating the Boot Manager Partition?on page 41.
36OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Installing OS/2 2.0 on an Existing System
If you are installing OS/2 2.0 on an existing system (on a hard disk
that currently contains an operating system), you see several
introductory screens, followed by this screen:
+--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
1. Select option 2.
You see the following screen:
+--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
2. If you want to save the programs or data in the partition, press
F3 and then use the BACKUP command (or its equivalent) from
your existing operating system. Note that if you do leave the
installation at this point, you will have to restart the entire
installation process.
Chapter 4. Installing Multiple Operating Systems 37
3. If you have already backed up the data, or if you do not need
to keep the data, press Enter to start the FDISK utility program.
Note: If your hard disk has previously defined partitions, and none
of the partitions is large enough to install OS/2 2.0, the
following screen is displayed:
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
To start the FDISK utility program and modify the partition sizes,
press Enter.
Warning: If you are increasing the size of an existing partition,
you must back up any information you want to save in that
partition.
To continue with installation, you must modify your hard disk
configuration. This is done with the FDISK utility program. Press
Enter. You will see the Modifying Partitions Warning screen again.
Press Enter, and the FDISK utility program will start.
38OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Setting Up Your Hard Disk
The FDISK screen shows all partitions that are currently set up on
your system. +--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
If you are installing the OS/2 operating system on a new system,
go to 﨏reating the Boot Manager Partition?on page 41. If
partitions exist on your system, they are listed on the FDISK
screen. Follow the procedures listed below under 﨑eleting
Existing Partitions.?
Deleting Existing Partitions
To set up your system, you must make sure there is enough room
on your hard disk to accommodate the desired setup. It might be
necessary for you to delete some or all of the existing partitions on
your hard disk.
For example, if your hard disk currently has only one partition that
takes up the entire hard disk, you must delete that partition.
However, if your hard disk has ample free space, you can keep
one or more existing partitions and add to them. (An example of
installing the Boot Manager and OS/2 2.0 while preserving an
Chapter 4. Installing Multiple Operating Systems 39
existing partition is shown in Appendix C, 﨓xamples of Installing
OS/2 2.0 and Partitioning Your Hard Disk?on page 77.)
Note that any changes you specify on the FDISK screen do not
actually go into effect until you press F3 to exit FDISK. You will
then be asked to confirm that you want to save your changes.
Warning: All information you want to save must be backed up.
Changing the size of a partition deletes all information about that
partition, and the entire operating system must be reinstalled
when the new partition is created.
1. Use the Up Arrow ( ) or Down Arrow () key to ? the ? highlight
partition you want to delete.
2. Press Enter to display the Options menu.
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
3. Select Delete Partition and press Enter.
Notice that the information about the partition is deleted. The
words Free Space are displayed in the space formerly occupied
by the partition information.
4. Repeat steps 1 through 3 for any other partitions that you need
to delete.
40OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
5. When you are finished deleting partitions, continue to
﨏reating the Boot Manager Partition?on page 41.
Creating the Boot Manager Partition
The first partition you create is the Boot Manager partition. To
create this partition:
1. Make sure that the line is highlighted. IfFree Space it is not,
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is
highlighted.
2. Press Enter to display the Options menu.
3. Select Install Boot Manager and press Enter.
4. Specify whether the partition should be at the beginning or the
end of the available space on the hard disk.
Note: It is recommended that you install the Boot Manager
partition at the beginning of the hard disk. However,
the only restriction on the placement of the Boot
Manager partition is that it be within the first 1GB
(gigabyte) of the disk space. (A gigabyte is equal to 1
073 741 824 bytes.)
Chapter 4. Installing Multiple Operating Systems 41
Creating Partitions for Operating Systems Other than
OS/2 2.0 and for Logical Drives
After you create the partition for the Boot Manager, create primary
partitions for any DOS or previous versions of the OS/2 operating
system you might want to install. Also create any logical drives to
use for data or programs. (Some operating systems, such as AIX,
require that their own disk utility program create the installation
partition. The OS/2 Version 2.0 FDISK utility program cannot
create the partition for these operating systems.)
If you are creating only one partition (for OS/2 Version 2.0), go to
﨏reating the Partition or Logical Drive for OS/2 2.0?on page 47.
Otherwise, follow these steps to create partitions and logical
drives:
1. Make sure that the line is highlighted. Free Space If it is not,
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is
highlighted.
2. Press Enter to display the Options menu.
3. Select Create Partition and press Enter.
42OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
4. Type the size (in MB) of the partition you are creating. Use the
following chart to help you determine how large the partition
should be. For more specific information about partition sizes,
see the documentation that came with the product you are
installing. For example, if you are installing OS/2 Version 1.3
Extended Edition, you should refer to the IBM OS/2 Version 1.3
Information and Planning Guide for more specific guidance.
Table 1. Planning Table for Partition Sizes
Contents Size Hard Disk Considerations
DOS 3.3 2MBMust be in a primary partition within the
first 32MB on the first hard disk.
DOS 4.0 3MBMust be in a primary partition on the first
hard disk.
DOS 5.0 4MBMust be in a primary partition on the first
hard disk.
OS/2 1.x 20MB Must be in a primary partition on the first
SE hard disk. Installs in less than 20MB, but
segment swapping is inhibited.
OS/2 1.x 30MB Must be in a primary partition on the first
EE hard disk. Installs in less than 30MB with
reduced function.
OS/2 2.0 15-30MB Can be in a primary partition or logical
(See drive. Installs in less than 20MB with
Note b.) reduced function.
AIX Partition size determined and built by AIX
Disk utility program. Partition is created
at the end of the hard disk.
Notes:
a. Place system tools or common applications in a logical
drive within the extended partition so that the data can be
shared among the operating systems.
b. If you will be installing LAN Requester or one of the
Extended Services programs, you need to increase the size
of the OS/2 2.0 partition. These programs require a certain
amount of space in the OS/2 partition, even if you are
Chapter 4. Installing Multiple Operating Systems 43
installing them in separate partitions. If you are going to
add these programs, create an OS/2 partition of 32MB.
5. Specify whether this is a primary partition or a logical drive
within the extended partition. Consider the following:
? All versions of DOS must reside in primary partitions.
Versions of OS/2 before 2.0 must also reside in primary
partitions.
?Your hard disk can be separated into a maximum of
three primary partitions (in addition to the Boot
Manager partition.) If you are going to create logical
drives within an extended partition, you can set up two
primary partitions (in addition to the Boot Manager
partition).
?Remember that primary partitions cannot share data.
? Logical drives within an extended partition are shareable.
This means that any data installed in the logical drive can
be used by an operating system running from any other
active logical drive on the system, if the file system formats
are compatible.
6. Specify the location of the partition or logical drive you want to
create. Select either Create at Start of Free Space or Create
at End of Free Space. Note that all logical drives must be in
contiguous space on the hard disk. Therefore, when you
create more than one logical drive, make sure that you specify
Create at Start of Free Space for the subsequent drive.
Note: This option is not available when the amount of free
space equals the size of the request.
Once you have set up the partition, you use the Options menu
choices to specify information about the partition.
Options Menu Choices
The following list describes each of the choices on the Options
menu. Note that some of the options are available under certain
conditions only. When an option is not available, it cannot be
selected. (In other words, you cannot move the cursor to the
option to select it.)
44OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Install Boot Manager
This choice is used only oncehen you create the
partition for the Boot Manager. It is unavailable
thereafter.
Create Partitions
This choice is used to create primary partitions and
logical drives within the extended partition. You can
use this choice whenever there is free space available
on the hard disk.
Add to Boot Manager Menu
This choice is used to add the name of a partition or
logical drive to the Boot Manager startup menu. You
should use this choice for any operating system that
you want to be able to select when you start the
system. When you select this choice, the New Name
window is displayed. You use the New Name window
to assign a meaningful name to the partition or logical
drive.
Change Partition Name
This choice is used to change the name that you have
previously assigned to a partition or logical drive.
Assign C: Partition
This choice is used to specify which primary partition
you want to be active (when more than one primary
partition is installed on your system). The placement of
the drive letter (C) tells you which primary partition will
be visible (or accessible) after you restart the system.
Set Startup Values
This choice is used to specify the actions of the Boot
Manager startup menu. For example, with Set Startup
Values, you can specify how long you want the Boot
Manager menu to be displayed before the default
operating system is started. You can also specify which
operating system you want as the default.
Remove from Boot Manager Menu
This choice is used to delete a name from the Boot
Manager startup menu. When you delete the name,
you can no longer select the operating system
Chapter 4. Installing Multiple Operating Systems 45
associated with that name from the Boot Manager
startup menu.
Delete Partition
This choice is used to delete information about a
primary partition or logical drive. After you exit from
FDISK, all the data in the partition or logical drive is
deleted.
Set Installable
This choice is used to mark a partition or logical drive
as the target for installation. For example, before you
install the OS/2 Version 2.0 operating system, you set
one primary partition (or logical drive) as installable.
Later, when you install other operating systems, you
mark their partitions as installable before you actually
install the operating systems.
After you install OS/2 2.0, the status of this partition is
changed from Installable to Bootable.
Make Startable
This choice is used to determine which partition or
logical drive is activated when you start your system.
When you install the Boot Manager, it is automatically
marked as startable. This means that the Boot
Manager is in control when you start your system. Only
one partition on the first hard disk can be made
startable. If you set any other partition startable, the
Boot Manager startup menu will not appear when you
start the system.
Specifying Options
To specify options for the partition you just created:
1. Press Enter to display the Options menu.
2. Select Add to Boot Manager Menu if you want this partition
displayed on the Boot Manager startup menu. If you do not
select this choice for the partition, you cannot select the
operating system that exists in this partition from the menu at
startup time.
46OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
a. If you select Add to Boot Manager Menu, you see the
window in which you are asked to type a name for the
partition. Type the name.
b. Press the Enter key.
If you have additional partitions to set up, follow the instructions
outlined in 﨏reating Partitions for Operating Systems Other than
OS/2 2.0 and for Logical Drives?on page 42. Otherwise, continue
to 﨏reating the Partition or Logical Drive for OS/2 2.0.?
Creating the Partition or Logical Drive for OS/2 2.0
After you have created the partitions for the Boot Manager and for
each of the other operating systems you plan to install, create the
partition or logical drive in which you will install OS/2 2.0. OS/2
2.0 can be installed in either a primary partition or a logical drive
within the extended partition.
Important: Some operating systems, such as AIX, use their own
disk utility program to set up partitions. The partitions for such
operating systems are created when you actually install the
operating systems. You must leave sufficient space on the hard
disk to accommodate these operating systems.
To create the partition or logical drive for OS/2 2.0:
1. Make sure that the line is highlighted. IfFree Space it is not,
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is
highlighted.
2. Press Enter to display the Options menu.
3. Select Create Partition and press Enter.
4. Type the size (in MB) of the partition or logical drive you are
creating.
5. Specify whether this partition is a primary partition or a logical
drive within the extended partition.
If you have already marked three partitions as primary
partitions, you might want to select Extended Logical Drive for
OS/2 2.0. Your hard disk can be made up of a maximum of
four primary partitions or three primary partitions and multiple
Chapter 4. Installing Multiple Operating Systems 47
logical drives within one extended partition. So, if you create a
primary partition for OS/2 2.0 when three primary partitions
already exist, you cannot create any logical drives.
6. Specify the location of the partition or logical drive you want to
create.
Note: This option is not available when the amount of free
space equals the size of the request.
Specifying Options for the OS/2 2.0 Partition or Logical
Drive
Once you have set up the partition or logical drive, you use the
Options menu choices to specify certain information. For example,
you use the Options menu to give the partition or logical drive a
name.
To specify options:
1. Press Enter to display the Options menu.
2. Highlight Add to Boot Manager Menu and press Enter.
3. Type the name you want to assign to this partition or logical
drive, and press Enter.
4. Press Enter to display the Options menu.
5. Highlight Set Installable and press Enter.
You must select Set Installable for this partition or logical drive.
By selecting Set Installable, you indicate which partition or
logical drive should be used for OS/2 2.0.
6. Use the Set startup values choice if you are going to have
multiple operating systems installed. (You use Set startup
values to configure the Boot Manager environment. In this
window, you indicate how you want the Boot Manager startup
menu displayed.)
Note: You can indicate how you want your Boot Manager
environment configured during this part of installation,
or you can choose to configure the environment after
installation. To configure the Boot Manager
environment after installation, use the FDISKPM utility
48OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
program. (FDISKPM includes most of the features of
FDISK, but it is displayed in a Presentation Manager
window.) To start FDISKPM after installation, type
FDISKPM at an OS/2 command prompt.
Chapter 4. Installing Multiple Operating Systems 49
When you select Set startup values from the Options menu of
FDISK, the following screen is displayed:
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
a. Specify the default drive:
1) Highlight the line that contains the information for the
operating system you want preselected at startup time.
For example, if you want OS/2 2.0 to be the preselected
choice on the Boot Manager startup menu, highlight
the line. OS/2 2.0
2) Press Enter to display the Options menu.
3) Select Set startup values.
4) With Default highlighted, press Enter. Notice that the
name of the partition you chose is listed next to
Default.
b. Set the menu display time:
1) Indicate how long you want the Boot Manager startup
menu displayed when you start your system. If you
want the menu displayed for a certain period of time
before the default operating system starts, accept the
value of Yes. If you want the menu to be displayed
indefinitely (until you explicitly select a choice from the
50OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
menu), highlight Timer and press Enter to change the
value to No.
2) If you selected Yes for Timer, indicate how long you
want the menu displayed before the default operating
system is started. You can either accept the value
listed next to Timeout or you can change the value. To
change the value:
a) Select Timeout.
b) Type the amount of time (in seconds) that you want
the menu displayed before the preselected
operating system is automatically started.
c) Press Enter.
c. Set the menu mode to indicate how you want the Boot
Manager startup menu to be displayed.
You can select Normal or Advanced. The normal mode
menu looks like this:
+--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
The following screen shows the same menu in the
advanced mode format.
Chapter 4. Installing Multiple Operating Systems 51
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
To change the mode that is currently displayed:
1) Highlight Mode.
2) Press Enter.
d. Press F3 to update your FDISK screen.
Saving Your Changes
Once you have set up your hard disk, you must save your
changes.
1. Press F3.
2. Select Save and Exit and press Enter.
The options you select during your FDISK session will not be
active until you select Save and Exit and press Enter.
Note that you will be asked to reinsert the Installation Diskette and
the numbered diskettes.
52OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Continuing with OS/2 2.0 Installation
Once all your partitions are set up, continue installing the OS/2
Version 2.0 operating system. Follow the instructions on the
screen.
When the Installation Drive Selection screen is displayed, select
option 1, Accept the drive.
Selecting the Operating System Features
Once the hard disk of your computer is set up, you see the OS/2
Setup and Installation screen. In this part of installation, you make
choices about which features of the operating system you want to
install.
If you need assistance in completing the screen, press the F1 key
to see more information about your choices. (Or, you can refer to
Chapter 2, 蘒nstalling OS/2 2.0 as the Only Operating System?on
page 9, which provides additional information about making
selections on the screen.)
Formatting Logical Drives
If you have any logical drives that you want to format, you can do
so by selecting Format from the Options menu of the OS/2 Setup
and Installation screen. For example, if you want to format one of
your logical drives for the High Performance File System, you
would do the following:
1. Select Options from the menu bar of the OS/2 Setup and
Installation screen.
2. Select Format.
3. Specify the High Performance File System.
Viewing the Tutorial
After OS/2 installation is completed, you will see the OS/2 Tutorial.
After you complete the tutorial, install any other operating systems
for which you have created partitions.
Chapter 4. Installing Multiple Operating Systems 53
Installing Other Operating Systems
When the Boot Manager and OS/2 2.0 are installed, you can install
the other operating systems.
54OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Do you have more than one primary partition?
If you set up more than one primary partition (other than the
Boot Manager partition) when you set up your hard disk, follow
this procedure before you begin the installation of the operating
systems.
You need to indicate which primary partition should be used for
the operating system you are installing. For example, suppose
three partitions (in addition to the Boot Manager partition) are
set up on your hard disk: two primary partitions and one
extended partition containing logical drives. If you want to
install OS/2 Version 1.3 in the first primary partition, you have
to make sure that the first primary partition is marked as
installable.
To set the partition to installable, use FDISKPM. (FDISKPM
includes most of the features of FDISK, but it is displayed in a
Presentation Manager window.)
1. Select OS/2 System.
2. Select Command Prompts.
3. Select OS/2 Window.
4. Type fdiskpm and press Enter.
The drive letter (for example, C:) is shown next to the primary
partition that is active. (Remember that only one primary
partition can be active, or accessible, at a time.) If the partition
in which you want to install the operating system is not the
active primary partition, do the following:
1. Highlight the partition in which you want to install the
operating system.
2. Select Options from the menu bar.
3. Select Set Installable.
4. Select Options from the menu bar.
5. Select Exit.
6. Select the Save pushbutton from the window that is
displayed.
Chapter 4. Installing Multiple Operating Systems 55
Once you set the correct primary partition as installable (if you
have more than one primary partition), you can begin the
installation of the other operating systems.
Note: If you going to install DOS and a version of the OS/2
operating system in the same primary partition, refer to
Chapter 3, 嗀dding OS/2 2.0 to a DOS System?on page 17
for instructions. Remember that, to use the Dual Boot
feature, you must install DOS in the partition before you
install the OS/2 operating system.
1. Insert the installation diskette from the operating system you
are installing. Then, press and hold Ctrl+Alt, and press Del to
restart the system.
2. During installation, make sure that you install the operating
system in the desired partition. If you are asked whether you
want to format the partition, indicate that you do. FDISK sets
up partitions but does not format them.
3. Press and hold Ctrl+Alt, and press Del to restart the system.
4. If you installed OS/2 Version 1.3 or DOS Version 5.0, you will
need to make the Boot Manager partition startable. You
should also follow the steps outlined below if, for any reason,
the Boot Manager startup menu does not appear as you
specified it during installation of the OS/2 Version 2.0 operating
system. (For example, if you installed multiple operating
systems and wanted the Boot Manager startup menu to appear
but, instead, one of the other operating systems starts, you
would need to make the Boot Manager partition startable. In
DOS terminology, this is the same as making the partition
active.) You can use the version of FDISK (or its equivalent)
from the operating system that is active to make the Boot
Manager partition startable. Or, you can do the following:
a. Insert the OS/2 Installation Diskette into drive A.
b. Press and hold Ctrl+Alt, and press Del to restart the
system.
c. When prompted to do so, remove the Installation Diskette,
insert Diskette 1, and press Enter.
d. When the Welcome screen is displayed, press Esc to
display an OS/2 command prompt.
56OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
e. Type fdisk and press Enter.
f. Make sure that the Boot Manager partition is highlighted.
If it is not, press the Up Arrow ( ) or Down Arrow () key ? ?
until it is highlighted.
g. Press Enter to display the Options menu.
h. Select Make Startable and press Enter.
i. Press F3 to save your changes.
j. Select Save and Exit and press Enter.
k. Remove the diskette from drive A.
l. Press and hold Ctrl+Alt, and press Del to restart the
system.
5. If one of your primary partitions is set up for Dual Boot, copy
the BOOT.COM file from OS/2 2.0 to the Dual Boot partition.
(Copying the BOOT.COM file will replace the versions supplied
by the other operating systems.)
6. If you have installed AIX, you should add it to the Boot
Manager startup menu. With OS/2 running, type FDISKPM at
an OS/2 command prompt. Then do the following:
a. Highlight the line that contains information about AIX.
b. Select Options from the menu bar.
c. Select Add to Boot Manager menu.
d. Type a name for the partition and press Enter.
e. Select Options from the menu bar.
f. Select Exit.
g. Select the Save pushbutton from the window that is
displayed.
You will now be able to select AIX from the Boot Manager
startup menu.
Chapter 4. Installing Multiple Operating Systems 57
58OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 5. Alternative Ways to Install
This chapter describes alternative ways to install the OS/2
operating system. It is intended primarily for the person who will
be setting up workstations for other users.
Included in this chapter is information on installing OS/2 2.0 using
a response file. The chapter also includes a section on modifying
the response file that is shipped with the OS/2 installation
diskettes.
This chapter also explains how to redirect the installation process
so that you can install from a source other than diskette drive A.
Note that a brief overview of redirected installation is provided.
Detailed information about managing remote installations can be
found in OS/2 Version 2.0 Remote Installation and Maintenance
(GG24-3780).
Understanding the Response File Installation
If you have installed a previous version of the OS/2 operating
system or if you have installed other operating systems, you are
probably familiar with the typical installation procedure: you insert
diskettes and answer screen prompts. When you use a response
file, it is not necessary to answer any prompts. All the answers
are in the response file. You can place the response file on
Diskette 1 and begin the installation as usual. Or, you can place
the response file on another source. (See 蘒nstalling OS/2 2.0 from
a Source Other than Drive A?on page 63.) In either case, the
installation program will read the file (instead of prompting the
user) for the installation information.
+ Copyright IBM Corp. 1991 59
Modifying the Response File
A response file is included on the OS/2 installation diskettes.
When you install the operating system, this response file (named
SAMPLE.RSP) is placed in the OS2\INSTALL directory. So, after
you install the operating system on your own system, you can
modify the sample response file and then use it for installation on
another workstation. You use an editor (such as the System
Editor) to modify the response file.
The following is an example of what the response file looks like.
60OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
**************************************************************
*AlternateAdapter *
* *
* Specifies secondary adapter for two display systems. *
* This should be a lower or equal resolution display since *
* the highest resolution display will be primary for PM. *
* *
* Valid Parms: *
* *
* 0=none (DEFAULT) *
* 1=Other than following (DDINSTAL will handle) *
* 2=Monochrome Printer Adapter *
* 3=Color Graphics Adapter *
* 4=Enhanced Graphics Adapter *
* 5=Video Graphics Adapter *
* 6=8514/A Adapter *
* 7=XGA Adapter *
**************************************************************
AlternateAdapter=0
**************************************************************
*BaseFileSystem *
* *
* Specifies which file system should be used to format *
* the install partition *
* *
* Valid Parms: *
* *
* 1=HPFS (DEFAULT) *
* 2=FAT *
**************************************************************
BaseFileSystem=2
**************************************************************
* CDROM *
* *
* Specifies which, if any, CD ROM IFS files should be *
* installed. *
* *
* Valid Parms: *
* *
* 0 = None *
* 1 = All *
* 2 = CD-ROM IFS (DEFAULT) *
* 3 = IBM CD-ROM Device Drivers *
**************************************************************
CDROM=2
As you can see, the file contains comments about the various
options and lists the values you should enter if you want
something other than the default value. If you do not modify a
response, the default value is used.
Chapter 5. Alternative Ways to Install 61
For example, suppose you want to set up a system in which no
CD-ROM support is required. In the response file, you would
indicate that no support be installed by entering:
CDROM=0
The following is a list of the steps you would perform to modify a
response file and then place the response file on Diskette 1.
1. Make a copy of the SAMPLE.RSP file (located in the
OS2\INSTALL directory).
2. Use an editor (such as the System Editor) to modify the file.
The file contains comments that explain each of the installation
options.
3. Once you have modified and saved the response file, copy it to
Diskette 1 with the name OS2SE20.RSP.
Note: You can place the response file in a location other than
Diskette 1. For example, the response file could be
located on the server in a local area network. The next
section describes the process for pointing to a source
other than drive A for installation information.
4. Copy the RSPINST.EXE file (located in the OS2\INSTALL
directory) to Diskette 1.
5. Begin the installation of the workstation by inserting the
Installation Diskette and restarting the system.
6. When prompted, switch diskettes and press Enter.
From this point, the installation program will prompt only for the
insertion of diskettes. No other installation screens will appear.
Note that you can use this procedure to install the same set of
options on multiple workstations. Using a response file, you can
make sure that all workstations in an area are set up with the
same set of options.
62OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Installing OS/2 2.0 from a Source Other than Drive A
The operating system typically is installed from a diskette inserted
into drive A. However, with OS/2 2.0, you can redirect the
installation by specifying a source other than the diskettes in drive
A. For example, you can direct the installation to a CD-ROM. In a
local area network environment, for example, any or all of the
workstations connected to a server could request that the
installation source be a drive on the server. This type of
installation requires additional software (such as a LAN support
product).
Redirecting the Installation
There are several ways to redirect the installation of OS/2 2.0.
You can modify information on Diskette 1 to point to another
source. If that source contains a copy of the installation diskettes,
the user is prompted for choices but is not asked to swap
diskettes. The source can also be specified in a response file. If a
response file exists on the redirected source, the user is not
prompted for any choices.
You can modify the CONFIG.SYS file that is found on Diskette 1 to
indicate that installation should proceed from a source other than
drive A.
? One of the ways to indicate redirection is to modify the
PROTSHELL statement of the CONFIG.SYS file. For example,
to point to an alternative source for installation information,
you would add a drive letter and file name to the
PROTSHELL= statement:
PROTSHELL=SYSINST1.EXE SYSINST2.EXE Z:\OS2SE20
When the system reads Diskette 1, it finds this statement and
looks for the SYSINST1.EXE and SYSINST2.EXE installation
programs in the specified directory of drive Z. Installation then
proceeds from that drive, and there is no prompting for
insertion of diskettes.
? Instead of modifying the PROTSHELL statement, you can add
an environment variable to the CONFIG.SYS file. For example,
you could add the following statement to the file:
Chapter 5. Alternative Ways to Install 63
SET SOURCEPATH=Z:\OS2SE20
You would then add the same drive and file name to the PATH
and DPATH statements of the CONFIG.SYS file.
Another way to specify redirection of installation is to use the
response file on Diskette 1 to point to another source. For
example, you can modify the sample response file by adding the
following statement to the response file:
SourcePath=Z:\OS2SE20
Then, when this response file is placed on Diskette 1, the
installation program looks to the drive specified for its installation
information.
A response file can be copied to the directory specified above
rather than to Diskette 1. If a response file (with the correct name
OS2SE20.RSP) exists in both places, the file on the diskette is
checked first.
Setting Up an Alternative Installation Source
The OS/2 installation program can use a drive other than A as its
installation source. This redirected drive can be a CD-ROM, a
drive on the hard disk, or a remote drive that is connected to a
LAN. If the redirected drive requires special software, you will
have to copy those files to Diskette 1 and modify the CONFIG.SYS
file on Diskette 1. The following section describes the steps
needed to install from a CD-ROM. For information on installing
from other drives, refer to OS/2 Version 2.0 Remote Installation and
Maintenance (GG24-3780).
Installing from a CD-ROM Device
When the installation program begins, it searches all the drives on
a system for a file named OS2SE20.SRC. If that file is found by the
installation program, it reads the first line of the file to find the
installation source information.
When OS/2 is delivered on a CD-ROM, it already contains the
OS2SE20.SRC file. You begin the installation from diskette, as
64OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
usual, but after a certain point, the installation is redirected to the
CD-ROM.
If the OS/2 Version 2.0 operating system was delivered on a
CD-ROM, do the following:
1. Insert the CD-ROM into its drive.
2. Insert the Installation Diskette into drive A.
3. Turn on the computer. If the computer is already on, press
and hold the Ctrl and Alt keys, and press Del to restart the
system.
4. Follow the prompts that are displayed on the screen. You will
be asked to switch diskettes before the installation program
begins to read the OS2SE20.SRC file on the CD-ROM drive.
Chapter 5. Alternative Ways to Install 65
66OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Appendix A. Customizing the Operating System
This appendix describes how you can customize your operating
system without completely reinstalling it.
You can use the System Configuration folder to change choices
such as the time and date, your screen colors and window
borders, and to change your mouse for right- or left-hand use.
Select the System Configuration folder from the OS/2 System
folder to see the objects (for example, the mouse) that you can
customize.
You can also replace the user interface (sometimes called a shell)
that comes with the OS/2 Version 2.0 operating system. You
replace the user interface by modifying a statement in the
CONFIG.SYS file. See the online Master Index for details on
replacing the user interface.
Features that You Can Change or Add
After you install the operating system, you might decide to change
your mouse or display. Or, you might decide that you want to add
some features that you chose not to add during the initial
installation. You can make the change or add the features without
completely reinstalling the operating system.
The following are the features you can add to your system:
?
CD-ROM Device Support
Provides system support for CD-ROM devices.
?
Documentation
Adds the OS/2 Tutorial, the OS/2 Command Reference, or the
REXX Information.
? Fonts
+ Copyright IBM Corp. 1991 67
Determines the print style for your system. The OS/2
operating system offers bit-map fonts and fonts in Adobe ** Type
1 format for displaying and printing data on many output
devices; however, the bit-map fonts are not supported for
printing on vector devices, such as plotters. For compatibility,
the operating system also supports the Presentation Manager
outline fonts.
When no fonts are selected, the system default font and the
Helvetica ** fonts are installed.
? Optional System Utilities
Provide a full set of system utility programs to:
?Back up the hard disk
?Change file attributes
?Display the directory tree
?Manage partitions
?Label diskettes
?Link object modules
?Convert, display, and print pictures
?Use PMREXX
?Recover files
?Restore backed-up files
?Sort files
?Install OS/2 compilers.
? Tools and Games
Provide productivity aids (such as an enhanced editor and a
calculator) as well as games.
?
OS/2 DOS and Windows Support
Enables DOS and Microsoft Windows programs to run on the
OS/2 operating system. If you select this feature, you will be
prompted to indicate which of your existing DOS and Windows
applications you want to migrate to OS/2 2.0.
?
High Performance File System
** Trademark of Adobe Systems Incorporated.
** Trademark of the Linotype Company.
68OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Provides fast access to large disk volumes. Features of the
High Performance File System include:
?File names up to 254 characters in length
?Large file support
?Strategic allocation of directory structures
?Processing of metacharacters that are generally used for
displaying and printing graphics.
?
REXX
Installs the REXX Operating System/2 procedures language.
This batch language can be used to develop Systems
Application Architecture * (SAA*) programs.
? Serial Device Support
Provides system support for attached serial devices, such as a
modem, a serial plotter, or a serial printer assigned to a
communication port. This choice is not required for mouse
support.
? Serviceability and Diagnostic Aids
Provide information primarily for a technical coordinator to
isolate and correct system problems.
?
Optional Bitmaps
Provides a set of bitmaps that you can use to change the
background of your system.
Changing Your Setup or Adding Features
To change your setup or add a feature, do the following:
1. Select OS/2 System.
2. Select System Setup.
3. Select Selective Install.
* Trademark of the IBM Corporation.
Appendix A. Customizing the Operating System 69
4. Select the item you want to change (for example, mouse,
keyboard, display, or country). After making any changes,
select the OK pushbutton.
5. On the next screen, select the features that you want to install.
Note: If a More pushbutton accompanies a feature, you must
select the pushbutton to view the features. For
example, if you want to install a document, select
Documentation and then select the More pushbutton to
display a list of documents. Then, select the document
that you want to add.
6. When prompted, insert the numbered installation diskettes to
complete the process.
70OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Appendix B. Diagnosing System Problems
The operating system provides programs that help you gather
information to isolate and correct system problems. You can learn
more about this information by selecting topics under the Problem
determination heading in the Master Index.
If your system has failed, however, it will not be possible to get
online help. This appendix provides information about such
system failures, and about:
? Recovering the CONFIG.SYS file
? Recovering user and system INI files
? Recovering from errors on the hard disk
? Responding to installation errors.
Note: Backing up your system regularly may help you avoid
having to re-create files in the event of a system failure.
Recovering the CONFIG.SYS File
The CONFIG.SYS file contains command statements that set up
your system. If the file is changed incorrectly, you cannot restart
the system or edit the file. To recover the CONFIG.SYS file:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
press Del to restart the system.
3. When the logo screen appears, remove the Installation Diskette
and insert Diskette 1.
4. Press Enter.
5. When the Welcome screen appears, press Esc.
6. Change to the drive where your operating system resides. For
example, if the operating system is in drive C, type:
C:
and press Enter.
+ Copyright IBM Corp. 1991 71
7. Rename the damaged CONFIG.SYS file by typing
REN CONFIG.SYS CONFIG.BAD
and pressing Enter.
8. Copy the CONFIG.SYS backup file to the root directory of the
drive where your operating system resides. (The CONFIG.SYS
backup file was created during installation.) For example, if
the operating system is in drive C, type:
COPY C:\OS2\INSTALL\CONFIG.SYS C:\CONFIG.SYS
and press Enter.
9. Remove Diskette 1 from drive A.
10. Press and hold Ctrl+Alt, and press Del to restart the system.
Note: If you changed the CONFIG.SYS file after installing the
operating system, use an editor to either correct the
damaged file (now named CONFIG.BAD) or update the
current CONFIG.SYS file.
Recovering User and System INI Files
System settings, such as application defaults, display options, and
file options, are defined in the OS2.INI startup file in the OS2
directory of your hard disk. Information about installed fonts and
printer drivers is contained in a system file called OS2SYS.INI. If
you receive a message that the OS2.INI file has been damaged,
replace both of these files as follows:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
press Del to restart the system.
3. After the logo screen appears, remove the Installation Diskette
and insert Diskette 1.
4. Press Enter.
5. When the Welcome screen is displayed, press Esc.
6. Change to the drive where your operating system resides. For
example, if the operating system is in drive C, type:
72OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
C:
and press Enter.
7. Change to the OS2 subdirectory by typing
CD \OS2
and pressing Enter.
8. Erase the current OS2.INI file by typing
ERASE OS2.INI
and pressing Enter.
9. Create a new user INI file by typing
MAKEINI OS2.INI INI.RC
and pressing Enter.
10. Erase the current OS2SYS.INI file by typing
ERASE OS2SYS.INI
and pressing Enter.
11. Create a new system INI file by typing
MAKEINI OS2SYS.INI INISYS.RC
and pressing Enter.
Note: The MAKEINI.EXE file was added to the OS2 directory of
your hard disk during installation of the operating
system.
12. Remove Diskette 1 from drive A.
13. Press and hold Ctrl+Alt, and press Del to restart the system.
You can protect your INI files by copying back levels of the files
each time you start your system. For example, you could include
the following statements in your CONFIG.SYS file:
CALL=C:\OS2\XCOPY.EXE C:\OS2\*.INX c:\OS2\*.INY
CALL=C:\OS2\XCOPY.EXE C:\OS2\OS2*.INI C:\OS2\*.INX
These statements make a copy of your current INI files and also
make a copy of the INI files you previously backed up.
Appendix B. Diagnosing System Problems 73
By copying your files each time you start the system, you will
always be able to recover an earlier verion of the INI files.
Recovering from Errors on the Hard Disk
The CHKDSK command with the parameter /F can be used to
correct disk and directory errors. However, when you use the /F
parameter, no activity can occur on the disk. Therefore, if you
need to correct errors on the drive from which you normally start
the operating system, you must use the version of CHKDSK that is
on the installation diskettes (instead of the version that has been
installed on the hard disk).
To correct errors on the drive from which you normally start the
operating system:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
press Del to restart the system.
3. When the logo screen appears, remove the Installation Diskette
and insert Diskette 1.
4. Press Enter.
5. When the Welcome screen appears, press Esc.
6. When the OS/2 command prompt appears, remove Diskette 1
and insert Diskette 2 (the diskette that contains the CHKDSK
command).
7. To correct the errors on your hard disk, type the following at
the command prompt:
CHKDSK C: /F
and press Enter. (If your operating system resides on a drive
other than C, type the appropriate drive letter after the
CHKDSK command.)
8. Remove the diskette from drive A.
9. Press and hold Ctrl+Alt, and press Del to restart the system.
74OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Responding to Installation Errors
If you receive an error message while installing the operating
system, take the appropriate corrective action.
Only some files were copied. You might be out of disk space.
Explanation: (1) The installation program could not transfer one or
more files, because a version of the files already exists on the hard
disk with the read-only, system, or hidden attributes set.
(2) The installation program stopped transferring files because there
was not enough hard disk space.
Action: (1) Return the attributes of the OS/2 files to their original
setting. Use the ATTRIB command to remove the read-only
attributes.
(2) Move non-OS/2 operating system files out of the installation
partition. You can store these files in the extended partition or on a
diskette. If you intend to format the installation partition, remember
to use the BACKUP command to save any important files.
An error occurred when the installation program tried to copy a file.
Explanation: (1) The installation program could not transfer one or
more files, because a version of the files already exists on the hard
disk with the read-only, system, or hidden attributes set.
(2) The installation program stopped transferring files because there
was not enough hard disk space.
(3) The hard disk might contain errors.
Action: (1) Return the attributes of the OS/2 files to their original
settings. Use the ATTRIB command to remove the read-only
attributes.
(2) Move non-OS/2 operating system files out of the installation
partition. You can store these files in an extended partition or on a
diskette. If you intend to format the installation partition, remember
to use the BACKUP command to save any important files.
(3) Follow the CHKDSK procedure outlined in the section
ecovering from Errors on the Hard Disk?on page 74.
Appendix B. Diagnosing System Problems 75
An error occurred when the installation program tried to transfer
system files to your hard disk. Your hard disk might be unusable.
Explanation: The installation program stopped transferring files
because there was not enough hard disk space. The system files
consist of the OS2LDR and OS2KRNLI files on the Installation
Diskette.
Action: Move non-OS/2 operating system files out of the installation
partition. You can store these files in an extended partition or on a
diskette. If you intend to format the installation partition, remember
to use the BACKUP command to save any important files.
An error occurred while trying to run a program.
Explanation: (1) The installation program could not find one of the
following programs: FDISK, MAKEINI, CHKDSK, FORMAT, or
UNPACK.
(2) The installation program could not run a program, because there
is not enough memory to install it.
Action: (1) Verify that the program exists on the diskette or
installation partition.
(2) Add more system memory.
The installation program was unable to load a module into memory.
Explanation: The installation program could not load a system
module because there is not enough memory.
Action: Add more system memory.
Making the Boot Manager Active
If you set up multiple operating systems but the Boot Manager
startup menu does not appear as you specified it during
installation, you will need to make the Boot Manager partition
startable. See page 56 for instructions on making the Boot
Manager partition startable.
76OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Appendix C. Examples of Installing OS/2 2.0 and
Partitioning Your Hard Disk
This appendix shows four examples of partitioning the hard disk of
your system during the installation of the OS/2 Version 2.0
operating system.
Example 1 shows you how to delete an existing partition and set
up two areas on the hard disk: a primary partition for OS/2 2.0
and a logical drive within the extended partition for data. The
remaining examples show you how to set up your system so that
you can install multiple operating systems in their own partitions.
Example 1: Creating a Primary Partition and a Logical
Drive for Data
This example shows you how to set up a primary partition for OS/2
2.0 and a logical drive in the extended partition. The logical drive
will be used to hold data.
This example assumes that you are installing on a hard disk that
currently has one partition that takes up the entire disk.
In this example, you will create:
? A 30MB primary partition
? A 12MB logical drive within the extended partition.
This example does not involve the installation of the Boot
Manager.
1. Back up any data you want to save from the existing partition.
(Use the BACKUP command from your existing operating
system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing partition (which you have backed up):
+ Copyright IBM Corp. 1991 77
a. Press Enter to display the Options menu.
b. Select Delete Partition.
5. Create the primary partition:
a. Press Enter to display the Options menu.
b. Select Create Partition.
c. Type the size of the primary partition (in this example, 30)
and press Enter.
d. Select Primary Partition and press Enter.
e. Select Create at Start of Free Space and press Enter.
6. Create the logical drive for data:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 12) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
7. Exit FDISK:
a. Press F3.
b. Select Save and Exit and press Enter.
8. Continue with OS/2 installation until you see the OS/2 Setup
and Installation screen.
9. Format the logical drive:
a. When the OS/2 Setup and Installation screen is displayed,
select Select features and install.
b. Specify any changes to the System Configuration screen.
c. When the next OS/2 Setup and Installation screen is
displayed, select Options from the menu bar.
d. Select Format.
e. Indicate which file system you want to use to format the
logical drive.
Note that you can format the logical drive for a file system
that is different from the one with which you formatted the
primary partition. For example, if the primary partition is
formatted for the High Performance File System, you can
format the logical partition for the File Allocation Table file
78OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
system. This way, you can have both file systems installed
on the hard disk.
10. Finish the installation of the OS/2 Version 2.0 operating
system.
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 79
Example 2: Installing the Boot Manager, OS/2 2.0, and
One Additional Operating System
This example shows you how to set up a partition for the Boot
Manager, a primary partition for DOS, and a logical drive for OS/2
2.0.
This example assumes that you are installing on a hard disk that
currently has one partition that takes up the entire disk.
In this example, you will create:
? A 4MB primary partition for DOS
? A 30MB logical drive for OS/2 2.0.
You will also install the Boot Manager in its own partition.
1. Back up any data you want to save from the existing partition.
(Use the BACKUP command from your existing operating
system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing partition (which you have backed up):
a. Press Enter to display the Options menu.
b. Select Delete Partition.
5. Install the Boot Manager partition:
a. Press Enter to display the Options menu.
b. Select Install Boot Manager.
c. Select Create at Start of Free Space and press Enter.
6. Create the DOS partition:
a. Highlight the line. Free Space
b. Select Create Partition.
c. Type the size of the primary partition (in this example, 4)
and press Enter.
d. Select Primary Partition and press Enter.
e. Select Create at Start of Free Space and press Enter.
80OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
f. Press Enter to display the Options menu.
g. Select Add to Boot Manager Menu.
h. Type DOS and press Enter.
7. Create the OS/2 Version 2.0 logical drive:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 30) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
g. Press Enter to display the Options menu.
h. Select Add to Boot Manager Menu.
i. Type OS/2 2.0 and press Enter.
8. Set up OS/2 Version 2.0 as the default:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set startup values.
d. Select Default.
e. Press F3.
9. Indicate which partition should be used for the OS/2 2.0
installation:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set installable.
10. Exit FDISK:
a. Press F3 to exit FDISK.
b. Select Save and Exit and press Enter.
11. Finish the installation of the OS/2 Version 2.0 operating
system.
12. When OS/2 installation is completed, insert the DOS
installation diskette. Then, press and hold Ctrl+Alt, and press
Del to restart the system.
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 81
Example 3: Installing the Boot Manager, OS/2 2.0, and
Two Additional Operating Systems
This example shows you how to set up a partition for the Boot
Manager, a primary partition for DOS, a primary partition for OS/2
Version 1.3, and a logical drive for OS/2 Version 2.0.
This example assumes that you are installing on a hard disk that
currently has one partition that takes up the entire disk.
In this example, you will create:
? A 4MB primary partition for DOS
? A 20MB primary partition for OS/2 Version 1.3
?
A 30MB logical drive for OS/2 Version 2.0.
You will also install the Boot Manager in its own partition.
1. Back up any data you want to save from the existing partition.
(Use the BACKUP command from your existing operating
system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing partition (which you have backed up):
a. Press Enter to display the Options menu.
b. Select Delete Partition.
5. Install the Boot Manager partition:
a. Press Enter to display the Options menu.
b. Select Install Boot Manager.
c. Select Create at Start of Free Space and press Enter.
6. Create the DOS partition:
a. Highlight the line. Free Space
b. Select Create Partition.
c. Type the size of the primary partition (in this example, 4)
and press Enter.
d. Select Primary Partition and press Enter.
82OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
e. Select Create at Start of Free Space and press Enter.
f. Press Enter to display the Options menu.
g. Select Add to Boot Manager Menu.
h. Type DOS and press Enter.
7. Create the OS/2 Version 1.3 partition:
a. Highlight the line. Free Space
b. Select Create Partition.
c. Type the size of the primary partition (20) and press Enter.
d. Select Primary Partition and press Enter.
e. Select Create at Start of Free Space and press Enter.
f. Press Enter to display the Options menu.
g. Select Add to Boot Manager Menu.
h. Type OS2 1.3 and press Enter.
8. Create the OS/2 2.0 logical drive:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 30) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
g. Press Enter to display the Options menu.
h. Select Add to Boot Manager Menu.
i. Type OS/2 2.0 and press Enter.
9. Set up OS/2 Version 2.0 as the default:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set startup values.
d. Select Default.
e. Press F3.
10. Indicate which partition should be used for the OS/2 2.0
installation:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set installable.
11. Exit FDISK and continue with installation:
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 83
a. Press F3 to exit FDISK.
b. Select Save and Exit and press Enter.
c. Continue with OS/2 installation.
12. Install DOS
a. Insert the DOS installation diskette.
b. Press the Ctrl and Alt keys, and then press Del to restart
the system.
13. Restart the system by pressing the Ctrl and Alt keys and then
pressing the Del key.
14. Select OS/2 2.0 from the Boot Manager startup menu.
15. Make the OS/2 1.3 partition active.
a. Select OS/2 System.
b. Select Command Prompts.
c. Select OS/2 Window.
d. Type:
fdisk
and press Enter.
e. Highlight the line. OS2 1.3
f. Press Enter to display the Options menu.
g. Select Set Installable.
h. Press F3 to exit.
16. Install OS/2 Version 1.3
a. Insert the OS/2 Version 1.3 installation diskette.
b. Press the Ctrl and Alt keys, and then press the Del key to
restart the system.
17. Make the Boot Manager Startable:
a. With OS/2 1.3 running, select Manage Partitions from the
Utilities group.
b. Highlight the Boot Manager line.
c. Select Options.
d. Select Startable.
18. Restart the system to see the Boot Manager startup menu.
84OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Example 4: Installing Boot Manager without
Repartitioning the Entire Hard Disk
This example shows you how to install the Boot Manager and
install OS/2 2.0 without repartitioning the entire hard disk.
This example assumes that your current hard disk setup has a
primary partition (with DOS Version 4.0) and an extended partition.
In this example, you will preserve the primary partition that
contains DOS Version 4.0. You will delete the extended partition to
make room for OS/2 2.0 and the Boot Manager. In this example,
you will put the Boot Manager partition at the end of the hard disk.
In this example, you will create:
? A 30MB logical drive for OS/2 2.0
? A 10MB logical drive for data.
You will also install the Boot Manager in its own partition.
1. Back up any data you want to save from the existing extended
partition. (Use the BACKUP command from your existing
operating system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing extended partition (which you have backed
up):
a. Highlight the line that contains information about the
extended partition.
b. Press Enter to display the Options menu.
c. Select Delete Partition.
5. Install the Boot Manager partition:
a. Press Enter to display the Options menu.
b. Select Install Boot Manager.
c. Select Create at End of Free Space and press Enter.
6. Create the OS/2 2.0 logical drive:
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 85
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 30) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
g. Press Enter to display the Options menu.
h. Select Add to Boot Manager menu.
i. Type OS/2 2.0 and press Enter.
7. Create the logical drive for data:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 10) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
8. Set up OS/2 2.0 as the default:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set startup values.
d. Select Default.
e. Press F3.
9. Indicate which partition should be used for the OS/2 2.0
installation:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set installable.
10. Add a name for the DOS partition to the Boot Manager startup
menu:
a. Highlight the line that contains information about the DOS
partition.
b. Press Enter to display the Options menu.
c. Select Add to Boot Manager menu.
d. Type DOS and press Enter.
11. Exit FDISK:
86OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
a. Press F3 to exit FDISK.
b. Select Save and Exit and press Enter.
12. Continue with OS/2 installation until you see the OS/2 Setup
and Installation screen.
13. Format the logical drive:
a. When the OS/2 Setup and Installation screen is displayed,
select Select features and install.
b. Specify any changes to the System Configuration screen.
c. When the next OS/2 Setup and Installation screen is
displayed, select Options from the menu bar.
d. Select Format.
e. Indicate which file system you want to use to format the
logical drive.
14. Finish the installation of the OS/2 Version 2.0 operating
system.
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 87
88OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Index
Boot Manager partition
A creating 41
Add to Boot Manager Menu placement of 31
choice 45 Boot Manager startup menu
adding OS/2 to a DOS system 17
configuring 48
after installation, adding example of 26
features 67
AIX, adding name to Boot Manager
startup menu 57 C
AIX, note about installing 42 caching 69
Assign C: Partition choice 45 CD-ROM, installing from 65
AUTOEXEC.BAT file Change Partition Name choice 45
creating or modifying for Dual changing partition sizes 38
Boot 21 CHKDSK command, recovering
migrating from a previous from errors on the hard disk 74
version 14 colors, changing screen 67
modifying to load DOS from Command Reference
within OS/2 32 adding after installation 70
choosing to install 14
communication port 69
B
? configuration options 67
basic installation 9 16 CONFIG.SYS file
bit-map fonts 67 creating or modifying for Dual
bitmaps, adding additional 69 Boot 21
BOOT command 24 migrating from a previous
Boot Manager
version 14
example of setting up three modifying to load DOS from
operating systems 82 within OS/2 32
example of setting up two recovering 71
operating systems 80 considerations for installing
FDISK utility 39
multiple operating systems 4
hard disk architecture 30 Create Partitions choice 45
hard disk management 30 creating
installation of 34partitions and logical drives 42
installation on existing the Boot Manager partition 41
system 37
the OS/2 partition 47
installation on new systems 36 creating or modifying
startup menu time, setting 50 AUTOEXEC.BAT and
system setup CONFIG.SYS 21
recommendations 31
+ Copyright IBM Corp. 1991 89
customization information, example of (continued)
migrating 14 formatting a data partition 77
customizing the system 67 installing Boot Manager with
three operating systems 82
installing Boot Manager with two
D
operating systems 80
date, changing 67 installing Boot Manager without
default operating system, setting repartitioning the entire
(for Boot Manager) 50 disk 85
default printer, choosing 15 installing DOS and OS/2 in
Delete Partition choice 46
separate partitions 80
deleting partitions 39 installing multiple partitions 80
diagnostic aids 69 installing three operating
directory structure, for Dual systems 82
Boot 19 setting up two partitions 77
documentation, online
extended partition 27
adding after installation 70
choosing during installation 14
DOS F
Dual Boot restriction 18 failures, system 71
DOS programs FDISK
installing in a Dual Boot examples of using 77
setup 22 screen 39
migrating 14 FDISKPM, description of 49
DOS 5.00 Upgrade, note about file systems, installing both 78
installing 32 fonts, adding after installation 67
DOS 5.0, note about installing 56 formatting a logical drive 14
drive mapping 29
Dual Boot
copying COMMAND.COM in a H
Boot Manager hard disk architecture 30
hard disk management 30
environment 57
Dual Boot feature high performance file system
requirements 19 Dual Boot restriction 18
restrictions 18
starting 24
I
increasing partition size 38
E INI files, recovering 72
error messages, installation 75 Install Boot Manager choice 45
example of installable, marking a partition
adding partitions to an existing as 46
hard disk 85
90OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
installation modem 69
after, adding features 67 more than one operating system,
basic 9?6 installing 25
installation, redirecting 59 mouse
installing customizing use of 67
AIX, note about 42tutorial on using 12
Boot Manager without multiple operating systems
repartitioning the entire considerations for installing 4
disk 85 installing 25
both file systems 78
from a drive other than A 59
more than one operating O
system 4 online documentation
multiple partitions, example adding after installation 70
of 80, 82 choosing during installation 14
online help
OS/2 on a DOS system 17
OS/2 only 9 for loading DOS from
other operating systems 54 diskette 7
with a response file 59 problem determination 71
interface, replacing 67 operating systems
installing additional 54
recommended partition sizes
L for 43
LAN installation 59 optional bitmaps 69
logical drive optional utilities 68
description of 27OS/2 Tutorial
formatting during adding after installation 70
installation 14 choosing to install 14
logo screen 10, 23OS/2 1.3, note about installing 56
outline fonts 67
M
Make Startable choice 46 P
marking a partition as partition
installation 46 accepting the default 10
messages, installation 75 adding a second 11
metacharacters 69 partition size and considerations,
migrating planning table 43
CONFIG.SYS and partitions
AUTOEXEC.BAT files 14 defining 39
customization information 14 restriction on number of 27
DOS programs 14 setting up 39
Windows programs 14
Index 91
Partitions Too Small warning 38 S
planning the Boot Manager
setup 31 screen colors, changing 67
plotter, utilities 69 serial printer or plotter 69
PM fonts 67 Set Installable choice 46
Set Startup Values choice 45
primary drive, changing 7 setting a partition installable 46
primary partitions
restriction on number of 27 setting the Boot Manager default
specifying which should be used operating system 50
for installation 54 setting up
partitions and logical drives 42
printer, choosing the default 15 two partitions, example of 77
problem determination 69, 71
problem information 71 sharing printer resources 69
shell, replacing 67
starting the Dual Boot feature 24
Q System Configuration folder 67
system problems, diagnosing 71
Quick Reference
description of x
installing with 3
T
technical coordinator 69
R timeout values, Boot Manager 50
time, changing 67
recommendations for a Boot
Manager setup 31 trouble shooting 71
recommended partition sizes 43 Tutorial
reconfigurable diskette drives 7 adding after installation 70
recovering choosing to install 14
from errors on the hard disk 74
from system failures 71?4
the CONFIG.SYS file 71 U
user and system INI files 72 Upgrade, DOS 5.00 32
redirecting installation 59 upgrading to DOS 5.00 before
installing Boot Manager 32
Remove from Boot Manager Menu user INI files, recovering 72
choice 45
replacing the user interface 67 user interface, replacing 67
response file installation 59 utilities, system 68
REXX information
adding after installation 70 W
choosing to install 14 window borders, changing 67
REXX program 69
Windows programs
installing in a Dual Boot
setup 22
92OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Windows programs (continued)
migrating 14
Index 93
�
OVER6167.DOC
IBM OS/2 32-bit
Overview
Pre-Release Copy
Document Number 84F8465
October 15, 1991
First Edition October 1991 < *
The following paragraph does not apply to the United Kingdom or any
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION 嗀S IS?WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not apply
to you.
This publication could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services
that are not announced in your country. Such references or information
must not be construed to mean that IBM intends to announce such IBM
products, programming, or services in your country.
Requests for technical information about IBM products should be made to
your IBM Authorized Dealer or your IBM Marketing Representative.
IBM may have patents or pending patent applications covering subject
matter in this document. The furnishing of this document does not give
you any license to these patents. You can send license inquiries, in
writing, to the IBM Director of Commercial Relations, IBM Corporation,
Purchase, NY 10577.
+ Copyright International Business Machines Corporation 1991. All rights
reserved.
Note to U.S. Government Users ?Documentation related to restricted
rights ?Use, duplication or disclosure is subject to restrictions set forth
in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
About This Book ..... . . . . . . . . . . . . . . . . . . . . . . . vii
Using This Book ..... . . . . . . . . . . . . . . . . . . . . . . . vii
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Changes from Previous Versions ......... . . . . . . . . . . x
Chapter 1. Introducing OS/2 2.0 ......... . . . . . . . . . . 1
Introducing Folders and Objects ......... . . . . . . . . . . 2
Managing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .5.
Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . .6.
Using Pop-up Menus. . . ..... . . . . . . . . . . . . . . . . . 7
Working Directly with Objects. . . . ....... . . . . . . . . 8
Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .9.
Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Printing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Arranging Objects . . . . . . . . . . . . . . . . . . . . . . . .13.
Opening Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Selecting Window Parts ....... . . . . . . . . . . . . . . . 15
Using the Window.List . . . ..... . . . . . . . . . . . . . . 16
Sizing a Window ..... . . . . . . . . . . . . . . . . . . . . . 17
Moving a Window . . . ..... . . . . . . . . . . . . . . . . . . 18
Introducing Online Information ......... . . . . . . . . . . 21
Using the Master Index ....... . . . . . . . . . . . . . . . 22
Searching for a.Topic. ..... . . . . . . . . . . . . . . . 23
Printing a Master Index Entry ......... . . . . . . . . 24
Using Related Information. . . . ....... . . . . . . . . 25
Using the Information Folder. . . . ....... . . . . . . . . 26
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Displaying Help for an Object.or Folder. ......... 28
Displaying Help for a Pop-up Menu Choice. . . . . . . . . 28
Displaying Help for a Highlighted Word.or Phrase . . . 28
Displaying Help for OS/2 Messages. . . . . ........ 29
Displaying Help for OS/2 Commands. . . . . ...... . 30
Chapter 2. Features . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Installation of OS/2.2.0. . ... . . . ... . . . . . . . . . . . . 33
+ Copyright IBM Corp. 1991 iii
Multitasking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
DOS Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Multiple Virtual DOS Machines . . . . . ......... . . . . 36
DOS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Dual Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Microsoft Windows Compatibility. . . . ....... . . . . . . . 37
Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Special Needs Support. . . ..... . . . . . . . . . . . . . . . . 37
Lockup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
High Performance File System. . . . ....... . . . . . . . . 40
Extended Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 40
OS/2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Procedures Language/2.REXX . ..... . . . . . . . . . . . . . 41
System Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Games Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Productivity Programs . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix A. Keyboard and Mouse Use ......... . . . . . 47
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
ivIBM OS/2 32-bit Overview Pre-Release Copy
Notices
References in this publication to IBM products, programs, or
services do not imply that IBM intends to make these available in
all countries in which IBM operates. Any reference to an IBM
product, program or service is not intended to state or imply that
only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not
infringe any of IBM's intellectual property rights or other legally
protectible rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in
conjunction with other products, programs, or services, except
those expressly designated by IBM, are the user's responsibility.
The following terms, denoted by a single asterisk (*) in this
publication, are trademarks of the IBM Corporation in the United
States and/or other countries:
AIX IBM Operating System/2
OS/2 Presentation SAA
Manager
Systems Application
Architecture
The following terms, denoted by a double asterisk (**) are
trademarks of other companies:
AST AST Corporation
Intel386 Intel Corporation
Intel486 Intel Corporation
Intel Intel Corporation
Lotus Lotus Corporation
Microsoft Microsoft Corporation
Windows Microsoft Corporation
+ Copyright IBM Corp. 1991 v
viIBM OS/2 32-bit Overview Pre-Release Copy
About This Book
This book introduces you to IBM * Operating System/2 * (OS/2 * )
Version 2.00. It describes the graphical appearance of the
operating system, the features of the operating system, and
explains how to use the online information. It also introduces you
to some important operating system concepts and describes the
differences between this version and previous versions of the
operating system.
This book describes how to complete most tasks and actions using
a mouse. If you are using a keyboard, see Appendix A,
﨣eyboard and Mouse Use?on page 47 for information on how to
most efficiently use the keyboard keys to perform tasks and
actions.
During installation, you are asked if you want to learn how to use
the mouse. If this is the first time you are using a mouse, choose
this option. After you install the operating system, you can learn
more about using a mouse in the OS/2 Tutorial.
Using This Book
Everyone who will be using OS/2 Version 2.00 should read this
book.
Keep this book as a reference.
Related Information
The following describes the documentation and online information
that comes with the product. Online describes information that
can be displayed on your screen.
* Trademark of the IBM Corporation
+ Copyright IBM Corp. 1991 vii
Quick Start
This card provides a brief, limited set of instructions on
how to install the operating system and quickly become
productive. If you want to install the entire operating
system (rather than select only certain features), use
this card. If you want more detailed information about
installing the operating system, use the Installation
Guide.
OS/2 Installation Guide
This book describes how to prepare for and install the
operating system. It also provides information about
installing more than one operating system on your
computer.
OS/2 Tutorial
This online, interactive program shows you the basics
of the operating system. The tutorial starts
automatically after you install the operating system.
Master Index
This online, alphabetic list contains most of the
information you need to use OS/2 2.0.
Glossary This online, alphabetic list contains computer and
operating system terms and definitions.
OS/2 Command Reference
This online information describes how to use OS/2
commands.
REXX Information
This online information describes how to use the REXX
procedure language.
viii IBM OS/2 32-bit Overview Pre-Release Copy
The following publications will be available and can be ordered
separately:
IBM Operating System/2 Keyboards and Code Pages
This book contains reference information for those who
use code-page switching to provide support for files that
are received from or sent to other countries.
OS/2 Version 2.00 Volume 1: Control Program, GG24-3730
This book provides detailed information about the
Control Program component of the OS/2 Version 2.00
operating system. The book describes memory and
task management, debugging support, and enhanced
application programming interfaces.
It also describes installation and national language
considerations, and discusses enhanced hardware
support.
OS/2 Version 2.00 Volume 2: DOS and Windows Environment,
GG24-3731
This book provides detailed information about the
Multiple DOS Machines feature, and support for
Microsoft ** Windows ** programs. The book describes
the architecture of Multiple Virtual DOS Machines, 8086
emulation, device drivers, extended memory support,
DOS settings, and using specific versions of DOS.
It also provides technical information about using
Microsoft Windows programs, and DOS Protect Mode
Interface (DPMI).
OS/2 Version 2.00 Volume 3: Presentation Manager, GG24-3732
This book provides detailed information about the
*
Presentation Manager component of OS/2 Version 2.00.
The book introduces the Presentation Manager, and
describes the enhanced graphical appearance of the
operating system, and enhanced help facilities.
** Trademark of the Microsoft Corporation
* Trademark of the IBM Corporation
About This Book ix
It discusses programming considerations for 32-bit or a
mix of both 16- and 32-bit code application
development, and when migrating existing 16-bit
applications. It also describes support for national
languages and double-byte character sets.
Changes from Previous Versions
The operating system has a changed look and many new features.
The Desktop Manager, File Manager, Print Manager, and Control
Panel are replaced by folders and objects. The Task List is now
called the Window List.
Although the appearance of the operating system is changed, you
can still use your existing programs with this version. To save
your existing programs in a folder called OS/2 Programs, be sure
you do not format your hard disk before or during installation of
OS/2 Version 2.00.
The following describes the new features in OS/2 Version 2.00.
Enhanced DOS compatibility
The Multiple Virtual DOS Machines feature removes the
restriction of running only one DOS program at a time
in DOS mode.
The DOS Settings feature helps optimize performance
of DOS programs.
Previous versions of the operating system did not
support DOS timing-dependent programs, such as
communications and real-time programs. Many of
these programs now run in OS/2 Version 2.00.
Microsoft Windows Compatibility
Microsoft Windows programs now run in OS/2 Version
2.00.
Boot Manager
The Boot Manager feature provides support for
installation of multiple operating systems.
xIBM OS/2 32-bit Overview Pre-Release Copy
Special Needs Support
The Special Needs feature provides support for
changing the way the keyboard keys work.
Security Support
The Lockup feature provides protection for information
in your computer.
Additional Programs
Games and Productivity programs have been added.
Use these programs to, for example, edit files, chart
graphs, create to-do lists, or play games.
About This Book xi
xiiIBM OS/2 32-bit Overview Pre-Release Copy
Chapter 1. Introducing OS/2 2.0
Welcome to OS/2 2.0.
The OS/2 operating system transforms your computer into a
powerful tool that helps you manage your work. It takes full
advantage of Intel386 ** and Intel486 ** technology. Increased
performance made possible by this technology means 32-bit and
16-bit programs run faster.
OS/2 2.0 supports multitasking (running more than one program at
once), installation of other operating systems, and compatibility
with existing programs that run under DOS and Microsoft **
**
Windows . You can organize programs, communicate with other
computers, write and print letters, and play games.
A lockup feature helps protect important information. A special
needs feature is available, if you need to change the way keyboard
keys work because of manual dexterity preferences.
The OS/2 operating system features a graphical appearance.
Whether you are writing a letter, using a printer, or playing a
game, you work with objects that graphically represent the letter,
printer, or game.
The OS/2 operating system is your lectronic workplace.?
OS/2 2.0 also features online information. Whether you need help,
want to learn about the operating system, need a term defined, or
want to explore topics related to concepts, commands, or REXX,
the information is online.
The online information is your lectronic library.?
This chapter describes folders and objects, explains how to use
the online information, and introduces some operating system
** Intel386 and Intel486 are trademarks of the Intel Corporation, and Microsoft and
Windows are trademarks of the Microsoft Corporation.
+ Copyright IBM Corp. 1991 1
concepts. Chapter 2, 﨔eatures?on page 33 describes other
operating system features.
Introducing Folders and Objects
The OS/2 operating system is like your real workplace, except the
things you work with are arranged on your computer screen, not
on your desk or in your office. For example, in your real
workplace, you might work with a letter, an appointment book, or a
printer. With the OS/2 operating system, you work with an object
that represents the letter, appointment book, or printer.
An object that contains other objects is a folder. You can use
folders to organize objects. For example, in your real workplace,
you probably organize the things you frequently use to do your
work in a convenient place. With the OS/2 operating system, you
can organize the objects you frequently work with in a folder.
Conceptual art
2IBM OS/2 32-bit Overview Pre-Release Copy
Folders and objects appear on your screen as miniature pictures
that look similar to real things in your workplace. For example, if
you install a printer, your printer object appears as a miniature
picture of a printer. A miniature picture that represents a folder or
an object is an icon.
When you finish installing OS/2, the OS/2 Tutorial and the icons
that represent the folders and objects that come with OS/2 appear
on the screen, like this:
Screen Capture of shell
Note: The tutorial appears automatically only the first time you
use the operating system.
The tutorial has information about using a mouse and presents
some operating system concepts. You also get a chance to
practice using many of the features. When you complete the
tutorial, you can start using the folders and objects that come with
OS/2 2.0.
There is one folder that comes with the OS/2 operating system that
is unique, called the Desktop folder. It fills the entire screen, and
contains all other folders and objects.
Chapter 1. Introducing OS/2 2.0 3
The following list describes the contents of the other folders or
objects.
OS/2 System
This folder contains other folders and objects that:
? Show drive locations
? Contain startup instructions
? Help you customize the system
?
Contain games and productivity programs
? Are used to select OS/2 or DOS command prompts.
Master Index
This object contains an alphabetic list of online topics
related to understanding and using the operating
system.
For example, use the Master Index to find information
about how to install programs or copy, move, print, and
arrange objects.
Information
This folder contains objects that represent the:
? Tutorial, which has information about using a
mouse and how to use the operating system
? Glossary, which lists terms and their definitions
? OS/2 Command Reference, which describes
commands and their usage
? REXX Information, which describes using the REXX
procedures language.
Shredder This object is used to delete objects.
Templates
This folder contains templates (blank forms) for objects.
Use the templates to create OS/2 or DOS full-screen or
window sessions, or data, program, device, or
installation objects.
4IBM OS/2 32-bit Overview Pre-Release Copy
During installation, you will make choices about the hardware and
software you are using. Depending on the choices you make, the
following folders or objects appear in the Desktop folder.
Network This folder contains other folders and objects that
represent a Local Area Network (LAN).
Printer This object represents a printer.
DOS Programs
This folder contains programs previously installed using
DOS.
Microsoft Windows Programs
This folder contains programs previously installed using
Microsoft Windows.
OS/2 Programs
This folder contains programs previously installed using
earlier versions of the OS/2 operating system.
Note: If you format the hard disk before or during installation, any
programs previously installed using DOS, Microsoft
Windows, or an earlier version of the OS/2 operating
system are not saved in a folder.
Managing Objects
You can manage objects in a way that is similar to the way you
already manage your work. For example, during your work day,
you might select letters or file folders you need to work with,
arrange your work in order of importance, or copy letters at a
copier.
With objects, you can do the same kinds of tasks. You can select,
arrange, or copy objects. In addition, you can open, move,
discard, or print objects.
Chapter 1. Introducing OS/2 2.0 5
Selecting Objects
You must select (choose) an object before you can perform an
action on it. This is similar to selecting what letters you will write
or what files you will work with that day. For example, if you want
to print or copy an object, you first select it. Then, you select the
appropriate action on the pop-up menu (print or copy) that you
want to apply to the selected object.
To select an object:
1. Move the mouse pointer to the object.
2. Press the left mouse button (mouse button 1) once.
(When you select an object, a shaded box appears around the
object.)
Screen Capture - Selected object
Once you select an object, there are two ways to perform an
action on the object:
? Select the action from a pop-up menu. (A pop-up menu lists
actions that can be applied to the object).
? Perform the action directly on the object.
6IBM OS/2 32-bit Overview Pre-Release Copy
Using Pop-up Menus
To display the pop-up menu for the selected object, move the
mouse pointer to the object; then press the right mouse button
(mouse button 2) once.
Once the pop-up menu appears, you can select a choice from it. A
typical pop-up menu for an object might look like this:
Screen Capture - Typical menu for object
To select a choice:
1. Move the mouse pointer to the choice.
2. Press the left mouse button (mouse button 1) once.
Sometimes one or more choices on the menu have additional
choices available. If additional choices are available, an arrow
appears to the right of the pop-up menu choice.
To display the additional choices:
1. Move the mouse pointer to the arrow.
2. Press the left mouse button (mouse button 1) once.
Chapter 1. Introducing OS/2 2.0 7
Working Directly with Objects
You have already read about how to select an object, and then
how to apply an action to that object by selecting a choice on a
pop-up menu. You can also directly manage objects. Generally,
this means that without using a pop-up menu you can perform
most actions directly on an object.
The following list shows some of the terms associated with
performing an action directly on an object.
Click Press the left mouse button (mouse button 1) once.
Double-click
Press the left mouse button (mouse button 1) twice.
Drag Move the mouse pointer to the object. Then, press and
hold down a mouse button (either 1 or 2, depending on
the action being performed) while moving the mouse
pointer across the screen.
As you move the mouse pointer, the object moves
along with it.
In addition to these actions, some actions must be done using both
the keyboard and the mouse. When performing these actions, the
key you press and hold down changes the way the basic mouse
operation works. For example, when you copy an object, you
press and hold down the Ctrl key and drag the object. Holding
down the Ctrl key tells the operating system to copy the object, not
move it.
8IBM OS/2 32-bit Overview Pre-Release Copy
Moving Objects
You can move an object to another object. The object you move
no longer appears in the previous location. This is similar to
moving a letter from one file folder to another or moving a letter
from your desk to a file cabinet.
Conceptual Art
To move an object, you do the following:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2 while dragging the object
to another object.
3. When the object is over the object you want to move it to,
release mouse button 2.
Chapter 1. Introducing OS/2 2.0 9
Copying Objects
You can copy an object to another object. A duplicate of the
object is created and placed in the other object. This is similar to
making a copy of a letter on a copier and then placing the original
in one file folder and the copy in another.
Conceptual Art
To copy an object, you must use both the keyboard and the
mouse, as follows:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2.
3. Press and hold down the Ctrl key.
4. Drag the object to the object where you want a copy.
5. When the object is over the object you want a copy to appear
in, release mouse button 2.
6. Release the Ctrl key.
10IBM OS/2 32-bit Overview Pre-Release Copy
Printing Objects
If you are using a printer or plotter, you can print objects.
Conceptual Art
To print an object, you do the following:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2 while dragging the object
to the Printer.
3. When the object is over the Printer, release mouse button 2.
Chapter 1. Introducing OS/2 2.0 11
Deleting Objects
You can delete or permanently remove an object that you are sure
you no longer need. This is similar to shredding papers in a
shredder.
Conceptual Art
To delete an object, you do the following:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2 while dragging the object
to the Shredder.
3. When the object is over the Shredder, release mouse button 2.
Once an object is deleted, it cannot be recovered.
12IBM OS/2 32-bit Overview Pre-Release Copy
Arranging Objects
You can arrange objects on the screen according to your
preference and work needs. This is similar to arranging or placing
the things on your desk that you will need to work with that day.
For example, if you work with certain objects every day, you might
want to place them in a row at the bottom of your screen.
Conceptual Art
To arrange objects, you do the following:
1. Move the mouse pointer to one of the objects you want to
arrange.
2. Press and hold down mouse button 2.
3. Drag the object in the direction you want to move the object.
4. When the object is in the new location, release mouse button
2.
Repeat these actions until you are satisfied with the arrangement.
Chapter 1. Introducing OS/2 2.0 13
Opening Objects
You can open an object to look at the contents of the object. This
is similar to opening a file folder to look at the letters that are
inside. For example, if you file a letter (object) in a folder and
want to display the contents of the letter, first open the folder.
Then, open the letter to look at its contents.
To open an object, move the mouse pointer to the object, then
press mouse button 1 twice (double-click).
When you open an object, the contents appear in a separate area
on the screen called a window. Each object opened appears in its
own window. For example, if you install a database program and
a text editor program, and open both programs, they appear in two
separate windows, like this:
Screen Capture - Two windows/titles
While many programs can be opened and displayed in windows,
you can work directly with only one. The program you choose to
work with is the interactive program.
14IBM OS/2 32-bit Overview Pre-Release Copy
Selecting Window Parts
The following describes some of the parts of a window and how to
use them. For more detailed information about the parts of a
window, review the OS/2 Tutorial.
Screen Capture of Window
?? Border . This part of the window is the boundary. When the
border is highlighted, the window is interactive (contains the
interactive program) and is usually the topmost window when two
or more windows are displayed. Use the border to size the
window. For more information about sizing a window, see izing
a Window?on page 17.
?? .Close button Use this button to close the window. Move the
mouse pointer to the button and double-click on it.
?? .Title bar This part of the window shows the title of the
window. Use the title bar to move the window. For more
information about moving a window, see 﨧oving a Window?on
page 18.
?? .Minimize button Use this button to make the window the
smallest possible size. (Generally, when minimized, the window is
invisible). Move the mouse pointer to the button and double-click
on it. The contents of the window are not affected when you
minimize it.
?? .Maximize button Use this button to make the window the
largest possible size. (Generally, when maximized, the window
fills the entire screen). Move the mouse pointer to the button and
double-click on it. The contents of the window are not affected
when you maximize it.
?? .Scroll bar Use the scroll bar to show more information in the
window. Move the mouse pointer to the up, down, right, or left
arrow; then press and hold down mouse button 1. When you press
and hold down mouse button 1, the information in the window
scrolls up, down, right, or left. Release the mouse button when
you are done scrolling through the information in the window.
Chapter 1. Introducing OS/2 2.0 15
Using the Window List
The Window List shows a list of the objects and programs you are
using. This includes objects or programs that you minimized
(made invisible).
To display the Window List, move the mouse pointer to any area of
the Desktop folder that is blank, (not on a window or any part of a
window, an object, or another folder); then press mouse button 2
once. The Window List looks like this:
Screen Capture - Window List
Use the Window List to quickly switch to an object or a program
shown in the list, by double-clicking on the name of the object or
program.
16IBM OS/2 32-bit Overview Pre-Release Copy
Sizing a Window
You can make a window larger or smaller. Changing the size of a
window does not affect the contents of the window.
Conceptual Art
To size a window, you do the following:
1. Move the mouse pointer to the border of the window. (The
mouse pointer changes shape to a double arrow when it is in
position correctly on the border.)
2. Press and hold down mouse button 2.
3. Drag the border in the direction that you want.
4. When you are satisfied with the new size, release mouse
button 2.
Chapter 1. Introducing OS/2 2.0 17
Moving a Window
You can move a window to any location on the screen. For
example, if two windows are open at the same time, you might
want to place one window in the upper-left corner and the other in
the lower-right corner of the screen. You can move the windows
to those positions.
Conceptual Art
To move a window, you do the following:
1. Move the mouse pointer to the title bar of the window.
2. Press and hold down mouse button 2.
3. Drag the window in the direction you want to move it.
4. When the window is in the new location, release mouse button
2.
Repeat these actions until you are satisfied with the new
arrangement.
When you move a window (using the method described below) the
contents and size of the window are not affected.
18IBM OS/2 32-bit Overview Pre-Release Copy
In addition to arranging windows by moving each one individually,
you can arrange automatically all the windows you have open.
1. Display the pop-up menu for the Window List. To do this,
move the mouse pointer to an area (within the Window List
window) that is blank. Then, press the right mouse button
(mouse button 2) once.
2. Move the mouse pointer to the Window choice.
3. Move the mouse pointer to the right arrow; then press mouse
button 1 once.
4. Select the Cascade or Tile choice.
If you cascade or tile windows, the contents of the windows are not
affected. However, the contents may not be completely visible, but
you will always be able to see the title bars. In addition, the size
of the windows might change, and the windows might appear to
overlap.
The cascade arrangement places the window that contains the
interactive program on top (closest to you). Other open windows
are put behind this window.
The cascade arrangement looks like this.
Screen Capture - Cascade
Chapter 1. Introducing OS/2 2.0 19
The tile arrangement places the window that contains the
interactive program in the upper-left corner of your screen. Other
open windows are put next to this window and to each other, until
the screen is completely full.
The tile arrangement looks like this.
Screen Capture - Tile
20IBM OS/2 32-bit Overview Pre-Release Copy
Introducing Online Information
Most of the information for the operating system is online. The
information you need can be displayed on your screen while you
are doing your work. The online information is your lectronic
library.?
Conceptual Art
Chapter 1. Introducing OS/2 2.0 21
Using the Master Index
The Master Index is an alphabetic list of topics related to
understanding and using the OS/2 operating system. The list
contains the following kinds of topics:
? Things to consider before performing a task
?
The steps you need to take to complete a task
? Operating system concepts
? DOS error messages.
After you install the OS/2 operating system and review the OS/2
Tutorial, open the Master Index by double-clicking on the Master
Index folder.
When the Master Index is open, it looks like this:
+-------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-------------+
The list of topics appears in an area within the window that looks
like a notebook with tabs. Each tab has a letter of the alphabet on
it that corresponds to the group of topics that start with that letter.
Use the letters on the tabs to move through the index. For
example, if you need information about the topic opying an
object,?you do the following:
1. Move the mouse pointer to the tab that has the letter C on it.
2. Press mouse button 1 once to select the first topic that starts
with the letter C.
3. Move the mouse pointer to the down arrow on the scroll bar.
22IBM OS/2 32-bit Overview Pre-Release Copy
4. Press mouse button 1 to scroll through the topics that start
with the letter C, until you locate the entry for copying an
object.
5. Double-click on the entry (copying an object).
The information for the entry (copying an object) appears in a
window to the right of the Master Index window, like this:
Screen Capture - MI w/entry open
If you leave the Master Index open while you work with the OS/2
operating system, it is always available for you to use. You can
move the Master Index window to any location on the screen (just
like other windows).
Searching for a Topic
The Master Index has a search action. You can search for an
entry using one or more words that describe the topic. For
example, to search for information about how to duplicate an
object, you might search using the word uplicate,?uplicates,?
or even uplicating.?The result of a search (using duplicate,
duplicates, or duplicating), is opying an object.?
Chapter 1. Introducing OS/2 2.0 23
To search for a topic:
1. Display the Master Index pop-up menu. To do this, move the
mouse pointer to an area (within the Master Index window)
that is blank. Then, press the right mouse button (mouse
button 2) once.
2. Move the mouse pointer to the Search choice; then press
mouse button 1 once.
A window appears that looks like this:
Screen Capture - Search pop-up
3. Type the word or words that describe the topic.
4. Move the mouse pointer to the word Search (located in the
lower-left corner); then press mouse button 1 once.
5. When the list of topics appears, double-click on the entry.
Printing a Master Index Entry
Once you locate a topic, you might want to print that entry. (You
can only print one entry at a time).
To print an entry:
1. Move the mouse pointer to the entry you want to print; then
press mouse button 1 once.
24IBM OS/2 32-bit Overview Pre-Release Copy
2. Display the Master Index pop-up menu. To do this, move the
mouse pointer to an area (within the Master Index window)
that is blank. Then, press the right mouse button (mouse
button 2) once.
3. Move the mouse pointer to the Print choice; then press mouse
button 1 once.
Using Related Information
You have just read about using the Master Index, and searching
for and printing entries. As you use the Master Index, you will
often find that the entry you select has related topics, which you
may find useful. Related topics are listed under the heading
elated Information,?like this:
Screen Capture - MI w/entry w/hypertext
To select a related topic, move the mouse pointer to the entry;
then double-click on the entry.
For more information about using the Master Index, searching for
topics, printing an entry, or using related information, review the
OS/2 Tutorial.
Chapter 1. Introducing OS/2 2.0 25
Using the Information Folder
The Information folder contains the OS/2 Tutorial, Glossary, OS/2
Command Reference, and REXX Information. Use the contents of
the Information folder to learn more about the operating system, to
look for the definition of a term, to use OS/2 commands, or to use
REXX.
To open the Information folder, double-click on it. When the
Information folder is open, it looks like this:
Screen Capture - Info folder/open
The OS/2 Tutorial has information about how to use a mouse, work
with objects and folders, use windows, get help, and other general
information. (The first time you use the operating system, the
tutorial is opened automatically for you.)
The Glossary is an alphabetic list of terms and their definitions. If
you are not familiar with a term you read about in the online
information or online help, use the Glossary to find the definition
for the term.
The OS/2 Command Reference describes the purpose of each
command, and the syntax and parameters for each command. It
26IBM OS/2 32-bit Overview Pre-Release Copy
also has information about topics such as batch files, command
operators, redirection symbols, and substitution variables.
The REXX Information describes the commands you use to write
simple batch programs. It also has information about topics such
as procedures, elements, and comments.
To open the OS/2 Tutorial, or the Glossary, or the OS/2 Command
Reference, or the REXX Information, double-click on it.
Getting Help
Online help is always available. To get help, select the word
﨟elp?when it is displayed on your screen or press F1.
When you request help, the information appears in a help window,
like this:
Screen Capture - Help Window
You can also get help for OS/2 messages and commands.
The following describes some of the different ways you can get
help. For more detailed information, review the OS/2 Tutorial or
request help from within a help window.
Chapter 1. Introducing OS/2 2.0 27
Displaying Help for an Object or Folder
The help for an object or folder describes the object or contents of
the folder.
To display help for an object or folder:
1. Move the mouse pointer to the object or folder.
2. Press the right mouse button (mouse button 2) once. (The
pop-up menu for the object appears.)
3. Move the mouse pointer to the Help choice.
4. Press mouse button 1 once.
Displaying Help for a Pop-up Menu Choice
The help for a pop-up menu choice describes the action you can
apply to a selected object or folder.
To display help for a pop-up menu choice:
1. Move the mouse pointer to the pop-up menu choice.
2. Press and hold down mouse button 1. (Do not release mouse
button 1).
3. Press the F1 key.
4. When the help window appears, release mouse button 1.
Displaying Help for a Highlighted Word or Phrase
Sometimes a word or a phrase in a help window is highlighted.
The highlighting means that additional help information is
available. The additional help information might be a definition, or
related information, or help for a field.
28IBM OS/2 32-bit Overview Pre-Release Copy
The following shows a help window with highlighted phrases. (In
this example, the highlighted phrases show that additional help
information is available for fields.)
Screen Capture - Help Window w/highlighted phrases
To display the additional help:
1. Move the mouse pointer to the highlighted word or phrase.
2. Press mouse button 1 twice. (The additional help information
appears in another help window. The original help window is
directly underneath the new help window and is not visible.
However, the original help window is still open.)
3. When you finish reviewing the additional help information,
press Esc to return to the original help window.
Displaying Help for OS/2 Messages
The help for OS/2 messages describes how to correct an error or
respond to a warning, or provides general information. The way
you request help for a message depends on how the message is
displayed.
If the message appears in a message window with the word
﨟elp?in it, then do the following:
1. Move the mouse pointer to the word 﨟elp.?
Chapter 1. Introducing OS/2 2.0 29
2. Press mouse button 1 once.
If the message appears full-screen, and is enclosed in a box, then
do the following:
1. Move the mouse pointer to the phrase 﨑isplay Help.?
2. Press mouse button 1 once.
If the message appears and it has a message number, preceded
by the letters SYS, then do the following:
1. At the OS/2 command prompt, type HELP followed by a space.
Type the message number. (It is not necessary to type the
letters SYS).
2. Press Enter.
For example, if you received this message:
SYS0002: The system cannot find the file specified.
To request help, you type:
HELP 2
Then, press Enter.
The following help appears:
SYS0002: The system cannot find the file specified.
EXPLANATION: The file named in the command does
not exist in the current directory or search path
specified. Or, the file name was entered incorrectly.
ACTION: Retry the command using the correct file name.
Displaying Help for OS/2 Commands
As described earlier, the OS/2 Command Reference contains the
purpose of and syntax for commands. There are two ways to get
help for a command: open the Command Reference or request
help from the OS/2 command prompt.
If you will be entering more than one command, you might find it
more convenient to open the Command Reference in one window,
while entering commands in another window.
30IBM OS/2 32-bit Overview Pre-Release Copy
If you just want to display help for a command and do not want to
open the Command Reference, then do the following:
1. At the OS/2 command prompt, type HELP followed by a space
and the name of the command, like this:
HELP COPY
2. Press Enter.
Chapter 1. Introducing OS/2 2.0 31
32IBM OS/2 32-bit Overview Pre-Release Copy
Chapter 2. Features
As described in Chapter 1, the operating system has a graphical
appearance and most of the information you need is online. In
addition to the features already described, the operating system
has other features. This chapter describes some of them.
Installation of OS/2 2.0
OS/2 2.0 features a graphical installation. For example, progress
bars show you what percentage of features on each installation
diskette is installed.
During installation, you will be asked if you want to learn how to
use the mouse. If this is the first time you are using a mouse,
choose this option to learn how to use the mouse.
For more information about installing OS/2 2.0, see the Quick Start
card or the Installation Guide.
Multitasking
Multitasking is a feature that makes it possible to work with more
than one program or task at a time. This feature is available as
soon as you finish installing the OS/2 operating system.
Think of each program or task you use as a session.
A session can be one of two types:
? Foreground Session
You work directly with this interactive session. It receives
input from your keyboard and mouse or displays information
on your screen.
? Background Session
You do not work directly with this session. However, programs
or tasks running in a background session can be processing
data.
+ Copyright IBM Corp. 1991 33
For example, if you have a large database, it may contain
thousands of records. Normally, updating a database this size
takes some time, and with other operating systems your
computer cannot be used while the data is updating.
Multitasking removes that barrier. You can instruct the
database program to start processing data, and then you can
place it in the background session. While the database
program is running in the background session, you can be
working with another program in the foreground session.
A program or a task in a background session will stop running
only when it needs further instructions from you. At that time
you can end the session or bring it to the foreground.
For more information about multitasking, see the Master Index.
34IBM OS/2 32-bit Overview Pre-Release Copy
DOS Compatibility
DOS programs take full advantage of most of the features of the
OS/2 operating system. For example, DOS programs use the
multitasking feature, and run either full-screen or in windows. You
can size, arrange, or move DOS programs running in windows,
exactly like OS/2 programs running in windows.
Conceptual Art
Chapter 2. Features 35
There are also features in this version of the OS/2 operating
system that enable DOS programs to run as well as programs
written specifically for the OS/2 operating system. These features
are described below.
Multiple Virtual DOS Machines
This feature makes it possible to run up to 16 DOS programs at the
same time. Each DOS program can run in a foreground or
background session. Up to 630KB (KB equals 1024 bytes) of
memory are available for each program. DOS programs that use
the Lotus****/ Intel /Microsoft ** (LIM) Expanded Memory Specification
(EMS) and the Lotus/Intel/Microsoft/AST ** (LIMA) Extended Memory
Support (XMS) can also be run.
For more information about using Multiple Virtual DOS Machines,
see the Master Index.
DOS Settings
DOS Settings can be used to tailor the way a DOS program runs.
For example, you can prevent sounds normally heard when a
program is running or you can specify the amount of memory (up
to 630KB) that each DOS program uses.
For more information about using DOS Settings, see the Master
Index and the OS/2 Command Reference.
Dual Boot
The Dual Boot feature provides support for installing DOS Version
3.2 or later and OS/2 2.0 on the same hard disk. With the dual
boot feature, you can switch back and forth between the DOS and
OS/2 operating systems. This feature is useful if you are using
DOS programs that run only under DOS.
For more information about installing the dual boot feature, see the
Installation Guide.
** Lotus is a trademark of the Lotus Corporation, Intel is a trademark of the Intel
Corporation, Microsoft is a trademark of the Microsoft Corporation, and AST is a
trademark of the AST Corporation.
36IBM OS/2 32-bit Overview Pre-Release Copy
Microsoft Windows Compatibility
Text is under development.
Boot Manager
The Boot Manager feature makes it possible for OS/2 Version 2.00
to coexist with other operating systems (for example, DOS,
*
previous versions of the OS/2 operating system, and AIX ). If you
install this feature, you choose which operating system you want to
be active each time you start your computer.
For more information about installing and using the Boot Manager,
see the Installation Guide.
Special Needs Support
The Special Needs feature provides support for changing the way
the keyboard keys work. This support is useful, for example, for
individuals whose manual dexterity is impaired.
The Special Needs feature is used to change:
? The amount of time a key can be held down before it is
considered to have been pressed
? The amount of time a key can be held down before it begins
repeating its function
? The rate at which a key will repeat its function when it is held
down
? The way a series of keys is pressed and released.
For example, to restart the computer, you press the
Ctrl+Alt+Del keys at the same time. You can change the
way this series of keys works (without changing the result they
produce) by using the sticky keys function.
The sticky keys function sets the keys (in this example,
Ctrl+Alt+Del) to behave as if they were pressed at the same
* Trademark of the IBM Corporation.
Chapter 2. Features 37
time without actually having to press them at the same time.
You can press the keys one at a time to produce the same
result as pressing them together.
For more information about the Special Needs feature, see the
Master Index.
38IBM OS/2 32-bit Overview Pre-Release Copy
Lockup
The Lockup feature provides protection for the information in your
computer. When Lockup is used, the mouse and keyboard are
locked.
When you use Lockup, a password (known only by you) is set.
Each time you want to unlock your system, you must type this
password to gain access to the system.
For more information about using Lockup, see the Master Index.
Conceptual Art
Chapter 2. Features 39
High Performance File System
The High Performance File System feature provides fast access to
information on your computer's hard disk. The High Performance
File System is an installable file system like the DOS file system
FAT (File Allocation Table). An installable file system manages the
information stored on diskettes or the hard disk of your computer.
The High Performance File System is faster than FAT because of
the method that it uses to find information on the hard disk.
The High Performance File System provides support for long file
names (up to 254 characters). File names can contain blank
spaces, if the part of the file name that contains the blank space is
enclosed by quotation marks ().
The High Performance File System saves file names exactly as
typed. For example, if you create a file and name it AbC, it is
saved as AbC, not ABC. However, when you search for the file, it
is found whether you type ABC, AbC, or abc.
For more information about installing the High Performance File
System, see the Installation Guide. For more information about
using the High Performance File System, see the Master Index.
Extended Attributes
Attributes are characteristics that describe a file to the operating
system. For example, a file attribute might be the time or date the
file was created.
Extended attributes are additional attributes that describe the file.
For example, an extended attribute might be the name of the
person who created the file. If you use extended attributes to
describe a file, you can search for the file using the extended
attribute. For example, if the name of the person who created the
file is 﨡oe,?you can search for the file using the name Joe as one
of your search parameters.
For more information about using extended attributes, see the
Master Index.
40IBM OS/2 32-bit Overview Pre-Release Copy
OS/2 Commands
Commands are words that you type that tell the OS/2 operating
system to perform an action. Enter OS/2 commands from either
the OS/2 full-screen or window command prompt.
There are a number of OS/2 commands that you can use. Some
examples of these are: COPY (to copy files), DATE (to display or
change the date), and DISKCOPY (to copy diskettes).
For more information about using commands, see the OS/2
Command Reference.
Procedures Language/2 REXX
Procedures Language/2 REXX is a generalized command
language. This small, powerful language is the Systems
Application Architecture * (SAA * ) procedures language for the OS/2
operating system.
REXX is useful for writing batch programs, as well as other
programs. It uses common English words and single number
concepts.
For more information about using REXX, see the REXX Information.
System Editor
The System Editor is a simple text editor. You can create, edit, or
view files using the System Editor. Use the editor for simple
editing tasks, for example, editing small batch programs. If you
are doing extensive text editing or word processing, install an
editor designed for those purposes.
The System Editor supports both the mouse and keyboard, and has
extensive online help. It also supports several different font styles,
* Trademark of the IBM Corporation
Chapter 2. Features 41
font sizes, and type styles. You can set the font to the same style
your printer uses and see how the file looks before you print it.
For more information about using the System Editor, see the
Master Index.
42IBM OS/2 32-bit Overview Pre-Release Copy
Games Programs
Use the Games programs for entertainment or educational
purposes. For example, if you want to use a strategy game, try
Reversi. The object of the game is to fill more squares (with red
circles) than your opponent the computer does (with blue circles)
Conceptual Art
For more information about using the games programs, see the
Master Index.
Chapter 2. Features 43
Productivity Programs
Productivity programs are simple programs that can help you with
most operating system and business tasks. For example, use
Presentation Manager * (PM) Chart to make graphs, or Calculator to
add, subtract, multiply, and divide numbers.
Conceptual Art
For more information about using the productivity programs, see
the Master Index.
* Trademark of the IBM Corporation.
44IBM OS/2 32-bit Overview Pre-Release Copy
Chapter 2. Features 45
46IBM OS/2 32-bit Overview Pre-Release Copy
Appendix A. Keyboard and Mouse Use
The following lists some of the most common tasks you can do,
using either the keyboard keys or a mouse.
For a detailed list of keys assignments, do one of the following:
? See the Master Index
? From a pop-up menu, select Help; then select Keys Help
? From within a help window, select Help; then select Keys Help.
The plus sign (+) between key names means to press and hold
down the keys in the order shown and release them together.
System Tasks
Task Keys Mouse
Get Help. F1 Click on the word 﨟elp?
Restart the system. Ctrl + Alt + Del
Switch to next window. Alt + Tab Click on window
Switch to next window or Alt + Esc Click on window or icon
full-screen session.
Display Window List. Ctrl + Esc Move mouse pointer to
blank part of desktop; then
press mouse button 2 once
Folder and Object Tasks
Task Keys Mouse
Move among folders or ? , ? , ? , or ? Click on the folder or
objects. object
Display a pop-up menu. Shift + F2 Press both mouse buttons
at the same time
Select first choice in Home Click on choice
pop-up menu.
Select last choice in End Click on choice
pop-up menu.
Select a choice using the Type the underlined letter
underlined letter.
Open selected folder or Enter Double-click on folder or
object. object
+ Copyright IBM Corp. 1991 47
Task Keys Mouse
Delete selected objects. Del Drag to Shredder
Print selected objects. Shift + Print Screen(PrtSc) Drag to Printer
Select a folder or object. Spacebar Click on folder or object
Select more than one Shift + F8 (to begin Add Hold down Ctrl key while
folder or object. mode), use arrow keys to clicking on each one
move among folders and
objects and press
Spacebar to make each
selection. Press ShiftF8 +
again (to end Add mode)
Select a range of folders Shift + F8 (to begin Add Click on first object in
or objects from cursor's mode), use arrow key to range; then press and hold
current position to move to first file in the down Shift. Click on last
cursor's new position. range and press Spacebar object in range.
to select. Press and hold
down CtrlShift while +
moving to last file in the
range. Release CtrlShift. +
Press ShiftF8 again (to +
end Add mode).
Move folder or object. F7 Drag to another folder or
object
Copy folder or object. F8 Hold down Ctrl key while
dragging to folder or
object where you want a
copy to appear.
Window Tasks
Task Keys Mouse
Move window. AltF7 Move mouse +
pointer to title
bar; then press
and hold mouse
button 2 while
dragging to new
location
Size window. AltF8 Move mouse +
pointer to
border; then
press and hold
mouse button 2
while dragging
border in any
direction
Minimize window. Alt on + F9 Click
Minimize button
48IBM OS/2 32-bit Overview Pre-Release Copy
Task Keys Mouse
Maximize window. Alt on + F10 Click Maximize
button
Close window. AltF4 Double-click on +
Close button
Scroll contents of window up one page. Page Up < PgUp *
Scroll contents of window down one page. Page Down
PgDn < *
Scroll contents of window left one page. Ctrl + Page Up
PgUp < *
Scroll contents of window right one page. Ctrl + Page
Down PgDn < *
Help Window Tasks
These tasks only work from within a help window.
Task Keys Mouse
Switch between Help and program. Alt + F6 Click on
program
Display General Help. F2 Click on
General Help
Display Keys Help. F9 Click on Keys
Help
Display Help Index. F11 Click on Help
Index
Display Using Help. Shift + F10 Click on Using
Help
Display Tutorial. Shift on + F2 Click
Tutorial
Display help for highlighted word or phrase. Use Tab key to Move mouse
move cursor totopointer
highlighted highlighted
word or phrase; word or phrase;
then press Enter then
double-click
Display previous help window. Esc Click on
Previous
Appendix A. Keyboard and Mouse Use 49
Master Index Tasks
Task Keys Mouse
Open Master Index. Select; then Double-click on
press Enter Master Index
icon.
Move through topics one line at a time. Click on topic
Move up through topics one page at a time. Page Up (PgUp)
Move down through topics one page at a time. Page Down
(PgDn)
Move to topic areas. Type letter of Click on letter
the alphabet of the alphabet
Display related information. Use the Tab key Move mouse
to move cursortopointer
to related related
information; information;
then press Enter then
double-click
Remove related information help window. Esc Click on
previous
Change focus. Click on Master
Index listing or
topic
50IBM OS/2 32-bit Overview Pre-Release Copy
Index
Index
closing a window 15
A Command Reference
arranging objects 13 description of viii
arranging windows 18 displaying 27
attributes, definition of 40
commands, using 41
compatability
DOS 35
B Microsoft Windows 37
background session 33 copying objects 10
Boot Manager 37
border, definition of 15
button D
Close 15 deleting an object 12
Maximize 15 Desktop folder, defintion of 3
Minimize 15 discarding objects 12
displaying
C Command Reference 27
Glossary 27
cascade arrangement 19 help for folders 28
Changes from previous versions help for highlighted phrases 28
Boot Manager x
Control Panel x help for highlighted words 28
Desktop Manager x help for messages 29
help for objects 28
DOS compatibility x help for OS/2 commands 30
DOS Settings x help for pop-up menu
File Manager x
games xi choices 28
Lockup xi Information folder 26
Master Index 22
Microsoft Windows objects 14
compatibility x OS/2 Tutorial 27
Multiple Virtual DOS
Machines x pop-up menu 7
Print Manager x related information 25
REXX Information 27
Productivity programs xi DOS compatibility 35
special needs x DOS Programs
Task List x
changing the location of an compatibility 35
object 9 DOS Settings 36
Dual Boot 36
click, definition of 8 Multiple Virtual DOS
Machines 36
+ Copyright IBM Corp. 1991 51
Index
DOS Programs (continued) features of OS/2 33
running more than one 36 file systems, definition of 40
DOS Programs folder, description folders
of 5 DOS Programs 5
DOS Settings 36 help for 28
double-click, definition of 8 Information 4
dragging a window 18 introducing 2
drag, definition of 8 Microsoft Windows Programs 5
Dual Boot 36 Network 5
duplicating an object 10 OS/2 Programs 5
OS/2 System 4
Templates 4
E folder, definition of 2
editor, system 41 foreground session 33
erasing an object 12
extended attributes 40
G
Games
F getting help 27
features Glossary, displaying 27
Boot Manager 37
DOS compatiblity 35
DOS Settings 36 H
Dual Boot 36 Help
extended attributes 40 for a folder 28
Games programs 43 for a highlighted phrase 28
High Performance File for a highlighted word 28
System 40 for a pop-up menu choice 28
installation 33 for an object 28
learning to use a mouse 33 for messages 29
Lockup 39 for OS/2 commands 30
Microsoft Windowshelp window, description of 27
compatibility 37High Performance File System 40
Multiple Virtual DOS highlighted phrase, help for 28
Machines 36 highlighting, defintion of 28
multitasking 33
OS/2 Commands 41
I
Procedures Language/2
REXX 41 icons, introducing 2
Productivity programs 44 icon, definition of 3
special needs support 37 index, online 22
System Editor 41 Information folder
description of 4
52IBM OS/2 32-bit Overview Pre-Release Copy
Index
Information folder (continued) mouse
displaying 26 introducing vii
Installation Guide use of 6, 8
description of viii moving objects 9
installation of OS/2 33 Multiple Virtual DOS Machines 36
installing, more than one operating multitasking
system 37 definition of 1
interactive program, definition description of 33
of 14
interactive window, definition
N
of 15
Network folder, description of 5
K
keyboard and mouse use 47 O
objects
arranging 13
L copying 10
locking your system 39 discarding 12
Lockup 39 displaying 14
look at the contents of an displaying a pop-up menu 7
object 14 help for 28
introducing 2
managing 5
M Master Index 4
Master Index moving 9
description of 22 opening 14
displaying 22
Printer 5
printing an entry 24 printing 11
searching for a topic 23 Shredder 4
topics 22 working with 8
using 22 object, definition of 2
using related information 25
online information
Master Index object, description27getting help
of 4 Glossary 26
maximizing a window 15 Information folder 26
messages, help for 29 introducing 1, 21
Microsoft Windows
Master Index 21
compatiblity 37 OS/2 Command Reference 26
Microsoft Windows Program folder,26OS/2 Tutorial
description of 5 REXX Information 27
minimizing a window 15 searching for a topic 23
using 21
Index 53
Index
open an object 14 R
opening the Master Index 22
OS/2 commands 41 rearranging objects 13
displaying help for 30 related information, displaying 25
using 41 REXX Information
description of viii
OS/2 operating system displaying 27
changes from previous
versions x REXX, description of 41
description of 1 running multiple DOS
features 33 programs 36
running more than one
program 33 S
OS/2 Programs folder, description
of 5 scroll bar 15
OS/2 System folder, description searching for a topic 23
securing your system 39
of 4 select, definition of 6
OS/2 Tutorial sessions
description of viii
displaying 27 background 33
foreground 33
mulitple DOS 36
Shredder object, description of 4
P shredding an object 12
pop-up menu
definition of 6 sizing a window 17
displaying 7 special needs support 37
help for choices 28 sticky keys, definition of 37
System Editor 41
using 7
working with 7
preventing unauthorized use of
system 39 T
Printer object, description of 5 tailoring a DOS program 36
Templates folder, description of 4
printing a Master Index entry 24 throwing away an object 12
printing objects 11 tile arrangement 19
Procedures Language/2 REXX 41
productivity programs tiling windows 18
program, interactive 14 title bar 15
topmost window 15
protecting information on tutorial 27
system 39
Q U
Quick Start using the keyboard 47
description of viii
54IBM OS/2 32-bit Overview Pre-Release Copy
Index
V
view the contents of an object 14
W
Window List
description of 16
using 16
windows
arranging 18
border 15
cascade 18
closing 15
dragging 18
interactive 15
maximizing 15
minimizing 15
scroll bar 15
selecting parts 15
sizing 17
tile 18
title bar 15
Window List 16
window, definition of 14
working with objects 8
Index 55
�
READ6167.DOC
Read Me First
Welcome to IBM * OS/2 * Version 2.0, the integrating platform for the
personal computer systems.
This development version of the OS/2 operating system is intended
to run existing OS/2, Windows ** and DOS applications.
IBM and others are testing many DOS, Windows, and OS/2 appli-
cations with this operating system. However, some applications,
or functions within applications, might not currently work. We
encourage you to use the support system provided to you to give
us your comments. IBM needs your feedback to ensure that OS/2
Version 2.0 is the best possible product.
Enjoy the new world of the OS/2 operating system!
What's New in This Version?
? The Workplace Shell is now the user interface.
? You can run Windows applications in standard mode,
unchanged, without installing Windows on your system.
? You can start ANY version of DOS in DOS sessions. This
means you can run even version-specific DOS applications.
? Support for DOS unique device drivers has been added.
? More mini-applications, including an asynchronous communi-
cations connection and a LAN-based chess game, have been
added.
? PM installation has been simplified. The enhancements assist
users in customizing the system to their needs.
* Trademark of the IBM Corporation.
** Trademark of the Microsoft Corporation.
Read Me First 1
Installation
Before installing this version of OS/2 2.0, you need to format the
partition in which it will be installed. Otherwise, all your compo-
nents might not work correctly.
Select Features and Install
If you choose the installation option elect Features and Install,?
you must select DOS and all font choices. Otherwise, problems
might occur later.
Migration of Existing Applications
Although you are prompted to migrate your existing applications
during installation, this function has not been implemented in this
development version.
Printer Port Warning Message
When you install a printer during system installation, you will
receive the following pop-up message, even if you have not
installed another printer:
The port you have selected has a printer attached to it.
Select OK and your printer will be installed, using the port you
selected.
Additionally, you will have an extra print object named LPT1Q.
This object is attached to the IBMNULL driver and may be dis-
carded. To discard the object, place the mouse pointer over the
object, press and hold mouse button 2, and drag the object to the
shredder. When you release the mouse button, the object will be
discarded.
2
Installing Printers after OS/2 Installation
We recommend that you install printers during the OS/2 installa-
tion. If you do not, you will need to manually copy IBMNULL.DRV
from the Presentation Manager Device Driver diskette 1 to the
\OS2\DLL\ subdirectory before you install the printer.
In addition, you must make this printer your application default. To
select the printer as your default printer:
1. Move the mouse pointer to the printer object.
2. Press mouse button 2 to get a pop-up menu for the print
object.
3. Select Set default.
4. Select your printer.
Minimum System Configuration Requirements
To install and use the OS/2 operating system, you need a personal
computer system with an 80386, 80386SX, 80486, or 80486SX micro-
processor.
Currently, you need 4MB of memory to install OS/2 2.0.
We are continuing to work on improving the DASD usage of OS/2
2.0. The following numbers reflect current requirements and might
be different in the final product.
Currently, there are three installation options. The DASD require-
ments for these are:
? Install All Features: 26MB
? Install Preselected Features: 18MB
? Select Features and Install: 12MB?6MB
Note: These numbers are more accurate than the numbers shown
on the installation screens.
You also need to plan for a swap file, which can be placed on any
drive. The size of the swap file varies greatly, depending upon
Read Me First 3
how much memory you have in your system and how much
memory your applications use. We recommend a swap-file size of
5MB to 9MB.
If the system cannot extend the swap file when required, the oper-
ation being attempted (for example, an application being loaded)
will fail, and a pop-up message will appear.
Currently, the installation program scans your hard disk and
allows you to install OS/2 only if the target partition is at least
18MB.
If you are planning to install IBM Extended Services for OS/2 or
IBM OS/2 LAN Server V2.0, refer to the estrictions and Installa-
tion Instructions?for these products for more information about
DASD requirements.
Hardware Considerations
XGA Displays
The current version does not have an XGA driver. All XGA dis-
plays will be run in VGA mode.
Floating Point Emulator
Applications that require the use of a math coprocessor might not
run; those that can exploit the math coprocessor might run slower.
This is because the system has a floating-point emulator, which
emulates the math coprocessor when floating-point hardware is
not present. In hardware configurations that have a ?86 B1 step-
ping level,?the system will disable the 80387 hardware and use
the floating-point emulator without notifying the user.
The floating-point emulator will NOT generate denormal
exceptions.
4
Printing from a Serial Port with a PS/2 Model 90 or 95
*
If you need to use the COM port in a PS/2 Model 90 or 95 with
Enhanced set to ON, make sure that the Serial Transmit and Serial
Receive Arbitration Levels shown in the hardware configuration
are set to Dedicated, with different numbers. To do this, you need
to use the Setup/Diagnostics diskette. When both levels of a serial
port are set to Shared, data communication and printing from the
COM port with Enhanced set to ON will not work correctly
For example, when Serial Port is SERIAL 2 in the hardware config-
uration, its corresponding Serial Transmit Arbitration Level should
be DEDICATED 3, and Serial Receive Arbitration Level should be
DEDICATED 4.
Overall System Performance
Because performance work on OS/2 2.0 is not finished, we recom-
mend that you do not use this version for performance
benchmarking or evaluation.
FAT File System Performance
Performance of the FAT file system is better than in earlier ver-
sions.
Performance enhancements that add intelligent read-ahead and
lazy-writing were made to DISKCACHE. In the previous EEP
version, OS/2 had the potential to lose data if bad sectors were
found during lazy-write; this has been corrected.
* Trademark of the IBM Corporation.
Read Me First 5
High Performance File System Performance
The performance work on HPFS is not yet finished. In partitions
smaller than 60MB, performance is about the same as that of the
FAT file system; in larger partitions, it is somewhat faster.
In some configurations, formatting your hard disk for the HPFS
might be slower than formatting the same disk for the FAT file
system.
Scheduler Performance
OS/2 now uses dynamic time-slicing. Try the default first. If per-
formance is not better, go back to your specific setting.
Loader Performance
Application load time is better than in previous versions, but still
not as fast as in Version 1.3. To improve application load times,
add ,128 to the end of the DISKCACHE statement
(DISKCACHE=64,LW,128). This change improves load times for
the FAT file system.
DOS-Session Performance
DOS performance is best in DOS full-screen sessions; DOS window
sessions provide somewhat slower performance. The perform-
ance of some applications can be increased by adjusting:
? IDLE_SENSITIVITY
? EMS_MEMORY_LIMIT and XMS_MEMORY_LIMIT. If your appli-
cation does not need extended or expanded memory, you need
not allocate it.
Workplace Shell Performance
The performance work on the Workplace Shell is not yet finished.
6
Windows Performance
The performance work on Windows is not yet finished.
Printing Performance
The performance on printing has been improved.
Workplace Shell
? We recommend that you use the Shutdown option from the
desktop pop-up menu before powering down your system.
?
In this development version, be careful not to shred the OS/2
System and Startup folders. If these objects are shredded, you
have to reinstall the operating system to recover them.
? Some of the documentation states that you must press mouse
buttons 1 and 2 at the same time to display a pop-up menu.
The correct action is to single-click mouse button 2.
? In this development version, Refresh has been included in the
folder context menus to allow users to update the contents of a
folder. This function enables folders to see objects that
another program may have copied since the folder was
opened. In the final version, folders will update automatically
and Refresh will be removed from the menus.
? Before using the diskette object, make sure that the diskette is
properly inserted in the diskette drive. Failure to do so might
cause unpredictable results.
? Copying files from one drive to another using the Drives folder
is not functioning. Use the OS/2 and DOS command prompts
instead.
? The edit icon option from the Icon page of a Settings notebook
is not yet fully functional.
?
If you use the FIND command from a pop-up menu and specify
?.*?as the item to find, the system will hang; you will have to
restart it.
? The Sort page of the Folder Settings notebook is not func-
tioning, so the system will not sort the contents of a folder.
Read Me First 7
? The Include page of the Folder Settings notebook is not func-
tioning. Redefining the files to include in a folder does not
work.
? The Menu page of the Folder Settings notebook is not func-
tioning, so you cannot modify folder menus.
? The color palette can only be manipulated by using the mouse.
Windows
The current OS/2 version supports VGA only for Windows sessions.
On the 8514/A and XGA, Windows will not run in VGA mode.
Windows printing
The current version supports printing only to the OS/2 default
printer.
The current version contains only a subset of the available
Windows printer drivers. They are automatically installed when
you install and configure the OS/2 printer drivers. The drivers
shipped with this version of OS/2 2.0 are:
? PSCRIPT.DRV
? EPSON24.DRV
? EPSON9.DRV
?
PROPRINT.DRV
? PROPRN24.DRV
? QWIII.DRV
? IBMCOLOR.DRV
? IBMGRX.DRV
? TTY.DRV
If you currently use the Windows program, you can install the
printer drivers using the Windows control panel the same way you
would under Windows. If you use a Windows driver that was not
shipped with the OS/2 operating system, do the following:
1. Start a Windows session by clicking on the Windows Session
icon in the Command Prompts folder (in the OS/2 System
folder).
8
2. Start the Windows Control Panel.
3. Double-click on the printer icon.
4. Select Add Printer.
5. Select Unlisted Printer from the list of printers to install.
6. Select the Install push button.
7. Search for the driver you wish to install.
8. Select OK to exit this panel.
9. Select Configure.
10. Select LPT1.OS2 or LPT2.OS2 to associate the printer driver
with a printer port. Do NOT use LPT1 or LPT2.
11. Select Setup.
12. Select the printer you wish to use.
13. Select OK to exit this panel.
14. Select OK to exit the next panel.
15. Exit to an OS/2 session by double-clicking on the OS/2 icon at
the bottom of the Windows screen.
16. Select the OS/2 printer object.
17. Use create another, copy, or copy from template to create
another print destination.
18. Use open settings to configure the required port (for example,
LPT1) and printer driver (IBMNULL).
19. OS/2 always installs IBMNULL during system installation. If
IBMNULL is not shown in the list of available printer drivers,
use the Install pop-up menu option on an existing printer driver
to get the printer driver install dialog. Insert PM device driver
diskette 1, and press Refresh. Select IBMNULL from the list,
and press Install. Press Cancel and select IBMNULL for the
print destination.
Read Me First 9
Windows Information
? To install Windows applications in the OS/2 operating system,
follow the manufacturer's instructions. If the installation proce-
dure does not work properly, open a DOS session and try the
installation procedure again. If the procedure still does not
work, run the installation command using RUN from the File
menu.
? To run Windows applications, choose one of the following:
?Create a Windows full-screen object and type the name of
the Windows application.
?Create a DOS full-screen object and type WINOS2.COM
and the name of the Windows application in the parameter
field.
?Select RUN in the Windows Program Manager.
?Type WINOS2 followed by your program name in a DOS
session.
You cannot run DOS applications using RUN from the File
menu.
? If a Windows application produces an error indicating that
there is insufficient memory available, increase the DOS
setting, DPMI_MEMORY_LIMIT from the default (3MB) to 4MB
or 5MB. This setting should not be set arbitrarily high since
the OS/2 Swapper will grow by the amount of additional
memory allocated.
? To enable Ctrl+Esc to bring up the Windows task list or
Alt+Esc to switch between your Windows applications only,
change the DOS setting KBD_CTRL_BYPASS.
? If you get FATAL ERROR 401 (or 410) when you try to start a
multiple-application Windows session, the Windows video
drivers were not properly configured. Make sure that the fol-
lowing lines are in the SYSTEM.INI file in the directory
c:\os2\mdos\winos2 (where c: is your OS/2 startup drive).
display.drv=vga.drv
fonts.fon=vgasys.fon
fixedfon.fon=vgafix.fon
oemfonts.fon=vgaoem.fon
10
? If you are using multiple Windows applications, change the
DOS setting, DOS_FCBS to improve performance.
? Dynamic data exchange between Windows applications in sep-
arate DOS sessions, or between Presentation Manager (PM)
and Windows applications, might require switching between
the DOS sessions (using Ctrl+Esc).
? If you set the Windows Clipboard to PUBLIC:
?PrintScreen in the Windows session will not copy data to
the clipboard.
?Any text string, bit map, or metafile that is greater than
48KB will not be transferred to the Public Clipboard.
DOS Applications and Environments
Interrupt 21h Find First Call
Some DOS applications that use the interrupt 21h find first call
might not work properly (for example, TAPCIS). To fix this problem
in this development version, execute FIX_FIND (located in
\OS2\MDOS) in the DOS session before you run the failing applica-
tion. It will not be necessary to correct this problem in future ver-
sions.
UNDELETE Command
Currently, the UNDELETE command works only in OS/2 sessions.
In later versions, UNDELETE also will be supported in DOS ses-
sions.
Background DOS Programs
Some DOS programs need special DOS settings to run properly in
the background. Without these settings, some applications appear
to stop.
The OS/2 operating system has a feature called 﨑OS Settings.?
Its purpose is to provide the highest level of compatibility for indi-
Read Me First 11
vidual DOS applications. DOS settings are defined for each DOS
session and are set with the Settings choice in the pop-up menu.
There are two DOS settings that might help when you run pro-
grams in the background:
? HW_TIMER: Changing this setting from Off to On enables the
application to receive timer interrupts while running in the
background. Some programs need these interrupts (for
example, SuperKey****, or WordPerfect when it is running
macros). Some communications programs also run better
when this setting is On.
? IDLE_SENSITIVITY: Increasing this property to a setting above
the default of 75% will boost the priority of that individual DOS
session.
Double Mouse Pointers
If you run an application in a DOS window session, and two mouse
pointers are displayed, change the DOS setting,
MOUSE_EXCLUSIVE_ACCESS to On.
Generic Hardware Support
Generic hardware support enables OS/2 2.0 to run many programs
that were not possible in earlier versions. Scanners, FAX, 3270,
network, and other specialized hardware can be used in a DOS
session just as they are in DOS.
Novell DOS LAN Requestor
To use the Novell DOS LAN Requestor in a DOS session under
OS/2 2.0, set the DOS settings as follows:
DOS_DEVICE
c:\dxma0mod.sys
c:\dxmc0mod.sys
** WordPerfect is a trademark of WordPerfect Corporation. SuperKey is a trade-
mark of Borland International, Inc.
12
Note that these are the settings for Token Ring.
DOS_VERSION
net4.com,4,0,255
DOS_LASTDRIVE
m
If you have more drives than m, change to the highest drive
letter.
The drive after the one you specified for LASTDRIVE will become
your logon drive.
Novell will use the adapter directly, so you will not be able to use
the network adapter in another session.
Expanded Memory Conflicts
To function, expanded memory service (EMS) needs 64KB of con-
tiguous space above 640KB. Unfortunately it must share this
memory with adapters (network, disk, display, and 3270) that
locate themselves in memory above 640KB. If you have used an
EMS emulator under DOS, you are probably aware of these con-
flicts and know some techniques to fix them. The OS/2 operating
system also provides a technique that simplifies the resolution of
these conflicts.
The DOS setting, MEM_INCLUDE_REGIONS, enables you to disable
the adapter memory for any session and let EMS use it instead.
For example, if you have a 3270 adapter and already have OS/2
Communications Manager support, you will not need to use the
3270 memory in a DOS session. To disable this memory, you will
need to find the address of the 3270 adapter. Use the PS/2 Refer-
ence Diskettes (or an equivalent method for your system). When
the address is known, specify the range in the Include regions
property. Most IBM 3270 adapters will start at CE00 (0xCE000
absolute). The property should be set to:
CE000-CFFFF
This will allow EMS to use this memory if there is enough near this
range.
Read Me First 13
If this is not sufficient because you need access to multiple
adapters from a single DOS session, you will need to rearrange
your memory addresses. This is the same process you follow
under DOS.
VCPI and Other Non-DPMI Extenders
VCPI (Virtual Control Program Interface) and other non-DPMI (DOS
Protect Mode Interface) extenders will not be supported in OS/2
DOS sessions. These extenders are believed to compromise
system integrity in a multitasking environment such as OS/2 2.0.
Disk Writes using Physical Sector Addressing
Hard-disk writes using physical sector addressing are not sup-
ported because they violate system integrity in a multitasking
operating system. (Although most functions of the Norton Utilities **
are supported, the SORT/UNDELETE functions are not. Use the
OS/2 UNDELETE command instead.)
High Memory and Upper Memory Blocks
The second parameter of the DOS= statement specifies whether
applications can use memory above 640KB (upper memory
blocks). The default for this release is DOS=LOW,NOUMB (low
memory blocks). We encourage you to change the DOS settings
DOS_UMB and DOS_HIGHL so that your applications have access
to upper memory blocks and extra memory.
Borland Turbo Assembler
To run the Turbo Assembler ** (TASMX), you must set the DOS
setting, DPMI_API to enabled.
** Norton Utilities is a Trademark of Symantec Corporation. Turbo Assembler is a
trademark of Borland International, Inc.
14
Miscellaneous
32-Bit Programs
For this development version of OS/2 2.0, developers of 32-bit pro-
grams need to relink their programs using the latest version of
LINK386.
Printing to Files
The printer object Output to File option is not functioning properly.
This will be corrected in the final version.
High Performance File System
We are aware of intermittent problems with the high performance
file system on certain hardware configurations. If you experience
these problems, insert the line 﨏ACHE /LAZY:OFF?in your
STARTUP.CMD file. You may notice some performance degrada-
tion as a result of this.
Sticky Pad
When you select Sticky Pad from the Productivity Folder, you will
get the message: SHLERR_MESSAGE_NOT_FOUND.
The Sticky Pad will not work and you will be returned to the Pro-
ductivity folder.
The DOS_VERSION Setting
When you change the DOS setting, DOS_VERSION, you must save
it immediately after entering the value. If you change another DOS
setting before you save the DOS_VERSION value, the value will be
lost.
Read Me First 15
Print Object Pop-Up Menu
The pop-up menu brought up from the title bar icon does not func-
tion properly. Click on the window's background instead.
16
�
V2-WIN.DOC
IBM Internal Use Only
1.0 Microsoft Windows Applications
Editor's Note
This component of the product was being extensively worked at the time of
writing, and no firm information was available. The subject must be thor-
oughly researched and documented prior to publication.
OS/2 V2 provides the capability for Microsoft Windows applications to run under
OS/2 V2. This support allows applications written for Windows 3.0 and previous
versions of Windows to coexist and execute in the same machine under OS/2 V2.
Each Windows application executes as a protected mode process. As such,
Windows applications are subject to the same application protection facilities
provided to other protected mode applications (both OS/2 and MVDM tasks)
under OS/2 V2. Windows applications are protected from other Windows appli-
cations and from DOS and OS/2 applications executing in the system. This is in
contrast to the native Windows 3.0 environment, where protection is limited to
Windows 3.0 applications only.
The execution of Windows applications as protected mode tasks also allows
these applications to take full advantage of the pre-emptive multitasking capabili-
ties of OS/2 V2, with full pre-emptive multitasking between Windows applications,
OS/2 applications and DOS applications. This is again in contrast to the native
Windows 3.0 environment, where pre-emptive multitasking is available only when
Windows 3.0 is running in enhanced mode, thereby impacting performance and
preventing many applications written for previous versions of Windows from exe-
cuting. OS/2 V2 has no such restriction. Windows applications running under
OS/2 V2 will run in a mode equivalent to the real or standard modes of Windows
3.0. The enhanced mode of Windows 3.0 is not required since OS/2 V2 operating
system itself provides equivalent function.
1.1 The Windows Environment
Microsoft Windows 3.0 application support is provided by default during the
installation of OS/2 V2. Should the user select Selective Install at time of installa-
tion and highlight DOS + Windows Environment, then all the files necessary to
provide Windows Application support will be installed in the following subdirecto-
ries:
? \OS2\MDOS\WINOS2
? \OS2\MDOS\WINOS2\SYSTEM
OS/2 V2 CONFIG.SYS will be updated to include these directories in the PATH
statement; MVDM (Multiple Virtual DOS Machine) support is also installed.
Windows REAL Mode requires 640Kb of Conventional memory and several MB of
Expanded memory (EMS). The EMS VDD (Virtual Device Driver) is also required.
Windows STANDARD Mode requires that the following statements be included in
the OS/2 2.0 CONFIG.SYS file:
? DEVICE=C:\OS2\MDOS\VDPMI.SYS (DOS Protect Mode Interface)
+ Copyright IBM Corp. 1991 1-1
IBM Internal Use Only
? DEVICE=C:\OS2\MDOS\VDPX.SYS (DOS Extender Virtual Device Driver).
If these device drivers are not loaded, Windows will execute in REAL Mode.
Windows can use Expanded Memory which conforms to the LIM EMS 4.0 specifi-
cation when running in REAL Mode. This memory is primarily used for storing
background applications. An appropriate Expanded Memory Manager must be
installed. Windows Applications can however use a LIM EMS 3.2 Expanded
Memory manager to store data in memory. In STANDARD Mode, Windows will
use Extended Memory.
Upon completion of the installation process the user will be given the opportunity
to migrate installed Windows Applications to the OS/2 V2 Workplace Shell.
All Windows Applications which are migrated, will have the appropriate DOS and
Windows Settings established, as defined in the Certified Application Database
(shipped as a standard component of OS/2 2.0).
Editor's Note
The Certified Applications Datbase is currently under development. This
aspect must be tested, once available. The procedures involved in updating
this database must be investigated.
1.1.1 The Certified Applications Database (CAD)
The Certified Applications Database provides the vehicle to automatically set the
DOS Property settings for both certified DOS and Windows applications. The user
will be presented with a list of the certified applications found, which can be
migrated. The user may select any or all of these applications. The CAD will be
searched for each of the selected applications. The DOS and/or Windows proper-
ties information found in the database will be used to automatically assign set-
tings to the applications. Windows applications will be placed in a single
Windows Folder. DOS applications are placed in a single DOS Applications
Folder.
Note only the property settings for applications which differ from the default set-
tings will be held in the database.
DOS Settings information for DOS applications will be stored in the OS2.INI file.
Windows applications' settings are stored in the WIN.INI file.
Note
Only the settings for those applications which have been certified via
approved IBM testing channels will be recorded in the Certified Applications
Database (CAD).
The CAD will be a binary database generated from an ASCII database and a pre-
defined tag file. Each field in the ASCII database will start with a descriptive tag
that is associated with a value between 0-225 in the predefined tag file. When the
binary CAD generation tool encounters one of the descriptive tags, it will gen-
erate an entry in the binary CAD with a 0-255 value specified in the predefined
1-2 VMBOOT
IBM Internal Use Only
tag file. To add new or additional DOS properties, a short descriptive tag is
created for the ASCII file and associated with an unused value between 0-255 in
the predefined tag file. A length specification is also provided for the value in the
tag file.
Each field in the binary CAD starts with a predefined tag value of 0-255 that iden-
tifies the field. This tag is followed by a "size" field, which in turn is followed by
the actual value of the field. The maximum number of tags is 256.
Each application in the CAD will have the following minimum information:
? The filename used to start the application
? A next application pointer
? The title of the application.
The filename that starts the application is used to identify the application on the
hard drive. The next application pointer points directly to the next application
entry in the CAD. This provides the ability to jump from one entry to the next
without parsing all of the tags between entries in the CAD. The application title is
displayed to the user if the application is found on the hard drive. The user will
use this information to specify if the application is to be migrated.
The filename extensions held in the CAD will determine what files are searched
for, that is all .EXE, .COM and .BAT files.
1.1.2 Single Application and Multiple Application VDMs
Two Windows environments are supported:
? SAVDMs (Single Application VDMs) which contain a single Windows Applica-
tion. The icon supplied with the Windows Application will be defined in the
SAVDM.
?
MAVDMs (Multiple Application VDMs). This activates the Windows Program
Manager, allowing the user to access a number of Windows Applications.
Each SAVDM will indicate the Windows execution mode based on the file type
specified in the *.EXE header of the Windows Application. REAL Mode will be
indicated for non-Windows 3.0 applications. Auto-Select (Real or Standard mode)
is selected, based on processor type.
The following components of Microsoft Windows 3.0 will be supported and are
available within the OS/2 2.0 kernel:
? Windows Real Mode kernel (WINOS2.COM and KERNEL.EXE)
? Modified Windows Standard Mode kernel (OS2K286.EXE)
? Modified DOS Extender (OS2DOSX.EXE)
? Print Manager (Spool Function)
? Program Manager:
?Permit the starting of multiple Windows Applications in a VDM
?Permit switching between Windows Applications in the VDM
? Help Manager
Microsoft Windows Applications 1-3
IBM Internal Use Only
? Video Device Drivers
? Keyboard, Mouse and Communications Device Drivers
? TaskManager
? Windows User and GDI DLLs
? Printer Device Drivers
? Clipboard support
? Control Panel with functions limited to:
?Printer Install
?Color
?Fonts
?Sound
?Mouse
?International
?Date/Time
?KBD (Keyboard rate).
The Clock program and Recorder Utility (Create/Recall keystroke macros) are
available in Fullscreen Windows - (MAVDM) Multiple Application Virtual DOS
Machine.
Note
1. Microsoft Windows 386 Enhanced Mode is not supported
2. Microsoft Windows Multi-Media extensions are not supported.
The following Microsoft Windows 3.0 components are not included within the
OS/2 kernel, as OS/2 equivalents are provided, or are not required within an
OS/2 environment:
? File Manager
? Systems Editor (SYSEDIT)
? Games
? Write
? Terminal
? Notepad
? Cardfile
? Calendar
? Calculator
? PIF Editor
? Paintbrush
?
Wallpaper bitmaps
1-4 VMBOOT
IBM Internal Use Only
? Setup (Windows' Installation and Configuration changes).
1.2 Defining Windows Applications
Figure 1-1. Program Reference Object's Setting Notebook.
+-----------------------------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------------------------------------+
The Windows application execution environment is defined in the Program Page
of the program reference object's settings notebook. The Windows Application
name is entered as the Path and Filename. This entry will cause DOSQAppType
to be issued to determine the application type. The Program Type in the Mode
Page will be set to Windows Full Screen. A "Windows" page will appear for the
Windows application containing a New Windows Setting. This defines whether
the Windows kernel will execute in REAL, Standard, or Auto-Select mode. REAL
mode is highlighted as the default if the Windows application is NOT a Protect
mode Windows application, otherwise AUTO-SELECT is the default. All DOS set-
tings are selectable for Windows applications via the Windows page, Windows
settings are also included in the same list.
Changes are effective immediately and are saved when the Settings Notebook is
closed or when the system is shut down. The Reset Button resets to the previous
settings.
The Windows application is started by double-clicking on the icon within the
folder. The application executes in the VDM in which it was defined.
Microsoft Windows Applications 1-5
IBM Internal Use Only
Operation
The SAVDM is created for the execution of the Windows application. The
Workplace Shell starts WINOS2.COM as the application to start in the VDM.
The Windows Application to be executed is passed as a parameter to
WINOS2. This process is transparent to the user. If the application is
launched from an OS/2 Command Prompt, the user will notice the VDM being
launched as the DOS prompt is momentarily displayed before the Windows
application is launched.
If WINOS2 is to execute in REAL Mode, the /r option will be inserted into the
parameter list for the VDM creation, based on the WIN Setting. If STANDARD
Mode was highlighted, /s is passed as a parameter to WINOS2. The default is
to pass no Windows options, just the application name.
When the Windows Application is terminated, WINOS2.COM terminates
causing the VDM to be terminated.
Each SAVDM will have an icon on the Desktop, for the application within the
SAVDM. This icon will be the Windows icon for this application. The icon title will
be the text specified in the Program Title field of the New Program dialog.
Editors Note
Check to ensure that the Windows Application icon is used and that the
SAVDM does not display the default DOS icon.
Ctrl-Esc is the key combination used to display the Task List.
Alt-Esc is the key combination used to switch to the next session as defined in
the Workplace Shell.
In the case of MAVDM (Windows Application Group), the Windows Program
Manager is loaded in the MAVDM transparently to the user. Applications are
launched from the Windows Program Manager. Here the Task List will display
the Windows Application currently executing in this VDM.
Ctrl-Esc is used within the VDM to display the Task List.
Alt-Esc is used to switch to the next session defined in the Workplace Shell.
The Workplace Shell icon will represent the Windows VDM, not the application(s)
executing within the VDM.
The user must select Exit Windows in the Windows Programs Manager to termi-
nate the VDM, or close the VDM from the Workplace Shell.
The following applications are already started (iconized) on first entry into the
VDM for both SAVDMs and MAVDMs:
? Modified Windows Clipboard Viewer Program
? DDE Server/Agent Application
1-6 VMBOOT
IBM Internal Use Only
? Recorder (not started in MAVDM)
? Presentation Manager icon
? Task Manager (no icon)
? Windows Program Manager (not visible in a SAVDM)
? Clock (Iconized, MAVDM only)
? Windows Control Panel (not started, MAVDM only).
1.3 Launching Windows Applications in OS/2 2.0
The following methods may be used to start Windows Applications:
1. Select the Application name from within File Manager
2. Enter the Application name at an OS/2 Command line prompt
3. Install the application in a folder, in the Workplace Shell Desktop.
If the application is started from either the OS/2 File Manager or an OS/2
command prompt, an SAVDM will be created. If the Application is started from
an icon, either a SAVDM or a MAVDM will be created, depending on how the
application was defined at installation.
When a MAVDM icon is selected, a Windows VDM will be created with the
Windows Program Manager maximized. The user may then elect to start any
Windows applications within the VDM via the Windows Program Manager. The
user may also define a group of Windows applications which will be activated
when this VDM is started. These applications are specified in the Parameters
field of the of the New Program Dialog. Full path name and parameters should
be specified.
The syntax for the parameters field is:
/R|/S 詛~?|泘 App1 App-parms ?~
?|洺 App2 App-parms
? /R Windows REAL Mode
? /S Windows Standard Mode
? Optional Parameters ? ~
?
! Start the Windows Application Minimized
?
?Start the Windows Application Maximized.
If neither the Exclamation Mark nor the Caret is specified, the Windows Applica-
tion will start Normalized, approximately one third the screen size.
A MAVDM will be created if one of the following are present:
? {} Braces
?
Comma separating the application names
? An Application Name is not passed as a parameter.
Microsoft Windows Applications 1-7
IBM Internal Use Only
1.4 Windows Device Drivers and Environment Settings
A WIN.INI file is built during OS/2 installation. The options for the devices
selected for the OS/2 environment are included in this file.
Should the user migrate from a Windows 3.0 environment, the Windows WIN.INI
will be left unchanged. WINOS2 will look in C:\OS2\MDOS\WINOS2 subdirectory
for the correct WIN.INI file. The initial WIN.INI file in the WINOS2 subdirectory is
created from the Windows WIN.INI.
The following initialization files are created (including the WIN.INI file):
? PROGMAN.INI
? CONTROL.INI
? SYSTEM.INI.
1.4.1 WIN.INI
WIN.INI contains a number of sections which may be customized by the user,
including which applications should be started or run, when Windows is started.
Each Windows Application is recorded in a separate section indicating the drive
and path to execute the application. The supported file extensions for each appli-
cation installed, are recorded in the Extensions section.
1.4.2 PROGMAN.INI
PROGMAN.INI contains the Program Manager settings, the following sections are
included:
? Setting: Describes the settings of the Program Manager, the user's prefer-
ence
? Groups: Specifies the Program Groups that exist in Program Manager.
1.4.3 CONTROL.INI
CONTROL.INI contains the color and desktop settings for the Control Panel. The
following options are available:
?
Current: Specifies the Window color setting
? Color Schemes: Specifies the available color options
? Custom Colors: Specifies up to 16 customization colors
? Patterns: Specifies options for the Desktop pattern.
1.4.4 SYSTEM.INI
SYSTEM.INI contains the global system information used by Windows when it
starts. Changes are not effective until Windows is restarted.
The following sections are included:
? Boot: Lists the drivers and Windows modules. The OS/2 file contains a sepa-
rate Boot section which covers MAVDM and SAVDM default applications:
?GOPM This program returns the user to the Workplace Shell
?Clock The Windows clock program
1-8 VMBOOT
IBM Internal Use Only
?Clipbrd The modified Clipboard program
?DDEAGENT The modified DDE (Dynamic Data Exchange) program
?Printman: MAVDM only, the Printer Manager program
? Boot.description: Lists the names of devices the user can change using
Windows Setup
? Keyboard: Contains information about the keyboard
? NonWindowsApp: This section should not contain any information, non
Windows Applications are started from the OS/2 desktop
? Standard: Contains information required by Windows to run in Standard
Mode
? 386Enh: Contains information used by Windows to operate in 386 Enhanced
Mode. This section is not used as OS/2 provides equivalent function.
The Initialization and Group files are required to restore a corrupted Windows
environment. Backups of these files should be taken prior to making any
changes to this environment.
Note
The Windows 3.0 APIs will access the new WIN.INI file.
The WIN.INI file is updated by Install and OS/2 Print Manager.
The WIN.INI file is updated with the appropriate information for the following
options. Installation will install the Windows Device Driver files in the appropriate
directories.
? Keyboard
? Mouse
? Video
? Printer
? Codepage.
If a device driver (Video, Mouse, Keyboard) is supported in Windows and NOT
supported by OS/2, the Windows version will not be supported.
Install will update the new WIN.INI file to include the printer device driver details
that Windows requires for printers selected under OS/2. Install selects a
Windows printer device driver comparable with an OS/2 printer device driver.
The Windows printer device driver will operate in its default mode. If the printer
device driver needs to be configured in a mode other than the default mode, the
printer should be configured from within the Windows Control Panel.
If there is no equivalent OS/2 printer device driver, the device driver should be
installed and configured via the Windows Control panel.
Microsoft Windows Applications 1-9
IBM Internal Use Only
Note
At the time of writing this facility/function could not be tested
1-10 VMBOOT
IBM Internal Use Only
2.0 Dynamic Data Exchange (DDE)
This chapter describes DDE support between Windows Applications in a full
screen VDM.
DDE is a message protocol for dynamic data exchange between Windows pro-
grams. Data may be shared among applications, the intention being to create an
integrated Windows environment.
The native Windows environment supports the following mechanisms which
applications can use to exchange data:
? Clipboard transfers
? Dynamic link libraries
? Dynamic Data Exchange (DDE).
Note
DDE is the only mechanism that supports passing of Global Memory Handles
between applications.
2.1 Clipboard Transfers
The Clipboard acts as a temporary repository of information. This process
requires the direct involvement of the user to initiate and complete the data
transfer process.
2.2 Dynamic Link Libraries (DLL)
A DLL can be designed to act as repository for data being shared between appli-
cations. The data is stored in the static data area of the DLL's data segment.
2.3 Data Exchange in Windows
Windows is a Message-based Architecture and message passing is used to
transfer information between applications.
Windows messages however contain only two parameters, wParam and lParam
for passing data. The DDE protocol defines how these message parameters will
be used to pass large amounts of data by means of Global atoms and Global
shared memory handles.
A Global atom is a reference to a character string and is used to identify:
? The applications exchanging data
? The nature of the data being exchanged
?
The data items.
+ Copyright IBM Corp. 1991 2-1
IBM Internal Use Only
A Global shared memory handle is a handle to a block of allocated memory.
Global shared memory objects store data items passed between applications,
protocol options and remote execution strings.
2.3.1 DDE Concepts
Client, Server and Conversation:
Two applications participating in dynamic data exchange are engaged in a DDE
Conversation. The application that initiates the conversation is the Client Appli-
cation. The application which responds to the client is the Server Application.
An application may be engaged in several conversations at the same time,
acting as a client in some applications and as a server in others. A DDE conver-
sation takes place between two windows, one for each of the participating appli-
cations. The window may be the main window of the application, a sub-window
associated with the application, or a hidden window. The hidden window is used
to process DDE messages.
DDE identifies the units of data passed between the client and server with a
three-level hierarchy of:
? Item
?
Topic
? Application Name.
Each DDE conversation is uniquely identified by the application name and topic.
The application name is normally the name of the server application. The topic is
a general classification of data, within which multiple data items may be
exchanged during the conversation. The item is the actual information related to
the conversation topic that is exchanged between the applications. Values for the
data item can be passed from the server to the client, or from client to server.
The format of the data item may be any one of the clipboard formats.
2.3.2 Permanent Data Links
Once the DDE conversation has been initiated, the client can establish one or
more permanent data links with a server. A data link is a communication mech-
anism by which the server notifies the client whenever the value of a given data
item changes.
The link is permanent in the sense that the notification process continues until
the data link or DDE conversation is terminated.
The DDE link may be WARM or HOT. In a warm data link, the server notifies the
client that a value of a given data item has changed, but the server does not
actually send the data value to the client until the client requests it. In a hot data
link, the server immediately sends the changed data value to the client.
Applications which support DDE, typically provide a Copy/Paste Link command in
the Edit menu to allow the user to establish a DDE link.
2-2 VMBOOT
IBM Internal Use Only
2.4 OS/2 DDE Support in Fullscreen VDM
In a native Windows 3.0 environment, a Windows Application (Client) will send a
broadcast DDE Initiate message. Windows serially posts a message to every
Windows Application currently running and then awaits a reply. As described
above, the Initiate conversation message contains the DDE topic to which any
Windows application can respond. The Client application continues execution
when all other applications have serviced their message. At this time the Client
application communicates directly with the Server applications, as opposed to
the initial broadcast message.
OS/2 provides two applications to support communications between VDMs,
without altering the Windows code:
1. A resident Windows application referred to as the DDE ServerAgent (SA)
2. A DOS Protect Mode application referred to as the DDEServer
(VDMSRVR.EXE).
2.4.1 ServerAgent
The Windows VDM resident ServerAgent consists of two parts:
? A "ServerAgent" which sends and receives messages outside of the VDM
? One or more "Agents" (each agent is a child window of the ServerAgent),
which act as clones of applications running in other VDMs.
DDE will not be available outside of the VDM, if either the DDEServer or the
VDM's ServerAgent is not executing. The ServerAgent is automatically started
when the Windows VDM is started.
p.The ServerAgent provides a user interface with the following pulldown menus:
1. File Menu:
? Exit: The ServerAgent exits, all subsequent DDE is local to the VDM
? Save As: The contents of the internal trace log buffer is written to the
named file.
2. Options Menu:
? Trace: When selected this option traces and displays all DDE transactions
taking place outside of the VDM. The default is No Trace/Display. Once
enabled, this option remains in effect until explicitly disabled.
? Public DDE: If selected, DDE communicates outside of the confines of the
VDM. If not selected, DDE is local to the VDM. The default is Public DDE.
Should the user choose to exit from the DDE Interchange Agent, an information
message will be displayed indicating that DDE activity will be visible only to the
Windows applications executing in the current VDM, discontinuing DDE commu-
nication between Presentation Manager applications and other Windows applica-
tions.
The ServerAgent is responsible for all routing of DDE messages, including
broadcast messages beyond the confines of the VDM to the DDEServer. The
ServerAgent communicates to the DDEServer via named pipes.
Dynamic Data Exchange (DDE) 2-3
IBM Internal Use Only
Agent applications communicate with Windows applications in their VDM and the
ServerAgent executing in their VDM. Only the ServerAgent uses named pipes.
Agents send requests to the ServerAgent to be forwarded outside of the VDM.
2.4.2 DDEServer
The DDEServer is responsible for routing requests from ServerAgents to the
appropriate VDMs. The DDE process is schematically represented below:
�葺葺葺葺葺葺葺葺葺葺葺葺葙
� Windows Application A �
� SAVDM �
�葺葺葺葺葺?葺葺葺葺葺葺?
�葺葺葺葺莨葺葺葺葺葺葺葙
1. � DDE Initiate Message �
�葺葺葺葺?葺葺葺葺葺葺?
�葺葺葺葺馆葺葺葺葺葺葺葙 �葺葺葺葺葺葺葺葺葙
� DDE ServerAgent App A 谳葺葺 4 葺葺葺?Child Window �
�葺葺葺葺�葺葺葺葺葺�葺? �葺葺葺葺葙 � Agent for App D �
2. �葺馆葺葺葙 �葺葺葺� � �葺葺葺葺�葺葺葺葺�
�葺葺葺莼DDEServer谳葺葺葺葺葺葺葺葺? 3 �
� �葺葺葺�葺� (Named Pipes) � � 5
�葺葺馆葺葺葺葙 �莨葺葺葺葺葺葺?�葺葺莨葺馆葺葺? �
� ServerAgent � � ServerAgent � � ServerAgent � �
� App B � � App C � � App D 谳葺?
�葺葺葺葺葺葺? �葺葺葺葺葺葺葺� �葺葺葺�葺葺葺?
6
�葺葺葺莨葺葺葺葺葙
� Child Window �
� Agent for App A �
�葺葺葺葺葺葺葺葺?
Figure 2-1. DDE Process
1. A DDE Initiate Message is broadcast from Windows Application A.
2. The message is forwarded by the ServerAgent to the DDEServer, which in
turn forwards the message to every Windows Application SeverAgent.
3. ServerAgent for Windows Application D responds affirmatively to the DDE
Initiate message. This response is forwarded back to the ServerAgent for
Application A. This response includes the Windows Application handle and
the VDM handle of the VDM running Windows Application D.
4. The ServerAgent in Windows Application A creates a Child Task which
serves as the Agent for Windows Application D.
5. The Agent forwards the data to Windows Application D.
6. When Windows Application D responds, the ServerAgent D creates a Child
Window which acts as an Agent for Windows Application A. The response is
forwarded by the application to the Agent, which in turn forwards the data to
the ServerAgent for Application D.
7. The ServerAgent for Windows Application D routes the DDE data to the
DDEServer. The DDEServer determines which VDM this "DDE Packet" is des-
tined for and forwards it to the ServerAgent for Windows Application A.
2-4 VMBOOT
IBM Internal Use Only
Note
If two Windows Applications require significant amounts of DDE, these appli-
cations should be executed from within the same MAVDM, in this instance
the ServerAgent and DDEServer applications would not be required,
improving performance and usability.
2.5 OS/2 DDE Environment
Existing DDE support between PM Applications remains essentially unchanged.
DDE support between Windows Applications and Presentation Manager Applica-
tions requires that the DDEServer be linked with the Presentation Manager DDE
APIs, both DDE messages and data formats are translated during the data
exchange between the PM session and any given VDM running a Windows Appli-
cation. This process consists of a Protect Mode DDEServer, a Windows DDE
ServerAgent, as described above, and a PM DDE ServerAgent. The PM DDE
ServerAgent is a mirror to the Windows DDE ServerAgent. The ServerAgent is
responsible for routing all DDE messages beyond the confines of Presentation
Manager to the DDEServer. The ServerAgent communicates with the DDEServer
via named pipes.
The following data formats will be translated between the PM environment and
the Windows environment:
? Bitmaps: Windows DIB to/from OS/2 BITMAPINFO2 and PM BITMAPINFO
to/from Windows DIB format.
? Windows Device Dependent Bitmaps: Pre-Windows 3.0 format to Windows
DIB format to/from PM BITMAPINFO.
? Windows Metafiles: Metafiles are converted to Window DIB format prior to
being translated as above.
? Text: Codepage translation is provided in both directions.
The PM DDE ServerAgent will reside in a Productivity Folder as a Utility. Where
there is a demand to provide DDE support between PM Applications and
Windows Applications, the PM DDE ServerAgent should be placed in a
WorkPlace Startup Folder. The DDE ServerAgent runs ONLY as a minimized
icon. To shutdown global DDE, the PM DDE ServerAgent must be terminated
through the Window List.
Where DDE is only used between PM applications, the DDEServer should be
deactivated to improve performance.
Schematically the DDE process between PM Applications and Windows Applica-
tions may be represented as follows:
Dynamic Data Exchange (DDE) 2-5
IBM Internal Use Only
Figure 2-2. DDE Process PM and Windows.
�葺葺葺葺葺葺葺葺葺葙 �葺葺葺葺葺葺葺葺葺葺葺葺葙
� PM DDE Application� � Windows DDE Application �
�葺葺葺葺�葺葺葺葺葺� �葺葺葺葺葺葺葺葺葺葺葺??
�葺葺葺葺? �葺葺葺葺葺葺葺葺葺葺葺? �
� � DDE Initiate Message � �
� � or � �
� � DDE Conversion � �
� �葺葺葺葺?葺葺葺葺葺葺� �
� �葺葺葺葺葺葺葺葺莨葺葺葺葺葺葺葺? �
� �葺葺葺馆葺葺葺葺? �葺葺葺馆葺葺葺葺? �
�莼 DDE ServerAgent� � DDE ServerAgent谳?
�葺葺葺�葺葺葺葺? �葺葺葺�葺葺葺葺?
�莨葺葙 �莨葺葙
�Agent� �Agent�
�?葺? �?葺?
� �葺葺葺葺葺葺? �
�葺葺葺葺葺莼 Named Pipes谳葺葺葺�
�葺葺?葺葺葺�
�
�
�葺葺馆葺葙
�DDEServer�
�葺莨葺葺葺葺莨葺?
�Data Translation�
�葺葺葺葺葺葺葺葺�
2.6 Object Linking and Embedding (OLE)
Note
As at OS/2 Driver 6.163 OLE is not available.
Check to confirm whether OLE is planned for OS/2 2.0 or a later
release/upgrade
Object Linking and Embedding (OLE) focuses on document formats rather than
an application's ability to exchange data - the DDE approach. OLE defines a
format for compound documents, which contain multiple forms of data. The data
formats are understood and managed by multiple applications. The application
uses various combinations of data to construct a Compound Document.
The concepts used in OLE are best described by contrasting them with the
approach adopted by Clipboard and DDE.
When using the Clipboard, an application obtains data from another application
in a standard format, usually ASCII, a Bitmap or a Metafile. This data exists only
as data, there is no link with the application that originally placed the data in the
Clipboard.
When using DDE, an application also obtains data from another application in a
standard format, ASCII, Bitmap or Metafile. The Client can however establish
and maintain a link with the application that delivered the data. Should the data
change in the Server application, the Client application's data is also updated.
2-6 VMBOOT
IBM Internal Use Only
OLE also enables an application to obtain data from another application; in this
instance the data can be in two formats:
? One format is understood only by the application sending the data
? The Display format (ASCII, Bitmap or Metafile) for the receiving application to
display on the screen.
The significance of this approach may be appreciated by way of an example:
Voice annotation may be attached to a Word Processing application, the Word
Processing application need not have any facility to support or manage voice.
The Word Processor will store the data in two formats - the digitized sound and
a display format (an icon). When the icon is selected in the document, the Voice
application is invoked and the Word Processing application passes the digitized
sound to the Voice application, which then plays the sound.
Dynamic Data Exchange (DDE) 2-7
IBM Internal Use Only
2-8 VMBOOT
IBM Internal Use Only
3.0 OS/2 Clipboard Support
OS/2 V2 provides Clipboard support between Windows applications in the same,
or separate VDMs, as well as support between Windows Applications and OS/2
Applications.
The Clipboard serves as a data-exchange feature acting as a common area to
store data handles through which applications exchange formatted data. The
same data may be represented in a number of different formats as specified by
the application. Note that Clipboard objects may be of any size and format.
Data is formatted in either a predefined or private format, before being copied to
the Clipboard. In most cases the data is copied to pre-allocated global memory
and a function call is used to copy the memory handle to the clipboard.
Windows provides a number of predefined data formats:
TEXT Null-terminated text
OEMTEXT Null-terminated text using an OEM character set
METAFILEPICT Metafile-picture structure
BITMAP Device dependent bitmap
DIB Device independent bitmap
SYLK SYLK Standard data interchange format
DIF DIF standard data interchange format
TIFF TIFF standard data interchange format
The OwnerDraw feature in the Windows Clipboard is only supported within a
MAVDM, as shared memory is required. OwnerDraw is a process whereby a
Windows Application takes control over the appearance of menu items and has
responsibility for managing these menu items.
The native Microsoft Windows 3.0 Clipboard provides support for both Windows
applications and non-Windows applications. Non-Windows applications run in
either fullscreen or "windowed" mode. Windowed mode requires that Windows
run in 386 Enhanced mode, this mode is not supported under OS/2 V2. In REAL
or STANDARD modes, non-Windows applications run in fullscreen mode only.
386 Enhanced Mode is a mode which Windows 3.0 runs in to access the virtual
memory capabilities of the Intel 80386 processor, to use more memory than is
physically available and to provide multitasking capabilities for non-Windows
applications.
OS/2 V2 fully exploits the functions provided by the Intel 80386 processor, hence
there is no need to support this mode under OS/2 V2. Moreover, because DOS
applications may be run in a DOS Window (VDM), full Clipboard support is avail-
able.
Should the user wish to capture the contents of a VDM running in fullscreen
mode, the following approach is adopted:
1. Switch to the PM Screen containing the VDM
+ Copyright IBM Corp. 1991 3-1
IBM Internal Use Only
2. Select the System menu on the VDM icon
3. Select Copy All.
This procedure should copy the VDM's video buffer to the PM Clipboard (ASCII
or PM Bitmap).
Note
Selective Copy is available in window'ed mode
3.1 Windows Clipboard Support
The Windows Clipboard view utility will display the captured data in a number of
formats, either predefined or private. Auto displays the data in the format it had
when placed onto the clipboard.
The Clipboard Viewer program (CLIPBRD.EXE), installed in
C:\OS2\MDOS\WINOS2, is available within each SAVDM and MAVDM by default.
This is a modified version of the original Windows 3.0 Clipboard program.
A Clipboard Server (Global Clipboard) runs as a Protect Mode background
process to service clipboard functions between VDMs. If the Clipboard Server is
not executing, clipboard functions are limited to that single VDM. The global
VDM server is started from the CONFIG.SYS file at system boot:
RUN=C:\OS2\MDOS\WINOS2\VDMSRVR.EXE
Should a user elect to exit from the Windows Clipboard, a warning message will
be displayed advising that exit will terminate public clipboard functions. The
Clipboard functions within each VDM are public by default, unless expressly set
to LOCAL, which restricts Clipboard activity to that Windows session only.
The Windows Clipboard viewer pulldown menus have been enhanced to include
support for an Options Menu, which contains the Public Clipboard option.
Selecting this option causes changes to the Local clipboard to be reflected in the
Public clipboard and vice versa. When deselected the contents of the Public clip-
board and Local clipboard will not affect each other.
The File pulldown menu now supports Import/Export functions; PUBLIC must be
deselected from the Options pulldown menu before Import/Export can be
selected.
Implementation Notes
The Import/Export functions communicate via named pipes to the
\pipe\CLPAgent to the Clipboard program (CLIPBRD.EXE) within each VDM.
Export will copy the current contents of the Local clipboard to the Public clip-
board.
Import will copy the contents of the Public clipboard to the Local clipboard.
3-2 VMBOOT
IBM Internal Use Only
3.2 Using Cut and Paste
The following three scenarios describe the clipboard functions:
1. Cut and Paste from a Windows Application in a VDM to another application
in a separate VDM - PUBLIC is deselected.
2. Cut and Paste between two Windows applications within the same VDM
(MAVDM)
3. Cut and Paste between the OS/2 and Windows environments. Cut and Paste
within the OS/2 environment remains essentially unchanged.
3.2.1 Scenario 1 - Cut/Paste Between Windows VDMs
1. CUT the data into the Local Windows VDM Clipboard.
2. Select EXPORT from the Clipboard pulldown menu. The data is copied into
the External Clipboard.
3. Select the VDM containing the destination Windows application.
4. Select IMPORT from the Clipboard pulldown menu. The data is copied from
the external Clipboard into the local Clipboard of the receiving VDM.
5. Paste the data into the destination Windows application.
3.2.2 Scenario 2 - Cut/Paste Within A MAVDM
1. CUT the data into the Windows VDM Clipboard
2. PASTE the data from the Clipboard into the destination application.
3.2.3 Scenario 3 - Cut/Paste Between OS/2 And Windows
The OS/2 2.0 Clipboard is activated upon loading the Operating System. A new
OS/2 PM utility, CLIPVIEW.EXE located in the OS2\APPS\ directory has been pro-
vided to support the extended clipboard functions. CLIPVIEW.EXE must be
launched in order to view and transfer the contents of the OS/2 2.0 clipboard.
Excluding the File option of the Windows clipboard, the same pulldown menus
are provided. The RENDER option is the same as the DISPLAY option in the
Windows clipboard. RENDER will display the contents of the clipboard in a
number of different formats. Because the contents of the clipboard are stored in
separate areas in memory, it is possible to view both the ASCII (text) and
graphics contents of the clipboard.
Note
An application may or may not clear the entire contents of the clipboard,
prior to copying data to it.
The Global Windows VDM Clipboard (DPMI Clipboard) is visible to the PM Clip-
board. CLIPVIEW.EXE has been enhanced to perform the following two activities:
1. Update the PM Clipboard when changes are made to the Global VDM Clip-
board
2. Update the the Global Windows VDM Clipboard when changes are made to
the PM Clipboard.
OS/2 Clipboard Support 3-3
IBM Internal Use Only
The PM Clipboard server application is registered as "clipboard viewer" to
receive notifications of clipboard updates. This ensures that the following mes-
sages are forwarded to the Clipboard Server, so that when updates are made to
the PM Clipboard, messages are sent to the PM CLIPVIEW.EXE.
? WM_DESTROYCLIPBOARD: Signals that the contents of the clipboard are
being destroyed
? WM_DRAWCLIPBOARD: Signals an application to notify the next application
in the chain of a change to the clipboard
? WM_HSCROLLCLIPBOARD: Requests horizontal scrolling of the clipboard
contents
? WM_PAINTCLIPBOARD: Requests painting of the contents of the clipboard
? WM_RENDERALLFMTS: Notifies the owner of the clipboard that it must
render clipboard data in all possible formats
?
WM-RENDERFMT: Notifies the clipboard owner that it must format the last
data copied to the clipboard
? WM_SIZECLIPBOARD: Notifies the clipboard owner that the clipboard appli-
cation's window size has changed
? WM_VSCROLLCLIPBOARD: Requests vertical scrolling of the clipboard con-
tents.
Note
No changes have been made to the PM APIs to accommodate this design.
Data formats are translated from PM to Windows formats and vice versa, as and
when required. This translation is performed when data is placed in the Global
Clipboard. The following data formats will be translated between PM and
Windows:
?
Bitmaps: The Windows DIB to/from OS/2 BITMAPINFO
? Device Dependent Bitmaps: This is a pre-Windows 3.0 format to/from OS/2
BITMAPINFO
? Windows Metafiles: Metafiles are first converted to WINDOWS DIB format by
the Windows clipboard viewer, before being forwarded to the Global Clip-
board
? Text: ASCII with codepage translation will be translated in both directions.
Schematically the Clipboard process may be represented as follows:
3-4 VMBOOT
IBM Internal Use Only
Figure 3-1. .
�葺葺葺葺葺葺葺葺葺葺? �葺葺葺葺葺葺葺? �葺葺葺葺葙
�SAVDM Windows App 1.� �SAVDM - App 2.谳葺莼 Windows �
�葺葺葺?葺葺葺葺葺葺� �葺葺葺葺葺葺葺� �Clipboard�
� �葺?葺葺?
�葺葺葺莨葺葺葺葺葙 2. �
1. �Windows Clipboard� �
�葺葺葺?葺葺葺葺? �
�葺葺葺葺葺葺葺葺葙 �
(Named Pipes) � �
�葺葺葺葺莨葺葺葺葺葺葙 �
�DPMI Global Clipboard谳葺葺葺葺葺葺�
� Data Translation � (Named Pipes)
�葺葺葺葺?葺葺葺葺葺?
�葺葺葺葺葙 3. �
� OS/2 谳葺葺葺葺葺葺葺�
�Clipboard� (Named Pipes)
� Server �
�葺葺�葺葺�
� �葺葺葺葺葙 �葺葺葺葺葺葺葙
� � OS/2 谳葺葺葺?OS/2 PM �
�葺葺葺葺莼Clipboard� �Applications �
�葺葺�葺葺� �葺葺葺葺葺葺?
� �葺葺葺葺葺葺葙
�葺葺葺葺葺葺籚DM Window'ed�
�Applications �
�葺葺葺葺葺葺?
1. A Windows application (App.1) copies data to the Windows Clipboard.
2. The contents of the Clipboard are available to Windows App.2 via the Global
Clipoard (Clipboard Server).
3. The OS/2 Clipboard Server is registered as a Windows "Clipboard Viewer".
Data is translated into OS/2 formats via the DPMI Global Clipboard and vice
versa as required.
OS/2 Clipboard Support 3-5
IBM Internal Use Only
Figure Definitions
id File Page References
FIGDEF 3731SU
1-1
Table Definitions
id File Page References
TDEF 3731SU
1-1
Figures
id File Page References
3731WI2 3731WIN
3731DD1 1-5 1-1 3731DDE
2-4 2-1
3731DD2 3731DDE
2-6 2-2
3731CL1 3731CLIP
3-5 3-1
Headings
id File Page References
WIN 3731WIN
1-1 1.0, Microsoft Windows Applications
Processing Options
Runtime values:
Document fileid V2-WIN SCRIPT
Document type USERDOC
Document style IBMXAGD
Profile EDFPRF20 Service Level 0018
SCRIPT/VS Release 3.2.1
Date 91.10.15
Time 11:58:22
Device 3820A
Number of Passes 2
Index YES
SYSVAR G INLINE
SYSVAR X YES
Formatting values used:
Annotation NO
Cross reference listing YES
Cross reference head prefix only NO Dialog LABEL
Duplex YES
DVCF conditions file (none)
DVCF value 1 (none)
DVCF value 2 (none)
DVCF value 3 (none)
DVCF value 4 (none)
DVCF value 5 (none)
DVCF value 6 (none)
DVCF value 7 (none)
DVCF value 8 (none)
DVCF value 9 (none)
Explode NO
Figure list on new page YES
Figure/table number separation YES Folio-by-chapter YES
Head 0 body text Part
IBM Internal Use Only
Head 1 body text Chapter
Hyphenation YES
Justification YES
Language ENGL
Layout OFF
Leader dots YES
Master index (none)
Partial TOC (maximum level) 4
Partial TOC (new page after) INLINE
Print example id's NO
Print cross reference page numbers YES
Process value (none)
Punctuation move characters .,
Read cross-reference file (none)
Running heading/footing rule NONE Show index entries NO
Table of Contents (maximum level) 3
Table list on new page YES
Title page (draft) alignment RIGHT
Write cross-reference file (none)
Imbed Trace
Page 0 3731WIN Page 0 3731SU
Page 0 3731VARS
Page 1-10 3731DDE
Page 2-7 3731CLIP
Page 3-4 3731CL1
�
VMBOOT.DOC
IBM Internal Use Only
1.0 Virtual Machine Boot
IBM Internal Use Only
Draft extract from ITSC Red Book OS/2 Version 2 GG24-3731. Subject to
revision
1.1 VMB Overview
An important goal of OS/2 V2 is the ability to run past, current, and future PC
DOS programs; indeed most DOS applications available today run unchanged in
the MVDM DOS Emulation environment.
However, it should be remembered that the 﨑OS?which runs in this case is
highly optimized for (and specific to) an OS/2 V2 virtual 8086 machine. Because
of this, there are subtle internal differences between DOS Emulation and real
DOS. Unfortunately some DOS programs may be inherently bound to a specific
DOS version, relying on internal DOS structures or features not present in MVDM
DOS Emulation, such as internal DOS tables, LAN redirector hooks, or even
absolute routine addresses or undocumented features.
Another restriction of MVDM DOS Emulation is that only DOS character device
drivers can be loaded. The user may own a block device (often a special disk or
tape drive) for which no OS/2 driver is available.
Virtual Machine Boot allows the user to boot ff-the-shelf?DOS 3.x, 4.0, or 5.0 in
a VDM session, including DOS block device drivers. This gives the user the
greatest possible compatibility with PC DOS.
Another benefit of Virtual Machine Boot is the ability to run DOS of a different
National Language to that of OS/2 V2. This may be useful in a multilingual or
testing environment.
1.2 Virtual Machine Boot Environment
The 80386 processor and VDM component of OS/2 V2 together emulate a 8086
processor, keyboard, display, BIOS and other supporting hardware - a complete
virtual Personal Computer. So it shouldn't really be too surprising that eal?
DOS can run in a Virtual DOS Machine session. Control is passed to the boot
record (the first sector) of the DOS system diskette, which in turn loads and ini-
tializes the rest of the DOS kernel, just as it does when booting on a real PC.
Indeed the VDM environment is so like a real PC system that Virtual Machine
Boot can actually support any 8086 kernel, such as Digital Research DR-DOS and
1
CP/M, Microsoft MS-DOS, or even a PS/2 Reference Diskette . However, since
the purpose of Virtual Machine Boot is to run PC DOS applications, formal IBM
support is announced for IBM DOS 3.x, 4.0, and 5.0 only.
1 Do not attempt to run diagnostics or change the configuration from a VDM; the results are unpredictable.
+ Copyright IBM Corp. 1991 1-1
IBM Internal Use Only
Multiple DOS VDM kernels may be booted and operated concurrently. Each runs
in its own virtual 8086 session; access to hardware and other system resources
is managed by the underlying OS/2 V2 operating system.
1.3 Using Virtual Machine Boot
The booted DOS operating system can be:
1. An actual DOS system diskette
2. An image of a DOS system diskette saved to fixed disk
3. A DOS partition on fixed disk.
A Virtual Machine Boot session is created as a normal Program icon on the
OS/2 desktop. Here is an sample Program notebook page:
+-----------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------+
Figure 1-1. VMB Program parameters
Program title A suitable description
Path and filename * (actually ignored, but must be valid)
Optional Parameters (blank - ignored)
Working directory (blank - ignored)
The Session type may be DOS Fullscreen or DOS Window as desired.
1.3.1 DOS Startup drive
The difference from a normal DOS item is that the DOS Settings value 﨩ther:
DOS startup drive?is set. This contains the location of the DOS kernel to be
booted.
1-2 VMBOOT
IBM Internal Use Only
+---------------------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+---------------------------------------------------+
Figure 1-2. DOS Startup drive
Example values for DOS startup drive are:
Startup setting Meaning
a: Boot the diskette in drive A:
c: bootimgdos33.vmb \ \ Boot the specified DOS image file
c: Boot the primary partition of the C: drive
Note:
? You cannot specify a second diskette drive (B:) or fixed disk (D:) as the
startup drive.
? To boot DOS from the C: partition, you must have Boot Manager installed,
and OS/2 V2 must reside in an extended partition on the first fixed disk, or
on another fixed disk. See 1.7, 﨎ooting a DOS partition?on page 1-9.
1.3.2 Virtual Machine Boot and 5?inch drives
You cannot specify 﨎:?or an external diskette drive as the startup drive. There
may be situations where you wish to boot a 5?inch diskette; often the B: drive
on PS/2 systems. One way to do this is by creating an image of the diskette,
then booting this image. (See 1.4, MDISK?on page 1-4.)
If a 5?inch diskette must be booted directly for some reason, this is possible if
drive remapping is supported by the system (such as a PS/2 Model 57, 90 or 95).
Normally A: is Drive 0 (3?inch), and B: is Drive 1 (5?inch, if fitted). To change
this, run et Startup Sequence?from the Reference Diskette, and ensure Drive
1 appears before Drive 0. Then the 5?inch drive will become the A: drive.
Some 5?inch drives (such as the IBM External 1.2MB drive and associated
adapter) require a device-driver, and are accessed as D: or higher. They cannot
be specified as a startup drive, nor can they be readdressed as A:, but can be
the source drive when creating a bootable image file.
Virtual Machine Boot 1-3
IBM Internal Use Only
1.3.3 Other DOS Settings
DOS Settings which control the VDM hardware environment are applicable to the
Virtual Machine Boot session and operate in the same way as for a DOS Emu-
lation window or fullscreen session. Those which modify the virtual DOS environ-
ment are ignored; these are instead determined by the CONFIG.SYS of the
booted DOS kernel. Ignored settings include:
? BREAK
?
DOS Device drivers
? DOS owns UMBs
? DOS SHELL
? DOS High / Low
? LASTDRIVE
? Simulated DOS version
The FCB limit is the lesser of either the booted DOS, or OS/2 V2 CONFIG.SYS
value. The Virtual Machine Boot session will by default have 640 KB of real
memory, mouse support, 2 MB Expanded (EMS) memory, 3 MB DPMI, and 2 MB
XMS memory.
In other respects the VMB session is no different to any other VIO window. It
may be minimized, maximized and switched between windowed and fullscreen
mode, and is subject to the same graphics limitations when windowed. The
session cannot be ended by typing exit at its command prompt. The session can
only be closed from its system icon or the Window List.
1.4 VMDISK
As already described, it is possible to boot from a diskette image which itself
resides on fixed disk. This image is created using the VMDISK utility supplied
with OS/2 V2. The syntax of the VMDISK command is:
vmdisk <source drive> <image filename>
For example:
vmdisk a: c:\bootimg\dos33.vmb
The image file is a complete binary ump?of the diskette, consisting of a short
header record followed by the diskette's boot sector, FAT(s), and all data clus-
ters. Its filesize corresponds to the source diskette capacity regardless of the
amount of space actually used on the source diskette. No compression of the
image is performed. The diskette must be of a normal DOS format (FAT, 512 byte
sectors). It is not possible to create, then boot, an image of a copy-protected
diskette which has a non-DOS format. It may be possible to boot such a diskette
directly in a VDM.
VMDISK can run under either DOS or OS/2, and supports all 3?inch (720KB,
1.44MB and 2.88MB) and 5?inch (360KB and 1.2MB) source diskette formats.
1-4 VMBOOT
IBM Internal Use Only
1.5 Drive letter allocation and access
This is one of the more complex area of Virtual Machine Boot. The following pos-
sible areas of confusion may arise for the user:
? If DOS is booted from an image file, it sees this image file as its A: drive.
This prevents access to the real A: diskette drive. Attempts to the write to the
apparent A: drive will fail.
? A DOS VDM cannot see an HPFS partition on the fixed disk.
? A DOS 3.x VDM cannot see a large (>32MB) FAT partition on the fixed disk,
or FAT partitions beyond HPFS.
?
Even if the booted DOS can otherwise see the fixed disk partition, it is only
given read access. Attempts to write will fail with simulated errors such as
. The 礼eneral failure writing drive C:? user might mistake this for genuine
hardware fault.
? If the booted DOS loads a block device-driver, the allocated drive letter may
be the same as that of a different device outside this VDM.
The results could be somewhat disorienting for the user. To help resolve these
issues, two utilities FSFILTER and FSACCESS are provided with OS/2 V2.
1.5.1 FSFILTER
FSFILTER.SYS is a device driver which manages DOS VDM access to OS/2 disks.
FSFILTER.SYS should be copied from the OS2MDOS directory to the DOS \ \
diskette, and the following statement added to the DOS CONFIG.SYS:
device=a:fsfilter.sys
This gives PC DOS full access to all OS/2 partitions - whatever the filesystem
type or partition size.
This is an important and somewhat surprising point. For example, DOS 3.3 (in a
VDM) has no problem accessing a 300MB HPFS partition, once FSFILTER is
loaded. I/O calls within the DOS virtual machine are passed transparently to
OS/2 V2. DOS itself is unaware of the underlying filesystem. DOS can read, write
and modify files on the fixed disk, and for most configurations the drive letter
mapping within the VMB session will match those of OS/2 V2.
Note
FSFILTER.SYS is loaded via CONFIG.SYS of the booted DOS, not the OS/2 V2
CONFIG.SYS. It should be preceed any statements which load block device=
device drivers.
The FSFILTER device driver occupies approximately 11KB of memory. It can be
loaded high (evicehigh=fsfilter.sys? under DOS 5.0.
Some operating systems may be confused by FSFILTER's actions during their
boot processing. For example the setting of the current drive or COMSPEC may
be invalid, or AUTOEXEC.BAT may not run. This has been noted with DR-DOS
and PC DOS 3.3 (but not 4.0 or 5.0). To avoid this problem specify the path to
COMMAND.COM in the SHELL= statement of CONFIG.SYS (as well as the
Virtual Machine Boot 1-5
IBM Internal Use Only
command processor itself). For example, if you cave copied DOS files to C: DOS,
\
the CONFIG.SYS of a diskette intended for VMB should contain a statement:
shell=c:\dos\command.com c:\dos /p
The first parameter specifies the comand procesor to load. The second param-
eter specifies the reload path (ie the COMSPEC path). This is preferable to a et
comspec= ...?line in AUTOEXEC.BAT.
1.5.1.1 FSFILTER limitations
Even when FSFILTER is loaded, the following restrictions still apply:
? A DOS VMB cannot see HPFS files or directories which have:
?long filenames (9 or more characters)
?invalid FAT characters (eg plus, comma, blank).
?multiple dot separators
? HPFS filenames containing lowercase letters are folded to uppercase.
? PC DOS commands which require low-level disk access will fail. These
include:
?CHKDSK
?SYS
?UNDELETE
?FORMAT
?UNFORMAT
?MIRROR
In such cases OS/2 V2 will simulate a disk error condition. DOS may inter-
pret this as a hardware fault, or report that the command is not supported on
a Network or Assigned drive.
1.5.2 FSACCESS
FSACCESS.EXE is a utility supplied with OS/2 V2 but intended to run in a Virtual
Machine Boot session. It cooperates with FSFILTER to manage drive letters
within the VMB session. This serves three purposes:
1. Drives may be registered for filtering.
2. The drive letter for a device can be changed, giving consistency across ses-
sions.
3. Letters can be removed in order to hide the OS/2 device from the VMB
session.
The syntax of the FSACCESS command is:
FSACCESS 葺葺葺葺葺葺�葺葺葺葺葺葺葺葺葺葺葺葺?葺葺?葺 .
谳�葺??DOSletter 葺葺葺? �
� � ! � �
谳葺葺?DOSletter - DOSletter 葺?
� �
�葺葺葺 DOSletter = OS2drive 葺�
FSACCESS lists the current drive mapping. For example:
1-6 VMBOOT
IBM Internal Use Only
Local C: is mapped to OS/2 C:
Local D: is mapped to OS/2 D:
Local E: is mapped to OS/2 K:
FSACCESS F: registers DOS letter F: for filtering. References to F: will be
sent to OS/2 V2.
FSACCESS !F: deregisters DOS letter F: from filtering.
FSACCESS F:-H: registers DOS letters F: through H: for filtering.
FSACCESS M:=C: registers DOS letter M: and routes requests to OS/2 drive
C:
Parameters can be combined on a single command line, and the colon is
optional.
1.5.3 Practical Considerations
? When booting from an image file, you will probably wish to issue the
command ? fsaccess a: ?in order to access the A: diskette drive.
?This will remove access to the image file, so the booted DOS will be
unable to reload its COMMAND.COM when necessary. You may wish to
copy all the DOS files to a subdirectory on fixed disk, ensuring the PATH
and COMSPEC point there.
An alternative is to access the diskette drive via a different letter. For
example, you can issue the command ? ,?then use G: to fsaccess g=a
access the real A: drive. The image file remains as A:, avoiding PATH
and COMSPEC problems.
?
FSACCESS error messages are contained in the OS/2 file OSO001.MSG,
which is in the OS2SYSTEM subdirectory. \ \ You should ensure that this file
is accessible to the booted DOS via its APPEND search path, otherwise an
FSACCESS error will only report that its message file cannot be found.
? Each block device driver loaded in DOS CONFIG.SYS is allocated the next
free OS/2 letter excluding LAN drives. This can result in a drive letter clash.
An example may illustrate the point. OS/2 drives are:
A: Diskette drive 0
B: Diskette drive 1
C: Fixed disk
D: External Diskette drive
E: Remote LAN drive on a Server
FSFILTER will ensure that a booted DOS sees these drives by the same
letter. The booted DOS has the same access to the external diskette drive
and LAN resources as does OS/2 itself. This is true whether the VMB
session is started before or after user Logon to the network, when remote
drive letters are assigned.
However, a VMB block device driver will also initialize as E:, so LAN drive
access is lost. To remedy this, issue an command. The LAN saccess f=e?
drive is now accessible as F: within the DOS session.
? If a Virtual Machine Boot session hangs for any reason, you can close it from
its system icon or the Window List. Remember that CTRL-ALT-DEL will
reboot OS/2, not the foreground virtual machine session.
Virtual Machine Boot 1-7
IBM Internal Use Only
Hint
Always give disk volumes a meaningful name - either when formatting or
later using the LABEL command. The name will remain constant and help
you identify where you are, even if the assigned drive letter is different some-
times.
1.6 XMS, EMS and MOUSE Support
The booted DOS receives XMS (HIMEM), EMS, DPMI and mouse support services
from its VDM environment (assuming the Virtual DOS Machine has default DOS
Settings). It should not load its own HIMEM, EMS or mouse drivers - indeed they
may cause errors in the VDM.
DOS programs call these services via appropriate API register parameters and a
designated Interrupt:
Mouse INT 33h
XMS INT 2Fh (multiplex)
EMS INT 67h
OS/2 V2 traps these interrupts from the virtual machine and handles the request
accordingly.
This may present a problem for certain programs which can use such services,
but first test for their presence by issuing an OPEN to the associated device-
driver, or check that a valid interrupt handler is pointed to by the Interrupt Vector
Table. When a VMB session is started, these device driver names are not
present, and the interrupt vectors point to null handlers. The application will
therefore assume that these services are not useable.
To resolve this, OS/2 V2 provides three alternative tub?drivers:
? MOUSE.COM
?
HIMEM.SYS
? EMM386.SYS
These stub drivers are very small (and use minimal memory when loaded) but
satisfy programs which depend on drivers with such names being present. They
also set handler addresses in the Interrupt Vector Table.
The user must load these OS/2 files rather than any similarly named files which
may be shipped with DOS or applications, such as:
DOS 4.0 XMAEM.SYS, XMA2EMS.SYS
DOS 5.0 HIMEM.SYS, EMM386.EXE, MOUSE.COM
Other MOUSE.SYS
There are two ways to achieve this. Assuming OS/2 V2 is installed on drive C:
Method 1 Copy the above OS/2 files from C: OS2MDOS to the DOS diskette, \ \
and edit CONFIG.SYS and AUTOEXEC.BAT accordingly to load these
files from the A: drive. VMDISK may then be run to create a bootable
image if desired.
1-8 VMBOOT
IBM Internal Use Only
device=a:fsfilter.sys
device=a:himem.sys
device=a:emm386.sys
Method 2 Edit CONFIG.SYS and AUTOEXEC.BAT to load these files directly from
C:OS2 \ \ MDOS. (FSFILTER must be loaded first if the OS/2 drive would
otherwise be inaccessible to the booted DOS).
device=a:fsfilter.sys
device=c:\os2\mdos\himem.sys
device=c:\os2\mdos\emm386.sys
The first method should be used if you wish to load FSFILTER high using DOS
5.0:
device=a:himem.sys
device=a:emm386.sys
devicehigh=a:fsfilter.sys
The second method has one notable advantage; if and when Corrective Service
is applied to the OS/2 V2 system, and HIMEM, EMM386 or MOUSE are updated,
you won't need to update your DOS diskettes and recreate image files. FSFILTER
itself will have to be updated manually (unless the OS/2 V2 partition is directly
accessible to your DOS and you load FSFILTER from here too).
Note: EMS memory size and frame location are determined by DOS Settings,
not parameters on the EMS386.SYS statement.
1.7 Booting a DOS partition
If you anticipate using Virtual Machine Boot regularly, the most convenient
method may be to do so from a DOS partition on the fixed disk, rather than via
diskettes or diskette images. A partition boot proceeds more quickly and offers
the user a more amiliar?working environment. Also, it is easier to apply DOS
Corrective Service to a disk partition than to diskettes or images.
The configuration requirements are:
1. Boot Manager must be installed
2. DOS must be installed on a primary partition on the first fixed disk
3. OS/2 V2 must be installed on an extended partition on the first fixed disk, or
on another fixed disk.
This will require repartitioning on single drive systems if the disk initially con-
taining DOS alone, or earlier versions of OS/2.
Note: This is not the same as a single partition with the Dual Boot feature.
To boot the DOS partition in a VMB session, enter the DOS Settings Startup
Drive parameter as 﨏:?
Virtual Machine Boot 1-9
IBM Internal Use Only
1.7.1 Configuration files
This particular setup presents one significant problem. The DOS partition is itself
bootable directly via Boot Manager, should the user so choose, and there may a
requirement to boot this DOS partition directly on occasions. The problem is: As
there is only one CONFIG.SYS and one AUTOEXEC.BAT in the C: root directory,
which drivers should be specified - DOS or OS/2 stub drivers?
If the partition is booted via VMB the DOS drivers are inappropriate.
If the partition is booted directly via Boot Manager the OS/2 stub drivers are
inappropriate.
It might appear that the user would have to maintain multiple configuration files
and rename or copy them according to the next desired boot type. This is clearly
rather unsatisfactory. Fortunately there is a solution which avoids this. The key is
to specify both sets of drivers in CONFIG.SYS and AUTOEXEC.BAT.
The following example assumes:
? DOS 5.0 is installed on the C: Primary partition
? OS/2 V2 is installed on the D: Extended partition
CONFIG.SYS on the C: drive contains:
device=c:\fsfilter.sys
device=c:\dos\setver.exe
device=c:\dos\himem.sys
device=c:\dos\emm386.exe noems
device=d:\os2\mdos\himem.sys
device=d:\os2\mdos\emm386.sys
dos=high,umb
... etc ...
When this file is processed under an OS/2 VMB, the DOS HIMEM load fails as it
sees no available Extended memory. EMM386.EXE cannot load as it sees protect-
mode software already running. Then, the OS/2 HIMEM and EMM386 stubs load
as normal.
When this file is processed as part of a native DOS boot, the DOS HIMEM and
EMM386 load as normal, but the OS/2 stubs realize they are not running under
OS/2 and do nothing.
A similar technique works for mouse support in AUTOEXEC.BAT:
@echo off
prompt 減済
set path=c:\dos
lh d:\os2\mdos\mouse
lh c:\dos\mouse
... etc ...
Note that here the OS/2 driver is listed first. When booting DOS native, the OS/2
mouse stub will realize this, and not load. Then the DOS mouse driver loads as
normal.
1-10 VMBOOT
IBM Internal Use Only
When this file is processed under OS/2 VMB, the OS/2 stub loads first. Then, the
DOS mouse driver sees that a mouse driver is already present, so does not
install itself.
Note: Unfortunately this technique cannot be taken too far. For example, you
may need to load IBM LAN Support Program drivers for the Token Ring adapter
(DXMxxMOD.SYS) files in your DOS CONFIG.SYS. If you already have sessions
using the Token Ring adapter (either OS/2 Extended Services or previously
started DOS communications) and then boot the DOS partition, its LAN device
drivers attempt to reinitialize the adapter. This will corrupt existing Token Ring
sessions.
1.8 Virtual Machine Boot Limitations
Virtual Machine Boot does not support:
? VCPI and other non-DPMI DOS extenders
? I/O to disk which bypasses the file system
? Feature adapter sharing without a virtual device driver
? Real-time or timing critical DOS applications
?
Some copy-protection schemes.
1.9 Available Memory
Table 1-1 shows the amount of available base memory for MVDM DOS Emu-
lation, DOS in a VMB session, and native DOS.
Table 1-1. Free Base Memory
Setting VDM DOS Emu- DOS 5.0DOS 4.0 DOS 3.3
lation
DOS low 610 KB 566 KB 588 KB 545 KB
DOS high 633 KB 612 KB - -
With mode728 KB 707 KB 653 KB 670 KB
restriction
(CGA)
Native DOS - 564 KB (low) 545 KB 562 KB
614 KB (high)
Note: Each configuration has HIMEM, EMS and Mouse drivers loaded. Values are approximate.
1.10 Customizing DOS
There is little point in loading the following in a booted DOS:
? Disk cache
? Print spooler
? RAM disk
These are better left to &OS2V2..
Do not configure EMS or XMS if the DOS session doesn't use them, as this can
impact the performance of the rest of the system.
Virtual Machine Boot 1-11
IBM Internal Use Only
1.11 Expanded Memory (EMS) and Upper Memory (UMB)
The following section applies to both VDM DOS Emulation and DOS Virtual
Machine Boot.
Expanded Memory Specification (EMS) is discussed in detail in -- Heading
'3731EMS' unknown --. One requirement of EMS is a page frame in real memory
between 640KB and 1MB (hex addresses X A0000 to X FFFFF). Since IBM ' ' '
'
systems reserve addresses X A0000 to X BFFFF for video, and X E0000 to ' ' ' '
' '
X FFFFF ' ' for BIOS, the EMS Page Frame is normally restricted to addresses
between X C0000 and X E0000 ' ' ' ' . This area can also be used for Upper Memory
Blocks, where DOS device drivers and resident programs can be loaded. This
frees up valuable space below 640KB for conventional DOS programs.
Unfortunately, memory between X C0000 and X E0000 is also needed for ' ' ' '
Option Adapter ROM and RAM. Indeed it can be difficult or even impossible to
configure EMS on a system which has several intelligent adapters installed.
There is really no solution to this problem (sometimes known as AM Cram?
under DOS. However OS/2 V2 provides an elegant alternative.
Normally a VDM inherits a memory map which mirrors the actual system hard-
ware configuration; adapter ROM and RAM addreses set by the PS/2 Reference
Diskette (or adapter switches on non Micro Channel systems) are mapped into
the VDM address space and are not available for EMS or UMBs.
But since the VDM occupies virtual memory this can easily be changed. The
DOS Settings value Other: Include Regions parameter releases adapter
addresses for use as EMS or UMBs. In most cases this can be set to the com-
plete X C0000-X DFFFF range. ' ' ' '
If a VDM uses an adapter directly (usually via DOS device drivers), any adapter
ROM or RAM address must not be specified in Include Regions. Addresses of
adapters used indirectly by the VDM (through OS/2 V2) may be included. For
example, the full X C0000 to X DFFFF ' ' ' ' range may be included on a
SCSI-based
PS/2, even though the SCSI adapter ROM may occupy X D8000 to X DFFFF. '
' ' '
The DOS VDM does not directly access the SCSI adapter so doesn't need SCSI
ROM mapped into its address space. It can still access files on SCSI disks via
the OS/2 V2 filesystem.
Note (** this may change **)
The Include Regions parameter should be entered as shown above, using
5-digit hex addresses (not 4-digit segment addresses, as is often the case).
Also, note that the range is inclusive - you must specify the second address
as (for example) X DFFFF, not X E0000 ' ' ' ' . The parameter is not
validity-
checked when entered. If an invalid parameter is saved, the default (no
include region) is used when the VDM is initialised; no error message is gen-
erated.
In summary, a typical DOS VDM may have a 64KB EMS page frame and 64KB of
UMBs (or 128KB of UMBs) regardless of the hardware adapters installed. Such a
configuration is not possible under PC DOS.
1-12 VMBOOT
IBM Internal Use Only
2.0 Index
A M
Adapter memory 1-12 MOUSE.COM. 1-8
B O
Block device driver 1-7 OSO001.MSG 1-7
Block device drivers 1-1
Boot Manager 1-9
P
PC DOS 1-1
C
COMSPEC 1-6
S
Settings (DOS) 1-4
D Stub drivers 1-8
DOS 1-1
DOS Image 1-4
U
DOS Settings 1-4 UMB 1-12
DOS Startup drive 1-2
Upper Memory 1-12
E
V
EMM386.SYS 1-8 VCPI 1-11
EMS 1-12
EMS. 1-8 Virtual Machine Boot 1-1
VMDISK 1-4
Expanded Memory 1-12
F X
XMS 1-8
FAT 1-5
FCB 1-4
FSACCESS 1-6 Numerics
FSFILTER 1-5 5?inch disks 1-3
H
HIMEM.SYS. 1-8
HPFS 1-5
I
IBM DOS 1-1
Include Regions 1-12
L
LAN 1-1
large partitions 1-5
+ Copyright IBM Corp. 1991 2-1
IBM Internal Use Only
Figure Definitions
id File Page References
FIGDEF 3731SU
1-1
Table Definitions
id File Page References
TDEF 3731SU
1-1
Headings
id File Page References
VMB 3731VMB
VMDISK 1-1 1.0, Virtual Machine Boot 3731VMB
1-4 1.4, VMDISK
1-3
BOOTPRT 3731VMB
1-9 1.7, Booting a DOS partition
1-3
3731EMS ?
? ?
1-12
Footnotes
id File Page References
REFDISK 3731VMB
1-1 1
1-1
Tables
id File Page References
FREEMEM 3731VMB
1-11 1-1
1-11
Processing Options
Runtime values:
Document fileid VMBOOT SCRIPT
Document type USERDOC
Document style IBMXAGD Profile EDFPRF20
Service Level 0018
SCRIPT/VS Release 3.2.1
Date 91.10.15
Time 10:42:52
Device 3820A
Number of Passes 2
Index YES
SYSVAR G INLINE
SYSVAR X YES
Formatting values used:
Annotation NO
Cross reference listing YES Cross reference head prefix only NO
Dialog LABEL
Duplex YES
IBM Internal Use Only
DVCF conditions file (none)
DVCF value 1 (none)
DVCF value 2 (none)
DVCF value 3 (none)
DVCF value 4 (none)
DVCF value 5 (none)
DVCF value 6 (none)
DVCF value 7 (none)
DVCF value 8 (none)
DVCF value 9 (none)
Explode NO
Figure list on new page YES
Figure/table number separation YES
Folio-by-chapter YES
Head 0 body text Part Head 1 body text Chapter
Hyphenation YES
Justification YES
Language ENGL
Layout OFF
Leader dots YES
Master index (none)
Partial TOC (maximum level) 4
Partial TOC (new page after) INLINE
Print example id's NO
Print cross reference page numbers YES
Process value (none)
Punctuation move characters .,
Read cross-reference file (none)
Running heading/footing rule NONE Show index entries NO
Table of Contents (maximum level) 3
Table list on new page YES
Title page (draft) alignment RIGHT
Write cross-reference file (none)
Imbed Trace
Page 0 3731SU Page 0 3731VARS
Page 0 3731VMB
�
- WIN31TXA.ZIP [Info on the beta release of Windows 3.1. Text only but very informative.]
WIN31USR.TXT
From: tom@mims-iris.waterloo.edu (Tom Haapanen)
Newsgroups: comp.windows.ms
Subject: FYI - Windows 3.1
Date: 9 Sep 91 10:15:23 GMT
Sender: news@watserv1.waterloo.edu
Organization: University of Waterloo, WATMIMS Research Group
Lines: 345
Reposted from bit.listserv.win3-l...
LINDA@HUB2.BITNET writes:
>The following is from Z*NET PC INTERNATIONAL ONLINE:
>
> Z*NET PC INTERNATIONAL ONLINE MAGAZINE
> --------------------------------------
> Volume 1, No.13 Issue #13 August 27, 1991
> Copyright (c)1991, Rovac Industries, Inc.
>
> Publisher\Editor: Ron Kovacs
> Assistant Editor: Mike Mezaros
> Media Consultant: Drew Reid Kerr of Four Corners Communications
>---------------------------------------------------------------------------
>
> /////////////////////////////////////
> /////////////////////////////////////
> /////////////////////////////////////
> The Graphical Edge
> by Mike Mezaros
>
>
> "I understand the whole affair in the Soviet Union
> was over Windows and PM."
>
> - Richard Finkelstein, CompuServe IBMOS2 Forum Member
>
>
>
> /// WINDOWS 3.1 SNEAK PREVIEW: A GUIDED TOUR
>
> We've all heard about the new technical advances in Win 3.1, but which
> parts will actually change the way we work? Which will make it easier?
> Which little things will mean a lot? Assuming, of course, that we will
> even be using Windows 3.1... OS/2 2.0 presents a significant challenge.
> Whether that challenge will be met, I don't know. But until I do, I'll
> continue to keep a close eye on Windows, for better or for worse.
>
> Also, please remember, all of this is preliminary information, subject
> to change, based on my personal inspection of the latest Windows 3.1
> beta version. I am not a member of the beta test team, and therefore am
> not bound by any non disclosure agreements. However, an acquaintance
> who is a tester was kind enough to let me visit and explore the latest
> pre-release version of Microsoft Windows.
>
>
> o Program Manager 3.1
>
> The new ProgMan, like most of Windows 3.1, doesn't seem terribly
> different at first glance. But it does contain a number of interesting
> new features.
>
> The most noticeable, and arguably the best, change is the new StartUp
> group. No more fiddling with the Run= and Load= lines in the WIN.INI
> file, setting an application to automatically launch at startup is now
> as easy as dragging it from one group to another.
>
> The "Save Settings" check box from the Exit Windows dialog has been
> changed to an option on the "Options" menu.
>
> You still can't change the default group icon to any icon you'd like...
> but what we are stuck with HAS been spruced up a little. The group icon
> in Windows 3.0 appears to be a white box holding a bunch of plain,
> square icons. It's supposed to look like a miniature version of our
> group windows. But how many group windows do you have that are filled
> with plain, square icons? ProgMan 3.1's group icons are a bit more
> realistic -- they hold six, tiny pseudo-icons, some of which are even
> recognizable. For example, a capital "A," a printer, and a clock...
>
> The ProgMan icon itself (which incorporates the group icon design) has
> also been modified to reflect this difference.
>
> The "Properties..." dialog has also been overhauled. For instance, you
> can now set a program to launch minimized (but why not maximized???).
> Selecting a new icon is now easier than ever. The "Change Icon..."
> dialog now shows you ALL of the icons in the selected program at once,
> or if they all can't fit in the sub-window, you can scroll through them.
>
> But the most significant change to the "Properties..." dialog is the
> addition of the WORKING DIRECTORY entry! Finally!! No longer do we have
> to rely on silly tricks, third party programs, or the whims of
> developers to provide us with this option. It is now extremely easy to
> set your applications to default to ANY directory on ANY drive.
>
>
> o File Manager 3.1
>
> Contrary to the situation with the new ProgMan, FileMan 3.1, at first
> glance, appears to be completely overhauled. But when you get right
> down to it, things haven't changed so much at all.
>
> The most striking differences are purely cosmetic. Color has been used
> to brighten up the interface, the small file icons (used to identify
> data, executables, etc.) have all been redesigned, and a selection of
> fonts and sizes is now provided. Even the program's icon has been
> "modernized," with color and a 3-D effect added. But functionality
> hasn't been increased nearly as much as good lucks.
>
> But don't get the wrong idea; there HAVE been improvements. There is no
> longer a single "main" window which spawns "directory" windows. Indeed,
> EVERY window is BOTH a main window and a directory window. In the
> classic DOS-shell style, directories reside on the left side of windows,
> while files reside on the right (and the space each gets can be
> determined by dragging a divider line). Each window has it's own drive
> icons. This makes the system a bit more flexible, and here's why...
>
> Let's say you have your window logged to drive C:. If you'd like to
> open a window for drive A:, you now have two choices. Single-clicking
> on the drive A: icon will log the current window onto drive A:,
> double-clicking on the drive A: icon will open a new window logged to
> that drive. In a few seconds, you can even set up your FileMan
> workspace so that it acts somewhat like the Mac; with drive icons on the
> side, spawning windows for those drives when double-clicked.
>
> I know, I know, it sounds a bit confusing. It's just one of those
> things that are hard to put into the words; when you see it, you'll pick
> it up right away. It isn't that radically different from what we have
> now, but it is a measurable improvement.
>
>
> o Control Panel 3.1
>
> Well, it doesn't look like the Control Panel from the Multimedia
> Extensions will be included with 3.1. As reported a long while back
> right here in Z*Net PC, the Control Panel included with those
> extensions is extendible. You can add applets, better known as CDEV's
> on the Mac. Instead, what we have is basically just an improved version
> of the old Control Panel.
>
> The biggest improvements are evident in the Desktop applet...
>
> First of all, there's the "Wrap Title" check box. Sounds innocent
> enough, doesn't it? Well, in my opinion this is one of the most
> significant contributions to the GUI ever made on the PC. Icons that
> contain long titles often overlap, causing portions to be unreadable.
> This is a major nuisance. The Macintosh's solution is to stagger the
> icons and their titles (many Mac users call this "Naimanizing" for some
> reason), like so:
>
> Program Manager Print Manager Windows Help
> File Manager Control Panel
>
> It's a nice enough solution. But Windows 3.1's answer is even better,
> actually word wrapping the titles, like this:
>
> Program File Print Control Windows
> Manager Manager Manager Panel Help
>
> The Desktop applet also adds support for the new, included screen saver.
> Four screen saver modules are included: Default (plain, boring, and
> black), Starfield (fly through space on your desktop), Mystify (colorful
> wireframe lines and shapes dancing against a black background), and
> Marquee (words scroll across the screen). Each of the screen saver
> modules (except Default) are highly customizable -- for example, the
> Marquee module lets you alter the scrolling message, it's size, it's
> font, it's location on the screen, and more. There's even a password
> protection option, so you can ensure your desktop is for your eyes only.
> The screen saver function itself seems to work very well -- even with
> DOS apps, which was a problem for some commercial screen savers.
>
> The Wallpaper selector in the Desktop applet is the same old garbage
> from 3.0. The combo box still only lists BMPs (RLEs also work, and save
> tons of space), and only those found in the Windows directory.
>
> The Color applet now lets you set things that formerly required digging
> into the WIN.INI file or using a third-party utility such as Playroom's
> excellent OSFrame customization utility. For example: button face,
> button text, button shadow, inactive title bar text, etc...
>
> The Fonts applet is basically the same, but adds "(Scalable)" to the
> description if it's a TrueType font. There's also a check box to disable
> TrueType. And speaking of TrueType and fonts...
>
>
> o TrueType and Bit-mapped Fonts
>
> TrueType is, as promised, included. It works, and it works beautifully.
> The on-screen bitmap fonts scale magnificently, often nicer than ATM. I
> didn't get a chance to actually try printing with the new fonts. But if
> they print half as good as they look, many people who are on the
> borderline deciding whether or not they need Adobe Type Manager may
> decide not to bother. On the other hand, the wealth of support
> available for ATM through Type 1 fonts is likely to keep it on top for
> those who actually need it throughout the foreseeable future.
>
> Anyhow, here's the list of included TrueType fonts, and my probably
> inaccurate descriptions of them (I'm not much of a typographer).
>
> Arial: Regular, Bold, Bold Italic, and Italic versions. Similar to the
> bit-mapped Helvetica in 3.0, but not exactly. It seems a bit heavier.
>
> Courier: Regular, Bold, Bold Italic, and Italic versions. Just like the
> bit-mapped Courier we now have.
>
> Times New Roman: Regular, Bold, Bold Italic, and Italic versions.
> Basically the same as the bit-mapped Times Roman from Windows 3.0.
>
> Symbol: Regular version. The same as...do I sound like a broken record?
> ("Daddy, what's a record?" "Well, son, they're like eight-tracks...")
>
> There are also three new bit-mapped fonts. Well, not exactly new. You
> see, Helvetica and Times Roman are gone. They have been replaced by MS
> Sans Serif and MS Serif, which look the same as their predecessors to
> me. Also, Small is now included, which looks pretty much like the
> Preview font from Word for Windows and Excel, used for previewing a full
> page when you're not in WYSIWYG (I hate that pseudo-acronym) mode.
>
>
> o The Included Utilities and Applications 3.1
>
> If there's only ONE reason to buy Windows 3.1, it's the new CLOCK
> utility! You won't believe the new functionality! Naah, just kidding.
>
> The Clipboard application has been renamed to Clipboard Viewer, which
> is, after all, exactly what it is. The old name confused new users.
>
> The Time/Date bug in Notepad has been fixed. If you're not aware of the
> bug, just select "Time/Date" from the "Edit" menu in Notepad 3.0. Only
> the date is pumped in.
>
> Write has remained pretty much the same. I expected the "Ruler" to be
> modified to look more like the toolbar in Word, with a 3-D look.
>
>
> o The Common Dialogs
>
> Windows 3.1 includes a DLL that provides for some standard dialogs, such
> as the "File" dialog that can be used for "Open...," and "Save As..."
> These dialogs can be called up by any application running under Windows.
>
> I'm happy to report that the new file dialogs use the same, easier to
> use controls as Visual Basic software. Remember: We reported on these
> new controls, predicted that they were the new standard, and provided a
> BMP picture of them a while before VB was even released. This proves
> that Z*Net PC isn't only the best place to turn for real news, it's also
> the best place to turn for the scoops on unimportant stuff, too. (smile)
>
> These new common dialogs keep executable sizes down, and provide a
> definitive and undoubtedly improved standard. For example, a list box
> is now provided for extensions. No longer will you have to modify
> Notepad or Write to get them to default to "*.*" (as explained by Jack
> McKinley in an article in Z*Net PC Issue #12).
>
> There is also apparently a common dialog for "About..." boxes... either
> that, or Microsoft has just decided to adopt a standard style for all of
> their applications. All of the About boxes in 3.1 look alike, provide
> the name of the person who registered Windows, the amount of free system
> resources, and amount of free memory. Definitely handy information!
>
> But the best thing about the new dialogs is that programmers will be
> more likely to offer a "Browse..." button instead of just a text box,
> because they won't have to dedicate much extra effort or code.
>
> And Microsoft has picked up on this. There are "Browse..." buttons
> throughout Windows 3.1, including in the "Run..." and "Change Icon..."
> dialogs in the Program Manager. In the same vein, "Help..." buttons are
> also plastered everywhere, to remind people who forget about F1.
>
>
> o Windows Help 3.1
>
> And speaking of help, the Windows Help engine has also been updated.
>
> For example, the "Index" button has been changed to "Contents," which
> makes a lot more sense. How often do you find an index at the FRONT of
> anything? The "Search" command is more like an Index, but that's still
> being called Search.
>
> In addition to the "Back" button that will back-track you to your last
> spot in the help file, the new help system also features a "History"
> button. Clicking on it brings up a Window with a list box featuring the
> last few help topics you've visited.
>
> "Pop-up" hyperlink items with the dotted underline, such as definitions,
> that now only appear while you click on them, stay up until you click on
> them again in 3.1.
>
> The buttons on the toolbar in Windows Help 3.0 merely "gray" when a
> certain feature is unavailable, such as "Search." In 3.1, non-
> functional buttons actually don't appear. Also, the filename of the
> help file is no longer found on the title bar -- i.e., "Program Manager
> Help - PROGMAN.HLP." And it seems that the new standard is to NOT
> include the word "help" in the title bar at all.
>
> All of this seems to be an attempt to further the illusion that a
> customized help system is built into each application.
>
>
> o DOS Support
>
> The only change in DOS support that I could detect what that when you
> open a DOS session, the first line is now, "Type Exit to close this DOS
> prompt." It isn't a function of the PIF or a special batch file, either,
> because you can just run COMMAND.COM and the same will happen.
>
> This is good for new users who don't understand the concept of running a
> DOS session under Windows. But it's also good for those of us who
> occasionally forget where we are and shut off the PC before exiting...
>
>
> o Object Linking and Embedding
>
> OLE, the compound document standard, is also included as promised. All
> of the included applications are OLE aware. After playing with OLE for a
> few minutes, I came to the conclusion that this is NOT something that
> every Windows user is going to be using every day. OLE is interesting,
> and by all means a "neat trick," but it is still complicated and all of
> it's benefits are not yet evident.
>
> Some things have had to change to suit OLE. For instance, file
> associations, where you associate a filename extension with an
> application. This way you can simply run README.TXT and Notepad (or
> whatever text editor you like) will launch with README.TXT loaded. A
> side eff RegEdit you could define a file type called "TEXT FILE." As an
> example, you could define this type as follows: All text files that are
> launched will be sent to Notepad and automatically printed. (There are,
> of course, many more options that you could configure, including DDE.)
> Then, using the FileMan, you could associate all of your "TXT," "ASC,"
> and "ME," files with the TEXT FILE file type.
>
>
> o Unrecoverable Application Errors
>
> Aaah, the dreaded UAE. UAE's have taken down many systems in their day,
> due to Windows 3.0 extremely poor interapplication protection.
>
> Windows 3.1 apparently does a lot to rid us of this problem. I was
> shown a known bug in the prior beta's version of Microsoft Write, and
> indeed, up came the unfortunately familiar UAE dialog.
>
> But guess what happened? The UAE dialog TOLD me which application was
> the culprit. It TOLD me what the problem was (albeit in technical
> terms). And then it terminated THAT application, and THAT application
> only. There were no follow-up UAE's. I continued to use the system for
> more than an hour without a hitch! All went well until shut-down time.
>
> Now, who knows if this will happen with every or nearly every other UAE?
> Mine was just one case, where a known problem was exploited. But
> according to Microsoft, they have declared war on the UAE. And what
> I've seen in Windows 3.1 so far is proof that they ARE at least trying.
>------------------------------END MESSAGE------------------------------------
[ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ]
[ eesti vabaks --- brivu latviju --- lietuva laisva --- free the baltics! ]
[ "i don't even know what street canada is on" -- al capone ]
�
WIN31MS.TXT
Article 18266 of comp.windows.ms: Path: news.claremont.edu!usc!sdd.hp.com!cs.utexas.edu!uunet!microsoft!georgem From: georgem@microsoft.UUCP (George MOORE) Newsgroups: comp.windows.ms Subject: Windows 3.1 backgrounder Message-ID: <#81cp_p@microsoft.UUCP> Date: 10 Oct 91 02:19:13 GMT Organization: Microsoft Corp. Lines: 475 What follows is the Windows 3.1 backgrounder which is being distributed freely to members of the press. It talks about the new features in Windows 3.1, new robustness, TrueType, the better networking support, Windows for Pen Computing, multimedia support, etc, etc. I have received permission to post this information here. Please do not mail me with questions about this document -- I cannot say anything more than what is written here. It should answer most of your questions about what is coming up in Windows 3.1. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Microsoft Windows Environment Version 3.1 August 1991 Overview With more than 4 million copies sold since the announcement of version 3.0 in May 1990, the end user community has affirmed its support for the Microsoft(R) Windows(TM) environment. Users have made Windows the best-selling retail software product of all time and the second most popular operating system ever (after MS-DOS). More than 200,000 Windows users have attended Microsoft-sponsored conferences, workshops, shows and 20 third-party events this year. And users have made Windows applications the fastest growing segment of the total software applications market, according to data from Software Publisher Association and other sources. It is fitting, then, that Microsoft should look to users to understand how to advance Windows in its next release, version 3.1. In the year since the announcement of version 3.0, Microsoft has conducted an unprecedented campaign to reach out and listen to the feedback and comments of the Windows installed base. This feedback collection process has taken several forms: o A commissioned survey of 11,000 U.S. households revealed Windows usage patterns, satisfaction levels, favorite and least favorite features as well as data about the hardware configuration of typical Windows users. This data was particularly interesting in that it was a "pure" user pool, not biased toward users who are more likely to register their software, subscribe to a particular magazine, etc. o Microsoft "Strike Teams" fanned out to gather data from corporate Windows 3.0 users. Nearly 90 percent of the suggestions resulting from these meetings have been implemented in Windows 3.1. o About two thousand Windows users called Microsoft Product Support Services each day for more information about using Windows. From these calls, PSS has developed an extensive knowledgebase; a representative from PSS served on the Windows 3.1 design committee. The 10 most commonly asked questions have been addressed in Windows 3.1. o An active CompuServe(R) support forum through the auspices of the Windows Presentation Manager Association (WPMA) resulted in extensive suggestions and feedback. User suggestions were the driving force behind the improvements and new features in version 3.1. As an important evolutionary step in what is planned to be a long series of Windows-based operating systems from Microsoft, Windows version 3.1 will offer refinements to version 3.0 that are designed to bring greater ease of use, functionality, and performance to Windows users while maintaining backward compatibility with Windows version 3.0 applications. These refinements fall into the following categories: o Improved usability and performance o Application and system robustness o TrueTypeTM scalable font technology o Improved application integration o Extensions for new computing platforms This paper will describe the key added features of Windows version 3.1 in greater detail. Improved Usability and Performance Among the results of the extensive feedback from users of Windows version 3.0 are significant enhancements to the usability of the Windows environment. Dozens of improvements will be immediately noticeable, while hundreds of others work behind the scenes to support the new features. While many of them are minor, taken together, these improvements contribute to a smoother, more responsive user interaction with Windows. Improved Installation The Windows version 3.1 Install program will be able to detect even more hardware and software configurations than its version 3.0 predecessor. The result is an improved ability for Windows to configure itself optimally for the machine on which it is being installed. The Installer program detects a wide variety of TSRs (terminate-and-stay-resident programs), and hardware devices that are known to cause problems, taking action to notify the user or correct the problem without user involvement. Windows version 3.1 will be easier for novice users to install with Express Install, and more customizable for advanced users, who can select groups of programs to install. For PC coordinators, Windows version 3.1 installation is improved with the batch install option, and better network setup features for installation in networked environments. File Manager Improvements The Windows version 3.1 File Manager has been completely redesigned for improved usability and performance. The File Manager now supports multiple "panes" for easy browsing. Users can now display the directory tree and a list of files side-by-side in a window. The File Manager also allows the display of more file attributes than before and can even display file and folder names in a choice of fonts. Another significant improvement is the new "quick format" capability, which allows users to format floppy disks in much less time than before. The File Manager will support an easier, more intuitive "drag and drop" model for manipulating files. For example, to print a file, the user drags the file's icon with the mouse and "drops" it onto the Print Manager, which prints the document. Users will also be able to take an icon and drop it on a running application or the application title bar; then the application will automatically open that file. Program Manager Improvements Improvements to the Program Manager include "wrappable" icon titles that sit neatly under each icon in multiple lines, instead of a single long line that may overlap with other icon titles. Users also will appreciate the new "startup group," which allows them to launch any group of applications automatically when the Windows environment is started. Printing Improvements The Windows version 3.1 Print Manager now has the ability to resume stalled print jobs automatically, without user intervention. For example, if a printer runs out of paper, the print job will be resumed after the paper tray is restocked. Another printing improvement introduced with Windows version 3.1 is the universal printer driver (UNIDRV). This software offers a single, printer- independent driver for which specific printer drivers can be built rapidly. The universal printer driver makes it easier for printer manufacturers to write or update printer drivers because it encapsulates all the major features of a printer driver in a single piece of software. Vendors simply provide a table of printer-specific parameters for each printer. Instead of using dozens of large "monolithic" printer drivers, the Windows environment will need only a single driver and a small support table for each printer. Nearly 250 printers will be supported in Windows 3.1, with the majority supported through UNIDRV. Better Support for Networks A number of improvements will make Windows version 3.1 easier to use on a computer that is attached to a network. Network administrators will find that setup is easier under Windows version 3.1, especially for complex system configurations. Network problems are also easier to trace and fix because network errors are displayed with more information regarding the type and source of the problem. Another significant change is that users can specify "persistent" network connections, meaning that information about a remote disk drive or printer is maintained by the Windows environment after a network session is terminated. Any "disconnected" drives will appear in the File Manager's drive bar as "unavailable." To re-establish connection, users will simply click on the drive's icon. Improved Performance Performance improvements have been achieved throughout Windows 3.1. These include faster, more responsive user shell components (notably File Manager and Program Manager); increased display driver performance (for example, the VGA and 8514 drivers); better printing performance (overall speed is improved, but Windows will also give control back to the application quicker once the print command is invoked); and faster paging in 386 enhanced mode. Version 3.1 will include FastDisk, a 32-bit driver that allows Windows to bypass DOS in the BIOS for its virtual memory paging file. Application and System Robustness Since its shipment in May of 1990, Windows version 3.0 has proven to be a remarkably stable product. In fact, Microsoft has only implemented a single update release (version 3.0a) to accommodate minor bug fixes. Like any mature operating system, however, Windows works in cooperation with a vast number of hardware platforms, applications software and peripherals. With the countless permutations of software and hardware, occasional conflicts are inevitable, and approximately one to two percent of Windows-related calls to Microsoft Product Support Services are regarding these "Unrecoverable Application Errors" (UAEs). Through its communication with Windows version 3.0 users and developers, Microsoft has developed a fine-tuned understanding of how applications generate and handle errors. Most UAE questions have been resolved through helping users deinstall misbehaved TSRs, resolve questions on Windows 3.0 versions of drivers or software, or remove unnecessary lines in the Windows CONFIG.SYS files. In Windows version 3.1, Microsoft's accumulated knowledge serves as the basis for the following design focal points: 1) Better diagnostics to pinpoint the cause of application errors; 2) Tools and information to help developers write error-free applications; 3) Graceful handling of application errors if they do occur (so the faulting application doesn't crash the system). Following are several examples of how these design goals are implemented in Windows version 3.1. Error Diagnostics and Reporting If an application program generates an error under Windows version 3.1, the user will receive an error dialog box with more specific information about the type of fault that occurred and which application generated the error (the Windows 3.0 dialog box says: "Unrecoverable Application Error"). This allows problems to be traced and corrected much more quickly than before. Additionally, Windows version 3.1 will ship with a diagnostic tool called "Dr. Watson" that will record and store information about an application error, should one occur. This data will provide feedback on the error that can be used by a support technician to determine the solution for the error. Developer Tools for Error Tolerance and Prevention Microsoft's developer support program for Windows version 3.1 includes tools and information to help developers write more error-free Windows applications. For instance, a new mechanism has been implemented within Windows version 3.1 that enables validation of the many parameters that applications use to communicate with the Windows environment. If an application uses the wrong type of parameter, or if the parameter's value is outside the acceptable range, Windows will report an error. Developers are thus notified of potential parameter problems before their product ships. Several utilities are also being made available to Windows developers that help to detect and trace the source of problems. For example, a new "stress test" utility creates a highly active and dynamic environment in which application bugs may be "shaken out" during all stages of development. Error Recovery Windows version 3.1 includes a number of improvements designed to handle UAEs more effectively. Under version 3.1, if an application "hangs," users can press the CTRL+ALT+DEL reboot key sequence, and Windows will ask whether the application should be continued or closed. If the user chooses to close the application, Windows will reset the environment to a stable state which will allow the user to continue working within the Windows environment. There is no longer a need to exit and restart the Windows environment. TrueType Scalable Font Technology Windows version 3.1 includes the new TrueType(TM) scalable font technology. TrueType provides "outline" fonts, giving users instant access to fonts in any point size, and allowing high quality output on any monitor or printer supported by Windows itself. TrueType was designed and developed to meet the requirements of type professionals and graphic designers. TrueType offers the following benefits. Complete Integration with the Operating System TrueType is an integrated component of Windows version 3.1. For users, this means that there is nothing to buy or install. All the benefits of scalable font technology are built into the operating environment itself, and existing Windows applications can use them immediately. Four TrueType scalable font families will ship with all copies of Windows version 3.1: Arial (alternative to Helvetica), Times New Roman, Courier and Symbol. Every major font vendor (with the exception of Adobe) has committed to develop substantial TrueType font libraries for both the Macintosh(R) and Windows platforms. Cross-Platform Compatibility TrueType is also offered on the Apple(R) Macintosh and TrueType fonts can be ported between Windows and the Macintosh without conversion. So documents using TrueType fonts may be exchanged between a Windows PC and the Macintosh without required changes in character set, font metrics or line endings. TrueType is also available in Macintosh-compatible laser printers, in TrueImage printers, and has been licensed to numerous printer vendors for use in future products. Dynamic Font Downloading TrueType fonts are automatically converted to bitmap images and downloaded to laser printers so that what the user sees on the screen is the same as the printed page. TrueType uses dynamic downloading, sending only the characters requested rather than the entire character set, resulting in faster, more efficient printing. Open Technology In order to make it easy for vendors to support TrueType fonts, each font's "metrics" are made available as public specifications and are available without royalties. A font's metrics provide a complete mathematical description of the font's characteristics, which allows vendors of output devices to render the font exactly as it appears on the screen. Public availability of TrueType font specifications will make it easier and less expensive for vendors to support TrueType fonts on their products. Improved Application Integration Windows environment version 3.1 provides the most sophisticated platform yet for application integration, making it easier for users to exchange data between documents and for programmers to build these capabilities into Windows applications. Application integration is supported by the following features in version 3.1: Object Linking and Embedding An important technology for the 1990s, Object Linking and Embedding (OLE) creates an environment in which applications can share information seamlessly. With OLE, all data can be thought of as being a type of "object." A spreadsheet chart, an illustration, a table, and even a paragraph of text are all examples of objects. OLE provides the capability for applications to share these objects easily. Windows environment version 3.1 supports OLE by providing standard libraries, interfaces and protocols that applications will use to exchange data objects. As Windows developers begin implementing OLE capabilities within their programs, users will see a new generation of applications that work together cooperatively. OLE capabilities have already been implemented within new versions of the Windows Write, Paint, and Cardfile accessories, all of which are provided with the Windows version 3.1 product. A user can, for example, create an illustration using the Paint program and "embed" the graphic in a Write document. If the illustration must be updated, the user can click on its icon within the Write document, which automatically launches Paint to allow editing of the drawing. Since the original graphics file is "linked" to the image embedded in the document, any change made to one will automatically update the other. This eliminates the need to modify multiple copies of the image or modify the original image and re-import it into the document. Better Support for Dynamic Data Exchange In the Windows environment, the standard way of sharing data between applications is through a mechanism known as dynamic data exchange (DDE). Object Linking and Embedding (as well as other forms of data exchange) use DDE as their primary means of data exchange. Windows environment version 3.1 provides developers with a new Dynamic Data Exchange Manager Library (DDEML) that offers a higher-level programming model and makes it easier for developers to implement DDE capabilities in a Windows application. Better Support for DOS Applications A number of changes improve support for existing DOS* applications within the Windows environment. In particular, DOS application performance is enhanced when using Windows version 3.1 in conjunction with MS-DOS version 5, since MS-DOS 5 makes significantly more memory available to DOS applications. In addition, Windows version 3.1 now supports DOS applications in VGA graphics mode in a window or running in the background. Also, Windows version 3.1 will include more pre-written Program Information Files (PIF files "tell" Windows how to run specific DOS applications) for even greater DOS application support. Finally, disk-paging will allow users to run more DOS applications than they can under Windows version 3.0. Extensions for New Computing Platforms Windows version 3.1 will allow users to exploit significant new computing platforms such as pen-based computers and multimedia PCs. Windows for Pen Computing Building on the Windows graphical user interface and coupled with advances in symbol recognition, pens will be the foundation for highly intuitive and "personal" user interfaces. To exploit the potential of pen computing, Microsoft has developed a series of extensions to Windows that include: enhancements to the user interface to allow for pen input; a pen message interpreter allowing existing Windows (and DOS) applications to use the pen; and a modular open handwriting recognition engine. More than 30 hardware vendors will ship Microsoft Windows version 3.1 with extensions for pen- based computing with their systems, starting in early 1992. Multimedia Windows version 3.1 will work seamlessly with the Microsoft extensions for multimedia computing. These extensions allow users to include new objects such as audio, animation and full-motion video and embed them in existing applications. These features will also enable a whole new class of multimedia documents, such as encyclopedias enhanced with video and audio clips, or catalogs that display animated illustrations. Personal computers integrating Windows and the multimedia extensions to Windows will begin shipping this fall. Windows' extensible architecture makes it possible for multimedia computing to span low-cost systems for home and education and sophisticated multimedia authoring platforms for the high end of the market. An important enabling technology for multimedia computing is the OLE protocol described above. With OLE plus the Windows multimedia extensions, a user can embed a multimedia "object" such as a video or audio clip into an existing Windows application, just as he or she would a chart or text file. Laptop Support Many vendors of today's popular 286 and 386(TM)-based laptop computers ship Windows version 3.0. Users of laptops will appreciate a feature in Windows version 3.1 called "mouse blur," which makes it easier to find the cursor on a laptop display. In addition, Windows version 3.1 supports the Advanced Power Management specification, which allows Windows to interact with native power management of a laptop PC for longer battery life. With version 3.1, vendors of laptops and other small form-factor computers will have the option of licensing a special version of Windows in ROM. This version of Windows 3.1 will be burned in to a ROM chip and will execute directly from ROM rather than from a hard disk. A ROM version of Windows opens the doors to other types of computing as well, including the emerging category of palm-top computers. Beta Testing and Developer Support Windows environment version 3.1 is currently in beta testing. The beta program will be one of the largest Microsoft has ever conducted, eventually involving as many as 10,000 participants. Additionally, Microsoft is conducting technical seminars for Windows developers to discuss the details of the new APIs in Windows version 3.1. A new Software Development Kit (SDK) and Driver Development Kit (DDK) will allow developers to more effectively implement the API features. Microsoft's Hardware Compatibility Program currently includes 350 testers and Microsoft is actively recruiting additional participants to ensure the tightest possible compatibility of Windows with the vast array of hardware and peripherals on the market today. Developer enthusiasm for Windows version 3.1 is high. Nearly 2,000 Windows developers attended a recent Seattle conference on Windows version 3.1. In addition, a June 1991 survey of the top 70 PC independent software vendors (ISVs) found that 100 percent are planning to test for and take advantage of Windows version 3.1. Conclusion Windows version 3.1 is an important next step in Microsoft's core Windows strategy, an evolutionary strategy that spans 286 laptops to high-end workstations or servers. Today, Windows runs on MS-DOS, the operating system that spawned the PC industry and is currently in use by tens of millions of people. Today's Windows runs the thousands of existing MS-DOS and Windows-based applications. Extended versions of Windows -- for example, for multimedia or pen -- allow users to run all of these applications as well, plus unique new applications developed with pen or multimedia in mind. Microsoft will ship a high-end version of Windows called Windows NT (for "new technology") in 1992. Windows NT will run the same DOS-based and Windows-based applications as Windows 3.1., while also supporting advanced security, multithreading, multiprocessor systems, and RISC chips that promise even higher performance. Microsoft's vision of computing in the 1990s and beyond is that computers will empower individuals and organizations. With its scalable implementations, the investment of Microsoft and the commitment of third parties, Windows will be the foundation for realizing this vision. ######### Microsoft, the Microsoft logo, MS, and MS-DOS are registered trademarks and Windows is a trademark of Microsoft Corporation. Apple and Macintosh are registered trademarks and TrueType is a trademark of Apple Computer, Inc. Arial and Times New Roman are registered trademarks of Monotype Corporation PLC. CompuServe is a registered trademark of CompuServe, Inc. Helvetica is a registered trademark of Linotype AG and/or its subsidiaries. 386 is a trademark of Intel Corporation. (C) 1991 Microsoft Corporation. All rights reserved. Printed in the United States of America. This backgrounder is for informational purposes only. Microsoft makes no warranties express or implied, in this summary. * As used herein, "DOS" refers to MS-DOS and PC-DOS operating systems. �
- MS-DOS 5.0 Beta 文档
DOS5B_1.ZIP [NEWS ABOUT MSDOS 5.0 [Come with MS-DOS 5.00.409c]]
READ_ME.NOW
Microsoft has added a feature to it's DOS 5.00.409c ßeta test version that indicates it will either release DOS 5.00 by July 1, 1991 or place another ßeta test version into the test pipeline before that date. The enclosed text files were supplied by Microsoft with DOS 5.00.409c. As they reveal this DOS version is being readied for the power 80386 & 80486 market. It will, however, speedup an 80286 machine, but not allow high memory management. 8086 & 8088 users would be better off using DOS 3.3 or 4.01. Read the 3 enclosed files for more information. �
NETWORKS.TXT
HOW TO UPGRADE NETWORKS FOR MS-DOS VERSION 5.0
************************************************************
* *
* BEFORE YOU INSTALL MS-DOS 5.0: *
* ------ *
* *
* 1. CHECK THE "NETWORK COMPATIBILITY LIST" IN THIS *
* DOCUMENT TO ENSURE YOUR NETWORK SUPPORTS MS-DOS *
* VERSION 5.0. *
* *
* 2. IF YOUR NETWORK IS ON THE LIST, PRINT THIS FILE *
* (NETWORKS.TXT) OR OBTAIN A PRINTED COPY. *
* *
* 3. LOCATE THE SECTION IN THIS DOCUMENT FOR THE TYPE *
* AND VERSION OF THE NETWORK YOU ARE USING. *
* *
* 4. FOLLOW THE INSTRUCTIONS IN THE APPROPRIATE SECTION *
* TO UPGRADE YOUR NETWORK FILES. *
* *
* *
************************************************************
THE INSTRUCTIONS IN THIS DOCUMENT ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
* Searching a file for text
* Editing a text file (in some cases)
ALTHOUGH INSTRUCTIONS ARE INCLUDED FOR BOTH BEGINNING AND
ADVANCED DOS USERS, MAKE SURE YOU UNDERSTAND THE
INSTRUCTIONS BEFORE YOU PROCEED. IF YOU DO NOT, GET
ASSISTANCE FROM SOMEONE WHO DOES.
NOTE: When you type the commands in the instructions, make
sure you type the correct drives and directories for
your configuration. These might differ from those
shown in the instructions. The commands in the
instructions are only examples.
---------------------
CONTENTS OF THIS FILE
---------------------
This table of contents includes a three-character code for
each section in this document. To go to a section quickly,
use your text editor to search for the code that corresponds
to the section you want. For example, to go to the Network
Compatibility List, you would search for $NC.
$NC -- Network Compatibility List
$SA -- A Note to System Administrators
$UN -- Upgrading Specific Networks
$LM -- Microsoft LAN Manager (or 100-percent
compatible)
$L2 -- Version 2.x Enhanced
$LB -- Versions 2.x Basic and 1.x Basic
$L1 -- Version 1.x Enhanced
$MS -- MS-Net (or 100-percent compatible)
$NW -- Novell NetWare
$3S -- 3Com 3+Share version 1.6
$3O -- 3Com 3+Open
$32 -- Version 2.x Enhanced
$3B -- Version 2.x Basic
$31 -- Version 1.x Enhanced
$3A -- Version 1.x Basic
$BV -- Banyan Vines
$PC -- IBM PC LAN Program versions 1.31 and later
$DC -- DCA 10Net versions 3.0 and later
$AR -- Artisoft LANtastic versions 2.5 and later
$TS -- Troubleshooting
$RN -- Returning to Your Old Network
$FC -- File Creation Error
$IV -- Incorrect DOS Version
$MC -- Memory Conflicts with Network Adapter Cards
$EM -- Networks that Use Expanded or Extended
Memory
$SH -- Conflicts with the MS-DOS Shell Task
Swapper
$V? -- Identifying Your Version of LAN Manager or
3+Open
--------------------------------
NETWORK COMPATIBILITY LIST - $NC
--------------------------------
To find out whether your network supports MS-DOS version
5.0, check the following list:
Redirectors
Compatible on MS-DOS
Company Product Versions 5.0 Disks?
------- ------- ---------- -----------
Artisoft LANtastic 3.0 and later No
Banyan Vines 4.0 and later No
DCA 10-Net 4.0 and later No
DEC PCSA 3.0 and later No
LAN Works 3.0 and later No
HP Office Works All Yes
LAN Manager 1.0 and later Yes
IBM PCLP 1.3 and later Partial
LAN Server 1.1 and later No
Microsoft MS-NET All Yes
LAN Manager 1.0 and later Yes
Novell NetWare 2.1 and later Yes
Olivetti Olinet-LAN 1.0 and later Yes
Olinet-LM 1.0 and later Yes
Sitka Tops All No
3COM 3+Share 1.6 and later Yes
3+Open 1.1 and later Yes
UB Net/One PC 2.0 and later Yes
Net/One LM 1.1 and later Yes
NOTE: MS-DOS version 5.0 supports most DOS version 4.x
compatible network redirectors. Microsoft recommends
that you use MS-DOS version 5.0 redirectors, when
possible, for maximum compatibility.
-------------------------------------
A NOTE TO SYSTEM ADMINISTRATORS - $SA
-------------------------------------
It is strongly recommended that you customize this document
and streamline the network-upgrade process for your setting.
Users will find these instructions easier to use if the
examples include the actual location of network redirectors
and MS-DOS 5.0 files for your network configuration. You
might even be able to create one or more simpler documents,
each covering a particular configuration.
The network redirectors that come with MS-DOS version 5.0,
like the MS-DOS files themselves, are in compressed form on
the Setup disks. To make them usable, these files must be
expanded. You can simplify the newtork-upgrade process for
users by expanding the network redirectors before making
them available to your users. You can do this using the MS-
DOS 5.0 EXPAND command. (The EXPAND command itself is not
compressed.) Place these expanded 5.0 redirectors and any
version 4.x-compatible redirectors your users might need on
a single shared network directory. This way, users will not
need to
expand or search for
redirector files.
As a general rule, it is a good idea to make sure that users
complete each one of these steps before starting the next:
1. Check the system to make sure its working properly and
free of disk errors.
2. Upgrade network files, as described in this document.
3. Install MS-DOS 5.0 and make sure it is functioning
properly.
4. Optimize the performance of MS-DOS, as described in the
Microsoft MS-DOS User's Guide and Reference and in the
UMB.TXT online file.
---------------------------------
UPGRADING SPECIFIC NETWORKS - $UN
---------------------------------
************************************************************
* *
* MICROSOFT LAN MANAGER (and 100% compatible) - $LM *
* *
************************************************************
Compatible networks include Ungermann-Bass (UB), NCR,
Olivetti and Hewlett-Packard (HP).
NOTE: If you are not sure which version of Microsoft LAN
Manager you are using, see the section "Determining
Which Microsoft Network You Are Using," at the end of
this document.
--------------------------
VERSION 2.x ENHANCED - $L2
--------------------------
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
To upgrade LAN Manager version 2.x Enhanced, replace your
current NETWKSTA.EXE file with the new version of this file
supplied with MS-DOS version 5.0. You must expand the new
file as you copy it to your hard disk.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your LAN Manager files.
3. Back up your existing NETWKSTA.EXE file, which is
probably in your LAN Manager directory.
4. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 file called NETWKSTA.EX_ to your LAN
Manager directory. Syntax:
EXPAND <path>NETWKSTA.EX_ <path>NETWKSTA.EXE
5. Upgrade your computer to MS-DOS version 5.0.
>> Complete instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each NETWKSTA.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ NETWKSTA.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ NETWKSTA.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the NETWKSTA.EXE file(s)
on your disk. Note the location(s).
3. Back up each NETWKSTA.EXE file by copying it to a file
called NETWKSTA.OLD.
For example, if your NETWKSTA.EXE file is located in the
C:\LANMAN.DOS\NETPROG directory, you would type the
following command (on one line):
COPY C:\LANMAN.DOS\NETPROG\NETWKSTA.EXE
C:\LANMAN.DOS\NETPROG\NETWKSTA.OLD
Make sure you type the correct drive and directories for
the actual location of each NETWKSTA.EXE file you have.
4. Use the Expand command to expand and copy the MS-DOS
version 5.0 redirector file (called NETWKSTA.EX_) to the
directory (or directories) containing your old redirector
file(s). Make sure you name the new file NETWKSTA.EXE.
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirector is in
C:\LANMAN.DOS\NETPROG. You would insert the floppy disk
containing NETWKSTA.EX_ (Disk 3 for 3.5-inch disks or
Disk 6 for 5.25-inch disks) into drive A and then type
the following command:
EXPAND A:\NETWKSTA.EX_ C:\LANMAN.DOS\NETPROG\NETWKSTA.EXE
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\LANMAN.DOS\NETPROG. You would then type the
following command (on one line):
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\NETWKSTA.EX_
C:\LANMAN.DOS\NETPROG\NETWKSTA.EXE
Make sure you type the correct drive and directories for
the actual location of the new and old redirector
file(s).
NOTE: If you receive a "File creation error" message when
you try to expand this file, see the
Troubleshooting section later in this document.
5. Upgrade your computer to MS-DOS version 5.0.
--------------------------------------
VERSIONS 2.x BASIC and 1.x BASIC - $LB
--------------------------------------
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
* Searching a file for text
To upgrade LAN Manager version 2.x Basic or 1.x Basic,
replace your current REDIR.EXE and SETNAME.EXE files with
the new versions of these files supplied with MS-DOS version
5.0. You must expand the new files as you copy them to your
hard disk.
VERSION 1.X USERS: You can use this procedure to upgrade
your network. It is recommended, however,
that you obtain an updated version of the
1.x redirector by contacting Beta
Support.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your LAN Manager files.
3. Back up your existing REDIR.EXE and SETNAME.EXE
files, which are probably in your LAN Manager
directory.
4. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 files called REDIR.EX_ and
SETNAME.EX_ to your LAN Manager directory. Syntax:
EXPAND <path>REDIR.EX_ <path>REDIR.EXE
EXPAND <path>SETNAME.EX_ <path>SETNAME.EXE
5. Upgrade your computer to MS-DOS version 5.0.
>> Complete instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each REDIR.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ REDIR.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ REDIR.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the REDIR.EXE file(s)
on your disk. Note the location(s).
3. Back up each REDIR.EXE file by copying it to a file
called REDIR.OLD.
For example, if your REDIR.EXE file is located in the
C:\LANMAN.DOS\BASIC directory, you would type the
following command (on one line):
COPY C:\LANMAN.DOS\BASIC\REDIR.EXE
C:\LANMAN.DOS\BASIC\REDIR.OLD
Make sure you type the correct drive and directories for
the actual location of each REDIR.EXE file you have.
4. Locate each SETNAME.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ SETNAME.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ SETNAME.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the SETNAME.EXE file(s)
on your disk. Note the location(s).
5. Back up each SETNAME.EXE file by copying it to a file
called SETNAME.OLD.
For example, if your SETNAME.EXE file is located in the
C:\LANMAN.DOS\BASIC directory, you would type the
following command (on one line):
COPY C:\LANMAN.DOS\BASIC\SETNAME.EXE
C:\LANMAN.DOS\BASIC\SETNAME.OLD
Make sure you type the correct drive and directories for
the actual location of each SETNAME.EXE file you have.
6. Use the Expand command to expand and copy the MS-DOS
version 5.0 redirectors (called REDIR.EX_ and
SETNAME.EX_) to the directory (or directories) containing
your old redirector file(s). Make sure you name the new
files REDIR.EXE and SETNAME.EXE, respectively.
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirectors are in
C:\LANMAN.DOS\BASIC. You would insert the floppy disk
containing REDIR.EX_ and SETNAME.EX_ (Disk 3 for 3.5-inch
disks or Disk 6 for 5.25-inch disks) into drive A and
then type the following commands:
EXPAND A:\REDIR.EX_ C:\LANMAN.DOS\BASIC\REDIR.EXE
EXPAND A:\SETNAME.EX_ C:\LANMAN.DOS\BASIC\SETNAME.EXE
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\LANMAN.DOS\BASIC. You would then type the
following commands (each on one line):
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\REDIR.EX_
C:\LANMAN.DOS\BASIC\REDIR.EXE
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\SETNAME.EX_
C:\LANMAN.DOS\BASIC\SETNAME.EXE
Make sure you type the correct drive and directories for
the actual location of the new and old redirector
file(s).
NOTE: If you receive a "File creation error" message when
you try to expand these files, see the
Troubleshooting section later in this document.
7. Upgrade your computer to MS-DOS version 5.0.
--------------------------
VERSION 1.x ENHANCED - $L1
--------------------------
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
VERSION 1.X USERS: If you have the REDIR.400 redirector, you
can use this procedure to upgrade
your network. It is recommended, however,
that you obtain the new version of the
1.x redirector by contacting Beta
Support, whether or not you have
REDIR.400.
NOTE: If you are using LAN Manager version 1.x and DOS
version 4.x, you do not need to upgrade your network
files to run with MS-DOS 5.0.
>> Instructions in Brief (for advanced DOS users)
------------------------------------------------
1. Locate the directory on your hard disk containing your
LAN Manager files.
2. Back up your existing NETWKSTA.EXE file, which is
probably in your LAN Manager directory.
3. Copy the DOS version 4.x compatible NETWKSTA redirector
to the directory containing your LAN Manager files.
Name this file NETWKSTA.EXE. If you don't have this
redirector, contact your system administrator.
4. Upgrade your computer to MS-DOS version 5.0.
>> Complete Instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the WHERE command to your hard disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following command:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Search for the NETWKSTA.400 file on your hard disk by
typing the following command:
WHERE /R \ NETWKSTA.400
If you do not have the file, do not continue this
procedure. Contact Beta Support to obtain the latest
version of this file.
3. Locate each NETWKSTA.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ NETWKSTA.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ NETWKSTA.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the NETWKSTA.EXE file(s)
on your disk. Note the location(s).
4. Back up each of the redirector files by copying it to
a file called NETWKSTA.OLD.
For example, if your NETWKSTA.EXE file is located in the
C:\LANMAN.DOS\NETPROG directory, type the
following command (on one line):
COPY C:\LANMAN.DOS\NETPROG\NETWKSTA.EXE
C:\LANMAN.DOS\NETPROG\NETWKSTA.OLD
Make sure you type the correct drive and directories for
the actual location of the redirector file(s).
5. Copy the NETWKSTA.400 redirector to the directory that
contains your current redirector.
For example, suppose your current redirector and
NETWKSTA.400 are in C:\LANMAN.DOS\NETPROG. You
would type the following command:
COPY C:\LANMAN.DOS\NETPROG\NETWKSTA.400
C:\LANMAN.DOS\NETPROG\NETWKSTA.EXE
Make sure you type the correct drives and directories for
the actual location of the redirector files.
NOTE: If you receive a "File creation error" message when
you try to copy this file, see the
Troubleshooting section later in this document.
5. Upgrade your system to MS-DOS version 5.0
NOTE: Do not use MS-DOS Shell Task Swapper if you are using
NETWKSTA.400.
************************************************************
* *
* MS-NET (and 100-percent compatible) - $MS *
* *
************************************************************
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
* Searching a file for text
* Editing a text file
To upgrade MS-NET or 100-percent compatible networks,
replace your current REDIR.EXE and SETNAME.EXE files with
the new versions of these files supplied with MS-DOS version
5.0. You must expand the new files as you copy them to your
hard disk. Also, you might need to edit your MSNET.INI file.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your MS-NET files.
3. Back up your existing REDIR.EXE and SETNAME.EXE
files, which are probably in your MS-NET directory.
4. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 files called REDIR.EX_ and
SETNAME.MS_ to your MS-NET directory. Syntax:
<path>EXPAND <path>REDIR.EX_ <path>REDIR.EXE
<path>EXPAND <path>SETNAME.MS_ <path>SETNAME.EXE
5. In the MSNET.INI file, ensure the REDIR command
appears before the SETNAME command each time both
commands appear in the same command set.
6. Upgrade your computer to MS-DOS version 5.0.
>> Complete Instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each REDIR.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ REDIR.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ REDIR.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the REDIR.EXE file(s)
on your disk. Note the location(s).
3. Back up each REDIR.EXE files by copying it to a file
called REDIR.OLD.
For example, if the files are located in the C:\NETWORK
directory, type the following command:
COPY C:\NETWORK\REDIR.EXE C:\NETWORK\REDIR.OLD
Make sure you type the correct drive and directories for
the actual location of the files.
4. Locate each SETNAME.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ SETNAME.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ SETNAME.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the SETNAME.EXE file(s)
on your disk. Note the location(s).
5. Back up each SETNAME.EXE file by copying it to a file
called SETNAME.OLD.
For example, if the file is located in the C:\NETWORK
directory, you would type the following command:
COPY C:\NETWORK\SETNAME.EXE C:\NETWORK\SETNAME.OLD
Make sure you type the correct drive and directories for
the actual location of the files.
6. Use the Expand command to expand and copy the MS-DOS
version 5.0 redirectors (called REDIR.EX_ and
SETNAME.MS_) to the directory (or directories) containing
your old redirector file(s). Make sure you name the new
files REDIR.EXE and SETNAME.EXE, respectively.
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirectors are in
C:\MSNET. You would insert the floppy disk
containing REDIR.EX_ and SETNAME.MS_ (Disk 3 for 3.5-inch
disks or Disk 6 for 5.25-inch disks) into drive A and
then type the following commands:
EXPAND A:\REDIR.EX_ C:\MSNET\REDIR.EXE
EXPAND A:\SETNAME.MS_ C:\MSNET\SETNAME.EXE
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\MSNET. You would then type the
following commands (each on one line):
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\REDIR.EX_
C:\MSNET\REDIR.EXE
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\SETNAME.MS_
C:\MSNET\SETNAME.EXE
Make sure you type the correct drive and directories for
the actual location of the new and old redirector
file(s).
NOTE: If you receive a "File creation error" message when
you try to expand these files, see the
Troubleshooting section later in this document.
7. Use a text editor to open the file MSNET.INI. This file
is probably located in the same directory as your
redirector file.
8. In MSNET.INI, make sure the command that starts REDIR.EXE
appears before the command that starts SETNAME.EXE each
time both commands appear in the same command set.
If it doesn't, move the command for REDIR.EXE so it
appears before the command for SETNAME.EXE.
9. Save the MSNET.INI file (as an unformatted text file)
and exit the editor.
10. Upgrade your computer to MS-DOS version 5.0.
************************************************************
* *
* NOVELL NETWARE (versions 2.1 and later) - $NW *
* *
************************************************************
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
* Editing a text file
To upgrade Novell NetWare, replace the command that starts
the network with the NET5.COM command, supplied with MS-DOS
version 5.0. You must expand the NET5.COM file as you copy
it to your hard disk.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your NetWare files.
3. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 file called NET5.CO_ to your NetWare
directory. Syntax:
EXPAND <path>NET5.CO_ <path>NET5.COM
4. If you start NetWare from a batch file, edit the
file so that NET5.COM is the startup command.
5. Upgrade your computer to MS-DOS version 5.0.
>> Complete instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each NET?.COM file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ NET?.COM
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ NET?.COM
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the NET?.COM file(s)
on your disk. Note the location(s).
For example, if your network files are in a directory
called C:\NOVELL, you will see a display similar to the
following:
C:\NOVELL\NET2.COM
C:\NOVELL\NET3.COM
C:\NOVELL\NET4.COM
3. Use the Expand command to expand and copy an MS-DOS
version 5.0 file NET5.CO_ to each directory containing
your old network file(s). Make sure you name the new file
NET5.COM.
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirector is in C:\NOVELL.
You would insert the floppy disk containing NET5.CO__
(Disk 3 for 3.5-inch disks or Disk 6 for 5.25-inch disks)
into drive A and then type the following command.
EXPAND A:\NET5.CO_ C:\NOVELL\NET5.COM
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\NETWORK. You would then type the following
command:
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\NET5.CO_
C:\NOVELL\NET5.COM
Make sure you type the correct drive and directories for
the actual location(s) of the network files.
4. If you start your network from AUTOEXEC.BAT or another
batch file:
a) Use a text editor to open AUTOEXEC.BAT or other batch
file.
b) Edit the file so that it starts NetWare with the
NET5.COM command (instead of NET2.COM, NET3.COM or
NET4.COM).
5. Upgrade your computer to MS-DOS version 5.0.
NOTE: You might experience difficulties with certain
existing Novell utilities (for example, Map, Login,
and Session) while using MS-DOS Shell Task
Swapper. If this occurs, do not use the utilities.
NOTE: Use an updated version of the Novell Token Ring
drivers to avoid problems using the MS-DOS Shell Task
Swapper.
************************************************************
* *
* 3COM 3+SHARE (VERSION 1.6 ONLY) - $3C *
* *
************************************************************
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
To upgrade 3Com 3+Share version 1.6, replace your
current MSREDIR.EXE file with the new version of this file
supplied with MS-DOS version 5.0. You must expand the new
file as you copy it to your hard disk. The new file is
called REDIR.EX_ on the MS-DOS Setup disks. You must rename
the file MSREDIR.EXE when you copy it to your hard disk.
NOTE: With a 3Com network, do NOT use the version of
SETNAME.EXE supplied with MS-DOS 5.0. Use the version
supplied by 3Com.
NOTE: No currently available version if 3Com's remote
startup software is not compatible with MS-DOS
versions 5.0 or 4.x.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your 3+Share files.
3. Back up your existing MSREDIR.EXE file, which is
probably in your 3+Share directory.
4. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 file called REDIR.EX_ to your 3+Share
directory. Syntax:
EXPAND <path>REDIR.EX_ <path>MSREDIR.EXE
5. Upgrade your computer to MS-DOS version 5.0.
>> Complete instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each MSREDIR.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ MSREDIR.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ MSREDIR.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the MSREDIR.EXE file(s)
on your disk. Note the location(s).
3. Back up each of the redirector files by copying them to
a file called MSREDIR.OLD.
For example, if your MSREDIR.EXE file is located in the
C:\NETWORKS\3COM directory, type the following command:
COPY C:\NETWORKS\3COM\MSREDIR.EXE
C:\NETWORKS\3COM\MSREDIR.OLD
Make sure you type the correct drive and directories for
the actual location of the redirector file(s).
4. Use the Expand command to expand and copy the MS-DOS
version 5.0 redirector file (called REDIR.EX_) to the
directory (or directories) containing your old redirector
file(s). Make sure you name the new file MSREDIR.EXE.
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirector is in
C:\NETWORKS\3COM. You would insert the floppy disk
containing REDIR.EX_ (Disk 3 for 3.5-inch disks or Disk
6 for 5.25-inch disks) into drive A and then type the
following command.
EXPAND A:\REDIR.EX_ C:\NETWORKS\3COM\MSREDIR.EXE
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\NETWORKS\3COM. You would then type the following
command:
EXPAND E:\MSDOS\UPGRADE\REDIR.EX_
C:\NETWORKS\3COM\MSREDIR.EXE
Make sure you type the correct drive and directories for
the actual location of the new and old redirector
file(s).
NOTE: If you receive a "File creation error" message when
you try to expand this file, see the
Troubleshooting section later in this document.
5. Upgrade your computer to MS-DOS version 5.0.
NOTE: If you are using a 3Com 3C505 network adapter card
and have difficulty connecting to a server, add the
following parameter to the "MSREDIR" line in your
network startup batch file:
MSREDIR /HIMEM:NO
NOTE: You cannot run a 3+Share server under MS-DOS version
5.0.
************************************************************
* *
* 3COM 3+OPEN - $3O *
* *
************************************************************
NOTE: With a 3Com network, do NOT use the version of
SETNAME.EXE supplied with MS-DOS 5.0. Use the version
supplied by 3Com.
NOTE: No currently available version if 3Com's remote
startup software is compatible with MS-DOS
versions 5.0 or 4.x.
--------------------------
VERSION 2.x ENHANCED - $32
--------------------------
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
To upgrade 3+Open version 2.x Enhanced, replace your
current NETWKSTA.EXE file with the new version of this file
supplied with MS-DOS version 5.0. You must expand the new
file as you copy it to your hard disk.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your 3+Open files.
3. Back up your existing NETWKSTA.EXE file, which is
probably in your 3+Open directory.
4. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 file called NETWKSTA.EX_ to your LAN
Manager directory. Syntax:
EXPAND <path>NETWKSTA.EX_ <path>NETWKSTA.EXE
5. Upgrade your computer to MS-DOS version 5.0.
>> Complete instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each NETWKSTA.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ NETWKSTA.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ NETWKSTA.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the NETWKSTA.EXE file(s)
on your disk. Note the location(s).
3. Back up each NETWKSTA.EXE file by copying it to a file
called NETWKSTA.OLD.
For example, if your NETWKSTA.EXE file is located in the
C:\3COM directory, you would type the
following command (on one line):
COPY C:\3COM\NETWKSTA.EXE C:\3COM\NETWKSTA.OLD
Make sure you type the correct drive and directories for
the actual location of each NETWKSTA.EXE file you have.
4. Use the Expand command to expand and copy the MS-DOS
version 5.0 redirector file (called NETWKSTA.EX_) to the
directory (or directories) containing your old redirector
file(s). Make sure you name the new file NETWKSTA.EXE.
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirector is in C:\3COM.
You would insert the floppy disk containing NETWKSTA.EX_
(Disk 3 for 3.5-inch disks or Disk 6 for 5.25-inch disks)
into drive A and then type the following command.
EXPAND A:\NETWKSTA.EX_ C:\3COM\NETWKSTA.EXE
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\3OPEN\DOSWKSTA\LANMAN\NETPROG. You would then
type the following command (on one line):
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\NETWKSTA.EX_
C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\NETWKSTA.EXE
Make sure you type the correct drive and directories for
the actual location of the new and old redirector
file(s).
NOTE: If you receive a "File creation error" message when
you try to expand this file, see the
Troubleshooting section later in this document.
5. Upgrade your computer to MS-DOS version 5.0.
------------------------
VERSIONS 2.x BASIC - $3B
------------------------
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
* Searching a file for text
To upgrade 3+Open version 2.x Basic, replace your current
REDIR.EXE file with the new version of supplied with MS-DOS
version 5.0. You must expand the new file as you copy it to
your hard disk.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your 3+Open files.
3. Back up your existing REDIR.EXE file, which is
probably in your 3+Open directory.
4. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 file called REDIR.EX_ to your 3+Open
directory. Syntax:
EXPAND <path>REDIR.EX_ <path>REDIR.EXE
5. Upgrade your computer to MS-DOS version 5.0.
>> Complete instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each REDIR.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ REDIR.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ REDIR.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the REDIR.EXE file(s)
on your disk. Note the location(s).
3. Back up each REDIR.EXE file by copying it to a file
called REDIR.OLD.
For example, if your REDIR.EXE file is located in the
C:\3OPEN\DOSWKSTA\LANMAN\BASIC directory, you would type
the following command (on one line):
COPY C:\3COM\REDIR.EXE
C:\3OPEN\DOSWKSTA\LANMAN\BASIC\REDIR.OLD
Make sure you type the correct drive and directories for
the actual location of each REDIR.EXE file you have.
4. Use the Expand command to expand and copy the MS-DOS
version 5.0 REDIR.EX_ to the directory (or directories)
containing your old REDIR.EXE file(s).
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirector is in C:\3COM. You
would insert the floppy disk containing REDIR.EX_ (Disk 3
for 3.5-inch disks or Disk 6 for 5.25-inch disks) into
drive A and then type the following command:
EXPAND A:\REDIR.EX_ C:\3COM\REDIR.EXE
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\3OPEN\DOSWKSTA\LANMAN\BASIC. You would then type
the following command (on one line):
E:\MSDOS\UPGRADE\EXPAND E:\MSDOS\UPGRADE\REDIR.EX_
C:\3OPEN\DOSWKSTA\LANMAN\BASIC\REDIR.EXE
Make sure you type the correct drive and directories for
the actual location of the new and old redirector
file(s).
NOTE: If you receive a "File creation error" message when
you try to expand this file, see the
"File Creation Error" section later in this
document.
5. Upgrade your computer to MS-DOS version 5.0.
--------------------------
VERSION 1.x ENHANCED - $31
--------------------------
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
VERSION 1.X USERS: If you have the NETWKSTA.400 redirector,
you
can use this procedure to upgrade
your network. It is recommended, however,
that you obtain the new version of the
1.x redirector by contacting Beta
Support, whether or not you have
NETWKSTA.400.
NOTE: If you are using 3+Open version 1.x and DOS
version 4.x, you do not need to upgrade your network
files to run with MS-DOS 5.0.
>> Instructions in Brief (for advanced DOS users)
------------------------------------------------
1. Locate the directory on your hard disk containing your
3+Open files.
2. Back up your existing NETWKSTA.EXE file, which is
probably in your 3+Open directory.
3. Copy the DOS version 4.x compatible redirector
(NETWKSTA.400) to the directory containing your 3+Open
files. Name this file NETWKSTA.EXE. If you don't have
this redirector, contact your system administrator or
Beta Support.
4. Upgrade your computer to MS-DOS version 5.0.
>> Complete Instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the WHERE command to your hard disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following command:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Search for the NETWKSTA.400 file on your hard disk by
typing the following command:
WHERE /R \ NETWKSTA.400
If you do not have the file, do not continue this
procedure. Contact Beta Support to obtain the latest
version of this file.
3. Locate each NETWKSTA.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ NETWKSTA.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ NETWKSTA.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the NETWKSTA.EXE file(s)
on your disk. Note the location(s).
4. Back up each of the redirector files by copying it to
a file called NETWKSTA.OLD.
For example, if your NETWKSTA.EXE file is located in the
C:\3OPEN\DOSWKSTA\LANMAN\NETPROG directory, type the
following command (on one line):
COPY C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\NETWKSTA.EXE
C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\NETWKSTA.OLD
Make sure you type the correct drive and directories for
the actual location of the redirector file(s).
5. Copy the NETWKSTA.400 redirector to the directory that
contains your current redirector.
For example, suppose your current redirector and
NETWKSTA.400 are in C:\3OPEN\DOSWKSTA\LANMAN\NETPROG. You
would type the following command:
COPY C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\NETWKSTA.400
C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\NETWKSTA.EXE
Make sure you type the correct drives and directories for
the actual location of the redirector files.
NOTE: If you receive a "File creation error" message when
you try to copy this file, see the
Troubleshooting section later in this document.
5. Upgrade your system to MS-DOS version 5.0
NOTE: Do not use MS-DOS Shell Task Swapper if you are using
NETWKSTA.400.
-----------------------
VERSION 1.x BASIC - $3A
-----------------------
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
VERSION 1.X USERS: If you have the REDIR.400 redirector, you
can use this procedure to upgrade
your network. It is recommended, however,
that you obtain the new version of the
1.x redirector by contacting Beta
Support, whether or not you have
REDIR.400.
NOTE: If you are using 3+Open version 1.x and DOS
version 4.x, you do not need to upgrade your network
files to run with MS-DOS 5.0.
>> Instructions in Brief (for advanced DOS users)
------------------------------------------------
1. Locate the directory on your hard disk containing your
3+Open files.
2. Back up your existing REDIR.EXE file, which is
probably in your 3+Open directory.
3. Copy the DOS version 4.x compatible redirector
(REDIR.400) to the directory containing your 3+Open
files. Name this file REDIR.EXE. If you don't have this
redirector, contact your system administrator or Beta
Support.
4. Upgrade your computer to MS-DOS version 5.0.
>> Complete Instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the WHERE command to your hard disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following command:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Search for the REDIR.400 file on your hard disk by typing
the following command:
WHERE /R \ REDIR.400
If you do not have the file, do not continue this
procedure. Contact Beta Support to obtain the latest
version of this file.
3. Locate each REDIR.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ REDIR.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ REDIR.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the REDIR.EXE file(s)
on your disk. Note the location(s).
4. Back up each of the redirector files by copying it to
a file called REDIR.OLD.
For example, if your REDIR.EXE file is located in the
C:\3OPEN\DOSWKSTA\LANMAN\NETPROG directory, type the
following command (on one line):
COPY C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\REDIR.EXE
C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\REDIR.OLD
Make sure you type the correct drive and directories for
the actual location of the redirector file(s).
5. Copy the REDIR.400 redirector to the directory that
contains your current redirector.
For example, suppose your current redirector and
REDIR.400 are in C:\3OPEN\DOSWKSTA\LANMAN\NETPROG. You
would type the following command:
COPY C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\REDIR.400
C:\3OPEN\DOSWKSTA\LANMAN\NETPROG\REDIR.EXE
Make sure you type the correct drives and directories for
the actual location of the redirector files.
NOTE: If you receive a "File creation error" message when
you try to copy this file, see the
Troubleshooting section later in this document.
5. Upgrade your system to MS-DOS version 5.0
************************************************************
* *
* BANYAN VINES (versions 4.0 and later) - $BV *
* *
************************************************************
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
To use Banyan Vines version 4.0 or later with MS-DOS version
5.0, you need the REDIRALL.EXE or REDIR4.EXE redirector
supplied with your network. If neither or these redirectors
is in the directory containing your Banyan files, ask your
system administrator for the location of one of the
redirectors.
NOTE: If you are using Banyan Vines version 4.0 or later and
DOS version 4.x, you do not need to upgrade your
network files to run with MS-DOS version 5.0.
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the WHERE command to your hard disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following command:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Find out if either the REDIRALL.EXE or REDIR4.EXE file is
on your hard disk. Use the WHERE command, supplied with
MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following commands:
WHERE /R \ REDIRALL.EXE
WHERE /R \ REDIR4.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following commands:
E:\MSDOS\UPGRADE\WHERE /R \ REDIRALL.EXE
E:\MSDOS\UPGRADE\WHERE /R \ REDIR4.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
If either of these files is in the directory containing
your network files, you will not need to make any changes
before installing MS-DOS version 5.0
3. If neither REDIRALL.EXE nor REDIR4.EXE is present on
your system, contact your system administrator to get
these files.
NOTE: Certain applications will not run under MS-DOS
version 5.0 if executed over Banyan network version
4.0 or earlier. The support for these applications
will be available in Vines version 4.1.
NOTE: If you experience problems running Windows 3.0 in 386
Enhanced mode with MS-DOS version 5.0, obtain
a code patch and an updated version of REDIRALL.EXE or
REDIR4.EXE from Banyan.
************************************************************
* *
* IBM PC LAN (versions 1.31 and later) - $PC *
* *
************************************************************
THE INSTRUCTIONS IN THIS SECTION ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF THE FOLLOWING:
* Using DOS to change drives and directories
* Connecting to a network
* Searching a disk for a file
* Searching a file for text
* Editing a text file (in some cases)
To upgrade IBM PC LAN version 1.31 or later, replace your
current REDIR.EXE file with the new version of this file
supplied with MS-DOS version 5.0. You must expand the new
file as you copy it to your hard disk. Rename any DOS
commands in your PC LAN directory. If you are currently
using DOS version 4.x, you need to edit your CONFIG.SYS
file.
>> Instructions in Brief (for advanced DOS users)
-------------------------------------------------
1. If you are installing MS-DOS 5.0 from floppy disks,
copy the EXPAND.EXE file from the Setup disks to
your hard disk. If you have 5.25-inch disks,
EXPAND.EXE is on Disk 5. If you have 3.5-inch disks,
it is on Disk 3.
2. Locate the directory on your hard disk containing
your PC LAN files.
3. Back up your existing REDIR.EXE file, which is
probably in your 3+Open directory.
4. Use the MS-DOS 5.0 EXPAND command to expand and copy
the MS-DOS 5.0 file called REDIR.EX_ to your 3+Share
directory. Syntax:
EXPAND <path>REDIR.EX_ <path>REDIR.EXE
4. If you are upgrading from DOS version 4.x, delete
two lines from your CONFIG.SYS file:
IFS = <path>REDIR.SYS
INSTALL = <path>IFSFUNC.EXE
5. Rename any DOS commands in your PC LAN directory by
giving them the .OLD extension.
6. Copy the same MS-DOS version 5.0 commands to the
PC LAN directory.
7. Upgrade your computer to MS-DOS version 5.0.
>> Complete instructions
------------------------
1. If you are installing MS-DOS version 5.0 from floppy
disks, copy the EXPAND and WHERE commands to your hard
disk:
a) If you are using 3.5-inch disks, insert Disk 3 in
drive A.
Or, if you are using 5.25-inch disks, insert Disk 5
into drive A.
b) Type the following commands:
COPY A:\EXPAND.EXE C:
COPY A:\WHERE.EXE C:
If you are installing MS-DOS from a network, you can skip
step 1.
2. Locate each REDIR.EXE file on your disk by using the
WHERE command, supplied with MS-DOS version 5.0.
For example, if you copied the WHERE command to your hard
disk (in step 1), you would type the following command:
WHERE /R \ REDIR.EXE
Or, suppose you are installing MS-DOS files from a shared
network directory called E:\MSDOS\UPGRADE. You would type
the following command:
E:\MSDOS\UPGRADE\WHERE /R \ REDIR.EXE
(If you have more than one hard disk drive or partition,
change to each drive and repeat the WHERE command to
search every drive on your disk.)
DOS displays the location(s) of the REDIR.EXE file(s)
on your disk. Note the location(s).
3. Back up each of the redirector files by copying them to
a file called REDIR.OLD.
For example, if your REDIR.EXE file is located in the
C:\PCLP directory, type the following command:
COPY C:\PCLP\REDIR.EXE C:\PCLP\REDIR.OLD
Make sure you type the correct drive and directories for
the actual location of the redirector file(s).
4. Use the Expand command to expand and copy the MS-DOS
version 5.0 redirector file (called REDIR.EX_) to the
directory (or directories) containing your old redirector
file(s). Make sure you name the new file REDIR.EXE.
For example, suppose you are installing MS-DOS 5.0 from
floppy disks and your old redirector is in C:\PCLP.
You would insert the floppy disk containing REDIR.EX_
(Disk 3 for 3.5-inch disks or Disk 6 for 5.25-inch disks)
into drive A and then type the following command.
EXPAND A:\REDIR.EX_ C:\PCLP\REDIR.EXE
Or suppose you are installing MS-DOS 5.0 from a network
directory called E:\MSDOS\UPGRADE and your old redirector
is in C:\NETWORK. You would then type the following
command:
EXPAND E:\MSDOS\UPGRADE\REDIR.EX_ C:\PCLP\REDIR.EXE
Make sure you type the correct drive and directories for
the actual location of the new and old redirector
file(s).
NOTE: If you receive a "File creation error" message when
you try to expand this file, see the
Troubleshooting section later in this document.
5. If you were previously running under MS-DOS version
4.0:
a) Use a text editor to open your CONFIG.SYS file.
b) Delete the following lines from CONFIG.SYS:
ifs = <path>\REDIR.SYS
install = <path>\IFSFUNC.EXE
c) Save your CONFIG.SYS (as an unformatted text file)
and exit the editor.
6. The IBM PC LAN Installation program copies several
MS-DOS files into the directory containing your network
files. These files include MODE.COM, PRINT.EXE, and
SHARE.EXE.
Rename any DOS commands in the directory containing your
PC LAN files by giving them the .OLD extension.
For example, to rename the previously mentioned commands,
type the following commands (assuming the directory is
called C:\PCLP):
REN C:\PCLP\MODE.COM C:\PCLP\MODE.OLD
REN C:\PCLP\PRINT.EXE C:\PCLP\PRINT.OLD
REN C:\PCLP\SHARE.EXE C:\PCLP\SHARE.OLD
Make sure you type the correct drive and directories for
the actual location of the old DOS files.
7. Use the Expand command to copy and expand the MS-DOS 5.0
versions of the commands you just renamed (in step 6) to
your PC LAN directory. Follow these steps:
a) If you are installing from floppy disks, use a text
editor to open the file PACKING.LST, which
is located on Disk 1.
b) Look in this file for the disk location of each of the
MS-DOS commands you need to copy to your PC LAN
directory.
c) Expand the files to your PC LAN directory.
8. Upgrade your system to MS-DOS version 5.0
NOTE: If an old version of the SHARE command is present
when you try to start the network with MS-DOS 5.0,
your workstation will hang.
NOTE: To update a PCLP server for MS-DOS 5.0, you must do
the following:
1. Follow steps 1, 2, 3 and 5 in the previous
procedure.
2. Install MS-DOS 5.0 on the server.
3. Using MS-DOS 5.0, type the following command:
SETVER PSPRINT.EXE 3.3
NOTE: You will not be able to use the Print Screen
function under MS-DOS version 5.0 at this time. IBM
will release a new redirector in the near future that
will contain support for this feature.
NOTE: After you install MS-DOS version 5.0, you cannot
install PC LAN with the PC LAN installation program.
************************************************************
* *
* DCA 10NET (versions 3.0 and later) - $DC *
* *
************************************************************
DCA 10Net version 3.0 or later is compatible with
with MS-DOS version 5.0.
NOTE: Although versions 3.0 and later of DCA 10Net are
compatible with MS-DOS version 5.0, some minor
problems were fixed in DCA 10Net version 4.2.
If you are using a version of 10Net before 4.2 and you
load MS-DOS version 5.0 into the high-memory area
(HMA), the 10Net software must be loaded above the
first 64K of memory. You can do this by using the
CONFIG.SYS file to load large enough device drivers,
such as SMARTDRV.SYS or RAMDRIVE.SYS. If you cannot
load 10Net above 64K, do not load MS-DOS into the HMA
or attempt to use the reserved-memory support provided
by EMM386.EXE.
************************************************************
* *
* DEC (PCSA AND LAN WORKS) - $DE *
* *
************************************************************
If you are using Digital Equipment Corporation's PCSA (based
on MS-Net) or LAN WORKS (based on Microsoft LAN Manager),
contact Microsoft beta support to get the compatible
network redirectors for MS-DOS version 5.0.
************************************************************
* *
* ARTISOFT LANTASTIC (versions 2.5 and later) - $AR *
* *
************************************************************
Artisoft LANtastic version 2.5 or later is compatible with
MS-DOS version 5.0.
NOTE: Although versions 2.5 and later of LANtastic are
compatible with MS-DOS version 5.0, some minor
problems were fixed in LANtastic version 3.02.
NOTE: If you currently use LANtastic version 2.x or later,
you can purchase an upgrade from Artisoft. If you
currently use LANtastic version 3.0, this upgrade is
free. Contact the Artisoft Sales Department (to
purchase an upgrade) or the Customer Service
Department (to obtain a free upgrade) at
(602)293-6363.
NOTE: If you are using EMM386.EXE to provide EMS support,
you might need to exclude a memory area by using the
X=<memory-address-range> switch. If you are using
the factory-set defaults for LANtastic, you will need
to exclude the range D800-DFFF. If this memory region
is not excluded, you might experience problems when
using the MS-DOS Shell Task Swapper.
---------------------
TROUBLESHOOTING - $TS
---------------------
RETURNING TO YOUR OLD NETWORK - $RN
-----------------------------------
If you need to return to your old network, remember to
reverse the steps you took during the network-upgrade
process. For example, rename your backup files so they have
the .EXE extensions, where appropriate. If you need
assistance, contact Beta Support.
FILE CREATION ERROR - $FC
-------------------------
If you receive the "File creation error" message when you
try to expand or copy a new network file, your old file(s)
are probably read-only. To remove this read-only protection,
use the ATTRIB command before copying the new file. For
example, suppose you received the error message when you
tried to expand the REDIR.EX_ to
C:\LANMAN.DOS\BASIC\REDIR.EXE. You would type the
following commands before retyping the EXPAND command:
ATTRIB -R C:\LANMAN.DOS\BASIC\REDIR.EXE
INCORRECT DOS VERSION - $IV
---------------------------
If after you follow the instructions in NETWORKS.TXT you
receive the "Incorrect DOS Version" message, you might be
able to use the SETVER command to solve the problem. With
this command, you can report a specific DOS version number
to a program or device driver that requires it. SETVER will
be effective only if the program or device driver is
actually compatible with MS-DOS 5.0.
For more information about the setver command, see the
"Microsoft MS-DOS User's Guide and Reference."
CAUTION: A program you use with SETVER might not have been
verified by Microsoft on MS-DOS version 5.0. Please
contact your software manufacturer for information
on whether the program will operate properly with
MS-DOS version 5.0. If you execute a program by
instructing MS-DOS to report a different DOS
version number, you might lose or corrupt data, or
cause system instabilities. In that circumstance,
Microsoft is not responsible for any loss or
damage.
MEMORY CONFLICTS WITH NETWORK ADAPTER CARDS - $MC
-------------------------------------------------
If you are using EMM386.EXE to provide either expanded
memory (EMS) or access to reserved memory (also known as
upper-memory blocks or UMBs) and you experience problems
with your network, you might need to exclude the memory
address of your network adapter card.
To exclude a memory address, use the X=<memory-address-
range> switch on the device command line for EMM386.EXE.
For more information about this switch, see the "Microsoft
MS-DOS User's Guide and Reference."
To determine the memory address range to exclude, see the
documentation that came with your network adapter card. If
you have an IBM PS/2-compatible computer, you can use the
reference diskette to locate the memory address range your
network card is using.
Some common memory address ranges are:
C000-C7FF
C800-CFFF
D000-D7FF
D800-DFFF
NETWORKS THAT USE EXPANDED OR EXTENDED MEMORY - $EM
---------------------------------------------------
Some of the network software that is explicitly designed to
make use of extended or expanded memory might not work with
MS-DOS version 5.0.
CONFLICTS WITH THE MS-DOS SHELL TASK SWAPPER - $SH
--------------------------------------------------
Some earlier versions of some network software might not
work when you enable the Task Swapper in MS-DOS Shell. If
you experience difficulties, disable the Task Swapper.
IDENTIFYING YOUR VERSION OF LAN MANAGER OR 3+OPEN - $V?
-------------------------------------------------------
If you are Microsoft LAN Manager or 3Com 3+Open, but you're
not sure which version, follow these steps to find out:
1. At the command prompt, type the following command:
NET
If DOS displays the message "Command does not exist,"
you are running a BASIC version.
If the Net program appears on your screen, you are
running an ENHANCED version. In this case,
exit the Net program and continue to the next step.
2. If you are using ENHANCED version:
a) Change to the directory that contains your
LANMAN.INI file.
b) Type the following command:
FIND "DOMAIN" LANMAN.INI
If DOS does not find the string "DOMAIN", then type
the following command (the search is case-
sensitive):
FIND "domain" LANMAN.INI
c) If "DOMAIN" or "domain" is in the file, you are
running version 2.x ENHANCED.
If neither "DOMAIN" nor "domain" is in the file,
you are running version 1.x ENHANCED.
If you are using BASIC version, you might be able to
determine whether you are running 1.x or 2.x by trying a
few network commands. Some configurations will display
the version number when commands are run. If this
doesn't work, check the dates of your network files by
changing to the directory containing those files and
typing the DIR command. If the files are dated mid or
late 1990, you are probably using version 2.x BASIC.
Otherwise, you are probably running version 1.x BASIC.
DOS5B_2.ZIP
README.TXT
This file provides information about the following topics:
Notes on Setup
Creating the Uninstall disk(s)
A directory called OLD_DOS is created by Setup
Setup may create multiple OLD_DOS directories
Using CLEANUP to remove old DOS information
Old LINK.EXE versions may be left in path
WINA20.386 file
Manually Unpacking MS-DOS 5.0 files
Setting up MS-DOS 5.0 on OS/2 systems
Running the upgrade on an OS/2 system
MS-DOS 5.0 and OS/2 dual boot
Notes on Windows 2.x
Running Windows/286 with MS-DOS 5.00
Using Windows 2.1 run-time applications with MS-DOS 5.0
Notes on Windows 3.x
Windows 386 debugger and MS-DOS 5.00
Running Windows 3.0 real mode in an enhanced mode window
The SETVER command
Disk Partitioning Software
Identifying the Disk Utility
Upgrading to MS-DOS 5.0
Upgrading Disk Manager
Upgrading SpeedStor
Upgrading Multivol or Volume Expansion
Upgrading Vfeature Deluxe
Hard drive partitions with logical sectoring
Making your hardware compatible with MS-DOS 5.0
Intel Aboveboard
HP Vectra CS Model 20
Logitech C7 mouse
Adaptec controller boards
101-key keyboards and Qbasic/Edit
Corel Systems drives
Plus Development Hardcard II
Video 7 video cards
ProComm Floppy Drives
Making your software compatible with MS-DOS 5.0
Soft Ice by Nu-Mega
Software Carousel
Metro and Displaywrite III
MS-DOS Multitasking Software
Asynchronous I/O and DOSSHELL.EXE task switching
Gazelle Systems QDOS II
Microsoft CodeView 3.0
Raid and MS-DOS 5.0
Quarterdeck Manifest
Quarterdeck QEMM
Kingston Memory Board EMS driver
Software that accesses extended memory via INT 15
386 To The Max (386MAX)
Tandy Deskmate
Northnet Atlast!
PC-Tools Backtalk
Microsoft CD-ROM extensions
Softlogic Solution's Disk Optimizer
Mountain High's autorun.exe
Borland's Turbo Debugger 386
For more information about Upper Memory Block support, see the UMB.TXT
file. For more information about Networks, see the NETWORK.TXT file.
NOTES ON SETUP-------------------------------------------------------------
CREATING THE UNINSTALL DISK(S)
If you use a bad disk to create the Uninstall disk during Setup,
you may not be able to successfully uninstall MS-DOS 5.0. Be sure to use an
unformatted or newly formatted disk.
A DIRECTORY CALLED OLD_DOS.1 IS CREATED BY SETUP
A directory called OLD_DOS.1 is created by Setup during the installation
of MS-DOS 5.0. The files in this directory, in combination with the files
on your Uninstall disk, can be used to restore your old DOS.
Do not remove or alter the OLD_DOS.1 directory on your hard disk if you
think you might reinstall your old DOS. After you remove the directory,
reinstalling your old DOS is not possible. You can delete the OLD_DOS.1
directory at any time by typing CLEANUP at the command prompt.
SETUP MAY CREATE MULTIPLE OLD_DOS DIRECTORIES
If you upgrade to MS-DOS 5.0 more than once, without using CLEANUP to
delete previous OLD_DOS directories, a new directory will be created each
time you upgrade. Subsequent OLD_DOS directories will be named OLD_DOS.2,
OLD_DOS.3, and so on.
If you have run the upgrade several times on the same system and have
created several Uninstall disks in the process, be sure to use the most
recent Uninstall disk to recover your system.
USING CLEANUP TO REMOVE OLD DOS INFORMATION
After you have used MS-DOS 5.0 and are confident that you will not need
to restore your previous version of DOS, you can use the CLEANUP program to
remove your old DOS from your hard disk. To remove the old DOS from your
hard disk, type CLEANUP at the command prompt, press ENTER, and follow the
directions.
You will not be able to restore your previous DOS after running CLEANUP.
OLD LINK.EXE VERSIONS MAY BE LEFT IN PATH
If you are running a compiler and it fails, you may have an old version
of LINK.EXE in your DOS subdirectory. MS-DOS Setup puts the DOS directory
at the front of the path in your AUTOEXEC.BAT file. The LINK.EXE file that
was in the DOS directory before you installed MS-DOS 5.0 may be put ahead
of the location of the LINK.EXE file you want to use.
LINK.EXE is not shipped with MS-DOS 5.0.
WINA20.386 FILE
When installing upon systems capable of running Windows in Enhanced mode
MS-DOS 5.00 will place a read only file called WINA20.386 in the root
directory. This file provides support for Windows when it is running in the
enhanced mode and has to stay in the root.
MANUALLY UNPACKING MS-DOS 5.0 FILES:
Files on MS-DOS 5.0 master disks that have extensions ending with an
underscore (_) are in a compressed format. To retrieve a single file from
the MS-DOS 5.0 master disks, use the EXPAND utility located on Disk 5.
Syntax: expand [drive1:][path1]infile [drive2:][path2]outfile
[drive1:][path1]infile Specifies the location and name of the
compressed file you want to expand
[drive2:][path2]outfile Specifies the destination and new name
of the expanded file
Example: expand a:\redir.ex_ c:\dos\redir.exe
SETTING UP MS-DOS 5.0 ON OS/2 SYSTEMS----------------------------------
RUNNING THE UPGRADE ON AN OS/2 SYSTEM
If you install the upgrade over IBM OS/2 1.0 you will not be able to
uninstall. This is not a problem for MS OS/2 1.0 or for IBM and MS OS/2
1.1 and later versions. You can work around this by renaming the IBM OS/2
1.0 system files, IBMBIO.COM and IBMDOS.COM, to something else so the setup
program does not confuse them with DOS system files
If you run the uninstall on a system which had OS/2 on it before the
upgrade running chkdsk may show some lost extended attributes. This will
happen whenever a file which had extended attributes under OS/2 was altered
under dos before the uninstall
MS-DOS 5.0 AND OS/2 DUAL BOOT
OS/2 1.1 and Compaq OS/2 1.21 dual boot installation programs don't work
with MS-DOS 5.00. MS OS/2 1.21 dual boot works fine.
NOTES ON WINDOWS 2.X-------------------------------------------------------
RUNNING WINDOWS/286 WITH MS-DOS 5.0
If you run Windows/286 on a computer with MS-DOS 5.0, you will need to
run COMMAND.COM from a program information file (PIF). Winoldapp allocates
only about 39K for the COMMAND.COM file, which is not enough for the MS-DOS
5.0 COMMAND.COM.
USING WINDOWS 2.1 RUN-TIME APPLICATIONS WITH MS-DOS 5.0
If you are using Windows 2.1 run-time applications, there may be older,
incompatible, versions of SMARTDRV.SYS and HIMEM.SYS on your hard disk.
An older version of SMARTDRV.SYS will cause an "Incorrect DOS version"
error message to appear on your screen, and SMARTDrive will not install.
An older version of HIMEM.SYS will cause the run-time application not to
run, and may cause other incompatibility problems.
Be sure to change your CONFIG.SYS file so the SMARTDRV.SYS and HIMEM.SYS
files supplied with MS-DOS 5.0 are used instead of those supplied with your
Windows application.
NOTES ON WINDOWS 3.X-----------------------------------------------------
WINDOWS/386 DEBUG VERSION AND MS-DOS 5.0
If you are running the debug version of Windows/386 with DOS=LOW, the
DOS segment will be below the BIOS segment, causing your system to fail.
Call Microsoft Product Support Services at (206)454-2030 for a solution to
this problem.
RUNNING WINDOWS 3.0 REAL MODE IN AN ENHANCED MODE WINDOW
If your computer hangs or gets an application error when running win /r in
an Enhanced Mode VM, it may help if you remove the line "ebios=*EBIOS" in
the 386ENH section of the SYSTEM.INI file. However, this may make it
impossible to run other programs after exiting.
THE SETVER COMMAND---------------------------------------------------
With the SETVER command, you can control what version MS-DOS reports to
certain programs. SETVER "fools" programs that rely on a certain version
of DOS into running under MS-DOS 5.0.
DISK PARTITIONING SOFTWARE-------------------------------------------
MS-DOS 5.0 Setup may not be able to directly upgrade your hard disk
if one of the following disk utilities was used to set up hard disks
on your system:
Manufacturer Name Device Driver
---------------------------------------------------------------------
Ontrack Disk Manager DMDRVR.BIN
Storage Dimensions SpeedStor SSTOR.SYS or HARDRIVE.SYS
Golden Bow Systems Vfeature Deluxe FIXT_DRV.SYS
Hewlett-Packard MultiVol MULTIVOL.SYS
Hewlett-Packard Volume Expansion HARDRIVE.SYS
If MS-DOS 5.0 Setup detects a disk partition created by one of the
above utilities, it will refuse to upgrade your hard disk
automatically. In order to install MS-DOS 5.0, follow the detailed
steps outlined below.
IDENTIFYING THE DISK UTILITY
You may already know which disk utility was used to set up your hard
disk. If not, look in your CONFIG.SYS file for one of the device
driver names in the above table. For example, if the line
"DEVICE=SSTOR.SYS" appears in your CONFIG.SYS file, the SpeedStor
disk utility was used to set up your hard disk. If you find
HARDRIVE.SYS in your CONFIG.SYS file, you must determine whether
the device driver came from Hewlett-Packard (HP DOS 3.3) or Storage
Dimensions.
UPGRADING TO MS-DOS 5.0
Procedures to determine whether you can upgrade your system and to
carry out the upgrade vary between the disk utilities. Each is
discussed separately below.
Note: MS-DOS 5.0 Setup requires at least 2.5 MB of free space in
your boot partition (drive C). If you have a very small boot
partition, you may need to repartition your hard disk to create a
larger boot partition before upgrading to MS-DOS 5.0.
Setup utility comments out the device driver line in your CONFIG.SYS
file after the installation is successfully completed.
UPGRADING DISK MANAGER
If you are currently running DOS version 4.0 or 4.01, you can upgrade
your hard disk to MS-DOS 5.0 by running Setup with the /u switch, as
follows:
setup /u
If you are running an earlier version of DOS, you should contact
Microsoft Beta support for DOS 5.0 compatible disk manager drivers
(provided to MS by Ontrack systems).
UPGRADING SPEEDSTOR
If you are currently running DOS version 4.0 or 4.01, you should have
no difficulty upgrading to MS-DOS 5.0 by running setup with the /u
switch, as follows:
setup /u
If you are running an earlier version of DOS, you should contact
Microsoft Beta support for DOS 5.0 compatible disk manager drivers
(provided to MS by storage dimension).
UPGRADING MULTIVOL or VOLUME EXPANSION
These disk utilities were distributed with HP DOS versions 3.2 and
3.3. Hewlett-Packard recommends that you repartition and reformat your
hard disk with MS-DOS 5.0, eliminating the need for MultiVol or
Volume Expansion. To do this, carry out the following steps:
* Install MS-DOS 5.0 on floppy disks. You can do this by running
MS-DOS 5.0 Setup. Although Setup will refuse to upgrade your hard
disk, it will install DOS on floppy disks.
* Back up your hard disk using the HDBACKUP program provided with MS-DOS
5.0 or some other backup utility. The program HDBACKUP.EXE can be found
on UPGRADE DISK 1 and can be run by typing in HDBACKUP at the A:> prompt.
Backups created this way can be restored with the dos RESTORE command.
* Boot from the MS-DOS 5.0 startup floppy disk you created.
* Run FDISK.
* Delete non-DOS partitions.
* Create new partitions.
* From the MS-DOS 5.0 floppy disk, run FORMAT to format each new
partition.
* Restart your system from the hard disk (remove floppy disks from
drives first).
* Run MS-DOS 5.0 Setup. Setup will upgrade your hard disk.
* Restore the files from the deleted partitions, using the backup
copies you created.
UPGRADING VFEATURE DELUXE
Current versions of Vfeature Deluxe is not compatible with MS-DOS
5.0. Golden Bow Systems is planning to upgrade the software to take
advantage of MS-DOS 5.0 advanced features. Contact Golden Bow system
for information about Vfeature upgrades. Until the upgrade is
available, you can install MS-DOS 5.0 on floppy
disks. However, you may not be able to access your hard disk while
running MS-DOS 5.0.
HARD DRIVE PARTITIONS WITH LOGICAL SECTORING---------------------------
If the version of DOS you were using before upgrading to dos 5 used
logical sectoring partitions that were larger than 32MB on the hard drive
you should never boot with your previous dos and then access the hard drive.
Because dos 5 upgrade has changed the structure of your hard drive partition
doing this could very easily destroy information on the drive. At this point
in time we know that NEC, Toshiba, Wyse and Zenith Dos' use logical sectoring
on large hard drive partitions. This is by no means a complete list and will
be enlarged.
MAKING YOUR HARDWARE COMPATIBLE WITH MS-DOS 5.0----------------------------
INTEL ABOVEBOARD
If you have an Intel Aboveboard in your system you will need to run Intel's
Aboveboard setup program after installing dos 5 in order to access the memory
on the board. This needs to be done because the Dos 5 installation program
overwrites the Aboveboard's initilization information which is stored on your
harddrive.
HP VECTRA CS MODEL 20
The Hewlett Packard portable Vectra CS Model 20 requires a 1.44Mfloppy
in drive A at boot time for MSDOS FORMAT, DISKCOPY and DISKCOMP to recognize
the drive as a 1.44MB floppy drive. Failure to do so will make FORMAT,
DISKCOPY and DISKCOMP think that the drive is a 720K floppy drive and prevent
their proper operation with 1.44MB floppies. Hewlett Packard's version of
MS-DOS 5.0 will not have this requirement.
LOGITECH C7 MOUSE
If you are unable to use a Logitech C7 mouse, contact the company to
obtain an updated mouse driver. You will need to get version 5.0 or later.
ADAPTEC CONTROLLER BOARDS
If you are using an Adaptec controller board with two hard drives
attached and are using expanded memory (EMS), you may need to obtain
Adaptec's adaptec.sys device driver. For more information, contact your
Adaptec dealer or distributor or call Adaptec's technical support
hotline at 408/945-2550.
101-KEY KEYBOARDS AND QBASIC/EDIT
If you are unable to use the arrow keys on your numeric keypad when
running Qbasic or EDIT, Microsoft offers a TSR called FIXSHIFT.COM which
may help. To obtain FIXSHIFT.COM call Microsoft Product Support at
(206)454-2030
COREL SYSTEMS DRIVERS
If you are having trouble with a Corel System driver for a large
capacity drive (WORM, Winchester, etc.) you may need to obtain an updated
driver from Corel Systems.
PLUS DEVELOPMENT HARDCARD II
If you are having trouble with Plus Development's Hardcard II when
running EMM386.EXE, you will need to add the option X=D700-D7FF on the
DEVICE= line for EMM386.
VIDEO 7 VGA CARDS
If you are having trouble with MS-DOS Shell and the Microsoft mouse when
using a Video7 VGA card, it may help if you use the /Y option on the mouse.
PROCOMM FLOPPY DRIVES
If you have trouble with ProComm floppy drives you may need to obtain
an updated driver from ProComm.
MAKING YOUR SOFTWARE COMPATIBLE WITH MS-DOS 5.0----------------------------
SOFT ICE BY NU-MEGA
If you are using Nu-Mega's Soft Ice program you should not load it after
HIMEM.SYS on a Compaq system when you are using SMARTDRV.SYS. Soft Ice can
corrupt the disk cache in this situation, resulting in a corrupted hard drive.
SOFTWARE CAROUSEL
Software Carousel will lock up when running under MS-DOS 5.0 unless
SETVER has been used to report version 4.00 to it.
Example: SETVER C: CAROUSEL.EXE 4.00
LOTUS METRO, LOTUS EXPRESS, AND IBM DISPLAYWRITE III
These software packages do not support the extended ROM BIOS for 101-key
keyboards. If you have trouble with them, add the following line to your
CONFIG.SYS file and restart your computer:
SWITCHES=/K
This will instruct MS-DOS 5.0 not to use the extended ROM BIOS. The
applications will work, but you will not be able to access the F11 or F12
keys through MS-DOS.
MS-DOS MULTITASKING SOFTWARE:
If you are using software that provides multitasking support for MS-DOS,
do not enable the switcher in MS-DOS Shell. The multitasking system and
MS-DOS SHELL task swapping are likely to conflict.
ASYNCHRONOUS I/O and DOSSHELL.EXE TASK SWITCHING
The MS-DOS Shell task switcher does not support switching of programs
performing asynchronous communications. This includes all terminal
emulation software such as SmartCom, Procomm Plus, and server/client
software such as Laplink and Blast. The MS-DOS Shell task switcher should
not be enabled if you are using asynchronous communications programs.
GAZELLE SYSTEMS QDOS II:
QDOS II is a DOS version-specific application. Only versions of QDOS II
that support MS-DOS 4.xx will work correctly with MS-DOS 5.0.
MICROSOFT CODEVIEW 3.00:
If you are using Microsoft Codeview 3.0 to debug applications that use
expanded memory, and are using the EMM386.SYS memory manager of MS-DOS 5.0
in AUTO mode, you may experience some problems. Whenever using Codeview to
debug EMS applications you should either turn EMM386 on before debugging or
use the /d or /e switches on Codeview 3.0.
RAID AND MS-DOS 5.O (IBETA)
If you are a raid user and are upgrading from MS-DOS 3.x, copy the
NISAMR.EXE file from \\dos5server\beta. If you are upgrading from DOS 4.x,
you probably have this file and will not need to get it.
QUARTERDECK MANIFEST:
Versions of this application previous to 1.01 are closely tied to
internals specific to earlier versions of DOS and do not work with MS-DOS
5.0. Quarterdeck Manifest v1.01 will work on MS-DOS 5.00. For an upgrade to
v1.01 contact Quarterdeck
QUARTERDECK QEMM
Versions of Qemm prior to 5.11 have problems when the HIMEM.SYS file is
loaded with the /INT15=xxxx option. Add the QEMM option MEMORY=yyyy to the
DEVICE=QEMM.SYS line in your CONFIG.SYS file, where yyyy = xxxx - 64. Or
can update your Qemm to version 5.11.
The buffers program supplied with some versions of Qemm should not be
used with MS-DOS 5. If you were using this program previous to upgrading to
MS-DOS 5.0 you will need to increase your dos BUFFERS= line in your
config.sys. We suggest BUFFERS=20 as a new setting.
KINGSTON MEMORY BOARD EMS DRIVER:
The Kingston EMSDRVR.SYS driver is incompatible with the MS-DOS 5.0
HIMEM.SYS file. You can use the MS-DOS 5.0 EMM386.SYS file to access EMS
memory instead of the Kingston diver.
SOFTWARE THAT ACCESSES EXTENDED MEMORY VIA INT 15
Some software that uses extended memory, such as Paradox, Oracle, QEMM,
or Turbo EMS, does so using interrupt 15. To use this type of software
with MS-DOS 5.0 loaded high, you can use the HIMEM.SYS /INT15=xxxx switch.
The /INT15 switch allocates the specified amount of extended memory for
the INT15h interface.
It may also be necessary to use options on the particular software to
specify the amount of extended memory accessible through INT15. This can
be done using the /M switch with Turbo EMS, and the MEMORY option
with QEMM.
386MAX:
In some cases, after loading a program high with 386LOAD.COM, the loaded
program will report "Incorrect DOS version." If this occurs use the SETVER
command to set the version number for 386MAX to the lower version required
by the program reporting the error.
If a program is loaded high using 386LOAD.COM, the DOS version number
reported by SETVER will not be passed to it by 386MAX . This happens
because the 386MAX reports the version it sees to programs that have been
loaded high, not the version they see.
WARNING: After this has been done, all programs loaded by 386LOAD.COM
will be reported this new version number
The Maxhi.exe program supplied with versions of 386MAX prior to 5.0
should not be used with MS-DOS 5.0 as it will cause the machine to hang.
TANDY DESKMATE
Versions of Deskmate prior to 3.0.2 incorrectly calculated disk space
size for large disks. If problems occur writing files to a disk because
Deskmate reports that there is not enough disk space, contact Tandy to get
the most recent version of Deskmate.
NORTHNET ATLAST!
If you experience problems with Northnet's Atlast! upper memory manager,
contact Northnet for an upgrade.
PC-TOOLS BACKTALK
Loading PC-Tools Backtalk into upper memory blocks with the LOADHIGH
command may cause your machine to hang. Usually this will only happen if
you have filled up the rest of the UMB space with other device drivers and
TSR's. You should load Backtalk in conventional memory and fill the UMB
space with other device drivers or TSR's.
MICROSOFT CD-ROM EXTENSIONS
While any version of MSCDEX.EXE that worked under MS-DOS 4.x will
function in most situations under MS-DOS 5, there are known problems with
MSCDEX.EXE when using it with the /s option to run a CD-ROM drive as a
network server. This function will not work in MS-DOS 5.00 until a new
version of MSCDEX.EXE is written.
SOFTLOGIC SOLUTION'S DISK OPTIMIZER
Versions of Softlogic Solutions Disk Optimizer prior to 4.05 would give
the message "File Allocation Table Contains Invalid Information. Run
CHKDSK". If you encounter this problem you will need to contact Softlogic
for an upgrade.
MOUNTAIN HIGH'S AUTORUN.EXE
If you experience problems with autorun.exe, a tape drive backup program
written by Mountain High, you will need to contact the company to obtain
an upgrade
BORLAND'S TURBO DEBUGGER 386
Borland's Turbo Debugger 386 is configuration dependent and will need to
be reinstalled after upgrading to MS-DOS 5.00 or you may experience machine
hangs while running the debugger.
DOS5B_3.ZIP
UMB.TXT
HOW TO OPTIMIZE MEMORY WITH UMBS
*************************************************************
* *
* BEFORE YOU BEGIN *
* *
* * Print this file (UMB.TXT). *
* *
* * You'll need an 80386 or 80486 processor with *
* at least 350K of XMS memory. *
* To determine how much XMS memory is available, *
* type MEM at the command line. If less than 350K, *
* you need to free up XMS memory before continuing *
* (See "Troubleshooting"). *
* *
* * Backup your CONFIG.SYS and AUTOEXEC.BAT files *
* on a startup floppy disk. If you don't have *
* this disk already: *
* 1. Insert a floppy disk into drive A. *
* 2. Type FORMAT/S A: and press ENTER. *
* 3. Type COPY C:\CONFIG.SYS A:\CONFIG.SAV *
* and press ENTER. *
* 4. Type COPY C:\AUTOEXEC.BAT A:\AUTOEXEC.SAV *
* and press ENTER. *
* *
*************************************************************
THE INSTRUCTIONS IN THIS DOCUMENT ARE INTENDED FOR USERS WHO
HAVE A BASIC KNOWLEDGE OF MS-DOS. YOU SHOULD BE ABLE TO OPEN
AND EDIT FILES, UNDERSTAND THE CONTENTS OF CONFIG.SYS AND
AUTOEXEC.BAT FILES, AS WELL AS THE FUNCTION OF DEVICE DRIVERS,
MEMORY MANAGERS, AND TSRS.
NOTE: When you use the commands in the instructions, be sure
to type the correct drives and directories for your
configuration. What you actually use might differ
from what is shown in the instructions. The commands
in the instructions are examples only.
-------------------
Contents of UMB.TXT
-------------------
* Optimizing Memory with UMBs
Setting Up UMB Support
Viewing UMBs
Optimizing UMB Usage
Windows 3.0 and UMBs
* Troubleshooting
* Networks and UMBs
* Alternate Memory Managers
------------------------------------------
Optimizing Memory with Upper Memory Blocks
------------------------------------------
With MS-DOS 5.0 you can increase the amount of conventional memory
that your computer has available for running applications. Conventional
memory is the first 640K of memory automatically used by MS-DOS and
your applications. Above 640K there's additional memory space called
reserved memory that contains Upper Memory Blocks (UMBs). Reserved
memory is set aside for use by your computer, but typically, some is
left unused. With MS-DOS 5.0 you can free up conventional memory by
moving some device drivers and programs (TSRs) into upper memory.
This new feature of MS-DOS 5.0 requires an 80386 or 80486 processor
with at least 350K of XMS memory available.
=================================
Setting Up MS-DOS 5.0 UMB Support
You set up UMB support by including new commands in your CONFIG.SYS and
AUTOEXEC.BAT files. If you don't have a high-memory manager you install
one first. Then you'll revise commands to place your device drivers
and programs (TSRs) into UMBs.
NOTE: If you are using an alternate memory manager, see the "Alternate
Memory Managers" section at the end of this document.
------------------------------------------------------------
| |
| SUMMARY FOR ADVANCED USERS |
| -------------------------- |
| If you find this summary procedure too abbreviated, |
| see the detailed procedure immediately following. |
| |
| To use UMBs: |
| ------------ |
| |
| 1. Edit your CONFIG.SYS to include the following: |
| |
| device=c:\dos\himem.sys |
| dos=umb |
| device=c:\dos\emm386.exe noems |
| |
| (If CONFIG.SYS already contains the EMM386 line, |
| add RAM at the end: device=c:\dos\emm386.exe ram) |
| |
| 2. For device drivers you want in upper memory, replace |
| DEVICE= with DEVICEHIGH=. |
| |
| 3. For programs in your AUTOEXEC.BAT file that you |
| want in upper memory, add LOADHIGH (or LH): |
| |
| LH <program name> |
| |
| 4. Restart your computer. |
| |
------------------------------------------------------------
NOTE: Some drivers and programs might be incompatible with MS-DOS 5.0.
A list of the drivers and programs that shipped with MS-DOS follows the
next procedure. If you have trouble installing drivers and programs in
upper memory, see the "Troubleshooting" section later in this document.
To set up UMB support and load drivers and programs:
----------------------------------------------------
1. Use MS-DOS EDITOR to open your CONFIG.SYS file by entering:
edit c:\config.sys
Or you can use any other text editor, but you must save your
CONFIG.SYS file as a text-only file.
2. Make sure your CONFIG.SYS file contains the following lines, in the
following order:
device=c:\dos\himem.sys
dos=umb
device=c:\dos\emm386.exe noems
* The first command gives MS-DOS access to extended memory.
* The second command places MS-DOS into the upper memory area.
* The third command installs the EMM386 memory manager. If the
emm386 line already appears, add RAM to it as follows:
device=c:\dos\emm386.exe ram
3. After the DEVICE= line for EMM386, replace DEVICE= with the
following to place device drivers in UMBs:
devicehigh=
For example, to load ANSI.SYS in upper memory, you would change
DEVICE=C:\DOS\ANSI.SYS to DEVICEHIGH=C:\DOS\ANSI.SYS.
4. Save your CONFIG.SYS file as a text file.
5. Use MS-DOS EDITOR to open your AUTOEXEC.BAT file by entering:
edit c:\autoexec.bat
Or you can use any other text editor, but you must save your
AUTOEXEC.BAT file as a text-only file.
6. Add LOADHIGH to programs you want to place in UMBs.
For example, to load the PRINT command in upper memory, you would change
PRINT to LOADHIGH PRINT. (Or use LH, the abbreviation for loadhigh.)
7. Save your AUTOEXEC.BAT file as a text-only file.
8. Restart your computer.
SAMPLE CONFIG.SYS FILE
----------------------
dos=high
files= 50
buffers=30
device=c:\dos\himem.sys
dos=umb
device=c:\dos\emm386.exe noems
devicehigh=c:\dos\ansi.sys
devicehigh=c:\dos\printer.sys
devicehigh=c:\dos\smartdrv.sys 2048 512
SAMPLE AUTOEXEC.BAT FILE
------------------------
echo on
loadhigh c:\MOUSE1\mouse
cls
break=on
path=c:\dos;C:\WINDOWS;c:\util;
prompt=$p$g
set TEMP=C:\WINDOWS\TEMP
loadhigh doskey
loadhigh mode
loadhigh append
loadhigh dosshell
The following drivers are shipped with MS-DOS 5.0 and are safe to
load in UMBs:
EGA.SYS DISPLAY.SYS ANSI.SYS
RAMDRIVE.SYS SMARTDRV.SYS DRIVER.SYS
PRINTER.SYS
The following MS-DOS 5.0 programs are safe to store in UMBs:
DOSKEY.COM DOSSHELL.COM KEYB.COM
GRAPHICS.COM NLSFUNC.EXE MODE.COM
SHARE.EXE PRINT.EXE APPEND.EXE
You might have OTHER drivers and programs that you'd like to place in
UMBs. Some of these might not be compatible with the MS-DOS 5.0 UMB
feature. If you have trouble, see the "Troubleshooting" section later
in this document.
For more information about running device drivers and programs from
upper memory, see Chapter 12 of the MS-DOS 5.0 USER'S GUIDE.
============
Viewing UMBS
You can determine which programs and are loaded into UMBs by
first typing the EMM386 command to see where UMBs start, and then using
the MEM/DEBUG (or MEM/Program) command to see how UMBs are used.
Using the EMM386.EXE Memory Manager
-----------------------------------
If you type EMM386.EXE at the command line, you'll see something
similar to the following:
MICROSOFT Expanded Memory Manager 386 Version 4.20.06X
(C) Copyright Microsoft Corporation 1986, 1990
Expanded memory services unavailable.
Total upper memory available . . . . . . . . .0 KB
Largest Upper Memory Block available . . . . .0 KB
Upper memory starting address . . . . . . . . C800 H
EMM386 Active.
The information above shows no upper memory available. That's because
all upper memory has been allocated for use by MS-DOS.
NOTE: If you are using Windows, make sure you exit before attempting
this procedure. If you don't exit first, you'll see the following
message: EMM386 driver not installed.
Using MS-DOS Commands
---------------------
To view memory usage:
--------------------
* Type MEM/DEBUG|MORE and press ENTER.
To print memory usage output to a printer:
------------------------------------------
* Type MEM/DEBUG|PRINT and press ENTER.
To print memory usage output to a file:
---------------------------------------
* Type MEM/DEBUG> mem.txt
The "Upper memory starting address" is the first segment in
which UMBs are located. You'll see something like the following:
Address Name Size Type
------- -------- ------ ------
000000 000400 Interrupt Vector
000400 000100 ROM Communication Area
000500 000200 DOS Communication Area
000700 IO 000A80 System Data
CON System Device Driver
AUX System Device Driver
PRN System Device Driver
<.. removed lines here to shorten output ..>
01A990 MSDOS 085650 -- Free --
09FFF0 MSDOS 028010 System Program
0C8010 MSDOS 000130 -- Free --
0C8150 MSDOS 000AE0 -- Free --
0C8C40 XNSBIOS 000120 Environment
0C8D70 XNSBIOS 002610 Program
0CB390 SESSION 000120 Environment
0CB4C0 PRTSC 000120 Environment
0CB5F0 PRTSC 000320 Program
0CB920 DOSKEY 000FE0 Program
0CC910 MIRROR 001990 Program
0CE2B0 MOUSE 003830 Program
0D1AF0 MSDOS 0064E0 -- Free --
0D7FE0 MSDOS 008020 System Program
0E0010 IO 001500 System Data
RAMDRIVE 0004A0 DEVICE=
D: Installed Device Driver
ANSI 001040 DEVICE=
CON Installed Device Driver
0E1520 SESSION 000410 Program
0E1940 REDIR 0093E0 Program
0EAD30 MSDOS 0052C0 -- Free --
656384 bytes total conventional memory
655360 bytes available to MS-DOS
625664 largest executable program size
4194304 bytes total contiguous extended memory
0 bytes available contiguous extended memory
3124224 bytes available XMS memory
MS-DOS resident in High Memory Area
Given the upper memory starting segment of C800 reported by EMM386, you
should examine the MEM/DEBUG output for any address greater than or equal
to C8000. Anything with "-- Free --" in the type column is available
UMB memory. Anything with a name other than MSDOS is a program or device
driver running in a UMB. In the example, XNSBIOS program, XNSBIOS
environment, SESSION, PRTSC, DOSKEY, MIRROR, MOUSE, RAMDRIVE, ANSI,
and REDIR are all running in UMBs.
The size is in hexadecimal. In the example, there are free UMBs at 0C8010
(size:130h), 0C8150 (size:AE0h), 0D1AF0 (size:64E0h), and OEAD30 (size:52C0h).
If you are unfamiliar with the Hex numbering method, you can get a rough
approximation of the UMB size in kilobytes as follows:
(Multiply 10,000 digit by 16) + (Multiply 1,000 digit by 4) + (Divide
100 digit by 400) = K.
Thus, in the example, the UMB at location OEAD30, size 52C0, is
(5*4)+(2/4)=20.5K.
====================
Optimizing UMB Usage
UMB usage with MS-DOS 5.0 requires an in-depth understanding of memory.
The following information is meant for experienced MS-DOS users only.
You can control how UMBs are used in two ways:
* Load order
* Load contents
If you have enough upper memory space to load all your device drivers
and programs high, then optimization is easy: simply load them all in
upper memory. If you don't have enough space, then optimizing is
considerably more difficult. You'll need to use the EMM386 and MEM/DEBUG
commands to see which UMBs are available and then decide what to load high.
Device drivers are loaded into the largest available UMB. That UMB is
reduced in size by the amount of space the device driver requires.
Thus, if a large network file is started in your AUTOEXEC.BAT, you might
not want to load smaller device drivers into upper memory since they
might reduce the size of the UMB so much that there won't be room for the
large network file. It will probably take some trial and error to achieve
the most optimal solution.
EMM386 and the E000 Segment
---------------------------
If you are certain that your system doesn't use the memory segment from
E000 to EFFF after initialization, you can include it by adding
I=E000-EFFF to the EMM386 line in your CONFIG.SYS file.
Check your hardware manual or ask your manufacturer to find out
whether or not this area is available. Or you can experiment by editing
your CONFIG.SYS to include it. Then remove it if you have trouble.
======================================
Windows 3.0 and MS-DOS 5.0 UMB Support
MS-DOS 5.0 UMB support works great with Windows 3.0, but programs must
be loaded high before starting Windows.
---------------
Troubleshooting
---------------
When you restart your computer after editing your CONFIG.SYS and
AUTOEXEC.BAT files, watch the messages carefully. If you see a
message indicating a problem loading a device or starting a program,
edit the appropriate startup file (CONFIG.SYS or AUTOEXEC.BAT). In
the CONFIG.SYS change the DEVICEHIGH= back to DEVICE= for the affected
driver. In your AUTOEXEC.BAT remove LOADHIGH for the affected program.
When you restart your computer, the device or program you changed
will be loaded low and the problem should be corrected.
If your system hangs after you restart it, note the messages you see.
Use this information to identify the driver or program that is causing
the problem. Use the startup disk (system disk) you created during
the UMB setup procedure to restart your computer. Then move drivers back
to conventional memory one at a time until your system starts properly.
==================
Potential Problems
* Not enough XMS memory available.
If MEM reports that less than 350K of XMS memory is available,
you can increase XMS by reducing the size of your RAMDRIVE or
the amount of memory used by EMM386.
* Device drivers that grow during initialization.
DOS ensures that the UMB contains enough room for the device driver
file. However, if the device driver grows larger than its file size
during initialization, loading high might not be possible. If you
suspect this problem, use the SIZE option on the DEVICEHIGH= line
to specify the required size for the device driver. The size must
be specified in . The line should be in the form:
DEVICEHIGH=<driver name> SIZE=hhhh path
where hhhh is a hexadecimal number. You can determine the final
size of a device driver with the MEM /DEBUG or MEM /PROGRAM command.
However, some device drivers can grow and then shrink before finishing
initialization. There is no easy way to determine the necessary size
for this type of device driver.
* Programs that make assumptions about memory available above them.
Some programs assume that there is always memory above them (up to
a 64K boundary for example). These programs can have trouble when
loaded into a UMB. The solution is to load them low.
* Programs that get confused by addresses >640K.
These programs must be loaded low.
* Programs/hardware that cause RAM to appear after EMM386 finishes
its ROM/RAM scan.
Some hardware/software maps memory into reserved address space when
software is loaded. Since EMM386 has already completed it's ROM/RAM
scan and determined that no memory is there, EMM386 will be mapping
a UMB into the address. When the other program causes other memory
to be mapped to the same address, you'll have problems. To solve,
edit the EMM386 line to include the X= option and exclude specific
regions from consideration for UMBs.
For example:
device=c:\dos\emm386.exe noems x=d800-dfff
This line causes EMM386 to exclude the area from segment D800 to DFFF.
==============
Other Problems
Problem: I think I have set up my system for UMBs, but when I use MEM/D,
nothing seems to be loaded in upper memory.
What to check:
1. That you included DOS=UMB in your CONFIG.SYS.
2. That EMM386 is loaded with UMB support (run EMM386 from the
command line and check the "Starting Upper Memory Address").
Note that MEM will not report memory above 640K if you run it
from Windows 3.0 in 386 enhanced mode. Make sure that you
specified either NOEMS or RAM in the DEVICE=EMM386.EXE line
in your CONFIG.SYS.
3. Ensure that you specified DEVICEHIGH for device drivers and
put LOADHIGH (or LH) in front of the programs and TSRs.
4. Ensure that the EMM386.EXE line appears after the HIMEM.SYS
line in your CONFIG.SYS.
5. For device drivers, ensure that the device driver line
in the CONFIG.SYS file appears after the EMM386 line.
Problem: I have a device driver or TSR whose size appears to be small
enough to fit into an available UMB, yet it is still loaded low.
What to check:
Look at the file size of the device driver. Some device drivers
shrink after initialization. Before attempting to load a device
driver into a UMB, MS-DOS checks the driver file size and makes
sure there's enough space available in the UMB.
To correct the problem, you need more memory space for the
driver. Try putting DEVICEHIGH= for that driver ahead of
other drivers you're loading into upper memory.
Problem: My system hangs intermittently.
Solution:
Edit the DEVICE=EMM386.EXE line in your CONFIG.SYS by inserting
REM before DEVICE=. Restart your computer. If your system works
without problem, then the trouble is related to EMM386 UMBs.
Remove REM from the DEVICE=EMM386 command and insert it in
front of DOS=UMB. Restart your computer.
If the problem persists, you need to exclude some memory.
Consult your hardware manual to see what range you can exclude.
Add X=<memory range> to the end of the EMM386 line. You might
need to try several ranges before your computer starts properly.
If the problem does not persist when you include REM DOS=UMB,
one of your device drivers or programs is not loading properly.
You can correct the problem by returning the problem drivers
and programs to low memory. One at a time, change the DEVICEHIGH=
line back to DEVICE= and remove LOADHIGH from programs. Restart
your computer after each change. Repeat the procedure until
the problem stops.
If you notice that the size of a program or driver is smaller
when loaded into a UMB than when it is loaded low, the program
tried to grow beyond its allocated UMB when it moved into upper
memory. (You can check for size variations by using the MEM /P
command, first loading the driver or program low, and then
in UMBs.) To correct the problem, you need more memory space
for the program or driver. Try putting the DEVICEHIGH= or
LOADHIGH command ahead of commands for other drivers or
programs you're loading into upper memory.
Problem: I receive the "UNABLE TO CREATE PAGE FRAME" message when using
the RAM option with EMM386.
Solution: Use the NOEMS option instead of RAM. EMM386 is unable to find
the 64K contiguous space in reserved memory that is required
to create a page frame.
-----------------
Networks and UMBs
-----------------
The procedures that follow are somewhat abbreviated. If you are
unfamiliar with modifying your network configuration, please ask
your Network Administrator (or consultant) for assistance.
Network programs tend to require a significant amount of memory. By moving
network programs into UMBs, you can free up substantial space in lower
memory. The following sections describe how to load some of the
major networks into UMBs. If your network isn't covered here, please
contact your network vendor for the proper procedures.
If you're not sure which network you're using, see the NETWORKS.TXT
file in the same directory as UMB.TXT for instructions.
NOTE: Before using the following procedures, complete the "Setting Up
UMB Support" section earlier in this document.
====================
MS-NET-type Networks
Most MS-NET based redirectors are loaded with the NET command. Check
your AUTOEXEC.BAT file (or other file that you use to start the
network) for a command similar to:
NET START <other...>
where <other ...> indicates that the text following START is not important
to this procedure.
Edit the NET START line as follows:
loadhigh net start <other...>
Restart your computer and watch the messages that appear to ensure that
the network loads without problem. You can use the MEM command to see
how much memory you now have available.
LANMAN 1.x/2.x Basic
--------------------
The redirectors for the Basic version will often fit into a UMB. To load
them high, add the word LOADHIGH before NET START as follows:
loadhigh net start <other...>
Restart your computer and watch the messages that appear to ensure that
the network loads without a problem. You can use the MEM command to see
how much memory you now have available. For information on using MEM,
see the "Viewing UMBs" section earlier in this document.
LANMAN 1.X/2.X Enhanced
-----------------------
With the enhanced version of LANMAN (2.0b and earlier), you can free
the most lower memory by instructing the network to use LIM memory
as follows.
1. Make sure the EMM386 command line in your CONFIG.SYS appears as follows:
device=c:\dos\emm386.exe ram
2. Locate the LANMAN.INI file that is used to start your network.
3. Find the LIM= line and, if necessary, edit it to appear as follows:
LIM=YES
4. Save LANMAN.INI and restart your network.
NOTE: If you receive the UNABLE TO CREATE PAGE FRAME message when you
restart your network, EMM386 is unable to find the 64K of contiguous
space in reserved memory that's required to create a page frame.
You need to remove the RAM option from the EMM386 line (step 1) and
add NOEMS. This prevents EMM386 from attempting to use expanded memory.
Then edit your CONFIG.SYS and AUTOEXEC.BAT (or the batch file you use
to start your network) to load the network drivers low. Next you need
to use the Setup Disk that came with your computer system to reconfigure
your hardware so that a 64K page frame is free, if possible. Then you can
return the RAM option and try loading network drivers into upper memory.
If you are unable to create a 64K block, comment out the LIM=YES line
in LANMAN.INI, replace RAM with NOEMS on the EMM386 line, and load drivers
other than LANMAN in upper memory.
=================================
Loading Novell Networks into UMBs
Insert LOADHIGH (LH) in front of your network startup command whether you
include it in your AUTOEXEC.BAT or type it at the command line.
For example, if you are using NET5.EXE to start Novell, your AUTOEXEC.BAT
(or other batch file) command will appear as follows:
loadhigh net5
Or you could type the same command on the command line.
---------------------------
Alternate Memory Managers
---------------------------
If you are using an alternate memory manager, you can let it handle
loading device drivers and programs into upper memory. Memory managers
from alternate vendors will be recognized by MS-DOS if their drivers
support allocating UMBs from extended XMS memory.
However, if you want to use the MS-DOS 5.0 LOADHIGH and DEVICEHIGH
commands instead, you need to make the following changes:
1. Edit your CONFIG.SYS file to include DOS=UMB.
2. Replace the alternate commands for loading high with the MS-DOS 5.0
DEVICEHIGH and LOADHIGH commands.
You might want to refer to the "Setting Up UMB Support" section for
detailed instructions about editing CONFIG.SYS and using the high memory
commands.
DOS5.ZIP [A Review Of The Beta Dos 5.00 By Y. Barbero.]
DOS5.TXT
NOTES ON DOS FIVE by Yves Barbero I finally bit the bullet and had a look at a DOS version past the very satisfactory DOS 3.3. DOS 4.X had a buggy reputation and I avoided it. But, increasingly, many of my clients would buy 4.01 so I figured I'd better scope out the changes. I jumped a step and obtained a copy of DOS 5.0 in Beta version. I carefully backed up my hard disk, replaced the Speedstor partitions with DOS partitions (after re-initializing the HD since FDISK wouldn't remove my "non-DOS" partitions -- but maybe I missed a beat on that one) and restored my files. [Note: I used Backit4 for this operation. Not a lost byte of the 90 megabytes of data despite its speed and compression. I recommend using the Super Verify mode for such a potentially terminal situation. On my reasonably fast 286, it doesn't take that much longer. The backup took around an hour. The restore was somewhat faster. Good program.] I then installed five using the fairly straightforward SETUP program. It's almost intuitive and not half bad. Not having seen much of four, I hesitate to compare it. I find it generally satisfactory and certainly no threat to my consulting business. I went from a vague understanding of HIMEM, SMARTDRV and RAMDRIVE systems to a very specific one in under an hour. The documentation which comes with the Beta version is sketchy and I didn't have it all. Playing around in the configuration file, I came up with this: - device=c:\dos\himem.sys dos=high device=c:\dos\smartdrv.sys 640 device=c:\dos\ramdrive.sys 128 /e device=c:\everex\emm.sys c800 258,00 device=c:\dos\ansi.sys BUFFERS=20 FILES=49 SHELL=C:\DOS\COMMAND.COM C:\DOS\ /P /E:230 stacks=0,0 BREAK=ON lastdrive=h I have an old Everex board from which I get my EMM.SYS but the rest is pretty straight forward. The order is important and I recommend the one I have. The only casualty was Datamorphics' excellent DiskCache. It can't operate with HIMEM properly. Microsoft has again bludgeoned the opposition (and not with a better product but with one which eliminates the opposition by being incompatible). Why, for instance, does RAMDRIVE* only allow me 64 files? With the Datamorphics system, I could put the ram disk right in my cache and only have one device driver. Still, it is nice to be able to put most of DOS in high memory and gain (in my case) 25K of ram. Microsoft seems to be on a campaign to replace a number of existing programs but their DOSSHELL, as good as it is, doesn't hold a candle to any of the XTREE products and their EDIT, while handy, doesn't compare with the shareware QEdit. On the other hand, the ANSI.SYS seems to handle my VGA well and I was able to dump the VEGAANSI that I was using. Screen graphics of a more generic variety is to be preferred. On a couple of occasions, I've found the colors and other settings I designed at my home office have changed when I went to a client's computer. Like WINDOWS, DOS 5.0 is designed for an easy user interface and as with WINDOWS, the first time user would have to be lucky in his/her setup. Most dealers install 4.X so it goes into DOSSHELL and that isn't the most efficient use of five. Most of the time, clients claim something is too slow and I fine tune the configuration file to get it up to snuff. I've seen a number of machines which have four or more megs of RAM on the floor and absolutely no device drivers to access them. In one case, the guy had lived with it for almost a year. This is a bit like flying a 747 with one engine. He only called when he couldn't get an upgrade of 123 to work. I think there's a lot of room for third party programs with this version and certainly the potential of work for us consultants in the fine tuning of systems whose owners don't crack a manual. Still, Microsoft did come out with a nice product this time. It has a better potential than WINDOWS 3.0 so the hype will probably be less. *RAM disks are mostly unnecessary with modern fast computers but its hard to get out of old habits. Since I teach DOS basics, I use one. I also partition my hard disk to teach about logical drives. Generally, its best to avoid a RAM disk if you have a newer 286 or better and partitions are not necessary with DOS 4.X or better unless you need a UNIX partition or somesuch. Yves Barbero 1073 Dolores Street San Francisco, CA 94110 (415) 285-4358 �
DOS50.ZIP [Upcomming Enchancements In Dos 5.0.]
DOS50.DOC
What will be new with DOS 5.00?
Well, DOS 5.00 will probably be out by the end of 1990, and you
are probably anxious to know what is new. Most people either don't
know what is new, or "can't tell you". I'll tell you all I know (and
whatever I can make up). Maybe I shouldn't be telling anyone, but no one
knows who I am so it doesn't matter.
Anonymous User
Changes/Additions:
1. DOS can now load itself into the first 64K of Extended memory if
you have it. You must have the line, "DOS=HIGH" in your config.sys
and you must have at least 64K of extended memory available. This
will only work on AT machines since 8088/8086 processors can only
address up to 1 Megabyte of memory, and Extended Memory begins at
1 Meg. Loading DOS high will free up quite a bit of valuable
conventional memory.
2. The QuickBasic interpreter is included along with GWBasic.
3. The Shell program (DOSSHELL) has been completely changed. It now
resembles the "File Manager" Program that comes with Windows or
OS/2. DOSSHELL can be run in either graphics or text mode, in
color or black and white. The F1 key brings up online help.
4. If the environment variable "TEMP" is set, DOS will use the
directory set in "TEMP" to write temporary files for piping
operations. If there is no "TEMP" directory set, the current
directory is used.
5. If the environment variable "DIRCMD" is set, DOS uses it for
all "DIR" commands. For example, if "DIRCMD=/W", when you type
"DIR", DOS would act like you typed "DIR/W" (Wide display).
6. A short help screen is available for all DOS commands by adding
a "/?" after the command, for example, "DIR /?" would give you
a help screen for the DIR command.
7. There is a utility called "DOSKEY" that is basically a command
line editor that lets you backup through your previous DOS
commands. Here is the help screen for DOSKEY:
DOSKEY [/reinstall] [/bufsize=] [/dmacs] [/dhist] [macro=text]
/reinstall Installs a new copy of doskey.
/bufsize= Specifies the size of the command buffer.
/dmacs Displays all macros and lets you redirect them to a file.
/dhist Displays all command lines stored in memory.
8. A program called UNFORMAT is included. It restores a hard drive
to its condition prior to the last FORMAT command.
9. The DIR command now reports how many bytes the files listed
total up to. Here is an example DIR command:
E:\>dir
Volume in drive E is whatever
Directory of E:\
WIERDOS <DIR> 06-28-90 12:42a
DUDE ZIP 724409 07-26-90 10:14p
TMP <DIR> 07-28-90 6:32p
IHATE-U <DIR> 06-28-90 12:42a
MASM EXE 103175 07-31-87 12:00a
STSCFG CFG 2339 04-30-90 1:49a
SD INI 2497 07-13-90 2:52a
FRECOVER DAT 50688 07-14-90 1:25a
8 File(s) 3883108 bytes
21868544 bytes free
E:\>
10. The FORMAT command now supports 2.88 Meg 3.5" diskettes.
Here are the help screens for a few of the DOS commands:
DIR [pathname] [/p] [/w] [/a:attributes] [/o:sortorder] [/s] [/b]
/p Pause after each screen page of display.
/w List Files in columns with up to five filenames on each line.
/a:attributes Displays only files with the attributes you specify.
/o:sortorder Displays files sorted in the specified order.
/s Displays files in the specified directory and all subdirectories.
/b Lists filenames, one per line, without any file information.
FORMAT drive: [/1] [/4] [/8] [/n:sectors] [/t:tracks] [/f:size]
[/b] [/s] [/u] [/v[:label]]
/1 Formats a single side of a floppy disk.
/4 Forces a high-capacity floppy drive to format a 360K Floppy-disk.
/8 Formats eight sectors per track.
/n Specifies the number of sectors per track.
/t Specifies the number of tracks on the disk.
/f Specifies the size of the floppy disk to format.
/b Formats the disk, leaving space to copy an operating system.
/s Copies the operating system files.
/u Specifies an unconditional format for a hard disk.
/v Specifies the volume label.
COPY [pathname1] [pathname2] [/v] [/a] [/b]
/v Verifies sectors written on the target disk.
/a Copies Ascii files.
/b Copies binary files.
BACKUP source destination [/s][/m][/a][/f:size][/d:date][/t:time][/L:pathname]
/s Backs up subdirectories
/m Backs up only those files that have changed since the last backup
/a Adds backed-up files to an existing backup disk
/d:date Backs up only files modified since the specified date
/t:time Backs up only files modified since the specified time
/L:pathname Creates a log entry to record the backup operation
/f:size Formats the target backup disk
RESTORE drive1: [drive2] [pathname] [/s] [/p] [/b:date]
[/a:date] [/e:time] [/l:time] [/m] [/n]
/s Restores all subdirectories.
/p Prompts before restoring read-only files or filed modified
since the backup.
/b Restores only those files last modified on or before date.
/a Restores only those files last modified on or after date.
/e Restores only those files last modified a
/n Restores only those files that no longer exist on the
target disk
MODE - Configure a device.
Device Status: MODE [device] [/sta]
Printer port: MODE LPTn[cols=c] [lines= l] [retry=r]
Serial port: MODE COMm baud=b [data=d] [stop=s] [parity=p] [retry=r]
Display mode: MODE con:[cols=m] [lines=n]
Typematic rate: MODE con [:] [rate=r] [delay=d]
Prepare codepage: MODE device cp prepare=((yyy) [drive:][path]filename
Select codepage: MODE device cp select=yyy
Redirect printing: MODE LPTn[:]=COMm[:]
XCOPY pathname1 [pathname2] [/a] [/d:date] [/e] [/m] [/p] [/s] [/v] [/w]
/a Copy files with archive bit, but don't modify archive bit.
/d Copies source files modified on or after specified date.
/e Copies any subdirectories, even if they are empty.
/m Copy files with archive bit set and clear the archive bit.
/p Prompts before creating a new file in the target directory.
/s Copy directories and subdirectories, unless empty.
/v Verify each file as it is written to the target.
/w Causes xcopy to wait before it starts copying files.
There is also a neat little program included with the beta
version of DOS 5.0 called "Microsoft Infer". I don't know if Infer
will be included with the release version of DOS. Infer tells lots
of useful information about your system, like: Operating System
Version, Machine type, Environment, Processor type, Memory info,
Video Adapter info, Serial/Parallel port info, disk drive info,
and much more. Infer includes a ROM BIOS browser, memory browser,
and several other useful functions.
DOS5BUG.ZIP [Program That Demonstrates & Documents A Bug In Ms-dos Version 5.00's Handling Of Upper Memory Blocks. Dos Programmers, Note]
BUGTEST.COM 文本提取
DOS PROGRAMMERS, NOTE: The purpose of this program is to demonstrate a bug I
have noticed in the way MS-DOS Version 5.00 loads a program into an Upper
Memory Block (UMB). You may want to write a few extra lines of code to
compensate for it. Here is what happens: When a user enters a DOS command
followed immediately by filenames or drive letters in the format "?filename"
(i.e. drive letter followed by a colon), DOS is supposed to encode each drive
letter in the bytes at offsets 5Ch and 6Ch, respectively, in the program
segment prefix (PSP) as the first byte of an unopened FCB. An entry of "A:" is
supposed to give you 01h, "B:" yields 02h, and so forth. However, when MS-DOS
Version 5.00 is running and your program has been loaded into a UMB using the
LOADHIGH or LH command, DOS falls down. The byte at 5Ch always remains a zero
no matter what, and the byte at 6Ch is coded for the *first* drive specified!
(If you specify a second drive, it ends up who-knows-where.) If you enter
"BUGTEST a: b:" under DOS Version 5.00, it will correctly return the specified
drives. But if you enter "LOADHIGH BUGTEST a: b:" instead, you'll notice that
DOS reports no first drive and the wrong second drive. Probably nobody uses
FCBs anymore, but those drive bytes come in very handy sometimes. Grrrrr!
-- Jerry Monroe, CIS # 72321,1257
June 23, 1991
First drive specified: (byte at PSP offset 5Ch = 00h)
Second drive specified: (byte at PSP offset 6Ch = 00h)
DOS5HELP.ZIP [Preliminary Help For Dos 5.0 (3-29-91).]
DOS5.TXT
Allows programs to open data files in specified directories as if they were in
the current directory.
APPEND [[drive:]path[;...]] [/X[:ON | :OFF]] [/PATH:ON | /PATH:OFF] [/E]
APPEND ;
[drive:]path Specifies a drive and directory to append.
/X:ON Applies appended directories to file searches and
application execution.
/X:OFF Applies appended directories only to requests to open files.
/X:OFF is the default setting.
/PATH:ON Applies appended directories to file requests that already
specify a path. /PATH:ON is the default setting.
/PATH:OFF Turns off the effect of /PATH:ON.
/E Stores a copy of the appended directory list in an environment
variable named APPEND. /E may be used only the first time
you use APPEND after starting your system.
Type APPEND ; to clear the appended directory list.
Type APPEND without parameters to display the appended directory list.
Redirects requests for disk operations on one drive to a different drive.
ASSIGN [x[:]=y[:][...]]
ASSIGN /STATUS
x Specifies the drive letter to reassign.
y Specifies the drive that x: will be assigned to.
/STATUS Displays current drive assignments.
Type ASSIGN without parameters to reset all drive letters to original
assignments.
Displays or changes file attributes.
ATTRIB [+R | -R] [+A | -A] [+S | -S] [+H | -H] [[drive:][path]filename] [/S]
+ Sets an attribute.
- Clears an attribute.
R Read-only file attribute.
A Archive file attribute.
S System file attribute.
H Hidden file attribute.
/S Processes files in all directories in the specified path.
Backs up one or more files from one disk to another.
BACKUP source destination-drive: [/S] [/M] [/A] [/F[:size]]
[/D:date[/T:time]] [/L[:[drive:][path]logfile]]
source Specifies the file(s), drive, or directory to back up.
destination-drive: Specifies the drive to save backup copies onto.
/S Backs up contents of subdirectories.
/M Backs up only files that have changed since the last
backup.
/A Adds backup files to an existing backup disk.
/F:[size] Specifies the size of the disk to be formatted.
/D:date Backs up only files changed on or after the specified
date.
/T:time Backs up only files changed at or after the specified
time.
/L[:[drive:][path]logfile]
Creates a log file and entry to record the backup
operation.
Sets or clears extended CTRL+C checking.
BREAK [ON | OFF]
Type BREAK without a parameter to display the current BREAK setting.
Calls one batch program from another.
CALL [drive:][path]filename [batch-parameters]
batch-parameters Specifies any command-line information required by the
batch program.
Displays the name of or changes the current directory.
CHDIR [drive:][path]
CHDIR[..]
CD [drive:][path]
CD[..]
.. Specifies that you want to change to the parent directory.
Type CD drive: to display the current directory in the specified drive.
Type CD without parameters to display the current drive and directory.
Displays or sets the active code page number.
CHCP [nnn]
nnn Specifies a code page number.
Type CHCP without a parameter to display the active code page number.
Displays the name of or changes the current directory.
CHDIR [drive:][path]
CHDIR[..]
CD [drive:][path]
CD[..]
.. Specifies that you want to change to the parent directory.
Type CD drive: to display the current directory in the specified drive.
Type CD without parameters to display the current drive and directory.
Checks a disk and displays a status report.
CHKDSK [drive:][[path]filename] [/F] [/V]
[drive:][path] Specifies the drive and directory to check.
filename Specifies the file(s) to check for fragmentation.
/F Fixes errors on the disk.
/V Displays the full path and name of every file on the disk.
Type CHKDSK without parameters to check the current disk.
Clears the screen.
CLS
Starts a new instance of the MS-DOS command interpreter.
COMMAND [[drive:]path] [device] [/E:nnnnn] [/P] [/C string] [/MSG]
[drive:]path Specifies the directory containing COMMAND.COM file.
device Specifies the device to use for command input and output.
/E:nnnnn Sets the initial environment size to nnnnn bytes.
/P Makes the new command interpreter permanent (can't exit).
/C string Carries out the command specified by string, and then stops.
/MSG Specifies that all error messages be stored in memory. You
need to specify /P with this switch.
Compares the contents of two files or sets of files.
COMP [data1] [data2] [/D] [/A] [/L] [/N=number] [/C]
data1 Specifies location and name(s) of first file(s) to compare.
data2 Specifies location and name(s) of second files to compare.
/D Displays differences in decimal format. This is the default
setting.
/A Displays differences in ASCII characters.
/L Displays line numbers for differences.
/N=number Compares only the first specified number of lines in each file.
/C Disregards case of ASCII letters when comparing files.
To compare sets of files, use wildcards in data1 and data2 parameters.
Copies one or more files to another location.
COPY [/A | /B] source [/A | /B] [+ source [/A | /B] [+ ...]] [destination
[/A | /B]] [/V]
source Specifies the file or files to be copied.
/A Indicates an ASCII text file.
/B Indicates a binary file.
destination Specifies the directory and/or filename for the new file(s).
/V Verifies that new files are written correctly.
To append files, specify a single file for destination, but multiple files
for source (using wildcards or file1+file2+file3 format).
Changes the terminal device used to control your system.
CTTY device
device The terminal device you want to use, such as COM1.
Displays or sets the date.
DATE [date]
Type DATE without parameters to display the current date setting and
a prompt for a new one. Press ENTER to keep the same date.
Runs Debug, a program testing and editing tool.
DEBUG [[drive:][path]filename [testfile-parameters]]
[drive:][path]filename Specifies the file you want to test.
testfile-parameters Specifies command-line information required by
the file you want to test.
After Debug starts, type ? to display a list of debugging commands.
Deletes one or more files.
DEL [drive:][path]filename [/P]
ERASE [drive:][path]filename [/P]
[drive:][path]filename Specifies the file(s) to delete. Specify multiple
files by using wildcards.
/P Prompts for confirmation before deleting each file.
Displays a list of files and subdirectories in a directory.
DIR [drive:][path][filename] [/P] [/W] [/A[[:]attributes]]
[/O[[:]sortorder]] [/S] [/B] [/L]
[drive:][path][filename]
Specifies drive, directory, and/or files to list.
/P Pauses after each screenful of information.
/W Uses wide list format.
/A Displays files with specified attributes.
attributes D Directories R Read-only files
H Hidden files A Files ready for archiving
S System files - Prefix meaning "not"
/O List by files in sorted order.
sortorder N By name (alphabetic) S By size (smallest first)
E By extension (alphabetic) D By date & time (earliest first)
G Group directories first - Prefix to reverse order
/S Displays files in specified directory and all subdirectories.
/B Uses bare format (no heading information or summary).
/L Uses lowercase.
Switches may be preset in the DIRCMD environment variable. Override
preset switches by prefixing any switch with - (hyphen)--for example, /-W.
Compares the contents of two floppy disks.
DISKCOMP [drive1: [drive2:]] [/1] [/8]
/1 Compares the first side of the disks.
/8 Compares only the first eight sectors of each track.
Copies the contents of one floppy disk to another.
DISKCOPY [drive1: [drive2:]] [/1] [/V]
/1 Copies only the first side of the disk.
/V Verifies that the information is copied correctly.
The two floppy disks must be the same type.
You may specify the same drive for drive1 and drive2.
Edits command lines, recalls MS-DOS commands, and creates macros.
DOSKEY [/REINSTALL] [/BUFSIZE=size] [/MACROS] [/HISTORY]
[/INSERT | /OVERSTRIKE] [macroname=[text]]
/REINSTALL Installs a new copy of Doskey.
/BUFSIZE=size Sets size of command history buffer.
/MACROS Displays all Doskey macros.
/HISTORY Displays all commands stored in memory.
/INSERT Specifies that new text you type is inserted in old text.
/OVERSTRIKE Specifies that new text overwrites old text.
macroname Specifies a name for a macro you create.
text Specifies commands you want to record.
UP and DOWN ARROWS recall commands; ESC clears command line; F7 displays
command history; ALT+F7 clears command history; F8 searches command
history; F9 selects a command by number; ALT+F10 clears macro definitions.
The following are some special codes in Doskey macro definitions:
$T Command separator. Allows multiple commands in a macro.
$1-$9 Batch parameters. Equivalent to %1-%9 in batch programs.
$* Symbol replaced by everything following macro name on command line.
Microsoft (R) DOS Version 5.0 MS-DOS Shell
Copyright (c) Microsoft Corp 1991. All rights reserved.
Starts MS-DOS Shell.
DOSSHELL [/T[:res[n]]] [/B]
DOSSHELL [/G[:res[n]]] [/B]
/T Starts MS-DOS Shell in text mode.
:res[n] A letter (L, M, H) and number indicating screen resolution.
/B Starts MS-DOS Shell using black-and-white color scheme.
/G Starts MS-DOS Shell in graphics mode.
Displays messages, or turns command-echoing on or off.
ECHO [ON | OFF]
ECHO [message]
Type ECHO without parameters to display the current echo setting.
Starts the MS-DOS Editor, which creates and changes ASCII files.
EDIT [[drive:][path]filename] [/B] [/G] [/H] [/NOHI]
[drive:][path]filename Specifies the ASCII file to edit.
/B Allows use of a monochrome monitor with a color graphics card.
/G Provides the fastest update of a CGA screen.
/H Displays the maximum number of lines possible for your hardware.
/NOHI Allows the use of a monitor without high-intensity support.
Starts Edlin, a line-oriented text editor.
EDLIN [drive:][path]filename [/B]
/B Ignores end-of-file (CTRL+Z) characters.
Turns on or off EMM386 expanded memory support.
EMM386 [ON | OFF | AUTO] [W=ON | W=OFF]
ON | OFF | AUTO Activates or suspends EMM386.EXE device driver,
or places it in auto mode.
W=ON | OFF Turns on or off Weitek coprocessor support.
Deletes one or more files.
DEL [drive:][path]filename [/P]
ERASE [drive:][path]filename [/P]
[drive:][path]filename Specifies the file(s) to delete. Specify multiple
files by using wildcards.
/P Prompts for confirmation before deleting each file.
Converts .EXE (executable) files to binary format.
EXE2BIN [drive1:][path1]input-file [[drive2:][path2]output-file]
input-file Specifies the .EXE file to be converted.
output-file Specifies the binary file to be created.
Quits the COMMAND.COM program (command interpreter).
EXIT
Expands one or more compressed files.
EXPAND [drive:][path]filename [[drive1:][path1]filename[ ...]] destination
[drive:][path]filename Specifies the location and/or name of a file or
set of files to be expanded. You cannot use
wildcards.
destination Specifies the new location and/or name of an
expanded file or set of files. Destination can be
a drive letter and colon, directory name,
filename, or combination.
The destination can only be a filename if you have specified a single
filename for the source filename parameter. To expand multiple files to a
different directory and keep the original filenames, specify only a
directory as the destination.
Decreases the amount of time needed to open frequently used files
and directories.
FASTOPEN drive:[[=]n] [drive:[[=]n][ ...]] [/X]
drive: Specifies the hard disk drive you want Fastopen to work with.
n Specifies the maximum number of file locations Fastopen retains
in its filename cache.
/X Creates the filename cache in expanded memory.
Compares two files or sets of files and displays the differences between
them.
FC [/A] [/C] [/L] [/LBn] [/N] [/T] [/W] [/nnnn] [drive1:][path1]filename1
[drive2:][path2]filename2
FC /B [drive1:][path1]filename1 [drive2:][path2]filename2
/A Displays only first and last lines for each set of differences.
/B Performs a binary comparison.
/C Disregards the case of letters.
/L Compares files as ASCII text.
/LBn Sets the maximum consecutive mismatches to the specified number of
lines.
/N Displays the line numbers on an ASCII comparison.
/T Does not expand tabs to spaces.
/W Compresses white space (tabs and spaces) for comparison.
/nnnn Specifies the number of consecutive lines that must match after a
mismatch.
Configures a hard disk for use with MS-DOS.
FDISK
Searches for a text string in a file or files.
FIND [/V] [/C] [/N] [/I] "string" [[drive:][path]filename[ ...]]
/V Displays all lines NOT containing the specified string.
/C Displays only the count of lines containing the string.
/N Displays line numbers with the displayed lines.
/I Ignores the case of characters when searching for the string.
"string" Specifies the text string to find.
[drive:][path]filename
Specifies a file or files to search.
If a pathname is not specified, FIND searches the text typed at the prompt
or piped from another command.
Runs a specified command for each file in a set of files.
FOR %variable IN (set) DO command [command-parameters]
%variable Specifies a replaceable parameter.
(set) Specifies a set of one or more files. Wildcards may be used.
command Specifies the command to carry out for each file.
command-parameters
Specifies parameters or switches for the specified command.
To use the FOR command in a batch program, specify %%variable instead of
%variable.
Formats a disk for use with MS-DOS.
FORMAT drive: [/V[:label]] [/Q] [/U] [/F:size] [/B | /S]
FORMAT drive: [/V[:label]] [/Q] [/U] [/T:tracks /N:sectors] [/B | /S]
FORMAT drive: [/V[:label]] [/Q] [/U] [/1] [/4] [/B | /S]
FORMAT drive: [/Q] [/U] [/1] [/4] [/8] [/B | /S]
/V[:label] Specifies the volume label.
/Q Performs a quick format.
/U Performs an unconditional format.
/F:size Specifies the size of the floppy disk to format (such
as 160, 180, 320, 360, 720, 1.2, 1.44, 2.88).
/B Allocates space on the formatted disk for system files.
/S Copies system files to the formatted disk.
/T:tracks Specifies the number of tracks per disk side.
/N:sectors Specifies the number of sectors per track.
/1 Formats a single side of a floppy disk.
/4 Formats a 5.25-inch 360K floppy disk in a high-density drive.
/8 Formats eight sectors per track.
Directs MS-DOS to a labelled line in a batch program.
GOTO label
label Specifies a text string used in the batch program as a label.
You type a label on a line by itself, beginning with a colon.
Enables MS-DOS to display an extended character set in graphics mode.
GRAFTABL [xxx]
GRAFTABL /STATUS
xxx Specifies a code page number.
/STATUS Displays the current code page selected for use with GRAFTABL.
Loads a program that can print graphics.
GRAPHICS [type] [[drive:][path]filename] [/R] [/B] [/LCD]
[/PRINTBOX:STD | /PRINTBOX:LCD]
type Specifies a printer type (see User's Guide and Reference).
[drive:][path]filename
Specifies the file containing information on supported printers.
/R Prints white on black as seen on the screen.
/B Prints the background in color for COLOR4 and COLOR8 printers.
/LCD Prints using LCD aspect ratio.
/PRINTBOX:STD | /PRINTBOX:LCD
Specifies the print-box size, either STD or LCD.
Provides help information for MS-DOS commands.
HELP [command]
command - displays help information on that command.
Performs conditional processing in batch programs.
IF [NOT] ERRORLEVEL number command
IF [NOT] string1==string2 command
IF [NOT] EXIST filename command
NOT Specifies that MS-DOS should carry out the command only
if the condition is false.
ERRORLEVEL number Specifies a true condition if the last program run returned
an exit code equal to or greater than the number specified.
command Specifies the command to carry out if the condition is
met.
string1==string2 Specifies a true condition if the specified text strings
match.
EXIST filename Specifies a true condition if the specified filename
exists.
Joins a disk drive to a directory on another drive.
JOIN [drive1: [drive2:]path]
JOIN drive1: /D
drive1: Specifies a disk drive that will appear as a directory on
drive2.
drive2: Specifies a drive to which you want to join drive1.
path Specifies the directory to which you want to join drive1. It
must be empty and cannot be the root directory.
/D Cancels any previous JOIN commands for the specified drive.
Type JOIN without parameters to list currently joined drives.
Configures a keyboard for a specific language.
KEYB [xx[,[yyy][,[drive:][path]filename]]] [/E] [/ID:nnn]
xx Specifies a two-letter keyboard code.
yyy Specifies the code page for the character set.
[drive:][path]filename Specifies the keyboard definition file.
/E Specifies that an enhanced keyboard is installed.
/ID:nnn Specifies the keyboard in use.
Creates, changes, or deletes the volume label of a disk.
LABEL [drive:][label]
Loads a program into the upper memory area.
LOADHIGH [drive:][path]filename [parameters]
LH [drive:][path]filename [parameters]
parameters Specifies any command-line information required by the
program you want to load.
Loads a program above the first 64K of memory, and runs the program.
LOADFIX [drive:][path]filename
Use LOADFIX to load a program if you have received the message
"Packed file corrupt" when trying to load it in low memory.
Loads a program into the upper memory area.
LOADHIGH [drive:][path]filename [parameters]
LH [drive:][path]filename [parameters]
parameters Specifies any command-line information required by the
program you want to load.
Creates a directory.
MKDIR [drive:]path
MD [drive:]path
Displays the amount of used and free memory in your system.
MEM [/PROGRAM | /DEBUG | /CLASSIFY]
/PROGRAM or /P Displays status of programs currently loaded in memory.
/DEBUG or /D Displays status of programs, internal drivers, and other
information.
/CLASSIFY or /C Classifies programs by memory usage. Lists the size of
programs, provides a summary of memory in use, and lists
largest memory block available.
Records information about one or more disks.
MIRROR [drive:[ ...]] [/1] [/Tdrive[-entries][ ...]]
MIRROR [/U]
MIRROR [/PARTN]
drive: Specifies the drive for which you want to save information.
/1 Saves only the latest disk information (does not back up
previous information).
/Tdrive Loads the deletion-tracking program for the specified drive.
-entries Specifies maximum number of entries in the deletion-tracking
file.
/U Unloads the deletion-tracking program.
/PARTN Saves hard disk partition information to a floppy diskette.
MIRROR, UNDELETE, and UNFORMAT Copyright (C) 1987-1991 Central Point Software,
Inc.
Creates a directory.
MKDIR [drive:]path
MD [drive:]path
Configures system devices.
Printer port: MODE LPTn[:] [COLS=c] [LINES=l] [RETRY=r]
Serial port: MODE COMm[:] [BAUD=b] [PARITY=p] [DATA=d] [STOP=s] [RETRY=r]
Device Status: MODE [device] [/STATUS]
Redirect printing: MODE LPTn[:]=COMm[:]
Prepare code page: MODE device CP PREPARE=((yyy[...]) [drive:][path]filename)
Select code page: MODE device CP SELECT=yyy
Refresh code page: MODE device CP REFRESH
Code page status: MODE device CP [/STATUS]
Display mode: MODE [display-adapter][,n]
MODE CON[:] [COLS=c] [LINES=n]
Typematic rate: MODE CON[:] [RATE=r DELAY=d]
Displays output one screen at a time.
MORE < [drive:][path]filename
command-name | MORE
[drive:][path]filename Specifies a file to display one screen at a time.
command-name Specifies a command whose output will be displayed.
Loads country-specific information.
NLSFUNC [[drive:][path]filename]
[drive:][path]filename Specifies the file containing country-specific
information.
Displays or sets a search path for executable files.
PATH [[drive:]path[;...]]
PATH ;
Type PATH ; to clear all search-path settings and direct MS-DOS to search
only in the current directory.
Type PATH without parameters to display the current path.
Suspends processing of a batch program and displays the message "Press any
key to continue...."
PAUSE
Prints a text file while you are using other MS-DOS commands.
PRINT [/D:device] [/B:size] [/U:ticks1] [/M:ticks2] [/S:ticks3]
[/Q:qsize] [/T] [[drive:][path]filename[ ...]] [/C] [/P]
/D:device Specifies a print device.
/B:size Sets the internal buffer size, in bytes.
/U:ticks1 Waits the specified maximum number of clock ticks for the printer
to be available.
/M:ticks2 Specifies the maximum number of clock ticks it takes to print a
character.
/S:ticks3 Allocates the scheduler the specified number of clock ticks for
background printing.
/Q:qsize Specifies the maximum number of files allowed in the print queue.
/T Removes all files from the print queue.
/C Cancels printing of the preceding filename and subsequent
filenames.
/P Adds the preceding filename and subsequent filenames to the print
queue.
Type PRINT without parameters to display the contents of the print queue.
Changes the MS-DOS command prompt.
PROMPT [text]
text Specifies a new command prompt.
Prompt can be made up of normal characters and the following special codes:
$Q = (equal sign)
$$ $ (dollar sign)
$T Current time
$D Current date
$P Current drive and path
$V MS-DOS version number
$N Current drive
$G > (greater-than sign)
$L < (less-than sign)
$B | (pipe)
$H Backspace (erases previous character)
$E Escape code (ASCII code 27)
$_ Carriage return and linefeed
Type PROMPT without parameters to reset the prompt to the default setting.
Starts the MS-DOS QBasic programming environment.
QBASIC [/B] [/EDITOR] [/G] [/H] [/MBF] [/NOHI] [[/RUN] [drive:][path]filename]
/B Allows use of a monochrome monitor with a color graphics card.
/EDITOR Starts the MS-DOS Editor.
/G Provides the fastest update of a CGA screen.
/H Displays the maximum number of lines possible for your hardware.
/MBF Converts the built-in functions MKS$, MKD$, CVS, and CVD to
MKSMBF$, MKDMBF$, CVSMBF, and CVDMBF, respectively.
/NOHI Allows the use of a monitor without high-intensity support.
/RUN Runs the specified Basic program before displaying it.
[[drive:][path]filename] Specifies the program file to load or run.
Removes (deletes) a directory.
RMDIR [drive:]path
RD [drive:]path
Recovers readable information from a bad or defective disk.
RECOVER [drive:][path]filename
RECOVER drive:
Consult your User's Guide and Reference before using the RECOVER command.
Records comments (remarks) in a batch file or CONFIG.SYS.
REM [comment]
Renames a file or files.
RENAME [drive:][path]filename1 filename2
REN [drive:][path]filename1 filename2
Note that you cannot specify a new drive or path for your destination file.
Renames a file or files.
RENAME [drive:][path]filename1 filename2
REN [drive:][path]filename1 filename2
Note that you cannot specify a new drive or path for your destination file.
Replaces files.
REPLACE [drive1:][path1]filename [drive2:][path2] [/A] [/P] [/R] [/W]
REPLACE [drive1:][path1]filename [drive2:][path2] [/P] [/R] [/S] [/W] [/U]
[drive1:][path1]filename Specifies the source file or files.
[drive2:][path2] Specifies the directory where files are to be
replaced.
/A Adds new files to destination directory. Cannot
use with /S or /U switches.
/P Prompts for confirmation before replacing a file or
adding a source file.
/R Replaces read-only files as well as unprotected
files.
/S Replaces files in all subdirectories of the
destination directory. Cannot use with the /A
switch.
/W Waits for you to insert a disk before beginning.
/U Replaces (updates) only files that are older than
source files. Cannot use with the /A switch.
Restores files that were backed up by using the BACKUP command.
RESTORE drive1: drive2:[path[filename]] [/S] [/P] [/B:date] [/A:date] [/E:time]
[/L:time] [/M] [/N] [/D]
drive1: Specifies the drive on which the backup files are stored.
drive2:[path[filename]]
Specifies the file(s) to restore.
/S Restores files in all subdirectories in the path.
/P Prompts before restoring read-only files or files changed since
the last backup (if appropriate attributes are set).
/B Restores only files last changed on or before the specified date.
/A Restores only files changed on or after the specified date.
/E Restores only files last changed at or earlier than the specified
time.
/L Restores only files changed at or later than the specified time.
/M Restores only files changed since the last backup.
/N Restores only files that no longer exist on the destination disk.
/D Displays files on the backup disk that match specifications.
Removes (deletes) a directory.
RMDIR [drive:]path
RD [drive:]path
Displays, sets, or removes MS-DOS environment variables.
SET [variable=[string]]
variable Specifies the environment-variable name.
string Specifies a series of characters to assign to the variable.
Type SET without parameters to display the current environment variables.
Sets the version number that MS-DOS reports to a program.
Display current version table: SETVER [drive:path]
Add entry: SETVER [drive:path] filename n.nn
Delete entry: SETVER [drive:path] filename /DELETE [/QUIET]
[drive:path] Specifies location of the SETVER.EXE file.
filename Specifies the filename of the program.
n.nn Specifies the MS-DOS version to be reported to the program.
/DELETE or /D Deletes the version-table entry for the specified program.
/QUIET Hides the message typically displayed during deletion of
version-table entry.
Installs file-sharing and locking capabilities on your hard disk.
SHARE [/F:space] [/L:locks]
/F:space Allocates file space (in bytes) for file-sharing information.
/L:locks Sets the number of files that can be locked at one time.
Changes the position of replaceable parameters in a batch file.
SHIFT
Sorts input and writes results to the screen, a file, or another device.
SORT [/R] [/+n] < [drive1:][path1]filename1 [> [drive2:][path2]filename2]
[command |] SORT [/R] [/+n] [> [drive2:][path2]filename2]
/R Reverses the sort order; that is, sorts Z to A,
then 9 to 0.
/+n Sorts the file according to characters in
column n.
[drive1:][path1]filename1 Specifies a file to be sorted.
[drive2:][path2]filename2 Specifies a file where the sorted input is to be
stored.
command Specifies a command whose output is to be sorted.
Associates a path with a drive letter.
SUBST [drive1: [drive2:]path]
SUBST drive1: /D
drive1: Specifies a virtual drive to which you want to assign a path.
[drive:2]path Specifies a physical drive and path you want to assign to
a virtual drive.
/D Deletes a substituted (virtual) drive.
Type SUBST with no parameters to display a list of current virtual drives.
Copies MS-DOS system files and command interpreter to a disk you specify.
SYS [drive1:][path] drive2:
[drive1:][path] Specifies the location of the system files.
drive2: Specifies the drive the files are to be copied to.
Displays or sets the system time.
TIME [time]
Type TIME with no parameters to display the current time setting and a prompt
for a new one. Press ENTER to keep the same time.
Graphically displays the directory structure of a drive or path.
TREE [drive:][path] [/F] [/A]
/F Displays the names of the files in each directory.
/A Uses ASCII instead of extended characters.
Displays the contents of a text file.
TYPE [drive:][path]filename
Restores files which have been deleted.
UNDELETE [[drive:][path]][filename] [/LIST | /ALL] [/DT | /DOS]
/LIST Lists the deleted files available to be recovered.
/ALL Undeletes all specified files without prompting.
/DT Uses only the deletion-tracking file.
/DOS Uses only the MS-DOS directory.
MIRROR, UNDELETE, and UNFORMAT Copyright (C) 1987-1991 Central Point Software,
Inc.
Restores a disk erased by the FORMAT command or restructured by the RECOVER
command.
UNFORMAT drive: [/J]
UNFORMAT drive: [/U] [/L] [/TEST] [/P]
UNFORMAT /PARTN [/L]
drive: Specifies the drive to unformat.
/J Verifies that the mirror files agree with the system information
on the disk.
/U Unformats without using MIRROR files.
/L Lists all file and directory names found, or, when used with the
/PARTN switch, displays current partition tables.
/TEST Displays information but does not write changes to disk.
/P Sends output messages to printer connected to LPT1.
/PARTN Restores disk partition tables.
MIRROR, UNDELETE, and UNFORMAT Copyright (C) 1987-1991 Central Point Software,
Inc.
Displays the MS-DOS version.
VER
Tells MS-DOS whether to verify that your files are written correctly to a
disk.
VERIFY [ON | OFF]
Type VERIFY without a parameter to display the current VERIFY setting.
Displays the disk volume label and serial number, if they exist.
VOL [drive:]
Copies files (except hidden and system files) and directory trees.
XCOPY source [destination] [/A | /M] [/D:date] [/P] [/S [/E]] [/V] [/W]
source Specifies the file(s) to copy.
destination Specifies the location and/or name of new files.
/A Copies files with the archive attribute set,
doesn't change the attribute.
/M Copies files with the archive attribute set,
turns off the archive attribute.
/D:date Copies files changed on or after the specified date.
/P Prompts you before creating each destination file.
/S Copies directories and subdirectories except empty ones.
/E Copies any subdirectories, even if empty.
/V Verifies each new file.
/W Prompts you to press a key before copying.
- Windows 95 Plus! Pack b309
PLUS309A.ZIP
WIN95APP.NFO
Windows 95 Applications: An Open Letter to the Pirate Community ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Windows 95 is the biggest and most exciting development to hit the software scene in years, and everyone wants to jump on the bandwagon. Problem is - there is a lot of misinformation going around regarding the labelling of releases. In the past few months, I have seen many "Windows 95" versions of popular Windows applications floating around, and have downloaded a number of them, only to find that the bulk of them are NOT "Windows 95" versions, but simply the latest version of a Windows 3.1x application. WINDOWS 95 APPLICATIONS ARE 32-BIT APPLICATIONS. They are completely different from 16-bit applications, and Windows 95 users will want to avoid using 16-bit applications as they seriously degrade system performance. If you have a new app to release, label it appropriately - if you're some lame ass group who wants to get more recognition with all your "Windows 95" applications when they turn out to be 16-bit applications, you're just going to show the world that you can't tell the difference between 16 and 32 bit programs. Despite the frustration at finding real Windows 95 applications, I'll continue to release what I can (such as many Windows 95 betas, Plus Packs, Qmodem for Windows 95, Bounds Checker, WinICE, Windows 95 Docs, the Windows 95 Gold, ABC Flow Chart Beta for Windows 95, Micrographix Designer 6.0 Beta for Windows 95, Picture Publisher Beta for Windows 95, and more) to the community at large - the more quality and ACCURATELY LABELLED releases we have, the better it is for all of us.
文件:Windows XP 2462 Anleitung.rtf
- CHGO95.ZIP [Why Windows 4.0 will not be generally available in retail stores until 1995.]
FILE_ID.DIZ
Why Windows 4.0 Will Not be Available Until 1995. Received By: Tic-2-PCB 01-05-94 From:fwos2nfo <DIZ by: PEGASUS Autodiz * 813-481-5575>
CHGO95.TXT
WHY WINDOWS 4.0 WILL NOT BE GENERALLY AVAILABLE IN RETAIL STORES UNTIL 1995 Microsoft has officially said that Windows 4.0 will enter beta testing in February 1994 and be available in the third quarter of 1994. I believe that this schedule is not achievable and that Windows 4.0 will not be generally available in retail stores until 1995. I am presenting the following information to encourage open discussion of this possibility and its implications for business decisions and technical decisions. Here are three reasons: 1. Microsoft consistently underestimated the length of time that would be required to develop Windows NT. Microsoft originally officially forecast that Windows NT would ship (my definition is available for sale in retail stores) by the end of 1992. About the time that Microsoft released the large scale beta test of Windows NT in October 1992, it revised the official forecast ship date to March 1993. This would have been a 6 month beta test. In reality, Windows NT was initially available in August 1993. This was 8 months later than the original forecast and five months later than the revised forecast. 2. Microsoft takes longer (4.5 - 5 months) to debug the results of a large beta test release than IBM takes (3 months). This is also empirical data. The Windows NT beta test lasted 9 or 10 months. There was a large scale beta release in October 1992 and another large scale beta release in March 1993 before general availability in August 1993. The empirical result is that the Windows NT beta test averaged one release every 4.5 to 5 months. The IBM OS/2 2.0 beta test lasted from July 1991 through March 1992, a nine month period. There were three large beta releases. If my memory is correct, these releases were 1) at the beginning of July, 2) sometime in late September or early October 1992 and 3) late December 1992. The OS/2 2.0 beta test averaged one release every three months. The IBM OS/2 2.1 beta test lasted from December 1992 through June 1993. The two beta releases were in December 1992 and March 1993. The OS/2 2.1 beta test averaged one release every three months. 3. Windows 4.0 will be harder for Microsoft to develop and debug than Windows NT was to develop and debug. Windows 4.0, like OS/2 2.X, is a monolithic kernel operating system. Windows NT is a message passing kernel operating system. IBM's Workplace OS is characterized as a microkernel based operating system. Microkernel based operating systems are a type of message passing kernel operating system. For the purpose of this analysis, the key difference between monolithic kernel operating systems and message passing kernel operating systems is that the monolithic kernel is larger and more tightly integrated than the message passing kernel. Some of the functions that are integrated into the kernel of a monolithic kernel operating system are equivalent to "server subsystems" that interface with the kernel in a message passing kernel operating system design . The result is that the monolithic kernel is larger than the message passing kernel and also has more internal interfaces. The advantage of the monolithic kernel operating system is that it requires fewer systems resources and runs faster than the message passing kernel operating system. In the recent testing experience comparing a monolithic kernel operating system (OS/2 2.1) with a message passing kernel operating system (WINNT), the speed difference has been observed even though it has been somewhat obscured by differences in device driver quality between OS/2 2.1 and WINNT. It has also been somewhat obscured by differences in subsystem design, such as WINNT's superior disk caching (which was demonstrated in the PC Magazine benchmarks). The advantage of the message passing kernel operating system design is that it tends to be more robust than the monolithic kernel operating system design. The message passing kernel design should be easier to develop and debug than the monolithic kernel design because the code is more modular due to the server subsystems. Software development focusses on modular design because it allows multiple groups to develop in parallel and because debugging several smaller modules is easier than debugging one larger module. Some users suggest that Microsoft will need to do very little new development and debugging for Windows 4.0. There are two methods suggested that would be shortcuts for the development of Windows 4.0. The shortcut that seems to be most frequently proposed is to scale down Windows NT (i.e. create Windows 4.0 as 'NT Lite'). Microsoft has reportedly considered this approach and chosen not to pursue it. Imagine taking a number of modules, removing a few (e.g. security) and then integrating the remaining modules into a single piece of code. Other than the RAM requirements of the removed modules, it is hard to imagine that the "footprint" that remained could be shrunk very much. Furthermore, it seems unlikely that performance, as it has been measured by most of the singletasking benchmarks today, would be significantly improved. The other shortcut that has been proposed is to use the Windows 3.1(1) code and recompile it with a 32 bit compiler. Windows 3.1 cooperatively (i.e. non-preemptively) multitasks Win16 applications. Windows 3.1 includes no internal support for multiple threads within Windows applications. Thus, an ISV who wishes to write a multithreaded Win16 applications must include a multithreading engine within the application. Few, if any, ISVs have done this. Microsoft has repeatedly described Windows 4.0 (and/or DOS 7) as a preemptive multithreaded multitasking operating system. I do not believe that this is simply a matter of recompiling Windows 3.1 code on a 32 bit compiler. As a final note, Microsoft will be writing a new object oriented user interface (OOUI) for Windows 4.0. This OOUI will compete with the Workplace Shell that is used on OS/2 2.1 and will be used on the COSE Unix implementation. From my personal experience, the Workplace Shell in OS/2 2.0 was buggier than the rest of the operating system. Microsoft will face the challenge of debugging the new OOUI. Conclusion: It will take longer than 10 months, and probably longer than a year, for Microsoft to debug Windows 4.0. The time estimate comes from both the second and third sections above. It will take Microsoft longer to beta test Windows 4.0 than it took IBM to beta test OS/2 2.0. It will take Microsoft longer to beta test Windows 4.0 than it took Microsoft to beta test Windows NT. In the 11/15/93 issue of InfoWorld on page 14, Stuart Johnston's article "Microsoft to show Windows NT running SGI's OpenGL" includes the following quote about the Windows 4.0 testing program: 'Chicago, also called Windows 4.0, entered alpha testing in August. A second alpha will go out next month (note: December 1993), with the formal beta probably beginning in February, Mike Maples, executive vice president of worldwide products said last month.' In the 11/22/93 issue of InfoWorld on page 6, Stuart Johnston's article "Windows 4 supports hot-swapped devices" updates the information from Mike Maples: 'A second alpha is set for December, with the formal beta cycle beginning in February or March, Maples said.' The same 11/22/93 InfoWorld forecasts the general availability as: 'The product is expected to ship next summer, earlier than was expected, Microsoft said. Previously, the company forecast shipment during the second half of 1994.' '"Third quarter is what you should count on," said Mike Maples...' On page 1 of the 12/13/93 issue of PC Week, Amy Cortese's article "Chicago nears 32-bit goal" and subtitled "But developers chafe at looming delays and 16-bit leftovers," is the comment: 'Last week industry analysts reported that Microsoft had pushed back its internal delivery date for Chicago from September 1994 to October or November.' The accompanying graphic titled 'Driving toward Chicago' includes the following timeline for the beta program: February 1994: First beta geared for end users slated for release, featuring the first pass at the final Chicago GUI as well as 32-bit OLE support. May-June 1994: Second beta release expected. October-November 1994: Target date for commercial release, to be followed by "DOS 7," essentially Chicago without the graphical shell. This timeline is an 8 to 9 month beta program with two releases. This forecast is the same timeline as the actual experience with Windows NT. As explained above in section 3 (i.e. reason 3), Windows 4.0 will be more difficult to test and debug than Windows NT was. Unless Microsoft has made significant improvements in its debugging and quality assurance methodology, the actual Windows 4.0 beta program will be longer than this forecast. In other words, if a large scale beta test (tens of thousands of test sites) of Windows 4.0 does not begin until February or March of 1994, it seems difficult to imagine that the product will be available in retail stores by the end of 1994. It looks more and more like it will be available in retail stores towards the end of first quarter 1995. It is even possible that it will not ship until second quarter 1995. During the beta test of OS/2 2.0, Microsoft criticized OS/2 by referring to the difficulty that IBM would have in developing and debugging the first release of a large monolithic kernel preemptive multithreaded multitasking operating system with object oriented user interface. Now it is Microsoft's turn to develop a first release of a monolithic kernel preemptive multithreaded multitasking operating system with object oriented user interface. We will see how well they will match up to IBM's development experience.
- OS2WIN95.RAR [Russian, COMPARISON OF OS/2 Warp AND Windows 95 OPERATING SYSTEMS]
OS2WIN95.TXT
СОПОСТАВЛЕНИЕ ОПЕРАЦИОННЫХ СИСТЕМ OS/2 Warp И Windows 95
Путеводитель по технологии 32-разрядных операционных систем для лиц,
принимающих решения
Реферат для руководства
Настоящий документ предназначен для представления корпоративному лицу,
принимающему решения, выгод системы OS/2 и информации о слабостях
операционной системы Windows 95 (кодовое наименование "Чикаго"). Центром
обсуждения являются ключевые архитектурные, операционные и стратегические
просчеты в современной структуре и стратегии операционной системы Windows 95, и
это те просчеты, которые компания Microsoft либо замалчивала, либо игнорировала в
своих усилиях по маркетингу системы Windows 95 как настольной платформы Windows
"следующего поколения".
Например, вы узнаете следующее:
Почему способность системы OS/2 изолировать индивидуальные 16-разрядные
приложения Windows в их собственных отдельных виртуальных машинах DOS (WM)
обеспечивает уровень перекрестной защиты между приложениями, не достижимый под
Windows 3.1 или Windows 95.
Как эта же самая изоляция позволяет также системе OS/2 обеспечивать полную
многозадачную реализацию 16-разрядных приложений Windows без воздействия на
работу собственных приложений.
Почему важно иметь продуманную Модель Системного Объекта (SOM), и каким
образом реализация SOM в OS/2 соединяет в одно целое интерфейс Оболочки Рабочего
Места (Workplace Shell).
Режимы, в которых реализация виртуальной машины DOS в OS/2 более гибка, чем
соответствующая реализация в Windows 95.
В числе основных разделов:
Архитектурные пороки, которые могут ухудшить стабильность системы Windows 95
при работе с 16-разрядными Windows-приложениями.
Как эти самые пороки вдобавок ограничивают имеющиеся у Windows 95 в настоящее
время многозадачные возможности для смеси типов приложений.
Почему отсутствие Модели Системного Объекта делает "хрупким" интерфейс Windows
95.
Режимы, в которых наследие DOS делает систему Windows 95 негибкой при работе с
16-разрядными драйверами устройств DOS.
В конце каждого раздела проводится прямое сравнение реализации конкретной
подсистемы или характеристики/функции в Windows 95 с соответствующей
реализацией у лидера среди 32-разрядных настольных операционных систем -
Операционной Системы/2 корпорации IBM.
Материал в данном документе основывается на глубоком анализе следующих
несекретных и в настоящее время широко доступных источников: публичные
официальные заявления компании Microsoft в отношении характеристик структуры
Windows 95, различные презентации, данные консультантами отрасли на торговых
выставках и литература из списка на стр.
Система OS/2 - правильное решение
Выбор правильной операционной системы. Во многих отношениях это наиболее важное
решение в области технологии персональных компьютеров, которое вам предстоит
сделать в этом веке. Выберете разумно, и вы будете пожинать успех годами. Плохо
выберете, и тогда можете попасть в кошмар плохо работающего программного
обеспечения и недостаточной вычислительной мощности.
Так что же является разумным выбором в современном запутанном рынке
персональных компьютеров? Ответ прост: это продукт, который лучше всех сохраняет
ваши прежние вложения и в то же время открывает дверь в будущее. Короче говоря,
разумным выбором будет Операционная Система/2.
Операционная система OS/2 - самая популярная в мире 32-разрядная
операционная система для персональных компьютеров IBM и
совместимых с ними
Почему OS/2? Потому что она предлагает наиболее логичный путь модернизации для
современных пользователей персональных компьютеров. Операционная система OS/2
сохраняет в целости ваши вложения в 16-разрядные приложения DOS и Windows,
обеспечивая одновременный доступ в новый мир 32-разрядной, объектно-
ориентированной технологии.
Модернизация до OS/2 - это во всех отношениях выигрышное предложение. Просто
спросите у любого из более чем 5 миллионов пользователей OS/2, т.е. свыше чем в 8
раз большего сообщества, чем у сегодняшнего 32-разрядного предложения компании
Microsoft
- пакета Windows NT. Наши клиенты - это такие же люди, как и вы, которые выросли
из существующих операционных сред DOS и Windows и ищут большего: больше
мощности, больше функциональности, больше стабильности.
С операционной системой OS/2 они нашли мощную комбинацию обратной
совместимости, 32-разрядной производительности, простоты применения, а также
монолитную надежность, которую может предложить только зрелая, установившаяся
операционная системная платформа. С выпуском версии V3 операционная система
OS/2 вступает в свое третье поколение, и репутация этого продукта по надежности и
показателю цена/производительность не имеет себе равных в отрасли персональных
компьютеров.
А что же операционная система Windows 95?
Это вопрос, который смущает умы как лиц, принимающих решения в корпорациях, так
и конечных пользователей. При всей той шумихе в средствах массовой информации,
которая окружает так называемое "новое поколение" Windows компании Microsoft,
многие клиенты чувствуют себя парализованными на момент принятия решения о
покупке операционной системы. Некоторых угнетает боязнь выпасть из общей струи
при ставке на Windows 95.
Так называемое "новое поколение" Windows несколько менее привлекательно, чем тот
образ, в который вас пытаются заставить поверить. В реальности ядро Windows 4.0
вероятнее всего уже работает в персональном компьютере рядом с вами: оно
называется Windows 3. 1 .
Архитектура
Операционная система Windows 95: тот же самый программный код,
другая упаковка
"Как такое могло случиться? Ведь выглядит совершенно по-другому!"
Внешний вид может быть обманчивым. В то время как Windows 95 действительно
может похвастаться совершенно другим пользовательским интерфейсом (подробнее о
нем ниже), снятие с нее слоев графического пользовательского интерфейса (GUI) и
внешней упаковки приведет вас к открытию того факта, что продукт в реальности
весьма похож на Windows 3.1. В действительности система Windows 95 настолько
привержена своему изначальному наследию от DOS/Windows, что сохранила даже ее
наиболее известный порок в рабочих характеристиках - нестабильность.
Например, под Windows 3.1 все программные приложения, а также сам код
операционной системы делят единое адресное пространство памяти. При том, что такая
модель управления памятью увеличивает производительность, в то же время она
означает, что ошибка в любом одном- единственном приложении может потенциально
привести к краху всей операционной системы.
Феномен краха операционной системы часто называют Общим Нарушением Защиты
(Genera) Protection Fault, GPF), и он был хронической болезнью для пользователей
Windows начиная с версии 3.0. Именно в силу этой внутренне присущей архитектурной
слабости система Windows 3.1 приобрела хорошо известную репутацию нестабильной и
ненадежной операционной Среды.
Под Windows 95 сохраняется та же самая модель единого адресного пространства
(так называемая "системная виртуальная машина"), а также продолжает
присутствовать внутренняя слабость в виде оставления ключевых участков кода
операционной системы незащищенными для потенциально сбойных приложений.
Таким образом, те же самые сбои в приложениях, которые приводили к краху
Windows 3. 1 , потенциально способны вывести из строя всю операционную систему
Windows 95.
К чести Microsoft нужно отметить, что компания много сил потратила на устранение
множества ошибок в первоначальном коде Windows 3.1 при подготовке его для
включения в Windows 95. Однако они не в состоянии, избежать внутренне присущих
архитектурных пороков, вводимых единой моделью системной виртуальной машины
Windows 3.1. В результате всегда сохраняется опасность того, что плохо отлаженное
приложение приведет к разрушительному краху системы.
OS/2: тот же самый код, лучшее исполнение
Система OS/2 решает проблему стабильности единичной системной виртуальной
машины, позволяя вам запускать приложения Windows в собственных раздельных
сеансах, или в "VDM " (виртуальных машинах DOS). Таким образом, эффект сбоя
приложения под OS/2 ограничен индивидуальным сеансом. Другие приложения, а
также сама операционная система остаются незатронутыми.
Кроме того, благодаря сохранению большей части из базы кода Windows 3.1 , среда
OS/2 сохраняет высокий уровень обратной совместимости с приложениями и
драйверами устройств Windows 3.1.
Многозадачность
Система Windows 95 - полувытесняющий переключатель заданий?
Одной из наиболее привлекающих покупателей сторон в Windows 95 было обещание
нового поколения 32-разрядных Windows-приложений. Эти приложения должны быть
полностью многозадачными под Windows 95 и иметь доступ к современным методам
улучшения производительности типа много поточности (multithreading).
Давайте определим разницу между вытесняющей и совместной многозадачностью.
Вытеснение - это непроизвольная потеря контроля, с которой должно справиться
приложение. При совместной многозадачности контроль остается за приложением, и
приложению решать, когда его отдать для исполнения других приложений.
Движение к модели вытесняющей многозадачности представляет собой значительный
отход от идеологии Windows 3.1. В этой среде приложения должны "сотрудничать" для
обеспечения многозадачности. Каждое приложение "поддается" операционной системе
таким образом, чтобы последняя могла переключать контроль центрального процессора
персонального компьютера на другое приложение (эту операцию часто называют
"совместной многозадачностью" или "переключением заданий").
Хорошо известен тот факт, что модель "совместной многозадачности" Windows
неэффективна. Она также заставляет программистов писать приложения сложным
образом, снижающим производительность. Поэтому неудивительно, что обещание
компании Microsoft обеспечения полной вытесняющей многозадачности в системе
Windows 95 было торжественно заявлено как одна из наиболее важных характеристик
новой платформы.
Но истина в том, что компания Microsoft не раскрывает всех секретов, когда дело
доходит до описания многозадачной архитектуры Windows 95. В действительности,
пока вы не работаете с 32-разрядными Win32-приложениями, вы не получите выгод от
истинной вытесняющей многозадачности.
Почему? Все из-за сильной опоры системы Windows 95 на 16-разрядный код эпохи
Windows 3.1. Под Windows 95 как 16-разрядные, так и 32-разрядные приложения
опираются на 16-разрядные структуры кода внутри системной виртуальной машины,
т.е. кода, который был перенесен из Windows 3.1.
При том, что разрядность кода сама по себе несущественна, существенной остается
Среда, откуда этот код происходит. Система Windows 3.1 была написана как среда
совместной, а не вытесняющей многозадачности. Когда вы вводите участки такого кода
в вытесняющие условия, где в любое наперед заданное время более чем одна задача
может стремиться получить услуги операционной системы, код может дать сбой.
Для защиты от такого типа "разрушения кода" компания Microsoft установила
последовательный доступ к ключевым участкам инфраструктуры WINDOWS 95:
наиболее примечательны в этом плане подсистемы "ПОЛЬЗОВАТЕЛЬ" (USER,
управление окнами) и GDI (Интерфейс Графического Устройства). Технически такой
подход называется нереентерабельной конструкцией, означающей, что в любое наперед
заданное время только одно приложение может исполняться в таких модулях.
При том, что подобный подход срабатывает для WIN32-приложений, вытесняемых в
любой момент во время их исполнения, он отказывает, как только начинает
исполняться 16-разядное приложение Windows (Win16). На настоящий момент
выпускаемые Win16-приложения нельзя надежным образом вытеснять в ходе их
исполнения. Попытка такого вытеснения при вызове подобным приложением
нереентерабельного 16-разрядного программного модуля может привести к краху
всей операционной системы.
Во избежание этого и для сохранения в результате некоего подобия многозадачности
компания Microsoft реализовала особый механизм блокировки. Названный как
"WinMUTEX", этот механизм препятствует доступу к старому коду в случае
обращения 16-разрядного приложения к сервису системы. Таким образом, только
исполняемое в настоящий момент Win16-приложение имеет доступ к 16-разрядному
коду, а все другие приложения, включая сюда Win32-приложения, "заблокированы" от
исполнения до тех пор, пока 16-разрядное приложение не завершится, и Среда не
сделается безопасной для исполнения следующего задания.
На практике связанный с таким феноменом блокировки ущерб для производительности
минимален для работы исключительно с 32-разрядными приложениями. Однако при
работе в смеси 16-разрядных и 32-разрядных приложений (что является наиболее
вероятной практической ситуацией при предсказуемом отсутствии доступных Win32-
продуктов) подход WinMUTEX становится серьезной проблемой.
Тип приложения
Многозадачность
Win32
Вытесняющая
Win16
Совместная
Смесь Winl6 и Win32
"Полу вытесняющая"
Большинство 16-разрядных Windows-приложений известны своей плохой
управляемостью под Windows 3.1 , и до тех пор, пока они не станут надлежащим
образом управляться под Windows 95, все остальные приложения будут заблокированы
от доступа к функциям USER и GDI (в действительности поражается только 50 % всех
вызовов GDI, однако это наиболее часто встречающиеся функции, поэтому итоговый
результат остается тем же).
В целом эти два компромисса -установление последовательности под системных
доступов и WinMUTEX, - создают нечто, лучше всего описываемое как "полу
вытесняющая" многозадачная среда. В результате в среде совместной многозадачности
появляется узкое место, которому, по-видимому, не должно быть места в системе
Windows "следующего поколения", заявленной как вытесняющая многозадачная для
собственных Win32-приложений .
Система OS/2 - истинное вытеснение для лучшей производительности
Система OS/2 обладает истинной вытесняющей многозадачностью для собственных
приложений с первого дня своего появления. Вне зависимости от состава смеси типов
приложений система OS/2 в состоянии гладко реализовать многозадачность для
десятков одновременно выполняющихся программ, и ее реентерабельные подсистемы
позволяют ей обслуживать многократные одновременные запросы без необходимости в
реализации блокировки типа WinMUTEX.
Вместе с тем благодаря своей способности исполнять 16-разрядные Windows-
приложения в раздельных виртуальных машинах DOS система OS/2 может также
реализовывать вытесняющую многозадачность и на них, чего система Windows 95
сделать не в состоянии. Таким образом, вы можете иметь приложения DOS, Windows
и OS/2, работающие одновременно, бок о бок друг с другом, без какого-либо ущерба
для производительности и все в режиме вытесняющей многозадачности. Эта
возможность, по-видимому, не достижимая для системы Windows 95 без
основополагающих изменений в архитектуре, является хорошим добавлением в
арсенал пользователя высокопроизводительных систем.
Интерфейс
Система Windows 95 - поверхностная красота
Другой важной чертой системы Windows 95, которая привлекла значительное внимание
со стороны отраслевой прессы, является ее новый пользовательский интерфейс.
Термины типа "объектно-ориентированный" и "метафора поверхности рабочего стола"
часто используются для описания этого радикально отличающегося внешнего вида
среды Windows.
Но как и с большинством других обоснований для Windows 95, здесь реальной базой
пользовательского интерфейса программы является не что иное, как расширение того,
что уже присутствовало в системе Windows 3.1. В отличие от истинной объектно-
ориентированной среды, в которой связи между индивидуальными объектами "живые"
и обновляются автоматически, интерфейс GUI Windows 95 статичен. "Объекты" в
рабочем поле Windows 95 - это просто указатели файлов на диске. "Свойства" этих
объектов хранятся в .INI-файлах (для Windows-приложений) или в .PIF-файлах (для
DOS-приложений), и связи между ними (в системе Windows 95 называются
"кратчайшие пути") в той же степени статичны.
Например, если вы создаете кратчайший путь для исполнимого файла и помещаете его
на рабочую поверхность Windows 95, затем переименовываете первоначальную
исполнимую программу, то этот кратчайший путь будет существенно поврежден. Для
его переустановки вам придется воссоздавать кратчайший путь с самого начала.
В истинной объектно-ориентированной среде все связи типа кратчайшего пути должны
обновляться автоматически с помощью основополагающей модели управления
объектами. Система Windows 95 не имеет таких оснований, поэтому связи могут быть
легко прерваны пользователями-новичками, не знакомыми с несовершенствами
интерфейса Windows 95.
Рука об руку с механизмом кратчайшего пути системы Windows 95 идет поддержка
длинных имен файлов и директорий на томах с таблицами размещения файлов (FAT).
Компания Microsoft специально подчеркивает способность системы Windows 95
автоматически преобразовывать длинные имена файлов и директорий в сокращения
формата 8.3 символов для обеспечения совместимости с существующими приложениями
DOS и Windows. Однако похоже, что при этом игнорируется тот факт, что без
основополагающей модели объекта такое использование длинных имен может привести
к опасным последствиям.
Представьте себе, например, неопытного пользователя, который по обнаружении
возможности задавать длинные имена решает "реорганизовать" свой жесткий диск. Он
беззаботно переименовывает директории по своему желанию, не осознавая, что тем
самым разрушает один кратчайший путь за другим. Вдруг ни одно из приложений не
работает, и приходится вызывать сервис обслуживания для восстановления (которое в
ряде случаев может означать переустановку как операционной системы, так и
приложений).
Сама рабочая поверхность стола Windows 95 не является объектом OLE 2.0. Такая
новость сама по себе не звучит угрожающе до тех пор, пока вы не начнете понимать,
какого типа интеграция потеряна из-за этого пропуска в объектной технологии. Этот
недостаток программного продукта означает, что приложение не лучшим образом
интегрируется с рабочим столом и не приобретает никаких преимуществ типа
поддержки функции "тащить и бросать" (Drag'n'Drop).
Провозглашенный компанией Microsoft как одно из наиболее привлекательных для
покупателя преимуществ новый графический интерфейс Windows может в конечном
итоге оказаться одним из его важнейших пороков. Без основополагающей системной
модели объекта, связывающей все воедино, такая новая "оболочка" может стать
кошмаром в обслуживании.
Система OS/2 - объектная ориентация
Оболочка Рабочее Место (Workplace Shell) является истинным объектно-
ориентированным интерфейсом. Положенная в ее основу Модель Системного Объекта
(System Object Model, SOM) настолько просто обеспечивает объектное отслеживание,
что операции типа перетаскивания одной директории в другую не нарушит связей и
других интерфейсных структур. Тем самым она проще как для неопытных
пользователей, так и для специалистов технического обслуживания.
Кроме того, модель SOM позволяет приложениям в полной мере манипулировать
интерфейсом оболочки Workplace. Хорошим примером здесь может служить пакет
cc:Mail для OS/2, который использует модель SOM для гладкой интеграции своих
входящих и исходящих интерфейсов с настольной поверхностью оболочки Workplace.
Такой уровень интеграции не возможен при работе под системой Windows 95,
поскольку ее сама ее оболочка не является объектом.
Поддержка приложений
Система Windows 95 - все еще DOS после всех этих лет
"Система Windows 95 устраняет необходимость в DOS. Это истинная операционная
система. . "
Это один из самых цветистых мифов, окружающих операционную среду Windows 95
компании Microsoft. Компания Microsoft заявляет, что система Windows 95 устраняет
необходимость в DOS, т.е. DOS и Windows теперь полностью интегрированы и старые
обусловленные системой DOS ограничения устранены.
При том, что это правда, что теперь вам не нужно покупать отдельный продукт DOS
для того, чтобы инсталлировать и использовать Windows 95, это ни в коей мере не
устраняет DOS как часть уравнения операционной системы Windows. Система DOS все
еще здесь, прячется в тени. Она просто хорошо замаскирована иным интерфейсом
Windows GUI. И хотя многие из ее функциональных характеристик, включая доступ к
файловой системе, заменены 32-разрядными драйверами Windows 95 VxD
(виртуальные драйверы устройств), у DOS все еще сохраняются возможности
ухудшить среду Windows.
Возьмите, например, драйверы устройств реального режима. Под управлением
DOS/Windows вас вынуждали загружать все драйверы устройств DOS во время
загрузки DOS посредством файла CONFIG.SYS. Эти драйверы затем занимают все
сеансы DOS в 386 Расширенном Режиме Windows, сокращая доступную им обычную
память и ограничивая общую конфигурируем ость архитектуры виртуальных машин
DOS для Windows.
Система Windows 95 страдает от тех же самых ограничений. Любые драйверы
устройств DOS реального режима, к которым вы пожелаете получить доступ из
Windows 95, должны быть загружены посредством CONFIG.SYS в момент начальной
загрузки. Таким образом, если вы хотите получить доступ к некоторому ресурсу,
которому требуется драйвер устройства DOS, вы будете вынуждены заплатить дань в
виде потерь в обычной памяти и потенциальных проблем совместимости по всем
виртуальным машинам DOS системы Windows.
А что сделано в отношении таких капризных приложений, как игры? У системы
Windows 95 имеется специальный сеанс DOS - "Режим одиночного приложения MS-
DOS", в котором такие приложения исполняются без ограничений традиционной
машины DOS (виртуальные вводы/выводы, видеопамять и т.п.). При всем том компания
Microsoft не опубликовала тот факт, что для вызова этого режима вам по существу
требуется отключить Windows 95. Все текущие приложения закрываются, и сам
интерфейс GUI Windows 95 сбрасывается на диск. Весь подобный процесс может
занять порядка минуты в зависимости от скорости используемого аппаратного
обеспечения и количества открытых приложений, что может оказаться довольно
долгими перерывом, особенно если вы пытаетесь закончить ту самую пресловутую
срочную докладную или подгружаете большой файл с хост-системы.
Система OS/2 - выполняет DOS-приложения лучше, чем сама DOS
Система OS/2 действительно устраняет необходимость в DOS. Ее виртуальные машины
DOS полностью конфигурируемы и позволяют вам создавать индивидуальные файлы
CONFIG.SYS и AUTOEXEC.BAT для каждого сеанса DOS. Это важное преимущество
для тех ситуаций, когда единый драйвер устройства или конфигурация резидентных
программ не пригодна для всех виртуальных машин DOS.
Виртуальные машины DOS системы OS/2 также обладают обратной совместимостью
высокого уровня и вдобавок могут быть сконфигурированы для прямого доступа к
аппаратным средствам от приложения, которому это требуется. И если все же
приложение отказывается работать под OS/2, вы всегда можете использовать опцию
"двойной загрузки" для запуска настоящей системы DOS примерно в то же время,
которое требуется для вызова "Режима одиночного приложения MS-DOS" в системе
Windows 95.
Обязательства Независимых Поставщиков Программного
Обеспечения (ISV)
Система Windows 95: головная боль для ISV
Одной областью, в которой компания Microsoft остается в неопределенности - это
вопрос стандартов API. Независимые Поставщики Программного Обеспечения (ISV)
безуспешно борются за фиксацию общей стратегии компании Microsoft в отношении
API. Это в особенности важно для собственного интерфейса API системы Windows 95,
который сам по себе является подмножеством полного Win API, опубликованного почти
два года тому назад и реализованного в системе Windows NT.
Еще более усугубляет ситуацию постоянное обновление компанией Microsoft
спецификации Win32c. Новые API появляются почти каждый месяц, многие из них
расширяют Win32 в части привязывания приложений к платформе Windows 95. Это
обстоятельство тревожит ISV, которые хотели бы писать единые приложения для
Windows, Windows NT и Windows 95. Единственным способом, которым эти ISV могут
писать единые приложения, является обращение к Ядру системы, определение
доступного API и написание двух- или трех путевого программного кода. При
интерфейсах API, все еще находящихся в стадии разнобоя, нет никакой гарантии того,
что много путевой код будет работать.
Для клиента 32-разрядной операционной системы это означает потенциальную
задержку в выпуске Win32-приложений, совместимых с Windows 95. При имеющихся у
системы Windows 95 архитектурных ограничениях в поддержке Winl6-приложений
(особенно в случаях, когда требуются многозадачность и стабильность) отсутствие
Win32-приложений может составить серьезное препятствие в деле широкого внедрения
платформы. Системе Windows 95 нужны Win32-приложения еще до того, как она
серьезно начнет претендовать на место, занимаемое системой Windows 3.1. Но при том
смущении и разочаровании в сообществе ISV может пройти значительное время до
момента, когда появится существенный набор Win32-приложений.
Система OS/2 - состоятельное предложение
В отличие от постоянно меняющейся стратегии API компании Microsoft корпорация
IBM твердо придерживается своих обещаний поддерживать открытые стандарты и
уважать обязательства ISV. У системы OS/2 имеется единый 32-разрядный интерфейс
Presentation Manager API для клиентских и для серверных систем. Функции
приложений, написанные в таком API, будут работать во всех версиях OS/2 для
персональных компьютеров на базе процессоров Intel, а также будут легко
переноситься в более совершенные реализации в будущем (включая OS/2 для
PowerPC).
Система OS/2 в настоящее время располагает более чем 2000 собственных приложений,
и все эти приложения реализуют превосходную многозадачность и производительность.
Выводы
Система OS/2: верный ответ
Как вы можете видеть, операционная система Windows 95 компании Microsoft широка в
заявлениях и несколько узковата в технологии. Но это откровение в действительности
неудивительно, если вы следили за их предложениями программных продуктов в
течение нескольких последних лет. Компания Microsoft имеет репутацию поставок
"косметически усовершенствованных" операционных систем при игнорировании более
важных вопросов, типа надежности, мощности и истинной объектной
ориентированности.
В отличие от этого у корпорации IBM совершенно иная репутация, которая говорит о
приверженности открытым стандартам и учете потребностей клиентов. Это та самая
корпорация, которая разрабатывала передовую технологию OS для больших машин и
миникомпьютерных систем с самого начала информационной эпохи. С системой OS/2
корпорация IBM заложила основание для истинно надежной, высокопроизводительной
вычислительной среды, которая сохраняет в целости ваши вложения и в то же время
открывает дверь в будущее.
Разницу вы можете видеть в таких аспектах, как пользовательский интерфейс системы
OS/2. Оболочка Workplace в соединении с моделью системного объекта (SOM)
обеспечивает истинную объектно-ориентированную вычислительную среду, которая
способна думать за вас и не разрушается при ваших попытках отобрать у нее
мощности. Вместе с тем многозадачность системы OS/2 представляет собой
бескомпромиссный подход в доведении до масс пользователей этих мощных
возможностей. Во всем спектре от собственных приложений OS/2 до надежных Win-
OS/2 виртуальных машин DOS это операционная система, с легкостью исполняющая
ваши самые сложные задания.
Итак, в завершение, разумный выбор очевиден: система OS/2 имеет обратную
совместимость, которую вы хотите заполучить, стабильность и надежность, которые вам
требуются, и тот тип непоколебимой приверженности превосходству в разработках,
который вы можете ожидать от крупнейшей в мире компании в области программного
обеспечения - корпорации IBM. Система Microsoft 95 все больше выглядит как вновь
подогреваемая версия вчерашней технологии, а вовсе не как платформа "Windows
следующего поколения", как это рекламируется компанией Microsoft.
Так что же сказать о системе Windows 95? Хороший вопрос! С одной ногой, все еще
стоящей в могиле DOS/Windows, система Windows 95 -это вчерашняя технология,
приукрашенная, чтобы выглядеть как завтрашняя 32-разрядная операционная система.
Так зачем дожидаться прихода ненастоящей системы? Система OS/2 уже на рынке, и
она представляет настоящее будущее в операционных системах для персональных
компьютеров.
Для оснащения системой OS/2 Warp позвоните по телефону 1-800-IBM-CALL,
либо повидайтесь с вашим местным продавцом программного обеспечения.
Приложение А: Таблицы характеристик для OS/2 и Windows 95
Нижеследующие таблицы подводят итог сопоставления характеристик OS/2 и Windows
95, включая характеристики многозадачности. Среды приложений и прилагаемые
средства повышения производительности.
Сопоставление OS/2 Warp и Windows 95: введение в 32- раз рядную технологию ОС
Сопоставление OS/2 Warp и Windows 95 по архитектуре
Характеристика Warp Windows 95
32-разрядное управление окнами Да Нет1
32-разрядная графическая подсистема Да Нет2
32-разрядная подсистема печати Да Да
32-разрядная подсистема мультимедиа Да Да
32-разрядное ядро Да Да
Заказная пейджинговая виртуальная память Да Да
Поддержка HPSF Да Нет
Не блокируемая входная очередью
(Приложение может продолжать работать) Да Нет
1 USER - это 16-разрядный нереентерабельный код
2 50 % вызовов GDI обслуживаются 16-разрядным нереентерабельным кодом
3 WARP как новая версия системы OS/2 имеет средство разблокировки входной
очереди, если она оказывается заблокированной
Сопоставление OS/2 Warp и Windows 95 по средам для приложений
Характеристика Warp Windows 95
16-разрядные приложения OS/2 РМ Да Нет
32-разрядные приложения OS/2 РМ Да Нет
Win32s-приложения
(версии 1.0 и 1.1) Да Да
Вытесняющая многозадачность4 Да Нет
Поддержка Win16-приложений Да Да
Поддержка драйверов устройств Win16 Да Да для некоторых5
Количество доступных 32-разрядных
приложений Более 0
2000
4 Cм. таблицу сопоставления по многозадачности
5 Коммуникационные драйверы Windows 3.х требуют обновления
6 Собственные приложения Windows 95
Сопоставление OS/2 Warp и Windows 95 по характеристикам
многозадачности
Характеристика Warp Windows 95
Вытеснение 32-разрядных приложений OS/2
и Win32s, версия 1.1 Да Нет
Вытеснение DOS-приложений Да Да
Вытеснение смешанных 16/32-разрядных
приложений7 Да Нет8
Множественные защищенные Win16 VDM Да Нет9
Защита от краха Да Нет10
Вытесняющая многопоточность Да Да
7 16- и 32-разрядные приложения OS/2, WIN16 и WIN32s vl.l
8 WinMUTEX запрещает доступ к USER и частям GDI при выполнении WinlG-
приложения
9 Все IG-разрядные приложения делят единое адресное пространство - Системную
Виртуальную Машину (VM)
10 Ключевые структуры кода операционной системы (USER и GDI) делят адресное
пространство системной виртуальной машины (VM) с 16-разрядными приложениями
Сопоставление OS/2 Warp и Windows 95 по пользовательскому
интерфейсу
Характеристика Warp Windows 95
Рабочие области папок Да Нет
Интеграция с операционной SOM Да Нет11
Панель запуска Да Да
Удаление "тащить и бросить" Да Нет
Посылка факса "тащить и
бросить" Да Да
Пути доступа "тащить и бросить"
(работоспособность при изменении путей исполнения)
Да Нет
Шаблоны объектных типов Да Нет
Опции закрытия порождающих папок
Да Нет
11 Компоненты оболочки Windows 95 не являются объектами OLE 2.01
Сопоставление OS/2 Warp и Windows 95 по мультимедиа
Характеристика Warp Windows 95
Утилита просмотра изображений Да Нет
Поддержка системы Photo CD Да Нет
Система мультипликации
Autodesk Animation Да Нет
Воспроизведение любого аудиофайла
из сети Internet Да Нет
Менеджер синхронизации
аудио/видео Да Нет
Поддержка формата MPEG Да Да
Воспроизведение 32-разрядных
аудио/видео Да Да
Сопоставление OS/2 Warp и Windows 95 по входящим в состав пакета
приложениям
Характеристика Warp Windows 95
Средства доступа к сети Internet:
Да Нет
FTP Да Нет
Telnet Да Нет
Gopher Да Нет
Newsreader Да Нет
WEBExplorer Да Нет
Входной интерфейс CompuServe Да Нет
Текстовый процессор Да Нет12
Электронная таблица Да Нет
База данных Да Нет
Диаграммы и графики Да Нет
Генератор отчетов Да Нет
Электронная почта Да Да
Утилита просмотра изображений Да Нет
Факс Да Да
Телефонная книга Да Нет
Менеджер персональной информации
Да Нет
Утилита системной информации Да Нет
Видеовход Да Нет
Видеоконференции Да Нет
12 Система Windows 95 будет выпущена с простым текстовым редактором, а не с
текстовым процессором
Литература
King, Adrian, "Windows (ТМ), the Next Generation: An Advansed Look at the
Architecture of Chicago" (Кинг, Эйдриан. "Windows (TM), Следующее Поколение:
Детальный Обзор Архитектуры системы Chicago"), Microsoft Systems Journal, January
1994, pp. 15-24.
King, Adrian, "Memory Management, the Win32(R) Subsystem, and Internal
Synchronization in Chicago" ("Кинг, Эйдриан. "Управление памятью. Подсистема Win32*)
и Внутренняя Синхронизация в системе Chicago"), Microsoft Systems Journal, May 1994,
pp. 57-61.
Pietrek, Matt, "Stepping Up to 32 Bits: Chicago's Process, Thread, and Memory
Management" (Питрек, Мэтт. "Поднимаясь до 32 Разрядов: Управление Процессами,
Потоками и Памятью в системе Chicago"), Microsoft Systems Journal, August 1994, pp.
27-41.
Pietrek, Matt, "Investigating the Hybrid Windowing and Messaging Architecture of
Chicago" (Питрек, Мэтт. "Изучение Гибридных Средств Образования Окон и
Архитектуры Сообщений в системе Chicago"), Microsoft Systems Journal, September
1994, pp. 15-30.
Pietrek, Matt, "Which Win32 Is For You?" (Питрек, Мэтт. "Какая Подсистема Win32 Вам
Годится?"), PC Magazine, September 1994.
Замечание:
Информация, содержащаяся в настоящем документе, отражает настоящий взгляд
корпорации IBM на обсуждаемые вопросы на момент публикации. Поскольку
корпорация IBM обязана реагировать на изменяющиеся условия рынка, этот документ
не должен считаться обязательством со стороны IBM. Вся информация, заявления,
ссылки и сравнения в отношении системы Windows 95 в настоящем документе
основаны на несекретной информации, доступной на дату публикации.
Этот документ предназначен только для информационных целей. Корпорация IBM В
ДАННОМ РЕФЕРАТЕ НЕ ПРЕДСТАВЛЯЕТ НИКАКИХ ГАРАНТИЙ, ВЫРАЖЕННЫХ
ИЛИ ПОДРАЗУМЕВАЕМЫХ.
1994 IBM Corporation. Все права сохраняются. Напечатано в Соединенных Штатах
Америки.
OS/2 является зарегистрированной торговой маркой фирмы International Business
Machines. Microsoft является зарегистрированной торговой маркой, а Windows является
торговой маркой фирмы Microsoft, Inc. NetWare является зарегистрированной торговой
маркой фирмы Novell, Inc.
15 вопросов к Microsoft
------------------------
Может ли Windows 95 жить с рекламой,
которую для него создал Microsoft?
15 вопросов к Microsoft
Может ли Windows 95 жить с рекламой, которую для него создал Microsoft? Эта
вопросы основаны на информации, опубликованной о готовом продукте, занимающем
второе место в Windows 95 Resource KIt. Принята решение вам поможет Windows 95
Reviewer's Guide.
Надежность
Что происходят с 32-битовыми
приложениями в случае сбоя
приложений Winl6 под Windows
95?
Они могут остановить работу. Поскольку Microsoft
создал Windows 95 используя туже самую модель
System Virtual Machine как и в Windows 3.1
операционная система находится во власти
наследия 16-битовых приложений. Если повисает
программа Winl6 это может связать критические
16-битовые кодовые модули, находящиеся в System
Virtual Machine. И все другие вычисления
останавливаются.
Вывод: Windows 95 является не надежной
платформой для решения критических и
специальных прикладных задач.
Защищает ли Windows 95
содержание своей системной кэш
памяти от вторжений программ
Win32?
Нет. Также как и с упомянутой выше структурой
системы Windows 95 не может защитить
содержание кэш памяти - дисковый кэш, сетевой
кэш и кэш CD-ROM. В результате в участке
занятой кэш памяти может быть записана
блуждающая прикладная программа Win32.
Потенциальные последствия: неточность данных,
искаженные данные файловой системы, и т.д.
Вывод: Целостность данных для Windows 95
остается под знаком вопроса.
Как Microsoft решает проблему
неустойчивости Драйвера
виртуальных устройств (VxD)?
Никак. На самом деле Windows 95 интенсивно
использует VxD с целью дополнения, а во многих
случаях замены функции DOS. VxD являются
чрезвычайно мощными программами, которые могут
буквально куда угодно идти и что угодно выполнять
в операционной системе. Они имеют свободный
доступ напрямую к системной памяти, способны
управлять "железом" и даже заменять порциями
Windows 95 во время его работы. Это предоставляет
неограниченную гибкость программисту VxD при
разработке приложений, нуждающихся в
изменении работы Windows 95. Сам Microsoft часто
развивал интерфейс VxD в качестве механизма для
обеспечения высокой производительности
быстродействующих приложений Windows. К
сожалению мощь VxD может стать роковой. С
увеличением числа разработчиков, использующих
этот интерфейс, имеющий ограниченный контроль,
с практически отсутствующей межпроцессовой
изоляцией, свободное программирование с участием
многочисленных третьих пользователей, аналогично
изменяющих систему, может окончиться
непредсказуемыми результатами. Сбой
единственного VxD может повлиять на
стабильность всей среды Windows 95.
Вывод: VxD - потенциальная катастрофа,
ожидающая своего часа, чтобы поразить
корпоративную Америку.
Правда ли, что Windows 95 не
полностью защищает коды
операционной системы от сбоев
приложений Win 32?
Да. Приложения Win 32 могут производить запись
в районы наивысших и наинизших адресов
виртуальной памяти, критически важных для
работы всей среды. В результате этого неверная
работа памяти может нарушить стабильность
системы и потенциально разрушить всю
операционную систему.
Вывод: Полный отказ Windows 95 может произойти
в результате одной ошибочной операции с памятью.
Виртуализирует ли Windows 95
аппаратные средства ПК для
защиты от дефектных
приложений при работе с
приложениями DOS
Нет. Windows 95 не может виртуализировать
важнейшие аппаратные компоненты как флаг
прерывания. Это в свою очередь может привести к
крушению системы в случае,
если какая-либо неисправная программа становится
безответной, в то время как прерывания не
задействованы.
Вывод: Старые приложения, используемые в
предыдущих операционных системах - Ахиллесова
пята для управления памятью Windows 95.
Удобство использования
Динамично ли Windows 95
отслеживает объекты?
Нет. Windows 95 использует целый ряд
статических путей доступа и .INI файлов DOS для
определения взаимоотношений между тем, что
отображено на десктопе, и файлами на диске.
Например, механизм сокращений интерфейса
Windows 95 полагается на записанную копию
данных о пути доступа к оригиналу во время его
размещения и обращения к нему. Если файл
перенесен в пределах границ директории, Windows
95 должен осуществить его поиск по всему диску,
основываясь на данных о размере файла и отметки
о дате. Несмотря на то, что такой метод работает
почти постоянно, он ограничен поиском в пределах
одного логического тома - если вы перенесли файл
в другой том диска связь нарушается полностью. А,
поскольку Windows 95 в случае подключения к
сети будет просматривать всю сеть, то операция
просмотра, скажем, пяти Гита-байт может стать
бесконечной
Вывод: Вызовы о помощи "Хелп-деска" будут
постоянными в случае экспериментирования
пользователя с сокращениями и длинными именами
файлов.
Выполняет ли Windows 95
последовательный "дрэг &
дроп"?
Нет. Особенность Windows 95 "дрэг & драп"
применяется только с некоторыми объектами,
такими как файлы и папки, и больше ни с какими
другими. Например, вы
не сможете перемещать сетевое соединение
кодового вызова (dial-up networking connection) в
Windows 95 Recycler, равно как и не сможете
перенести ваши объекты в My Computer folder -
поскольку оба они являются "особыми объектами" в
интерфейсе Windows 95 и не подлежат к обычным
правилам Windows 95 по "дрэг & драп". Это
приводит к определенной степени
непоследовательности в интерфейсе и возможному
камню преткновения для начинающих
пользователей, пытающихся воспользоваться "дрэг
& драп".
Вывод: Интерфейс Windows 95 не последователен
от функции к функции.
Последователен ли и объектно-
ориентирован ли Windows 95?
Нет. Например, задействовав правую клавишу
"мыши" вы можете вызвать меню почти по всем
объектам, содержание стартового меню и субменю
сюда не входят. Это делает операцию по
управлению Стартовыми меню неудобной с
вызовом диалогового блока "Таскбар" и нескольких
уровней меню и окон. Поскольку правая клавиша
"мыши" работает во многих остальных областях
интерфейса отклонение стартовых клавиш от
нормы делает объектно-ориентированную
поддержку Windows 95 незаконченной.
Вызов: Windows 95 не полностью использует
технологию объектного ориентирования.
Windows 95 и
многозадачный режим
Могут ли Windows 95
опережающе выполнять
многозадачные функции на
приложениях Win 16?
Нет. Поскольку приложения Win 16 были написаны
для кооперативной многозадачной среды они не
могут выдержать опережения во время исполнения.
Таким образом Windows 95 должен оперировать эти
приложения также, как это делает Windows 3.1:
передавая их под исключительное управление
центрального процессора на весь период их
использования. Когда, и только тогда, когда
приложение совершает вызов API - один из
немногих таких вызовов, обеспечивающих
безопасность. Windows может снять контроль с
программы при условии разрешения на выполнение
других программ. В этом заключается
кооперативный многозадачный режим, оказавшийся
неэффективным при одновременном выполнении
более чем нескольких программ или при
выполнении программ, требующих интенсивной
работы процессора, таких как связь, печать и/или
факсимильные программы.
Вывод: Windows 95 не на много повышает ценность
крупных приложений Win 16, используемых в
предыдущих операционных системах.
Существуют ли какие-либо
предостережения в отношении
многозадачного использования
приложений Win 32 под
Windows 95?
Да. В своем стремлении сохранения высокой
степени обратной совместимости с одновременным
уменьшением требований к ОЗУ операционной
системы Microsoft решил сохранить свои
имеющиеся (в эпохе Windows 3.1) модули USER и
GDI (Graphics Device Interface) нежели создавать
новые 32-битовые версии. С целью использования
своего старого 16-битового кода в 32-битовой
многозадачной среде Windows 95 с потенциальной
возможностью опережения (в отношении
приложений Win32) Microsoft
был вынужден осуществить серийный допуск к
USER и GDI. В результате этого только одна Win32
или Winl6 программа имеет доступ к таким
важнейшим модулям в определенный момент. Это
негативно отражается на производительности
прикладных программ, на перегрузке системы, по
причине того, что программы вынуждены вставать
"в очередь" и ждать возможности выполнения
операций USER или GDI. Все вызовы USER (как
для 16-битовых, так и для 32 битовых приложений)
сериализирукется и обрабатываются в 16-битовом
коде, в то время как большинство вызовов GDI
обрабатываются аналогичным способом (остальные
50% обрабатываются более новым способами).
Вывод: Многозадачный режим Windows 95 более
полно может быть охарактеризован, как
"Требующий опережения"
Что происходит с многозадачным
режимом Windows 95, если вы
сразу запускаете несколько
типов приложений?
Он возвращается к совместной многозадачной
модели. То, что Windows 95 продолжала опираться
на единственную системную модель VM Windows
3.1. ставит способности многозадачного режима
оперативной системы в зависимость от обычного
знаменателя самого низкого уровня: 16-разрядного
приложения Windows. В любом случае, когда
запускается приложение Winl6, способности
многозадачного режима оперативной системы
ставятся под угрозу необходимостью предоставить
данному приложению действовать как
"нераспределенному" настолько долго, насколько
это будет необходимо. В результате, когда
многозадачный режим представляет собой смесь
приложений Winl6 и Win32, настоящие резервные
операции становятся невозможными, поскольку в
любое время, 16-разрядному приложению может
понадобиться исключительное правление
центрального процессора. Ситуация осложняется
тем, что, поскольку приложение Win16 выполняет
часть 16-разрядного USER или кода GDI - доступ к
которому должен осуществляться последовательно
- все остальные процессы, включая приложение
Win 32, блокированы для исполнения. В результате
сеть находится в состоянии, которое может быть
описано как "полу-резервный многозадачный
режим".
Вывод: При введении смеси приложении Winl6,
Windows 95 приобретает смешанные с Windows 3.1
характеристики.
Компенсирует ли многозадачный
режим Windows 95 недостатки
Windows 3.1, связанные с
мультимедиа?
Не совсем. Недостаточно отлаженная работа
многозадачного режима Windows 95 -побочный
продукт единственной системной модели VM -
ставит под угрозу ее работу как солидную
платформу для производства мультимедиа.
Комплекс зажимов AVI подвергается
значительному разрушению, когда на систему
Windows 95 падает значительная нагрузка по
вводу-выводу. Даже простые операции, такие, как
открытие приложения, могут не выполняться при
считывании считывания мультимедиа.
Вывод: Вы не сможете одновременно использовать
мультимедиа и производить значительный объем
работ по вводу-выводу.
- IMPORTANT PWA NOTICE TO ALL!!
NOTEPWA.ZIP
FILE_ID.DIZ
IMPORTANT PWA NOTICE TO ALL!! ▄ ▀▀██▄ ▄ ▄ ▄ ▀█▄ ▀█▌▀█▄ ▐ ▄█▀ ▄▄██▌ A Group ▐█▌ ▐▌ ▐█ █▌▐█▌ ▄█▀ █ That Gives ▄██▌▄▀ ▄██▌▀██▌ ██ ▐▌ Slightly ▀███ ▀███ ▀█ ▐███▄▄ █ Less Than ▐█▌ ▐█▌ ▐▌ ▀██▀ ▀▄ A Fuck. ▀ ▀ ▀ ▀ -XeN PLEASE READ!! ─═■POINTBREAK+32·11·436925■═─
README.TXT
%%% IMPORTANT NOTICE ABOUT Microsoft RELEASES %%%
________________________________________
Here at PWA we don't release any fake
stuff. Some rather LAME groups insist
that some of our Microsoft releases are
fake or not the "real release". This
is probably due to the fact that some of
our Microsoft releases are packaged
slightly differently than the ones that
some other LAME groups release after we
have released ours. The different
packaging is due to the fact that we
release our stuff AS SOON as Microsoft
sees it fit for release. They may have
forgotten to remove some text file saying
that the release is a beta etc., but this
is later cleaned up by "packagers" (at
Microsoft) that are in charge of removing
such text files and maybe restructuring
some MINOR things - but nothing that
affects the way that the product runs.
So - finally - would all SYSOPS please nuke
everything that LAME groups release after
we've already released it - claiming to be
the "REAL" Release! They are - pardon my
French - full of shit.
This also goes for i.e. our OS2 release "WARP"
that people assumed to be fake because we're
so DAMN fast at releasing it. It was assumed
to be fake because "there was no install file".
Well if you open your fucking eyes and look -
the install file is on the LAST disk not the
first.
I hope we won't have to write another one of
these text files ever again.
Thanx,
DARK LORD, P W A COUNCIL MEMBER '94
i i t
r t t
a h i
t t
e u
s d
e
MS-DOS 6.21不同文件日期
存在两种文件日期RTM版本， 1) 1994-2-13，English-OEM, Italian-OEM Spanish-OEM, Dell OEM. 2) 1994-3-10. English Retail Upgrade. They first released OEM, in later release Retail
WinXP SP2 2600.2177信息
Windows XP SP2 Build 2177 Nfo
OK, here's the rundown for 2177 (xpsp_sp2_rtm.040729-2314): IE: 6.0.2900.2177. It's now known as "Internet Explorer 6 for Windows XP Service Pack 2" or some other ridiculously long name marketing and legal dreamt up. MSJVM: not included. DirectX: 9.0c (4.09.0000.0904) WMP: 9.00.00.3250 Movie Maker: 2.1.4026.0 .NET Framework: not included Windows Update components: 5.4.3790.2177 Remote Desktop Connection: 5.1.2600.2177 BITS: 6.6.2600.2177. MSDN calls this BITS 2.0. XML Parser: 8.50.2162 (msxml3.dll). Probably safe to call this XML 3.0 SP5. MDAC: 2.81.1117.0 Windows Messenger: 4.7.3000 MSN: MSN 9 stub installer included. Windows Installer: 3.00.3790.2177 Other notes of interest: The network install weighs in around 265 MB, but it is anticipated that most users will use Automatic Updates or Windows Update to install, in which case the relevant files will total about 100 MB. BITS will be used to download these components so the download will only consume your unused bandwidth. The updated support tools include BITSAdmin 2.0 and a newer version of netdom, but most everything else remains the same. Retail CD's slipstreamed with SP2 will differ slightly from homebrew slipstreams, mostly in directories outside of /i386. The /DOTNETFX directory will include .NET Framework 1.1. Also, the /CMPNENTS (CD2) directory will now include files for Tablet PC 2005 (Lonestar) and Media Center 2004 (Harmony). However, making your own MCE slipstream will not be supported; you will need to obtain updated CD2 files from your OEM. I won't delve too deeply into the enormous amount of new and updated features included in SP2. The firewall, popup blocker, and Security Center all come to mind, as well as tons of smaller fixes to help protect your computer. The bottom line is: install SP2 on your computer and urge everyone you know to do the same. A number of keys and key ranges are blocked with SP2, however, legitimate users will have no problems updating. If you do have problems installing SP2, Microsoft's How To Tell site has specific information to help you. Watch http://www.microsoft.com/windowsxp/ for news and where to obtain it.
备用OS2补丁和版本号
- Internal revision 6.412, 92/06/02
https://www.ibiblio.org/pub/micro/pc-stuff/os2/os2krnl.zip
- Internal revision 6.540, 93/07/14
无用或无实物NFO
- Windows 95
Win95 Build 216 表格恢复后NFO 备用
* THE NOKTURNAL TRADING ALLIANCE PRESENTS *
┌──────────┬───────────────┬───────────────────────────────────────┐
│Date: │ 10/31/94 │ File Date: 11/2/94 │
├──────────┼───────────────┴───────────────────────────────────────┤
│Software: │ MS CHICAGO / WINDOWS V4.0 BUILD 216 │
├──────────┼───────────────┬───────────────────────────────────────┤
│S/N: │ Beta 162330 │Location: 01a74a138 │ │
└──────────┴───────────────┴───────────────────────────────────────┘
Thanks to Ambassador Gkar Final Frontier For This Release!
THE FINAL FRONTIER IS WORLD HEADQUARTERS FOR =RiSc=
RiSc Is The Official Courier For =NTA=
Greetings To Our Sister Group: RiSc! The Guys Who DO The Impossible Everyday!
┌─────────────────────────────────────────────┐
│-=NTA=- Boards: SysOps: │
├─────────────────────────────────────────────┤
│The PITS The PieMan │
│The Unknown The Punk │
│The Final Frontier MikeySoft │
│Access Denied The Wanderer │
│The Eclipse The Mustang │
│The Elusive Dream The Toyman │
│Turbo Italian Network Jurgen │
│Orion's Belt The Drunkard/Pompei │
├─────────────────────────────────────────────┤
│ -=NTA=- Members │
├─────────────────────────────────────────────┤
│The Mustang Oyl Patch William Zardoz │
│The Toyman The Punk MikeySoft │
│Jurgen The Wanderer The Cat │
│The PieMan Bryn Rogers Hi.T.Moonweed │
│ │
│Fiona Void Master Boomer │
└─────────────────────────────────────────────┘
* Important Final Note * FROM MIKEYSOFT / NTA LEAD BOARD *
* We all must strive to bring as much credibilty to the vast community of *
* "Groups" which make-up the system that we all contribute to and enjoy! *
* The Friendly Rivalry between these groups is just that, "FRIENDLY". It *
* adds a certain flavor of positive competition that we feel is necessary *
* to encourage the greater sharing of information. "*KEEP IT FRIENDLY*" *
* Please honor our group ID'S tags by NOT removing this file! If you feel *
* the necessity to rename the ZIP, maintain the integrity of the group ID *
* WE EXTEND THE SAME COURTESY AND POLICY TO OTHER GROUPS *
* Remember to make it work, keep it friendly! *
Win95 Build 345 表格恢复后NFO 备用
■ THE NOKTURNAL TRADING ALLIANCE PRESENTS ■
╔════════════╦══════════╦═════════════════════╦══════════════════════╗
║ Date: ║ 03/01/95 ║ File Date: 02/24/95 ║ SN: None Required! ║
╠════════════╬══════════╩═════════════════════╩══════════════════════╣
║ ║ ║
║ Software: ║ WINDOWS 95 BUILD 345(M8) ║
║ ║ ║
╠════════════╩═══════════════════════════════════════════════════════╣
║ A ≡ BIG ≡ Thanks to Yakumo & Asclep ║
╚════════════════════════════════════════════════════════════════════╝
Enjoy! Oyl Patch
Note: This is the M8 Final Beta release. Just sent to be dup'd.
Requires no Beta ID or Number, so install and enjoy!
┌─────────────────────────────────────────────┐
│ =NTA= The Nokturnal Trading Alliance =NTA= │
├─────────────────────────────────────────────┤
│The PITS The PieMan │
│The Unknown The Punk │
│The Final Frontier MikeySoft =WHQ= │
│Access Denied The Wanderer │
│The Eclipse The Mustang │
│The Elusive Dream The Toyman │
│Turbo Italian Network Jurgen │
│Orion's Belt The Drunkard/Pompei │
│ -=NTA=- Members │
│ The Mustang Oyl Patch William Zardoz │
│ The Toyman The Punk MikeySoft │
│ Jurgen The Wanderer The Cat │
│ The PieMan Bryn Rogers Hi.T.Moonweed │
│ Fiona Void Master Boomer │
└─────────────────────────────────────────────┘
╔════════════════════════════════════════════════════════════════════════╗
║ Important Final Note * FROM MIKEYSOFT / NTA LEAD BOARD ║
║We all must strive to bring as much credibilty to the vast community of║
║"Groups" which make-up the system that we all contribute to and enjoy!║
║The friendly rivalry between these groups is just that, "FRIENDLY". It║
║adds a certain flavor of positive competition what we feel is necessary ║
║to encourage the greater sharing of information. "*KEEP IT FRIENDLY*"║
║Please honor our group ID'S tags by NOT removing this file! If you feel║
║the necessity to rename the ZIP, maintain the integrity of the group ID ║
║ WE EXTEND THE SAME COURTESY AND POLICY TO OTHER GROUPS ║
╚════════════════════════════════════════════════════════════════════════╝
- Windows 2000
Windows 2000 Advanced Server Build 2195.zip\RHA.nfo
HTTP://RHA2000.CJB.NET
███
███ ░██ ░░
░███░ ███ ▒██ ▒▒
░█████░ ███ ▒██ ██░
▒██████░ ███ ▒█▓ ██▒
▒██▓░███ ██▓ ▒█▓ ░███
▒██▓ ▓██▓ ██▓ ▓█▓ ▒███░
▒██▓ ░██▓ ██▓ ▓█▓ ▓███▒
▒██▒ ███ ██▓ ▓█▓ ▓███▓
▒██▒ ███ ██▓ ▓█▒ ██▓██
▓██░ ░███ ██▓ ▓█▒ ░██▒██░
▓██░ ███▓ ██████▒ ▒██░██▒
▓██░░███░ ██▒ ██▒ ▒██████
▓██░███▒ ██▒ ██▒ ▓█▓ ███░
▓█████▒ ██▒ ██░ ██▓ ▓██▒
▓███▓░ ██▒░██░ ░██▒ ▒██▓
▓███▒ ██▒░██░ ░██▒ ░███
███████ ██▒░██░ ▒██░ ███░
███ ▓███░ ██▒░██░ ▒██░ ▒▓▓▒
███ ░█▓ ██▒░██
-=RUSSIAN HACKERS ALLIANCE!=-
▄▄███▄▄ RUSSIAN PIRATES COPY ONLY THE BEST TECHNOLOGY...
██ ▄███▄▀ ▄▄▄▄▄▄▄ WE STEAL THE REST!
▀█████▀▄▄▄ █▀▀████████ ▄▄▄▄██████▄▄▄▄
▀▀ █████ ██▄████▀▀▀▀▀▀ ▄▄▄▄▄▄▄▄▄▄▄ ▄███▀▀▀ ▀▀▀███▄
▀▀▀ ▄███▓▄▀▀▄▄▄▄████████▀▀▀▀▀▀▀▀▀▀▀████████▄▄ ██▀ PRESENTS ▀██
████████ █████▀ P R E S E N T S ▀███ ▐██ ON ██▌
████████ ▀▀▀▀Windows 2000 Advanced Server▀▀▐██ 19/12/1999 ██▌
▄▄ ▀█▄██▀ Microsoft Corp. ██▄ ▄██
▄██▀▀ ▄▄ ▀███▄▄▄ ▄▄▄███▐
███ ▄██▀ Cracker : CyberAdmin Supplier : RHA ▀▓▀████████▀▀▀ █
▐██ ███ Packager : CyberAdmin Disks : 27 * 15Mb░ ▄▄ ▓
██▄ ▀█▄ Protection : Serial OS : Win9x/NT4 ▄██ ░
▀███▄ ▀ ▄███▀
▄▄▀▄▀████▄▄▄▄ ░ Retail : $N/A ▄▄▄▄████▀▀ ▄
▄█▀██▌▐▀██▌ ▀▀▀▀██████▄▄▄▓▄▄▄▄ ▄▄▄▄▄▄▄▄██████▀▀▀▀ ▄ ▄████
██████▄▄▐█ ▄▄▄▄▄▀▀▀▀▀▀▀▀███████████▀█▀▀▀▀▀▀ ▄▄ ▄█████▌█▄▀▀▀▄
▀▀████▀ █ ▄█▀▄▄██████▄ ▀███ █▌ █▌ ▀██▄█▀■▄██████▄
▐█▓ ████████████ ▐█▌ ▓ ▐▓▒ ▄▄████████ █▐███▄▄
▀ ▀██████████▀ ▄███▄▄▄▐█▌▄▄▄▄ ▀ ▀████████▄█▀▐█ ▀█
▄▄▄▄█████▄▄▄▄▀▀███▀▀ ▄▄████████▀▀▀▀ █ ▀▀▀▀████████▄▄▄▄▄▄▀▀▀▀█▀▀ ████▄▄█
▄███▀▀▀ ▄ ▀▀▀███▄ ▀▀▀▀ ▓ ▀▀▀▀▀▀████▄▄▄▄ ▀▀▀
██▀ ▄▄▀ ▀██ ░ ▀█████▄▄
▐██ ░▓█▌ NOTES ██▌ Here's the final build of Windows 2000 ░▓█▐▀ ▀██▄
██▄ ▀▄ ▄██ for you which will go RTM! ▀██ ██▄
▀███▄▄▄ ▄▄▄███▀ ▀▐ ██
▀▀▀███████▀▀▀ The product will hit stores worldwide on ▄ ██
██ February 17, 2000! This version of Windows 2000 ██
██ is the Professional Version. Microsoft Windows 2000 ██
██ Professional is the best desktop and mobile operating ██
██ system for businesses of all sizes, designed to replace ██
██ Windows 95 as the standard. It's the easiest, most ██
██ reliable Windows yet because it combines the ██
██ reliability, security, and manageability of Windows NT ██
██ Workstation with a user interface that's even simpler ██
██ than Windows 98. Easiest Windows Yet: Windows 2000 ██
██ Professional is the easiest Windows yet for working ██
██ with your computer, browsing the Web, and setting up ██
██ and configuring your system. Best of Windows 98: ██
██ Windows 2000 Professional provides broader support for ██
██ hardware and mobile devices by enhancing the next- ██
██ generation hardware support introduced with Windows 98. ██
██ Power of Windows NT: The tradition strengths of Windows ██
██ NT have been built on to provide business users with ██
██ standards-based security, industrial strength ██
██ reliability, and faster overall performance. Delivers ██
██ Lowest Total Cost of Ownership: Windows 2000 ██
██ Professional can help your company save money because ██
██ it is designed to be easier to deploy and easier to ██
██ manage. Use this serial to install the Professional ██
██ version: RBDC9-VTRC8-D7972-J97JY-PRVMG
To clear up all the rumours about our Win2000 Rip
release: We released the non-timebombed, non-cracked
final 2195. What has changed between our release and
the one you will be able to buy in February 2000 is
just the product key verification algorithm. The key
we used was strictly for MS INTERNAL USE ONLY!
Just one final note: It seems that almost nobody
noticed that CyberAdmin never cracks a product. If
cracking is necessary, we release it as RHA.
██
██ We hope Russian Hackers Alliance releases are used only to ██
██ learn software and become better informed about it. ██
██ If you use it for more than this please buy legal copy ██
██ of this product. ██
██ ██
██▄ ██
▄ ███▄ Enjoy another RHA release! ▄██
▄█▀██▐█▀███▄▄▄ ▄███▀
██▄██▌██▌ ▀▀▄▀████▄▄▄▄ ▄▄▄▄████▀▀
▀████▐█▓ ▐▀██▌ ▀▀▀▀██████▄▄▄▄▄▄▄ ▄▄███▄▄ ▄▄▄▄▄▄▄██████▀▀▀▀▄▄▄▄██▌
▀▀ ▓ ■▐█ ▀██▀ ▀▀▀▀▀▀▀ ██ ▄█████ ██▀▀▀▀▀▀▀ ▀▀████▀▀
░ ▀ ▄██▄▄▄▄▄▄▄▄▄ ▀███████▀ ▄▄ ▄▄███▄▄
▄▄▄▄▄█████████▀▀▀▀▀▀▀▀▀▓▀ ▀▀▀ ▄███▄▀▀█████████▄▄▄▄ ▀████▄ ██
▄▄▄████▀▀▀▀ G r o u p N e w s▒ ▀███▀ ▀▀▀▀████▄▄▄▀▀██▀
▄▄██▀▀▀ ▀▀▀██▄▄
██▀ After a little while in RiSE, we've decided to come back to ▀██
██ our original releasing title. So look for more quality RHA ██
▄▄ releases on a site near you. ▄▄
▄▄ ▄▄
▄▄ We're currently looking for: ▄▄
▄▄ * If you can supply unreleased software. ▄▄
▄▄ * If you work for an ISP or can provide us with shell accounts. ▄▄
▄▄ * If you are an experienced cracker or a cracker with asm exper- ▄▄
▄▄ ience and is willing to learn. ▄▄
▄▄ * If you work for a store, software developer, publisher and can ▄▄
▄▄ get us either advanced copies of Finals. ▄▄
▄▄ * Coders, 2D/3D artists. ▄▄
▄▄ * Trainer coders. ▄▄
▄▄ ▄▄
▄▄ If you can help, e-mail us at admin@rha2000.cjb.net ▄▄
▄▄ ▄▄
▄▄ The Russian Hackers Alliance now is: ▄▄
▄▄ ▄▄
██▄ Seniors : CyberAdmin, NorthStar ▄██
▀██▀ ▄▄▄▄█████▄▄▄▄ Members : Nasty Boy, Sav||or, ▄██▀
▄███▀▀▀ ▄ ▀▀▀███▄ Vic, Corwin ▄▄▄██▀▀
██▀ Russian▀█▄▄ ▀██ ░ ▄▄▄▄███▀▀▀
▐██ Hackers █▓░ ██▌█▄▄▄▄▄▄▄▄ ▄▄▄▄▄▓▄▄███████▀██▀█▀▄█▄▄
██▄ Alliance▀ ▀ ▄██ ▄▀▀▀▀▀▀▀▀███████████▀▀▀▀▀▀▀▀ ▐▀███▀▄ █ ██████▄
▀███▄▄▄ ▄▄▄███▀▄████████ ▐█ ██▌█▐█████ █
▀▀▀███████▀▀▀▄▄█▄▀▀███▀▀ █ ▀█▌■█████▄█▀
▀▀ ▐█▓ ▀▀████▀▀
.nfo header and layout by Zone ▓
.last update by CyberAdmin [09/02/99] ░
.mail: Admin@rha2000.cjb.net
- Windows XP
Windows Xp Beta 2 Build 2474 Serial.zip\Winxp2474pro-dffiso.nfo
▀ ▀▀ ▀▀▀▀█▄▄▄▄ ▄▄▄▄▄▄▄█▀▀▀▀▀▀▀▀█▄
██████████▄▄▄▄ ▀▀▀█▄▄ ▄▄▄█▀▀▀▀ ▄▄▄▄▄▄▄██████▄ █
███████████████████▄▄ ▀▀█▄ █▀▀▀ ▄▄▄█████▒░░░░░░░░▒██ ▀▀▀▀▀▀▀▀▀▀█▄▄ ▄
██████░░░░░░░░░░███████▄ ▀██▀ ████░░░░░░░░░░░░░░░░░▒██ ▀████████▄▄▄▄▄▄ ▀
███████░░░░░░░░░░░░██████▄ ▀ ██▒░▒░░░░░░░░▒██████▀▀▀▀▀▀░░░░░░░░░░░░░░██████
████░░░▒▒▒░░░░░░░░█████ █░░░░░▒████▀▀▀▀ ▄░░░░░▒░░░░░░░░░░░░░░░░░█
████░░▒▒▒▒▒▒░░░░░░░░████ ▀█░▒░░██ ▄█░▒░░░░░▒████▀▀▀██████░█▀
████░░░▒▒▓▓▓▒▒▒▒░░░░░░███ ▀█░▒▒░█ ▀█▒▒░▒▒░█▀▀ ▀▀▀
████░░▒▒▒▓▓▓▓▓▓▒▒░░░░░███ ▀█▒▒▒██ ▄▄▄▄██ ▀█░▒▒▒█▀
████░░▒▒▒▓▓▓▓▓▓▒▒░░░░░░███ █▒▒▒▒██████▒░░░██ █▒▒▒░█▄▄▄▄
███░░░▒▓▓▓▒▒▒▒▒▒▒██░░░░░██ ▀█░▒▒▒░▒▒░░░░▒▒▒█▄ ▒▒▒▒▒▒▒▒█████▄▄▄
███░░░▒▒▓▓▒██████░░░░░░░███ █▒▒▒▒▒▒████▀▀▀▀▀█ ▒░▒▓▒▒▒▒▒▒▒▒▒▒██
███░░░▒▒▓▒▒█ ████░░░░░░██ █▓▒▓▒██▀ ▄▄▒▒▓▒██▀▀▀▀█████
████░░▒▒▒▒▒██ ██░░░░░░███ █▒▒▒▒█ █▒▓▒▒▒▒█ █▀
███░░░▒▒▒▒███ ████░░░░██ ▄█▓▒▒▓██ █▓▓▒▒▓▒█
██░░░░▒▒▒▒███ ████░░░░░██ ██▒▓▒▒██ ██▓▓▓▒▓▓██
███░░░░░▒▒▒▒▒█████░░░░░░░██ ▄█▓▓▓▒▓███ ██▓▓▓▓▓▓██
███░░░░░░░░░░░░░░░░░░█████ ▄█▓▓▓▓▓▓▓██ ██▓▓▓▓▓██ ▄
███░░░░░░░░░░███████████▀▀ ▄█▓▓▓▓▓▓▓▓█ ████▓▓▓▓██ ▄
███████████████████▀▀▀▀ ▄▄█▄ ▀███▓▓▓▓▓██ ▄▄ ███████▓▓▓██
▄▄▄ ▀▀▀▀▀▀▀▀▀▀ ▄▄▄▄▄█▀▀▀▀ ▀█▄▄ ▀▀█████ ▄▀ █▄ ▀▀██████▓▓█ █
▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ▀▀█▄▄▄▄▄▄▄█ ▀▀█▄▄▄ ▀▀▀▀▀█ █
▀▀▀▀▀█▄▄▄█
-= AFFILS Needed!!! =-
.:: DFFiSO ::.
Is Proud To Present
┌────────────────────────────────────────────────────────────────────┐
│ Microsoft Windows XP build 2474 │
└─────────────────────────────────┬──────────────────────────────────┘
│
┌─────────────────────────────────┼──────────────────────────────────┐
│SUPPLIED BY [ Mr no pants ] │RELEASE TYPE [APP ISO] │
│PACKAGED BY [ Mr no pants ] │RELEASE DATE [May 21, 2001] │
│PROTECTION [ serial ] │RELEASE SIZE [xx/32] │
└─────────────────────────────────┼──────────────────────────────────┘
│
┌──────────┴───────────┐
│░▒▓█ RELEASE INFO █▓▒░│
└──────────┬───────────┘
│
┌─────────────────────────────────┴──────────────────────────────────┐
│ The features in the table below illustrate why the Microsoft │
│ Windows XP Professional operating system is the best choice for │
│ businesses of all sizes. Windows XP Professional integrates the │
│ strengths of Windows 2000 Professionalùstandards-based security, │
│ manageability, and reliabilityùwith the best business features of │
│ Windows 98 and Windows MeùPlug and Play, simplified user interface, │
│ and innovative support servicesùto create the best desktop operating│
│ system for business. Whether your business deploys Windows XP │
│ Professional on a single computer or throughout a worldwide network,│
│ this new operating system increases your computing power while │
│ lowering the total cost of ownership for desktop computers. │
└─────────────────────────────────┬──────────────────────────────────┘
│
┌──────────┴───────────┐
│░▒▓█ INSTALL INFO █▓▒░│
└──────────┬───────────┘
│
┌─────────────────────────────────┴──────────────────────────────────┐
│ Unrar this release and burn the image to a recordable CD-R. │
│ │
│ Serial code :DTWB2-VX8WY-FG8R3-X696T-66Y46 also on cd. │
└─────────────────────────────────┬──────────────────────────────────┘
│
│
┌────────┴────────┐
│░▒▓█ MEMBERS █▓▒░│
└────────┬────────┘
│
┌─────────────────────────────────┴──────────────────────────────────┐
│ No need to list them here. You know if you are one. │
└─────────────────────────────────┬──────────────────────────────────┘
│
┌─────────┴─────────┐
│░▒▓█ Join DFF! █▓▒░│
└─────────┬─────────┘
│
┌─────────────────────────────────┴──────────────────────────────────┐
│If you think you fit in this group and you are willing │
│to help us in making DFF even better than it is now, │
│feel free to contact us by mail at info@dff-board.nl. │
│tell us about your how, what and why. │
│ │
│Currently we are looking for: │
│ │
│ � Suppliers (Movies, Games, Apps) │
│ � 10+ MBiT & 10+ GB Sites │
└─────────────────────────────────┬──────────────────────────────────┘
│
┌──────────┴───────────┐
│ ░▒▓█ DFF SITES █▓▒░ │
└──────────┬───────────┘
│
┌─────────────────────────────────┴──────────────────────────────────┐
│ XXX.XXX.XXX.XXX............ 100 MBiT .................. NL HQ │
│ XXX.XXX.XXX.XXX............ 10 MBiT .............. 2ND NL HQ │
│ XXX.XXX.XXX.XXX............ 10 MBiT ...............3RD NL HQ │
│ XXX.XXX.XXX.XXX............ 10 MBiT ...............4TH NL HQ │
│ XXX.XXX.XXX.XXX............ 10 MBiT ................ DUMP HQ │
│ ??? (you maybe?)........... ? MBiT ................... ? HQ │
└─────────────────────────────────┬──────────────────────────────────┘
│
┌────────┴─────────┐
│░▒▓█ GREETS █▓▒░│
└────────┬─────────┘
│
┌─────────────────────────────────┴──────────────────────────────────┐
│ We would like to greet: │
│ │
│ │
│ Friends in other groups suchs as: │
│ │
│ │
│ EPiSODE, WAD, IRP-FXP, ViSiON, Rosevalley, Anatomic, │
│ and all the others i forgot to mention! │
│ Our special tnx go to Marve ,[AA]FXP ,[AA]maus and Sjomp │ │
│ │
└─────────────────────────────────┬──────────────────────────────────┘
│
┌─────────┴──────────┐
│░▒▓█ CONTACT US █▓▒░│
└─────────┬──────────┘
│
┌────────────────────────────────┴──────────────────────────────────┐
│ [WWW] ............................... [ http://www.dff-board.nl ]│
│ [eMail].................................... [ info@dff-board.nl ]│
│ [IRC] ........................... [ IRC @ EFNET in channel #DFF ]│
└───────────────────────────────────────────────────────────────────┘