ADVISORY: Norton 360 v3 .0.0.134 - program no longer executing e.g. Corel Paint Shop Pro Photo X2

Hi hrguy1,

 

I hope you or CGoldman don't mind me intruding for just a minute.  

 

There are two ways that you can accomplish getting to this directory while using DOS (Disk Operating System).

 

Copy this " cd \program files\norton 360\engine\3.0.0.134 " (without the quotes) and after you enter the Run command simply paste what was copied (cd \program files\norton...) into this window and hit enter.  It should take you to the subdirectory you just entered and continue from there.

 

Or after you enter the run command and are at the command shell window enter - "cd \" (without the quotes) and then enter the command "cd \program files\norton 360\engine\3.0.0.134" (without the quotes)[please note the space between cd and \].

 

If you wish (some packages are now being shipped (I think they already are) with version 3.0.0.135) you can cd\ (change directory) to "cd\ program files\norton 360\engine" (no quotes) and then enter the command "dir"  (no quotes)[which shows the contents of the DIRectory]. If it shows 3.0.0.135 instead of 3.0.0.134 please simply enter the command "cd 3.0.0.135" (no quotes).  And then proceed accordingly.

 

Take care,

Mumford68

Message Edited by mumford68 on 03-27-2009 07:12 AM

hrguy1,

 

I edited my last post. Take a look above. 

 

Mike

Mike

Here are the results:

 

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Moser>cd\

C:\>cd program files

C:\Program Files>cd norton 360
The system cannot find the path specified.

C:\Program Files>

hrguy1,

 

To avoid confusion I will post my last post again. 

 

You must be running 64 bit windows. You can type the following:

 

cd "\program files (x86)\Norton 360\Engine64\3.0.0.134"

 

Thanks,

Mike

 

Mike

I tried the 64 bir suggestion and same thing. i am certain I have 32 bit. As certain as a dummy at this can be????

hrguy1

hrguy1,

 

The istallation directory of Norton 360 must have been changed. Do you remember changing the location of install? If not could you do a system side search for buShell.dll?

 

Thanks,

Mike

Hi Mumford68

 

here are the results of your suggestion:

 

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Moser>cd \

C:\>cd \program files\norton 360\engine\3.0.0.134
The system cannot find the path specified.

C:\>

Mike

I just downloaded from Norton and let it put it where it wanted it. I have not moved it. I don't know how to do a search like you suggested. Sorry you are dealing with an old retired dummy!

hrguy1

Hi hrguy1 -

 

If you could go to the Norton 360 shortcut that is on your desktop and right click it, and go to Properties.

 

From there if you copy and paste the text in the "Start in:" field into your command line.  Also if you could post that here.

 

Thanks.

hrguy1, Sorry, If I had known Michael_S was interacting with you I would have stayed out of it :)

 

 

Mike

I went back to the program files and the file is called norton 360 premier edition

hrguy1

John

This seemed to work. I got the message that the process succeded! Praise the Lord! Now if I can open Corel. Ihave tried yet. I wanted to tell you the news! Here is what I did

 

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Moser>cd "C:\Program Files\Norton 360 Premier Edition\Engine\3.0.0.134"


C:\Program Files\Norton 360 Premier Edition\Engine\3.0.0.134>regsvr32 /u bushell
.dll

C:\Program Files\Norton 360 Premier Edition\Engine\3.0.0.134>exit

Hi hrguy1 -

 

Good to hear.  I hope the work around works for you.

 

John

John, Mike and Mumford68,

Thanks for the time in helping me! I greatly appreciate it.

Hrguy1

hrguy1,

 

Great that it worked. The instuctions are a bit different depending on the edition and platform. But you should reboot your system to unload our shell from explorer now before Paint Shop will work. 

 

Mike

mumford68


mumford68 wrote:

Hi hrguy1,

 

I hope you or CGoldman don’t mind me intruding for just a minute.  

 

…cut…

I dont mind at all. Of course not.

hrguy1

 

I had not thought of "premier"; its a good job you posted here. Alas I cant edit the original advisory but hopefully others fill pick on the postings if they too have premier.

 

Glad all is working.

mumford68, John and Mike,

I just tried to opne my Corel PSPP and it worked great!!!   Just like a pickle seeder as my Dad would say. I don't know how a pickle seeder works but the Corel works wonderful!

 

I have been a loyal Norton user for many years and so many of my friends thinks it is a bad program, but it is things like this forum that make me feel good about being a loyal norton user. I have always loved the programs andf this new 360 is no exception!

 

Again, thanks to you pros from this old retired computer learner!

 

Dick Moser (hrguy1) 

Michael

 

There are some posting in NIS forum about users applying workarounds and being concerned (or unconcerned in some cases) as to what will happen when the patch is released.

 

I think I may have privately mentioned this, but I would like to make a suggestion please.

 

Users who have applied the workaround (based on v2 experience) may have undertaken one or more of the following actions:

 

1. They may have simply de-registered the dll.

2. They may have removed the dll

3. They may have renamed the dll.

 

My suggestion is that the patch, in respect specifically of this bushell.dll, should install a new bushell.dll and not patch any existing bushell. to the new version, and should re-register the new bushell.dll. In that way whatever action the user has taken, a new bushell.dll will be written to the existing directory and become registered.

 

It is hinted that this is not necessarily the approach that symantec might take for patch releases, but in my view it is the most logical and will avoid us having to advise users who applied the patch to ensure that the dll is in place prior to the patch release and ensuring that such dll is registered.[ I have not, as you may know, set out the re-registration process.]

 

 

cgoldman,

 

We are replacing the DLL and hopefully will automatically re-register the DLL for the users who used the work-around. We will know more details soon. 

 

Mike

Message Edited by michael_shavell on 03-27-2009 12:10 PM