From 18da4023b7fb86f96023ed492e11268609ea62d4 Mon Sep 17 00:00:00 2001 From: "B. Watson" Date: Fri, 11 Nov 2022 18:34:47 -0500 Subject: Bullet-proof dla2img.sh, update README.txt. --- README.txt | 48 ++++++++++++++++++++++++++++++------------------ 1 file changed, 30 insertions(+), 18 deletions(-) (limited to 'README.txt') diff --git a/README.txt b/README.txt index f55efbd..6661309 100644 --- a/README.txt +++ b/README.txt @@ -68,12 +68,13 @@ black, while the image is generated. Be patient... After the image is finished generating, the image will be displayed. The bottom line shows a menu, from which you can choose to: -- Save: Save the image to disk. You'll be prompted for a filename, - which must be a complete filespec (examples: D:TEST.DLA, - D2:THING.DLA). The file will be the raw pixels, 8 per byte, 256 - pixels (32 bytes) per line, 170 lines. Size will be 5440 bytes, - or 44 sectors on a single-density disk. If an error happens while - saving, you'll get the chance to retry the save. +- Save: Save the image to disk. You'll be prompted for a filename. + If you don't include a drive spec (e.g. D: or D2:), drive 1 (D:) + is assumed. + The file will contain the raw pixels, 8 per byte, 256 pixels (32 + bytes) per line, 170 lines. Size will be 5440 bytes, or 44 sectors + on a single-density disk. If an error happens while saving, you'll + get the chance to retry the save. - Redo: Run the generation process again, with the current particle count and seed type settings. @@ -89,24 +90,23 @@ Using dla2csv.xex (or just dla2csv) This program operates almost identically whether it's running on an Atari or a modern machine. -First, you will be prompted for an input filename. On the Atari, you -must include the drive specifier (e.g. D:TEST.DLA or D2:FOO.DLA). This -must be a file created by the Save option in dla.xex. The file is read -into memory immediately. +First, you will be prompted for an input filename[*]. This must be +a file created by the Save option in dla.xex. The file is read into +memory immediately. -Next, choose the line-ending type. Choices are Atari, Unix, and MS -(aka MS-DOS or Windows). Choose the system under which you'll be -actually using the CSV file. +Next, choose the line-ending type. Choices are Atari, Unix (including +Linux and Mac), and MS (aka MS-DOS or Windows). Choose the system +under which you'll be actually using the CSV file. -Next, you're asked for the output filename. On the Atari, this must -include the drive specifier (e.g. D:OUTPUT.CSV). This file will be +Next, you're asked for the output filename[*]. This file will be overwritten if it exists (unless of course it can't be overwritten due to permissions or the Atari locked-file bit). Next, the conversion process starts. This takes about one minute on the Atari, and is instantaneous on a modern machine. Progress is shown as a percentage. When it's finished, the output CSV file has been -written. +written. On the Atari, you can press Ctrl-C during the conversion to +abort the process (and delete the partial CSV file). Last, you're asked whether to convert another file. Answering N here will exit the program. On the Atari, you should be returned to the DOS @@ -114,6 +114,13 @@ menu or prompt, but your mileage may vary (it works on DOS 2.0S, at least). Answering Y (or just pressing Return) starts the whole process over at the input filename prompt. +[*] On the Atari, if you don't include a drive specifier (e.g. D: or D2:) + in the filename, drive 1 (D:) is assumed. Also, when you're asked + for the input or output filename, you can enter a number (a single + digit) to see a directory of that drive number. If you're using an + emulator that supports the H: (host drive) device, you can enter 0 + to see the directory of H:. + Using dla2img.sh ---------------- @@ -147,5 +154,10 @@ shell's $PATH), you can run it as e.g.: MAGICK=/path/to/magick ./dla2img.sh [arguments] -dla2img.sh has been tested with various shells, including bash, zsh, ksh93, -mksh, and dash. +If you get "stat: command not found", +Note: dla2img.sh has been tested with various shells, including bash, +zsh, ksh93, pdksh, mksh, dash, and bosh (from Schily-tools)... and +the ancient V7 UNIX Bourne shell compiled for Linux from AT&T source +(seriouly). If your system doesn't have a /bin/sh that's compatible, +edit the script and change the "#!/bin/sh" to something that works on +your system. -- cgit v1.2.3