IRPStackSize Change did not fix the problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

This happen when any computer tries to map a drive on a
XP Pro machine. I have changed the IRPStackSize from 11
to 14 then to 20 and now have it at 32. I have also
redited the system varable for path. This fixed it once
when that was wrong, but after many days of trying to
install a new ver of Norton Anti-virus it started up
again.
I did
get Norton SystemWorks 2003 on and working.
I'm out of guess (Yes I did reboot for ever change. Oh
and it can not map to a drive on its self either, but can
map the other computers.
 
This happen when any computer tries to map a drive on a
XP Pro machine. I have changed the IRPStackSize from 11
to 14 then to 20 and now have it at 32. I have also
redited the system varable for path. This fixed it once
when that was wrong, but after many days of trying to
install a new ver of Norton Anti-virus it started up
again.
I did
get Norton SystemWorks 2003 on and working.
I'm out of guess (Yes I did reboot for ever change. Oh
and it can not map to a drive on its self either, but can
map the other computers.
Click to expand...

Old saying when you cant get help:

If in doubt, kick it out.

Eg, use System Restore do a date before the shit hit the fan.
 
Back
Top