Conference abbott::teamlinks_windows

Field test 1 drafts of the TeamLinks for Windows Getting Started guide 
and TeamLinks for Windows Client Administration Guide for V3.0 are now 
available for your reading pleasure!    

The Getting Started is available in PostScript format in this directory:

	BOOKIE::WORK1:[TLWIN_DOC.V3_FT]

Each chapter is in a separate PostScript file (sorry, but Word kept
crashing on me when I tried to create one .PS file containing all the
chapters!).

A ZIP file containing the Admin. Guide in WinHelp format (the only format
in which it will be available from now on) also is in the above directory.

Word 7 (Word 95) source files for the Getting Started are available in a
folder called TLWIN GETTING STARTED GUIDE in this shared ALL-IN-1 drawer:

     XANADU::"[TEAMLINKS]KITS AND DOCS"

The ZIP file with the Admin. Guide help file is in a folder called
TLWIN CLIENT ADMIN GUIDE in that same drawer.

Enjoy!

-- Nina

Guys,

	Please can you set up WEB access to the kits and Docs as it is very
akward getting to a DECnet address when you only have TCP/IP running on your PC
(like i have). There is already a WEB server running on xanadu, all you need to
do is setup a home page for yourselves and point in pointers to the kits and
docs.

On the same subject, PostScript isnt nice to handle on the PC and can we have
the WORD sources made available or at least PDF versions.

Thanks
	Gerald

re: web access

I'll mention this to the WWW powers. If we can't do it on
xanadu, maybe we can do it elsewhere.

re: DECNET

Use xanadu.zko.dec.com. Either FTP or add it to your LMHOSTS
and use Windows to connect. I don't think you could use your
web browser and ftp:// though. Either Purveyor or UCX would
prevent changing to another directory.

Jerry

>On the same subject, PostScript isnt nice to handle on the PC and can we have
>the WORD sources made available or at least PDF versions.

Hello, the Word sources ARE available: in a shared ALL-IN-1 drawer, as
mentioned in .5 (you ARE using TeamLinks, right? :-) ).  Sources only for 
the Getting Started guide are there; the Admin. Guide already is available 
in a PC-friendly format (help file).

We may provide .PDF of the Getting Started in the not-too-distant future.
I'll update this topic if/when that happens.

- Nina

P.S. BOOKIE is accessible via TCP/IP (bookie.zko.dec.com).

re last 2

Thanks,

Gerald

I just found out that released documentation and courses (in PostScript
format only, as far as I can tell) are available on the Web from the 
MCS Learning Utility (I guess it is pulled from GEL).  

See the information below on how to access it.
-- Nina
-----------------------------------------------------------------------------

The MCS Learning Utility uses World Wide Web technology to provide access 
to Digital training and documentation whenever and wherever you need it.  

The Learning Utility database is distributed across strategically located 
servers.  Each server contains the same information as the Corporate server. 
The "local" servers may also contain information of interest to that 
particular region.  Please use the server designated for your geographic area 
to minimize network congestion.  The other servers are accessible if your 
designated server becomes unavailable.  

The URL for the Learning Utility home page is:

        http://www-mcslu.***.dec.com/mcsl/mcslhome.html 

where the *** should be replaced by the site of the server located nearest 
to you.

THE FOLLOWING SITES ARE THE SERVER LOCATIONS:

Americas:
--------
      DAS - Andover, Massachusetts (Corporate Server)

      ALF - Alpharetta, Georgia (Master Americas Server)

      CXO - Colorado Springs, Colorado

Asia-Pacific:   
------------
      HGO - Tsuen Wan, Hong Kong (Master AP Server)

      SNO - Sydney, Australia
              
      TBJ - Tokyo, Japan

Europe:
------      
      RTO - Munich, Germany

      SOO - Stockholm, Sweden
             
      EVT - Evry, France

      REO - Reading, England (Master European Server)

      GEO - Geneva, Switzerland

      UTO - Utrecht, Netherlands

Please remember to use lower case letters for url addresses.

