Monthly Archives: July 2011

Mercurial hg pull, hg push and hg update

A small tutorial on using Mercurial as a website repository.

This is a small tutorial on how to use mercurial 1.8.4. as a version control system. If you need information on what a version control system is: check out this link: Version Control.

A few things to note:

Configuring your repository:

  • Make sure to be in the correct directory before you do any commands in mercurial, you may end up making changes you will regret later!
  • My Repository (home repository) is located in “D:\Repositories”.
    • It’s called “Repo_1”, located at “D:\Repositories\Repo_1”.

Hg Pull

  1. At some point we might want to make changes to “Repo_1”. We can pull “Repo_1” from the Mercurial website Repository. “A pull propagates changesets from a “remote” repository (the source) into a local repository (the destination)” (Mercurial Wiki). When one pulls from the “source” repository, only changes that are not in the “home” repository will be added. Hg pulls all the changes, but doesn’t automatically update your working directory with the changes. The changes pulled area called ‘changesets’, and can include files, branches, heads, etc.
  2. Note: If you want to pull you must first have a repository named/initialized in your repository folders.
  3. Notice that if the repository is named correctly and not initialized the command “hg pull” will not work. The repository must be named and initialized for “hg pull” to work.
  4. The commands for “hg init” are below. (hg init initializes the repository)
    cd D:\repositories\hg\repo_1
    hg init
  5. The commands for “hg pull” are below
    cd D:\repositories\hg\repo_1
    hg pull https://mercurial.<your domain>/hg/repo_1
    enter username: <your username>
    enter password: <your password>
  6. If everything went correctly your home repository will have changesets added to it from the source repository.
  7. Keep the command prompt open, we will be using this for “hg update”.

Hg update

  1. Now that we have pulled the changesets of Repo_1 off of the source repository, it is now possible to retrieve the files and folders off of the source repository. We can do this by using the command “Hg update”.
  2. My home repository for Repo_1 has no files contained inside of it.
  3. The source repository has three files on it right now, that I want on the home repository.
  4. My source repository has three files called “Repo_1_text.txt”, “Repo_update_text.txt” and “Other_New_Text.txt”. My goal is to have these files added to my home repository “Repo_1”.
  5. You always want to “hg pull” before we can do an “hg update”. That way, you have the most current repo information. You should still have the command prompt open from the last step. In the command prompt type in the following command.
    hg update
  6. Simple! If everything worked out correctly, the three files from the source repository will be inside your home repository.

Hg Push

  1. Now let’s say we added a couple files to our home repository. These files are called “fox.txt” and “zebra.txt”. We have our current home repository how we like it, now we want to update the source repository to reflect the changes we’ve made. We can do this by “pushing” our changesets to the source repository.
  2. Couple updates, we must run “hg add” to add the “zebra.txt” and “fox.txt” files to our repository. Then we must run “hg commit“. It’s necessary to “commit” before each “push”.
  3. Here is my home repository before the hg push.
  4. Commands for push
    hg add
    hg commit -m "message" --user "username"
    hg push https://mercurial.<yourDomain>/hg/repo_1
  5. This is what the source repository looks like after the push.
Side Note: If you liked/disliked this blog please leave a comment! I want to know what you think!

Posted by on July 22, 2011 in Mercurial, Mercurial Tutorial


Tags: , , , ,

Net Stop 5 (Pro) Kiosk Set Up Instructions

This blog post covers setting up a kiosk computer running Netstop Pro. Students use the computer to watch video tutorials on chemistry experiments. When they finish, the kiosk will print a certificate stating they finished the tutorial. The purpose of Netstop is to ensure that unauthenticated users can’t abuse access to the networked machine.

A few things to note:

  • Operating System: Windows 7 64bit
  • Domain: KioskDomain
  • Software: NetstopPro latest build

Setting up the computer and users on the Domain:

  1. Ensure the “kioskPc” is connected to the domain.
  2. Open “Active Directory Users and Computers”.
  3. Make sure the KioskPC is connected to your Domain, and that it’s in the correct OU per your organizational standards.
  4. Create a new user for the kiosk. This will be the user what the kiosk automatically logs in as when it boots. I’ve named my user “DomainUser”.

  5. Ensure that the DomainUser account is not set as a Domain Administrator.

