| Title: | DECtp Desktop for ACMS |
| Moderator: | UCROW::GIBSON |
| Created: | Mon Sep 24 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 859 |
| Total number of notes: | 3034 |
I wonder if anybody can help me with a query that I received from one
of our SI partners in the UK. I have reproduced their question below.
They are stuck for the moment at old versions of software because of
particular applications and special requirements of this major
government site. They are doing their best to sort out a plan to move
to later versions.
regards and thanks for any help
David Gallagher
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
""As you know we currently run a windows 3.1 application which
interfaces with our VAX (VMS5.5) using ACMS (v3.3) running over DECnet.
We build the PC application using ACMS libraries that are downloaded
from the VAX.
We are currently looking at porting our windows 3.1 code onto a PC
running NT. To build the application, is it just a case of retrieving
the NT version of the ACMS libraries (contained in logical
ACMSDI$NT_I86) from the VAX and recompiling?
The area that we are unsure about is that the NT libraries may just
cater for 32 bit applications and so will not work with our 16 bit
application.""
Thanks for your help,
David Gallagher
UK SBU Pre-Sales
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 819.1 | WNT 16 bit application support | UCROW::KNEELAND | Tue Jan 28 1997 14:38 | 34 | |
.We are currently looking at porting our windows 3.1 code onto a PC
.running NT. To build the application, is it just a case of retrieving
.the NT version of the ACMS libraries (contained in logical
.ACMSDI$NT_I86) from the VAX and recompiling?
The ACMS Desktop V2.2 kit/libraries contain NT 3.51 DLLs, that are 1 byte
aligned, and should support 16 bit applications without any trouble.
?Does your client use ACMS Desktop V2.2?
?Do you mean VB3 or VB4(16 bit) as the 16 bit application environment?
?Do they use large workspaces?
?Do they intend to use NT 4.0 or NT 3.51?
We have an NT client ECO for V2.2 that enables the use of large (>30K)
workspaces. This ECO contains 4 byte aligned DLLs for NT 3.51 and
caters to the 32bit VB4 implementation which requires 4 byte alignment.
16 bit applications should still work using the 4 byte DLLs/V2.2 ECO,
however ONLY *optimized* workspace users with 1 byte aligned applications
(16 bit) ran into trouble trying to use the 4 byte aligned DLL due to
the ACMSDI_WORKSPACE_OPT struct definition in the ACMSDI include file.
There's a workaround (pending ECO) that uses #pragma wrapper around
the ACMSDI_WORKSPACE_OPT structure definition to enable 1 byte aligned
applications to be built against the 4 byte aligned DLLs.
We plan to incorporate the ECOs into the V2.3 release scheduled for SSB
in April/May. Note 799 references some of the other features planned for
V2.3 as well. We have done some testing on NT 4.0, however with the
already restricted V2.3 time schedules, we may not be able to officially
support NT 4.0.
Colette
| |||||
| 819.2 | Thanks very much | CHEFS::CHEFS::GALLAGHER_D | Wed Jan 29 1997 03:57 | 1 | |