Printable View
XP is starting to piss me off :P
Man,
I just installed xp, loaded up visual basic... loaded up a vb project which I have been working on... Run it. Wham bam thank you mr mircosoft man... They got rid of the lil API that makes a program a service :/
Anyone know of a workaround?
i had the same problem, couldn't be arsed with all the alterations. i just pissed it off and went back to Me, XP is crap simply!!!
I don't think i'll get it now :eek:
I had XP and now I am back to Me. :\ But Xp is nice ... Me blueScreen piss me off!
Well I'm going to keep it on cause I know I'm going to have to program for this stupid os... :/
anything that might cause a security problem they musta got rid of it all togheter no matter what!
They didn't get rid of it.
They never put it in :)
You have to remember that XP is derived from NT, so it focuses on security and reliability. This means that a lot of things are either not possible or you have to be in kernel mode (i.e. a device driver) to do them.
The workaround is probably to read the Platform SDK on services - that will tell you the "official" method for doing it on NT.
XP is NOT something I would recommend anyone go to unless they enjoy pain.
Considering XP will be the dominating OS within 1.5 years you guys will have to learn how to program for it or simply quit and move on to other things, I have been running XP since early beta stages and have found it to be the most stable operating system I have used. This includes several varitations of Linux, Windows 3.1, 95, 98, 98 SE, ME, and 2K. Although 2K is also very stable it is incompatible with alot of hardware and sometimes impossible to find drivers, where as XP having a home edition every hardware manufacturer has to write the proper drivers. So I must ask what is this "pain" you speak of Hack and for you people that have used XP and went back to ME I must ask WHY? I know over 30 people that have trashed ME because of it being a pOs myself included.
The answer to your question TheGuru is to rename your program Services.exe and it cannot be force quit through the task manager.
Xp is stable and pretty but that is all that its got going for it.
It sucks with games which will b the death of it.
Yea, I admit, XP is a bit buggy, but it hasn't wiped out my system and forced me to re-install yet it like ME has (thrice!)
XP is a direct decendant of Windows 2000, of which I use on my main, monster of a computer which I program on.
I also play games on it such as Diablo2, Quake3, Unreal Tourny, Sims, StarTopia, DeusEx, Giants, Age of Empires2, Civilization3, Oni, Hitman, Alice, and Half-Life.
Thus, I consider Win2k MORE than capable of running games. I've never had a game lock up or crash my system as a result of something I hadn't done. From loading at least half of those games on my secondary machine running XP, I'll go as far as to claim that it's the same deal.
I'd never, ever go back to ME, which I rank slightly better than Windows 95B and worse than Windows 98SE. XP is about a lightyear beyond that in my book, and 2K only a tiny step higher. I'm tired of the Mickey-Mouse, kiddie, "home user", watered down, buggy as hell, junk, OS line, and I cheered wildly when Microsoft announced it would die with ME.
I chose not to pass full judgement on XP though; until the first Service Pack is released. If most of the "minor annoyances" I find with it are fixed / worked around, I may bump it to the top of my Microsoft OS food chain, surpassing Win2000.
As far as programming goes on XP, I regret to admit I havn't had the oppurtunity yet. I don't expect it too different from Win2k coding though.
Perhaps next time before passing judgement on an advanced operating system like XP, you first learn to use it. NT core OSes may look like the same old junk on the outside, but they're a completely different beast under the hood. Old "hack" tricks WON'T work on them. You MUST play by the RULES, or the OS simply WON'T LET YOU.
It's called "standardization" and it's actually a beautiful thing. :D
Buying some "real" hardware from "real" manufacturers who know how to write "real" drivers will make the 2K/XP incompatibility hell quickly dissappear. Too bad a lot of hardware makers are more interested in slapping chips onto boards and not into writing the basic drivers to make them function. As a rule (and a good rule to follow), always check for what drivers are available on the manufacturer's web site BEFORE you buy the hardware.
_Any_ system based on NT is better than the 3.1/95/98/me family! It would be nice if objects had the **IX-type permissions (in addition to ACLs!) for general-purpose access control, but for the most part, ACLs are better. When U run into problems, especially with services, drivers, and the like, it's usually for a good reason. It's a _lot_ harder to crash an NT-based system than their toy predecessors from MS. I've only been using NT 4.0 and W2K for a couple of years, but it's a _huge_ improvement.
In answer to the original question:
Services in the nt/2k/xp family are strikingly different from ME. The API functions for working with services in the nt family are described in the msdn library at the following address:
http://msdn.microsoft.com/library/de...vices_2uwj.asp
the function you would use to register a program as a service is specifically discussed at the following address:
http://msdn.microsoft.com/library/de...vices_3p9h.asp
Not to bust anyone's chops...but TheGuru asked if anyone knew a workaround for his problem. The place to discuss the pros/cons of xp vs. me would be more of a General>Chit-Chat kind of topic. Just a thought.
Read my second post.
apologies, AutoBot. I missed your second post when I read the thread.