Re: Configuring audio in BootCamp Windows 10

['Janina Sajka' via MacVisionaries]

Hi, Gena:

I would strongly advise against reinstalling Windows. At least in my
experience, it's far too much of a hit and miss proposition, and mostly
miss. I think it'll be far easier fixing whatever ails, since you know
you have a working install that you can get at over USB in the worst
case instance.

Just my two cents.

Janina

Georgina Joyce writes:
> Hello Simon and Janina,
> 
> Well, I thought I had. For some reason every now and again upon boot the mute 
> is applied. I shall reinstall bootcamp drivers again. Hopefully, it will 
> settle down.
> 
> But likewise I thank you both for your input. I was going to give up having 
> installed Windows 10 3 times. Let’s hope it’s third time lucky. Now I know 
> what the problem is I’m not going to wipe it out and start again. As I’m 
> confident that it is not something I did wrong, or corrupted file downloads.
> 
> It’s interesting that we think of Apple products being the same but issues 
> like this show that from a software driver point of view Apple has variations 
> from year to year.
> 
> Best regards,
> 
> Gena
> 
> Call: M0EBP
> Loc: IO83PS
> 
> 
> 
> > On 13 Jan 2018, at 15:56, 'Janina Sajka' via MacVisionaries 
> >  wrote:
> > 
> > Glad to hear you got it going, Gena!
> > 
> > 
> > Thanks again for your support on this. 
> > 
> > Janina
> > 
> > Georgina Joyce writes:
> >> 
> >> Hello,
> >> 
> >> Thanks, Simon. Looking through the messages I remember seeing about F10 
> >> and I had tried it. I guess I did it just once and muted it. Because now I 
> >> just pressed F10 and have NVDA droning way.
> >> 
> >> So I’m happy and can go out shopping now.
> >> 
> >> Gena
> >> 
> >> “Blindness is not a handicap, it is something I have always lived with. 
> >> The real handicap is the prejudices people have about blindness.”
> >> 
> >> Michael Hinson 2011
> >> 
> >>> On 12 Jan 2018, at 09:40, Georgina Joyce  wrote:
> >>> 
> >>> Hello Janina,
> >>> 
> >>> Yes, I discover that I have not had the missing directory problem. 
> >>> Looking on the USB stick from which I installed windows and the 
> >>> subsequent driver install via bootcamp have the $WinPeDriver$ directory. 
> >>> Using my iPhone and seeing AI I’m able to get fragments of text read but 
> >>> obviously it can’t tell me what has focus . But twice I’ve had Windows 
> >>> installer has stopped working. Both of these were done from a fresh 
> >>> bootcamp driver download. So I copied the audio driver into the root and 
> >>> run it from there. seeing AI tells me that I am in the driver 
> >>> installation wizard. After accepting Apple’s license terms. There’s some 
> >>> text about the there is a newer version already installed. So nearly 
> >>> 2a.m. I crawl to bed. I won’t write what I feel my next step will be at 
> >>> the moment.
> >>> 
> >>> I am going to train with a new Guide Dog on the 22nd and retire my 
> >>> current dog on this Sunday so I’ve got a lot to do while I can get out 
> >>> and about. So I’ll take my Mac either as a single or double boot machine 
> >>> with me on Guide dog training.
> >>> 
> >>> Dammed Computers………
> >>> 
> >>> 
> >>> Gena
> >>> 
> >>> Braille is a reading and writing language that all blind people should 
> >>> learn to use.
> >>> 
> >>> Michael Hingson 2011.
> >>> 
>  On 12 Jan 2018, at 06:51, 'Janina Sajka' via MacVisionaries 
>       >> wrote:
>  
>  Yes, at the root of the USB device.
>  
>  Later, I got the entire payload of drivers in that directory. However,
>  at the time I discovered this directory was missing, creating an empty
>  one proved sufficient to run the installation and, in my case, get audio
>  working natively from the builtin speakers.
>  
>  Gena, are you saying that even with a folder load of drivers and a
>  successful BootCamp install, you're still not getting audio?
>  
>  Georgina Joyce writes:
> > Hello,
> > 
> > Just to be clear this folder needs to be in the route of the USB stick? 
> > Using bootcamp to generate another set of drivers it puts the 
> > $WinPeDriver$ at the same level as the bootcamp folder. As my USB 
> > headset stopped working I tried to do it blindly. Seeing AI read that 
> > an installation was successful but the Air is still mute.
> > 
> > 
> > 
> > Gena
> > 
> > “Blindness is not a handicap, it is something I have always lived with. 
> > The real handicap is the prejudices people have about blindness.”
> > 
> > Michael Hinson 2011
> > 
> >> On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
> >>  >>  >>  

RE: Configuring audio in BootCamp Windows 10

[Simon Fogarty]

Have you checked apple to see if there is actually bootcamp drivers or should I 
say an update to the bootcamp drivers?

From: macvisionaries@googlegroups.com [mailto:macvisionaries@googlegroups.com] 
On Behalf Of Georgina Joyce
Sent: Sunday, 14 January 2018 5:28 AM
To: AppleVis List <macvisionaries@googlegroups.com>
Subject: Re: Configuring audio in BootCamp Windows 10

Hello Simon and Janina,

Well, I thought I had. For some reason every now and again upon boot the mute 
is applied. I shall reinstall bootcamp drivers again. Hopefully, it will settle 
down.

But likewise I thank you both for your input. I was going to give up having 
installed Windows 10 3 times. Let’s hope it’s third time lucky. Now I know what 
the problem is I’m not going to wipe it out and start again. As I’m confident 
that it is not something I did wrong, or corrupted file downloads.

It’s interesting that we think of Apple products being the same but issues like 
this show that from a software driver point of view Apple has variations from 
year to year.

Best regards,

Gena

Call: M0EBP
Loc: IO83PS



On 13 Jan 2018, at 15:56, 'Janina Sajka' via MacVisionaries 
<macvisionaries@googlegroups.com<mailto:macvisionaries@googlegroups.com>> wrote:

Glad to hear you got it going, Gena!


Thanks again for your support on this.

Janina

Georgina Joyce writes:


Hello,

Thanks, Simon. Looking through the messages I remember seeing about F10 and I 
had tried it. I guess I did it just once and muted it. Because now I just 
pressed F10 and have NVDA droning way.

So I’m happy and can go out shopping now.

Gena

“Blindness is not a handicap, it is something I have always lived with. The 
real handicap is the prejudices people have about blindness.”

Michael Hinson 2011


On 12 Jan 2018, at 09:40, Georgina Joyce 
<g...@gena-j.me.uk<mailto:g...@gena-j.me.uk>> wrote:

Hello Janina,

