winevdm.exe problem - trying to load gsp Family Tree

[igor]

I am trying to install gsp Family Tree version 3 software with wine.
Previously this was successful with Fedora 11 and Fedora 19 (i686 32bit) without any config changes. (Wine 1.7.8-1.fc19)
Now I have 64bit hardware Intel Core i3-4130 3.4Ghz Haswell CPU, H81 chipset with integrated Intel HD 4400 Graphics, running Fedora 20 x86_64 with Wine 1.7.13-1 installed via yum.
I get the error when running the Family Tree setup.exe
'The program winevdm.exe has encountered a serious problem and needs to close'
After a couple of failures I removed wine and its prefixes and made a clean start.
Installed wine from the Fedora 20 repo.
Created a 32 bit prefix.
Attempted to install 'Family Tree' software to 32bit prefix.
below is console output and backtrace. (note I did try to attach but txt extension not allowed)
If anyone can see what I'm doing wrong, or can advise on the errors shown I would be most grateful.

Sudo yum install wine

Installed:
wine.x86_64 0:1.7.13-1.fc20

Dependency Installed:
mingw32-wine-gecko.noarch 0:2.24-1.fc20
mingw64-wine-gecko.noarch 0:2.24-1.fc20
wine-alsa.x86_64 0:1.7.13-1.fc20
wine-capi.i686 0:1.7.13-1.fc20
wine-capi.x86_64 0:1.7.13-1.fc20
wine-cms.i686 0:1.7.13-1.fc20
wine-cms.x86_64 0:1.7.13-1.fc20
wine-common.noarch 0:1.7.13-1.fc20
wine-core.i686 0:1.7.13-1.fc20
wine-core.x86_64 0:1.7.13-1.fc20
wine-courier-fonts.noarch 0:1.7.13-1.fc20
wine-desktop.x86_64 0:1.7.13-1.fc20
wine-filesystem.noarch 0:1.7.13-1.fc20
wine-fixedsys-fonts.noarch 0:1.7.13-1.fc20
wine-fonts.noarch 0:1.7.13-1.fc20
wine-ldap.i686 0:1.7.13-1.fc20
wine-ldap.x86_64 0:1.7.13-1.fc20
wine-marlett-fonts.noarch 0:1.7.13-1.fc20
wine-mono.noarch 0:4.5.2-1.fc20
wine-ms-sans-serif-fonts.noarch 0:1.7.13-1.fc20
wine-openal.i686 0:1.7.13-1.fc20
wine-openal.x86_64 0:1.7.13-1.fc20
wine-pulseaudio.i686 0:1.7.13-1.fc20
wine-pulseaudio.x86_64 0:1.7.13-1.fc20
wine-small-fonts.noarch 0:1.7.13-1.fc20
wine-symbol-fonts.noarch 0:1.7.13-1.fc20
wine-system-fonts.noarch 0:1.7.13-1.fc20
wine-systemd.noarch 0:1.7.13-1.fc20
wine-tahoma-fonts.noarch 0:1.7.13-1.fc20
wine-twain.i686 0:1.7.13-1.fc20
wine-twain.x86_64 0:1.7.13-1.fc20
wine-wingdings-fonts.noarch 0:1.7.13-1.fc20
wine-wow.x86_64 0:1.7.13-1.fc20

Complete!
[chris@localhost ~]$

[chris@localhost ~]$ WINEARCH=win32 WINEPREFIX=~/.wine-new winecfg
wine: created the configuration directory '/home/chris/.wine-new'
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:storage:create_storagefile Storage share mode not implemented.
p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:iphlpapi:NotifyAddrChange (Handle 0x122e8b0, overlapped 0x122e8bc): stub
wine: configuration in '/home/chris/.wine-new' has been updated.

[chris@localhost ~]$ WINEPREFIX=/home/chris/.wine-new wine /run/media/chris/gspcd213a/setup.exe
wine: Unhandled page fault on execute access to 0x00000000 at address (nil) (thread 0028), starting debugger...
fixme:dbghelp:addr_to_linear Failed to linearize address 1247:13b0 (mode 0)
[chris@localhost ~]$




