IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing startup splash screen errors on legacy panel PCs

Panel PCs and displays Published 5 min read

Short answer

Corrupted splash screens at power-up on a legacy panel PC come from two graphics-heavy programs initializing in the same boot window. Keep the HMI runtime shortcut in the Startup folder, move the remote-access utility to the desktop, and launch it by hand once the runtime has painted. Then verify flash-disk free space and RAM headroom before trusting the unit in production.

On this page
  1. What the fault looks like
  2. The fix: stagger the two programs
  3. Why staggering works
  4. Check the flash disk before it fills
  5. Set the RAM floor for a retrofit
  6. Reported legacy configurations
  7. Faults that look like this but are not it
  8. Questions asked

Garbled or half-drawn splash screens at power-up on a legacy panel PC are usually a load-order problem, not a dying display. On the units where this fault was run down, the HMI/SCADA runtime and a remote-access utility were both launching from the Startup folder, and the integrated graphics could not serve two full-screen applications initializing in the same boot window. The fix is sequencing, not replacement: keep the runtime's project-file shortcut in Startup, move the utility to the desktop, and launch it by hand once the runtime has painted. This article gives the stagger procedure, the differential against look-alike faults, and the flash-disk and RAM checks that decide whether the unit stays in service.

What the fault looks like #

The corruption appears only during boot, while both programs are loading: splash screens render torn, half-drawn, or in wrong colors. Once loading finishes, both applications behave normally, and starting either one by itself renders cleanly every time. The reported trigger was a shortcut to the runtime project file (a .scs file on the unit that showed the fault) sitting in Startup alongside the factory-placed shortcut for the remote-access (RAS) utility. The field evidence points at simultaneous graphics loading on shared-memory integrated graphics as the cause; it does not establish a defective driver, and the fix is the same either way.

The fix: stagger the two programs #

  1. Put the machine in a safe state and brief the operator first: until the runtime loads, the panel is not supervising the machine.
  2. Open the System Configuration Utility, and on the General tab, under Startup Selection, choose Selective Startup so no startup items load. Restart and confirm the desktop comes up clean.
  3. Return the runtime's project-file shortcut to the Startup folder so the HMI loads automatically at boot.
  4. Leave the remote-access utility out of Startup and keep its shortcut on the desktop.
  5. Restart and watch the boot: the runtime splash must render correctly and the runtime must reach its first operator screen before you launch the utility manually.
  6. Re-enable any other startup items one at a time, restarting between each, so a recurrence identifies the exact item.

On panel PCs running newer operating systems, the same control lives in the Task Manager Startup tab: select the application or service and click Disable.

Why staggering works #

Integrated graphics on these platforms has no dedicated video memory: framebuffers and 2D surfaces come out of system RAM. With 512 MB installed, two full-screen applications drawing splash screens at the same instant peak together on the same memory and the same display handling, and one or both splash screens corrupt. Sequencing the launches separates the peaks; the same two programs coexist without issue once initialization is over, which is why the fault never appears after boot.

Check the flash disk before it fills #

The earliest reported units shipped a 1 GB solid-state disk that left roughly 500 MB free once the embedded OS image was installed; later configurations moved to 2 GB flash disks or DOMs (disk-on-modules). Run the budget once at commissioning, using the 1 GB unit as the example:

  • Reported: 1000 MB nominal capacity, about 500 MB consumed by the OS image.
  • Example inputs: the runtime and its utilities install into 250 MB, and alarm and event logs grow at 10 MB per day.
  • Free space: 1000 MB − 500 MB − 250 MB = 250 MB.
  • Time to a full disk: 250 MB ÷ 10 MB/day = 25 days.
  • The same load on the 2 GB configuration: 2000 MB − 500 MB − 250 MB = 1250 MB, which is 1250 ÷ 10 = 125 days.

Decision: a 1 GB disk with continuous logging fills within a month of commissioning, so cap or offload the logs there, and treat 2 GB as the minimum when specifying any retrofit. Confirm whether the OS image runs a write filter before building a log-retention plan: filtered writes never consume the disk, but they are discarded at reboot, so retention must be planned around the filter state rather than free space alone.

Set the RAM floor for a retrofit #

The reported display units carried 512 MB; later box versions were offered with 1024 MB. The field verdict on 512 MB was that it runs the runtime adequately on its own and comes up short with demanding SCADA plus a second graphics-heavy program sharing the same memory. Commit to 1024 MB as the floor for any retrofit panel PC that will run an HMI/SCADA runtime, a remote-access utility, and anything else at boot — 512 MB leaves no margin once the integrated graphics takes its share. If the check points to replacement rather than repair, work through the selection criteria in Planning an HMI Terminal Replacement From an Older Operator Panel.

