If anyone has ANY ideas about this:

/postlite95582-.html
(re: my original post from Wed Dec 29, 2004 11:41 pm),

please pass them along -- I'd love to hear them.

I've scoured every inch of Symantec's site and have tried
e-mailing and calling them, but they don't support NIS/NAV 2003 anymore, so they're no help.

This one has stumped everyone on the Net (at least who I've asked) and I can't find any reference via Google (or any other Search Engine).

Thanks in advance,

Mike___________

Hello again,

I have been thinking about your problem with the dates that scans are completed. It reminded me of the Y2K bug. Remember that?

I think that in order to change those dates you will need to edit the application settings in the Registry. The problem even with that is that the dates are not entered in the Registry like we see them, but in hexadecimal format. That too, could also be in special, non-standard code.

Looking at it this way, I understand why other people who might know what to do, have not come forward. It would mean hacking into your NAV. That's against most reputable boards policies. It would be against ours too.

Learn all you can.


Best regards

_________________

Microsoft MVP Consumer Security 2006, 2007 & 2008

Hi,

I PM'd you (just letting you know in case you don't look at your PMs on a regular basis).

Thanks about the above (Regedit)...

Mike_________

Hi MekongDelta69,

Nice to see you again. Your thread is unlocked, as you can see. Sorry about not getting back to you after our last PM. I have had several large projects too. When my memory gets too full, it leaks.


Larry

_________________

Microsoft MVP Consumer Security 2006, 2007 & 2008

I ( MekongDelta69 ) would like to thank you ( Anonymous )
for re-opening this post!
(Don't blame me - I was just fooling around with some of the new
input parms!!)

No problem - every now and again, I have to reboot too!

Thanks for your assistance - I appreciate it,

Mike__________

_________________
TF-116 Gamewarden (PBRs) RivRon 59 -- 'Nam '69

Just repeating (some of) my post from Mon Dec 13, 2004 1:31 am
(in this thread), to make the solution easier to find:

-----------------------------------------------------------------

I've JUST spent about 12 hours finding and fixing all this.

This being:
('Symantec LU1815 - can't connect because you need Admin Privileges')
is just one of scores of problems I've had to fix...

1.) Go here:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/pfdocs/2002072215205213?Open

2.) Then:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/pfdocs/2003041613185213

3.) Then:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/pfdocs/2000071310294913?Open
[In here, they mention an lusetup.exe File. That's for Enterprise users.
Substitute the lusetup-lt.exe File (Live Update 'Lite' -- for home users --
assuming that you're a home user)]

4.) Also - here:
http://www.symantec.com/techsupp/files/lu/lu.html
[Pick the lusetup-lt.exe (1,934,880 bytes) download from 12/2/04]

5.) Then:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/pfdocs/2003122213384913?Open
[Expand the Consumer Icon first; then expand the 'Deleting damaged files
from the LiveUpdate Downloads folder' next]

{My advice is to print ALL the relevant docs above BEFORE you do all this,
so you have everything handy for reference at your fingertips}

Log off -> Restart -> Run Live Update Again

I've wasted so much of my time with Symantec in the last 4 years,
so maybe I can help somebody else avoid a little grief...

Mike__________

So you can find it!...

[quote="Prince_Serendip"]

Quote:

I no longer use Symantec products. Easier alternatives exist, cheaper and more effective.

Main page (after you sign in) has some good reviews...

Just in case...