Issues with OEM & Appliance Editions of Windows – Updated

When non-standard versions of Windows are used you may be affected by OEM and Appliance(embedded end-user application specific) versions when trying to install and use Reality.

This is typically end-user Windows versions, like Home or “light” versions that have OEM deliveries not designed to load significant products like databases.

For Reality evaluation and personal use sometimes these can be worked around…
… for example trying to use mkdbase to make a database in the Windows root folder, typically “c:”, may have local or roaming profile access protection or some kind of OEM controlled access; so just trying a user level folder can recover this.

Or you may need to use Windows settings like “Turn Windows features on or off” to access networking features, for example, being able to telnet into a database.

However, some of the installation, database and networking may not be recoverable on a non-standard  Windows build.

For example:

• Reality Services may be prevented from running, generating error messages in log files and event logs, or causing hangs.
   
• During installation or when users first try and log in to databases you may see error messages like…
  … GetFreeSpaceCString — Bad call to GetDiskFreeSpaceEX Access is denied.
   
• Access to “run as Administrator” may not be available for use by Reality…
  … e.g. when running low level commands like realserv, netadmin, mkdbase.

Typically, the only recovery is to reload the Windows System with a standard version of Windows, refer to supported platforms in the Installation Guides.

Also refer to FAQ, V14.0 doesn't seem to load on Windows 7 or Server 2008 and Installation, Demo & Getting Started pages.

Back to articles