>> Don’t get full around Access 2003 and Outlook 2003

My friend Jitu and my younger brother Yogesh told me that they have installed MS-CIT Exam Demo V. 2.0.1 on various machines having Office 2007 and Office 2003 loaded. But every time when they start exam demo and start attempting practical questions on Access 2007 and Outlook 2007, the Exam demo opens its predecessor version Access 2003 and Outlook 2003. To get kick out this problem they have uninstalled the previous version of office i.e. Office 2003 but it won’t work.

Actually the Exam Demo created by P. C. Technology Pvt. Ltd. Is a nice software created for MKCL. Programming for MS-WORD, MS-EXCEL, MS-POWERPOINT, WINDOWS is real programming and the Exam Demo opens the actual applications (MS-WORD, MS-EXCEL, MS-POWERPOINT, WINDOWS Explorer). So, for this Demo to run successfully, you need to install any version of Office like Office 2000, Office 2003 or Office 2007. And according to your installed version of Office, the Demo opens the latest installed version of Office. For example, if you have installed two versions of Office in your PC say Office 2003 and Office 2007 then Demo opens newer version of office i.e. Office 2007.

For other applications i.e. MS-Access, MS-FrontPage and MS-Outlook they have created .SWF files. The file format SWF (acronym of "Small Web Format") can be generated from within Macromedia Flash. So just follow me to check out the secret of these files.

Right click on the Exam Demo icon on the desktop.


Popup menu appears. From the popup menu, select properties. The shortcut properties dialog appears on the screen.

Now, click on the command button Find target. Another windows appears and shows the location of the application Exam Demo. In our case it is D:\Program Files\MSCIT Demo Exam. Look at the figure below.

Now double click on the folder name files. This will show the contents of the folder as below :





Observe that most of the files are having extension .SWF. Now right click on any one of these file and select Open with… option. It presents the following screen:

Now click on the select the program from list option button and the click on OK. Another dialog box appears as below :


Notice that, by default form the Recommended Program groups the option Internet Explorer is already selected. Click on OK.

Security warning appears below the address bar. Right click on it and from the popup menu select Allow Block Content… .

Selected SWF file now opens. Move your mouse on the image and try experimenting to click on the various parts on the screen. Now try right clicking the image and you know why you need flash player to run this Demo.

So, now no more installation and uninstallation. After all, Life is adjustment, adjust it.

When Turbo C/C++ takes more time to start...

Many times I have observed that Turbo C++ 3.0 ( Mostly used Turbo C++ compiler, used by almost everyone C/C++ programmer) takes time to load when you start it. Look at the screen shot below to remove all your doubts about which version I am talking about:

The message “Loading desktop…” flashes on the status bar of Turbo C++ editor. Most of the computer users think that its system maintenance time. They start their job by removing temporary files in their output directory, removing unwanted temporary files, defragmentation of volume and may be check system for virus attack. After doing all these dirty jobs when again they start Turbo C++, they realize that they have wasted their time as the problem remains as it was.
The solution of this problem is quite simple. Just log onto your Turbo C++ directory and remove the file TCDEF.DSK. Now try starting Turbo C++ and njoy.

[Note : This topic is dedicated for all ALCs of MKCL.]

Worm server is a best software ever made by MKCL. I really want to congratulate MKCL for creation of such wonderful and amazing series of software like LMS, Worm Sever/Client and Bizclient.
After creation of ALCs (Authorized Learning Center), it is mandatory to send the configuration of all PCs to MKCL server. The first step of this process is to install Worm Server on Server machine (Dual core having at least 2 GB of RAM, 160 GB of HDD etc.) and Worm Client on client machines (PIV having at least 1 GB of RAM, 160 GB of HDD etc.). During this process, I face the following error when working with Worm Server.
The error message was,
“Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click quit, the application will close immediately.
Object error not set to an instance of an object"

This error pops up specially when working with branded machine. Before installation of Worm software in Server machine we need to install some prerequisites software that are Windows installer 3.1 and Dot Net FX 2.0. After installation of these software and successfully installation of Worm Server, when I started worm server this error occurs. After that I install Service Pack 2 as a possible remedy for this error but it doesn’t works. So, I am sharing the remedy of this problem with you.
Actually this error occurs due to improper installation of device driver or if you do not install device driver for any device. To get rid of this error simply install all the drivers for your PC or disable the device having no device driver. The first method is a complete solution and it is recommended method. Second method also work but it is partial solution for this problem. So It is totally up to you which method is best suitable for you.

Good luck !

Create DVD from CDs ( for MKCL ATCs)

Hi friends,

[Note : This topic is dedicated for all ALCs of MKCL.]

Windows vista installation is very tough job even if all your systems are connected to each other through LAN. As you need separate CD drive for all PCS to install Windows Vista. Another thing is that we have set of 4 CDs and if anyone CD of this set is get corrupted then this installation became nightmare for computer user. In this topic I will guide you how you can make your Vista installation easy without having CD drive on every computer. But of course you need XP as an OS in every computer.

Best of luck !

Thats all folks !

>> Shutting the Shutdown Event Tracker

Annoying Shut down Event Tracker

I am using Windows Server 2003 OS from last 6 months. The Windows 2003 server is a new experience for me as I never work with server OS from long time (before this I have worked with Windows 2000 and explore some networking features and server capabilities of it with great fun). But in case of Windows 2003 server I feel awkward to tell you that I am using it as a desktop OS. And in Desktop Operating System restarting or shutting down a machine is a common procedure. So it is annoying for me to pop up Shut Down Event Tracker every time I shut down or restart machine.
According to Microsoft, "The Shutdown Event Tracker is a Microsoft Windows Server 2003 and Microsoft Windows XP feature that you can use to consistently track the reason for system shutdowns. You can then use this information to analyze shutdowns and to develop a more comprehensive understanding of your system environment."
In server environment shutting down or restart the system is not occurred frequently. Therefore, when it is, Administrators should keep a log of exactly why the machine was powered down. This can be a good thing since it allows you to store a database of shutdown events for future reference.
For some special people like me, especially those that use Windows 2003 as a desktop operating system where restarting or shutting down a machine can be a common procedure - it might get to be quite annoying.
When you click on Shut Down option from the from the Start menu, the Shutdown Event Tracker pops up the following dialog box:




The following seven event tracker options are available.
Ø Other (Planned)
Ø Hardware: Maintenance (Planned)
Ø Hardware: Installation (Planned)
Ø Operating System: Reconfiguration (Planned)
Ø Application: Maintenance (Planned)
Ø Application: Installation (Planned)
Ø Security issue.
You can use any options from the above according to your task and place appropriate comment to the comment text box.

Shutting the Shutdown Event Tracker

You can shut the shutdown event tracker using Group Policy Object Editor. To start the Group Policy Object Editor do the following :
Ø Click on Start > Run.
Ø Type gpedit.msc and click on OK.
Ø Select Computer Configuration > Administrative Templates > System
Ø In the right pane, select the “Display Shutdown Event Tracker” setting. Look at the following screenshot:
You can shut the shutdown event tracker using Group Policy Object Editor. To start the Group Policy Object Editor do the following :
Ø Click on Start > Run.
Ø Type gpedit.msc and click on OK.
Ø Select Computer Configuration > Administrative Templates > System
Ø In the right pane, select the “Display Shutdown Event Tracker” setting. Look at the following screenshot:

Ø Double Click this setting to open the Properties page.
Ø Click on the Disabled option button and he click on OK.
Ø Restart the machine.Now try to restart your machine and noticed that, the Shutdown event tracker will no longer be visible.

Hurrey … You did it buddy !