winflashrom | Windows 200X/XP port

by pinczakko C Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | winflashrom Summary

winflashrom is a C library. winflashrom has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

This is the Windows port of the universal (LinuxBIOS) flash utility. It's named winflashrom. This code has not been merged into the LinuxBIOS repository. Therefore, it's available publicly only from Google Project hosting for a while. There are still some minor issues that prevent us to merge it into the LinuxBIOS repository. Anyway, you might want to watch LinuxBIOS mailing list (for further updates on Winflashrom. Once a stable release of Winflashrom is available. The code in Google Project hosting will be updated as well.

Support

Quality

Security

License

Reuse

Support

winflashrom has a low active ecosystem.

It has 9 star(s) with 2 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

winflashrom has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of winflashrom is current.

Quality

winflashrom has 0 bugs and 0 code smells.

Security

winflashrom has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

winflashrom code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

winflashrom does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

winflashrom releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of winflashrom

Get all kandi verified functions for this library.

winflashrom Key Features

No Key Features are available at this moment for winflashrom.

winflashrom Examples and Code Snippets

No Code Snippets are available at this moment for winflashrom.

Community Discussions

No Community Discussions are available at this moment for winflashrom.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install winflashrom

To build the winflashrom utility you need to have the following packages installed on your Windows system:.
MinGW
MSys
Windows XP DDK or Windows Driver Kit (WDK). This tool is optional because the package comes with a precompiled driver. However, if you want to make changes to the driver source code, you will need one of them.
DbgView (optional). You can use this tool for remote debugging if you want to try some changes to the driver code. DbgView is available from Sysinternals as a freeware.
Building the application. To build the application, "cd" to the source code root directory of the source code from within MSys (or other compatible shell that you might use) and invoke "make". Building the driver. To build the driver, run the Windows XP DKK or WDK shell (The WinXP Free Build environment or the WinXP Checked Build environment). Then, "cd" to the directory named "driver" in the root directory of the source code and invoke "build" from there. If you would like to have debugging message, use the "The WinXP checked build environment" of the Windows XP DDK or WDK shell. Remote debugging the driver. To do a remote debugging, first run the DbgView client in the test machine by invoking the following command in DbgView installation directory: DbgView.exe /c /t Then, connect to the test machine from the remote machine by running DbgView.exe. In the remote DbgView window, activate the Capture|Capture Kernel option, Capture|Pass-Through option, and Capture|Capture Events option and Disable the Capture|Capture Wind32 option as it will clutter the output with unnecessary messages. Now, you can monitor the debug messages from the test machine.
Building the application. To build the application, "cd" to the source code root directory of the source code from within MSys (or other compatible shell that you might use) and invoke "make".
Building the driver. To build the driver, run the Windows XP DKK or WDK shell (The WinXP Free Build environment or the WinXP Checked Build environment). Then, "cd" to the directory named "driver" in the root directory of the source code and invoke "build" from there. If you would like to have debugging message, use the "The WinXP checked build environment" of the Windows XP DDK or WDK shell.
Remote debugging the driver. To do a remote debugging, first run the DbgView client in the test machine by invoking the following command in DbgView installation directory: DbgView.exe /c /t Then, connect to the test machine from the remote machine by running DbgView.exe. In the remote DbgView window, activate the Capture|Capture Kernel option, Capture|Pass-Through option, and Capture|Capture Events option and Disable the Capture|Capture Wind32 option as it will clutter the output with unnecessary messages. Now, you can monitor the debug messages from the test machine.