CVSCreatingNewNLV

Most recent edit on 2010-06-03 09:20:15 by AlexTaylor [Add Peer SMP fix instructions]

Additions:
4. Update the Peer install files with the SMP fix from IBM.

Deletions:
4. Update the Peer install files with the SMP fix from IBM.
(TODO)




Edited on 2010-01-25 02:01:43 by AlexTaylor [Corrections to SI patch]

Additions:
- Copy INSTRES.DLL from wherever it is packed inside the OS2IMAGE tree, and patch the resources to set controls #5905, 5906 (SBCS only), 5604, 5605 (SBCS only), 6200 and 6300 (SBCS only) in dialog #136 to set the "NOT WS_VISIBLE" flag. (This disables the Primary and Secondary Display controls.)
IMPORTANT: After applying FixPaks, the updates for Step 6 under Creating the NLV Tree must be (re-)applied (as must the steps listed below, if already done).
5. (Optional) Delete all files named PACK?? from under OS2IMAGE\DISK_* except for the one which contains MMPMDIG.FON (these files are no longer needed as the multimedia files are installed separately). This frees up several megabytes of disk space on the final CD.


Deletions:
~~-Copy LVM.DLL from another NLV to OS2IMAGE\DISK_6. This is a special wrapper DLL which calls the "real" LVM.DLL (as IVM.DLL).
IMPORTANT: After applying FixPaks, the updates for Step 6 under Creating the NLV Tree must be (re-)applied, as must Steps 1 through 4 under Other Tasks.
5. (Optional) Delete all files named PACK?? from under OS2IMAGE\DISK_* except for the one which contains MMPMDIG.FON; delete the corresponding entries from the file OS2IMAGE\DISK_3\BLISTLAY.OUT. This frees up several megabytes of disk space on the final CD.




Edited on 2009-07-30 14:59:18 by AlexTaylor [Added link to LVM.DLL patch instructions]

Additions:
2. Install the updated JFS drivers required to support Bootable JFS
3. Patch LVM.DLL for the 1024-cylinder and Boot Manager fixes.


Deletions:
2. Install the updated JFS drivers required to support Bootable JFS: CVSBootableJFS
3. Patch LVM.DLL for the 1024-cylinder and Boot Manager fixes.




Edited on 2009-07-30 14:47:17 by AlexTaylor [Moved BootJFS install instructions to a separate page.]

Additions:
1. Apply the latest FixPaks and other updates to the OS2IMAGE and CID\SERVER trees. This is done using UpdCD. (Instructions not included here.)
2. Install the updated JFS drivers required to support Bootable JFS: CVSBootableJFS
3. Patch LVM.DLL for the 1024-cylinder and Boot Manager fixes.
4. Update the Peer install files with the SMP fix from IBM.
5. (Optional) Delete all files named PACK?? from under OS2IMAGE\DISK_* except for the one which contains MMPMDIG.FON; delete the corresponding entries from the file OS2IMAGE\DISK_3\BLISTLAY.OUT. This frees up several megabytes of disk space on the final CD.


Deletions:
1. Install the patched JFS drivers required to support Bootable JFS.
2. Patch LVM.DLL for the 1024-cylinder and Boot Manager fixes.
3. Update the Peer install files with the SMP fix from IBM.
4. (Optional) Delete all files named PACK?? from under OS2IMAGE\DISK_* except for the one which contains MMPMDIG.FON; delete the corresponding entries from the file OS2IMAGE\DISK_3\BLISTLAY.OUT. This frees up several megabytes of disk space on the final CD.
5. Apply the latest FixPaks and other updates to the OS2IMAGE and CID\SERVER trees. This is done using UpdCD. (Instructions not included here.)




Edited on 2009-07-30 14:37:43 by AlexTaylor [More information on BootJFS update]

Additions:
~-Also replace OS2IMAGE\DISK_2\JFS.IFS and OS2IMAGE\DISK_3\UJFS.DLL with the same updated versions.



Edited on 2009-07-30 14:35:06 by AlexTaylor [Clarify location of LVM/IVM DLL]

