Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!philabs!seismo!harpo!eagle!mhuxl!houxm!ihnp4!clyde!akgua!sb1!sb6!sjt From: sjt@sb6.UUCP Newsgroups: net.micro.6809 Subject: Re: OS-9 and double sided disks Message-ID: <150@sb6.UUCP> Date: Sat, 19-Nov-83 13:25:51 EST Article-I.D.: sb6.150 Posted: Sat Nov 19 13:25:51 1983 Date-Received: Sun, 20-Nov-83 04:23:32 EST References: bbncca.321 Lines: 63 Since Steve Dyer obviously did not get my previous responce on using debug to change modules I will post this one as a followup. After you quit the debug module you have only to SAVE the module that you just modified. This will put an exact copy of the module "in memory" onto your current work directory. Then uset ATTR and verify to update the module. The exact sequence should be: verify u < module to update > new updated module attr new updated module e pe this sets execute and public execute After you have formatted a new disk use os9gen to build yourself a new boot module. It will probably be necessary to save all modules out of memory and include them one at a time. Read the book since there are several that you do not include in the os9boot. OS9, OS9P2, INIT, BOOT <--- don't include Frank Hogg also published a letter outlining the mods to make in the modules of OS 9 for the COCO. To paraphrase: change the CCDisk module and if you are game BOOT. a) make changes below as required 1. byte #1(old value) #2(new value) ==== ============ ============ 0007 81 82 Rev number 0008 D3 D0 checksum 01FE 13 10 speed 10=6ms 11=12ms 12=20ms 13=30ms 0204 22 08 delay 0205 2E 8B " 0210 04 41 make drive 2 back of d 0 0211 40 42 make d 3 back of d1 02DD 43 40 speed 40=6ms 41=12ms 42=20ms 43=30ms 02E9 03 00 speed 00=6ms 01=12ms 02=20ms 03=30ms 0308 52 43 crc 0309 4C BC crc 030A EB 6E crc If you make changes exactly as listed you SHOULD not have to do a verify, I do one every time since it is safer to do so. 2. save the module onto disk and then gen yourself a new boot( or since you did a mod to the Rev number just have your startup do a load newmodule each time you boot and this one will overlay the earlier version) I did modify the modules on the RS OS 9 and it does work! This procedure is required since the device descriptors on the RS are different from the real OS 9 (which is what I run since I do all my development on a SWTPC type system). I hope this is of some help as OS 9 is not easy to learn and is not as user friendly as it should be. Sidney Thompson