Over the years I have collected a bunch of Amiga file archives from different places. During this collecting period I had the need to find files quickly inside disk images, iso images and even inside archives. I have the need to sometimes find files for a certain project I'm working on like my "JCL ColourPic Digitizer", "RocGen RG300C Genlock", "Alcotini Stereo Soundsampler", "Vidi Amiga/ROMBO Ltd.", "Amiga Aminet Set CD's" and "PDF Computer Books & Magazine Search engine" (which is based on the incredible "DLH's Commodore Archive" by Bombjack, The Awesome "Commodore Is Awesome") and the recent fantastic addition RetroPDFs website. Great people doing a great job!

Additionally I created searchable databases based on these projects:
CD files from TEKNO Magazine (Norwegian computer magazine)
All recorded music from Stone Oakvalley's Authentic SID Collection (SOASC=)
All recorded music from Stone Oakvalley's Amiga Music Collection (SOAMC=)
All games indexed and used in Stone Oakvalley's Multi Arcade Console 2000 (SOAMC)
including some other random database tests of the many collections I have collected during 10 years of various kind.

During that time I fiddled with some very crude GUI and slow working search software that I made myself. Eventually I decided to create a suitable global database engine and search tool so others can benefit of the collections I have structured and spent quite a lot of time to make it possible to search for filenames, disknames and even text inside PDF files, archive, disk images and so fourth.

The good thing is the database engine and main tool are dynamic so it can be used for practically anything text related, not only Amiga related. The generation of the actual optimized database is only done by my tools as was at the beginning very slow (used days to index).

I'm currently at the end of 2014 improving the entire routine with plans to release a user tool where you can index an HDD and produce a suitable database package for use with the SOTDS engine. After that, there is no limitions basically, anything can be indexed and be able to produce a suitable package (as long as it can be contained within 4 text data fields, where the last is always expected to be numeric, like filesize, page number or some kind of id).





Some of the databases rely on filenames and directory structures, so it's natural that you may not recognize some of the hits you will get (they are kind of a personal collection, where some minor things was tweaked to fit my needs and directories were named by me as I see personally fit). Also, know that I will not host any of these files as I do not have the dedicated space hosting it and have no desire to participate in piracy activity (even its for historical reasons regarding obsolete-ware).

So, it's sad you find a filename and where the file was located on, be it ISO, ADF, PDF Magazine or others, and still you can't download, right? Think of this database project as a "encyclopedia". If you look up for example "Mona Lisa", you will learn it was painted by Leonardo da Vinci. This does not mean you will "get" Leonardo da Vinci?!, right, you simply learned the origin of "Mona Lisa".

This is how the database concept works and intended intentionally. Now, today, you do have the benefit of googling "Leonardo da Vinci" and find more data about "Mona Lisa" and so fourth. In our example, you can use Google to search for the ISO, ADF, PDF filename or anything else that the database spit out. And voila! You might find the file you are looking for in a online collection hidden deep inside the web.

The tools and databases I provide are merely a "helper pin-pointer" to help you on your quest for "THAT" exact desired file.

If you are like me, a dedicated old-school and nostalgic collector of all-things-that-was-your-childhood, most likely, the 80's, you will already have the mentioned collections already on your harddrive :-)