C:\Documents and Settings\Mike\Cookies is where your cookies are stored on
Windows XP.

E:\Documents and Settings\Mike\Local Settings\Temporary Internet Files is
"virtual viewer" of Windows and displays a mix of cookies and cache files.

Your cache files are really in alphanumerically named sub-folders of
E:\Documents and Settings\Mike\Local Settings\Temporary Internet
Files\Content.IE5.

Try this. If Windows is installed on your E drive (according to Logfile of
HijackThis, it is), then run regedit and go to

HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\Shell
Folders

What is the path for Cookies, in the right-hand pane? (Is it C:\Documents
and Settings\Mike\Cookies or E:\Documents and Settings\Mike\Cookies, or
something else?)

Go to

HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\User
Shell Folders

Is the Data for Cookies "%USERPROFILE%\Cookies" (no quotes)?

"Mike" <Mike@discussions.microsoft.com> wrote in message
news:7074D65E-B09B-48DD-83A6-4D9689891102@microsoft.com...
> HI again
>
> Are you the only other person on this forum LOL
>
> Yeah maybe, why they could not just come out and say that I don't know.
>
> I really don't think ZA is to blame, I am running ZA 6.1.744.001 which is
> old but stable, then new versions I found unreliable.
>
> This version of ZA has no cookie control.
>
> One thing I have noticed that puzzles me.
>
> The location for cookies in IE is E:\Documents and Settings\Mike\Local
> Settings\Temporary Internet Files
>
> yet the system location for cookies is shown as user C:\Documents and
> Settings\Mike\Cookies
>
> Two locations for the same thing?
>
> I did a IE reset today and I can now add sites to the allowed list and
> they
> do stay there, however when I close and re start IE the log in info is
> still
> lost.
>
> Thanks
>
> "PA Bear [MS MVP]" wrote:
>
>> The tech was telling you that they don't think any of the updates you
>> installed have anything to do with your problem, Mike.
>>
>> Time to post in ZA Forums (or uninstall ZA Free, enable the Windows
>> Firewall
>> & see if the behavior persists).
>>
>>