4 Jan
2015
4 Jan
'15
8:32 a.m.
Hi everyone,
I downloaded Dave Pitts' SIM990 emulator and the pre-rolled DX10 disk
images available on his site yesterday evening, thinking I'd give it a run.
SIM990 compiled clean; I'm running on Debian 7.7, 32-bit, on an Intel D510
Atom system.
I feel as though this should be plenty of power... I run Hercules on this
same system all the time to fool around with MTS and MVS 3.8J and I find
the performance to be just fine... (way better than on my old Sun Fire
V120s, LOL)
I extracted the DX10 images and I started the emulator on them as directed:
sim990 -msc 12 512K dx10.cfg
For a terminal emulator, I'm using PuTTY; I also tried Procomm Plus (latest
version) with a few different emulations and couldn't make it work, I seem
to get furthest with PuTTY.
I connect using Telnet protocol to port 2000 on the emulation host. I get
the DX10 IPL screen:
* TEXAS INSTRUMENTS * DX10 "SYS3 " SYSTEM IPL * ST01
I hit F10 then "!" and I get a sort of menu-like thing:
****************************
DX10 3.7.0
THIS SYSTEM HAS THE FOLLOWING SUBSYSTEMS INSTALLED:
COBOL
PASCAL
SORTMRG
BASIC
...
*****************************
I don't get a signon prompt but I assume user login has not been enabled on
this basic disk image, however...
I never get the SCI prompt, [], and it seems unresponsive; I've tried
typing i.e. BASIC, COBOL, commands from the DX10 manual, totally random
junk, etc. and I don't get any response; I mean, it seems to be refreshing
the screen every time I hit RETURN; it's not giving me any kind of error
message, but it's not really doing anything either.
Is my emulation just not working right? I tried the DNOS image too and I
was able to get a little further... At IPL it prompts for date and time
which I'm able to fill in, and there is a login stage (l: SYSTEM, p:
SYSTEM) which I can get through, just use the cursor keys to move through
the fields and hit RETURN to push the screen (it seems screen-oriented,
feels reminiscent of an IBM) but once that's done I land at an equally
unresponsive main menu just like I describe occurring with DX10.
Has anyone played with this and found a Telnet client that works well? I
don't see anything on the author's site other than to note that Windows
Telnet won't work. Not clear what I'm doing wrong.
Thanks!
Sean
12:05 p.m.
Could be? That might throw me... I don't know if there is any contemporary
software out there that will emulate the TI VDTs... I checked in Procomm
which is the best I've got for emulating strange terminals and it's got
nothing.
Best,
Sean
On Sun, Jan 4, 2015 at 2:22 PM, Al Kossow <aek at bitsavers.org> wrote:
On 1/4/15 8:32 AM, Sean Caron wrote:
For a terminal emulator, I'm using PuTTY
It just occured to me that you probably have to be running something that
looks
like a TI CRT.
3:35 p.m.
On 1/4/2015 12:05 PM, Sean Caron wrote:
Could be? That might throw me... I don't know if
there is any contemporary
software out there that will emulate the TI VDTs... I checked in Procomm
which is the best I've got for emulating strange terminals and it's got
nothing.
Best,
Sean
The description says that ansi terminal is required.
I got a response from the emulator. I have a windows XP running Putty
for my main system.
I was ssh'ed into a linux system running the emulator. I compiled it
and moved it to /usr/local/bin.
I started with the DX10 system as Sean did. when you follow the example
(with path set to /usr/local/bin and sim990 there) you get an error as
the simulator cannot find the roms.
I moved copies from the build directory into the dx10 directory, and ran
the emulator again. I got a good message there.
jws at jws2:~/nas/projects/jws-main/ti990/dx10$ sim990 -msc 12 512K dx10.cfg
TI 990 Simulator 3.0.2: /12 CPU 512K
To connect to the emulator, I used another putty session ssh'ed into the
same linux system. Once there I used linux telnet to connect to the
emulator. The ssh session will be an ANSI compatable ssh terminal
emulation. Running telnet into the same system to port 2000, means that
the session supports ANSI for the terminal.
Once connected, I hit F10 (and then carriage return). The banner appeared.
I typed the LL to elicit a response. I The "ERROR, COMMAND..." message
appeared after typing ll (echoed back upper cased) then enter.
Below is what I have so far. Time to read and see what should actually
work.
Jim
********************************************************************************
* *
* DX10 3.7.0 *
* *
* THIS SYSTEM HAS THE FOLLOWING SUBSYSTEMS
INSTALLED: *
* *
* COBOL 3.5.0 FOCAL 1.0.4 (REQUIRES /12
CPU) *
* PASCAL 1.8.0 FORTH
1.0.2 *
* SORTMRG 3.1.0 TXDS FORTRAN
3.1.0 *
* BASIC 3.1.0 *
* *
* THIS SYSTEM HAS BEEN PATCHED FOR
Y2K. *
* *
********************************************************************************
LL
ERROR, COMMAND OR SCROLL FUNCTION REQUIRED:
4:02 p.m.
New subject: SIM990/DX10 help? Keyboard mappings
On 1/4/2015 3:35 PM, jwsmobile wrote:
The
description says that ansi terminal is required.
Page 342, or A-2 of the Errors and codes manuals has keyboard mapping
pages. Studying them for inspiration.
I have not found the error message anywhere as to what keystroke is
required for a "Command" or "Scroll" yet, but will play some more. The
keyboard mapping might help.
Jim
http://bitsavers.trailing-edge.com/pdf/ti/990/dx10/0946250-9706F_DX10_Vol6_…
4:04 p.m.
On 1/4/2015 3:35 PM, jwsmobile wrote:
Below is what I have so far.
Control X is your friend. It is the
"Command" key for some terminal,
and gets a "System is not initialized response back.
Onward to screw up my disk image...
T E X A S I N S T R U M E N T S
D X 1 0 S Y S T E M 3 . 7 . 0
SELECT ONE OF THE FOLLOWING COMMAND GROUPS
/DEV - DEVICE OPERATIONS
/FILE - FILE OPERATIONS
/PDEV - PROGRAM DEVELOPMENT
/SMAIN - DX10 MAINTENANCE
/SOP - DX10 OPERATION
Jim
7:43 p.m.
Yeah, I kind of "figured it out"... poring through README.txt and just
noodling around a little bit. So, you extract the disk images and run
sim990 (still, from a SSH session via PuTTY):
sim990 -m 10 -s 512K -c dx10.cfg
Once it starts up, from within that window, I found I could hit Esc (not
F10) then "!" and then I got an SCI prompt and a message about the system
being uninitialized!
I ran a "IS" command as described in Vol. 2 of the DX-10 documentation...
this system is pretty easy to use... just filled in the date and ran with
defaults otherwise. It churned for no more than 30 seconds and eventually
it lands at a QUIT message. I let it sit for a while and once I convince
myself it's idle, I try poking at it again...
Hit Esc and "!" and I get prompted to sign on to SCI now! I logged in with
the username and password given in README.txt (SYS001/SYSTEM). I get the
SCI prompt at the console, I can run commands just fine. Cool!
So, now that I can use the system from the console, I'm trying to test it
with Telnet again, to see if it'll behave differently after the system has
been initialized.
I find that now when I open Telnet sessions to port 2000, I get a prompt to
signon to SCI, which I didn't get before, and if I create a new user
account for myself using "AUI" at the console, I can get logged in. After
login, I'm at the same menu I saw before, but I still don't get a SCI
prompt in the Telnet sessions like I do from the console.
I strongly am suspecting it might be an "emulation" issue with the Telnet
sessions, where the console is set up as a "TTY" while it is expecting the
Telnet sessions to look more like a TI VDT. I'm still poking at it but at
this point I'm confident I'll get to the bottom of it... or... I can just
use it from the console, failing all else.
The scheme used for user accounts in DX10 is bizarre and amusing. It took
me a minute to figure out that the user ID /is/ the three digits in the
account name and they need to be unique across accounts! LOL
Woo hoo!
Best,
Sean
On Sun, Jan 4, 2015 at 7:04 PM, jwsmobile <jws at jwsss.com> wrote:
On 1/4/2015 3:35 PM, jwsmobile wrote:
Below is what I have so far.
Control X is your friend. It is the "Command" key for some terminal,
and
gets a "System is not initialized response back.
Onward to screw up my disk image...
T E X A S I N S T R U M E N T S
D X 1 0 S Y S T E M 3 . 7 . 0
SELECT ONE OF THE FOLLOWING COMMAND GROUPS
/DEV - DEVICE OPERATIONS
/FILE - FILE OPERATIONS
/PDEV - PROGRAM DEVELOPMENT
/SMAIN - DX10 MAINTENANCE
/SOP - DX10 OPERATION
Jim
7:48 p.m.
And if I hit Ctrl-X in my Telnet session /now/ (after I have initialized
the system; this seems important) as you say, it works! I'm off! Thanks for
your ideas!
Best,
Sean
On Sun, Jan 4, 2015 at 10:43 PM, Sean Caron <scaron at umich.edu> wrote:
Yeah, I kind of "figured it out"... poring
through README.txt and just
noodling around a little bit. So, you extract the disk images and run
sim990 (still, from a SSH session via PuTTY):
sim990 -m 10 -s 512K -c dx10.cfg
Once it starts up, from within that window, I found I could hit Esc (not
F10) then "!" and then I got an SCI prompt and a message about the system
being uninitialized!
I ran a "IS" command as described in Vol. 2 of the DX-10 documentation...
this system is pretty easy to use... just filled in the date and ran with
defaults otherwise. It churned for no more than 30 seconds and eventually
it lands at a QUIT message. I let it sit for a while and once I convince
myself it's idle, I try poking at it again...
Hit Esc and "!" and I get prompted to sign on to SCI now! I logged in with
the username and password given in README.txt (SYS001/SYSTEM). I get the
SCI prompt at the console, I can run commands just fine. Cool!
So, now that I can use the system from the console, I'm trying to test it
with Telnet again, to see if it'll behave differently after the system has
been initialized.
I find that now when I open Telnet sessions to port 2000, I get a prompt
to signon to SCI, which I didn't get before, and if I create a new user
account for myself using "AUI" at the console, I can get logged in. After
login, I'm at the same menu I saw before, but I still don't get a SCI
prompt in the Telnet sessions like I do from the console.
I strongly am suspecting it might be an "emulation" issue with the Telnet
sessions, where the console is set up as a "TTY" while it is expecting the
Telnet sessions to look more like a TI VDT. I'm still poking at it but at
this point I'm confident I'll get to the bottom of it... or... I can just
use it from the console, failing all else.
The scheme used for user accounts in DX10 is bizarre and amusing. It took
me a minute to figure out that the user ID /is/ the three digits in the
account name and they need to be unique across accounts! LOL
Woo hoo!
Best,
Sean
On Sun, Jan 4, 2015 at 7:04 PM, jwsmobile <jws at jwsss.com> wrote:
On 1/4/2015 3:35 PM, jwsmobile wrote:
Below is what I have so far.
Control X is your friend. It is the "Command" key for some terminal,
and
gets a "System is not initialized response back.
Onward to screw up my disk image...
T E X A S I N S T R U M E N T S
D X 1 0 S Y S T E M 3 . 7 . 0
SELECT ONE OF THE FOLLOWING COMMAND GROUPS
/DEV - DEVICE OPERATIONS
/FILE - FILE OPERATIONS
/PDEV - PROGRAM DEVELOPMENT
/SMAIN - DX10 MAINTENANCE
/SOP - DX10 OPERATION
Jim
7:56 p.m.
Telnet is a little dodgy but Ctrl-X always brings back the SCI prompt once
you're logged in (given that the system has been initialized from the
console, first). The console (set up as TTY) seems to work with 100%
consistency. Honestly, I might just like to set the Telnet sessions up as
TTY, too, if I could, but this is definitely working well enough to get the
point across now.
I love it! SYSTEM COMMAND INTERPRETER - PLEASE LOG IN. No lowercase!
Best,
Sean
On Sun, Jan 4, 2015 at 10:48 PM, Sean Caron <scaron at umich.edu> wrote:
And if I hit Ctrl-X in my Telnet session /now/ (after
I have initialized
the system; this seems important) as you say, it works! I'm off! Thanks for
your ideas!
Best,
Sean
On Sun, Jan 4, 2015 at 10:43 PM, Sean Caron <scaron at umich.edu> wrote:
Yeah, I kind of "figured it out"...
poring through README.txt and just
noodling around a little bit. So, you extract the disk images and run
sim990 (still, from a SSH session via PuTTY):
sim990 -m 10 -s 512K -c dx10.cfg
Once it starts up, from within that window, I found I could hit Esc (not
F10) then "!" and then I got an SCI prompt and a message about the system
being uninitialized!
I ran a "IS" command as described in Vol. 2 of the DX-10 documentation...
this system is pretty easy to use... just filled in the date and ran with
defaults otherwise. It churned for no more than 30 seconds and eventually
it lands at a QUIT message. I let it sit for a while and once I convince
myself it's idle, I try poking at it again...
Hit Esc and "!" and I get prompted to sign on to SCI now! I logged in
with the username and password given in README.txt (SYS001/SYSTEM). I get
the SCI prompt at the console, I can run commands just fine. Cool!
So, now that I can use the system from the console, I'm trying to test it
with Telnet again, to see if it'll behave differently after the system has
been initialized.
I find that now when I open Telnet sessions to port 2000, I get a prompt
to signon to SCI, which I didn't get before, and if I create a new user
account for myself using "AUI" at the console, I can get logged in. After
login, I'm at the same menu I saw before, but I still don't get a SCI
prompt in the Telnet sessions like I do from the console.
I strongly am suspecting it might be an "emulation" issue with the Telnet
sessions, where the console is set up as a "TTY" while it is expecting the
Telnet sessions to look more like a TI VDT. I'm still poking at it but at
this point I'm confident I'll get to the bottom of it... or... I can just
use it from the console, failing all else.
The scheme used for user accounts in DX10 is bizarre and amusing. It took
me a minute to figure out that the user ID /is/ the three digits in the
account name and they need to be unique across accounts! LOL
Woo hoo!
Best,
Sean
On Sun, Jan 4, 2015 at 7:04 PM, jwsmobile <jws at jwsss.com> wrote:
On 1/4/2015 3:35 PM, jwsmobile wrote:
Below is what I have so far.
Control X is your friend. It is the "Command" key for some terminal,
and gets a "System is not initialized response back.
Onward to screw up my disk image...
T E X A S I N S T R U M E N T S
D X 1 0 S Y S T E M 3 . 7 . 0
SELECT ONE OF THE FOLLOWING COMMAND GROUPS
/DEV - DEVICE OPERATIONS
/FILE - FILE OPERATIONS
/PDEV - PROGRAM DEVELOPMENT
/SMAIN - DX10 MAINTENANCE
/SOP - DX10 OPERATION
Jim
8 p.m.
Sorry to keep responding to my own messages but I figure it's a good
documentary thread... I'll try to make this the last one ;)
The secret for best behavior in the Telnet sessions seems to be to hit
Ctrl-D instead of Enter. Once you do that, it appears to be pretty
well-behaved. So unusual! Quasi-screen-oriented, feels a little IBM-y, but
not.
Best,
Sean
On Sun, Jan 4, 2015 at 10:56 PM, Sean Caron <scaron at umich.edu> wrote:
Telnet is a little dodgy but Ctrl-X always brings back
the SCI prompt once
you're logged in (given that the system has been initialized from the
console, first). The console (set up as TTY) seems to work with 100%
consistency. Honestly, I might just like to set the Telnet sessions up as
TTY, too, if I could, but this is definitely working well enough to get the
point across now.
I love it! SYSTEM COMMAND INTERPRETER - PLEASE LOG IN. No lowercase!
Best,
Sean
On Sun, Jan 4, 2015 at 10:48 PM, Sean Caron <scaron at umich.edu> wrote:
And if I hit Ctrl-X in my Telnet session /now/
(after I have initialized
the system; this seems important) as you say, it works! I'm off! Thanks for
your ideas!
Best,
Sean
On Sun, Jan 4, 2015 at 10:43 PM, Sean Caron <scaron at umich.edu> wrote:
Yeah, I kind of "figured it out"...
poring through README.txt and just
noodling around a little bit. So, you extract the disk images and run
sim990 (still, from a SSH session via PuTTY):
sim990 -m 10 -s 512K -c dx10.cfg
Once it starts up, from within that window, I found I could hit Esc (not
F10) then "!" and then I got an SCI prompt and a message about the system
being uninitialized!
I ran a "IS" command as described in Vol. 2 of the DX-10
documentation... this system is pretty easy to use... just filled in the
date and ran with defaults otherwise. It churned for no more than 30
seconds and eventually it lands at a QUIT message. I let it sit for a while
and once I convince myself it's idle, I try poking at it again...
Hit Esc and "!" and I get prompted to sign on to SCI now! I logged in
with the username and password given in README.txt (SYS001/SYSTEM). I get
the SCI prompt at the console, I can run commands just fine. Cool!
So, now that I can use the system from the console, I'm trying to test
it with Telnet again, to see if it'll behave differently after the system
has been initialized.
I find that now when I open Telnet sessions to port 2000, I get a prompt
to signon to SCI, which I didn't get before, and if I create a new user
account for myself using "AUI" at the console, I can get logged in. After
login, I'm at the same menu I saw before, but I still don't get a SCI
prompt in the Telnet sessions like I do from the console.
I strongly am suspecting it might be an "emulation" issue with the
Telnet sessions, where the console is set up as a "TTY" while it is
expecting the Telnet sessions to look more like a TI VDT. I'm still poking
at it but at this point I'm confident I'll get to the bottom of it... or...
I can just use it from the console, failing all else.
The scheme used for user accounts in DX10 is bizarre and amusing. It
took me a minute to figure out that the user ID /is/ the three digits in
the account name and they need to be unique across accounts! LOL
Woo hoo!
Best,
Sean
On Sun, Jan 4, 2015 at 7:04 PM, jwsmobile <jws at jwsss.com> wrote:
On 1/4/2015 3:35 PM, jwsmobile wrote:
>
> Below is what I have so far.
>
Control X is your friend. It is the "Command" key for some terminal,
and gets a "System is not initialized response back.
Onward to screw up my disk image...
T E X A S I N S T R U M E N T S
D X 1 0 S Y S T E M 3 . 7 . 0
SELECT ONE OF THE FOLLOWING COMMAND GROUPS
/DEV - DEVICE OPERATIONS
/FILE - FILE OPERATIONS
/PDEV - PROGRAM DEVELOPMENT
/SMAIN - DX10 MAINTENANCE
/SOP - DX10 OPERATION
Jim
3420
days inactive
3421
days old
10 comments
4 participants
participants (4)
-
aek＠bitsavers.org -
jws＠jwsss.com -
jwsmail＠jwsss.com -
scaron＠umich.edu