Pending File Operations
Posted 05 March 2002 - 20:56
Posted 06 March 2002 - 01:20
Posted 07 March 2002 - 02:30
I've only tried one install since learning of this location, but, despite requiring a reboot, it didn't write anything to this area of the registry.
Any ideas would be appreciated. Thanks in advance.
Posted 07 March 2002 - 21:35
Two others are:
If there are values in there, it is a good bet your machine should be rebooted!
In my case, the RunOnce were empty, but the pending file operations was not.
Posted 07 March 2002 - 21:58
From what I've read, if there is a reboot needed, BATCH_INSTALL equals a Non-Zero value. Can anyone confirm this?
Posted 08 March 2002 - 00:10
My question though was a more general one since the install I'm referring to is done by a 3rd party, so I don't have access to its system variable.
As suggested though, I'll check out the RunOnce and RunOnceEx entries.
However since this third party is a vendor, I may end up just getting with them to figure out the exact conditions in which they require a reboot or have them publish something which I can check to know whether or not it's necessary.
Posted 16 June 2003 - 19:59
How do we detect what file needed to be replaced but was locked?
In this instance all three registry locations previously discuussed are empty on a Windows 2000 Professional SP3 system.
Posted 16 June 2003 - 21:09
For each file group containing files that may be in use, set the Potentially Locked property to Yes in the Files Groups pane of the IDE.
If a locked file is encountered during installation, InstallShield copies the file to the target system with the file extension “.tmp” (or “.1” with IS5), and commits the file for installation for when the system is rebooted. As you know, InstallShield sets the Boolean system variable BATCH_INSTALL to the value TRUE if any locked files were encountered. Your script should call SdFinishReboot if BATCH_INSTALL is TRUE, otherwise call SdFinish.
On Windows 9x, installation of locked files works by creating a WinInit.ini file that runs when the system is rebooted; the initialization file moves the formerly locked files, and renames the “.tmp” (or “.1” IS5) files to their original names. On Windows NT, InstallShield calls the Windows API MoveFileEx to create registry values under the key HKEY_LOCAL_MACHINE_SYSTEM\CurrentControlSet\Control\Session Manager, in the value named PendingFileRenameOperations, which specify how to replace the locked files the next time the system is rebooted. (The data stored in the value PendingFileRenameOperations is of the Windows NT-only data type REGDB_STRING_MULTI, and can be viewed with the registry editor Regedit32.)
Posted 16 June 2003 - 22:13
I will look for the existence of such temporary files.
Posted 17 June 2004 - 07:19
Posted 17 June 2004 - 08:01
Look into the help for StrGetTokens and GetProfString.
hope this helps ...
Posted 17 June 2004 - 08:04
if i had the whole string i could use your function. is there an other
function to read the whole value of a reg-key ?
thanks for help
Posted 17 June 2004 - 12:51
If you look into the result string of GetProfString when searching for all keys in a section, you will see only the first one (it is delimited by \0, so after the first string, the text isn't shown ...).
But try to use StrGetTokens on the result string ... it may have more contents than you can see.
Posted 17 June 2004 - 12:57
thanks for help.