adamsc22
10-19-2004, 04:54 PM
Hello,
At work we have this third party app (Cicero) that we've customized. Much of the customization is done through the registry. We have about an 8,000 line .reg file that is called from a batch file each time the program is launched. So, before the program is launched we first delete and then write all the registry entries for our program.
This has always worked correctly, until we moved to XP. Now, it seems that the whole registry is not being written before the program starts (and subsequently starts to read from the registry for the configuration details).
This is the batch file line that calls the .reg file
%SystemRoot%\regedit /s "C:\Progra~1\NF_Cicero\Registry\HKLM_Level8.reg"
Is there batch file call that does not execute the next statement, until the previous has returned? Or does someone see another solution to this issue?
Thanks for any input
At work we have this third party app (Cicero) that we've customized. Much of the customization is done through the registry. We have about an 8,000 line .reg file that is called from a batch file each time the program is launched. So, before the program is launched we first delete and then write all the registry entries for our program.
This has always worked correctly, until we moved to XP. Now, it seems that the whole registry is not being written before the program starts (and subsequently starts to read from the registry for the configuration details).
This is the batch file line that calls the .reg file
%SystemRoot%\regedit /s "C:\Progra~1\NF_Cicero\Registry\HKLM_Level8.reg"
Is there batch file call that does not execute the next statement, until the previous has returned? Or does someone see another solution to this issue?
Thanks for any input