OS4.1 Update 2 problems & solutions

"Update 1" and "Update 2" headings

There are two places where the system says "Update 1" and we want to change it to "Update 2":

1) The Workbench title. I believe that the Workbench prefs title string is only patched to say "Update 2" if it was unchanged from the original file, otherwise you'll have to change it yourself in Workbench prefs.

2) The heading in Kicklayout. Again, if the Kicklayout file is unchanged, the "Update 1" label will be changed to "Update 2", otherwise you'll have to change it yourself with Notepad or some other editor.

Note that when booting, SLB looks for the label in the Kicklayout file, named in the u-Boot variable "boot_config". If "boot_config" still says "Update 1", SLB will default to loading the first configuration in the kicklayout, which is probably "Update 2".

So, you'll still see "Update 1" on the boot screen and wonder why, even though the Kicklayout file has been changed to read "Update 2". To complete the update nicely, change "boot_config" to say "Update 2" (that can't be done easily by the installer script). You can use the command "nvsetvar boot_config xxxx".

@sundown

All righty

Thank you

Diskimage device still shows up in Media Toolbox, thought it was an easy fix, maybe forgotten? Was my understanding, that device was left off the imbedded skip list.

@sundown

imbedded? do you mean embedded?

@tonyw
Quote:
Does the installer make any other changes if you had an unchanged Kicklayout? Mine has several unused items commented out and I'm wondering if I am missing any Update2 changes as a result.

It looks like the textclip documentation was left out again. Fortunately I still have the docs from a previous release but it's a shame to get new features in OS4 that nobody will use becuse the docs are missing.

@xenic

The kicklayout file hasn't changed in update 2, apart from the reference to "Update 1", so if it is not updated, the only changes are informational.

There have been no functional changes to textclip-handler, so updated docs are not necessary.

Simon

@DaveP

Yah, embedded, I was told by a beta tester that Media Toolbox has a built-in list of devices to ignore & the diskimage device was not included in the update 1-2 build. This wasn't a problem with os4.1. You only see the problem if you install Diskimage_device, doesn't hurt, but shouldn't be there.

"Again, if the Kicklayout file is unchanged, the "Update 1" label will be changed to "Update 2", otherwise you'll have to change it yourself with Notepad or some other editor."

I don't remember changing my kicklayout, but I check the installation script.
Error was that the script check "AmigaOS_4.1_update_1" rather than "AmigaOS 4.1 update 1".

(ie : "_" rather than " " (space)).

@sundown

Quote:

Why shouldn't it "be there" and why is it "a problem"?? What if someone wants to create an RDB hardfile with diskimage.device? What program would you suggest him to do this with if not Media Toolbox?

@salass00

Your Diskimage device didn't show in Media Toobox with os4.1, it just magically showed up with update 1. Me & others thought this was a bug in Media Toobox, so I stand corrected, thanks.

Edit: Just looked at the icon tooltypes I realized I had set it to DEVICE=a1ide.device in os4.1. This was the reason I never saw the diskimage device option until os4.1 update 1. Getting old I guess...

@tonyw

Thanks for the info regarding labels. I've changed them accordingly just not to confuse others when I show them my system. Anyway I think this should be changed by the update itself. I know this is just a detail but still...

Anyway it's great to have another update so soon :)

@Dirk-B

I had issues with my screen going blank when moving windows, requesters opening etc and I still do if I'm using the DVI port.

It's been reported here:

http://amigaworld.net/modules/newbb/v ... _id=30503&forum=14#539933

The issue remains with update 2 even though it isn't as bad as in update 1 but bad enough to be unusable. I've tried the automatic settings as well setting them in the tooltype of the monitor file but it doesn't work.

Hoping for a solution for the next update.

@hotrod his message,

Ahum, can anybody give a comment, i have no knowledge of this.

@Rigo
Update1 moved the handlers to their own directory in SYS:Documentation and the con-handler documatation was placed in SYS:Documentation/Kickstart. The textclip-handler.doc file was in the the old SDK. Most of the handler docs were removed from the latest SDK autodocs because they appear in the OS4 user documentation. The textclip-handler.doc file was removed but does not appear in the OS4 user documentation.