Crash from "wine ./SETUP.EXE".

Questions about Wine on Linux
Post Reply
peasthope
Level 1
Level 1
Posts: 6
Joined: Sat Sep 28, 2019 11:21 am

Crash from "wine ./SETUP.EXE".

Post by peasthope » Sat Sep 28, 2019 11:41 am

Wine in Debian 10 here.

cd aDirectory ; wine ./SETUP.EXE
gave an immediate crash with backtrace http://easthope.ca/backtrace .

Tips?

Thanks, ... Peter E.

jkfloris
Level 6
Level 6
Posts: 688
Joined: Thu Aug 14, 2014 10:10 am

Re: Crash from "wine ./SETUP.EXE".

Post by jkfloris » Sun Sep 29, 2019 4:47 am

Is this a MSDOS application? Did you install dosbox?

Is there a free/ demo version to test the application?

peasthope
Level 1
Level 1
Posts: 6
Joined: Sat Sep 28, 2019 11:21 am

Re: Crash from "wine ./SETUP.EXE".

Post by peasthope » Sun Sep 29, 2019 9:07 am

Thanks for the reply.

The software is for Windows and came with a JVC camera.
I should have given this link also.
http://easthope.ca/JVC.KY-F.TWAINdiskette.jpg

... Peter E.

jkfloris
Level 6
Level 6
Posts: 688
Joined: Thu Aug 14, 2014 10:10 am

Re: Crash from "wine ./SETUP.EXE".

Post by jkfloris » Tue Oct 01, 2019 11:15 am

Windows drivers don't work with Wine. Does Debian recognize the camera?

peasthope
Level 1
Level 1
Posts: 6
Joined: Sat Sep 28, 2019 11:21 am

Re: Crash from "wine ./SETUP.EXE".

Post by peasthope » Fri Oct 11, 2019 3:33 pm

Yes, Debian recognizes the camera. Here is the output from hwinfo --scsi. Is recognition as a "Storage Device" acceptable? If so the next step would be to configure to also be available in Wine? Then try to configure the JVC software to access the pseudo-Windows device. Any further tips before I plow ahead?

Thanks, ... Peter E.

20: SCSI 06.0: 10680 Storage Device
[Created at scsi.1783]
Unique ID: olmp.0cgEuxP19dC
Parent ID: oxTw.8Wc+vtM+OBC
SysFS ID: /class/scsi_generic/sg2
SysFS BusID: 0:0:6:0
Hardware Class: unknown
Model: "JVC KY-F70"
Vendor: "JVC"
Device: "KY-F70"
Revision: "1.00"
Driver: "advansys"
Driver Modules: "advansys", "advansys"
Device File: /dev/sg2
Device Number: char 21:2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #10 (SCSI storage controller)

== no further output from hwinfo ==

peasthope
Level 1
Level 1
Posts: 6
Joined: Sat Sep 28, 2019 11:21 am

Re: Crash from "wine ./SETUP.EXE".

Post by peasthope » Fri Oct 11, 2019 5:57 pm

A few additional points.

According to hwinfo, the camera is character device /dev/sg2. Must it be mounted in Linux
before Wine can access it? For linux to mount sg2, a driver will be necessary; correct?

Thanks, ... Peter E.

jkfloris
Level 6
Level 6
Posts: 688
Joined: Thu Aug 14, 2014 10:10 am

Re: Crash from "wine ./SETUP.EXE".

Post by jkfloris » Sat Oct 12, 2019 2:47 pm

Must it be mounted in Linux before Wine can access it?
Yes. First try to mount the device on Debian.
Unfortunately, I don't have any experience with SCSI devices.

peasthope
Level 1
Level 1
Posts: 6
Joined: Sat Sep 28, 2019 11:21 am

Re: Crash from "wine ./SETUP.EXE".

Post by peasthope » Sat Oct 26, 2019 11:50 am

> Yes. First try to mount the device on Debian.

The most common block device is a store. With SCSI, a disk drive.
Probably Debian can mount almost any SCSI drive since years ago.
If the camera were to behave as a SCSI drive, I'd expect that to be
mentioned in the manual and for Debian to mount it with no difficulty.

Not surprisingly, no success in mounting the /dev/sg2 reported by hwinfo.
Therefore I'm trying to run the JVC Windows software through Wine.

In Debian, created directory /home/peter/JVC, copied the contents of
the installer diskette there and in winecfg declared the JVC directory
as the A: drive. Also in winecfg, set the system to Windows 98.

Then did "wine A:\SETUP.EXE" yielding a fault with this backtrace.

