| From: STAR::ZALEWSKI "OpenVMS Development 381-1458" 15-DEC-1995 12:41:18.19
To: RMARCELLO,GORHAM
CC: @DISTLIST:OPENVMSINTEREST,@DISTLIST:OPENVMS,MCQUAID,ZALEWSKI,DAN_S,CHANE,KEITH_B,KEN_B
Subj: Wind/U V3.0 (Win32 APIs) for OpenVMS product has shipped!
----------------------------- TM
| | | | | | | |
| d | i | g | i | t | a | l | I N T E R O F F I C E M E M O
| | | | | | | |
+---------------------------+
TO: Rich Marcello DATE: 15 December, 1995
Mark Gorham FROM: Stephen Zalewski/Ann Mcquaid
CC: List DEPT: OpenVMS Engineering
EXT : 381-1458
LOC : ZK3-4/S23
ENET: STAR::ZALEWSKI/STAR::MCQUAID
SUBJECT: Wind/U V3.0 (Win32 APIs) for OpenVMS product has shipped!
The Bristol Technologies Wind/U for OpenVMS V3.0 product is now available
for general release to the OpenVMS customer base. This product implements
the Win32 APIs on OpenVMS V6.2 or greater. The product consists of a
developers kit and a runtime kit. The run-time kit will be packaged with
OpenVMS V7.0.
The product is available directly from Bristol Technologies. To request kits
and/or licenses, you must send mail to Bristol at the following address:
[email protected]
or call Bristol at: (203)438-6969
Information about the product and associated technical support is available
at the follow web sites:
http://www.bristol.com
http://bulova.zko.dec.com (Digital Internal)
http://www.openvms.digital.com (External)
I would like to take this opportunity to thank the following Digital
engineers for their support in bringing this product to OpenVMS. Without
their timely consulting and engineering help, we would not have been able to
have successfully ported, field tested and shipped this major new product in
just 6 months!
Bob Messenger Decwindows
Rich June Cross platform development
Duane Smith C RTL
Gary Delong C++ RTL
Kathy Kimmel C++ Class libraries
Myth Hollinger UCX/NFS
Eleanor Tanner POSIX
Rich Peterson DECC
Keith Griffin OpenVMS
Burns Fisher OpenVMS
Stu Davidson OpenVMS
Nancy Beckley C++ compiler
Ken Cowan
|
|
Product Information
Product Description:
Wind/U for OpenVMS V3.0 is an implementation of the Microsoft
Windows APIs under OpenVMS/Motif and is a developer's tool for porting
applications to OpenVMS. Wind/U for OpenVMS is a product of Bristol
Technology, Inc.
Product components:
Win32: implementation of the Microsoft Windows Win32 APIs
Microsoft Foundation Class (MFC) library V4.0
WinSock DDL: full support for Windows sockets which
provide networking capabilities to Windows applications
Xprinter: software for adding sophisticated printing
capabilities to OpenVMS or UNIX based applications
Windows 95 Common Controls: support for 12 controls that
are in Windows NT 3.51 and Windows 95 (examples: Tree
View, List View, Progress Bars, Tab Controls, Toolbars, and
so on.)
APIs:
While the implementation of Win32 in Wind/U today is most
closely analogous to the Win32s implementation, the real
focus of the product is compatibility with Visual C++ and
MFC. Wind/U will port applications written with Visual C++
2.1 and MFC 4.0. Wind/U for OpenVMS includes support for
the new Windows 95 controls as well as additional API's
from Windows 95 and Windows NT 3.51.
Bristol Technology, Inc. has also ported HyperHelp to
OpenVMS. HyperHelp is industry standard software for
creating OpenVMS- or UNIX-based online help systems
with WinHelp functionality. HyperHelp is a complementary
product to the Wind/U for OpenVMS development kit and
will be sold separately by Bristol Technology, Inc.
If product demand is high for HyperHelp on OpenVMS we
will consider distributing the HyperHelp binaries on
OpenVMS.
Next release: Wind/U for OpenVMS V3.1 (First half of calendar
year 1996)
Major enhancement:
OLE 2.0: The complete OLE implementation from Windows
NT 3.51, including for example in-place activation,
structured storage and in-process and local process servers.
Threads APIs Implemented
RPC APIs Implemented
Pricing and Distribution:
The Wind/U Bristol Development Toolkit and Runtime binaries will be
bundled with OpenVMS Version 7.0.
The licenses for the Bristol products will be sold separately and will not be
included in the OpenVMS operating system license.
Digital is bundling the Wind/U binaries with OpenVMS as a customer
convenience consideration. All OpenVMS customers who have Version 7.0
or greater will automatically receive the product binaries and will be able to
turn on the Wind/U for OpenVMS software by simply calling Bristol
Technology, Inc. at (203) 438-6969 for their Product Authorization Key
(PAK). Note that the Wind/U for OpenVMS V3.0 VAX and Alpha product
will run on OpenVMS Version 6.2 or later.
Frequently Asked Questions about Bristol's Win32
APIs on OpenVMS
1Q. What is Wind/U for OpenVMS and what will be implemented?
1A. Wind/U is an implementation of the Microsoft Windows APIs under
OpenVMS/Motif and is a developer's tool for porting applications to
OpenVMS.
Wind/U for OpenVMS V3.0:
Win32: implementation of the Microsoft Windows Win32 APIs
WinSock DDL: full support for Windows sockets which
provide networking capabilities to Windows applications.
Xprinter: software for adding sophisticated printing
capabilities to OpenVMS or UNIX based applications.
Microsoft Foundation Class (MFC) library V4.0
Windows 95 Common Controls: support for 12 controls that
are in Windows NT 3.51 and Windows 95 (examples: Tree
View, List View, Progress Bars, Tab Controls, Toolbars, and
so on.)
Supported APIs:
While the implementation of Win32 in Wind/U today is most
closely analogous to the Win32s implementation, the real
focus of the product is compatibility with Visual C++ and
MFC. Wind/U will port applications written with Visual C++
2.1 or greater and MFC 4.0 or greater. Wind/U for OpenVMS
will include support for the new Windows 95 controls as well
as additional APIs from Windows 95 and Windows NT 3.51.
Bristol Technology, Inc. has also ported HyperHelp to
OpenVMS. HyperHelp is industry standard software for
creating OpenVMS- and UNIX-based online help systems
with WinHelp functionality. HyperHelp is a complementary
product to the Wind/U development kit and will be sold
separately by Bristol Technology, Inc.
Wind/U for OpenVMS V3.1 (First half of calendar year 1996)
Major enhancements:
OLE 2.0: The complete OLE implementation from Windows
NT 3.51, including for example in-place activation,
structured storage and in-process and local process servers
Threads APIs Implemented
RPC APIs Implemented
Q2. When will Wind/U for OpenVMS be available?
A2. Field test will begin in October with OpenVMS Version 7.0, and we
expect first customer ship to be in December.
Q3. When will Digital internal users be able to begin field test?
A3. Internal field test will begin in October. Bristol Technology, Inc. has
agreed to provide field test customers with a field test kit via Internet ftp.
Q4. I have a customer who would like to be a field test site. How do I
sign him up?
A4. External field test will begin in October. Customers will be able to
register for field test via both the OpenVMS home page Flash! item and the
Bristol home page.
Q5. Will Wind/U for OpenVMS be available on VAX?
A5. Yes.
Q6. What version of OpenVMS will Wind/U require?
A6. Version 6.2 or greater.
Q7. How will OpenVMS customers get Wind/U for OpenVMS?
A7. The Wind/U for OpenVMS binaries will be bundled with OpenVMS
Version 7.0.
Q8. How will Wind/U for OpenVMS be licensed? Will the price be
included with OpenVMS?
A8. The Wind/U Bristol Development Toolkit and Runtime binaries will be
bundled with OpenVMS. The customer should contact Bristol Technology,
Inc. for a Product Authorization Key (PAK).
The price for Wind/U for OpenVMS will not be included in the operating
system price. Digital is bundling the Wind/U binaries with OpenVMS as a
customer convenience consideration. All OpenVMS customers who have
Version 7.0 or greater will automatically receive the product binaries and
will be able to turn on the Wind/U for OpenVMS software by simply calling
Bristol Technology, Inc. at (203) 438-6969 for their activation key.
Q9. How many licenses will a customer need and what are the prices?
A9. Developers need a Wind/U for OpenVMS Developer Kit for each
system they develop. Each workstation platform/operating system
combination requires its own specific version of the Wind/U Developer Kit.
Users need one license per concurrent user of the Wind/U for OpenVMS
Runtime. Therefore, if there are 10 simultaneous users on a network, then
10 licenses are required. If multiple servers are available on a networked
system, one license per user per server is required. This is similar to how we
license DECwindows Motif today.
Note: Bristol Technology, Inc. plans on implementing LMF.
DEVELOPER TOOLKIT
Digital Customer Fee:
Wind/U for OpenVMS Developer's Environment.....$9,950.00
Additional Development Seats..............$5,000.00
30-day Evaluation...........................$250.00
Digital Internal Developer Use Fee:
Wind/U for OpenVMS Developer's Environment.....$3,000.00
Runtime
Digital OpenVMS Customer Fee:
Wind/U for OpenVMS Runtime Fee.....................$65.00
Licensed Per Seat/Volume discounts available
Digital Internal Use Fee:
Wind/U for OpenVMS Runtime Fee..................$50.00
Note: Internal users will also purchase the Product Authorization Key
(PAK) from Bristol Technology, Inc.
Q10. Who will support the Wind/U for OpenVMS environment?
A10. Bristol Technology, Inc. will provide customer support for Digital's
Wind/U for OpenVMS customers and internal Digital customers.
Bristol Support and Upgrades includes 12 months of customer support and
free upgrades. The Support and Upgrade fee is 20% of the list price of
purchased development seats of Wind/U for OpenVMS.
Q11. What will be the "look and feel" on a workstation? Will it be like
SoftWindows?
A11. The "look and feel" will be Motif with all the functionality of
Windows. No, it will not be like SoftWindows, SoftWindows is strictly an
emulation product.
Q12. When applications run on OpenVMS or UNIX, will they adopt
the Motif visual characteristic?
A12. Yes.
Q13. What support is there for client/server development? For
example, can I build a Windows client and use OLE to share
information from OpenVMS or UNIX servers?
A13. The infrastructure to do this is in the Bristol product today; however,
the current OLE 2.0 implementation does not have the "glue logic" to locate
and launch objects over the network.
The next major revision of OLE from Microsoft (in Cairo) will deliver this
capability. After this functionality is available from Microsoft, Bristol will
incorporate it in Wind/U for OpenVMS.
Q14. Will we be able to take Windows applications out of the box and
run them on OpenVMS?
A14. No, Wind/U for OpenVMS is a developer tool, not an end-user tool.
Wind/U for OpenVMS is used by developers to port their applications to
OpenVMS, while SoftWindows is used by end users to run Windows
applications out of the box.
Q15. What kind of performance should I expect?
A15. A Wind/U for OpenVMS application will achieve native
OpenVMS/Motif performance.
Q16. Can I develop a Win32 application on OpenVMS? Can I use
Visual C++ or Visual Basic on OpenVMS?
A16. Yes, you can use the DEC C++ or DEC C compilers and the existing
OpenVMS editors, debugger, and linker to develop your Win32 applications
on OpenVMS.
No, unfortunately Visual C++ and Visual Basic are not supported today on
OpenVMS; however, you can use Visual C++, C++, and C on your PC
environment to develop a Win32 application that will run on OpenVMS.
For more information
For more information, contact:
Ann McQuaid
Phone: (603) 881-2907
Internet: [email protected]
Steve Zalewski
Phone: (603) 881-1458
Internet: [email protected]
Copyright and Trademark Information
� 1995 Digital Equipment Corporation. All rights reserved.
Digital believes the information in this publication is accurate as of its
publication date; such information is subject to change without notice.
Digital is not responsible for any inadvertent errors.
Digital conducts its business in a manner that conserves the environment
and protects the safety and health of its employees, customers, and the
community.
The following are trademarks of Digital Equipment Corporation:
DEC, DECwindows, Digital, OpenVMS, and the DIGITAL logo.
Wind/U is a registered trademark and HyperHelp and Xprinter are
trademarks of Bristol Technology, Inc.
Microsoft, Visual Basic, Win32, Win32s, and Windows 95 are
registered trademarks and Visual C++, Windows, and Windows NT
are trademarks of Microsoft Corporation.
Motif is a registered Open Software Foundation, Inc.
SoftWindows is a trademark of Insignia Solutions.
UNIX is a registered trademark licensed exclusively by X/Open
Company Ltd.
All other trademarks and registered trademarks are the property of
their respective holders.
WINUVMSD.HTM
4 October 1995
OpenVMS Marketing
|