I am looking at CrashRpt, I used that piece of software a while ago, (when they were on Codeproject) and I was quite happy with it.
Because it is open source and written it C++, it makes it very easy to incorporate in Courseplanner.

I am also looking at other kinds of Crash handling software, especially Google and Firefox, not because I think they are better, but simply because I would be foolish to ignore such big names.

One of the most attractive option they have is the possibility to send the report directly to the website, in the past users were reluctant to send an email, or, in worse cases the emails would be trapped in some spam filter.

I also created a privacy policy page, it basically says that I have no plans to pass any information to any third party. Currently the policy is limited to the crash report, but at some stage I will have to update it to include registration and the forum.

I am planning on releasing it to the beta team later today, (my ftp server is down for some reason).

But be warned a lot of issues have been reported, Wine does not work 100% all the time.
So, before I venture down the road of installing Courseplanner on my ubuntu machine I need to venture down the road of installing Wine.

Start the terminal server (Applications > Accessories > Terminal).
At the command prompt, type

sudo apt-get install wine
[sudo] password for username:

Enter your password, and then wait for the relevant packages to be downloaded, (only 19Mb but for me it took a bit of time for some reason).

When this is done… there is nothing else to do, you can type…

wine –version

To get the version number, but to be fair, this won’t help you much

Next I need to install Coursplanner…

First things first, download the latest source code of the plugin and we will talk about each files in a bit more details.

The file type:
The file is nothing more than a DLL with an ‘.amp’ extension. So when you create your plugin make sure that the output file has a ‘.amp’ extension.

The files to include:
You need to include 2 files, a header(h) file and a library(.lib) file.

// support for PluginAPI
#include "../../api/amplugin/amplugin.h"

// add the libs
#ifdef _DEBUG
#pragma comment(lib, "../../debug/amplugin.lib" )
#else
#pragma comment(lib, "../../release/amplugin.lib" )
#endif

And in the cpp file, the one and only function.

PLUGIN_API
AM_RESPONSE am_Msg( AM_MSG msg, WPARAM wParam, LPARAM lParam  )
{
  return AM_RESP_NOT_SUPPORTED;
}

Some important messages…

...
  switch( msg )
  {
  case AM_MSG_INIT:   // called when the plugin is first loaded.
  case AM_MSG_DEINIT: // called when we are closing the app
  case AM_MSG_MAIN:   // called when one, (or more), of the commands we 
                      // registered are called.
  }

When the message ‘AM_MSG_INIT’ is called you can add an action using the ‘addAction( … )‘ function.

AM_MSG_MAIN will be called when that action is entered.

Things to note:

• Place your plugin in the __in folder, (normally found in %appdata%\MyOddWeb\ActionMonitor_d\RootCommands\__in).
• Don’t mix debug and release builds, to debug your plugin you will need to run it again the debug version of Action monitor, (and the folder is %appdata%\MyOddWeb\ActionMonitor_d\RootCommands\__in).
• Have a look at the file “#include “am_plugins.h”“, it explains what most messages do.
• Call [Caps lock] this.reload to reload everything.
• Download the plugin code here.

Visit the forum if you have any technical questions.

So a while ago, (a year ago I think), I created a small tool that simply takes your keyboard input and runs a pre-programmed script accordingly, it can be anything, from launching calculator to login into your favourite website using another browser that your favourite one.

You can write your scripts in LUA, C++, Python, or even DOS (batch).

Note, by default the tool does not write scripts for you, it comes with a few basic scripts but nothing too exiting. So please use the forums if you have any scripting questions.

This is probably because Ubuntu assumes you made a mistake. Whatever the reason you need to update the menu.lst file.

First of all lets make sure that you read all the previous articles so we are all talking about the same thing.

1. Install Ubuntu 9 on Virtual PC 2007.
2. Update the menu.lst after install.
3. Update the menu.lst again after updating the kernel.

