[ 53280,0:53281,0:646,(162):"":" USE LYNX TO DISSOLVE THIS FILE":10 1 *LYNX BY CBMCONVERT 2.0* 3 _Ҡ 3 P 208 AUTOΠ 22 P 197 AUTO.DOC 42 P 140 TD_AR] PRG formatted GEOS file V1.0IРпӧмЄׄ 3 3 TD RB PATCH V1.0@Irv Cobb Irv Cobb 5107 N. 15th St. Omaha, NE 68110N ) O ) O ) O ) ON L, ©Å ;­` 8© 8`128 DESKTOPDESK TOPTopDeskTempautoRUN]  PRG formatted GEOS file V1.0 H?s8s8?3@0I$0&x8autoRUNNER V3.0@Irv Cobb Irv Cobb 5107 N. 15th St. Omaha, NE 68110 ? ڇiňLw ;© t© ~ w P  LPautoRUNNER V3.0  Cx ɀL%% L,©Åυ ©  L,©%ƅA L,©ʅƅ  ©ƅA  L,autoRUN L,­ɀ`?`mmii?>KM`@  %  e  eP`8` @` 4 P (h`0``Ͱsovmlfm6mffm6mcfm3n3m x<;Jd 3JJ$ %JJ %%4JJD %%$Jd %%4Jd;K dx<%]`(Q $E,UQ bE)4 !})%Q"E)%Q@"D] d?  A` * P 袐 ? j U b" T`   J ??8('&E@??E%))I5E%*Oj@E%,iHժ"9$%GA< U?<@D 8888888881I@autoRUNI (AutoRUNNER 3.0) 8888888880 Since its original version, AutoRUNNER (now called I@autoRUNI) has provided the function of loading and executing all of the AUTO_EXEC files found on a disk (up to a 16 file limit). If you use AUTO_EXEC utilities on your boot disk, this is helpful after a I@LOAD "RBOOT",8,1 Ior I@SYS 49152 I(in 64 mode) or the I@RESETI button was pressed (in 128 mode) or after the use of the I@rbootI command from I@geoWizardI or I@geoDebuggerI. 888888888(more) => 888888888!I@autoRUNI Requirements 8888888880 I@autoRUNI requires some sort of expanded RAM and works with Geos 64 2.0 and Geos 128 2.0 in both 40 and 80 column modes. It has been tested with 1541, 1571, 1581 and RAM 1571 drives and in both 64 and 128 modes with the standard BSW DeskTop and with TopDesk. I@TopDesk users: please see Addendum 1.I I@PLEASEI read the WARNINGS section of these docs! 888888888(more) => 8888888881IInstalling and Using I@autoRUNI 888888888Simply copy I@autoRUNI onto your boot disk and boot Geos. During the boot process, you will see a dialog box informing you that I@autoRUNI is being installed. Geos will then automatically execute I@autoRUNI during any re-boot situation. I@autoRUN ImustI be present on either drive A or B in order for a successful re-boot to take place. If it is not, you will be shown a somewhat garbled dialog box asking for a disk with the DeskTop. What the system actually needs is a disk with I@autoRUNI on it. Just put your boot disk in drive A or B and click OK. BBR, BBU and CMD RAMdrive users please see I@Addendum 2I for instructions on installing I@autoRUNI without doing a cold boot. 888888888more => 8888888881I@Disk Search OrderI 8888888880 Previous versions of I@AutoRUNNERI searched up to three disk drives looking for AUTO_EXEC files to run. This feature has been removed from v3.0 in order to provide greater simplicity and to place the program itself in AUTO_EXEC format. I@autoRUNI will search the Idrive from which it was runI. I@IFI it finds any AUTO_EXEC files, it will load and execute them and then quit. If it Idoesn'tI find any AUTO_EXEC files, then it will simply exit to the DeskTop. 888888888(more) => 8(Px88881I@WARNINGSI 8(Px88880 *** I@autoRUNI ImustI INOTI be renamed! If it is, the system will become permanently confused and a cold boot will be required. INEVERI rename I@autoRUN!I I@autoRUNI will IignoreI the I@CONFIGUREI and I@128 CONFIGUREI files. This is because running I@CONFIGUREI will clear an REU (hardly productive - we're trying to SAVE clicks here!) If for some arcane reason you should IrenameI a I@CONFIGUREI file, you will fool I@autoRUNI, and it will execute the file. This I@willI clear the REU and you I@willI lose any files that were in it. IDon't rename ICONFIGUREI filesI! Your system will lock/crash if I@autoRUNI tries to load and execute I@geoWizardI (or I@GEOWIZMOVEI, I think) when I@geoWizardI is already active. I@autoRUNI simply executes the AUTO_EXEC files it finds; it does InotI check to see what may already be running. Thus, if I@geoWizardI is active, I@autoRUNI will try to activate it "over top of itself." As Jim Collette says in his docs: "There's no reason to do this anyways." But if you accidentally double-click the I@autoRUNI icon, this may occur. A cold boot will then probably be your only solution. Unfortunately, I@autoRUNI will I@NOTI work from the I@DUAL TOP Ienvironment. Actually, you're going to have to experiment with your system and the AUTO_EXEC files that you use. Programs that do unusual things with Geos (see I@geoWizardI and I@DUAL TOPI notes above; I@SuperBoxI is probably another) will likely give you trouble if you try to re-run them. I@QWIKSTASHI might overwrite the contents of a drive. Who knows what can happen? With programmers taking Geos to its limits, there IwillI be incompatabilities. All I can say is that I@autoRUNI meets my personal needs (which is why I wrote it). I've done my best to make it work for you, too, but I can't make any guarantees. PLEASE experiment using backup disks and learn I@autoRUN'sI strengths and weaknesses on your system with your files BEFORE you trust it to work in real life, especially if you are using some kind of non-volatile RAM and have valuable files stored on it. I@USE THIS PROGRAM AT YOUR OWN RISK!I 8(P888888(more) => 8H88888880I@autoRUNI is shareware: If you like and use this program, five bucks would prove your appreciation to me quite nicely! Irv Cobb 5107 N. 15th Street Omaha, NE 68110 8H8888888****************** 8H88888880"I@One who chases fantasies will have his fill of poverty."I 888888888Addendums (Addendi?) => 8H8888888!I@Addendum 1 IUsing I@autoRUN IwithI@ TopDeskI 8H8888888 888888888TopDesk users who utilize the RAMDESKTOP option will find that I@autoRUNI causes a crash instead of returning them to the TopDesk environment. The program I@TD_ARI (I@TIopI@DIesk_I@AIUTOI@RIunner) will fix this. Simply put it on any disk with AUTO_EXEC files and you will have no further problems. IIf you don't use I@TopDeskI, IDON'TI use I@TD_ARI. While it should cause you no huge problems, it is unnecessary. 888888888more => 8888888881I@Addendum 2 IUsing I@autoRUN IwithI@ BBR, BBUI or I@RAMdriveI 8888888880 I@autoRUNI should work with these units, but I don't have them for testing nor do I claim to understand their operation completely. Here's what you can try: 1. Make a "rescue" disk by placing a disk in drive A (the drive that you would do a cold boot from) and copy I@autoRUNI and all of your AUTO_EXECS onto it. Also copy any special RBOOT files you may need onto it. 2. Delete I@autoRUNI from the RAM drive if you happen to have copied it there. 3. Hold down the "i" key (make sure CAPS LOCK and SHIFT LOCK are both up) and double-click on the I@autoRUNI icon. I@autoRUNI should run and you should see the I@Now Installing...I dialog box. 4. In theory, anyway, you can now shut down you system and then RBOOT from your rescue disk. I@autoRUNI should automaticaly re-install your AUTO_EXECs in the process. Please let me know how this works for you, especially if you have problems. I would really like this program to be helpful to all users, but can't afford the hardware to test it in all configurations. I can be reached on GEnie as I.COBB1. Good luck!hx<;Jd 3JJ$ %JJ %%4JJD %%$Jd %%4Jd;K dx<%]`(Q $E,UQ bE)4 !})%Q"E)%Q@"D] d?  A` * P 袐 ? j U b" T`   J ??8('&E@??E%))I5E%*Oj@E%,iHժ"9$%GA< U?<@D