FAX problems

Folks, a while back I asked about a problem I had adding the Windows Fax 
components.

Thanks for all the tips, I got it going,, in no small part thanks to 
pointers from here.

Bar0 wrote:
> Folks, a while back I asked about a problem I had adding the Windows
> Fax components.
>
> Thanks for all the tips, I got it going,, in no small part thanks to
> pointers from here.

So did you just remove and replace from windows components or did you
have to do something more complicated?

-- 
Mike Easter
kibitzer, not SC admin

"Mike Easter" <MikeE@ster.invalid> wrote in message 
news:fsrd4u$97r$1@news.spamcop.net...
....
> So did you just remove and replace from windows components or did you
> have to do something more complicated?

The latter, with some "risk" It seems the problem relates to something
that 
happens upgrading SP1 systems to SP2 where FAX (and some other) services or 
programs have not yet been added pre SP2 upgrade. My situation exactly, as I 
bought the system around the release date, so the first action on taking 
delivery and configuring for the net on that PC was to run windows update, 
since the Dell allows you to create only one backup system image on the OEM 
Windoze that came with it.

So, there was a recommendation to rebuild the security database with 
esentutil, which M$oft recommended not doing, and there was a hotfix 
meanwhile that M$ issued, which I was able to get.

I installed the hotfix, with no result.

I fell back to the esentutil option (documented in an HP help) which solved 
the problem.

After that, I was able to use the Fax wizard which runs the add/remove 
components successfully, got a FAX printer, in the Printer "folder"
that 
actually worked, and the console in the Accessories list.

The risk is that the hotfix has not been upgraded to patch status, so who 
knows what else might be broken,  and the security database rebuild may be 
incomplete with the esentutil according to M$.

In any case the problem affects only certain kinds of installs or component 
additions, FAX happens to be one of several others that fail the same way.

Basically your pointer to the Microsoft ng got me there.