| RTP Series - RTP17 |
| QTIPS - PERFORM Arguments and FMT Specifications |
| What's New (and un(der)documented!) In 2.12 |
| Playing with Scan Codes |
| QTIPS - Compiling Protection Code |
| QTIPS - Invalid Code and Command |
| QTIPS - Code/Command Help |
| Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd) |
| QTIPS - Command Line Options |
| QTIPS - Invalid Code and Command |
| QTIPS - Code/Command Help |
| Utility Diskette # 4 |
| SecureUser |
| VERBatim - V25 |
| @ATTACK - @Files.System |
| Advanced Revelation Initialisation Sequence (Overview) by Mike Pope |
| REVMEDIA Revisted |
RevMedia FKB
| Document | V3I6A7 |
| Title | QTIPS - TCL Disabled |
| Keywords | TCL DISABLE MACRO |
| Text | As developers it can occasionally be embarrassing to be caught on client's site requiring TCL access but WITH the TCL key disabled In older releases the solution was simple just Ctrl Break and EXECUTE at the debugger However this loophole has (thankfully) been stopped Another technique which still works IF CREATION OF MACROS HAS NOT BEEN DISABLED is to invoke the Macro Window WITH Alt M Create a dummy macro set and assign Alt 1 a code of E and no command Pressing Alt 1 will then invoke a TCL window To block this loophole into the system simply disable the creation of macros in the environment (Volume 3 Issue 6 Pages 7 8) |
Page last modified: 31/01/03