npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

laser500-exomizer

v0.0.2

Published

Exomizer self extracting build tool for Laser 500.

Downloads

1

Readme

laser500-exomizer

Exomizer self extracting build tool for Laser 500.

Takes an exomized Laser 500 program and turns it into a self extracting executable.

The self-extractor uses the Z80 deexo.asm routine relocated at the address $F500. After decompression, the system VARTAB pointer is set according to the uncompressed file length. That can be overidden for special cases (e.g. multiple chunks programs) with the -v option which sets explicitly the VARTAB pointer.

Installation

npm i -g laser500-exomizer

Usage

After installation, you can call the command exolaser from the prompt.

Example:

First create the exomized data bytes from AMSTERD.bin. It's assumed that exomizer.exe is already installed and in the path.

exomizer.exe raw -P0 amsterd.bin -o amsterd.exo.dat

Now create the Laser 500 self extracting program amsterd.exo.bin

exolaser -i amsterd.exo.dat -u amsterd.bin -o amsterd.exo.bin 

Testing

You can also test decompression with the test_deexo command. It runs the deexo routine in a simulated Z80 environment using the given parameters.

Example

test_deexo -o amsterd.bin 8995 -c amsterd.exo.dat e400
  • amsterd.bin is the original uncompressed file
  • 8995 is the memory address where the file will be decompressed to
  • amsterd.exo.dat is the exomized bytes file
  • e400 is the memory address where to put the exomized data bytes

There is also a -b option that switches to backward compression using the Z80 assembler routine deexo_b.asm. It requires that the exomized data bytes are created with the exomizer -b option.

Backward compression is used when the compressed data have to be placed in memory before the decompressed section. Normal forward compression is used when the compressed data are placed after the decompressed section.