Yes, I discover that I have not had the missing directory problem. Looking on 
the USB stick from which I installed windows and the subsequent driver install 
via bootcamp have the $WinPeDriver$ directory. Using my iPhone and seeing AI 
I’m able to get fragments of text read but obviously it can’t tell me what has 
focus . But twice I’ve had Windows installer has stopped working. Both of these 
were done from a fresh bootcamp driver download. So I copied the audio driver 
into the root and run it from there. seeing AI tells me that I am in the driver 
installation wizard. After accepting Apple’s license terms. There’s some text 
about the there is a newer version already installed. So nearly 2a.m. I crawl 
to bed. I won’t write what I feel my next step will be at the moment.

I am going to train with a new Guide Dog on the 22nd and retire my current dog 
on this Sunday so I’ve got a lot to do while I can get out and about. So I’ll 
take my Mac either as a single or double boot machine with me on Guide dog 
training.

Dammed Computers………


Gena

Braille is a reading and writing language that all blind people should learn to 
use.

Michael Hingson 2011.


On 12 Jan 2018, at 06:51, 'Janina Sajka' via MacVisionaries 
<macvisionaries@googlegroups.com<mailto:macvisionaries@googlegroups.com><mailto:macvisionaries@googlegroups.com>>
 wrote:

Yes, at the root of the USB device.

Later, I got the entire payload of drivers in that directory. However,
at the time I discovered this directory was missing, creating an empty
one proved sufficient to run the installation and, in my case, get audio
working natively from the builtin speakers.

Gena, are you saying that even with a folder load of drivers and a
successful BootCamp install, you're still not getting audio?

Georgina Joyce writes:

Hello,

Just to be clear this folder needs to be in the route of the USB stick? Using 
bootcamp to generate another set of drivers it puts the $WinPeDriver$ at the 
same level as the bootcamp folder. As my USB headset stopped working I tried to 
do it blindly. Seeing AI read that an installation was successful but the Air 
is still mute.



Gena

“Blindness is not a handicap, it is something I have always lived with. The 
real handicap is the prejudices people have about blindness.”

Michael Hinson 2011


On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
<macvisionaries@googlegroups.com<mailto:macvisionaries@googlegroups.com><mailto:macvisionaries@googlegroups.com>>
 wrote:

I got it sorted! Alleluia!

BootCamp drivers most certainly failed to install during the initial
Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:

$WinPEDriver$ folder not found

Following guidance I found at:
https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it<https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it>

I created the missing folder via my Linux console and reran the above
command. This made Windows happy. Ins

Re: Configuring audio in BootCamp Windows 10

[Georgina Joyce]

Hello Simon and Janina,

Well, I thought I had. For some reason every now and again upon boot the mute 
is applied. I shall reinstall bootcamp drivers again. Hopefully, it will settle 
down.

But likewise I thank you both for your input. I was going to give up having 
installed Windows 10 3 times. Let’s hope it’s third time lucky. Now I know what 
the problem is I’m not going to wipe it out and start again. As I’m confident 
that it is not something I did wrong, or corrupted file downloads.

It’s interesting that we think of Apple products being the same but issues like 
this show that from a software driver point of view Apple has variations from 
year to year.

Best regards,

Gena

Call: M0EBP
Loc: IO83PS



> On 13 Jan 2018, at 15:56, 'Janina Sajka' via MacVisionaries 
>  wrote:
> 
> Glad to hear you got it going, Gena!
> 
> 
> Thanks again for your support on this. 
> 
> Janina
> 
> Georgina Joyce writes:
>> 
>> Hello,
>> 
>> Thanks, Simon. Looking through the messages I remember seeing about F10 and 
>> I had tried it. I guess I did it just once and muted it. Because now I just 
>> pressed F10 and have NVDA droning way.
>> 
>> So I’m happy and can go out shopping now.
>> 
>> Gena
>> 
>> “Blindness is not a handicap, it is something I have always lived with. The 
>> real handicap is the prejudices people have about blindness.”
>> 
>> Michael Hinson 2011
>> 
>>> On 12 Jan 2018, at 09:40, Georgina Joyce  wrote:
>>> 
>>> Hello Janina,
>>> 
>>> Yes, I discover that I have not had the missing directory problem. Looking 
>>> on the USB stick from which I installed windows and the subsequent driver 
>>> install via bootcamp have the $WinPeDriver$ directory. Using my iPhone and 
>>> seeing AI I’m able to get fragments of text read but obviously it can’t 
>>> tell me what has focus . But twice I’ve had Windows installer has stopped 
>>> working. Both of these were done from a fresh bootcamp driver download. So 
>>> I copied the audio driver into the root and run it from there. seeing AI 
>>> tells me that I am in the driver installation wizard. After accepting 
>>> Apple’s license terms. There’s some text about the there is a newer version 
>>> already installed. So nearly 2a.m. I crawl to bed. I won’t write what I 
>>> feel my next step will be at the moment.
>>> 
>>> I am going to train with a new Guide Dog on the 22nd and retire my current 
>>> dog on this Sunday so I’ve got a lot to do while I can get out and about. 
>>> So I’ll take my Mac either as a single or double boot machine with me on 
>>> Guide dog training.
>>> 
>>> Dammed Computers………
>>> 
>>> 
>>> Gena
>>> 
>>> Braille is a reading and writing language that all blind people should 
>>> learn to use.
>>> 
>>> Michael Hingson 2011.
>>> 
 On 12 Jan 2018, at 06:51, 'Janina Sajka' via MacVisionaries 
 >> wrote:
 
 Yes, at the root of the USB device.
 
 Later, I got the entire payload of drivers in that directory. However,
 at the time I discovered this directory was missing, creating an empty
 one proved sufficient to run the installation and, in my case, get audio
 working natively from the builtin speakers.
 
 Gena, are you saying that even with a folder load of drivers and a
 successful BootCamp install, you're still not getting audio?
 
 Georgina Joyce writes:
> Hello,
> 
> Just to be clear this folder needs to be in the route of the USB stick? 
> Using bootcamp to generate another set of drivers it puts the 
> $WinPeDriver$ at the same level as the bootcamp folder. As my USB headset 
> stopped working I tried to do it blindly. Seeing AI read that an 
> installation was successful but the Air is still mute.
> 
> 
> 
> Gena
> 
> “Blindness is not a handicap, it is something I have always lived with. 
> The real handicap is the prejudices people have about blindness.”
> 
> Michael Hinson 2011
> 
>> On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
>> > >  >> wrote:
>> 
>> I got it sorted! Alleluia!
>> 
>> BootCamp drivers most certainly failed to install during the initial
>> Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:
>> 
>> $WinPEDriver$ folder not found
>> 
>> Following guidance I found at:
>> https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it
>>  
>> 

Re: Configuring audio in BootCamp Windows 10

['Janina Sajka' via MacVisionaries]

Glad to hear you got it going, Gena!


Thanks again for your support on this. 

Janina

