MSDN Frequently Asked Questions (FAQ)

3.10    | 3.10

The information in this article applies to:

• Microsoft Developer Network (MSDN) Development Platform CD

SUMMARY

There are six sections in this document:

1. General MSDN Questions and Answers

MORE INFORMATION

1. General MSDN Questions and Answers

How much does a membership in the Developer Network cost?

   MSDN Level 1 membership costs $195 U.S. ($275 CAN) per year, MSDN Level
   2 membership is $495 U.S. ($555 CAN) per year. Developers who are
   currently members of MSDN Level 1 can upgrade to Level 2 membership for
   $395 U.S. ($555 CAN). International customers, please contact your local
   subsidiary.

   Realizing that most developers already have one or more of the
   individual components of the Development Platform, we chose not to have
   an upgrade price (no one would pay the suggested retail price). Instead
   of using marketing tactics, we chose to have one "real price" for all
   developers.

   In the U.S. and Canada, call (800) 759-5474, 24 hours a day, 7 days a
   week. In France, call 05 90 59 04 (Toll Free). In Germany, call
   0130 81 02 11 (Toll Free). In the Netherlands, call 06 022 24 80 (Toll
   Free). In the United Kingdom, call 0800 96 02 79 (Toll Free). For any
   other country in Europe, call +31 10 258 88 64. In Japan, call
   03-5461-2617. Everywhere else, call 402-691-0173.

   MSDN Level 1 membership provides information that you need to develop
   for Windows and Windows NT via the searchable Development Library (CD)
   and the Developer Network News. Level 2 membership includes Level 1
   benefits plus all the operating systems and Windows, Windows for
   Workgroups, and Windows NT SDKs and DDKs on the Development Platform (CD
   set).

   For Library setup support, call (425) 635-7033. For Platform setup
   support, call (800) 936-5800.

   Development Platform support is available by calling (800) 936-5800.

   Level 1 membership includes a single-user license for the Development
   Library. Level 2 membership includes a single-user license that applies
   to both the Development Library and Platform.

   For the Development Library, additional user licenses to share a single
   CD over a network may be purchased for $40 ($55 CAN) each. Each
   additional user license allows one designated user to install the
   Development Library viewer software on a single workstation to access
   the CD contents. To order additional user licenses, call (800) 759-5474.

   For large workgroups, Level 1 memberships with concurrent-user licenses
   are available in two configurations: a five-user license is $595 ($835
   CAN) and a twenty-five-user license is $2495 ($3495 CAN). Concurrent-
   user licenses permit the members of a large group to install the
   Development Library viewer software on their workstations, but allow no
   more than five (or twenty-five) users to run the application at a given
   time. The number of developers supported by a concurrent-user license
   depends primarily on their usage patterns and network performance.
   Developers who expect to make heavy use of the Development Library
   should consider individual memberships.

   No. Level 2 membership includes a single-user license for both the
   Development Library and Development Platform. Because Microsoft
   operating systems can be licensed only to a single user, additional
   licenses are not available for Level 2 memberships.

   The Windows Development Toolkit is a retail product that provides the
   base level toolkits that developers need to write applications for
   Windows, WFW and Windows NT. It is essentially an entry level product
   for developers who want to "get their feet wet" with Windows
   programming. It is not designed to satisfy the demands of other Windows
   programmers. This is Microsoft's only retail software development kit
   for Windows. All other kits have been discontinued and are available via
   MSDN only. This product includes:

      * Win32 SDK v. 3.1 (no DDK)
      * Windows 3.1 SDK
      * OLE 2.01 (16 bit Windows only- not 32-bit or Mac)
      * Simple MAPI SDK (not MAPI 1.0)
      * A "Special Edition" of the Development Library containing docs and
        samples for the above SDKs, as well as a sampling of the Technical
        Articles, MSJ issues etc.

   Major differences between MSDN Level 2 and WDT

      * MSDN Level 2 is a membership program that delivers the latest in
        Microsoft operating systems, development kits and technical and
        strategic information . WDT is a retail product.
      * MSDN includes more than 20 different SDK's - WDT has 4
      * MSDN includes DDK's - WDT does not
      * MSDN includes nearly 40 different operating system versions - WDT
        does not
      * MSDN includes international versions of SDK's where available - WDT
        does not

   Limited Developer Network News subscriptions are available. Send email
   with your mailing address to:

      CIS: >INTERNET:msdn@microsoft.com
      Internet: msdn@microsoft.com

   If you have a membership problem or question, call the Microsoft
   Developer Network Service Center at (800) 759-5474.

   Please send in your MSDN suggestions to one of the following addresses:

      Internet:  msdn@microsoft.com

      Mail: Microsoft Developer Network
            One Microsoft Way
            Redmond, WA  98052-5399

      Fax:  (425) 936-2490
            Attn: Developer Network

