[Bug 38051] New: emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

Bug ID: 38051
           Summary: emisosft command line update generates tons of errors
                    and pop ups
           Product: Wine
           Version: 1.7.32
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Dear Wine,

Would you please fix this for me?

wine-1.7.32.tar.bz2 (complied as 32 bit)
Scientific Linux 6.6, 64 bit

I am trying to do an command line update of my Emsisoft Emergency Kit from a
Linux script.

You can download this kit from:
http://www.emsisoft.com/en/software/eek/

I am currently on Version 9.0.0.4523.

The command to update the databases is:
wine [unzip directory]/bin/a2cmd.exe /u

And it does work.

Problem: there are so many crashes and fix me's and three a2ddax86.sys pop ups
that it becomes almost impossible to run.

Many thanks,
-T

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #1 from Todd Chester  ---
wine cmd /c "a2cmd.exe /u"

Does the same thing

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #2 from Todd Chester  ---
(In reply to Todd Chester from comment #1)
> wine cmd /c "a2cmd.exe /u"
>
> Does the same thing

Any progrfess with this?

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #3 from Todd Chester  ---
(In reply to Todd Chester from comment #2)
> (In reply to Todd Chester from comment #1)
> > wine cmd /c "a2cmd.exe /u"
> >
> > Does the same thing
>
> Any progrfess with this?

Progress.  Stinking typos

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #4 from Todd Chester  ---
Created attachment 50934
  --> https://bugs.winehq.org/attachment.cgi?id=50934
after effect of running the emsisoft update from wine

The plot thickens.  After running the Emisosoft update utility from wine, the
next time you reboot your computer, you get the following pop up (see
attachment) 
and I waited two hours to see if it would populate.

The work around is to compile and install the latest Wine tar ball.

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #5 from Austin English  ---
(In reply to Todd Chester from comment #4)
> Created attachment 50934 [details]
> after effect of running the emsisoft update from wine
>
> The plot thickens.  After running the Emisosoft update utility from wine,
> the next time you reboot your computer, you get the following pop up (see
> attachment) 
> and I waited two hours to see if it would populate.

Use 'winetricks nocrashdialog'
> The work around is to compile and install the latest Wine tar ball.

Are you saying the bug is fixed in latest wine?

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #6 from Todd Chester  ---
(In reply to Austin English from comment #5)
> (In reply to Todd Chester from comment #4)
> > Created attachment 50934 [details]
> > after effect of running the emsisoft update from wine
> >
> > The plot thickens.  After running the Emisosoft update utility from wine,
> > the next time you reboot your computer, you get the following pop up (see
> > attachment) 
> > and I waited two hours to see if it would populate.
>
> Use 'winetricks nocrashdialog'

Thank you!
> > The work around is to compile and install the latest Wine tar ball.
>
> Are you saying the bug is fixed in latest wine?

No.  Just telling you how to clear the error so it won't bug the living
daylights out of you when you are troubleshooting.  Also, it might be a clue. 
You can reinstall the current version too.

I would be sincerely appreciative if you guys fix this sooner than later.  I
have to update my sticks with it that I take to customer sites to clear off
junkware (it is not my only too).  I could download it at the customer site,
but it can take up to an hour (it is really, really slow), especially on a
compromised machine.

Many thanks,
-T

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download
                URL|                            |http://dl.emsisoft.com/Emsi
                   |                            |softEmergencyKit.exe

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #7 from Austin English  ---
Confirming, looks service related.

austin@debian-home:~$ sha1sum EmsisoftEmergencyKit.exe 
128c8f6e9354c765d6108bb84af708e4008417e3  EmsisoftEmergencyKit.exe
austin@debian-home:~$ du -h EmsisoftEmergencyKit.exe 
159M    EmsisoftEmergencyKit.exe
austin@debian-home:~$ wine --version
wine-1.7.37

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #8 from Nikolay Sivov  ---
Could you attach a relevant trace log, +service,+tid for example.

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #9 from Todd Chester  ---
Created attachment 50946
  --> https://bugs.winehq.org/attachment.cgi?id=50946
a2cmd.log +service,+msi

(In reply to Nikolay Sivov from comment #8)
> Could you attach a relevant trace log, +service,+tid for example.

Certainly!

WINEDEBUG=+service,+msi wine cmd /c "bin/a2cmd.exe /u" > /home/temp/a2cmd.log 
2>&1

tar -cjvf a2cmd.log.tar.gz a2cmd.log

Use "tar -xjvf a2cmd.log.tar.gz" to de-tar

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #50934|0                           |1
        is obsolete|                            |

--- Comment #10 from Austin English  ---
Created attachment 50947
  --> https://bugs.winehq.org/attachment.cgi?id=50947
service,tid

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #11 from Nikolay Sivov  ---
---
0009:trace:service:StartServiceW 0x144aa0 0 (nil)
001c:trace:service:svcctl_StartServiceW (0x112f70, 0, (nil))
001c:trace:service:service_send_start_message L"A2DDA" (nil) 0
wine: Unhandled page fault on read access to 0x00000000 at address 0x24261c
(thread 002d), starting debugger...
001c:err:service:service_send_start_message service L"A2DDA" failed to start
001c:trace:service:service_start returning 1053
0009:trace:service:CloseServiceHandle 0x144aa0
---

Do you still this service installed after update is finished? I mean if you
ignore this page fault, let it update, and terminate it do you still have A2DDA
service in registry?

If you do try to start it separately with 'wine sc start A2DDA' and attach
+relay,+tid,+service log of that.

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #50946|0                           |1
        is obsolete|                            |
  Attachment #50947|0                           |1
        is obsolete|                            |

--- Comment #12 from Austin English  ---
Created attachment 50950
  --> https://bugs.winehq.org/attachment.cgi?id=50950
relay,seh,tid,service

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #13 from Todd Chester  ---
Hi All,

I upgraded to .38

$ wine --version
wine-1.7.38

And ran "wine cmd bin/a2cmd.exe /u" to make sure there was no symptom change. 
There were two changes:

1) it did not download the updates

2) it exited to a DOS style command prompt:

Z:\home\CDs\WindowsInternet\MalWare\EmsisoftEmergencyKit\EmsisoftEmergencyKit-9.0.0.4700

typing "exit" got me back to Linux (bash).

running "wine sc start A2DDA" was weird.  It took about 4 minutes to return to
the command prompt.  Then proceeded to fill me up with "fixme's":

fixme:advapi:RegisterEventSourceA ((null),""): stub
     fixme:advapi:RegisterEventSourceW (L"",L""): stub
     fixme:advapi:ReportEventA  
     ...

Do you want me to also run the latest trace request, or was Autsin's enough?

Many thanks,
-T

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #14 from Todd Chester  ---
After the service start did its thing (wine sc start A2DDA), I reran.  Still no
downloads.  Got the DOS prompt again.  On a hunch, I ran "bin\a3cmd.exe /u" and
two pop ups later and a bunch of fix me's and I got the download this time.

The bash terminal constantly gets fixme's from the server start thing.

And, back at the bash terminal, ran "wine bin/a2cmd.exe /u" without the "cmd"
in the run string.  It tried to get the updates but failed.

I am now running "wine sc stop A2DDA" to get some peace restored to my bash
terminal.

[Bug 38051] emisosft command line update generates tons of errors and pop ups

https://bugs.winehq.org/show_bug.cgi?id=38051

--- Comment #15 from Nikolay Sivov  ---
> From relay log Austin attached this will probably need a debugger to look into

this driver crash. By the way, any idea what this driver might do? If it needs
hardware access or something similar it's unlikely we can get it to work.