Georgina Joyce writes:
> 
> Hello,
> 
> Thanks, Simon. Looking through the messages I remember seeing about F10 and I 
> had tried it. I guess I did it just once and muted it. Because now I just 
> pressed F10 and have NVDA droning way.
> 
> So I’m happy and can go out shopping now.
> 
> Gena
> 
> “Blindness is not a handicap, it is something I have always lived with. The 
> real handicap is the prejudices people have about blindness.”
> 
> Michael Hinson 2011
> 
> > On 12 Jan 2018, at 09:40, Georgina Joyce  wrote:
> > 
> > Hello Janina,
> > 
> > Yes, I discover that I have not had the missing directory problem. Looking 
> > on the USB stick from which I installed windows and the subsequent driver 
> > install via bootcamp have the $WinPeDriver$ directory. Using my iPhone and 
> > seeing AI I’m able to get fragments of text read but obviously it can’t 
> > tell me what has focus . But twice I’ve had Windows installer has stopped 
> > working. Both of these were done from a fresh bootcamp driver download. So 
> > I copied the audio driver into the root and run it from there. seeing AI 
> > tells me that I am in the driver installation wizard. After accepting 
> > Apple’s license terms. There’s some text about the there is a newer version 
> > already installed. So nearly 2a.m. I crawl to bed. I won’t write what I 
> > feel my next step will be at the moment.
> > 
> > I am going to train with a new Guide Dog on the 22nd and retire my current 
> > dog on this Sunday so I’ve got a lot to do while I can get out and about. 
> > So I’ll take my Mac either as a single or double boot machine with me on 
> > Guide dog training.
> > 
> > Dammed Computers………
> > 
> > 
> > Gena
> > 
> > Braille is a reading and writing language that all blind people should 
> > learn to use.
> > 
> > Michael Hingson 2011.
> > 
> >> On 12 Jan 2018, at 06:51, 'Janina Sajka' via MacVisionaries 
> >> > 
> >> wrote:
> >> 
> >> Yes, at the root of the USB device.
> >> 
> >> Later, I got the entire payload of drivers in that directory. However,
> >> at the time I discovered this directory was missing, creating an empty
> >> one proved sufficient to run the installation and, in my case, get audio
> >> working natively from the builtin speakers.
> >> 
> >> Gena, are you saying that even with a folder load of drivers and a
> >> successful BootCamp install, you're still not getting audio?
> >> 
> >> Georgina Joyce writes:
> >>> Hello,
> >>> 
> >>> Just to be clear this folder needs to be in the route of the USB stick? 
> >>> Using bootcamp to generate another set of drivers it puts the 
> >>> $WinPeDriver$ at the same level as the bootcamp folder. As my USB headset 
> >>> stopped working I tried to do it blindly. Seeing AI read that an 
> >>> installation was successful but the Air is still mute.
> >>> 
> >>> 
> >>> 
> >>> Gena
> >>> 
> >>> “Blindness is not a handicap, it is something I have always lived with. 
> >>> The real handicap is the prejudices people have about blindness.”
> >>> 
> >>> Michael Hinson 2011
> >>> 
>  On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
>    > wrote:
>  
>  I got it sorted! Alleluia!
>  
>  BootCamp drivers most certainly failed to install during the initial
>  Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:
>  
>  $WinPEDriver$ folder not found
>  
>  Following guidance I found at:
>  https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it
>   
>  
>  
>  I created the missing folder via my Linux console and reran the above
>  command. This made Windows happy. Installation took about 3 minutes and
>  required a reboot.
>  
>  Windows 10 is now happily chattering via the builtin speakers on my
>  Airbook.
>  
>  Thanks especially to Gena for the suggestion to try using a USB
>  headphone. That gave me the screen reader I was lacking via the 3.5
>  audio jack on the Airbook.
>  
>  I'm so happy to be past this step. It's been driving me bonkers for
>  weeks and weeks.
>  
>  Thanks to everyone who took an interest and offered suggestions. I
>  appreciate your help very much.
>  
>  Janina
>  
>  'Janina Sajka' via MacVisionaries writes:
> > Hi, Gena:
> > 
> > I've changed the subject and disaccoiated the old thread -- hopefully
> > helpful should anyone go searching ...
> > 
> > The USB headphones are working. They're giving me access to both NVDA
> > and Narrator in the Windows 10 installation on my 

Re: Configuring audio in BootCamp Windows 10

['Janina Sajka' via MacVisionaries]

Thanks, Simon. And thanks also to Gena for suggesting USB headphones.
Had I gone to those sooner, it would have still been a fully accessible
install process, even with the breakage in BootCamp driver installation.

There are other gotchyas I ran into that are probably worth documenting.
Some of these that come immediately to mind:

1.) Put your USB stick on a USB2 port. According to an Apple page
about BootCamp, which I won't stop to find just now, USB3 isn't
supported for BootCamp.

2.) Make sure Disk Utility is happy with your USB stick. Should you
have accidentally removed it somewhere without unmounting it first,
BootCamp will complain, but it won't complain for about 20 minutes.
Sloppy scripting, there, Apple!

3.) Make sure your Apple drive's Mac partitions take up the entire
drive. BootCamp won't be happy if you've repartitioned in various ways,
and it won't tell you for a good hour into the process.

4.) You need to babysit the BootCamp process. While it may seem oK
to go away and get something unrelated accomplished while you waith for
the slow BootCamp process to run, that isn't safe. Eventually, BootCamp
will prompt for your password and that starts a clock. If you don't
respond in what it considers a reasonable amount of time, the entire
process may blow up, and you'll have to start over again from scratch. I
got a "BootCamp Busy" message which I couldn't get out of except by
rebooting or by killing the PID from an ssh session into the Mac.

5.) Don't despair of the Windows side of the installation aborts.
This happened to me many times, some dozen times, before it finally
worked. Windows would be "Preparing files for installation" and reading
out a percentage. Then, suddenly, it would abort where the only option
is to hit OK and reboot the machine. Very, Very frustrating, but there's
quite a bit of discussion on line where people have had the same
experience. Eventually, it will work, provided your Mac is on the
supported list that Apple publishes.


