************************************************************************** - THE LEGENDARY >> SUBSOFTWARE << IN 87/88/89/90 !!! ==================================================== - CONTACT US - BP: 36 - - 1380 REBECK - - BELGIUM - - DON'T SEND ANY DISKS - ************************************************************************** Dear Amiga Developer -------------------- We'd like to thank all of you participating in the testing of the 2.0 operating system software. Enclosed are the "KickIt" developer disks for the 2.0 release system software which was shipped on the A3000 this week. These disks and the KickIt command allow most developers to install 2.0 on Amigas other than the A3000 and soft-kick into 2.0 using the KickIt command. Developers who have purchased A3000's will receive the A3000 release software installation disks under separate cover. Updated 2.0 Includes, Autodocs, and Examples should be available shortly after the Developer's Conference. Instructions for installing 2.0 follow. Instructions ============ ***** This Release consists of the following software: - Kickfile disk containing 512K 2.0 Kick.[version].20 file - Workbench 2.0 - Extras 2.0 ***** Where to find some important commands and files: - BugReport In ReportForms file on Kickfile disk - CompatReport In ReportForms file on KickFile disk - CPU Workbench/c directory (cpu.doc in Kickfile/tools) - KickIt Tools directory of Kickfile disk - Kick.[vers].20 In the root of the Kickfile disk - SampleStartup Kickfile disk ***** How to boot 2.0 In order to use the new 2.0 Workbench, you must "soft-kick" the 2.0 operating system "kick.[version].20" using the new "Kickit" command (both found on the Kickfile disk). Owners of GVP accelerator plus harddisk cards will need to get special PALs from GVP, and get a special $F00000 kickfile from CATS for use with the mmu soft-kick program (Mmukick). If you need the special MMUKICK disk, call CATS Administration at 215-431-9180 to have it mailed to you. NOTE - You should always back up your harddisk and work disks before installing new operating system software. ***** Easy Ways To Try 2.0 The simplest setup for trying 2.0 is ANY MODEL Amiga whose first or only autoconfig expansion card is RAM. Some simple setups include an A2000 or A1000 with a 2-meg RAM expansion. The new KickIt command allows you to "soft-kick" a special 2.0 operating system file so that you can use the 2.0 Workbench disk. The easy no-installation way to boot 2.0 on a simple setup is as follows: --------------------------------------------------------------------------- 1. Boot normally with 1.3 and open a shell or CLI 2. Insert the Kickfile disk in df0: and type: df0:Tools/kickit df0:kick.38n.20 (kickit will read the kick.38n.20 file and reboot your machine) 3. When the 2.0 Workbench disk prompt appears, insert the 2.0 Workbench disk. NOTE - If you have an autoboot harddisk, pull the Kickfile disk during the KickIt reboot, and insert the 2.0 Workbench disk to boot the 2.0 Workbench. See the SampleStartup file on the Kickfile disk for instructions on installing 2.0 so that you can easily boot into your choice of 1.3 or 2.0 from your harddisk. --------------------------------------------------------------------------- You don't need an MMU, or coprocessor, or new ROMs, or ECS. You just need a first configured autoconfig RAM device 1 meg or larger. (might work with a 1/2 meg autoconfig card - not tested). In addition to "plain" RAM expansions, the A2620 and A2630 coprocessor carsd may be used because they contain RAM which is configured first. Third party coprocessor+RAM cards should also work. Some harddisk+RAM or coprocessor+harddisk+RAM cards may work, but only if they configure their RAM first (the A590 and A2091 do not, but you could use a 2091 if you have a separate RAM card in the right slot). GVP owners should see the earlier notes about GVP. ***** The following items are all OPTIONAL when using 2.0: 68020, 68030, MMU, Enhanced Chip Set, multisync monitor, additional hardware If you have a 2620 or 2630, the soft-kicked 2.0 will be in 32-bit RAM (fast!). If you have a harddrive, you can set your system up so that you can boot boot into 1.3 OR 2.0 off your harddrive (see SampleStartup on Kickfile disk). If you have the Enhanced Chip Set you will be able to try the new video modes (most require a multisync monitor). ***** Special instructions for PAL machines and Multisync monitors Addmonitor can be used in your startup-sequence to add the PAL A2024, and multisync monitors. Or you can drag the monitor icons into the Workbench startup drawer. (However, you may not be able to boot in the proper mode in that case.) addmonitor NUM=2 NAME=pal.monitor addmonitor NUM=3 NAME=multisync.monitor addmonitor NUM=4 NAME=A2024.monitor The initial setting is for a 640x200 NTSC screen. To try another size, use the WBSCREEN preferences editor (after either adding the ADDMONITOR calls to the Startup-Sequence or by dragging the icons to the WBStartup drawer) ========================================================================== SOME GENERAL COMPATIBILITY PROBLEM AREAS ---------------------------------------- Generally fatal with any new OS: - Calling ROM code directly - Requiring all free RAM - Shaving stack size too close Often disastrous with new OS or hardware: - Depending on unsupported side effects - Bad flags/registers/condition code handling - Poking / peeking private system structures - Assuming current choices or configurations - Processor speed/instruction dependencies Strap: - romboot.library is gone - boot from other floppies (+5,-10,-20,-30) Exec: - Everything has moved, of course - Exec handles early expansion - Cold Capture done later - Exception/Interrupt vectors may move (VBR) - Size and types of MemHeaders may change - Survive reboot may break - new provided Expansion: - Two pass config, address slot reordering - ExpansionBase private - Use FindConfigDev() DOS: - Real library base with regular LVO vectors - Stack use all changed (variables, direction) - New packet and lock types - Process struct bigger, roll-your-own fails Workbench: - New sizes, depths, modes, fonts - Default Tool searches paths - New Look icons ( boxed ) Intuition: - Private IBase variables moved/changed - Poking IBase Max Mouse variables now a no-op - Poking other private variables may be fatal - Larger screens, new modes, overscan support - GetScreenData() not enough to clone a screen - Scrollable screens (Left-Amiga/select stolen) - Rawkey|Vanillakey gives raw fkeys, help, etc. - Move SimpleRefresh win may not send refresh Layers: - Use NewLayerInfo() to create not FattenLayerInfo,ThinLayerInfo,InitLayers - Simple-refresh preserves all pixels it can Graphics: - Copper lists changed, illegal poking breaks - ColorMap bigger, must GetColorMap() to create - Blitter rtns decide ascend/descend on 1st plane - Some flying mode changes may break - GfxBase DisplayFlags and row/cols may != WB Fonts: - Some format changes (old format supported) - Private format of .font files has changed - Default font may be larger, proportional - Topaz is now sans-serif - Size created via bitmap scale if requested CLI / Shell: - Many more commands built-in (no longer in C:) - Limit of 20 gone, DOSBase CLI table changed - EOF char passed for Close Gadget in CLI This is -1L from CON: getchar, close gad esc seq from raw - Uses simple-refresh character-mapped console Console: - CON: default is character-mapped console - Superbitmap console now has cursor (bug fixed) Audio.device: - Not initialized until used - This means lo-mem open failure possible Gameport.device: - Currently exclusive access Serial.device: - Clears io_Device on CloseDevice() Multi-Serial Boards: - May not support all params - So serial SetParams command may fail Timer.device: - Timer.device now trashes request as doc'd - IO_QUICK may defer and reply as doc'd Trackdisk: - Private trackdisk structures changed - Buffer freeable, lo-mem open fail possible CIA Timers: - CIAA Timer A is used by the system - CIAB Timer A and B currently available Hardware: - New RAM amounts and addresses - 32-bit addrs (trashed hi byte now matters) - New registers and bits - Battery-backed clock different New Look: - New default colors, new gadget images - Inner border line render - Window borders filled on active AND inactive ========================================================================== BUG AND COMPATIBILITY REPORT FORMS ================================== There are two different report forms: 1. Compatibility Report (for 3rd party product compatibility problems) 2. System Bug Report (for reporting Kickstart, Workbench, Extras problems) Submitted reports must include a TELEPHONE number. Reports must be CLEAR, COMPLETE and CONCISE. Based on your bug report alone, we must be able to REPEAT the problem. Completed reports may be submitted by any of the following methods: USENET: mail "uunet!cbmvax!bugs","rutgers!cbmvax!bugs" or "bugs@commodore.COM". (email suggestions to "suggestions" instead of "bugs".) BIX: Post in your closed conference (amiga.com/bugs or amiga.update/bugs) or bixmail to afinkel. USMAIL: Amiga Software Engineering, ATTN: BUG REPORTS, Commodore Business Machines, 1200 Wilson Drive, West Chester, PA 19380-4231, USA The next pages contain the System Bug Report Form, followed by the Compatibility Report Form. Note - please fill in all ":" keyword lines on the same line with the keyword. For example, Name: Joe Wizard SYSTEM BUG REPORT - For Bugs in System Commands, OS, or Hardware ================================================================ Date: Name: Company: Address: Developer#: EMail: Phone: Report Class: [] Fatal [] Problem [] Cosmetic ### Brief Bug Description: ### Bug Location: [Hardware, Documentation, Software, Other]: ### I know this works with: [] 1.3 [] 68020/30 [] ECS ### Your Configuration [Model number, number and type of disks, memory, ### add-on equipment, special chip sets, etc.]: ### Revisions [Kickstart/Workbench revision numbers, etc.]: Kickstart Rev: Workbench Rev: Other Revs: ### Other software running or resident at the time of the bug [should be ### "none"]. Don't forget any commands hidden in your startup-sequence!: ### Bug Generation Procedure [remember that someone else will be trying to ### repeat this bug based on your description alone]: ### Other important details: ### Related bugs: COMPATIBILITY REPORT - For 3rd Party Product Compatibility Test Results ======================================================================= Date: Name: Company: Address: Developer#: EMail: Phone: ### Third Party Product Information ( Omit "Inc.", etc. in Company name ) ProductName: Product Version: Product Company: Report Class: [] Fatal [] Problem [] Cosmetic [] OK !!! ### ---- Cut here if report type is "OK", else complete rest of report ---- ### ----- Please submit a separate report for each distinct problem ------- ### Brief Problem Description: ### Problem Location [Hardware, Documentation, Software, Other]: ### I know this works with: [] 1.3 [] 68020/30 [] ECS ### Your Configuration [Model number, number and type of disks, memory, ### add-on equipment, special chip sets, etc.]: ### Revisions [Kickstart/Workbench revision numbers, etc.]: Kickstart Rev: Workbench Rev: Other Revs: ### Other software running or resident at the time of the problem [should be ### "none"]. Don't forget any commands hidden in your startup-sequence!: ### Problem Generation Procedure [remember that someone else may need to ### repeat this problem based on your description alone]: ### What are you doing in this part of your code or hardware ? ### Other important details: ### Related problems: ========================================================================== Sample Startup ============== This file describes a way for 68020/MMU, 68030, or autoconfig RAM board owners to set up their harddisk system so that they can choose to boot into either 1.4 or their normal 1.3 environment. This sample startup uses "Kickit". GVP accelerator + harddisk owners must use MmuKick instead, with a special $F00000 Kickfile from CATS, and special PALs from GVP. Contact CATS Admin (215-431-9180) if you need the special $F00000 kickfile; contact GVP about the PALs. Users without harddisks should be able to modify the Boot Partition startup to work off diskettes by referencing floppy volume names rather than harddisk partitions and directories. Part I describes a minimal boot floppy and floppy startup for 2090 owners. This minimal boot floppy is just enough get you to the dh0: "boot" partition and call its s/startup-sequence as if you had started there. (SCSI owners - change the dh0:'s to dh2:'s) Part II describes a minimal boot partition and startup to let you choose between your normal 1.3 environment OR 1.4 when you reboot. WARNING - Please BACK UP your hard disk and floppies, and read the KnownBugs files before testing any pre-release version of the operating system. NOTE - Partition mounting under 1.4b requires that you provide a modified mountlist. The sample startup references your old 1.3 mountlist as devs:mountlist1.3, and your modified mountlist as devs:mountlist1.4. In the modified mountlist, the FileSystem lines for your FFS partitions must be deleted or commented out C-style like this: /* FileSystem = l:FastFileSystem */ AND the DosType for all FFS and old-FS entries must be correct: DosType = 0x444F5301 (for FFS) or DosType = 0x444F5300 (for old-FS) ------------------------------------------------------------------------ Part I - Minimal Boot Floppy for 2090 Owners A. Minimal Contents of Boot Floppy =============================== NOTE: You should use 1.3 files/commands on your boot disk or partition, but future revisions of 1.4 may require some 1.4 files when booting. SetPatch, FastMemFirst, FastFileSystem, and Disk-Validator are not found on (and not used by) Workbench 1.4. ; NOTE - Copy the 1.4 Workbench system-configuration here to get the ; proper 1.4 colors. Whenever you change "classic" preferences within ; 1.4 (colors, printer, etc.), copy the 1.4 devs:system-configuration ; to this boot floppy. c (dir) Assign Binddrivers CD Echo EndIf If SetPatch version System (dir) FastMemFirst L (dir) disk-validator RAM-Handler devs (dir) system-configuration s (dir) startup-sequence Libs (dir) icon.library Expansion (dir) HdDisk HdDisk.info B. Startup-Sequence for Boot Floppy ================================ cd c: version >NIL: graphics.library 36 IF WARN SetPatch >NIL: r ;patch system functions Sys:System/FastMemFirst >NIL:; move C00000 memory to last in list ENDIF BindDrivers assign t: ram: ;=== NOTE - SCSI owners change dh0's below to dh2's assign >NIL: dh0: exists if not warn assign sys: dh0: assign c: dh0:c assign s: dh0:s assign l: dh0:l assign devs: dh0:devs cd sys: execute s:startup-sequence endif ------------------------------------------------------------------------ Part II - Minimal 1.3/1.4 Boot Partition A. Minimal Contents of Boot Partition (Use 1.3 files where available) ================================== NOTE: You should use 1.3 files/commands to get to your 1.4 Workbench partition or directory, but future revisions of 1.4 may require some 1.4 files when booting. SetPatch, FastMemFirst, FastFileSystem, and Disk-Validator are not found on (and not used by) Workbench 1.4. Copy the 1.4 Workbench system-configuration here to get the proper 1.4 colors. Whenever you change "classic" preferences within 1.4 (colors, printer, etc.), copy the 1.4 devs:system-configuration to this boot partition (or to your boot floppy if your hard disk is not an autoboot drive). c (dir) ask assign Echo else endif execute if Kickit Mount setcpu SetPatch version system (dir) FastMemFirst l (dir) Disk-Validator FastFileSystem devs (dir) mountlist1.3 mountlist1.4 [ramdrive.device] system-configuration [if autoboot] s (dir) startup-sequence kick.38n.20 (^^^ version# between the .'s may vary; final .20 means for $200000) Optional RAD directory (same as minimal boot floppy) (This RAD just fits LoCyl=0 to HiCyl=6) ==================================================== c (dir) Assign Binddrivers CD Echo EndIf If SetPatch version System (dir) FastMemFirst L (dir) disk-validator RAM-Handler devs (dir) system-configuration s (dir) startup-sequence Libs (dir) icon.library Expansion (dir) HdDisk HdDisk.info B. Startup-Sequence for Boot Partition =================================== NOTE! Please read through all of the comments in this startup. The comments point out the lines and areas you must change depending on your configuration. ; Sample harddisk startup-sequence to boot into either 1.3 or 1.4. ; ; NOTES: ; ; Non-autoboot (2090) users will also need the minimal boot disk ; described earlier, and can comment out the SetPatch and FastMemFirst ; lines in this script (They will be done by the boot disk startup). ; ; The system in this example is set up as follows: ; ; Small initial normal-FS "boot" partition (SYS:, becoming INIT:) ; containing KickIt and the specially linked Kick.[version].20 file. ; If you do not have room in INIT: for the Kick file, you can ; mount another partition to load it from. ; ; The INIT: partition is either directly booted (autoboot) or quickly put ; in control by minimal boot disk described above (non-autoboot). ; ; This example system also contains: ; 1.3 FFS Workbench partition called WB3: (mounted for 1.3) ; 1.4 FFS Workbench partition called WB4: (mounted for 1.4) ; FFS user work partition called FH0: (mounted for both 1.3 and 1.4) ; ; Alternately, you could just store each Workbench in its own directory, ; rather than in separate partitions. ; ; IMPORTANT: During the post-soft-kick startup sequence, you should ; not echo or output any information to the console until AFTER ; the Workbench 1.4 startup completes its IPrefs initialization. ; Console output will cause the initial shell window to open ; and this should not be done until after IPrefs configuration ; of the Workbench screen. ; THE SCRIPT ;=== Convenient label for referencing this boot partition assign INIT: SYS: ;=== Are we running 1.3 or 1.4 Kickstart ? version >NIL: graphics.library 36 IF WARN ;=== Currently running 1.3. Ask if 1.4 desired. ask "Kick 1.4 (y or n) ?" IF WARN ;=== You asked for 1.4 ;=== If necessary, change the kick file name to reflect current ;=== version, and if you have it stored on a different partition, ;=== first mount that partition with your 1.3 mountlist KICKIT INIT:kick.38n.20 Quit ;=== (Your Amiga now reboots) ELSE ;=== You want 1.3 ;=== Comment out this SetPatch and FastMemFirst if you are a 2090 ;=== owner booting from the minimal boot disk (boot disk does them). SetPatch >NIL: r Sys:System/FastMemFirst >NIL: ;=== If you need to mount partitions, mount using 1.3 mountlist mount FH0: from devs:mountlist1.3 mount WB3: from devs:mountlist1.3 ;=== Assign SYS: to your Workbench 1.3 disk, partition, dir, etc. assign SYS: WB3: ENDIF ELSE ;=== Currently running 1.4 ;=== If you need to mount partitions, mount a copy of your mountlist ;=== which you have modified for 1.4 (here called mountlist1.4) !!! ;=== FFS entries in your 1.4 mountlist should have their Filesystem ;=== lines deleted or commented out, and ALL partitions ;=== being mounted must have their correct DosType listed. ;=== (DosType = 0x444F5301 (FFS), DosType = 0x444F5300 (normalFS)) mount FH0: from devs:mountlist1.4 mount WB4: from devs:mountlist1.4 ;=== Assign SYS: to your Workbench 1.4 disk, partition, dir, etc. assign SYS: WB4: endif ;=== Assign all system directories to the selected Workbench (1.3 or 1.4) assign c: sys:c assign s: sys:s assign l: sys:l assign fonts: sys:fonts assign devs: sys:devs assign libs: sys:libs ;=== Set any assignments and paths you want for both 1.3 and 1.4 ;=== (my examples shown in following comments) ; assign H: FH0: ; assign INCLUDE: h:Include1.4 ; path H:DevTools H:PdTools H:s add ;=== Temporarily assign T: to RAM: for temporary scripts ;=== (Don't makedir ram:T or subsequent makedir ram:T in startups will fail) assign T: RAM: ;=== Can get rid of the INIT: assign assign INIT: ;=== CD where you want to be cd ram: ;=== Now, enter either 1.4 Workbench, or your normal 1.3 environment ;=== ;=== Are we running 1.3 or 1.4 Kickstart ? version >NIL: graphics.library 36 IF NOT WARN ;=== We are running 1.4 ;=== For 1.4, just go to the 1.4 startup-sequence EXECUTE SYS:s/startup-sequence ELSE ;=== We are running 1.3 ;=== Here execute or insert the rest of your normal 1.3 startup, ;=== minus the volume mounting and system directory assignments ;=== (SYS:, c:, etc) which were done earlier in this script. ;=== This simple example just calls the 1.3 SYS:s/startup-sequence. ;=== You may have additional assigns, background tools, paths, etc. ;=== Keep any tools or initializations that could interfere with ;=== 1.4 testing either here or within your 1.3 startup sequence. ;=== 2090 owners may want to create a RAD: for normal rebooting. ;=== Here, the dir INIT:RAD (a copy of the minimal boot disk's contents) ;=== is copied to a RAD. Just uncomment if you want this feature. ;=== This RAD will just fit in locyl=0 to hicyl=5. ;=== Note that RAD will not survive a rekick. ; ; assign >NIL: RAD: exists ; if warn ; echo "Mounting RAD:... " NOLINE ; mount RAD: from INIT:devs/mountlist1.3 ; if not exists RAD:c ; echo "setting up... " NOLINE ; relabel drive RAD: name RamDrive ; copy INIT:RAD RAD: all quiet ; endif ; echo "Done" ; endif EXECUTE SYS:s/startup-sequence ENDIF THE SUBSOFTWARE ---------------