Tools Quick Reference			Previous	Tools	Next

cprmedit

Edits Java permissions for security zones recognized by Microsoft® Internet Explorer 4.0 and later.

The cprmedit tool enables you to edit Java permissions for specific security zones using a graphical user interface. The permissions set by cprmedit are recognized by Internet Explorer 4.0 and later. The user interface presented by the cprmedit tool is similar to the dialog boxes in Internet Explorer 4.01 that allow administrators to set security options.

To run the Custom Permission Editor, type cprmedit on the command line. The Custom Permission Editor dialog box will appear. To edit the permissions for a particular zone, choose one of the zones listed in the drop-down list box. For each zone, there are three sets of permissions that you can edit.

Permission Set	Description
Unsigned Permissions	Permissions that are granted to unsigned content.
Trusted Signed Permissions	Permissions (requested by signed content) that do not require user approval.
Untrusted Signed Permissions	Permissions (requested by signed content) that require user approval or permissions that are absolutely denied.

You can choose to add all permissions to a permission set or you can edit specific permissions in the set. If you need more information about how to edit a particular permission, you can get context-sensitive help by pressing F1 after you have selected a check box or text box.

For more detailed information about how to use the Custom Permission Editor, see the Using the Custom Permission Editor article.

Distribution Unit Archiving Utility (dubuild)

dubuild filename.cab [drive:][path] [options]

Writes an Open Software Distribution (OSD) file and places it in a cabinet file archive with any specified contents. The dubuild utility is similar to cabarc, but uses the OSD manifest instead of .inf files. Dubuild and Distribution Units are only used by Internet Explorer 4.0.

For more information, see Using DUBuild.

Parameter	Description
filename.cab	Specifies the Distribution Unit filename.
path	Specifies the source path to the files that are included in the archive.
options	Can be a combination of the following: /H or /? Displays the list of available options. /D "friendlyname" Sets the Distribution Unit's friendly name. /P oldDUName.cab Specifies a previous Distribution Unit filename used in creating Split DUs. /M Creates a multi-cab Distribution Unit. /I pattern Includes files that match the specified pattern. /X pattern Excludes files that match the specified pattern. /N "namespace" Sets the DU's namespace. /B BeanInfo Used to register ActiveX controls as JavaBeans. /S pattern Marks packages as system packages. /V version Use default version numbers for VD, VP, and VN. /VD version Sets the minimum version number for the Distribution Unit. /VP version Sets the minimum version number for the packages included in the DU. /VN version Sets the version number for new packages included in the DU (used in creating Split DUs). /Z Builds DUs with MSZIP compression for Internet Explorer 3 compatibility. By default, LZX compression is used.

Remarks:

The dubuild utility creates Distribution Units, Split Distribution Units and registers ActiveX controls as Beans. Any command-line parameters may be specified from a file by providing that file's name as @file.

The {BeanInfo} syntax is as follows:

/B package,class,regmode,progid,guid,iconfile,flags,tlbguid,
   tlbfile,bitmap32

The arguments must be in this order and may not have any spaces, and there cannot be any spaces between comma separators if any parameters are excluded. For example, if you do not want to include an iconfile, you would use the following syntax:

C:\..\>dubuild /B pkg,cls,regmd,pid,guid,,flags,tlbguid,tlbfile,bit32

Simple Bean identification can be done by supplying only the package name and the class filename. ActiveX registration requires regmode and at least the guid argument, as well.

Simple Registration
C:\..\>dubuild /B com.foo.net,Connect.class

Full Registration
C:\..\>dubuild /B com.foo.net,Connect.class,ActiveX,
      FooNetConnector,{FCOCF5C5-06DA-11d1-8F36-00C04FD8FF5E},
      com\foo\net\Connect.ico,1,
      {FCOCF5C6-06DA-11d1-8F36-00C04FD8FF5E},
      com\net\foo\Connect.tlb,
      com\net\foo\Connect.bmp

GUID Generator (guidgen)

Generates a globally unique identifier (GUID).

Remarks:

The guidgen utility displays a dialog box that you specify the format of the GUID definition with. You can then save the definition to the Clipboard and paste it into your source file. For more information about using this utility, press F1 in the guidgen dialog box to open a Help window.

Java/ActiveX Integration Utility (jactivex)

jactivex [options] filename