Simon Fogarty writes:
> Hey Janina 
> 
> Great work, and sticking with it.
> 
> I'mm going to keep this on file somewhere in case I get the same issue when 
> upgrading.
> -Original Message-
> From: 'Janina Sajka' via MacVisionaries 
> [mailto:macvisionaries@googlegroups.com] 
> Sent: Friday, 12 January 2018 6:14 AM
> To: 'Janina Sajka' via MacVisionaries <macvisionaries@googlegroups.com>
> Subject: Re: Configuring audio in BootCamp Windows 10
> 
> I got it sorted! Alleluia!
> 
> BootCamp drivers most certainly failed to install during the initial Windows 
> installation. Launching d:\BootCamp\Setup.exe yielded the error:
> 
> $WinPEDriver$ folder not found
> 
> Following guidance I found at:
> https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it
> 
> I created the missing folder via my Linux console and reran the above 
> command. This made Windows happy. Installation took about 3 minutes and 
> required a reboot.
> 
> Windows 10 is now happily chattering via the builtin speakers on my Airbook.
> 
> Thanks especially to Gena for the suggestion to try using a USB headphone. 
> That gave me the screen reader I was lacking via the 3.5 audio jack on the 
> Airbook.
> 
> I'm so happy to be past this step. It's been driving me bonkers for weeks and 
> weeks.
> 
> Thanks to everyone who took an interest and offered suggestions. I appreciate 
> your help very much.
> 
> Janina
> 
> 'Janina Sajka' via MacVisionaries writes:
> > Hi, Gena:
> > 
> > I've changed the subject and disaccoiated the old thread -- hopefully 
> > helpful should anyone go searching ...
> > 
> > The USB headphones are working. They're giving me access to both NVDA 
> > and Narrator in the Windows 10 installation on my Airbook. Strange as 
> > this will sound, I'm actually getting the best info by running NVDA 
> > and Narrator simultaneously! Wierd, but effective for the moment.
> > 
> > Here's the latest iteration of the problem ...
> > 
> > I can launch the Setup.exe in the BootCamp folder on my USB stick.
> > However, it immediately errors out complaining of a missing folder 
> > whose exact name I couldn't quite catch. I haven't gone back to the 
> > Narrator docs to learn how to get character by character screen 
> > review--that's next.
> > 
> > The missing folder is something like:
> > 
> > $WinPC
> > 
> > I have confirmed via my Linux machine that it is indeed missing from 
> > the USB stick. So, this sounds like some kind of BootCamp error? I 
> > think I'll need to get the exact spelling in order to Google the problem.
> > 
> > PS: Want to hear something really wierd? NVDA's audio son

RE: Configuring audio in BootCamp Windows 10

[Simon Fogarty]

Great prioroitys

Now have speech can go shopping.

From: macvisionaries@googlegroups.com [mailto:macvisionaries@googlegroups.com] 
On Behalf Of Georgina Joyce
Sent: Friday, 12 January 2018 10:56 PM
To: AppleVis List <macvisionaries@googlegroups.com>
Subject: Re: Configuring audio in BootCamp Windows 10


Hello,

Thanks, Simon. Looking through the messages I remember seeing about F10 and I 
had tried it. I guess I did it just once and muted it. Because now I just 
pressed F10 and have NVDA droning way.

So I’m happy and can go out shopping now.

Gena

“Blindness is not a handicap, it is something I have always lived with. The 
real handicap is the prejudices people have about blindness.”

Michael Hinson 2011

On 12 Jan 2018, at 09:40, Georgina Joyce 
<g...@gena-j.me.uk<mailto:g...@gena-j.me.uk>> wrote:

Hello Janina,

Yes, I discover that I have not had the missing directory problem. Looking on 
the USB stick from which I installed windows and the subsequent driver install 
via bootcamp have the $WinPeDriver$ directory. Using my iPhone and seeing AI 
I’m able to get fragments of text read but obviously it can’t tell me what has 
focus . But twice I’ve had Windows installer has stopped working. Both of these 
were done from a fresh bootcamp driver download. So I copied the audio driver 
into the root and run it from there. seeing AI tells me that I am in the driver 
installation wizard. After accepting Apple’s license terms. There’s some text 
about the there is a newer version already installed. So nearly 2a.m. I crawl 
to bed. I won’t write what I feel my next step will be at the moment.

I am going to train with a new Guide Dog on the 22nd and retire my current dog 
on this Sunday so I’ve got a lot to do while I can get out and about. So I’ll 
take my Mac either as a single or double boot machine with me on Guide dog 
training.

Dammed Computers………


Gena

Braille is a reading and writing language that all blind people should learn to 
use.

Michael Hingson 2011.

On 12 Jan 2018, at 06:51, 'Janina Sajka' via MacVisionaries 
<macvisionaries@googlegroups.com<mailto:macvisionaries@googlegroups.com>> wrote:

Yes, at the root of the USB device.

Later, I got the entire payload of drivers in that directory. However,
at the time I discovered this directory was missing, creating an empty
one proved sufficient to run the installation and, in my case, get audio
working natively from the builtin speakers.

Gena, are you saying that even with a folder load of drivers and a
successful BootCamp install, you're still not getting audio?

Georgina Joyce writes:

Hello,

Just to be clear this folder needs to be in the route of the USB stick? Using 
bootcamp to generate another set of drivers it puts the $WinPeDriver$ at the 
same level as the bootcamp folder. As my USB headset stopped working I tried to 
do it blindly. Seeing AI read that an installation was successful but the Air 
is still mute.



Gena

“Blindness is not a handicap, it is something I have always lived with. The 
real handicap is the prejudices people have about blindness.”

Michael Hinson 2011


On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
<macvisionaries@googlegroups.com<mailto:macvisionaries@googlegroups.com>> wrote:

I got it sorted! Alleluia!

BootCamp drivers most certainly failed to install during the initial
Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:

$WinPEDriver$ folder not found

Following guidance I found at:
https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it

I created the missing folder via my Linux console and reran the above
command. This made Windows happy. Installation took about 3 minutes and
required a reboot.

Windows 10 is now happily chattering via the builtin speakers on my
Airbook.

Thanks especially to Gena for the suggestion to try using a USB
headphone. That gave me the screen reader I was lacking via the 3.5
audio jack on the Airbook.

I'm so happy to be past this step. It's been driving me bonkers for
weeks and weeks.

Thanks to everyone who took an interest and offered suggestions. I
appreciate your help very much.

Janina

'Janina Sajka' via MacVisionaries writes:

Hi, Gena:

I've changed the subject and disaccoiated the old thread -- hopefully
helpful should anyone go searching ...

The USB headphones are working. They're giving me access to both NVDA
and Narrator in the Windows 10 installation on my Airbook. Strange as
this will sound, I'm actually getting the best info by running NVDA and
Narrator simultaneously! Wierd, but effective for the moment.

Here's the latest iteration of the problem ...

I can launch the Setup.exe in the BootCamp folder on my USB stick.
However, it immediately errors out complaining of a missing folder whose
exact name I couldn't quite catch. I haven't gone back to the Narrator
docs to learn how to get character by character screen review--that's
n

Re: Configuring audio in BootCamp Windows 10

[Georgina Joyce]

Hello,

Thanks, Simon. Looking through the messages I remember seeing about F10 and I 
had tried it. I guess I did it just once and muted it. Because now I just 
pressed F10 and have NVDA droning way.

So I’m happy and can go out shopping now.

Gena

“Blindness is not a handicap, it is something I have always lived with. The 
real handicap is the prejudices people have about blindness.”

Michael Hinson 2011

