First Delivery of Airbus A380

 

Airbus delivered its first Airbus A380 on 15th of October 2007. If anyone of you who is interested have missed the occasion you can have a look at the event by visiting the following web site.

http://www.a380delivery.com/

You can watch many other multimedia content highlighting the development and launch of A380 in the same web site.

Enjoy !!!

Microsoft Flight Simulator X

I got Flight Simulator X (FSX), which is the latest version of Microsoft Flight Simulator line of products. It seems to be really high in detail, also they have improved the liveliness of the artificial world. This version has moving traffic on roads, moving ships in the sea, people are there, birds are flying, push back vehicles are there. Also they have improved the virtual cockpit a lot. Only problem is, to support all these you need a good machine with high powered processor and a good graphics card.

My earlier graphics card doesn't seems to be much comfortable with FSX, so had to buy a new graphics card as well.

But it seems to me FSX is a really good game to go for if you are a flight enthusiastic like me.

Also I am planning to start again creating some fun stuff for FSX as I did some years back for FS2004.

Visit the official web site and find out more.

http://www.microsoft.com/games/flightsimulatorx/

There is also a trial version available from Microsoft at the following location.

http://www.microsoft.com/games/flightsimulatorx/downloads.html

Microsoft HealthVault

Microsoft HealthVault is an online service which you can use to collect, store, and share the health information critical to your family's well-being.

Above all this service is provided free by Microsoft.

Try it out by paying a visit to Microsoft.
http://search.healthvault.com/hvindex.htm?rmproc=true

Executing .NET Applications Located on a Remote Location

Have you tried executing an application which is on a remote machine from yours. Think it like this, you have an application written in .NET (any version) and two users are there who are willing to use the application using there machines. (Please note that in this secnario all the machines are in the same network.)

The normal process is to setup your application on both machines and tell them to use. But the problem is that you are not yet finished development so constatly there will be updates to the application. So if you install in two machines, all the time you change the application you have to install the new version in both machines. (This is ok as you think because it is only two machines, but think is there are 50 users using in 50 machines.)

In this kind of a scenario, installing the application in one machine and sharing it and making the other user access the same installation can ease your life. Isn't it?

If you just try running the application from the remote location, application might not work correctly. This is because you have to set a code group for the remote application in the local machine. Then only the local .NET classes will be accessible without problem to the remote application. To configure the things follow the points.

1. Install your required application in one machine and share the application folder if possible. (It doesn't really matter whether it is shared or not. What matters is the accessibility to the folder.) Run the application from the installed machine first to make sure the application is working properly in the local environment.

2. Install the required .NET framework on all the client (user) machines. (In my scenario above, in both uiser machines.) This is because the application is actually ran on the users machine even though it is located on a remote machine.

3. Browse to the application installation folder from a client (user) machine.
Get the 'Run' window by clicking on Start -> Run. Type the machine name or IP address of the machine where your application is installed (Note that my application resides in the machine having the IP 192.168.1.165 in my LAN).If the login criteria is asked, enter them and login. It is ok even if you use the 'Guest' account to log into the system if you have access to the shared application by the guest.
4. Open the .NET Configuration window by clicking on Start -> Control Panel -> Administrative Tools -> Microsoft .NET Framework x.x Configuration.

5. Expand the 'Runtime Security Policy' node from the left hand pane. Then expand the 'Enterprise' node and finally 'Code Groups' node. Then right click on 'All_Code' and click on New....

6. Specify a Name and Description for the code group and click Next.

7. Choose the condition type of the code group as 'URL'. In the underneath URL text box type the path to the remote application folder and put a backslash and an asterisk . In my case I typed file://192.168.1.165/Bin/* (The asterisk is used to include all the items under the folder Bin into the code group that we are creating). Then press Next.

8. From the list of existing permission sets select 'LocalIntranet' and click Next. Then click Finish in the next screen to finish and setup the new code group.

9. Now the code group is created for our remote application. But to make the application really run you have to change one property in the Code Group Properties. Continue by right clicking on the new code group that we created named 'My Code Group' and selecting 'Properties'. 10. In the code group properties, check the 'Policy levels below this level will not be evaluated' check box and press 'Ok' to apply the setting.

11. Close the open .NET Configuration windows and launch the application from the share.

If any specific functionality or if the entire application is not working please contact me, I might be able to help you out of the problem.

Installing Office 2007 on Windows

Hi all,
This is my second post on installing Office 2007. The reasons behind this post are that I have seen that installing Office 2007 is a problem not only in Vista but also in all other operating systems and also to mention you a tried and tested way (by me :-)) to install Office 2007 in one shot.