If you experience problems using the Learning Utility, there is a User Guide 
that you can access right from the LU Home Page.

    Is there something "funny" about the V2.7 Client Administrator and 
    Getting Started postscript files? I've tried printing them on an 
    LPS20, an LPS32, and a DECLaser 2250, and on all three printers, 
    for both documents, the printers encounter problems when they get
    to the first bit of graphics (page 1-1 in the GS doc, and page 2-4
    in the ADMIN doc), failing in a variety of ways.
    
    HELP!

    I have a site that is trying to order the TeamLinks for Windows
    Client Administration Guide but is being told by DEC Direct
    that there is not such thing.
    
    The Part Number he is giving them is AA-R06VA-TK, from the Title
    page of the Client Admin Guide.
    
    Could someone please tell me so I can tell him how to order this
    manual?
    
    He is using TeamLinks 2.7.
    
    Thanks,
    
    Beth Andres
    

    I've been having the same problems, but haven't had time to try to see
    waht the cause is.  I was trying to print 2-UP, Double-sided, which
    works for about half of the document, then starts printing 1-UP for
    large chunks of the document.
    
    - Dave

    re: .12 - Interesting; My attempts at using NUM=2 failed immediately 
    with an error about 'mysetup' not being defined. I gave up on that 
    and was trying to do just a plain print with no options of any kind,
    and those attempts failed when they hit the graphics. 
    
    Dave

this problem is quite often caused by the postscript engines in the printers
being different, depending on their age.

I used to have problems with some postscript on an LPS17 that would print fine
on an LPS20 (or was it the other way round :-) ) similar symptoms as you are
seeing especially with diagrams.

Just try another type of printer.

Gerald

RE .11 - .13 - I don't know what to tell you, except maybe try upgrading
your print server software?  I can print out both those files (assuming you
are talking about the .PS files mentioned in .3) on an LPS32 and an LPS20
without any problem.  (I do get a bunch of %DCPS-I-USERDATA informational
messages in my DECterm window while they're printing, but the files print
fine.)

Or you could try opening the Word files from the shared KITS AND DOCS drawer
(see .3) and printing directly from Word.  Of course, that requires printing
each chapter individually...

-- Nina

RE .15 - I don't know much about the ordering process for doc'n (I never have
to order my own :-) ).  Phil Gabree is probably the one who will know, and
I forwarded your question to him.  However, he's away until next week...

-- Nina

    re: .14 - I've tried all three printers available to me.
    
    re: .16 - I've been looking at the postscript in the files, and doing
    some research in the POSTSCRIPT_PRINTING conference; question to the
    doc team - Are you folk embedding _color_ images in these documents? 
    
    Dave

    I'm running the latest version of the DECprint Supervisor software
    (V1.3) and my printer is an LPS20.  I haven't had this problem on other
    documents.
    
    - Dave

The only way to order the Client Admin Guide is to order the TLs documentation kit.
	QB-0N1AA-GZ	$11 list price

Phil

>    re: .16 - I've been looking at the postscript in the files, and doing
>    some research in the POSTSCRIPT_PRINTING conference; question to the
>    doc team - Are you folk embedding _color_ images in these documents? 

I can only speak definitively for the Getting Started as I didn't do the 
Admin. Guide hard copy.  All screen shots and icons I put in the Getting 
Started I captured as 256-color graphics and converted to 16-color grey scale.
I suppose that may still count as "color," technically... (?) 

The V2.7 Admin. Guide may have some non-grey-scale color graphics in it.

If anyone has other suggestions for dealing with graphics and PostScript
output in Word, we're open (but won't be changing the existing V2.7 docs).
All I can say is that the current methods/drivers work for us and for 
production...

- Nina

    I did some experimenting using the first few chapters of the Getting
    Started file, and by hacking the postscript was able to get the job 
    to complete successfully on my DECLaser 2250, including the use of 
    NUMBER_UP. (N.B. I haven't seen the output yet, as I'm working home.)
    
    See note 6657 in HUMANE::POSTSCRIPT_PRINTING for details.
    
    Dave

RE .21 - Glad you got something working, though it's too bad you had to
go to the trouble of hacking the PostScript code.

Per a comment you made in your notes in the POSTSCRIPT_PRINTING conference,
the files are, in fact, actually contatenated .PS files, created using the
"Find File" feature in Word 6 (which was the only way to get a single .PS file
for an entire book whose chapters were in separate source files without using
the less-than-robust Master Document feature in Word).  Basically, you use
the Find File command to select all the .DOC files and choose Print to File, 
and Word shoves them all in a single .PS file.  I was less than successful 
with this method in Word 7 (where it uses the Open dialog instead of a Find
File one) for the V3 EFT1 Getting Started, as I noted in .5.

