Scalos - General

[deadwood]

@AMIGASYSTEM

I understand.

[OlafS3]

Deadwood I found the problems.... you must copy themes from scalos over themes in prefs/presets then it works in Win Hosted. I would prefer to use Win Hosted if possible

Ok, I understand. There can be a number of reasons why this is needed on Windows but not needed on Wine. Since I can't replicate Windows behavior, for the time being I will only accept problems reported on Linux-hosted. Once we are in better shape in general, we can look into specific problems of windows-hosted on Windows.

I still do not really understand how you did your installation working correctly without copying themes like I did,... I had the same problem when I installed it on 68k. Assign for themes is used for both aros and scalos and you said it is hardcoded in Scalos source. How is it possible that it works on Wine without workaround I used (copying files from scalos to the aros themes?)

[deadwood]

@All

Just to re-iterate, the improvements that happened in this version were around preferences programs. You should not be able to use the programs to load and save preferences including Menu13.prefs. In you run into issues with preferences programs please report them here.

[OlafS3]

@AMIGASYSTEM

I understand.

if you look at the screenshot from amigasystem it is obvious that it is the same as it was with me.... themes Scalos not recognized because colliding with aros theme assign... I solved it by copying the files to prefs/presets as workaround. I would bet that this also solves it now. You see it because when all works you have the screenshot like on yours, if all is grey then this is not correct

[OlafS3]

@All

Just to re-iterate, the improvements that happened in this version were around preferences programs. You should not be able to use the programs to load and save preferences including Menu13.prefs. In you run into issues with preferences programs please report them here.

I tested prefs on X86 before... much more stable than before. No issues when I tested them

[deadwood]

Deadwood I found the problems.... you must copy themes from scalos over themes in prefs/presets then it works in Win Hosted. I would prefer to use Win Hosted if possible

Ok, I understand. There can be a number of reasons why this is needed on Windows but not needed on Wine. Since I can't replicate Windows behavior, for the time being I will only accept problems reported on Linux-hosted. Once we are in better shape in general, we can look into specific problems of windows-hosted on Windows.

I still do not really understand how you did your installation working correctly without copying themes like I did,... I had the same problem when I installed it on 68k. Assign for themes is used for both aros and scalos and you said it is hardcoded in Scalos source. How is it possible that it works on Wine without workaround I used (copying files from scalos to the aros themes?)

I don't know. As you can see on the screenshots it works on both linux-hosted and windows-hosted under Wine. It might be something related to random memory being overwritten where different memory gets damaged on Linux, on Windows or in a VM. Eventually the problem will be found and solved - but not right now. All I can ask is that you all continue testing using linux-hosted.

[magorium]

@AMIGASYSTEM @OlafS3
I know it must be frustrating but i can confirm the behaviour as reported by deadwood for i386 linux and x86-64 linux hosted.


I extracted the AROS archives into their respective folders, extracted the content of the scalos archive to their corresponding aros directories, started aros, then scalos and it works out of the box 

[OlafS3]

@AMIGASYSTEM @OlafS3
I know it must be frustrating but i can confirm the behaviour as reported by deadwood for i386 linux and x86-64 linux hosted.


I extracted the AROS archives into their respective folders, extracted the content of the scalos archive to their corresponding aros directories, started aros, then scalos and it works out of the box 

What do you mean corresponding dirrectories regarding themes? Do you copy something or not?

[magorium]

What do you mean corresponding dirrectories regarding themes? Do you copy something or not?

Inside the scalos archive there are 3 directories, one for each platform (68k, i386, x86-64). directly underneath those directories (still in the archive) there are 4 directories. i copy those 4 directories out of the scalos-archive into the corresponding aros installation directory (i386, x86-64). Thus, classes, libs, extras and.. i forgot the name of the last directory, and all their subdirectories (we are still in the scalos-archive) to for example c:\aros-hosted\i386 (for i386) and to for example c:\aros-hosted\x86-64 (for x86-64).


But then ofc. for linux, so the example paths differ as i am on linux.


And now i am too late for an appointment  Bye

[OlafS3]

I have the impression we have a problem with installation and thus ending with different results. Perhaps f.e. Deadwood can exactly write step by step what he does so that we can follow it exactly

[deadwood]

I have the impression we have a problem with installation and thus ending with different results. Perhaps f.e. Deadwood can exactly write step by step what he does so that we can follow it exactly

First try my setup, which has Scalos integrated:
https://axrt.org/development/AROS-20190416-2-mingw32-i386-system-integrated.tar.bz2

Start AROS from command line. It will boot to Wanderer. Double click System. Select from top menu, Window->View->All files. Double-click Extras. Double click Scalos directory. Double-click Scalos program.

[OlafS3]

it works all correctly. No clue what I did wrong there. I used it as full replacement starting it directly. And I changed Scalos dir and not simply copied Extras. Thanks.

Snapshot, show all and opening directories work correctly

[deadwood]

Glad to hear that it is resolved. It might be that Scalos has some hardcodes at Extras/Scalos and when in this location works better than in other locations. It might be also that if Scalos is used instead of Wanderer it behaves differently. Or if it is started from Shell/Startup-Sequencec instead from Workbench it behaves differently. These things will also be solved in time.

Now the we know the "correct" procedure for now, we can focus on other things.

[AMIGASYSTEM]

What do you mean corresponding dirrectories regarding themes? Do you copy something or not?

Inside the scalos archive there are 3 directories, one for each platform (68k, i386, x86-64). directly underneath those directories (still in the archive) there are 4 directories. i copy those 4 directories out of the scalos-archive into the corresponding aros installation directory (i386, x86-64). Thus, classes, libs, extras and.. i forgot the name of the last directory, and all their subdirectories (we are still in the scalos-archive) to for example c:\aros-hosted\i386 (for i386) and to for example c:\aros-hosted\x86-64 (for x86-64).

There is no need to copy to the Root or copy Scalos to Extras, Scalos can be put wherever one wants, what is of interest is to assign the Scalos path, which "need not be done in user-startup or Startup-sequence."

As you can see from my Screnshot I copied the Scalos folder in SYS and both systems can be run, both Wanderer and Scalos and everything seems to work smoothly (to be tested)

The "AROS-20190416-2-mingw32-i386-system-integrated.tar" deadwood works fine because Scalos was assigned to SYS:Extras through the "Packages" preferences

[AMIGASYSTEM]

deadwood, for Bug finding I am using your ISO "AROS-20190416-2-mingw32-i386-system-integrated.tar"

Currently found these problems:

- Guru if you try to move an icon to the Workbench "Leave Out", see screenshot

- Guru if you try to save the Menu, see screenshot

(I attach second screenshot on next post for forum limitation 192 KB!)