P1POPStarter DocsRecovered preservation manual
Setup Storage Reference Archive

Version and Integrity

Build identification offsets, final-build boundary, old RIP/WIP caveats, hash discipline, and tampered-bundle warnings.

Verify the build before debugging#

Many POPStarter contradictions come from mixing old RIP/WIP/prototype behavior with final r13 instructions. Before debugging commands, IGR, IRX modules, or config bytes, identify the exact launcher build.

Hex identification#

The recovered version page says the build identity can be checked directly in POPSTARTER.ELF with a hex editor. This is a verification method, not a download instruction.

Where to inspectMeaningHow to use it
Offset $59Build date area.Check whether the visible date matches the package/build being documented.
Starting at $5EBuild ID area.Compare against source notes before applying build-specific fixes.
Final public baselineRev 13 Beta 2019/06/05.Use this as the normal documentation target unless intentionally testing old behavior.
Old beta/prototype IDsSome old beta ranges share IDs; many prototypes use different markers.Do not collapse old build labels into final r13 behavior without proof.

Final build boundary#

  • Final public build: r13 Beta 2019/06/05.
  • Recovered history says the final build includes the Jan 14 2019 USB driver line.
  • Recovered history also says $IGR5 was likely fixed in this final public beta.
  • Normal docs should target the final build unless a page is explicitly about WIP/RIP/prototype behavior.

Old package caveats#

Package familyWhy it still mattersDocumentation stance
RIP buildsOld public packages and module experiments may reference them.Label as old and build-specific; do not present as preferred setup.
WIP / OBT buildsSome features, bytes, and module-loader notes changed over time.Useful for history and experiments only when the source names that build.
PrototypesMay expose behavior that was broken, changed, or never meant for normal users.Archive context, not user-facing default instructions.
Modern fix packsCan post-date final r13 and add compatibility layers.Document as external fixes, not as changes inside the final ELF.

Tampered-bundle warning#

The recovered warning pages are useful because they teach an integrity lesson: avoid modified repacks that remove credits, alter logos, obscure provenance, or make aggressive claims about "fixed" builds without hashes and source labels. The public site does not need to repeat personal drama to keep users safe.

Use hashes, build IDs, filenames, package role, and source labels. If a package cannot be identified, treat it as unknown even if it has a familiar filename.

Verification checklist#

  1. Record the exact filename and package label.
  2. Record any available SHA or hash identifier.
  3. Check the build date area near offset $59.
  4. Check the build ID area starting around $5E.
  5. Classify the file as final r13, old RIP/WIP, prototype, fix pack, or unknown.
  6. Only then apply build-specific command, config-byte, IRX, or IGR advice.