From time to time Ubuntu will update various software, (or you can do it your self,  System > Administration > Update Manager. Any one of those update might be a brand new kernel update, in that case you will need to edit the menu all over again.

1. Open the terminal , (‘Applications>Accessories>Terminal’)
2. At the cursor type ‘gksudo gedit /boot/grub/menu.lst‘, (without the quotes), press enter.
3. Enter your password if you have to.
4. Look for the first boot option

   ## ## End Default Options ##
   title ...
   uuid ...
   kernel ...

5. look for the entry that mentions ‘Kernel’.
6. Add ‘noreplace-paravirt‘ at the end of it.
7. Save the file
8. Close the editor.
9. Tell Ubuntu that you changed the file:

   sudo update-grub

10. Reboot and everything should be back to normal … until you update again.

NB: If you cannot boot at all, (because your screen is black or throwing some errors), simply follow the same instructions in the first article on booting up Ubuntu.

NB2: If you still have a question, feel free to go to the forum and I’ll try to help as much as I can.

Courseplanner tracking a waypoint

I finally managed to get back to flying a little over the week-end, I am working on some new features for Courseplanner, namely the ability to turn into a waypoint, (or past a waypoint depending on the one you want to visit).

All the coding is done, I am just testing with various aircraft if everything works as expected. With all the small aircraft, (Cessna, Mooney and so on), it works well, but it is another story for the heavies. It is just very hard to remain on course without having some wild turns in order to remain on course.

I also added some small features to see where the automatic flight management of Courseplanner is aiming.

But all in all it is fun to get back to flying again.

So you need to edit the ‘boot’ file once and for all so that from now on it boots into the right screen.

You need to do 2 things, first you need to edit the boot, one more time to get into Ubuntu and then you will need to update the boot file so that you no longer have to do this again.

So, reboot Ubuntu, when you see something like ‘grub loading…‘, press esc and you will see a menu.

Select the first line, it will say something along the lines of ‘Ubuntu 9.0.4, Kernel …’. The other lines should say almost the same with extra words like, ‘Recovery mode‘ and ‘memtest86+‘ don’t choose those.
Press ‘e’ to edit the boot commands.

Select the line that says something like “Kernel …“, (normally the first one, but sometimes the second line).
Press ‘e’ again, (to edit that line).
At the end of that line simply add

noreplace-paravirt vga=771

or

noreplace-paravirt vga=791

Press ‘enter‘.
Press ‘b’ to start the boot sequence.

Now you are back in business, Ununtu is up and running again.
The last thing you need to do is make sure the changes you just did are saved so you don’t have to do the same thing over and over.

So, once Ubuntu is up and running select the menu option, ‘Applications>Accessories>Terminal’ and you should get a white window with a blinking cursor.
Next to that cursor type the following, ‘gksudo gedit /boot/grub/menu.lst‘, press enter, give your password.

## ## End Default Options ##
title ...
uuid ...
kernel ...

At the end of the line that says ‘Kernel‘ add ‘noreplace-paravirt‘, (without the quotes of course).
Save the file.
Close the editor

Back at the command prompt simply update the grub, (in other words tell Ubuntu that you changed the file).

sudo update-grub

And that’s all, you can now reboot into your Virtual PC Ubuntu and all should be fine.

Note: If like me you are lazy and you don’t want to type everything, simply copy the text, place your cursor where you want the text to go and in Virtual PC select ‘Edit>Paste‘ and it will ‘type’ everything for you.

This is what I used to install Ubuntu on my virtual server.

• Virtual PC2007 sp1, (get it here).
• Ubuntu Alternate CD, (get it here).

Create a virtual machine with enough resource, I chose 1024Mb of memory and 30Gb disk space. I think the minimum requirement is 256Mb of memory or something like that but if you can spare 1Gb of memory, use it .

Start the virtual machine and go to CD->Capture ISO image…, (you might need to reset the virtual machine afterwards if, like me, you are not quick enough).

When Ubuntu start it should pickup your ‘CD/ISO image’, you then choose your language
At this point if you try to do the install it will not work, this is because the install program does not ‘guess’ what your video mode is, (after all it is a virtual machine, so you cannot blame Ubuntu for guessing wrong).
So you need to tell it what to use.

To do that when you see the Install Ubuntu menu, (make sure that it is highlighted) . Press F6 and then press esc again to close the menu, (I know, I know there are other ways of doing it, but this way is good enough).

You will see a new line at the bottom that will say ‘Boot Options‘ at move your cursor, (with the arrows), to the end of the line. It should say something like “… quiet –“, delete that and replace it with “ noreplace-paravirt vga=791” and press enter to start the install.
The rest of the install should be fairly straight forward.

A couple of notes:

Select ‘No’ when asked to setup the keyboad, it will then ask you what country you are in and what country your keyboard comes from, otherwise Ubuntu will ask you to test your keyboad.

Be careful when choosing a username and password, remember that this is all case sensitive and the username must start lower case.

I chose not to encrypt the directory.

That’s it, enjoy Ubuntu 9.0.4.