Hosts automation-enabled ActiveX Controls in Java and generates Java source from type libraries.

For more information, see Using Jactivex's JavaTLB Compatibility Support and Using Jactivex to Create a User-Defined Type for Java/COM Marshaling.

The default operation is to create a JavaBean wrapper for an ActiveX Control. Jactivex creates IDispatch wrappers for an ActiveX object using code and helper objects that are similar to JavaBeans to add and remove listeners for the ActiveX event interfaces.

The jactivex utility also inherits all the capabilities of the jcom utility (released in previous versions of the Microsoft SDK for Java) to generate Java source files from type libraries. These operations are performed with an additional switch, /javatlb, but are otherwise the same as with the jcom utility.

Parameter	Description
options	/javatlb Accesses Component Object Model (COM) integration features not available in default mode (generates Java source from type libraries). To access lower-level COM integration features with the jactivex utility, use the /javatlb switch and any combination of the following switches: /b Follows JavaBeans design pattern for properties. /cj Creates template for implementing coclass in Java. /d directory Sets the output directory for concerted controls. By default, the directory is set as (default=%WINDIR%\java\trustlib). /e Excludes the output for typelibs not on command line. /G3.1 Targets 3.1 Microsoft virtual machine (default=/G4). /G4 Targets 4.0 Microsoft virtual machine (default=/G4) /j Generates undecorated Java source. /l list file Creates a list of all output files (default=none). /n jnffile Specifies a JNF file (default=none). /nologo Suppresses the Microsoft copyright message. /p package name Sets the root package. By default, the package name is not set. /p:b- Indicates that the type library name is not included in the package. /r Registers type libraries. /w Disables all warnings. /WX Elevates warnings to error status. /x2 Represents 2-byte integers as a char. /xc Ignores coclasses in typelib. /xd- Do not generate Default interfaces. /xh Do not map S_FALSE to ComSuccessException. /X:m- Disables auto-marshaling. By default, auto-marshaling is enabled. /xi Exposes default interface methods directly on coclass. /? Displays command-line help and usage.
filename	When run in default mode, this is the name of the ActiveX file to create a wrapper for. The following command creates a JavaBean wrapper for an ActiveX control: jactivex mscal.ocx Otherwise, if you use the /javatlb switch and any other options, this is the name of the type library that the Java source will be generated from. For more information on jactivex command-line options that relate to Java/COM integration, see Jactivex Extended Command-Line Options.

Remarks:

Warning Do not use Microsoft® Visual J++™ compilers earlier than version 1.02.3920 to compile the files generated by this utility.

Java Register (version 3.0 pre-release 2) (javareg)

javareg [options]

Registers Java classes as COM components in the Microsoft® Windows® Registry.

For more information about using this utility, see Using JavaReg.

Parameter

Description

options

/? Provides command-line Help and usage information. /register Registers the command-line class parameter with the specified class identifier in classid. You can also use /register with /class, but without the class identifier to force javareg to create a CLSID and register it. Javareg will also recognize the /regserver switch for this command. The /register switch can also be used with several other switches to register a JavaBeans object as an ActiveX Control. /codebase:[filename|URL] Specifies the base location, either a URL or a filename, to obtain the Java class. /control Adds the necessary Registry information for containers to treat the Java class as an ActiveX control. /typelib: [filename] Generates the type library for this Java class at the specified filename's location. In order to register a typelib without generating a new one, use this option combined with the nomktyplib option. /nomktyplib Registers an existing typelib, specified in the filename argument of the /typelib switch, without creating a new one. /unregister Unregisters the class specified in the class parameter. If /unregister is specified, /class:classname must be specified as well. /class:classname Specifies the name (classname) to be registered with the classid (or with the CLSID generated by javareg if no classid is provided). /clsid:CLSID Specifies the class identifier (CLSID) to be registered with the class. Omit this parameter to force javareg to create a CLSID. /surrogate Supports remote access to COM classes. Writes the appropriate Registry entries necessary to allow the Java class to be activated out-of-process. /progid:PROGID Specifies a ProgID for the class being registered. /remote:RemoteServerName Activates the class on a remote server, using Distributed Component Object Model (DCOM). /q Suppresses all message boxes (quiet mode).

Package Manager Extraction Utility (javasrc)

javasrc [-] [class_zip]

Extracts all java source files from class_zip, or classes.zip (created by clspack) if no .zip archive is specified.

