DOCSLIB.ORG

Softmac XP(Via WINE) Previous Sheepshaver Pearpc QEMU-PPC

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Softmac XP(Via WINE) Previous Sheepshaver Pearpc QEMU-PPC Mini vMac PCE/macplus MESS ShoeBill Basilisk II Fusion PC (Via DOSBox) SoftMac XP (via WINE) Previous SheepShaver PearPC QEMU-PPC VirtualBox VMWare Fusion VMWare Player Parallels Desktop PCEm x86Box VirtualPC 7 (PPC) Hardware Needed Comments 68K Systems Twiggy Prototype 128k with patchedNo OS or the correct oneUnknown of the two TwiggyNo configs with matchingNo unpatchedNo OS No No No No No No No No No No No No 128k or Twiggy Dev or Twiggy 4.3 https://apple.wikia.com/wiki/List_of_Mac_OS_versions System 0.85 128k config 128k config Unknown No No No No No No No No No No No No No No No 128k System 0.97-2.1 Yes Yes Unknown No No Unknown No No No No No No No No No No No No 128-IIcx System 3.0-3.4 Yes Yes Unknown No No Unknown Yes No No No No No No No No No No No 128-IIcx System 4.0 Plus config Yes Unknown No No Unknown Yes No No No No No No No No No No No 512k-IIcx System 4.1-4.3 Plus config Yes Unknown No No Unknown Yes No No No No No No No No No No No Plus-IIcx System 6.0-6.0.4 Yes Yes Yes No No No Yes No No No No No No No No No No No Plus-24-bit System 6.0.5-6.0.8 Yes Yes Yes Unknown Custom build - seeUnknown https://www.emaculation.com/forum/viewtopic.php?f=6&t=9984&p=61690#p61688Yes No No No No No No No No No No No Plus-68k System 6.0.8L Classic config Classic config Unknown No No No Classic config No No No No No No No No No No No Classic/LC/PB100 System 7.0-7.1.1 Yes Yes Unknown Unknown Yes Yes Yes No No No No No No No No No No No Plus-68030 System 7.0.1P-7.1P6 No No Unknown No Yes Unknown Yes No No No No No No No No No No No Performas System 7.1.2P No No Unknown Unknown Yes Unknown Yes No No No No No No No No No No No Limited 68040 Mostly Performas A/UX 1.x No No No Yes No No Unknown No No No No No No No No No No No Mac II with FPU and PMMU http://aux-penelope.com/hardware.htm A/UX 2.x No No No Yes No No Unknown No No No No No No No No No No No II / SE/30 with FPU and PMMU A/UX 3.x No No No Yes, except 3.1.1 No No Unknown No No No No No No No No No No No II / SE/30 / Quadra with FPU and PMMU. 3.1.1 requires a 32-bit clean Mac Copland No No Unknown Unknown No Unknown Unknown No No No No No No No No No No No Old World PPC Linux/m68k No No Unknown Unknown No Unknown Unknown Unknown No No No No No No No No No No 68030/68040 Only 68K / PPC Systems System 7.1.2PPC-7.5.1PPC No No No No No No No No No No No No No No No No No No nuBus PPC System 7.5-7.5.1 68k Yes Yes Unknown Unknown Yes Yes Yes No No No No No No No No No No No Plus-68040 There were custom versions for each hardware set Mac OS 7.5.2 No No No No No No No No Yes No No No No No No No No No Mac OS 7.5.3-7.5.3r2.1 Yes Yes Yes Unknown Yes Yes Yes No Yes No No No No No No No No No Plus-68040 There were custom versions for each hardware set Mac OS 7.5.3L No No Unknown No Yes Unknown Yes No No No No No No No No No No No Limited 68040 Mac OS 7.5.5 Yes Yes Yes Unknown Yes Yes Yes No Yes No No No No No No No No No Plus - Old World PPC Mac OS 7.6-7.6.1 No No Unknown No Yes Yes Yes No Yes No No No No No No No No No 32-bit Clean Only Mac OS 8.0-8.1 No No Unknown No Yes Yes Yes No Yes No No No No No No No No No 68040 / PPC NEXTStep No No Unknown Unknown No Unknown Unknown Yes No Unknown Unknown No No No No No No No PPC Systems Mac OS 8.5-8.6 No No No No No No No No Yes No No No No No No No No No PPC Only Mac OS 9.0-9.0.4 No No No No No No No No Yes No Yes (64-128MB RAM) No No No No No No No PPC Only Mac OS Rhapsody (PPC) No No No No No No No No No No Unknown No No No No No No No Mac OS X Server 1.0-1.1 No No No No No No No No No No No No No No No No No No Mac OS X Server 1.2 No No No No No No No No No No Custom config No No No No No No No Beige PPC G3 only Needs specific BootX parameters in Open Firmware. Easiest to use BootX from the boot partition of the CD image instead of attempting to create the parition on the host drive. Mac OS X Public Beta No No No No No No No No No No Custom config No No No No No No No New World PPC Only Time must be set between 2000-09-13 and 2001-05-14. This can be done in Open Firmware with the command: "decimal dev rtc 00 00 00 14 09 2000 set-time" Under qemu, maybe -prom-env before that would be enough? If not, -rtc base="2000-09-14" should work. Mac OS 9.1 No No No No No No No No No No Yes No No No No No No No Mac OS 9.2-9.2.2 No No No No No No No No No No Yes No No No No No No No Mac OS X 10.0 No No No No No No No No No No Yes No No No No No No No Mac OS X 10.1 No No No No No No No No No Custom config Yes No No No No No No No Memory must be 128MB Mac OS X 10.2 No No No No No No No No No Yes Yes No No No No No No No Mac OS X 10.3 No No No No No No No No No Yes Yes No No No No No No No MacOS X 10.4 (PPC) No No No No No No No No No Yes Yes No No No No No No No PPC G3+ Only See Mac OS X 10.5 (PPC) No No No No No No No No No No Yes No No No No No No No PPC G4+ with PMU Only MkLinux No No No No No No No No No Unknown Unknown No No No No No No No PPC Only Intel Systems NeXTStep No No No No No No No No No No No Unknown Yes Yes Unknown Unknown Unknown Unknown OpenSTEP No No No No No No No No No No No Yes Yes Yes Yes Unknown Unknown Unknown OpenStep is the Open Source version of NextSTEP and the precursor to Darwin. Mac OS Rhapsody (32-bit) No No No No No No No No No No No Unknown Unknown Unknown Unknown Yes Yes Yes Mac OS X DR 2 (32-bit) No No No No No No No No No No No Unknown Unknown Yes Unknown Yes Yes Unknown Mac OS X 10.4 (32-bit) No No No No No No No No No No No Custom config No No No Unknown Unknown Unknown 32-bit Intel Only (No Classic) Mac OS X 10.4 Server (32-bit) No No No No No No No No No No No Custom config Custom config Custom config No 32-bit Intel Only (No Classic) (Needs 32-bit EFI) https://github.com/ranma42/TigerOnVBox Mac OS X 10.5 (32-bit) No No No No No No No No No No No Custom config No No No Unknown Unknown Unknown 32-bit Intel Only Mac OS X 10.5 Server (32-bit) No No No No No No No No No No No Custom config Yes Unknown No Unknown Unknown Unknown 32-bit Intel Only (Needs 32-bit EFI) Mac OS X 10.6 No No No No No No No No No No No Custom config Custom config Unknown No Unknown Unknown Unknown Intel Only Mac OS X 10.6 Server No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown Intel Only Mac OS X 10.7 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only Mac OS X 10.8 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only Mac OS X 10.9 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only OS X 10.10 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only OS X 10.11 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only macOS 10.12 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only macOS 10.13 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only macOS 10.14 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only macOS 10.15 No No No No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel Only macOS 11 No No No No No No No No Yes Yes Yes (unverified) Yes Unknown Unknown Unknown 64-bit Intel/Apple M1 Other Systems NetBSD No No Unknown Unknown No Unknown Unknown Unknown No Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Yes No bootloader; needs to boot from Mac OS.
Load more

