creo-remotelisted

# Creo Remote — Operation Skill Run a Creo J-Link batch on a Windows machine you are not sitting at. One command from the Mac: push the app, compile, launch, wait, clean up. Companion to **`creo-jlink`**, which owns the recipe (JVM version, `protk.dat`, writing the Java app) and ships `creo-run.bat`. This skill only adds the remote plumbing, and reuses that `creo-run.bat` on the far end rather than reimplementing it. ## Prerequisites on the Windows box | | Why | |---|---| | WSL, reachable by `ssh <alias>` | the only sane way in — see "Why WSL" below | | Creo + a JDK new enough for `otk.jar` | `creo-remote.sh --check` verifies this | | **An interactive session that is logged on** | Creo needs a GUI rendering context. An RDP session counts, and it may be *disconnected* — it just has to exist | That last one is not optional and is the most common reason a run does nothing. `--status` shows it. ## Setup Edit the block at the top of `creo-remote.sh` (or set the matching `CREO_*` environment variables): ```bash HOST=winbox # ssh alias of the WSL on the Windows machine WIN_USER=dev # Windows account logged in interactively WORK_WIN='C:\creo-auto' # working directory, Windows path CREO_ROOT='C:\Program Files\PTC\Creo 13.4.0.0' JDK_WIN='C:\Program Files\Eclipse Adoptium\jdk-25.0.3+9' CODEPAGE=GBK # Windows console codepage: GBK (zh), CP1252 (en) ``` `~/.ssh/co