On 2013-05-07 18:18, Sampsa Laine wrote:
Do I need to reset this thing somehow?
All I'm getting is garbage, thinking the baud rate is wrong - it's connected to a VT420 on port 1, baud rate 9600
Has it booted, or is it still sitting in the boot loop? (You can see that on the display of the DS300, when it has booted, it do an animation loop on the display.)
Before it has booted it prints things, normally on port 1, and I think at the fixed speed of 9600. Once it has booted, it all depends on the setup of the port, which is stored in nonvolatile ram.
Johnny
sampsa
On 7 May 2013, at 18:12, Sampsa Laine <sampsa at mac.com> wrote:
OK, I'll power it up and see what happens :)
On 7 May 2013, at 18:07, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-05-07 17:24, Sampsa Laine wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
Yes, both V1 and V2. And MIM serves anyone connected with MOP if they request it.
Johnny
Do I need to reset this thing somehow?
All I'm getting is garbage, thinking the baud rate is wrong - it's connected to a VT420 on port 1, baud rate 9600
sampsa
On 7 May 2013, at 18:12, Sampsa Laine <sampsa at mac.com> wrote:
OK, I'll power it up and see what happens :)
On 7 May 2013, at 18:07, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-05-07 17:24, Sampsa Laine wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
Yes, both V1 and V2. And MIM serves anyone connected with MOP if they request it.
Johnny
On 2013-05-07 18:02, Bob Armstrong wrote:
I've built an RSX system (Yipee :-) I've even figured out how to VMR it
if I change the configuration or move it to another device. Cool!
In [6,54] there's a BRUSYS.SYS which I'm guessing is supposed to be a
standalone BRU system. I can boot it on my original disk and it works
great, but if I copy the contents of [6,54] to another drive then it doesn't
work anymore. I can still boot it, but it no longer knows about any tasks
(e.g. BAD, BRU, etc). I'm guessing that it needs to be VMR'ed in its new
home so that it can find the task files on the new disk.
But what's the procedure for doing this? For the real system there's a
RSX11M.TSK file in [1,54] as well as a SYSVMR.CMD file that you use to
actually build the bootable system. Where's the command file for VMRing
BRUSYS? And what's the unconfigured system that you start from? And what's
the VMRM64.TSK file in [6,54] for (I'm guessing it has something to do with
all this)?
BRUSYS is a standalone system that runs without any disk. It has all the necessary tasks in order to install a distribution on a disk.
This is a system that is only intended for when you boot from tape.
VMRM46.TSK is a plain 11M V4.6 VMR task. It is good to have since its a known version matching all the needs to write your BRUSYS to a bootable tape.
If you copy BRUSYS.SYS to another disk, it should work just as well as from the original disk. All tasks needed are actually included in the image file (think of BRUSYS.SYS as a memory dump).
You cannot set up a disk to boot BRUSYS from scratch.
Booting from scratch to a disk requires that you first boot up the system, and then save it again, and update the boot block. BRUSYS do not have that ability.
So, whatever you did when you copied the file over to another disk was probably not doing what you thought you were doing.
Any bootable disk is normally created by doing a build of a normal RSX system, copy all the files to the target disk, do a VMR on the target disk, boot the result, and then do a SAV /WB to dump the memory, and update the boot block.
To create a bootable tape, on the other hand, you use VMR. VMR have a SAV command as well, which writes to tapes, and creates a bootable tape with the system you are manipulating.
Johnny
OK, I'll power it up and see what happens :)
On 7 May 2013, at 18:07, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-05-07 17:24, Sampsa Laine wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
Yes, both V1 and V2. And MIM serves anyone connected with MOP if they request it.
Johnny
I'm starting a new job. Part of that is being trained on their application that I'll be supporting.
The training will be taking place in the office in London.
For all of you EU-ers who'll be in London, near London or within reasonable travel distance to London the week of June 3rd contact me off-list. I'd love the chance to meet up with people.
-brian
On 2013-05-07 17:24, Sampsa Laine wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
Yes, both V1 and V2. And MIM serves anyone connected with MOP if they request it.
Johnny
I've built an RSX system (Yipee :-) I've even figured out how to VMR it
if I change the configuration or move it to another device. Cool!
In [6,54] there's a BRUSYS.SYS which I'm guessing is supposed to be a
standalone BRU system. I can boot it on my original disk and it works
great, but if I copy the contents of [6,54] to another drive then it doesn't
work anymore. I can still boot it, but it no longer knows about any tasks
(e.g. BAD, BRU, etc). I'm guessing that it needs to be VMR'ed in its new
home so that it can find the task files on the new disk.
But what's the procedure for doing this? For the real system there's a
RSX11M.TSK file in [1,54] as well as a SYSVMR.CMD file that you use to
actually build the bootable system. Where's the command file for VMRing
BRUSYS? And what's the unconfigured system that you start from? And what's
the VMRM64.TSK file in [6,54] for (I'm guessing it has something to do with
all this)?
Thanks,
Bob
I have it. I will put it online when I get to my desk in about an hour.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On May 7, 2013, at 11:24 AM, Sampsa Laine <sampsa at mac.com> wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
sampsa
Johnny Billquist wrote:
I thought I'd plug a little for a few utilities and tools that I have used, sometimes, for years under RSX, that others might not know about, but find useful.
Some more programs for the RSX available at BOPOHA::[.RSX-11.SOFTWARE]
--
CAL*.* - UNIX-like `cal' command (M/M+)
PUT*.* - send the commands to any terminal in the system (M/M+)
TDXF*.* - DEC TDX replacement (M/M+)
UPTIME.* - mu own version of UNIX-like `uptime' command (M+)
WRITE.* - ugly UNIX-like `write' program (M+)
--
>CAL JUN 2013
June 2013
Su Mo Tu We Th Fr Sa
1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30
>PUT TT1:HEL GUEST/
15:34:06 Login user GUEST [377,377] TT1:
>PUT /NW TT1:RMD
>UPT
15:35:18 up 0 day(s), 02:41, 3 user(s), 0 batch job(s), 16 active task(s)
>
Message from BIGSYS::GUEST (TT1:) at 15:36
This is a test...
[EOF]
