Hyperion Entertainment Message Boards

@dstastny

Take a look here.
Maybe that explains your crashes?

Thank you Niels

Thank you for confirming

This could be (but not has to be) related to this bug

1) Get lha from here 2) Unpack 3) Type "lha ?" in a shell not high enough to trigger the "Press space to continue" 4) Click on shell window's close gadget It printed unwanted text after it got to the end. 21.System:> ;0;0;0;0;0;0;0| There is even an invisible "1" hidden...

shakenfr wrote: ↑Sat Apr 17, 2021 10:14 am hello,

thanks for your help @rigo @xray

I works now !!!

best

Bruno

Welcome then...have fun

@nbache Nothing ultimate here. But it works for me so far. It slows down WB boot a lot, compared to before, but at least I now *know* that the network is available and as I already wrote, it solved a bunch of boot problems i had...heck, even my cold boot with the case button works again. :-? I typed...

@@nbache Possible, yes. But right now I'd like to have a non-script solution through single line commands. I was rewriting the contextmenu commodities config file yesterday to use AISS images instead of the few that came with the program (finally all entries have Icons now). Unfortunately the progra...

@MikeSteed That would be a thing to test, thank you I have lots of stuff starting after the network *ought* to be up. Some personal AREXX scripts relying on working internet access. I wrote myself a script that checks to *really* make sure internet is available before starting the remaining scripts....

I know there is a rather enhanced WB AREXX port with quite a lot of actions. One in particular is bothering me since years now and i'd like to know if there is an option to turn it off or change it's behaviour otherwise, or maybe even enhance it's functionality? CM_INVOKEWB,WINDOW.NEWDRAWER Right-cl...

Thank you *very* much for this thread and description of the problem. I was scratching my head for a long time, trying to find out why my system randomly stalls during boot. I did everything to find out and came close to the date command, but never blamed it. My problem was, that i had a >NIL; after...