Unhandled exception: page fault on read access to 0x000000c2 in 32-bit code (0x7f5c1241).
Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:003b GS:0033
EIP:7f5c1241 ESP:0065f600 EBP:0065f658 EFLAGS:00010202( R- -- I - - - )
EAX:000000c2 EBX:7f612eec ECX:00000000 EDX:0000003b
ESI:0000008e EDI:7f5b8892
Stack dump:
0x0065f600: 00000000 00000000 00000000 00000000
0x0065f610: 00000000 00000000 00000000 00000001
0x0065f620: 00000000 00000001 00000001 0065f7f4
0x0065f630: 00000005 00000000 00000000 b5c9c000
0x0065f640: 00000000 00000000 7f5c0adb 7f612eec
0x0065f650: 0065fac0 0065f7f4 0065f688 7f5c1c8a
Backtrace:
=>0 0x7f5c1241 (0x0065f658)
1 0x7f5c1c8a (0x0065f688)
2 0x7bc46338 (0x0065f6f8)
3 0x7bc855ce (0x0065f758)
4 0x7bc85ab6 (0x0065f7d8)
5 0xdeadbabe (0x0065fb38)
6 0x7f5f4e21 (0x0065fb88)
7 0x7f5df131 (0x0065feb8)
8 0x7f5e95b4 (0x0065fed8)
9 0x7bc82d10 (0x0065feec)
10 0x7bc862c9 (0x0065ffdc)
11 0x7bc82d02 (0x0065ffec)
0x7f5c1241: cmpw $64,0x0(%eax)
Modules:
Module Address Debug info Name (13 modules)
PE 7b420000-7b5d0000 Deferred kernel32
PE 7bc10000-7bc14000 Deferred ntdll
PE 7ef30000-7ef39000 Deferred msacm32
PE 7ef60000-7ef64000 Deferred rpcrt4
PE 7f000000-7f028000 Deferred ole32
PE 7f140000-7f1b8000 Deferred winmm
PE 7f280000-7f28b000 Deferred mpr
PE 7f350000-7f354000 Deferred imm32
PE 7f630000-7f634000 Deferred version
PE 7f660000-7f664000 Deferred advapi32
PE 7f6d0000-7f6d7000 Deferred gdi32
PE 7f810000-7f8f7000 Deferred user32
PE 7ffd0000-7ffd3000 Deferred winevdm
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
00000022 0
0000001d 0
00000013 0
00000010 0
0000000f 0
00000011 winedevice.exe
00000018 0
00000017 0
00000016 0
00000012 0
00000019 plugplay.exe
0000001f 0
0000001e 0
0000001a 0
0000001b explorer.exe
00000028 0
00000027 0
00000025 0
0000001c 0
00000020 winedevice.exe
00000026 0
00000024 0
00000023 0
00000021 0
00000029 (D) C:\windows\system32\winevdm.exe
0000002b 0 <==
0000002a 0
System information:
Wine build: wine-4.0 (Debian 4.0-2)
Platform: i386
Version: Windows 98
Host system: Linux
Host version: 4.19.0-6-686-pae

Similar results for the Windows 95 and NT systems.

Does 0x000000c2 identify a drive? Any implication from that?

Any ideas about settings in winecfg? Other ideas?

Thanks, ... Peter E.

peasthope
Level 1
Level 1
Posts: 6
Joined: Sat Sep 28, 2019 11:21 am

Re: Crash from "wine ./SETUP.EXE".

Post by peasthope » Fri Nov 08, 2019 10:29 pm

Another approach is use Wine to install the StarTech software for a
USB3HDCAP video capture device and then capture images via this device
and Wine. Ref.
https://www.startech.com/AV/Converters/ ... ~USB3HDCAP

This is the attempt to install the StarTech software.

peter@imager:/media/peter/USB/Startech$ wine ./Setup.exe
0030:err:mscoree:LoadLibraryShim error reading registry key for installroot
0030:err:mscoree:LoadLibraryShim error reading registry key for installroot
0030:err:mscoree:LoadLibraryShim error reading registry key for installroot
0030:err:mscoree:LoadLibraryShim error reading registry key for installroot
DEVCON.X86.EXE failed.
0030:err:msi:custom_get_thread_return Invalid Return Code 10
0030:err:msi:ITERATE_Actions Execution halted, action L"MsiProcessDrivers" returned 1603
0030:err:msi:ITERATE_Actions Execution halted, action L"ExecuteAction" returned 1603
peter@imager:/media/peter/USB/Startech$

Any ideas about the meaning of "registry key for installroot"?
Can the failure be resolved?

Thanks, ... Peter E.

Post Reply