File Variables
Argument passing - Subroutines and Functions - Mike Pope
RevTech Replies - Mike Pope (RevTech UK Ltd)
Symbol Table Structure
Merge Processor
QTIPS - Using INIT.VIEW with Printers
@ATTACK - @PDisk.On
QTIPS - DOS File Names
DOS Interfacing (Part II)
VERBatim - V116
@ATTACK - @Pri.File
@ATTACK - @Rollout.File
File Variables
How Indexes Are Updated
Index Record Layouts
QTIPS - File Variable of File In SELECT Statement
QTIPS - Amending non-Attached Files
LINEAR HASH FILE STRUCTURES - Part 1
Index Flush
QTIPS - File Handle Structure
@ATTACK - @PDisk.On
QTIPS - Postscript Driver Problem
QTIPS - Assorted Oddments
A RevTI Techie Replies - Mike Pope - Revelation Technologies (UK) Ltd
QTIPS - Command Line Options
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Utility Diskette # 4
@ATTACK - @PDisk.On
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
What's New (and un(der)documented!) In 2.12
SecureUser
VERBatim - V25
@ATTACK - @Files.System
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
REVMEDIA Revisted
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
Version 2
Directory Exists on Novell
Gas Bar
Prompt Help
DOS Interfacing (Part II)
@ATTACK - @Help.Level
@ATTACK - @StatList
QTIPS - Standardising Error Message Display
Video Control
Customising the Status Line
QTIPS - Testing For Boolean False
QTIPS - Command Line Options
Customising the Status Line
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
Reader's Clinic - Screen Width
Screen Grabber
Reader's Clinic - Slow Multivalued Screen Display
Utility Diskette # 4
VERBatim - V70
VERBatim - V123
VERBatim - V124
QTIPS - Improving the LH_VERIFY Window
@ATTACK - @Modal
Utility Diskette # 4
@ATTACK - @File.Error
@ATTACK - @File.Error.Mode
@ATTACK - @Last.Error
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
RTP5 and RTP51
QTIPS - Standardising Error Message Display
QTIPS - Interrupt Proof Error Messages
Version 3 Technical Highlights - ValidateName
QTIPS - AREV Logon
What Happens At Logon
QTIPS - Undocumented Logon Options
QTIPS - Video Characteristics for Logon Messages
QTIPS - File Naming - RLIST Problems
Reader's Clinic - Changing from LPT1 to LPT2 in RBASIC

RevMedia FKB

DocumentV2I5A8
Title@ATTACK - @PDisk.On
Keywords@PDISK.ON
PDISK
AREV.EXE
PRINTER
TextThis variable is used to check whether printer output has been redirected to
the file by the PDISK command If @PDISK ON is set to 1 this indicates that
the system believes that printer output is directed to file if 0 that
printer output is routed to the printer

With 2 0 AREV EXE was modded so that if the printer is on (PRINTER ON)
every print opcode checks the status of @PDISK ON before it outputs to the
printer If false the system will check to see if a printer is on line and
if not produce a Quit or Retry message on the top line of the screen If
true the system will just output without checking the port assuming that
all output has been directed to disk This is a necessary distinction
because if a printer is not attached printer applications may still be run
using PDISK

Thus if it is required that the printer be checked programmatically before
output is performed programs should be modded as follows

OK = 1
IF @PDISK ON = 0 THEN
* not redirected so check that printer is alright
CALL PRNSTAT(X)
IF X THEN
* NB Not checking for a specific number as these results do
* not always seem to be reliable Just test for the existence
* of any error
OK = 0
END
END
IF OK THEN
GOSUB PRINTOUT
END

Note however that this technique must be used WITH care @PDISK ON is only
set to 0 at logon or when a PDISK PRN is encountered Confusion could result
if a PDISK command was issued to a DOS reserved filename such as LPT2 or
COM1 Under these circumstances @PDISK ON would be set to 1 (as PDISK
considers a redirection to have taken place) which would mean that no
checking would be made before PRINTs were performed resulting in the Abort
Retry Ignore Fail message To avoid this set @PDISK ON to 0
programmatically Can be amended


(Volume 2 Issue 5 Pages 9 10)
[revmedia/copyrigh.htm]

Page last modified: 30/01/03