http://bugs.winehq.org/show_bug.cgi?id=23937
Summary: [The Master Genealogist 4.0d] Perhaps the DPMI free memory information needs some hard limits. Product: Wine Version: 1.3.0 Platform: x86 URL: http://appdb.winehq.org/objectManager.php?sClass=versi on&iId=11482 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dos AssignedTo: wine-bugs@winehq.org ReportedBy: saturn_systems@yahoo.com
(In reply to comment #21 From Andrew Nguyen ) of bug 12874 <snip>
For the next problem:
fixme:int31:DPMI_xalloc failed to allocate linearly growing memory (2148921344 bytes), using non-linear growing... fixme:int31:DPMI_xalloc failed to allocate any memory of 2148921344 bytes! fixme:int31:DPMI_xalloc failed to allocate linearly growing memory (2148511744 bytes), using non-linear growing... fixme:int31:DPMI_xalloc failed to allocate any memory of 2148511744 bytes! fixme:int31:DPMI_xalloc failed to allocate linearly growing memory (2148102144 bytes), using non-linear growing... fixme:int31:DPMI_xalloc failed to allocate any memory of 2148102144 bytes! ...
For some reason, the application uses the queried DPMI free memory information to try to allocate all available memory, and it spends a huge amount of time doing this until it crashes. Hacking DPMI_xalloc to reject allocation sizes larger than 512 MB (or some reasonable arbitrary value) gets the application to start. Perhaps the DPMI free memory information needs some hard limits for applications like this one. There are many more issues after this, but that would seem to belong in another bug report.
TMG 4.0d freezes and is unresponsive as per Andrews explanation.
http://bugs.winehq.org/show_bug.cgi?id=23937
--- Comment #1 from nathan.n saturn_systems@yahoo.com 2010-09-09 21:33:23 CDT --- present in wine 1.3.1 and wine 1.3.2
http://bugs.winehq.org/show_bug.cgi?id=23937
--- Comment #2 from nathan.n saturn_systems@yahoo.com 2010-09-10 00:15:26 CDT --- Ok Found a way to get TMG4 running:
Create a "config.fpw" (or download the attachment ) with the following settings: ----------------- TITLE=The Master Genealogist
MVCOUNT=3000
CODEPAGE=AUTO
POINT="."
MEMLIMIT = 5, 16384 ,262144 ----------------- And copy "config.fpw" to the "c:\TMGW" directory before starting the program.
Only question is why TMG4 works fine on Window 3.1 thru Windows XP without needing this change? -- Used the following useful tidbits to find the workaround: ----------- http://news.rootsweb.com/th/read/TMG/2002-05/1020890723
RootsWeb: TMG-L RE: [TMG] Installation trouble - Suggestions . . . .:
From: "Mycek-Memoli, Anne" Subject: RE: [TMG] Installation trouble - Suggestions . . . .
Date: Wed, 8 May 2002 16:45:23 -0400
<snip>
4. When Ultimate Family Tree started working, and TMG still wasn't working
(both are FoxPro for Windows Apps), I looked for similarities, and found
CONFIG.FPW files associated with both of the programs. I printed a copy of
the Ultimate Family Tree - CONFIG.FPW file, and started adding parameters to
the TMG - CONFIG.FPW file, and after some trial and error, finally got TMG
working.
The parameters that I tweaked (in the TMG - CONFIG.FPW file) were:
MEMLIMIT=50 (it was originally set to 100, which means 100% of memory)
<snip>
So my Config.FPW file looks like this:
TITLE=The Master Genealogist
RESOURCE = TMGWUSR.DBF
MVCOUNT = 3000
CODEPAGE = AUTO
POINT="."
MEMLIMIT=50
<snip> -------------------------------------------------- Which lead me to
http://www.tek-tips.com/viewthread.cfm?qid=1043754&page=6
Microsoft: FoxPro (old versions 1 to 2.6) Forum(thread182-1043754) Error: Too many memory variables
rgbean (Programmer)
19 Apr 05 15:12
You may need the other two parameters for MEMLIMIT. I use:
CODE
MEMLIMIT = 80, 2048, 16384
Remember that the first number is the percentage of available memory to use, the second is the minimum RAM memory required (in K's), and the third is the maximum RAM requested. FP always uses the lesser of the first and third, and in my experience, if you give it more than 16MB, it can also fail.
Unless you've changed the number of varibles required in the program, 1024 should be sufficient.
One last thing are you sure you are actually using this CONFIG.FPW? Do you explicitly use this CONFIG by using the command line switch -c in your shortcut?
--- And: http://rickschummer.com/blog/2008/06/vfp-include-configfpw-in-exe.html
Rick Schummer VFP: Include Config.FPW in EXE Sunday, June 22, 2008
http://bugs.winehq.org/show_bug.cgi?id=23937
--- Comment #3 from nathan.n saturn_systems@yahoo.com 2010-09-10 00:16:24 CDT --- Created an attachment (id=30669) --> (http://bugs.winehq.org/attachment.cgi?id=30669) modified config.fpw to copy to c:\tmgw
http://bugs.winehq.org/show_bug.cgi?id=23937
nathan.n saturn_systems@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win16
http://bugs.winehq.org/show_bug.cgi?id=23937
--- Comment #4 from nathan.n saturn_systems@yahoo.com 2010-10-02 21:44:33 CDT --- present in wine 1.3.4
http://bugs.winehq.org/show_bug.cgi?id=23937
--- Comment #5 from nathan.n saturn_systems@yahoo.com 2011-09-21 23:00:13 CDT --- Present in Wine 1.3.28
http://bugs.winehq.org/show_bug.cgi?id=23937
--- Comment #6 from nathan.n saturn_systems@yahoo.com 2011-11-09 02:15:28 CST --- Present in Wine 1.3.32
http://bugs.winehq.org/show_bug.cgi?id=23937
--- Comment #7 from Austin English austinenglish@gmail.com 2013-11-13 16:52:33 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.6 or newer) wine? If so, please attach the terminal output in 1.7.6 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=23937
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #8 from Austin English austinenglish@gmail.com --- Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=23937
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Austin English austinenglish@gmail.com --- Closing.