Reader's Clinic - AREV Runtime
QTIPS - Compiling Work around on runtimes
QTIPS - Runtime Version
V119 - Part I
V119 - Part II
VERBatim - V121
Utility Diskette # 3 - Part I
SecureUser
VERBatim - V25
@ATTACK - @Files.System
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
REVMEDIA Revisted
File Variables
Argument passing - Subroutines and Functions - Mike Pope
RevTech Replies - Mike Pope (RevTech UK Ltd)
Symbol Table Structure
RTP Series - RTP42
RTP Series - RTP51
Reader's Clinic - AREV Runtime
@ATTACK - @PDisk.On
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
AREV Comes to Czechoslovakia Les Palenik, Cosmotron Systems
Reader's Clinic - Naming Routines
Reader's Clinic - Prompting for Passwords
Reader's Clinic - Removing "Searching Cross References" Message
Message
Trapping Message Calls
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
QTIPS - Standardising Error Message Display
QTIPS - Interrupt Proof Error Messages
QTIPS - Improving the Message Window
Version 3 Technical Highlights - New Message Types
@ATTACK - @Modal
Reader's Clinic - Page Marks in Windows

RevMedia FKB

DocumentV3I1A9
TitleQTIPS - Runtime Version
KeywordsRUNTIME
BITAND
TextDevelopers writing for distribution on Runtime versions may want to restrict
use of certain routines to only those users possessing a full development
version

This sort of information is stored in a system variable called RUNTIME() To
check whether the version of AREV running currently is runtime just BITAND
the variable WITH 2048 To maintain consistency WITH the AREV way of doing
things to deny access to things on a runtime use the same message RevTech
use i e


IF BITAND(RUNTIME() 2048) ELSE CALL MSG(140 '' '' '')


(Volume 3 Issue 1 Page 15)
[revmedia/copyrigh.htm]

Page last modified: 30/01/03