Unhandled exception: page fault on execute access to 0x00000000 in 32-bit code (0x00000000).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:00000000 ESP:0104e2ac EBP:0104e2e8 EFLAGS:00010216( R- -- I -A-P- )
EAX:7e4216a5 EBX:7e423000 ECX:0104e300 EDX:0039ddd8
ESI:0104e32c EDI:00001247
Stack dump:
0x0104e2ac: 7e421a5a 0104e32c 00000000 00000000
0x0104e2bc: 00000000 00000000 00000000 00000000
0x0104e2cc: 00000000 00000000 00000000 0104e300
0x0104e2dc: 00001400 0000121f 00001247 0104e308
0x0104e2ec: 7e42169c 00000000 00000000 00000000
0x0104e2fc: 7e42169c 0104e32c 00000000 0104e618
Backtrace:
=>0 0x00000000 (0x0104e2e8)
0x00000000: -- no code accessible --
Modules:
Module Address Debug info Name (77 modules)
ELF 45865000-45889000 Deferred libxcb.so.1
ELF 4594e000-45959000 Deferred libxrender.so.1
ELF 459d7000-459db000 Deferred libxau.so.6
ELF 45ab9000-45bf5000 Deferred libx11.so.6
ELF 7b800000-7ba5d000 Deferred kernel32<elf>
\-PE 7b810000-7ba5d000 \ kernel32
ELF 7bc00000-7bce5000 Deferred ntdll<elf>
\-PE 7bc10000-7bce5000 \ ntdll
ELF 7bf00000-7bf04000 Deferred <wine-loader>
ELF 7e169000-7e1ad000 Deferred usp10<elf>
\-PE 7e170000-7e1ad000 \ usp10
ELF 7e1ad000-7e1d2000 Deferred imm32<elf>
\-PE 7e1b0000-7e1d2000 \ imm32
ELF 7e23b000-7e247000 Deferred libxcursor.so.1
ELF 7e247000-7e258000 Deferred libxi.so.6
ELF 7e258000-7e26b000 Deferred libxext.so.6
ELF 7e26b000-7e300000 Deferred winex11<elf>
\-PE 7e280000-7e300000 \ winex11
ELF 7e400000-7e406000 Deferred libxfixes.so.3
ELF 7e406000-7e40c000 Deferred libxxf86vm.so.1
ELF 7e410000-7e424000 Deferred winoldap.mod16.so
PE 7e420000-7e424000 Deferred winoldap.mod16
ELF 7e424000-7e439000 Deferred sound.drv16.so
PE 7e430000-7e439000 Deferred sound.drv16
ELF 7e43a000-7e465000 Deferred msacm32<elf>
\-PE 7e440000-7e465000 \ msacm32
ELF 7e465000-7e4e9000 Deferred rpcrt4<elf>
\-PE 7e470000-7e4e9000 \ rpcrt4
ELF 7e4e9000-7e62c000 Deferred ole32<elf>
\-PE 7e500000-7e62c000 \ ole32
ELF 7e62c000-7e6e5000 Deferred winmm<elf>
\-PE 7e630000-7e6e5000 \ winmm
ELF 7e6e5000-7e711000 Deferred mmsystem.dll16.so
PE 7e6f0000-7e711000 Deferred mmsystem.dll16
ELF 7e711000-7e725000 Deferred mouse.drv16.so
PE 7e720000-7e725000 Deferred mouse.drv16
ELF 7e725000-7e73a000 Deferred keyboard.drv16.so
PE 7e730000-7e73a000 Deferred keyboard.drv16
ELF 7e73a000-7e750000 Deferred display.drv16.so
PE 7e740000-7e750000 Deferred display.drv16
ELF 7e750000-7e778000 Deferred mpr<elf>
\-PE 7e760000-7e778000 \ mpr
ELF 7e778000-7e7c9000 Deferred user.exe16.so
PE 7e780000-7e7c9000 Deferred user.exe16
ELF 7e7c9000-7e7fd000 Deferred gdi.exe16.so
PE 7e7d0000-7e7fd000 Deferred gdi.exe16
ELF 7e7fd000-7e812000 Deferred comm.drv16.so
PE 7e800000-7e812000 Deferred comm.drv16
ELF 7e812000-7e827000 Deferred system.drv16.so
PE 7e820000-7e827000 Deferred system.drv16
ELF 7e873000-7e89c000 Deferred libexpat.so.1
ELF 7e89c000-7e8d9000 Deferred libfontconfig.so.1
ELF 7e8d9000-7e910000 Deferred libpng16.so.16
ELF 7e910000-7e927000 Deferred libz.so.1
ELF 7e927000-7e9c9000 Deferred libfreetype.so.6
ELF 7e9c9000-7e9eb000 Deferred libtinfo.so.5
ELF 7e9eb000-7ea13000 Deferred libncurses.so.5
ELF 7ea2b000-7ead9000 Deferred krnl386.exe16.so
PE 7ea40000-7ead9000 Deferred krnl386.exe16
ELF 7ead9000-7eaf3000 Deferred version<elf>
\-PE 7eae0000-7eaf3000 \ version
ELF 7eaf3000-7eb67000 Deferred advapi32<elf>
\-PE 7eb00000-7eb67000 \ advapi32
ELF 7eb67000-7ec8a000 Deferred gdi32<elf>
\-PE 7eb70000-7ec8a000 \ gdi32
ELF 7ec8a000-7ede9000 Deferred user32<elf>
\-PE 7eca0000-7ede9000 \ user32
ELF 7ede9000-7ee00000 Deferred winevdm<elf>
\-PE 7edf0000-7ee00000 \ winevdm
ELF f7372000-f737f000 Deferred libnss_files.so.2
ELF f7380000-f73c7000 Deferred libm.so.6
ELF f73c8000-f73cd000 Deferred libdl.so.2
ELF f73cd000-f758b000 Deferred libc.so.6
ELF f758b000-f75a6000 Deferred libpthread.so.0
ELF f75a6000-f775c000 Dwarf libwine.so.1
ELF f7775000-f7797000 Deferred ld-linux.so.2
ELF f7797000-f7798000 Deferred [vdso].so
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
0000001e 0
0000001d 0
00000014 0
00000010 0
0000000f 0
00000012 winedevice.exe
0000001c 0
00000019 0
00000017 0
00000013 0
0000001a plugplay.exe
00000020 0
0000001f 0
0000001b 0
00000023 (D) C:\windows\system32\winevdm.exe
00000028 0 <==
00000025 0
00000024 0
00000026 explorer.exe
00000027 0
System information:
Wine build: wine-1.7.13
Platform: i386
Host system: Linux
Host version: 3.13.7-200.fc20.x86_64

