• Date
    brucek
  • Date
  • Replies 2 replies
  • Subscribers 183 subscribers
  • Views 3719 views
  • Users 0 members are here

What Windows services, drivers, etc load for the Client, and how to stop them.

What Windows services, drivers, etc load for the Client, and how to stop them?

Just wondering what things can be turned off (and how) when the client isnt running on a computer.  It would be nice to prevent un-needed stuff from loading into windows when the client is not going to be run, and thus prevent any more window-gunk from building up in my machine.

  • Actually, nothing is installed for an Offline or Client installation that starts automatically. It tries to register itself with Microsoft .NET, but the .NET services are only started when something that uses .NET is actually run. (.NET is not included in the installer as it is included in the vast majority of Windows XP and Vista installations.)

    There is the driver for the USB dongle, and that only loads into memory when the dongle is inserted.

    (When installing on a console a few other drivers and services are installed, but these aren't required for Client or Offline as they never need to directly connect to ACN equipment.)



    [edited by: Richard at 9:14 AM (GMT -6) on Sat, Aug 23 2008]
  • in reply to Richard

    So EOS/ION does not use any NET2/3 drivers or such to run the client, except for what is loaded when the client starts?  This is good.

    What about NET2Config?  Does that load anything before it is started up?

    This is all relevant to WinXP

     

    I guess what I really need is a list of all the ETC services/drivers loaded for everything from Lightmanager, EELOAD, Dimstat, Congo, ION /EOS.

     

    This will help with managing computers that are not exclusively used with ETC products

     

Related

www.etcconnect.com