ModifyOEM

Modify OEM File

Related Topics Link IconRelated Topics

Definition

Use this command with ASCII and ANSI files such as AUTOEXEC.BAT and CONFIG.SYS. Since these files do not support the Windows INI file syntax (file, section, key, value), you must precisely define the usage of commands.

All text boxes in the command dialog box contain wildcards (* and ?); they are used without the restrictions that apply to DOS commands. For example, if you create commands using *DOS*, the character sequence DOS will be found independent of leading or trailing characters (InString search). Remark lines (REM...) will be ignored because remarks would be misinterpreted as an actual command.

You cannot use the AddINI, ModifyINI, ModifyOEM and ModifyOEMEx commands to share central files over a network.

If an error occurs while running the command, the script stops. If you want to continue the script if there is an error, enable the setting Continue script despite error in the Script Editor.

Settings

Input

  • File
    Name of the file to be modified.

Action

You can select three different actions:

The command operates line oriented for every selected action. You have to execute the command twice if you want to replace the character sequence DOS by SYSTEM in: LH_C:\DOS\KEYB_GR,850,C:\DOS\KEYBOARD.SYS

Buttons

The buttons have the following functions:

  • SysEdit
    Starts the system configuration editor (SYSEDIT.EXE).
    This function is available on 32-bit computers only.
  • Edit File
    Opens the specified file in the default editor (NOTEPAD.EXE) if you did not specify another editor.

Options

Ask for confirmation of each modification
If checked, the user will be prompted to confirm each change to an existing entry. Using this option, you can make sure that a modification will be implemented exactly at the specified position.

In the following dialog box you can control how the ModifyOEM command will be executed:

  • Modify: The modification will be implemented.
  • Skip: The modification will be skipped.
  • Recommend: Recommends and displays alternative modifications

Disable file redirection on x64 machines 
For reasons of compatibilty, Ivanti DSM maps file and registry access to the default storage location for 32 bit applications (provided that the storage location differs from that of 64-bit applications). File access: whenever a 32-bit application attempts to access %windir%\System32, the access is redirected to %windir%\SysWOW64. Registry commands: when accessing HKEY_LOCAL_MACHINE\SOFTWARE the calls are redirected to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node. The x64-switch stops this redirection of file and registry accesses when running the script command on a x64 computer; the eScript command runs on the specified path. CallScript command: the script runs in a 64-bit process.