How to? Volatile Registry

Oct 18, 2008
272
1
#1
Hello ---

I been having start up issue with my w7 computer and discovered that this command

set /e /v info=1

took over 9 minutes to finished --

I got the timing from the log since I had logging turned on in tcc

any suggestions would be appreciated

thanks

fpe
 
#4
Hello ---

I been having start up issue with my w7 computer and discovered that this command

set /e /v info=1

took over 9 minutes to finished --

I got the timing from the log since I had logging turned on in tcc

any suggestions would be appreciated

thanks

fpe
That sounds hard to believe. Can you reproduce it at will? Have you got any more details (like when/how it's being run, and what other things are going on at the same time)?
 
Oct 18, 2008
272
1
#5
Wow --

I miss read the log ... it was 7 seconds not 9 minutes -- I must have been looking
at some other point in the log ... My guess is that the registery was locked at that point
during the start up -- sorry for my mix-up

[ 9/28/15 14:28:42][3244] set kedit16=1
[ 9/28/15 14:28:42][3244] set rxdebug=-1
[ 9/28/15 14:28:42][3244] cdd "C:\Users\frank\AppData\Local\Temp"
[ 9/28/15 14:28:42][3244] iff %bginfo NE 1 then
*[ 9/28/15 14:28:42][3244] set /e /v bginfo=1
*[ 9/28/15 14:28:49][3244] call r
[ 9/28/15 14:28:49][3244] r
[ 9/28/15 14:28:49][3244] echo off
[ 9/28/15 14:28:49][3244] iff defined go.bginfo then
[ 9/28/15 14:28:49][3244] set /v /e go.bginfo=1
[ 9/28/15 14:28:49][3244] gosub go
[ 9/28/15 14:28:49][3244] setlocal
[ 9/28/15 14:28:49][3244] switch FPE1003
 
#6
7 seconds is still a long time for an operation that simple. Is it in a logon script? The volatile environment is in HKCU. Perhaps that hive isn't fully loaded at that time, or as you said, it's locked for some reason.
 
Oct 18, 2008
272
1
#7
7 seconds is still a long time for an operation that simple. Is it in a logon script? The volatile environment is in HKCU. Perhaps that hive isn't fully loaded at that time, or as you said, it's locked for some reason.
Hello -- Thanks for your reply ... its not a "logon" script, but part of tcstart.cmd when TCCLE starts -- and TCCLE is in the "startup" folder under "programs"