On Thu, Oct 26, 2017 at 1:34 AM, Marko Mäkelä <msmakela@gmail.com> wrote: > On Wed, Oct 25, 2017 at 06:32:05PM -0400, Ethan Dicks wrote: >>> >>> The ZIP files contains LNX files. > > I thought that it is the standard way how Lynx files work. It is an > uncompressed archive format that allows in-place operation. You could just > edit the next-sector pointers in-place to assemble or expand a Lynx archive. I am entirely unexperienced with the nuances of how Lynx works. I can see how that would be helpful on these machines, but I wouldn't have guessed it just glancing at the files. > Did you try the -l option of my cbmconvert? It supports the Lynx format. As it happens, I already have a compiled version of that on my retro dev box, and it totally took care of extracting the files. Thanks for the tip! Sadly, the contents are not 100% of what I was looking for, but now I know. My entire goal with this was to track down the origin of a PET ROM I got around 1979-1980 that AFAIK was a version of Micromon for the 2001-N/3032. I used it heavily as a learning and production tool for assembly because I didn't have a disk drive (tape only) and writing out code by hand and typing the hex into TIM got old over about 200 bytes. With the line-at-a-time assembler/disassembler, I was writing code bits 4K and larger. I never have verified exactly what version of what product it was that I got, and since it was relocated up into expansion ROM space, I wanted to check some things before putting my copy of it up on Zimmers.net so I could include some basic documentation. The ICPUG disks are full of Micromon and Extramon code, but, with one exception, not set up for burning into ROMs. -ethan Message was sent through the cbm-hackers mailing listReceived on 2017-10-26 18:01:29
Archive generated by hypermail 2.2.0.