Most recent edit on 2010-04-11 07:32:43 by AlexTaylor

Additions:
A: Yes, but it requires some slightly awkward manual setup.

• • SOURCE\COMMON\GPS\xx\EINET*_CLI.GPS, renaming them to remove the trailing '_CLI'. (If you are testing the server installation, use the *_SRV.GPS files instead.)

By default, the installer will generate response files in \ECS\INSTALL\RSP on the selected install drive. For this reason, you are advised not to select your actual eCS drive as the installation target. Alternatively, you can have the response files placed in another location by editing every single GPS file (in the NLS\xx subdirectory you created) which defines a response file path, and changing that path to somewhere more appropriate. (There are quite a few files you need to change, although you can probably skip the ones named RE*.GPS and RI*.GPS. Running grep -i "\\\\ecs\\\\install\\\\rsp" *.gps should show you what needs changing.)
You may also wish to comment out the INCLUDE=MAKEDIRS.GPS statement from INSTMODE.GPS, EAS_FORM.GPS, and ADV_FORM.GPS, otherwise the installer will create a bunch of directories on whatever drive you choose as your install drive. (However, you should make sure the target directory for writing response files — ?:\ecs\install\rsp by default — actually exists, unless you changed it as above.)

Deletions:
A: Yes, but it requires some rather tricky manual setup.

• • SOURCE\COMMON\GPS\xx\EINET*_CLI.GPS, renaming them to remove the trailing '_CLI'. (If you are testing the server installation, copy the *_SRV.GPS files instead.)

By default, the installer will generate response files in \ECS\INSTALL\RSP on your boot drive, which may overwrite the actual response files that were used to install your system (depending on your selections). This is not necessarily a problem, since these files are not used after installation, but you should be warned anyway. If you prefer it not to do this, then you will need to edit every single GPS file (in the NLS\xx subdirectory you created) which defines a response file path, and change that path to somewhere more appropriate. There are quite a few files you need to change, although you can probably skip the ones named RE*.GPS and RI*.GPS. Running grep -i "\\\\ecs\\\\install\\\\rsp" *.gps should show you what needs changing.
You may also wish to comment out the contents of MAKEDIRS.GPS, otherwise it'll create a bunch of directories on whatever drive you choose as your install drive.

---

Edited on 2010-04-02 14:20:57 by AlexTaylor [Tweaks]

Additions:
~- Edit EINETCMN.GPS and make sure the 'Data=100' item contains the name of the directory where NIC drivers may be found.
To enable hardware detection (optional):

• Copy the contents of the COMMON\ECS\INSTALL\DETECTEI directory into a subdirectory of the test installer directory.
• Edit EIHARDWR.GPS and make sure the path to the above directory (under the 'Data=10' section) is specified correctly. The path should be specified relative to the location of the GuidProc executables.

SET MEMDRIVE=Z
Where:

• xx is the subdirectory of the language files you are testing. (You can also put '%1' in your CMD file instead of the directory name; this lets you specify it on the command line instead if you want to be able to test multiple different languages.)
• Z is a drive letter of your choice; it should not have a trailing colon.

Note: The SET MEMDRIVE statement is important; GuidProc will not run properly without it. The drive you specify must exist, although there doesn't have to be anything on it. (I recommend using a RAM disk if you have one.) The installer debug logfile and hardware detection files will get written to the root directory of this drive.
Do not attempt to start the actual install process using this method. Cancel out of the installer once you reach the last page (or at whatever earlier point is suitable for your testing).

Deletions:
~- Edit EINETCMN.GPS and make sure the Data=100 variable contains the name of the directory where NIC drivers may be found.

• Edit EIHARDWR.GPS and make sure the path to the detectei directory (under Data=10) is correct, relative to the location of the GuidProc executables. (This is optional; without it, hardware detection will not run.)

set MEMDRIVE=Z
The SET MEMDRIVE is important; the drive you specify must exist, although there doesn't have to be anything on it. (I recommend using a ram disk if you have one.) The installer debug logfile will get written to it.
Do not attempt to start the actual install process using this method. Cancel out of the installer once you reach the last page (or at whatever earlier point is suitable for your testing).

---

Edited on 2010-04-02 11:30:15 by WikkaAdmin [Corrected MEMDRIVE statement (skip the colon!)]

