For some years I've used TMG. With release 4.0 (and subsequent updates)
I have a truly strange problem. When first installed it works OK; but then
it very shortly starts giving me the "Black Screen of Death aka BSD
" -- I hit the icon to start and the screen goes black and the system locks
up totally -- sometimes. Shortly after that I get the BSD every time.
If I totally uninstall TMG and reinstall I go through the same pattern
of OK, sometimes OK, to BSD always.
TMG says it's a memory allocation problem related to FoxPro. Even if I
delete everything running on the system except the Win98 kernel, I still get
the BSD.
I've switched over to using Legacy 3.0 Pro which has 95% of the same
features, but I would still like to know what causes this nasty problem.
Ideas??
Jim Cobbs
jim...@nospam.bigfoot.com
--
Pam
pa...@msn.com
http://www.geocities.com/Heartland/Woods/6771/
"James Cobbs" <jac...@worldnet.att.net> wrote in message
news:QI5k7.7410$KV3.5...@bgtnsc04-news.ops.worldnet.att.net...
James Cobbs wrote in a message to All:
JC> From: "James Cobbs" <jac...@worldnet.att.net>
JC> Sidebar: Trust me on this: I am a very experienced PC/Windows
JC> user; my computer has plenty of speed, memory and hard disk space.
I have a 450Mhz AMD processor, 64 megs of RAM, and just over 1 gig free disk
space.
JC> For some years I've used TMG. With release 4.0 (and subsequent
JC> updates) I have a truly strange problem. When first installed it
JC> works OK; but then it very shortly starts giving me the "Black
JC> Screen of Death aka BSD " -- I hit the icon to start and the screen
JC> goes black and the system locks up totally -- sometimes. Shortly
JC> after that I get the BSD every time.
JC> If I totally uninstall TMG and reinstall I go through the same
JC> pattern of OK, sometimes OK, to BSD always.
JC> TMG says it's a memory allocation problem related to FoxPro.
JC> Even if I delete everything running on the system except the Win98
JC> kernel, I still get the BSD.
I've had the same experience, and I've given up on TMG.
I've found it very unstable, and I've got tired of ininstalling it and
reinstalling it every time I try to enter or edit data.
JC> I've switched over to using Legacy 3.0 Pro which has 95% of the
JC> same features, but I would still like to know what causes this
JC> nasty problem.
If you find out, please let me know. The TMG support people are unable to help.
Perhaps they need to rewrite the program in something other than FoxPro.
Keep well
Steve Hayes
WWW: http://www.geocities.com/Athens/7734/steve.htm
E-mail: haye...@yahoo.com
FamilyNet <> Internet Gated Mail
http://www.fmlynet.org
> <snip>
> I have a 450Mhz AMD processor, 64 megs of RAM, and just over 1 gig free disk
> space.
That's plenty of free space and not the issue.
> <snip> JC> TMG says it's a memory allocation problem related to FoxPro.
> JC> Even if I delete everything running on the system except the Win98
> JC> kernel, I still get the BSD.
>
> I've had the same experience, and I've given up on TMG.
>
> I've found it very unstable, and I've got tired of ininstalling it and
> reinstalling it every time I try to enter or edit data.
Uninstalling & reinstalling is senseless wasted effort and not a fix in any way.
> JC> I've switched over to using Legacy 3.0 Pro which has 95% of the
> JC> same features, but I would still like to know what causes this
> JC> nasty problem.
>
> If you find out, please let me know. The TMG support people are unable to help.
That statement is FALSE. TMG support has offered a workaround which is to load TMG
right after booting. It may be a pain to have to do that, but it supposedly always
works. You can lead a horse to water, but . . .
> Perhaps they need to rewrite the program in something other than FoxPro.
Version 5.0 will hopefully be out soon.
Bob
I've also run it across a network with the data drive mapped to from
another machine with no problems.
Greg
: For some years I've used TMG. With release 4.0 (and subsequent updates)
: I have a truly strange problem. When first installed it works OK; but then
: it very shortly starts giving me the "Black Screen of Death aka BSD
: " -- I hit the icon to start and the screen goes black and the system locks
: up totally -- sometimes. Shortly after that I get the BSD every time.
[snip]
: TMG says it's a memory allocation problem related to FoxPro. Even if I
: delete everything running on the system except the Win98 kernel, I still get
: the BSD.
This comes up every so often on the TMG-L maillist. Evidently it's
a *resource* issue which may (or may not) be related to the 16-bit
Foxpro engine used by TMG.
The best answer seems to be to load TMG first, and run Resource
Meter to monitor how much is available. At least, most of the
people with that problem have reported success doing so.
TMG v5 will use the 32-bit Foxpro, which hopefully will solve the
problem.
--
Paul Havemann (pa...@havemann.com)
Havemann Family History: http://www.havemann.com/
Researching BAUER, BERESFORD, BOEME (Ger. > USA), BROWN (No. NJ),
CONKLIN (No. NJ), FRAME, HARTUNG, HAVEMANN, HEAD (Eng. > USA),
HEWITT, KIEP (Ger. > USA), MUSTERER, WETZEL (Ger. > USA),
WINGENDORFF (Ger. > USA)
Have info related to BEHRENS (PA), HEIMOWITZ (NYC 1920s),
NOVOTNY (NYC 1920s)
>Stephen Hayes wrote:
>
>> <snip>
>> I have a 450Mhz AMD processor, 64 megs of RAM, and just over 1 gig free disk
>> space.
>
>That's plenty of free space and not the issue.
>
>> <snip> JC> TMG says it's a memory allocation problem related to FoxPro.
>> JC> Even if I delete everything running on the system except the Win98
>> JC> kernel, I still get the BSD.
>>
>> I've had the same experience, and I've given up on TMG.
>>
>> I've found it very unstable, and I've got tired of ininstalling it and
>> reinstalling it every time I try to enter or edit data.
>
>Uninstalling & reinstalling is senseless wasted effort and not a fix in any way.
Exactly, that's why I've given up trying to use TMG.
>
>> JC> I've switched over to using Legacy 3.0 Pro which has 95% of the
>> JC> same features, but I would still like to know what causes this
>> JC> nasty problem.
>>
>> If you find out, please let me know. The TMG support people are unable to help.
>
>That statement is FALSE. TMG support has offered a workaround which is to load TMG
>right after booting. It may be a pain to have to do that, but it supposedly always
>works. You can lead a horse to water, but . . .
It doesn't work for me.
Steve Hayes
http://www.suite101.com/myhome.cfm/methodius
For spammers:
tos...@aol.com ab...@aol.com ab...@yahoo.com u...@ftc.gov
ab...@hotmail.com ab...@msn.com ab...@mindspring.net
abuse-n...@uu.net ab...@dialsprint.net ab...@earthlink.com
postm...@attglobal.net ab...@bellsouth.net ab...@sympatico.ca
Trust me: it doesn't work on my system. Clean boot=black screen of
death; clean boot and delete all running modules except Win98 kernel =
black screen of death. Etc.
>
> > Perhaps they need to rewrite the program in something other than FoxPro.
Amen, halauah, brother preach on!
> "Robert Heiling" <rh...@qwest.net> wrote in message
> news:3B965EA0...@qwest.net...
> > Stephen Hayes wrote:
> >
> >> <snip>
> >>> If you find out, please let me know. The TMG support people are unable
> >>> to help.
> >
> > That statement is FALSE. TMG support has offered a workaround which is to
> > load TMG
> > right after booting. It may be a pain to have to do that, but it
> > supposedly always
> > works. You can lead a horse to water, but . . .
>
> Trust me: it doesn't work on my system. Clean boot=black screen of
> death; clean boot and delete all running modules except Win98 kernel =
> black screen of death. Etc.
Then you have more problems with your system than that particular workaround was
meant to deal with. In any case, it's not my problem so I don't have to worry
about it.
> > > Perhaps they need to rewrite the program in something other than FoxPro.
>
> Amen, halauah, brother preach on!
Word is that TMG 5.0 will use the 32-bit version. I see no problem with that and
am waiting to upgrade to see if what I consider to be the current problems have
been addressed.
Bob
Robert Heiling wrote in a message to All:
> > That statement is FALSE. TMG support has offered a workaround
> > which is to
> > load TMG
> > right after booting. It may be a pain to have to do that, but it
> > supposedly always
> > works. You can lead a horse to water, but . . .
>
> Trust me: it doesn't work on my system. Clean boot=black screen of
> death; clean boot and delete all running modules except Win98 kernel =
> black screen of death. Etc.
RH> Then you have more problems with your system than that particular
RH> workaround was meant to deal with. In any case, it's not my problem
RH> so I don't have to worry about it.
Then why not just shut up, since you have nothing useful to offer?
> > > Perhaps they need to rewrite the program in something other than
> > > FoxPro.
>
> Amen, halauah, brother preach on!
RH> Word is that TMG 5.0 will use the 32-bit version. I see no problem
RH> with that and am waiting to upgrade to see if what I consider to be
RH> the current problems have been addressed.
I hope they are going to offer it as a free bug fix to those who paid money for
the program that doesn't work.
I certainly would want to be sure that it works before shelling out money for
it.
Bob