Hi,
Thanks for the reply. A late update, and plea for more help:
I'm looking at
https://techpubs.jurassic.nl/library/man.../ch09.html for help with Command Monitor usage.
I'm connecting the 13W3-to-VGA cable to the Indy and my Dell U2412M monitor.
Turning on the Indy I hear the boot tune (faintly), and press Esc immediately after that.
I then press "5" and Enter, and hope I'm in the Command Monitor.
Then I perform "unsetenv monitor". Nothing happens on the monitor.
I try "init". Nothing happens on the monitor.
I try "exit" to get back to the System Maintenance Menu, and then press "5" and Enter to get back to the Command Monitor. Nothing happens on the monitor.
I'm working in the dark, as I've found no adapters to go from VGA to a connector my TV has. So the only way I've found to check whether I've managed to enter the Command Monitor or not (i.e. if I've timed the Esc press correctly) is the "off" command, which sometimes works and sometimes not.
Turning the computer on again after a successful "off" command, I still get a blank monitor, even though I must have been in the Command Monitor when I entered "off", and before entering "off" I performed "unsetenv monitor". So "unsetenv monitor" does not give the expected result.
So, any ideas as to how to proceed? Any sequence of commands and keypresses that should get me a working VGA signal?
Also, some questions:
1. I've tried the "ping" command, with a TP cable to a laptop. The LED on the TP connector on the laptop turns on, so there is a link. But just trying "ping 192.168.1.1" doesn't work, the tcpdump on the laptop shows nothing. "setenv netaddr 192.168.1.2" and then "ping 192.168.1.1" also doesn't work. According to the instructions the "setenv netaddr" command is just for bootp booting, is that correct? In that case, how is one supposed to use the "ping" command?
2. There's a "-p" flag to the setenv command, but not to the "unsetenv" command. Does "unsetenv monitor" survive exiting to the System Maintenance Menu (with "exit") and then pressing "5"+Enter to get back to the Command Monitor? Does "unsetenv monitor" survive an "off" command and then pressing the power button to start the system again (the power cable to the Indy is plugged in throughout this)?
3. Is there any way, other than the "off" and "ping" commands, to somehow check whether I've even managed to enter the Command Monitor?
