Conference abbott::teamlinks_windows

Check out 1996.*. I would guess that you need to pick
a different default printer to keep the 3rd party control
that we use happy.

Jerry

    re: .1
    
    Jerry,
    
    I use several printer setups depending on what I'm trying to
    accomplish.  I would like to understand why one printer driver vs.
    another would create this problem.
    
    Can you provide more detail or a pointer to that detail?
    
    THANKS!!
    
    Rick

We're not completely sure why the editor component (Visual Writer)
that we use for both TEXT and RTF has a problem with some drivers,
but it does.

Often the problems seem to be related to fonts though. Did changing
the default printer fix things for you?

PTR this one if you like, specifying what printer driver and
where it can be found. I think it's not 11 that describes how
to report problems.

Jerry

    
    I experience the same kind of problem. 
    
    TeamLinks seems to stop just after having logges SetTBar for the
    CreateMesage window in the logfile.
    
    I have tried to reinstall the V2.7, and it runs with the same pronter
    settings. I tried to set Text only printer as default. but with no luck
    so far.
    
    Any hints? I seriously doubt that it is caused by the TX control and
    printer settings.
    
    rgds
    
    Preben J

I'll see if we can have someone look into
this, but could you please report on what
happens if you set it to a PostScript or
LaserJet printer?

Jerry

    Tried the following printer types
    
    DEC Printerserver 17 Postscript
    LaserWriter
    Generic Text
    File to disk
    
    all of which fails the same place
    
    rgds

    re: .3
    
    Jerry,
    
    Sorry to be so late getting back - end of quarter revenue bookings!!
    
    The driver I use most often is the DEClaser 5100 to LPT1:.  I do use a
    software app which allows multipage printing - Clickbook.  Clickbook
    installs a driver for the same printer called "CB DEClaser 5100 on
    LPT1:" which I've used for several years now - save those trees &
    Office clutter!
    
    I never saw the error message I reported in .0 prior to the install of
    V3 EFT1.  I've installed everything from SSB V2.1 through all test
    versions and SSB versions up to the present (which explains why he
    really doesn't want to post his OFFICE.INI file - it's a mess!!).  No,
    no clean system upgrades or application installs on this machine in
    over 18 months.
    
    Any thoughts or any information you'd like to have?
    
    THANKS!!
    
    Rick
    
    PS:  Yes, I do still get the message (TWICE) when I do Create Message
    and it doesn't seem to matter which printer driver I have selected as
    the default.

I'll ask the person most recently involved with
the Create Message window to take a look at this
note string.

Jerry

Could you please supply your version of office.ini --
My guess is that some of the RTF settings did not get properly updated
with the installation of V3.0.

One other thing to try -
Create a NEW Create Message style and set this style as your current
style.  Open and close Create Message and see if the problem goes away.
If it does, then there is a setting that is bad in you ini file for 
the style you are using in Create Message.  

I would like to use your settings to see if I get the same error --
I would also like to know what did not get updated with the install of
V3.0 that might be causing your problem.  

I installed the DEC 17 postscript, and I do not get this error.  
The error is occuring when it tries to set the width of the editor view
based on the selected fontname and fontsize.  If the display is too small
for the settings -- you can get this error.

Let me know where I can copy your ini file, or send it in this message :
what I am most interested in are the [CMStyle~x] settings. and the 
[TeamLinks Mail] settings that set the default styles.

Thanks
Karen Chiasson

    This morning I noticed that this behavior only occurs on the FIRST
    Create Message I do in the session.  At least that's the behavior I saw
    this morning.
    
    Hope this helps.
    
    THANKS!!
    
    Rick

FYI: We're still looking into this one.

Jerry

    re: .9
    
    Karen,
    
    I mailed a copy of my OFFICE.INI file to you @ZKO.  I haven't seen a
    rejection message yet, so hopefully it's made its way to you by now.
    
    Let me know if you need anything else.
    
    THANKS!!
    
    Rick
    
    PS:  OK Jerry - stop laughing at my OFFICE.INI file.  I told you before
    it was full of junk! 8^)

