The best plugins and scripts for 3D, VFX and motion graphics software including Adobe After Effects, Cinema 4D and Premiere Pro. Lots of video tutorials showing how to use the tools provided. Mac OS X & macOS names. As you can see from the list above, with the exception of the first OS X beta, all versions of the Mac operating system from 2001 to 2012 were all named after big cats.
Note: The headings on this list indicate the Macintosh System bundle names; the bullet points indicate the version of the System File included in that bundle. This is to make it clearer for people searching for specific bundle versions as opposed to System File versions. Finder File versions are not indicated. 1 Classic Mac OS 1.1 Macintosh System Software (0 - 0.3) 1.1.1 System File 1 1.1.2. Learning About Mac OS X 45 Customizing Your Desktop and Setting Your Preferences 46 Using Applications 47 When an Application Does Not Respond 47 Keeping Your Software Up to Date 48 Connecting to a Printer 49. Your other Mac has built-in FireWire. As dialabrain says there is no way to predict whether Apple will allow your model Mac to run the next version of OS X - presumably 10.12. Even if it cannot it will still run current applications. With it being currently eight years old you have already got your moneys worth out of it.
Throughout this document, commands that you have to type or buttonsyou have to click will appear like so.
PennSim is written in Java, which means Java must beinstalled on the computer you plan to use. Java should already beavailable on all public SEAS machines. If you plan to work on yourpersonal machine, you may need to install Java yourself. You can download Java here. PennSim requires Java 1.5 or newer (which is available forWindows, Linux, and Mac OS X).
Next, you need to download the simulator. It is distributed in a .jarfile (short for Java ARchive). In Windows or on a Mac, youshould be able to double-click the .jar file to launch thesimulator. You can also launch the simulator from the command line ofyour operating system (such as Linux) by using the command
If you have any problems starting the simulator, please post yourproblems to the CSE240 discussion forum. This will ensure thefastest response.
We will not be distributing the source to the simulator, becausea later assignment will build parts of the simulator in C (which issimilar to Java in many ways).
Now the simulator is running, but to get it to do anythinginteresting, we need to load some software. The first piece ofsoftware we should load is, naturally, an operating system. The LC-3operating system is very basic: it handles simple I/O operations andis responsible for starting other programs, such as the ones you'llwrite for this homework. Download the LC-3 OShere.
So that you can understand what the operating system does, wedistribute it as an assembly language file. But the machinedoesn't understand assembly directly; we first have to 'assemble' theassembly code into machine language (a .obj file containing binarydata). PennSim has a built-in assembler, accessible (as isthe case for most of its functionality) via the Command Line text box(see screenshot above). To assemble the operating system, type
Now we can load the lc3os.obj file into the simulator, either via thecommand load lc3os.obj or by going to theFile menu and selecting
Now assemble and load the solution file forProblem 0 into the simulator. The memory has changed again, but youmay not notice since the relevant memory addresses (starting at x3000)aren't visible unless you've scrolled the screen. User-level programs(i.e., non-OS code) start, by convention, at x3000. If you type thecommand list x3000 the memory view willjump to x3000 and you can see the 1-instruction solution to thisproblem.
To actually run code, you can use the 4 control buttons at the top ofthe simulator, or type commands into the command line interface (thecommand names are the same as the buttons). Note that the PC registeris set to x0200, which is the entry point to the operating system byconvention. Recall that the solution code for Problem0 increments the value in R2 and puts the result in R5. Set thevalue in R2 to something you fancy, either by double-clicking it inthe Registers section, or via the command set R2(value). Now, actually run the code by hitting the
Clearly, some things are going on here. But to determine what they areexactly, we need to slow the execution down. You can hit the
Let's try running the program again, but just one instruction at atime. Notice that from the halted state, the PC points to aninstruction that will branch us right back to the start of theoperating system. So we can hit next onceand start the cycle over again. Note that registers are as we leftthem. You can put a new value into R2 if you want, and the old valuein R5 will get overwritten. Sometimes, having old values lying aroundeverywhere can be problematic, and it's good to do a real 'reboot' viathe reset command. This clears allof memory and resets registers to default values, so you have toreload the OS and your program.
You can keep next-ing over the OS code;eventually you will hit the RTT instruction at location x0205 thatjumps to the start of our program at x3000. Now you can see the 2instructions that constitute our program. You can see the ADD beingperformed, and then the machine gets halted again.
Continue running the increment-R2-into-R5 code until, if ever, you getbored. Then move on to Problem 1.
Going one instruction at a time is great, but somewhat tedious. Weneed a happy medium between not knowing what's going on at all, andhaving to go through every single instruction, whether we care aboutit or not. Breakpoints are this happy medium.
A breakpoint is set at a particular memory location, and tells thesimulator to stop execution upon reaching that point. Memory locationswith breakpoints set on them show up in the simulator with a redsquare in the 'BP' column. It is left as an exercise to the reader todetermine what 'BP' stands for. You can set a breakpoint at a memorylocation with the command break set (memorylocation), or by checking the checkbox in the 'BP' column. Youcan get rid of a previously-set breakpoint with the command
When you tell the simulator to continue,it will only run until it hits a breakpoint (or the system halts orhas an error). When you are writing and testing your answer forProblem 1, you can use the command breakpointset START to set a breakpoint at the beginning of yourcode. Then, you can use continue to skipall the OS code and get to the instructions you care about. Then youcan next over your code to make sure it'sdoing what you want it to do.
Now try running some of the test scripts that we've provided forProblem 1. You can do this with the command
Scripting is also a great way of testing your code. You can write afew test cases and check your code easily, especially for the problemsin this homework which are pretty easy to test. Use the
This document doesn't cover all of the simulator's functionality; foran extended discussion of usage see the PennSim Manual. For quick help within the simulator itself,you can use the help command to see alist of all of PennSim's commands. Use help(command) to get help on a specific command.
Many of the PennSim commands have shortcuts -
The PennSim Command Line has a history feature - use the up and downarrow keys to go backwards and forwards through the commands you'vepreviously entered.
If you resize the simulator window to make it bigger, the CommandlineOutput Pane will grow. If you have a small screen and the CommandlineOutput Pane still isn't big enough, you can open an external, resizableCommand Output Window by selecting the OpenCommand Output Window option from the
If you have trouble running the simulator, try checking the classforum in case someone else has had the same problem as you. Postingyour questions to the forum is a good idea in general, because thenother people can learn from your experience. The forum is checkedregularly by Professor Lewis and the TAs. Of course, you can alsoemail cse240@seas, or drop by office hours.
If you think you've found a bug in the simulator (which is,theoretically speaking, a possibility:), check the Simulator distribution/bugspage to see if you've found a known bug with a workaround. Ifyou've found a new bug, post to the forums (if you want to embarrass us)or email cse240@seas (if you're feeling kinder). Be sure to include thefollowing: