<\-:::::::::::::::::::-/> (\):> Phantom Access 5.7K <:(/) _____________________________ | | | (C)reated By Lord Digital | |_____________________________| =:=:=:=:=:=:=:=:= [ Introduction: ] =:=:=:=:=:=:=:=:= [%][> *PLEASE NOTE* <][%] The entire Phantom Access series is *NOT* to be distributed. You have a copy of the software because you are a friend or associate of mine. I have no interest in making this software available to the idiots at large, that now constitute almost all computer users (or more correctly `Kuehl dudez!'). *+* *+* ================== [Utility Disk 2.0] ================== The software that accompanies these documentation files, is full disk release number two. This revision contains enhanced utilities as well as a complete editing system for the Phantom Access program itself. Release 2.0 is composed of six sides, contained on three `flippy' diskettes. ^%[> Disk: [A], Side(s): [1] and [2]. <]%^ ^%[> Disk: [B], Side(s): [1] and [2]. <]%^ ^%[> Disk: [C], Side(s): [1] and [2]. <]%^ )=-> Diskette [A1] contains three central programs. Those being: o Phantom Access 5.7K - o PA.Editor o PA.Utils [> Phantom Access 5.7K is the hacker itself. It could be described as the final processing unit of the instruction sets, but without the utilities it would be useless to the end user, as that is ALL it is. Sub-Modules must already exist prior to usage. This was a necessary compromise, as there is NO memory left on a 64K system once the Slider's and Rotation system are activated. |For information on the LAST Phantom Access [6.6], read the closing comments.|  [> PA.Editor is the Sub-Module creation/editing program. With it you can write new Sub-Module's from scratch, or modify existing systems. This allows you to create any Block-Set you wish to implement. To modify the Phantom Access program itself you MUST use the PA.Prog.Ed program, which is available on diskette [B1]. [> PA.Utils are for archiving Status Reports and Code Files, and allow you to manipulate, edit, merge, sort, search for occurrences of (X), rename, purge, and compare either of these file types according to any criteria you choose to use (date, length, comparative systems, Slider in use, etc). )=-> Diskette [A2] contains five documentation files which pertain to the programs found on the opposite side of the diskette (a1). o PA.DOC1 o PA.DOC2 o PA.DOC3 o PA.DOC4 o PA.DOC5 )=-> Diskette [B1] contains: o PA.Prog.Ed and its attendant data files and documentation. This program allows modification of all set variables in Phantom Access that are not user modifiable in normal circumstances or under Slider control, due to memory limitations imposed by the environment the 5.7 system was designed to run under (the ][+, un-enhanced //e, and clones). This also allows minor (10 cycles at peak, or approximately one week of automatic run) ThunderClock compatible clock control when configured for support of the card. NOTE: The Pa.Prog.Ed system allows the creation of ANY Phantom Access system ---- processor from version 5.7(a) to 5.7(z), Including (but not limited to): - RGB control for Taxan monitors. - ThunderClock compatible clock card support for Slider use. - Enhanced character generator and ROM support (Enhanced //e). - SSI201 decoder support. - Complete configuration for DOS 3.3 compatible hard discs. Selecting default settings returns Phantom Access to generic revision K. ALSO: The Processor will change system revisions INTERNALLY only. The file is ---- called `Phantom Access 5.7K' EXTERNALLY at all times, as the other programs are hard coded to interact with that specific filename.  )=-> Diskette [B2] contains: o Spectre and its Slider System links. The Spectre supplied is version 2.0 modified to allow Slider links. It's not the Spectre of 6.6 which could not function on limited systems. The Spectre provided allows user creation of a pattern matching system and fulfills the bare criteria of allowing the user to hack ASCII based systems such as mainframes, bulletin boards, online services, etc. The only documentation provided on side 2 for Spectre; is the minimum needed to allow the user to configure and install the system. Revision 2 never had any documentation written for it, as it was basically a beta version of what became 4.0 and was not originally intended for any use beyond routine testing. Full theory behind operation, functions, editor, etc. appear in the 6.6 documentation. Scaled down documentation and the minimum background information needed to understand pattern matching and other ASCII hacking principles are contained on side [C2]. )=-> Diskettes [C1], and [C2] both contain a synopsis of 6.6 documentation that is relevant to the 5.7 system series. _______________________________________________________________________________ Slider support in the 5.7 series is very limited. All the normal (as per 6.6) creation rules apply, but only ONE Slider may be active at any given time. The complete Slider explanation in the 6.6 documentation should be referred to in you require clarification. _______________________________________________________________________________  ============ [Background] ============ The eventual goal of Phantom Access was to realize a fully automated system for the Apple-Cat modem. The sound sampling and evaluation system has been almost unchanged from revision 4.0 to 5.7 of the series, everything else has been rewritten several times. The final 6.6 revision is a full implementation of the original design (read: it has very little in common with anything in the 5.7 series) with a final processor that is capable of passing data through the Apple-Cat's serial port to an external machine, thus allowing use of the entire Apple computer system as nothing more than a very sophisticated auxiliary modem. This was my solution to working within the Apple's limits. No other modem comes close to having the Apple-Cat's capabilities, but the Apple itself leaves much to be desired. In this manner, a workstation with additional control modules made with an object oriented language more suitable for its task, may be interfaced with with the Apple-Cat. A flowchart for a simple example system follows: 01> Hack #: NPA-ANC-XXXX until you have 25 valid codes. 02> Using the 25 valid codes from step 1 rotatively, scan the exchange of NPA-ANC-XXXX. In this exchange note all systems that connect @ 1200 bps and identify in a manner generally used by the unix system. 03> If it is no later than xx;xx;xx, login to TRW using password x and dialup y and pull reports on all people in file z. If password x is no longer valid try password x1,x2,x3,etc until a valid password is found or backup file is exhausted. 04> If it is no later than xx;xx;xx then look through the dialup's found by the scan in step 02, load the standard unix IS and start a password scan on the system in question. 05> ...Etc. In brief; a series of programs with the same style of syntax, that write and retrieve information from a set of modules whose format is compatible with all other systems within the series. Hence: a acquisition oriented programmable database with infinite capabilities. Using simple commands you can create a custom self running database that will react to a range of internal or external conditions and perform whatever tasks you desire. _______________________________________________________________________________  =============================================== [Phantom Access 5.7K (This disk specifically).] =============================================== Phantom Access 5.7X (X being the hardware specific version you have configured your processor to, with `K' as the default) is the code hacker of the series. It is fully programmable in the sense that you can customize existing (example) Sub-Modules to hack whatever you want them to, or you may just as easily create new modules for complex systems from scratch. A few simple flowcharts: 01> Call MCI 02> Hack code - 01> Call MCI 02> Enter valid code for MCI 03> Call a PBX @ NPA-ANC-XXXX 04> Hack code for PBX. - 01> Call MCI 02> Enter valid code for MCI 03> Call OCC to hack. 04> Hack codes using OCC dialthrough. - 01> Call MCI 02> Enter valid code for MCI 03> Call number NPA-ANC-XXXX 04> Trunk it. 05> K(p (\):> Phantom Access 5.7K <:(/) _____________________________ | | | (C)reated By Lord Digital | |_____________________________| =^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^= [ Hacker Overview / Documentation ] =^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^= ============== [Introduction] ============== Since it is presumed that the user can manage to figure out the main menu on his or her own, the following documentation deals exclusively with the final system processor. Editing the processor is explained in detail on diskette [B1] while the construction of Sub-Modules and usage of the Utility Package are covered after this file. _______________________________________________________________________________ ===================== [Phantom Access 5.7K] ===================== Upon initial program entry you will see the following: (Everything following this, up to the central menu display, assumes that you are in manual control of the processor. If a Slider is activated, none of this will be present, except for the central menu.) [Slot][X] [Drive][X] [Volume][XXX] X(XX) = The Slot, Drive, Volume, you want to direct all further disk access to. Simply typing a carriage return in response to any prompt will set the system to the default of: S6,D1,V000. After a preliminary memory search (to see what is or isn't already there), the program will drop you at its central menu. Selecting a `3' will exec the file `PAX'. Selecting `2' switches applications to the Utility Package, and a `1' jumps to the beginning of the system startup routine. After choosing the first option you will be prompted with a `Sub-Module' to load into memory. This is a text file that must already be present on the disk, and contains the general Block-Set that Phantom Access will be using during this run. Typing will give you a catalog of the current S,D,V.  After typing in the Sub-Module name, assuming the module is found on the S,D,V selected, you will be asked whether you want this to be a random or sequential scan at the C[ode] variable. (If you are using saturation tables, or want a pseudo random number generator instead of true RND, you must do a system edit on the processor. It is also possible to do a call to a specific algorithm at this step, for systems where it is advantageous to do this ie: TravelNet, TelTones, et al. <------------------[Input:]----------------------[Comments:]------------------> -=[> Code To Start Scan At: Enter the code you wish to begin this scan with. It must be equal in length to the code variable specified in this Sub-Module. If it isn't you will be returned back to the previous input. -=[> Random Or Sequential Scan? (R/S):X Do you wish to scan in a random, or sequential order. -=[> Re-Test Valid Codes (Y/N):X Do you want to retest the codes that come up positive, to make certain that the code is good. -=[> Please Enter Current Date, In The -=[> Format of (01/01/85) : [00/00/00] Enter the current date. If you have a ThunderClock compatible clock card you may use the system editor to configure the processor to automatically date stamp files. -=[> Activate (OCC Dial) Option? (Y/N):X Will you be using a OCC Sub-Module for this scan. For complete information on OCC Dial read the appendix in this file. (Answering negative at this prompt will skip the next 3 or 4 input questions.) -=[> Number To Dial-Through: May be any number you select. Input is not checked against any specific length, so make certain you enter the correct number. -=[> Valid Code For OCC: Input a valid code to use on the OCC Dial port. ____________________________________________________________ NOTE: The two previous prompts ask default questions that are valid under most ---- circumstances. However there are times that you might want to add another `Launch Sequence'. You should understand that the previous prompts can in fact perform (254+254=508) 508 separate actions BEFORE even passing the w of control over to the central Block-Set. This is useful when you desire a build up to initial OCC dialthrough connect.  IE: Under a non OCC Block-Set if you want to dial a `9' to get an outside -- line, you'd build the following into the first several blocks: 01> P [Pick-Up/Hang-Up] 02> D9 [Dial]: 9 (To secure the outside line) 03> A [Await Dialtone] (outside dialtone) 04> D1234567 [Dial OCC, or whatever you're calling as normal] People kept asking me to put in another `Dial before Block-Set' prompt. Well it doesn't need one! You aren't thinking it through because it may not be totally obvious, but Phantom Access was the ultimate elegant solution to complex situations, that doesn't require 500 options or a new modification every time system X is encountered, and it requires mod Z. ANY number of actions can be taken in a Block-Set, in ANY order. Or to be exact: 40*254+(2*254)=10668 steps per any Block-Set. And this may be increased even more by Slider and Rotation system use. THUS: 00508 steps may take place BEFORE an OCC Block-Set. ----- 10160 steps may take place DURING an OCC Block-Set. (The actual number of steps available will depend upon which options you have linked in with the System Editor. If there aren't 10160 bytes free in memory while your Slider is in control, or the Rotation System is active, then you obviously cannot enter 10160 steps. The System Editor will tell you exactly how much room you have at any rate.) (Some settling may occur during shipping, this is perfectly normal as the product is sold according to weight, not volume.) So if you wanted to dial a `9' before connecting with the OCC you are using to scan with, all you'd have to do is: -=[> Number To Dial-Through: (Pick-Up occurs as an automatic first step, as does dialtone detect)[9](Dial the 9)[%](The `%' is used for dialtone detect within strings, as the `A' key emits the `A' tone in dialing mode.) Thus: 9%ANCXXXX (OCC) and -=[> Valid Code For OCC: TheCode One more thing that should be made clear: The `Number To Dial-Through', and `Valid Code For OCC' prompts will take the entire string that follows it, as a dialing command. So Dial Mode defaults must be used (commands that can be parsed by the D command character as explained in Document file: pa.doc3).  The `-=[> Number To Dial-Through:' prompt will: a> Test for incoming rings, if the line is not clear, it will clear the line and go offhook. b> Wait for a steady tone on the line. c> Begin parsing YOUR input at this prompt. The `-=[> Valid Code For OCC:' prompt will: a> Wait for a steady tone on the line. b> Begin parsing YOUR input at this prompt. This is much simpler than it sounds at first (like most things). ____________________________________________________________ -=[> Install Maximum Fail Limit?: X Do you want to set a maximum number of times that pound out can fail on the OCC Dial Option. This exists so if the port you are hacking takes itself down or if the hunt pilot keeps assigning you a lousy link, you don't end up being charged for 5000 local calls to it. If you have untimed and unlimited local service, you will not care about this option, it was implemented mainly for people (such as myself) under the NYNEX (RBOC) which has no such thing as unlimited local calls. (Answering negative at this prompt will skip the next input question.) If this failure limit is ever reached the hacker shuts itself down. -=[> Maximum Number of Times Dialtone, -=[> Detect Can Fail on OCC Dial: XX The maximum number of times that pound out can fail. -=[> Is Everything Correct? (Y/N): X Are you ready to begin the scan. If no then you are returned to the original `Start Scan At Code' prompt, if yes the scan begins. _______________________________________________________________________________  The central scan menu will vary depending on what options you have toggled on or off with the system editor. If you are using the generic 5.7K setup it will look like this: =^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^= % )=-> PHANTOM ACCESS [5.7K] <-=( % =/%/%/%/%/%/%/%/%/%/%/%/%/%/%/%/%/%/%/= % (C)opyright 1982-86, Lord Digital % =^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^=^= (Sub-Module Loaded) /:::::::::::::::::::::::::::::::::::::\ : : : [Code File]:[Filename For Save] : : [Now Testing Code]:[012345] : : [Total Codes Scanned]:[1234] : : [Valid Codes Scanned]:[99] : : [Last Valid Code]:[012345] : : : -:::::::::::[System Status]:::::::::::- : : : [SND][PHN][PCN][OCC][RNG][---][SEQ] : : [%][ Current Function Active ][%] : : [Block]:[-] : : [Audio Duration]:[00]:000 : : [Time Left In Audio Test]:[-] : :.....................................: \Type to Exit After Current Code/ Depending on what is happening at any given time, various status bars will pop up to indicate current conditions. Most of this is self explanatory, although the command bar may need a little clarification: [SND]: Lights up when there is sound on the line. [PHN]: Lights up when the phone is offhook. [PCN]: Percentage of codes correct thus far. [OCC]: Lights up when the OCC Dial option is in use. [RNG]: Lights up when an incoming ring is detected. [---]: Current dialing status and lookup mode. [SEQ]: SEQ or RND, depending on the type of scan you are doing. Typing quits after the current code and asks you if you want a status report on the scan that has just taken place. If you do not, the system re-runs itself and places you back at the central menu.  [Note]: Typing will NOT exit if you are under Slider control. If you want ------ to regain local control before final completion you must type ^C. This will bring you to the `Generate Status Report' menu as in normal mode. If you are going to compile the processor, you MUST specify this at the time of modification. The System Editor has to re-calculate certain timing functions, as well as modify several areas of code to remain compatible with the other modules and the compiler itself. You have the option of selecting either Einstein 5.3 (Einstein Corp.), or TASC (Microsoft), to compile the processor. You MUST specify which of these programs you will be using. Upon specification, a `Program Report' will be issued, which will list the EXACT values, that have to be input in answer to the compiler's queries. _______________________________________________________________________________  ========== [Appendix] ========== (OCC Dial Theory): There are many instances where you want to call a system through another system port. You may be hacking a toll dialup through a toll free dialup, or hacking a out of NPA system, or any number of other possibilities. With Phantom Access it is easy enough to chain as many systems as you desire, however upon completion of the current Block-Set when the hacker goes onhook, there is a long delay in order to go through the entire chain again and again after each code test. This is where OCC Dial comes in. You must be using MCI (or any other service that allows you to regain the OCC's dialtone back with a `#') as the initial dialup. When OCC Dial is active Block #1 is replaced by it, so there is only one physical Pick-Up; every other time the hacker cycles through to the Pick-Up/Hang-Up routine it will `pound out' instead. OCC Dial is useful for the following reasons: 01> Speed. Hacking long distance by this method is even faster than hacking local using physical Pick-Up/Hang-Up. When hacking locally, speed is vastly improved. 02> As mentioned before, if you live in an area that offers no flat rate for local calls, this becomes incredibly useful. 03> ESS (DMS, or any digital switch for that matter) can be set up to dispatch a procedure that will `drop trouble cards' when it finds a large number of calls originating from the same number for extended periods. Usually this is not done because more often than not, they will end up with some fellow who was demon dialing his radio station. But for people who don't want any irregularities to appear - no matter what the circumstance happens to be, this is very useful. While nothing usually comes of call volume checks, it is much better not to be a statistic in the first place. If your number comes up month after month, some bored person may decide to see just what is happening over at ANCXXXX. With OCC Dial there is only one outgoing call (or whatever you set your maximum failure limit to (Maximum of 99)) made for the entire scan, instead of the several thousand calls that would be made with every other hacker. NOTE: In the 1986 FCC regulations update, one of the new rules set into ---- existence is the prohibition of using any dialing device that will progress beyond 15 consecutive tries. - I realize most people (myself included) couldn't care less about any FCC ruling, however this does give your local BOC yet another reason to check up on your number.  (If you understand SCC's a really amusing thing to do is to set a fortress to forward to your OCC and dial off of it. Unfortunately fortress' don't last and choke to death on change (fortress murder, tsk tsk). On the bright side ATM's survive indefinitely (for complete information on every type of ATM found in NYC, and how to make them do whatever you want. Pick up my ATM file, or call me for a copy). Either way, this is a very bulletproof way of scanning.) (Maximum Failure Limit): After it has pounded out (#) Phantom Access searches for a dialtone indicating that it can go restart the Block-Set and redial. If no dialtone is found then it will cycle through to a physical hang-up followed by a redial to the OCC and restart from where it left off. Imposing the failure limit tells Phantom Access to shut itself down after the dialtone detect has failed (XX) number of times. Other than all the purely logical reasons to do so, if you have any sense of irony it is quite uplifting to hack MCI through itself. Incidentally an OCC is a [O]ther [C]ommon [C]arrier. Which is AT&T's way of saying LDS. _______________________________________________________________________________  <\-:::::::::::::::::::-/> (\):> Phantom Access 5.7K <:(/) _____________________________ | | | (C)reated By Lord Digital | |_____________________________| =^=^=^=^=^=^=^=^=^=^=^=^=^=^= [ Sub - Module Construction ] =^=^=^=^=^=^=^=^=^=^=^=^=^=^= ====================== [Building a Block-Set] ====================== Each Phantom Access Sub-Module is simply a text file that is loaded prior to hacker execution, and contains the instructions for the actions to be performed during each Block-Set. The following are all valid commands: P, D, H, C, T, R, W, A. [P] - Pick-Up/Hang-Up Step. [D] - Dial Number that follows. [H] - 2600Hz. [C] - Enter the code being tested at this point. [T] - Time delay for (x) seconds. [R] - Reset to Block (x) [W] - Test the code for (x) seconds [A] - Await the presence of a steady tone on the line. [In Depth> P - Hang's up the phone, & if OCC dial is activated passes control to that area of the program in favor of actually hanging up. If it is not active it will 1) Hang up the phone, 2) Test the line status for any incoming calls, if a ring is encountered it will pick up wait 13 seconds, then hang up & wait 30 seconds before attempting to dial out again. (this is to prevent people who call & manage to connect , from interfering with the status of your scan.) 3) once it has a 'line clear' status, it will pick up the phone, and await dialtone, before passing control to the next block. - Usage: P  D - Dial's the number that follows. Valid Numbers include; 0-9,*,#,K(p),S(t),A, B,C,D,W,X,Y,Z,P(ulse),T(one), %, and @. The `%' is used to await a steady tone on the line in D, the `@' will pause for 2 seconds, for whatever reason that you might want to delay between tones. The `%' (dialtone detect) option, is available ONLY in the two prompts that are reserved for `OCC dial.' In every other case you should use the `A' option. - Usage: DXXXXXXXXXXXXXXXXXX - NOTE: When the "K(ey Pulse Forward.)" Dx is selected, all numbers between ---- The K(p) and S(tart) will automatically switch to MF. When the S is encountered dialing changes back to DTMF. IE: H, K(MF)123456789S(DTMF) - ALSO: W,X,Y,Z MUST be defined using the system editor PRIOR to their use. ---- (Format : hertz,hertz / : hertz,0). If you wish to enable P(ulse) & T(one) dialing modes, you must specify this in the system editor as well. When W,X,Y,Z &/or P,T are enabled, dialing switches to `slowdown mode' automatically, as Novation in its infinite wisdom (and cheap hardware design), has managed to cause a great number of timing problems when you switch from tone, to pulse, back to tone again (these problems may be fixed with 3 pieces of wire, and a resistor, or through software slowdown (as has been done for the 5.7 Bmodules)). H - 2600Hz. Self Explanatory. - Usage: H C - Generate code to be tested at this point in the scan. - Usage: C T - Time Loop/Delay. Will delay for (x) seconds. - Usage: TX(XX) / X is the number of seconds to loop. R - Reset to block (x). This is always the final block in a block-set, & tells the hacker what block to pass control to next. - Usage: RX(X) / X is the number of the block to process next.  W - Wait-Test. This is the block that does the actual testing of the code. The specific method used for the code test varies with the options you have setup with the system editor. There is a custom mode (for systems such as Sprint) where you may enter any method you choose. There are also two `standard' modes of code test. - Method 1 (System Default): The code test number is a terminator. A terminator is just a 600 Ohm termination. When in this mode the hacker looks for a LACK of audio. ANY audio will cause the Audio Counter (see below) to increment until the code is declared invalid. An example of a 600 ohm termination: 214-371-2222. NOTE: These are NOT loops, if you start hacking off a loop you are going ---- to get questionable results at best. There are many terminators in every NPA. Several people can even use the same one. The above is a perfect EXAMPLE, I suggest calling it to see what it sounds (or doesn't sound) like and finding one of your own to use. They appear most frequently in the 99XX suffix of most ANC's. It doesn't make any difference whether or not your terminator is local, as the #'s do not supervise. The audio test if used because it's a good deal faster than searching for a carrier, and ANY audio will set it off (whether a siren, eternal ring error message, or as some OCC's are becoming fond of doing: a carrier for 15 seconds after each invalid code. - Method 2: In this case the audio test is the exact reverse. Any steady tone on the line will cause the code to be declared valid (for systems such as TravelNet). - Usage: WX / X is the number of seconds to TEST the code, NOT the Audio Counter... A - Await Dialtone / Steady tone. Waits for a steady tone on the line before going on to the next block. If no tone is found it goes to an error handler and restarts the current cycle. If the number being dialed rings more than 3 times, the audio test is considered a failure. IE: D1234567, A, C is a set of steps, dial: 123-4567, Await dialtone, then enter the code to be tried. If for some reason you get a `all circuits are busy', re-order, or ring, instead of a dialtone, it will declare the audio test a failure. NOTE: The amount of time a steady tone must be continuously present to be ---- considered a dialtone, is 4 seconds. This value is arbitrary and can be modified like most other options using the system editor. - Usage: A  Other variables that MUST be present in each Sub-Module: 1 - Tone Length (Dialing speed, 1 is very fast, 255 is very slow, unless you are on a digital switching system, I wouldn't suggest using anything faster than a setting of 3.) 2 - Name File: Name of the system you are hacking, ie: MCI, SBS, ITT, Billy Joe Jim Bob's Pbx, whatever... 3 - Code File: Name of the file that valid codes are being written to. 4 - Code Length: Length of the codes being hacked. Ie: 5 digits, 8 digits, etc 5 - Slot: Slot of MAIN Apple-Cat board. 6 - Audio Counter: The Audio counter & Block W are complimentary to each other. W is the test codes step, the number following the W is the # of seconds to TEST the CODE. The Audio Counter is set for the maximum ACCUMULATED amount of audio that can be present before the code is declared invalid. A good # to set this to is 5. This is NOT seconds, this value is just a Counter of audio units. For example, you dial the 600Ohm. termination, and now do a W4 (test code for 4 seconds), the AC (Audio Counter) is set to 5, on the way to NPA-ANC-XXXX the phone pop's (1 AC), you encounter some static (3 AC for a total of 4 so far. (Remember: CUMULATIVE.)), & finally you reach the destination number, and start to test the code. The code is good so there is no audio, and the hacker cycles to the next block. Now on a BAD code the Audio Counter will trip very fast (error msg, siren, whatever.) and declare the code invalid, IMMEDIATELY hanging up the phone, and continuing to the next block.  -=[> Putting it all together <]=- Okay, now that 80% of the people who are reading this no longer understand what I'm talking about, an example; _______________________________________________________________________________ P 1] - Hang Up / Pick Up D1234567 2] - Dial #: 123-4567 A 3] - Await OCC's Dialtone. C 4] - Dial code to be tested D1234567890 5] - Dial 600Ohm. Termination W3 6] - Test the code for 3 seconds R1 7] - Reset to block 1 (P) Following is 40 - 7 c/r's. The array that is loaded in as the Block-Set may have a maximum of 40 separate block's. If it takes less then 40 instructions to complete a single blockset then the rest MUST be equal to: "" 's. (The editor takes care of this for you...) 2 1] - Dial Speed MCI 2] - Name of System MCI-Codes.1234 3] - Code file 5 4] - Length of Codes 2 5] - Slot of Apple-Cat 5 6] - Audio Counter _______________________________________________________________________________  The above is a fairly simple Sub-Module, designed to hack a Normal local OCC. The same system could be hacked using the OCC option with 1 or 2 changes; Block 2] - Instead of D1234567, you would dial> DNPA1234567. (Remember you are now dialing THROUGH an OCC and it requires an NPA to precede the number you are hacking.) Block 3] - This varies a great deal, if the connection is good enough, then you can leave it at `A', however, usually what will happen is that the dialtone detect will fail because the dialtone that is coming through is no longer loud enough to be detected. This is where the program reaches the limits of standard Apple-Cat hardware, and without modifications to the Apple-Cat, I cannot solve this problem through software. A 99% effective solution (it has never failed to work for friends that use this software and have normal Apple-Cat's. I can't speak from personal experience though, since my Cats have been modified), is to substitute the `A' with a `T5'. The reason the audio detect on OCC dialthrough fails at times is because; when the Cat first clicks on and encounters the dial tone, it picks up the click. However after the initial click, the dialtone is steady, and the Cat can no longer sample it correctly. This poses no problem on the code and audio tests because the error messages are not steady like the dialtone. IE: --- Audio Counter senses initial click, since dialtone detect is NOT cumulative if the sound isn't steady, the initial click is ignored. | ^^^^^^^^^^^^^^^ Apple-Cat doesn't pick this up ^^^^^^^^^^^^^^ \_/ vvvvvvvvv(3rd generation dialtone xmitted over OCC.)vvvvvvvvv Dialtone: zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz. Error: we'resorrythe. _ _ _ _ / \ / \ / \ / \ | | | | Code test IS cumulative, series of clicks add up & successfully test the code in question. There is no actual `click' between words, or rings or a error siren, but SOME sound (the word following the pause between the recording's words) is louder than NO sound (the pause). _______________________________________________________________________________ For people that are confused, there should be several example (read: fill in blanks) Sub-Modules for a variety of Block-Sets included on side one of the diskette. _______________________________________________________________________________  ============ [Appendix 1] ============ The D(600 ohm termination (in default mode)) command that is inserted towards the end of most Sub-Modules to provide the audio test destination number, isn't always needed. Many OCC's will start an error message after the code + NPA has been dialed. So you can replace the D(Termination) command with an even faster: [Block][XX> D And take an immediate audio check at this point. If you were to do it this way, you should set the W(ait test) to no more than `2', as the OCC's re-order will come on if you pause too long. On a invalid code many OCC's will even let you pound out `#' (Or as some people have recently `discovered' (why this is so shocking, I do not know. As SPC has ALWAYS been reset on 2600hz.) that Sprint can be reset with 2600hz.) and test another code, thus allowing you to stay connected until you find one valid code. Most people just take a program, insert the port # they wish to hack, and then turn the hacker on. This works, but is hardly optimal. For example, as it is in its generic mode, 5.7K is designed to work with GTE and Xbar systems. What this translates to is: low quality phone systems, which cannot handle excessive speeds. If you're on an electronic switch, you should optimize the processor using the System Editor. You can also do a call to your `custom' module if you have configured it, for systems like TravelNet (algorithm), SPC (ever changing 411, 41*, 111, etc), AllNet (`A' tone, `#', etc. Depending on location), et al. While hacking on a `custom' system, you can generate up to 20,000 tries in a 10 hour period. _______________________________________________________________________________ ============ [Appendix 2] ============ One thing I'd like to clear up for the benefit of the more dense concerning the use of 2600 hertz. Electronic systems can be set to detect ANY `foreign' tones present, however `wavering' the tone (as has become popular in some rather amusing, if not functional, recent programs) to distort `pure' 2600hz. does absolutely NOTHING. What the CO detects is `kickback' from the dropped trunk, NOT 2600hz. `Pink noise' does have its uses, but `wavering' the pure 2600 + or - by a few cycles, is not pink noise, and does not get past all the `Blue Box detectors' (to put it into `their' terminology) that lie in wait for twits who have decided that the most efficient means to auto-dial their favorite BBS, is to write a Blue box auto-dialer, made safe by `sending over pink noise!' or `wavering the tone dudez!' On the subject of boxing from home, it IS NOT dangerous (even on ESS), in most cases it is all in the number you're using to box off of, I'm not going to get into an entire tutorial, but if you are having problems or need help, call me and I will give you any information you might need. _______________________________________________________________________________  <\-:::::::::::::::::::-/> (\):> Phantom Access 5.7K <:(/) _____________________________ | | | (C)reated By Lord Digital | |_____________________________| =^=^=^=^=^=^=^=^=^=^=^= [ Sub - Module Editor ] =^=^=^=^=^=^=^=^=^=^=^= ============== [Introduction] ============== The PA.Editor facilitates the creation of Phantom Access Sub-Modules It is not the system editor, which is contained on diskette [B1]. To load a existing Sub-Module from disk enter option `2', `1'. When it has been loaded into memory you can take a look at it by selecting option `3' of the current menu. To return to the central menu select `4'. _______________________________________________________________________________ ======================================================= [Editing Existing Sub-Modules And Creating New Systems] ======================================================= You will probably want to start by loading a generic, fill in the blanks (or to be precise; edit the options) Sub-Module. This process has been described in the previous section. After the Sub-Module is in memory the next logical step is to select `1' from the central menu, and `Modify/Create Modules'. From start to completion the easiest way to build a Sub-Module if you are not familiar with the editor is: 01> Select `1' for the block editing section. Modify or create the total block structure of this Sub-Module. 02> Select `Q' to quit out to the central menu. 03> Select `3' from the central menu to set up this Block-Sets defaults. 04> Once defaults are set to your liking, select `4' to return to central menu. 05> Select `1' one more time and proofread the Sub-Module in its entirety. If the end result is the one you had in mind; `Q'uit, `2', and `3'. _______________________________________________________________________________  ==================== [Defaults Explained] ==================== At the default editing section you will have four choices: 01> Edit system and codes filenames. 02> Edit tone length, code length, audio length. 03> Select Apple-Cat slot. 04> Return to the central menu. Selecting `1' will give you the following: __________________________________________ [System Name]:[Generic System] [Code File..]:[Generic Codes.] Change (S)ys, (C)ode, (Q)uit (S/C/Q)? X S - You may type in the system name (this is not the Sub-Module filename, just a system identified for your own benefit and Slider use). C - The name of the file you want to save valid codes to. Phantom Access does not attach any form of prefix to Code File names, so what you call it, is what its final name will be. Q - Quits back to the Defaults menu. __________________________________________ Selecting `2' will give you the following: [Tone Length]:X(XX) [Audio Count]:X [Code Length]:X Change (T)one,(A)udio,(C)ode, or (Q)uit [> X T - Corresponds to dialing speed. Digital switching systems can handle a 1 in this variable. Xbar's a 2-3, SxS a 5 or higher. A - How many Audio Units will the Audio Counter start with at the beginning of each Block-Set. For most systems anything between 4-5 is good. Less than 4 and you might start encountering problems, while more than 5 is a needless waste of time. C - Length of the codes you will be scanning in this Sub-Module. __________________________________________ Selecting `3' will give you the following: [Enter Slot of Apple-Cat (1-7)] [Slot]:[X] __________________________________________ Selecting `4' returns you to the central menu. _______________________________________________________________________________  ========================== [The Block Editor/Creator] ========================== To get a help screen in this area, type `?' and you will get the following: [A>dd........Begin or Add to Sub-Module [C>lr......................Clear Screen [D>elete........Delete Sub-Module Block [E>dit............Edit Sub-Module Block [I>nsert........Insert Sub-Module Block [L>ist..................List Sub-Module [N>ew..................Erase Sub-Module [O>utput........Route Output to Printer [P>roofread............Check For Errors [Q>uit.............Exit to Central Menu [?>...................Display This Menu [In Depth> A - Begin a Sub-Module or add blocks to an existing one. If memory is cleared then `A' will place you at block number 1. If a Sub-Module is already in memory, you will be placed at the next available block. - Usage: A C - Clear. Simply clears your local display. This has no effect on either the Sub-Module, Block-Set, or anything but screen control. - Usage: C D - Delete a block within the current Block-Set. - Usage: D(X) (Delete block X(X)). E - Edit a block or set of blocks within the current Block-Set. - Usage: E(X) begins editing block (X). <-- and --> keys can be used to move the cursor back and forth non-destructively. When you are done editing type . I - Insert block(s). - Usage: I(X) begins inserting blocks at (X). If you want to add more than one block, you may simply keep typing as in add mode. If you only want to add a single block, type as the first character in the second input block (second being relative to where you began insertion, has nothing to do with `physical' block 2).  L - List a block or set of blocks within the current Block-Set. - Usage: L (lists all blocks in Block-Set). L(X)/X (lists from block (X) to X in current Block-Set). NOTE: There are 2 modes for list; (A)ctual and (I)mplied. Actual mode ---- will give a `physical' listing, while Implied gives a logical list mode. IE: [Actual]: [Implied]: 01> P 01> [Hang-Up/Pick-Up] 02> D1234567 02> [Dial]: 1234567 03> A 03> [Await Dialtone] 04> C 04> [Dial Code]: (X) [Digits] --- Etc. --- N - New, clears the current Block-Set from memory and restores defaults to their original modes. - Usage: N O - Routes list output to slot 1. - Usage: O. You will be asked for a string to send to the printer to initialize it. IE: ^I80N P - Proofread. This reads through your Block-Set to make certain each Block can be successfully parsed. However it only tests for a valid control command start sequence (A,C,D,H,P,R,T,W). It can't tell whether or not the system you've built will make any sense. IE: Entering 40 elements of `A' while perfectly valid, isn't going to accomplish a great deal. - Usage: P Q - Quit, exits Block Editor to central menu. - Usage: Q ? - Help screen. Displays the help screen. - Usage: ? _______________________________________________________________________________  =^=^=^=^=^=^= [ Utilities ] =^=^=^=^=^=^= ========================== [Phantom Access Utilities] ========================== This module is a sort/list/print/merge/analyze/purge system for code files. It also reads in Status Reports if you have chosen to activate them. The central menu has three options: [1] - Load/Save/List/Sort Codes. This is the code manipulation section. [2] - Examine Status Reports. List or print scan status listings. [3] - Exit Utilities. _______________________________________________________________________________ =========================== [Code Manipulation Section] =========================== [1] - Load/Append Code Files [2] - Save Code Files [3] - List/Sort Codes [4] - Return to central menu Option `1' allows you to load or merge Code Files into memory. If there is a Code File in memory when you make your selection, you will have the option of appending it to the current file (merging two files from two scans of the same system, etc), or clearing memory. You can only merge Code Files of the same code length. IE: 6 digit codes with 6 digit codes, 8 digit codes with 8 digit codes, et al. Option `2' will save whatever codes you have in memory to a file. Option `3' allows you to list codes to the screen or a printer. It also lets you sort the code file and search for or remove duplicate codes. _______________________________________________________________________________  ================ [Status Reports] ================ When you want to read in a report, just enter its date. If you have configured for a ThunderClock you can use `@' in place of the current date. The prefix `Pa.Final Status' is automatically inserted before the date. <--------------------[Statement:]--------------[Comments:]--------------------> ___________[:Final::Status:]___________ [Date of Scan]:01/01/85 ...................The date (really!). [System That Was Scanned]: MCI .......................Name of system. [Hacker Module Loaded]: MCI.1 ...................Name of Sub-Module. [Code Used For OCC]:123456 .....Code used for OCC Dial if active. [Number of Times Pound Out Failed]:00 ..............OCC audio test failures. [Name of Valid Code File]:MCI.CODES ................Code filename on disk. [Total Codes That Were Scanned]:12345 ....................Total codes tried. [Valid Codes That Were Found]:123 .........Number of valid codes gained. [Last Valid Code Found]:123456 .The last valid code that was scanned. [Percentage of Codes Correct]:0% .............Bad code/good code ratio. [Slot of Apple-Cat]:2 ................Slot of the Apple Cat. [Rings Detected]:1 ...........Incoming calls intercepted. [Audio Counter Was Set For]:5 ..Audio Units assigned to the counter. [Dialing Speed Was]:2 ........................Dialing speed. [Codes Were Tested For]:4:[Seconds] ..................Length of Wait-Test. _____________________________________ [Phantom Access 5.7K]:(C) Lord Digital) _______________________________________________________________________________ Please Note: These utilities are provided for your convenience in creating the Sub-Modules, and manipulating data from the code hacker. They have error trapping, but they are not idiot proof. If you are deliberately trying to cause an error, you will most likely get the malfunction you desire. There are numerous opportunities to make mistakes, however I am working under the assumption that you're not a complete cretin. Of course I might be wrong, but that is your problem, not mine. _______________________________________________________________________________  <\-:::::::::::::::::::-/> (\):> Phantom Access 5.7K <:(/) _____________________________ | | | (C)reated By Lord Digital | |_____________________________| =^=^=^=^=^= [ Various ] =^=^=^=^=^= ============================= [Differences Between 5.6/5.7] ============================= Phantom Access 5.6 was the last system I wrote before ignoring the limitations of foreign systems and writing to suit only myself and those willing to upgrade their hardware to the level required by the programs. The major differences between the 5.6 series and 5.7 are detailed below: o All programs previously written in C, have been rewritten in basic to cut down on memory overhead and thus allow more features to be implemented. o Due to the space cleared up by the previous action, the 6.X Sliders and a limited Rotation System have been added. o 6.X prototype programs have been modified downwards to allow them to be used on a limited system. An example of this is Spectre. o A limited set of utilities have been provided. While not very extensive, the programs are adequate for the small systems that are the target of this release. )=-> All programs and the documentation needed to configure and use them are contained on 5.7(x) diskettes; [A1], [A2], [B1], and [B2]. Theories behind operation, advanced options, and in some cases excerpts from 6.6 documentation when applicable, are provided on 5.7(x) diskette [C], sides <1> and <2>. - This brings the entire 5.7(x) series down to a more reasonable length of six disk sides. Complete Phantom Access history, theories, goals, documentation, comments, and in depth explanation of every program from 1.0 to the 6.6 series, is contained in the 6.6 documentation. This is available in disk format, as well as a bound laser printed copy which looks nice, and is very useful to anyone who has an interest in the Phantom Access series, where it began and where it's headed. If you want complete information refer to this reference, all the information in the 5.7(x) document disk has been edited from the original 6.6 copy. I am not willing to type megabytes of documentation more than once. _______________________________________________________________________________  ================================ [Phantom Access 6.6 Information] ================================ Phantom Access 6.6 is approximately 3 megabytes in length. This includes some of the documentation as well. If you are serious about using it, have the hardware necessary, and are able to modify certain hardware in order to make full use of it, call me and we'll work something out. The hardware required to utilize Phantom Access 6.6, follows: 01> Enhanced Apple //e computer with 80 columns and at least 128K RAM. General rule to follow with RAM is (as always); the more the better. 02> A ThunderClock compatible clock card. 03> A Taxan RGB monitor is optional. Model number doesn't matter, as all models utilitze the same screen update controls. 04> A ProDOS compatible hard disc with at least 2MB of space devoted to Phantom Access. 05> A Racal Vadic 2400 Maxwell modem is optional. There are also drivers that allow use of Novation's 2400, as well as Hayes clones. Both of these modems are inferior to the Vadic, some (Hayes and clones) to a great degree. 06> A Grappler compatible printer interface (Graph functions, etc). 07> Support of 5.25" and 3.50" drives is optional. The complete system will, in any case, REQUIRE a hard disc. Even 2 UniDisk drives for storage use will not suffice. 08> 65SC02 CPU for Apple //e. 09> A COMPLETE Apple-Cat system consisting of: a> Main board b> 212 card c> SSI201 Receiver d> Expansion Module __________________ e> Firmware Switcher _________________| f> BSR Controller and 2 BSR modules | g> Tape deck | h> Coil system _______________________| | _____________________________________|______________________________ | | | The `Cat Console' interface system is required to make use of this | | and many other options. If you feel comfortable with hardware, you | | can receive the schematics, and build this yourself. If this isn't | | the case, I or some associate of mine can build the console, and | | do what is needed to the Apple-Cat board itself, for you. | |____________________________________________________________________| If you are under the impression that 6.6 is perfect, it is not. Nothing is ever really complete. I would define perfect as being at the level where the program is sufficiently intelligent enough to be able to modify itself and rewrite portions without the need of human intervention. This enters the domain of true artificial intelligence and is not possible on an Apple. This is the reason 6.6 is the definite LAST Apple revision, as has been stated in the past, all modem control is complete, and in the end the entire Apple will function as no more than an intelligent modem under the control of a workstation capable of using object oriented languages.  The present 6.6 has a `Thought module' which can look at all sorts of criteria, analyze situations, and decide what needs to be done at any given time. Ripped down to its base level, it might as well be `if, then, else'. In reality it is nothing more than complex error trapping. All arrogance and conceit aside for a moment (I know it's difficult), 6.6 isn't a statement on anything, nor is it designed to be something that you cannot have. As I said, give me a call and we'll work something out. I do not want it to ever appear in any kind of distribution. If this ever comes to pass, and somehow 6.6, or parts of 6.6 are distributed, it will still not be usable without full documentation, and even then it won't function unless the hardware modifications are done. If somebody goes through all of it, taking it apart and turning off certain capabilities to make it work with normal hardware, with all the time and energy they've spent to get a limited version running, they may as well have written it themselves. 6.6 would be the equivalent of low grade ICE, any attack may be launched by using the loader, but these must still be written by people, the program cannot do that itself. If I begin the 7.x series, it will have this capability and I will actually have real ICE. I may also add a human interface which makes it much easier to use, reminiscent of something like the AT&T Unix PC's overlay for idiot proof Unix. The reason this hasn't been done is mostly because I do not want the programs too easy to use. If it ever comes to pass that somebody is arrested with a copy of Phantom Access, I am not really thrilled by the idea of having it fall into the hands of security agencies. To this date there exist only 3 other people with copies other than myself, they are intelligent enough to avoid arrest, however (no reflection on anybody else intended) if I do give 6.6 to any others, it will be complete with a integral virus built in. Which cannot be removed without rendering the programs useless. I don't really know exactly what I'll set up yet, but at the very least it will kill every system and write random garbage back in if certain negative criteria are met. At this time (early 1986) I do not know if I will ever work on it again. There are too many other things I need to do that take precedence over it, and for a extended period of time I won't have access to any machines at all. As strange as it may sound, my world view has shifted a great deal lately and I'm sometimes very hard pressed to justify to myself just why any of `this' is important to me. If I do begin work on 7.0 it will be in late 1986 and I will have to decide what machine to use. It's almost certain the operating system will be Unix based, however I need hardware to drive it. If the new Mac is the workstation Apple claims it will be, I think that'll be the machine I end up using. _______________________________________________________________________________  ================= [Version Numbers] ================= This is where confusion really starts. When I (or someone else) want(s) a new feature, or screen display, or support of various peripherals, in the 6.6 series, then I simply add it in with ACPL. When someone wants the same thing in the 5.X series, I add the modification, make a note in one of my notebooks that lists exactly what was changed, and give it to whomever wanted it WITHOUT changing anything but a single internal signature byte that allows me to keep track of what is what. Thus there are (at last count) at least 25 different versions of the 5.7X series alone. Some have cosmetic modifications, some have things like lightbar catalogs, or mouse support (this is not standard, as I despise both, finding it much faster to touch type something then scroll through a listing with arrow keys, or even better; clear desk space and find the buried mouse), or support of 80 columns, etc. So ALL 5.7(x) (even when the processor is configured for the EXACT same hardware layout using the system editor) versions, are NOT identical. They all work, but in slightly different ways. This is, for the most part minor bullshit, but it can get somewhat confusing. On the subject of modifications, if you desire any (within reason), let me know, and I shall send you a copy of the version you desire, or add in the code necessary to implement your changes. Everything is modular and easy to modify, so presuming you have full documentation, you could do it yourself. NOTE: By modifications, I mean exactly that; not rewrites of the entire ---- series to `work just like 6.6'. If you want everything, you must upgrade your hardware to the program's level, not visa versa. SUGGESTION: Before embarking on anything beyond cosmetic changes to any of the ---------- programs, plan out what you want to change, and why you want to change it. None of the programs should need ANYTHING beyond the most minor changes to satisfy your aesthetic desires. Cases where you would benefit from modifications, involve oddball situations, which should not exist to begin with. IE: Call waiting, 3-way calling, or other `features' that certain idiots insist on adding to their MODEM dedicated lines. In any case, 1 line for-next loops take care of this and can be linked together under their own heading: `Options for the terminally stupid.' in the system editor. COMMENTS: If the features you wish to implement are not built into the System -------- Editor's linkage routines, chances are, they are useless. Many people write features that are present to satisfy their own neurosis, while serving no actual purpose in avoiding the pitfalls of whatever technology you are up against.  Examples: -------- Multiple destination numbers: I have no idea who first came up with this, but the fact is; it serves no purpose whatsoever. When a code is invalid the OCC does not record the destination number that the hacker tried to reach (in cases when you are actually using a full destination number). In cases where the code is valid, the number being dialed does not supervise, and after the 5 second test period (or whatever you configured for), the destination is flushed from call store (as are busy's, rings, etc. Many OCC's used to begin billing after a arbitrary period of time had passed, regardless of connection status. With current competition being what it is, and all major carriers billing only when connected, there are very few, if any OCC's left, that make use of this billing method. Even those that do, start billing in 10-15 seconds, not in 5. So the destination does not show up anywhere). Rotation Systems: This DOES serve a valid purpose when hacking MCI. But when you activate it, BE CERTAIN that you are hacking multiple NODES, not PORTS. If the hacker trips the pilot after consecutive calls, you shouldn't delude yourself into thinking that they aren't going to flag the entire rotary group, because they will, and this serves to utterly nullify any benefits you might have gained. Graphics Page Display: Ahem (cough, cough), if mummy and dada are actually going to care what you are doing, then you can always turn off the monitor eh? (We pause now for hysterical laughter). Chaining Ports to Avoid `Trace': Some simpleton decided that he would only be `traced' half as much, if he made the second call to the SAME system, using the system itself, as a chaining link. I don't pretend to know what he was on, at the time whomever it was, made this great `discovery,' but I can tell you that the only thing it accomplishes with success, is slowing down the hacker to half normal speed. But if being `traced' `half as much' means something to you (I in my blind stupidity must have missed it), by all means add it in (Once more with the hysterical laugh). Dial twice as fast with 3-way calling: Someone actually did this. I never would have believed it either, but some cretin decided that he could hack `twice as fast' if he made his hacker use 3-way calling to dial another number. Did you also know that you can keep your machine cool by pouring some cold water into the motherboard? Even if you did know that, I bet you didn't realize that your hard disc can go twice as fast if you hook it up to a snow blower engine! (This isn't even worth a laugh). _______________________________________________________________________________  If you are going to write your own modifications, make sure you fully understand the memory maps provided with the System Editor. If you add line numbers to the program, in spaces that are free NOW; it might not work when you do another system edit, as those same line numbers might be used if you are going to select another configuration. Be certain that the line numbers you define are within the range listed as `Always free,' in the documentation. NEVER relocate Bmodules by hand, they are situated to `stack up' when all features are activated. This may give cause to odd positioning on an `empty' assembly, but it does not interfere with functionality, and you should NEVER relocate ANY module. Another action you are not encouraged to take, is adding a DOS that loads itself into the language card. When Sliders are activated in certain systems, I use my own routines to r/w the language card. It is NOT `free' for DOS, stick with 48K DOS. _______________________________________________________________________________ Several people have expressed their disappointment at my selection of ProDOS for all further development. To them I'd like to say; If I were using two disk ][ drives, and 64K RAM, I wouldn't bother with ProDOS either. It DOES take much more system overhead then DOS, and is annoying to use with small storage type devices. It is also the ideal system to use on a hard disc where there are very few space limitations. In this type of environment the advantages far outweigh the disadvantages. _______________________________________________________________________________  ========================================== [System Editor/Spectre/Wraith Information] ========================================== The System Editor contained on side [B1], is actually an offshoot of the KKK: 2.01 hacker assembler, sans user lethal routines. Full documentation is contained on the same side as the Editor itself, however several things should be made clear concerning the program. More than anything else the System Editor is a linker; it will either remove or add whatever routines are needed to implement the system you desire. In doing so the Phantom Access 5.7 processor changes version numbers, length, ability to handle more or less external control (Rotation System, Sliders, Powerfiles, et al), and of course internal functions. You should understand that the Editor actually links, removes, and/or changes code in the processor. If I had written the processor in such a way that all code was always present, and could simply be toggled on or off, memory intensive funtions like the Rotation System, and Sliders would have been severely limited and in some cases not possible at all. With the System Editor it is up to you what your processor will be capable of doing. Being the sort of person who likes ALL options on, ALL the time, I can understand being upset at limitations. However these are limitations I can do nothing about, and come inherent with the limited systems 5.7 was designed to run under. You can toggle every function available on (presuming you have the hardware to take advantage of it), at the sacrifice of almost all external control. On a small scale system, the Sliders and Powerfiles lose most of their importance at any rate. For those familiar with the three central `processors' of the 6.6 series (for the uninitiated, they are: Phantom Access, Spectre, and Wraith), I'm sorry to inform you (actually I couldn't care less, but you're probably sorry) that Wraith cannot run on smaller systems, without a massive rewrite from ACPL down to Basic and DOS. Something that I am not willing to invest the time in. So it is not available at this time, or anytime in the foreseeable future. `If you want everything, upgrade your hardware.' _______________________________________________________________________________  =================== [Future Prediction] =================== These disks have been assembled against my better judgment, because one day in the not too distant future, Marc or Rich or some other semi sentient life form will wander into Dave or Yuri's house, and while fastcopying a stack of the latest k-radical new wares, he will copy these disks along with Archon XXI, and Wizardry VI. And it will become the latest ware on all the world's AE lines, and whatever lines will then be running that week's standard in 202 transfer programs. I have never liked my software to be the latest ware on transfer systems all over the country. Not so much that I really care who uses it or not (although I have no burning desire to see others benefit from my work), I just see no purpose to it. I don't like writing the long text files that I am forced to write in order to explain it to people, but have found that I have to do this for even simple systems such as the 5.X series, because people are for the most part, fools. Rather than spend thirty minutes explaining it to each person I give a copy to, it is better to write the documentation once and get it over with. There still remain those who cannot read or follow simple instructions so even this is somewhat futile, however I have done what I could. If worst comes to worst and it does leak out, I've thought about it and decided that it's not such a big deal in the cosmic scheme of things (although 6.6 is the crux of the universe!), and for every 1,000 idiots, there will be one intelligent person who gets a copy and might even get some ideas from it. Which makes it all balance out. _______________________________________________________________________________ (Goodness, wasn't that cold and officious.) If anyone is taking me too seriously, don't. It's been a while since I last went to sleep and am probably typing something nobody will ever read, because as past experience shows no matter how complete the documentation, at the first sign of difficulty I will get a call asking dumb questions anyway. If it is actually being read; I want to make it clear that I really have nothing against idiots, since there would be nobody left to take advantage of if everyone had intelligence and made use of it. (Ego leaves the stratosphere.) _______________________________________________________________________________ All of this started life at 4:30am, and it's now about an hour later. There will doubtlessly be several typos and run on sentences, but I really don't care and neither should you. I don't feel inspired enough to run it through a spelling checker, so you'll have to live with it. _______________________________________________________________________________ This Document File Has Been Approved By The Society For The Betterment Of The World By Capitalizing Lots Of Words For No Particular Reason. _______________________________________________________________________________  [Thanks To]: ----------- [Paul Muad'Dib, The Tempest, and Magnetic Surfer] - For - [Creative input.] [Special Thanks To]: ------------------- [Track Trixster,] - For - [Taking the time to write several of the list/sort/print applications, for the] [Phantom Access utilities in this revision.] [Captain Avatar] - For - [The title page, as well as access to every program ever written for the Apple] [// computer] [False Prophet and The Plague,] - For - [Testing] [Extra Special Thanks To]: ------------------------- [Brackets] - For being brackets [Underscores] - Same principle as the brackets. [Led Zeppelin] - For being Led Zeppelin _______________________________________________________________________________  ============= [Misc. Items] ============= This May I will be leaving for Europe, I will return in September and will be in NYC for about a week. Towards the end of September I will be moving to the west, possibly back to California, maybe somewhere else. I don't know which of my father's houses will be empty at the time, so I have to wait and see. I am still on TPX and will in all likelihood stay there as long as it stays up. Even though my accounts are there, I won't be able to pick up mail for a few months. My ADS is still functional at this time, as are most of my father's numbers. As soon as I figure out where I will be, I will give everyone with whom I've lost touch during this time, a call. So if you can't get a hold of me, you know why. (Ever notice what a great word `will' is? Well I did too, in fact the previous paragraph is my official tribute to the word `will'. Pretty k-radical eh?) Incidentally, people tell me that my name is showing up on bulletin boards once again. As usual I am not on ANY bulletin boards, and having exchanged mail with any of the people claiming to be me, would doubtlessly allow you to figure that out for yourself, so I'm just saving you some time. For those who've forgotten or never knew, my account on TPX remains; Lucifer. _______________________________________________________________________________ Everything has been made as idiot proof as could be foreseen, since I just know that somebody will have insurmountable problems anyway, all I can say is: Too bad, if you are still experiencing difficulties after reading all the documents available, tsk tsk tsk. _______________________________________________________________________________  In this ancient time swept city, discredited gods do brood, on all the imagined insults which down the aeons they've received It is a place of graves and here dreams are destroyed Dreams are brought from all corners of the world, To be crushed or ripped or melted down into a healthy cynicism Here are tricksters born and fools divested of enchantment This is where Pierrot is killed And from his flesh Harlequin created Racing across the world, laughing at nothing Laughing at everything, laughing at his pain Laughing at the tired gods who bore him. Here in this city, this city of shadows, This city of irony berift of imagination This city of suppression, this city of pragmatism, Where the jesters weep, and the tricksters scheme, Parading in motley, too afraid to scream Too wary to even acknowledge life, unless life itself is made a game And games can be won Here, in this city of swaggering fantasicos, of calculated gallantry Was Harlequin the Trickster born, to go about the world, to win, To attract; to display easy cleverness; to lie and to deceive, To show what shallow things are dreams, and promises impossible to keep And should he meet with frankness, unashamed honesty Back to this city Harlequin might flee To be endlessly replenished, armed afresh by his weary masters, The glorious gods of disharmony... Darkness falls, :Lord Digital _____________________________________________________________________________ | o ___ ___ o | | ___|___ [Phantom Access (tm) Copyright (c) 1982-86 by Lord Digital] ___|___ | | ___| [All rights reserved] |___ | |_______________________________ _____________ _______________________________| | | | [23-Jan-86] | |_____________|