reboot required but RTE wasn't changed

[menchar]

Can anyone tell me what the "reboot required" logic (or illogic ) is when using a distribution kit?

I have a distribution kit that demands a system reboot (and demands a project recompile when creating it), even if nothing has changed ?!

Is this a setting I have inadvertently set?

\Thanks

Menchar

[tstanley]

I know that if a driver is included in the distribution kit the installer generally wants a reboot (which is unnecessary if one goes into Device Manager and tells Windows to scan for new hardware if the device in question in Plug and Play).

[menchar]

I do have a .fp in the project only to create a type library for the DLL.

It may well be that this is forcing the reboot even though nothing's changed.

I don't think it always does it though, that's what has me puzzled.

Thnaks,

Menchar

[vix]

I've been experiencing the same behaviour: while developing an application I install it on the same PC several times day after day, and I noticed that sometimes the reboot is required, and sometimes it isn't.

Sometimes I modify two or three lines of code, and the installer says both the application and NI components will be updated, then the reboot is required;

in other situations I modify a whole part of my application and the installer says only the application will be updated, then reboot is not required.

I've been trying to understand this behaviour for a long time, but I heven't been able to find an explanation

[tstanley]

When I was talking about drivers, I meant including a .inf and .sys with the distribution kit, which the installer then automatically interprets as a driver to install (which is actually annoying in the sense I have no control over this and the installer doesn't check the version of the current driver to see if it actually needs updating).  Now that I think about it, the reboot seems only be requested on a system where the driver was already installed, and therefore an uninstall of the old driver is needed.  If it's a fresh computer without the driver, the installer installs the driver and doesn't seem to force the reboot most of the time.  In all I actually prefer the old, much simpler installer from CVI 7.1 than the installer from the current version of CVI.