As my hint above you can use this method to install Office 2007 in any operating system.
Before starting the setup I recommend you ti update windows by running Windows Update.

1. Run a Disk Cleanup on the partition that you are going to install Office by getting the drive properties by right clicking on the drive and clicking Properties.

2. Create a folder named 'Office' in one of the drives in your hard disk and copy the full contents of Office setup CD/DVD in to this folder.

3. Start the installation by double clicking on the Setup.exe.

4. Select the customized option of the setup and right click on the top node and select 'Install on first use'. This will make all the items install when you try to use them.5. Now continue with the installation.

6. If there are any problems the setup will bring up a window and tell you to browse for files that it is unable to find or sees as corrupt. If this happens to you,

i. Try pointing to the 'Office' directory that you created in the point number 2 and press Ok.

If the window again comes up then,

ii. Copy the entire folder which setup reports as having problems from the CD/DVD to the 'Office' directory again. (For example if the setup saying it is unable to process ExcelLR.cab, copy all the folders having the name Excel to the 'Office' directory again from the CD/DVD.)

iii. Point the setup again to the 'Office' directory. This time the setup will continue.

7. When the setup finishes, start one or two applications (Word, Excel, ...) and make the installer install the necessary files. If at this point it asks for any missing files, follow the same procedure as at point number 6.

8. After you have successfully opened at least two applications of Microsoft Office family of products, start the Office installer again from the 'Add or Remove Programs' section in Windows Control Panel. Select 'Add or Remove Features' and click Continue. Then choose the applications you want to run and proceed with the setup. (If the setup is asking for any missing files follow the same procedure as at point number 6.)

9. When the setup finishes successfully, you can carry out a Repair on Office by starting Office setup again from 'Add or Remove Programs' to fix any missing files.

Breakpoints are Not Working in Visual Studio - .NET Compact Framework (.NET CF)

Recently I had the issue while debugging a smart device application. All my breakpoints stop functioning. But if I ran the application in the device emulator the breakpoints are working fine.
So it was occurring only when I debug in an actual device (In my case Pocket PC).

After some trying I found that the problem is in the .NET CF which was installed in the Pocket PC.
To fix the thing,
1. Stop all the applications running in the Pocket PC (Do a soft restart or use the Runnning Programs tab in the System -> Memory).
2. Un install the .NET CF from the Pocket PC and soft reset the Pocket PC again.
3. Install the .NET CF in to the Pocket PC. (Also note that you can make the Visual Studio install the .NET CF by starting an application from Visual Studio.)
4. Connect the Pocket PC to the computer using Active Sync and try debugging. In most cases now the breakpoints should work.

If this did not fix the issue you will have to cold reset the Pocket PC and also I would instruct you to reinstall the SDKs (Windows Mobile 5/6 Pocket PC SDKs) if you have any installed.

Airbus A300
Airbus has delivered its last A300 to FedEx on 12th July 2007. This marks the closure of Airbus’ first production line and brings to a close a very special chapter of the company’s history.

To read more details and watch the first A300 being made pay a visit to Airbus.
http://www.airbus.com/en/corporate/people/company_evolution/a300/index.html
http://www.airbus.com/store/mm_repository/videos/att00010264/media_object_image_teaserA300_Airbus.swf

Accessing Windows XP Machines

Have you noted that when you try to access a Windows XP machine, in the Connect To window (Login screen) the User name field is disabled?

Earlier versions of Windows did not had this disabled so we were able to logon as any valid user by typing the account name and the password. But in Wondows XP this was disabled by a security policy.

This policy will also restrict the machine's ability of sharing files, per user sharing will not be possible.

Want to change it? Ok proceed by openning the Local Security Policy Settings window through Start -> Control Panel -> Administrative Tools -> Local Security Policy.
Now go to Network Access section and find out Net access : Sharing and security model for local accounts.
Then open the properties page of that by double clicking or right clicking and clicking on properties.

Did you note that the default is, Guest only - local users authenticate as Guest change this to Classic - local users authenticate as themselves.
Then press Ok to apply the setting and close all the opened windows.

Now from some other machine try to access your machine. See the difference. Now you can type any user name and the appropriate password and log in.

Also if you now go to folder properties you will see that the Sharing tab is having different content than earlier and also you will see a new tab named Security. You can use these tabs to set per user security and access rights.

