Copyright 2003-2015, Penn State University
Table of Contents
- What is Blast Image Config?
- System Requirements
- Blast Image Config Public Email List
- Revision History
- Reporting Bugs
What is Blast Image Config? (Top)
Blast Image Config (aka "BIC") is a complete software solution to quickly restore and configure a Macintosh back to a known state:
- Very easy to get up and running in no time.
- One of the fastest system image restore tools available.
- Restores asr ready (/usr/sbin/asr) disk images (.dmg) created with various tools: Apple Disk Utility and System Image Utility, AutoDMG, InstaDMG, etc.
- Quickly restore a master system disk image (.dmg) via a local file, AFP/SMB/CIFS network servers, http, or from an asr multicast server, to a Mac's internal hard disk.
- Works great with a diskless NetBoot image, configured to launch at login and automatically restore an image to the Mac's internal hard disk.
- Excellent standalone solution (boot with and restore from a Firewire/USB disk/flashdrive) for restoring system disk images.
- Securely auto-mount AFP/SMB network servers to restore system disk images via BIC.
- Select default and autorun settings via Workflow Preferences and Workflows Manager system.
- Extensible through pre and post restore scripts.
- Configure and set the bootup firmware security, preventing unauthorized access via single (root) user mode and booting from external devices.
- Configure the network settings for "Built-in Ethernet" (pre 10.5) or "Ethernet" (10.5 and later) on the restored disk (via ncutil):
- IP Address : DHCP or Manual (Static)
- Subnet Mask & Router
- DNS Servers
- Network Names (Computer and Local)
- Supports Macs with dual on-board ethernet ports too (configures the "Built-in Ethernet 1" or "Ethernet 1" port in this case).
- Change the startup disk to the restored disk (via bless command).
- Set the date and time with international format support.
- Enable the Airport network interface (on Mac OS X 10.4.7 and later).
- Used by many Universities and Enterprise Companies.
- A Public Listserv for BIC discussions and announcements is available for support.
System Requirements (Top)
- BIC v3.0 and later support Snow Leopard (OS X 10.6) through and including OS X El Capitan (10.11).
- NOTE: On OS X El Capitan (10.11) you will need to disable Apple's System Integrity Protection in order for BIC to change the startup disk (via '/usr/sbin/bless') to the restored disk volume. If you don't disable it then BIC will report an error message when trying to change the startup disk. This change by Apple affects all third party system disk image restore utilities (not just BIC).
- If you need support for Mac OS X 10.5 and earlier or PowerPC based Macs (G4, G5), please download BIC v2.9 instead, which is the last universal version to support PowerPC Macs, and is no longer being developed.
- Logged in as an admin user.
- For BIC v2.9 and earlier: For PowerPC (G3/G4/G5) Macs: If you desire Open Firmware security, the Mac to restore to must be capable of supporting it. Note that Open Firmware security settings are machine specific and not stored on the hard disk. All Intel Macs have EFI firmware security and are supported.
- With permission of Dr. Jeffrey T. Frey (ncutil developer), ncutil is now included with the download of the BIC disk image.
The current version of Blast Image Config is available for download below. Please note that it requires an Intel Mac running 10.6 (Snow Leopard) or later:
You may also want to read over the new documentation for BIC v3.0 to get familiar with the new feature set and UI:
- BlastImageConfig-3.1.9b4.dmg (7.7 MB)
- Screen shots, Demo Videos
- BIC Firmware Passwords Editor
- BIC Workflows Manager
- BIC Workflow Preference Settings
If you need support for Mac OS X 10.5 and earlier or PowerPC based Macs (G4, G5), please download BIC v2.9 below, which is no longer being developed:
- PSUBlastImageConfig-2.9.3b2.dmg (8.8 MB)
All previous versions are available for download on the archives download page.
Blast Image Config Public Email List (Top)
This list is for announcements and discussion of topics related to the integration, deployment and support of Blast Image Config. Please note that technical support can be provided by anyone who subscribes to the list, not just the developer of Blast Image Config, who will also post to the list.
To join the PSU Blast Image Config discussion and announcements list, send an email to:
You should then receive an email confirmation within a few minutes to complete the process of joining the list. Click the URL provided in the email to confirm that you want to join the list.
Archives of the list discussions are also available on the BLASTIMAGECONFIG-L Archives listserv page, as of 1/1/2010.
- Initial Building:
- How to Build a CLC Managed Lab Mac
- How to Build a PSU Signature Station Mac via an external FireWire Disk
- How to build a PSU Mac via the PSU Mac Lab Build DVD (Old, was for Mac OS X 10.2)
- Penn State MacAdmins Conference
- MacWorld Conference and Expo
- University of Utah: Mac Managers Meeting (April 21, 2010)
- May 25, 2006: University of Utah's review of Blast Image Config 2.0b11
Revision History (Top)
- More in-depth revision history is available for each version.
Reporting Bugs (Top)
There is a log file created during the execution of Blast Image Config for debugging purposes. If an error should occur during the execution of Blast Image Config, please follow these steps:
- Capture the error dialogs by pressing SHIFT + COMMAND + 3 to create an entire screen capture. The screen will be saved to a file on the desktop named similiary to "Screen Shot YYYY-MM-DD at HH.MM.SS AM/PM.png". If the problem is more complex to explain with just one screen image you could also record the screen with Apple's QuickTime Player application. To help reduce the size of the video file please lower your screen resolution as close to 1024 x 768 as you can. Please do NOT email me the large video file - provide me a download URL for it instead. DropBox is a good option, among others. Thanks!
- Acknowledge and dismiss any dialogs that Blast Image Config might have displayed so that all errors get logged.
- Quit out of all applications.
- Copy the last run log file located in the 'Logs' folder, which is located in the Blast Image Config folder in the ~/Library/Logs folder. The run logs were moved to ~/Library/Logs as of BIC version 3.1.7 to make it more convenient to review the logs with Apple's Console.app. You can navigate to this folder following these steps:
- In the Finder, under the Go menu, select Go To Folder... and enter in ~/Library/Logs/ and press Return. The Finder will open the Logs folder where you can select and open the Blast Image Config folder or the BIC Firmware Passwords Editor folder which contains the most recent run log files.
- Copy the file that begins with PSUBlastImageConfig.RUN. and ends with .log. (An example filename is PSUBlastImageConfig.RUN.2014-06-20-16-58-07.log)
- Optional, but still very helpful: Create and save a System Information (Profiler) report file, compress it, and include it in your email to me as an attachment. Don't worry, the report file does not contain any sensitive or private data.
- Email a .zip file (compressed) containing the .log file, screen capture image, System Profiler report, and your video download URL (if created) to with as much information about the Mac's configuration as possible. As this is freeware, there are no guarantees that I'll be able to help you, but I'll do my best.
PSU Blast Image Config was created and is developed by Justin Elliott, developer and Manager of the Mac and Linux Teams in the Classroom and Lab Computing department at Penn State University. This software is released as freeware. Feel free to email me at with any questions, comments, feature requests, or bug reports you may have. Also consider joining the PSU BIC email discussion list for further support discussions.
The icon for Blast Image Config was created by David Stong, a graphic designer in the ETS department at Penn State. Thanks to Kenster Rosenberry for his brilliant insight and suggestions.
PSU Blast Image Config is written in Xojo, a high level, object oriented programming, "Rapid Application Development" environment which can create stand-alone executables. C++ and Java programmers should seriously consider Xojo to develop their applications AND command line tools. Xojo compiles completely stand-alone, native cocoa applications and can easily interface to Apple's Carbon and Cocoa APIs. It's very similiar to Visual Basic/.NET.
(c) 2003-2014, The Pennsylvania State University. These materials are protected under the
copyright laws of the United States of America. All rights reserved.
By downloading this software, you are agreeing to abide by the terms and conditions
contained herein. By downloading, you are obtaining a non-exclusive license to use
these materials in accordance with these terms. Nothing contained herein shall be
deemed a waiver of any rights by The Pennsylvania State University in these materials.
The license offered hereby may be revoked at any time upon written notice of revocation
to the User.
# THIS SOFTWARE IS PROVIDED "AS IS," AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE EXPRESSLY
# DISCLAIMED. IN NO EVENT SHALL PENN STATE UNIVERSITY OR ITS EMPLOYEES BE
# LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED, THE COSTS OF
# PROCUREMENT OF SUBSTITUTE GOODS OR SERIVICES; LOSS OF USE, DATA OR
# PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
# LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH
# Redistribution and use of this software in binary forms, without modification,
# are permitted, provided that the following conditions are met:
# 1. Any redistribution must include the above copyright notice and
# disclaimer and this list of conditions in any related documentation
# and, if feasible, in the redistributed software.
# 2. Any redistribution must include the acknowledgment, "This product
# includes software developed by The Pennsylvania State University," in
# any related documentation and, if feasible, in the redistributed software.
# 3. The names "Penn State" and "Penn State University", and “The Pennsylvania
# State University” are trademarks of The Pennsylvania State University and may
# not be used in association with any goods or services, including products
# derived from these materials, without the prior express written agreement of
# The Pennsylvania State University.
Last Updated October 1, 2015