home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
newdlg11.zip
/
resmgr.zip
/
rdc.inf
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1995-05-31
|
12KB
|
395 lines
ΓòÉΓòÉΓòÉ 1. Resource Decompiler ΓòÉΓòÉΓòÉ
Select one:
Introduction
Help
Using
Options
Bug report
Copyright
History
ΓòÉΓòÉΓòÉ <hidden> Resource Decompiler - Introduction ΓòÉΓòÉΓòÉ
The OS/2* Resource Decompiler (RDC) is an application-development tool that
lets you extract application resources, such as message strings, pointers,
menus, and dialog boxes, from the executable file of your application. The
Resource Decompiler is primarily intended to prepare data for OS/2
applications that use functions such as WinLoadString, WinLoadPointer,
WinLoadMenu, and WinLoadDlg. These functions load resources from the
executable file of your application or another specified executable file. The
application can then use the loaded resources as needed.
The Resource Decompiler and the resource functions let you quickly modify
application resources without recompiling the application itself. That is,
RDC can modify the resources in an executable file at any time without
affecting the rest of the file. This means that you can create custom
applications from a single executable file - you just use RDC to edit the
custom resources you need to each application.
The Resource Decompiler is especially important for international applications
because it lets you define all language-dependent data, such as message
strings, as resources. Preparing the application for a new language is
simply a matter of editing new resources from the existing executable file.
Note: Make sure the file RDCPP.EXE (the Resource Decompiler preprocessor) is
available for the use of the Resource Decompiler. It can be in the current
directory, or in a directory to which there is a path.
ΓòÉΓòÉΓòÉ <hidden> Resource Decompiler - Help ΓòÉΓòÉΓòÉ
To display Resource Decompiler help, type RDC at the prompt, with no
parameters. The appropriate copyright statement will be displayed, along with
a list of Resource Decompiler options.
Usage: rdc [<option>] <.EXE input file> [<.RC output file>]
-r - Extract .res file
-l - List resources (but do not extract)
-h - Access Help
Environment variables:
TMP=temporary file path
TEMP=temporary file path
ΓòÉΓòÉΓòÉ <hidden> Resource Decompiler - Using ΓòÉΓòÉΓòÉ
The Resource Decompiler (RDC) extracts a binary resource file from the
executable file of the application.
The binary resource file is decompiled in a resource script file.
You can start RDC in any of three ways.
o Extract and decompile a binary resource file from an executable file.
o Extract a binary resource file from an executable file.
o Decompile a binary resource file.
The RDC command line has the following three basic forms:
rdc executable-file [resource-script-file]
rdc binary-resource-file [resource-script-file]
rdc -r executable-file [binary-resource-file]
Note: The third option does not decompile the binary resource file.
The resource-script-file field must be the filename of the resource script
file to be decompiled. If the file is not in the current directory, you must
provide a full path. If you provide a filename without specifying a filename
extension, RDC automatically appends the .RC2 extension to the name. If you
omit the resource-script-file field, RDC puts the decompiled resources to the
executable file that has the same name as the binary resource file but which
has the .RC2 filename extension.
The executable-file field must be the name of the executable file from which
to extract the compiled resources. This is a file having a filename extension
of either .EXE or .DLL. If the file is not in the current directory, you must
provide a full path. If you specify the executable-file field but omit the
filename extension, RC will append the .EXE extension. If this executable
file does not exist, RDC displays an error message.
The -r option directs RDC to extract the binary resource file without
decompiling it to a resource script file. You can use this option to prepare
a binary resource file that you can decompile to a resource script file at a
later time. If you do not explicitly name a binary resource file along with
the -r option, RDC uses the same name as the executable file but with the .RES
filename extension.
The binary-resource-file field must be the name of the binary resource file to
be extracted from the executable file. If the binary resource file does not
already exist, rdc creates it; otherwise, rdc replaces the existing file. If
the file is not in the current directory, you must provide a full path. The
binary resource file must have the .RES filename extension.
For example, to extract the binary resource file EXAMPLE.RES from the
executable file EXAMPLE.EXE and decompile it to the resource script file
EXAMPLE.RC2, use the following command:
rdc example.exe
RDC creates the binary resource file EXAMPLE.RES and puts the decompiled
resources to the resource script file EXAMPLE.RC2.
To extract the binary resource file from EXAMPLE.EXE without decompiling the
resources to a resource script file, use the following command:
rdc -r example.exe
The decompiler creates the binary resource file EXAMPLE.RES. To create a
binary resource file that has a name different from the executable file, use
the following command:
rdc -r example.exe newfile.res
To decompile the compiled resources in the binary resource file EXAMPLE.RES to
a resource script file, use the following command:
rdc example.res
To specify the name of the resource script file, if the name is different from
the resource file, use the following command:
rdc example.res newfile.rc
To extract the compiled resources of a dynamic-link-library (.DLL) file, use
the following command:
rdc -r dynalink.dll
In addition to -r, RC offers one other command-line option: -l. The -l option
lets you view the resources contained in an executable file. The syntax is as
follows:
rdc -l executable-file
ΓòÉΓòÉΓòÉ <hidden> Resource Decompiler - Options ΓòÉΓòÉΓòÉ
The following options can be specified on the Resource Decompiler command
line:
-r Extract .res file
-l List content of a .exe file
-h Access Help
ΓòÉΓòÉΓòÉ <hidden> Resource Decompiler - Bug Report ΓòÉΓòÉΓòÉ
If you encounter a bug while using RDC or RESMGR, please send a description of
it to the following address:
lafaix@mimosa.unice.fr
or
Martin Lafaix
16, rue de Dijon
06000 Nice
FRANCE
Be sure to include at least your calling command and the output produced by RDC
or RESMGR. Thank you!
ΓòÉΓòÉΓòÉ <hidden> Resource Decompiler - Copyright ΓòÉΓòÉΓòÉ
The term OS/2 is a trademark of the IBM Corporation.
RDC and RESMGR (c) Martin Lafaix 1994, 1995.
Author: Martin Lafaix
Address:
16, rue de Dijon
06000 Nice
France
email: lafaix@mimosa.unice.fr
ΓòÉΓòÉΓòÉ 2. Resource Manager ΓòÉΓòÉΓòÉ
Select one:
Introduction
Help
Using
Options
Bug report
Copyright
History
ΓòÉΓòÉΓòÉ <hidden> Resource Manager - Introduction ΓòÉΓòÉΓòÉ
The OS/2* Resource Manager (RESMGR) is an application-development tool that
lets you manage application resources, such as message, strings, pointers,
menus, and dialog boxes.
You can start RESMGR with a single command from the command line.
With RESMGR, you can:
o Extract specified resources from a file.
o Add resources to a file.
o View the resources included in a file.
o Delete specified resources from a file.
Note: In the previous list, "file" can be a binary resource file or an
executable file.
ΓòÉΓòÉΓòÉ <hidden> Resource Manager - Help ΓòÉΓòÉΓòÉ
To display Resource Manager help, type RESMGR at the prompt, with no
parameters. The appropriate copyright statement will be displayed, along with
a list of Resource Manager options.
Usage: res <option> <.RES file> [id.type] [file]
-a - Add specified resources (default)
-d - Delete specified resources
-l - List resources (short format)
-v - List resources (long format)
-x - Extract specified resources
-h - Access Help
.RES file = .EXE or .DLL filename
file = Input or output file name
type = Resource type or *
id = Resource ID or *
Possible type value (with -d, -l, -v or -x):
Acceltable Bitmap Chartbl Dialog Displayinfo Dlginclude Fd Fddir
Fkalong Fkashort Font Fontdir Helpsubtable Helptable Keytbl Menu
Messagetable Pointer RCData Stringtable Vkeytbl
Environment variables:
TMP=temporary file path
TEMP=temporary file path
ΓòÉΓòÉΓòÉ <hidden> Resource Manager - Using ΓòÉΓòÉΓòÉ
The Resource Manager (RESMGR) manages resources from binary resource files or
executable files.
You can start RESMGR in any of four ways.
o Add a binary resource file to a file.
o Extract specified resources from a file.
o Remove specified resouces from a file.
o List specified resources from a file.
The RESMGR command line has the following four basic forms:
resmgr -a file binary-resource-file
resmgr -x file [id.type] [binary-resource-file]
resmgr -d file [id.type]
resmgr -l file [id.type] -or- resmgr -v file [id.type]
The file field must be the name of the executable or binary resource file from
which to manage the resources. This is a file having a filename extension of
either .RES, .EXE or .DLL. If the file is not in the current directory, you
must provide a full path. If this file does not exist, RESMGR displays an
error message.
Note: You cannot perform "destructive" actions (-A or -D) if the file is in
use. If you want to do so, close the program using the file, or make your
modifications over a copy of the file, and replace it later when it is no
longer used.
The id.type field can be used to specify a range of resources. The id part is
either "*" or a number (the resource ID), while the type part can be "*", a
resource type name (such as DIALOG, STRING, or ...) or a number (the resource
type ID). If this field is specified, the requested command will only affect
the specified resources.
The binary-resource-file field must be the name of the binary resource file to
be added or extracted from the file. If the binary resource file does not
already exist, rdc creates it; otherwise, rdc replaces the existing file. If
the file is not in the current directory, you must provide a full path. The
binary resource file must have the .RES filename extension.
For example, to view all resources included in the binary resource file
EXAMPLE.RES, use the following command:
resmgr -v example.res
To only view all Dialog resources included in the binary resource file
EXAMPLE.RES, use the following command instead:
resmgr -v example.res *.dialog
To extract the all string resources included in EXAMPLE.EXE, use the following
command:
resmgr -x example.exe *.string example.res
The manager creates the binary resource file EXAMPLE.RES. To add resources to
a file, use the following command:
resmgr -a example.exe newfile.res
The resources included in NEWFILES.RES will be added in EXAMPLE.EXE. If a
resource already exists in the file, it will be replaced (but if a resource is
present in EXAMPLE.RES but not in NEWFILE.RES, it will be preserved).
To remove the resource 123.999 from EXEMPLE.RES, use the following command:
resmgr -d example.res 123.999
ΓòÉΓòÉΓòÉ <hidden> Resource Manager - Options ΓòÉΓòÉΓòÉ
The following options can be specified on the Resource Manager command line:
-a Add resources to a file
-d Remove specified resources from a file
-l List specified resource content of a file (short form)
-v List specified resource content of a file (long form)
-x Extract specified resources from a file
-h Access Help
ΓòÉΓòÉΓòÉ <hidden> Resource Decompiler - History ΓòÉΓòÉΓòÉ
2.00.007 Apr 03 1994
--- First release to the unsuspecting public.
Included in EDM 2_6 (real code in 2_7).
2.04.002 May 26 1995
--- Bug fixes:
o Special characters in strings are correctly emitted.
o Accelerators were incorrectly emitted.
--- New commands:
o Added a -l option (list content).
--- New features:
o Added packed (Iterated and Iterated II) resources support.
o Added direct EXE to RC translation.
o Improved error messages.
o Temporary files no longer overwrite pre-existing files.
2.05.001 May 27 1995
--- Bug fixes:
o closing infile before COPYing it.
--- New features:
o Nothing done when there's no resource.
2.05.002 May 28 1995
--- Bug fixes:
o Font directory emitted as RESOURCE.
o Display info emitted as RESOURCE.
o Control characters are emitted as '\xnn'.
2.06.000 May 31 1995
--- New features:
o Adding exit codes (0 when OK, 1 when error and 2 when no resources).
ΓòÉΓòÉΓòÉ <hidden> Resource Manager - History ΓòÉΓòÉΓòÉ
0.01.004 May 31 1995
--- First release.