New Zealand Gazette – 2004 – No. 79

Page 1982

✨ Gaming Machine Software Requirements



1982

NEW ZEALAND GAZETTE, No. 79

29 JUNE 2004

1.46.11 If a non-IBM DOS compatible computer is supplied or dial-up access to an operating environment is granted for software compilation, a CRC check must be implemented on both the manufacturer’s operating system and the evaluation laboratory systems so that the laboratory may ensure the integrity of the source code. This CRC program, for both operating systems is to be provided by the manufacturer. Source code of the CRC program, and instructions for generating an executable file from the source must also be provided. The CRC must be initiated with a random seed value (to be manually input by officers of the evaluation laboratory).

1.46.12 Supply detailed, step-by-step information on how to generate EPROM files and EPROMs from the source code provided.

Program Storage Image File

1.46.13 The manufacturer shall provide the designated testing body with detailed written instructions on how to create a Program Image File from their certified gaming machine software memory storage devices.

Miscellaneous Functions

1.46.14 Indicate how test mode is entered.

1.46.15 Describe all tests provided by the game for testing specific functions and/or event sequences.

1.46.16 Detail if there is maximum number of credits that the machine can hold before an attendant pay is required.

1.46.17 State the procedures that must be undertaken to clear the RAM.

Fault Conditions

1.46.18 For each fault condition (including those specified for communications) provide the following details:

a) the condition name and how it is displayed;

b) type of machine alarm (e.g. bell, message on screen, tower light);

c) how software "defines" the alarm;

d) whether or not the machine locks up on the alarm temporarily or indefinitely;

e) how the machine is reset from alarm conditions; and

f) the event code transmitted to the monitoring system (where applicable).

1.46.19 For each condition indicated by the tower light describe:

a) condition name;

b) how the condition is indicated (i.e. which colours are utilised); and

c) whether the light flashes or not.

Random Number Generator

1.46.20 Provide full details in technical terms of random number and symbol selection/mapping.

1.46.21 List all text and journal references where applicable used in the design of the RNG. Provision of this information may assist in reducing testing costs and the evaluation time.

1.46.22 List all points in game play and the gaming program operation where the RNG is activated, updated, or numbers are obtained, including details of background RNG activity.

1.46.23 Explain the seeding process of the RNG.

1.46.24 Provide a detailed flow chart and software listing of the RNG process.

1.46.25 Provide results for any empirical and/or theoretical tests conducted on the RNG.

System Security/Integrity

1.46.26 Describe the use and function of all DIP switch settings, jumpers, wire wrap selectable options or other external mechanisms by which the functioning of the device, or game may be affected, and state the settings for normal game operation.



Next Page →



Online Sources for this page:

VUW Te Waharoa — PDF NZ Gazette 2004, No 79


Gazette.govt.nz — PDF NZ Gazette 2004, No 79




✨ LLM interpretation of page content

🏭 Full Software Submission Requirements (continued from previous page)

🏭 Trade, Customs & Industry
Software Submission, Gaming Machine, Source Code, Software Compilation, Development Environment, Software Tools, Dial-up Facilities, IBM DOS Compatible, Flow Charts, Program Block Diagrams, CRC Check, EPROM Files, Program Image File, Test Mode, Fault Conditions, Random Number Generator, System Security