> On 12 Jan 2018, at 09:40, Georgina Joyce  wrote:
> 
> Hello Janina,
> 
> Yes, I discover that I have not had the missing directory problem. Looking on 
> the USB stick from which I installed windows and the subsequent driver 
> install via bootcamp have the $WinPeDriver$ directory. Using my iPhone and 
> seeing AI I’m able to get fragments of text read but obviously it can’t tell 
> me what has focus . But twice I’ve had Windows installer has stopped working. 
> Both of these were done from a fresh bootcamp driver download. So I copied 
> the audio driver into the root and run it from there. seeing AI tells me that 
> I am in the driver installation wizard. After accepting Apple’s license 
> terms. There’s some text about the there is a newer version already 
> installed. So nearly 2a.m. I crawl to bed. I won’t write what I feel my next 
> step will be at the moment.
> 
> I am going to train with a new Guide Dog on the 22nd and retire my current 
> dog on this Sunday so I’ve got a lot to do while I can get out and about. So 
> I’ll take my Mac either as a single or double boot machine with me on Guide 
> dog training.
> 
> Dammed Computers………
> 
> 
> Gena
> 
> Braille is a reading and writing language that all blind people should learn 
> to use.
> 
> Michael Hingson 2011.
> 
>> On 12 Jan 2018, at 06:51, 'Janina Sajka' via MacVisionaries 
>> > 
>> wrote:
>> 
>> Yes, at the root of the USB device.
>> 
>> Later, I got the entire payload of drivers in that directory. However,
>> at the time I discovered this directory was missing, creating an empty
>> one proved sufficient to run the installation and, in my case, get audio
>> working natively from the builtin speakers.
>> 
>> Gena, are you saying that even with a folder load of drivers and a
>> successful BootCamp install, you're still not getting audio?
>> 
>> Georgina Joyce writes:
>>> Hello,
>>> 
>>> Just to be clear this folder needs to be in the route of the USB stick? 
>>> Using bootcamp to generate another set of drivers it puts the $WinPeDriver$ 
>>> at the same level as the bootcamp folder. As my USB headset stopped working 
>>> I tried to do it blindly. Seeing AI read that an installation was 
>>> successful but the Air is still mute.
>>> 
>>> 
>>> 
>>> Gena
>>> 
>>> “Blindness is not a handicap, it is something I have always lived with. The 
>>> real handicap is the prejudices people have about blindness.”
>>> 
>>> Michael Hinson 2011
>>> 
 On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
 > 
 wrote:
 
 I got it sorted! Alleluia!
 
 BootCamp drivers most certainly failed to install during the initial
 Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:
 
 $WinPEDriver$ folder not found
 
 Following guidance I found at:
 https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it
  
 
 
 I created the missing folder via my Linux console and reran the above
 command. This made Windows happy. Installation took about 3 minutes and
 required a reboot.
 
 Windows 10 is now happily chattering via the builtin speakers on my
 Airbook.
 
 Thanks especially to Gena for the suggestion to try using a USB
 headphone. That gave me the screen reader I was lacking via the 3.5
 audio jack on the Airbook.
 
 I'm so happy to be past this step. It's been driving me bonkers for
 weeks and weeks.
 
 Thanks to everyone who took an interest and offered suggestions. I
 appreciate your help very much.
 
 Janina
 
 'Janina Sajka' via MacVisionaries writes:
> Hi, Gena:
> 
> I've changed the subject and disaccoiated the old thread -- hopefully
> helpful should anyone go searching ...
> 
> The USB headphones are working. They're giving me access to both NVDA
> and Narrator in the Windows 10 installation on my Airbook. Strange as
> this will sound, I'm actually getting the best info by running NVDA and
> Narrator simultaneously! Wierd, but effective for the moment.
> 
> Here's the latest iteration of the problem ...
> 
> I can launch the Setup.exe in the BootCamp folder on my USB stick.
> However, it immediately errors out complaining of 

Re: Configuring audio in BootCamp Windows 10

[Georgina Joyce]

Hello Janina,

Yes, I discover that I have not had the missing directory problem. Looking on 
the USB stick from which I installed windows and the subsequent driver install 
via bootcamp have the $WinPeDriver$ directory. Using my iPhone and seeing AI 
I’m able to get fragments of text read but obviously it can’t tell me what has 
focus . But twice I’ve had Windows installer has stopped working. Both of these 
were done from a fresh bootcamp driver download. So I copied the audio driver 
into the root and run it from there. seeing AI tells me that I am in the driver 
installation wizard. After accepting Apple’s license terms. There’s some text 
about the there is a newer version already installed. So nearly 2a.m. I crawl 
to bed. I won’t write what I feel my next step will be at the moment.

I am going to train with a new Guide Dog on the 22nd and retire my current dog 
on this Sunday so I’ve got a lot to do while I can get out and about. So I’ll 
take my Mac either as a single or double boot machine with me on Guide dog 
training.

Dammed Computers………


Gena

Braille is a reading and writing language that all blind people should learn to 
use.

Michael Hingson 2011.

> On 12 Jan 2018, at 06:51, 'Janina Sajka' via MacVisionaries 
>  wrote:
> 
> Yes, at the root of the USB device.
> 
> Later, I got the entire payload of drivers in that directory. However,
> at the time I discovered this directory was missing, creating an empty
> one proved sufficient to run the installation and, in my case, get audio
> working natively from the builtin speakers.
> 
> Gena, are you saying that even with a folder load of drivers and a
> successful BootCamp install, you're still not getting audio?
> 
> Georgina Joyce writes:
>> Hello,
>> 
>> Just to be clear this folder needs to be in the route of the USB stick? 
>> Using bootcamp to generate another set of drivers it puts the $WinPeDriver$ 
>> at the same level as the bootcamp folder. As my USB headset stopped working 
>> I tried to do it blindly. Seeing AI read that an installation was successful 
>> but the Air is still mute.
>> 
>> 
>> 
>> Gena
>> 
>> “Blindness is not a handicap, it is something I have always lived with. The 
>> real handicap is the prejudices people have about blindness.”
>> 
>> Michael Hinson 2011
>> 
>>> On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
>>>  wrote:
>>> 
>>> I got it sorted! Alleluia!
>>> 
>>> BootCamp drivers most certainly failed to install during the initial
>>> Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:
>>> 
>>> $WinPEDriver$ folder not found
>>> 
>>> Following guidance I found at:
>>> https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it
>>> 
>>> I created the missing folder via my Linux console and reran the above
>>> command. This made Windows happy. Installation took about 3 minutes and
>>> required a reboot.
>>> 
>>> Windows 10 is now happily chattering via the builtin speakers on my
>>> Airbook.
>>> 
>>> Thanks especially to Gena for the suggestion to try using a USB
>>> headphone. That gave me the screen reader I was lacking via the 3.5
>>> audio jack on the Airbook.
>>> 
>>> I'm so happy to be past this step. It's been driving me bonkers for
>>> weeks and weeks.
>>> 
>>> Thanks to everyone who took an interest and offered suggestions. I
>>> appreciate your help very much.
>>> 
>>> Janina
>>> 
>>> 'Janina Sajka' via MacVisionaries writes:
 Hi, Gena:
 
 I've changed the subject and disaccoiated the old thread -- hopefully
 helpful should anyone go searching ...
 
 The USB headphones are working. They're giving me access to both NVDA
 and Narrator in the Windows 10 installation on my Airbook. Strange as
 this will sound, I'm actually getting the best info by running NVDA and
 Narrator simultaneously! Wierd, but effective for the moment.
 
 Here's the latest iteration of the problem ...
 
 I can launch the Setup.exe in the BootCamp folder on my USB stick.
 However, it immediately errors out complaining of a missing folder whose
 exact name I couldn't quite catch. I haven't gone back to the Narrator
 docs to learn how to get character by character screen review--that's
 next.
 
 The missing folder is something like:
 
 $WinPC
 
 I have confirmed via my Linux machine that it is indeed missing from the
 USB stick. So, this sounds like some kind of BootCamp error? I think
 I'll need to get the exact spelling in order to Google the problem.
 
 PS: Want to hear something really wierd? NVDA's audio sonicons are
 playing via the Airbook's internal speaker. But, I can't get TTS output
 there! Stranger and stranger.
 
 Janina
 
 Georgina Joyce writes:
