Note Pad: Larry Tesler The Legacy of the Lisa A member of the Lisa development team reflects on how the Lisa changed personal computing On April 29 Appl announced char ic would cease production of che Macintosh XL computer, formerly known as che Lisa. As a member of ch group that helped create che Lisa, I c uldn'c help but feel a pang w hen I heard the news. Yer my verriding fe ling is one of gratifi cation. In its brief product cycle, the Lisa changed people's expectaci ns of a personal computer. A mong Apple products, che Lisa spawned not only the Macintosh but also che MouseText opti n on che Apple II (see "The Lisa·s Influence'} Even I BM PC pro ducts were heavil y influenc d by che cechnology, including VisiCor p's Visi On, Microsoji \'(lfndows, Digital Research's GEM, As hron Tace·s Frameu ork, and IBM 's Top View. The user interface wa the most publiciz d characterist ic of the Lisa. Ir introduced a host of ideas thac have been w idely emulated, ranging from how column s are wid ned in a spreadsheet ro how people are notified of mistakes and problems. When the Lisa developm nt team d signed the user interface, we I arrowed good ideas from wherever we could find them. For example, the Lisa borrowed pop-up menus and overlapping w indows from Smalltalk, status lines from VisiCalc, and automatic remova l of extra spaces afc r text deletion from Douglas Engelban's research at RI I mernacional. But the Lisa user inter face was not a copy of any chat preceded it; it was distinctive. It was ch firsc to feature the nowfarn ili ar menu bar, the onebutton mouse, the Clipboard, and che TJ·ash can . Although the Xerox tar had icons, the Lisa was the first prod uct to lee you drag them w ith the mouse, open them by double-clicking, and watch them zoom into overlapping w indows. Tu minimize the time it would take people to learn to use che Li a, Apple technical writer., programmer , and marketers struggled for two years to find suitable termi nology to appear in menus, dialogs, alerts, and manuals. Our foreign-language translaror spent months more choosing the corresponding terms in French Ita lian, German , Spanish, and other languages. It may come as a suq ri se that terms like Revert, Plain Text, Align Le.ft, Clipboa rd, and Panel we re difficult to coin and even more difficult to agree upon. When we stud ied VisiCa/c, we discovered chat people had trouble imerpreting the term General Format, which means that a number ryped into a spreadsheet cell is right justified, w hile texc is left justified. After extensive brainstorming and testing of LisaCalc, we cho e Words left, numbers rigbt, which was sel fexplanator y if a bit verbose. Much has been made of the high cost and five-year develop ment time of the Lisa. True, the development was expensive, but it did not take five years. The first Lisa was shipped in May 1983. Five years earlier, in 1978, Apple had launched a project code-nam ed "Lisa," bur that project's goal was quite different from w ha…

The Past, Present, and Future of the Macintosh Desktop Dan Smith Interview, Semaphore Signal March, 1986 To a first-time user, perhaps the most striking thing about the Macintosh is its use of the desktop metaphor: the folders and other icons intended to help make the Macintosh a user-friendly machine. For a perspective on where those ideas came from, how they were further developed by Apple, and what they might lead to in the future,we interviewed Dan Smith, an Apple Principal Software Engineer. Signal: Give us a brief history of your career at Apple. Smith: I've been at Apple for a little over five years now. I initially signed on to the Lisa project to work on what we called the Desktop Manager, essentially the equivalent of the Finder on the Macintosh. I worked on that for about two years,until the whole Lisa project was near completion. Then I became User Interface Coordinator for the Lisa project, then switched to a consulting role for theMacintosh, since Mac picked up about halfway into the Lisa development stage. I took some time off from the Macintosh and Lisa to start working on some future projects, did that for about nine months, then got pressed back into service to do a program development environment for the Macintosh, which is what I'm working on right now. Signal: Were you the desktop programmer? What was the organization responsible for the desktop and the other Lisa software? Smith: The effort was split up into a couple of different groups. There was the desktop group. Two of us actually did the implementation. I programmed the user interface portion, and Frank Ludolph did a fair amount of the lower level implementation. Then there was the applications group, and that was split up into essentially the different applications that came out: LisaDraw, LisaWrite, and so on. There was also an operating system group, which did the much lower level software. Signal: How did the ideas for the desktop originate, and how were they incorporated into your design? Smith: That's a pretty interesting story. When I started at Apple, the idea of the desktop hadn't really quite been born. In fact, it was thought we'd do something fairly simple, and it would be a one-person job for a couple of months and it would be over. It was a little later in the project that we realized the desktop was going to be a central part of the entire system. The idea of an iconic form didn't come along until quite late into the development of the product. We started off with something that was pretty Smalltalk-like. There was a notion of a thing called a browser, which is essentially a table you could flip through, listing the documents you had in a hierarchical fashion. But the whole initial desktop was essentially technically oriented. We went through iteration after iteration. I remember doing prototype after prototype, and trying them on several groups of people, getting it to be more and more useable. But a number of us were not happy with what we were gettin…

Apple Lisa Computer Technical Information The Story Behind the Lisa (and Macintosh) Interface Source: http://home.san.rr.com/deans/lisagui.html 23 April 2000 -----------------------------------------------------------------------* Cover message * Inventing the Lisa Interface * Goals and Guiding Principles * The Beginnings of the Lisa * The Early User Interface * Outside Influences * A Shift in Thinking * The Desktop Metaphor * The Role of User Testing * Arriving at an Interface * The Early Days of the Desktop Manager * Desktop Icons Rejected! * A Document Browser * The 20 Questions Filer * "Son of Dataland" * The IBM Contribution * Today's Desktop Model * Citations * Pictures of Lisa UI Prototypes -----------------------------------------------------------------------_________________________________________________________________________ Cover message Date: From: To: Subject: Mon, 17 Jun 1996 17:13:10 -0700 "Rod Perkins" "Multiple recipients of list cpsr-history@cpsr.org" Inventing the Apple Lisa; original paper. Although the Macintosh receives the recognition for creating Apple's desktop metaphor, the development of Lisa user interface pre-dates the Mac. Many of the concepts developed for the Lisa were used in the Mac's design. Other Lisa features are creeping into the UI in 1996 as Apple implements multi-processing and protected memory. Although the Lisa was not a commercial success, without the early work done by the Lisa team, there would not be the Macintosh we know today. I was among the first software engineers to work on the applications for the Lisa and its user interface. Myself, and two others from the Lisa "Filer" team wrote a paper in 1989 that described how the Lisa's UI was designed. The paper was to be a chapter in the book, "The Art of Human-Computer Interface Design", edited by Brenda Laurel, Addison-Wesley, 1990. However, as someone pointed out earlier, Apple was actively litigating against Microsoft at the time, so it was though better not to have the paper published. The paper included screen shots that pre-dates the legendary visits to Parc by Steve and other people from Apple. No doubt the Parc visits provided inspiration but its was not "standard myth that Apple lifted the user interface of the Lisa and Mac in whole from the Star". I included the text of the paper below. The Story Behind the Lisa (and Macintosh) Interface -- 1 of 20 Apple Lisa Computer Technical Information _________________________________________________________________________ Inventing the Lisa Interface Frank Ludolph Ludolph@aol.com Rod Perkins rod@aviodigital.com Dan Smith dkeller@palm.com Today's familiar Macintosh user interface is a direct descendent of the interface first developed and used on Apple's Lisa computer. Instead of a text-based system that presented the user with a blank screen and blinking cursor, the Lisa gave the user a picture of an electronic desktop, a picture that the user manipulated directly to tell the computer…

By the way, many Apple documents became public record as a result of a shareholder lawsuit around 1985. I am sure if you make inquiries you could locate many interesting documents including the Lisa MRD. It's almost a bible of personal computing. Best of luck with your project, and by all means check out 3DO! Regards, T~~ Trip Hawkins President and CEO The 3DO Cumpan)' MR. TRIP HAWKINS PRESIDENT AND CEO. THE 3DO COMPANY 600 GALVESTON DRIVE REDWOOD CITV. CA 94063 /?ece,'Veef= (}3 /{Ar (fff Re: Apple Lisa computer Dear Mr. Hawkins: Thank you very much for the generous reply to my recent letter concerning the origins of the Lisa computer. The remarks you made in your letter of 07 February were fascinating reading. I plan to incorporate them into the revision of my Lisa legacy paper. If you can answer some more questions about the Lisa I would be very appreciative. These wi 11 be the last questions I have for you since I assume you have more pressing matters at hand, e.g. running 3DO. I've enclosed a SASE to make this reply easier (or you can e-·mai I me at my CompuServe address in the letterhead)= 0) May I make your letter available to others with an interest in the Lisa? '{ e 5 l) Who came up with LISA= 1.ocal Integrated ~oftware Architecture? I assume uo~.Ldid. A T Jowr rt.IA<~ 2) Were there ever other names for the Lisa. besides5~or example. ~~l:a~J.e...vt.u, 3) I noticed that Apple changed its corporate phone number afound 1983 to end in 1016 which is the A-line trap value in binary that Lisa (and Macintosh) programmers use for making system calls. Was this change do~ring the Lisa's development? Were you involved with this change? t.1 v wtU 908 /IJ/O -fin as {~ tfU T ~'1 re~ 1N.. pkevte. rr;c, v.idJ. ~ h~ I 'f~3 .' Thanks for the comment about the Lisa MAD. I wi II look around and see if I can find copy. FYI. I have a copy of the Lisa PIP and found that a very interesting read. Good luck at 3DO. Sincerely, 0,, -~7 /'/? . /-r-1,~ /~ /. David T. Craig {f,e . / IQ . we_~;f~f-1 [b<- fvf-;f WtJt! ttfw415 -h ''[,-,. {J,.,jed" 1;./Y'____ Wednesday. February 23. 199'1 J: r~~ ~ u,l/ ;{- A-ppfe Q!!! Apple Lisa Historical Info from Trip Hawkins 21 Apr ii 1994 -- David T. Craig The following information was provided by Owen W. Linzmayer of San Francisco, CA via CompuServe: David, April 21, 1994 I'm pretty busu finishing up mu b~ but I just got a nice missive rrcm Trip Hawkins that I tha!ght uw might like. --owz. I worked for Steve Jobs until Lisa was taken away from him in the fall of 1980, on the eve of Apple's IPO. A few months after that, Steve took over Jef Raskin's project, contirned to call It Macintosh, and totally changed it into Steve's vision of a scaled-down Lisa. All of the core ideas were the same for both Lisa and Mac. Steve did have some legitimate concerns about Lisa being too high-end in its conception, but Ironically over time the Mac grew to have as much memory and cost as Lisa had. I have a huge amount of re…

rnul' .i.tr:1 tn~· rr10L ·b I l.J I.. 1 • I & I i LISA FILER EXTERNAL REFERENCE SPECIFICATION Frank Ludolph Gail Pilkington Dan Smith July 23, 1981 Approved: - ~~v- u &, Lisa Software Lisa Publications - Acknowledgement Many thanks to all the POS people that offered their time and ideas during t:he development of the Filer and this ERS.o APPLE CONFIDENTIAL .FILER 'ERS Project Identif+cation - PROJECT IDENTIFICATION 1.1 Pr()ject Name: Lisa Filer 1.2 Project Number: El46 1.3 Related Documents [l} Lisa Preliminary Personal Applications M.RD 1 June 30 1 1980. Barry Margerum [2} Lisa User Interface Standards Document: September 24, 1980. Bill Atkinson. 13] Lisa Diagnostics ERS, Version 1.1, December 23, 1980. Rich Castro. [41 :t.isa Software Theft Protection MRD, Version 1.0, April 30, 1981M Eric Michelman. 1.4 Product Abstract The Filer performs a btoad range of functions relating to the access and management ()f documents on the Lisa's deskto.p and storage media: * Creating, filing. and retrieving documents. * Init:l.alizing mounting, unmounting, and verifying the cons.istency of 1 disk.s. * Contr.olling the movement of tools between disk(ette)s. * Stationery (forms) management• Chapter two contains a complete list.of functions. The filing model is based on the.paper office but is even simpler; documents are placed in files which are on disk( ette)s ('drawers' in the paper office). As detailed in .chapter 2, many of the rest.rictions that exist in the paper off ice have been lifted; those that still remain are identical to those that exist in the paper officet e.g. disks (drawers) have a finite storage capacity. The user interacts with the Filer via .the dialog box - window$ are reserved for use by documents on the desktop.. This makes it easy for the user to get to the Filer by selecting a single menu option rather than hav1ng to search through the documents on the desktop. In general, the user specif1es the (set of) document(s) s/he wants to operate on.and then the operation, just as in the rest of Lisa. The Filer steps the. user through the standard document page 1 July 23, 1981 A1'PLE qoNFIDENTIAL Project ldentificatioll specification procedure (which the user can easily override) prompting for informacion and providinghi.Dl/her with tbe v11lU choices.. This appraaeh m111imizes 1 the lea'dling time. and the number of ki;ly1n;rcikes needed to accomplish .the task. 1.4 .1 Typie41 Users AlJ. Lisa use"t"s nll use the Filer. It is 'the first tool the new user. is trained on. Design of tha File:r has been bias:ad such tha.t the everyday o.perations are: exceedingly s:l.:mt>le. l .4.2 Novel Eeat'!lres • S:Lm.plUiel:I retrieval: Although the filer supports a (limi~ed) hie.r•rchical view of stored d.ocuments (documents in files <in d.isk(ette)s ).' the user can scan the do<:;umenrs unincu11bered by ft.le and disk(ette) b®ndries. • Simplified st.ationery handling: ~Y document can, be made :Ln'.to stationery .... by simp…

APPLENET IF SPEC Preliminary APPLENET Interface Specification June 3, 1981 R. Hochsprung R. Paratore 6/3/81 page 1 APPLENET IF SPEC This specification is a first-cut at describing how the Lisa Host, interfaces with the APPLENET card to execute the basic network services provided by the Z8. Many details are left out, such as exact sizes of host queue elements, etc. since these are dynamiclly defined. This document should give the reader a basic sense of the "style" of interaction to be provided. The host sees the APPLENET card as a shared-memory device. All commands are initiated by setting parameters into a single Task Command Block (TCB) within this shared memory. Periodically, the Z8 performs a scan of. this TGB and will execute the command when it discovers it. After a command has been completed, the Z8 will generate an interrupt to the Host. At this time, the host is responsible to examine the results of the command. In addition, the APPLENET card is normally always armed to receive packets over the net. Data from received packets are placed wi thin buffers in the shared memory. Several such buffers (called Host Queue Elements - HQE) are maintained by the 28 after Initailization. As in the case of a completed command, the Z8 will interrupt the Host after each packet is successfully received. The term "queue" is somewhat misleading, since no explicit queuing mechanisms are provided. Instead, by mutual agreement between the Host and the Z8, these Host Queue Elements are scanned in a cyclic fashion. Thus, the Z8 will guarantee to fill the Host Queue in sequence (chronological order). Likewise, the Host should maintain such a cyclic sequencing when examining the queue. The only time when this "queue" will become full is when the Host does not free a HQE. The Z8 will consider the buffer overrun and Jam directed packets and increment the buffer overrun status on bradcast packets until the next HQE is free. In order to properly synchronize the shared usage of thes TCB) and HQEs (and long buffers), each such object contains a semaphore. The value of the semaphore always indicates the current state of the object. The interpretation of the semaphores is as follows: o A value of zero for any semaphore means that the object is currently free; ego neither the Z8 nor Host is using the object. + Any (strictly) positive value indicates that the object is being processed by the Z8. For the TCB, the value is set by the Host with a unique value indicating the desired command. For HQEs and long buffers, the value is set by the Z8 when the object is first allocated to begin reception of a new packet. - A negative value indicates that the object has been "completed" by the Z8 and should thus be processed by the Host. For the TCB, this indicates that the command is done. For HQEs, this indicates that a packet has been successfully received and should be processed by the Host. The following scenarios describe the sequence of semaphore values for two cases: …

September 7th 1982 LISA Hardware Manual LISA HARDWARE MANUAL Forrest Warthman and Associates Final Draft September 7th 1982 Author: D. Berry September 7th 1982 LISA Hardware Manual PREFACE (Full Version Only) The LISA Hardware Manual is concerned with the internal functioning of the LISA system. It is intended for use by people concerned with the detailed functional operation of the LISA hardware. It is divided into two sections. Section I provides information on the functional performance and specification of the system. Chapter 1 provides a general introduction to the Lisa system, while giving a brief description of the system architecture. Chapter 2 will be of interest to programmers who need to know the address and interrupt structure, as well as the operation of the Memory Mapping Unit. Chapter 3 contains in!ormation on dimensions and environmental requirements and interfaces to the system, which are of use to design engineers wishing to interface to the Lisa. Section II of the· manual contains full functional. descriptions and theory of operation for each of the modules in the Lisa system. It will not be of interest to the general reader and is intended for use only by design and service personnel. Section II includes chapters on: * * * * * * * * The _processor board The memory board The I/O board The video board The operator interface The floppy disk unit The power supply System assembly The appendices supply schematics for the system components. Other documents relevant to the system are: * * * * LISA Hardware Manual (Condensed Version) LISA Floppy Disk Drive Manual LISA Owner's Guide LISA Operating System Manual * * * * * * Motorola 68000 User's Manual Motorola 6504 User's Manual Motorola 6522 Data Sheet COPS42l User's Manual 8530 sec User's Manual AMD 9512 Data Sheet xii LISA Hardware Manual September 7th 1982 TABLE OF CONTENTS Preface -- Section I -- Chapter 1 1.1 1.2 1.3 1.4 1.S 1.6 1.7 1.8 Chapter 2 SYSTEM ARCHITECTURE System Layout • • • • • • • • • • 1-1 Hardware Structure • • • • • • • • • • 1-4 The Central Processing Unit • • • • • • 1-6 f-temory • • '. • • • • • • • • • 1-6 Internal Buses • • • • • • •• •• 1-10 Storage Media • • • • • • • • • • • • • 1~11 User In'terfaces • • • • • • • • • • • • .1-11 Additional Features • • • • • • • • 1-11 SYSTEt-t PROGRAUMING 2.3 ..·.·.. 2-1 CPU Registers and Their Osp. · . . • .•.• 2-2 Memory Management Scheme 2-3 · · ·· •• ·· ·· •· 2-5 2.3.1 Address Transformation 2.3.2 The MMU Registers • 2-8 · · · · · · 2.3.3 MMU Initialization 2-11 2.3.4 System Contexts • · · · · · · · • ·• ·• 2-13 2.4 Addressing in Special I/O Space • • • • 2-15 2.5 System I/O Map. '. • • • • • 2-15 2.5.1 Floppy Disk Control • 2-16 • • • 2.5.2 Serial Port Control • 2-19 • • 2.5.3 Parallel Port Control • 2-22 • 2.5.4 Keyboard/Mouse Control 2-26 2.5.5 Processor Board Control • • 2-33 2.6 Interrupt Handling 2.7 Error Processing 2.8 System Status • • • 2.1 2.2 The Instruction Set ii . …

F~l Version 2.0 July 14" 1983 Please direct your COlITIEnts in fII.l"iting to: Gary ttarten I1S 2R Peul 88ker IfS 2R Ann Nunziata ItS 2R I Apple Computer Confidential ApprovalS Engineering SOftware Engineering ,fvlaIkeUn:1 < Marufacturtng .~. Mass Star. Dtvision Approval of ."..~ Whopper" project by the ·aoove releases "The Wl1Opper" as defined by this doCu'nent. All' fUture Changes, If Sly, fTlJStbe agreed ~ by above. lheCtJ~t ' , , The Lls~ haS evolvedto be a falrly COfllllexCitd expensive system to build. OUr initial idea of 'Ntlat the hardWc31e would be has grown sl~lflcantly dUe to software requlrements.and f1aS grealtly increased the cost of.the.Lisa system to ~le ana the customer.' " The LIsa system has iune:rous tlOarC2s in it. The bOardS/SUbSyStems 1rolUC1eO 1n tne Llsa assencly are : ~ o 1-QlU . 0 1- 11.0 .. . 0 2 - 1/2 tEl t1eIoory cards o l~' Power Sl4lPly o 1- Video . .' o 2 - floppy D1Sk Dr1ves . o 1 - Profile Hard 1~1Sk aSS8ftt)ly .. The goal of the, IIIhopper 1~» to repackage the aboVe tlard~e 1n the exi sting Lisa package 1n sucn a way that the packag~no CleSigl 1s m1n~m1zea .n1le the sate functionality 1s prov1dEtd to·tne user for lower cost. In specific, tt:e care cage, power supply, v1t1EKt board, CI1dtne DiSk assetlOl1es .aula De cnangea while Rt.tCh of the package and the keyobard wouldrema1n the sane. The Lisa card cage contains four plug-tn caras; tne wnopper logic will De conta1nea on two ,.cards. In addition a hard diSk cantle 1nstall891n place of cne of the floppy dr1ves, tnus eliminating toe cost Of one floppy and tneProf11e packag1ng <nl power s u p p l y . ' . The final Whopper System ~ld trus have the following conf1gurat1oo: o'lCHiZ 68010 prt':a~ssor 0' Mt1U w1 ttl 512 byte pages crtd 4, t'8 teal address space , < . o 720 x 544 videO (w1 ttl 720 x 364 RJlde) , o 1281< Ra1 (max1f1U1'J) o 896K RAM (max1nunl withOUt expans10n card) o Bu1lt-in SOny Floppy DiSk drive ' o Bull t-in Widget Hard DiSk dr1ve o 2 Bu1l t -in serial ports o Keyboard/f1OJS8 1"terface .,1th TOO clOCk To emance the COItfJ8t1b111ty bet.een ~r f.nj Mac, a"square dOts" videO rooae1s prov1ded, the SOny Floppy Disk'dr1ve 1s used and a "Mac-like SCUl(j" generator 1s provided. ca,s1derable software effort w1ll still be required to make Hac applications 1\1"\ (lI'l the M1tRlef. In addition to tne electrical des1!J1 the M1tRler ,,111 requ1re mechanical Clesl~ to prev1ae new sneet Etal for IIO.I1ting the d1sk drives ana a1 fferent card cage ~ts. Anew power cable namess w111 also haVe to be desit7l8d. COst rec:lJCtion 1s a'l1~!1:ant part Of tile WlOpperproJect ana these parts w111 be redeSigned in the nest Ctlst ~ffect1ve IIS'V'lef poss1ble. ~ly 14, 1983 - 1- The _hopper ERS . D1ffeI'8ceslntte~ , " , from A s1gn1,f1cant space rectuctlon 1n the '~r' C(JES theflCtRly diSk cootroller, which 1n the lisa I1s abOUt. 30 IC' s anct ~ies abOUt 1/2 the lID board. This 1s r~ to the s1ngle XWi Chipancfseveral 1/0 b1ts 1n…

--·--- Lisa 1 .75 ROM --------·----------------------·----------------..,-------------~-- To: From: Date: Subject: Ron Johnston, Marian Catelain, Ken c.<in, Gary Marten Rick ·Meyers May 26, 1983 Lisa 1.75 ROM Organization The Lisa· l.75 is expected ti0 have 128K bytes of ROM and 128K bytes of RAfvl on the CPU board. Additional RA!'-1 will range from none·(in a servant) to 768K (full memory board) and upward (given extra memory bo'ards). In a 512K system (assuming a 512K memory board, 128K CPU F~OM, 128K CPL,J RAM), the CPU ROM and RAM account for one third of the memory in the entire system. It's extremely important that we use this CPU memory wisely. Careful coordination bet"veen POS hardware and software group will be required. This memo outlines some of the planning that snould begin 1mmec:Uate1y. 1'1ernory COntents and Budgf!ts we need to carefully select both ROM· ancJ RAf'-1 contents, and budget their use of memory. Possible ROM .contents include: · • diagnostics (CPU, memory, peripherals) • boot code (ini tiallzation, load from disk) . • hardware interface (cursoJ, mouse, keyboards, s·peaker, timers, clock, power, etc.) • drivers (built in disk, twiggy, profHe, priam, RS-232, printers) ,. • partial file system· (for booting, keyboard tables, preferences, etc.) • miniature dubugger • fonts · • QuickDraw Possible RAl'-1 contents include: ., • primary screen (32,...() • optional al temate s;creen (32K) • interrupt and trap vectors (defaults, soft vectors, etc.) 0 hardware interface global data (keyboard mapping, keyboard queue, timers, etc.) • QulcKDraw. global o~ata (screen size, address, etc.) · • disk buffers, caches: ' . ·. • debugger data area (regis,ters, oreakpolnts, etc.) Ard'li tecture The dependencies between tlhe possible ROM contents are complex. For example: • diagnostics need hardware interface, fonts, QuickDraw • boot code needs halrdware interfac:e, drivers, file system • hardware Interface needs dr,lvers and me system (for keyboard definitions) • debugger needs nardware interface, but· hardware. interface must oe. deougged • QuickDraw needs hardware interface • etc. ·· 'There is no currently no linear ordering of the ROM software components which expresses the dependencies. This mak~s ~ layered organizatiori difficult Unfortunately, some ordering is require1ci, if only for initialization. we ~eed to break free from our current organization (or lack thereofl,. shuffle the software around, and define easily understood relatlonsnlps between the ROM components. Ga.llirg Cooventloos Calling conventions must. satisfy assembly language, Pascal, etc. How do we get Pascal lil~raries (QuickOraw, HW!nt, etc.) to point to ROM? If a ROM routine needs to be replaced, now do we override it in RA1'1? Certain ROM routines. will need domain and/or privlledged mode. Mechanism? Bad addresses as parameters to the ROM wm cause disaster. How is this preventea? 1 a Default interrupt and ~p han~lers will be In ROM. How .are t…

Apple ComptLter Inc. To: W. Rosing, Inter-Office HernorCl'ldLJn J Couch, K.' Okin,. J. Davis, M. Ca.telain, w. Henry, R. Johnston, P. Baker, B. Fox, B. Daniels, Birss, M. Deppe, R. Page, A. Benjamin, But.ter;field, R. Mey.ers, B. Atkinson, R. Hochsprung, G. Ma.rt en:, D. Pol lo.ck, B. Smith, D. Cla.inos L. Tessler, E. s. cc: R. C~stro~ A. Herz£i•ld, 0. Densmore, D. 0££en, Phillips, G. ·cossey,- R. Battat, D. era.ft, ·9. Mi 11 er,. ,J. Shea., T. $vea. t G. Date: 07 June.l983 From: Mic haef'?(fi~uha.rt Subj: Lisa. 1.75 Firmva.~e Project Plan: Preliminary "' Attached in the preliminary project plan for the Lisa i.75 Ravt. I refer to the Rgvt ln the plan as trie system Firmware Moau1e or SFM. me plan 1s tentative and can only be completed with your cooperation and approval. The size of thE? · RCJVt ana the role tnat tne usa 1.75 CPUMdeo ooara must play In Llsa 1. 75 ana the various servers requires a well planned ~roach. Please review the plan as soon as you can. I am arranging a meeting at tne tlme ana pla0!.1na1cateo oe1ow so that open issues can be quickly resolved. Note that the most important issue ls knowing Who wlll oe ctolng wnat! To help you ln your review of the plan I am providing the following tidbits: Meeting place: Meeting time: Meeting aate:: S1tt1ng Bull 1:30-4:00 Monaay 13 June 1983 Usa 1.75 versat111ty i..1sa i.1s·s CPUMaeo ooara contains tne processor, 128-256K oytes of Ravt ana 128K.;_256K bytes of t=~AM. it is to oe designea to operate as a sing1e ooara or as part of a two board set me sec.ona ooard ·contains more Rf\M ana the MMU. In the single board configuration, Lisa 1.75 is effectively a Macintosh with two to four times tne firmware space. Even ln tne two ooara setup, no map moae (1.e. setup bit set) is effectively Macintosh made. From a marketing perspect1ve1 the~st be a reason for more firmware ln Lisa 1.75 versus Macintosn's 64K oytes Knowing tnat Mac provtaes a stanaara aesKtop capabil1ty using Quickdraw and the rest. Providing Lisa 1.75 with double or quaaruple tne amount of firmware space· means tnat eltner L the- equlv8lent functionality must be present ln Llsa 1. 75 flrmware, or 2. there must oe otner aspects at;>out the Usa 1.75 flrmware tnat demonstrates its worthiness as· part of a tiiger cost product For example, extensive diagnostics. Mac has virtually zero diagnostics in RCJ'-1. . . From a manufacturing e>r service perspective, there should only be one type of CPUNldeo board between 1.75 ~d servers. This reduces problems ana costs associated, with keeping track of differ:enc~ R()'Y1s, different ooards, installing ~rong RCMs, wrong. boards, lnventortes~: different repair proceaures.. etc. Increasing available memory Destgnlng a firmware.· module which thinks only 128K of RAl'1 is always available and which provides most of the basic ingrediants for qesKtop operation means• that additona! memory Gan be used more effectively. (_():)viously., things in RCJv1 should alway,s be thing~…