Skip to content


The School of Mechanical Engineering seeks to provide students with secure and timely access to IT equipment and online services and resources necessary for undertaking their study.

In addition to the University's IT Acceptable Use and Security Policy the following information provides an overview of acceptable use of computing facilities within the School.

For all enquiries and requests (excluding lost passwords and inabillity to access emails), please contact

  • IT Acceptable Usage Policy

    The University of Adelaide's acceptable use policy governs all use of and access to IT facilities and must be adhered to by all staff, students and visitors. All equipment should only be used for activities relating to university business.

    Illegal software is not allowed on the School of Mechanical Engineering's computers. If questionable software is found on your PC, the School will request proof of licence. If proof cannot be supplied, the software will be removed from the PC and further action may be taken. The School will not provide support for PCs containing illegal software.

    Do not store media files (i.e. video and music files, including personal collections) on the School's PCs for which you do not own the copyright or have appropriate permissions to use. Unauthorised files will be removed and further action may be taken.

    If you wish to connect a device to the School of Mechanical Engineering's network or alter network settings (i.e. IP addresses) on any existing PC on the network, please contact the School. Failure to do this results in considerable disruption to other users, and further action will be taken.

    Due to the potential for misuse, file trading software (i.e. major peer-to-peer downloading software) may not be installed on your PC. Should you require such software for essential activities relating to the School of Mechanical Engineering, please seek prior permission from the School.

    Internet access is provided for activities related to the School of Mechanical Engineering only. As the School is charged for access to the Internet, any students with excessive usage will be asked to justify how it relates to School activities. If usage cannot be justified, the excess charges for Internet access may be passed on to you at the School's discretion.

    Accounts and access may be disabled or downgraded for a time at the discretion of the School for breach of these rules.

  • Final Year Project - IT Acceptable Usage Policy

    The following information relates specifically to final year project IT usage. Disregarding these rules will result in restricted network access and in some cases further action may be taken.

    Supply of PC Hardware

    You may be supplied with a PC for use during your final year project. This PC, and all attached peripherals (including mouse, monitor, keyboard, and network cables) are for the use of you and your project group only, and is not for personal use.

    • Do not "borrow" peripherals for use with other PCs, including personal laptops or other PCs in the room. We do not allow this as it frequently leads to their subsequent theft.
    • Do not interfere with the PCs and peripherals belonging to other project groups.
    • If a piece of hardware, such as a mouse or keyboard, does not function properly, please notify the School so that a replacement can be organised.

    You are welcome to bring in your own mouse and/or keyboard. If you no longer need the supplied mouse and/or keyboard, please contact the School and return them. Do not give them away, swap them, or take them home.

    Please contact the School if:

    • your PC or peripherals have been interfered with
    • you require additional hardware
    • you need to move your PC, either temporarily or on an ongoing basis

    Network Access

    Direct MechEng network access (via the in-wall network points) is strictly controlled. If you have been provided network access, it is for the PC you have been supplied with only.

    • Do not connect any devices to the network on your own. You must contact the School for any new hardware that needs to be connected.
    • Do not change the network settings of any PC that we have configured as it will interfere with other PCs on the network.
    • Do not interfere with the network cabling of yours or any other group's PCs.

    The School strictly enforces these rules due to the great deal of time it takes to track down the cause of network disruptions, and the inconvenience it causes to other users. Further action will be taken for misuse

    Students are welcome to connect to any general university-wide wireless networks (e.g. Freewire) from any personally owned laptop. The School can assist with this if required.

    Account Access

    Accounts are for your use only. Do not share accounts or passwords with other users. If someone else needs an account, please advise them to contact the School.

    Administrative Account Access

    Some users may be given administrative accounts at the request of their project supervisor in limited circumstances. If you are given such access, it is for the particular use for which you were given it only. If you have been given explicit permission to do so, you may only install software directly related to your project as approved by your project supervisor. Do not abuse this privilege or it will be removed immediately and further action will be taken.

    Support Requests

    All general enquiries and support requests should be directed to:

    If you are experiencing hardware, account, or login problems that prevent you from using email, please visit us in Engineering South, room S218. All other problems should be resolved by email.

    Consequences of Breach of Rules

    Action will be taken against individuals who break IT usage rules. Action will depend on the severity of the breach. This may include limited access to network resources or removal of the PC for a period of time. In severe cases, further action may be taken by the School or the University.

  • TortoiseSVN mini-quide for MechEng students

    The Basics

    Subversion is a revision control tool that is used to manage simultaneous modification of a set of project files. The basic idea is that changes are managed in a central repository that all people can access, from which each person can get a copy of the most recent files (SVN Checkout), update their local copy of the files to the latest (SVN Update), and send their changes back to the repository (SVN Commit).

    TortoiseSVN is a graphical interface to the Subversion tool.

    Starting Out

    The first thing we need to do is to create a repository. To do this:

    • Create a folder in a shared location (eg. in a shared folder on a network drive) for your subversion repository. In CATS you may have a folder in "w:\Projects", and in the MechEng labs you may have a folder in "m:\finalyear" (for the latter, if you want one for your project, please contact us). Call it "repos".
    • Right click on it, select "TortoiseSVN" / "Create repository here".
    • Ensure "Native Filesystem (FSFS)" is selected. EXTREMELY IMPORTANT: Do NOT select "Berkeley database (BDB)", it doesn't work properly on network drives. It will fail later.
    • Click "Ok", then "Ok".

    You have now created your repository. You should leave this folder completely alone at this point, as changing the files within can break the repository. Now:

    • Create a new folder somewhere else (on your desktop is fine). Call it "import".
    • Inside this folder, create another folder with a suitable project name. I'll assume that you call this "project" for now.
    • Inside the "project" folder, put all of the files you would like controlled by subversion. You should discuss this with your group and decide which files should and shouldn't go in there.
    • When you are done, return to the "import" folder. Right click on it, select "TortoiseSVN" / "Import".
    • Click the "..." on the right of "URL of repository".
    • Browse to the "repos" folder you made earlier and select "Ok". The URL should now look something like: "file:///your/path/here/repos".
    • Click "Ok".
    • Wait, then click on "Ok".
    • You should now check to see if the import worked correctly. To do this:
      • Locate the "repos" folder, right click on it
      • Select "TortoiseSVN" / "Repo-browser".
      • Browse through the repository by either clicking the "+" button or double-clicking folders.
      • Open a file to view it by right clicking on it and choosing "Open" or "Open with...". This will grab a copy of the file from the repository and open it for you.
    • If the repository looks right, then continue. If it doesn't, remove the repository and retry these instructions.
    • Close the repository browser.

    Now that you are done, move the "import" directory somewhere safe. You won't be using it any more, but it's worth keeping a backup of it, just in case.

    Check Out a Copy

    Eventually, each group member will need to check out a copy from the repository. To do this:

    • Create a working folder that you will be working in. You can actually choose any name you like, but I'll assume that you use "work" for now. It is recommended that you create it on your desktop to start with. In the future you might like to store it on a USB stick instead, to allow you to work at home.
    • Right click on it ("work"), and select "SVN Checkout".
    • Ensure the repository name is correct. If it is blank or you are not sure, browse to the repository ("repos") using the "..." button on the right. The repository should be of the form: "file:///your/path/here/repos". If "project" appears after the repository name, either remove it or browse to "repos" instead.
    • Ensure the checkout directory is correct. The default is generally set to the "work" folder you clicked, and is usually fine.
    • Click on "Ok".
    • The files will now be checked out. Wait, then click on "Ok".

    You can now work on the files. Simply go into your "work" folder, then into "project" (or whatever you called it when setting it up). All of the files you originally imported should be there. Notice that as you make changes, the icon on each file should change from a little green tick to a red exclamation mark. If you have created your "work" folder on a network drive or on your desktop in CATS, you will not see these icons.

    Commit Your Changes

    To send your changes back to the repository where they can be used by other group members, you need to commit your changes. To do this:

    • Right click on your "work" folder, and select  "SVN Commit...".
    • Enter a comment describing your changes, so you and your other group members know why you changed the files. You can look below to see the changes you are about to commit.
    • When you're ready, hit "Ok".
    • Assuming there are no problems, you'll be told the process is complete, after which you should hit "Ok".

    If there are any problems, you may need to do an update first - refer to the next section.

    You can also commit individual files instead if you wish- simply right click the file and select "SVN Commit..." to do so.

    Update Your Copy

    If another group member has changed any files, you will have to perform an update to get those changes from the repository. To do this:

    • Right click on your "work" folder, and select "SVN Update".

    Subversion will then attempt to merge in the latest changes from the repository into your "work" folder. Sometimes it can do this automatically, and sometimes there are problems.

    If there are problems, for example, if more than one of you have made changes to the same file, you may have to manually resolve the conflict. Refer to the TortoiseSVN and Subversion documentation for more information.

    Adding New Files

    To add a new file:

    • Inside your "work" folder, place the new file in the appropriate place.
    • Right click the file, and select "TortoiseSVN" / "Add...".
    • Click "Ok", wait, then click "Ok".
    • You may notice a blue "+" on the file if icons are working (not on a network drive or in CATS). This indicates that TortoiseSVN (and Subversion) now knows that the file needs to be added to your project.

    To send the new file to the repository so that other group members can check it out, you need to commit your changes. This is detailed previously.

    Further Resources

    The above information is a fairly basic outline designed to get you started quickly. Subversion is a powerful tool and there is much to learn about it. For further information, you should refer to the following resources:

    • The TortoiseSVN help pages. You can view the help pages from the Start Menu at: "Programs" / "TortoiseSVN" / "Help"
    • The TortoiseSVN web pages
    • The Subversion web pages

    For further assistance, please contact

School of Mechanical Engineering

Engineering South, L1


T: +61 8 8313 5460
F: +61 8 8313 4367