[Bug 1010] Unhandled exception in VFP6R.DLL (Visual FoxPro 6)

[Wine Bugs]

http://bugs.winehq.com/show_bug.cgi?id=1010





------- Additional Comments From z_god at wanadoo.nl  2003-23-06 05:28 -------
Bug comments restored from Gmane.org: 
 
I've been trying to install and run a simple Visual Fox Pro 6 application. 
 
At first, I was having trouble registering MSCAL.OCX. I solved that by adding 
the line "comcat"="builtin,native" to the DLLOverrides section of 
~/.wine/config. The application installed, and all the components registered 
properly. 
 
But when I try to run the application, I'm immediately dropped to the debug 
window, with the following (final) statement: 
 
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code 
(0x0c0b4ce6). 
In 32-bit mode. 
0x0c0b4ce6 (VFP6R.DLL.DllWinMain+0x5e1e9 in 
C:\WINDOWS\SYSTEM\VFP6R.DLL): mov1 
0x0(%eax),%eax 
 
 
------- Additional Comments From oscar.valdez <at> plastipak.com.sv  2002-09-05 
11:11 ------- 
I've gotten over this problem by setting "nt40", "win2k" or "winxp" as 
the 
Windoze version to imitate. 
 
The Visual FoxPro application now runs, although with "OLE exception errors". 
That's a completely different matter though, so I consider this particular case 
closed. 
 
 
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de  2002-09-05 11:24 
------- 
So you want to tell us that Visual FoxPro only runs on an NT-based Windows version 
(NT, Win 2000, XP) and never on a Win 9x system, right ? 
Or why else would you consider this bug to be closed ? 
 
 
------- Additional Comments From oscar.valdez <at> plastipak.com.sv  2002-09-05 
11:35 ------- 
No, that's not exactly the way I would interpret things. 
 
At least on Wine, Visual FoxPro "runs" when Wine is imitating NT40, W2K or WXP, 
but not when it's imitating W9x. It seems like a simple workaround. 
 
And I say "runs", because I'm still getting OLE exception errors. 
 
 
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de  2002-09-05 11:46 
------- 
Did you realize what you just said ? You said it's a *workaround*, not a bug fix. 
Thus this bug is still valid :) 
(as I'm damn sure that VFP *should* run on a Win 9x based system) 
 
Sounds like there's a problem with some Wine Win9x support code that's being run 
when the app decides to switch to Win9x mode instead of NT mode. 
 
So should that bug be reopened ? 
(please submit a --debugmsg +Relay log file in win9x mode in this case) 
 
 
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de  2002-09-05 11:47 
------- 
Argl, I meant --debugmsg +relay 
 
 
------- Additional Comments From oscar.valdez <at> plastipak.com.sv  2002-09-13 
09:45 ------- 
Created an attachment (id=290)
 --> (http://bugs.winehq.com/attachment.cgi?id=290&action=view) 
Debug messages when imitating Win 9x 
 
 
------- Additional Comments From oscar.valdez <at> plastipak.com.sv  2002-09-13 
09:46 ------- 
Created an attachment (id=291)
 --> (http://bugs.winehq.com/attachment.cgi?id=291&action=view) 
More (but similar) debug messages when imitating Win 9x 
 
 
------- Additional Comments From oscar.valdez <at> plastipak.com.sv  2002-09-13 
09:47 ------- 
As Andreas Mohr pointed out, the bug persists when Wine imitates Win 9x, so it 
can't really be considered closed. 
 
 
------- Additional Comments From oscar.valdez <at> plastipak.com.sv  2002-09-18 
18:13 ------- 
When imitating Win9x and thus causing the unhandled exception, the debugger and 
it's bt command report: 
 
> Unhandled exception: page fault on read access to 0x0000000 in 32-bit code 
(0x0c0b4ce6) 
> In 32-bit mode 
> 0x0c0b4ce6 (VFP6R.DLL.DllWinMain+0x5e1e9 in 
C:\WINDOWS\SYSTEM\VFP6R.DLL): movl 
0x0(%eax),%eax 
> Wine-dbg>bt 
> Backtrace: 
> 0 0x0c0b4ce6 (VFP6R.DLL.DllWinMain+0x5e1e9 in 
C:\WINDOWS\SYSTEM\VFP6R.DLL) 
(ebp=405d664c) 
> 1 0x0c0f162e (VFP6R.DLL.DllOleInit+0x.6b8f in 
C:\WINDOWS\SYSTEM\VFP6R.DLL) 
(ebp=0000100f) 
 
 
------- Additional Comments From aztecconsultants <at> java.fsbusiness.co.uk 
2003-04-02 12:03 
------- 
I have to say that this bug is also to be found in Visual FoxPro 6.0 SP5  
running under native Win2K SP3.  It only occurs if you use an OCX control on a  
form.  I believe that it is related to an OCX control firing internal events. 
 
When considering GPF faults with Visual FoxPro it is better to make sure that  
they do not occur on the native platform.  FoxPro is single threaded (or stolen  
zero threaded during big SQL extracts!) so how it responds to underlying  
windows messages is very precarious. 
 
To date I have about 20 different variations of various unacknoledge Visual  
FoxPro GPFs.  I have to work around then all during my Visual FoxPro  
development.  I did report them via MS WWW site but noticed months later that  
they had no outstanding bugs with this horrid product so I stopped reporting  
them! 
 
I am now a Sun Java Certified programmer and hope never to have to deal with  
this FoxPro product again. 
 
 
Anton 
 
 
------- Additional Comments From abdulet <at> x-mail.net  2003-06-06 06:04 ------- 
seems visual fox only works in a windowsNT wine installation/simulation look 
here for details http://appdb.winehq.com/appview.php?appId=296 
 
S8^> 

-- 
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.