• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.

Archived

This topic is now archived and is closed to further replies.

T2k

How to make my app unremovable from taskmanager in Win2k/NT

36 posts in this topic

i have an app that starts doing stuff by logoff at win2k/nt systems, and i want to secure my app, so the user cannot end the process etc... ive already searched the web, but all ive found was a solution for win98/95... and i dont want it to be a service (it wouldnt be able to interact with the user, and would not recognice the logoff message) thanks for any help... T2k
0

Share this post


Link to post
Share on other sites
Why are you so opposed to people killing your app? Are you doing something the user isn''t supposed to know about? One of the very annoying things are installation programs (for Symantec software, for example) that in the end present you with the messagebox that asks you to reboot your computer and have only one button: "OK". Task manager is a useful tool in case you want to kill software that is written by developers who think their way is the only correct one.

In case you don''t know: even though taskman can''t kill certain processes, it doesn''t mean that they are "unkillable". It takes only a couple more lines of code to kill any running process (provided you have necessary privileges, of course!). So I doubt that general solution exists that can prevent your program from getting killed. I suppoer you, however, can write a task manager extension that will detect your program and prevent the user from killing it, but this will work only for the taskman.
0

Share this post


Link to post
Share on other sites
maybe iam a bit unclear: my app is in no way destructive!!!, and i dont want to disable the taskmanager! So i have to secure my app, for MY COMPUTER, from other people killing it (iam not interessted to prevent coded apps doing it)


T2k
0

Share this post


Link to post
Share on other sites
By the way, I agree with the other two posters, you shouldn''t make it impossible to kill your app...

However, I don''t think anyone''s going to convince you, so here''s one way: You could have two copies of your program running, one which does basically nothing and the other which does the actual work. If one of them is killed, the other can detect that and re-start it (just have a thread waiting on a handle to the other process).

You could still get around it by killing both simultaneously, however you can''t kill two processes simultaneously from the task manager.


codeka.com - Just click it.
0

Share this post


Link to post
Share on other sites
Make your app a service. You can''t stop a service from the task manager, but you can go to the services plugin and stop it there.
0

Share this post


Link to post
Share on other sites
kill.exe(from the resource kit)or taskkill.exe(supplied with XP) should be able to kill it no matter what you do.

0

Share this post


Link to post
Share on other sites
quote:
Original post by Arild Fines
kill.exe(from the resource kit)or taskkill.exe(supplied with XP) should be able to kill it no matter what you do.



Provided the process is running under your user context, or, if it''s not, you have the Debug Any Process privilege, that is correct.
0

Share this post


Link to post
Share on other sites
I have the impression that Windows sometimes has the characteristics of "not wanting to be turned off".
Unfortunately Mic*oft doesn''t publish any source code. :D
(btw. this is not a Windows-offensive-post)

===========================
UNKNOWN caused an invalid page fault in module unknown at 0000:bff80eb6
: win98 with multiple sclerose
0

Share this post


Link to post
Share on other sites
You will always be able to stop a process. However here''s a little hack.

2 processes monitoring each other. If one exits, the other one launches it again. Get it?

The user will be able to stop your process but it will get created again faster then the user could stop the other process.
0

Share this post


Link to post
Share on other sites
quote:
Original post by LordShade
You will always be able to stop a process. However here''s a little hack.

2 processes monitoring each other. If one exits, the other one launches it again. Get it?

The user will be able to stop your process but it will get created again faster then the user could stop the other process.


So I just suspend one process and kill them in turn.
0

Share this post


Link to post
Share on other sites
quote:
Original post by DrPizza
So I just suspend one process and kill them in turn.



Like I said in my post, it''s still possible to kill it, but not for the average user...

Still, I think it''s a bad idea to make a progam "unkillable", since you''re taking too much control away from the end-user. If they don''t want your program running, who are you to say they''re wrong?


codeka.com - Just click it.
0

Share this post


Link to post
Share on other sites
check for WM_QUIT and WM_DESTROY.

then CreateProcess and run your program again.

windows will kill the last instance but not the new one.

Its my duty, to please that booty ! - John Shaft
0

Share this post


Link to post
Share on other sites
Why can I not close down the process of Fortres running at my school then? What are they doing special?
0

Share this post


Link to post
Share on other sites
why would the app need to be unkillable? password protection of some sort?

