First impressions of 4.1 Update 1

[Karlos]

I downloaded the ISO yesterday and intended to install it today. However, reading through the early responses over at aw.net since then I've been a bit put off.

On top of the issues mentioned here, it seems a few other things don't work as expected. Some inbuilt shell commands don't behave as they should. For example

Set foo ""'

This assigns the empty string to local var $foo in earlier versions, but fails on 4.1U1

If ?

This displays the template for the 'If' keyword when entered in a shell in earlier versions, then fails (as it's only valid within a script), but apparently fails immediately in the update.

TBH, I really don't see what the WBStartup thing was about. One of the best things about the existing system was it's sheer simplicity. I can understand that perhaps people don't want to drag stuff there and forget where it came from if they ever wanted to put it back or disable it, but there are surely other ways to deal with that (tooltypes to mark as disabled and where a tool was dragged from might have sufficed, for example).

As for not running scripts, that's not good for me. I use a few ARexx scripts to extend my Workbench with various shortcuts that I've been using since OS3.5 and still use in 4.1.

[Karlos]

If anybody is interested, I installed it on my A1 XE and posted my initial reaction here.

[Karlos]

"doesn't support the execution of scripts"

No? Not here. All scripts are executed. No difference between old WBStartup drawer and new WBStartupPrefs. What are you doing wrong?

It works fine for me, provided the scripts have a proper icon with the associated default tool.

[Karlos]

What default tool did you use? I thought I couldn't get anything going with RX, but it's been a few weeks since I tried and I may not be remembering correctly (and I've since gone back to the "classic" WBStartup methodology, so it's not a big deal).

For AmigaDOS scripts, C:IconX. For ARexx scripts, C:Rx

It used to be the case that the Rx command was in SYS:Rexxc, which doesn't appear to exist any more. Check your path to the executable, mine was still pointing at SYS:Rexxc/Rx at first.

[Karlos]

Well, that should also work.

All the commands in old SYS:Rexxc are reentrant and marked pure, so they can be resident, either manually or by setting the h-flag, why people insist on accessing disk all the time is beyond me.

If you call the same command twice the chances are that the command will be in disk-cache memory anyway so it makes little sense to make it resident. Especially if it is used a couple of times during startup only.