[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

2138.0. "Problem Viewing from TeamLinks 2.7-1 VW error" by ALFSS2::GIANNETTI_D () Fri Apr 18 1997 20:41

Customer has Windows 95 without plus pak and has TeamLinks 2.7 	            
with ECO1. Has Word 6.0 attachment to a message.  They have set the             
path to launch winword.exe piece works, however, they are unable             
to view a Winword 6.0 document. Local PC installation of TeamLinks
and as you can see throughout this document it appears they can't
view any format type.                                             
                                                                                
They receive VW_Error: - 209                                                   
Unsupported input file format                                                  
                                                                                
OK                                                                             
                                                                                
Customer does not have the Local Demonstration Drawer installed or any
local drawers for that matter so I could not try our sample document.

Checked for the viewer files both the w4w49T.dll and w4w49F.dll                
were present and were the same size as was on Beth's PC which                  
is running 2.7-1.                                                              
                                                                                
I walked customer through doing a file/new and trying to view                  
it - no luck.  Received the following error                                    
                                                                                
Title Bar - had title of document                                              
                                                                                
Error.  Unable to view document.  Document contains invalid                    
data.                                                                          
                                                                                
Suggested reinstalling converters and viewers                                  
                                                                                
Reinstallation of converters/viewers did not help

I asked customer to try to view an Excel file.
                                                                                
Customer was not able to view from Excel.                                      
                                                                                
I suggested trying another video driver - but he was unsure of                 
what to use on his COMPAQ system.                                              
                                                                                
I had him go to TeamLinks Setup/File Formats and select the                    
WinWord viewer and select View with Text viewer - select - a new               
error.                                                                         
                                                                                
The error he received...                                                       
                                                                                
A disk error was encountered while reading this file it may not                
be completely displayed                                                        
                                                                                
OK                                                                              
                                                                                
The customer has the kit on CD.  He is a Canadian site and they do not
work directly with DEC but rather, acquired their kit from G.E. who is their 
contractors that installed TeamLinks, etc.  I told him I would put note out
to engineering and in the meantime, remove TeamLinks (according to packing.lst)
and reinstall.  They have local PC installation.

Does anyone have a clue on this one?

Debbie Giannetti
T.RTitleUserPersonal
Name
DateLines
2138.1TAMARA::CUMMINGSJerry Cummings, TeamLinksMon Apr 21 1997 08:425
Beats me; maybe someone else has some ideas. I forwarded
your note to Carson, but he's out for a bit. All users
see this?

Jerry
2138.2A few more suggestionsCHEFS::annep.uvo.dec.com::tayloraMon Apr 21 1997 14:5923
Debbie,

FWIW I have no idea either. You sound like you've tried all right things, but these are 
my suggestions for extras to try.  

- Get them to run ScanDisk, just in case there IS a problem on their disk.
- Delete all temporary files in the staging directory
- Check that office.ini has correct directory info for the staging directory.
- See if there is anything "odd" about their hard disk - eg removable, or if
  it needs any weird drivers.
- try creating a local file cabinet on a floppy disk and see if they can read the 
document from there.
- Presumably they CAN read "normal" documents in Word/Excel, ie if they save the 
attachment to a directory not the file cabinet can they then view it?
- try looking at the settings in the Control Panel|system|Performance tab|File System 
button|Troubleshooting tab.  I can't remember what they all do, but it may be worth 
disabling everything and see if that helps!

Regards,

Anne
Basingstoke, UK

2138.3Check tlcvtvu.inibachlr.zko.dec.com::tamara::hoveyTue Apr 22 1997 19:2811
Check tlcvtvu.ini; see if numconverters is set to zero. If it is; there
was some sort of problem during install (or a munged .ini file before
the installation and install got confused during the update).

If tlcvtvu.ini being set to zero is the problem; the best thing to do is
delete this .ini file and reinstall. 

This happens from time to time and I have not as yet been able to 
determine if it's because the user changed some things in there and didn't
know what they were doing or if something else is going on here.

2138.4Not his numconvertersAIMTEC::GIANNETTI_DWed Apr 23 1997 15:409
    Carson,
    
    The NumConverters=209.  I have asked for a FAX of tlcvtvu.ini,
    tlformat, office.ini.  I would have him email but he can't.
    
    Anyway, I will take a look at those files to see if anything is
    strange.
    
    Deb