Dear Wine-experts, I've tested the functionality of simple CUI-applications with wineconsole (Wine-0.9.50, Ubuntu 7.10). Somewhat surprisingly, there seems to be numerous major flaws in the current implementation. The best (worst?) example is the widely distributed sample code ("Console: Demonstration of the Console Functions") available in the MSDN library (http://msdn2.microsoft.com/en-us/library/aa263818.aspx). With this code it is easy to replicate the "missing output" bug (http://bugs.winehq.org/show_bug.cgi?id=10404) and demonstrate several other previously unreported bugs and crashes. In fact, these problems seem to prevent the sound running of virtually all CUI-applications utilizing console functions. Should there be one big bug report for this sample console application or a separate report for each defect? I also wonder if someone else could test whether these potential problems are real, and confirm that no simple solutions are available.. The actual sources are available in the full PSDK sample package downloadable from: http://download.microsoft.com/download/vstudio60pro/Utility/6.0/W98NT42KMeXP/EN-US/vs6samples.exe. As that is a quite large file (131Mb), the example of interest extracted from the package is temporarily available at http://www.helsinki.fi/~sund/sdk_WinUI_console.exe, or in a zipped form at http://www.helsinki.fi/~sund/console_vs6.zip. An older (vs97) version of the same SDK sample that includes a compiled binary can be found at http://www.helsinki.fi/~sund/console_vs97.zip. The sample code compiles easily with Winelib after the standard --cuiexe transformations with Winemaker.
On Saturday December 15 2007 10:13, Reijo T Sund wrote:> Should there be one big bug report for this sample console application > or a separate report for each defect?There is should be separate bug reports for different defects in WINE implementation. For example, if you have found 3 different bugs in WINE when using single Windows application you should file 3 bug reports. Thank you for using WINE.
Reijo T Sund wrote:> Dear Wine-experts, > > I've tested the functionality of simple CUI-applications with > wineconsole (Wine-0.9.50, Ubuntu 7.10). Somewhat surprisingly, > there seems to be numerous major flaws in the current > implementation. > > The best (worst?) example is the widely distributed sample code > ("Console: Demonstration of the Console Functions") available in > the MSDN library (http://msdn2.microsoft.com/en-us/library/aa263818.aspx). > > With this code it is easy to replicate the "missing output" bug > (http://bugs.winehq.org/show_bug.cgi?id=10404) and demonstrate several > other previously unreported bugs and crashes. In fact, these problems > seem to prevent the sound running of virtually all CUI-applications > utilizing console functions. >Please add your results to this bug and vote on it.> Should there be one big bug report for this sample console application > or a separate report for each defect? >One bug/defect -> One report. Attach logs/output. And please do a through search of Bugzilla before reporting.> I also wonder if someone else could test whether these potential > problems are real, and confirm that no simple solutions are available.. >Please add as much information to reproduce in the bug reports. If they require downloading large packages, please be aware that some are bandwidth restricted.> The actual sources are available in the full PSDK sample package > downloadable from: > http://download.microsoft.com/download/vstudio60pro/Utility/6.0/W98NT42KMeXP/EN-US/vs6samples.exe. > > As that is a quite large file (131Mb), the example of interest extracted > from the package is temporarily available at > http://www.helsinki.fi/~sund/sdk_WinUI_console.exe, > or in a zipped form at http://www.helsinki.fi/~sund/console_vs6.zip. > An older (vs97) version of the same SDK sample that includes a compiled > binary can be found at http://www.helsinki.fi/~sund/console_vs97.zip. >Please put these links in the bug reports. Not many are going to download possibly damaging code from your site, however. The sources maybe all that are needed. James McKenzie
Reasonably Related Threads
- Bug in loadNamespace?
- How to call directly "dotTcl" C-function of the tcltk-package from the C-code of an external package?
- Bug in loadNamespace?
- How to call directly "dotTcl" C-function of the tcltk-package from the C-code of an external package?
- Help cleaning up domain SID mess...