Additions:
set MEMDRIVE=Z

Deletions:
set MEMDRIVE=Z:

---

Edited on 2010-04-02 09:15:06 by AlexTaylor [Added requirements for NIC support and hardware detection.]

Additions:
~- Edit EINETCMN.GPS and make sure the Data=100 variable contains the name of the directory where NIC drivers may be found.

• Edit EIHARDWR.GPS and make sure the path to the detectei directory (under Data=10) is correct, relative to the location of the GuidProc executables. (This is optional; without it, hardware detection will not run.)
  
  

  ---

  
  Edited on 2010-03-22 03:43:55 by AlexTaylor
  
  Additions:
  You may also wish to comment out the contents of MAKEDIRS.GPS, otherwise it'll create a bunch of directories on whatever drive you choose as your install drive.
  
  Deletions:
  You should also comment out all the contents of MAKEDIRS.GPS, otherwise it'll create a bunch of directories on whatever drive you choose as your install drive.
  
  

  ---

  
  Edited on 2010-03-22 03:43:08 by AlexTaylor
  
  Additions:
  By default, the installer will generate response files in \ECS\INSTALL\RSP on your boot drive, which may overwrite the actual response files that were used to install your system (depending on your selections). This is not necessarily a problem, since these files are not used after installation, but you should be warned anyway. If you prefer it not to do this, then you will need to edit every single GPS file (in the NLS\xx subdirectory you created) which defines a response file path, and change that path to somewhere more appropriate. There are quite a few files you need to change, although you can probably skip the ones named RE*.GPS and RI*.GPS. Running grep -i "\\\\ecs\\\\install\\\\rsp" *.gps should show you what needs changing.
  
  Deletions:
  By default, the installer will generate response files in \ECS\INSTALL\RSP on your system boot drive, which will overwrite the existing, actual response files that were used to install your real system. (This is not necessarily a problem, since these files are not used after installation, but you should be warned anyway.) If you prefer it not to do this, then you will need to edit every single GPS file (in the NLS\xx subdirectory you created) which defines a response file path, and change that path to somewhere more appropriate. There are quite a few files you need to change, although you can probably skip the ones named RE*.GPS and RI*.GPS. Running grep -i "\\\\ecs\\\\install\\\\rsp" *.gps should show you what needs changing.
  
  

  ---

  
  Edited on 2010-03-22 03:40:02 by AlexTaylor [Added instructions for GPS files in SOURCE. More formatting improvements.]
  
  Additions:
  

  Testing the Installer Without Building a CD

Q: Is there a way to test installer files (.GPS scripts or GuidProc modules) without building a CD and running an installation (e.g. under Virtual PC)?

• Copy *.EXE and *.DLL from the COMMON\ECS\INSTALL directory to your test directory.
• Create an NLS\xx subdirectory for the GPS files, where xx is the language you are testing for. Copy the following files to this subdirectory:
  • *.GPS and *.DLL from the COMMON\ECS\INSTALL\NLS\xx
  • SOURCE\COMMON\GPS\xx\EIPACKAG.GPS
  • SOURCE\COMMON\GPS\xx\EINET*_CLI.GPS, renaming them to remove the trailing '_CLI'. (If you are testing the server installation, copy the *_SRV.GPS files instead.)
• Edit EISTART.GPS and change 'MODE=shell' to 'MODE=wizard'.

By default, the installer will generate response files in \ECS\INSTALL\RSP on your system boot drive, which will overwrite the existing, actual response files that were used to install your real system. (This is not necessarily a problem, since these files are not used after installation, but you should be warned anyway.) If you prefer it not to do this, then you will need to edit every single GPS file (in the NLS\xx subdirectory you created) which defines a response file path, and change that path to somewhere more appropriate. There are quite a few files you need to change, although you can probably skip the ones named RE*.GPS and RI*.GPS. Running grep -i "\\\\ecs\\\\install\\\\rsp" *.gps should show you what needs changing.
Finally, create a CMD file to launch the installer. It should be something like:
Do not attempt to start the actual install process using this method. Cancel out of the installer once you reach the last page (or at whatever earlier point is suitable for your testing).

Deletions:

Testing the Installer Without Building a CD

Q: Is there a way to test installer files (.GPS scripts or GuidProc modules) without building a CD and running an installation (e.g. under Virtual PC)?

