Long pause at boot

Hi Kryptic - Yet another request

Please make the necessary adjustment(s) to produce a logon without the delay, then create a BootlogXP log of that logon. Make yet another log with a delayed logon. Post the header info and first process info from each log please. Example of what I want below.

No Delay
XPBA 1.0
26.12.2007 22:28:47.791
===
ProcessId -1
C:\WINDOWS\system32\ntoskrnl.exe
26.12.2007 22:27:33.703

Delayed
XPBA 1.0
26.12.2007 23:09:37.401
===
ProcessId -1
C:\WINDOWS\system32\ntoskrnl.exe
26.12.2007 23:07:08.687

 

Ok. Well True Vector started in almost no time, a couple seconds. The zlclient did stay there for a bit and then loaded properly, all for about a minute and change.

 

But was the logon still delayed, or did disabling from startup allow for a normal logon time?

 

Sorry

Disabling from startup did allow for a normal logon time.

What I said before was for when I manually started true vector and zlclient

 

As per request

No Delay
XPBA 1.0
26.12.2007 2:1:31.650
===
ProcessId 4
C:\WINDOWS\system32\DRIVERS\nic1394.sys
26.12.2007 01:59:12.627
120675 ms

Delayed
XPBA 1.0
26.12.2007 2:15:27.62
===
ProcessId 2732
G:\WINDOWS\system32\rundll32.exe
26.12.2007 02:13:18.796
1322 ms

 

Those are not the results I expected.

No delay log
time completed less time started = 2:19.024

Delay log
time completed less time started = 2:08.824



Is there a process start time earlier than the one shown in the delayed log? (02:13:18.796) Is there one in the non-delayed log?

 

I will try again and post the whole logs.

 

No Delay Log pt 1

***** it. These logs too long.

No Delay Log:
http://download.yousendit.com/8F65125875C7F9B7

Delay Log:
http://download.yousendit.com/6AB2474340F7FB7D

Btw, noahdfear, I emailed you the logs.

 

I installed the 464 beta just to see. No change.

 

Hi Kryptic,

I got the logs, and I see now that for whatever reason the first process in the delay log is not the first process to begin being logged, as past logs have been. I haven't had time yet to analyze them at all, but just one process in the delay log reveals the below.

C:\WINDOWS\system32\comres.dll
26.12.2007 08:46:01.122
C:\WINDOWS\system32\msi.dll
26.12.2007 08:50:04.879

Starting time of the logon process in the delay log was 08:45:35.525 and completion time was 08:50:39.723
5 min and 5 seconds ...... definitely a considerable delay.

Starting time of the non-delay log is 08:37:25.639 and the completion time is 08:39:39.270
2 min and 14 seconds

May I ask what method was used to avoid the delay?

If you don't mind, I'd like for you to download SIW and run it (it's a standalone application), then click File>Create log file and email me the log. I would just have you post the log, but it's quite large and contains quite a lot of information about your system, more than what should be posted in public. However, it will show me your installed software and hardware, it's configuration, drivers loaded and failed to load, etc etc. It may prove very helpful in pinpointing a possible conflict. I have also been discussing possible conflicts with members quite knowledgable in the hardware area, and this information will be helpful in determining recommendations in that area as well.

 

Opened Zone Alarm Client, went preferences, deselected Load at Startup and then rebooted.

 

I can't make txt logs without purchasing. Are the others ok?

 

The HTML is fine.

 

I'd like for you to test a hack for starting Zone Alarm, and see if you still experience such a long delay.

First open the ZA console and deselect the option to load at startup.

Next, highlight and copy the bolded text below then paste it into a command window.

echo.>desktop\enableZA.txt
echo To enable ZA hack paste the line below in a command window then hit enter>>desktop\enableZA.txt
echo.>>desktop\enableZA.txt
echo reg add "HKCU\software\microsoft\windows\currentversion\run" /v "Zone Alarm" /t REG_SZ /d "C:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe" /f>>desktop\enableZA.txt
echo.>>desktop\enableZA.txt
echo.>>desktop\enableZA.txt
echo To disable ZA hack paste the line below in a command window then hit enter>>desktop\enableZA.txt
echo.>>desktop\enableZA.txt
echo reg delete "HKCU\software\microsoft\windows\currentversion\run" /v "Zone Alarm" /f>>desktop\enableZA.txt
reg add "HKCU\software\microsoft\windows\currentversion\run" /v "Zone Alarm" /d "C:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe" /f
exit
cls

Reboot

That is going to create an entry in the registry (enable the hack) for your userprofile to start Zone Alarm. It is also going to create a text file on your desktop that tells how to enable the hack and disable the hack. Disable it should you need to turn ZA back on via the console>load at startup option.

 

Before I do this can you tell me what it is all about?

 

Timing. I just want to see if loading ZA at a different time will prevent the delay.

 

Mein Gott!!!

The delay!!!! She is gone!!

So what is happening with the True Vector Service now?

 

True Vector should have started as well. Please verify.

I would also like to change it just a bit and see if the results are the same. Copy the disable command from the enableZA.txt file on the desktop and paste it into a command window then hit enter. Now lets change the enable command to affect the local machine key rather than the current user key. Change the "HKCU\ in the reg add command to "HKLM\, then paste the command into the command window and hit enter. Reboot.

 

Oh yes! It has. But the startup type is set to manual. Does this mean that ZA starts it?

 

Yes, it is initiated by starting zlclient.exe
By deselecting 'Load on startup' the True Vector service is set to manual and the normal zlclient.exe run entry is removed. The hack just puts a zlclient.exe run entry back in the registry.

Would you also check Task Manager and verify whether ScanningProcess.exe is running after logon. It should be intialized by starting zlclient and True Vector.