Note If you run classd.exe from the \bin directory and then run javasrc, the error message, "Unable to open file classes.zip" may appear. Run javasrc from within the Java\Classes directory, or run it with a command line that includes the path to classes.zip.

C:\..\>javasrc C:\Windows\java\classes\classes.zip

The classd.zip debug source file is not installed automatically and can be installed from the Active Setup SDK installation program.

Parameter	Description
options	The javasrc utility has the following command-line options: /? Displays help and usage information. - Deletes all java source files that are extracted from class_zip.

Java Win32 Executable Generator (jexegen)

jexegen [options] [@command file] filename

Converts Java classes into a fully executable Microsoft Win32® application.

For more information, see the Introduction to Jexegen.

Parameter	Description
options	Can be a combination of the following: /main:classname Sets the name of the main .class file. This option is required. /nomain Indicates that no main .class file is specified (useful only in conjunction with the /raw or /bindto options). /base:dir Changes the base directory used when determining package names of specified .class files to dir. /out: filename Sets the output filename. /r[–] Recurses into subdirectories when searching for the specified .class files. Use a hyphen (-) after the switch to disable this option if /r has already been used in the command string. /v Provides detailed output. /w The generated executable will not have an associated console window. /bindto: stub Specifies the stub (.exe or .dll file) to bind the class resources to. /raw Saves resource data to a file and does not generate an executable. For a detailed description of each of these options, see Reference to Jexegen Command-Line Options.
@command file	As an alternative to specifying all the class files and options on the jexegen command line, you can use a command file. For more information, see the Introduction to Jexegen.
filename	Name of the Java .class file or files that the executable will be generated from.

Remarks:

If you do not specify the /out option, the utility creates the executable file Jex.exe (by default).

Examples:

The following command line creates the executable file, Hello.exe, from a single .class file, Hello.class.

jexegen /out:hello.exe /main:Hello Hello.class

The following command line creates the executable file, classvue.exe, from all classes in the classvue directory in the Microsoft SDK for Java.

jexegen /out:classvue.exe /main:ClassVue *.class

Windows NT Service Executable Generator (jntsvc)

jntsvc [options] [@command file] files

The jntsvc utility generates self-contained, self-installing/uninstalling, redistributable executables (.exe files) for Microsoft® Windows NT® system services.

For more information about using the jntsvc utility and about the user options for the generated service executable, see the com.ms.service package overview.

Parameter	Description
options	Can be a combination of the following: /base:dir Changes the base directory and is used to determine package names of specified class files. When used with the /raw or /bindto option, /base specifies the base directory that file operations are relative to. By default, package names and file operations are determined relative to the current directory. If this option is used more than once on the command line, all /base options are relative to the original (current) directory. /out: filename Specifies the name of the output file. /r Indicates that jntsvc should search recursively into subdirectories when searching for the specified class files. By default, subdirectories will not be searched. /r– Used to turn off subdirectory recursion. This is only useful if the /r option has already been used. As an example, consider the following partial command line: /r This*.class /r- That*.class This example command line instructs jntsvc to find all class files that match This*.class in the current directory and all subdirectories, and all files that match That*.class only in the current directory. /v Verbose mode; provides detailed output. /svcmain: classname (Required) Sets the name of the main service class file. This class must be derived from com.ms.service.Service. The name specified on the command line must be the same as the class's internal name; it is case-sensitive and you must separate package names with periods. For example, if the service's class name is MyService and is in package MyPackage, the appropriate switch for jntsvc would be /svcmain:MyPackage.MyService. This option may be used multiple times to specify the service class of each service that may be run within the same process. One or more service-specific options may follow each service: /servicemain: service name Sets the name the service is registered as. /displayname display name Sets the descriptive name of the service. This is displayed in the first column of the Services control panel. /eventsource event source name Sets the event source name. The default is Java Service. This is displayed in the Source column of the event viewer. /classpath path Sets any additional class paths required. Because the service classes are embedded in the generated executable, this does not need to point to the service classes (unlike Microsoft SDK for Java version 1.5 services). /bindto: stub Specifies the stub (.exe or .dll file) to bind the class resources to. /raw Saves resource data to a file and does not generate an executable.
@command file	As an alternative to specifying all the class files and options on the jntsvc command line, you can use a command file. For more information, see the Introduction to Jexegen.
files	The name of the Java .class file or files that the executable will be generated from.