Preparing the computer.

  1. Start with a fresh install of Windows 7 SP1 64 bit, fully patched.
  2. Logon as the local administrator.
  3. Under “User Account Settings”, turn “User Account Control settings” to “Never Notify”.

Installing Netstop Pro:

  1. Logon to the computer as the local administrator. If you install as a domain administrator, the install will proceed without warning but secure mode will not work with a limited user account.
  2. Double Click “NetstopSetup_370.exe”. After the installer starts Click “Next”.
  3. Accept the License Agreement and click next.
  4. Select Destination Location and start menu folder click next.
  5. At the final screen click install.
  6. Installation will finish and when it does choose “Restart now”.
  7. After the restart log in as the local administrator.
  8. There should be two new icons on your desktop, “Designer Pro” and “ShellPro”. Designer Pro is used for setting up how ShellPro will function.

Configuring ShellPro

  1. I’m going to concentrate on the important sections of Designer Pro and leave the rest up to you to set up (graphical interface stuff).
  2. Open Designer Pro, find and expand “Access”, then click “Keyboard Settings”.
    • Uncheck “Enable Key Control” and any boxes under “Suppressed Key Combinations”.
    • Check “Allow Disabling”, this allows you to unlock ShellPro. Set four keys that will allow disabling.
  3. The reason we unchecked the “Enable Key Control” setting is for testing purposes. When first using Netstop Pro, I locked myself out of the program multiple times. This happens because in secure mode the ctrl-alt-del function is disabled. Even after a reboot the computer will still be in secure mode.
  4. Still under “Access” scroll down and click “Admin Password”. Choose a password for “Admin Password (full and Limited)”.
  5. Under “Access” right below “Admin Password”, select “Windows XP/Vista/7 Secure Mode User”. These are very important steps, if these are done incorrectly, you may be locked out of your computer!
  6. Under “Kiosk Secure Mode User”, for “User” enter DomainUser, for password type DomainUser’s Windows logon password. For the domain type kioskDomain.
  7. For the “Admin Account {Reboot to Desktop}”, the user will be the local administrator or just “administrator” and the password will be the local administrator’s windows logon password. Leave the Domain blank.
  8. This is enough to get this up and running, close Designer Pro.
  9. Open Shellpro. My home screen looks like so.
  10. Now as you can see there isn’t much going on here, that’s good! To unlock your computer from ShellPro you must hit your disabling keys, then directly afterward type in your “Admin Password”, set in step 4. After the password is entered, ShellPro will present a menu.
  11. Choose “Reboot to Secure Mode”. After reboot, the Domain User (DomainUser) will be logged in automatically and ShellPro should start up right after the logon screen.
  12. If for some reason ShellPro doesn’t run (i.e. blank black/blue screen), Press ctrl-alt-del and login as “administrator”, this should make ShellPro start. From here you can open the menu and “Reboot to Desktop”, which will return you to the desktop. If you experience this “blank screen”, go through this guide again and see if you missed anything.
  13. When everything is set up how you want it, remember to go back to the “keyboard settings” and disable keys that you do not want the user to be able to use.
Side Note: If you liked/disliked this blog please leave a comment! I want to know what you think!
Leave a comment

Posted by on July 12, 2011 in Net Stop Pro Kiosk


Tags: , , ,

The task sequence has been suspended [Solution]

Recently I was re-imaging a computer and I came accross an unusual error.

*This picture was taken from google images.

For extra clarity here is what the message says:

  • The task sequence has been suspended.
  • Litetouch has encountered an Environment Error (Boot into WinPE!).
  • If booting from a USB Flash Disk, please remove all drives before Retrying.
  • Otherwise, ensure the hard disk is selected first in the boot order of the BIOS.
  • Reboot WinPE (Close all windows) to resume.

Solution to this error:

I found the solution on this site: The Decoder Wheel. For reference, here are the steps:
  • Note: This will delete all information on disk 0.
  • Hit F8 at the error message, this will bring up the command prompt.
  • Type diskpart
  • Type Select disk 0
  • Type clean    (hit enter)
Side Note: If you liked/disliked this blog please leave a comment! I want to know what you think!

Posted by on July 6, 2011 in Re - Imaging


Tags: , , , , , ,