TRMDEF.INI
#26379
07 Feb 09 11:54 AM
|
Anonymous
Unregistered
|
Anonymous
Unregistered
|
Having just set up Ashell 5.1.1136.1c on a 64 bit Vista machine I am having difficulty setting the job names in TRMDEF.INI As the software relies on each user having a Job name of JOBnn it is essential that I make this work.
The computer name is EDL-PC-CH
Miame.ini has CONSOLE=NETUNIQUE,PCTDVG
TRMDEF.INI has
TRMDEF=EDL-PC-CH:1,JOB01,TERM1,PCTDVG TRMDEF=EDL-PC-CH:2,JOB02,TERM2,PCTDVG TRMDEF=EDL-PC-CH:3,JOB03,TERM3,PCTDVG
each job comes up as TSKAAA, TSKAAB, TSKAAC
apart from the computer name, this is as it was previously on AShell 4.8 where it worked fine.
any suggestions please
CH
|
|
|
Re: TRMDEF.INI
#26380
07 Feb 09 05:10 PM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
Member
|
Member
Joined: Jun 2001
Posts: 11,794 |
It would be helpful to verify the console names generated by A-Shell, which you can display with SYSTAT/C. It may be that the syntax is slightly different (perhaps EDL-PC-CH:01 rather than :1?)
|
|
|
Re: TRMDEF.INI
#26381
09 Feb 09 04:33 AM
|
Joined: Sep 2003
Posts: 4,158
Steve - Caliq
Member
|
Member
Joined: Sep 2003
Posts: 4,158 |
Hi Colin, nice to see another friendly face pop on on the BBS I just tried your trmdef.ini under my Ashell 5.1.1134.3c under 32Bit Vista and it looks like it works fine, so as Jacks says I would first confirm your console name maybe 32bit and 64bit Vista returns something different.
|
|
|
Re: TRMDEF.INI
#26382
09 Feb 09 12:07 PM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
Member
|
Member
Joined: Jun 2001
Posts: 11,794 |
Indeed, I suspect that the whole issue is the zero after the colon, i.e. ":01", ":02", etc. instead of ":1", ":2", etc. It seems like we've used the ":01" format forever, but perhaps back in 4.8 it was only ":1".
|
|
|
Re: TRMDEF.INI
#26383
12 Feb 09 04:50 AM
|
Anonymous
Unregistered
|
Anonymous
Unregistered
|
Well done folks - it was the '0'. EDL-PC-CH:01 works fine. One other problem - despite loading and installing mfont & (mfont2) off my old system when I select Miame Terminal it always rolls back to Courier - which on a reduced screen looks like a spider crawled across the screen. It doesn't seem to like Miame Terminal. Hi there Steve - give my regards to everyone there - if there are any others that remember me! Thanks for your help.
|
|
|
Re: TRMDEF.INI
#26384
12 Feb 09 07:53 AM
|
Joined: Sep 2003
Posts: 4,158
Steve - Caliq
Member
|
Member
Joined: Sep 2003
Posts: 4,158 |
Will do Colin, yes there are sure a few left here who know you. Ive not used the old mfont for a while, think we use "Lucida Console" (from what I can remember) do they all do the same?
|
|
|
Re: TRMDEF.INI
#26385
12 Feb 09 10:45 AM
|
Joined: Jun 2001
Posts: 11,794
Jack McGregor
Member
|
Member
Joined: Jun 2001
Posts: 11,794 |
Colin -
It's true that virtually no use uses the MIAME Terminal font anymore; it quietly slipped off the stage some years ago without anyone ever noticing (until you did). In theory, if the font was installed, I don't see any reason why it wouldn't work, although you may have trouble keeping it selected if you have a FONT= statement in the MIAME.INI which references something else.
As for which is the best font, indeed, Courier is lousy, but Lucida Console (standard on all Windows since W2000), Andale Mono (available free from Microsoft), or Consolas (included in Vista) are all quite good. And much more scalable than the MIAME Terminal font, especially for higher resolution screens. (I don't know how small your window size is, but certainly anything from 640x480 and up is quite readable in any of those fonts.)
|
|
|
|
|