This manual page is part of Xcode Tools version 3.2

To obtain these tools:

If you are running a version of Xcode Tools other than 3.2, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.


UNREZWACK(1)                             BSD General Commands Manual                            UNREZWACK(1)

NAME
     /usr/bin/UnRezWack -- Split a RezWack file into separate data and resource files.

SYNOPSIS
     /usr/bin/UnRezWack file -o outFileNameBase [-f]

DESCRIPTION
     The /usr/bin/UnRezWack command takes a file created by RezWack(1) as its input file (it does not read
     Standard In) and divides it into two files, one containing the data fork and one containing the
     resource data.  /usr/bin/UnRezWack takes the following flags and arguments:

     file     Path to the input file.  This must be a file created with RezWack(1).

     -o outFileNameBase
              Base path of the output files.  UnRezWack will create two files at this base path, one with
              the extension ".data" and one with the extension ".qtr".  The resource data will be written to
              the data fork of the resource data file; it is not possible to create a HFS or Extended HFS
              resource fork file using UnRezWack.

              If either file exists, /usr/bin/UnRezWack will exit with error 2 unless the -f flag is pro-vided. provided.
              vided.

     -f       Force overwriting of output files.

SEE ALSO
     Rez(1), DeRez(1), RezWack(1), SplitForks(1)

Mac OS X                                       April 12, 2004                                       Mac OS X

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.