Question about a program I want to develop in C++

[konac]

Dear all,
I want to develop a piece of software in C++ and I can use a little help.
The program has the following requirements :

The software should be able to run in all Windows versions.

When first running the setup, the software must ask me to enter an x number of days.
When windows starts up, it must run in background (as a service), meaning it may not be visible for users nor tracable.

Every time windows starts up, the program should check if the number of days initially configured has not already passed.
If not, nothing should happen.

If the time has expired, the program should ask for a password.. As long as the password is entered incorrectly, Windows access should be blocked (by means of a password popup loop or maybe better, a restart of windows every couple of time the password is entered incorrectly)


If the password is entered correctly, nothing should happen , the program keeps running in the background or uninstalls itself)

It must be relatively secure, meaning a user should not be able to stop running the program..(with the windows taskmanager for example)

My questions are now :

Is this easy to implement using C++ ?
Do you have some tips to share ?

I am basically a web developer, but I have some experience in C++ (unfortunately the borland version) and this is a good opportunity to finally learn Visual C++.. (I used it very long time ago)

Many thanks in advance for your answers !!

konac

 

[palbano]

First you can only do that if the Windows OS’s let you, meaning that there must be some API that provides support for your requirements. If there is such support you will not find it a simple task since the support will undoubtedly vary across the different OS’s

-pete

 

[konac]

Thank you for your reply, pete !

Regarding the API-support issues, let's suppose the program should run in WIN 95/98 (this is easily feasible I think)and possibly in XP..

 

[PerFnurt]

>WIN 95/98 (this is easily feasible I think)

In the contrary, since these have to secure securety functionality provided by the OS.

As for the idea of blocking the entrire OS when a particular application has expired - well, that doesn't really conform to the well-behaving windows application paradigm.

When dealing with login etc, this is should be handled by the OS itself as it is in NT/2000/XP.



/Per
_{Nerdy signatures are as lame as the inconsistent stardates of STTNG.}