|
WINDOWS ME-MILLENIUM
for the Reporting to the MAX
Posted by Rob Luke - CMS Training and Design on November 30 at 00:03:18:
In Reply to: Running CMS v14G on MS Windows ME posted by Belnando A. Weekes on November 21
at 08:34:21:
There are several issues with the use of CMS products on the Windows ME operating system.
The first issue is that the
real-mode startup files, CONFIG.SYS and AUTOEXEC.BAT are still there but are not used by
WinME. Anything placed
into these files is ignored and the files are "reset" each time the machine is
booted. This presents two main problems for CMS:
1- how do I get enough file handles set to run Cougar?
and
2- how do I set an environment variable to use CMS for Windows over a peer to peer
network?
It is possible to make additional file handles available to CMS by adding the line:
PerVMFiles=225
into the [386 Enh] section of the SYSTEM.INI file located in the Windows folder. This adds
extra file handle entries to the
table which is allocated each time a new Virtual Machine is started (happens anytime CMS
is started.) A complete description
of the issue and why the number is 225 and not 250 or 255 is available in the Microsoft
white paper at this URL:
http://support.microsoft.com/support/kb/articles/Q269/0/30.asp
To allow the use of DOS-level environment variables, WinME has moved these functions
directly into the Windows Registry
files under a particular registry key entry. The easiest way to add a global environment
variable is to set it up in MSCONFIG,
which has been changed in WinME to allow modification of this registry information.
CMS Quality Assurance is currently testing our windows product line on the WinME
platform... we have not certified any of
our products at this time to run on the WinME operating system. This, coupled with the
fact that WinME is intended to be a
"Home Computing" product system and not a "Business Operating System"
leave us in a position where we cannot recommend
the use of CMS products with WinME at this time. We cannot recommend that the end-users of
the product edit the
SYSTEM.INI file, the Windows Registry and etc. There are also other unresolved issues with
an inability to locate some of the
needed shared components when running CMSWIN over a network that I theorize at this time
may be related to the fact that
we are mapping CMSWIN on a network using a 16-bit networking model.
A note specific to CMS DOS products under WinME is that Expanded Memory is not available
inside a DOS session... this
alone may render ACT for DOS unusable if the client has large data files.
Win ME is essentially a release of Windows 98SE with much of the real-mode (aka 16-bit)
functions either changed radically
or removed. More information on real-mode removal in WinME is available in the Microsoft
whitepaper at this URL:
http://support.microsoft.com/support/kb/articles/Q269/5/24.ASP
My advice for the time being is to install Win98SE or Windows 2000 Workstation and thereby
avoid these issues.
Rob Luke
Systems Trainer
Reporting to the MAX including Point of Sale and Non-profit Versions
[http://cougarmtnsupport.com/This_page_covers_the_following.htm]
| |
|
