Hi Bill. I graduated from ECU in 1983 and did some of my grad work at Pitt Memorial. I have fond memories of Pitt County.
Enough of old home week - push back. Really really hard. That's ridiculous. Services are even easy to do in the Win32 API. It takes less than 20 lines of code in C# to start a service cleanly and only about 10 to shut a service down cleanly. -----Original Message----- From: Mayo, Bill [mailto:[email protected]] Sent: Thursday, January 21, 2010 4:05 PM To: NT System Admin Issues Subject: Reality check I am terribly frustrated with an application vendor who is on-site to add a new module to on of our critical software packages, and I want to confirm it is not just me being difficult. This system already has the requirement that a workstation be logged on with 3 different programs running in the foreground to shuffle data around between modules. To be clear, an account has to be logged into this machine at all times for this system to work properly. They are here now, installing a new server for a new module, and they now have to have it doing the same thing on the server (logged on account, foreground applications running). This is not a minor system (either in size or cost) and the parent company is not tiny (rhymes with "bun hard"). When I say "services" they look at me like I am from Mars. The problems with needing an account logged onto a server at all times seem obvious to me. (The workstation was bad enough.) Am I alone? Bill Mayo ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