Remarks:

The use of the command file and specification of the class files in combination with the /base and /r options are identical to jexegen.

Microsoft Compiler for Java (jvc)

jvc [options] filename

Creates Java programs and applets by compiling Java source code.

For more information, see the Introduction to jvc and Jvc Release Notes.

For a listing of all errors and warnings produced by this compiler, see Jvc Errors and Warning Messages.

Parameter	Description
options	Can be a combination of the following: /cp classpath Sets the class path environment variable for the current compilation. /cp:o Prints the class path to standard output. /cp:p path Inserts the path entered and a semicolon to the beginning of the class path environment variable. /d Specifies an output directory other than the current directory for the .class files. /g [-] Generates all debugging information. Use a hyphen (-) after the switch to disable this option. /g:l [-] Generates line number debugging information. Use a hyphen (-) after the switch to disable this option. /g:t [-] Generates debug tables. Use a hyphen (-) after the switch to disable this option. /nowrite Compiles a .java file and suppresses the writing of a .class file. /O [-] Combines optimizing options to produce the fastest possible program. Use a hyphen (-) after the switch to disable this option. /O:I [-] Optimizes compilation by inlining methods (when appropriate). Use a hyphen (-) after the switch to disable this option. /O:J [-] Optimizes bytecode jumps (default setting). Use a hyphen (-) after the switch to disable this option. /verbose Prints messages about compilation progress. /w[0-4] Sets warning level (the default is 2). /x [-] Disables extensions (the default is to enable extensions). For a detailed description of each of these options, see Reference to Jvc Command-Line Options.
filename	Name of one or more source files.

Remarks:

You can specify any number of options and filenames, if the number of characters on the command line does not exceed 1024 or the limit prescribed by the operating system.

Java Viewer (jview)

jview [options] classname [arguments]

Executes Java applets and applications from the command line.

For more information, see the Introduction to Jview.

Parameter	Description
options	Can be a combination of the following: /a Invokes the use of the Microsoft AppletViewer. Applets viewed with the Microsoft appletviewer function the same as when viewed with a browser, including sound, loading, security features, and so on. When the appletviewer switch is used, all other remaining command-line tokens become parameters used by the appletviewer. /cp classpath Sets the classpath environment variable. For more information, see CLASSPATH Environment Variable. /cp:a path Appends the path entered at the end of the classpath environment variable and inserts a semicolon between them. /cp:p path Inserts the path entered and a semicolon at the beginning of the classpath environment variable. For more information, see Reference to Jview Command-Line Options. /p Pauses before terminating if an error occurs. /n namespace Provides a namespace in which to run an application. This allows Java packages with identical names to exist without conflict, if they are in separate namespaces. The Microsoft JPM stores packages in a global namespace and searches there for packages if no namespace is specified to its API elements (for example, the contents of classes.zip is stored in the global namespace). Note, however, that applications running in the name space specified with the /n switch cannot access other namespaces. /v Verifies all invoked methods (normally, only methods from untrusted loaders are verified). /D:property=value Sets a system property to a specified value. System properties are defined in the Java.lang.system.getProperty method.
classname	Name of the .class file to execute. Do not use the .class extension with this filename.
arguments	Command-line arguments to be passed to the .class file supplied in classname.

X.509 Certificate Creation Utility (makecert)

makecert [options] OutputCertificateFile

Generates a test X.509 certificate. It creates a public and private key pair for digital signatures and associates it with a name that you choose. The utility also associates the key pair with a specified publisher's name and creates a X.509 certificate that binds your name to the public part of the key pair.

