-->
For Windows the Azure CLI is installed via an MSI, which gives you access to the CLI through the Windows Command Prompt (CMD) or PowerShell.When installing for Windows Subsystem for Linux (WSL), packages are available for your Linux distribution. See the main install pagefor the list of supported package managers or how to install manually under WSL.
Gnokii provides tools and drivers for use with mobile phones under various operating. Under Linux but also Solaris,.BSD family and MS Windows families are known to work). Nov 6 14:59:23 host yum: Installed: gnokii.i386 0.6.19-1.el4.rf.
The current version of the Azure CLI is 2.0.80. For information about the latest release, see the release notes. To find your installed version and see if you need to update, run
az --version
.Install or update
The MSI distributable is used for installing or updating the Azure CLI on Windows. You don't need to uninstall any current versionsbefore using the MSI installer.
When the installer asks if it can make changes to your computer, click the 'Yes' box.
You can also install the Azure CLI using PowerShell. Start PowerShell as administrator and run the following command:
This will download and install the latest version of the Azure CLI for Windows. If you already have a version installed, it will update the existing version. After the installation is complete, you will need to reopen PowerShell to use the Azure CLI.
You can now run the Azure CLI with the
az
command from either Windows Command Prompt or PowerShell. PowerShell offers some tab completion featuresnot available from Windows Command Prompt. To sign in, run the az login command.- Run the
login
command.If the CLI can open your default browser, it will do so and load an Azure sign-in page.Otherwise, open a browser page at https://aka.ms/devicelogin and enter theauthorization code displayed in your terminal. - Sign in with your account credentials in the browser.
To learn more about different authentication methods, see Sign in with Azure CLI.
Troubleshooting
Here are some common problems seen when installing on Windows. If you experience a problem not covered here, file an issue on GitHub.
Proxy blocks connection
If you can't download the MSI installer because your proxy is blocking the connection, make sure thatyou have your proxy properly configured. For Windows 10, these settings are managed in the
Settings > Network & Internet > Proxy
pane. Contact your system administrator for the required settings,or for situations where your machine may be configuration-managed or require advanced setup.Important
These settings are also required to be able to access Azure services with the CLI, from bothPowerShell or the Command Prompt. In PowerShell, you do this with the following command:
In order to get the MSI, your proxy needs to allow HTTPS connections to the following addresses:
https://aka.ms/
https://azurecliprod.blob.core.windows.net/
Uninstall
If you decide to uninstall the Azure CLI, we're sorry to see you go. Before you uninstall, use the
az feedback
command to let us knowwhat could be improved or fixed. Our goal is to make the Azure CLI bug-free and user-friendly. If you found a bug, we'd appreciate it if you file a GitHub issue.You uninstall the Azure CLI from the Windows 'Apps and Features' list. To uninstall:
Platform | Instructions |
---|---|
Windows 10 | Start > Settings > Apps |
Windows 8 Windows 7 | Start > Control Panel > Programs > Uninstall a program |
Once on this screen type Azure CLI into the program search bar. The program to uninstall is listed as Microsoft CLI 2.0 for Azure. Select this application, then click the
Uninstall
button.Next Steps
Now that you've installed the Azure CLI, take a short tour of its features and common commands.
PermalinkAll your code in one place
GitHub makes it easy to scale back on context switching. Read rendered documentation, see the history of any file, and collaborate with contributors on projects across GitHub.
Sign up for free See pricing for teams and enterprises Find file Copy path
Cannot retrieve contributors at this time
README-WINDOWS |
The graphical X version, the AT-emulator and virtual device are not ported to |
Windows. This might change in the future but as far as I know no work is in |
progress. Of course the effort of porting only makes sense if there is a need. |
Do you have the need for extended Windows functionality don't ask me but let us |
all know on the gnokii mailing list. |
Recent Windows-related information is updated on the gnokii wiki. The main |
Windows page is: http://wiki.gnokii.org/index.php/Windows |
Compile using Microsoft Visual C++ 2010 Express Edition |
Below a description how to compile gnokii with the Microsoft Visual C++ 2010 Express Edition. |
1) Extract gnokii source into <path> |
2) (optional) Build settings are in <path>WindowsMSVC2010Expressconfig.h you may edit that. |
2) Read <path>WindowsMSVS2011ExpressREADME to install additional libraries required to compile. |
3) Open <path>WindowsMSVS2011Expressgnokii.sln and compile :) |
Distributed gnokii binaries for Windows are built with this compiler. |
Compile using Microsoft Visual Studio 2005 |
Below a description how to compile gnokii with the Microsoft Visual Studio 2005 C/C++. |
Both the commercial MSVS 2005 or MS Visual C++ 2005 Express Edition do work. |
1) Extract gnokii source into <path> |
2) (optional) Build settings are in <path>WindowsMSVS2005config.h you may edit that. |
3) Open <path>WindowsMSVS2005gnokii.sln and compile :) |
The solution will contain three projects: gnokii.dll, gnokii.exe and setup. |
The setup build will fail on Visual C++ Express edition as the setup tools are |
available only in the commercial Visual Studio. |
You may want to change the compiler run-time library settings to single |
threaded / debug single threaded to have much smaller binaries. |
Compile using Microsoft Visual C++ 4.2 and 6.0 |
Current versions do not compile. |
Maintainers chose not to support these compilers. Microsoft don't support |
those either. There are free of charge alternatives available from Microsoft. |
Compile with Cygwin (B20) |
Current versions do not compile. |
This is on a TODO list and will be supported on later versions. |
Cross compiling with MinGW |
Current versions do not compile. |
This is on a TODO list and will be supported on later versions. |
Configuring gnokii |
Current versions attempt to read the config file from: |
1. Application installation directory: %APPDATA%gnokiignokii.ini |
2. User's home directory: %HOMEDRIVE%%HOMEPATH%gnokii.ini |
3. Windows installation directory: %SYSTEMROOT%gnokii.ini |
First being found (the lookup order is as above) is used. |
Three values are required in the config file for gnokii to work: port, model |
and connection. See the comments in the config file for further information. |
In Windows the port is always a Com-port, a hard wired or virtual. |
See the README-files for correct phone model number. See the README-files for |
correct connection cable type. |
Example: |
port = com5: |
model = 6510 |
connection = dlr3p |
gnokii wiki has example configurations for various handsets at |
http://wiki.gnokii.org/index.php/Config |
IrDA support for Windows |
gnokii does support IrDA connection on Windows system. The support is built |
in as default. |
You will need Nokia IrDA driver for this to work, it is in Nokia PC Suite software |
package. The driver will create a virtual Com-port when phone is near the PC. |
If you want to disable the IrDA do the following: |
1) Disable IrDA support in config.h file (see above) by replacing a line: |
#define HAVE_IRDA 1 |
with |
#undef HAVE_IRDA |
2) Build gnokii as described above |
Bluetooth support for Windows |
gnokii does support Bluetooth connection on Windows system. The support is built |
in as default. Please note that it supports only MS bluetooth stack. |
If you want to disable the Bluetooth do the following: |
1) Disable Bluetooth support in config.h file (see above) by replacing a line: |
#define HAVE_BLUETOOTH 1 |
with |
#undef HAVE_BLUETOOTH |
2) Build gnokii as described above |
Disclaimer |
No warranty, you are on your own. If you have questions or remarks, |
please let me know on my email address mentioned below. |
Maintainer: Jari Turkia <jmjt at lut dot fi> |
Copy lines Copy permalink