Thanks for the info.
--
Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim Thrasher" <(E-Mail Removed)> wrote in message
news:41e401c375b4$6d223fb0$(E-Mail Removed)...
> Ken,
>
> Sorry to take so long to answer your question. I've been
> away from my PC for a few day's of vacation.
>
> My Home PC is an HP Pavillion 752n, with 5GB of the disk
> drive partitioned as drive D, labeled HP_RECOVERY. I got
> the good copy of SRVSVC.DLL from a Microsoft XP Home CD
> that came with a laptop that I purchased for my daughter.
> I would have downloaded it from the Microsoft website, if
> I knew how to find it there.
>
> Thanks
> Jim
>
>
> >-----Original Message-----
> >I've been wondering where these corrupted copies of
> srvsvc.dll were coming
> >from. I'll try and get a hold of one of these recovery
> disks and check it
> >out.
> >
> >What model HP do you have?
> >
> >--
> >
> >Ken Wickes [MSFT]
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >"Jim" <(E-Mail Removed)> wrote in message
> >news:03a701c370df$1a8f9060$(E-Mail Removed)...
> >> It's been a while since I've done any DOS command line
> >> work, but when I expanded the srvsvc.dl_ from an
> original
> >> XP disk and copied it over the one in the System32
> folder,
> >> the service started working. The srvsvc.dl_ on my HP
> >> recover drive didn't work. So, I'm guessing it's been
> >> corrupt since the original install.
> >>
> >> Thanks
> >> Jim
> >>
> >> >-----Original Message-----
> >> >I wonder why sfc doesn't catch this. Either way your
> >> best bet is probably
> >> >to get a good copy of srvsvc.dll off the XP disc.
> >> >
> >> >--
> >> >
> >> >Ken Wickes [MSFT]
> >> >This posting is provided "AS IS" with no warranties,
> and
> >> confers no rights.
> >> >
> >> >
> >> >"Jim" <(E-Mail Removed)> wrote in message
> >> >news:016801c36f28$859957a0$(E-Mail Removed)...
> >> >> At the command prompt, I also ran "sfc/scannow",
> which
> >> did
> >> >> not return any messages. So, I assume that all the
> >> >> protected Windows files are intact and in their
> original
> >> >> versions.
> >> >>
> >> >> Jim
> >> >>
> >> >> >-----Original Message-----
> >> >> >After trying to restart the service, I opened a
> command
> >> >> >prompt and typed "sc queryex lanmanserver" and got
> >> these
> >> >> >results:
> >> >> >SERVICE NAME: lanmanserver
> >> >> >TYPE : 20 WIN32_SHARE_PROCESS
> >> >> >STATE : 1 STOPPED
> >> >> > (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
> >> >> >WIN32_EXIT_CODE : 2001 (0x7d1)
> >> >> >SERVICE_EXIT_CODE : 2001 (0x7d1)
> >> >> >CHECKPOINT : 0x0
> >> >> >WAIT_HINT : 0x0
> >> >> >PID : 0
> >> >> >FLAGS :
> >> >> >
> >> >> >I hope that helps.
> >> >> >
> >> >> >Thanks
> >> >> >Jim
> >> >> >>-----Original Message-----
> >> >> >>I've never been able to share files across my home
> >> >> >network
> >> >> >>from my XP Home system, but it's never been a
> problem
> >> >> >>because the XP Home system could see the other PCs
> on
> >> >> the
> >> >> >>network. I just do all the file movement from the
> XP
> >> >> >>machine.
> >> >> >>
> >> >> >>I decided to diagnose the problem today, since I
> just
> >> >> >>bought a laptop that also has XP Home, thinking I
> >> might
> >> >> >be
> >> >> >>able to swap files and fix the problem. When I
> looked
> >> >> >>through the services, I found the Server service
> >> >> >>(LanManServer) was not running, although it was
> set to
> >> >> >>start automatically. When I try to start the
> >> service, I
> >> >> >>get Error 2001: The Specified Driver is Invalid.
> >> >> >>
> >> >> >>I understand hardware drivers, and know how to
> figure
> >> >> out
> >> >> >>a problem in device manager. But I don't have a
> clue
> >> >> >what
> >> >> >>driver this error is referring to. Other services
> >> >> >>provided by the SVCHOST.EXE file seem to be working
> >> fine.
> >> >> >>
> >> >> >>Can anyone provide a clue as to what I should do
> next?
> >> >> >>
> >> >> >>I would appreciate an e-mail, but will check back
> here
> >> >> >>tomorrow.
> >> >> >>
> >> >> >>Jim
> >> >> >>.
> >> >> >>
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
|
Similar Threads
