Autodoc type'os
After the release of AutodocViewer v1.x I received many emails from people complaining
on autodocs that AutodocViewer rejected. Well, it's not my fault that they contain
one or more type'os. It's infact human to do mistakes.
Anyway, here are the autodocs that I have tested and detected the type'os in. You can download
the correct autodocs from this site, if I have the permission from the author to make a
public release of the corrected version.
Permission has been granted from Steffen Haeuser author of rtgmaster and Sam Jordan from
Haage & Partner.
Name of autodoc |
Where I found it |
The type'o and what todo to correct it |
Corrected |
powerpc.doc |
WarpUp_Release40.lha
WarpUp_Release40_Update.lha |
- The function name SetCache68K is missing in the 68k part of Table Of Contents
- The function name GetTaskbyID is missing in the PPC part of Table Of Contents
- The function name RawDoFmtPPC is missing in the PPC part of Table Of Contents
|
Yes |
narrator.doc |
AmigaDeveloper CD v1.1
AmigaDeveloper CD v2.1 |
- The function names OpenDevice and CloseDevice must switch place in the Table Of Contents,
the Table Of Contents do not match the actual function text.
|
Nope |
wizard_end_auto.doc |
StormWizard (Demo) v2.0 |
- All ASCII LINEFEED's in the text have a ASCII CARRIGERETURN ($0D) infront of it, ASCII CARRIGERETURN
are normally not used on Amiga, ASCII LINEFEED ($0A) should be used.
|
Nope |
rtgmaster.ad |
Rtgmaster Developer v42.0 |
- The whole Table Of Contents was missing.
|
Yes |
cybergraphics.doc |
CyberGraphX CD v4 |
- The function WritePixelArray must be moved one step downwards in the Table Of Contents
- The function ExtractColor must be moved in the text array
- The function FillPixelArray must be moved in the text array
- The function GetCyberIDAttr must switch place with GetCyberMapAttr
in the Table Of Contents and in the text array
- The function IsCyberModeID must be moved in the text array
|
Yes |
cgx3dvirgin.doc |
CyberGraphX CD v4 |
- The function --Overview-- must be moved to the top of the text array.
- A FORMFEED are missing at the end of the autodocfile.
- The function V3D_MoveRect must be moved in the function array.
|
Yes |
If you got an autodoc with error(s), please fill the form below. There are some steps that can help you detect an error
in an autodoc, it may take some time to detect all errors.
- Check if the Table Of Contents match the text array of the autodoc. You may find that some of the autodoc functions
described do not exists in the table of contents or that they are not ordered in the same (alphabetically) order as
the table of contents (or visa versa)
- Often there are missing ASCII FORMFEED (0x0c) in the autodoc text, there MUST always be one ASCII FORMFEED behind each
function described in the autodoc text and one after the table of contents. Also some autodocs contains ASCII
ACKNOWLEDGE (0x06) instead of a ASCII FORMFEED
- Each entry in the table of contents must have an entry name with a trailing slash followed by the name of the function.
eg. exec.library/AllocMem or SAD/ALLOCATE_MEMORY both found in exec.doc autodoc file.