I dont know when this cropped up, but im running 997.8/997.6 ate/linux, and now, when printing to a network printer using xcall spool,"prt000", which is using auxloc (see below), it prints, but then hangs and never returns to ATE... I put a trace right before and right after the xcall spool statment, and the second trace never prints. A CTRL-C will wake up ATE and cause a bit of flakiness from there.

Also, there is also being generated an additional FF after the document. I dont know if that is new, or if windows automatically does this, but my program is only requesting 1 chr(12) at the end of report or page to eject the page, but im getting an additional blank page as well. Thanks.


Here is the prt000.ini that we have been using:

; File for Terminal Printing
; Sample printer initialization file for
; A-Shell/UNIX
DEVICE= AUXLOC: ; Redirect output to terminal/PC
;FORMFEED= ON ; Formfeed after print jobs (A-Shell/DOS)
DELETE= OFF ; Delete after spool
;PREFIX= SYS:LP0.PFX ; Send as a prefix
;SUFFIX= SYS:LP0.SFX ; Send as a suffix
AUTOFF= OFF ; Auto append FF if needed (overrides SUFFIX)

Further testing has also revealed that in some cases, the text the program would have displayed on the screen after print was complete is being echoed to the printer instead of the screen.

i.e. I pop a dialog after the print request that says the print request was passed onto the printer.. and instead of that showing on the screen, it dumped that to the printer. Feels like a timing or other related issue with shutting down the aux output properly.

I think this crept in around 997.1 when support for WYSE50 was added. (The aux on/off codes between Wyse and AMxxx emulations are reversed, which led to a mixup in detecting the aux off code.) Try running this update:

http://www.microsabio.net/dist/temphold/ash-5.0.998.1-w32-upd.zip

Thanks, this has resolved it.

But, Doh! I installed 2 systems yesterday with our FMC Install version of ATE of 997.6... was that version corrupt?

When the dust settles on this, could you please build us a new FMC install.

Thanks.

Yes, the problem started in ATE 997.1 - sorry about that. (worked fine with WYSE5G mode, but not with AM75G)

I'll post a set of 998.1 installs and updates shortly...

Thanks for the new builds.

Jack, when you get a chance, can you post some "tw" updates (in AIX and Linux-generic). We are running into this problem as well...

John - this particular fix was entirely on the ATE side, so you should be able to just pull down the latest 998.1 install package (or run ASHUPD).

In general though, I'm working on a couple of other minor issues and will then post linux/aix updates (although I'm not sure that you need them.)

i have A-Shell/AIX Version 5.0.997.7 load on my machine. i have updated ATE to 5.0.998.1 build 3.1.189-02 installed on my pc.

when i attempt to print to device=AUXLOC: it continues to print to my ATE screen, instead of to my windows printer.

Also ... AUXLOC does work in Zterm.

Also ... ASHUPD does not update anything. ::
==========
A-Shell Update 1.2(120)
Checking for A-Shell/UNIX updates...
Checking for ASHUPD.LIT update...
Current A-Shell version: A-Shell Version 5.0.997.7
Current ashell executable is up to date

Proceed with updating any auxiliary components (LIT, RUN, etc.) [Y/n] ?Y
Checking for LIT/RUN/other updates...
Operation complete; 0 files updated

See OPR:ASHUPD.TRC and OPR:ASHUPD.LOG for details.
Also: ASHUPD/RECAP to display recap of last update.
==========


Jason

Ouch. First, I meant "ATEUPD", not "ASHUPD". (ASHUPD would only update the server version of A-Shell, and I remain convinced that the problem here is only on the client. The fact that ZTERM's aux printing works seems to confirm that as well.)

The problem that started this thread had to do with a mixup between the AUX ON/OFF codes in AMxxx vs WYxxx emulations (which are reversed, for whatever reason). So my guess is that the issue is specific to the combination of emulation under ATE and TERM setting on the server side. Can you confirm what those are?

As for the license expiring, that could have happened simply because you updated the ATE client and your ATE license (stored on the server) was due to expire. You should be able to check that with the ABOUT utility. If necessary, ask Ty to generate an updated ATE license for you.

I think I've confirmed that the aux printing is now broken in the WYxxx emulations of ATE. Stand by for a fix...

Sorry, my bad. When I fixed the aux problem for AMxxx, I broke it for WYxxx. It's fixed in 998.3, which you should be able to get via RUN ATEUPD, or, if not that, you can the full ate-5.0.998.3.exe