Reported legacy configurations #

Form factor Display RAM Storage
Panel PC 12 in 512 MB 2 GB flash disk
Panel PC 15 in 512 MB 2 GB flash disk
Box unit None 512 MB 2 GB DOM
Box unit None 512 MB 4 GB DOM
Box unit None 1024 MB 2 GB DOM
Box unit None 1024 MB 4 GB DOM

Processor across the reported range: 1.3 GHz. A separate 17 in touch panel supported 1280 × 1024 (SXGA), the resolution the existing SCADA applications were built against. These are field-reported legacy configurations, listed to anchor sizing checks on units already installed, not a statement of current product offerings. The earliest units also shipped the 1 GB flash disk covered above; measure free space on the actual unit rather than inferring it from the size label.

Faults that look like this but are not it #

  • Corruption only at boot, clearing once loading finishes, and reproducible whenever both programs start together: the startup conflict above — stagger the loads.
  • A black screen immediately after the operating-system logo, at every boot: a damaged image or driver, not application sequencing; repair the image, with a clean reinstallation as the documented last resort.
  • Artifacts such as thin colored vertical lines that also show in the firmware setup screen: the display path — panel, cable, or board — rather than software. Comparing an external monitor, where the unit exposes a video output, splits panel from board.
  • Screens that load correctly but update slowly or freeze during operation: a communication fault class, not graphics, covered in Why an HMI Freezes or Updates Slowly Over Serial.

Questions asked

Does a corrupted splash screen at boot mean the graphics hardware is failing?

No. On the reported units the corruption appeared only when two graphics-heavy programs initialized in the same boot window, and it cleared once the loads were staggered. If artifacts persist at all times, including in the firmware setup screen, treat it as the display path instead and split panel from board with an external monitor before ordering parts.

How do I keep a 1 GB flash disk from filling?

Cap alarm and event logging in the runtime and offload archives to a network share on a schedule so the disk only holds transient data. Also confirm whether the embedded OS image runs a write filter: filtered writes never consume disk space, but they are discarded at reboot, so log retention has to be planned around the filter state rather than free space alone.

Is it safe to disable every item in Startup while testing?

Disable one item at a time and restart between changes so a recurrence identifies the culprit. Never disable the runtime itself, its licensing service when the software uses a USB dongle, or any machine watchdog software. On panel PCs running newer operating systems, the same control sits in the Task Manager Startup tab, where you select the item and click Disable.

How do I check whether 512 MB of RAM is enough on a running unit?

Open Task Manager, go to the Performance tab, and compare Peak commit charge with the physical memory total after a full shift with both the runtime and the remote-access utility running. Peak commit at or near the physical total means the unit is paging and has no headroom, so move to the 1024 MB configuration before adding anything else to the boot.

Will moving the remote-access utility out of Startup break remote support?

No, but it changes availability. The utility still runs when launched from its desktop shortcut; until someone starts it, the panel PC will not accept remote sessions. Make the manual launch part of the shift routine, or have a local operator start it during commissioning before the machine is handed over.

Keep reading

  • Selection guide

    Planning an HMI Terminal Replacement From an Older Operator Panel

    Decide an operator-terminal replacement on installed cost — the terminal, cutout adaptation, application software, engineering, commissioning, downtime and a spare — never on terminal price alone. Measure the opening against the replacement's documented cutout range and count displays before ordering: a slightly smaller terminal needs a bezel adapter, and a large converted application can force the higher-performance model. Convert in the same brand when the source project opens cleanly; rebuild cross-brand when you accept the extra engineering hours for source control.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Freezes or Updates Slowly Over Serial

    A panel-wide freeze or slow updates over serial is a link fault — driver, PLC port, wiring, or startup timing — not a screen-object fault. Test the two field-proven fixes first: a 10-second startup delay before the first poll, and a port set to four-wire RS-422 at 19,200 baud. Fix an isolated stale tag separately, by address and data type.

    HMI and touchscreens

  • How-to

    How to Upload an HMI Program Without the Right Cable Pinout

    Upload an HG3F with the documented programming cable HG9Z-XCM1A, which runs from a 9-pin RS-232 port on the PC to Serial Interface 2 on the panel. Do not fabricate a pinout, and confirm the installed WindOI-NV2 version permits upload before you connect.

    HMI and touchscreens