@database "AmiNet_ReadMe.guide" @Node Main "Welcome to the Aminet Text File Listings, v3.0 by Dotoran!" @{"General Description" link GENERAL} ~~~~~~~~~~~~~~~~~~~~~~ @{"Installing for the FIRST TIME into a v3.xx CNet Amiga BBS!" link V3XX} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @{"Installing for the FIRST TIME into a v4.xx CNet Amiga BBS!" link V4XX} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @{"UPGRADING to v3.0 from v1.0/v2.0 AMINET TEXTS!" link UPGRADE} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @{"OTHER SYSOPS wanting to Install these AmiNet Listings!" link OTHER} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @{"AFTER YOU'RE DONE INSTALLING" link AFTER} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @{"Pointers on Effective Use of these Text File Lists" link POINTERS} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @{"Anything Else to Add?" link LAST} ~~~~~~~~~~~~~~~~~~~~~~~~ @endnode @Node GENERAL "General Description" If you have a CD-Rom connected to your system, you also most probably are the owner of one or more of the AmiNet Amiga-Based CD-Rom disks. This package is a TEXT FILE LIBRARY containing the index listings of ALL FILES contained on the following CD-Roms: AmiNet # 5 AmiNet SET II (4 CD's) AmiNet # 6 AmiNet # 9 AmiNet SET I (4 CD's) AmiNet # 10 AmiNet # 7 AmiNet # 8 The files contained in this archive were extracted from the directory sorted "Aminet_Dir.doc" file, located in the "Lists/" directory of the AmiNet # 10 CD-Rom. Each list contains the title, size, cd location, as well as short description of each directory housed within AmiNet. Each listing has also been automatically colorized, as well as having an informational header attached to the start of each listing. NOTE: New for 3.0 is that the COLORIZED listings now use ANSI color codes, instead of the CNet Specific MCI Commands, which will allow them to be used on ANY AMIGA BBS! (An ARexx script is also included to DELETE the CNet Specific "data/" directories, which will then leave only the text files themselves) SysOps of "Non-CNet" bbs's need only add these files into their bbs's directory structures to use them. These files can be used by your users to get an idea as to what they can find in each library within AmiNet, and can even be used as a means of your users to REQUEST files(for those of us with just 1 CD-Rom online), so they can ask us to place a particular AmiNet CD-Rom in the drive to snag files off of. @endnode @Node V3XX "Installing into a v3.xx CNet Amiga" Installing for the FIRST TIME into a CNet Amiga BBS! (v3.05c) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1: Go into your GFILES section of the bbs and create a new listing using the filename of "Aminet" (Capitalize the "A" for aesthetics later). 2: Change any of the list settings you feel the need to, just make sure to specify the above for the filename. For the title, you can specify any text of your choosing, but keep in mind that the listings given pertain to ALL AmiNet CD-Roms, so your title may wish to reflect this point. 3: Now, either from a shell, or through a directory program, go into your GFILES: path and DELETE the "Aminet/" directory that CNet created above. 4: Using LHA again, unpack the "AMINET_TEXTS.LHA" archive directly into the path that the "Aminet/" directory you deleted above was stored in. 5: This archive contains a NEW "Aminet/" directory, which in turn houses numerous other directories! 6: Once it's unpacked, you're all set! @{"AFTER INSTALLING" link AFTER} @endnode @Node V4XX "Installing into a v4.xx CNet Amiga" Installing for the FIRST TIME into a CNet Amiga BBS! (v4.xx) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1: Enter the area of your bbs where you wish to store these text listings, then use the AL (Add List) command to create a NEW List Type. 2: Press ENTER to skip the "Copy from Physical Sub#" prompt, then select number 0 to create a "Subdirectory". 3: Use "Aminet CD-Rom Listings" as the "Title to appear on list" prompt, followed by using AMINETS (all uppercase) for the "Unique Name", as this will become the "GO" keyword. 4: For "Path to subboard data files", use "Base0:TextFiles/Aminet/". NOTE: I renamed my "GFiles" directory in the Base0: directory into the "TextFiles" directory used above to more adequately conform to the way CNet 4.xx does things. You may wish to use "GFiles" instead, but it MUST appear in your "Base0:" directory, and you MUST also include an ASSIGN to a "TEXTFILES:" directory which points to the same directory your "GFILES:" assign uses, as each of the internal subdirectories uses this assignment. 5: You may then choose whatever other characteristics you wish from the VDE screen pertaining to this directory. Hit "<< Exit" when complete. 6: Now, either from a shell, or through a directory program, go into your Base0:TextFiles/ (or Base0:GFiles/) path and DELETE the "Aminet/" directory that you had CNet create above. 7: Using LHA again, unpack the "AMINET_TEXTS.LHA" archive directly into the path that the "Aminet/" directory you deleted above was stored in. 8: This archive contains a NEW "Aminet/" directory, which in turn houses numerous other directories! 9: Once it's unpacked, you're all set! NOTE: Each of the internal subdirectories also has "GO Keywords" set up for them for use on your bbs. The keyword used starts with AMINET and is then followed by the directory interested in, so for instance, files pertaining to bbs programs are under the AMINETCOMM keyword, whereas game files are under AMINETGAME, etc. @{"AFTER INSTALLING" link AFTER} @endnode @Node UPGRADE "Upgrading to v3.0 from v1.0 or v2.0" UPGRADE to v3.0 from v1.0/v2.0 AMINET TEXTS! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For SysOps using a previous release, you can upgrade to these newer listings by following these steps: 1: Use a cli-shell prompt or a directory manipulation program to enter your GFILES: path, then DELETE the "Aminet/" directory(and EVERYTHING in it)! 2: Using LHA, unpack the "AMINET_TEXTS" archive into the path you accessed in the step above. 3: That's it! @{"AFTER INSTALLING" link AFTER} @endnode @Node OTHER "Installation Procedure for Other SysOps" OTHER SYSOPS wanting to Install these AmiNet Listings! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1: If you're a SysOp using a bbs program OTHER than CNet Amiga, choose a location on one of your hard drives with at least 3.5 MEGS free, then unpack the AMINET_TEXTS.LHA file into this path. 2: Use whatever commands are appropriate for your bbs program to create a subdirectory called Aminet, then create subdirectories INSIDE this Aminet directory for each of the included subdirectories. 3: You'll now have to add each text file into it's subdirectory. Hopefully, your bbs program will have a means of adopting these files quickly and easily, else you'll need to do each one individually. 4: Lastly, I included a straight ARexx file, titled "StripCNet.rexx" in the main AMINET_LISTS.LHA archive. You can use this file to DELETE the CNet Amiga specific data files from within each archive, which will save you a LITTLE more space. The script will ask you two questions before it begins it's work. When finished, you'll be set to start using them on your bbs's! @{"AFTER INSTALLING" link AFTER} @endnode @Node AFTER "After you've completed the installation..." For v3.0, as mentioned above, each listing uses ANSI color codes, so the listings can be viewed by/on ANY Amiga BBS, instead of the CNet specific MCI Color Commands. These listings contain files stored on AmiNet Set II, #9, and #10, which were NOT present in the previous release. Each listing uses the long desc. of each directory, as specified in the "Index" file on AmiNet #10, instead of the, sometimes, confusing directory path. A "talley" was also included at the conclusion of each listing, which specifies the total number of files found within this area. In addition, slight modifications were made to the "CD Locations" used in these listings, so as to hopefully be a bit more understandable. The CD's in AmiNet Set I used A, B, C, and D for their locations, while the newer AmiNet Set II used a, b, c, and d for their locations. In addition to these letters, I included a "1" preceeding the letter for "Set I", and used a "2" preceeding the letter for "Set II", so you may see references like 1A, or 2d under the "CD" column. I also replaced the space with the number "10" if the file was found on AmiNet # 10(which was the current CD-Rom when these lists were created). The SPACE that was used could be confusing to users trying to figure out which CD the file was found on. Lastly, inside each "data/" directory is a text file titled "sys.entry" which can be used as a "title screen" for use upon entering a specific area. These screens use an ASCII character set, with NO color, so should be usable on any Amiga BBS as well. @endnode @Node POINTERS "Helpful pointers on Effective use of this mod..." Text File List Pointers ~~~~~~~~~~~~~~~~~~~~~~~~ - If your bbs allows you to, it is HIGHLY recommended that you ENABLE your "More?" type prompts for each of these listings, as some of them are rather long, so a "More?" type prompt can be QUITE useful. - If your bbs allows text files to be DOWNLOADED from the same prompt they can be viewed from, keep in mind that the ANSI codes will also be sent with the file. If a user wishes to obtain a "clean" listing, it is recommended they capture a listing in their terminals BUFFER, then Save their buffer to disk. Most terminal programs will either automatically(or can be set to) strip these ansi codes before being placed into their buffers. @endnode @Node LAST "Before finishing up..." Anything Else to Add? ~~~~~~~~~~~~~~~~~~~~~ Yes! This is the first in a series of files I'll be working on to make working with, and using the Aminet series of CD-Roms easier for both YOU and your users. If there's a specific feature pertaining to the use of AmiNet CD-Roms you'd like to see implemented for CNet Amiga, drop me a line and I'll see what I can do. You can get in touch with me through any of the following channels: Through Internet: dotoran@bluemoon.net Through FidoNet: David Weeks@1:260/121.0 Through CLinkNet: David Weeks@911:6840/2.0 Through ChipsNet: Dotoran@546:7/1.0 Through SnailMail: David Weeks 318 Woodside Avenue Buffalo, NY 14220-2015 - Dotoran ============================================================================ Frontiers BBS (716)/823-9892! ============================================================================ @endnode