http://bugs.winehq.org/show_bug.cgi?id=24821
Summary: Custom app doesn't respond Product: Wine Version: 1.3.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: ced@bernispa.com
It's an old problem that i'm tracking from 1.1.32 (wine package from Debian) and for which i wasn't able to find the cause: some library not available? A bug? Since the official Debian packages are stuck on Wine 1.1.x, now i'm using the rpm provided by Suse (latest 1.3.5), converted to deb with alien.
We have an old custom closed source application that almost works under Wine, except for an important portion. This application is a mix of Microfocus Cobol and VB6 that interacts with a MSSQL2000 server through ODBC. We have no access to the source code.
The problematic part is a sub-program that starts a graphic form, where i have to fill two field, then press a sort of "OK" button to exec a query (see attached "form-windows.jpg"). When the form opens, under Windows (98, 2000, 2003, XP, Vista, 7) the cursor is on the first field and blinks; now i type a specific char to define the query type and the cursor automatically moves to the next field, where i can type my search parameter; then i click "Invio" to start the query; a new windows opens with the search results. Under Wine the cursor doesn't automatically move from the first to the second field but, more important, when i click on "Invio" nothing happen: the windows doesn't react to any events and i have to kill the process to close it. But it's not blocked: i can delete what i've typed, and i can see to button go up and down when i click it. This unresponsive behaviour is the same if i don't fill any field.
The difficult part is that when this forms is open, there is some code spinning under the hood (as i can see from the cpu usage) and it's like that by design, since it happens also under Windows. This has the side effect to flood the logs and render them very difficult to read.
I've setup mdac28 with winetricks, registered some needed DLL, but i'm not able to find if something else is missing. During the last month i've tried installing many things: JET, DCOM, older MDAC, etc. Nothing changed. The most useful infos i've found are from Dependency Walker, profiling with the options reported in the "dependencywalker.jpg" attachment. I've attached the logs taken from Windows 2000 (AcmEngWR_wine135_ced002.mod.txt) and from Wine 1.3.5 (AcmEngWR_wine135_wine.mod.txt). They are hand modified to make diff easier: i've removed all except the log, removed timestamps, unified filesystem path, reordered many loaded DLL and removed loaded DLLs later unloaded.
From these modified logs you can see that under Windows 5 thread are created,
always started by kernel32.dll, while under Wine only 4 are started and called by MTXDM.DLL and OLEDB32.DLL. For the rest Windows loads mode DLLs but i can't understand it they are really needed and if they corresponds to something that i have to install under Wine too.
Have you got some advice to track down these problem? I can provide the unmodified Dependency Walker logs, Wine logs or launch Wine with the required parameter, if needed.
Cesare.
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #1 from Cesare ced@bernispa.com 2010-10-19 18:27:07 CDT --- Created an attachment (id=31389) --> (http://bugs.winehq.org/attachment.cgi?id=31389) Form Windows under Win2000
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #2 from Cesare ced@bernispa.com 2010-10-19 18:28:16 CDT --- Created an attachment (id=31390) --> (http://bugs.winehq.org/attachment.cgi?id=31390) Dependecy Walker profiler options
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #3 from Cesare ced@bernispa.com 2010-10-19 18:30:09 CDT --- Created an attachment (id=31391) --> (http://bugs.winehq.org/attachment.cgi?id=31391) Dependecy Walker log under Win2000
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #4 from Cesare ced@bernispa.com 2010-10-19 18:30:39 CDT --- Created an attachment (id=31392) --> (http://bugs.winehq.org/attachment.cgi?id=31392) Dependecy Walker log under Wine 1.3.5
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #5 from Austin English austinenglish@gmail.com 2010-10-19 20:57:34 CDT --- Terminal output from wine is usually a good start.
I presume this can't be downloaded anywhere, right?
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #6 from Cesare ced@bernispa.com 2010-10-20 02:08:11 CDT --- (In reply to comment #5)
Terminal output from wine is usually a good start.
I presume this can't be downloaded anywhere, right?
Hi Austin, thank you very much for your fast reply.
Unfortunately i can't provide you the program primarily because it requires an MSSQL2000 server properly setup to work: the aspect and behaviour of the non-working program is in fact partially determined by the contents of some SQL tables (if i recall correctly the action to take in response of many window events are described inside those tables). Secondly it is not a single executable but it's scattered across many files that depends on a Microfocus environment that i know just a little and that i think has some license restriction. There are parts of the program almost older than me! :-)
Following i attach the Wine terminal output obtained setting WINEDEGUG like this: WINEDEBUG=-all,fixme+all,+file,+loaddll
The .wine folder were deleted and completely recreated many times. The last time was to report the initial results, so it should be rather clean.
Thank you for your time.
Cesare.
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #7 from Jeff Zaroyko jeffz@jeffz.name 2010-10-20 02:13:16 CDT --- Please attach terminal output as per:
http://wiki.winehq.org/FAQ#get_log
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #8 from Cesare ced@bernispa.com 2010-10-20 02:20:24 CDT --- Created an attachment (id=31395) --> (http://bugs.winehq.org/attachment.cgi?id=31395) Wine terminal log
The log documents the program activity from the starts, not only the problematic sub-program. The subprogram activity starts from line 51426 and ends on 61344, where i've given the kill command.
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #9 from Cesare ced@bernispa.com 2010-10-20 02:48:59 CDT --- Created an attachment (id=31396) --> (http://bugs.winehq.org/attachment.cgi?id=31396) Wine terminal log without any WINEDEBUG settings
As requested, here is the terminal log without any WINEDEBUG settings and the program launched with that command line: wine program.exe &> wine.log
The problematic sub-program started with line 30 and was killed after line 33.
For the err:ole messages in the past i've done some research on the internet and i've found many people with VB6 programs reporting it. Many complains were from few years ago (2006), so i supposed that if the error is here yet is not so important.
Cesare.
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #10 from Austin English austinenglish@gmail.com 2010-10-20 17:43:28 CDT --- Does 'winetricks dcom98' help at all?
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #11 from Cesare ced@bernispa.com 2010-10-21 00:24:37 CDT --- (In reply to comment #10)
Does 'winetricks dcom98' help at all?
In the past it didn't help. Today i'll retry and i'll report the result. IIRC at some point i was able to make the err:ole disappear but not the problem i've reported here.
Cesare.
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #12 from Cesare ced@bernispa.com 2010-10-21 11:20:55 CDT --- (In reply to comment #10)
Does 'winetricks dcom98' help at all?
Hi Austin, i confirm what i've said in the previous message: dcom98 solves the err:ole lines but the sub-program continues to not respond. The terminal log with no WINEDEBUG settings is substantially clear, apart some variable "fixme:win:AnimateWindow partial stub" that are bound to whether i pass the mouse on some links.
Before inserting form data, the window seems responsive yet, in fact i can press ESC to close it. As i said, however, the cursor doesn't move automatically to the next field as under Windows.
When i insert data into the form fields and confirm, with wireshark i can see a query packet to the SQL server and then the reply. I'm not able to understand where exactly the problem is: database transaction, thread, ole?
Cesare.
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #13 from Cesare ced@bernispa.com 2010-11-21 12:31:58 CST --- No more idea to narrow the problem?
Cesare.
http://bugs.winehq.org/show_bug.cgi?id=24821
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |frederic.delanoy@gmail.com
--- Comment #14 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-05-14 14:58:14 CDT --- Does this still happen in recent wine (1.5.30 or later)?
http://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #15 from Cesare ced@bernispa.com 2013-05-15 00:51:29 CDT --- (In reply to comment #14)
Does this still happen in recent wine (1.5.30 or later)?
The official wine package in Debian is 1.5.7 (newer than the unofficial Debian package cited in your download page) and the problem still persists in this version. But now that Debian 7 has been just released, i hope it will be soon upgraded to the latest development release. Then i'll be happy to test and report if there is anything new.
Thanks.
Cesare.
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #16 from Frédéric Delanoy frederic.delanoy@gmail.com --- (In reply to Cesare from comment #15)
(In reply to comment #14)
Does this still happen in recent wine (1.5.30 or later)?
The official wine package in Debian is 1.5.7 (newer than the unofficial Debian package cited in your download page) and the problem still persists in this version. But now that Debian 7 has been just released, i hope it will be soon upgraded to the latest development release. Then i'll be happy to test and report if there is anything new.
Thanks.
Cesare.
Any update on this?
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #17 from Cesare ced@bernispa.com --- Still the same. Re-tested today with wine develpment official Debian package, version 1.7.25.
https://bugs.winehq.org/show_bug.cgi?id=24821
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #18 from Anastasius Focht focht@gmx.net --- Hello folks,
--- quote --- I've setup mdac28 with winetricks, registered some needed DLL, but i'm not able to find if something else is missing. During the last month i've tried installing many things: JET, DCOM, older MDAC, etc. Nothing changed. --- quote ---
your last terminal output from years ago shows you didn't install MDAC and JET properly.
Install the app in clean (new!) 32-bit WINEPREFIX with 'winetricks -q mdc28 jet40' - no other stuff. BTW dependency walker logs from Windows are useless. You need to trace the thing with WINEDEBUG under Wine/Linux.
Regards
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #19 from Cesare ced@bernispa.com --- It's been a long time since my last accurate test and i had to recap many things. These days i repeated many tests, deleting .wine folder many times, testing many libray from winetricks and changing different library (ole, comdlg, etc.) between native and builtin.
The result are always the same i've originally reported: i've never been able to improve the situation nor to identify the root cause of the problem. Following i try to summarize the base setup and i'll attach some logs.
(In reply to Anastasius Focht from comment #18)
your last terminal output from years ago shows you didn't install MDAC and JET properly.
I don't know what you mean by properly: it's simple wizard and i can't imagine what i made wrong.
Install the app in clean (new!) 32-bit WINEPREFIX with 'winetricks -q mdc28 jet40' - no other stuff.
It's not so simple: the application require more setup than just mdac and jet.
The application is written in Cobol and VB6 and uses a remote MS SQL Server for data but also to contruct the user interface. But i don't know the internals: it's written by an external supplier and it's closed source. It's an old app, from about 2002, and runs under Win98, WinNT4, Win2000, WinXP and Win7. Main os: WinNT4/Win2000.
Under Windows these are the steps to prepare the application: * setup MDAC for the remote MS SQL Server, via TCP/IP. * launch a setup.exe from the supplier: fundamentally it seems to install VB6 runtime. * unregister then register some DLLs from the supplier, with regsvr32. * map a remote folder with a specific drive letter. * create a specific folder under C:.
Under Windows i never had to install Jet.
Under Wine i've followed your advice and i've used these steps (simplified): wineboot winetricks -q mdac28 winetricks -q jet40 # Manual MDAC setup wine control # VB6 runtime from the supplier. wine "InstallRuntimeVB/setup.exe" gvfs-mount $RDIR ln -s $MNT ~/.wine/dosdevices/x: ln -s $MNT/work ~/.wine/dosdevices/unc/$RHOST/work mkdir -p ~/.wine/drive_c/work # Look more as under Windows. cp -v font/vgafix.fon ~/.wine/drive_c/windows/Fonts/ for i in dll1 dll2 dll3 dll4; do regsvr32 /u "$i" regsvr32 "$i" done gvfs-mount /u $RDIR
Then the application can be run.
Attached the following logs from the application preparation: log_winetricks-mdac.txt: log from winetricks for MDAC log_winetricks-jet.txt: log from winetricks for JET log_odbc-setup.txt: log from MDAC manual configuration log_acme-runtime.txt: log from the supplier's setup (VB6RUN)
Attached also the log from the application run: log_run-menu.txt It report the minimal steps to reache the point where the application doesn't react anymore and then i have to kill a subprocess.
For the preparation the WINEDEBUG is defined as: WINEDEBUG=err+relay,warn+relay,+seh,+tid
For the run is defined as: WINEDEBUG=err+relay,warn+relay,+seh,+tid,+loaddll,err+ole,warn+ole,+odbc
I've not used the WINEDEBUG settings suggested by the FAQ (+relay,+seh,+tid) because it produces a too huge log: tenth of MB.
Le "run" log shows some errors and exceptions but i simply cannot understand them.
As i said before, in other tests i've tried to install form winetricks: comctl32, comctl32ocx, comdlg32ocx, mfc40, mfc42, vb6run, vcrun6. Then i've tried to use many native DLL, rather than builtin. No change.
Any suggestion?
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #20 from Cesare ced@bernispa.com --- Created attachment 49546 --> https://bugs.winehq.org/attachment.cgi?id=49546 Run log
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #21 from Cesare ced@bernispa.com --- Created attachment 49547 --> https://bugs.winehq.org/attachment.cgi?id=49547 Praparation MDAC
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #22 from Cesare ced@bernispa.com --- Created attachment 49548 --> https://bugs.winehq.org/attachment.cgi?id=49548 Praparation JET
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #23 from Cesare ced@bernispa.com --- Created attachment 49549 --> https://bugs.winehq.org/attachment.cgi?id=49549 Preparation VB6 runtime
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #25 from Cesare ced@bernispa.com --- Created attachment 49550 --> https://bugs.winehq.org/attachment.cgi?id=49550 Run log
Previously i had attached the wrong run log and was unable to delete it.
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #26 from Cesare ced@bernispa.com --- Sorry for the mess with the attachments...
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #27 from Ken Sharp imwellcushtymelike@gmail.com --- Please retry in Wine 3.9 or later.
https://bugs.winehq.org/show_bug.cgi?id=24821
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=24821
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #28 from joaopa jeremielapuree@yahoo.fr --- No download, no answer from the OP since 6 years. Can an administrator close this bug as ABANDONED?
https://bugs.winehq.org/show_bug.cgi?id=24821
--- Comment #29 from Cesare ced@bernispa.com --- (In reply to joaopa from comment #28)
No download, no answer from the OP since 6 years. Can an administrator close this bug as ABANDONED?
Hello, since from 2010 to 2014 there was no sign of progress on this bug report, I simply gave up and not retried anymore.
Feel free to close this bug, as nowadays it's way too complicated and time consuming to put together that environment and retry.
Cesare.
https://bugs.winehq.org/show_bug.cgi?id=24821
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #30 from Nikolay Sivov bunglehead@gmail.com --- Thanks, marking abandoned.
https://bugs.winehq.org/show_bug.cgi?id=24821
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de Status|RESOLVED |CLOSED
--- Comment #31 from André H. nerv@dawncrow.de --- closing abandoned