Short: Progress bar while booting w/ picture Author: bdf11146@fs2.bdtf.hu (Álmos Rajnai) Uploader: bdf11146 fs2 bdtf hu (Álmos Rajnai) Type: util/boot Requires: Kick V2.04, iff.library V23 Architecture: m68k-amigaos Replace: util/boot/BootProgress.lha --------------------------------------------------------------------- BootProgress V1.01 Easy2use progress bar while your Startup-Sequence is running. Why BootProgress, and not an other one? * It is easy to use, needs just a few modification in your Startup-Sequence * Fully system friendly, no hacking at all * Can display an IFF/ILBM file * It can divide the bar by itself * It works after you or any program modified your Startup-Sequence * It is Freeware How does it work? ----------------- The program consists two part: the main part is BootProgress, which shows the IFF picture, sets up all it needs, and waits. Then come BumpProgress, it tells the bumps to BootProgress. When a bump arrives (to the public port of BootProgress), the progress bar raises one step. Usage ----- Place to the beginning of Startup-Sequence the BootProgress. (It is better to place right after the SetPatch, but it's up to you.) The template of BootProgress is: PICTURE/A,XPOS/A/N,YPOS/A/N,WIDTH/A/N,HEIGHT/A/N,COLOR/A/N,BUMPS/N those parameters are: PICTURE/A - the full path and name of your picture to display XPOS/A/N,YPOS/A/N - x and y position of left-up corner of your progress bar on the picture (numeric of course) WIDTH/A/N,HEIGHT/A/N - width and height of your progress bar COLOR/A/N - the color to use for drawing the bar BUMPS/N - number of bumps (or steps, if you prefer) it is not need to be set, if it is missing, BootProgress counts the calls of BumpProgress in your Startup-Sequence, and uses as the number of bumps, you can override this by using this parameter After every time you want to force a bumping, just call BumpProgress. Do not use BumpProgress in other boot-up scripts (eg. User-Startup), than Startup-Sequence! If you want to use this way, you have to set bumps by yourself using BUMPS parameter! (Not adviced anyway.) When the progress bar filled up, BootProgress exits. You are also able to terminate BootProgress by starting again. (Both will be terminated of course.) --------------------------------------------------------------------- An example: ----------- c:setpatch >NIL: c:patchopenwb >NIL: run >NIL: c:BootProgress work:visual/pictures/own/bootpic.iff 2 40 635 5 255 ; x=2, y=40, width=635, height=5, color=255 Resident >NIL: c:bumpprogress PURE C:AddBuffers >NIL: DF0: 15 [...snip...] FailAt 21 BumpProgress C:MakeDir RAM:T RAM:Clipboards [...snip...] Assign >NIL: FONTS: Workbench:Fonts BumpProgress C:IPrefs BumpProgress BindDrivers C:Mount >NIL: DEVS:DOSDrivers/~(#?.info) BumpProgress SetEnv Workbench $Workbench [...snip...] BumpProgress C:ConClip Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities BumpProgress IF EXISTS S:User-Startup Execute S:User-Startup EndIF BumpProgress ;That was the last bump, BootProgress terminates itself. resident bumpprogress remove C:LoadWB EndCLI >NIL: --------------------------------------------------------------------- Don't forget to use Run command on BootProgress! Check out of the cases of BumpProgress! BootProgress counts only when appears like "BumpProgress", and that is why I used lowercase version ("bumpprogress") when it was made resident, and when it was removed. That's all. (Easy? Let's say.) Warranty -------- BootProgress is totally Freeware, you may use as you want, but THE AUTHOR DOES NOT ASSUME THE RESPONSIBILITIES OF ANY LOSS OF DATA OR DAMAGE CAUSED BY USE, MISUSE OR CRASH OF THE PROGRAM. YOU USE THIS TOOL AT YOUR OWN RISK. Thanks to --------- * Wouter van Oortmerssen for AmigaE * Christian A. Weber for IFF.library * Opi (Geo) of BiĝHazard for support and beers together Author ------ Álmos Rajnai (Rachy/BiĝHazard) E-Mail: bdf1146@fs2.bdtf.hu Normal mail: H-8360 Keszthely Bercsényi M.u. 46. Hungary I am waiting for your bug report, suggestions etc... History ------- V1.01 Width division fixed, thanks to Paolo Zanellati for bug report (9. March 1998) V1.0 First public release (6. March 1998)