Re: Thank you for still trying

Same "copy error?"
You are not dealing with the same problem at all.
Read the first post. You problem does not match.
--
Russ Valentine
[MVP-Outlook]
"LarseeBear" <grandpaallen@xxxxxxxxxxx> wrote in message
news:eeVpsw3jFHA.1416@xxxxxxxxxxxxxxxxxxxxxxx
>I followed your instructions implicitly. There was no difference in my
>file fxsocm.inf and the one you sent me. So I used the fxsocm_modified.inf
>you sent for that contingency. Tried add/remove again and got the same
>copy error. So I rebooted and tried add/remove again-again the same copy
>error. So I put my original file fxsocm.inf back in the i386 folder as if
>nothing had happened.
>
> These were your instructions attendant with the zip attachment:
>
> I'm attaching a zip file here called faxocm.zip. This zip file contains
> two inf files: (a) fxsocm.inf & (b) fxsocm_modified.inf
>
> The first thing you need to do is compare your fxsocm.inf with (a) above
> and see if there are any differences, especially in the security line. If
> there is any difference, you can replace your fxsocm.inf with this file
> and try setting up fax.
>
> If there is no difference, you can then use the (b) file. All they've done
> there is remove the security section for the [Faxsvc.Service]. You can
> rename fxsocm_modified.inf file to fxsocm.inf and copy this over your
> existing fxsocm.inf and then try to setup the fax service. This will not
> set the ACE specifically on the fax service object (instead it picks the
> Windows default) and hence installation will most likely go through.
>
> In the above operations, you need to ensure that "Windows Resource
> Protection" is not replacing back the fxsocm.inf file with the file from
> the original Windows XP CD during the installation.
>
> I want to emphasize that this is still trying a work-around and the root
> problem still exists. I expect the you to face the same setup problem with
> some other services too - because most service will try "setting up ACE"
> for the service object. This problem most likely lies outside fax.
>
> Last point I want to mention is that if using fxsocm_modified.inf file
> solves the problem, this is not opening any big security holes.
>
> Russ Valentine
>
>


.

Relevant Pages

  • Re: "All fax printers are inaccessible" after Remove-then-Add Fax
    ... Russ Valentine ... You ask about my Windows XP version and source of installation files. ... The Microsoft Shared Fax Driver printer driver is not installed on ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Microsoft Fax Services
    ... Thanks to Russ Valentine for suggesting to look into Control Panel> Admin ... installation routine states it cannot find the necessary files). ... Printer Driver Microsoft Shared Fax Driver for Windows NT x86 ... Some, now cured, problems were definitely pre SP2. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Microsoft Fax Services and Shared Driver
    ... Russ Valentine ... [MVP-Outlook] ... Printer Driver Microsoft Shared Fax Driver for Windows NT x86 Version-3 ... Some, now cured, problems were definitely pre SP2. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: "All fax printers are inaccessible" after Remove-then-Add Fax
    ... Using calling cards with Windows XP Fax can be tricky to impossible. ... Russ Valentine ... [MVP-Outlook] ... You ask about my Windows XP version and source of installation ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Microsoft Fax Services
    ... Russ Valentine ... [MVP-Outlook] ... Printer Driver Microsoft Shared Fax Driver for Windows NT x86 Version-3 ... Some, now cured, problems were definitely pre SP2. ...
    (microsoft.public.windowsxp.print_fax)
Loading