[Bob Wya]

@igor,

Please, please, please can you use CODE tags when posting code or console dumps inline.

I don't use Fedora (and never have seriously) - so I can't comment about the packages required on that particular distro at all. Assuming you have installed wine correctly however...

Code: Select all

WINEPREFIX=/home/chris/.wine-new wine /run/media/chris/gspcd213a/setup.exe

If that's a real or virtual DVD/CD mountpoint then you probably want to do something more like...

Code: Select all

export WINEPREFIX=/home/chris/.wine-new
winecfg
cd '/home/chris/.wine-new/dosdevices/d:'
wine setup.exe

(use the winecfg to get the mapped drive letter of your DVD/CD media - replace d: with a different letter as appropriate)

Bob

[igor]

Hi Bob, thanks for your reply. Yes, the actual path to the dvd drive was what is shown and worked fine before with 32bit hardware. As you suggested I exported the WINEPREFIX and ran winecfg. The drive tab shows letter C: target folder ../drive_c and letter Z: target folder / I presume from that the dvd drive is not mapped ?
igor

[Bob Wya]

Hi Bob, thanks for your reply. Yes, the actual path to the dvd drive was what is shown and worked fine before with 32bit hardware. As you suggested I exported the WINEPREFIX and ran winecfg. The drive tab shows letter C: target folder ../drive_c and letter Z: target folder / I presume from that the dvd drive is not mapped ?
igor

