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

Conference jamin::pathworks32

Title:Digital PATHWORKS 32
Moderator:SPELNK::curless
Created:Fri Nov 01 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:337
Total number of notes:1612

104.0. "PowerTerm File|Print Setup... hangs for me" by VMSNET::S_VORE (Smile - Mickey's Watching!) Wed Jan 29 1997 14:26

    Does PowerTerm's File|Print Setup... menu choice do anything for anyone
    (other than sometimes hang the application for about 10 seconds)?
    
    -Steven
    
T.RTitleUserPersonal
Name
DateLines
104.1More details, and a QAR, pleaseJOBIM::VUJNOVICI�t�r��t���l�z�t��L���l�z�t��Wed Jan 29 1997 17:4511
Give us more details, PowerTerm version, OS, etc. I've just done it
on NT/Intel and I got the Windows Printer Setup dialog. It's the 
same one that you get in, say, WRITE, from the File\Print... option.

Did you play with Terminal\Setup\Printer? Does print screen work?

Please QAR this; there were at least 2 QARs regarding printing that
were successfully closed.

Regards,
Slobodan
104.2PTW*.CFG files?SUTRA::MOXLEYShiny Shoes, Shiny MindThu Jan 30 1997 04:4811
    
    Re: Printing QARS.
    Yes, as someone who raised one of these I can make some pertinent
    comments.
    I used 95, and had similar symptoms - it couldn't find the default
    printer, and failed to bring up the printer dialog box. That was until
    we discovered some PTW*.CFG files lurking in C:\WINDOWS, or, on NT in
    C:\WINNT. Once these were deleted - magically the printer poperties
    page appeared.
    
    Simon
104.3QAR 1473 EnteredVMSNET::S_VORESmile - Mickey's Watching!Thu Jan 30 1997 08:5838
PowerTerm 4.00.32
Windows NT 4.0
connected via telnet

File|Print Setup menu choice does one of two things for me,
neither very useful:

- hangs PowerTerm for aproximately 10 seconds and then does nothing
- does nothing

By "does nothing" I mean that no dialog box is displayed, that I am
returned immediately to the terminal window.  No pointer change, no
sounds, nothing.


Under Terminal Setup's Printer tab I have tried with both File (the
default) and Print Manager selected, no change.  Currnet settings
are:

  Print Device			x Use Form Feed
   Print Manager                  Print Line Graphics as Text

  Device
    (section disabled)     Print Screen Data Conversion:  Graphics
                           Slave Printer Data Conversion: None
                           Slave Printer Job Delimiter:   None


Based on note 104.2, I looked in D:\WINNT and found the following
files:
	ptw.cfg
	ptw_prt1.cfg
	ptw_prt2.cfg

Removing these files did indeed allow the Print Setup dialog box
to appear.


104.4Not universalTLE::LUCECharlie Luce, Digital Unix QCSThu Jan 30 1997 11:276
    The odd thing is that I have the same setup as 104.3, and those same
    three files are in my C:\WINNT35 directory, but I don't have the
    problem -- selecting File|Print Setup pops up the Print Setup screen,
    just like it's supposed to.
    
    It doesn't make any difference if the printer is local or network, BTW.
104.5HmmmSUTRA::MOXLEYShiny Shoes, Shiny MindThu Jan 30 1997 11:349
    >>  C:\WINNT35 directory,
    
    This *was* a typo, right?
    I had this problem too, hence my suggestion to remove the files. I had
    the problem on 95, and not on NT. But I suspect it may be due to having
    upgraded/re-installed the software, and having changed printer
    assignments along the way, perhaps?
    
    Simon
104.6Your PTW_PRT*.CFG were left-overs, I thinkJOBIM::VUJNOVICI�t�r��t���l�z�t��L���l�z�t��Thu Jan 30 1997 11:524
A lot depends on the FT stuff you have lying around on your system. 
Ericom belive that first-time users will not have the problem.
Regards,
Slobodan
104.7Old name, new OSTLE::LUCECharlie Luce, Digital Unix QCSThu Jan 30 1997 16:457
        >>  C:\WINNT35 directory,
        >This *was* a typo, right?
    
    No, just a system that was upgraded from 3.51 to 4.0, and the default
    system root directory for NT 3.5 and 3.51 was WINNT35. I thought about
    changing the name, but it's not like it's hurting anything...