request to change appdb message

[Jesse Allen]

On 6/29/07, Louis Lenders <xerox_xerox2000 at yahoo.co.uk> wrote:
>
> Yeah, so maybe we could add a list of "Common failures" to the documention,
>  with the solution. I can live with that. Then we could point garbage test
> submitters to that page. That would be a nice work around. I'll have to
> figure out how wiki works, and then i could give it a shot lateron i guess.
>
> Something like:
>
> Problem:
> err:module:import_dll Library MSVBVM60.DLL (needed by L"C:\\app.exe")
> not found
> err:module:LdrInitializeThunk Main exe initialization for L"C:\\app.exe"
> failed,status c0000135
>
> Solution:
> winetricks vcrun60
>
> or
>
> Problem:
> wine app.exe
> err:ole:CoGetClassObject class {00000514-0000-0010-8000-00aa006d2ea4}
> not registered
> err:ole:create_server class {00000514-0000-0010-8000-00aa006d2ea4}
> not registered
> err:ole:CoGetClassObject no class object
> {00000514-0000-0010-8000-00aa006d2ea4}could be created for
> context 0x5
> Unhandled page fault etc.........
>
> Solution:
> winetricks mdac27
>
> Would that be something useful?
>
> Cheers, Louis
>
>
>

Well, yeah. But the maintainer should be doing that already using
appdb notes based on his own knowledge or reading test reports. The
maintainer already screens the reports. So I can't see why we need to
be more automatic.

However we should set up a wiki for common problems or procedures so
the maintainer can  link to them from the notes.