It's possible that your speakers won't work when your headphones are plugged in. Try connecting your speaker and headphones to a different USB port. Remember some speakers and apps have their own volume controls. Make sure the mute setting is not turned on, and try turning up all the volume controls. Make sure the power is turned on and check the volume level. Note: Some systems use a green jack for output and pink for mic input and others will be labeled "headphone" or "microphone." If it’s not clear which jack goes with which cord, consult your hardware manufacturer, or try the most obvious outputs one at a time and see if they work. If you have multiple 5mm jacks to plug into, especially on a surround sound system, make sure all cords and cables are plugged into the correct jack. Make sure all cords and cables are plugged in. Locate D:\scripts\set-pcvolume.Check your speaker and headphone connections for loose cords or cables. I have stated emphatically that this must run on PowerShell V2.Īll of the help you have gotten in this forum has required V2. Locate D:\scripts\set-pcvolume.ps1:439 word:33 Locate D:\scripts\set-pcvolume.ps1:437 word:43 Locate D:\scripts\set-pcvolume.ps1:436 word:33 Locate D:\scripts\set-pcvolume.ps1:434 word:43 Locate D:\scripts\set-pcvolume.ps1:433 word:33 Locate D:\scripts\set-pcvolume.ps1:431 word:46 Locate D:\scripts\set-pcvolume.ps1:430 word:9Ĭannot find type: please confirm whether install those components or not. 'Add-Type' cannot be recognized as Cmdlet、variable, executable command, please check keyword, and try one more time. I receive following error, when I run it within powershell. Powershell v2? I am currently using Powershell v1, may try v2 in this weekend. Once I download this file and save as set-pcvolume.ps1, could you please give me any suggestions on what to do next with this file? Does it require Doesn't that look like the error message you posted? How did that get in a PS1 file? It say sthat one line executed and returned a -1.
SO many users just panic when they see a red error message. Someone in a blog noted that we should turn error mesages from red into something cooler so they wouldn't scre people so much. I also don't underestand why anyone would just pay no attention to the conmtents of an error. No I realize it is not their fault as there is likely a language difference.
I get frustrated when I can't get teh OP to read teh instructions carefully. + FullyQualifiedErrorId : DotNetMethodException + CategoryInfo : NotSpecified: (:), MethodInvocationException I commented out the Try Catch parts as you said, and then I get this: (Yes, I am running 64-bit Windows 7)Įxception calling "SetVolume" with "1" argument(s): "Cannot Set Volume"
0 kommentar(er)
