Service Manuals, User Guides, Schematic Diagrams or docs for : xerox sdd memos_1978 19780615_Issues_VM_to_DA_Log_File

<< Back | Home

Most service manuals and schematics are PDF files, so You will need Adobre Acrobat Reader to view : Acrobat Download Some of the files are DjVu format. Readers and resources available here : DjVu Resources
For the compressed files, most common are zip and rar. Please, extract files with Your favorite compression software ( WinZip, WinRAR ... ) before viewing. If a document has multiple parts, You should download all, before extracting.
Good luck. Repair on Your own risk. Make sure You know what You are doing.



Image preview - the first page of the document



>> Download 19780615_Issues_VM_to_DA_Log_File documenatation <<

Text preview - extract from the document

              Inter-Office Memorandum

    To         Debugger Planners                            Date           June 15, 1978


    From      Barbara Koalkin                               Location       Palo Alto


    Subject   Issues - VM to oA log file                    Organization   SOD/SO/DE
                                                                                       XEROX SDD ARCHIVES
XEROX                                                                           I have read and understood
                                                                               Pages_ _ _ _To _ _ _ _.
                                                                             Reviewer             Date_ __
    Filed on: [Iris]  >
                               XD PilotDebugger6-15.bravo
                                                                             I of Pages         Ref .. 7ISb.b-/~~
    The following list is a set of issues related to working out the interface for the VM to OA
    log file. These issues have been discussed in the June 14th meeting of Pilot Implementors
    (Johnsson, Koalkin, Lauer, McJones, Redell. Sandman, and Wick).

    1. We need a mapping from virtual memory to physical disk address.
              Can Pitot provide this?

    Pilot has agreed to provide a log of changes to its virtual memory to physical disk address
    (e.g. drive. head. track. sector) map for use by the debugger. Pilot must go through several
    levels of mapping in order to provide this: from virtual memory to file id and file page
    number, to virtual disk address, to seek address (through the exception table and Pilot disk
    driver). to physical disk address. The debugger will use this log to build a complete map of
    virtual memory to disk addresses.

    2. We propose having part of the file label (i.e .

◦ Jabse Service Manual Search 2024 ◦ Jabse Pravopis ◦ onTap.bg ◦ Other service manual resources online : Fixya ◦ eServiceinfo