From Wine-Wiki

AVR Studio is used by embedded programmers for programming and debugging for many of the Atmel microprocessors such as the Atmega8 or even the Atmega128. While it has support for assembly programming for those who prefer to use higher languages, it uses the coff format for debugging. Beginning with version 4 AVR Studio has now moved to dwarf2, and can be more readily used in conjunction with the open source gcc based compiler WinAVR.

Contents 1 Wine Application Database 2 Forum Comments 3 Links 3.1 (Official) Wine Links 3.2 (Unofficial) Wine-Wiki Links 3.3 External Links

[edit] Wine Application Database

Maintainers are needed for this software. This software would also benefit from clear bug reports for some the dll overrides required. With a new Wine folder each time (hint move your .wine folder to .oldwine and wine will automatically create a new folder), try and see what happens with the dll override, and what happens without. Then file a bug report each layout/gui/button etc bug, one at a time and follow the suggestions by the bugzilla team so they can track down what is happening. vcrun 2005 just might no longer be needed.

• http://appdb.winehq.org/appview.php?appId=402
• http://appdb.winehq.org/objectManager.php?sClass=version&iId=11340 Currently [sept 08] 4.13 and 4.14 are rated as silver with Wine version 1.13. With only one Maintainer, another would help share the load and bounce ideas off.
• http://appdb.winehq.org/appview.php?iVersionId=4528 version 4 [Aug 07] currently rated as garbage, though with some recent patches this may improve.
• [sept 08] One supermaintainer (More Volunteers please apply)
• [sept 08] One maintainer (More Volunteers please apply)

• Please consider submitting your test results for running this software under Wine.

Become a Maintainer

Please consider volunteering to be an additional Maintainer for this software. Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release. Who can be a Maintainer? - anyone. no programming experience required. What is required of a Maintainer? - not much, but you do make a real difference. Wine AppDB - Maintainers Guidelines Wine AppDB - Application Database FAQ A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help. Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it. This often results in very quick fixes.

[edit] Forum Comments

U. Bonnes [Sept 05] discussing a patch mentioned that it could be started with Wine Archive:

env WINEDLLOVERRIDES=msvcrt,msxml3,ole32,oleaut32,rpcrt4,urlmon=n [path to /AVRStudio.exe

U. Bonnes [July 05]: with native urlmon(and ole32,oleaut32,rpcrt4), Atmel Avrstudio brings up the "Program AVR" option in the "Tools" pulldown menu, with builtin this item is missing. [A fix was discussed, but not posted to the list]. Wine Archive A prerequist for AvrStudio is IE6. AvrStudio depends on some IE extensions. To setup IE6, follow the instructions coming with "winetools" (http://www.von-thadden.de/Joachim/WineTools/), use the wine version recommended there and download/install at least the base setup.

[update 2008, winetools is no longer supported and is not required with latest wine]

U. Bonnes: [July 05]: The JTAG AVR ICE adapter [is currently] working with AVRSTUDIO Wine Archive

U. Bonnes:[July 05] The usbserial Atmel AVR ICE uses a FTDI FT232 which is well supported. It works quite well, with the serial related patches I sent to the list (but some of them not yet in CVS).Wine Archive

[edit] Links

Wine Links

[edit] (Official) Wine Links How to install Wine] Wine's Application Database Your Privacy and Wine Submitting An Application to the Application Database What is asked of a Maintainer General Help running software on Wine [edit] (Unofficial) Wine-Wiki Links Installing Wine Tips and Tricks Page Developers Corner Page Installing with InstallShield Installing with MSI Advanced Wine User Information - Copying Software across from a native Windows Installation Wine_DirectX_status Debugging_Wine Tips and Tricks Page Introduction to Making Stubs Internet Explorer Wine_Appdb_Maintainers_Notes

[edit] External Links

• [1] Official Atmel AVR Studio download page
• [2] Atmel Norway AVR Studio beta download page
• [3] AVR freaks forum tips for Wine