✨ Gaming Machine Software Standards
27 MAY NEW ZEALAND GAZETTE 1473
3.2.28
The method of loading programs to the storage media (e.g. disk file transfer or down line load) must be approved.
3.2.29
Superseded approved versions of programs may be held on the storage media. However, it must be possible to clearly identify which files belong to which version of the program.
3.2.30
The method of changing to different versions of the program, including reverting to older versions must be approved.
Flash Memory Devices
Security Controls
3.2.31
If in-circuit writing of flash memory is available the use of flash memory devices presents additional security risks to some other forms of firmware and therefore this technology will only be accepted if there are adequate controls to prevent unauthorised reading, erasure or copying of flash memory devices.
Physical Protection against Modification
3.2.32
A flash memory device must be protected from unauthorised modification which is to be permitted only once appropriate security measures are satisfied (e.g. a high voltage chip that allows modification of the flash memory devices is installed on the PCB).
3.2.33
The use of jumpers or similar devices can be used to enable/disable erasure/writing to flash memory provided there is a feedback signal to the software so that the setting of the jumper position can be recorded or appropriately acted upon. These jumpers must be located within the logic area of the machine.
3.2.34
Any change to the contents of the Flash Memory Device through erasure, writing to the contents, and so on, should result in a hardware signal feeding back to the gaming machine software.
3.2.35
Any unauthorised access to the contents of a Flash Memory Device through erasure, writing to the contents, and so on, should trigger an event that must be stored in NVRAM in the same way that a “door open” event is. Clearance of the event should not be possible other than under the control of the gaming machine hardware and software.
3.2.36
If a Flash Memory Device is irreversibly configured at the hardware level as a read only device (for example, the write line is cut off), it is to be treated for all purposes as an EPROM.
Downloading Programs to Flash Memory Devices
3.2.37
The method of loading programs to the flash memory device (e.g. Down-line load from CMCS) must be approved.
3.2.38
Only the actual program and fixed data required are to be written to the flash memory device.
Program Verification
3.2.39
During the programming operation on flash memory, each byte programmed should be verified by a program comparison controlled by the programming device.
3.3
Metering
Soft Meter Update
3.3.1
A meter must be updated on the occurrence of the event. All meters must be added to, not incremented with the exception of coin handling meters (i.e. coin in and out meters) which may be either added to or incremented. The term “added to” indicates the fetching of the current value from memory, conducting an arithmetic add operation and storage in memory.
Credit Meter
3.3.2
Next Page →
Online Sources for this page:
VUW Te Waharoa —
NZ Gazette 2003, No 56
Gazette.govt.nz —
NZ Gazette 2003, No 56
✨ LLM interpretation of page content
🏛️
Software Standard for Gaming Machines
(continued from previous page)
🏛️ Governance & Central AdministrationGaming Machine, Software Requirements, Memory, Critical Data, Audit Meters, Validity Check, Memory Corruption, Data Partitioning, Program Execution, Flash Memory, Security Controls, Physical Protection, Metering