TMG-L Archives

Archiver > TMG > 2007-06 > 1182947592


From: "Teresa Elliott" <>
Subject: Re: [TMG] 16 bit Bandit/friend in need....
Date: Wed, 27 Jun 2007 07:33:12 -0500
References: <!&!AAAAAAAAAAAYAAAAAAAAAGvoveoabjVGnLsrW3gDeALCgAAAEAAAANK4bX/a/PRDmU+slGzl85UBAAAAAA==@cox.net> <JJEIIPLALFIIBFPLABBJKEBPFJAA.chris@masquerade.demon.co.uk><!&!AAAAAAAAAAAYAAAAAAAAAGvoveoabjVGnLsrW3gDeALCgAAAEAAAAJFMH4oGLttEtlGM+dQc3/oBAAAAAA==@cox.net>
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAGvoveoabjVGnLsrW3gDeALCgAAAEAAAAJFMH4oGLttEtlGM+dQc3/oBAAAAAA==@cox.net>


Gene, You would need to talk to Bob about that.


Teresa Ghee Elliott
--http://freepages.genealogy.rootsweb.com/~rutherfordcemetery/
-----Original Message-----
From: [mailto:] On Behalf
Of GeneJunky
Sent: Monday, June 25, 2007 8:43 AM
To:
Subject: Re: [TMG] 16 bit Bandit/friend in need....

It is my understanding....that the MSWord driver in TMG7 will be new. Is
anyone able to _confirm_ same?

-----Original Message-----
From: [mailto:] On Behalf
Of Chris
Sent: Monday, June 25, 2007 12:04 AM
To:
Subject: Re: [TMG] 16 bit Bandit/friend in need....


> the TMG programmers don't believe that their MSWord 2000
> driver is the culprit. In the alternative, wouldn't it
> make sense that if the driver was causing the
> problem, an updated driver would resolve the conflict.

It depends <grin>. If the TMG Word driver was causing the problem, then
many more of us would experience the issue. I suspect that this is the
anomaly being faced by the support engineers trying to find out what is
wrong. If dozens, possibly thousands, of people were seeing this "bandit"
then it could clearly show that their driver was the cause. However, there
has been just one person - and now there are two. This could mean (stress
could) that you are both running 16-bit code (possibly different code) that
conflicts with this driver. I suggest that saying which piece of code is at
fault is pointless - you just need a solution. This solution could be to
identify this other piece of 16-bit code and stop using it. However, it may
be something you'd rather not loose - for example it could be the driver for
your Apple screen (just a guess - I certainly don't have the knowledge of
graphics drivers to say).

Personally, I would not expect TMG to replace their code at this stage in
the development cycle. However, I would expect them to seriously consider
doing so for the next major release (e.g. V7) since it will not be long
before 16-bit code won't work on a Microsoft platform (I don't think it
works on 64-bit platforms, for example). Whether or not this cures your
problem is impossible to say since we don't know the root cause of the
problem. If the rot cause was TMG - then I suggest many, many, more of us
would experience it.

Many of us will not be able to move to 64-bit because we have some programs
or hardware that just will not work - some of which we do not realise are
16-bit.

By the way - I'm still looking at your process list to see if I can identify
16-bit code. However it could be embedded and so invisible at this level of
detail.

regards

Chris

-------------------------------
For searching the list archives and other list information, please go to
http://lists.rootsweb.com/index/other/Software/TMG.html.
To contact the TMG List Administrator, send a message to
.
-------------------------------
To unsubscribe from the list, please send an email to
with the word 'unsubscribe' without the quotes in
the subject and the body of the message

-------------------------------
For searching the list archives and other list information, please go to
http://lists.rootsweb.com/index/other/Software/TMG.html.
To contact the TMG List Administrator, send a message to
.
-------------------------------
To unsubscribe from the list, please send an email to
with the word 'unsubscribe' without the quotes in
the subject and the body of the message


This thread: