jwhitman@st-louis-emh2.army.mil (Jerry Whitman) (03/08/89)
Hi again. Here is the next wave of inane questions. I have been using VT100 (Ver 2.6) for a little while and I am ready to develop some custom scripts and INIT files, but first I need a little additional information. 1. If I understand the documentation correctly the BUFFER parm does nothing to the send or receive packet length. How can I change those via a parm? I have different needs depending upon which host I am accessing. 2. Because of the currently slow transfer time with the default short packet I would like to put VT100 in the background and do other things. When I click the front to back gadget I get no response. I am usually running from the CLI or Shell. Is the failure of front-to-back strictly because of where I am running? If so, will running VT100 from an icon clear that problem? If not, I would appreciate a work-around that will let me start a lengthly transfer and put it in the background. 3. The documentation does not address the file transfer requestor that is used to indicate the file and the in-flight statistics. The DONE gadget that is displayed causes me a little confusion. If I click on it the requestor goes away, but I sometimes end up sending a garbage character or two to the host. If I click outside the requstor the requestor will go away and no spurious garbage is generated. Does VT100 have some hard and fast rule here? It seems to me that VT100 has been well thought out and a very reasonable implementation. My kudos to all involved here. Also a hearty THANK YOU to those who can contribute to the demise of my ignorance in yet another subject area. (This is an amazing world - - The more I know, the more I know I don't know!) Regards, Jerry
kpmancus@phoenix.Princeton.EDU (Keith P. Mancus) (03/09/89)
As long as we're on the subject: I would like to be able
to run VT100 at 19200 or faster with a null modem cable. VT100 2.7
does not accept this in the profile, nor is there a menu for it.
Can I just change the code selecting baud rate and recompile,
or was this deliberately omitted because the machine cannot keep
up with it?
--
------------------------------------------------------------------
-Keith Mancus <kpmancus@phoenix.princeton.edu> <- preferred
<kpmancus@pucc.BITNET>acs@pccuts.pcc.amdahl.com (Tony Sumrall) (03/09/89)
In article <6900@phoenix.Princeton.EDU> kpmancus@phoenix.Princeton.EDU (Keith P. Mancus) writes: } } As long as we're on the subject: I would like to be able }to run VT100 at 19200 or faster with a null modem cable. VT100 2.7 }does not accept this in the profile, nor is there a menu for it. }Can I just change the code selecting baud rate and recompile, }or was this deliberately omitted because the machine cannot keep }up with it? It was (and still is) deliberately omitted. The reason? I don't have access to anything over 2400 baud (yet). I assumed that it would work at 9600 baud. If you want to put in the menu selection and give it a try, be my guest. Please send me e-mail detailing the outcome. If it works I'll include 19.2K support in version 2.9. }-Keith Mancus <kpmancus@phoenix.princeton.edu> <- preferred } <kpmancus@pucc.BITNET> -- Tony Sumrall acs@pccuts.pcc.amdahl.com <=> amdahl!pccuts!acs [ Opinions expressed herein are the author's and should not be construed to reflect the views of Amdahl Corp. ]
acs@pccuts.pcc.amdahl.com (Tony Sumrall) (03/10/89)
In article <10354@louie.udel.EDU> jwhitman@st-louis-emh2.army.mil (Jerry Whitman) writes: >Hi again. Here is the next wave of inane questions. I have been using >VT100 (Ver 2.6) for a little while and I am ready to develop some custom >scripts and INIT files, but first I need a little additional information. I would suggest that you move to VT100 2.8 or, preferably, 2.8A. There were some fairly hefty changes to VT100 in that time frame. Further, 2.6 was none too stable in itself. >1. If I understand the documentation correctly the BUFFER parm does nothing >to the send or receive packet length. How can I change those via a parm? >I have different needs depending upon which host I am accessing. You can't in 2.6. BUFFER changes the serial devices buffer size, not the maximum packet size. KMAXPACK in later version will do what you want. >2. Because of the currently slow transfer time with the default short packet >I would like to put VT100 in the background and do other things. When I click >the front to back gadget I get no response. I am usually running from the CLI >or Shell. Is the failure of front-to-back strictly because of where I am >running? If so, will running VT100 from an icon clear that problem? If not, I >would appreciate a work-around that will let me start a lengthly transfer and >put it in the background. This is one place that, I believe, 2.6 is "better" than the later versions. When VT100 opens its window on a custom screen (caused by the init file command SCREEN CUSTOM) it should allow the window to be moved down a pixel or two to allow the user access to the SCREEN's front/back gadgets. You need to click in one of THEM, not in the window's gadgets (if VT100 is on its own screen there are NO other windows on that screen so there is no other window to put VT100's behind). I generally screw up when I modify VT100 and forget to allow the user to slide the window down...hence, users with custom screens can't easily move the window (and screen) to the back. Left-Amiga N and M allow you to move screens without having to get to the screen's front/back gadgets. Till I release 2.9, this is how you'll have to do it (sorry). To summarize: if you use SCREEN CUSTOM, use Left-Amiga M and/or N to "hide" the screen. >3. The documentation does not address the file transfer requestor that is >used to indicate the file and the in-flight statistics. The DONE gadget that >is displayed causes me a little confusion. If I click on it the requestor >goes away, but I sometimes end up sending a garbage character or two to the >host. If I click outside the requstor the requestor will go away and no >spurious garbage is generated. Does VT100 have some hard and fast rule here? Hmmm...you've got me here. I just can't remember what happened in this case with 2.6. 2.8 is better but not perfect. I'll try to address the documentation in the 2.9 release. >(This is an amazing world - - The more I know, the more I know I don't know!) Yeah, ain't it great! >Regards, Jerry -- Tony Sumrall acs@pccuts.pcc.amdahl.com <=> amdahl!pccuts!acs [ Opinions expressed herein are the author's and should not be construed to reflect the views of Amdahl Corp. ]