| Prompt Help |
| QTIPS - Improved Menu Help 1 |
| QTIPS - Improved Menu Help 2 |
| @ATTACK - @Macro.Hex |
| Playing with Scan Codes |
| Uncommon Knowledge - WC_Detail_Help% |
| Uncommon Knowledge - WC_Protect_Help% |
| File Variables |
| Argument passing - Subroutines and Functions - Mike Pope |
| RevTech Replies - Mike Pope (RevTech UK Ltd) |
| Symbol Table Structure |
| A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd |
| QTIPS - Standardising Error Message Display |
| @ATTACK - @File.Error |
| @ATTACK - @File.Error.Mode |
| QTIPS - Standardising Error Message Display |
| Version 3 Technical Highlights - ValidateName |
RevMedia FKB
| Document | V3I8A6 |
| Title | QTIPS - Standardising Error Message Display |
| Keywords | MSG MESSAGE OSBREAD OSBWRITE STATUS OSERROR @FILE.ERROR BFS |
| Text | Developers keen to apply consistent standards when creating applications have been aided by the introduction of FSMSG which can be used for reporting on all BFS file i/o PROBLEMS Unfortunately it does not help when errors are encountered USING standard OS functions such as OSBREAD and OSBWRITE which return error status in the STATUS() variable An undocumented routine called OSERROR can be used to convert the STATUS() value into a meaningful @FILE ERROR message suitable for use WITH FSMSG The routine takes four parameters as follows Call OSERROR ( Unknown Environment File Status ) where Unknown seems not to be used Environment contains a literal to include in error messages indicating the environment originating the error (E G DOS/ MSDOS) File contains the filename to include in the error message and Status contains the error status generated by the i/o action Sample usage follows Osbread Chunk FROM Os_File At X Length 60000 If Status() Then Status = Status() Call Oserror("" "DOS" File Status) Call Fsmsg() End (Volume 3 Issue 8 Page 9) |
Page last modified: 31/01/03