Hi igor,

Yup. So that implies you are using physical DVD - right? (Hint: you still haven't confirmed or denied this - is it a secret??) How did you mount this DVD drive disc? Did you use a DE builtin tool like Udisks2 (looks like you are from the specified path)? Are you using Gnome Shell or a different DE?

I presume the Autodetect button in the winecfg / Drives tab doesn't help?

Can you dump /proc/mounts inline with CODE tags - so we can check how your DVD is mounted.

Using Udisks2+physical media or simply manually mounting a DVD disc image, I would expect to see wine auto-populate it's mapped drives automagically (without any user intervention). So there appears to be a problem with your system or your particular wine package that is not working correctly.

Bob

[igor]

Hi Bob
The windows software is on physical CD.
My DE is Xfce on Fedora 20
Disc mount is right click option
I realised that the last time I ran winecfg I didn't have the drive mounted.

Fedora repo now has wine 1.7.16 so I have upgraded
Running winecfg now shows D: target folder /run/media/chris/gspcd23a

I tried cd 'home/chris/.wine-new/dosdevices/d:' and got no such file or directory

Code: Select all

[chris@localhost ~]$ WINEPREFIX=/home/chris/.wine-new
[chris@localhost ~]$ winecfg
[chris@localhost ~]$ cd '/home/chris/.wine-new/dosdevices/d:'
bash: cd: /home/chris/.wine-new/dosdevices/d:: No such file or directory

so tried wine /pathto drive/setup.exe as below and installer ran

Code: Select all

[chris@localhost ~]$ wine /run/media/chris/gspcd213a/setup.exe
[chris@localhost ~]$ winevdm: can't exec 'C:\users\chris\Temp\dosshell.pif': file not found

The installer ran and installed program files. A window appeared headed
16 bit DOS subsystem with
C:\users\chris\Temp\dosshell.pif
Invalid program file name Check your pif file
So we progress -
I haven't tried running the family tree software yet as I've no idea what the error means.
So if you can advise on the pif error we might be winning !
Regards
Igor

[Bob Wya]

Hi Bob
...
Running winecfg now shows D: target folder /run/media/chris/gspcd23a

I tried cd 'home/chris/.wine-new/dosdevices/d:' and got no such file or directory

Code: Select all

[chris@localhost ~]$ WINEPREFIX=/home/chris/.wine-new
[chris@localhost ~]$ winecfg
[chris@localhost ~]$ cd '/home/chris/.wine-new/dosdevices/d:'
bash: cd: /home/chris/.wine-new/dosdevices/d:: No such file or directory

...

Okay lets get this fixed. So all I'm doing here is giving you "example code". I am expecting you to have enough command line "foo" to do something like:

Code: Select all

cd '/home/chris/.wine-new/dosdevices/'
'ls' -ahl # show detail view of dosdevices and their mappings, then...
cd 'd:' # might be right
cd 'd::' # might also be the correct mapping!!

Back to BASH "Elementary School"??

But in all seriousness. Getting familiar with BASH (or your shell of choice) never did any Linux User any harm !! Wine is definitely not POL and is not known for it's user friendliness! So it can be very unforgiving if you don't run a program in the correct wineprefix, working directory, etc.

I am not familiar with 16-bit Windows support in Wine. But certainly, according to the Wine FAQ, such applications should run in a 32-bit Wineprefix!

Bob

[igor]

Hi Bob
After upgrading to wine 1.7.16 all the errors went away, the gsp software installer ran through to completion and wine reported the 16 bit dos subsystem 'invalid program file name'.
I now have run the gsp family tree software and everything appears to work satisfactorily. Time will tell.
I'm inclined to run with it for a bit and hope the error reported can be ignored. Searching around I found bug 3638 where comment 16 refers to the same Temp file with gsp software, although different could be related perhaps ?

I tried 'ls' as suggested which shows d:: as you thought, but still 'not a directory'.

Code: Select all

[chris@localhost ~]$ cd /home/chris/.wine-new/dosdevices
[chris@localhost dosdevices]$ ls -ah1
.
..
c:
d::
z:
[chris@localhost dosdevices]$ cd d::
bash: cd: d::: Not a directory
[chris@localhost dosdevices]$ cd d:
bash: cd: d:: No such file or directory

I sincerely thank you for all your efforts on my behalf. I hope the family tree keeps running well.
If you have any further advice I would be pleased to receive it.
Regards
igor

[Bob Wya]

Hi Bob

Code: Select all

[chris@localhost ~]$ cd /home/chris/.wine-new/dosdevices
[chris@localhost dosdevices]$ ls -ah1
.
..
c:
d::
z:
[chris@localhost dosdevices]$ cd d::
bash: cd: d::: Not a directory
[chris@localhost dosdevices]$ cd d:
bash: cd: d:: No such file or directory

@Igor,

There are some BASH "gotcha's" that you still need to pick up! You need to escape (\) certain characters or put them in quotes (either "" or '' in this case)...

Code: Select all

[chris@localhost dosdevices]$ cd d\:\:
[chris@localhost dosdevices]$ cd d\:
[chris@localhost dosdevices]$ cd "d::"
[chris@localhost dosdevices]$ cd "d:"

I've just had a look back over your thread and checked out the winevdm docs... to quote...

Wine is also able to run 16 bit processes, but this feature is only supported on Intel IA-32 architectures.

I am sure I read somewhere that it's a hardware limitation of 64-bit x86 processors that they can either run in 32/16-bit mode or in 64/32-bit mode. You can't run all three levels at once. Someone more knowledgable than me might correct this of course! Which would explain why 32-bit Fedora was able to run the program and 64-bit Fedora isn't. I don't know whether using an Linux Container (LXC) might give you a realmode 32-bit instance of an OS?? I know one chap (who posted recently on the forums) who eventually ran his application, via Wine, in a 32-bit Ubuntu Container - all because he couldn't be bothered to work out what 32-bit libraries he needed to get the application working! So it can't be that hard to do!

I'll maybe ask on the winedev(eloper) mailing list about this issue...

Bob

[oiaohm]

Bob Wya the guide is out of date on what winevdm does these days. To use dos applications you do need a WINEARCH=win32 prefix. If you system is 64 bit you do need an application called dosbox installed. Even if you are on a 32 bit system you most likely want dosbox installed.

http://source.winehq.org/source/program ... /winevdm.c

Bob Wya the 16/32/64 bit protected modes what you use to run win16, win32 and win64 binaries these all exist in 64 bit long mode. vm86 is what is missing from 64 bit mode that is required for some forms of dos emulation. vm64 is x86 old real mode emulation. Wine old dos emulation is not as good as dosbox so wine by default attempts dosbox first. No dosbox then wine attempts old solution requiring vm86 then wine gives up and tells the user to install dosbox.

http://www.winehq.org/announce/1.3.12 its been this way for a fair while.

If you are running a dos application you are most likely better to just to install dosbox and use that instead.

There is no requirement to use containers or anything. Just install dosbox and use a WINEARCH=win32 prefix.

Before anyone asks why wine bothers checking for vm86 mode on a 64 bit kernel. Never underestimate the creatively of Linux Developers. http://v86-64.sourceforge.net/ Yes there is a hack and a half to allow vm86 mode from 64 bit mode by switch the cpu to 32 bit mode then running vm86 and after existing doing the reverse trip. Totally not recommended due to issues it can bring due to mode changing a cpu on fly and scheduler disruption. The odds of your distribution having this patch is basically zero. But just in case wine still attempts. Bob Wya cpu spec sheets only tell you so much. Particular developers twist cpus in insane directions.