[Bug 24821] Custom app doesn't respond

[wine-bugs at winehq.org]

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

--- Comment #19 from Cesare <ced at 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?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.