247SimManager Suite

A friendlier thank-you, with a focused upgrade option

Completed October 1: the Thank You for Playing message now supports Markdown and all six booking/location tokens in both its title and message. Friendly golf-themed defaults ship with a deployment option that replaces only those two saved text values. Deployment Manager now uses the 247SimManager Suite logo and Windows icon. The full Debug 1.46.18 installer passed all 971 tests and independent package verification, and its Google Drive delivery is confirmed.

• Formatted, personal thanks: use headings, bold text, callouts, lists and paragraph breaks in the message. Both fields support all six general tokens, using the ending session rather than the next customer. See the new defaults and customer preview.
• Refresh deployed copy in one selection: leave full settings overwrite cleared and select Replace only Thank You for Playing title and message during AccessControl Install / Upgrade or Repair. The option defaults off and backs up the existing settings during the value-preserving update. Follow the upgrade steps.
• Recognizable installer: Deployment Manager now carries the full Suite logo, its Windows application icon, and matching window titles. Both brand assets are embedded for offline use. See the approved appearance.
• Verified current handoff: Debug 1.46.18 contains 988 manifest-controlled files across 989 ZIP entries. All hashes and versions passed; the final packaged logo and icon match the approved assets. Download the verified installer.
• Finish with confidence: after final Done or booking-end timeout, the kiosk locks before showing the closing message. Close or the message timeout returns to the locked kiosk. See the customer screen, Settings, and end-to-end flow.
• Location-owned copy: edit the plain-text title and Markdown message, preview unsaved wording, then Save. Both fields resolve tokens from the ending booking context. The default TPS inactivity wording reflects the pilot's reported behavior; AccessControl does not request or verify a TrackMan sign-out.
• Energy-saving work is deferred: the September 25 monitor-power research has not been approved for implementation. Windows sleep, monitor control, and GPU power changes are not implemented by this work. Existing booking-aware PJLink behavior continues. Read the deferred research scope.
• Two clear identities: Suite branding identifies the software; the facility logo identifies the location. Leave Kiosk Branding Icon blank for the default 24/7 Golf logo, or select a custom facility image. See the kiosk and Settings previews.
• Manual incident reports: choose a customer reboot, export eight hours of prior Windows events and the after-window through service startup plus four hours, and include broad retained TrackMan/support evidence. Partial windows and unavailable sources are labelled; no report runs during customer restart or service startup.
• Clearer safe actions: the requested Keep Playing, Continue, I ACCEPT, Close and no-buffer Done buttons are green. Help places the red Reboot Simulator button at the top right and green Close at the bottom right. See the six updated dialog previews.
• TrackMan monitoring is configurable: Monitor TrackMan related log files defaults on, with Scan Frequency set to 5 minutes. Choose a whole number from 1 to 1,440 in Deployment Manager or Admin Settings → WinSysMaint. Restart WinSysMaint after saving changes. Review the settings, screenshots, and event meanings.
• Useful signals without replaying old incidents: recognized application failures, memory or disk warnings, persistent device problems, content errors, recoveries, and startup/close markers become events 1120–1127. The first scan starts at the ends of existing logs; later scans resume saved positions.
• Bounded background work: scans never overlap, read at most 8 MiB of log data per scan, and retain bounded checkpoints. Unchanged-log component checks took about 6 ms on Simulator #1; this is a short idle measurement, not a live-play performance guarantee.
• Browser teardown repaired: Make A Booking, Extend My Time, and Feedback now release their embedded browsers before window destruction, with guarded repeated cleanup. Forty-five native browser cycles closed their browser processes; a persistent native-handle increase remains under investigation.
• Administrator booking diagnostics: Make A Booking shows the current requested and navigated URL in Admin Mode, including redirects and fragment changes. Customer sessions do not show this diagnostic row.
• Deployment files stay available: overlapping launches of the same package cannot replace its extracted files while Deployment Manager is open. Settings review creates a support report before installation and offers Copy diagnostics with selectable errors.
• Customer reboot is an owner choice: enable Windows Auto Start in General, then select Show Reboot Simulator button under Kiosk → Customer Help. The checkbox defaults off and becomes unchecked and disabled when auto start is unavailable; its help icon explains the prerequisite.
• Reason before recovery: Reboot Simulator opens a native reason-and-comments dialog. A valid reason and explicit confirmation are required; Other also requires comments. Cancel, Escape, closing, or timeout cancels the restart. Normal Feedback and Customer Shutdown retain their web form.
• The established full-PC restart: AccessControl rechecks auto start and asks WinSysMaint to run the same settings, application-close, and Windows restart sequence used by scheduled maintenance. It works independently of the saved schedule and does not change that schedule. Update both components together.
• Customer restart evidence: WinSysMaint events 1020 and 1025 retain the submitted reason and comments. Event 1025 marks the customer restart-command boundary; Windows boot and service-start records establish the subsequent timeline. Debug → Customer Reboots lists genuine events for 30 days and exports reports only when an administrator requests one.
• Specific retention defects corrected: replaced immutable Debug rows can now be collected, process monitoring retains only the newest 2,000 observations, and a slow CourtReserve response cannot accumulate periodic refresh requests. Window timers, browser initialization, process wrappers, and settings operations now have tighter cleanup.
• Clear review limits: automated tests verified specific managed-object and cleanup fixes. The September 17 review also found remaining native-browser handle growth. No CPU/memory trace was captured during the reported blank screens; a coordinated live-play capture is still needed.
• Clear booking-end choices: Done remains enabled and locks the kiosk. Keep Playing appears only when eligible time remains; a timed-out notification locks the kiosk. Notification teardown now protects the main application lifetime and records lifecycle diagnostics for support.
• Five-minute AccessControl watchdog: enabled by default and independent of nightly maintenance. Recovery starts AccessControl as the registered interactive kiosk user; the new kiosk begins locked and requires a booking code again.
• Intentional exits stay closed: an authenticated administrator close or the final accepted Customer Shutdown exit persists a stop instruction. Merely entering Admin Mode or accepting a warning does not disable recovery. Manually starting AccessControl re-arms monitoring.
• Two pre-end messages: owners edit separate messages for bookings that qualify for buffer time and bookings that do not. Selection uses the fresh, complete buffer decision; extension permission remains independent.
• Shared minutes token: [SETTING-MINUTES-BEFORE-BOOKING-END] expands to values such as 10 minutes across supported token surfaces, including Time Extended. It represents the live setting, not a running countdown.
• Two maintenance choices: Settings enforcement only and Restart System. TPS QR reset settings, scheduling, warnings, commands, readiness signaling, state, and events have been removed.
• Practical remote monitoring: the TeamViewer reference explains Application-log checks for both AccessControl and WinSysMaint across Error, Warning, and Information. The safe sample writer now covers 55 named events without performing their underlying actions; remote alert delivery still needs onsite verification.
• No extra customer action: each timed notification waits for a fresh booking check, applies current booking rules, and appears only if it is still due. The interface remains responsive while CourtReserve is queried.
• New paid time is recognized: an amended booking or qualifying same-customer chain resets the remaining time and notification schedule. An obsolete notification closes automatically.
• Buffer permission is rechecked: another booking at or below Booking Gap after the final paid end removes courtesy time. Larger gaps still cap any eligible buffer at the next booking start.
• Safe verification: failed, stale, missing, unpaid, reassigned, or conflicting booking data cannot grant extra time. Existing paid time remains the enforcement boundary when verification fails.
• Restrictions follow the booked product: every Booking Buffers reservation-type row can expand into its own Restricted Applications table. A restriction on one type does not affect another type.
• Owner-authored customer guidance: each selected EXE has its own warning title and Message action. The two-panel editor keeps Markdown source on the left and a live formatted preview on the right before Save.
• Five-second detection with fail-closed recovery: AccessControl checks the active reservation type in nonoverlapping background work, covers the complete kiosk monitor, and presents the configured warning. After the customer selects I UNDERSTAND, it requests every matching process to close, force-terminates any instance still running after five seconds, verifies exit, waits two seconds, and restores the configured Startup applications in their saved order.
• Recovery stays visible until the simulator is ready: the full-screen Returning to Home Screen shield cannot be dismissed. If process closure or application restoration fails, AccessControl logs the problem and retries the complete recovery every five seconds instead of returning a customer to a partially restored simulator.
• Simple EXE selection: administrators may browse to multiple different EXE paths even when Windows reports the same process name. The same normalized full path cannot be saved twice, and each shared process name is checked only once.
• Cumulative Debug discovery: Monitor Running Applications samples every five seconds and retains the newest 2,000 observations, including closed processes until they age out. Reopening with a new PID creates a new retained observation; repeated sightings of the same process instance do not create duplicate rows.
• Interactive-app filter: Show Only Interactive limits the visible Debug history and subsequent monitor samples to processes with a main window. Turning the filter off restores previously retained rows instead of deleting evidence.
• Policy follows the reservation type: each Location Code-matched CourtReserve type has its own Enable Buffer, Allow Extending, Min Duration, and Buffer Minutes values. New types begin safely with both optional privileges disabled.
• Simple catalog maintenance: Refresh Reservation Types adds new matching types, removes types no longer returned by CourtReserve, refreshes API-owned names and colors, and preserves owner-entered policy for surviving type IDs.
• Fast booking-list display: AccessControl renders every booking first, then reviews enabled customer indicators sequentially in the background and applies each result as it completes. Cancellation and refresh-generation guards prevent an older schedule review from changing a newer list.
• Continuous sessions are evaluated correctly: back-to-back or qualifying linked bookings for the same verified member use their combined paid duration and final booking boundary. Two linked 30-minute bookings therefore satisfy an inclusive 60-minute reservation-type minimum.
• Optional customer guidance: Show Extend / Allow Indicators On Bookings is off by default. When enabled, lower-right clock-plus and hourglass glyphs explain extension and buffer availability on hover; unavailable states use the same glyphs with a high-contrast red circle/slash.
• No hidden performance cost when indicators are off: disabling the presentation setting hides both glyphs and skips indicator-specific continuity, duration, gap, and handoff analysis while leaving actual Extend My Time and post-booking enforcement active.
• Reservation type at a glance: every booking card carries a thin right-edge marker using the reservation type color supplied by CourtReserve, independent of the optional policy indicators.
• Deployment begins with the right catalog: Deployment Manager requires a Location Code, retrieves matching reservation types before AccessControl Install or Repair, and provisions safe-disabled rows. Value-preserving updates retain owner choices for surviving IDs.
• Readable administrator controls: Booking Buffers now uses the same dark table language as Startup Applications, with white text, large keyboard-focusable ON/OFF toggles, clear numeric inputs, and no row-delete action.
• One download and one launch: location administrators download a single EXE from the configuration-specific Google Drive folder. The launcher validates its embedded archive, extracts a versioned local copy, checks every packaged file, records a support log, requests Windows administrator approval, and opens Deployment Manager automatically.
• A fixed kiosk-ready taskbar: Search is hidden; no applications are pinned; Task View, Widgets, and Resume are off; the hidden-icon menu is on; alignment is centered; auto-hide is selected; taskbar buttons always combine without labels; and smaller buttons are always used.
• One owner-controlled taskbar switch: Configure the required Windows taskbar settings is enabled by default. It is available in AccessControl Admin Settings and Deployment Manager, and it controls the complete ten-setting baseline without exposing ten separate configuration choices.
• Four clear Windows security choices: Deployment Manager and AccessControl Admin Settings expose default-enabled controls to turn off all firewall profiles, turn off the supported App & browser control protections, and maintain Microsoft Defender exclusions, plus an independent default-off choice for Smart App Control. Clearing a choice leaves that Windows policy area unchanged while retaining its saved configuration.
• Existing installations remain authoritative: when Deployment Manager finds a valid installed C:\ProgramData\WinSysMaint\service.json, it preloads the computer's current firewall, App & browser control, Smart App Control, Defender-exclusion switch, and exclusion-path choices. A new computer instead starts with the approved 24/7 Golf defaults, which the administrator can review and edit before deployment.
• Five trusted antivirus folders by default: Defender maintenance now includes C:\ProgramData\Trackman, C:\Program Files\TrackMan Performance Studio, C:\Program Files\247Golf, C:\Program Files\247Golf\SimManager, and C:\Program Files\247Golf\SimManager\AccessControl. Defender itself remains enabled.
• Defined App & browser scope: the shared policy turns off Windows and Microsoft Edge SmartScreen, App Install Control, potentially unwanted application blocking, Microsoft Store app web-content evaluation, and Enhanced Phishing Protection. Smart App Control has its own switch because turning it off can require a Windows reset or reinstallation before Windows permits it to be enabled again.
• Smart App Control is explicit and fail-visible: on Windows 11 version 22H2 or newer, selecting the default-off choice sets Smart App Control to Off and refreshes Code Integrity policy. Unsupported Windows versions, a missing refresh tool, or an apply/read-back failure produce a yellow nonblocking warning and do not cancel the remaining deployment or maintenance work.
• All individual setting problems remain nonblocking: a permission problem, unloaded user profile, unsupported driver or Windows value, or failed read-back is shown as a warning and written to the local and Windows Application logs when appropriate. Remaining settings and the selected Install, Repair, Verify, or maintenance action continue.
• Full-build requests now include the location-admin package: full Debug, full Release, and ALL workflows rebuild the complete solution, run every test, create and independently verify the one-click EXE, and identify the matching 247SimManager\Debug or 247SimManager\Release Drive destination.
• One configuration engine from deployment through nightly maintenance: Deployment Manager Install and Repair call the same WinSysMaint enforcer and validator used by AccessControl administrator actions and scheduled maintenance. Verify is read-only, so the owner sees the same requirements and results at every stage.
• Automatic Windows Updates are disabled: the managed baseline prevents unattended update installation, preview builds, optional or early feature rollouts, and the Get the latest updates as soon as they're available opt-in.
• Other Microsoft product updates are disabled: SimManager writes both policy and Windows Settings values to off and unregisters the Microsoft Update service so the separate product-update opt-in cannot remain active from the PC's earlier use.
• File Explorer is ready for onsite support: hidden items and file extensions are visible, full paths and drive letters are shown, compressed/encrypted files use color, and empty-drive hiding, merge-conflict hiding, and the Sharing Wizard are turned off for loaded real-user profiles.
• New-PC review is required and complete: when WinSysMaint is being installed on a new computer, the operator reviews every service setting before deployment. Missing GPU executables and unsupported adapter properties remain visible for correction, but they no longer prevent the applications and all other supported settings from being deployed.
• One unsupported setting cannot stop commissioning: each system-policy area has its own safety boundary. WinSysMaint writes the condition to the Windows Application log, continues with the remaining settings, and still proceeds to the selected maintenance action. Deployment Activity shows the same nonblocking warning to the installer.
• Full configuration is the safe default: complete Windows configuration is selected by default for a new deployment. Installing application binaries without applying the computer baseline remains an explicit operator choice.
• TrackMan-specific support: TrackMan Performance Studio remains a configurable Startup application, with editable Defender and GPU defaults and optional diagnostic-log monitoring. TrackMan QR reset workarounds have been removed; ordinary startup, customer booking QR images, and restricted-application recovery remain available.
• Duplicate-safe application lists: Startup Applications and High Performance GPU Applications reject repeated executable paths, including paths that differ only by letter case or contain equivalent . or .. segments. Existing duplicate JSON is repaired deterministically by retaining the first row and its order.
• Clear support boundary: SimManager owns Windows kiosk access, ordered application startup, maintenance, and the selected device adapter properties; simulator firmware, calibration, telemetry, and vendor application preferences remain with the selected vendor.
• Settings-first maintenance tests: the Admin Settings Test Maintenance button saves and reloads the current service configuration, clearly identifies the selected action, requests Windows approval, and records the result without depending on the nightly schedule.
• Service health is fail-visible: every locked-kiosk presentation checks WinSysMaint. If the service is stopped, AccessControl logs the condition, requests a start with narrowly scoped rights, waits for recovery, and records success or failure.
• Updates preserve owner choices: AccessControl and WinSysMaint normalize missing, invalid, and retired settings property by property. Deployment Manager presents a guided side-by-side review before a value-preserving update is approved.
• One managed workstation policy: Deployment Manager, manual owner validation, manual Apply, and nightly WinSysMaint maintenance use the same required end state for Windows time, firewall, App & browser control, Smart App Control, Defender, GPU, taskbar, Windows Update, File Explorer, and the dedicated simulator device adapter.
• Physical adapter selection: the installer lists physical wired adapters without Wi-Fi, packet filters, WAN miniports, Bluetooth, kernel-debug, VPN, or virtual interfaces; it recommends the single connected wired adapter with no default gateway when that choice is unambiguous.
• Simulator device link stability: Auto Disable Gigabit, Energy-Efficient Ethernet, and Power Saving Mode are Disabled; Speed & Duplex is fixed at 1.0 Gbps Full Duplex. The stable interface GUID is stored internally while owners and support see the Windows connection name and hardware model.
• Manual proof before troubleshooting: AccessControl Admin Settings can validate every managed value without changing Windows, highlight mismatches with current and required values, or apply the same enforcement pipeline used by nightly maintenance and validate again.
• Main-screen selections remain authoritative: the deployment settings review now shows Simulator, CourtReserve, path, and simulator device adapter values already selected on the main screen instead of asking an administrator to type package defaults or a network GUID.
• Licensed CourtReserve startup: AccessControl calls the authenticated locations endpoint before it creates the kiosk, starts simulator software, or controls the projector. Demo Mode cannot bypass the check.
• Location proof in Settings: General Settings shows the licensed CourtReserve ID and Name returned during startup and includes a safe mock preview of the always-on-top unlicensed notification.
• Actionable licensing failures: API or verification failures write Application Error event 24702 and exit; an unlicensed response writes event 24703 with the returned ID and Name, shows support instructions, and then exits.
• Current Debug handoff: the complete version 1.46.18 source, settings schemas, and deployable one-click Debug EXE passed all 971 automated tests. Independent verification matched all 988 manifest-controlled files across 989 internal ZIP entries, confirmed every first-party executable reports 1.46.18.0, preserved blank reusable credentials and adapter identity, retained the bundled WebView2 installer's valid Microsoft signature, and verified the 394,211,328-byte outer package with SHA-256 AD39BE884EE6135E62DCD98C9C6D41A1078E18A64CAE39B120F1F75A6BA24A64.
• Early Access readiness: a paid booking requests projector power at its Early Access boundary, even when no CourtReserve refresh occurs at that exact moment.
• Unlock safety: valid customer and Admin Code unlocks request power immediately without waiting for projector warmup or allowing a PJLink failure to change access.
• Owner-controlled idle threshold: Booking Gap To Turn Projector Off defaults to 30 minutes and measures to the next Early Access window rather than the later scheduled start.
• Authoritative shutdown only: no bookings or a qualifying gap may request standby only after a successful booking refresh; a failed refresh can never interpret missing data as permission to shut down.
• Help power recovery: when PJLink is enabled, customers can select Turn On Projector at the top of Help.
• Transition protection: warming and cooling complete before an opposite command, while the newest power request supersedes older intent.
• Payment required before access: when CourtReserve reports a positive PriceToPay, AccessControl requires PaidAmount to meet or exceed that price before the booking can unlock the kiosk.
• Null-safe payment handling: a missing PaidAmount is treated as 0, so an unpaid reservation fails closed instead of being accepted accidentally.
• Clear customer and owner visibility: underpaid rows stay in the bookings list with red treatment, an Invalid Booking pill, and Amount Pending calculated as PriceToPay minus PaidAmount.
• Free bookings remain valid: when PriceToPay is 0, the reservation is valid regardless of PaidAmount, supporting no-fee reservations and administrator price overrides.
• Chains reject invalid segments: invalid reservations cannot start or continue a continuity chain, cannot validate a PIN, and cannot qualify as newly purchased extension time.
• Schedule gaps stay honest: an invalid reservation still occupies its complete scheduled interval in every before/between-booking gap calculation, so the kiosk never advertises its reserved time as open.
• Portable invalid-booking demos: the five-column Demo CSV now accepts UnpaidAmount; any positive value produces the same visible invalid state and amount-due behavior without touching CourtReserve.
• One reliable current source version: version 1.46.18 is defined once for the solution, used by ordinary Debug builds and settings schemas, and reported by every first-party executable.
• Protected customer shutdown confirmation: the Kiosk tab has a dedicated Customer Shutdown card for the enable option, four-digit code, warning title, Markdown warning message, and a safe Preview Dialog action.
• Friendly default warning: the built-in Markdown explains that the code is for simulator-unlock problems, that accepted shutdowns are logged, and that customers may be billed for overtime or use of an unbooked simulator.
• Explicit acceptance before logging: entering the shutdown code opens the warning but does not write the production event. Only I ACCEPT writes event 24701, opens customer feedback, and continues to application close.
• Safe cancellation and timeout: Cancel, Escape, and the shared kiosk-dialog timeout return to the locked kiosk without logging the shutdown event or closing AccessControl.
• Monitoring sample kept current: Write Event Log Samples includes the new customer-accepted warning message while remaining a labeled no-impact test that performs no shutdown.
• Request URL beside JSON: every admin-only CourtReserve Debug entry shows the exact request URL and returned JSON response together while keeping the Authorization header hidden.
• Installed version at a glance: the locked kiosk shows only the application version in the bottom-left corner so owners and support can confirm which build is running.
• Complete 24/7 reservation coverage: CourtReserve report boundaries are sent as simulator-local clock values, preventing timezone conversion from excluding bookings that start before 8:00 a.m. at an always-open location.
• Midnight and overnight support: AccessControl retrieves the previous day through tomorrow, keeps an overnight reservation available after the calendar changes, recognizes bookings that start exactly at midnight, and supports an exact midnight handoff between back-to-back bookings.
• Customer list stays current: the wider retrieval window protects cross-midnight sessions while completed reservations are still removed from the locked-screen booking list.
• Help throughout the session: new deployments keep a compact Help control visible before the normal session countdown appears. Owners may clear Always Show Help Indicator, and the Help action still remains beside the countdown whenever the timer itself is visible.
• Practical simulator-use tips: the default Help guide now explains approved white or yellow golf balls, the no-marker rule that protects the impact screen, blue painter's tape for reflective clubheads, and prompt putting setup when shots do not register.
• Settings compatibility on startup: when a valid installed settings file does not contain a setting introduced by a newer AccessControl version, the app adds it with the current default when it opens. Explicitly saved owner values remain authoritative.
• Complete new-install identity: Deployment Manager now requires both Simulator Name and Location Name, preloads them during an update, and writes both values into the installed AccessControl configuration.
• One scheduling value, two customer flows: an operator can paste one CourtReserve scheduler widget during deployment and apply it to both Make A Booking and Extend My Time.
• CourtReserve ready on first launch: API Key ID and the masked API Secret can be supplied during deployment; the secret follows a one-time, kiosk-account-only encrypted handoff and is never written as plain text.
• Approved application defaults: new installations use the supplied AccessControl profile, with a generic Location Name placeholder, working scheduler defaults, and blank API credential defaults.
• Approved service defaults: the canonical WinSysMaint service.json is packaged and installed with the same defaults owners see in AccessControl Settings.
• Reset without losing site identity: Reset to Default restores the new-deployment profile while always preserving Simulator Name, Location Name, and the CourtReserve API URL.
• Explicit reset choices: owners may separately clear both scheduler widgets, clear the API Key ID and Secret, and restore WinSysMaint defaults; the corrected dialog height keeps Cancel and Reset Now fully visible.
• Complete token reference: the six general dynamic tokens cover booking owner, booking start, booking end, Simulator Name, Location Name, and the configured pre-end lead time; the Help-only [POST-BOOKING-GRACE] placeholder is documented separately with its supported scope.
• Safe update control: an existing simulator retains custom values through the normal upgrade review. Full configuration overwrite and the focused Thank You title/message replacement are separate, explicit choices.
• Exact Early Access transition: a presentation-only timer changes the next booking from Early Access to Active at its scheduled start without requesting or rescheduling a booking refresh.
• Inclusive booking rules: Make A Booking appears when an opening is equal to or longer than its threshold; Extend My Time requires both an equal-or-longer remaining opening and an equal-or-longer paid booking duration.
• Verified booking continuity: chronological bookings on the same court are joined only when their positive CourtReserve OrganizationMemberId values match and the transition gap is equal to or less than the shared continuity threshold.
• Clear continuity display: linked booking cards show that they are treated as one session, remain unlocked through the transition, suppress Make A Booking inside the chain, and support chains of two or more reservations.
• Zero-minute support: a continuity threshold of 0 joins exact back-to-back reservations for the same verified member without joining a positive opening.
• Paid-time duration accounting: Extend My Time adds confirmed booking minutes in the continuity chain but excludes any unbooked transition gap from duration eligibility.
• Member identity instead of names: extension and continuity validation use OrganizationMemberId; privacy-safe display names remain presentation only and are never identity proof.
• Compact Settings help: every field has one short visible sentence plus a detailed information popup, with shared Live and Demo descriptions sourced from one application catalog.
• Testing access: Admin Mode now offers a Minimize button, and the AccessControl notification-area icon provides an obvious Restore AccessControl action.
• More dependable deployment: the live activity log no longer risks a WPF collection reentrancy crash, the visible install-time Admin Code defaults to 0000 for easy onsite confirmation, and duplicate startup instructions collapse to one canonical simulator launch row.
• WinSysMaint inside Admin Settings: owners can review every current service option, choose JSON, folder, and application paths, manage time, maintenance, connectivity, AccessControl watchdog, TrackMan monitoring, Defender, and GPU settings, and request an administrator-approved restart from one dark-glass tab.
• Narrow machine permissions: the kiosk account may update only the installed WinSysMaint service.json; service binaries, the surrounding ProgramData folder, and Windows service control remain protected.
• Booking time that matches the simulator: CourtReserve start and end values are treated as the simulator computer's local wall clock, and notification timeout now locks the kiosk, including a pre-end notification timeout.
• Optional live diagnostics: owners can expand the session countdown with labeled Booking Name, Start Time, End Time, and Current Time rows when troubleshooting schedule behavior.
• Consistent customer privacy: the bookings list, countdown, notifications, scheduler instructions, diagnostics, and Demo Mode all use first name plus last initial instead of retaining or displaying full customer names.
• Safer extension offers: Extend My Time now has its own owner-configurable Booking Gap and not-allowed message, independent from Make A Booking availability rows.
• Readable owner-authored rules: Small preserves the original Guidelines typography, while Medium and Large add predictable four- and eight-point increases. Unsaved choices can be reviewed in the real preview before saving.
• Review before acceptance: the wider Guidelines dialog wraps long text without horizontal scrolling; if content extends below the viewport, I ACCEPT remains disabled until the customer reaches the bottom.
• Readable customer guidance everywhere: Help, Make A Booking, Extend My Time, and Booking Guidelines each offer independent Small, Medium, and Large text choices, one-finger vertical scrolling, and larger touch-friendly scrollbars.
• Owner-controlled Windows startup: General Settings reports the current registration and can enable or disable AccessControl auto start immediately, requesting Windows administrator approval only for Deployment Manager-managed tasks.
• Safe monitoring checks: one button writes 55 clearly labeled AccessControl and WinSysMaint Application Log samples for TeamViewer testing without closing applications, rebooting, or changing maintenance state.
• Portable Demo Mode: owners can export or import a secret-free Demo Settings JSON profile, save the displayed booking sequence as a relative CSV timeline, reload a reviewed scenario with fresh safe PINs, or leave an imported file and generate a new varied schedule.
• AI-assisted scenario design: a new cross-tool skill package helps ChatGPT and Claude turn a plain-language test goal into coordinated Demo Settings and booking-timeline files, explain boundary cases, preserve unrelated settings, and validate the result before import.
• Reliable Demo CSV round trips: generated back-to-back bookings omit zero-minute Gap rows, and below/equal/above samples remain whole-minute values even when an owner selects an odd threshold.