Free 14-Day Evaluations    
Product Downloads    

Sign in     


DESKTOP MOBILE DOWNLOAD PURCHASE SUPPORT INFO COMPANY
 Home  >>  Support  >>  Knowledge Base
GetObject() Doesn’t Make TinyTERM Visible
May 2nd, 2007

Century Software, Inc., received comments from a customer writing a Visual Basic (VB) script to open TinyTERM with a specified .tpx file. Using the VB GetObject() command opens TinyTERM but makes it invisible. It’s listed in Task Manager, but there’s no icon or window for it, nor is there any way to bring it up. The basic script was

dim x
set x = getobject(“c:\default.tpx”)
‘x.visible = true
msgbox “test”

Note the line commented out. TinyTERM does not have a “visible” property to use in this situation.

The VB script that resolved the issue is:

dim retcode
dim alreadyrunning
set Wshshell= WScript.createobject(“wscript.shell”)
‘try to activate the tiny term window using the application title
Alreadyrunning = wshshell.appactivate(“C:\default.tpx”)
if not alreadyrunning then
‘launch Tiny Term
retcode = Wshshell.run (“%comspec% /C c:\default.tpx” , 1, FALSE)
Else
‘ send keystrokes to maximize the window
WshShell.SendKeys “% ”
WshShell.SendKeys “r”
end if

CR 735

Page Setup in LPD
May 2nd, 2007

The Century LPD server does not use a Page Setup dialog. It relies on the Windows default settings for the printer, unless the Bypass Windows printer driver option is set.

Century Software, Inc., has had a request to add a page setup option for those times when Bypass Windows printer driver is not set. We have also had a request to include an option to add line feeds at the beginning of the print job, as part of a page setup window.

CR 734, page setup
CR 751, line feeds

VT420 Doesn’t Set Scrolling Margins Correctly
May 2nd, 2007

The basic sequence to set scrolling margins in most VT emulations in TinyTERM — VT220, VT320 and VT420 — is:

CSI Pt ; Pb r

which you can find documented here. If that sequence is sent as part of a large block of screen information, the VT420 emulation can miss it. This leads to incorrect scrolling and bad display.

CR 733

Monitor Sleeps Immediately After Booting
May 2nd, 2007

Boot PIXIL Thin Client 1.18 from a USB memory device. After the PIXIL wallpaper comes up, the screen goes black, and the monitor goes to sleep. Moving the mouse brings it back to life.

CR 732, fixed in PIXIL Thin Client 1.19

Indirect Mode for Port Forwarding
May 2nd, 2007

Currently port forwarding in TinyTERM Plus does local-to-remote and remote-to-local forwarding. Century Software, Inc., has had a request  to use TinyTERM Plus as a sort of “go-between” from the SSH server to another system, encrypting on the way. This would requires a third, indirect port forwarding option be added to TinyTERM Plus.

CR 729

AT CHECKBOX Translated Incorrectly
May 2nd, 2007

Create a valid check box in TERM Script Language. Then run the script through tsltrans.exe. The resulting CScript file gives the error, “expected number, got string.” It’s due to incorrect translation. For example, this command:

at 104,10 id 4 tabstop get SENDCLMS checkbox “Send Claims”, 30,8

run through tsltrans.exe gives this line:

tsl_atobjdone(4,11,10,104,30,”Send Claims”,(8)|16384,””,””,0,0,-1,”sendclms”, “”);

It should give this line instead:

tsl_atobjdone(4,11,10,104,30,20,(8)|16384,”Send Claims”,””,0,0,-1,”sendclms”, “”);

Note the addition of the value 20 just after 30, and the relocation of the “Send Claims” argument after the value 16384.

CR 728

Directory “C:” Caused an Error: “Bad Pathname Specification”
May 2nd, 2007

Using SecureFT to transfer files via FTP from the PC to an IBM 4690 server generates the error above. Below is sample text from the output log window of SecureFT:

USER pos_dev
331 Password required for pos_dev.
PASS *****
230 User pos_dev logged in.
PWD
257 “c:” is current directory.
TYPE I
200 Type set to I.
SYST
215 OS 4690 operating system Passive mode on.
TYPE I
200 Type set to I.
c:\
Directory “c:” caused an error with message: “Bad pathname specification (e.g., syntax error).”.
CWD c:\c:
550 c:\c:: error 0.

In contrast, here is the output from a command-line FTP client:

220 FTP server (IBM 4690 TCP/IP FTP Version 1.0) ready.
User pos_dev
331 Password required for pos_dev.
Password:
230 User pos_dev logged in.
cd adx_upgm
250 CWD command successful.
pwd
257 “c:\adx_upgm” is current directory.
cd ..
250 CWD command successful.
bi
200 Type set to I.
get ace.dat
200 PORT command successful.
150 Opening BINARY mode data connection for ace.dat (55 bytes).
226 Transfer complete.
ftp: 55 bytes received in 0.00Seconds 55000.00Kbytes/sec.
quit
221 Goodbye.

CR 727

Can’t Upload to Latest ZMODEM
May 2nd, 2007

Download and compile the latest version of the ZMODEM software. You can use sz to send files to TinyTERM readily.

However, uploading to rz fails. It constantly resyncs, rather than completing the transfer.

CR 726

XMODEM Ignores Local Destination Directory
May 2nd, 2007

Set up an XMODEM file download to the PC. Configure a Local destination directory in TinyTERM’s Get File or File Transfer Properties dialog. The file will download into the TinyTERM directory regardless of how that’s set.

CR 723

Less Restrictive Folder Permissions
May 2nd, 2007

After TinyTERM Plus is installed, users with no administrator privilege can only use existing .tpx connection profiles. They can’t create new .tpx files or update the existing ones. This is because .tpx files are saved in C:\Program Files\Century\TinyTERM, and after installation, non-administrator users have read-only permission for that folder.

Century Software, Inc., has received a request to change that folder’s default permission to “Modify” for normal users during installation. After installation, this would allow all users to create their own connection profiles in that directory.

By design, TinyTERM Thin Client or TinyTERM Plus in a terminal server environment creates a TTweb folder for each user, in that individual user’s profile. Users should save custom configuration files to that folder, rather than to the TinyTERM install folder.

CR 722



  Copyright © 2025 Century Software, Inc. All Rights Reserved999 TERMS OF USE PRIVACY POLICY EULA