awwww

[Dan Kegel]

Hey, I wanted to see if my computer could run Vista, but:

$ ~/wine/programs/msiexec/msiexec /i VistaUpgradeAdvisor.msi
fixme:msi:MsiInstallProductW L"VistaUpgradeAdvisor.msi" (null)
err:msidb:load_string_table string table corrupt?
err:msidb:load_string_table string table load failed! (000218f3 != 000047ef)

Filed as http://bugs.winehq.org/show_bug.cgi?id=5395

[Vitaliy Margolen]

Friday, June 9, 2006, 10:56:43 PM, Dan Kegel wrote:
> Hey, I wanted to see if my computer could run Vista, but:
> $ ~/wine/programs/msiexec/msiexec /i VistaUpgradeAdvisor.msi
> fixme:msi:MsiInstallProductW L"VistaUpgradeAdvisor.msi" (null)
> err:msidb:load_string_table string table corrupt?
> err:msidb:load_string_table string table load failed! (000218f3 != 000047ef)
> Filed as http://bugs.winehq.org/show_bug.cgi?id=5395

Don't you forgetting something? That something is windows. Do you really think
that being able to install that would help anything at all?

How about working game installers?

How about some newer copy protection systems that Wine could support (instead of NONE)?

How about keeping things from breaking in favor of extra new features?

How about making number of things not 100% perfect, but closer to what they should be
instead of chasing that perfection?


PS:
If you is didn't understand, lots of bugs & problems that you raise are not as critical
as you think they are. At least of bigger number of people.


Vitaliy

[James Hawkins]

On 6/10/06, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> Don't you forgetting something? That something is windows. Do you really think
> that being able to install that would help anything at all?

I'm not Dan, but I can still answer: yes.  There's obviously a bug in
msi that is keeping this utility from installing.  If the bug gets
fixed, then that's one less bug for another installer to stumble over.
 As we've seen with several installers recently, one bug can affect
many apps.  You're missing the point about why he wants to run this
app.
> How about working game installers?
>
> How about some newer copy protection systems that Wine could support (instead of NONE)?
>
> How about keeping things from breaking in favor of extra new features?

I don't know if you've noticed, but Dan has been getting on to
everyone about adding regression tests even for simple fixes (which is
a good thing :)
> How about making number of things not 100% perfect, but closer to what they should be
> instead of chasing that perfection?

This really isn't about perfection...it doesn't run at all, so at
least letting it install is getting closer to what it should be.
> PS:
> If you is didn't understand, lots of bugs & problems that you raise are not as critical
> as you think they are. At least of bigger number of people.

I don't really agree, but assuming that were true, this is an open
source project.  You work on things you want to work on, fix bugs you
want to fix.  Bugs are bugs, and no matter how small or irrelevant
they are to you, we shouldn't ignore them, and if they are small, then
we should be fixing them quicker.

-- 
James Hawkins

[Dan Kegel]

On 6/9/06, James Hawkins <truiken(a)gmail.com> wrote:
> > If you is didn't understand, lots of bugs & problems that you
> > raise are not as critical as you think they are.
>
> I don't really agree, but assuming that were true, this is an open
> source project.  You work on things you want to work on, fix bugs you
> want to fix.  Bugs are bugs, and no matter how small or irrelevant
> they are to you, we shouldn't ignore them, and if they are small, then
> we should be fixing them quicker.

I do lots of random testing (e.g. by using Firefox on Wine) to
try to understand what it's like to really rely on Wine, and
as a result, I generate lots of bug reports that might seem odd
to the casual observer.

It may have been hard to tell from my post, but
I installed this tool on a lark, and my post was meant to be
tongue-in-cheeck.  The bug report is real; something's funky
with MSI.  The app is obviously low priority, but I thought it
was better to file it rather than just laugh.

If you want to see the bugs I consider high priority,
have a look at http://wiki.winehq.org/DanKegel
My top five app list is

* Visual Basic 6 and Visual C++ 6 (to make it easier for
Windows ISVs to debug their code on Wine)

* SPSS11 and Keeptool-Hora (because Munich chose those as apps
to test under Wine for their Limux linux desktop conversion project)

* iSBEM (http://www.ncm.bre.co.uk; uses Access 2000;
the UK gov't requires building contractors to use this software,
and it would be great PR for the Wine community to get this working well,
I think.)

Now how do you feel about my priorities?
- Dan

-- 
Wine for Windows ISVs: http://kegel.com/wine/isv

[Dan Kegel]

On 6/10/06, Dan Kegel <dank(a)kegel.com> wrote:
> If you want to see the bugs I consider high priority,
> have a look at http://wiki.winehq.org/DanKegel
> My top five app list is ...

I forgot to mention: I also consider any installer bug
a high priority bug.  Installers Should Just Work.
- Dan

[Mike McCormack]

Dan Kegel wrote:
> I forgot to mention: I also consider any installer bug
> a high priority bug.  Installers Should Just Work.

Agreed, as the installer blocks any other testing that can be done on an 
application.  That's the reason Jeremy has had CodeWeavers employees 
working on OLE32 and MSI for the last year or so ;)

Mike

[Jaap Stolk]

On 6/10/06, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> How about some newer copy protection systems that Wine could support

I was wondering about that.
I'm trying to run autocad 2004. (It's more an example to debug wine, I
don't really need it)
When run, it generates a temporary DLL, which in turn generates a
temporary DLL, which in turn runs the program. (obviously each step
involves new layer of encryption.) Would Wine be able to handle
something like that ?

Also. Some autocad extensions use printer port or USB hardware keys.
Does Wine support low-level printer port access to the real printer
port ?

Also fun: acad can open multiple files, but some extensions don't
support that, so you need to start a separate instance for each
drawing, each with it's own copy protection DLL's, so with a couple of
drawings open, more than 50 Mb of your system is wasted on the copy
protections....