When I've started up my MorphOS3.2 Mac Mini over the last couple of days I been getting a small Rx Output window with the message ...

Quote:

I thought it might have been the CRABUM tool strip script, but I replaced my amended version with the original script, and that made no difference, so I assume it must be something else. I did do some updates with Grunch, so I'm not sure if that has affected a program and is now causing this problem.

Anyone have any idea what the error message relates to, as I can't think what change I might have made to my system that would cause this error message ? In fact I cannot think of any specific change I have made to my MOS system to cause this.

Or, if there is a tool I can use to look into the boot-up mechanism to see what is causing it?

I can just close the Rx output window, and it doesn't return until I have to re-boot the machine, but I don't like problems that are unexplained, so thought I'd ask you guys for some idea of what might be causing it..

[ Edited by NewSense 30.08.2013 - 14:52 ]

This was just released on aminet a few days ago:

http://aminet.net/search?query=qboot

I have no idea if it works, but might be worth a try

Thanks, I'll probably give it a try, if I don't get any other responses, but will it work on PPC I wonder seeing as it's intended for 68k architecture.

I'm not sure the JIT will be active until much of the boot process has completed, anyway I don't suppose it would do much harm, but if it means putting it into the MorphOS folder, in the System partition, then I might not bother, as that folder is supposed not to be tampered with.

You may try "tco" to open the trace console and "ts" to start tracing on early startup.

Stefan

the easiest way is to add

set echo on

as first line in your user-startup.

This will show any launched command. Once the rexx message is shown, you should be able to find the tool triggered the requester, as it should be the last command shown on screen.

Geit

Thanks for the suggestions as to try to work out what is going wrong, but here is what I got by way of either the Trace Console or by "set echo on" (though I don't think this worked) as when I warm re-booted after amending my user-startup I got no output window of any sort from "set echo on" as the 1st active line in my user-startup script.

After trying the TCO/TS approach I got the message
Quote:
Which still didn't seem to point to a specific script, etc. as far as I could tell, but I then realised as the trace output was generated further that my initial suspicions about it being CRABUM were correct.

In the end, it ws basically all my own fault, as I lhad left a BACKUP of my menu script file for CRABUM in the WBStartup folder, and not put it in the DISABLED folder in there in case I needed it in the future.

So you guys thanks for pointing me in the right direction to use the tools available to figure out what was going on.

I've remarked (;) the "set echo on" and the "TCO" and "TS" lines in my user-startup file, but left them in there in case I need them in the future.

I really appreciate your help, and can only apologise for my own mistake that caused it in the first place, but at least I've learned a little bit more about MorphOS, and how it works - so there has been some benefit to me, and hope my tale has some bonus for you all - even if it is a much smaller benefit, than I received from this mistake of my own causing.