To realize the full capabilites of GroupWise 5.5 including MAPI support, the installation procedure insists on installing the "complete Windows Messaging System". While this is has presented no problems when installing GW on our desktop PCs within our Novell network, we are hesistant to do this blindly on our Winframe server without knowing exactly what comprises the "messaging system" and what impact, if any, the installation will have on other applications running on Winframe. As a result we have configured Winframe user profiles to run the GroupWise 5.2 16bit client from their respective default Novell server. Although this allows remote access users to read/send email, schedules, tasks, etc it is less than satisfactory.<br>
<br>
I have developed an application to be deployed on the Winframe server which requires 32bit MAPI to send email via GroupWise 5.5. The program is worthless until GW 5.5 is installed. <br>
<br>
Exactly what is the "Windows messaging system"? I would assume that it is comprised of a group of *.DLL files installed in the \system directory. True? If so where will these files be installed on the Winframe server? Will they be installed in the global \Winframe\System directory or into my personal profile's \users\MyName\windows\system directory? <br>
<br>
Greg Pencheff<br>
Data Processing<br>
County of Lancaster, PA <br>
<br>
<br>
I have developed an application to be deployed on the Winframe server which requires 32bit MAPI to send email via GroupWise 5.5. The program is worthless until GW 5.5 is installed. <br>
<br>
Exactly what is the "Windows messaging system"? I would assume that it is comprised of a group of *.DLL files installed in the \system directory. True? If so where will these files be installed on the Winframe server? Will they be installed in the global \Winframe\System directory or into my personal profile's \users\MyName\windows\system directory? <br>
<br>
Greg Pencheff<br>
Data Processing<br>
County of Lancaster, PA <br>
<br>