On 2013-05-07 18:54, Bob Armstrong wrote:
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.
I just booted it up and tried it to get the real message. Here's what I'm
doing -
Thanks. Now we're getting somewhere. :-)
Hardware boot DL0. This boots the "real" RSX; when it gets to the MCR
prompt, I say "BOO [6,54]BRUSYS".
BRUSYS boots normally, and asks the "first device/second device" stuff.
FWIW, I say "DL0" and "MS0".
That is probably a bad idea. The first device is where the distribution is. The second is the target where you want to install the stuff.
Hit enter and get the ">" prompt.
At this point, I enter "TIM 09:45 7-may-85" and it says
TIM -- 2
Syntax error. The MCR in BRUSYS is more than a little stupid.
You need to figure out in which form the time needs to be written for TIM to accept it. Probably something like "TIM 09:45 5/7/85".
Not "error 2" (sorry, I misremembered that part); just "2" ...
Yeah. MCR in BRUSYS is so limited it only gives these kind of error messages.
Typing BRU, BAD or INI all produce
MCR -- 1
Probably because BRU, BAD and INI are not known commands in MCR. You need to type "RUN BRU" and so on.
Curiously, entering just "TIM" with no argument actually works (although it
produces a bogus date/time).
:-)
I've never seen messages like this either; I'm hoping they mean something
to somebody.
I hope the above helps...
Johnny
On Tue, 7 May 2013, Sampsa Laine wrote:
Yeah, I'll try to get it working, I have NO IDEA what I'm doing though, no documentation that I can find by googling aside from some VMS install guide.
Any idea how to reset it to it's factory settings?
Holding the reset button during power on I believe. Can't remember for how long though.
On 7 May 2013, at 18:41, Johnny Billquist <bqt at softjar.se> wrote:
nning, turns out it was a bad transceiver.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Yeah, I'll try to get it working, I have NO IDEA what I'm doing though, no documentation that I can find by googling aside from some VMS install guide.
Any idea how to reset it to it's factory settings?
On 7 May 2013, at 18:41, Johnny Billquist <bqt at softjar.se> wrote:
nning, turns out it was a bad transceiver.
On Tue, 7 May 2013, Johnny Billquist wrote:
On 2013-05-07 18:48, Cory Smelosky wrote:
On Tue, 7 May 2013, Johnny Billquist wrote:
On 2013-05-07 18:35, Cory Smelosky wrote:
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.
Every time I've had a problem with any of these, it has been the power
supply. Got any hints on what breaks?
In the case of mine the fans failed which resulted in rubber around
inductors melting and having other components fail due to the heat.
Seems like similar has happened to people around the internet.
http://osx.dev.gimme-sympathy.org/users/b4/weblog/6b8a6/images/0e170.JPG#32…
I actually have ones with no fans...
Hopefully not with the original PSU? ;)
The board seems to be fine without fans...it's just the PSU needs them. I have a little fan running on my DECserver that has an external PSU now. It runs fine like this.
Although, in the case of mine the fans spinning in their condition probably would've resulted in extra heat.
(I also noticed that MIM tried booting a DS200 for quite a while and
failing, with the same "Line communication error" results. Same
transciever?)
Johnny
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
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.
I just booted it up and tried it to get the real message. Here's what I'm
doing -
Hardware boot DL0. This boots the "real" RSX; when it gets to the MCR
prompt, I say "BOO [6,54]BRUSYS".
BRUSYS boots normally, and asks the "first device/second device" stuff.
FWIW, I say "DL0" and "MS0".
Hit enter and get the ">" prompt.
At this point, I enter "TIM 09:45 7-may-85" and it says
TIM -- 2
Not "error 2" (sorry, I misremembered that part); just "2" ...
Typing BRU, BAD or INI all produce
MCR -- 1
Curiously, entering just "TIM" with no argument actually works (although it
produces a bogus date/time).
I've never seen messages like this either; I'm hoping they mean something
to somebody.
Thanks,
Bob
On 2013-05-07 18:48, Cory Smelosky wrote:
On Tue, 7 May 2013, Johnny Billquist wrote:
On 2013-05-07 18:35, Cory Smelosky wrote:
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.
Every time I've had a problem with any of these, it has been the power
supply. Got any hints on what breaks?
In the case of mine the fans failed which resulted in rubber around
inductors melting and having other components fail due to the heat.
Seems like similar has happened to people around the internet.
http://osx.dev.gimme-sympathy.org/users/b4/weblog/6b8a6/images/0e170.JPG#32…
I actually have ones with no fans...
(I also noticed that MIM tried booting a DS200 for quite a while and failing, with the same "Line communication error" results. Same transciever?)
Johnny
On 2013-05-07 18:45, Johnny Billquist wrote:
On 2013-05-07 18:41, Bob Armstrong wrote:
But the copy of BRUSYS.SYS on DL0 doesn't work. You can boot it
(using
BOO, just like above) and it'll ask for the first and second devices as
usual. But then once it's booted none of the tasks work - running
INI, BAD,
BRU all produce MCR errors (it says "MCR - error nn"; I forget the exact
number, but I could boot it up again and see if you need to know).
Those numbers would be helpful, but it sounds really weird that it would
not work just fine...
Give me the numbers, and maybe we can figure out what the errors are,
and go from there.
A full transcript would be even better. ;-)
(Although I should probably also point out that you do not need to copy the file anywhere to use it. What it booted from is rather irrelevant. But then again, I could also be totally wrong...)
Johnny
On Tue, 7 May 2013, Johnny Billquist wrote:
On 2013-05-07 18:35, Cory Smelosky wrote:
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.
Every time I've had a problem with any of these, it has been the power
supply. Got any hints on what breaks?
In the case of mine the fans failed which resulted in rubber around inductors melting and having other components fail due to the heat. Seems like similar has happened to people around the internet.
http://osx.dev.gimme-sympathy.org/users/b4/weblog/6b8a6/images/0e170.JPG#32…
Johnny
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On 2013-05-07 18:41, Bob Armstrong wrote:
You cannot set up a disk to boot BRUSYS from scratch.
Sorry, maybe I didn't make it clear but this ISN'T what I want to do. I'm
perfectly happy with booting the real RSX on DL0 (which works fine now) and
then saying "BOO [6,54]BRUSYS". That works great on DU0 - the BRUSYS boots,
asks the usual "enter the first device...", "enter the second device..."
dialog, and then you can run BAD, INI, BRU and I don't know what else.
Ok.
But the copy of BRUSYS.SYS on DL0 doesn't work. You can boot it (using
BOO, just like above) and it'll ask for the first and second devices as
usual. But then once it's booted none of the tasks work - running INI, BAD,
BRU all produce MCR errors (it says "MCR - error nn"; I forget the exact
number, but I could boot it up again and see if you need to know).
Those numbers would be helpful, but it sounds really weird that it would not work just fine...
Give me the numbers, and maybe we can figure out what the errors are, and go from there.
Johnny
On 2013-05-07 18:35, Cory Smelosky wrote:
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.
Every time I've had a problem with any of these, it has been the power supply. Got any hints on what breaks?
Johnny