Parameter	Description
basic options	The makecert utility supports the following basic options: /sk Subject's key container name (will be created if not present). /ik Issuer's key container name. /# Serial Number from 1 to 2^31-1. Default to be unique. /$ The signing authority of the certificate: either individual, commercial, minimal or all. /n Certificate subject X500 name (eg: CN=Fred Dews). /? Returns a list of basic options. /! Returns a list of extended options.
extended options	The makecert utility supports the following extended options: /sc Subject's certificate file. /sv Subject's PVK file (will be created if not present). /sp Subject's CryptoAPI provider's name. /sy Subject's CryptoAPI provider's type. /ic Issuer's certificate file. /iv Issuer's PVK file. /is Issuer's certificate store name (default to my+root+ca). /ir Location of issuer's certificate store, either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER. The default is HKEY_CURRENT_USER. /ip Issuer's CryptoAPI provider's name. /iy Issuer's CryptoAPI provider's type. /a The signature algorithm, either md5, or sha (the default is md5). /d Display name for the subject. /l Link to the policy information (such as URL). /ky Key types, either signature or exchange (the default is signature). /cy Certificate types, either end, authority, or both. /b Start of the validity period (default to now). /m The number of months for the certificate validity period. /e End of validity period (defaults to 2039). /h Max height of the tree below this certificate. /g Create a glue certificate. /r Create a self-signed certificate. /nscp Include Netscape client-authorization extension. /eku Comma separated enhanced key usage OIDs.
OutputCertificationFile	The test X.509 certificate (.cer) file.

Remarks:

The makecert utility uses slightly different syntax dependent on whether Internet Explorer 3.02 or Internet Explorer 4.0 is used. See Java Code Signing in Microsoft® Internet Explorer 4.0 for more information.

Header File Converter for Java (msjavah)

msjavah [options] ClassName

Generates C language header files for Java classes.

Parameter	Description
options	Can be a combination of the following: /v Specifies verbose output. /classpath pathname Sets an alternate class path to search in addition to the classpath environment variable. /d output directory Specifies an output directory to place the header files. Ignored if the filename used with the /o option includes absolute pathnames. /o outfile Specifies the output filename of the header file. By default, a separate header name is generated for each class name based on the class name. With this option specified, all classes are generated in the header file specified by outfile. /nologo Suppresses the Microsoft copyright message. /noclint Does not run class initializers in any specified classes. By default, msjavah attempts to run initializers. If the initializers fail, a warning message is displayed and the class is reloaded without running the initializers. /nowritebarrier Produces headers without const declarations of object member fields. Newer implementations of the Java garbage collector require all members of objects that are object references be modified with the GCSetObjectReferenceForObject API. As a result, these fields are generated as const fields. Pragmas for the Microsoft compilers are generated to disable the appropriate warnings encountered when the compiler fails to generate default constructors. The /portable switch suppresses these pragmas, to ensure portability. /portable Generates headers without enhancements specific to the Microsoft compiler (pragmas and so on). /helpers Generates inline wrapper methods for making static and non-static Java calls through the execute_java_dynamic_method and execute_java_static_method Raw Native Interface APIs. Use of these helpers allows incompatible changes to a Java method's signature to result in compilation errors, rather than runtime errors. /ctors Generates operator new wrapper methods for constructing Java objects through the execute_java_constructor API. This option is similar to /helpers; incompatible changes to constructors result in compilation errors, rather than runtime errors.
ClassName	Name of the Java class to create a C header file for (required).

Remarks:

Unlike other utilities, you must give a Java class reference instead of a filename for the given class, as in the following example.

msjavah java.lang.Thread

One command can create multiple headers, and a header file will be created for each (unless the /o option is included). For example, the following command line produces two header files, java_util_Hashtable.h and java_lang_System.h.

msjavah java.util.Hashtable java.lang.System

In contrast, the following command line generates a file called headers.h, which includes both classes.

msjavah /o headers.h java.util.Hashtable java.lang.System

You can use the /portable switch to create headers that suppress pragmas specific to the Microsoft compiler, and other compiler information, to ease portability. The following command line produces a portable file called headers.h, which includes several classes.

msjavah /o /portable headers.h java.util.Hashtable 
    java.lang.System java.lang.Thread

You use the /helpers and /ctors options with the msjavah utility to generate inline RNI wrapper method calls. For example, the following class has a constructor and a static and a dynamic method.

class fuzzle {
	void dynamicMethod (int i) {}
	static void staticMethod (String s) {}
	fuzzle (int i1, int i2) {}
}

The msjavah utility generates the following native code.

C:\..\>msjavah /helpers /ctors fuzzle

