Many downloads like Bibleworks 8 may also include a serial number, cd key or keygen. If this is the case then it's usually included in the full crack download archive itself. If you are still having trouble finding Bibleworks 8 after simplifying your search term then we highly recommend using the alternative full download sites (linked above). Bibleworks 8 serial numbers, cracks and keygens are presented here. No registration is needed. Just download and enjoy. As of June 15, 2018 BibleWorks ceased operation as a provider of Bible software tools. (installation requires activation code purchased before July 1, 2018.
John abraham in gym wallpaper for mac. https://softwareshift.mystrikingly.com/blog/sims-free-2019. There are two ways to install BibleWorks on a network: 1) Standalone configuration, or 2) Server configuation. Please note that the BibleWorks 9 Mac Installer does not support the Server configuration.
In a Standalone configuration, BibleWorks is installed locally on each workstation on the network. With Standalone configuration, no data is shared between workstations and when BibleWorks needs to be updated, each workstation will need to be individually updated.
For Mac users, you will need to purchase a BW9 Mac Installer code for each workstation running on a Mac. Click here for Mac installation instructions.
Here are the installation steps for BibleWorks in Standalone configuration on machines running Windows XP/Vista/7/8:
- Using an account with Local Administrator privileges, install BibleWorks onto a workstation just as you would normally install BibleWorks on a home computer. Note: When entering activation codes:
- If you received one BW90 and BNET activation code per node, then use a separate code for each machine.
- If you received only one BW90 and BNET activation code, use that code for all machines.
- The installation program should instruct you to restart after the files are all copied. Restart your computer.
- Using an account with Local Administrator privileges, run the program and activate the program and all modules.
- Using an account with Local Administrator privileges, apply any available BibleWorks updates from the Internet (Help | BibleWorks on the Internet | Check for updates). This is very important as fixes to the EXE file may have been issued after your DVD pressing.
- Shut down BibleWorks.
Multiple user accounts in a standalone configuration
Please note that the BibleWorks 9 Mac Installer does not support Multiple user accounts in a standalone configuration.
If you have installed BibleWorks on a machine (standalone configuration) and users will use BibleWorks directly on that machine through multiple user accounts, you can take configure BibleWorks to maintain individual settings and files for each user account. To enable this optional feature, follow these steps: Pella impervia vs milgard ultra.
- Create a shortcut to the BibleWorks executable. (Right-click on the bw900.exe file and select 'Create shortcut'.)
- In the Target field add /localuser='user' to the path shown. In the above example, the Target field would now contain
'C:Program Files (x86)BibleWorks 9bw900.exe' /localuser='user' - The Start in field should contain the full local path to the BibleWorks installation folder (e.g. 'C:Program Files (x86)BibleWorks 9'). The path should be surrounded by double-quotes.
- This shortcut can now be copied to all local users who will use the program. To run BibleWorks on the local machine with personal BibleWorks settings, the local user should run BibleWorks from this created shortcut.
Please note that the BibleWorks 9 Mac Installer does not support the Server configuration.
In a Server configuation, the installation procedures are a little more involved, but no files, except for a shortcut link, are stored on the workstations on the network. In this configuration, only the server installation needs to be updated when applying BibleWorks updates and patches. Setting up a Server configuration of BibleWorks involves the following steps:
I. Install BibleWorks on the server.
Select a node or server that accessible by all users who need access to BibleWorks. For the illustration purposes of this guide let us assume that you will be doing a full installation on a server named Snoopy in the directory c:Program FilesBibleWorks 9. On the server, please follow the steps below:
- Using a Local Administrator account, install BibleWorks and any additional BibleWorks modules you have purchased.
When running the installer, make sure you enter the activation codes both for BibleWorks 9 and for Network Installation. The BibleWorks 9 activation code is of the form 'BW90-WWWW-XXXX-YYYY-ZZZZ'. The Network Installation activation code is of the form 'BNET-WWWW-XXXX-YYYY-ZZZZ'. A full installation is strongly recommended. - On the server, run the program and activate the program and all modules.
NOTE: You must activate the network installation activation module before adding remote users on the workstations. If you do not activate the network support activation, the necessary files will not be copied. All modules should be installed and activated on the server before adding remote users on client machines. If not, the modules will not work. If you add modules to the server at a later date, then you must manually copy the *.ACV files from the BibleWorks 9init folder on the server to each BibleWorks 9users*init folder on the server. - Apply any available BibleWorks updates from the Internet (Help | BibleWorks on the Internet | Check for updates). This is very important as fixes to the EXE file may have been issued after your DVD pressing.
- Shut down BibleWorks.
- Change the folder sharing and security permission settings on the server.
a) On the server, enable the sharing of the BibleWorks 9 folder on the network (Properties | Sharing | Share this folder). In this window click 'Permissions' and set 'Full Control' for 'Everyone' and all User Groups which will use BibleWorks over the network.
b) Also select the Properties | Security settings, and enable 'Full Control' (which includes both Change and Read) for Everyone as well as for all users and user groups (Users, Authenticated Users) that will be accessing the server. See the pictures below. - Configure your workstation user accounts to connect to the BibleWorks folder when the user logs in.
II. Install the BibleWorks fonts and Adobe Flash Player on each workstation.
BibleWorks comes with a set of TrueType fonts that must be installed on each workstation in order to view Greek and Hebrew text. After the server installation, all of these fonts will be located in SnoopyBibleWorks 9 (where 'Snoopy' is your server name). Install all of the fonts found in this folder with the exception of Hebrew.ttf.
To view the training videos, Adobe Flash (for IE) needs to be installed on each workstation. If Flash is not installed, you can install it by running the install_flash_player_10.exe and install_flash_player_10_active_x.exe programs in the server BibleWorks folder. You need to be running from an account on the workstation with Administrative privileges to do this.
III. Change the Local Intranet security settings on each workstation.
In order to enable BibleWorks to run over the network without seeing the Open File - Security Warning window each time the program is started, the Local Intranet security settings need to be set as described below on each workstation that will connect to the server.
A. Set Computer Configuration settings
If you know how to use the Group Policy Object Editor, edit the following settings at Computer Configuration-Administrative Templates-Windows Components-Internet Explorer-Internet Control Panel-Security Page:
The following settings should be set here:
Turn on Automatic detection of intranet - Enabled (This option may only be visible with IE7+.)
Intranet Sites: Include all local (intranet) sites not listed in other zones - Enabled
Intranet Sites: Include all sites that bypass the proxy server-Enabled
Intranet Sites: Include all network paths (UNCs)-Enabled
Site to Zone Assignment List: Add the server name to the zone (e.g. SNOOPY) and give it a value of 1.
B. Set User Configuration settings
In the Group Policy Object Editor, go to
User Configuration-Windows Settings-Internet Explorer Maintenance-Security: What is the equivalent of word in mac.
Early 2011 macbook pro mojave. Right-click 'Security Zones and Content Ratings' and click 'Properties'.
Select 'Import the current security zones and privacy settings'. If you are prompted, click 'Continue'. Then click 'Modify Settings'.
Select 'Local Intranet' and then click 'Sites'.
The following settings should be set:
Include all local (intranet) sites not listed in other zones - Enabled
Include all sites that bypass the proxy server-Enabled
Include all network paths (UNCs)-Enabled
Click Advanced and enter the server name to the zone as a trusted site (e.g. SNOOPY). Click the Add button. (The server name should now appear in the Websites list.)
C. Link the GPU that you created and run 'gpupdate'
These changes should prevent the Open File - Security Warning window from displaying when BibleWorks is run from the client workstations.
Manual instructions: Alternately, to set the Local Intranet settings on the workstations without using Group Policies, you can do the following.
- On each of the workstations, login to the user accounts (the account that users will use when they are running BibleWorks).
- Open the Windows Control Panel | Internet Options | Security.
- Then, select 'Local intranet'.
- Click the Sites button.
- In the Local intranet window that opens, all the checkboxes should be checked. You may need to temporarily uncheck 'Automatically detect intranet network' in order to check all checkboxes.
- Select the Advanced button.
- In the 'Add this website to the zone' field, enter two backslashes followed by the name of the server. In our example, you would enter 'Snoopy'
- Click the Add button.
IV. Create a shortcut on each workstation.
In the network installation, user-selected settings are unique for each user, regardless of workstation. The BibleWorks fonts are stored on the workstation; all other files (including most executable and initialization files) are stored on the server.
- Create a shortcut file pointing to the BibleWorks executable. It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9').
- Open the Properties window for the shortcut and set the 'Target' field to point to the program file on the server. After the 'Target' path you must also include the string
/remoteuser='user'
(including the quotes and preceded by a space). The string /remoteuser='user' tells BibleWorks to create files and directories on the server in such a way as to allow each user access to their own settings and files regardless of which workstation the user logs onto.
For our example, if your server name is 'Snoopy', the 'Target' parameter would look like this:
'SnoopyBibleWorks 9bw900.exe' /remoteuser='user'
When the /remoteuser='user' setting is used, it is necessary to have already activated the network capability through activation of a network activation code. This activation code is entered above under step 1.The word 'user' can be any name. If you use the word 'user', the operating system will look up the name of the current user and substitute the current user name for the word 'user'. If you use a different name in place of 'user', the name used will be the name of the file where the new user's files will be located. - You must also enter the full path of the BibleWorks main directory in the 'Start in' field of the shortcut properties window. It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). 'Start in' would look like this for our example:
'SnoopyBibleWorks 9' - The shortcut can now be copied to all workstations which will be accessing BibleWorks.
V. Set up the COM Server settings.
BibleWorks needs to be registered as a COM server on each of the workstations. This, among other things, allows BibleWorks to provide popup verse text inside HTML Help files. To do this automatically, on each workstation that will be using BibleWorks, the following command needs to be run using Administrator privilegeswith elevation:
'SnoopyBibleWorks 9bw900.exe' /netclsetup
(where 'Snoopy' is the server name). It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). Under Vista, if you create a shortcut to do this, right-click the shortcut and select 'Run as administrator'.
If the 'Run As' window (see below) appears, select Current User and uncheck 'Protect my computer'. Click OK.
Bibleworks 10 Torrent
VI. Change the HTML Help security settings.
To set the HTML Help security settings on the workstations automatically, run the same automatic command described for automatically registering the BibleWorks COM server. If you have already done this, the step does not need to be repeated. On each workstation that will be using BibleWorks, the following command needs to be run using Administrator privilegeswith elevation:
'SnoopyBibleWorks 9bw900.exe' /netclsetup
(where 'Snoopy' is the server name). It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). In Vista, if you create a shortcut to do this, right-click the shortcut and select 'Run as administrator'.
If the 'Run As' window (see below) appears, select Current User and uncheck 'Protect my computer'. Click OK.
If for some reason that does not work, you can follow the manual instructions below:
Manual Instructions: On each workstation, using Administrator privileges, apply the hhctrl.reg file found in the BibleWorks main folder.
To see what security issues are involved in doing this see the following Microsoft links:
http://support.microsoft.com/?kbid=896054
http://support.microsoft.com/?kbid=892675
VII. Informational Note
The first time a user double clicks this shortcut to access the program, a subdirectory will be created on the server to store that user's files. The name of the directory will be derived from the user's login name on the workstation computer. John deere js48 service manual. For example, if a user logs in under the name 'JoeCool' a folder named 'snoopyBibleWorks 9usersJoeCool' will be created on the server snoopy to store any files that are created or modified by JoeCool.
VIII. Possible problems
BibleWorks starts from client machines but crashes on startup
Verify that BibleWorks and the BibleWorks Network Installation module are both activated on the server.
Verify that the client machine can read and write to the BibleWorks folder on the server (copy a test file from the client to the server folder).
Verify that the two folder settings for the BibleWorks shortcut on the client machines are correct.
Verify that all steps above are followed, particularly noting which steps need to be run as an Administrator and which steps need to be run from the user account.
BibleWorks keeps trying to register the COM/Automation server
In the above steps, it is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). Please check batch files and shortcuts and ensure you are using UNC pathnames with ServerName syle paths.
Then, please follow these manual instructions: Game tembak 3d untuk laptop.
In a Server configuation, the installation procedures are a little more involved, but no files, except for a shortcut link, are stored on the workstations on the network. In this configuration, only the server installation needs to be updated when applying BibleWorks updates and patches. Setting up a Server configuration of BibleWorks involves the following steps:
I. Install BibleWorks on the server.
Select a node or server that accessible by all users who need access to BibleWorks. For the illustration purposes of this guide let us assume that you will be doing a full installation on a server named Snoopy in the directory c:Program FilesBibleWorks 9. On the server, please follow the steps below:
- Using a Local Administrator account, install BibleWorks and any additional BibleWorks modules you have purchased.
When running the installer, make sure you enter the activation codes both for BibleWorks 9 and for Network Installation. The BibleWorks 9 activation code is of the form 'BW90-WWWW-XXXX-YYYY-ZZZZ'. The Network Installation activation code is of the form 'BNET-WWWW-XXXX-YYYY-ZZZZ'. A full installation is strongly recommended. - On the server, run the program and activate the program and all modules.
NOTE: You must activate the network installation activation module before adding remote users on the workstations. If you do not activate the network support activation, the necessary files will not be copied. All modules should be installed and activated on the server before adding remote users on client machines. If not, the modules will not work. If you add modules to the server at a later date, then you must manually copy the *.ACV files from the BibleWorks 9init folder on the server to each BibleWorks 9users*init folder on the server. - Apply any available BibleWorks updates from the Internet (Help | BibleWorks on the Internet | Check for updates). This is very important as fixes to the EXE file may have been issued after your DVD pressing.
- Shut down BibleWorks.
- Change the folder sharing and security permission settings on the server.
a) On the server, enable the sharing of the BibleWorks 9 folder on the network (Properties | Sharing | Share this folder). In this window click 'Permissions' and set 'Full Control' for 'Everyone' and all User Groups which will use BibleWorks over the network.
b) Also select the Properties | Security settings, and enable 'Full Control' (which includes both Change and Read) for Everyone as well as for all users and user groups (Users, Authenticated Users) that will be accessing the server. See the pictures below. - Configure your workstation user accounts to connect to the BibleWorks folder when the user logs in.
II. Install the BibleWorks fonts and Adobe Flash Player on each workstation.
BibleWorks comes with a set of TrueType fonts that must be installed on each workstation in order to view Greek and Hebrew text. After the server installation, all of these fonts will be located in SnoopyBibleWorks 9 (where 'Snoopy' is your server name). Install all of the fonts found in this folder with the exception of Hebrew.ttf.
To view the training videos, Adobe Flash (for IE) needs to be installed on each workstation. If Flash is not installed, you can install it by running the install_flash_player_10.exe and install_flash_player_10_active_x.exe programs in the server BibleWorks folder. You need to be running from an account on the workstation with Administrative privileges to do this.
III. Change the Local Intranet security settings on each workstation.
In order to enable BibleWorks to run over the network without seeing the Open File - Security Warning window each time the program is started, the Local Intranet security settings need to be set as described below on each workstation that will connect to the server.
A. Set Computer Configuration settings
If you know how to use the Group Policy Object Editor, edit the following settings at Computer Configuration-Administrative Templates-Windows Components-Internet Explorer-Internet Control Panel-Security Page:
The following settings should be set here:
Turn on Automatic detection of intranet - Enabled (This option may only be visible with IE7+.)
Intranet Sites: Include all local (intranet) sites not listed in other zones - Enabled
Intranet Sites: Include all sites that bypass the proxy server-Enabled
Intranet Sites: Include all network paths (UNCs)-Enabled
Site to Zone Assignment List: Add the server name to the zone (e.g. SNOOPY) and give it a value of 1.
B. Set User Configuration settings
In the Group Policy Object Editor, go to
User Configuration-Windows Settings-Internet Explorer Maintenance-Security: What is the equivalent of word in mac.
Early 2011 macbook pro mojave. Right-click 'Security Zones and Content Ratings' and click 'Properties'.
Select 'Import the current security zones and privacy settings'. If you are prompted, click 'Continue'. Then click 'Modify Settings'.
Select 'Local Intranet' and then click 'Sites'.
The following settings should be set:
Include all local (intranet) sites not listed in other zones - Enabled
Include all sites that bypass the proxy server-Enabled
Include all network paths (UNCs)-Enabled
Click Advanced and enter the server name to the zone as a trusted site (e.g. SNOOPY). Click the Add button. (The server name should now appear in the Websites list.)
C. Link the GPU that you created and run 'gpupdate'
These changes should prevent the Open File - Security Warning window from displaying when BibleWorks is run from the client workstations.
Manual instructions: Alternately, to set the Local Intranet settings on the workstations without using Group Policies, you can do the following.
- On each of the workstations, login to the user accounts (the account that users will use when they are running BibleWorks).
- Open the Windows Control Panel | Internet Options | Security.
- Then, select 'Local intranet'.
- Click the Sites button.
- In the Local intranet window that opens, all the checkboxes should be checked. You may need to temporarily uncheck 'Automatically detect intranet network' in order to check all checkboxes.
- Select the Advanced button.
- In the 'Add this website to the zone' field, enter two backslashes followed by the name of the server. In our example, you would enter 'Snoopy'
- Click the Add button.
IV. Create a shortcut on each workstation.
In the network installation, user-selected settings are unique for each user, regardless of workstation. The BibleWorks fonts are stored on the workstation; all other files (including most executable and initialization files) are stored on the server.
- Create a shortcut file pointing to the BibleWorks executable. It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9').
- Open the Properties window for the shortcut and set the 'Target' field to point to the program file on the server. After the 'Target' path you must also include the string
/remoteuser='user'
(including the quotes and preceded by a space). The string /remoteuser='user' tells BibleWorks to create files and directories on the server in such a way as to allow each user access to their own settings and files regardless of which workstation the user logs onto.
For our example, if your server name is 'Snoopy', the 'Target' parameter would look like this:
'SnoopyBibleWorks 9bw900.exe' /remoteuser='user'
When the /remoteuser='user' setting is used, it is necessary to have already activated the network capability through activation of a network activation code. This activation code is entered above under step 1.The word 'user' can be any name. If you use the word 'user', the operating system will look up the name of the current user and substitute the current user name for the word 'user'. If you use a different name in place of 'user', the name used will be the name of the file where the new user's files will be located. - You must also enter the full path of the BibleWorks main directory in the 'Start in' field of the shortcut properties window. It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). 'Start in' would look like this for our example:
'SnoopyBibleWorks 9' - The shortcut can now be copied to all workstations which will be accessing BibleWorks.
V. Set up the COM Server settings.
BibleWorks needs to be registered as a COM server on each of the workstations. This, among other things, allows BibleWorks to provide popup verse text inside HTML Help files. To do this automatically, on each workstation that will be using BibleWorks, the following command needs to be run using Administrator privilegeswith elevation:
'SnoopyBibleWorks 9bw900.exe' /netclsetup
(where 'Snoopy' is the server name). It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). Under Vista, if you create a shortcut to do this, right-click the shortcut and select 'Run as administrator'.
If the 'Run As' window (see below) appears, select Current User and uncheck 'Protect my computer'. Click OK.
Bibleworks 10 Torrent
VI. Change the HTML Help security settings.
To set the HTML Help security settings on the workstations automatically, run the same automatic command described for automatically registering the BibleWorks COM server. If you have already done this, the step does not need to be repeated. On each workstation that will be using BibleWorks, the following command needs to be run using Administrator privilegeswith elevation:
'SnoopyBibleWorks 9bw900.exe' /netclsetup
(where 'Snoopy' is the server name). It is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). In Vista, if you create a shortcut to do this, right-click the shortcut and select 'Run as administrator'.
If the 'Run As' window (see below) appears, select Current User and uncheck 'Protect my computer'. Click OK.
If for some reason that does not work, you can follow the manual instructions below:
Manual Instructions: On each workstation, using Administrator privileges, apply the hhctrl.reg file found in the BibleWorks main folder.
To see what security issues are involved in doing this see the following Microsoft links:
http://support.microsoft.com/?kbid=896054
http://support.microsoft.com/?kbid=892675
VII. Informational Note
The first time a user double clicks this shortcut to access the program, a subdirectory will be created on the server to store that user's files. The name of the directory will be derived from the user's login name on the workstation computer. John deere js48 service manual. For example, if a user logs in under the name 'JoeCool' a folder named 'snoopyBibleWorks 9usersJoeCool' will be created on the server snoopy to store any files that are created or modified by JoeCool.
VIII. Possible problems
BibleWorks starts from client machines but crashes on startup
Verify that BibleWorks and the BibleWorks Network Installation module are both activated on the server.
Verify that the client machine can read and write to the BibleWorks folder on the server (copy a test file from the client to the server folder).
Verify that the two folder settings for the BibleWorks shortcut on the client machines are correct.
Verify that all steps above are followed, particularly noting which steps need to be run as an Administrator and which steps need to be run from the user account.
BibleWorks keeps trying to register the COM/Automation server
In the above steps, it is important to use UNC pathnames (e.g. 'snoopyProgram FilesBIbleWorks 9') and not network drive letter pathnames (e.g. 'w:Program FilesBIbleWorks 9'). Please check batch files and shortcuts and ensure you are using UNC pathnames with ServerName syle paths.
Then, please follow these manual instructions: Game tembak 3d untuk laptop.
- Log in to the client machine with an account having Administrator privileges.
- Under Vista, right-click on the shortcut created in the previous steps, hold down the Shift key, and select 'Run as Administrator'. Hold down the Shift key until the Trouble-shooting Options window opens. If an 'Open file-Security Warning' window opens, keep holding the Shift key and click 'Run'.
Under XP, start BibleWorks on the client machine using the shortcut created in the previous steps, holding down the Shift key when you double-click on the shortcut. If an 'Open file-Security Warning' window opens, keep holding the Shift key and click 'Run'. - In the Trouble-shooting Options window that opens, select 'Reset Automation Server', then click 'Perform these actions and exit'.
If the 'Run As' window (see below) appears, select Current User and uncheck 'Protect my computer'. Click OK.
Bibleworks 9 Activation Code
Scripture Popups in Modules or Study Guide links are not working
This usually occurs when the COM server is not registered properly. See section V and the above section.
CHM file pages do not display ('Navigation to the webpage was canceled').
Bibleworks Free
This usually occurs when Internet Security settings and HTMLHelp settings are not adjusted. See sections III and VI.
BibleWorks keeps attempting to install Flash
This can occur if a previous version of BibleWorks or Flash were installed on the workstations. To remedy this, please go to the workstation Control Panel and completely uninstall all Adobe Flash 10 Player entries. Then, re-apply the steps in section II above.
The message 'Could not restore default book name file' appears when the user start BibleWorks
This occurs when /remoteuser='user' is not properly set in the shortcut (see step IV 'Create a shortcut on each workstation') Target field. Please carefully re-do step IV and ensure the Target field and the Start In fields are properly set.
The message 'Open File - Security Warning' appears when the user starts BibleWorks
If the above window appears when the user attempts to run BibleWorks, it is likely that step III ('III. Change the Local Intranet security settings on each workstation') above was not successfully applied. To check if step II was successfully applied, go to a Client workstation, log in as an Admin, and go to
Control Panel | Security | Local intranet | Sites
The following window should display, with ALL checkboxes checked:
Next, click Advanced. If step III was successfully accomplished, your server name (e.g. Snoopy or ws2008) should appear in the Websites list:
If your server is not in this list, carefully re-apply step III. You can also attempt to apply step II manually (see manual instructions at end of step III).
Last revised: December 12, 2012
