On Tue, 7 May 2013, Sampsa Laine wrote:
Got the DS200 running, turns out it was a bad transceiver.
Aww. I wanted another one to fix. ;)
Will try to get the 300 up if I can find a transceiver.
sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Tue, 7 May 2013, Sampsa Laine wrote:
Anybody have this?
My DS200/MC has just bit the dust it seems.
Send the DS200 my way. I like fixing those.
sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On 2013-05-07 18:23, Bob Armstrong wrote:
BRUSYS is a standalone system that runs without any disk.
Yep, that's what I thought.
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.
Well, that's one use. But you can also use it to backup or copy the
system disk too (e.g. a disk to disk transfer). That part is even
documented in the RSX manual.
Right, if you boot BRUSYS from a tape. If you actually booted from a disk, you'd use BRU on that disk for this instead.
If you copy BRUSYS.SYS to another disk, it should work just as well as from
the original disk.
Sounds good, but in practice it doesn't. Sorry...
Exactly what did you do for that to happen? It sounds more than strange.
So, whatever you did when you copied the file over to another disk was
probably
not doing what you thought you were doing.
UFD DL0:[6,54]
PIP DL0:[6,54]/CO=DU0:[6,54]*.*
Right. And then you do BOO DL:[6,54]BRUSYS, which should be just fine.
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.
Yep, that's basically what I did to create the bootable RSX system on DL0
from DU0.
If you have any other suggestions, please let me know. I'd really like to
get S/A BRU working on DL0.
There are some very important details here.
If you take your normal system and copy it over (I'm not talking about BRUSYS now), you will run a VMR on your new disk, using your SYSVMR.CMD and a copy of RSX11M.TSK copied into a new RSX11M.SYS. SYSTEM.CMD will then install all partitions, device drivers and tasks needed to get the system bootable. However, SYSVMR installs stuff using the device names LB: and SY:, so before running VMR, you need to make sure these names points to your new disk, or else you will install all tasks from a different disk. This is perfectly acceptable in VMR point of view, but when you boot your new disk, the "other" disk, where all the images are, is not mounted, and thus they will all be removed at boot time, and nothing will work.
So, essentially, getting a new disk set up, based on a current disk.
UFD xx:[1,1]
UFD xx:[1,54]
PIP xx:[1,1]=oo:[1,1]*.*
PIP xx:[1,54]=oo:[1,54]*.*
PIP xx:[1,54]RSX11M.SYS/CO/NV/BL:1026.=xx:[1,54]RSX11M.TSK
ASN LB:=xx:
ASN SY:=xx:
SET /UIC=[1,54]
VMR @SYSVMR
BOO [1,54]
SAV /WB
There are probably details you need to polish, but this should give you a rough idea.
(For M+, you also want [3,54], and of course there are plenty of other stuff you might want to suck over.)
Johnny
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
Looking at logs on MIM, I can see a request from 08-00-2B-1B-DF-1D. However after some loading time, I get an error "Line communication error". No idea what that might mean.
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
On 7 May 2013, at 18:22, Johnny Billquist <bqt at softjar.se> wrote:
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.)
The display just says "2"
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.
How do I reset the NVRAM?
BRUSYS is a standalone system that runs without any disk.
Yep, that's what I thought.
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.
Well, that's one use. But you can also use it to backup or copy the
system disk too (e.g. a disk to disk transfer). That part is even
documented in the RSX manual.
If you copy BRUSYS.SYS to another disk, it should work just as well as from
the original disk.
Sounds good, but in practice it doesn't. Sorry...
So, whatever you did when you copied the file over to another disk was
probably
not doing what you thought you were doing.
UFD DL0:[6,54]
PIP DL0:[6,54]/CO=DU0:[6,54]*.*
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.
Yep, that's basically what I did to create the bootable RSX system on DL0
from DU0.
If you have any other suggestions, please let me know. I'd really like to
get S/A BRU working on DL0.
Thanks,
Bob
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
