Read Only with Syamntec

[Salesman_Gil]

Hi All,
Long time...
I last left you with a huge Syamntec problem. All kinds of VPC32 errors and such. Basically NAV was non-operational.
What I found out after many,many hours. Was simply Nortons has to be installed first! Not sure about all Win 98 machines, but any Compaqs I would highly recommend it. I saw these errors with three different version of NAV, NAV 7.5, SAV8.0, SAV 8.5. All coperate editons.
Besides wanteing to get the word out about this, I have a question.
All problems root from the file MFC42.dll. Once it is modified after NAV, NAV is hosed.
If I make that file a Read Only file, will that prevent any other installations from modifiing it?

[TOAD6147]

IMO, you need to get rid of NAV and get a real anti-virus program. Do you really want to depend on a program that can be damaged so easily?

[Salesman_Gil]

You know I trully wish I could. I do not think NAV is bad, it just does not work well with Compaqs version of Windows.
If I could I would, but as usually that desion is far above me, I just fix what I get.

[John Prophet]

Hey dude...whats up?

Hmm, check this page here http://search.symantec.com/custom/us/query.html

I did a search for "Mfc42.dll" and it had lots of hits....I would go thru those if I were you and see if anything sounds familiar.

I never saw that other thread.

one thing you can try is to run "sfc" which is "system file checker"....there is an option to "extract one file from installation disk"...you check that then you type in the name of the file then it either knows where it goes or it asks you for the destination , which in this case is the "c:\windows\system" folder. One thing about those mfc type files is that a lot of apps mess with them....so they have lots of chances to be changed/corrupted etc....when I did a search for mfc42.dll I found it in 5 places on my comp...the system one in windows/system but then it was in like 5 other places in use by apps, like juno.exe and sonic/myDVD etc etc. So I would try to restore the one in the windows/system folder and see if that fixes the issue...if not, I might would try to actually take that newly restored one and then replace ALL the other instances of mfc42.dll on the comp.



or---------- you can run sfc and let it "scan for altered files"..see if it finds anything first..then go back and do the"extract blah blah"

Just something to try.

JP

edit....ok I just happened to look at ONE of those problems listed at the norton search for mfc42 and it had this as a fix http://service1.symantec.com/SUPPORT...rc=bar_sch_nam

Situation:
When you attempt to install Norton AntiVirus (NAV), you see the error message "NMAIN caused an invalid page fault in module MFC42.DLL."

Solution:
This can be caused by an outdated version of the Windows Mfc42.dll file. If it is in use when NAV is installed, then NAV may not be able to replace it with an updated version.

To fix this, you must locate all existing Mfc42.dll files, rename them while booted to a command prompt, and then reinstall NAV. Follow the instructions in the order shown.
------------------

and then of course it gives all the steps.

[John Prophet]

oh and "Was simply Nortons has to be installed first!"

I think you would be right about that..cuz the other apps are probably changing that mfc42 file and norton is balking.

If you tried the mfc42/name change/norton reinstall method on a comp and it did work you probably could make a batch file to do that name changing deal..cuz I know you have a lot of comps etc

[Salesman_Gil]

John Prophet...
Yeah I did all that searching.. and tried everything, and I mean everything. updated all the libraries, tried sfc, saved an older copy of that file, and renamed it. what I found was that NAV has its own version of that file, and it copies in to your system folder. The problem comes when you install something that has its own copy of it also. For instance Canon Creative software. It was the last thing to install too... but that is another story.
Basically what happens is that once you are hosed. It is permatently hosed. I tried finding my previous post, but could not. I've tried everything.
What is really scary is that it has to have been broken for at least 2 years, on our field computers.
Is there a way to protect that file? So that nothing can change it or overwrite it? I was thinking read only, but that did not do it. I've been thinking of having every computer have two users, one admin that no one knows the password, and one actual user. That way they can't install things, and in general mess things up, like only a field staff can do.
Any Ideas??

[John Prophet]

You cant do something like...install norton onto a new machine..take the mfc42 file from that new machine and then go replace every instance of it an another machine with that one file?...to see if it works etc

[Salesman_Gil]

I did something simliar, I saved the MFC42.dll to a floppy. Hosed NAV, then I tried copying that file back, restart, still hosed. I wonder if it keeps that info somewhere. How does it know that it was hosed before? Or maybe it corrupts another file, at said time of hosing.

[Salesman_Gil]

Hey John
Quick question.. If you turn your computer on, and the only thing that runs are the fans, no hard drive, no beeps, when you go to turn it off, the switch does not work. Are we talking bad motherboard? I think it is, but I've always had a hard time, troubleshooting mother board problems.

[John Prophet]

hard to say exactly...could be cpu also I guess....only way to know for sure is maybe swap cpu's....if it boots with other cpu its the cpu..if it dont..you could swap maybe video cards to make sure but probably at that point its motherboard..of course always try to reset the cmos to, just in case its something like that...

Ive had similar things happen when i am messing around trying to upgrade cpus etc....if the motherboard wont support that cpu it will still sometimes boot but just fans etc..nothing else...and the power button does nothing, I have to unplug it etc....so it could be cpu




on the other issue-----------

Have you tried uninstalling the norton....replacing ALL the mfc42.dll's on the comp and THEN RE INSTALLING norton??