mstools/ole20/mips/readme.wri - annotate

Return to readme.wri CVS log

Up to [WindowsNT SDKs] / mstools / ole20 / mips

Annotation of mstools/ole20/mips/readme.wri, revision 1.1.1.1

1.1 root 1: 1�� l�&&&&&&&
2:
3: OLE 2.0 Toolkit -- April 1993 Release
4:
5: MicrosoftR Object Linking and Embedding
6: Version 2 for the WindowsTM NT Operating System on MIPS
7: Beta2 Release Notes
8: July 1993
9:
10:
11:
12: This is a legal agreement between you (either an individual or an entity), the end user, and Microsoft
13: Corporation. If you do not agree to the terms of this Agreement, promptly return the disks and the
14: accompanying items (including written materials and binders or other containers) to Microsoft Corporation.
15:
16:
17: MICROSOFT LICENSE AGREEMENT FOR PRE-RELEASE PRODUCT
18: (Microsoft Object Linking and Embedding (OLE) Version 2.0 for Windows NT on MIPS, Beta2 Release)
19:
20:
21:
22: 1. GRANT OF LICENSE. Microsoft grants you the non-exclusive, non-assignable right to make an unlimited number of copies of the enclosed software (including all OLE libraries, debug utilities, and development tools) and documentation (collectively, "PRODUCT") solely for internal use for the purposes of testing and evaluation. You may not rent, lease, sell, sublicense, assign, or otherwise transfer this PRODUCT. You may not reverse engineer, decompile, or disassemble the PRODUCT. You must cease use of the PRODUCT upon the earlier of either Microsoft's public release of the commercial version of the PRODUCT, or upon request by Microsoft.
23:
24: 2. PRE-RELEASE CODE. This PRODUCT is pre-release code and is not at the level of performance and compatibility of the final, generally available product offering. The PRODUCT may not operate correctly and may be substantially modified prior to first commercial shipment.
25:
26: 3. COPYRIGHT. The PRODUCT is owned by Microsoft or its suppliers and is protected by United States copyright laws and international treaty provisions. Therefore, you must treat the PRODUCT like any other copyrighted material (e.g. a book or musical recording).
27:
28: 4. TERMINATION. Microsoft may terminate this Agreement in writing at any time, with or without cause. Upon termination, you shall immediately return, or certify destruction of, all full or partial copies of the PRODUCT and all other materials provided by Microsoft. You agree that your obligation regarding non-disclosure of any specific information shall terminate at such time as that specific information is in the public domain through no fault of your own, or upon written consent by Microsoft.
29:
30: 5. SAMPLE CODE. Microsoft grants you a non-exclusive royalty-free right to use and modify the source code version and to reproduce and distribute the object code version of those portions of the PRODUCT which are designated as Sample Code provided that you: (a) distribute the Sample Code only in conjunction with and as part of your software product; (b) do not use Microsoft's name, logo, or trademarks to market your software application product; and (c) agree to indemnify, hold harmless, and defend Microsoft from and against any claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of your software application product.
31:
32: DISCLAIMER OF WARRANTY
33:
34: The PRODUCT, including Sample Code, constitutes pre-release code and may be changed substantially before the first commercial release. The PRODUCT and Documentation are provided "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT FURTHER DISCLAIMS ALL IMPLIED WARRANTIES INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR OF FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE PRODUCT AND DOCUMENTATION REMAINS WITH YOU.
35:
36: IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE PRODUCT OR DOCUMENTATION, EVEN IF MICROSOFT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
37:
38: U.S. GOVERNMENT RESTRICTED RIGHTS
39:
40: The PRODUCT and Documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(i) and (2) of Commercial Computer Software -- Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Microsoft Corporation/ One Microsoft Way/Redmond, WA 98052-6399.
41:
42: This Agreement is governed by the laws of the State of Washington.
43:
44: Should you have any questions concerning this Agreement, or if you desire to contact Microsoft for any reason, please write:
45: Microsoft Corporation OLE Beta Coordinator/One Microsoft Way/ Redmond, WA 98052-6399.
46:
47: Before using this Beta2 release of the OLE 2.0 Toolkit for Windows NT on MIPS (referred to herein as 'this Beta OLE Toolkit' for brevity), please read the following release notes.
48:
49: Purpose of Release
50: This release shares much of its code and documentation base with the April 1993 final release of the OLE 2.0 Toolkit for Windows. A substantial portion of the overall functionality of OLE 2.0 for Windows NT is now in place and working at some level. However, it is important to keep in mind that this Beta OLE Toolkit is not at the same level of development as the final OLE 2.0 Toolkit for Windows. Some features which were included in the Windows version may not be implemented yet for the Windows NT version, and others may not work properly.
51:
52: This Beta2 release of OLE 2.0 for Windows NT on MIPS is virtually identical in functionality to the Beta2 release of OLE 2.0 for Windows NT on Intel machines for all provided components. The MIPS release has not been tested as extensively as the Intel release, and there are a few minor problems with the MIPS release that do not manifest on the Intel release. These problems are noted where appropriate in these release notes.
53:
54: Contents of this Beta OLE Toolkit
55: The following directory structure and files can be found in this release:
56: [ROOT]
57: Release notes for this OLE 2.0 Toolkit (this file)
58: Configuration batch files REGINIT.BAT and SETNVOLE.BAT
59: BIN
60: Debug versions of the OLE 2.0 DLLs
61: Sample and test application executables
62: .REG registration files for the sample and test application executables
63: DOCS
64: OLE documentation
65: Help files for OLE and UI Dialog implementation
66: OLE 2.0 Specification
67: Technotes
68: OLE 2.0 Backgrounders
69: Bug reporting template for Compuserve
70: H
71: The .H header files
72: LIB
73: The .LIB library files
74: SAMPLES
75: Sources for different sample programs demonstrating OLE 2.0
76: Sources for OLE 2.0 UI components
77:
78: Known Problems
79: OLE 2.0 objects cannot be activated or edited properly from within OLE 1.0 containers.
80:
81: Known problems with any of the sample or test applications are discussed in the section describing the application.
82:
83: Configuration
84: To properly configure your machine to make use of this Beta OLE Toolkit, create a new directory on your hard disk and copy the entire Beta OLE Toolkit tree from the CD/ROM to this new directory. The default location assumed by certain components in the toolkit is C:\MSTOOLS\OLE20. If you received your copy of this Beta OLE Toolkit with the Win32 SDK, this will be done for you as part of the Win32 SDK Setup procedure.
85:
86: Once you've done this you will need to manually run the REGINIT batch file to add registration information concerning Beta OLE Toolkit components to your registry. This batch file will first spawn REGADD.EXE, a tool which is used both to clean up out-of-date information in the registry as well as to set certain default OLE information in the registry; simply click on the "RegAdd" menu and select "Cleanup", then click on the "RegAdd" menu and select "Default", then close the tool. The batch file will continue and will run REGEDIT to add registry information specfic to OLE 2.0 and the samples. This will *only* need to be done the first time you install the SDK. Note, however, that REGADD.EXE may be used at any future time to remove all Beta OLE Toolkit related information from the registry if so desired by selecting "Cleanup" from the "RegAdd" menu.
87:
88: Please note that any registration information concerning the 32-bit OLE 1.0 test applications included in this release will be registered by the applications themselves when they are executed.
89:
90: To properly set the environment for building the sample code you will need to invoke the SETNVOLE batch file, which will add certain Beta OLE Toolkit directories to your PATH and other environment variables. If you wish this can also be done at the system level by way of the "System" applet in the control panel.
91:
92: You will need to use the "System" applet in the control panel to add the C:\MSTOOLS\OLE20\BIN directory to your path (assuming a default installation location) in order for certain OLE 1.0 applications (Mail and Cardfile) to work as OLE 1.0 containers properly with OLE 2.0 server applications.
93:
94: You will also need to manually create a new Program Group (e.g., Win32 OLE2) in the program manager, and create new Program Items within this new group for each of the .EXE files in the BIN directory of the Toolkit.
95:
96: Documentation
97: This Beta OLE Toolkit comes with the same electronic versions of the documentation that were released with the April 1993 final release of the OLE 2.0 Toolkit for Windows. Generally speaking, the documentation for the OLE 2.0 Toolkit for Windows is equally applicable for this Beta OLE Toolkit for Windows NT. The accompanying sample code should be used as supporting material for the documentation.
98:
99: Since the publishing of the Programmer's Reference, some edits were made in the documentation. These edits are reflected in the electronic copy of the documentation.
100:
101: A Windows Help file version of the documentation is included to ease the viewing of the documentation online.
102:
103: Technotes
104: A separate technote file (TECHNOTE.WRI) is included in the DOCS directory. The file contains helpful information and a more detailed discussion on different subjects and issues that we have found difficult and in a need of a more careful explanation. Please read the notes before writing your OLE 2.0 application. Especially the topics about in-place editing should be read carefully when writing in-place editing applications.
105:
106: Specification
107: This Beta OLE Toolkit contains the latest electronic version of the OLE 2.0 Specification. We have included the specification for those who are interested in a more detailed background and architectural discussion of the OLE 2.0 product. There is a significant overlap in material between the Programmer's Reference and the Design Specification. Some of the last minute edits that did not make it in the Programmer's Reference can be found in the Specification.
108:
109: Features Currently Implemented
110: This Beta OLE Toolkit supports the following major areas of OLE 2 functionality:
111: * Compound Files
112: * Linking
113: * Embedding
114: * Drag and Drop
115: * Visual (In-Place) Editing
116: * Linking to Embedded Objects
117: * Compatibility with OLE 1.0 applications
118:
119: The sample applications included in this release exercise each of these areas of functionality. In addition, these sample applications implement several of the recommended OLE 2 standard UI dialogs.
120:
121: Important Notes
122: The following notes are worth mentioning for this release:
123:
124: Adherance to 16-bit Implementation
125: This release of the 32-bit OLE code for Windows NT uses header files, interfaces, and APIs that
126: are fully compatible with the final release of the 16-bit OLE 2.0 Toolkit for Windows.
127: Registry Information
128: All CLSIDs are now stored under a CLSID entry, and all IIDs are under an Interface entry.
129: An OLE entry has been added under the HKEY_LOCAL_MACHINE\SOFTWARE tree which
130: includes the size and location of OLE shared memory, the list of 16-32 name mappings for
131: known dlls, the name of the shared memory server executable, and some miscellaneous info.
132: InprocHandler, Inprocserver now have optional 32 bit equivalents: Inprocserver32,
133: Inprochandler32. If only the old (16bit) entries are present their value is mapped using
134: the KnownDlls list.
135:
136: Areas Subject to Change
137: OLE Automation components will be provided in a future release.
138:
139: Some of the interfaces will undergo changes in order to have 32-bit OLE 2.0 for Windows NT be Unicode-based. Our plan is that *all* strings in all APIs and methods, incuding those in structures, will be Unicode, including IDispatch and typeinfo interfaces.
140:
141: Please note that ongoing work may result in a change, addition, or deletion of one or more interfaces.
142:
143: The changes that may take place between now and the final release:
144: * The final release will contain retail versions of the libraries (this Beta is debug only).
145: * The docfile format may change.
146: * Some of the interfaces may change.
147:
148: Hints
149: Please consider the following hints when using this Beta OLE Toolkit:
150: 1. Use of the Microsoft Win32 SDK is highly recommended. This Beta OLE Toolkit release
151: was developed using the final release of the Win32 SDK.
152: 2. Before installing this Beta OLE Toolkit on your machine, please make sure that you don't
153: have any OLE 2.0 components (dlls, libs, sample code, binaries etc.) in ANY directory on your
154: machine.
155: 3. If you experience difficulties where applications cannot find classes that are registered, try
156: rebuilding the registration database. Make sure that you follow the new registration guidelines.
157: 4. In order to correctly use this Beta OLE Toolkit, you need to add the BIN directory to your
158: PATH statement. This is to assure that the sample programs can find the OLE 2.0 DLLs. The
159: batch file SETNVOLE.BAT will take care of this and other important configuration issues for
160: you.
161: 5. To debug incoming messages in your application, place the breakpoint in CSvrLRPC::Invoke.
162: 6. To debug outgoing messages in your application, place the breakpoint in CCliLRPC::Call.
163: 7. To do low level debugging, place the breakpoint in LrpcWndProc.
164: 8. You are able to avoid some compiler problems if you keep the names in nested classes short.
165: 9. If you have a transacted storage, you should not rename an unopened child element more than
166: once before committing your changes or you will not be able to access it. For example, if
167: transacted Storage S contains child A, you shouldn't do the following:
168: pStgS->RenameElement("A", "B")
169: // optional ops without a Commit...
170: pStgS->RenameElement("B", "C")
171: // optional ops without a Commit...
172: pStgS->OpenStream("C", ..) // this will not work correctly
173: A simple solution is to open and release the child before renaming it (if you can't open it that
174: means its already open and you won't experience the above problem).
175: 10. If you begin to notice strange behavior, you might try re-registering the registration information
176: by re-executing the REGINIT batch file.
177: 11. Keep an eye on your TMP or TEMP directory for random .DFT files. These can build up and
178: really use up disk space.
179: 12. Use PVIEW and PVIEWER (supplied with the Win32 SDK) to clean up after any random or
180: unexpected program terminations.
181:
182: Issues Related with the OLE 2 Libraries
183: 1. 16/32-bit Interoperability is not supported in this release.
184: 2. OLE 1.0/2.0 compatibility is supported in this release.
185:
186: Issues Related with the Sample Code
187: 1. Different levels of debug output messages can be enabled in the OUTLINE sample applications.
188: The default level of debug messages is controlled by how the OUTLUI.DLL is built. This DLL
189: maintains a global debug level value which can be modified at run-time (via the Debug menu in
190: the OUTLINE applications--DbgSvr, DbgCntr, DbgISvr, DbgICntr). The debug level in effect
191: applies to all running applications because they all are bound to the same OUTLUI.DLL
192: instance.
193: The default value for the debug level for OUTLUI.DLL can be controlled by the value of the
194: DEBUG= entry in the UIMAKE.INI.
195: The following values produce the following levels of debugging information:
196: 0 -- no debug messages
197: 1 -- a small amount of debug messages
198: 2 -- debug messages to trace every OLE method/API called (default)
199: 3 -- debug messages to trace important functions in OUTLINE applications
200: 4 -- debug messages to trace object reference counting.
201: 2. The OUTLINE series must be compiled with the option to consider 50 characters significant in
202: function names.
203: 3. Although OUTLINE sample code uses the OLE 2.0 UI dialog as a separate DLL, we recommend
204: that you statically link the OLE 2.0 dialogs with your code. If you use the UI component as a
205: separate DLL, please use a unique name and install the DLL in the same directory you install
206: your application.
207: 4. ICNTROTL does not have a mechanism for managing the number of in-place server .exes that it
208: keeps running. Once activated, the servers will not be shut down until the document is closed.
209: When running in low memory, the applications should implement a mechanism that will take
210: care of shutting down the least recently used apps whose objects are not in view.
211: 5. ICNTROTL can be used as both inside-out and outside-in capable container. The option is
212: controlled via the debug menu in the application. Note that this menu (and the option to change
213: the behavior of the application) is provided for debugging purposes only. A 'real' application
214: should NOT provide a user control for changing between inside-out and outside-in modes. When
215: using ICNTROTL it is recommended that you set the option before inserting any in-place capable
216: objects (i.e. in the beginning of the session).
217: 6. ISVROTL.EXE is implemented (and registered in the registry) as an inside-out capable
218: server. It is recommended that the containers that support in-place editing use ISVROTL in
219: inside-out fashion.
220:
221: For a detailed discussion of the behavior and implementation of inside-out vs. outside-in capable
222: servers and containers, please refer to the OLE 2.0 Toolkit TECHNOTES and Specification.
223:
224: Debugging Tools
225: DFVIEW
226: DFVIEW.EXE is a Windows program that provides a listing of the elements within a docfile. Just load the file that you want to view via the File.Open... menu. DFVIEW has a Help dialog that will explain in detail how to use the tool.
227:
228: IDataObject VIEWER
229: The IDataObject Viewer can be used for looking at the list of data formats offered by IDataObject, either from a clipboard or a drag/drop operation.
230:
231: LRPC Message Monitor
232: LRPC Message Monitor is a tool that displays the messages passed between two applications. You are able to view the messages in the window and scroll through them.
233:
234: UUIDGEN
235: UUIDGEN.EXE is a program which generates a unique class id (CLSID). For UUIDGEN to correctly generate a unique id, you need to run it on a machine that has a network card. For details on CLSIDs and their use, please refer to the documentation in the Programmer's Reference and Chapter 4 of the Design Specification. If you don't have a network card in your system and you need a CLSID you can obtain one by calling Microsoft at 1-800-358-5015.
236:
237: Sample Code
238: This release contains several different sample programs with source code. Please note that the sample programs are not complete, that they do not have equal implementation of features, and that not all of them exercise all of the features implemented in the Beta OLE 2.0 libraries.
239:
240: Please note that all MAKEFILEs assume that you have properly configured your machine using the provided SETNVOLE batch file.
241:
242: OUTLINE SERIES
243: This sample application set demonstrates taking a 'base' application (in this case OUTLINE.EXE)
244: and extending it into an OLE 2.0 server and container (both in-place editing and non-in-place editing versions are provided -- the inplace editing version can contain both inside-out and outside-in objects).
245:
246: All five applications are built from common sources. Files that begin with CNTR are specific to
247: the container version, files that begin with ICNTR are specific to the in-place container version, files that begin with SVR are specific to the server version and files that begin with ISVR are specific to the in-place server version . These sample applications highlight the changes necessary to implement OLE into an existing application. The container versions have the same functionality as the base (OUTLINE) and also allow you to embed and link objects.
248:
249: All OUTLINE applications support loading and saving files using docfiles for storage. The five versions of the application are built in five subdirectories (outline\outline, outline\cntroutl, outline\icntrotl, outline\isvrotl, outline\svroutl). The same MAKEFILE (makefile) is used to build all five applications:
250:
251: nmake -- builds OUTLINE base application
252: nmake APP=svroutl -- builds SVROUTL server application
253: nmake APP=isvrotl -- builds ISVROTL in-place server application
254: nmake APP=cntroutl -- builds CNTROUTL container application
255: nmake APP=icntrotl -- builds ICNTROTL in-place container application
256: nmake clean -- deletes generated files for OUTLINE
257: nmake APP=XX clean -- deletes generated files for XX
258:
259: Cntroutl has problems activating OLE 1.0 server applications with this release. Also, Cntroutl presentations of Srvrdemo (OLE 1.0) objects do not look like they should.
260:
261: BTTNCUR.DLL
262: SAMPLES\BTTNCUR directory contains the source files that are used for creating the standard button images and cursors DLL. The MAKEFILE in the directory will build the BTTNCUR.DLL. For the use of the DLL, please see the OUTLINE sample code sources. This is version 1.1 of BTTNCUR, an update from the version 1.0 DLL shipped with "The Windows Interface" book. CHANGES.TXT file highlights the additions and modifications. If you use BTTNCUR.DLL you should use a unique name to avoid overwriting.
263:
264: GIZMOBAR.DLL
265: SAMPLES\GIZMOBAR directory contains the source files that are used for creating the standard gizmobar DLL. The MAKEFILE in the directory will build the GIZMOBAR.DLL. For the use of the DLL, please see the OUTLINE sample code sources. If you use GIZMOBAR.DLL, you should use a unique name to avoid overwriting.
266:
267: OLE 2.0 UI Component
268: The OUTLINE sample code applications use the standard OLE 2.0 dialogs found in OUTLUI.DLL. Although the OLE 2.0 UI can be used as a dynamically loaded library (DLL), we recommend that you statically link the dialog code (LIB) with your application. If you decide to use the OLE 2.0 dialogs as a DLL, please USE A UNIQUE NAME FOR YOUR DLL and install it in the same directory you install your application to avoid name conflict and overwriting.
269:
270: Test Applications
271: CL32TEST.EXE and SR32TEST.EXE
272: Cl32test and Sr32test are test applications that can be used for testing your OLE 2.0 applications. Both Cl32test and Sr32test are fully featured OLE 2.0 applications. Additionally, they implement ways to exercise OLE 2.0 features that cannot be found in a 'regular' OLE 2.0 application. The best way to become familiar with the features provided is to play with the test applications.
273:
274: There is a known problem with using Sr32test in interoperability scenarios with OLE 1.0 container applications. In general, Sr32test only works with OLE 2.0 container applications at this time.
275:
276: Cl32test does not correctly handle more than a single in-place object within a window. Also, when you delete an InPlaceSDemo1 object from a Cl32test window, you will receive a warning that the reference count is off; just press OK and continue.
277:
278: OLETEST.EXE
279: OLETEST is an OLE 2.0 application used to test container functionality. The best way to become familiar with the features provided is to play with the application. Please note that FileSave does not work properly (although FileSaveAs does), and the Test menu does not work at all.
280:
281: SDEMO1.EXE
282: This is an OLE 1.0 server sample application upgraded to an OLE 2 server. It allows you to create
283: a rectangle and set its color. It is an SDI application. You can create one rectangle at a time. It
284: supports 2 verbs (0=play, 1=edit). For verb play it cycles through the available object color choices.
285:
286: IPSDEMO1.EXE
287: This is an OLE 1.0 server sample application upgraded to an OLE 2 server. IPSDEMO1 is an SDI application. You can create one rectangle at a time. In addition, IPSDEMO1 supports in-place editing. It supports two verbs (0=play, 1=edit in place). For verb play it cycles through the available object color choices. IPSDEMO1 has a draggable button bar that can be anchored to the top of the frame window, anchored to the left side, or unanchored as a floating pallet.
288:
289: 32-bit OLE 1.0 Test Applications
290: A collection of 32-bit OLE 1.0 test applications is provided to enable testing of OLE 1.0/2.0 compatibility. The best way to become familiar with the features provided is to play with the test applications.
291:
292: It is also interesting to note that several 32-bit OLE 1.0 applications come with Windows NT or the Win32 SDK; these include the container applications Cardfile and Mail, and the server applications Media Player, Pbrush, Soundrec, and Packgr32.
293:
294: CLTEST.EXE
295: CLTEST is a 32-bit OLE 1.0 application used to test container funtionality.
296:
297: CLIDEMO.EXE
298: CLIDEMO is a 32-bit OLE 1.0 application used to test OLE 1.0/2.0 compatibility.
299:
300: SRVRTEST.EXE
301: SRVRTEST is a 32-bit OLE 1.0 application used to test server funtionality.
302:
303: SRVRDEMO.EXE
304: SRVRDEMO is a 32-bit OLE 1.0 application used to test OLE 1.0/2.0 compatibility.
305:
306: Developer Support
307: Technical support for this Beta OLE 2.0 Toolkit release for Windows NT will be supported on Compuserve via the WINOBJ forum. All communication (questions, bug reporting etc.) will happen via this forum of Compuserve. Below are the current section names:
308:
309: 1) Non Tech Services
310: 2) Component Obj Model
311: 3) Structured Storage
312: 4) OLE: User Interface
313: 5) OLE: Drag&Drop
314: 6) OLE: Naming/Monikers
315: 7) OLE1: Interop issues
316: 8) OLE: Automation
317: 13) OLE1 Issues
318: 17) Strategic Issues
319:
320: Bug Reporting Template
321: All bug reporting should be done via Compuserve by uploading a report using the following bug reporting template (this template can also be found in the DOCS subdirectory of the Beta OLE Toolkit):
322:
323: Bug Title: (66 characters maximum)
324: Product: July 1993 Beta2 OLE 2.0 Toolkit for Windows NT on MIPS
325: Version Number: [returned by OleBuildVersion()]
326: Description of Bug: (be as specific as possible)
327: Duplication Scenario: (be a specific as possible)
328: Work-around: (if any)
329: Tools, Services or Applications Running/Versions:
330: Machine Configuration:
331: Computer Brand and Model:
332: Processor Type and Speed:
333: Memory (RAM):
334: Peripherals (include make/model):
335: network cards:
336: network type:
337: hard disk size:
338: other disk/controllers:
339: CD-ROM drive:
340: video adapter:
341: Reproducible:
342: Always
343: Intermittent
344: Not reproducible
345: Severity level:
346: Sev 1: System crashes, data corruption error
347: Sev 2: Does not operate correctly
348: Sev 3: Cosmetic or minor usability problem
349: Sev 4: Suggestion or documentation error
350: Date:
351: Customer Name:
352: Customer Company:
353: Area Code and Phone:
354: CompuServe ID:
355:
356: Questions and Concerns
357: Any technical questions or concerns regarding OLE 2.0 should be presented via Compuserve.
358:
359: a warning that the reference count is off; just press OK and continue.
360:
361: OLETEST.EXE
362: OLETEST is an OLE 2.0 applicati��v�r�n�g�c�\1&X�T�PXLlIV`��
363: &&&&&&&@l>wct(p+l�h�d`\uXwT�P�L&&&&&&&�w)t�p m(i.eAaH]^YdUwQ~M&&&&&&&~� w� s� o!k�"g�"c+#_1#[%W%%T�'P�'M&&&&&&&�'�)w�)tu+p�+mS-if-f�-b�-^�.Z�.V�0R�0O&&&&&&&�003w23s93oz3k�3hV7df7`�7\�7X�7T8Pv<L&&&&&&&v<�<w=sA=o�Gk�Gh�Gd�H`�H\�IX�IT?JPHJL&&&&&&&&HJ
364: LwLt�Mp�Ml�Th�Td�V`�V\XXXU�YQ�YN&&&&&&&�Y�YwZsZ\o\\kR]ga]c^_�^[�_W�_S�aO�aL&&&&&&&�a�cw�cs�co�ckNdg^dc�d_�d[eWeS!ePgL&&&&&&&ggw�gs�gohkhgPhc_h_nh[}hW�hS�hO�hK&&&&&&�h�hw�hs�hoik8ig<icRi_�i[�iW<jSIjOxjK&&&&&&xj�jw:ks?koCkkQkgUkcfk_jk[~kW�kS�kO�kK&&&&&&�k�kw ls?koCkkQkgUkcfk_jk[~kW�kS�kO�kK&&&&&&��\�=�CkkQkg&����&����\�=&=&&=1&=&��&����1&3&\5&\7&\�&\\r\t\v\�\
\\\\�\�\=����\�\�\�\� \� \`\b\z\|\d\f\\�\�\=����\\�\�\�\F\�\�\�\V\X\l\\�\�\=��l�\�\>\@=c=�=�=�=%=*=X=��<��
365: *O\y\�\�\�\$\4\L\t\w\�\�\�\�\=����\\$\�\�\�\�\ \�\�\!\!\�!\�!\=���!#\#\9$\;$\%\%\%%\�&\�&\b'\d'\�'\�'\�'\�)\=���)�)\�)\s+\u+\�+\�+\�+\,\,\",\?,\^,\�,\�,\S-\=��S-U-\f-\�-\�-\�-\*.\�.\�.\�.\D/\�/\�/\O0\�0\�0\=���0�0\�0\1\1\"2\$2\�2\�2\�2\03\R3\x3\z3\�3\�3\=���3 4\Z4\�4=5="5=$2\�2\�2\�2\03\R�&���=��"5�5\�5\J6\�6\7\7\i7=�7=�2\03\R�&���=���7 8\i8\�8$9\q9\�9\�9\�9\:\D:\R�&���=��
366: D:�:\�:\�:\U;=;=�;=�;=Q<=t<=v<=R=��<��
367: v<�<\�<\=\=\C=\�=\>\b>\�>\?\"?\?\�?\�?\@\=��@4@\z@\�@\&A\bA\tA\�A\3B\�B\�B\C\lC\�C\D\{D\=��{D�D\BE\�E\F\7F\�F\�F\G\G\pG\�G\�G\�G\�G\�H\=���H�H\�H\~I\�I\�I\=J\?J\HJ\L\
368: L\L\3M\5M\�M\�M\=���M�M\&N\�N\�N\[O\-Q\/Q\lR\nR\�R\�R\S\TS\�S\�S\=���ST\
369: T\�T\�T\�T\�V\�V\�V\X\X\X\�Y\�Y\�Y\Z\=��Z�[\�[\Z\\\\\R]\T]\a]\}^\^\�^\�^\W_\�_\�_\�_\=���_�a\�a\�a\�b\�b\�c\�c\�c\�c\�c\�c\Nd\Pd\^d\�d\=���d�d\�d\e\e\!e\"f\$f\:f\Rf\if\�f\�f\�f\�f\�f\=���f�f\&g\g\g\�g\�g\
370: h\Nh\�h\�h\�h\i\:i\Ti\si\=��si�i\�i\�i\�i\�i\�i\j$j\:j\Kj\Tj\cj\vj\�j\�j\=���j�j\k\8k\Ak\Sk\hk\�k\�k\�k\�k\l\ l\l\�j\�j\=��
f�=�/����2�!&�;���(&&&�k&���k�����kQkgUkcfk_jk[~kW�kS�kO�kK&&&&&&&.�!CkkQkg&����&��&Times New Roman&=1&=&��&����

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.