As an official TeamLinks Engineer, I would never laugh at
anything that came about in this notes file or any bug
report.

For instance, I would never laugh if we ever had a 
nightly build that would magically send your message
whenever you switched from Text to Rich Text. That
just wouldn't be funny. (Believe me?!??!)

Jerry

 I mysteriously reproduced this bug on my machine yesterday -- It happened
 after I installed Office 97 - Excel.  The logic that is failing is in
 the editor FONTNAME setup.  I have logic in the code that tests all the
 available fontnames to see if the editor will accept them.  If the editor
 rejects the fontname, a message is placed in your cfcdebug.log --  
 indicating which font.  IN MOST cases this is a silent error.  The editor
 for some reason is displaying this message (even with error handling set
 to trap such errors).  

 I played around with re-installing the editor, and re-setting my printer -
 and the messages mysteriously went away.  

 I am still investigating this one.  
 Have you attempted re-installing TeamLinks lately?  It's only a hunch, 
 but I think one of the TX - editor dlls or flt (filters) is getting 
 corrupted.  

 Thanks --
 ps.  I will look at your ini file -- but with what I saw, unless your
 settings for default pagewidth and pageheight were munched, I don't 
 believe the problem is going to be with settings.

 Karen 

 One more thing --

 Delete any/all of the following files from your win95\system directory ::
	
FM.DLL		Font Manager
IC.DLL		Image Control
IC.INI		Image Control INI file
TX_BMP.FLT	Bitmap import filter
TX_RTF.DLL	RTF interpreter
TX_TIFF.FLT	TIFF import filter
TX_WMF.FLT	WMF import filter
TX4VBB.VBX	VisualWriter Pro controls
TX4VBDEV.DLL	VisualWriter Pro development enabler
TXB.DLL		Support DLL
TXTOOLS.DLL	Toolbars
WNDTOOLS.DLL	Control window manager
TXVBP.HLP		VisualWriter Pro help file
TX_DLL.RTF	DLL interface documention


This will ensure that TeamLinks puts a NEW copy on your machine --
If this is a corruption problem, then you will need to have new versions
of the editor files.

Thanks,
karen

    Karen,
    
    I looked at the sections you mentioned and I didn't see anything out of
    the ordinary, but then again I am not sure what I should be seeing in
    those sections.
    
    No, I haven't attempted a reinstall.  At this point I would rather
    await guidance from a higher authority before I took that action.
    
    I have found one other anomaly that could add to the mix here.  If I
    select to "Work Offline" in Exchange I get a message that the Username
    and Password entered (and I didn't enter one!) are invalid.  If I click
    on the OK button all File Cabinet Drawers which I expect to appear do
    appear.  Could these events be related?
    
    Let me know what you'd like me to try.  A reinstall only takes about 20
    minutes and I'd be willing to attempt it if it has the possibility of
    resolving this problem.  If you'd like me to attempt a reinstall are
    there any files you'd like me to back up prior to the reinstall in case
    we need to attempt to recreate this situation?
    
    Please advise.
    
    THANKS!!
    
    Rick
    
    BTW: The machine that we're woking on here has WINWORD 6.0C and Excel
    V5, but I don't see those as factors here.  I did NOT select the
    integration kits as part of the install of V3 EFT1.  

    I have the same problem.  It appears the first time I create a message
    or forward or reply, after staring Teamlinks Infoman.  After I click ok
    a few times, life is good.  It doesn't reappear until I close and
    restart infoman.  I'm printing to a network printer - LN03 or
    printserver 20.  (no newfangled printers here.)
    
    Any fix?
    
    Don Randall
    Seattle
    

No fix yet. A *very preliminary* theory is that there is
some conflict or confusion involving FM*.DLL files that the
third party editor uses and Office 97 uses. We've seen the
problem done a reinstall of TeamLinks and seen the problem
go away. You might try that.

Jerry

    This problem is resolved with TeamLinks V3 EFT2!
    
    Good Work!!
    
    THANKS!!
    
    Rick