Well, I got norton corporate edition o install. Here's how I did it. I
renamed the wsock32.dll in my \windows\system to wsock32.bak, then extracted
the wsock32.dll from the windows precopy1.cab (win98). Norton installation
then went off without a hitch. After installing, I renamed wsock32.dll to
wsock32.win, and renamed wsock32.bak to wsock32.dll.
All fine and dandy. Only one problem. Now, on windows startup, and program
I assume to be norton complains with a little popup which says:
Error Starting Program
The NTS.DLL file is linked to missing export WSOCK32.DLL:1109.
Hmm, why doesn't it link to a function? It looks like it's linking to a
specific location in the file. Why? More security? Grr.
However, live update, oddly enough, works without a hitch. But it locks up
when I try to go to the "Scan Computer" page. So what does it want an
"untainted" copy of wsock32.dll for? Does it send norton info about your
computer when you aren't looking? OK, I'll stop spreading conspiracy
theories. :) Does it download parts of the program (like a "browser" when you
go to different sections.
At any rate, if I go through the process of using the "real" wsock32.dll, it
runs fine, and will scan, etc. This is really aggravating. Oh well. Just
be careful what I download in my win session, eh? :)
j----- k-----
On Friday 09 February 2001 06:08, you wrote:
> I know the regular versions work ok. I re downloaded and installed the
> personal
> version of Norton Antivirus for win9x. I don't have access to the Corporate
> Edition.
>
> But while I was on Symantec's site, I did a search in their knowledge base
> for transman. This is a known problem, with 3 possible solutions.
>
> Here is number 2 of 3 possible causes; I'd say it's a fair chance this is
> the one
> hanging you up.
>
> "Another application has installed a proprietary version of Wsock32.dll
> This problem can be caused when a third-party application has replaced the
> Microsoft
> version of Wsock32.dll with a proprietary version of the file. ..."
>
> They also list a general solution. I've included the link to the article.
> The link is long and wraps
> to a new line.
>
> http://service1.symantec.com/SUPPORT/nav.nsf/552ba2f7636bedf088256818006f78
>bf/faa834dae29366a58825684f00823cc7?OpenDocument&Highlight=0,transman
>
> Regards,
> Mike Badger
> NeTraverse
>
> At 01:10 PM 2/8/01 -0900, you wrote:
> >I'm sorry. Yes, I'm running 2.0.1. Followed the upgrade procedure on the
> > web page. I realized I didn't include verions info in the e-mail right
> > after I sent it. One of the reasons I downloaded it as soon as I read
> > the e-mail was the line about Norton, because I had tried to install it
> > the other day. So, I'm now running 2.0.1, but Norton still won't
> > install. So, now, the update doesn't fix the problem.
> >
> >Thanks again for your help (and quick reply).
> >
> >j----- k-----
> >
--
Joshua Kugler
Associated Students of the University of Alaska Fairbanks
Information Services Director
[EMAIL PROTECTED]
907-474-7601
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