When will the Office Development Kit (ODK) show up?

   Most of the ODK (what was ready) was shipped in the April Library. We're
   working to prepare and test the rest of the ODK so it will show up in
   its entirety in the July Library.

Does the Development Library serve as the documentation for the Development Platform?

   Yes, the Development Library provides the documentation for the SDKs and
   DDKs distributed via the Development Platform, in addition to other
   information.

   Yes. Printed copies of selected manuals can be ordered from Microsoft
   Press at (800) MS-PRESS for an additional cost. Documentation for the
   operating systems is not provided as part of the Developer Network.

   The full SDKs (tools, headers, libs, docs, and so forth) are included on
   the Development Platform. Traditionally, SDKs do not contain compilers.
   The Development Platform is intended to be a development platform to
   which you add the compiler of your choice from the vendor of your
   choice.

   The only exception to this rule is when a compiler is not generally
   available, such as the Alpha and MIPS compilers in the Win32 SDK. These
   will remain in the SDK (and thus the Development Platform) until these
   compilers are generally available.

   Windows 95 will be included once the Non-Disclosure Agreement (NDA) is
   removed. We do not include NDA software on the Development Library or
   Platform. There are public Windows 95-related technical articles and
   other information on the Development Library.

   Pen Windows is included in Windows 3.1. The only thing not included is
   the tablet driver that is specific to the pen tablet the customer is
   using (this comes from the tablet's manufacturer). The Pen SDK is
   included in the Windows 3.1 SDK, and pen driver samples are in the DDK.

   Yes, the Development Platform contains the Simple MAPI SDK and CMC SDK,
   which are the kits developers need to mail-enable their applications.
   However, we don't have a full MAPI SDK, which would allow developing a
   MAPI-compatible mail provider. This SDK is not ready for distribution
   in the July Platform.

   The Simple MAPI is a simple, quick API for mail-enabling applications so
   that apps can access the messaging features of Windows for Workgroups or
   Microsoft Mail 3.x. Extended MAPI is a more complex, object-oriented API
   for building messaging-reliant applications like mail clients, groupware
   applications, and so forth. The Extended MAPI is currently in beta and
   under NDA.

   It's 16-bit. The 32-bit OLE is included in the Windows NT 3.5 (Daytona)
   SDK.

   We are looking at this, but there are no current plans.

   To include this content would require extensive work (specifically, for
   the documentation). We do not have enough demand for this content to
   justify the effort. We will continue to sell the LM PDK separately as
   long as we have customer demand and as long as MS continues to sell LAN
   Manager.

   We are planning on including the final version of WinG on the October
   Platform.

My search ranges keep disappearing. Why?

   There is a bug in the software. Ranges are stored in a file called
   VIEWER.INI which is located in your Windows directory. If you have lost
   your ranges, you can run Setup to have the default ranges restored.
   Create ranges you use often. Make a backup of VIEWER.INI. If your ranges
   should disappear again, simply restore the backup version of VIEWER.INI,
   or at least the search range section, [MSDNCDx. Ranges].

   The files referred to in the Knowledge Base are part of the
   Microsoft Software Library, which can be found on the Internet at
   ftp.microsoft.com in the /SOFTLIB/MSLFILES directory and on MSDL at
   (425) 936-MSDL. Download INDEX.ZIP for filenames and abstracts.

   VxD Lite was removed from the Development Library due to licensing
   issues. MSDN Level 2 members can use the DDK instead.

   This problem can occur if the Library is trying to refer to a topic that
   does not exist. Edit VIEWER.INI in the Windows directory using a text
   editor. In the [MSDNCDx.Last] section, set Source=0. Save the file and
   try the Library icon again.

   The most common reason for this is debris and dust on the disc. Use a
   soft cloth or facial tissue and some water (mild detergent if
   necessary).

   Wipe the disc from the center to the edge. NEVER use solvents of any
   kind as they may have an adverse effect on the polycarbonate material
   that the CD is made of. The second most common reason is that the CD-ROM
   drive is in need of cleaning or repair. Some older CD-ROM drives are
   unable to read more than 540 MB on a CD.

   If you suspect a bad CD, call the Microsoft Developer Network order
   center at (800) 759-5474 and request a replacement disc.

   The Library search engine uses the space pointed to by the MS-DOS TEMP
   environment variable (usually set in AUTOEXEC.BAT). Be sure that TEMP is
   not assigned to a RAM drive. Some searches require as much as 4 megs,
   sometimes more! Be sure you have enough space on your hard drive. If
   TEMP is assigned to a network drive, the Windows directory will be used
   by default.

   There is a bug in the search engine that doesn't release the system
   resources it uses. This only happens when you use a custom "Restricted"
   range. After 5 or so searches, all of your system resources will be used
   up. Closing the Viewer software will free up the resources again.

   Use CTRL-INSERT instead of Edit.Copy. Alternatively, you can install the
   Generic/Text Only printer driver in Control Panel and Connect it to
   FILE:.

   When you print to this printer, you will be asked for a file name.

   Yes. See the CD insert for licensing information.

   The hyperlinking process is automated. These 'false jumps' are a
   byproduct of the automated process.

   This is a known bug. There are no known workarounds. The problem has
   been addressed in the July Library.

   This is a known problem. Install the Olivetti HG 308 PS Postscript
   printer driver and try printing to your printer with that.

   This GPF occurs when you try to print a topic with a graphic to certain
   printers. If you are printing to a Hewlett-Packard printer, try using
   the HP4/4M printer driver instead of your usual driver. This problem has
   been addressed in the July Library.

   The "Dr. GUI" bitmap is an anchor for graphics that weren't prepped in
   time, or are not available in a format that can be converted to a
   viewable format for the Library. If there are important graphics
   missing, please send email to INTERNET:msdn@microsoft.com.

   This bug is caused by attempts to open multiple instances of the Library
   software which is not possible.

   Try copying the topic and pasting to word processing application. The
   Library software uses screen fonts and will not print correctly and can
   cause other errors with some printers and printer drivers. Pasting into
   a word processor will usually convert these fonts to printer or Windows
   TrueType fonts so that they can print correctly. This problem has been
   addressed in the July Library.

   One suggestion is to manually install the Library. There is a text file
   on the Library with instructions on how to do this. Look for the file
   MANSETUP.TXT.

   The Library uses Viewer 2.0 and will try to copy several files to the
   Windows \SYSTEM sub-directory. If you are running shared Windows from a
   network, setup may fail because it is unable to copy these files to the
   network drive. You must have write privileges to the drive where Windows
   is installed and running.

Development Platform .DOCs and .WRIs are unreadable. Is my disc corrupt?

   The Development Platform contains all of the operating systems and SDKs,
   including international ones. Some versions (i.e. Japanese) use
   double-byte character sets. Files created for these systems can only be
   read on DBCS-enables systems). To find the equivalent files in English,
   look on the next disc in the same directory.

   The liner notes were incorrect. Service Pack 2 is the latest. It
   includes CSD003, which is the latest.

   GO DAYTONADEV is the developer forum for Windows NT 3.5 prerelease
   developers.

   The tools had a bad setup that failed to copy some files and installed
   icons in the Program Manager that referenced locations on the Microsoft
   corporate network. The correct tools are on the July Development
   Library.

   The problem was not that the SDK did not install; it was that there was
   no entry to install the Video for Windows run time in our installer
   utility.

   This has been fixed for the July Platform.

   They were tough to find on the April Platform, but are available in the
   same directory as the Help compiler in the July Platform.

   We omitted some things on the Win32 SDK and Windows NT DDK disc (Disc 5)
   in April. For example, we left off the CD audio tracks that are part of
   the hardware compatibility tests. We will be fixing this for the July
   release of the Platform.

   Japanese Windows or Windows NT.

How do I get more information about DevCast?

   Send mail to >INTERNET:devcomm@microsoft.com.

   Send a brief programming profile, company name, address and phone
   number, plus the name of the product you wish to test, to

      Email:  >INTERNET:msdn@microsoft.com

      Mail:   Beta Coordinator - X product
              Microsoft
              One Microsoft Way
              Redmond, WA 98052

   FOR WINDOWS 95: email >INTERNET:winbeta@microsoft.com

   Call the Microsoft Developer Solutions Team at (800) 426-9400.