@database AView.guide @master AView.guide @$VER: 1.47 (19.02.98) @author "Guido Mersmann" @(c) "Guido Mersmann" @node "Main" "AView" @{b} AView V1.47 ------------------ (C) Guido Mersmann in 1996-1998 AVIEW IS A SHAREWARE PRODUCT READ THE DISTRIBUTION SECTION FOR INFORMATION ON DISTRIBUTION Contents@{ub} ---------- @{"           Introduction           " link "Introduction"} @{"        System Requirements       " link "SystemRequirements"} @{"           Feature List           " link "FeatureList"} @{"           Distribution           " link "Distribution"} @{" How To Register " link "HOWTOREGISTER"} @{"          How To Install          " link "HowToInstall"} AView @{" Quick start " link "KickStart" 0} @{" AView " link "AView" 0} @{" AView_Prefs " link "AP_Main" 0} @{" AView command list " link "COMMAND" 0} @{" AVDeficons " link "AVDeficons" 0} The Icon-Manager @{"               FAQS               " link "FAQS"} @{"             History              " link "History" 999} @{"              Future              " link "Future"} @{"             Bug List             " link "Buglist"} @{"              Thanx               " link "Thanx"} @{"            The Author            " link "Author"} Bug Reports,Incitements... @{" My other amiga projects ! " link "OtherPrgs" 0} @endnode @node "Introduction" "Introduction" @{b}Introduction@{ub} -------------- AView is an multiview enhancement. You ask why you need AView? Every file needs a datatype. Many datatypes aren´t available or not very effective. You want to view a JPG picture and your prefered viewer? No problem! AView allows to specify a viewer for every file format. AView detects your file and runs the specified program or tool. @endnode @node "Systemrequirements" "System requirements" @{b}System requirements@{ub} --------------------- AView (should work) works on all Amigas with OS 2.0 or higher. Some functions are not available under 2.0, because they presume OS3.x+ (MemoryPools,...) From OS2.1 on AView is able to work multilingual. If you want to run programs by using the WB-Mode you need the WBStart.library V2.x. This library is under development of Stefan Becker and is available on Aminet. That`s all! @endnode @node "Featurelist" "Feature List" @{b}Feature List@{ub} -------------- ° Local support ° Kickstart 2.04 or higher is required. ° Programmed in Commodore Styleguide ° All adjustments are possible per Gadtools-GUI ° Different versions for different Kickstart versions. ° 100% Assembler ° Online help ° pre defined file types for an easy configuration ° allows to specify own file types. @endnode @node "Distribution" "Distribution" @{b}Distribution@{ub} -------------- This program should be published on every public medium, as long as all files in the archive are unchanged. If this medium is a CD I expect a free copy. (AminetCDs excluded) @{b}AView is Shareware.@{ub} Some @{"features" link "CRIMP"} are not available without a keyfile. I expect from everybody, who uses AView regularly, to @{"register" link "HOWTOREGISTER"} immediatly. I think this does not hurt anybody, and I will have more fun to integrate new features or write a new game. Updates may be requested from @{b}Aminet@{ub} and via ADSG Homepage @{b}http://www.amigaworld.com/adsg@{ub}. @{b}I am not liable for injures or data loss caused by AView. The use of AView is on your own responsibility !!!@{ub} @endnode @node "HOWTOREGISTER" "How to register?" @{b}How to register?@{ub} ------------------ AView registration is very easy. The Shareware fee is 10$ or 15DM. I think the requested fee is not to much for this program. After registration you are able to use the @{"complete" link "CRIMP"} programm. The registration of AView is done by the Amiga Developer Shareware Group (ADSG) More information about paying and shipping is available within the @{"ADSG-RegTool" system "//RegTool/RegTool"}. The keyfile will be shipped within 1 or 2 weeks. If you want to register, then do it @{"now" system "//RegTool/RegTool"}. @{b}Please use the included @{"register-tool" link system "//RegTool/RegTool"}. This makes our work easier and your registration will be done much faster.@{ub} @endnode @node "CRIMP" "Restrictions of this unregistered version" @{b}Restrictions of this unregistered version@{ub} ------------------------------------------- The @{b}unregistered@{ub} version of AView is not able to process more than 10 file types. This should be enough for your test procedure. @{b}After @{"registration" link "HOWTOREGISTER"} AView allows to configurate an unlimited amount of file types.@{ub} @endnode @node "Kickstart" "Quick start" @{b}Quick start@{ub} ------------- After installing AView you should run AViewPrefs. Some file types are installed by default and are ready to be modified. If you want to include new types, then use the @{"select" link "AP_Main_Select"} gadget. A new @{"requester" link "AP_GeLw"} opens and allows to choose one of the pre defined file types. After selecting one listview in the @{"main" link "AP_Main"} window you are able to open the @{"Edit" link "AP_Edit"} window by using the "Return"-Key. It is also possible to choose via double clicking on one entry. The @{"Edit" link "AP_Edit"} window allows to specify the command. This command will be started any time AView recognizes the specified file type. Use @{"%f" link "AP_Edit_Command"} to define the position of the file name. AView replaces this pattern automatically during operation. Repeat this actions until all file types are defined. @{b}Note: The @{"unregistered" link "HOWTOREGISTER"} version is not able to handle more than 10 file types.@{ub} @endnode @node "HowToInstall" "How to Install AView" @{b}How to Install AView@{ub} ---------------------- To install AView please use the original Commodore Installer. It creates a directory, in which AView is installed. If you do not like AView, you can delete the whole drawer to destroy AView completely. @endnode @node "AView" "AView" @{b}AView@{ub} ------- This is the main program and needed for daily usage. You are able to run AView via CLI, Workbench or AppIcon, by using Toolmanager or something like that. Run via CLI ------------- This is the aview template: "AView @{"Name/M" link "PATTNAME"},@{"ARG=To=From/K" link "PATTARG"},@{"All/S" link "PATTALL"},@{"SC=SetComment/S" link "PATTSC"},@{"SD=ShowDetect/S" link "PATTSD"}, @{"Debug/S" link "PATTDEBUG"}" Run via Workbench ------------------- Under normal conditions it is not useful, because AView isn´t able to get file names. AView opens a ASL-file requester. Toolmanager and .. -------------------- By using tools like Toolmanager or something like that you are able to put AView on Docks, AppIcons, Menus and many more. AView will view all files without any problems. But it is required to define your prefered @{"file types" link "AP_Main"}. This procedure is required only once. @endnode @node "History" "History" @{b}History@{ub} --------- This text is telling the story of AView like a diary. 0.95B First working beta version. 0.96B Small changes. Manual updated and AView adjusted to allow the new features of the preference window 0.97B Small CurrentDir bug fixed. This bug causes crashes when using "mfs-handler" and "AmiCDFS". It seems that SystemTagList is doing some strange things by using the "NP_Current" tag that causes such problems. "df0:" it self didn`t make any problems. AViewPrefs is sorting all entries automatically. 0.98B Small @{"Match" link "SO_Match"} bug fixed. Debug mode implemented. Small prefs changes. 0.99B Some internal adjustments. 1.00 Small bugs fixed. @{"ShowDetect" link "PATTSD"} feature implemented. (requested by Andreas Boerner) Empty files caused problems. (reported by Andreas Boerner) France catalogs included. (Thanks to Jerome Chesnot) Enlarged string gadgets. (requested by Andreas Boerner) 1.01 @{"NOT" link "CO_Not"} Command implemented. (requested by Andreas Boerner) 1.02 Small sourcecode optimisations. 1.03 "1" and "0" are now valid commands, so it is possible to use AView to solve mathematical problems. I needed this "feature" to check the internal commands without using test files for recognition. 1.04 Some Manual adjustments. 1.05 It is possible to define Lha if DMS is already defined. (reported by Andreas Boerner) 1.06 New Command @{"FILESIZE" link "CO_FileSize"}. It allows to detect a file by its size. 1.07 BUGFIX: No longer endless loops. Thrust me! 5 hours of intensive debugging. It wasn`t possible to debug this direct, because the bug wasn`t reproducable. I had to debug a running task. (reported by Andreas Boerner, Silke Bormann and me) 1.08 Kickstart-Types implemented and @{"ShowDetect" link "PATTSD"} function fixed. 1.09 Keyfile-Support. 1.10 Many new File types. 1.11 During @{"ShowDetect" link "PATTSD"} and @{"SetComment" link "PATTSC"} AView is using the pre defined file types. 1.12 AView allows to remove the "" around the file names. (Requested by Steffen Koch) 1.13 A new @{"%a" link "AP_Edit_Command"} option, allows to specify a argument. 1.14 An other manual update. 1.15 WB start is working correct now. 1.16 Enlarged @{"ASCII" link "CO_ASCII"} command to support ESC sequences. 1.17 The whole detecting file detecting procedure enhanced. 1.17 New AViewPrefs. No longer Up/Down gadgets. A new @{"Edit" link "AP_Edit"} | window implemented. 1.29 New @{"expert mode" link "AP_Sett_Expert"}. 1.30 Small bug fixes and an other manual update. 1.31 Menus added. @{"AViewPrefs-preferences" link "AP_Sett"} requester added. Currently there is only one point: Expert mode. 1.32 AView adjustment to support the new features. 1.33 Small bug fix. (@{"Menu open" link "AP_Menu_Open"}) 1.34 Screen title is viewing register information. 1.35 = 1.34 (small catalog changes) 1.36 Internal rework. 1.37 @{"Binary" link "CO_BINARY"}-command implemented. 1.38 AViewPrefs detects problems within the identifier. 1.39 @{"Binary" link "CO_BINARY"}/@{"Ascii" link "CO_ASCII"} quick detect implemented. The identifier gadget is auto activating after error reports. 1.40 @{"AVDefIcons" link "AVDeficons"} implemented. This tool allows to define default icons for each filetype. 1.41 Catalog files updated. Little library sorting bug fixed. Installerscript now supports deinstallation and AVDeficons install. 1.42 = 1.41 (AVDeficons V1.1 included) 1.43 @{"AVDefIcons" link "AVDeficons"} is converting icons types. This allows to specify project icons for disks. EnforcerHit removed. 1.44 Deinstallation fixed. (reported by Tony Belding) AViewPrefs is telling the aview.library whats up, if no prefs are available. (reported by Hans-Joachim Reinsch) File icons included. 1.45 New multi select support within AView´s ASL Requester. AVDeficons is a little bit more compatible. 1.46 Path problems solved. (reported by Jerome Chesnot) 1.47 AViewPrefs edit window was creating an enforcer hit when opend the first time. (reported by Hans-Joachim Reinsch) @endnode @node "Future" "Future" @{b}Future@{ub} -------- ° I don´t know. (-8 Your wishes are welcome. @endnode @node "Buglist" "Buglist" @{b}Buglist@{ub} --------- ° Someone told me that AViewPrefs is crashing on an 68060. I am not able to detect the problem. If you are using an 68060, then send me your test results. ° Currently there are no other known bugs. @endnode @node "Thanx" "Thanx" @{b}Thanx@{ub} ------- @{b}Timo Hegemann@{ub} : Beta and Enforcer testing @{b}Andreas Vierkant@{ub} : Beta testing @{b}Jerome Chesnot@{ub} : for the france translation. @{b}Andreas Boerner@{ub} : for tips, suggestions and bug reports. @{b}Steffen Koch@{ub} : for his suggestions. And of course many thanks to all registered users. @endnode @node "Author" "The Author" @{b}The Author@{ub} ------------ If you find some bugs in AView, please send me a message, so that I can correct these bugs in the next version. @{b} Guido Mersmann Glatzer Straße 12 48477 Hörstel Germany FIDONET : 2:2449/246.15 INTERNET: geit@studST.FH-Muenster.DE @{ub} @endnode @node "OtherPrgs" "Other programs !" @{b}Other programs!@{ub} ----------------- @{b}BoulderDäsh@{ub} [game/jump/boulderdaesh.lha] ------------- Clone of the original Boulderdäsh for Amiga. It is the only version running faster on Amiga than the original. It looks and behaves like the original. I was asked, where the C64 is. (-8 And all this on a 68000 without Fastmem. @{b}SimpleCat@{ub} [dev/misc/simplecat.lha] ----------- This tool is for programmers and user. Using this program you can change catalogues of programs with your favourite text editor in the easiest way. These programs must include a CS file. Search for it in the archive of the catalogues drawer. @{b}Afind@{ub} [util/misc/afind.lha] ------- With this program you can search for programs on your Aminet CDs in the easiest way. It is the same than the original tool on the CD, but here you can use AminetCDs and AminetSets mixed. So you are not forced to search for a program on the first 5 Aminet CDs, that is on AminetSet1 Disk b. @{b}AView@{ub} [util/misc/aview.lha] ------- AView is a great multiview enhancement/replacement! It is working like Multiview, but you are able to specify a special viewer/player for each file typ. @{b}Guideformat@{ub} [text/edit/guideformat.lha] ------------- GuideFormat is a simple tool. It is easy to format text blocks, even if there are "links" or other guide commands in. @{b}SiedlerBoot@{ub} [game/patch/siedlerboot.lha] ------------- This allows to start the Settlers direct via CD and save the scores on HD. There is no hard disk install required. SiedlerBoot requires the "Amiga Plus Sonderheft 9" cover CDROM. @endnode @node "Technical" "Technical information about AView" @{b}Technical information about AView@{ub} ----------------------------------- AView is 100% assembler coded. The sourcecode takes 234320 bytes in 34 files. AView is assembled with DevPac 3.04. DevPac needs 4 seconds and 755150 KB each time. AView was programmed on an A2000-030/25Mhz (9 MEG). I wrote this guide using GoldEd (3.x/4.x) and his fantastic fold features together with "GuideFormat" to format lines containing links. @endnode @node "COMMAND" "The File Identification Commands" @toc "PREF" @{b}The File Identification Commands@{ub} ---------------------------------- The @{"identifier" link "AP_Edit_Identifier"} gadget allows to define own file types, by using the following commands. @{b}GENERAL@{ub} --------- ° All commands must be separated by one space as minimum. ° Command names are case insensitiv. "@{"MATCH" link "CO_MATCH" 0}" = "MaTcH" ° All commands are only scanning the fist 8 KB buffer of an file. If a command is reading beyond this 8KB the hole file type fails. A file size which is smaller than 8KB will be handled like a smaller buffer. @{b}A List Of All Commands@{ub} ------------------------ @{" " link "CO_MATCH" 0} MATCH Check specified Bytes or Strings @{" " link "CO_FIND" 0} FIND Search for Bytes or Strings @{" " link "CO_NAME" 0} NAME Check file name @{" " link "CO_FILESIZE" 0} FILESIZE Check file size. @{" " link "CO_ASCII" 0} ASCII Check for ASCII file @{" " link "CO_AND" 0} AND AND-operation @{" " link "CO_OR" 0} OR OR-operation @{" " link "CO_NOT" 0} NOT NOT-operation @{" " link "CO_BRACKET" 0} () Bracket operation @endnode @node "CO_MATCH" "Command: MATCH" @toc "COMMAND" @{b}Match@{ub} ------- @{b}TEMPLATE:@{ub} MATCH [Offset/N,] String @{b}SHORT:@{ub} This command allows to check bytes or strings starting on an direct offset. @{b}EXAMPLES:@{ub} MATCH "Hello" Checks for an "Hello" in the first 5 bytes of an file. MATCH 1,"Hallo" Checks for an "Hello". This time the offset is one. MATCH 27,$1234 This match is looking for an $1234 on file offset 27. MATCH 0,"FORM????ILBM" This detects a "FORM" on offset zero and an "ILBM" on offset eight. An "?" means no further check. This Byte will be skipped. @{b}IMPORTANT:@{ub} The offset is optional and always zero if not specified. The offset is always decimal. The String must start with an " or an $! The String may contain "?". This bytes won´t be checked. @endnode @node "CO_FIND" "Command: FIND" @toc "COMMAND" @{b}FIND@{ub} ------ @{b}TEMPLATE:@{ub} FIND [Start/N,] [End/N,] String @{b}SHORT:@{ub} This command allows to search for an string between two offsets. @{b}EXAMPLES:@{ub} FIND "Hello" AView is searching the whole buffer! The search pattern is "Hello". FIND 10,"Smurf" AView is searching the string "Smurf" between 0 and 10. FIND 1,10,"Smurf" AView is searching for the string "Smurf" between 1 and 10. 10 is the last offset. This means AView will search the last time by using offset 10: "S" on offset 10, "m" on offset 11 and so on. FIND 1,127,$0001 AView is searching for the bytes $00 and $01 between "1" and "127". @{b}IMPORTANT:@{ub} The offsets are optional. If only one is specified this is the search end. If nothing is declared the whole buffer will be searched. Both offsets are decimal. The String must start with an " or an $! @endnode @node "CO_NAME" "Command: NAME" @toc "COMMAND" @{b}NAME@{ub} ------ @{b}TEMPLATE:@{ub} NAME Pattern/N @{b}SHORT:@{ub} This command compares the file name by using dos pattern. @{b}EXAMPLES:@{ub} NAME "#?.gif" This command will be only successful on files like "Smurf.gif"! NAME "#?.(jpeg|jpg)" Only file names with .jpeg or .jpg at the end are valid. @{b}IMPORTANT:@{ub} The pattern must be enclosed with "! @endnode @node "CO_FILESIZE" "Command: FILESIZE" @toc "COMMAND" @{b}FILESIZE@{ub} ---------- @{b}TEMPLATE:@{ub} FILESIZE Number/N @{b}SHORT:@{ub} This command compares the file size and the declared number. @{b}EXAMPLES@{ub} FILESIZE 901120 This command only comes true if the file size is equal to the specified number. FILESIZE 1024 @{"AND" link "CO_AND"} @{"NAME" link "CO_NAME"} "BootBlock#?" This file size must be 1024 and the file name must start with "BootBlock". @{b}IMPORTANT:@{ub} The number must be decimal. @endnode @node "CO_ASCII" "Command ASCII" @toc "COMMAND" @{b}ASCII@{ub} ------- @{b}TEMPLATE:@{ub} ASCII @{b}SHORT:@{ub} This command checks for non ASCII Bytes and will return "1" on the condition that there is non. @{b}EXAMPLES:@{ub} ASCII @{b}IMPORTANT:@{ub} The @{"ASCII" link "CO_ASCII"} and the BINARY command are switched to an special mode, if specified first within the identifier gadget. @endnode @node "CO_AND" "Command: AND" @toc "COMMAND" @{b}AND@{ub} ----- @{b}TEMPLATE:@{ub} AND @{b}SHORT:@{ub} This command allows to connect @{"commands" link "COMMAND"} via an AND operation. @{b}EXAMPLES:@{ub} @{"NAME" link "CO_NAME" 0} "#?.txt" AND @{"ASCII" link "CO_ASCII" 0} This will be successful if the name ends with an ".txt" @{b}and@{ub} it is an @{"ASCII" link "CO_ASCII"} file. @{"NAME" link "CO_NAME" 0} "#?.txt" & @{"ASCII" link "CO_ASCII" 0} This is equal to the last example. @{"NAME" link "CO_NAME" 0} "#?.guide" & @{"ASCII" link "CO_ASCII" 0} AND @{"FIND" link "CO_FIND" 0} 40,"@Database" The file name must end with an ".guide" and the file must contain an "@Database" starting within the first 40 bytes. @{b}IMPORTANT:@{ub} You are allowed to use the short version of AND: "&" An AND operation is always solved before an @{"Or" link "CO_OR"} operation. It is possible to override this by using @{"Brackets" link "CO_Brackets"} @endnode @node "CO_OR" "Command: OR" @toc "COMMAND" @{b}OR@{ub} ---- @{b}TEMPLATE:@{ub} OR @{b}SHORT:@{ub} This command allows to connect @{"single commands" link "COMMAND"} with an OR operation. @{b}EXAMPLES:@{ub} @{"NAME" link "CO_NAME" 0} "#?.txt" OR @{"ASCII" link "CO_ASCII" 0} The @{"NAME" link "CO_NAME"} must end with ".txt" or the file mast be an @{"ASCII" link "CO_ASCII" text to succeed this identifier. @{"NAME" link "CO_NAME" 0} "#?.txt" | @{"ASCII" link "CO_ASCII" 0} This example is equal to the first one. @{"NAME" link "CO_NAME" 0} "#?.guide" | @{"ASCII" link "CO_ASCII" 0} OR @{"FIND" link "CO_FIND" 0} 40,"@Database" One of the three commands must succeed to make this file identification successful. @{b}IMPORTANT:@{ub} "|" is the short version of "OR" An @{"AND" link "CO_AND"} operation has an higher priority. The only way to change this priority is to use @{"Brackets" link "CO_BRACKET"}. @endnode @node "CO_NOT" "Command: NOT" @toc "COMMAND" @{b}NOT@{ub} ----- @{b}TEMPLATE:@{ub} NOT @{b}SHORT:@{ub} This command causes a negation. @{b}EXAMPLES:@{ub} @{"NAME" link "CO_NAME" 0} "#?.hft" @{"AND" link "CO_AND"} NOT @{"ASCII" link "CO_ASCII" 0} This line will check for an file that is not @{"ASCII" link "CO_ASCII"}. Additional to that the file name must end with an ".hft". @{"NAME" link "CO_NAME" 0} "#?.hft" @{"AND" link "CO_AND"} ~ @{"ASCII" link "CO_ASCII" 0} This example is equal to the first one. ~ (@{"NAME" link "CO_NAME" 0} "#?.data" & @{"ASCII" link "CO_ASCII" 0}) No ".data" and no @{"ASCII" link "CO_ASCII"} file. @{b}IMPORTANT:@{ub} "~" is the short version of "NOT" A NOT operations is always prefered. The only exception are @{"brackets" link "CO_BRACKET" 0}. => "NOT NAME "Hello" AND ASCII" = "(NOT NAME "Hello) AND ASCII" @endnode @node "CO_BRACKET" "COMMAND: ()" @toc "COMMAND" @{b}( and )@{ub} --------- @{b}TEMPLATE:@{ub} ( ) @{b}SHORT:@{ub} Brackets allow to prefer operations. @{b}EXAMPLES:@{ub} @{"NAME" link "CO_NAME" 0} "#?.guide" @{"AND" link "CO_AND" 0} (@{"ASCII" link "CO_ASCII" 0} @{"OR" link "CO_OR" 0} @{"FIND" link "CO_FIND" 0} 40,"@Database") File name must end with ".guide". Also an ASCII or an "@Database" within the first 40 bytes is required, to succeed this file type. This example is the equal to "a*(b+b)" @{b}IMPORTANT:@{ub} ° Make sure that all brackets are closed. A missing bracket causes the file type to fail. ° File types are always solved inside out! @endnode @node "PATTNAME" "Pattern: Name/M" @toc "AView" @{b}Name/M@{ub} -------- "Name" defines the name of the file you want to view. The "/M" means that AView is able to process as much filenames as possible. Every file name is able to handle DOS pattern matching : E.G "#?.gif" Examples: AView #?.gif AView Smurf.jpg PapaSchlumpf.gif #?smurf#? You are allowed to specify an path as well: AView sys:pictures/smurfs/Papa.gif sys:Pictures/old/A500.pic There are no limits. @endnode @node "PATTALL" "Pattern: All/S @toc "AView" @{b}All/S@{ub} ------- "All" allows to scan all sub directories. @endnode @node "PATTARG" "Pattern: ARG=To=From/K" @toc "AView" @{b}ARG=To=From/K@{ub} ------------- "ARG", "To" or "From" are very useful. This element will replace the @{"%a" link "AP_Edit_PreDefine"} string. For example "lha": "LHA x -M -X %n %a" @{"%n" link "AP_Edit_Command"} will be replaced by the name specified with the @{"name" link "PATTNAME"} pattern. @{"%a" link "AP_Edit_PreDefine"} is normally replaced by "t:". This means AView is. decrunching an lha file to "T:". You are able to specify the @{"default %a" link "AP_Edit_PreDefine"} argument separately for each file type. So "AView Dummy.lha ARG ram:" will decrunch the file "Dummy.lha" direct to "ram:". @{b}Important: To use this %a mode one of the following key words is required: ARG, To or From@{ub} Examples: @{b}AView BoulderDäsh.lha to ram:@{ub} This example will decrunch the archive "BoulderDäsh.lha" to "ram:" @{b}AView BoulderDäsh.lha from ram:@{ub} The result of this example is exact like the first. It looks stupid, because we decrunch to "RAM:" and not from! @endnode @node "PATTSC" "Pattern: SetComment=SC/S" @toc "AView" @{b}SetComment=SC/S@{ub} ----------------- "SetComment" or "SC" is switching AView into the marking mode. All files will be scanned and the result will be written into the file comment. @{b}AView is not able to start any commands during this mode!@{ub} @endnode @node "PATTSD" "Pattern: ShowDetect=SD/S" @toc "AView" @{b}ShowDetect=SD/S@{ub} ----------------- "ShowDetect" or "SD" is viewing the file type of any file. @{b}AView is not able to start any commands during this mode!@{ub} @endnode @node "PATTDEBUG" "Pattern: Debug/S" @toc "AView" @{b}Debug/S@{ub} --------- "Debug" shows any problems during file identification. This switch is not useful for normal users. At this moment AView is only able to view unknown commands and syntax errors. @endnode @node "AP_Main" "The AView preferences" @{b}The AView Preferences@{ub} ----------------------- The AView preferences program allows to modify all file types and the action behind. AViewPrefs supports @{"menu" link "AP_Menu"} functions as well. @{" " link "AP_Main_Sortby"} Sort by @{" " link "AP_Main_Name"} Name @{" " link "AP_Main_Select"} Select @{" " link "AP_Main_Delete"} Delete @{" " link "AP_Main_All"} All @{" " link "AP_Main_New"} New @{" " link "AP_Main_Save"} Save @{" " link "AP_Main_Use"} Use @{" " link "AP_Main_Abort"} Abort @endnode @node "AP_Main_SortBy" "Gadget: Sort by" @toc "AP_Main" @{b}Sort by@{ub} --------- @{b}This Gadget is only available during @{"expert mode" link "AP_Sett_Expert"}@{ub} This gadget allows to sort all entries by name or sub class. Under normal conditions all entries are sorted by name. AView is processing all entries by @{"sub class" link "AP_Edit_SubClass"}. If you have created own file types, sorting all entries by @{"sub class" link "AP_Edit_SubClass"} is useful to find problems. @endnode @node "AP_Main_Name" "Gadget: Name" @toc "AP_Main" @{b}Name@{ub} ------ This list contains all file types AView is able to detect. Use @{"select" link "AP_Main_Select"} and if needed @{"New" link "AP_Main_New"} to define new entries. You are able to scroll via cursor keys. Return or double clicking on one entry opens the @{"edit" link "AP_Edit"} window. @endnode @node "AP_Main_Select" "Gadget: Select" @toc "AP_Main" @{b}Select@{ub} -------- This gadget opens a @{"select" link "AP_Main_GeLw"} window. It allows to select one of the pre defined identifier. @endnode @node "AP_Main_Delete" "Gadget: Delete" @toc "AP_Main" @{b}Delete@{ub} -------- This gadget deletes the actual identifier. @endnode @node "AP_Main_All" "Gadget: All" @toc "AP_Main" @{b}All@{ub} ----- All pre defined file types will be added to your prefs list. Already existing entries won´t be modified. @endnode @node "AP_Main_New" "Gadget: New" @toc "AP_Main" @{b}New@{ub} ----- @{b}This Gadget is only available during @{"expert mode" link "AP_Sett_Expert"}@{ub} You are able to define complete new entries (file types). Just enter a name and AViewPrefs will add your entry to the list. @endnode @node "AP_Main_Save" "Gadget: Save" @toc "AP_Main" @{b}Save@{ub} ------ This adjustments will be saved and the requester will be existed. @endnode @node "AP_Main_Use" "Gadget: Use" @toc "AP_Main" @{b}Use@{ub} ----- All adjustments will be used will be existed. @endnode @node "AP_Main_Abort" "Gadget: Abort" @toc "AP_Main" @{b}Abort@{ub} ------- Cancels all adjustments and quit requester. @endnode @node "AP_Edit" "The Edit Window" @toc "AP_Main" @{b}The Edit Window@{ub} ----------------- This window allows all adjustments of the file types. @{" " link "AP_Edit_Name"} Name @{" " link "AP_Edit_Class"} Class @{" " link "AP_Edit_SubClass"} Sub Class @{" " link "AP_Edit_ExecType"} Exec type @{" " link "AP_Edit_Stack"} Stack @{" " link "AP_Edit_Command"} Command @{" " link "AP_Edit_CurrentTyp"} Current Type @{" " link "AP_Edit_CurrentDir"} Current Directory @{" " link "AP_Edit_WBOutput"} WB Output File @{" " link "AP_Edit_CLIOutput"} CLI Output File @{" " link "AP_Edit_Identifier"} Identifier @{" " link "AP_Edit_PreDefine"} Default %a @endnode @node "AP_Edit_Name" "Gadget: Name" @toc "AP_Edit" @{b}Name@{ub} ------ This defines the name of this file type. Do not define a name twice, because this could cause problems with later versions. @endnode @node "AP_Edit_Class" "Gadget: Class" @toc "AP_Edit" @{b}Class@{ub} ------- @{b}This Gadget is only available during @{"expert mode" link "AP_Sett_Expert"}@{ub} This Gadget allows to specify the type of the current file type. If you don´t find a match you should use the type "User". At the moment this class is used for output and sorting only. Please define this class correct to be on the save side. @endnode @node "AP_Edit_SubClass" "Gadget: Sub Class" @toc "AP_Edit" @{b}Sub Class@{ub} ----------- @{b}This Gadget is only available during @{"expert mode" link "AP_Sett_Expert"}@{ub} This is the most important gadget. It specifies where to insert this file type. A file detected by name only is not as save as a detection by contents. This means a file detected by name only should be checked at the end of the list. Just think about an lha file that is named "archive.c". This file may be interpreted as an c source if the sequence of an file identifier is not correct. I defined some classes my name: User: This class is used for user defined file types. You should use one of the other types. Normal: Under normal cases this is the best selection for new cases. Medium: This class is used for groups, (Kickstart - global, Icon - global) because it doesn`t make any sense to check a single Kickstart after a global definition. xxx or name: e.g. "(FIND "" OR NAME "#?.htm(l|)") AND ASCII" This is better than "Name and ASCII", but not as good as "Medium", because a file may not contain ""! Name and ASCII: This is reserved for file types that are only identified by name and ASCII. Name only: Checking a file by using only a name is one of the worst methods, but sometimes there is no other choice. So this is reserved for name only file types. @{b}Do not use the other classes, if not necessary.@{ub} If you create file types missing in AView defaults, then please send me your the prefs file. @{b}By the way:@{ub} It is possible to use the menu @{"open" link "AP_Menu_Open"} function to load the "Data/AView.data" file. This file contains all pre defined file types. Save this data by using the menu @{"Save as" link "AP_Menu_SaveAs"}. Be careful a wrong modification and AView isn`t working correct. Create a backup of this file before changing the files contents. @endnode @node "AP_Edit_ExecType" link "Gadget: Exec Type" @toc "AP_Edit" @{b}Exec Type@{ub} ----------- This Gadget allows to specify the way AView is starting the @{"command" link "AP_Edit_Command"}. Under normal conditions this is the CLI mode, but some programs may depends on an start via Icon. @endnode @node "AP_Edit_Stack" "Gadget: Stack" @toc "AP_Edit" @{b}Stack@{ub} ------- Each @{"command" link "AP_Edit_Command"} needs an amount of stack memory. Normally 8192 Bytes should be enough. If the program crashes increase this value. @endnode @node "AP_Edit_Command" "Gadget: Command" @toc "AP_Edit" @{b}Command@{ub} --------- If AView detects a known file type, it will start this command. You should take a look on the following % commands. %p : includes the path of the file specified by @{"name" link "PATTNAME"}.(e.g "SYS:Pictures/") %~p : like %p! No "" this time. %n : includes the file name of the file specified by @{"name" link "PATTNAME"}. (e.g "smurfs.gif") %~n : like %n! No "" this time. %f : The complete file name of the file will be included. (e.g. "SYS:Pictures/Smurf.gif") %~f : like %f! No "" this time. %a : This will be replaced by an @{"Arg" link "PATTARG"}. The default value may be modified by using the @{"Default %a" link "AP_Edit_PreDefine"} Gadget. %~a : like %f! No "" this time. There are only four command patterns (p,n,f,a). If you include an ~ after the % this means `insert no ""` @{b}If this command is processed during WB mode all % patterns will be removed. The only exclusion is the %a (%~a) pattern.@{ub} @{b}If you need a "%" in your command then use "%%"! AView replaces them to one "%"!@{ub} @endnode @node "AP_Edit_CurrentTyp" "Gadget: Current Type" @toc "AP_Edit" @{b}Current Type@{ub} -------------- This Gadget allows to specify a dos command feature that is called "Current Dir". It works like the DOS-CD command. File directory : Makes a CD to the path of the identified file. Current : No Change! Specified Dir : The Path is defined by the @{"CurrentDir" link "AP_Edit_CurrentDir" Gadget. @endnode @node "AP_Edit_CurrentDir" "Gadget: Current Directory" @toc "AP_Edit" @{b}Current Directory@{ub} ------------------- This Gadget is only available if the @{"Current Type" link "AP_Edit_CurrentTyp"} gadget is switched to "specified directory"! @endnode @node "AP_Edit_WBOutput" "Gadget: WB Output File" @toc "AP_Edit" @{b}WB Output File@{ub} ---------------- Any Output of the @{"Command" link "AP_Edit_Command"} will be directed to the file specified by this gadget. This redirection is only valid if AView is running via workbench. (Double click on AView icon or Toolmanager is starting AView in WB Mode) @endnode @node "AP_Edit_CLIOutput" "Gadget: CLI Output File" @toc "AP_Edit" @{b}CLI Output File@{ub} ----------------- Any Output of the @{"Command" link "AP_Edit_Command"} will be directed to the file specified by this gadget. This redirection is only valid if AView is running via CLI. @endnode @node "AP_Edit_Identifier" "Gadget: Identifier" @toc "AP_Edit" @{b}Identifier@{ub} ------------ @{b}This Gadget is only available during @{"expert mode" link "AP_Sett_Expert"}@{ub} It a very important gadget. It is the heart of the AView file recognition system. This is done by some @{"commands" link "COMMAND"}. @endnode @node "AP_Edit_PreDefine" "Gadget: Default %a" @toc "AP_Edit" @{b}Default %a@{ub} ------------ This is the default for the @{"%a" link "AP_Edit_Command"} pattern of the @{"command" link "AP_Edit_Command"} gadget. The contents of this gadget will be used, if no other argument is specified by the @{"AView Dos Command" link "AView"} @endnode @node "AP_GeLW" "The File Type Selection" @{b}The File Type Selection@{ub} ------------------------- This window is viewing all default file types of @{"AView_Prefs" link "AP_Main"}. This list is sorted by file classes, so it is easy to configurate AView. Use the Cursor keys to select an entry and select via return key. You are also able to use the mouse and double click to select. @endnode @node "AP_Sett" "The Settings of AViewPrefs" @{b}The Settings of AViewPrefs@{ub} ---------------------------- It is easier than it sounds. This window allows to modify some AViewPrefs internal Features. These settings have no effect on AView. @{" " link "AP_Sett_Expert"} The expert mode @{" " link "AP_Sett_Save"} Save @{" " link "AP_Sett_Use"} Use @{" " link "AP_Sett_Abort"} Abort @endnode @node "AP_Sett_Expert" "Gadget: Expert Mode" @toc "AP_Sett" @{b}Expert Mode@{ub} ------------- This gadget should be used by expert users only. It enables an special expert mode. This mode enables hidden gadgets to make additional adjustments to your configuration. @{b}You should understand the priority controlled file recognizing system and it is important that you understand the main problem behind.@{ub} For me the author it isn´t easy to find error in the pre defined file types. This means it won´t be easy for you. @endnode @node "AP_Sett_Save" "Gadget: Save" @toc "AP_Sett" @{b}Save@{ub} ------ All settings made in this window will be saved and this requester will be closed. @endnode @node "AP_Sett_Use" "Gadget: Use" @toc "AP_Sett" @{b}Use@{ub} ----- The settings will be used. @endnode @node "AP_Sett_Abort" "Gadget: Abort" @toc "AP_Sett" @{b}Abort@{ub} ------- The old settings will be restored. @endnode @node "AP_Menu" "The menus of AViewPrefs" @{b}The menus of AViewPrefs@{ub} ------------------------- These are the menu items of AViewPrefs: @{b}Project@{ub} @{" " link "AP_Menu_Open"} Open... @{" " link "AP_Menu_SaveAs"} SaveAs... @{" " link "AP_Menu_Quit"} Quit @{b}Default@{ub} @{" " link "AP_Menu_ResetToDefault"} Reset to Default @{" " link "AP_Menu_LastSaved"} Last Saved @{" " link "AP_Menu_Restore"} Restore @{b}Preferences@{ub} @{" " link "AP_Menu_AViewPrefs"} AView Prefs @endnode @node "AP_Menu_Open" "Menu: Open" @toc "AP_Menu" @{b}Open@{ub} ------ This item allows to load a prefs file. @{b}The current settings will be lost!@{ub} @endnode @node "AP_Menu_SaveAs" "Menu: SaveAs" @toc "AP_Menu" @{b}SaveAs@{ub} -------- This item allows to save the prefs file. @endnode @node "AP_Menu_Quit" "Menu: Quit" @toc "AP_Menu" @{b}Quit@{ub} ------ Quit AView prefs and cancel all modifications. @endnode @node "AP_Menu_ResetToDefault" "Menu: Reset to Default" @toc "AP_Menu" @{b}Reset To Default@{ub} ------------------ The file type list will be cleared a set to the default entries. @endnode @node "AP_Menu_LastSaved" "Menu: Last Saved" @toc "AP_Menu" @{b}Last Saved@{ub} ------------ This menu point forces an reload of the last saved preferences. @endnode @node "AP_Menu_Restore" "Menu: Restore" @toc "AP_Menu" @{b}Restore@{ub} --------- This menu point forces an reload of the last used preferences. @endnode @node "AP_Menu_AViewPrefs" "Menu: AView Prefs" @toc "AP_Menu" @{b}AView Prefs@{ub} ------------- This menu will open the @{"AViewPrefs-preferences window" link "AP_Sett"}. @endnode @node "AVDeficons" "AVDeficons" @{b}AVDeficons@{ub} ------------ @{" " link "AVDIntroduction"} Why AVDeficons is useful? @{" " link "AVDFeatures"} AVDeficons Features? @{" " link "AVDInstall"} How to install AVDeficons! @{" " link "AVDIcons"} Own Icon Definition. @{" " link "AVDProblems"} AVDeficon Problems. @endnode @node "AVDIntroduction" "Why AVDeficons is useful?" @toc "AVDeficons" @{b}Why AVDeficons is useful?@{ub} --------------------------- AVDeficons is a small but internal very @{"komplex" link "AVDComplex"} Program. You are able to specify an default icon for every file type. In addition to that AVDeficons supports many more very useful @{"Features" link "AVDFeatures"}. @endnode @node "AVDFeatures" "AVDeficons features" @toc "AVDeficons" @{b}AVDeficons Features@{ub} --------------------- ° No configuration required. Just create or get icons you want to use. Thats all. ° Default icons for each file type and file type class. ° Default icons for each directory name. (libs, docs) ° Default icons for disks based on: file system, device ° Additional disk icons for "BUSY", BAD" and "NDOS" ° Icon positions are freed automatically. ° Workbench is switched to "view icons and all files". ° Drawer sizes are adjusted automatically @endnode @node "AVDInstall" "AVDeficons Installation" @toc "AVDeficons" If you have switched off "AVDeficons" during installation you should do this now: 1. The Best Solution You should take the original archive and install AView again. This time install AVDeficons. Your configuration will stay unchanged. After installation process reset your system and AVDeficons is working. 2. The Advanced Solution Use you favourite text editor and load "s:user-startup". There you will find a line ";END AView". Insert "AVDeficons" right before this line. After restarting your system and AVDeficons is working. @endnode @node "AVDIcons" "Own Icon Definition" @toc "AVDeficons" @{b}Own Icon Definition@{ub} --------------------- Create icons by using your favourite Editor (e.G "IconEdit") or just get them out of the several icon collections on Aminet. AVDeficons allows you to specify 3 types of icons. @{" " link "AVDDrawer"} Drawer Icons @{" " link "AVDDisk"} Disk Icons (Status, Device, Dos Type) @{" " link "AVDFile"} File Type Icons @endnode @node "AVDrawer" "Drawer Icons" @toc "AVDeficons" @{b}Drawer Icons@{ub} -------------- This icons are my absolute favourit. I think you know this beautoful drawer icons. Each is containing a little picture to show the type of it contents. This is good, but if you install a new program, there are the same drawers and you have to install your picture icons manually. Exactly this is now AVDeficons´ job. For example take the "libs" drawer. Get the Icon you want to use for all drawers named "libs" and copy it to the "Deficons/drawers" drawer. The icons it self must be named "def_libs.info". That´s all. ("DefIcons/drawers/def_libs.info") @{b}All "Libs" drawers will get this icon, except the have there own real icon@{ub} @endnode @node "AVDisk" "Disk Icons" @toc "AVDeficons" @{b}Disk Icons@{ub} ------------ This feature allows to define all disk based icons. If you want to define a disk icon copy it to "Deficons/disk/". @{b}AVDeficons is using this icons only, if there is no disk icon on disk.@{ub} Examples: def_busydisk.info ;Disk not ready (df0:BUSY) def_ndosdisk.info ;No DOS disk def_baddisk.info ;Bad Disk def_dos2disk.info ;"DOS2" disk format def_dosxdisk.info ;no specific "DOS" disk format def_kickdisk.info ;Kickstart disk def_msddisk.info ;MS-DOS Disk def_cd0disk.info ;CDROM def_df0disk.info ;Disk in "df0:" def_dfxdisk.info ;Disk in "df0:", "df1:", "df2:" or "df3:" @endnode @node "AVFile" "File Icons" @toc "AVDeficons" @{b}File Icons@{ub} ------------ File icons are a special feature of AVDeficons. It takes the predefined file types of @{"AViewPrefs" link "AP_Main"} as identification base. There is no configuration needed. Just create as much icons you want. The icon destination drawer for file icons is "DefIcons/File/". So if you want to create an file icon for "LHA", the correct name is "def_lha.info". Easy isn´t it? @{b}Note: Spaces, ":" and "/" must not specified within icon definition@{ub} If AVDeficons isn´t able to find an file icon (e.G "def_lzx.info") it is searching for it´s class icon. The class name for "lzx" is "archive", so AVDeficons is searching for "def_archive.info". Another example: If there is no "def_Guide.info" file, AVDeficons is using the class icon "def_text.info". @{b}Node: Class icons are named english always!! (Text, Archive, Database, Diskimage, executable, ...)@{ub} @endnode @node "AVDComplex" "AVDeficons and the Problems behind!" @toc "AVDeficons" @{b}AVDeficons and the Problems behind!@{ub} ------------------------------------- Simple start and some patches are loading the icons. It looks so easy. But it isn´t. 6 Patches are needed to make this mirrical AVDeficons. The biggest problem is, that the AmigaOS is using the icon.library direct. This makes it impossible to scan what file icons is needed, so the dos.library is patched, too. Another problem is that AVDeficons won´t work on future versions of Amiga Systems. At the moment all versions since 2.0 are supported. To support Kick2.x there was already a little adjustment needed. If you think You are able to write such program, then try. I want to see the "very simple" drawer icons, too. (-8 @endnode @node "AVDProblems" "Problems by using AVDeficons" @toc "AVDeficons" @{b}Problems by using AVDeficons@{ub} ------------------------------ ° It is not possible to use "DefIcons" from the NewIcons-Archive together with AVDeficons. You should remove "Deficons" before using "AVDeficons". ° New Kickstarts (>3.1) won´t work, if there are any Workbench changes. ° "Drag and Drop" copy is viewing the default system drawer icon and not you special icon. At the moment I do not know how to to fix this problem. ° If you open a drawer (2.) within a drawer (1) and you are refreshing the upper (1) drawer all icons are shuffled around. At the moment I do not know how to to fix this problem. ° AVDeficons is not viewing you icon set: If you have specified a special @{"Icon-Drawer" link "AVDPattern"} check this path. You should be aware that AVDeficons is using some icons before others. So "disk/def_dfx.info" isn´t working for "df0:", if a "Disk/def_df0.info" icon is specified. @{b}AVDefIcons won´t replace icons!! AVDeficons is creating new fake icons only if no icons are available.@{ub} "File/def_archive.info" won´t be used for an Lha file until you delete "file/def_lha.info". ° AVDefIcons isn´t starting You @{b}must not install the AView.library@{ub} to you "libs:" drawer. @endnode @node "AVDPattern" "AVDeficons Template" @toc "AVDeficons" @{b}AVDeficons Template@{ub} --------------------- Deficons IconPath,Wait/S,NoFreeIcons=NFI/S,NoShowIcons=NSI/S NoDrawerReSize=NDR/S @{b}IconPath@{ub} Default: "Deficons/" This argument allows to specify an new icon storage directory! It is required to create the sub drawer. ("Path/File/", "Path/Drawer/", "Path/Disk/") @{b}Wait/S@{ub} Under normal circumstances AVDeficons is returning to DOS immediately. This switch forces AVDeficons to wait for "CTRL C". If AVDeficons isn´t reacting on the "CTRL C" break command there are other patches blocking the unpatch process. You must remove this patches first. In normal cases these patches are executed when AVDeficons was already running. @{b}NoFreeIcons=NFI/S@{ub} All "def_#?" icon positions are freed automatically. If you specify this switch AVDeficons won´t modify any icon position. @{b}NoShowIcons=NSI/S@{ub} By default AVDeficons is switch all "drawer/def_#?" icons to view "all files as icons", so it isn´t required to store this information within every "def_" drawer icon. This switch is used to disable this feature. @{b}NoDrawerResize=NDR@{ub} Drawer sizes are patched by default. This may no in your interest, so this pattern allows you to switch this of. @endnode @node "FAQ" "Frequently ask Questions" @{b}Frequently ask Questions@{ub} -------------------------- @{" " link "FAQStartProblem"} AView and AViewPrefs doesn`t run! @{" " link "FAQNoOnlineHelp"} The online help isn`t working! Why? @{" " link "FAQOnlineEnglish"} The online help is english only. @{" " link "FAQSpeed"} AViewPrefs sometimes is very slow. @endnode @node "FAQStartProblem" "AView and AViewPrefs aren`t running" @toc "FAQ" @{b}AView and AViewPRefs aren`t running@{ub} ------------------------------------- The OS2.1+ or OS3.0+ version of AView require special catalog files. These files contain all text information these programs need during operation. You will find the english catalog files in "AView/Catalogs/english/AView.catalog". It is not allowed to move a AView. This means after installing all file must stay on there place. This is needed, because AView and AViewPrefs must be able to find special files like "Data/AView.Data", "Prefs/AView.prefs" and so on. @endnode @node "FAQNoOnlineHelp" "The online help isn`t working! Why?" @toc "FAQ" @{b}The online help isn`t working! Why?@{ub} ------------------------------------- AView is using the "locale.library" and the locale settings. If the system is running in english you need the english guide file. In addition to that the "AmigaGuide.library" is required. @endnode @node "FAQOnlineEnglish" "The online help is english only." @toc "FAQ" ° The online help is english only. If you are using OS2.0 you should copy your german guide file from "docs/deutsch" to "docs/english": CD sys:tools/AView/Docs copy deutsch/aview.guide english/ There is no "deutsch/Aview.guide"? Then you disabled the german documentation during AView installation. The easiest solution is to install AView again. (AView.install recognises the pre install and is switching to an update mode) @endnode @node "FAQSpeed" "AViewPrefs sometimes is very slow." @{b}AViewPrefs sometimes is very slow.@{ub} ------------------------------------ This is normal. AViewPrefs is sorting his data file and your preferences by name. The Sorting procedure takes some seconds. During the save operation AView is sorting you preference by @{"sub class" link "AP_Edit_SubClass"}. After saving all entries are resorted by the mode specified in the @{"sort by" link "AP_Main_SortBy"} gadget. This is required because AView needs the settings sorted by @{"sub class" link "AP_Edit_SubClass"} to process them correct. This procedure is better than let AView sort every time. You are able to test the sorting speed by using the @{"expert mode" "AP_Sett_Expert"}. This will activate the @{"sort by" link "AP_Main_SortBy"} gadget. Use the @{"all" link "AP_Main_All"} gadget to see how fast is you computer. (-8 @endnode