«

On Tue, 04 Dec 2007 06:23:59 GMT, impossible <>
wrote in <news:3o65j.230112$Fc.89110@attbi_s21>:

> "Nicolaas Hawkins" <> wrote in message
> news:1sauype0s6q77$....
>> On Tue, 04 Dec 2007 14:58:53 +1300, thingy <> wrote
>> in <news:uroe25->:
>>
>>> Nicolaas Hawkins wrote:
>>>
>>> 8><-------
>>>
>>>> I'm not having problems of that magnitude - I am not a games person at
>>>> all
>>>> and use it simply for Skype with the motherboard (Gigabyte GA7VM400M-RZ)
>>>> sound system.
>>>> Mic remains on in playback mode (where I don't need it) but every time I
>>>> make or receive a Skype call I have to go in and turn the funking thing
>>>> on
>>>> in record mode. It will then stay on until I re-boot, and then I have
>>>> to
>>>> turn it on again.
>>>> It will not stay turned on over a re-boot, the setting on 'record' mode
>>>> does not appear to be 'sticky' - but the setting in 'playback' mode is -
>>>> and, in the words of the finance company advert, "I ... just ... don't
>>>> ...
>>>> know ... why!"
>>>
>>> yes Im experimenting with IM using a webcam at the moment and skype
>>> soon....and I am finding its not going to be usable for the reason....
>>>
>>> Im hoping that a mic built into the USB2 webcam will at least get the IM
>>> and skype going........
>>>
>>> regards
>>>
>>> thing
>>
>> Just to add a detaill for clarity, I'm connecting via the sound port, not
>> USB.
>>
>> --
>
> Seen this?
>
> http://www.skype.com/help/guides/soundsetup_xp.html
>
> May not solve your problem. But since Skype's in play, possibly worth a
> look.

Thanks, I'll give a twice over.

--
Nicolaas.

In article <iime25->, thingy did write:

> ... dimdows.......

Muahahahaha!

On Tue, 04 Dec 2007 20:16:05 +1300, Lawrence D'Oliveiro
<_zealand> wrote in
<news:fj2urk$r3$>:

> In article <iime25->, thingy did write:
>
>> ... dimdows.......
>
> Muahahahaha!

Perfectly predictable response from a linuxtic weenie. Nothing to say,
but has to say something ... anything.

On Tue, 04 Dec 2007 14:19:46 +1300, thingy wrote:

> At the moment I am trying to find (via google) a windows registry
> setting that will stop this or lock it on....I'm wondering if there is
> something going on with front v rear jacks/pins....some articles talk
> about auto sensing which pair is being used....so I'm wondering if I
> need to lock it to the rear jack....as the "auto sense" (sounds like an
> oxy-moron to me) is not sensing which properly then disabling the input
> as it detects no jack is inserted.

Is this all related to the voice recognition software that is built into
WinXP and/or M$ Office 2003?


--
Jonathan Walker

"The IT industry landscape is littered with the dead
dreams of people who once trusted Microsoft."

Jonathan Walker wrote:
> On Tue, 04 Dec 2007 14:19:46 +1300, thingy wrote:
>
>> At the moment I am trying to find (via google) a windows registry
>> setting that will stop this or lock it on....I'm wondering if there is
>> something going on with front v rear jacks/pins....some articles talk
>> about auto sensing which pair is being used....so I'm wondering if I
>> need to lock it to the rear jack....as the "auto sense" (sounds like an
>> oxy-moron to me) is not sensing which properly then disabling the input
>> as it detects no jack is inserted.
>
> Is this all related to the voice recognition software that is built into
> WinXP and/or M$ Office 2003?
>
>

I'm not/wasnt aware XP has voice rec software....and no i dont have MS
office....oOo, yes but it is not installed at present as i just rebuilt
the box....the common problem seems to be BF2142 in terms of no mic on
three machines I have had it on all on differing hardware....this
disabling of the mic seems random and a new feature......

regards

Thing

"thingy" <> wrote in message
newscfe25-...
> Hi,
>
> Installed a new motherboard and for some un-known reason the mic in volume
> control does not appear....so going into properties and I click on
> recording device...OK now it is tehre but its muted....unclick mute and
> try and get voice to go...no joy....go back in and it is muted
> again.....and again and again...
>
> So any idea how to fix this bug/issue?
>
> regards
>
> thing

Does your soundcard or motherboard have a connector on it for a mic input on
the front of your case and if so have you made sure that the input you want
is selected, my motherboard has such a thing and unexpectedly to me the
front connector was selected by default when I only use the output from the
motherboard on the rear of the machine, the setting to change this was not
immediately obvious either.

On Wed, 05 Dec 2007 08:23:15 +1300, thingy wrote:

> I'm not/wasnt aware XP has voice rec software.

The Win2k boxes that we look after all have M$ Orifice installed and
luzers sometimes get random text printing all over the place.

The solution is to disable the voice recognition part of the Orifice suite
that the luzer "accidentally" enabled.


--
Jonathan Walker

"The IT industry landscape is littered with the dead
dreams of people who once trusted Microsoft."

Jonathan Walker wrote:
> On Wed, 05 Dec 2007 08:23:15 +1300, thingy wrote:
>
>> I'm not/wasnt aware XP has voice rec software.
>
> The Win2k boxes that we look after all have M$ Orifice installed and
> luzers sometimes get random text printing all over the place.
>
> The solution is to disable the voice recognition part of the Orifice suite
> that the luzer "accidentally" enabled.
>
>

Charming, calling users "luzers". I bet you're popular in the office. I
suppose you're skilled in their job?

On Wed, 05 Dec 2007 23:40:12 +1300, Bobs wrote:

> Charming, calling users "luzers". I bet you're popular in the office. I
> suppose you're skilled in their job?

Luzers are generally well behaved. If they're not, then treatment with a
Lart generally brings them back into line.


--
Jonathan Walker

"The IT industry landscape is littered with the dead
dreams of people who once trusted Microsoft."

On Wed, 05 Dec 2007 23:40:12 +1300, Bobs <>
wrote in <news:47568383$>:

> Jonathan Walker wrote:
>> On Wed, 05 Dec 2007 08:23:15 +1300, thingy wrote:
>>
>>> I'm not/wasnt aware XP has voice rec software.
>>
>> The Win2k boxes that we look after all have M$ Orifice installed and
>> luzers sometimes get random text printing all over the place.
>>
>> The solution is to disable the voice recognition part of the Orifice suite
>> that the luzer "accidentally" enabled.
>>
>
> Charming, calling users "luzers". I bet you're popular in the office. I
> suppose you're skilled in their job?

The language of a linsux weenie, Bobs.

--
Nicolaas.


.... The more we learn, the more we discover how much we still have to
learn. Wisdom lies in surviving this.