sINCE ITS ORIGINAL VERSION, aUTOrunner (NOW CALLED
@AUTOrun
) 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
@load "rboot",8,1
@sys 49152
(IN 64 MODE) OR
@reset
BUTTON WAS PRESSED (IN 128 MODE) OR
AFTER THE USE OF THE
@RBOOT
COMMAND FROM
@GEOwIZARD
@GEOdEBUGGER
(MORE) =>
@AUTOrun
rEQUIREMENTS
@AUTOrun
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.
@tOPdESK USERS: PLEASE SEE aDDENDUM 1.
@please
READ THE warnings SECTION OF THESE DOCS!
(MORE) =>
iNSTALLING AND uSING
@AUTOrun
sIMPLY COPY
@AUTOrun
ONTO YOUR BOOT DISK AND BOOT gEOS. dURING THE BOOT PROCESS, YOU WILL SEE A DIALOG BOX INFORMING YOU THAT
@AUTOrun
IS BEING INSTALLED. gEOS WILL THEN AUTOMATICALLY EXECUTE
@AUTOrun
DURING ANY RE-BOOT SITUATION.
@AUTOrun
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
@AUTOrun
ON IT. jUST PUT YOUR BOOT DISK IN DRIVE a OR b AND CLICK ok.
bbr, bbu AND cmd ramDRIVE USERS PLEASE SEE
@aDDENDUM 2
FOR INSTRUCTIONS ON INSTALLING
@AUTOrun
WITHOUT DOING A COLD BOOT.
MORE =>
@dISK sEARCH oRDER
pREVIOUS VERSIONS OF
@aUTOrunner
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.
@AUTOrun
WILL SEARCH THE
DRIVE FROM WHICH IT WAS RUN
IT FINDS ANY auto_exec FILES, IT WILL LOAD AND EXECUTE THEM AND THEN QUIT. iF IT
DOESN'T
FIND ANY auto_exec FILES, THEN IT WILL SIMPLY EXIT TO THE dESKtOP.
(MORE) =>
@warnings
@AUTOrun
BE RENAMED! iF IT IS, THE SYSTEM WILL BECOME PERMANENTLY CONFUSED AND A COLD BOOT WILL BE REQUIRED.
never
RENAME
@AUTOrun!
@AUTOrun
WILL
IGNORE
THE
@configure
@128 configure
FILES. tHIS IS BECAUSE RUNNING
@configure
WILL CLEAR AN reu (HARDLY PRODUCTIVE - WE'RE TRYING TO save CLICKS HERE!) iF FOR SOME ARCANE REASON YOU SHOULD
RENAME
@configure
FILE, YOU WILL FOOL
@AUTOrun
, AND IT WILL EXECUTE THE FILE. tHIS
@WILL
CLEAR THE reu AND YOU
@WILL
LOSE ANY FILES THAT WERE IN IT.
dON'T RENAME
configure
FILES
yOUR SYSTEM WILL LOCK/CRASH IF
@AUTOrun
TRIES TO LOAD AND EXECUTE
@GEOwIZARD
(OR
@geowizmove
, i THINK) WHEN
@GEOwIZARD
IS ALREADY ACTIVE.
@AUTOrun
SIMPLY EXECUTES THE auto_exec FILES IT FINDS; IT DOES
CHECK TO SEE WHAT MAY ALREADY BE RUNNING. tHUS, IF
@GEOwIZARD
IS ACTIVE,
@AUTOrun
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
@AUTOrun
ICON, THIS MAY OCCUR. a COLD BOOT WILL THEN PROBABLY BE YOUR ONLY SOLUTION.
uNFORTUNATELY,
@AUTOrun
WILL
WORK FROM THE
@dual top
ENVIRONMENT.
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
@GEOwIZARD
AND
@dual top
NOTES ABOVE;
@sUPERbOX
IS PROBABLY ANOTHER) WILL LIKELY GIVE YOU TROUBLE IF YOU TRY TO RE-RUN THEM.
@qwikstash
MIGHT OVERWRITE THE CONTENTS OF A DRIVE. wHO KNOWS WHAT CAN HAPPEN? wITH PROGRAMMERS TAKING gEOS TO ITS LIMITS, THERE
BE INCOMPATABILITIES.
aLL i CAN SAY IS THAT
@AUTOrun
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
@AUTOrun'S
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.
@use this program at your own risk!
(MORE) =>
@AUTOrun
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
******************
@oNE WHO CHASES FANTASIES WILL HAVE HIS FILL OF POVERTY."
aDDENDUMS (aDDENDI?) =>
@aDDENDUM 1
uSING
@AUTOrun
@ tOPdESK
tOPdESK USERS WHO UTILIZE THE ramdesktop OPTION WILL FIND THAT
@AUTOrun
CAUSES A CRASH INSTEAD OF RETURNING THEM TO THE tOPdESK ENVIRONMENT. tHE PROGRAM
@td_ar
UNNER) WILL FIX THIS. sIMPLY PUT IT ON ANY DISK WITH auto_exec FILES AND YOU WILL HAVE NO FURTHER PROBLEMS.
iF YOU DON'T USE
@tOPdESK
don't
USE
@td_ar
. wHILE IT SHOULD CAUSE YOU NO HUGE PROBLEMS, IT IS UNNECESSARY.
MORE =>
@aDDENDUM 2
uSING
@AUTOrun
@ bbr, bbu
@ramDRIVE
@AUTOrun
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
@AUTOrun
AND ALL OF YOUR auto_execs ONTO IT. aLSO COPY ANY SPECIAL rboot FILES YOU MAY NEED ONTO IT.
2. dELETE
@AUTOrun
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
@AUTOrun
ICON.
@AUTOrun
SHOULD RUN AND YOU SHOULD SEE THE
@nOW iNSTALLING...
DIALOG BOX.
4. iN THEORY, ANYWAY, YOU CAN NOW SHUT DOWN YOU SYSTEM AND THEN rboot FROM YOUR RESCUE DISK.
@AUTOrun
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!
(.txt)