Posted by Rob Luke - CMS Training Design on January 19 at 21:42:18:
While the system modifications shown in the thread below on "Current issues with
Reporting to the MAX on WIN ME" will get the customer working to an extent in most cases,
a new issue has arisen.
File handles will be sufficient for the operation of the CMS DOS product line in nearly
all cases; the PerVMFiles= switch will add file handles to any process running inside a
virtual DOS machine (VDM).
The bad news for the Windows products is that Microsoft has admitted that there is an
artificial resource limit of 120 open files for any process using "Win 16" code
(CMS windows products). The PerVMFiles= switch does not help here, because Win 16 code
does not run inside a VDM.
This problem was encountered by Cougar Quality Assurance during testing for version 5.1a
when posting in Order Entry, it was dealt with by closing some of the open database files
before continuing with the next part of the posting process.
Posting for a single user installation (or CMS client install) on a WIN ME Machine
should not encounter this problem in most, if not all cases. However, Cougar
BP's should
avoid using WIN ME machines as a peer to peer network server under any circumstances, as a
WIN ME machine will encounter this 120 file limit while acting as the CMS server during
the posting process when initiated from any one of the CMS client machines. Any non-CMS
resources on a WIN ME server that are in use by other clients will only cause the problem
even more frequently.
As I noted before, WIN ME is a home-market product, the integrity of the end-user's
data would be better protected with a Windows NT/2000 server. If a small peer to peer
network must be set up because of cost concerns, please use WIN 98 on the peer to peer
server and steer clear of this potential issue.
[http://cougarmtnsupport.com/This_page_covers_the_following.htm]
| 
