Sorry I forgot what is probably the most important here.
This misleading thing:
IDENT=HCF.HSF
is yet an other pain inflicted on users by the Microsoft way of assembling software.
To save the PC manufacturers the effort of installing the right driver matching the modem installed in the machine, the Microsoft drivers for the Conexant HSF and Conexant HCF drivers have been packed in one same file which also includes a wrapper detecting the actual installed modem! Just fine, twice the required memory wasted to load the driver, as well as disk space to store it, but who cares, the Windows customers pay, that's all.
Jacques
Paul Diptanu wrote:
Hi Antinio,
Sorry I am saying anything wrong about your comments.However if you are looking in the
section of "NAME="Audio device:" which says HCF.HSF then it may be wrong.As because I am
not concerned abouth the intel Audio device. I am looking for the driver for the
Connexant modem which scan moem says as HSF modem.belwow is the O/p of scanmodem for the
connexant that I attached in my previos/initial mail. I am again attaching the
scanmodem o/p if required for your review.
Predictive diagnostics for card in bus 01:02.0:
Modem chipset detected on
NAME="Communication controller: Conexant Unknown device 2f30 "
CLASS=0780
PCIDEV=14f1:2f30
SUBSYS=14f1:205d
HDA2=00:1b.0
IDENT=hsfmodem
Driver=hsfmodem-drivers
For candidate modem in: 01:02.0
0780 Communication controller: Conexant Unknown device 2f30
Primary device ID: 14f1:2f30
Support type needed or chipset: hsfmodem
I regret If I have written anything wrong
Thanking you again for your response.
