WineHQ
Wine Forums

Board index » WineHQ » Wine Help » Linux




 Page 1 of 1 [ 8 posts ] 



 
Author Message
 Post Posted: Wed Mar 21, 2018 3:04 pm 
Offline
Newbie
Newbie

Joined: Wed Mar 21, 2018 2:23 pm
Posts: 4
Hello:
I cannot get Wine to open my program "admin.exe" on my new laptop. I am running a Dell Latitude E6430 with Debian/Gnu Linux 9.2.1, which uses Linux kernel 4.9.0-5-amd64. My Wine version is 1.8.7-2 installed by Synaptic Package Manager.

The program I am trying to run is "admin.exe" which is a GUI specific to my 15 or 20 year old Vodavi voice mail system. I can run it on my old laptop, a Fujitsu Lifebook E330, just fine. It has Debian 6.0.10 (using a Linux kernel 2.6.32-5-686) and has Wine 1.0.1 installed.

Back to my new laptop's problem. The command "wine notepad" works fine, as does "wine scantool" (a GUI for an OBDI reader), but when I type "wine admin" or "wine admin.exe", I get: "Function not supported by driver". When I click "OK", I get: "Bad handle passed to com function". Yet my "admin.exe" program GUI comes up--along with a notice that "a Program Error has occurred and that winevdm.exe must close". When I click "OK", Wine quits and Terminal lists the accompanying output. I have tried with and without changes to the file locations in the registry and have copied admin.exe into several directories, but have not tried winetricks.

Can you help me get my program to work? Thanks.


Top 
 Post Posted: Fri Mar 23, 2018 12:46 pm 
Offline
Level 5
Level 5
User avatar

Joined: Tue Nov 22, 2016 5:39 pm
Posts: 448
Does it work on the new system with that old wine version installed? Also, did you try wine 3.4 already?


Top 
 Post Posted: Sat Mar 24, 2018 7:04 am 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2128
Location: Cambridge
@logiflow,

When testing your old application, with a supported version of Wine...
It would be recommended to use a clean 32-bit WINEPREFIX, set to Windows XP compatiblity.

See: WineHQ FAQ: 6.5.3 How do I create a 32 bit wineprefix on a 64 bit system?

E.g.:
Code:
export WINEPREFIX=~/.wine32
WINEARCH="win32" wineboot -u
winetricks winxp


Bob


Top 
 Post Posted: Tue Mar 27, 2018 11:27 am 
Offline
Newbie
Newbie

Joined: Wed Mar 21, 2018 2:23 pm
Posts: 4
Thanks for the information. I think both of you may be on the right track about getting to a 32 bit version. I'll try that approach this week.

I couldn't get the following info into my original question, but it may shed more light on the subject:

Terminal Output:

wine: Unhandled page fault on read access to 0xffffffff at address 0x11ff:0x00002e75 (thread 0028), starting debugger...
Unhandled exception: page fault on read access to 0xffffffff bad address.
fixme:dbghelp:addr_to_linear Failed to linearize address 12c7:a038 (mode 0)
fixme:dbghelp:addr_to_linear Unsupported (yet) mode (ffffffff)
In (null) mode.
Register dump:
CS:11ff SS:12c7 DS:12c7 ES:0000 FS:006b GS:0063Bad segment (4807)
Stack dump:
Backtrace:
=>0 Unknown mode ffffffff
(Unknown mode ffffffff
)
Unknown mode ffffffff
: -- no code accessible --
Modules:
Module Address Debug info Name (15 modules)
PE 7b810000-7b9b0000 Deferred kernel32
PE 7bc10000-7bc14000 Deferred ntdll
PE 7efb0000-7efb3000 Deferred usp10
PE 7f250000-7f254000 Deferred winex11
PE 7f420000-7f429000 Deferred msacm32
PE 7f450000-7f454000 Deferred rpcrt4
PE 7f4e0000-7f4e8000 Deferred ole32
PE 7f610000-7f688000 Deferred winmm
PE 7f730000-7f73a000 Deferred mpr
PE 7f800000-7f804000 Deferred imm32
PE 7faa0000-7faa4000 Deferred version
PE 7fac0000-7fac4000 Deferred advapi32
PE 7fb40000-7fb47000 Deferred gdi32
PE 7fc60000-7fc9b000 Deferred user32
PE 7ffd0000-7ffd3000 Deferred winevdm
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
0000001a 0
00000019 0
00000018 0
00000013 0
0000001b plugplay.exe
00000020 0
0000001f 0
0000001c 0
00000021 (D) C:\windows\system32\winevdm.exe
00000028 0 <==
00000022 0
00000023 explorer.exe
00000027 0
00000026 0
00000025 0
00000024 0
System information:
Wine build: wine-1.8.7 (Debian 1.8.7-2)
Platform: i386 (WOW64)
Version: Windows XP
Host system: Linux
Host version: 4.9.0-6-amd64

logiflow


Top 
 Post Posted: Tue Mar 27, 2018 5:45 pm 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2128
Location: Cambridge
@logiflow

Yup, that's still an unsupported version of Wine (2.0.5 or ideally 3.4 - please!)

Please use the forum Code:
Code:
Code

tags for terminal commands and output. It'll make your posts a lot more readable (by the people that might be helping you!)

Thanks
Bob


Top 
 Post Posted: Tue Apr 03, 2018 12:14 pm 
Offline
Newbie
Newbie