Additions:
~~-Rename OS2IMAGE\DISK_6\LVM.DLL to IVM.DLL using the DLLRNAME utility: "dllrname lvm.dll LVM=IVM". (It may be necessary to force the MZ header on LVM.DLL first using LXLITE: "lxlite lvm.dll /c:minstub".)
6. Apply the necessary modifications for the eCS build environment (and required patches) to the IBM product images:
7. Update ecsInst1_2\SOURCE\LIST\xx_yy\Makefile.OS2 and DIRLIST.LST:
8. Populate the ecsInst1_2\PROGRAM\MEMDISK\BIN\xx directory by copying the files from another NLV.
9. Create the Guided Procedure scripts:
10. Edit the script ecsInst1_2\CONFIGURE.CMD, and make sure that xx is included in the 'short_languages' string, and xx_yy in the 'long_languages' string.
5. Apply the latest FixPaks and other updates to the OS2IMAGE and CID\SERVER trees. This is done using UpdCD. (Instructions not included here.)
IMPORTANT: After applying FixPaks, the updates for Step 6 under Creating the NLV Tree must be (re-)applied, as must Steps 1 through 4 under Other Tasks.


Deletions:
An NLV (National Language Vion) build is normally referred to by its assigned locale name, which takes the form 'xx_yy'.
6. Update ecsInst1_2\SOURCE\LIST\xx_yy\Makefile.OS2 and DIRLIST.LST:
7. Populate the ecsInst1_2\PROGRAM\MEMDISK\BIN\xx directory by copying the files from another NLV.
8. Create the Guided Procedure scripts:
9. Edit the script ecsInst1_2\CONFIGURE.CMD, and make sure that xx is included in the 'short_languages' string, and xx_yy in the 'long_languages' string.




Edited on 2009-07-26 13:26:50 by AlexTaylor [Added explicit syntax for MARKEXE (DBCS NLVs)]

Additions:
~~-Rename LVM.DLL to IVM.DLL using the DLLRNAME utility: "dllrname lvm.dll LVM=IVM". (It may be necessary to force the MZ header on LVM.DLL first using LXLITE: "lxlite lvm.dll /c:minstub")

An NLV (National Language Version) build is normally referred to by its assigned locale name, which takes the form 'xx_yy'.

xx = The two-letter language code of the NLV.

yy = The two-letter country code of whichever country is considered the primary market for that NLV. Note that multiple NLVs are not normally created for the same language, even if there are multiple national markets; e.g. there is only one English NLV, EN_US (English/United States) which is marketed to all English-speaking locales.

The major exception to this rule is Chinese: there are two written forms of Chinese (Traditional Chinese, used in Taiwan; and Simplified Chinese, used in mainland China), which are so different from each other that they are treated as separate languages and require their own NLVs.

Existing NLV locales names include:

DE_DE: German/Germany
EN_US: English/United States
ES_ES: Spanish/Spain
FR_FR: French/France
IT_IT: Italian/Italy
JA_JP: Japanese/Japan
NL_NL: Dutch/Netherlands
RU_RU: Russian/Russia
SV_SE: Swedish/Sweden
ZH_CN: Simplified Chinese/People's Republic of China
ZH_TW: Traditional Chinese/Taiwan

There is also a two-letter abbreviation used in some cases to refer to the language alone. This is the same as the 'xx' portion of the locale name, with the exception of the two Chinese languages: Simplified Chinese is CN and Traditional Chinese is TW.

In addition, the numerical three-digit country code is used in some contexts. This is referred to in this document as 'ZZZ'.

ZZZ = Three-digit country code of the same country represented in the locale name. Currently-used values include:

001 : United States (English)
007 : Russia (Russian)
031 : Netherlands (Dutch)
033 : France (French)
034 : Spain (Spanish)
039 : Italy (Italian)
046 : Sweden (Swedish)
049 : Germany (German)
081 : Japan (Japanese)
086 : China (Simplified Chinese)
088 : Taiwan (Traditional Chinese)

Each NLV must have the following directories or directory trees in CVS, following the naming convention described above:


(Note that some software packages also have language- or country-specific subdirectories and/or files; however, these are generally only required to support user interaction in the given language, and are not needed for a functioning install.)



Creating the NLV tree


1. Create the NLV-specific directories (in your CVS sandbox) listed above.

2. Populate the ecsInst1_2\SOURCE\xx_yy directory tree by copying the contents from an existing NLV. (Note: SBCS and DBCS versions are slightly different, so copy files from the appropriate one. You should generally use EN_US as the source for a new SBCS NLV, and Japanese for a new DBCS NLV.)

IMPORTANT: Make sure you remove all 'CVS' subdirectories from the new directory tree. New 'CVS' subdirectories will be created (with the proper information) when you run 'cvs add' later on.




3. Adjust the contents of the ecsInst1_2\SOURCE\xx_yy\ECSDISK* directories as necessary for the NLV. You should replace the following files with versions specific to the new NLV (which you can normally get from the OS/2 MCP2 CD for that language, if one exists):

ECSDISK0: ALTF1TOP.SCR, KBDBASE.SYS, OS2DBCS*, OS2DBCS.FNT*, OS2LDR.MSG
ECSDISK1: CMD.EXE, DOSCALL1.DLL, HARDERR.EXE, FONTMEM.SYS*, OSO001.MSG, VIOTBL.DCP
ECSDISK2: TEDIT.EXE, TEDIT.HLP
ECSDISK3 [DBCS NLVs only]*: all files. (The video DLLs should be taken from SNAP.)

* = DBCS systems only

(You should also take the opportunity to verify that the kernel boot files (OS2KRNL, OS2BOOT, OS2DUMP, OS2LDR and OS2LOGO) are the same as the ones in the ecsInst1_2\SOURCE\COMMON\KERNEL directory.)

The actual set of files is generally the same for all SBCS versions. However, in addition to the above, all DBCS NLVs require their own specific files in the ECSDISK3 directory (in particular the system font files *.MAP and *.FNT). Examine a MCP/WSeB boot system for the NLV in question to determine the specific files needed. Be sure to edit the ECSDISK*.LST packfiles to reflect any changes you make to the directory contents.

Especially, note the following for DBCS versions:

4. Edit the preboot options file ecsInst1_2\SOURCE\xx_yy\OS2CSM\MENU.BRN:




IMPORTANT: For DBCS NLVs, the keyboard code must be the correct value: JP for Japanese, CN for Simplified Chinese, TW for Traditional Chinese. If this is not the case, the boot CD will hang as soon as PM starts. DBCS systems do not support different keyboard names for the DEVINFO statement in CONFIG.SYS; instead, support for a limited number of different keyboards is achieved by replacing KBDBASE.SYS and KEYBOARD.DCP with different versions for each supported keyboard. Also note that the correct copy of KBDBASE.SYS must be used (the OS2IMAGE tree may contain several different versions)..





5. Populate the ecsInst1_2\xx_yy directory tree. (All references to the MCP2 CD are assumed to be that of the NLV in question, if one exists):





Important: All DBCS versions have some special options, usually related to Input Method Editor support, DBCS Fonts, keyboard support, DBCS-specific utilities and possibly others. (In particular, look for keywords like 'IME', 'MKK', 'OutlineFonts', 'FontDB', 'Keyboard', and 'OptionalDBCSUtilities'.) Also note that DBCS OS/2 allows two different versions of Win-OS/2 to be installed: a DBCS version and an SBCS (English) version, which use distinct response file keywords. These will all need to be handled by the package list in the installer; the file ecsInst1_2\SOURCE\COMMON\GPS\xx\eiPackag.gps may need to be modified to add these various options as appropriate.


Adjust ECS\INSTALL\DEFAULT\PACKAGE.RSP with any changed options suitable for the new NLV (e.g. language-specific fonts).


Also add the file ecsInst1_2\COMMON\ECS\BOOT\DESKTOP\ZZZ\INI.RC. This is almost the same as the above file, but is used for the CD boot desktop. You can copy this from the one above, but some values will have to be changed as the paths are different. Compare the differences in another NLV to see what must be changed. (In fact, in most SBCS NLVs you can just use the English version of this file, because none of the language-specific text will be seen by the user anyway. However, for DBCS versions, some font-specific entries and a few other things must be correct for the current language.)






6. Update ecsInst1_2\SOURCE\LIST\xx_yy\Makefile.OS2 and DIRLIST.LST:




7. Populate the ecsInst1_2\PROGRAM\MEMDISK\BIN\xx directory by copying the files from another NLV.

8. Create the Guided Procedure scripts:



9. Edit the script ecsInst1_2\CONFIGURE.CMD, and make sure that xx is included in the 'short_languages' string, and xx_yy in the 'long_languages' string.


Building


You should now be ready to try building the NLV installation CD. Run 'configure' to select the new language, and then 'make iso'.

Some common errors you may encounter:


Other Tasks


1. Install the patched JFS drivers required to support Bootable JFS.


2. Patch LVM.DLL for the 1024-cylinder and Boot Manager fixes.
(TODO)

3. Update the Peer install files with the SMP fix from IBM.
(TODO)

4. (Optional) Delete all files named PACK?? from under OS2IMAGE\DISK_* except for the one which contains MMPMDIG.FON; delete the corresponding entries from the file OS2IMAGE\DISK_3\BLISTLAY.OUT. This frees up several megabytes of disk space on the final CD.
Powered by eComStation Get Firefox! This page has been accessed 5989 times :: Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by Wikka Wakka Wiki 1.1.6.0
Page was generated in 0.6554 seconds