Drive: Load $ Jump $ FileName: Info! 40000 DF0: FileBoot V2.2 by the ENEMY! FileBoot V2.2 : User-interface: Drive - the unit you want to install Load - the absolute address you want to load the file in. Jump - the address where the code starts if it is "0" nothing will be executed. Filename - The name of the file wich should be loaded ! don't use DF0: ect. or any ":" in it! It contains only the filename and the path,if the file is not in the root-dir "Menu" or "C/Menu" or "S/INTRO" What does FileBoot do for you : You have the possibility to load a binary file from any disk ,you install with FileBoot . It just works like Bootleg or Trackwrite ,but Fileboot doesn't write to any blocks on the disk or anything like diz. It loads a complete File ,you copied to that disk,in memory and executes it . Remember : FileBoot does not copy the file to the disk , you install with FB. It writes only the BootBlock to that disk. To copy the file is up to you !! Fileboot is not as fast as trackwrite or bootleg in some cases, but you have all advantages of a normal dosdisk like OPTIMIZE, or VALIDATE ! If you use Trackwrite ect. Validating or optimizing will destroy your intro or menu you installed there (not very nice !). PRESS ANY KEY@ Features: - If you press the spacebar before booting the disk, FB skips loading the file and enters cli or the startup-sequence ,if it exists,will be executed. - If the screen flashes RED during boot , the current file does not exists or any load-error occured. - NOTE: FileBoot works ONLY on DOS-Disks, because it loads normal DOS-Files form the bootblock. - If the executed program returns correctly the bootblock enters CLI after executing. - FileBoot loads data also to fastmem The File to be load from bootblock ,could be any demo,intro,or menu, wich works on absolute addresses or it is packed with a packer like Double-Action ,Stonecracker ,Defjam-packer,ect. The executable files ,wich are generated with one of that packers , don't need to be relocated ,because the hunkheader in front of them contains only unimortant code like "ORI.B #n,d0",that means : You can execute the Menus ect. from the bootblock and from CLI !! In this case LOAD-ADDRESS is also the JUMP-ADDRESS. @ History: - V0.9 Only for my own usage . Hard to use! (not released) - V1.0 CONwindow-userinterface Debuged Menu and Bootcode Space-option added (not released) - V1.1 OH...no, this version was assembled on a CAF-Meeting ,to release the first official Version of this tool. I tried to insert this features : The program allocates now all workbuffers, also the bootblock !! (It used absolute addresses before) and the CONwindow was styled in a new way . Caused by some beer ect. nothing worked the way it should The new bootcode was absolute trashed and corruped and crashed several times during boot,because i forgot to insert some routines like Free mem ect. !! Urks - V1.2 the bootblock is completly rewritten ! You got no crashes anylonger during boot ,if the file is not present. In this cases the screen flashes RED and it behaves like a normal bootblock. - V1.4 Now ALL bugs are removed ,hope so ! (not released) - V2.0 Complete new outlook !! Every input is now easier ! Wrong input won't cause crashes any longer ! - V2.2 Checks the disk before writing . WB to back on exit is now removed. @ Credits : Idea and coding - THE ENEMY Userinterface-design - PAT 0815 Thanx to Campino and Pat for testing all Versions For any questions,bugreports,or good ideas contact me in THE CyberAKTIF WHQ DETONATION BOULEVARD #0 +49-2151-391197 #1 +49-2151-CH/\OS So long ... see you in another release .... ENEMY/CAF RAW:0/0/640/256/Fileboot V2.2 Documentation ! Installation failed ! Name is missing !! Bootblock installed Name-Syntax-error !! Hexnumber is faulty ! No DOSdisk in drive ! FileBoot v2.2 by THE ENEMY !