<< C and C++ Compilers

 

FreeOTFE Windows GUI 2 >>


 

STEP-BY-STEP ON BUILDING THE FreeOTFE GUI

USING BORLAND DELPHI FOR WIN 32 Part 1

 

BASIC MACHINE SPECIFICATION USED FOR THIS SCENARIO:

 

1.      OS:                        Windows XP Pro with Service Pack 2.

2.      Hardware:              Intel Duo Core 2.

3.      Memory:                2 GB DDR2.

4.      Compiler:               Borland Developer Studio 2006 (3 CDs) full version.

5.      We created a folder on our Win XP desktop and then download the SDeanComponents (v2.60.00) from SDeanComponents26000.zip and

      unzip it, check the hash for the integrity.

6.      Next we download FreeOTFE from download page and unzip it in the same folder, check the hash for the integrity.

7.      Our task is to build and run the FreeOTFE GUI just for FUN!

8.      If you are totally new, you may want to explore step-by-step how to install Borland Developer Studio 2006 (Get the trial and free version,

      currently the 2007 version already available – CodeGear RAD Studio 2007).

 


 

Firstly we just read and follow the instructions contain in the Build Notes doc (we recap here):

 

This is a description for Delphi newbies of the basic steps involved in compiling the FreeOTFE GUI.

To build the GUI, the following software is required:

 

 

The binary release of this software was built with Delphi v7, but you should well be able to use any version later than this.

 

  1. With each of the packages in the SDeanComponents archive,

§         Build each package

§         Install each package

§         Ensure that the correct path to each package is added to your Delphi environment ("Tools | Environment Options...", "Library" tab)

  1. Open the FreeOTFE project ("FreeOTFE.dpr")
  2. Build the application.
  3. You should now find a file called "FreeOTFE.exe" in the directory above the "src" directory

You have now successfully built the GUI frontend!

 

If required, the compiler definition "FREEOTFE_TIME_CDB_DUMP" may be set, in which case the time takes to dump a CDB ("Tools | Critical data block | Dump to human readable file...") will be shown after the dump completes.

 


 

Let Begin:

 

We use Delphi for Microsoft Win32 (It will generate the exe file for each package. If using the .NET version, the whole project will be converted to the .NET version and each package will be in .dll and do expect more warnings and errors! So let be safe by using compiler that ‘close’ to the original compiler used)

 

Launching Delphi for Microsoft Win32 application

 

Figure 1: Launching Delphi for Microsoft Win32 application

 

Delphi for Microsoft Win32 IDE

 

Figure 2: Delphi for Microsoft Win32 IDE

 

Next we open the SDeanComponents project.

 

Opening the SDeanComponents project file

 

Figure 3: Opening the SDeanComponents project file

 

Selecting the SDeanComponents project file

 

Figure 4: Selecting the SDeanComponents project file

 

The SDeanComponents project file and all components loaded in the Borland Developer Studio 2006

 

Figure 5: The SDeanComponents project file and all components loaded in the Borland Developer Studio 2006

 

Following the steps from the Build Notes, we build every package one by one. Keep in mind that you will encounter many warnings because our project environment settings are based on the default set. However, in this purpose we just want to see the working GUI, so warnings can be ignored at this stage.

If there are error(s) we need to correct them first else we could not run the program. The following is the build and install steps. You can select Install (Select a package and right click and select the Install menu) menu for each package directly because Install step contains Build step. That mean when you choose the Install menu, it will Build first and then Install (register the components/packages to the Delphi project environment that we will see later). We found a lot of warning but without a single error. That is a good sign that we can test the GUI using the demo main program.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

---------------------------------------------

Invoking the Build menu to build component

 

Figure 6: Invoking the Build menu to build component

 

The following are warnings examples generated when we Build a package. It seems that some package built without any warning and error. Default Delphi project setting will terminate the Build process if there are error(s). Just proceed to the Build and Install each package, ignoring those warnings.

 

Component building warning messages seen through Messages window

 

Figure 7: Component building warning messages seen through Messages window

 

The following figure shows the Install step of each package. There will be message dialog box displayed for each successful or failed Installed package as shown below.

 

Failed to install the component or package message box

 

Figure 8: Failed to install the component or package message box

 

Successfully install the component or package message box

 

Figure 9: Successfully install the component or package message box

 

 We successfully Build and Install each package without a single error but with a lot of warnings :-).

 

Invoking the Install menu to install the package or component

 

Figure 10: Invoking the Install menu to install the package or component

 

Next, let check whether our packages/components have been installed properly by choosing Project Options… menu.

 

Opening the project’s options page by invoking the Options… menu

 

Figure 11: Opening the project’s options page by invoking the Options… menu

 

Select the Packages folder and scroll down. You can see that those built and installed packages have been registered. Others are default packages that registered by default when we choose Delphi Win32 project.

 

Project options page for FreeOTFE

 

Figure 12: Project options page for FreeOTFE

 

Finally save all the project components.

 

 

 

 

 

 

 

 

 

 

 

 

 

Saving all the project components, files etc

 

Figure 13: Saving all the project components, files etc.

 

Before we build the sdDemo main program, optionally we can check the syntax by using the following menu. Any error(s) will be detected at in this step.

 

Checking all the sdDemo project syntax

 

Figure 14: Checking all the sdDemo project syntax

 

Next we build the demo program by choosing the following menu. This demo program will display the main GUI of the FreeOTFE.

 

Building the sdDemo program

 

Figure 15: Building the sdDemo program

 

Fortunately we only have one warning and one hint. The deprecated symbol need to be replaced with new symbol version that normally available in new edition of the Borland Delphi. So if we need to correct this, we need to read Borland Developer Studio 2006 manual/help file. However in this case, just forget it; we are not building this program for Release version! However if there are error(s) we need to correct it first else we can’t run the program.

 

A warning and hint seen in the Messages windows

 

Figure 16: A warning and hint seen in the Messages windows

 

Provided that there is no single error in the previous step, we are ready to run the main program (with all the related and needed packages/components have been registered). So, select Run Run Without Debugging menu shown below.

 

Running the program without debugging

 

Figure 17: Running the program without debugging

 

 

 

 

Well, the following error message dialog box displayed. It is normal because we just running the GUI, the driver is not installed (this is the next stage after successfully build the GUI, using Microsoft Visual C++ compiler). Just click the OK button.

 

Error message dialog box stating that the ScramDisk device driver is not loaded

 

Figure 18: Error message dialog box stating that the ScramDisk device driver is not loaded

 

VIOLAAAAAAAAAAAAAAA!!!

 

The TkrScramDisk GUI demo in action

 

Figure 19: The TkrScramDisk GUI demo in action

 

Exploring the TkrScramDisk GUI demo application

 

Figure 20: Exploring the TkrScramDisk GUI demo application

 

Save All and Close All the previous project.

 

Closing all the project

 

Figure 21: Closing all the project

 

 

 

 

 


<< C and C++ Compilers

C and C++ Resources

FreeOTFE Windows GUI 2 >>

 

FreeOTFE Windows GUI 1 | FreeOTFE Windows GUI 2 | Single Page pdf