Recommended publications
  • Effective Virtual CPU Configuration with QEMU and Libvirt
    Effective Virtual CPU Configuration with QEMU and libvirt Kashyap Chamarthy <[email protected]> Open Source Summit Edinburgh, 2018 1 / 38 Timeline of recent CPU flaws, 2018 (a) Jan 03 • Spectre v1: Bounds Check Bypass Jan 03 • Spectre v2: Branch Target Injection Jan 03 • Meltdown: Rogue Data Cache Load May 21 • Spectre-NG: Speculative Store Bypass Jun 21 • TLBleed: Side-channel attack over shared TLBs 2 / 38 Timeline of recent CPU flaws, 2018 (b) Jun 29 • NetSpectre: Side-channel attack over local network Jul 10 • Spectre-NG: Bounds Check Bypass Store Aug 14 • L1TF: "L1 Terminal Fault" ... • ? 3 / 38 Related talks in the ‘References’ section Out of scope: Internals of various side-channel attacks How to exploit Meltdown & Spectre variants Details of performance implications What this talk is not about 4 / 38 Related talks in the ‘References’ section What this talk is not about Out of scope: Internals of various side-channel attacks How to exploit Meltdown & Spectre variants Details of performance implications 4 / 38 What this talk is not about Out of scope: Internals of various side-channel attacks How to exploit Meltdown & Spectre variants Details of performance implications Related talks in the ‘References’ section 4 / 38 OpenStack, et al. libguestfs Virt Driver (guestfish) libvirtd QMP QMP QEMU QEMU VM1 VM2 Custom Disk1 Disk2 Appliance ioctl() KVM-based virtualization components Linux with KVM 5 / 38 OpenStack, et al. libguestfs Virt Driver (guestfish) libvirtd QMP QMP Custom Appliance KVM-based virtualization components QEMU QEMU VM1 VM2 Disk1 Disk2 ioctl() Linux with KVM 5 / 38 OpenStack, et al. libguestfs Virt Driver (guestfish) Custom Appliance KVM-based virtualization components libvirtd QMP QMP QEMU QEMU VM1 VM2 Disk1 Disk2 ioctl() Linux with KVM 5 / 38 libguestfs (guestfish) Custom Appliance KVM-based virtualization components OpenStack, et al.
    [Show full text]
  • QEMU Parameter Jungle Slides
    Finding your way through the QEMU parameter jungle 2018-02-04 Thomas Huth <[email protected]> Legal ● Disclaimer: Opinions are my own and not necessarily the views of my employer ● “Jungle Leaves” background license: CC BY 3.0 US : https://creativecommons.org/licenses/by/3.0/us/ Image has been modified from the original at: https://www.freevector.com/jungle-leaves-vector-background 2 Introduction 3 Why a guide through the QEMU parameter jungle? 4 Why a guide through the QEMU parameter jungle? ● QEMU is a big project, supports lots of emulated devices, and lots of host backends ● 15 years of development → a lot of legacy ● $ qemu-system-i386 -h | wc -l 454 ● People regularly ask about CLI problems on mailing lists or in the IRC channels → Use libvirt, virt-manager, etc. if you just want an easier way to run a VM 5 General Know-How ● QEMU does not distinguish single-dash options from double-dash options: -h = --h = -help = --help ● QEMU starts with a set of default devices, e.g. a NIC and a VGA card. If you don't want this: --nodefaults or suppress certain default devices: --vga none --net none 6 Getting help about the options ● Parameter overview: -h or --help (of course) ● Many parameters provide info with “help”: --accel help ● Especially, use this to list available devices: --device help ● To list parameters of a device: --device e1000,help ● To list parameters of a machine: --machine q35,help 7 e1000 example ● $ qemu-system-x86_64 --device e1000,help [...] e1000.addr=int32 (PCI slot and function¼) e1000.x-pcie-extcap-init=bool (on/off) e1000.extra_mac_registers=bool (on/off) e1000.mac=str (Ethernet 6-byte MAC Address¼) e1000.netdev=str (ID of a netdev backend) ● $ qemu-system-x86_64 --device \ e1000,mac=52:54:00:12:34:56,addr=06.0 8 General Know How: Guest and Host There are always two parts of an emulated device: ● Emulated guest hardware, e.g.: --device e1000 ● The backend in the host, e.g.: --netdev tap Make sure to use right set of parameters for configuration! 9 “Classes” of QEMU parameters ● Convenience : Easy to use, but often limited scope.
    [Show full text]
  • Many Things Related to Qubesos
    Qubes OS Many things Many things related to QubesOS Author: Neowutran Contents 1 Wiping VM 2 1.1 Low level storage technologies .................. 2 1.1.1 Must read ......................... 2 1.1.2 TL;DR of my understanding of the issue ........ 2 1.1.3 Things that could by implemented by QubesOS .... 2 2 Create a Gaming HVM 2 2.1 References ............................. 2 2.2 Prerequise ............................. 3 2.3 Hardware ............................. 3 2.4 Checklist .............................. 4 2.5 IOMMU Group .......................... 4 2.6 GRUB modification ........................ 4 2.7 Patching stubdom-linux-rootfs.gz ................ 5 2.8 Pass the GPU ........................... 6 2.9 Conclusion ............................. 6 2.10 Bugs ................................ 6 3 Create a Linux Gaming HVM, integrated with QubesOS 7 3.1 Goals ................................ 7 3.2 Hardware used .......................... 7 3.3 Main steps summary ....................... 7 3.3.1 Detailled steps ...................... 8 3.3.2 Using a kernel provided by debian ............ 8 3.4 Xorg ................................ 8 3.4.1 Pulseaudio ......................... 11 3.5 Final notes ............................ 11 3.6 References ............................. 12 4 Nitrokey and QubeOS 12 5 Recovery: Mount disk 12 6 Disposable VM 13 6.1 Introduction ............................ 14 6.1.1 References ......................... 14 6.1.2 What is a disposable VM? ................ 14 6.2 Playing online video ....................... 14 6.3 Web browsing ........................... 15 6.4 Manipulating untrusted files/data ................ 16 1 6.5 Mounting LVM image ...................... 17 6.6 Replace sys-* VM ......................... 18 6.7 Replace some AppVMs ...................... 18 7 Building a new QubesOS package 18 7.1 References ............................. 18 7.2 Goal ................................ 18 7.3 The software ............................ 19 7.4 Packaging ............................. 19 7.5 Building .............................
    [Show full text]
  • QEMU for Xen Secure by Default
    QEMU for Xen secure by default Deprivileging the PC system emulator Ian Jackson <[email protected]> FOSDEM 2016 with assistance from Stefano Stabellini guest guest Xen PV driver IDE driver Xen PV protocol mmio, dma, etc. qemu Emulated IDE controller Xen PV backend (usually), syscalls (usually) dom0 (usu.dom0) kernel Device driver kernel Device driver PV HVM ... ... ... ... ... from Xen Security Team advisories page, http://xenbits.xen.org/xsa/ Xen on x86 modes, and device model bug implications Current status for users of upstream Xen and distros and future plans Status Device model Notes bugs mean PV Fully supported Safe (no DM) Only modified guests HVM qemu in dom0 Fully supported Vulnerable Current default as root HVM qemu stub DM Upstream but not Safe Ancient qemu qemu-xen-trad. in most distros. Build system problems HVM qemu stub DM In progress Safe Rump build system rump kernel Hard work! is mini distro HVM qemu dom0 Targeting No privilege esc. Defence in depth not as root Xen 4.7 Maybe dom0 DoS Hopefully, will be default Xen on x86 modes, and device model bug implications Current status for users of upstream Xen and distros and future plans Status Device model Notes bugs mean PV Fully supported Safe (no DM) Only modified guests HVM qemu in dom0 Fully supported Vulnerable Current default as root HVM qemu stub DM Upstream but not Safe Ancient qemu qemu-xen-trad. in most distros. Build system problems HVM qemu stub DM In progress Safe Rump build system rump kernel Hard work! is mini distro HVM qemu dom0 Targeting No privilege esc.
    [Show full text]
  • Hyperlink: Virtual Machine Introspection and Memory Forensic Analysis Without Kernel Source Code Jidong Xiao Boise State University
    Boise State University ScholarWorks Computer Science Faculty Publications and Department of Computer Science Presentations 1-1-2016 HyperLink: Virtual Machine Introspection and Memory Forensic Analysis without Kernel Source Code Jidong Xiao Boise State University Lei Lu VMware Inc. Haining Wang University of Delaware Xiaoyun Zhu Futurewei Technologies © 2016 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. doi: 10.1109/ICAC.2016.46 HyperLink: Virtual Machine Introspection and Memory Forensic Analysis without Kernel Source Code Jidong Xiao∗, Lei Luy, Haining Wangz, Xiaoyun Zhux ∗Boise State University, Boise, Idaho, USA yVMware Inc., Palo Alto, California, USA zUniversity of Delaware, Newark, Delaware, USA xFuturewei Technologies, Santa Clara, California, USA Abstract— Virtual Machine Introspection (VMI) is an ap- nel rootkit detection [8], [9], kernel integrity protection [10], proach to inspecting and analyzing the software running inside a and detection of covertly executing binaries [11]. Being the virtual machine from the hypervisor. Similarly, memory forensics main enabling technology for cloud computing, virtualiza- analyzes the memory snapshots or dumps to understand the tion allows us allocating finite hardware resources among runtime state of a physical or virtual machine. The existing VMI a large number of software systems and programs. As the and memory forensic tools rely on up-to-date kernel information key component of virtualization, a hypervisor runs directly of the target operating system (OS) to work properly, which often requires the availability of the kernel source code.
    [Show full text]
  • Hardware Virtualization
    Hardware Virtualization E-516 Cloud Computing 1 / 33 Virtualization Virtualization is a vital technique employed throughout the OS Given a physical resource, expose a virtual resource through layering and enforced modularity Users of the virtual resource (usually) cannot tell the difference Different forms: Multiplexing: Expose many virtual resources Aggregation: Combine many physical resources [RAID, Memory] Emulation: Provide a different virtual resource 2 / 33 Virtualization in Operating Systems Virtualizing CPU enables us to run multiple concurrent processes Mechanism: Time-division multiplexing and context switching Provides multiplexing and isolation Similarly, virtualizing memory provides each process the illusion/abstraction of a large, contiguous, and isolated “virtual” memory Virtualizing a resource enables safe multiplexing 3 / 33 Virtual Machines: Virtualizing the hardware Software abstraction Behaves like hardware Encapsulates all OS and application state Virtualization layer (aka Hypervisor) Extra level of indirection Decouples hardware and the OS Enforces isolation Multiplexes physical hardware across VMs 4 / 33 Hardware Virtualization History 1967: IBM System 360/ VM/370 fully virtualizable 1980s–1990s: “Forgotten”. x86 had no support 1999: VMWare. First x86 virtualization. 2003: Xen. Paravirtualization for Linux. Used by Amazon EC2 2006: Intel and AMD develop CPU extensions 2007: Linux Kernel Virtual Machines (KVM). Used by Google Cloud (and others). 5 / 33 Guest Operating Systems VMs run their own operating system (called “guest OS”) Full Virtualization: run unmodified guest OS. But, operating systems assume they have full control of actual hardware. With virtualization, they only have control over “virtual” hardware. Para Virtualization: Run virtualization-aware guest OS that participates and helps in the virtualization. Full machine hardware virtualization is challenging What happens when an instruction is executed? Memory accesses? Control I/O devices? Handle interrupts? File read/write? 6 / 33 Full Virtualization Requirements Isolation.
    [Show full text]
  • Virtualization
    Virtualization ...or how adding another layer of abstraction is changing the world. CIS 399: Unix Skills University of Pennsylvania April 6, 2009 (CIS 399 Unix) Virtualization April 6, 2009 1 / 22 What is virtualization? Without virtualization: (CIS 399 Unix) Virtualization April 6, 2009 2 / 22 What is virtualization? With virtualization: (CIS 399 Unix) Virtualization April 6, 2009 3 / 22 Why virtualize? (CIS 399 Unix) Virtualization April 6, 2009 4 / 22 Why virtualize? Operating system independence Hardware independence Resource utilization Security Flexibility (CIS 399 Unix) Virtualization April 6, 2009 5 / 22 Virtualization for Users Parallels Desktop and VMware Fusion have brought virtualization to normal computer users. Mostly used for running Windows programs side-by-side with OS X programs. Desktop use has pushed support for: I USB devices I Better graphics performance (3d acceleration) I Integration between the guest and host operating system and applications. (CIS 399 Unix) Virtualization April 6, 2009 6 / 22 Virtualization for Developers Build and test on multiple operating systems with a single computer. Use VM snapshots to provide a consistent testing environment. Run the debugger from outside the virtual machine. I Isolates the debugger and program from each other. I Allows easy kernel debugging. I Snapshotting and record/replay allow you to capture and analyze rare bugs. (CIS 399 Unix) Virtualization April 6, 2009 7 / 22 Virtualization for Business Hardware independence - upgrade hardware without reinstalling software. Resource utilization - turn 10 hosts with 10% utilization into 1 host with 100% utilization. Big power and cooling savings! Migration - move a server to a different machine without shutting it down.
    [Show full text]
  • Digital Forensics and Preservation 1
    01000100 01010000 Digital 01000011 Forensics 01000100 and Preservation 01010000 Jeremy Leighton John 01000011 01000100 DPC Technology Watch Report 12-03 November 2012 01010000 01000011 01000100 01010000 Series editors on behalf of the DPC 01000011 Charles Beagrie Ltd. Principal Investigator for the Series 01000100 Neil Beagrie 01010000 01000011DPC Technology Watch Series © Digital Preservation Coalition 2012 and Jeremy Leighton John 2012 Published in association with Charles Beagrie Ltd. ISSN: 2048-7916 DOI: http://dx.doi.org/10.7207/twr12-03 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, without the prior permission in writing from the publisher. The moral right of the author has been asserted. First published in Great Britain in 2012 by the Digital Preservation Coalition. Foreword The Digital Preservation Coalition (DPC) is an advocate and catalyst for digital preservation, ensuring our members can deliver resilient long-term access to digital content and services. It is a not-for- profit membership organization whose primary objective is to raise awareness of the importance of the preservation of digital material and the attendant strategic, cultural and technological issues. It supports its members through knowledge exchange, capacity building, assurance, advocacy and partnership. The DPC’s vision is to make our digital memory accessible tomorrow. The DPC Technology Watch Reports identify, delineate, monitor and address topics that have a major bearing on ensuring our collected digital memory will be available tomorrow. They provide an advanced introduction in order to support those charged with ensuring a robust digital memory, and they are of general interest to a wide and international audience with interests in computing, information management, collections management and technology.
    [Show full text]
  • THE PRES/URRECTION of DEENA LARSEN's “MARBLE SPRINGS, SECOND EDITION” by LEIGHTON L. CHRISTIANSEN THESIS Submitted in Part
    THE PRES/URRECTION OF DEENA LARSEN’S “MARBLE SPRINGS, SECOND EDITION” BY LEIGHTON L. CHRISTIANSEN THESIS Submitted in partial fulfillment of the requirements for the degree of Master of Science in Library and Information Science in the Graduate College of the University of Illinois at Urbana-Champaign, 2012 Urbana, Illinois Adviser: Associate Professor Jerome McDonough © 2012 Leighton L. Christiansen Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License 2012 Leighton L. Christiansen Abstract The following is a report on one effort to preserve Deena Larsen’s hypertextual poetic work Marble Springs, Second Edition (MS2). As MS2 is based on Apple’s HyperCard, a software program that is no longer updated or supported, MS2, and other works created in the same environment, face extinction unless action is taken. The experiment below details a basic documentary approach, recording functions and taking screen shots of state changes. The need to preserve significant properties is discussed, as are the costs associated with this preservation approach. ii Acknowledgments This project would not have been possible without the help and support of many people. First I have to thank Deena Larsen for entrusting me with “her baby,” Marble Springs, and a number of obsolete Macs. Many thanks to my readers, Jerome McDonough and Matthew Kirschenbaum, who offered helpful insights in discussions and comments. A great deal of appreciation is due to my team of proofreaders, Lynn Yarmey, Mary Gen Davies, April Anderson and Mikki Smith. Anyone who has to try to correct my poor spelling over 3,000 pages deserves an award. Finally, thanks to my classmates, professors, and friends at GSLIS, who listened to me talk on and on about this project, all of whom had to wonder when I would finish.
    [Show full text]
  • Mac Os Versions in Order
    Mac Os Versions In Order Is Kirby separable or unconscious when unpins some kans sectionalise rightwards? Galeate and represented Meyer videotapes her altissimo booby-trapped or hunts electrometrically. Sander remains single-tax: she miscalculated her throe window-shopped too epexegetically? Fixed with security update it from the update the meeting with an infected with machine, keep your mac close pages with? Checking in macs being selected text messages, version of all sizes trust us, now became an easy unsubscribe links. Super user in os version number, smartphones that it is there were locked. Safe Recover-only Functionality for Lost Deleted Inaccessible Mac Files Download Now Lost grate on Mac Don't Panic Recover Your Mac FilesPhotosVideoMusic in 3 Steps. Flex your mac versions; it will factory reset will now allow users and usb drive not lower the macs. Why we continue work in mac version of the factory. More secure your mac os are subject is in os x does not apply video off by providing much more transparent and the fields below. Receive a deep dive into the plain screen with the technology tally your search. MacOS Big Sur A nutrition sheet TechRepublic. Safari was in order to. Where can be quit it straight from the order to everyone, which can we recommend it so we come with? MacOS Release Dates Features Updates AppleInsider. It in order of a version of what to safari when using an ssd and cookies to alter the mac versions. List of macOS version names OS X 10 beta Kodiak 13 September 2000 OS X 100 Cheetah 24 March 2001 OS X 101 Puma 25.
    [Show full text]
  • Linux Hardware Compatibility HOWTO Linux Hardware Compatibility HOWTO
    Linux Hardware Compatibility HOWTO Linux Hardware Compatibility HOWTO Table of Contents Linux Hardware Compatibility HOWTO........................................................................................................1 Patrick Reijnen, <[email protected] (remove both "antispam.")>..1 1.Introduction...........................................................................................................................................1 2.Computers/Motherboards/BIOS...........................................................................................................1 3.Laptops..................................................................................................................................................1 4.CPU/FPU..............................................................................................................................................1 5.Memory.................................................................................................................................................1 6.Video cards...........................................................................................................................................2 7.Controllers (hard drive).........................................................................................................................2 8.Controllers (hard drive RAID)..............................................................................................................2 9.Controllers (SCSI)................................................................................................................................2
    [Show full text]
  • Challenges in Firmware Re-Hosting, Emulation, and Analysis
    Challenges in Firmware Re-Hosting, Emulation, and Analysis CHRISTOPHER WRIGHT, Purdue University WILLIAM A. MOEGLEIN, Sandia National Laboratories SAURABH BAGCHI, Purdue University MILIND KULKARNI, Purdue University ABRAHAM A. CLEMENTS, Sandia National Laboratories System emulation and firmware re-hosting have become popular techniques to answer various security and performance related questions, such as, does a firmware contain security vulnerabilities or meet timing requirements when run on a specific hardware platform. While this motivation for emulation and binary analysis has previously been explored and reported, starting to either work or research in the field is difficult. To this end, we provide a comprehensive guide for the practitioner or system emulation researcher. We layout common challenges faced during firmware re-hosting, explaining successive steps and surveying common tools used to overcome these challenges. We provide classification techniques on five different axes, including emulator methods, system type, fidelity, emulator purpose, and control. These classifications and comparison criteria enable the practitioner to determine the appropriate tool for emulation. We use our classifications to categorize popular works in the field and present 28 common challenges faced when creating, emulating and analyzing a system, from obtaining firmwares to post emulation analysis. CCS Concepts: • Computer systems organization → Embedded and cyber-physical systems; Firmware; Embedded hardware; Embedded software; Real-time systems; • Hardware → Simulation and emulation. Additional Key Words and Phrases: Firmware re-hosting, system emulation, embedded systems, emulation fidelity, emulator classification, binary analysis, reverse engineering, emulation challenges ACM Reference Format: Christopher Wright, William A. Moeglein, Saurabh Bagchi, Milind Kulkarni, and Abraham A. Clements. 2020. Challenges in Firmware Re-Hosting, Emulation, and Analysis.
    [Show full text]