Joined: Wed Mar 21, 2018 2:23 pm
Posts: 4
Thanks for the information on how to set wine up for 32 bit operation. I think I now have it working as 32 bit--the output now shows "Platform: i386 (WOW64). But I still get: "Function not supported by driver" and "Bad handle passed to com function" when I execute "wine ADMIN.EXE" just like I did before.

My wine version is still 1.8.7-2 per Debian "stretch". Debian "buster" is showing wine version 3.0.1. Will that version be more likely to cure my problem? Would it be better to try to transfer the old wine version from my old laptop?

Thanks,


Top 
 Post Posted: Wed Apr 04, 2018 6:16 am 
Offline
Level 12
Level 12
User avatar

Joined: Sat Oct 16, 2010 7:40 pm
Posts: 2128
Location: Cambridge
logiflow wrote:
Thanks for the information on how to set wine up for 32 bit operation. I think I now have it working as 32 bit--the output now shows "Platform: i386 (WOW64). But I still get: "Function not supported by driver" and "Bad handle passed to com function" when I execute "wine ADMIN.EXE" just like I did before.


Code:
Platform: i386 (WOW64)


Indicates you are still using a 64-bit Wineprefix. A Wineprefix cannot magically change architecture.
You have to either:
  • delete the existing 64-bit Wineprefix
  • create a new 32-bit Wineprefix - at a different location in your filesystem

Also note that Wine uses the WINEPREFIX environment variable to tell what Wineprefix to use.
So you need to:
Code:
export WINEPREFIX= .... blah ....

everytime you start a new shell session and want to reference a specific Wineprefix.

logiflow wrote:
My wine version is still 1.8.7-2 per Debian "stretch". Debian "buster" is showing wine version 3.0.1. Will that version be more likely to cure my problem? Would it be better to try to transfer the old wine version from my old laptop?


Either version of Debian is fine... There are WineHQ packages available for all versions of Debian.

Bob


Top 
 Post Posted: Fri Apr 06, 2018 3:29 pm 
Offline
Newbie
Newbie

Joined: Wed Mar 21, 2018 2:23 pm
Posts: 4
Thanks for your info. I'm not sure I understand it, but here is what I did:

I established a ~/.wine32 directory and put my VodaviRaw folder in it. When I ran SETUP.EXE, what looked like Windows extracted the files from VodaviRaw but it put them in a folder in ~/.wine/drive_c. I moved the folder to ~/.wine32/drive_c and tried to run ADMIN.EXE. i got the same errors;

Code:
morris@DELLDEB:~/.wine32/drive_c/admin32$ ls
ADMIN.EXE  ADMIN.PB     AWMODEM.INI    ECOM.EXE      LOGS       RELEASE.TXT
ADMIN.INI  ADPHONE.INI  backtrace.txt  _ISREG16.DLL  MODEM.INI  REPORTS
morris@DELLDEB:~/.wine32/drive_c/admin32$ export WINEPREFIX=~/.wine32
morris@DELLDEB:~/.wine32/drive_c/admin32$ wine ADMIN.EXE


The return from Terminal was:

    wine: Unhandled page fault on read access to 0xffffffff at address 0x11ff:0x00002e75 (thread 0028), starting debugger...
    Unhandled exception: page fault on read access to 0xffffffff bad address.
    In (null) mode.
    Register dump:
    CS:11ff SS:12c7 DS:12c7 ES:0000 FS:006b GS:0063Stack dump:
    0x12c7:0x9fe0: *** Invalid address 0x00009fe0 ***

    000d: sel=006f base=00000000 limit=00000000 32-bit r-x
    Backtrace:
    =>0 Unknown mode ffffffff
    (0x12c7:0x9fe4)
    Unknown mode ffffffff
    : -- no code accessible --
    Modules:
    Module Address Debug info Name (15 modules)
    PE 7b810000-7b9b0000 Deferred kernel32
    PE 7bc10000-7bc14000 Deferred ntdll
    PE 7eef0000-7eef3000 Deferred usp10
    PE 7f180000-7f184000 Deferred winex11
    PE 7f370000-7f379000 Deferred msacm32
    PE 7f3a0000-7f3a4000 Deferred rpcrt4
    PE 7f430000-7f438000 Deferred ole32
    PE 7f550000-7f5c8000 Deferred winmm
    PE 7f670000-7f67a000 Deferred mpr
    PE 7f740000-7f744000 Deferred imm32
    PE 7f9f0000-7f9f4000 Deferred version
    PE 7fa10000-7fa14000 Deferred advapi32
    PE 7fa90000-7fa97000 Deferred gdi32
    PE 7fbb0000-7fbeb000 Deferred user32
    PE 7ffd0000-7ffd3000 Deferred winevdm
    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
    00000018 0
    00000013 0
    0000001a plugplay.exe
    00000020 0
    0000001f 0
    0000001b 0
    00000021 explorer.exe
    00000027 0
    00000026 0
    00000025 0
    00000022 0
    00000023 (D) C:\windows\system32\winevdm.exe
    00000028 0 <==
    00000024 0
    System information:
    Wine build: wine-1.8.7 (Debian 1.8.7-2)
    Platform: i386 (WOW64)
    Version: Windows 5.1 (0)
    Host system: Linux
    Host version: 4.9.0-6-amd64


I don't know what that means, but it seems to be the same as it has always been. ls there anything else I can do?

Thank you


Top 
Display posts from previous:  Sort by  
 
 Page 1 of 1 [ 8 posts ] 




Board index » WineHQ » Wine Help » Linux


Who is online

Users browsing this forum: Google [Bot] and 21 guests

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: