Norton Internet Security 2003 Install Problem

[sechs]

On first reboot, after installing NIS on Windows 2000 SP3, I get a stop error, "NO_MORE IRP_STACK_LOCATIONS," right when the GUI should start. I didn't have this problem on a previous installation on a different computer with the same OS.

I've tried running LiveUpdate before the reboot, to no avail. I've tried clean installing the OS, to no effect. I am able to recover the operating system by booting to last known good, and uninstalling NIS.

I haven't been able to find anything on Symantec's website on this kind of problem, and I haven't found anything useful about this error.

Has anyone else run into this and found a fix? Is there something I can try to fix this?


Thanks in advance.

 

[sechs]

I found some information on the error (generically) at http://www.osr.com/resources_ifsfaq.shtml . It's Q51. However, it isn't clear on exactly how to fix or, at least work around the issue.

 

[bsobel]

Sechs, ping me on Monday, I'll ask the NIS driver developer if he's seen any reports of this...
Bill

 

[sechs]

I tried adding the IRPStackSize key to the registry per the common WinNT problem.

I tried activating my serial and parallel ports.

I borrowed a copy of NPF, and get the same error.

Anyone have any other ideas?

 

[bsobel]

Quick question, do you happen to have a Highpoint RAID controller in your system?
Bill

 

[sechs]

As a matter of fact, yes. Both of my harddrives are on it in JBOD mode. Does this make a difference?

 

[bsobel]

Hi,

I talked with the NIS driver developer about this and they are actually currently dealing with the problem, it turns out there is a bug in the Hipoint RAID controller driver which causes an interaction with SymEvent. I have all the technical gory details if you want to discuss them. We are working with Highpoint on a fix for their driver, for the meantime the below was sent to me as a workaround:

"For now the solution is to delete the Highpoint driver \windows\system32\drivers\hptpro.sys .It will not disable functionality of RAID controller. Their tech support agreed with that solution."

(I'd actually recommend moving the driver out of teh drivers dir and not deleting it incase you need to put it back). If you're up to trying that, please let me know if it resolves the problem. I'll check back with them in a week or so and see if we have any update from Highpoint.

Best,
Bill

 

[sechs]

I'll give that a try. I'm a bit nervous about removing a driver... but we'll see.

 

[sechs]

Sure enough, that worked... so what's the point of the HighPoint driver if I don't need it?

 

[bsobel]

That I actually don't know (I was thinking the same thing). If I had to guess I would think they exposed some additional information (perhaps in the device properties in device manager) that the default driver doesn't support.

Bill

 

[jlathrop]

Thanks guys, I'll have to keep this in mind as I also have Highpoint RAID...