void nativeMethod () {
	GCFrame gcf;
	struct gc {
		Hfuzzle *fuzzle;
	};
	GCFramePush(&gcf, &gc, sizeof(gc));
#ifdef __cplusplus
	// Note that arguments are presented *before* the
	// class name, as arguments to the 'new' operator
	// and not directly to the constructor.
	// Generated by /ctors
	gc.fuzzle = new (3, 10) Hfuzzle;
	// Generated by /helpers
	gc.fuzzle->dynamicMethod(5);
#else
	/* Generated by /ctors */
	gc.fuzzle = new_fuzzle(3, 10);
	/* Generated by /helpers */
	fuzzle_dynamicMethod(gc.fuzzle, 5);
#endif
	/* Generated by /helpers */
	fuzzle_staticMethod(makeJavaString("Hello", 5));
	GCFramePop(&gcf);
}

Permission INI File Editor (piniedit)

piniedit [inifilename]

Creates and edits .ini files for use with the signcode tool.

The Permission INI File Editor tool provides a quick way to create .ini files that are used with the signcode tool. The signcode tool uses .ini files to provide descriptions of the permission settings that Java applets need. Using an .ini file with the signcode tool enables you to digitally sign your applet with the permissions encoded within the digital signature. The other way to create .ini files requires manually creating the file and setting the value of each variable in the file. The Permission INI File Editor creates and edits .ini files quickly and easily by enabling you to specify the permissions using a graphical user interface.

To start the Permission INI File Editor, type piniedit on the command line, optionally followed by the name of the .ini file that you want to edit.

To edit the .ini file, choose a Tab that corresponds to a permission that you want to specify. You can then edit the permission by selecting appropriate check boxes and entering parameters in the text boxes. The following table lists the Tabs and the permissions that can be edited in each Tab.

Tab Name	Permission Description
File	The ability to read, write, or delete files.
Registry	The ability to read, write, delete, create, or open keys in the registry.
Network	The ability to connect or bind to various hosts or ports on the network.
Client Services	The ability to access client storage, perform user-directed file I/O, access user interface functionality, print, use multimedia libraries, and access security classes.
System	The ability to run programs, access system properties, manipulate threads, and redirect system streams.
Reflection	The ability to access public or declared members of a class, based on the class loader.
Custom	The ability to use a non-system permission designed by the user.

If you need more detailed information about these permissions and how to edit them, see the Editing Permission Sets section of the documentation for the cprmedit tool. (The cprmedit tool uses the same user interface as piniedit, but instead of editing .ini files, cprmedit sets Java permissions for security zones.)

You can select the High or the Medium button to set all permissions to a High or Medium security level, respectively. These buttons are useful if you want to save time by adding to or removing permissions from a preset group of permissions. Be aware that selecting High or Medium erases any permission editing that you have done previously and then resets the permissions to High or Medium. To clear the settings for all permissions, select the Clear button. To create an .ini file with a Low security level, select the Full Permissions button. This setting allows all permissions.

You can also load the permissions from a specific zone by choosing Load from Zone from the Zone menu. This action will allow you to edit the .ini file using a set of permissions that are identical to the permissions for the specified zone.

To add ActiveX permissions to the .ini file, select the ActiveX permissions button.

When editing the File, Registry, Network, property access, or execution access permissions, you can use the asterisk (*) and the question mark (?) as wildcard characters in the text boxes. You can use semicolons (;) to delimit multiple entries in the property access and execution access text boxes. Multiple ports in the Network permission should be separated by commas.

If you are using an asterisk, a question mark, or a semicolon as a literal in an expression, you need to precede the literal character with a backslash and put the whole expression in double quotes. Each literal backslash must also be preceded by a backslash. For example, if you want to specify all files in the c:\windows directory whose second character is the asterisk, you should enter "c:\\windows\\?\**".

When you have finished editing the permissions, you should save the file. To save the permissions as an .ini file, choose Save from the File menu. To save the edited permissions to a zone, choose Save to Zone from the Zone menu, which will modify the permissions that are recognized by Internet Explorer 4.0 and later for the specified zone.

For more information on .ini files, see the Sample Permissions INI File and the Java Permissions INI Values Reference. To learn how .ini files are used with the signcode tool, see the Signing a Cabinet File with Java Permissions Using Signcode article.

Java Class Viewer (qvue)

qvue [options] classname

Prints out class method signatures and identifies .class files that were generated from a type library.

Parameter	Description
options	Can be used with: /s Only prints the type of class (whether a Java class or a class generated from a type library). Does not print the class methods. classname Specifies the name of the .class file to inspect. Qvue supports wildcards.

Remarks:

