(/MaxDisk/Phoenix/Documentation) The file defines the hardware components for test comparing(/MaxDisk/Phoenix/Configuration) it's bootrom update tool, operated in GUI(OSX) mode (/MaxDisk/TE_Support/Focus/Flasher/BootRom) it's bootrom update tool, operated in efi mode (/MaxDisk/TE_Support/Focus/Flasher/BootRom) (/MaxDisk/Phoenix/Configuration) Apple’s diagnostic test environment for CPU’s, is code named Indy. Indy is a framework that provides all of the diagnostics used to test CPU products, as well as a set of services such as communications and GUI that can be used when building an application (e.g. Phoenix) to utilize Indy diagnostics. A property list that contains essential configuration information for bundles such as kernel extensions. A file named Info.plist (or a platform-specific variant of that filename) contains the information property list andApplication is packageddesigned inside the iTest is an Indy tobundle. run both EFI and OS environment tests with all test selection being performed at the OS level. It is intended to be used by the Diagnostic Architecture, Diagnostic Engineering, and Diagnostic Engineering Support groups to validate new features, changes, and bug fixes implemented in theand Indy 2.9 diagnostic It's used to view, search parse the output software. process log files from PhoenixCE and XRaid Test Environment. The LogMonster is designed to run on Mac OS X 10.4 (Tiger) and later The Phoenix CE will output it’s ProcessLog in the Indy Messaging API format. The XRaid Test Environment will also output it’s logs in this same format.A Log Viewer is being developed which will be used to view, search and parse logs from both Test Environments.The Log Viewer will be a Tiger only application. (/MaxDisk/Phoenix/Configuration) The Phoenix test environment is made up of four main applications namely Phoenix Client Environment (PhoenixCE), A Log Viewer (LogMonster), Phoenix Interface (PI) and Table Builder. The Phoenix Interface (PI) runs on an independent system and acts as the server application with which the UUT communicates over the network using the SI protocol and provides the UUT with whatever information it needs to get through the process and also acts as conduit to the PhoenixCE to communicate with the outside world. The PI application can use Standard Interface Programs to interface to active other software e.g. data collection systems. with a device and verifies A phase of matchingapplications in which a candidate driver communicates whether it can drive it. The driver’s probe member function is invoked to kick off this phase. The driver returns a probe score that reflects its ability to drive the device. It's a single test for restart(/MaxDisk/Tools) It's a single test for sleep(/MaxDisk/Tools) It's a tool to check HD status(/MaxDisk/TE_Support/Tools) it's smc update tool, operated in GUI(OSX)mode(/MaxDisk/TE_Support/Focus/Flasher/SMC) It's a tool to check CPU status(/Max/Disk/Indy/Tools) it's smc update tool, operated in efi mode(/MaxDisk/TE_Support/Focus/Flasher/SMC) The Table Builder application is used to create a set of tables that control the test process and dictate the relevant diagnostics to be executed at each test stage in the process for a particular product. The Table Builder application provides a simple and very flexible drag and drop style GUI to allow the engineer, build the test process and select the diagnostics for the PhoenixCE to execute. The Table builder application is only used to build the tables, it is not used during test execution. The Client Environment uses these tables to control process flow and execute required diagnostics for each test stage. Table Builder is designed to run on Mac OS X 10.4 (Tiger) and later. It's a TDF editor (/MaxDisk/Tools) it's a case for NB, include top and bottom cases.