The V2.7 .PS files in BOOKIE::TLWIN_DOCS: were created using the LPS20 printer
driver that comes with Windows 95.

This is probably more than anyone wants to know... :-)

We certainly are looking at other ways (e.g., PDF, HTML) of making the 
doc'n available internally (and maybe externally as well), though I can make
no guarantees about when that might happen.

- Nina

    I don't know squat about the MS PS drivers, but from reading notes in the
    other conference there are strong recommendations regarding the options
    you should select. (things like 'Optimze: Portability' etc). I wonder
    if this (or the fact that this is a concatenated PS file) relate to the 
    NUMBER_UP problems I and others have encountered with these files...
    
    Dave

>    I don't know squat about the MS PS drivers, but from reading notes in the
>    other conference there are strong recommendations regarding the options
>    you should select. (things like 'Optimze: Portability' etc). I wonder
>    if this (or the fact that this is a concatenated PS file) relate to the 
>    NUMBER_UP problems I and others have encountered with these files...

Anything is possible.  We do have specific options we need to set up when
we use the DEClaser drivers (which produce PostScript that will run through
our production system).  I admit I haven't done anything special that I can
recall (except to turn on duplex printing) with regard to options for the 
LPS20 driver (which is what I used to create the V2.7 single/contatenated 
.PS file of the Getting Started guide).

One could, of course, order a nicely printed and bound V2.7 doc set from the
SSB. :-) (See doc kit order number in .19.)

- Nina

    FWIW,  I notice that I was able to print the V2.5 User Guide on the
    same LPS20 using 2-UP and double-sided.  I would imagine the problem is
    due to production methods used in producing the docs rather than any
    problem in the printer.
    
    - Dave

>    FWIW,  I notice that I was able to print the V2.5 User Guide on the
>    same LPS20 using 2-UP and double-sided.  I would imagine the problem is
>    due to production methods used in producing the docs rather than any
>    problem in the printer.

(Hi, Dave!) Well, yes -- the V2.5 User's Guide was produced with VAX DOCUMENT!
 :-)

- Nina

    RE: V2.5 docs
    
    Producing the docs with VAX DOCUMENT would certainly create PostScript
    formats compatible with an LPS20.  
    
    Any chance we could go back to that? %^P
    
    - Dave

RE .27 - Bite your tongue!! :-)

- Nina

    I finally made it into the office, and the 'colorgronk' hack, while
    allowing the files to print, results in fairly poor image rendition.
    (Wish I knew more about PS so I could come up with a better 'fix'.)
    
    I can see no ill effects from removing the %%BeginFeature %%EndFeature
    sequences from the files, and I was able to get (num=2,side=2) output.
    
    The fact they are concatennated PS files makes printing exceedingly slow, 
    since each chapter goes through the same loading/initialization steps.
    
    Dave

    I guess I spoke to soon; the ADMIN doc died on page 6-1 with:
    "
    This job requires more memory than is available in this printer.
    Try one or more of the following, and then print again:
    	In the Postscript dialog box, click Optimize For Portability.
    	In the Device Options dialog box, make sure Available Printer
    		Memory is accurate.
    	Reduce the number of fonts in the document.
    	Print the document in parts.
    "
    Editting the file to remove the first 5 chapters allows it to print 
    chapter 6. Apparently the per-chapter reloading/initialization takes 
    a memory toll. I wonder how many more chapters I'll get this time...
    
    Grrr....

Now available, for your viewing/searching/printing pleasure:  The V2.7
Getting Started and Client Admin. Guide in - yes - Adobe PDF format!

The files are in BOOKIE::TLWIN_DOCS:V27_GS.PDF and V27_ADMN.PDF (I kept
the names to 8 characters for those who still might be running Win 3.x).
(BOOKIE::TLWIN_DOCS: translates to BOOKIE::WORK1:[TLWIN_DOCS], fyi.)

They also are in the ALL-IN-1 shared KITS AND DOCS drawer in their respective
folders (see .3 for the drawer specification).

The .PDF files are not fancy - no hot links or anything; just a straight
conversion from PostScript.

I have successfully printed out (several pages of) the Admin. Guide .PDF
file on an LPS20. :-)

Enjoy!

-- Nina