Also a new user

Post by **DanKegel** » Wed May 28, 2008 3:39 pm

Austin wrote:

Might try native OLE to see if that helps.

I added an FAQ entry just for this:
http://wiki.winehq.org/FAQ?action=show# ... 8ef6de0326

austin987 · Post by **austin987** » Wed May 28, 2008 3:43 pm

On Wed, May 28, 2008 at 3:38 PM, Dan Kegel <[email protected]> wrote:

Austin wrote:
Might try native OLE to see if that helps.
I added an FAQ entry just for this:
http://wiki.winehq.org/FAQ?action=show# ... 8ef6de0326

I'm thinking we need to move towards a common errors wiki page. List
common CLSID's (wsh,msxml,etc.), dcom98, gdiplus, etc., etc.

Thoughts?

Post by **DanKegel** » Wed May 28, 2008 3:50 pm

On Wed, May 28, 2008 at 1:42 PM, Austin English <[email protected]> wrote:

I'm thinking we need to move towards a common errors wiki page. List
common CLSID's (wsh,msxml,etc.), dcom98, gdiplus, etc., etc.

How about a perl script that looks at a wine log
and makes suggestions? We could even run
it automatically.

austin987 · Post by **austin987** » Wed May 28, 2008 3:58 pm

On Wed, May 28, 2008 at 3:49 PM, Dan Kegel <[email protected]> wrote:

On Wed, May 28, 2008 at 1:42 PM, Austin English <[email protected]> wrote:
I'm thinking we need to move towards a common errors wiki page. List
common CLSID's (wsh,msxml,etc.), dcom98, gdiplus, etc., etc.
How about a perl script that looks at a wine log
and makes suggestions? We could even run
it automatically.

That'd be up to Alexandre, though I like the idea. I'd like to store
common CLSID's somewhere though, because googling for them floods
results with wine bugs/appdb reports.

Post by **DanKegel** » Wed May 28, 2008 4:08 pm

On Wed, May 28, 2008 at 1:56 PM, Austin English <[email protected]> wrote:

How about a perl script that looks at a wine log
and makes suggestions? We could even run
it automatically.
That'd be up to Alexandre, though I like the idea.

Only having it in the tree is up to him. We're free to
write a prototype for consideration; if it's useful, it can
live outside the tree if need be.

I'd like to store
common CLSID's somewhere though, because googling
for them floods results with wine bugs/appdb reports.

I still like the idea of keeping that info in a script...
maybe we could have a web form that runs input
through the script and spits out recommendations.

austin987 · Post by **austin987** » Wed May 28, 2008 4:11 pm

On Wed, May 28, 2008 at 4:07 PM, Dan Kegel <[email protected]> wrote:

On Wed, May 28, 2008 at 1:56 PM, Austin English <[email protected]> wrote:
How about a perl script that looks at a wine log
and makes suggestions? We could even run
it automatically.
That'd be up to Alexandre, though I like the idea.
Only having it in the tree is up to him. We're free to
write a prototype for consideration; if it's useful, it can
live outside the tree if need be.

Good point.

I'd like to store
common CLSID's somewhere though, because googling
for them floods results with wine bugs/appdb reports.
I still like the idea of keeping that info in a script...
maybe we could have a web form that runs input
through the script and spits out recommendations.

Either way's fine with me. I'm merely suggesting, I'm no perl guru,
and I know better than to look a gift horse in the mouth. If you've
got the urge to do some perl hacking (or getting an intern to

),
I'd be glad to test and offer suggestions.

-Austin

Post by **DanKegel** » Fri May 30, 2008 9:07 am

On Wed, May 28, 2008 at 1:56 PM, Austin English <[email protected]> wrote:

I'd like to store
common CLSID's somewhere though, because googling for them floods
results with wine bugs/appdb reports.

jswindle just pointed out that
http://wiki.jswindle.com/index.php/Read ... e_Examples
already has some of this, you could add things there for now.
- Dan