[Bug 32713] Fighting Force crashes on startup (32-bit PE from Win9x era calls 'int 0x1a', PCI BIOS v2.0c - find PCI device function)
wine-bugs at winehq.org
wine-bugs at winehq.org
Tue Aug 26 15:06:22 CDT 2014
https://bugs.winehq.org/show_bug.cgi?id=32713
Anastasius Focht <focht at gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |download
Status|UNCONFIRMED |RESOLVED
URL| |www.abandonware-france.org/
| |ltf_abandon/clic.php?idtele
| |=21100&type
CC| |focht at gmx.net
Resolution|--- |WONTFIX
Summary|fforce.exe had a serious |Fighting Force crashes on
|problem and closed when I |startup (32-bit PE from
|tried to run it. |Win9x era calls 'int 0x1a',
|installation was successful | PCI BIOS v2.0c - find PCI
|before that |device function)
--- Comment #5 from Anastasius Focht <focht at gmx.net> ---
Hello folks,
confirming.
Brain damage that is not going to work on modern Windows OS:
--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/Core Design Ltd/Fighting Force
$ WINEDEBUG=+tid,+seh,+relay wine ./fforce.exe >>log.txt 2>&1
...
0023:trace:seh:raise_exception code=c0000005 flags=0 addr=0x4366f1 ip=004366f1
tid=0023
0023:trace:seh:raise_exception info[0]=00000000
0023:trace:seh:raise_exception info[1]=ffffffff
0023:trace:seh:raise_exception eax=0000b102 ebx=00000000 ecx=00000061
edx=00001033 esi=00000000 edi=00001033
0023:trace:seh:raise_exception ebp=0033fd38 esp=0033fafc cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00010246
0023:trace:seh:call_stack_handlers calling handler at 0x454154 code=c0000005
flags=0
0023:Call KERNEL32.UnhandledExceptionFilter(0033f5d0) ret=0045827a
0023:Call KERNEL32.IsBadCodePtr(00371d70) ret=004597b1
0023:Ret KERNEL32.IsBadCodePtr() retval=00000000 ret=004597b1
wine: Unhandled page fault on read access to 0xffffffff at address 0x4366f1
(thread 0023), starting debugger...
...
Unhandled exception: page fault on read access to 0xffffffff in 32-bit code
(0x004366f1).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:004366f1 ESP:0033fafc EBP:0033fd38 EFLAGS:00010246( R- -- I Z- -P- )
EAX:0000b102 EBX:00000000 ECX:00000061 EDX:00001033
ESI:00000000 EDI:00001033
...
Backtrace:
=>0 0x004366f1 in fforce (+0x366f1) (0x0033fd38)
1 0x0042dedf in fforce (+0x2dede) (0x7ec789d0)
2 0xd1e80004 (0x01d06854)
0x004366f1: int $0x1a
Modules:
Module Address Debug info Name (66 modules)
PE 340000- 358000 Deferred winstr
PE 360000- 37d000 Deferred dec130
PE 380000- 3a3000 Deferred edec
PE 3b0000- 3cb000 Deferred winsdec
PE 400000- c7f000 Export fforce
PE 10000000-10013000 Deferred winplay
...
Threads:
process tid prio (all id:s are in hex)
...
00000022 (D) C:\Program Files\Core Design Ltd\Fighting Force\fforce.exe
00000023 0 <==
--- snip ---
Disassembly:
--- snip ---
004366C0 55 PUSH EBP
004366C1 8BEC MOV EBP,ESP
004366C3 81EC 30020000 SUB ESP,230
004366C9 53 PUSH EBX
004366CA 56 PUSH ESI
004366CB 57 PUSH EDI
004366CC BF 33100000 MOV EDI,1033
004366D1 33DB XOR EBX,EBX
004366D3 C745 FC 610000>MOV DWORD PTR SS:[EBP-4],61
004366DA 897D F0 MOV DWORD PTR SS:[EBP-10],EDI
004366DD 895D F4 MOV DWORD PTR SS:[EBP-C],EBX
004366E0 895D F8 MOV DWORD PTR SS:[EBP-8],EBX
004366E3 8B4D FC MOV ECX,DWORD PTR SS:[EBP-4]
004366E6 8B55 F0 MOV EDX,DWORD PTR SS:[EBP-10]
004366E9 8B75 F4 MOV ESI,DWORD PTR SS:[EBP-C]
004366EC B8 02B10000 MOV EAX,0B102
004366F1 CD 1A INT 1A ; sure ...
004366F3 72 07 JB SHORT fforce.004366FC
...
--- snip ---
http://www.delorie.com/djgpp/doc/rbinter/id/82/23.html
--- quote ---
Category: expansion bus BIOSes
INT 1A - PCI BIOS v2.0c+ - FIND PCI DEVICE
AX = B102h
CX = device ID (see #00735,#00742,#00743,#00873,#00875)
DX = vendor ID (see #00732)
SI = device index (0-n)
Return: CF clear if successful
CF set on error
AH = status (00h,83h,86h) (see #00729)
00h successful
BH = bus number
BL = device/function number (bits 7-3 device, bits 2-0 func)
EAX, EBX, ECX, and EDX may be modified
all other flags (except IF) may be modified
Notes: this function may require up to 1024 byte of stack; it will not
enable
interrupts if they were disabled before making the call
device ID FFFFh may be reserved as a wildcard in future implementations
the meanings of BL and BH on return were exchanged between the initial
drafts of the specification and final implementation
all devices sharing a single vendor ID and device ID may be enumerated
by incrementing SI from 0 until error 86h is returned
SeeAlso: AX=B182h
--- quote ---
--- quote ---
-=[ ProtectionID v0.6.5.5 OCTOBER]=-
(c) 2003-2013 CDKiLLER & TippeX
Build 31/10/13-21:09:09
Ready...
Scanning -> C:\Program Files\Core Design Ltd\Fighting Force\fforce.exe
File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 468992 (072800h)
Byte(s)
[File Heuristics] -> Flag : 00000000000001001100000000000000 (0x0004C000)
[Entrypoint Section Entropy] : 6.57
[CompilerDetect] -> Visual C++ 5.0
[!] File appears to have no protection or is using an unknown protection
- Scan Took : 0.290 Second(s) [000000122h tick(s)] [533 scan(s) done]
--- quote ---
$ sha1sum jeu-01230-fforce-PCwin.7z
48ba373878ac511d4c49a263354c6a8e0bd0f631 jeu-01230-fforce-PCwin.7z
$ du -sh jeu-01230-fforce-PCwin.7z
407M jeu-01230-fforce-PCwin.7z
$ wine --version
wine-1.7.25-21-gc87901d
Regards
--
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.
More information about the wine-bugs
mailing list