problem trying to run a Visual Foxpro app
rick at valeoinc.com
Wed Jan 22 11:08:39 CST 2003
On Wed, 2003-01-22 at 10:41, Joe Black wrote:
> On Wednesday 22 January 2003 10:33, Rick Romero wrote:
> > Outstanding Issues with Visual FoxPro that I know of:
> > 1. WAIT WINDOWS don't display properly. The graphics are
> > drawn after, and over, the text. The text is drawn with
> > gdi32.ExtTextOutA, and the window appears to be external.
> > Transgamings Wine doesn't seem to do Managed Windows, so the
> > WAIT WINDOW actually gets a 'windows border', with
> > Min/Max/Close buttons. That's probably the source of the
> > issue - windows created by VFP to show how long a SELECT is
> > taking display fine, and without the 'windows border'.
> > 2. No record locking. Apparently a patch was submitted some
> > time ago, but wasn't accepted.
> > 3. Window resizing. I've noticed in the IDE that the window
> > resizing doesn't work quite right.. not a killer, but a
> > nuisance.
> > AFAICS, the apps run pretty well.. unfortunately, I haven't
> > had a chance to test printing, but I know that's worked in the
> > past.
> > Rick
> And On Wednesday 22 January 2003 11:01, Paul McNett wrote:
> > Visual Foxpro only works when Wine is emulating a NT-based
> > system (nt40, win2k, winxp). Actually, I think for VFP6, Wine
> > needs to emulate nt351.
> I'm trying to run a production-quality database app based upon
> VFP (not sure what version---probably 6) and am also having
> problems, but not with fonts---I get an unhandled exception:
> localhost# wine --debugmsg +relay,+seh sw.exe
> shows (among other things):
> Unhandled exception: page fault on write access to 0x0000044a in
> 32-bit code (0x40fff7a3).
> In 32-bit mode.
> Register dump:
> CS:0023 SS:002b DS:002b ES:002b FS:02e7 GS:0307
> EIP:40fff7a3 ESP:41252880 EBP:41252898 EFLAGS:00210246( R- 00
> I Z- -P1 )
> EAX:00000019 EBX:4101b2e4 ECX:41264400 EDX:00000019
> ESI:00000400 EDI:00000000
> Stack dump:
> 0x41252880: 00000050 00000019 4101b2e4 41252914
> 0x41252890: 00000050 00000019 412528dc 410006da
> 0x412528a0: 00000400 4101b2e4 00008f16 00000000
> 0x412528b0: 4206fc84 4212a2d0 00000000 00001000
> 0x412528c0: 00010000 7fffffff 00000001 41006a2b
> 0x412528d0: 4101b2e4 0000583e 000005f0 412528ec
> 005c: sel=02e7 base=41263000 limit=00000fff 32-bit rw-
> =>0 0x40fff7a3 (WINEDOS.DLL.EntryPoint+0xff7 in winedos.dll.so)
> 1 0x410006da (WINEDOS.DLL.EntryPoint+0x1f2e in winedos.dll.so)
> 2 0x4100cbc0 (WINEDOS.DLL.EntryPoint+0xe414 in winedos.dll.so)
> 3 0x4100e851 (WINEDOS.DLL.EntryPoint+0x100a5 in winedos.dll.so)
> 4 0x400bcc7a (KERNEL32.DLL.__wine_call_from_16_regs+0x13e in
> libntdll.dll.so) (ebp=41252c08)
> 5 0x02f7:0xe9d5 (bp=03f7)
> 6 0x02f7:0x7551 (bp=656c)
> 7 0x40077a0e (NTDLL.DLL.RtlSetPropertySetClassId+0x2a0c6 in
> libntdll.dll.so) (ebp=41252f0c)
> 8 0x40072fbe (NTDLL.DLL.RtlSetPropertySetClassId+0x25676 in
> libntdll.dll.so) (ebp=41252f20)
> 9 0x400a5554 (NTDLL.DLL.wine_server_call+0x732c in
> libntdll.dll.so) (ebp=41252f38)
> 10 0x400a4970 (NTDLL.DLL.wine_server_call+0x6748 in
> libntdll.dll.so) (ebp=41252ff4)
> 11 0x420da1ca (NTDLL.DLL.sscanf+0x78e0a) (ebp=00000000)
> 0x40fff7a3: movw $0x50,0x4a(%esi)
> Address Module Name
> 0x08050000-08052000 (PE) Y:\cxoffice\bin\wineloader
> 0x40040000-40042000 (PE) C:\WINDOWS\SYSTEM\NTDLL.DLL
> 0x40730000-40732000 (PE) C:\WINDOWS\SYSTEM\WINMM.DLL
> 0x407a0000-407a2000 (PE) C:\WINDOWS\SYSTEM\USER32.DLL
> 0x408c0000-408c2000 (PE) C:\WINDOWS\SYSTEM\GDI32.DLL
> 0x40930000-40932000 (PE) C:\WINDOWS\SYSTEM\ADVAPI32.DLL
> 0x40970000-40972000 (PE) C:\WINDOWS\SYSTEM\KERNEL32.DLL
> 0x40a50000-40a52000 (PE) C:\WINDOWS\SYSTEM\X11DRV.DLL
> 0x40bc0000-40bc2000 (PE) C:\WINDOWS\SYSTEM\IMM32.DLL
> 0x40c30000-40c32000 (PE) C:\WINDOWS\SYSTEM\WINEOSS.DRV
> 0x40c50000-40c52000 (PE) C:\WINDOWS\SYSTEM\MSACM.DRV
> 0x40da0000-40da2000 (PE) C:\WINDOWS\SYSTEM\MIDIMAP.DRV
> 0x40ff0000-40ff2000 (PE) C:\WINDOWS\SYSTEM\WINEDOS.DLL
> This is actually output from Codeweavers' CrossOver version of
> wine, but when I do the same for Wine-20030115 (and the previous
> version), I get very similar output.
At what point does the exception occur? On startup? When you're
working within the app? It looks like FoxPro is trying to do a !run
command to me - I haven't tried that...
It also could be loading a module (say SMTP or ZIP) that Paul or I don't
use.. or haven't tried.
> Anyone here know if the issues that Rick and Paul mentioned above
> would rule out using this database app under wine in a
> business/production environment? Specifically, I'm concerned
> about problems with record locking. This app needs to be run by
> several different users on several different computers
> simultaneously (which is no problem in native windoze, but what
> about wine). The reason I ask (aside from the obvious) is that
> I'm considering paying Codeweavers to fix the bug that's causing
> the unhandled exception above, but if the issues that Rick and
> Paul mentioned would prevent using the app in a business
> environment as described, then I might be wasting my money by
> just fixing this one little problem---only to find that the
> other already known issues with VFP would prevent me being able
> to do what I need to do.
> Thanks for any thoughts.
Have you contacted CodeWeavers? I did last year, and I don't think they
fix one issue. I think they'll fix the whole app. There's a base price
for initial testing and troubleshooting, and if your issue can be fixed
in X number of hours, you're done. If not, then you pay an hourly rate
on top of it.
They're prices are reasonable, but you have to justify what you're
The biggest issue is Record Locks..
Paul mentioned he had found a patch for doing record locks, but I didn't
get a link... It might be a functional patch, but not up to 'standards'
for inclusion in Wine. I'm not sure if Codeweavers would use existing
work, just to make it work (kinda like CXO), or actually make it right.
> wine-users mailing list
> wine-users at winehq.com
Valeo, Inc. ph: 262.695.4841
Sussex, WI. fax: 262.695.4850
Rick at valeoinc.com
More information about the wine-users