anywho, make it fullscreen, always on top, and disable ctrl-alt-del/alt-tab via telling windows a screen saver is active. works for ALL windows systems. only way to kill the app is through a hard reboot or through the app itself.
0

Share this post


Link to post
Share on other sites
quote:
Original post by a person
anywho, make it fullscreen, always on top, and disable ctrl-alt-del/alt-tab via telling windows a screen saver is active. works for ALL windows systems.


Except for NT ones, where you can''t disable ctrl-alt-del.
0

Share this post


Link to post
Share on other sites
Oh, I must have been mistaken. I thought this was a programming forum, not a ''how can I bypass my school''s security software'' forum.
0

Share this post


Link to post
Share on other sites
quote:
why would the app need to be unkillable? password protection of some sort?


because it has to check if files are in a specified folder, if yes, let the user move them to other places, else quit, that works already, but at the moment the user can also kill the process (... maybe by mistake) and then the folder get filled up with files, and nobody would now if they are needed or not ...

quote:
check for WM_QUIT and WM_DESTROY.

then CreateProcess and run your program again.

windows will kill the last instance but not the new one.

yes, but what if you kill a process-tree ?

quote:
Still, I think it's a bad idea to make a progam "unkillable", since you're taking too much control away from the end-user. If they don't want your program running, who are you to say they're wrong?

iam the person who owns the computer on which the programm runs :D

to the others who dont read carefully:
and ive already said that i cannot use a service, because it dont notifies the WM_QUERYENDSESSION Message (processes run till shutdown, i need it at the logoff point) and i cannot interact with the user via dialogs etc. (ive already tried it out with CodeGurus NT'Service Wizard)


T2k


[edited by - T2k on May 29, 2002 3:53:49 AM]
0

Share this post


Link to post
Share on other sites
Maybe you should just tell us what your app actually does, so then people don''t think you''re doing something evil.

The only reason I can think for anyone wanting to do this, is if they wanted to write a program to steal other people''s passwords. I''m not too keen to help anyone do this.

Heck, I even had someone asking me to help him write a cheat for Counter-Strike. As if we don''t have enough jerks on the internet already.


Helpful links:
How To Ask Questions The Smart Way | Google can help with your question | Search MSDN for help with standard C or Windows functions
0

Share this post


Link to post
Share on other sites
quote:

because it has to check if files are in a specified folder, if yes, let the user move them to other places, else quit, that works already, but at the moment the user can also kill the process (... maybe by mistake) and then the folder get filled up with files, and nobody would now if they are needed or not ...



i really dont know why some people simple dont read previous posts !


Stealing password by logoff (like "please enter your password to logoff")? please explain this ...


T2k

[edited by - T2k on May 29, 2002 8:05:53 AM]
0

Share this post


Link to post
Share on other sites
quote:
Original post by T2k
Stealing password by logoff (like "please enter your password to logoff")? please explain this ...



What usually happens is the program detects you logging off and then starts it''s own full-screen app which looks just like the regular "log in" screen, the next user comes along, types his password and your program records it.

Under NT, it''s possible to make sure this can''t happen by requiring the user press ctrl-alt-del before logging in, this combination is hard-wired to the login screen so an app can''t intercept it at all.

Remember also that non-administrators can''t kill apps which belong to other users, so another way is to make your app run under a special account. I hope you don''t normally let your users run with adminitstrator privileges...


codeka.com - Just click it.
0

Share this post


Link to post
Share on other sites
Windows sends proper kill messages to apps before killing them directly. So check fore those, launmch another copy and close like normal .
0

Share this post


Link to post
Share on other sites
Did anybody at all read the fact that this guy isn''t making this program for other users? He said on HIS computer. He didn''t want people to kill it on his computer.
0

Share this post


Link to post
Share on other sites
He could be lying. People do that, ya know.

Note for budding flame warriors - I''m not saying he IS lying, but rather that if he were up to no good, he might want to conceal what he''s actually trying to code.


Helpful links:
How To Ask Questions The Smart Way | Google can help with your question | Search MSDN for help with standard C or Windows functions
0

Share this post


Link to post
Share on other sites
Lol, maybe he''s trying to catch his Wife or Kids surfing for porn... =) hahaha
0

Share this post


Link to post
Share on other sites