• Copy *.EXE and *.DLL from the common\ecs\install directory to your test directory.
• Create an NLS\xx subdirectory for the GPS files, where xx is the language you are testing for. Then copy all *.GPS and *.DLL from the common\ecs\install\nls\xx to this subdirectory.
• Edit EISTART.GPS and change 'MODE=shell' to 'MODE=wizard'.

If you don't want the installer to stick its RSP files in ?:\ecs\install\rsp (which may overwrite your real ones), you also need to edit every single GPS file which defines a response file path, and change that path to somewhere convenient. There are quite a few files you need to change, although you can probably skip the ones named RE*.GPS and RI*.GPS. Running

grep -i "\\\\ecs\\\\install\\\\rsp" *.gps

should show you what needs changing.
Finally, create a CMD file to launch the installer, something like:
Obviously, you shouldn't try to actually start an install using this method. Just cancel out of the installer once you reach the last page (or before).

---

Edited on 2010-03-19 08:19:36 by AlexTaylor [Formatting improvements]

Additions:
Q: Is there a way to test installer files (.GPS scripts or GuidProc modules) without building a CD and running an installation (e.g. under Virtual PC)?
A: Yes, but it requires some rather tricky manual setup.
First:

• Create a new directory for your "test" installer (it can be anywhere, but preferably not inside your CVS sandbox).
• Copy *.EXE and *.DLL from the common\ecs\install directory to your test directory.
• Create an NLS\xx subdirectory for the GPS files, where xx is the language you are testing for. Then copy all *.GPS and *.DLL from the common\ecs\install\nls\xx to this subdirectory.
• Edit EISTART.GPS and change 'MODE=shell' to 'MODE=wizard'.

set MEMDRIVE=Z:
guidproc.exe nls\xx\eistart.gps .
The SET MEMDRIVE is important; the drive you specify must exist, although there doesn't have to be anything on it. (I recommend using a ram disk if you have one.) The installer debug logfile will get written to it.

Deletions:
~& Is there a way to test the *.gps files without making an .iso and running an installation e.g. under VPC?
Yes, but it requires some fiddly setup, and in many ways it isn't really ideal.
Basically, create a new directory tree for your "test" installer. Copy *.EXE and *.DLL from the common\ecs\install directory it, and create an NLS\NL subdirectory for the GPS files. Then copy all *.GPS and *.DLL from the common\ecs\install\nls\nl to this subdirectory.
Edit EISTART.GPS and change 'MODE=shell' to 'MODE=wizard'.
set MEMDRIVE=i:
guidproc.exe nls\nl\eistart.gps .
The SET MEMDRIVE is important, although there doesn't have to be anything there. (I have a ram disk which I use.) The installer debug logfile will get written to it.

---

Oldest known version of this page was edited on 2010-03-18 08:30:38 by AlexTaylor [First version (copied from an email conversation)]

Testing the Installer Without Building a CD

• Is there a way to test the *.gps files without making an .iso and running an installation e.g. under VPC?

Yes, but it requires some fiddly setup, and in many ways it isn't really ideal.

Basically, create a new directory tree for your "test" installer. Copy *.EXE and *.DLL from the common\ecs\install directory it, and create an NLS\NL subdirectory for the GPS files. Then copy all *.GPS and *.DLL from the common\ecs\install\nls\nl to this subdirectory.

Edit EISTART.GPS and change 'MODE=shell' to 'MODE=wizard'.

If you don't want the installer to stick its RSP files in ?:\ecs\install\rsp (which may overwrite your real ones), you also need to edit every single GPS file which defines a response file path, and change that path to somewhere convenient. There are quite a few files you need to change, although you can probably skip the ones named RE*.GPS and RI*.GPS. Running
should show you what needs changing.

You should also comment out all the contents of MAKEDIRS.GPS, otherwise it'll create a bunch of directories on whatever drive you choose as your install drive.

Finally, create a CMD file to launch the installer, something like:

@echo off
setlocal
set MEMDRIVE=i:
guidproc.exe nls\nl\eistart.gps .
endlocal

The SET MEMDRIVE is important, although there doesn't have to be anything there. (I have a ram disk which I use.) The installer debug logfile will get written to it.

Obviously, you shouldn't try to actually start an install using this method. Just cancel out of the installer once you reach the last page (or before).