Mail Archives: djgpp/1998/06/18/01:18:40
This is a multi-part message in MIME format.
------=_NextPart_000_01BD9A3E.3E298440
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
HELP!,
I have a question about The Microsoft SDK and some directx samples. I
can't figure out how to install MSSDK so I can use the DJGPP to compiler
programs using the MSSDK includes. I also can't figure out how to use the
make program that comes with DJGPP to compiler the samples I got with the
MSSDK. If had an anwser to the first question that would probably slove
the second question. I would really appreciate any help. The MSSDK is
kind of short on documentation.
thank you,
Dino Gigliotti.
I just included the th MSSDK documentation in the email below:
Microsoft Windows Platform Software Development Kit (SDK)
Readme.txt
January 1998
=========
Contents:
=========
1. Platform SDK General Release Notes
2. Tested Compilers
3. Header File Conventions
4. UUID.Lib for Internet Explorer 4.0 and Windows
NT 5.0 Beta 1
5. Windows NT Server/Enterprise Edition 4.0 Support
6. Supported Internet Explorer Versions
7. NTFS 5.0 Release Notes
8. NetShow Version 2 Client Release Notes
9. RPC/MIDL Release Notes
10. OLE DB 1.5 Beta 2 Pre-release Notes
11. IIS 4.0 Beta 3 Release Notes
12. What's New in IMM/IME
13. What's New in Active Server Pages and Internet
Information Server
14. Developing TAPI 3.0 Applications
15. Windows NT 5.0 Beta 1-specific headers
16. Microsoft Small Business Server
17. Management Information Base (MIB) Files
18. Windbg Extensions and OS-specific Subdirectories
19. Microsoft SDK for Java 2.01
=====================================
1 Platform SDK General Release Notes
=====================================
1.1 Setup
---------
It is recommended that you either remove any previous installations
of the Platform SDK or install this release into a new, separate
directory. This January 1998 release of the Platform SDK supersedes
the previous release.
If you load the Platform SDK compact disc onto a machine running
Microsoft (R) Windows NT 5.0 Beta 1, the autorun feature may not
display readme.htm from the root of the compact disc. You will need
to specify a path for Microsoft (R) Internet Explorer (or let the
system locate it), then eject and reinsert the Platform SDK CD.
This is a known issue with this release of Windows NT and will
be fixed in a later release.
To set the SDK path, run SETEVN from your Platform SDK installation
directory. The MSSDK path must appear before your compiler path.
Usage: SETENV MSSDK
Where: MSSDK specifies where the Platform SDK was installed
Example: SETENV C:\MSSDK sets the environment relative to C:\MSSDK
If you are using Microsoft Visual C++ as your compiler, run
VCVARS32.BAT before running SETENV.BAT from the Platform SDK.
1.1 Documentation Setup
------------------------
If you are installing both the MSDN Library and the Platform
SDK documentation, it is recommended that you install the
Platform SDK documentation *after* you install the MSDN
Library. In addition, we have provided a batch file on the CD,
\mssdk\help\fixdocs.bat, which will review your registry and make
sure that you are viewing the latest version of the
documentation.
Note that the January 1998 Platform SDK documentation
contained on this compact disc is more recent than the
SDK documentation installed by Visual Studio version 5.0
(or earlier) and the MSDN Library January 1998 (or
earlier). The Platform SDK setup automatically replaces
your existing content with the updated content. If you
install an older copy of the SDK documenatation from
another source, you can reinstall the SDK documentation
on this compact disc to get the updated content.
1.3 Microsoft VM for Java
----------------------------
The most recent release of the Microsoft VM for Java can be installed
from <cd drive:>\Mssdk\Redist\JavaVM\MSJavAxp.exe or
<cd drive:>\Mssdk\Redist\JavaVM\MSJavx86.exe.
1.4 Known Issues
----------------
Running InfoViewer 5.0 on Windows NT 5.0 Beta 1 causes the
"Font setting for InfoViewer topic" to be set to very small.
Changing this setting from within InfoViewer has no effect.
To change the font size:
1. From the InfoViewer Tools menu, click Options.
2. Click the InfoViewer tab.
3. Click the Internet Explorer Options button.
4. Click the Accesibility button.
5. Check the Ignore font sizes specified on Web pages.
Problems with OLE DB and OCMM.h.
If you're using OLEDB.h and include OCMM.h into your project then you will
not
be able to compile your application. This is a known problem and will
being
addressed in a future release. If you need to use both OLE DB and the
interfaces
defined in OCMM then you will need to segment your code into multiple
source files,
some that use OLEDB and some that use OCMM.
The following samples do not build on Alpha. In some cases, the Microsoft
Visual C++ makefile shipped with the sample specifically targets x86.
In these cases, you can load the sample into Microsoft (R) Developer
Studio (R) and create an Alpha target.
Mssdk\Samples\Graphics\BA\Tvxsamp
Mssdk\Samples\Graphics\DirectX\Memtime
Mssdk\Samples\Internet\IE\ColBtn
Mssdk\Samples\Internet\IE\Drill\Driller
Mssdk\Samples\Internet\IE\IELnk
Mssdk\Samples\Internet\IE\IEMime
Mssdk\Samples\Internet\IE\IISLog
Mssdk\Samples\Internet\IE\Percy
Mssdk\Samples\Internet\IE\TDC
Mssdk\Samples\Internet\IE\UrlMon\Progress
Mssdk\Samples\Internet\IE\WabTool
Mssdk\Samples\Internet\IE\WalkAll
Mssdk\Samples\Internet\MSChat\Chat2000
Mssdk\Samples\Internet\NetMeeting\InstCodc
Mssdk\Samples\Internet\NetMeeting\NMFT
Mssdk\Samples\Internet\NetMeeting\NMShare
Mssdk\Samples\Internet\NetMeeting\NMUI
Mssdk\Samples\Internet\NetMeeting\Skippy
The following samples contain inline assembly and do not
build on Alpha.
Mssdk\Samples\WinBase\Security\WinNT\SampSSP
Mssdk\Samples\Graphics\DirectX\Duel
Mssdk\Samples\Graphics\DirectX\Flip2D
The following samples require Microsoft Internet Explorer
version 4.0 or later, which was not available on Alpha when
this compact disc was released.
Mssdk\Samples\WinUI\Shell\RegView
In winerror.h, the old error define:
CERT_E_VALIDIYPERIODNESTING
has been changed to:
CERT_E_VALIDITYPERIODNESTING
If you want to install the Platform SDK on Alpha using
the new browser-based setup, you must change your
Internet Explorer security settings to None.
==================
2 Tested Compilers
==================
The Platform SDK has been tested with Microsoft (R) Visual
C++ (R) version 5.0. Most samples will build with other
compilers, but other compilers were not explicitly tested.
2.1 Common Sources of Warnings
---------------------------------
* MakeProcInstance: Do not use this function. Pass
DLGPROC directly (the first parameter to MakeProcInstance).
Also, be sure to delete the FreeProcInstance function
that is paired with MakeProcInstance.
* Explicit casts are now necessary in many situations
where intrinsic casts worked before. An example:
MSSDK\samples\dbmsg\sql\dblib\c\sqltestn\SqltestN.c(186).
The (DLGPROC) cast was not necessary before. A warning
is now generated if a cast is omitted.
* CODE and DATA statements are not supported for use in
makefiles on the i386 platform.
=========================
3 Header File Conventions
=========================
If you want to target: You should set:
---------------------- ---------------
Microsoft (R) Windows (R) 95 WINVER=0x0400
and Windows NT 4.0 (and later)
Microsoft (R) Windows (R) 98 _WIN32_WINDOWS=0x0500
and Windows NT 4.0 (and later) WINVER=0x0400
Windows NT 4.0 (and later) _WIN32_WINNT=0x0400
WINVER=0x0400
Windows 98 and Windows NT 5.0 WINVER=0x0500
(and later)
Internet Explorer 3.0 _WIN32_IE=0x0300
(and later)
Internet Explorer 4.0 _WIN32_IE=0x0400
(and later)
Setting a WINVER of 0x0500 implies _WIN32_IE=0x0400
In the header files,
information guarded by: Is implemented in:
------------------------ ------------------
#if _WIN32_WINNT >= 0x0400 Windows NT 4.0 and later.
It is not implemented in
Windows 95.
#if _WIN32_WINDOWS >= 0x0500 Windows 98 and later.
#if _WIN32_WINNT >= 0x0500 Windows NT 5.0 and later.
#if WINVER >= 0x0500 Windows NT 5.0 and later
and Windows 98 and later.
#if _WIN32_IE >= 0x0300 Internet Explorer 3.0
and later.
#if _WIN32_IE >= 0x0400 Internet Explorer 4.0
and later.
#if _WIN32_WINCE Microsoft Windows CE 1.0
and later.
The value of _WIN32_WINNT is set in WIN32.MAK, depending on the
platform you choose to target. By default, WIN32.MAK sets the
TARGETOS to WINNT and the APPVER to 4.0. As a result, by default,
_WIN32_WINNT is now defined as 0x0400.
By default, WIN32.MAK sets _WIN32_IE to 0x0300 if it is not
already defined. To specifically target Internet Explorer 4.x or
to take advantage of the new CommCtrl features introduced in
Internet Explorer 4.0, set _WIN32_IE to 0x0400.
If you are building an application to run on Windows 95 and you want
compile-time notification of compatibility issues, set TARGETOS=BOTH
in your makefile. When TARGETOS is defined as BOTH, _WIN32_WINNT is
not defined for the precompiler, and the only information parsed at
compile time is applicable to both Windows 95 and Windows NT.
If you do not include WIN32.MAK in your makefile, you need to
explicitly define _WIN32_WINNT as 0x0500 to get the Windows NT
5.0-specific material from the header files.
There are several API sets present in Windows 95, OEM Service
Release 2 that are still guarded by (_WIN32_WINNT >= 0x0400),
that is, CryptoAPI. If you are writing an application
specifically for Windows 95, OEM Service Release 2, and you
want the header files to provide compile time access to these
functions, it is necessary to define _WIN32_WINNT as 0x0400.
Notice that an application that uses these technologies does
not run correctly on the retail release of Windows 95. The
vast majority of applications that are expected to run
on Windows 95 should be built without defining _WIN32_WINNT.
Previous releases of the Platform SDK or Win32 SDK included
definitions in WIN32.MAK to map structured exception handling
keywords to their proper underscored names:
try -> __try
except -> __except
finally -> __finally
leave -> __leave
This caused problems for developers who chose to use C++
structure exception handling where "try" is supposed to
be "try" and not "__try". For this reason, by default,
the mapping has been removed from WIN32.MAK. This may
cause build-time errors for your applications. To get
the old behavior add
SEHMAP = TRUE
to your makefile before including WIN32.MAK.
=======================================
4 UUID.Lib for Internet Explorer 4.0
and Windows NT 5.0 Beta 1
=======================================
Internet Explorer 4.0 and Windows NT 5.0 Beta 1 are
built with slightly different versions of UUID.Lib.
Just as Windows NT 5.0 Beta 1 uses a slightly older
version of Internet Explorer 4.0 based on Platform
Preview 2, Internet Explorer 4.0 is built using
a slightly older version of UUID.Lib from Windows
NT 5.0 Beta 1.
The default UUID.Lib in the Platform SDK has the
Internet Explorer 4.0 shell GUIDs.
In most cases this will not cause a problem. However,
if you are targeting new shell development on Windows
NT 5.0, there are a few GUIDs that differ between
Windows NT 5.0 Beta 1 and Internet Explorer 4.0. For
example, the GUID for IShellUIHelper has changed. To
use the Windows NT 5.0 Beta 1 GUIDs please replace
\MSSDK\Lib\UUID.Lib with \MSSDK\Lib\NT5B1\UUID.Lib.
For a complete list of differences, please review the
header changes using "windiff %mssdk%\Include
%mssdk%\Include\NT5B1". Many of the differences are due
to slightly different versions of MIDL used to generate
the Internet Explorer 4.0 and Windows NT 5.0 Beta 1
headers; using the F7/F8 keys you can quickly review
the changed lines.
===================================================
5 Windows NT Server/Enterprise Edition 4.0 Support
===================================================
This release of the Platform SDK adds support for
Microsoft Windows NT Server/Enterprise Edition 4.0.
In addition to Microsoft Cluster server, Microsoft
Message Queue Server and Microsoft Transaction Server,
Windows NT Server/Enterprise Edition 4.0 also
has been enhanced with 4 Gigabyte Tuning (4GT) to
support very large user mode address spaces (3 GB of
user-mode addressable space instead of the usual 2 GB).
To allow your application to run using all 3 GB of
address space it is necessary to re-link your application
using the updated linker provided in the Platform SDK and
to add "/LARGEADDRESSAWARE" to the linker command line.
It is necessary to review and test your application to
ensure that it works properly with the 3 GB address space.
During internal testing of 4GT many applications were found to
store pointers using signed integers and to have problems
with addresses larger than 2 GB. The /LARGEADDRESSAWARE
switch will only affect the behavior of your application
when run on Windows NT Server/Enterprise Edition. The
/LARGEADDRESS aware switch will only affect .EXEs.
However any DLL, control, or COM object loaded into that
address space will see the full 3 GB address space. It
is recommended that all control and COM objects be tested
with containers linked using /LARGEADDRESSAWARE and run
on Windows NT Server/Enterprise Edition.
===================================================
6 Supported Microsoft Internet Explorer versions
===================================================
Due to the fact that several versions of Internet Explorer
are available as part of your MSDN subscription, not all
samples and/or applications may behave the same on all
versions of Internet Explorer. You may observe different
behavior between beta versions of Windows 98 and Windows
NT 5.0 Beta 1 and the released versions of Internet
Explorer 4.0 and 4.01.
==========================
7 NTFS 5.0 Release Notes
==========================
7.1 Native structured storage for NTFS 5.0
-------------------------------------------
OLE structured storage has traditionally used a flat
compound file (docfile) format to allow maximum portability.
However, it is desirable for elements of the IStorage and
IStream interfaces to reside natively in the file system
for better performance and scalability, and to expose file
system features. Native structured storage takes advantage
of the Microsoft(R) Windows NT(R) file system (NTFS)
version 5.0 files in that they can contain multiple data
streams. Native structured storage (NSS) is a multistream
file format where IStream input/output (I/O) is more
efficient because it is mapped to a native NTFS stream.
NSS is compatible with all applications that use OLE
structured storage, and NSS files can only exist on
NTFS 5.0 volumes.
Copying an NSS file to a file allocation table (FAT) or
NTFS version 4.0 volume results in downgrading the NSS
file to a docfile. Accessing an NSS file from a remote
client (that is, a client that opens a file through the
redirector), accessing it directly with the CreateFile
function, or with the StgOpenStorage or StgCreateDocfile
functions, triggers a conversion. In a conversion, a
docfile view is seen by the client, but the file remains
in NSS format on disk. It is not currently possible
to create a new NSS file on a remote machine. The size
of an NSS file as reported by the "dir" command, and
probably by other utilities, is the size of the default,
or unnamed, data stream, not the total size of all the
streams. Thus the size reported may be smaller than the
actual size of the NSS file. This size reporting problem
will be fixed after Beta 1.
Two new functions can be used to create or open NSS files:
StgCreateStorageEx and StgOpenStorageEx. In this beta
release of Microsoft Windows NT 5.0, the STGFMT_STORAGE flag
(passed in the stgfmt parameter) is treated equivalently to
the STGFMT_NATIVE flag when the riid parameter is IID_IStorage.
In the next beta release, and the final release, of Microsoft
Windows NT 5.0, the STGFMT_STORAGE flag will be interpreted
to indicate that either NSS or a docfile storage is
acceptable.
For compatibility testing, the old docfile functions can
be enabled to create and open NSS files on NTFS 5.0 volumes
automatically by setting the following registry key values:
\HKLM\Software\Microsoft\Ole\
EnableNtfsStructuredStorage = "YY"
EnableCNSS = "Y"
7.2 NTFS Property Sets
----------------------
The OLE Structured Storage specification includes a
definition of the Property Set layout format. This
property set format for compound files ("docfiles") is
currently implemented. With this beta release of Microsoft
Windows NT 5.0, these property sets are also implemented
natively on NTFS files (for volumes formatted with the NTFS
5.0 file system). Because these property sets are
implemented directly by the file system, they are extremely
robust.
NTFS property sets are stored in a file as special streams,
alongside the file's data streams. You can create, open,
and delete property set streams using the normal file
manipulation functions, but it is not possible to directly
read or write a property set stream.
To create, open, delete, and manipulate NTFS property sets,
you use the IPropertySetStorage and IPropertyStorage interfaces,
just as you do with compound file property sets. To get an
IPropertySetStorage interface, you use the new StgCreateStorageEx
and StgOpenStorageEx functions, using the format flag STGFMT_FILE
and the interface identifier IID_IPropertySetStorage. For
example, if you have an HTML file with the name "default.html",
you can get an IPropertySetStorage interface for it, and use
it to put property sets on the file. To get the
IPropertySetStorage interface, you use the call:
IPropertySetStorage *pPropSetStg = NULL;
StgOpenStorageEx( L"default.html",
STGM_READWRITE | STGM_SHARE_EXCLUSIVE,
STGFMT_FILE,
0L,
NULL,
NULL,
IID_IPropertySetStorage,
(void**) &pPropSetStg ));
Once you have this IPropertySetStorage, you can call the
Create and Open methods to manipulate property set streams
for the file. Programs that only use the default data stream
on a file are unaware of these property sets. In the
preceding example, a Web browser continues to use the
"default.html" file as usual, having no awareness of the
fact that the file also had property set streams.
Please note the following:
* Microsoft Windows NT 5.0 does not use the IPropertyStorage
and IPropertySetStorage interfaces to create and manage
persistent property sets associated with files in the
Windows NT file system (NTFS). The system-provided
implementations of these interfaces apply to compound
files and do not apply to properties associated with
native files on an NTFS 5.0 partition.
* NTFS property sets currently only support Unicode, simple
property sets. Therefore, the PROPSETFLAG_ANSI and
PROPSETFLAG_NONSIMPLE flags on the
IPropertySetStorage::Create method are invalid.
* NTFS property sets are not currently supported for files
on a remote machine. For example, if X: is a remote
(redirected) drive, it is not valid to attempt to get an
IPropertySetStorage interface on the file "X:\DEFAULT.HTML".
* The IPropertyStorage::SetClass method is not implemented.
Also, NTFS property sets do not support timestamps, so the
IPropertyStorage::SetTimes method succeeds but cannot
actually store the times.
* NTFS property sets do not support transactioning, so the
IPropertyStorage::Revert method has no effect. The
IPropertyStorage::Commit method can still be used to flush
the property set to the disk.
* In the compound file implementation of property sets, an
IPropertyStorage is contained within the IPropertySetStorage
that created it. Thus, an IPropertySetStorage that was created
in read-only mode cannot be used to create an IPropertyStorage
in read/write mode. Similarly, if a compound file
IPropertySetStorage is released, its child IPropertyStorage
objects are put in the Reverted state. With NTFS property
sets, this containment does not currently exist, though similar
semantics may be added in a later release of Windows NT 5.0. When
you create or open an NTFS IPropertySetStorage, the flags you
specify in the grfMode parameter to the StgCreate or OpenStorageEx
functions are used to open the default data stream on the file.
When you subsequently create or open property sets, the flags
you specify in the grfMode parameter to the
IPropertySetStorage::Create or IPropertySetStorage::Open methods
are used to open the property set stream. This property set
stream can be opened with a mode that is inconsistent with
the mode used to open the IPropertySetStorage, and the
IPropertyStorage remains in a usable state even if the
IPropertySetStorage is released.
* When an NTFS file with property set streams is copied to
any file system other than NTFS 5.0, the property sets are
lost. So if you copy the "default.html" file in the preceding
example to a FAT file system, the default data stream is copied
successfully, but the property sets are lost. If you copy it to
an NTFS file system earlier than 5.0, all data streams are copied,
but again the property set streams are lost. The BackupRead and
BackupWrite functions behave in the same manner; restoring to an
NTFS 5.0 volume restores the property sets, restoring to another
file system does not.
7.3 Simple Mode Compound File Property Sets
-------------------------------------------
Compound file storages provide native support for property sets.
It was not previously possible, however, to obtain a property
set interface for a simple mode storage (a storage obtained
using the STGM_SIMPLE flag). With this release of Microsoft
Windows NT 5.0 Beta 1, simple mode compound file property sets
are now possible. A simple mode property set is obtained as are
compound file property sets, by calling IStorage::QueryInterface
for the IID_IPropertySetStorage interface. When the storage being
queried is in simple mode, the resulting IPropertySetStorage is
also in simple mode, as are IPropertyStorage objects that are
created by the IPropertySetStorage.
Simple mode property sets are subject to the same constraints as
simple mode storages. For example, after creating a property set
with IPropertySetStorage::Create, the resulting IPropertyStorage
must be released before another can be created. Note that in
this beta release of Microsoft Windows NT 5.0, it is possible to
marshal a simple mode IPropertyStorage, whereas in the final
version of Windows NT 5.0 this will not be possible.
==============================================
8 NetShow Version 2 Client Release Notes
==============================================
8.1 File Transfer Control Packet Formats
-----------------------------------------
The packet format used by the File Transfer service has changed
from that used in previous releases. Make sure the Microsoft(R)
NetShow(TM) server that is sending files and the File Transfer
control receiving files are the same release version. The NetShow
version 2.0 File Transfer control does not work with NetShow
server version 1.0 or previously released beta versions of
NetShow server.
8.2 Type Property
-----------------
Using Microsoft(R) Visual Basic(R) Scripting Edition (VBScript)
to set the value of the Type property exposed by the NetShow File
Transfer control requires the following syntax to work with
Microsoft(R) Internet Explorer version 4.0
NSFile1.object.Type
where NSFile1 is the NetShow File Transfer control object.
Earlier versions of Internet Explorer do not require or accept
the object keyword. Use the following syntax to access the
Type property with earlier versions of the browser:
NSFile1.Type
Note: This special syntax applies only to the Type property
exposed by the control. The object keyword is not required to
set any of the other properties running any version of
Internet Explorer.
8.3 "Receive Unicast" and "Total Demo" File Transfer Examples
-------------------------------------------------------------
Unicast file transfers require a stream-type socket connection.
Stream sockets use Transmission ControlProtocol (TCP), which
ensures the reliability of the transmission. Forward error
correction (FEC) is provided for multicast file transfers using
connectionless protocols, such as User Datagram Protocol (UDP)
and should not be used with stream sockets. Because of this,
the "Receive Unicast" example and the "Total Demo" example (when
it is used to receive unicast file transfers), need changes
before they work.
To use these example pages, make the following corrections to
their BtnReceiveFile_OnClick subroutines:
1. For unicasts, set the value of the Type property specifying
the socket type to use a stream socket connection (SOCK_STREAM)
and not a datagram socket connection (SOCK_DGRAM).
The command
nsfile1.Type=2
should be changed to
nsfile1.Type=1
2. Because stream sockets support TCP, FEC should not be
enabled for receiving unicasts, and the command
call nsfile1.FtsStartFileTransferReceive("", 5050, "", "%TEMP%\", 0,
1025)
should be changed to
call nsfile1.FtsStartFileTransferReceive("", 5050, "", "%TEMP%\", 0, 1024)
8.4 "Receive Multicast with Progress" Example
---------------------------------------------
The "Receive Multicast with Progress" example page has a
typographical error in the ButtonReceiveFile_OnClick subroutine.
The command
call nsfile1.FtsRegisterStatusCallback(0, 0, 4096, 4096, 0, , 0, 0, 0, 0,
0)
should be
call nsfile1.FtsRegisterStatusCallback(0, 0, 4096, 4096, 0, 0, 0, 0, 0, 0,
0)
8.5 Real-Time Encoder
----------------------
The Real-Time Encoder application sets the duration in minutes,
hours, and days, but the Automation interface allows only
values measured in seconds.
=================================
9 RPC/MIDL Release Notes
=================================
9.1 What's New
--------------
Asynchronous RPC. The RPC run-time environment now supports
asynchronous remote procedure calls to allow your programs
to handle multiple outstanding calls from a single-threaded
client and prevent data transmission bottlenecks that can
arise from slow or delayed clients or servers. With
asynchronous pipe parameters, client/server applications
can transfer large amounts of data incrementally, without
blocking the client or server threads from performing other
tasks. For more information, see the Asynchronous RPC section
in the Platform SDK online documentation.
New HTTP protocol sequence. The ncacn_http protocol allows
client and server applications to communicate across the
Internet by using the Microsoft(R) Internet Information
Server (IIS) as a proxy. Because calls are tunneled through
an established HTTP port, they can cross firewalls.
Name Service: The Remote Procedure Call (RPC) Name Service
(Locator) uses the Windows NT 5.0 Active Directory as its
database. This means that exported entries can be made
persistent even when a server is rebooted. For more information,
see the RPC reference pages for RpcNsBindingExport,
RpcNsBindingImportNext, RpcNsBindingLookupBegin, and
RpcNsBindingUnexport in the Platform SDK online documentation.
New Type Library Attributes. Microsoft Interface Definition
Language (MIDL) supports Double-Byte Character Set (DBCS)
international locales now. TLB file generation has been
significantly improved and all the type library attributes
are supported now. For more information, see Type Library
Attributes in the Platform SDK online documentation.
9.2 Known Limitations for Beta 1
----------------------------------
RPC over Microsoft Message Queue Server (MSMQ). There is no
official support for MSMQ, and MSMQ servers can not be
directly installed on Microsoft Windows NT 5.0 beta 1.
However, independent and dependent clients can be installed
for evaluation purposes.
Asynchronous pipes had a limited testing.
If you are using RPC over MSMQ (ncadg_mq) protocol, the
current MSMQ installation configures the RPC registry entries
for the Microsoft Windows NT 4.0 configuration. These must
be manually modified using Regedit32.Exe in order for RPC
over MSMQ to operate on Windows NT 5.0 Beta 1. Change the
values for the registry entries
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols\ncadg_mq
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ServerProtocols\ncadg_mq
from "RpcMqCl.dll" and "RpcMqSvr.dll" (respectively) to
"RpcLt1.dll".
9.3 MIDL Version
------------------
The current version of MIDL shipped on this compact disc is
version 3.3.0110. This version of MIDL supports developers who are
using Windows NT 4.0/Visual C++ 5.0 or Windows NT 5.0 Beta 1 (the
Platform SDK build environment). It is not compatible with a
Windows NT 4.0/Visual C++ 4.x environment. If you want to use the
latest MIDL compiler in this environment, or if you want to use the
latest MIDL compiler and distribute the MIDL generated files to
developers on environments other than those supported, you must
provide two additional files, rpndr.h and rpcproxy.h, from the
\mssdk\include directory of this compact disc.
=======================================
10 OLE DB 1.5 Beta 2 Pre-release Notes
=======================================
The major changes to the OLE DB Specification
(OLEDB15SPEC.HLP) since OLE DB version 1.5 beta 1
are as follows:
1. The beta 1 version of the IRowsetFind interface
has been changed to more closely align with the
IRowset::GetNextRows and IRowsetLocate::GetRowsAt
methods.
Specifically:
a. The methods FindNextRow and GetNextRows now share
the same fetch position. b. The fSkipCurrent argument of
FindNextRow has been replaced by ulRowsOffset, with the
same semantics as the ulRowsOffset argument in GetNextRows
and GetRowsAt.
2. Rowset Views have been added for applying simple
filtering and sorting to a rowset.
3. Numerous clarifications and bug fixes were made
throughout the document.
The header and library files included here reflect the
changes made in the OLE DB 1.5 beta 2 specification and
are newer than the header files provided in the original
OLE DB 1.5 beta 1 release.
The OLE DB Leveling document (OLEDBLeveling.doc) has also
been updated since the original OLE DB 1.5 beta 1 release.
The main changes to the leveling document include:
1. DBPROP_CANFETCHBACKWARDS is only required for providers
that also support DBPROP_CANSCROLLBACKWARDS.
2. Providers are not required to support DBPROP_COMMITPRESERVE,
because a number of relational providers do not support
preserve semantics.
3. The OLE DB Simple Provider Toolkit has been added as a
means of producing an OLE DB provider that exposes the
minimal consumer interfaces.
4. Additional clarifications have been made throughout
the document.
================================================
11 Microsoft Internet Information Server (IIS)
version 4.0 Beta 3 Release Notes
================================================
11.1 IRequestDictionary::get_Item
-----------------------------------
The IRequestDictionary::get_Item reference page does
not completely explain how to use the method to retrieve
an item from a Request collection. The method returns a
pointer to a variant. The data type of the variant that
is returned is VT_DISPATCH. If you need to convert the
returned item to a BSTR, you can use the Microsoft(R)
Win32(R) function, VariantChangeType. For more
information on VariantChangeType, see Variant Manipulation
functions in the Platform SDK.
11.2 IIS Headers
---------------
During installation the IIS headers are installed in
one of two places. If the Platform SDK is installed on
the system, then the headers are copied into its include
directory. If the Platform SDK is not installed on the
system, then the headers are copied to
\inetpub\iissamples\sdk\include. Before building IIS
4.0 specific projects, you must copy these headers to
the include directory of your build environment.
Please note that the Microsoft Transaction Server (MTS)
headers and libraries must be copied into your development
environment before building server components that use the
IContextObject interface to access the Active Server Pages
(ASP) intrinsics. MTS installs its headers and libraries
in the \Program files\Mts\ directory.
11.3 Sample Java Components
---------------------------
The sample Java components described in the documentation
have been replaced by the Java Component Framework samples.
These samples, along with the relevant documentation, can
be found in the directory
\Mssdk\Samples\Internet\Iis\Components\Java\Framework.
11.4 Java Class and Interface Definitions
----------------------------------------
The Java Class and Interface definitions topic contains
an error.
It states
"The Java type libraries are not installed with ASP. If
you are using Microsoft® Visual J++, you can generate
classes from the Microsoft Active Server Pages Object
Library with the Java Type Library Wizard.
"To use the built-in object interfaces in a Java
component, you must import the ASP classes into your
code as shown below.
"import asp.*;"
The topic should read
"The Java ASP interface class files are installed with PWS.
"To use the built-in object interfaces in a Java component,
you must import the ASP classes into your code as shown below.
"import com.ms.asp.*;"
11.5 Administration Property Reference
-------------------------------------
In the Administration Property Reference, the documentation
for the AspScriptTimeout property incorrectly states that
"A value of -1 for this property will disable script time-out
and allow the script to run indefinitely." The minimum value
for this property is 1 second.
In the Metabase Identifier Reference, the documentation for
the MD_ASP_SCRIPTTIMEOUT property incorrectly states that
"A value of 0xFFFFFFFF will allow a script to run indefinitely."
The range of values for this property is 1 through 0xFFFFFFFE.
===========================
12 What's New in IMM/IME
===========================
The Windows 98 and Windows NT 5 IMM/IME architecture retains the
Windows 95/Windows NT 4.0 design with some improvements to better
support intelligent IME development and integration of IME with
Windows. These changes are briefly listed following.
Note: The Platform SDK provides IME API documentation for
application development. For information on IME development, refer
to the Microsoft Windows NT Device Driver Kit documentation.
12.1 New IME function for applications
-------------------------------------
The following new IME functions allow applications to communicate
with IMM/IME:
ImmAssociateContextEx
ImmDisableIME
ImmGetImeMenuItems
12.2 New functions for IME developers
------------------------------------
The following new functions allow IMEs to communicate with IMM
and applications:
ImmRequestMessage
ImeGetImeMenuItems
12.3 Supporting reconversion
---------------------------
This is a new IME feature that allows you to reconvert a string
that has already been inserted into the application's document.
This function helps intelligent IMEs to get more information
about the converted result and improves conversion accuracy and
performance.
12.4 Adding IME menu items into Context menu of the system Pen icon
-------------------------------------------------------------------
This new feature provides a way for IMEs to insert the new IME
menu items into the Context menu of System Pen Icon in System Tray.
12.5 New bits and values for IME
-------------------------------
The following new bits support new conversion modes:
IME_CMODE_FIXED
IME_SMODE_CONVERSATION
IME_PROP_COMPLETE_ON_UNSELECT
12.6 Edit control enhancement for IME
------------------------------------
Through the two new edit control messages, EM_SETIMESTATUS and
EM_GETIMESTATUS, applications can manage IME status for edit
controls.
=====================================================================
13 What's New in Active Server Pages and Internet Information Server
=====================================================================
The Active Server Pages and Internet Information Server sections
of the Platform SDK include the following changes from the previous
release.
Section Sub-section Change
------- ----------- ------
Active Server Built in ASP Object Reference pages for new
Pages Reference methods, collections,
and objects have been
added.
Active Server Directive Reference This is a new set of
Pages reference pages for all
of the ASP @ directives.
Active Server Installable Components Reference pages for new
Pages components that ship with
IIS 4.0 have been added.
Active Server Windows Scripting Host This is a new set of
Pages reference pages for the
Windows Scripting Host.
Internet Web Application This is a new overview
Information Development Guide section that describes
Server Microsoft's programming
model for developing
applications on the
Internet and
intranets.
Internet Programmer's Overview sections have
Information Reference/Creating been revised to describe
Server Components for ASP the integration with
Microsoft Transaction
Server. New reference
pages for C++ and Java
interfaces have been
added.
Internet Programmer's This is a new section
Information Reference/IIS that contains both
Server Administration overview topics and
reference pages that
describe how to
administer Internet
Information Server
programmatically.
The data store for
configuration
information is
described. Reference
pages for the
interfaces that can
be used by programs
and the Automation
properties that can
be used by scripts
are included.
Internet Programmer's This is a new section
Information Reference/Logging that contains both
Server Interface overview topics and
reference pages that
describe how to control
logging IIS events
programmatically. It
describes both how to
use the Automation
properties in the
IIS data store, and
how to create a custom
logging module.
Internet Programmer's The overview topics
Information Reference/ISAPI have been revised to
Server provide more detail on
how to develop ISAPI
extensions and filters.
The overview topics
also describe new ISAPI
features. Reference
pages have been divided
into two sections, one
for ISAPI extensions,
and another for
SAPI filters.
Internet Programmer's A list of new sample
Information Reference/Developer scripts and programs
Server Samples that are provided
with the Platform SDK.
====================================
14 Developing TAPI 3.0 Applications
====================================
14.1 Developing TAPI 3.0 Applications
---------------------------------------
* When developing applications that feature TAPI 3.0 audio,
you are not advised to open message boxes that produce a
system sound (e.g. "default beep"), because playing system
sounds might prevent the TAPI 3.0 audio streams from running.
* Static terminals of type "speakers" cannot be used repeatedly
on different TAPI 3.0 calls: once the call (on which such a
terminal has been selected) is disconnected and released, the
static terminal must be released as well. For a new call, query
again the "speaker" terminal from the collection of static
terminals.
These aspects will be addressed in future releases of TAPI 3.0.
14.2 Developing TAPI 3.0 applications with
Visual Basic 5 (SP2)
--------------------------------------------
TAPI 3.0 and Visual Basic 5 SP2 are not fully compatible.
Therefore there are a few problems that developers will
encounter while developing applications that use tapi3.dll:
* Dialog boxes cannot be displayed on event procedures.
* Breakpoints cannot be set in event procedures.
* Occasionally, an access violation can occur in
Tapi3!Next, especially when quitting the application.
These aspects will be addressed in the next version of
Visual Basic or in future releases of TAPI 3.0.
==========================================
15 Windows NT 5.0 Beta 1-specific headers
==========================================
Microsoft Windows NT 5.0 beta 1 ships with the Platform
Preview 2 release of Internet Explorer 4.0. There have
been changes made in the shell and Internet client APIs
between the Platform Preview 2 release and the final
release of Internet Explorer 4.0. Because of these changes,
two versions of several shell headers are provided as
part of the Platform SDK. The default version of the
headers installed to \Mssdk\Include is the final released
Internet Explorer 4.0 versions. If you are targeting shell
development on Windows NT 5.0, you may need to use the
version of the headers provided in \Mssdk\Include\NT5b1.
=====================================
16 Microsoft Small Business Server
=====================================
Documentation on the Microsoft Small Business Server
is available in Microsoft Word format in \mssdk\doc, as
well as in the Platform SDK online documentation (.IVT).
* The Console Customization and Style Guide
(\mssdk\doc\consolesg.doc) outlines the rationale behind the
design of the Microsoft Small Business Server console.
The Console Customization and Style Guide is
also available from the Microsoft web site at
http://www.microsoft.com/backofficesmallbiz.
* You can simplify installing your application on Small
Business Server by integrating your setup program with the
Setup Computer Wizard (SCW). Details on SCW are available
in the Setup and Systems Management node of the
Platform SDK online documentation.
==============================================
17 Management Information Base (MIB) Files
==============================================
Management Information Base (MIB) files are no longer
available on the Microsoft Windows Platform SDK compact
disc. They are available for download from
ftp://ftp.isi.edu/mib/.
======================================================
18 Windbg Extensions and OS-specific Subdirectories
======================================================
Windbg installs two trees for debugger extensions, one
containing files specific to Microsoft Windows NT 4.0 and
one specific to Microsoft Windows NT 5.0. Both the BIN and
SYMBOLS directories contain \NT4 and \NT5 subdirectories.
The Windows NT 5.0 Beta 1 DDK assumes a default of NT5.
The Windows Platform SDK defaults to the OS version on
which it is installed (\NT4 for Windows NT 4.0 and \NT5
for Windows NT 5.0). If you want to use the debugger
for a specific OS other than the default, copy the files
from the .\NT<number> directory into the parent directory.
=================================
19 Microsoft SDK for Java 2.01
=================================
This SDK includes the latest version of the Microsoft
virtual machine for Java (build 2339). This is the
same virtual machine that ships with Internet Explorer
4.01 and provides the fastest, most functional and most
compatible Java support of any major browser.
Among the new features:
* Maintains Java performance leadership
* Win32 Classes for J/Direct - these classes simplify
using J/Direct let developers meld the productivity
of the Java language with the power of Windows.
Includes pre-built declarations for GDI, User, Kernel,
Multimedia and Common Control.
* Application Foundation Classes (AFC) support for
JDK 1.02 browsers - a standalone package for use
with browsers that do not offer sufficient
JDK 1.1 support.
* Console - a much requested developer feature allows
interactive viewing of output from Java programs.
* Permissions-based security - expanded user interface
allows users and administrators to view and edit
their Java security preferences in a very granular
manner, as well as new developer tools to simplify
the process of assigning permissions and signing code.
* Enhanced robustness and scalability for standalone use
* Improved accessibility support
* Improved printing of international characters
Additional information on AFC support for JDK 1.02 browsers
The new AFC standalone package included in this release
allows AFC to be used in browsers which do not offer
adequate JDK 1.1 functionality, such as Internet Explorer 3.0,
Netscape Navigator 3.0, and Netscape Navigator 4.0. The
original AFC classes that were released with Internet
Explorer 4.0, now being used by millions of users, relied
upon JDK 1.1 functionality. This new AFC package based
on JDK 1.02 functionality fulfills the stated design goal
for AFC, which was to provide a rich set of components
that could be used to build applets that run cross-browser
on Windows 95/Windows NT, Macintosh and Solaris.
Samples documentation:
The \Mssdk\Samples directory contains Platform SDK samples.
These samples demonstrate the use of interfaces and APIs for
Win32 and BackOffice. The samples run on Windows NT and Windows 95.
Some of the samples use interfaces or APIs that are only available
in beta operating system releases. Refer to the readme.txt in the
root of the Platform SDK CD for more information about how to
build an application using beta interfaces.
The build environment (headers, libraries, and minimum build
tools) for the Platform SDK must be installed in order to build
any of the samples in the \Mssdk\Samples directory. The build
environment can be installed from the readme.htm or by running
setup.exe on the root of the Platform SDK compact disc. The most
recent version of the build environment is also available at
http://www.microsoft.com/msdn/sdk/platform.htm.
Some components may also require you to install runtimes, depending
on the platform on which you are trying to run the sample.
Redistributables are available in the \Mssdk\Redist subdirectory
on the Platform SDK compact disc.
Documentation for the components listed above can be installed
from the Platform SDK compact disc, or can be viewed online at
http://premium.microsoft.com/msdn/library/. This is a free service;
registration is necessary.
Read the release notes in readme.htm and readme.txt in the root of
the Platform SDK compact disc or visist the MSDN web site for more
information about the Platform SDK at http://www.microsoft.com/msdn/sdk/
I included the Setenv file from the MSSDK platform and my currect
autoexec.bat is below.
This what happens when I run Setenv
To set the SDK environment paths, run SETENV from your Platform SDK
installation directory.
Usage: SETENV MSSDK
Where: MSSDK specifies where the Platform SDK was installed
Example: C:\MSSDK\SETENV C:\MSSDK sets the environment relative to
C:\MSSDK
Warning: check your LIB, INCLUDE and PATH to verify that the
SDK Lib, Include, and Bin directories precede the compiler
directories in the environment.
Microsoft Visual Studio provides VCVARS32.BAT to set them.
You must run VCVARS32.BAT first and then run SETENV.BAT.
Current settings:
LIB=
INCLUDE=
PATH=C:\DJGPP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND
This is my current autoexec.bat
LH /L:2,38400 MSCDEX.EXE /D:OEMCD001 /L:D
SET BLASTER=A220 I5 D1 H5 P330 T6
set PATH=C:\DJGPP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND
set DJGPP=C:\DJGPP\DJGPP.ENV
SET MIDI=SYNTH:1 MAP:E
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
------=_NextPart_000_01BD9A3E.3E298440
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<html><head></head><BODY bgcolor=3D"#FFFFFF"><p><font size=3D2 =
color=3D"#000000" face=3D"Arial">HELP!,<br><br>	I have a question =
about The Microsoft SDK and some directx samples. I can't figure =
out how to install MSSDK so I can use the DJGPP to compiler programs =
using the MSSDK includes. I also can't figure out how to use the =
make program that comes with DJGPP to compiler the samples I got with =
the MSSDK. If had an anwser to the first question that would =
probably slove the second question. I would really appreciate any =
help. The MSSDK is kind of short on documentation.<br><br>thank =
you,<br><br>Dino Gigliotti.<br><br>I just included the th MSSDK =
documentation in the email below:<br><br> =
Microsoft Windows =
Platform Software Development Kit (SDK)<br> =
&=
nbsp; &n=
bsp; Readme.txt<br> =
&=
nbsp; &n=
bsp; January =
1998<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Contents:<br>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br><br> 1. Platform SDK General =
Release Notes<br> 2. Tested Compilers<br> =
3. Header File Conventions<br> =
4. UUID.Lib for Internet Explorer 4.0 and =
Windows <br> NT 5.0 Beta 1<br> =
5. Windows NT Server/Enterprise Edition 4.0 =
Support<br> 6. Supported Internet Explorer =
Versions<br> 7. NTFS 5.0 Release Notes<br> =
8. NetShow Version 2 Client Release Notes<br> =
9. RPC/MIDL Release Notes<br> =
10. OLE DB 1.5 Beta 2 Pre-release Notes<br> =
11. IIS 4.0 Beta 3 Release Notes	<br> =
12. What's New in IMM/IME<br> 13. =
What's New in Active Server Pages and Internet <br> =
Information Server<br> =
14. Developing TAPI 3.0 Applications<br> =
15. Windows NT 5.0 Beta 1-specific headers<br> =
16. Microsoft Small Business Server<br> =
17. Management Information Base (MIB) Files<br> =
18. Windbg Extensions and OS-specific =
Subdirectories<br> 19. Microsoft SDK for Java 2.01 =
<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>1 Platform SDK =
General Release =
Notes<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>1.1 =
Setup<br>---------<br><br>It is recommended that you either remove any =
previous installations <br>of the Platform SDK or install this release =
into a new, separate <br>directory. This January 1998 release of the =
Platform SDK supersedes <br>the previous release.<br><br>If you load the =
Platform SDK compact disc onto a machine running <br>Microsoft (R) =
Windows NT 5.0 Beta 1, the autorun feature may not <br>display =
readme.htm from the root of the compact disc. You will need <br>to =
specify a path for Microsoft (R) Internet Explorer (or let the =
<br>system locate it), then eject and reinsert the Platform SDK CD. =
<br>This is a known issue with this release of Windows NT and will =
<br>be fixed in a later release.<br><br>To set the SDK path, run SETEVN =
from your Platform SDK installation <br>directory. The MSSDK path must =
appear before your compiler path.<br><br>Usage: SETENV =
MSSDK<br>Where: MSSDK specifies where the Platform SDK was =
installed<br><br>Example: SETENV C:\MSSDK sets the environment relative =
to C:\MSSDK<br><br>If you are using Microsoft Visual C++ as your =
compiler, run <br>VCVARS32.BAT before running SETENV.BAT from the =
Platform SDK.<br><br><br>1.1 Documentation =
Setup<br>------------------------<br><br>If you are installing both the =
MSDN Library and the Platform <br>SDK documentation, it is recommended =
that you install the <br>Platform SDK documentation *after* you install =
the MSDN <br>Library. In addition, we have provided a batch file on the =
CD,<br>\mssdk\help\fixdocs.bat, which will review your registry and make =
<br>sure that you are viewing the latest version of the =
<br>documentation.<br><br>Note that the January 1998 Platform SDK =
documentation <br>contained on this compact disc is more recent than the =
<br>SDK documentation installed by Visual Studio version 5.0 <br>(or =
earlier) and the MSDN Library January 1998 (or <br>earlier). The =
Platform SDK setup automatically replaces <br>your existing content with =
the updated content. If you <br>install an older copy of the SDK =
documenatation from <br>another source, you can reinstall the SDK =
documentation <br>on this compact disc to get the updated content.<br> =
<br><br>1.3 Microsoft VM for Java<br>----------------------------<br>The =
most recent release of the Microsoft VM for Java can be installed =
<br>from <cd drive:>\Mssdk\Redist\JavaVM\MSJavAxp.exe or =
<br><cd drive:>\Mssdk\Redist\JavaVM\MSJavx86.exe.<br><br><br>1.4 =
Known Issues<br>----------------<br>Running InfoViewer 5.0 on Windows NT =
5.0 Beta 1 causes the <br>"Font setting for InfoViewer topic" =
to be set to very small. <br>Changing this setting from within =
InfoViewer has no effect. <br>To change the font size:<br><br>1. From =
the InfoViewer Tools menu, click Options.<br>2. Click the InfoViewer =
tab.<br>3. Click the Internet Explorer Options button.<br>4. Click the =
Accesibility button.<br>5. Check the Ignore font sizes specified on Web =
pages.<br><br><br>Problems with OLE DB and OCMM.h.<br><br>If you're =
using OLEDB.h and include OCMM.h into your project then you will not =
<br>be able to compile your application. This is a known problem =
and will being <br>addressed in a future release. If you need to =
use both OLE DB and the interfaces <br>defined in OCMM then you will =
need to segment your code into multiple source files, <br>some that use =
OLEDB and some that use OCMM.<br><br><br>The following samples do not =
build on Alpha. In some cases, the Microsoft<br>Visual C++ makefile =
shipped with the sample specifically targets x86. <br>In these cases, =
you can load the sample into Microsoft (R) Developer <br>Studio (R) and =
create an Alpha =
target.<br><br>Mssdk\Samples\Graphics\BA\Tvxsamp<br>Mssdk\Samples\Graphic=
s\DirectX\Memtime<br>Mssdk\Samples\Internet\IE\ColBtn<br>Mssdk\Samples\In=
ternet\IE\Drill\Driller<br>Mssdk\Samples\Internet\IE\IELnk<br>Mssdk\Sampl=
es\Internet\IE\IEMime<br>Mssdk\Samples\Internet\IE\IISLog<br>Mssdk\Sample=
s\Internet\IE\Percy<br>Mssdk\Samples\Internet\IE\TDC<br>Mssdk\Samples\Int=
ernet\IE\UrlMon\Progress<br>Mssdk\Samples\Internet\IE\WabTool<br>Mssdk\Sa=
mples\Internet\IE\WalkAll<br>Mssdk\Samples\Internet\MSChat\Chat2000<br>Ms=
sdk\Samples\Internet\NetMeeting\InstCodc<br>Mssdk\Samples\Internet\NetMee=
ting\NMFT<br>Mssdk\Samples\Internet\NetMeeting\NMShare<br>Mssdk\Samples\I=
nternet\NetMeeting\NMUI<br>Mssdk\Samples\Internet\NetMeeting\Skippy<br><b=
r>The following samples contain inline assembly and do not<br>build on =
Alpha. =
<br><br>Mssdk\Samples\WinBase\Security\WinNT\SampSSP<br>Mssdk\Samples\Gra=
phics\DirectX\Duel<br>Mssdk\Samples\Graphics\DirectX\Flip2D<br><br>The =
following samples require Microsoft Internet Explorer <br>version 4.0 or =
later, which was not available on Alpha when <br>this compact disc was =
released.<br><br>Mssdk\Samples\WinUI\Shell\RegView<br><br><br>In =
winerror.h, the old error =
define:<br>	CERT_E_VALIDIYPERIODNESTING<br><br>has been changed =
to:<br>	CERT_E_VALIDITYPERIODNESTING<br><br><br>If you want to =
install the Platform SDK on Alpha using <br>the new browser-based setup, =
you must change your <br>Internet Explorer security settings to =
None.<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>2 =
Tested =
Compilers<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Th=
e Platform SDK has been tested with Microsoft (R) Visual <br>C++ (R) =
version 5.0. Most samples will build with other <br>compilers, but other =
compilers were not explicitly tested.<br><br>2.1 Common Sources of =
Warnings<br>---------------------------------<br>* MakeProcInstance: Do =
not use this function. Pass <br>DLGPROC directly (the first =
parameter to MakeProcInstance). <br>Also, be sure to delete the =
FreeProcInstance function <br>that is paired with =
MakeProcInstance.<br><br>* Explicit casts are now necessary in many =
situations <br>where intrinsic casts worked before. An example: =
<br>MSSDK\samples\dbmsg\sql\dblib\c\sqltestn\SqltestN.c(186). =
<br>The (DLGPROC) cast was not necessary before. A warning <br>is =
now generated if a cast is omitted.<br><br>* CODE and DATA statements =
are not supported for use in <br>makefiles on the i386 =
platform.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>3 Header File =
Conventions<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br><br>If you want to target: =
Y=
ou should set:<br>---------------------- =
-=
--------------<br><br> Microsoft (R) Windows (R) 95 =
WINVER=3D0x0400 <br> and Windows NT 4.0 =
(and later) <br><br> Microsoft (R) Windows =
(R) 98 _WIN32_WINDOWS=3D0x0500 <br> and =
Windows NT 4.0 (and later) WINVER=3D0x0400<br><br> =
Windows NT 4.0 (and later) =
_WIN32_WINNT=3D0x0400<br> =
&=
nbsp; &n=
bsp; WINVER=3D0x0400=
<br><br> Windows 98 and Windows NT 5.0 =
WINVER=3D0x0500<br> (and later)<br><br> =
Internet Explorer 3.0 =
_WIN32_=
IE=3D0x0300<br> (and later)<br><br> Internet Explorer 4.0 =
_WIN32_=
IE=3D0x0400<br> (and later)<br><br> Setting a WINVER of =
0x0500 implies _WIN32_IE=3D0x0400<br><br><br>In the header files, =
<br>information guarded by: =
Is implemented in: =
<br>------------------------ =
------------------<br><br> #if =
_WIN32_WINNT >=3D 0x0400 Windows NT 4.0 and =
later. <br>				It is not implemented in =
<br>				Windows 95.<br><br> #if _WIN32_WINDOWS =
>=3D 0x0500 Windows 98 and later. <br><br> =
#if _WIN32_WINNT >=3D 0x0500 Windows NT 5.0 =
and later.<br><br> #if WINVER >=3D 0x0500 =
Windows NT =
5.0 and later <br>				and Windows 98 and =
later.<br><br> #if _WIN32_IE >=3D 0x0300 =
Internet Explorer 3.0 =
<br>				and later.<br><br> #if _WIN32_IE >=3D =
0x0400 Internet Explorer 4.0 =
<br>				and later.<br><br> #if _WIN32_WINCE =
&=
nbsp; Microsoft Windows CE 1.0 <br> =
&=
nbsp; &n=
bsp; and later.<br><br>The value of =
_WIN32_WINNT is set in WIN32.MAK, depending on the <br>platform you =
choose to target. By default, WIN32.MAK sets the <br>TARGETOS to =
WINNT and the APPVER to 4.0. As a result, by default, =
<br>_WIN32_WINNT is now defined as 0x0400. <br><br>By default, =
WIN32.MAK sets _WIN32_IE to 0x0300 if it is not <br>already defined. To =
specifically target Internet Explorer 4.x or<br>to take advantage of the =
new CommCtrl features introduced in<br>Internet Explorer 4.0, set =
_WIN32_IE to 0x0400.<br><br>If you are building an application to run on =
Windows 95 and you want <br>compile-time notification of compatibility =
issues, set TARGETOS=3DBOTH <br>in your makefile. When TARGETOS is =
defined as BOTH, _WIN32_WINNT is <br>not defined for the precompiler, =
and the only information parsed at <br>compile time is applicable to =
both Windows 95 and Windows NT. <br><br>If you do not include WIN32.MAK =
in your makefile, you need to <br>explicitly define _WIN32_WINNT as =
0x0500 to get the Windows NT <br>5.0-specific material from the header =
files.<br><br>There are several API sets present in Windows 95, OEM =
Service <br>Release 2 that are still guarded by (_WIN32_WINNT >=3D =
0x0400), <br>that is, CryptoAPI. If you are writing an application =
<br>specifically for Windows 95, OEM Service Release 2, and you <br>want =
the header files to provide compile time access to these <br>functions, =
it is necessary to define _WIN32_WINNT as 0x0400. <br>Notice that =
an application that uses these technologies does <br>not run correctly =
on the retail release of Windows 95. The <br>vast majority of =
applications that are expected to run <br>on Windows 95 should be built =
without defining _WIN32_WINNT.<br><br>Previous releases of the Platform =
SDK or Win32 SDK included <br>definitions in WIN32.MAK to map structured =
exception handling <br>keywords to their proper underscored names:<br> =
try -> __try <br> except -> =
__except <br> finally -> __finally <br> =
leave -> __leave<br><br>This caused problems for =
developers who chose to use C++ <br>structure exception handling where =
"try" is supposed to <br>be "try" and not =
"__try". For this reason, by default, <br>the mapping =
has been removed from WIN32.MAK. This may <br>cause build-time =
errors for your applications. To get <br>the old behavior add <br> =
SEHMAP =3D TRUE <br>to your makefile before including =
WIN32.MAK.<br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=
4 UUID.Lib for Internet Explorer 4.0 <br>and Windows NT 5.0 Beta =
1<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>Internet =
Explorer 4.0 and Windows NT 5.0 Beta 1 are <br>built with slightly =
different versions of UUID.Lib. <br>Just as Windows NT 5.0 Beta 1 uses a =
slightly older <br>version of Internet Explorer 4.0 based on Platform =
<br>Preview 2, Internet Explorer 4.0 is built using <br>a slightly older =
version of UUID.Lib from Windows <br>NT 5.0 Beta 1.<br><br>The default =
UUID.Lib in the Platform SDK has the <br>Internet Explorer 4.0 shell =
GUIDs. <br>In most cases this will not cause a problem. However, =
<br>if you are targeting new shell development on Windows <br>NT 5.0, =
there are a few GUIDs that differ between <br>Windows NT 5.0 Beta 1 and =
Internet Explorer 4.0. For <br>example, the GUID for IShellUIHelper has =
changed. To <br>use the Windows NT 5.0 Beta 1 GUIDs please replace =
<br>\MSSDK\Lib\UUID.Lib with \MSSDK\Lib\NT5B1\UUID.Lib. <br><br>For a =
complete list of differences, please review the <br>header changes using =
"windiff %mssdk%\Include <br>%mssdk%\Include\NT5B1". Many of =
the differences are due <br>to slightly different versions of MIDL used =
to generate <br>the Internet Explorer 4.0 and Windows NT 5.0 Beta 1 =
<br>headers; using the F7/F8 keys you can quickly review <br>the changed =
lines.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>5 Windows NT Server/Enterprise Edition =
4.0 =
Support<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>This release of the Platform SDK adds support for =
<br>Microsoft Windows NT Server/Enterprise Edition 4.0. <br>In =
addition to Microsoft Cluster server, Microsoft <br>Message Queue Server =
and Microsoft Transaction Server,<br>Windows NT Server/Enterprise =
Edition 4.0 also <br>has been enhanced with 4 Gigabyte Tuning (4GT) to =
<br>support very large user mode address spaces (3 GB of <br>user-mode =
addressable space instead of the usual 2 GB). <br>To allow your =
application to run using all 3 GB of <br>address space it is necessary =
to re-link your application <br>using the updated linker provided in the =
Platform SDK and <br>to add "/LARGEADDRESSAWARE" to the linker =
command line. <br>It is necessary to review and test your =
application to <br>ensure that it works properly with the 3 GB address =
space. <br>During internal testing of 4GT many applications were =
found to <br>store pointers using signed integers and to have problems =
<br>with addresses larger than 2 GB. The /LARGEADDRESSAWARE <br>switch =
will only affect the behavior of your application <br>when run on =
Windows NT Server/Enterprise Edition. The <br>/LARGEADDRESS aware =
switch will only affect .EXEs. <br>However any DLL, control, or =
COM object loaded into that <br>address space will see the full 3 GB =
address space. It<br>is recommended that all control and COM =
objects be tested <br>with containers linked using /LARGEADDRESSAWARE =
and run <br>on Windows NT Server/Enterprise =
Edition.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<br>6 Supported Microsoft Internet =
Explorer =
versions<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br><br>Due to the fact that several versions of Internet =
Explorer <br>are available as part of your MSDN subscription, not all =
<br>samples and/or applications may behave the same on all <br>versions =
of Internet Explorer. You may observe different <br>behavior between =
beta versions of Windows 98 and Windows <br>NT 5.0 Beta 1 and the =
released versions of Internet <br>Explorer 4.0 and =
4.01.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>7 NTFS 5.0 Release =
Notes<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br><br>7.1 Native structured storage for NTFS =
5.0<br>-------------------------------------------<br>OLE structured =
storage has traditionally used a flat <br>compound file (docfile) format =
to allow maximum portability. <br>However, it is desirable for elements =
of the IStorage and <br>IStream interfaces to reside natively in the =
file system <br>for better performance and scalability, and to expose =
file <br>system features. Native structured storage takes advantage =
<br>of the Microsoft(R) Windows NT(R) file system (NTFS) <br>version 5.0 =
files in that they can contain multiple data <br>streams. Native =
structured storage (NSS) is a multistream <br>file format where IStream =
input/output (I/O) is more <br>efficient because it is mapped to a =
native NTFS stream. <br>NSS is compatible with all applications that use =
OLE <br>structured storage, and NSS files can only exist on <br>NTFS 5.0 =
volumes.<br><br>Copying an NSS file to a file allocation table (FAT) or =
<br>NTFS version 4.0 volume results in downgrading the NSS <br>file to a =
docfile. Accessing an NSS file from a remote <br>client (that is, a =
client that opens a file through the <br>redirector), accessing it =
directly with the CreateFile <br>function, or with the StgOpenStorage or =
StgCreateDocfile <br>functions, triggers a conversion. In a =
conversion, a <br>docfile view is seen by the client, but the file =
remains <br>in NSS format on disk. It is not currently possible =
<br>to create a new NSS file on a remote machine. The size <br>of =
an NSS file as reported by the "dir" command, and <br>probably =
by other utilities, is the size of the default, <br>or unnamed, data =
stream, not the total size of all the <br>streams. Thus the size =
reported may be smaller than the <br>actual size of the NSS file. This =
size reporting problem <br>will be fixed after Beta 1.<br><br>Two new =
functions can be used to create or open NSS files: =
<br>StgCreateStorageEx and StgOpenStorageEx. In this beta <br>release of =
Microsoft Windows NT 5.0, the STGFMT_STORAGE flag <br>(passed in the =
stgfmt parameter) is treated equivalently to <br>the STGFMT_NATIVE flag =
when the riid parameter is IID_IStorage. <br>In the next beta =
release, and the final release, of Microsoft <br>Windows NT 5.0, the =
STGFMT_STORAGE flag will be interpreted <br>to indicate that either NSS =
or a docfile storage is <br>acceptable.<br><br>For compatibility =
testing, the old docfile functions can <br>be enabled to create and open =
NSS files on NTFS 5.0 volumes <br>automatically by setting the following =
registry key values:<br><br>\HKLM\Software\Microsoft\Ole\<br> =
EnableNtfsStructuredStora=
ge =3D "YY"<br> =
EnableCNSS =3D =
"Y"<br><br>7.2 NTFS Property =
Sets<br>----------------------<br>The OLE Structured Storage =
specification includes a <br>definition of the Property Set layout =
format. This <br>property set format for compound files =
("docfiles") is <br>currently implemented. With this =
beta release of Microsoft <br>Windows NT 5.0, these property sets are =
also implemented <br>natively on NTFS files (for volumes formatted with =
the NTFS <br>5.0 file system). Because these property sets are =
<br>implemented directly by the file system, they are extremely =
<br>robust.<br><br>NTFS property sets are stored in a file as special =
streams, <br>alongside the file's data streams. You can create, =
open, <br>and delete property set streams using the normal file =
<br>manipulation functions, but it is not possible to directly <br>read =
or write a property set stream.<br><br>To create, open, delete, and =
manipulate NTFS property sets, <br>you use the IPropertySetStorage and =
IPropertyStorage interfaces, <br>just as you do with compound file =
property sets. To get an <br>IPropertySetStorage interface, you use the =
new StgCreateStorageEx <br>and StgOpenStorageEx functions, using the =
format flag STGFMT_FILE <br>and the interface identifier =
IID_IPropertySetStorage. For <br>example, if you have an HTML file =
with the name "default.html", <br>you can get an =
IPropertySetStorage interface for it, and use <br>it to put property =
sets on the file. To get the <br>IPropertySetStorage interface, =
you use the call:<br><br>IPropertySetStorage *pPropSetStg =3D =
NULL;<br>StgOpenStorageEx( L"default.html",<br> =
&=
nbsp; STGM_READWRITE | STGM_SHARE_EXCLUSIVE,<br> =
&=
nbsp; STGFMT_FILE,<br> =
&=
nbsp; 0L,<br> =
&=
nbsp; NULL,<br> =
&=
nbsp; NULL,<br> =
&=
nbsp; IID_IPropertySetStorage,<br> =
&=
nbsp; (void**) &pPropSetStg ));<br><br>Once =
you have this IPropertySetStorage, you can call the <br>Create and Open =
methods to manipulate property set streams <br>for the file. Programs =
that only use the default data stream <br>on a file are unaware of =
these property sets. In the <br>preceding example, a Web browser =
continues to use the <br>"default.html" file as usual, having =
no awareness of the <br>fact that the file also had property set =
streams.<br><br>Please note the following:<br>* Microsoft Windows NT 5.0 =
does not use the IPropertyStorage <br>and IPropertySetStorage interfaces =
to create and manage <br>persistent property sets associated with files =
in the <br>Windows NT file system (NTFS). The system-provided =
<br>implementations of these interfaces apply to compound <br>files and =
do not apply to properties associated with <br>native files on an NTFS =
5.0 partition.<br><br>* NTFS property sets currently only support =
Unicode, simple <br>property sets. Therefore, the PROPSETFLAG_ANSI and =
<br>PROPSETFLAG_NONSIMPLE flags on the <br>IPropertySetStorage::Create =
method are invalid.<br><br>* NTFS property sets are not currently =
supported for files <br>on a remote machine. For example, if X: is a =
remote <br>(redirected) drive, it is not valid to attempt to get an =
<br>IPropertySetStorage interface on the file =
"X:\DEFAULT.HTML".<br><br>* The IPropertyStorage::SetClass =
method is not implemented. <br>Also, NTFS property sets do not support =
timestamps, so the <br>IPropertyStorage::SetTimes method succeeds but =
cannot <br>actually store the times.<br><br>* NTFS property sets do not =
support transactioning, so the <br>IPropertyStorage::Revert method has =
no effect. The <br>IPropertyStorage::Commit method can still be used to =
flush <br>the property set to the disk.<br><br>* In the compound file =
implementation of property sets, an <br>IPropertyStorage is contained =
within the IPropertySetStorage <br>that created it. Thus, an =
IPropertySetStorage that was created <br>in read-only mode cannot be =
used to create an IPropertyStorage <br>in read/write mode. Similarly, if =
a compound file <br>IPropertySetStorage is released, its child =
IPropertyStorage <br>objects are put in the Reverted state. With =
NTFS property <br>sets, this containment does not currently exist, =
though similar <br>semantics may be added in a later release of Windows =
NT 5.0. When <br>you create or open an NTFS IPropertySetStorage, the =
flags you <br>specify in the grfMode parameter to the StgCreate or =
OpenStorageEx <br>functions are used to open the default data stream on =
the file. <br>When you subsequently create or open property sets, the =
flags <br>you specify in the grfMode parameter to the =
<br>IPropertySetStorage::Create or IPropertySetStorage::Open methods =
<br>are used to open the property set stream. This property set =
<br>stream can be opened with a mode that is inconsistent with <br>the =
mode used to open the IPropertySetStorage, and the <br>IPropertyStorage =
remains in a usable state even if the <br>IPropertySetStorage is =
released.<br><br>* When an NTFS file with property set streams is copied =
to <br>any file system other than NTFS 5.0, the property sets are =
<br>lost. So if you copy the "default.html" file in the =
preceding <br>example to a FAT file system, the default data stream is =
copied <br>successfully, but the property sets are lost. If you copy it =
to <br>an NTFS file system earlier than 5.0, all data streams are =
copied, <br>but again the property set streams are lost. The BackupRead =
and <br>BackupWrite functions behave in the same manner; restoring to =
an<br>NTFS 5.0 volume restores the property sets, restoring to another =
<br>file system does not.<br><br><br>7.3 Simple Mode Compound File =
Property Sets<br>-------------------------------------------<br>Compound =
file storages provide native support for property sets. <br>It was =
not previously possible, however, to obtain a property <br>set interface =
for a simple mode storage (a storage obtained <br>using the STGM_SIMPLE =
flag). With this release of Microsoft <br>Windows NT 5.0 Beta 1, simple =
mode compound file property sets <br>are now possible. A simple mode =
property set is obtained as are <br>compound file property sets, by =
calling IStorage::QueryInterface <br>for the IID_IPropertySetStorage =
interface. When the storage being <br>queried is in simple mode, the =
resulting IPropertySetStorage is <br>also in simple mode, as are =
IPropertyStorage objects that are <br>created by the =
IPropertySetStorage.<br><br>Simple mode property sets are subject to the =
same constraints as <br>simple mode storages. For example, after =
creating a property set <br>with IPropertySetStorage::Create, the =
resulting IPropertyStorage <br>must be released before another can be =
created. Note that in <br>this beta release of Microsoft Windows =
NT 5.0, it is possible to <br>marshal a simple mode IPropertyStorage, =
whereas in the final <br>version of Windows NT 5.0 this will not be =
possible.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>8 NetShow Version 2 Client Release =
Notes<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
br><br>8.1 File Transfer Control Packet =
Formats<br>-----------------------------------------<br>The packet =
format used by the File Transfer service has changed <br>from that used =
in previous releases. Make sure the Microsoft(R) <br>NetShow(TM) server =
that is sending files and the File Transfer <br>control receiving files =
are the same release version. The NetShow <br>version 2.0 File Transfer =
control does not work with NetShow <br>server version 1.0 or previously =
released beta versions of <br>NetShow server. <br><br>8.2 Type =
Property<br>-----------------<br>Using Microsoft(R) Visual Basic(R) =
Scripting Edition (VBScript) <br>to set the value of the Type property =
exposed by the NetShow File <br>Transfer control requires the following =
syntax to work with <br>Microsoft(R) Internet Explorer version 4.0 =
<br><br>	NSFile1.object.Type <br><br>where NSFile1 is the NetShow =
File Transfer control object. <br><br>Earlier versions of Internet =
Explorer do not require or accept <br>the object keyword. Use the =
following syntax to access the <br>Type property with earlier versions =
of the browser: <br><br>	NSFile1.Type <br><br>Note: This special =
syntax applies only to the Type property <br>exposed by the control. The =
object keyword is not required to <br>set any of the other properties =
running any version of <br>Internet Explorer. <br><br>8.3 "Receive =
Unicast" and "Total Demo" File Transfer =
Examples<br>-------------------------------------------------------------=
<br>Unicast file transfers require a stream-type socket connection. =
<br>Stream sockets use Transmission ControlProtocol (TCP), which =
<br>ensures the reliability of the transmission. Forward error =
<br>correction (FEC) is provided for multicast file transfers using =
<br>connectionless protocols, such as User Datagram Protocol (UDP) =
<br>and should not be used with stream sockets. Because of this, <br>the =
"Receive Unicast" example and the "Total Demo" =
example (when <br>it is used to receive unicast file transfers), need =
changes <br>before they work. <br><br>To use these example pages, make =
the following corrections to <br>their BtnReceiveFile_OnClick =
subroutines: <br><br>1. For unicasts, set the value of the Type property =
specifying <br>the socket type to use a stream socket connection =
(SOCK_STREAM) <br>and not a datagram socket connection (SOCK_DGRAM). =
<br><br>The command <br>	nsfile1.Type=3D2 <br><br>should be changed =
to <br>	nsfile1.Type=3D1 <br><br>2. Because stream sockets support =
TCP, FEC should not be <br>enabled for receiving unicasts, and the =
command <br><br> call =
nsfile1.FtsStartFileTransferReceive("", 5050, "", =
"%TEMP%\", 0, 1025) <br><br>should be changed to <br> =
<br>call nsfile1.FtsStartFileTransferReceive("", 5050, =
"", "%TEMP%\", 0, 1024) <br><br><br>8.4 =
"Receive Multicast with Progress" =
Example<br>---------------------------------------------<br>The =
"Receive Multicast with Progress" example page has a =
<br>typographical error in the ButtonReceiveFile_OnClick subroutine. =
<br><br>The command <br><br> call nsfile1.FtsRegisterStatusCallback(0, =
0, 4096, 4096, 0, , 0, 0, 0, 0, 0) <br><br>should be <br><br> call =
nsfile1.FtsRegisterStatusCallback(0, 0, 4096, 4096, 0, 0, 0, 0, 0, 0, 0) =
<br><br>8.5 Real-Time Encoder <br>----------------------<br>The =
Real-Time Encoder application sets the duration in minutes, <br>hours, =
and days, but the Automation interface allows only <br>values measured =
in seconds. =
<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>9 RPC/MIDL Release =
Notes<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>9.1 What's =
New<br>--------------<br>Asynchronous RPC. The RPC run-time environment =
now supports <br>asynchronous remote procedure calls to allow your =
programs <br>to handle multiple outstanding calls from a single-threaded =
<br>client and prevent data transmission bottlenecks that can <br>arise =
from slow or delayed clients or servers. With <br>asynchronous pipe =
parameters, client/server applications <br>can transfer large amounts of =
data incrementally, without <br>blocking the client or server threads =
from performing other <br>tasks. For more information, see the =
Asynchronous RPC section <br>in the Platform SDK online =
documentation.<br><br>New HTTP protocol sequence. The ncacn_http =
protocol allows <br>client and server applications to communicate across =
the <br>Internet by using the Microsoft(R) Internet Information =
<br>Server (IIS) as a proxy. Because calls are tunneled through<br>an =
established HTTP port, they can cross firewalls. <br><br>Name =
Service: The Remote Procedure Call (RPC) Name Service <br>(Locator) uses =
the Windows NT 5.0 Active Directory as its <br>database. This means that =
exported entries can be made <br>persistent even when a server is =
rebooted. For more information, <br>see the RPC reference pages for =
RpcNsBindingExport, <br>RpcNsBindingImportNext, RpcNsBindingLookupBegin, =
and <br>RpcNsBindingUnexport in the Platform SDK online =
documentation.<br><br>New Type Library Attributes. Microsoft Interface =
Definition <br>Language (MIDL) supports Double-Byte Character Set (DBCS) =
<br>international locales now. TLB file generation has been =
<br>significantly improved and all the type library attributes <br>are =
supported now. For more information, see Type Library <br>Attributes in =
the Platform SDK online documentation.<br><br><br>9.2 Known Limitations =
for Beta 1<br>----------------------------------<br>RPC over Microsoft =
Message Queue Server (MSMQ). There is no <br>official support for MSMQ, =
and MSMQ servers can not be <br>directly installed on Microsoft Windows =
NT 5.0 beta 1. <br>However, independent and dependent clients can be =
installed <br>for evaluation purposes. <br><br>Asynchronous pipes had a =
limited testing.<br><br>If you are using RPC over MSMQ (ncadg_mq) =
protocol, the <br>current MSMQ installation configures the RPC registry =
entries <br>for the Microsoft Windows NT 4.0 configuration. These must =
<br>be manually modified using Regedit32.Exe in order for RPC <br>over =
MSMQ to operate on Windows NT 5.0 Beta 1. Change the <br>values for the =
registry =
entries<br><br>\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols=
\ncadg_mq<br>\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ServerProtocols\n=
cadg_mq<br><br>from "RpcMqCl.dll" and "RpcMqSvr.dll" =
(respectively) to <br>"RpcLt1.dll".<br><br><br>9.3 MIDL =
Version<br>------------------<br>The current version of MIDL shipped on =
this compact disc is <br>version 3.3.0110. This version of MIDL supports =
developers who are<br>using Windows NT 4.0/Visual C++ 5.0 or Windows NT =
5.0 Beta 1 (the <br>Platform SDK build environment). It is not =
compatible with a <br>Windows NT 4.0/Visual C++ 4.x environment. If you =
want to use the <br>latest MIDL compiler in this environment, or if you =
want to use the <br>latest MIDL compiler and distribute the MIDL =
generated files to <br>developers on environments other than those =
supported, you must <br>provide two additional files, rpndr.h and =
rpcproxy.h, from the <br>\mssdk\include directory of this compact disc. =
<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>10 =
OLE DB 1.5 Beta 2 Pre-release =
Notes<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>The major =
changes to the OLE DB Specification <br>(OLEDB15SPEC.HLP) since OLE DB =
version 1.5 beta 1 <br>are as follows:<br><br>1. The beta 1 version of =
the IRowsetFind interface <br>has been changed to more closely align =
with the <br>IRowset::GetNextRows and IRowsetLocate::GetRowsAt =
<br>methods. <br><br>Specifically:<br> a. The methods FindNextRow =
and GetNextRows now share <br>the same fetch position. b. The =
fSkipCurrent argument of <br>FindNextRow has been replaced by =
ulRowsOffset, with the <br>same semantics as the ulRowsOffset argument =
in GetNextRows <br>and GetRowsAt.<br><br>2. Rowset Views have been added =
for applying simple <br>filtering and sorting to a rowset.<br><br>3. =
Numerous clarifications and bug fixes were made <br>throughout the =
document.<br><br>The header and library files included here reflect the =
<br>changes made in the OLE DB 1.5 beta 2 specification and <br>are =
newer than the header files provided in the original <br>OLE DB 1.5 beta =
1 release.<br><br>The OLE DB Leveling document (OLEDBLeveling.doc) has =
also <br>been updated since the original OLE DB 1.5 beta 1 release. =
<br>The main changes to the leveling document include:<br><br>1. =
DBPROP_CANFETCHBACKWARDS is only required for providers <br>that also =
support DBPROP_CANSCROLLBACKWARDS.<br><br>2. Providers are not required =
to support DBPROP_COMMITPRESERVE, <br>because a number of relational =
providers do not support <br>preserve semantics.<br><br>3. The OLE DB =
Simple Provider Toolkit has been added as a <br>means of producing an =
OLE DB provider that exposes the <br>minimal consumer =
interfaces.<br><br>4. Additional clarifications have been made =
throughout <br>the =
document.<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>11 Microsoft Internet Information Server (IIS) =
<br>version 4.0 Beta 3 Release =
Notes<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<br><br>11.1 =
IRequestDictionary::get_Item<br>-----------------------------------<br>Th=
e IRequestDictionary::get_Item reference page does <br>not completely =
explain how to use the method to retrieve <br>an item from a Request =
collection. The method returns a <br>pointer to a variant. The data type =
of the variant that <br>is returned is VT_DISPATCH. If you need to =
convert the <br>returned item to a BSTR, you can use the Microsoft(R) =
<br>Win32(R) function, VariantChangeType. For more <br>information on =
VariantChangeType, see Variant Manipulation <br>functions in the =
Platform SDK.<br><br>11.2 IIS Headers<br>---------------<br>During =
installation the IIS headers are installed in <br>one of two places. If =
the Platform SDK is installed on <br>the system, then the headers are =
copied into its include <br>directory. If the Platform SDK is not =
installed on the <br>system, then the headers are copied to =
<br>\inetpub\iissamples\sdk\include. Before building IIS <br>4.0 =
specific projects, you must copy these headers to <br>the include =
directory of your build environment.<br><br>Please note that the =
Microsoft Transaction Server (MTS) <br>headers and libraries must be =
copied into your development <br>environment before building server =
components that use the <br>IContextObject interface to access the =
Active Server Pages <br>(ASP) intrinsics. MTS installs its headers and =
libraries <br>in the \Program files\Mts\ directory.<br><br>11.3 Sample =
Java Components<br>---------------------------<br>The sample Java =
components described in the documentation <br>have been replaced by the =
Java Component Framework samples. <br>These samples, along with the =
relevant documentation, can <br>be found in the directory =
<br>\Mssdk\Samples\Internet\Iis\Components\Java\Framework.<br><br><br>11.=
4 Java Class and Interface =
Definitions<br>----------------------------------------<br>The Java =
Class and Interface definitions topic contains <br>an error. <br>It =
states<br>"The Java type libraries are not installed with ASP. If =
<br>you are using Microsoft=AE Visual J++, you can generate <br>classes =
from the Microsoft Active Server Pages Object <br>Library with the Java =
Type Library Wizard.<br><br>"To use the built-in object interfaces =
in a Java <br>component, you must import the ASP classes into your =
<br>code as shown below.<br><br>"import asp.*;"<br><br>The =
topic should read<br><br>"The Java ASP interface class files are =
installed with PWS.<br><br>"To use the built-in object interfaces =
in a Java component, <br>you must import the ASP classes into your code =
as shown below.<br><br>"import com.ms.asp.*;"<br><br>11.5 =
Administration Property =
Reference<br>-------------------------------------<br>In the =
Administration Property Reference, the documentation <br>for the =
AspScriptTimeout property incorrectly states that <br>"A value of =
-1 for this property will disable script time-out <br>and allow the =
script to run indefinitely." The minimum value <br>for this =
property is 1 second.<br><br>In the Metabase Identifier Reference, the =
documentation for <br>the MD_ASP_SCRIPTTIMEOUT property incorrectly =
states that <br>"A value of 0xFFFFFFFF will allow a script to run =
indefinitely." <br>The range of values for this property is 1 =
through =
0xFFFFFFFE.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>12 What's New in =
IMM/IME<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br>The Windows 98 and Windows NT 5 IMM/IME =
architecture retains the <br>Windows 95/Windows NT 4.0 design with some =
improvements to better <br>support intelligent IME development and =
integration of IME with <br>Windows. These changes are briefly listed =
following. <br><br>Note: The Platform SDK provides IME API documentation =
for <br>application development. For information on IME development, =
refer <br>to the Microsoft Windows NT Device Driver Kit =
documentation.<br><br>12.1 New IME function for =
applications<br>-------------------------------------<br>The following =
new IME functions allow applications to communicate <br>with IMM/IME: =
<br>ImmAssociateContextEx<br>ImmDisableIME<br>ImmGetImeMenuItems<br><br>1=
2.2 New functions for IME =
developers<br>------------------------------------<br>The following new =
functions allow IMEs to communicate with IMM <br>and =
applications:<br>ImmRequestMessage<br>ImeGetImeMenuItems<br><br>12.3 =
Supporting reconversion<br>---------------------------<br>This is a new =
IME feature that allows you to reconvert a string <br>that has already =
been inserted into the application's document. <br>This function helps =
intelligent IMEs to get more information <br>about the converted result =
and improves conversion accuracy and <br>performance.<br> <br>12.4 =
Adding IME menu items into Context menu of the system Pen icon =
<br>-------------------------------------------------------------------<b=
r>This new feature provides a way for IMEs to insert the new IME =
<br>menu items into the Context menu of System Pen Icon in System =
Tray.<br><br>12.5 New bits and values for =
IME<br>-------------------------------<br>The following new bits support =
new conversion =
modes:<br>IME_CMODE_FIXED<br>IME_SMODE_CONVERSATION<br>IME_PROP_COMPLETE_=
ON_UNSELECT<br><br>12.6 Edit control enhancement for =
IME<br>------------------------------------<br>Through the two new edit =
control messages, EM_SETIMESTATUS and <br>EM_GETIMESTATUS, applications =
can manage IME status for edit <br>controls. =
<br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<br>13 What's New in Active Server Pages and Internet Information =
Server<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=
<br>The Active Server Pages and Internet Information Server sections =
<br>of the Platform SDK include the following changes from the previous =
<br>release.<br><br>Section =
Sub-sec=
tion =
&=
nbsp;Change<br>------- =
-------=
---- =
&=
nbsp;------<br>Active Server Built in ASP =
Object Reference pages for new =
<br>Pages		 Reference =
&=
nbsp; methods, collections, <br> =
&=
nbsp; &n=
bsp; &nb=
sp; and objects have been <br> =
&=
nbsp; &n=
bsp; &nb=
sp; added.<br><br>Active Server =
Directive Reference =
This is a new set of <br>Pages =
&=
nbsp; &n=
bsp; &nb=
sp; reference pages for all <br> =
&=
nbsp; &n=
bsp; &nb=
sp; of the ASP @ =
directives.<br><br>Active Server =
Installable Components =
Reference pages for new <br>Pages =
&=
nbsp; &n=
bsp; &nb=
sp; components that ship with <br> =
&=
nbsp; &n=
bsp; &nb=
sp; IIS 4.0 have been =
added.<br><br>Active Server Windows =
Scripting Host This is a new set of <br>Pages =
&=
nbsp; &n=
bsp; &nb=
sp; reference pages for the <br> =
&=
nbsp; &n=
bsp; &nb=
sp; Windows Scripting Host. =
<br><br>Internet =
Web =
Application This =
is a new overview <br>Information =
Development Guide =
section that describes =
<br>Server =
&=
nbsp; &n=
bsp; &nb=
sp;Microsoft's programming <br> =
&=
nbsp; &n=
bsp; &nb=
sp; model for developing <br> =
&=
nbsp; &n=
bsp; &nb=
sp; applications on the <br> =
&=
nbsp; &n=
bsp; &nb=
sp; Internet and<br> =
&=
nbsp; &n=
bsp; &nb=
sp; intranets.<br><br>Internet =
Programmer's =
O=
verview sections have <br>Information =
Reference/Creating =
been revised to describe<br>Server =
C=
omponents for ASP the integration =
with <br> =
&=
nbsp; &n=
bsp; &nb=
sp; Microsoft Transaction <br> =
&=
nbsp; &n=
bsp; &nb=
sp; Server. New reference <br> =
&=
nbsp; &n=
bsp; &nb=
sp; pages for C++ and Java =
<br>				 =
interfa=
ces have been <br> =
&=
nbsp; &n=
bsp; &nb=
sp; added. <br><br>Internet =
Programmer's =
T=
his is a new section <br>Information =
Reference/IIS =
that =
contains both <br>Server =
A=
dministration =
overview =
topics and <br> =
&=
nbsp; &n=
bsp; &nb=
sp; reference pages that <br> =
&=
nbsp; &n=
bsp; &nb=
sp; describe how to <br> =
&=
nbsp; &n=
bsp; &nb=
sp; administer Internet <br> =
&=
nbsp; &n=
bsp; &nb=
sp; Information Server <br> =
&=
nbsp; &n=
bsp; &nb=
sp; programmatically. <br> =
&=
nbsp; &n=
bsp; &nb=
sp; The data store for <br> =
&=
nbsp; &n=
bsp; &nb=
sp; configuration <br> =
&=
nbsp; &n=
bsp; &nb=
sp; information is <br> =
&=
nbsp; &n=
bsp; &nb=
sp; described. Reference <br> =
&=
nbsp; &n=
bsp; &nb=
sp; pages for the <br> =
&=
nbsp; &n=
bsp; &nb=
sp; interfaces that can <br> =
&=
nbsp; &n=
bsp; &nb=
sp; be used by programs<br> =
&=
nbsp; &n=
bsp; &nb=
sp; and the Automation <br> =
&=
nbsp; &n=
bsp; &nb=
sp; properties that can <br> =
&=
nbsp; &n=
bsp; &nb=
sp; be used by scripts <br> =
&=
nbsp; &n=
bsp; &nb=
sp; are included. <br><br>Internet =
Programmer's =
T=
his is a new section <br>Information =
Reference/Logging =
that contains both <br>Server =
I=
nterface =
&=
nbsp; overview topics and<br> =
&=
nbsp; &n=
bsp; &nb=
sp; reference pages that <br> =
&=
nbsp; &n=
bsp; &nb=
sp; describe how to control <br> =
&=
nbsp; &n=
bsp; &nb=
sp; logging IIS events <br> =
&=
nbsp; &n=
bsp; &nb=
sp; programmatically. It <br> =
&=
nbsp; &n=
bsp; &nb=
sp; describes both how to <br> =
&=
nbsp; &n=
bsp; &nb=
sp; use the Automation <br> =
&=
nbsp; &n=
bsp; &nb=
sp; properties in the <br> =
&=
nbsp; &n=
bsp; &nb=
sp; IIS data store, and <br> =
&=
nbsp; &n=
bsp; &nb=
sp; how to create a custom <br> =
&=
nbsp; &n=
bsp; &nb=
sp; logging module. =
<br><br>Internet =
Programmer's =
T=
he overview topics <br>Information =
Reference/ISAPI =
have been revised =
to <br>Server =
&=
nbsp; &n=
bsp; &nb=
sp;provide more detail on <br> =
&=
nbsp; &n=
bsp; &nb=
sp; how to develop ISAPI <br> =
&=
nbsp; &n=
bsp; &nb=
sp; extensions and filters. <br> =
&=
nbsp; &n=
bsp; &nb=
sp; The overview topics <br> =
&=
nbsp; &n=
bsp; &nb=
sp; also describe new ISAPI <br> =
&=
nbsp; &n=
bsp; &nb=
sp; features. Reference <br> =
&=
nbsp; &n=
bsp; &nb=
sp; pages have been divided <br> =
&=
nbsp; &n=
bsp; &nb=
sp; into two sections, one <br> =
&=
nbsp; &n=
bsp; &nb=
sp; for ISAPI extensions,<br> =
&=
nbsp; &n=
bsp; &nb=
sp; and another for <br> =
&=
nbsp; &n=
bsp; &nb=
sp; SAPI filters.<br><br>Internet =
Programmer's =
A=
list of new sample <br>Information =
Reference/Developer =
scripts and programs <br>Server =
S=
amples =
&=
nbsp; that are provided <br> =
&=
nbsp; &n=
bsp; &nb=
sp; with the Platform SDK. <br> =
&=
nbsp; &n=
bsp; <br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<br>14 Developing TAPI 3.0 =
Applications<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br>14.1 =
Developing TAPI 3.0 =
Applications<br>---------------------------------------<br>* When =
developing applications that feature TAPI 3.0 audio, <br>you are not =
advised to open message boxes that produce a <br>system sound (e.g. =
"default beep"), because playing system <br>sounds might =
prevent the TAPI 3.0 audio streams from running.<br><br>* Static =
terminals of type "speakers" cannot be used repeatedly <br>on =
different TAPI 3.0 calls: once the call (on which such a <br>terminal =
has been selected) is disconnected and released, the <br>static terminal =
must be released as well. For a new call, query <br>again the =
"speaker" terminal from the collection of static =
<br>terminals.<br><br>These aspects will be addressed in future releases =
of TAPI 3.0.<br><br><br>14.2 Developing TAPI 3.0 applications with =
<br>Visual Basic 5 =
(SP2)<br>--------------------------------------------<br>TAPI 3.0 and =
Visual Basic 5 SP2 are not fully compatible. <br>Therefore there are a =
few problems that developers will <br>encounter while developing =
applications that use tapi3.dll:<br><br>* Dialog boxes cannot be =
displayed on event procedures.<br>* Breakpoints cannot be set in event =
procedures.<br>* Occasionally, an access violation can occur in =
<br>Tapi3!Next, especially when quitting the application.<br><br>These =
aspects will be addressed in the next version of <br>Visual Basic or in =
future releases of TAPI =
3.0.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=
15 Windows NT 5.0 Beta 1-specific =
headers<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Micros=
oft Windows NT 5.0 beta 1 ships with the Platform <br>Preview 2 release =
of Internet Explorer 4.0. There have <br>been changes made in the shell =
and Internet client APIs <br>between the Platform Preview 2 release and =
the final <br>release of Internet Explorer 4.0. Because of these =
changes, <br>two versions of several shell headers are provided as =
<br>part of the Platform SDK. The default version of the <br>headers =
installed to \Mssdk\Include is the final released <br>Internet Explorer =
4.0 versions. If you are targeting shell <br>development on Windows NT =
5.0, you may need to use the<br>version of the headers provided in =
\Mssdk\Include\NT5b1.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=
16 Microsoft Small Business =
Server<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Documentation on the =
Microsoft Small Business Server<br>is available in Microsoft Word format =
in \mssdk\doc, as <br>well as in the Platform SDK online documentation =
(.IVT).<br><br>* The Console Customization and Style Guide =
<br>(\mssdk\doc\consolesg.doc) outlines the rationale behind the =
<br>design of the Microsoft Small Business Server console.<br>The =
Console Customization and Style Guide is <br>also available from the =
Microsoft web site at =
<br>http://www.microsoft.com/backofficesmallbiz.<br>* You can simplify =
installing your application on Small <br>Business Server by integrating =
your setup program with the <br>Setup Computer Wizard (SCW). Details on =
SCW are available<br>in the Setup and Systems Management node of the =
<br>Platform SDK online =
documentation.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>17 Management Information Base (MIB) =
Files<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
br><br>Management Information Base (MIB) files are no longer =
<br>available on the Microsoft Windows Platform SDK compact <br>disc. =
They are available for download from <br>ftp://ftp.isi.edu/mib/. =
<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>18 Windbg Extensions and =
OS-specific =
Subdirectories<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Windbg installs two trees for debugger =
extensions, one <br>containing files specific to Microsoft Windows NT =
4.0 and <br>one specific to Microsoft Windows NT 5.0. Both the BIN and =
<br>SYMBOLS directories contain \NT4 and \NT5 subdirectories. <br>The =
Windows NT 5.0 Beta 1 DDK assumes a default of NT5. <br>The Windows =
Platform SDK defaults to the OS version on <br>which it is installed =
(\NT4 for Windows NT 4.0 and \NT5 <br>for Windows NT 5.0). If you want =
to use the debugger <br>for a specific OS other than the default, copy =
the files <br>from the .\NT<number> directory into the parent =
directory.<br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>19 Microsoft =
SDK for Java 2.01 =
<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>This SDK includes the latest version =
of the Microsoft <br>virtual machine for Java (build 2339). This =
is the <br>same virtual machine that ships with Internet Explorer =
<br>4.01 and provides the fastest, most functional and most =
<br>compatible Java support of any major browser. <br><br>Among =
the new features:<br>* Maintains Java performance leadership<br>* Win32 =
Classes for J/Direct - these classes simplify <br> using J/Direct =
let developers meld the productivity <br> of the Java language =
with the power of Windows. <br> Includes pre-built =
declarations for GDI, User, Kernel, <br> Multimedia and Common =
Control.<br>* Application Foundation Classes (AFC) support for <br> =
JDK 1.02 browsers - a standalone package for use <br> with =
browsers that do not offer sufficient <br> JDK 1.1 support.<br>* =
Console - a much requested developer feature allows <br> =
interactive viewing of output from Java programs.<br>* =
Permissions-based security - expanded user interface <br> allows =
users and administrators to view and edit <br> their Java security =
preferences in a very granular <br> manner, as well as new =
developer tools to simplify <br> the process of assigning =
permissions and signing code.<br>* Enhanced robustness and scalability =
for standalone use<br>* Improved accessibility support<br>* Improved =
printing of international characters<br><br><br>Additional information =
on AFC support for JDK 1.02 browsers<br><br>The new AFC standalone =
package included in this release <br>allows AFC to be used in browsers =
which do not offer <br>adequate JDK 1.1 functionality, such as Internet =
Explorer 3.0, <br>Netscape Navigator 3.0, and Netscape Navigator 4.0. =
The <br>original AFC classes that were released with Internet =
<br>Explorer 4.0, now being used by millions of users, relied <br>upon =
JDK 1.1 functionality. This new AFC package based <br>on JDK 1.02 =
functionality fulfills the stated design goal <br>for AFC, which was to =
provide a rich set of components <br>that could be used to build applets =
that run cross-browser <br>on Windows 95/Windows NT, Macintosh and =
Solaris.<br><br><br><b>Samples documentation:</b><br><br>The =
\Mssdk\Samples directory contains Platform SDK samples.<br>These samples =
demonstrate the use of interfaces and APIs for<br>Win32 and BackOffice. =
The samples run on Windows NT and Windows 95.<br>Some of the =
samples use interfaces or APIs that are only available<br>in beta =
operating system releases. Refer to the readme.txt in the <br>root =
of the Platform SDK CD for more information about how to <br>build an =
application using beta interfaces.<br><br>The build environment =
(headers, libraries, and minimum build<br>tools) for the Platform SDK =
must be installed in order to build<br>any of the samples in the =
\Mssdk\Samples directory. The build<br>environment can be installed from =
the readme.htm or by running <br>setup.exe on the root of the Platform =
SDK compact disc. The most <br>recent version of the build environment =
is also available =
at<br>http://www.microsoft.com/msdn/sdk/platform.htm.<br><br>Some =
components may also require you to install runtimes, depending<br>on the =
platform on which you are trying to run the sample.<br>Redistributables =
are available in the \Mssdk\Redist subdirectory<br>on the Platform SDK =
compact disc.<br><br>Documentation for the components listed above can =
be installed<br>from the Platform SDK compact disc, or can be viewed =
online at<br>http://premium.microsoft.com/msdn/library/. This is a free =
service;<br>registration is necessary.<br><br>Read the release notes in =
readme.htm and readme.txt in the root of <br>the Platform SDK compact =
disc or visist the MSDN web site for more <br>information about the =
Platform SDK at http://www.microsoft.com/msdn/sdk/<br><br>I included the =
Setenv file from the MSSDK platform and my currect autoexec.bat is =
below.<br><br><font face=3D"Courier"><b>This what happens when I run =
Setenv</b><br><br><br> To set the SDK environment paths, run SETENV from =
your Platform SDK<br> installation directory.<br><br> Usage: =
SETENV MSSDK<br> Where: MSSDK specifies where =
the Platform SDK was installed<br><br> Example: C:\MSSDK\SETENV C:\MSSDK =
sets the environment relative to C:\MSSDK<br><br><br> Warning: check =
your LIB, INCLUDE and PATH to verify that the<br> SDK Lib, =
Include, and Bin directories precede the compiler<br> directories =
in the environment.<br><br> Microsoft Visual Studio provides =
VCVARS32.BAT to set them.<br> You must run VCVARS32.BAT first and =
then run SETENV.BAT.<br><br> Current settings:<br><br> LIB=3D<br> =
INCLUDE=3D<br> =
PATH=3DC:\DJGPP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND<br><br><br><font =
size=3D1><b>This is my current autoexec.bat</b><font size=3D2 =
face=3D"Times New Roman"><br><br><font face=3D"Courier">LH /L:2,38400 =
MSCDEX.EXE /D:OEMCD001 /L:D<br>SET BLASTER=3DA220 I5 D1 H5 P330 T6 =
<br><br>set PATH=3DC:\DJGPP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND<br>set =
DJGPP=3DC:\DJGPP\DJGPP.ENV<br><br>SET MIDI=3DSYNTH:1 MAP:E<br>SET =
SOUND=3DC:\PROGRA~1\CREATIVE\CTSND<font face=3D"Arial"></p>
</font></font></font></font></font></font></body></html>
------=_NextPart_000_01BD9A3E.3E298440--
- Raw text -