=============================================================================== Volume 1 Issue 11 January 1990 ------------------------------------------------------------------------------- _____ _____ ____ ____ ___________ / | / | | | | | | _____ \ / |/ | | | | | | | \__\ / /| /| | | | | | | | / / | / | | | | | | | | / / | / | | | | | | | | ____ / / | / | | | | | | | | |__ \ / / | / | | \ \_______| | | |_________\ \ |___| |/ |___| \____________| |________________\ __ __ ____ ______ _____ ____ | \ || / __ \ --,,-- |,--- //--\\ ||\\ || || || || || \\__ || \\ || || || || |,== ---\\ || \\|| ||__|| || ||___ ___// || \_| \____/ || |____ ___/ The Official Newsletter of: The Motorola Users Group of London =============================================================================== =============================================================================== Beginners Month =============================================================================== January 1990 MUG Notes Page 1 Motorola Users Group of London 1989 EXECUTIVE PRESIDENT Stan Bischop 500 Osgoode Dr. #122. London N6E 2G9 668-7277 VICE- PRESIDENT Erik Tromp 1 Partridge St.. London N6A 1T4 679-6168 SECRETARY Judy Daviau 500 Osgoode Dr. #122 London N6E 2G9 668-7277 TREASURER Sheila Smith 11 Bridle Path London N6Y 2H1 672-4913 APPOINTED POSITIONS MEMBERSHIP CO-ORDINATOR Judy Daviau 500 Osgoode Dr. #122 London N6E 2G9 668-7277 NEWSLETTER EDITOR Sheila Smith 11 Bridle Path London N6Y 2H1 672-4913 P.D.LIBRARIAN Diane Gubbels R.R. #1 Miller Rd. Delaware N7G 3H8 652-3844 PUBLIC RELATIONS Gerry Thomas 232 Oakland Ave. London N5V 4H1 659-1374 B.B.S. SYSOP Wayne Morrison 532 Pinetree Dr. London N6H 3N1 471-5064 NEWSLETTER PUBLISHER Wayne Morrison 532 Pinetree Dr. London N6H 3N1 471-5064 TECHNICAL ADVISORS Stan Bischop 500 Osgoode Dr. #122 London N6E 2G9 668-7277 Wayne Morrison 532 Pinetree Dr. London N6H 3N1 471-5064 MUG Line B.B.S. 24 Hours Daily 300/1200 Baud N-8-1 641-0927 DISCLAIMER The opinions expressed by the authors are not necessarily those of the Motorola Users Group of London, the editors, or the club members. While we try to make sure that all software and hardware projects in this newsletter have been tested and do work, we will not be responsible for any damage to your own personal equipment resulting from using information contained in this newsletter. COPYRIGHT NOTICE Contents of this newsletter are copyrighted 1989 by the Motorola Users Group of London. Reproduction by any means other than for the personal use of members without prior written consent is forbidden. Other non-profit computer clubs may make use of the enclosed material as long as written acknowledgement is made of the source. MANDATE This newsletter is published by and for the Motorola Users Group of London. This club has no affiliation with the Motorola Corporation. This club is a non-profit organization for anyone that may have an interest in Motorola 68XX and 68XXX based microcomputers and the use and exchange of information about these machines. January 1990 MUG Notes Page 2 Table of Contents Page Item ==== ==== 1.....................List of Officers and Mandate 2.....................Table of Contents 3.....................P.D. Notes 4.....................About Basic09 6.....................Current Membership List 7.....................EZ-Gen Update 9.....................Making a New BootFile 14....................1990 Calendar (Second Half) SPECIAL INTEREST GROUPS The Motorola Users Group of London sponsors two special interest groups (SIG's for short). For January, the beginners SIG is being held at Wayne Morrison's (532 Pinetree Drive) on Tuesday nights starting at 7:00 P.M. The advanced SIG meets at Judy Daviau's (122-500 Osgoode Dr.) on Wednesday nights also starting at 7:00 P.M. Whether you have just started out or you are an experienced hacker, there should be something of interest for you! January 1990 MUG Notes Page 3 ***************** P.D. NOTES ***************** I hope everyone has had a good beginning to the new year. The weather sure has improved. This month we have Al Graig giving us our P.D. demo, he will be covering two disks this time. They are Mug P.D. 043, and COCO3 012. On disk 043 we have a banner program, that is pretty good with choice of background, with three widths to choice from, and easy on screen instructions. No messing thru doc's on this one, just run the program and have lots of paper handy. Biochart will print out your biorythm on to paper, so you can see if you should go to work that day. DIRLIST keeps those listings on to paper so you can see whats on all those precious disks of yours. DISKDUMP will take the contents of a disk or a sector and put it onto paper. Comes in handy looking for that bug on a disk. We have two joystick games on the disk PEGWARS, you have two build a wall around your opponent. Pong, you catch your man on a trampoline. SUPDUP, will duplicate your disks for you, and TRAK--40 will let you use all 40 tracks on your drives if you have the capability. All this and more is available on this disk. COCO3 012 has many utilities on it. 2COL.bin will take any ASCII file and print it to screen or printer in 2 columns. Nice to look at any way. When was the last time you cleaned your drives heads properly? They should be moving back and forth over the cleaning disk. CLEAN.bas will accomplish this for you. DIARY.bas, allows you to keep an electronic diary on tape or disk and is password protected. We have another copy program, this one being a multidisk upgraded for the COCO3. Looking for a spreadsheet program, DISKCALC.bas might be able to handle the job. It only supports disk and not cassette. Last but not least we have a viewer program, with some art work along with it. Hope to see everyone at the meeting this month. It is that time of the year we spend inside and work over the keyboard. See you next month. GERARD January 1990 MUG Notes Page 4 ABOUT BASIC09 By W. Morrison Over the last few months we have written and explored some Basic09 modules. This month I hope to be able to tie some of these together and provide you with a demonstration of how a final program works. At the same time I hope to provide you with an example of how you can manipulate data on your computer screen. Interestingly enough, this concept of manipulating this data will also work under Disk Basic, but, of course, the code will be quite different. Start up your Basic09 compiler and enter the following code; PROCEDURE demoscreen DIM count:INTEGER DIM timer:REAL count=0 PRINT CHR$(12) PRINT CHR$(5); CHR$(32) RUN locate(10,3) PRINT "This is a demonstration of screen printing and clearing" RUN locate(20,5) PRINT "NAME:" RUN locate(17,6) PRINT "ADDRESS:" RUN locate(20,7) PRINT "CITY:" RUN locate(19,8) PRINT "PHONE:" RUN locate(8,10) PRINT "Notice that neither this line nor the top line are disturbed" LOOP count=count+1 EXITIF count>3 THEN ENDEXIT RUN locate(27,5) PRINT "Fred Smith" RUN locate(27,6) PRINT "111 First St." RUN locate(27,7) PRINT "London" RUN locate(27,8) PRINT "555-1212" FOR timer=1 TO 1000 NEXT timer RUN partcls(27,5,8) RUN locate(27,5) PRINT "John Doe" RUN locate(27,6) PRINT "22 Second Ave." RUN locate(27,7) PRINT "London" RUN locate(27,8) PRINT "666-6666" FOR timer=1 TO 1000 NEXT timer RUN partcls(27,5,8) January 1990 MUG Notes Page 5 ENDLOOP PRINT CHR$(5); CHR$(33) RUN locate(20,19) PRINT "Thank you for trying this demo" After you have all the typos cleaned up load in LOCATE and PARTCLS from last time (you did save them, right?). From the B: prompt type run demoscreen and sit back and watch. If it worked properly, you should have watched the entering and replacing of data without the surrounding titles and comments being damaged. Also, no scrolling occured and the cursor disappeared for the duration of the program. Lets disect this bit of code and see what I was trying to accomplish. The first two lines dimension two variables, "count" and "timer", the first as an integer and the latter as a real number. I chose real because it takes longer for the machine to process a real number, and my intent for this variable is to use it in a timing loop, and after all, timing loops are used to slow down program execution. The next line sets the variable "count" equal to 0, and the line after that clears the computer screen. Now the program really begins. Line five turns off the cursor, line six runs the procedure "locate" which moves the cursor to the screen position given in the brackets, and seven prints a string starting at that location. The next ten lines locate and print more text either as titles or comments on our computer screen. At this point we come to a line which says simply LOOP. This indicates that we want to start a loop at this point in the procedure. This loop displays the changing name and address data that we see during program execution. To study the loop in detail, line one adds one to the value of the variable counter (remember that we set the value of this to 0 previously). Line two provides us with a way to get out of what would otherwise be a perpetual loop. When the value of "count" becomes greater than three, the program will exit this loop. Without this the program would never stop, it would just keep repeating itself until you either pressed the break key or shut off your computer. Line three completes the conditions for exiting the loop. Lines four to eleven print text at predetermined screen locations using the "locate" module to position the strings. Lines twelve and thirteen pause the program execution for about three seconds so that you can read the name and address. Line fourteen clears out the current name and address from the screen, using three numbers to indicate the x and y co-ordinates to start at, and the y co-ordinate to stop at and the remaining lines from here to the line reading ENDLOOP repeat this process using other data. ENDLOOP tells Basic09 to go back to the line LOOP to continue program execution and the next line turns the cursor back on. The last two lines simply locate and print one final text string. When you exit the loop at the line starting with EXITIF, it will then go to the first line after the line ENDLOOP to continue. This is how the final text string gets placed on the screen. If you are interested in trying this, but do not want to type in the code, I will be making the three modules used here available under the name "Demoscreen" on the BBS in the OS-9 download area. I hope my explanation for this module made sense to you, and next time we will explore this language some more. January 1990 MUG Notes Page 6 The Motorola Users Group Membership List as of December 11, 1989 (* - These are the current Executive) No. Name Address Phone# ---- ------------------ ----------------------------------------- -------- * 1) Stan Bischop 122-500 Osgoode Dr. London N6E-2G9 668-7277 * 2) Sheila Smith 11 Bridle Path London N6Y-2H1 672-4913 * 3) Gerry Thomas 311-232 Oakland Ave. London N5W-4M1 659-1374 * 4) Wayne Morrison 532 Pinetree Dr. London N6H 3N1 471-5064 * 5) Judy Daviau 122-500 Osgoode Dr. London N6E-2G9 668-7277 6) Gerry Davis 1053 Francis St. London N5W-2L8 453-8686 7) Jason Hollander 20 Bridlington Rd. London N6E-1X4 649-1902 7) Walt Hollander Same as above 8) Rick Tower 1106 Gatewood Rd. London N5Y-4Z5 663-8325 * 9) Diane Gubbels R.R. # 1 Deleware N0L-1E0 652-3844 9) Gerard Gubbels Same as above 10) Lawrence Schembri 2 Augusta Cres. London N6E-2E1 681-4652 11) Vern Smith 1065 Chippewa Dr. London N5V-2T8 453-6459 12) Stuart Robb 301-9 Grosvenor St. London N6A-1Y3 433-4456 13) Michael Warcholyk 403-274 Dundas St. London N6B-1T6 673-6879 14) Stephen Coveney 311-241 Simcoe St. London N6B-3L4 14) Nancy Coveney Same as above 15) Peggy Griffin 78 Beechmount Cres. London N6E-2J4 681-3587 15) Bob Griffin Same as above *16) Erik J. Tromp 1 Partridge St,RearBsmt London N5Y-3R5 679-6168 17) Michael Constant 207-1830 Dumont St. London N5W-2S1 451-3641 18) Len Fluhrer 129 Pond Mills Rd. London N5Z-3X3 686-6542 19) Roger Ross 767 Second St.Apt301 London N5V-3C4 452-1647 20) Ernest Gardner 101 Sunset Dr. Upper St. Thomas N5R-3B5 631-1402 22) Freda Murray London 23) Michael Gardner 1211-112 ArbourGlen London N5Y-2A2 672-7875 24) Calvin Thatcher 1217-170 Kent St. London N6A-1L4 679-8012 25) Wayne Pugh 132 Emery St. E. London N6C-2E1 663-9026 26) Marvyn Hooper RR# 3 Waterford N0E-1Y0 443-7809 27) Al Craig 40 Pitt Street Port Burwell N0J-1T0 874-4393 28) Aric Diament P.O. Box 292 Woodstock N4S-7X6 539-5163 29) Howard Strong 774 Elias St. London N5W-3P1 451-8830 Total Memberships = 28 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * T H E N E X T M E E T I N G O F * * _____ _____ ____ ____ ___________ * * / | / | | | | | | _____ \ * * / |/ | | | | | | | \__\ * * / /| /| | | | | | | | * * / / | / | | | | | | | | * * / / | / | | | | | | | | ____ * * / / | / | | | | | | | | |__ \ * * / / | / | | \ \_______| | | |_________\ \ * * |___| |/ |___| \____________| |________________\ * * * * Will Be Held On January 9, 1990 * * 6:30pm to 9:00pm * * London Central Public Library * * Lower Level * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * January 1990 MUG Notes Page 9 Downloaded CIS 21 Jan 88 Making a New Bootfile by Mark Griffith There has been some discussion in the Forum lately about the easiest and best way to generate a new OS9 bootfile. The major concern seems to be over the CONFIG utilty that comes with the OS9 production disk. CONFIG is not a very easy utility to use and has some real limitations. It's understandable that some of the newer OS9 users are having problems. Most new users are also put-off by the OS9GEN utility as being even more difficult to use. OS9GEN is only a small part of the procedure required to make a new boot disk and is somewhat of a mystery. The purpose then of this file to to describe a method to create a new boot disk using OS9GEN with a minimum amount of fuss and bother. Most of the work required to make a new boot disk has been done for you by Microware. All of the modules that you might need are placed in a directory on the second OS9 disk called MODULES. If you look at this directory using DIR, you'll see something like this: /d1/modules: aciapak.dr d2_35s.dd modpak.dr t3.dd Bootlist d2_40d.dd os9p2 term_vdg.dt CC3Disk.dr d2_80d.dd p.dd term_win.dt cc3go d3_35s.dd Pipe.dd vdgint.io CC3IO.dr ddd0_35s.dd Pipeman.mn w.dw clock.50hz ddd0_40d.dd Piper.dr w1.dw clock.60hz grfint.io printer.dr w2.dw d0_35s.dd HELP RBF.mn w3.dw d0_40d.dd Init SCF.mn w4.dw d1_35s.dd IOMan sio.dr w5.dw d1_40d.dd m1.dd t1.dd w6.dw d1_80d.dd m2.dd t2.dd w7.dw 48 files. 23 sectors (5888 bytes) free on "Color Computer 3 OS-9 LII" As you'll notice, most of the files have an extension to their name. These extensions have the following meanings: Extension Meaning --------- ------- .dd A device descriptor .dw A device window .dr A device driver .mn A file manager .io An input/output manager .dt A display terminal driver January 1990 MUG Notes Page 10 The first thing you must do in creating a new bootfile is to decide which modules you want to include in it. This is not hard at all, although there are some modules that are required to be present in the bootfile. Those that you MUST have are: OS9P2 IOMan Init CC3Go Clock.60hz RBF.mn CC3Disk.dr D0_35S.DD SCF.mn CC3IO.dr VDGINT.IO GRFINT.IO TERM_VDG.DT W1.DW This list of modules is contained in the file "/modules/bootlist" on the same disk as the modules directory. The modules named here are those that are REQUIRED to have a minimal running OS9 system. However, you can add to this list to create a custom bootfile for your system. Just use the BUILD utility, EDIT, or any other text editor/word processor that you might have. Notice that there are provided for you the disk drive descriptor modules to use either 35 track single-sided, 40 track double-sided, or 80 track double-sided disks on your system. To use one or the other type, all you do is to delete the entry for "D0_35S.DD" in the list above and replace it with the descriptor you want. If you want to add drive 1 and drive 2, include those descriptor module names too. You should also include one of the "/DD" modules in your bootlist to remain compatible with the latest software being developed. Now, just include in the bootlist all the remaining modules you'll need. For example; you're going to be using a printer, so include the p.dd and PRINTER.dr modules. To use the /T2 terminal port descriptor which is required for many of the OS9 terminal software programs, include the t2.dd descriptor and the ACIAPAK.dr driver. At this point you should include in the bootlist all the modules you'll ever think you'll need. You can't really have enough modules in your bootfile since there is always some time when you might need it and loading modules, especially system drivers and descriptors, into memory with Level II is a risky business at best. So put them all in there....even the NIL device and the NILDRV driver. Also, don't forget to include all the modules needed to work with pipes. If you have any doubts as to what to include, put it in! The worst that can happen is you'll end up with a bootfile that is larger than 64K and it won't load and run when you try to boot OS9. However, that is a remote possibility. For example; here is the bootlist that I use. It has some names you might not recognize and some that I've changed, but you'll get the picture of what you might need in your bootlist: January 1990 MUG Notes Page 11 OS9p2 OS9p3 Init IOman RBF CC3Disk D0 D1 DD SCF.kd Aciapak T2 CC3IO GrfInt VDGInt Term.win W W1 W2 W3 W4 W5 W6 W7 Ramdisk Printer P NILDRV NIL Pipeman Piper Pipe WizAcia M2W CC3Go Clock Notice that I've included both the GrfInt and VDGInt device drivers. This is so I can use both screen types, even though I only need the one device descriptor, the one for windows, TERM_Win. You should do the same. Also, I've included all the window device descriptors even though I only use three or four at one time. Lets face it, this little machine can do some powerful stuff, but not all of us write our applications and utilities to use the same window devices. So, you must have any window descriptor in your bootfile that might be used at some point in time. It makes sense to do this and doesn't take up much memory at all since each descriptor is only 67 bytes long. There is no reason NOT to include them. January 1990 MUG Notes Page 12 Now that you have your modules directory and bootlist all set up, you need to create a short Shell script to make a new boot disk automatically for you. Here is the one I use: cls echo - OS-9 Level II Boot Disk Procedure echo pause "Place a disk in Drive 1" echo - Formatting disk in /d1 format /d1 "OS-9 Level II Boot" chd /d0/modules chx /d0/cmds echo echo - Building new OS9Boot file os9gen /d1 /p ident -s /d1/os9boot >/p echo - Now, copying over all files arc -amv /d0 /d1 >>/p cls echo - New bootdisk complete. Let me go over this with you to clarify what is happening here. First, I clear the screen using a CLS utility. You could do the same with a "display c" instead. Next, I have another utility to pause the script, print a message to the screen, and wait for me to press a key before continuing on. You could leave this out if you wanted, just make sure a disk is inserted in /d1 before running this script. After formatting the new disk to receive the files, I'm now ready to create the new bootfile. Remember that the modules directory is where all the boot modules reside, and the bootlist is a list of all the modules you want placed in the new bootfile. OS9GEN expects to see the modules in the current data directory, so we CHD to the modules directory on your disk. Also, we CHX to the cmds directory to make sure we find OS9GEN. At this point, OS9GEN must be in the CMDS directory or the procedure will fail. If it's not, then copy it to that directory. Note also that the bootlist file is placed in the root directory of the disk. Next, we start OS9GEN, telling it to make a new bootfile on the disk in /d1, reading the bootlist for the names of all the modules to include, and reading those modules from the modules directory. After it's finished, the next command does an IDENT of the newly created bootfile and sends its output to your printer. This is so you can see if any of the modules in the bootfile are bad. If any are, a question mark (?) will appear in the output next to that modules name. In that case, the new bootfile is no good and trying to boot with it will cause a "BOOT FAILED" message to appear. I'm sure most, if not all of you, have seen that one. At this point, the new boot disk has been created and is in place, with the bootstrap program called from RSDOS with the "DOS" command also in place. One note to make here; This procedure assumes that you have not changed the disk drive descriptor modules to a different size disk, i.e. from 40 to 80 tracks. If you need to do this, there is a separate procedure you must do that is more complicated. There January 1990 MUG Notes Page 13 are files in the Compuserve OS9 Forum Data Libraries that will show you how to do this. I have not addressed this here since it is beyond the scope of this text. Getting back to the Shell script -- now that the new bootfile is in place, you must now make a commands directory on the new disk, and copy over the SHELL and GRFDRV files as a minimum. You WILL NOT be able to boot the new disk if these files are not there. What I do is use the ARC utility and tell it to copy the entire disk from /d0 onto /d1. ARC is very handy since it will create the directories for me, verify each copy, and report any verification errors back. Since I have redirected the standard error path to my printer, any error reports will be printed out. What I usually do is to start the procedure, and then go watch TV or eat dinner since it takes about 15 minutes for this to run on my system. Of course, I have double-sided 40 track drives and the modules and files on my bootdisk fill it completely. The less the number of files, the faster this procedure will be. You could skip all this and just copy the SHELL and GRFDRV files over with the appropriate commands in the script. It's up to you. The beauty if this system is twofold; First, I can have as many modules in the module directory as I want and can name them anything I want. I have several different versions of each module in my directory, some of them are patched for enhancements or to correct bugs, and the originals are also there in case I need them. Second, to change the bootfile to include new modules, or delete some, or simply change the order in which they appear in the bootfile, all I need to do is edit the bootlist file. After editing it, I make sure my current data directory is /D0 and simply type "make.boot". In case you haven't guessed, MAKE.BOOT is the name I gave to the procedure file. When it's all done, I take a look at the printer, see if any errors occurred, and if not, I'm all set. Finally, the procedure file I have included in this text is a very much stripped down version of what I currently use. My new MAKE.BOOT file has commands to create and open several windows on the screen in various colors and send different messages and error reports to the different windows. With this one, I can watch as the new boot disk is being made and even have some interaction with the procedure. Since it's set up for my specific system and uses many programs that many of you might not have, and also includes colors for RGB monitors, I did not put it in this file. However, I'm sure some of you will get the hankering to make one up yourself and maybe even upload it as an example of your prowess in script file programming. I hope this file helps some of you with "boot making". It has made this complicated and tedious procedure easy as pie for me and I'm never afraid to crank it up and generate a new boot disk. That's the wonderful thing about computers -- they can do so much on their own. Mark Griffith 76076,41 ============= | | | JUL 1990 | | | ============= SUN MON TUE WED THU FRI SAT ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1| 2| 3| 4| 5| 6| 7| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8| 9| MUG 10| 11| 12| 13| 14| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 15| 16| 17| 18| 19| 20| 21| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 22| 23| 24| 25| 26| 27| 28| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 29| 30| 31| | | | | ============================================================================== Motorola Users Group *-* MUG *-* ============= | | | AUG 1990 | | | ============= SUN MON TUE WED THU FRI SAT ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1| 2| 3| 4| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5| 6| 7| 8| 9| 10| 11| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 12| 13| MUG 14| 15| 16| 17| 18| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 19| 20| 21| 22| 23| 24| 25| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 26| 27| 28| 29| 30| 31| | ============================================================================== Motorola Users Group *-* MUG *-* ============= | | | SEP 1990 | | | ============= SUN MON TUE WED THU FRI SAT ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2| 3| 4| 5| 6| 7| 8| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9| 10| MUG 11| 12| 13| 14| 15| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 16| 17| 18| 19| 20| 21| 22| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 23| 24| 25| 26| 27| 28| 29| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 30| | | | | | | ============================================================================== Motorola Users Group *-* MUG *-* ============= | | | OCT 1990 | | | ============= SUN MON TUE WED THU FRI SAT ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1| 2| 3| 4| 5| 6| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7| 8| MUG 9| 10| 11| 12| 13| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 14| 15| 16| 17| 18| 19| 20| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 21| 22| 23| 24| 25| 26| 27| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 28| 29| 30| 31| | | | ============================================================================== Motorola Users Group *-* MUG *-* ============= | | | NOV 1990 | | | ============= SUN MON TUE WED THU FRI SAT ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1| 2| 3| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4| 5| 6| 7| 8| 9| 10| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 11| 12| MUG 13| 14| 15| 16| 17| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 18| 19| 20| 21| 22| 23| 24| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 25| 26| 27| 28| 29| 30| | ============================================================================== Motorola Users Group *-* MUG *-* ============= | | | DEC 1990 | | | ============= SUN MON TUE WED THU FRI SAT ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2| 3| 4| 5| 6| 7| 8| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 9| 10| MUG 11| 12| 13| 14| 15| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 16| 17| 18| 19| 20| 21| 22| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 23| 24| 25| 26| 27| 28| 29| ============================================================================== | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 30| 31| | | | | | ============================================================================== Motorola Users Group *-* MUG *-*