Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Looking for Command LIne Solution - WinPE

Created: 01 Feb 2013 • Updated: 01 Feb 2013 | 11 comments

Currently we are ghosting machines to replicate them quickly.

In addition to the ghost squence, there are a few others things which can be batched.  My problem is that although the Ghost Image will 'BEEP' when complete, my others do not.  I have searched high and low for a way to make my machine BEEP to alert me when certain projects are complete, but none seem to work in the WinPE environment. 

Can someone tell me how I might send a beep to the PC Speaker, much in the same way Ghost does when completing? 


Comments 11 CommentsJump to latest comment

Marianne's picture

Hopefully this is more appropriate forum....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

andykn101's picture

Have you tried the CTRL-G beep code?

Open a command prompt and type "copy con beep.txt"

Then hold down the CTRL key and press G then Z. Release the CTRL key and press Enter.

Then test the file by typing "type beep.txt", make sure your speaker isn't muted.

Then try it in WinPE.

Found it here:

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

Doug.Morrow's picture

Thanks for the reply (and thanks for moving to the right forum)

I have tried teh CTRL+G code in numerous ways to no avail. 

I have also used numerous beep and buzzer type aps to do the trick, but none seems to work in WinPE. They work in Windows, under a command prompt, butnot in WinPE.  Now, I know that the PC Speaker is connected and working because A) the post beeps, and B) Ghost beeps when completing it's ghosting procedures. The question is how to utilize this feature from the prompt in Win PE. 

EdT's picture
set wshShell = Wscript.CreateObject("wscript.Shell")
beep = chr(007)
WshShell.Run "cmd /c @echo " & beep, 0

Should run fine if you save it as a vbs file and then run it by called wscript.exe <path to vbs file>

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Doug.Morrow's picture

Thanks for the reply. I've not worked with scripting before, but let me see if I did it right.
I opened a copy of Notepad, and pasted in the above code. Then I saved this as beep.vbs in the root of my WinPE boot Flash Drive.

From the WinPE command line I typed
wscript.exe beep.vbs[enter]

Unfortunately, doing this, WinPE says that Wscript is not a recognized program.

EdT's picture

Try just running beep.vbs on its own and let me know how you get on.  It occurs to me that the configuration of WinPE used in Ghost may not have all the additional functionality options included.

If you have a look at my article here:   you will find the procedure I adopted to create my own edition of WinPE with all the options loaded.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Doug.Morrow's picture

Running just 'beep.vbs' gets it asking for the program to run it. I have read the article you mentioned, and would greatly love to get a copy of the ISO for that WinPE. Any chance you'd consider sharing it?

EdT's picture

As it's so easy to roll your own, I have no plans to upload the ISO anywhere...;-)

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Doug.Morrow's picture

I will see what I can do, though much of the instructions seem beyond my humble talents.

Doug.Morrow's picture

We finally got a bootable flash set up and yet, that script does not work.  Any further ideas? 

EdT's picture

Are you testing on one specific machine?  I just wonder whether the hardware implementation of the speaker on your test machine is not quite the "standard" implementation and needs some sort of chipset driver in order to enable it so that standard script operations can function.

I suspect Ghost is driving the hardware port that the speaker is on, directly, or at least at a lower level than is used by script commands.

Simple test would be to boot the test machine using a DOS floppy or some other DOS boot method and try the beep command from there. If it does not work at that level, then that would suggest there may be a chipset driver requirement.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.