In order for this site to work correctly, and for us to improve the site, we need to store a small file (called a cookie) on your computer.
By continuing to use this website, you agree to our cookies and privacy policy.
  
Home page Home page Home page Home page
Pixel
Pixel Header R1 C1 Pixel
Pixel Header R2 C1 Pixel
Pixel Header R3 C1 Pixel
Pixel

A RevTechie Replies - Mike Pope - Revelation Technologies (UK) Ltd

Commenting on Vol 3 Issue 7 - RTP5 and RTP51

The explanation in Volume 3 Issue 7 of how to access RTP51 files suffers slightly in that it allows access to the REVERROR file only from within your own program, and not for example from the editor. On the assumption that REVMEDIA readers might find it useful to do something besides simply display the error messages, I've taken the liberty of attaching the code you could use to go through the "cumbersome" process of creating permanent access to the file (under the nom d'AREV of ERRORS) and not incidentally, allow you to use some proper tools to hack about with the error messages. Remember though BACKUP THE WHOLE DOS FILE BEFORE PLAYING WITH IT!


0001   /*
0002    program  MAKE_ERROR_VOL
0003    author   Mike Pope, RT(UK) Ltd
0004    date     22nd December 1991
0005    desc     creates a volume by which the REVERROR file can be accessed w/in
0006             AREV as the ERRORSfile
0007   */
0008   $INSERT INCLUDE, FILE.SYSTEM.EQUATES
0009   DECLARE SUBROUTINE RTP51
0010   PATH = DRIVE()
0011   FILE = "ERRORS*GLOBAL"
0012   REC = "REVERROR.0"
0013   BFS = "RTP51"
0014  
0015   RTP51(INSTALL,BFS,"","","","",STATUS)
0016   RTP51(CREATE.MEDIA,BFS,"",PATH,"","",0)
0017   RTP51(OPEN.MEDIA,BFS,"",PATH,"",HANDLE,STATUS)
0018   RTP51(WRITE.MEDIA,BFS,HANDLE,"","",TIMEDATE(),STATUS)
0019   RTP51(WRITE.RECORD,BFS,HANDLE,FILE,"",REC,STATUS)
0020  
0021   OPEN "VOC" TO VOC_FILE THEN
0022    VOL_REC = "VOLUME" ; @FM : "RTP51" : @FM : PATH
0023    WRITE VOL_REC ON VOL_REC, "ERRVOL"
0024   END
0025  
0026   /* and now to make it all worthwhile... */
0027   EXECUTE "ATTACH ERRVOL ERRORS (S)"

%%MOUSEVARS%%

The fourth LC argument, the array, has these differences in real life than documented

     < 8 >     Mouse active
     < 13 >    Mouse type

Suppressing Break-On Columns (Again!)

Am I the only person who knows that you can put anything - anything - into G type items that might otherwise follow the file name?

(Volume 3, Issue 8, Page 4)
Pixel
Pixel Footer R1 C1 Pixel
Pixel
Pixel
Pixel