> Hello Janina,
> 
> Well good but bad news. I’ve been using my MacBook Air’s bootcamp 
> 

RE: Configuring audio in BootCamp Windows 10

[Simon Fogarty]

Hey Janina 

Great work, and sticking with it.

I'mm going to keep this on file somewhere in case I get the same issue when 
upgrading.
-Original Message-
From: 'Janina Sajka' via MacVisionaries 
[mailto:macvisionaries@googlegroups.com] 
Sent: Friday, 12 January 2018 6:14 AM
To: 'Janina Sajka' via MacVisionaries <macvisionaries@googlegroups.com>
Subject: Re: Configuring audio in BootCamp Windows 10

I got it sorted! Alleluia!

BootCamp drivers most certainly failed to install during the initial Windows 
installation. Launching d:\BootCamp\Setup.exe yielded the error:

$WinPEDriver$ folder not found

Following guidance I found at:
https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it

I created the missing folder via my Linux console and reran the above command. 
This made Windows happy. Installation took about 3 minutes and required a 
reboot.

Windows 10 is now happily chattering via the builtin speakers on my Airbook.

Thanks especially to Gena for the suggestion to try using a USB headphone. That 
gave me the screen reader I was lacking via the 3.5 audio jack on the Airbook.

I'm so happy to be past this step. It's been driving me bonkers for weeks and 
weeks.

Thanks to everyone who took an interest and offered suggestions. I appreciate 
your help very much.

Janina

'Janina Sajka' via MacVisionaries writes:
> Hi, Gena:
> 
> I've changed the subject and disaccoiated the old thread -- hopefully 
> helpful should anyone go searching ...
> 
> The USB headphones are working. They're giving me access to both NVDA 
> and Narrator in the Windows 10 installation on my Airbook. Strange as 
> this will sound, I'm actually getting the best info by running NVDA 
> and Narrator simultaneously! Wierd, but effective for the moment.
> 
> Here's the latest iteration of the problem ...
> 
> I can launch the Setup.exe in the BootCamp folder on my USB stick.
> However, it immediately errors out complaining of a missing folder 
> whose exact name I couldn't quite catch. I haven't gone back to the 
> Narrator docs to learn how to get character by character screen 
> review--that's next.
> 
> The missing folder is something like:
> 
> $WinPC
> 
> I have confirmed via my Linux machine that it is indeed missing from 
> the USB stick. So, this sounds like some kind of BootCamp error? I 
> think I'll need to get the exact spelling in order to Google the problem.
> 
> PS: Want to hear something really wierd? NVDA's audio sonicons are 
> playing via the Airbook's internal speaker. But, I can't get TTS 
> output there! Stranger and stranger.
> 
> Janina
> 
> Georgina Joyce writes:
> > Hello Janina,
> > 
> > Well good but bad news. I’ve been using my MacBook Air’s bootcamp partition 
> > for about an hour. I’ve lost audio. Just plugged in my USB headset that I 
> > used to install Windows. It made the new hardware sound through the headset 
> > and NVDA announced installing software for the new device. So I have lost 
> > sound via it’s own speakers and have sound through an independent sound 
> > card. So you were right it’s a driver issue.
> > 
> > Now why should Windows mess about with a driver while it is in use?
> > 
> > Regards,
> > 
> > 
> > Gena
> > 
> > Georgina Joyce
> > Applied Psychologist
> > Training and Coaching.
> > Because individuals of groups matter!
> > 
> > 
> > 
> > 
> > 
> > > On 10 Jan 2018, at 15:52, Georgina Joyce <g...@gena-j.me.uk> wrote:
> > > 
> > > Hello Janina,
> > > 
> > > I think the blind keystrokes might be:
> > > 
> > > Open the run dialog box:
> > > cmd r, i.e. Windows r.
> > > 
> > > If you have a cd/DVD version the USB will be assigned E:\ if not it is 
> > > likely to be d:\. I don’t know the path structure of the unzipped package 
> > > so you’ll need to know it by exploring it on the Mac side of things. 
> > > Going by the article your run command should be:
> > > e:\windowsSupport\setup.ext
> > > 
> > > Windows will want you to allow changes so you need:
> > > opt Y i.e. alt y.
> > > 
> > > Then the article suggests you might need to click continue, so you might 
> > > need to:
> > > opt c i.e. alt c.
> > > 
> > > You might need to do a:
> > > opt f i.e alt f.
> > > 
> > > To finish.
> > > 
> > > Then a opt y i.e. alt y.
> > > 
> > > Answering yes to a reboot. Then hold on to something that gives you 
> > > security to see what happens.
> > > 
> > > HTH
> > > Gena
> > &g

Re: Configuring audio in BootCamp Windows 10

['Janina Sajka' via MacVisionaries]

Yes, at the root of the USB device.

Later, I got the entire payload of drivers in that directory. However,
at the time I discovered this directory was missing, creating an empty
one proved sufficient to run the installation and, in my case, get audio
working natively from the builtin speakers.

Gena, are you saying that even with a folder load of drivers and a
successful BootCamp install, you're still not getting audio?