The qvue utility is similar to the jactivex utility's /javatlb /u option, which prints out class file summaries. The qvue utility is convenient for selecting the correct class file to use when the class files are generated from a type library using jactivex.

Win32 Resource File Merging Utility (resmerge)

resmerge [-a] target filename appended file 1 appended file 2 ...

The resmerge utility combines multiple Win32 resource (.res) files into a single file.

Parameter	Description
options	The resmerge utility supports the following option: -a Appends the specified resource files to the first named resource file (the target file).
target filename	The primary file that other files will be appended to.
appended files	Additional files that are appended to the target file.

Cabinet File Signing Utility (signcode)

signcode [options] -j JavaSign.dll [-jp level] [more options] filename

Signs a cabinet file with Java permissions to give developers more detailed control over the security restrictions placed on their applet when it is used over the Internet or an intranet.

For more information, see Signing a Cabinet File with Java Permissions Using Signcode.

Parameter

Description

options

SignCode accepts the following command-line options: /j JavaSign.dll The option that tells the signcode utility to use Java permission information. /jp level Level is an optional string that tells what level of permissions to encode in the cabinet file. This must occur immediately after the /j parameter. You can use any of the following flags: Low Medium High LowX MediumX HighX If the string is not one of these six, it is accepted as the name of an .INI file that specifies the permissions to encode. You can create this .INI file by hand, following the example provided by the sample permissions .INI file, or you can use the piniedit tool to generate the .INI file for you. See Using Signcode with Java Permission Information and the .INI Permissions Reference for more details on custom permissions. If the /jp option is not specified, a default level of LowX will be used. The exact permissions associated with these flags were previously described in Cabinet File Permission Levels and Cabinet Files and ActiveX. Other Options /spc SPC file containing software publishing certificates. /v Pvk filename containing the private key. /k Key container name. /n Text name representing content of the file to be signed. /i Place to get more information on content (usually a URL). /p Name of the cryptographic provider on the system. /y Cryptographic provider type to use. /$ Signing authority of the certificate, either individual or commercial. The default is using the certificate's highest permission. /a Hashing algorithm for signing, either md5 or sha (the default is md5). /t TimeStamp server's http address. /c Software publishing certificate file. /s Certificate store containing certificates (the default to my+root+ca+spc). /sp Add all the certificates in the chain or add only to spc store (the default is chain). /r Location of the certificate store in the registry, either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER. The default is HKEY_CURRENT_USER. /add Add the certificate in the store in signing. /addr Location of the added cert store in the Registry, either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER (the default is HKEY_CURRENT_USER). /x Does not sign the file. Only timestamps the file.

Remarks:

To add the Java permission information into the signature, add the /j JavaSign.dll option to signcode. You may also specify the /jp option for finer control over the exact permissions in the signature.

Java Window Viewer (wjview)

wjview [options] classname [arguments]

Executes Java applets and applications from the command line and spawns a separate window process.

Parameter	Description
options	Can be a combination of the following: /a Invokes the use of the Microsoft AppletViewer. Applets viewed with the Microsoft appletviewer function the same as when viewed with a browser, including sound, loading, security features, and so on. When the appletviewer switch is used, all other remaining command-line tokens become parameters that are used by the appletviewer. /cp classpath Sets the classpath environment variable. For more information, see CLASSPATH Environment Variable. /cp:a path Appends the path entered at the end of the class path environment variable and inserts a semicolon between them. /cp:p path Inserts the path entered and a semicolon at the beginning of the classpath environment variable. /n namespace Provides a namespace in which to run an application. This allows Java packages with identical names to exist without conflict, if they are in separate namespaces. The Microsoft JPM stores packages in a global namespace and searches there for packages if no namespace is specified to its API elements (for example, the contents of classes.zip is stored in the global namespace). Note, however, that applications running in the name space specified with the /n switch cannot access other namespaces. /v Verifies all invoked methods (normally, only methods from untrusted loaders are verified).
classname	Name of the .class file to execute. Do not use the .class extension with this filename.
arguments	Command-line arguments to be passed to the .class file supplied in classname.

Remarks:

Use this utility to launch window-based Java applications and applets. This utility is the same as the jview utility, with the exception that wjview runs the application as a separate graphical user interface (GUI) process and does not use or require a console window. Consequently, you do not use wjview for Java applications that require output to or input from the console window.