Invalid Vxd Dynamic Link Call from Vsdata95

From: Christopher Patrick Tyrrell (Christopher@tyrrell01.fsnet.co.uk)
Date: 12/10/01 

From: "Christopher Patrick Tyrrell" <Christopher@tyrrell01.fsnet.co.uk>
Date: Mon, 10 Dec 2001 22:12:41 -0000

Hello,

Recently, to try to solve an internet surfing problem, my ISP advised me to
remove all the protocols from my network configuration through control panel
> network and reboot before putting them back in. I found that during
reboot there was a blue screen message headed Windows and said

"Invalid VxD dynamic link call from Vsdata95(01) + 00014EE8 to device 0028,
service 800A. Your windows configuration is invalid. Run the windows setup
program again to correct this problem.

To continue running windows press Y or enter. To quit the current program
press N. If you continue running windows, your system may become unstable.
Do you want to continue?

Press Y for yes or N for no: Y"

I opted to continue and the same blue screen message was repeated except the
numbers were 00014FCE, 0028 and 8029 respectively. I opted to continue
again and the same blue screen returned again but the numbers this time were
00014EEE, 0028 and 800B respectively. I opted to continue for a third time
but now the screen went black with the lines at the top saying:

"While initialising device vsdata95:
Windows protection error. You need to restart you computer."

Needless to say I did restart my computer and attempted a windows re-install
but to no avail. I got round it by starting in safe mode and by carrying
out various tests found that if I'd uninstalled ZoneAlarm before removing
the protocols all would have been well.

It seems that ZoneAlarm objects to there being no network protocols and
prevents a good boot. I found it happened with versions 2.6.357 and 2.6.362
on Windows 98 and Windows 98SE. Has anyone else encountered this? Is this
meant to happen? 

--

Regards

Christopher Tyrrell
Mailto:Christopher@Tyrrell01.fsnet.co.uk

Relevant Pages

  • Re: Workgroup
    ... I have one XP Home used as a file server and 5 other PCs ... >>protocols are installed, it can access the internet, ... >than one protocol can make the network unreliable, ... >Windows XP Network Protocols ...
    (microsoft.public.windowsxp.network_web)
  • Re: PID 1212 slowly maxing out?
    ... Windows 2003 servers, but could it affect Windows XP as well? ... I'm on a home network running on wireless. ... Logical Disk Manager service ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Workgroup
    ... >it still will not see any computers in the workgroup. ... than one protocol can make the network unreliable, ... un-bind sharing from the other protocols. ... Windows XP Network Protocols ...
    (microsoft.public.windowsxp.network_web)
  • Re: Windows 2008 Server Core
    ... other VM's which are windows 2003 and Windows XP. ... of the fact that modifying network configuration will likely need to involve ... >> I am facing the issue with Windows 2008 Server Core. ...
    (microsoft.public.windows.server.active_directory)