Previous Topic "Windows 7 Installation Tips"
This section of the document covers issues reported by resellers. Topics range from slow performance over the network to screen settings to screen transparency issue.
It is known there are network performance issues with Window 7 and is well documented on the internet. This is especially the case with Windows 7 computers accessing shares on older MS Windows operating systems (i.e. XP, Vista, etc.). Accessing data and transferring data over a network with Windows 7 can result in noticeable delays.
It should be noted that slowness issues may be dependent on the files or programs being accessed. For example, when accessing a Word file, access may be limited to one file. However, in with Restaurant Manager, any DBF, DBT, NTX, SCR, DEF, MEM and BMP file could be accessed multiple times. Thus the constant checking adds-up. For DBF/DBT and NTX files, this could happen on a record by record basis - compounding the time spent "checking access privilege" even more.
The following sections are suggestions that may help with slowness issues with Windows 7.
Starting with Windows 2008 R2 , Vista, and Windows 7, Microsoft tightened up security for accessing files. Much of this usually is implemented in the "folder" being accessed (i.e. c:\rmwin) and these security, most likely, gets inherited to all files and sub-folders in the folder. These permissions and owner settings are stored as file/folder metadata and gets copied around.
Prior to the three operating Systems mentioned above, a cookie cutter approach by just copying to from staging machine to server usually does not pose a problem. Currently, however, this could pose a problem in the following possible scenarios:
Privileged user from the XP computer does not exist in the Windows 7 server
User security is encrypted in incompatible method as with the Windows 7 server
Files and sub-folder ownership has different user
When the above occurs, it is believed the operating system attempts to check every time the file is being queried, read, updated and deleted. Also, if the "folder" has been copied from one machine to another, potentially changing privileges and ownership in the process, the list of "previous" owners will be checked every time there is an access to stated files and folders.
If at all possible, using the installation executable, install the rmwin directory directly on the rmserver. This should be done during initial installation on the new computer.
Many resellers choose to begin programming Restaurant Manager on a staging computer to expedite the installation process. If you are "staging" a system a secondary computer, make sure you do the following:
On the new (target) rmserver, create an "rmwin" folder . This step will make sure that the "rmwin" folder is owned and maintained by the user on the server computer as well as the pre-installed users (i.e. administrator, system, authorized user, etc.)
Copy all the files and sub-folders from the source "rmwin" folder to the target rmserver "rmwin folder". Do not copy the "rmwin" folder itself.
Make sure only local users are in the permissions list, for example, if server is "rmserver", remove users that maybe listed as demoserver\administrator (right click on rmwin folder > Properties > Security > Advanced > Permissions tab)
Note: for steps 3 and 4 above, this should apply to all files and sub-folders
In addition to step 3, remove unknown users usually represented by some long alpha numeric string (probably a GUID).
Click on the Edit button
Select the correct user (i.e. posuser (rmserver\posuser)
Place a check mark in the "Replace owner on subcontainers and objects
Click "Apply
Click "OK" on the Windows security prompt.
Click on the "OK" button on the remaing screen to exit from the rmwin folder properties menus
If copied already to server, a possible solution might be:
rename rmwin folder to "rmwinold"
create new "rmwin" folder
copy all files and sub-folders to the new "rmwin" from "rmwinold"
If the steps in this section do not work, as additional measures, try using steps 3 to 5 in the staging section above.
Note: If staging a system on a Windows 7 machine, the slowness problem might still happen because the "user" seems to be tied to the MAC address of the machine and not just to "computername\username" combination.
Next Topic "Disable RDC ( Remote Differential Compression)"