Paul Vriens
Email: <Paul DOT Vriens DOT Wine AT SPAMFREE gmail DOT com>
TODO list
This is the list I'm trying to work on:
- Try to find more time for Wine.
- Update this page more regularly.
Winetest
There are some specific things I'd like to work on with respect to winetest on Windows and tests in general:
- Run winetest on some real machines, but also on VMware sessions.
Fix tests in general (get a green http://test.winehq.org is the ultimate goal)
- Make sure tests results are consistent. Known suspects:
- Fix tests where it's assumed that everyone is having the system and/or root drive set to C:\. The following tests are possible suspects:
- dlls/advpack/tests/advpack.c
- dlls/advpack/tests/files.c
- dlls/crypt32/tests/sip.c
- dlls/hlink/tests/hlink.c
- dlls/kernel32/tests/path.c
- dlls/kernel32/tests/volume.c
- dlls/msi/tests/install.c
- dlls/msi/tests/msi.c
- dlls/msi/tests/package.c
- dlls/setupapi/tests/parser.c
- dlls/shell32/tests/shelllink.c
- dlls/shell32/tests/shlfileop.c
- dlls/shell32/tests/shlfolder.c
- Fix tests that are language/locale dependent
- Fix tests that assume everyone is an administrator. Suspects:
- dlls/advpack/tests/advpack.c
- dlls/advpack/tests/install.c
- dlls/msi/tests/msi.c
- dlls/msi/tests/source.c
- dlls/netapi32/tests/access.c
- dlls/quartz/tests/filtergraph.c
- dlls/quartz/tests/filtermapper.c
- dlls/wintrust/tests/register.c
- Fix tests where there is not network connectivity
- Fix tests where the local firewall blocks everything (or a lot)
Fix tests that are dpi specific (DetlefRiekenberg is also working on this)
- Have some way of spotting new test failures more easily (kind of like Patchwatcher but after the commit).
Run winetest in a more automated way (at least on my boxes
)
Snelstart (Dutch accounting software)
(AppDB doesn't accept GIT test results so I put it here. All of the below is with GIT as of Jan-22-2009 : a44ff54d814d4c54bebcf88144b6bedad8521602).
As my wife is starting up a small new business she was looking into Snelstart. I've donated my old laptop (with her promise I could buy a new one ) and of course wanted this piece of software to run on Linux/Wine.
I downloaded the demo software and gave it a try on a fresh .wine. The installer starts up and downloads a dotnetfx.exe which is a wrapper around a .NET installer. This installation of .NET hangs. See bug 17076 and bug 13995
(Stepped out to Windows). I started up my WindowsXP box and started the installation. This went fine. As soon as .NET was installed the installation of the application started. At that point I copied the SnelStartV8.msi from the temporary install directory.
(Back to Wine). As I needed some extra stuff installed (clean .wine again) I did:
wget http://www.kegel.com/wine/winetricks sh winetricks dotnet20 /* It's a .NET app and decided to go with V2 although the app downloads/installs V1.x */ sh winetricks mdac28 jet40 /* The out-of-the-box installation uses a MS Access DB */ sh winetricks wsh56 /* Requested by the app when started */ msiexec /i SnelStartV8.msi
This makes sure one can start the app and open a .MDB file. Working with that database was not possible (didn't look to deep into this yet) but with the help of:
Do the oleaut32 override after the installation or the app will not run (so an old oleaut32 messes up the installation).
sh winetricks native_oleaut32
it's working !!! (I actually did a manual override afterwards, via winecfg, just for the app).
I'll update this with more stuff as I go along. Some bug reports will come out of this as well I guess. The wonderful thing is that I wasn't able to get this working with a stock 1.1.13 but with patches coming in by the dozens lately the app suddenly started working !!!
Wine AppDB Entry for SnelStart
What I've done so far
I think the accepted patches give the best overview :