Georgina Joyce writes:
> Hello,
> 
> Just to be clear this folder needs to be in the route of the USB stick? Using 
> bootcamp to generate another set of drivers it puts the $WinPeDriver$ at the 
> same level as the bootcamp folder. As my USB headset stopped working I tried 
> to do it blindly. Seeing AI read that an installation was successful but the 
> Air is still mute.
> 
> 
> 
> Gena
> 
> “Blindness is not a handicap, it is something I have always lived with. The 
> real handicap is the prejudices people have about blindness.”
> 
> Michael Hinson 2011
> 
> > On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
> >  wrote:
> > 
> > I got it sorted! Alleluia!
> > 
> > BootCamp drivers most certainly failed to install during the initial
> > Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:
> > 
> > $WinPEDriver$ folder not found
> > 
> > Following guidance I found at:
> > https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it
> > 
> > I created the missing folder via my Linux console and reran the above
> > command. This made Windows happy. Installation took about 3 minutes and
> > required a reboot.
> > 
> > Windows 10 is now happily chattering via the builtin speakers on my
> > Airbook.
> > 
> > Thanks especially to Gena for the suggestion to try using a USB
> > headphone. That gave me the screen reader I was lacking via the 3.5
> > audio jack on the Airbook.
> > 
> > I'm so happy to be past this step. It's been driving me bonkers for
> > weeks and weeks.
> > 
> > Thanks to everyone who took an interest and offered suggestions. I
> > appreciate your help very much.
> > 
> > Janina
> > 
> > 'Janina Sajka' via MacVisionaries writes:
> >> Hi, Gena:
> >> 
> >> I've changed the subject and disaccoiated the old thread -- hopefully
> >> helpful should anyone go searching ...
> >> 
> >> The USB headphones are working. They're giving me access to both NVDA
> >> and Narrator in the Windows 10 installation on my Airbook. Strange as
> >> this will sound, I'm actually getting the best info by running NVDA and
> >> Narrator simultaneously! Wierd, but effective for the moment.
> >> 
> >> Here's the latest iteration of the problem ...
> >> 
> >> I can launch the Setup.exe in the BootCamp folder on my USB stick.
> >> However, it immediately errors out complaining of a missing folder whose
> >> exact name I couldn't quite catch. I haven't gone back to the Narrator
> >> docs to learn how to get character by character screen review--that's
> >> next.
> >> 
> >> The missing folder is something like:
> >> 
> >> $WinPC
> >> 
> >> I have confirmed via my Linux machine that it is indeed missing from the
> >> USB stick. So, this sounds like some kind of BootCamp error? I think
> >> I'll need to get the exact spelling in order to Google the problem.
> >> 
> >> PS: Want to hear something really wierd? NVDA's audio sonicons are
> >> playing via the Airbook's internal speaker. But, I can't get TTS output
> >> there! Stranger and stranger.
> >> 
> >> Janina
> >> 
> >> Georgina Joyce writes:
> >>> Hello Janina,
> >>> 
> >>> Well good but bad news. I’ve been using my MacBook Air’s bootcamp 
> >>> partition for about an hour. I’ve lost audio. Just plugged in my USB 
> >>> headset that I used to install Windows. It made the new hardware sound 
> >>> through the headset and NVDA announced installing software for the new 
> >>> device. So I have lost sound via it’s own speakers and have sound through 
> >>> an independent sound card. So you were right it’s a driver issue.
> >>> 
> >>> Now why should Windows mess about with a driver while it is in use?
> >>> 
> >>> Regards,
> >>> 
> >>> 
> >>> Gena
> >>> 
> >>> Georgina Joyce
> >>> Applied Psychologist
> >>> Training and Coaching.
> >>> Because individuals of groups matter!
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
>  On 10 Jan 2018, at 15:52, Georgina Joyce  wrote:
>  
>  Hello Janina,
>  
>  I think the blind keystrokes might be:
>  
>  Open the run dialog box:
>  cmd r, i.e. Windows r.
>  
>  If you have a cd/DVD version the USB will be assigned E:\ if not it is 
>  likely to be d:\. I don’t know the path structure of the unzipped 
>  package so you’ll need to know it by exploring it on the Mac side of 
>  things. Going by the article your run command should be:
>  e:\windowsSupport\setup.ext
>  
>  Windows will want you to allow changes so you need:
>  opt Y i.e. alt y.
>  

Re: Configuring audio in BootCamp Windows 10

[Georgina Joyce]

Hello,

Just to be clear this folder needs to be in the route of the USB stick? Using 
bootcamp to generate another set of drivers it puts the $WinPeDriver$ at the 
same level as the bootcamp folder. As my USB headset stopped working I tried to 
do it blindly. Seeing AI read that an installation was successful but the Air 
is still mute.



Gena

“Blindness is not a handicap, it is something I have always lived with. The 
real handicap is the prejudices people have about blindness.”

Michael Hinson 2011

> On 11 Jan 2018, at 17:13, 'Janina Sajka' via MacVisionaries 
>  wrote:
> 
> I got it sorted! Alleluia!
> 
> BootCamp drivers most certainly failed to install during the initial
> Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:
> 
> $WinPEDriver$ folder not found
> 
> Following guidance I found at:
> https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it
> 
> I created the missing folder via my Linux console and reran the above
> command. This made Windows happy. Installation took about 3 minutes and
> required a reboot.
> 
> Windows 10 is now happily chattering via the builtin speakers on my
> Airbook.
> 
> Thanks especially to Gena for the suggestion to try using a USB
> headphone. That gave me the screen reader I was lacking via the 3.5
> audio jack on the Airbook.
> 
> I'm so happy to be past this step. It's been driving me bonkers for
> weeks and weeks.
> 
> Thanks to everyone who took an interest and offered suggestions. I
> appreciate your help very much.
> 
> Janina
> 
> 'Janina Sajka' via MacVisionaries writes:
>> Hi, Gena:
>> 
>> I've changed the subject and disaccoiated the old thread -- hopefully
>> helpful should anyone go searching ...
>> 
>> The USB headphones are working. They're giving me access to both NVDA
>> and Narrator in the Windows 10 installation on my Airbook. Strange as
>> this will sound, I'm actually getting the best info by running NVDA and
>> Narrator simultaneously! Wierd, but effective for the moment.
>> 
>> Here's the latest iteration of the problem ...
>> 
>> I can launch the Setup.exe in the BootCamp folder on my USB stick.
>> However, it immediately errors out complaining of a missing folder whose
>> exact name I couldn't quite catch. I haven't gone back to the Narrator
>> docs to learn how to get character by character screen review--that's
>> next.
>> 
>> The missing folder is something like:
>> 
>> $WinPC
>> 
>> I have confirmed via my Linux machine that it is indeed missing from the
>> USB stick. So, this sounds like some kind of BootCamp error? I think
>> I'll need to get the exact spelling in order to Google the problem.
>> 
>> PS: Want to hear something really wierd? NVDA's audio sonicons are
>> playing via the Airbook's internal speaker. But, I can't get TTS output
>> there! Stranger and stranger.
>> 
>> Janina
>> 
>> Georgina Joyce writes:
>>> Hello Janina,
>>> 
>>> Well good but bad news. I’ve been using my MacBook Air’s bootcamp partition 
>>> for about an hour. I’ve lost audio. Just plugged in my USB headset that I 
>>> used to install Windows. It made the new hardware sound through the headset 
>>> and NVDA announced installing software for the new device. So I have lost 
>>> sound via it’s own speakers and have sound through an independent sound 
>>> card. So you were right it’s a driver issue.
>>> 
>>> Now why should Windows mess about with a driver while it is in use?
>>> 
>>> Regards,
>>> 
>>> 
>>> Gena
>>> 
>>> Georgina Joyce
>>> Applied Psychologist
>>> Training and Coaching.
>>> Because individuals of groups matter!
>>> 
>>> 
>>> 
>>> 
>>> 
 On 10 Jan 2018, at 15:52, Georgina Joyce  wrote:
 
 Hello Janina,
 
 I think the blind keystrokes might be:
 
 Open the run dialog box:
 cmd r, i.e. Windows r.
 
 If you have a cd/DVD version the USB will be assigned E:\ if not it is 
 likely to be d:\. I don’t know the path structure of the unzipped package 
 so you’ll need to know it by exploring it on the Mac side of things. Going 
 by the article your run command should be:
 e:\windowsSupport\setup.ext
 
 Windows will want you to allow changes so you need:
 opt Y i.e. alt y.
 
 Then the article suggests you might need to click continue, so you might 
 need to:
 opt c i.e. alt c.
 
 You might need to do a:
 opt f i.e alt f.
 
 To finish.
 
 Then a opt y i.e. alt y.
 
 Answering yes to a reboot. Then hold on to something that gives you 
 security to see what happens.
 
 HTH
 Gena
 
 “Why not?”
 
 Michael Hinson 2011
 