For people who would like to know more, following is the explanation for the setting Net access : Sharing and security model for local accounts given by Microsoft.

---

Network access: Sharing and security model for local accounts
This security setting determines how network logons using local accounts are authenticated. If this setting is set to Classic, network logons that use local account credentials authenticate by using those credentials. If this setting is set to Guest only, network logons that use local accounts are automatically mapped to the Guest account.

The Classic model allows fine control over access to resources. By using the Classic model, you can grant different types of access to different users for the same resource. By using the Guest only model, you can have all users treated equally. All users authenticate as Guest, and they all receive the same level of access to a given resource, which can be either Read Only or Modify.

There are two models available:

• Classic: Local users authenticate as themselves.
• Guest only: Local users authenticate as Guest.

Default:Guest only on Windows XP Professional. Classic on the Windows Server 2003 family and Windows XP Professional computers joined to a domain.

Important:With the Guest only model, any user who can access your computer over the network (including anonymous Internet users) can access your shared resources. You must use the Internet Connection Firewall (ICF) or other similar device to protect your computer from unauthorized access. Similarly, with the Classic model, local accounts must be password protected; otherwise, those user accounts can be used by anyone to access shared system resources.
This setting only affects computers running Windows XP Professional which are not joined to a domain.This policy will have no impact on computers running Windows 2000.

Notes:This setting does not affect interactive logons that are performed remotely by using such services as Telnet or Terminal Services.When the computer is not joined to a domain, this setting also modifies the Sharing and Security tabs in the Windows Explorer to correspond to the sharing and security model that is being used.

The Car of the Future - M 200G

Have you seen the car of the future? Even though people call this a car this is more towards a personal helicopter. The M 200G is manufactured by Moller International located in Davis, California, USA. This is capable of vertical take-off and landing.

Read more at BBC.
http://news.bbc.co.uk/1/hi/business/6970031.stm

In the future there won't be necessary to us to wait in long traffic ques. But what will happen if all the people buys this car?

I think it will increase the Air Traffic :-).

Windows Vista Service Pack 1

Microsoft is going to release Service Pack 1 (SP1) for Windows Vista. It will have the updates that Microsoft had released up to now and also some reliability and performance improvements addressing the issues they have found.

The beta version is planned to be available in few weeks time from today (2007-September-09).

Importing Yahoo contacts to Outlook

This was actually a doubt that I had in my mind after I had accidently deleted my contact list by synchronizing in wrong way. This is possible and the method is as follows.

1. Open your Yahoo Mail and click on the Options -> Mail Options on the top right corner of the page.2. Select Contacts Options from the left pane.

3. Click on Import/Export under Management column.
4. Go down to Export section and press on the button named Export Now which is infront of Microsoft Outlook and save the file to your hard disk when it prompts.
5. Open Outlook and click on File -> Import and Export..., then select Import from another program or file option and click next.
6. Select Comma Separated Values (Windows) from the list and click next.
7. Browse for the file that you saved in Step 4 then select what to do if it finds duplicate items and click next.

8. Select the Contacts item from the list and click next.

9. If you want to map the contact fields manually you can do so by clicking on Map Custom Fields..., most of the time this is not required.

10. To do the import click Finish.

WOW you have successfully imported Yahoo contacts to Outlook.

Changing Manufacturer Icon in System Properties

Changing Manufacturer Icon in System Properties
Recently a friend of mine did ask me how to change the manufacturer icon and supported by text in System Properties. Even though, I have changed the Boot Screens and Welcome screen languages when I was at my earlier employer I forgot how to achieve this. :-)

Then after some trying I found the way and thought it is better to blog it.

1. You have to create an icon to be shown as the manufacturer logo. Also remember that even though how large your image, System Properties will only show 180x114 pixels.

• The point is that the image you create should be 180x114 pixels to be shown as a whole.
• The image name should be OEMLogo.bmp.

2. Create an ini file to hold the Manufacturer, Model and Support Information.
Open notepad and create a file in the following structure.

[General]
Manufacturer= Arjuna
Model= My Model

[Support Information]
line1= Tele xxx - xxxxxx
line2= Fax ### - ######
line3= EMail ME@MyCompany.Com
line4= What ever you want

When saving you have to save this file as OEMInfo.ini.

3. Ok, since now files are ready, you have to copy them to system32 folder inside windows installation folder. The default location would be C:\WINDOWS\system32.

Job well done !, now if you go on to System Properties you will see the image that you have just created with the information that you have just saved in the notepad.