> On 10 Jan 2018, at 15:16, Georgina Joyce  > wrote:
> 
> Hello Janina,
> 
> Good to hear from you too.
> 
> Yes the first thing that needs to be done is to install the bootcamp 
> 

Re: Configuring audio in BootCamp Windows 10

['Janina Sajka' via MacVisionaries]

I got it sorted! Alleluia!

BootCamp drivers most certainly failed to install during the initial
Windows installation. Launching d:\BootCamp\Setup.exe yielded the error:

$WinPEDriver$ folder not found

Following guidance I found at:
https://stackoverflow.com/questions/33491592/bootcamp-drivers-lost-winpedriver-folder-how-to-create-it

I created the missing folder via my Linux console and reran the above
command. This made Windows happy. Installation took about 3 minutes and
required a reboot.

Windows 10 is now happily chattering via the builtin speakers on my
Airbook.

Thanks especially to Gena for the suggestion to try using a USB
headphone. That gave me the screen reader I was lacking via the 3.5
audio jack on the Airbook.

I'm so happy to be past this step. It's been driving me bonkers for
weeks and weeks.

Thanks to everyone who took an interest and offered suggestions. I
appreciate your help very much.

Janina

'Janina Sajka' via MacVisionaries writes:
> Hi, Gena:
> 
> I've changed the subject and disaccoiated the old thread -- hopefully
> helpful should anyone go searching ...
> 
> The USB headphones are working. They're giving me access to both NVDA
> and Narrator in the Windows 10 installation on my Airbook. Strange as
> this will sound, I'm actually getting the best info by running NVDA and
> Narrator simultaneously! Wierd, but effective for the moment.
> 
> Here's the latest iteration of the problem ...
> 
> I can launch the Setup.exe in the BootCamp folder on my USB stick.
> However, it immediately errors out complaining of a missing folder whose
> exact name I couldn't quite catch. I haven't gone back to the Narrator
> docs to learn how to get character by character screen review--that's
> next.
> 
> The missing folder is something like:
> 
> $WinPC
> 
> I have confirmed via my Linux machine that it is indeed missing from the
> USB stick. So, this sounds like some kind of BootCamp error? I think
> I'll need to get the exact spelling in order to Google the problem.
> 
> PS: Want to hear something really wierd? NVDA's audio sonicons are
> playing via the Airbook's internal speaker. But, I can't get TTS output
> there! Stranger and stranger.
> 
> Janina
> 
> Georgina Joyce writes:
> > Hello Janina,
> > 
> > Well good but bad news. I’ve been using my MacBook Air’s bootcamp partition 
> > for about an hour. I’ve lost audio. Just plugged in my USB headset that I 
> > used to install Windows. It made the new hardware sound through the headset 
> > and NVDA announced installing software for the new device. So I have lost 
> > sound via it’s own speakers and have sound through an independent sound 
> > card. So you were right it’s a driver issue.
> > 
> > Now why should Windows mess about with a driver while it is in use?
> > 
> > Regards,
> > 
> > 
> > Gena
> > 
> > Georgina Joyce
> > Applied Psychologist
> > Training and Coaching.
> > Because individuals of groups matter!
> > 
> > 
> > 
> > 
> > 
> > > On 10 Jan 2018, at 15:52, Georgina Joyce  wrote:
> > > 
> > > Hello Janina,
> > > 
> > > I think the blind keystrokes might be:
> > > 
> > > Open the run dialog box:
> > > cmd r, i.e. Windows r.
> > > 
> > > If you have a cd/DVD version the USB will be assigned E:\ if not it is 
> > > likely to be d:\. I don’t know the path structure of the unzipped package 
> > > so you’ll need to know it by exploring it on the Mac side of things. 
> > > Going by the article your run command should be:
> > > e:\windowsSupport\setup.ext
> > > 
> > > Windows will want you to allow changes so you need:
> > > opt Y i.e. alt y.
> > > 
> > > Then the article suggests you might need to click continue, so you might 
> > > need to:
> > > opt c i.e. alt c.
> > > 
> > > You might need to do a:
> > > opt f i.e alt f.
> > > 
> > > To finish.
> > > 
> > > Then a opt y i.e. alt y.
> > > 
> > > Answering yes to a reboot. Then hold on to something that gives you 
> > > security to see what happens.
> > > 
> > > HTH
> > > Gena
> > > 
> > > “Why not?”
> > > 
> > > Michael Hinson 2011
> > > 
> > >> On 10 Jan 2018, at 15:16, Georgina Joyce  > >> > wrote:
> > >> 
> > >> Hello Janina,
> > >> 
> > >> Good to hear from you too.
> > >> 
> > >> Yes the first thing that needs to be done is to install the bootcamp 
> > >> drivers. You needed to go to the system tray and bootcamp hangs out 
> > >> there. There must be a way of triggering the install from the run 
> > >> dialog. If that is the sate of the machine like installs with Narrator 
> > >> support a USB headset would provide audio. Did you use a USB headset 
> > >> that has it’s own sound card for the installation?
> > >> 
> > >> Looking on the web I think you should be able to run the setup.exe from 
> > >> the run dialog.
> > >> 
> > >> See here:
> > >> https://support.apple.com/en-gb/HT204923 
> > >> 
> > >> 
> > >> 
> > >> 
> > >> Gena
> > >> 
> > >> Call: M0EBP
> > >> Loc: