AROS World Exec
Development => Development (General) => Topic started by: deadwood on July 10, 2022, 02:22:13 AM
-
Hello,
This is a thread created to discuss developments of Scalos for AROS x86 ABIv0, AROS x86_64 ABIv11 and AROS m68k. There will be a separate thread created later for AxRuntime version of Scalos.
Here you can find builds for all 3 mentioned platform: https://axrt.org/development/scalos-builds-20220710.zip
In the package you will not only find Scalos itself, but also additional components that need to be updated as well as default configuration files. Please update those components AND the configuration files.
Changes:
- Code base for all 3 targets has been synchronized and is identical. Any difference in behavior between them should as of now be due to Scalos bugs specific to a given platform or to a lesser extend differences in platform themselves.
- Preference programs have been fixed to at least load and save preferences without crashing.
Note: There were no other fixes made. Things, for example relating to PNG icons, should still be broken.
What I would like to focus on right now is the operations of Preferences programs. Please report any bugs you see there. You can also report other new bugs, but I won't be looking into them right now.
How to report bugs (IMPORTANT):
You might have your own configurations and setup of Scalos already working and you might want to just update them. This has already caused arguments in the past and unnecessary frictions because we were comparing different software versions and different configurations.
In order to avoid that this time, if you spot a bug, you MUST repeat the bug using clean system integrated with full release from scalos-builds.zip (that is also using configuration files from this release as starting point). I won't be accepting bug reports that cannot be reproduced on such setup.
For ABIv0, use this release as base: https://www.axrt.org/download/aros/v0/AROS-20190416-2-linux-i386-system.tar.bz2, alternatively https://www.axrt.org/download/aros/v0/AROS-20190416-2-mingw32-i386-system.tar.bz2
For ABIv11, use this release as base: https://www.axrt.org/download/aros/v11/AROS-20220318-1-linux-x86_64-system.tar.bz2
Once you repeat a bug in such setup, describe steps to trigger it - what should I click where to get to a bug. Screenshots or videos welcomed.
Have fun and let's get Scalos in better shape :)
-
with Windows hosted in the system generated folders (def_Drawer) you cannot enter, if you click nothing happens, this happens only if you run with Scalos.
Also if you do a "SnapShot" to an Icon strange things happen, the Disk System don't open anymore, the "SnapShot" from the Scalos Menu doesn't work, from the Wander Menu it works but some times the Ixcona will be corrupted.
For the test I used "AROS-20190416-2-mingw32-i386-system.tar" copied the Scalos in SYS folder and assigned the path SYS:Scalos
-
For the test I used "AROS-20190416-2-mingw32-i386-system.tar" copied the Scalos in SYS folder and assigned the path SYS:Scalos
Clarification from my side: Copy exactly the structure as it is in the build_scalos directory, so Scalos should be in Extras/Scalos. Don't add any assigns or change any paths.
Also don't change anything in Startup-Sequence, this means booting to Wanderer and then starting Scalos.
-
with Windows hosted in the system generated folders (def_Drawer) you cannot enter, if you click nothing happens, this happens only if you run with Scalos.
Please check on linux-hosted as well. It should be easy to install Linux into VM and then test linux-hosted.
I just tried on linux-hosted (20190416-2) and I can enter C directory for example. Also icons for def_Drawer drawer display the same for me (low color) as for drawers with icons, where in your case they look different.
-
The same thing also happens on Native AROS (your latest ISO) + Scalos, without Scalos no problem !
Mine have a different look because I had tried on AROS 68k to resave the icon as Icon Drawer
-
Snapshot works for me and I only use the newst builds from this thread
-
The same thing also happens on Native AROS (your latest ISO) + Scalos, without Scalos no problem !
Mine have a different look because I had tried on AROS 68k to resave the icon as Icon Drawer
It is more complicated to me. I copied all the files in the appropriate position and not just one assign to one directory. Also I start LoadWB from Scalos to start Scalos
-
@AMIGASYSTEM
Try linux-hosted please. Unzip the base system. Unzip scalos_builds. Copy directories in scalos_builds/x86/AROS/ to AROS-20190416-2-linux-i386-system combining with existing directories there and overwriting existing files where needed.
See screenshot, it works on such setup.
-
on Win Hosted X86 I have the same problem if I use "Show all" the directories are shown but I cannot open them (like C)
-
The same thing also happens on Native AROS (your latest ISO) + Scalos, without Scalos no problem !
Mine have a different look because I had tried on AROS 68k to resave the icon as Icon Drawer
Looking at the screen shot, you have 2 partition system with Extras being on Work: as well as Scalos in located in SYS. Any of those differences compared to requested test setup can introduce a problem.
-
on Win Hosted X86 I have the same problem if I use "Show all" the directories are shown but I cannot open them (like C)
Works for me as intended. See attached screenshot. Note however that this is using Wine - I don't have other means of running Windows-hosted. I'll remove WinHosted as base since we can't get same results.
-
with Windows hosted in the system generated folders (def_Drawer) you cannot enter, if you click nothing happens, this happens only if you run with Scalos.
I am unable to confirm this behaviour on linux hosted x86-64, version 20220318-1, clean install, only scalos added as instructed.
-
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
-
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 have to report an old problem with Scalos Prefs that still persists, basically if from the FileTypes Menu you ask for a "ResetToDefault", all the FileTypes are assigned, but then if you try to save the "FileTypes" they are not saved
-
@AMIGASYSTEM
I understand.
-
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?)
-
@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.
-
@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
-
@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 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.
-
@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 :-\
-
@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?
-
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 :P Bye
-
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
-
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.
-
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
-
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.
-
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
-
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!)
-
Scalos Prefs Guru Menu !
-
@AMIGASYSTEM
1) Which icon did you try to Leave Out?
2) What are the steps to reproduce the software failure in Preferences (starting from a clean unzip of AROS-20190416-2-mingw32-i386-system-integrated.tar)?
-
Dovrebbe farlo con tutte le icone, ho creato un video che mostra i due Guru (Save Menu e Leave Out?)
https://drive.google.com/file/d/16cpCgFz_8dKR54N0eD85Dzy2QZGidcTH/view?usp=sharing
Ho provato a spostare l'icona "Screemode" da Prefs con "Leave Out" con il menu nativo Scalos e anche in questo caso ho ottenuto un Guru, vedi screenshot
-
Ok, Thanks. I reproduced both bugs on linux hosted as well.
-
theoretical put out works (file is put out after reboot). Put back works correctly
-
Ok, Thanks. I reproduced both bugs on linux hosted as well.
To be more precise, in the menu to generate the Guru and when you add the "User-defined Button" item, basically these buttons do not exist and therefore cannot save something that does not exist.
I would add instead that the Guru appears "on all items" if you try to delete any, reverse drag and drop
-
I add if you hadn't noticed on my previous Screenshot that DualPNG icons are always cut by Scalos ! on Wander they are pefect, while Scalos cuts them.
(https://ae.amigalife.org/index.php?action=dlattach;topic=947.0;attach=3238;image)
-
To be more precise, in the menu to generate the Guru and when you add the "User-defined Button" item, basically these buttons do not exist and therefore cannot save something that does not exist.
I would add instead that the Guru appears "on all items" if you try to delete any, reverse drag and drop
Actually when you drag&drop User-defined Button, you then need to select command from the drop down list (bottom of window). If you select, it saves, if not, it crashes.
-
I add if you hadn't noticed on my previous Screenshot that DualPNG icons are always cut by Scalos ! on Wander they are pefect, while Scalos cuts them.
I know, you reported that previously. :)
The fixes done for this version were only in Preferences programs as mentioned in first post.
-
There also seems to be a graphical problem, buttons sometimes do not appear or show up badly, same thing for backgrounds.
-
@OlafS3: glad you got it worked out now
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."
I am aware that there is no need when it comes to Scalos itself.
The need to do so arises from the fact that deadwood request us to do so.
That way the errors as reported can be consistently reproduced. If you go ahead and use your own custom setup then it could be you are able to produce bugs that are not able to replicated by other users (unless they match the exact same setup as yours).
So, instead of being stubborn and install things my own way (even if it works as your screenshots show) , i follow the instructions as requested by deadwood ;)
-
Sorry to continue with my 68 year old stubbornness :), in my opinion, nothing should change if all the assignments are correct, the bugs i reported were almost always confirmed by deadwood.
Then in any case for confirmation I also do the counter test even with Scalos installed on Extras, if you watch the video I attached above where I reported the bugs, Scalos it is installed in SYS:Extras, as recommended by deadwood..
Also consider that the Extras folder on AROS, depending on the choice you make on InstallAROS, could then be in DH1:Extras and thus would not work, unless you make the change I made on AROS One after the report that deadwood made to me.
In my opinion it is right to keep all the Scalos files in the "Scalos" Folder to prevent some homonymous file from overwriting some other file with the same name.
-
@deadwood:
Not sure if this falls into your selected category of reporting...
i386 linux hosted
Steps to reproduce:
- Start Scalos as instructed
- Menu/Drawers/scalos prefs/scalos_prefs
- from list on left: text windows
- then on the tabpage fonts
- Press Use TT TextWindow Font
- Press dropdown
- Crash
Crashlog:
[KRN] Protecting host process stack (0xffee4430 - 0xffeee430)
[X11] BitMap class @ 0xe88ca6e4
*** Could not create object of Urltext.mcc
*** Couldn't find Urltext.mcc
UpdateWorkbench("NewPopupMenu.prefs", LOCK e89c0b90, 0x00000001)
Scalos_Prefs: MUI Notification loop detected! (#0)
Source object: 0xe9cd5afc Dest object: 0xe9d1f04c
Attribute: 0x8042654b Value: 0x1
Scalos_Prefs: MUI Notification loop detected! (#1)
Source object: 0xe9cd5afc Dest object: 0xe9d1f04c
Attribute: 0x8042654b Value: 0x0
Scalos_Prefs: MUI Notification loop detected! (#2)
Source object: 0xe9cd5afc Dest object: 0xe9d1f04c
Attribute: 0x8042654b Value: 0x1
[KRN] Trap signal 11, SysBase e88881e0, KernelBase e8888f44
SP=e96bae20 FP=e96bb0c8 PC=e96da71a
R0=ffffffbc R1=e8e1518a R2=e96bb260 R3=e96da6f9
R4=00000000 R5=e89a2fc0
*** Logged alert:
Program failed
Task : 0xE9600600 - Scalos_Prefs
Error: 0x80000002 - Hardware bus fault/address error
PC : 0xE96DA71A
Module Scalos_Prefs Segment 1 .text (0xE96D790D) Offset 0x00002E0D
Function TextWindowTtfPopOpenHookFunc (0xE96DA6F9) Offset 0x00000021
CPU context:
EAX=0xFFFFFFBC EBX=0xE8E1518A ECX=0xE96BB260 EDX=0xE96DA6F9
ESI=0xE89A2FC0 EDI=0x00000000 ESP=0xE96BAE20 EBP=0xE96BB0C8
EIP=0xE96DA71A ESP=0xE96BAE20 EFLAGS=0x00010293
Stack trace:
0xE971AA71 Scalos_Prefs Function HookEntry + 0x00000024
0xE8E421B5 muimaster.library Segment 1 .text + 0x000475B5
0xE8E42D0D muimaster.library Function Notify__MUIM_CallHook + 0x0000003C
0xE8E434C1 muimaster.library Function Notify_Dispatcher + 0x000001F6
0xE8E151B8 muimaster.library Function metaDispatcher + 0x0000002E
0xE8E22883 muimaster.library Function Area_Dispatcher + 0x000006DA
0xE8E151B8 muimaster.library Function metaDispatcher + 0x0000002E
0xE8E34E92 muimaster.library Function Group_Dispatcher + 0x0000074E
0xE8E151B8 muimaster.library Function metaDispatcher + 0x0000002E
0xE8E463E5 muimaster.library Function Popstring_Dispatcher + 0x0000018F
@AMIGASYSTEM: you do you, and i do as instructed. No need to argue about it ;D
-
@deadwood
The buttons on native AROS x86 are perfect, see screenshot, so the problem was only on AROS Hosted Windows
I suspect that the problem on AROS Hosted Windows is due to the Graphics Card
-
@OlafS3: glad you got it worked out now
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."
I am aware that there is no need when it comes to Scalos itself.
The need to do so arises from the fact that deadwood request us to do so.
That way the errors as reported can be consistently reproduced. If you go ahead and use your own custom setup then it could be you are able to produce bugs that are not able to replicated by other users (unless they match the exact same setup as yours).
So, instead of being stubborn and install things my own way (even if it works as your screenshots show) , i follow the instructions as requested by deadwood ;)
+1
for testing and reporting we should have standardized platforms to make it reproduceable. I for example used Scalos as full replacement, installed it elsewhere and mixed it with original files. After that a lot of worked and I had a lot of discussions with Amigasystem who did it different. :). To have a step by step standardized way to create the test environment or use the same archive is more efficient in my view. It will be interesting to see what happens if it is installed elsewhere or used as full replacement and started directly but first the current bugs should be fixed.
-
In my opinion besides testing following deadwood's directions is correct, but testing other ways is also important because it might uncover other bugs, this has taught me my experience.
Olaf, moving a drawer does not imply the operation, I also did a direct boot of Scalos "without moving or or add anything" without Wanderer and found no difference, same operation same bugs.
@deadwood
I confirm the bug reported by magorium on both Native AROS and Hosted Windows
-
@magorium
Thanks for the report
-
@AMIGASYSTEM
Think about it this way: every minute I spend trying to figure out differences in people's configurations is a minute I do not spend on actually fixing problems.
You are right, Scalos should work with different setups. According to me, with the amount of existing problems, it is still more efficient to use a standardized configuration to spot and solve them. I'd like to ask that if you report a problem you also mention whether you were able to reproduce it on standardized configuration - that's all.
-
@Deadwood
+1
Otherwise only unproductive and in worst case emotional discussions start that nobody help. Testing it step by step
-
Sorry deadwood maybe my English is not understandable, I do the tests as you may have noticed "first" with your configuration, and then for confirmation, and on my behalf, i test them "also" with all my configurations, this is to have a broader view.
-
Sorry deadwood maybe my English is not understandable, I do the tests as you may have noticed "first" with your configuration, and then for confirmation, and on my behalf, i test them "also" with all my configurations, this is to have a broader view.
Now it is clear - thank you.
-
@deadwood:
Again not sure if this is what falls into your category.
i386-linux hosted
I list the first crash because it might perhaps helps but i can't reproduce that all the time.
The steps i took to invoke the crash:
- menu/scalos prefs
- Scalos_prefs
- From the list I select every item (top to bottom) and watch the tab page appear
- in between I resized the window, one time
- then end up at the list: Filetypes
- Press def_project button on the right with left mouse button
crash-log:
[Bootstrap] Entering kernel at 0xe77af000...
[KRN] Protecting host process stack (0xffd90ef0 - 0xffd9aef0)
[X11] BitMap class @ 0xe890f6e4
*** Could not create object of Urltext.mcc
*** Couldn't find Urltext.mcc
UpdateWorkbench("NewPopupMenu.prefs", LOCK e8a05d90, 0x00000001)
[KRN] Trap signal 11, SysBase e88cd1e0, KernelBase e88cdf44
SP=ea197918 FP=ea197918 PC=e8a378c6
R0=ea1437b0 R1=ea158808 R2=e88cd1e0 R3=00000000
R4=ea156f5c R5=ea197ba4
*** Logged alert:
Program failed
Task : 0xEA142800 - DiskInfo
Error: 0x80000002 - Hardware bus fault/address error
PC : 0xE8A378C6
Module stdc.library Segment 1 .text (0xE8A105E0) Offset 0x000272E6
Function strlen (0xE8A378C0) Offset 0x00000006
CPU context:
EAX=0xEA1437B0 EBX=0xEA158808 ECX=0xE88CD1E0 EDX=0x00000000
ESI=0xEA197BA4 EDI=0xEA156F5C ESP=0xEA197918 EBP=0xEA197918
EIP=0xE8A378C6 ESP=0xEA197918 EFLAGS=0x00010282
Stack trace:
0xEA18AA93 DiskInfo Function DiskInfo__OM_NEW + 0x000015F3
0xE8E5A1B8 muimaster.library Function metaDispatcher + 0x0000002E
0xE7870950 intuition.library Function Intuition_106_NewObjectA + 0x00000070
0xEA18C409 DiskInfo Function main + 0x000000F9
0xEA188FDD DiskInfo Segment 1 .text + 0x000000CD
0xEA18B98F DiskInfo Segment 1 .text + 0x00002A7F
0xEA18BF3B DiskInfo Segment 1 .text + 0x0000302B
0xEA18BFD2 DiskInfo Segment 1 .text + 0x000030C2
0xEA18C046 DiskInfo Segment 1 .text + 0x00003136
0xEA18C1F6 DiskInfo Segment 1 .text + 0x000032E6
However, when starting afresh and:
- menu/scalos prefs
- Scalos_prefs
- From leftside list directly select: Filetypes
- Press def_project button with left mouse button
crashlog:
[KRN] Protecting host process stack (0xffeadb10 - 0xffeb7b10)
[X11] BitMap class @ 0xe89626e4
*** Could not create object of Urltext.mcc
*** Couldn't find Urltext.mcc
UpdateWorkbench("NewPopupMenu.prefs", LOCK e8a58b10, 0x00000001)
[KRN] Trap signal 11, SysBase e89201e0, KernelBase e8920f44
SP=e89fbf90 FP=e89fc008 PC=e7828c19
R0=e7807bb8 R1=ea11cc58 R2=00000001 R3=00000000
R4=e89e7610 R5=00000014
[KRN] Trap signal 11, SysBase e89201e0, KernelBase e8920f44
SP=e897559c FP=e8975664 PC=e8d56003
R0=00090007 R1=00000000 R2=00000000 R3=ea11cf60
R4=e89756ec R5=00000019
[KRN] Trap signal 11, SysBase e89201e0, KernelBase e8920f44
SP=e8974b40 FP=e8974bc8 PC=e789d1d7
R0=e8974b98 R1=ea11e890 R2=000000c0 R3=00000041
R4=e94f6190 R5=e8964180
################################################################################
# Software Failure! #
# Task : 0xE89695A0 - input.device #
# Error: 0x80000002 - Hardware bus fault/address error #
################################################################################
PC : 0xE8D56003
Module Decoration Segment 1 .text (0xE8D52590) Offset 0x00003A73
CPU context:
EAX=0x00090007 EBX=0x00000000 ECX=0x00000000 EDX=0xEA11CF60
ESI=0x00000019 EDI=0xE89756EC ESP=0xE897559C EBP=0xE8975664
EIP=0xE8D56003 ESP=0xE897559C EFLAGS=0x00010293
Stack trace:
0xE78E47BC intuition.library Function SysIClass__IM_DRAW + 0x000007EC
0xE78C17DB intuition.library Function Intuition_103_DrawImageState + 0x0000033B
0xE78CE92E intuition.library Function ButtonGClass__GM_RENDER + 0x0000011E
0xE78DEAD2 intuition.library Function Custom_DoMethodA + 0x00000042
0xE78C0FC6 intuition.library Function Intuition_135_DoGadgetMethodA + 0x00000206
0xE78CE5EC intuition.library Function RefreshBoopsiGadget + 0x0000003C
0xE78C9A75 intuition.library Function int_refreshglist + 0x000000A5
0xE78C9D13 intuition.library Function int_RefreshWindowFrame + 0x00000153
0xE78BDA68 intuition.library Segment 1 .text + 0x00003748
0xE78E122D intuition.library Function DoASyncAction + 0x0000010D
################################################################################
ObtainSemaphore called in supervisor mode!!!
sem = 0xe89fcc58 task = 0xe89695a0 (input.device)
ReleaseSemaphore called in supervisor mode!!!
sem = 0xe89fcc58 task = 0xe89695a0 (input.device)
ObtainSemaphore called in supervisor mode!!!
sem = 0xea11dc60 task = 0xe89695a0 (input.device)
ObtainSemaphore called in supervisor mode!!!
sem = 0xe89fcc58 task = 0xe89695a0 (input.device)
ReleaseSemaphore called in supervisor mode!!!
sem = 0xe89fcc58 task = 0xe89695a0 (input.device)
ObtainSemaphoreShared called in supervisor mode!!!
sem = 0xe89643dc task = 0xe89695a0 (input.device)
And that repeats itself indefinitely.
edit: the last item with reproduction steps, always seem to cause another type of crash. Sometimes it reboots AROS, sometimes it gets stuck (no pres more log possible) but it always crashes one way or another for me.
Also (but i probably need to take a picture for that) the same preferences window show some widget at the top right directly next to the tab-header text (upper header with name of the selected item from the list) for certain pages (i believe 3 or 4 specific pages). It has a up-down widget and what seems to be a very tiny part of a slider (as if the header text does not fit inside it's (parent) area.).
-
EDIT:
You can delete your posts about my help, thank you:
I was able to create an executable script to run AROSBootstrap.
-
@deadwood
Even on Linux Hosted the Buttons are corrupted or missing, so "only" on AROS x86 Native they work fine
-
@all
Not to be negative, but on AROS we already have Magellan, which is open source and much more advanced/configurable feature-wise than ScalOS. It would be a GREAT desktop replacement/file manager for any modern operating system, if it only was zunified and had a graphic overhaul.
-
Yes true, although for me Wandeer being native if improved would be the best choice, both Scalos and Magellan will always clash with Wanderer and there will always be small conflicts.
-
@all
Not to be negative, but on AROS we already have Magellan, which is open source and much more advanced/configurable feature-wise than ScalOS. It would be a GREAT desktop replacement/file manager for any modern operating system, if it only was zunified and had a graphic overhaul.
it cannot be zunified because it implements its own system (what has both advantages and disadvantages). Regarding porting it to Linux we should before ask gpsoft if they are ok with it. It was permitted to port it to amiga platforms but if it would be ported to Linux it would be first time available on a mainstream platform. Officially commercial they only support Windows so perhaps they are ok with it but it should be asked.
Other than that I like (as known) Magellan. It is very powerful and extremely configurable. But Scalos also has advantages. It is in some areas even more configurable and it is more doing it "the amiga way" whereas Magellan often is a kind of blackbox replacing many system routines. For many hardcore amigans Scalos propably is more appealing. Wanderer is more or less a 3.1 replacement (concept and functionality).
-
@deadwood:
As promised some pictures.
i386-linux hosted
The first picture shows the gadget in the tab header.
It is present for me on the following tabs:
- truetype fonts
- menu
- pattern
- popup menu
- palette
- filetypes
The second picture also shows a gadget that does not seem to belong and that is on the misc tab, vertical middle, right side.
-
@deadwood
Even on Linux Hosted the Buttons are corrupted or missing, so "only" on AROS x86 Native they work fine
Thanks. Noted.
-
@deadwood:
As promised some pictures.
i386-linux hosted
The first picture shows the gadget in the tab header.
It is present for me on the following tabs:
- truetype fonts
- menu
- pattern
- popup menu
- palette
- filetypes
The second picture also shows a gadget that does not seem to belong and that is on the misc tab, vertical middle, right side.
Thanks for the report and screen shots.
-
I have to report an old problem with Scalos Prefs that still persists, basically if from the FileTypes Menu you ask for a "ResetToDefault", all the FileTypes are assigned, but then if you try to save the "FileTypes" they are not saved
-
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
Sorry what themes are you talking about, I on Windows Hosted have no problem, see screenshot "standard configuration by deadwood with Scalos in Extras"
-
@deadwood:
As an observation regarding the preferences testing.
Every time you/i change a setting and save it, scalos "re-starts" itself loading the new configuration. While doing so it detects that intuition has window(s) open (probably wanderer as i closed everything else ?) and asks to close them. Each time i press the retry button scalos closes itself (well, sort of) leaving behind an empty workbench screen. Depending on some settings a part of the scalos screen/window is visible on the wanderer window/screen.
The fact that the graphics is garbled and drawn to the wrong location is not an issue (i can understand there are still glitches there, so not important) but more annoying is the fact that scalos is 'stuck' and can't be closed. So a reboot of AROS is required.
That makes it very tiresome to check/test each individual setting, especially since that is what you asked us to verify :)
Just telling in case you aren't aware of that fact (at least fact for me) and in case that should not be the default behaviour.
-
@deadwood:
As an observation regarding the preferences testing.
Every time you/i change a setting and save it, scalos "re-starts" itself loading the new configuration. While doing so it detects that intuition has window(s) open (probably wanderer as i closed everything else ?) and asks to close them. Each time i press the retry button scalos closes itself (well, sort of) leaving behind an empty workbench screen. Depending on some settings a part of the scalos screen/window is visible on the wanderer window/screen.
The fact that the graphics is garbled and drawn to the wrong location is not an issue (i can understand there are still glitches there, so not important) but more annoying is the fact that scalos is 'stuck' and can't be closed. So a reboot of AROS is required.
That makes it very tiresome to check/test each individual setting, especially since that is what you asked us to verify :)
Just telling in case you aren't aware of that fact (at least fact for me) and in case that should not be the default behaviour.
You can use Scalos also as WB-Replacemtn what might lead to different results
-
You can use Scalos also as WB-Replacemtn what might lead to different results
Equal does not change anything, although avii Scalos WB-Replacement will always behave the same (tested)
-
@deadwood:
As an observation regarding the preferences testing.
Every time you/i change a setting and save it, scalos "re-starts" itself loading the new configuration. While doing so it detects that intuition has window(s) open (probably wanderer as i closed everything else ?) and asks to close them. Each time i press the retry button scalos closes itself (well, sort of) leaving behind an empty workbench screen. Depending on some settings a part of the scalos screen/window is visible on the wanderer window/screen.
The fact that the graphics is garbled and drawn to the wrong location is not an issue (i can understand there are still glitches there, so not important) but more annoying is the fact that scalos is 'stuck' and can't be closed. So a reboot of AROS is required.
That makes it very tiresome to check/test each individual setting, especially since that is what you asked us to verify :)
Just telling in case you aren't aware of that fact (at least fact for me) and in case that should not be the default behaviour.
Yes I noticed that, but it does not happen all the time for me. I start Scalos from a left out icon on Wanderer desktop, so I don't have any windows opened (apart from Wanderer itself). Configuration reloads correctly (that is Scalos is not left at blank screen ) most of the times. If this happens more frequent for you, maybe you can see if there is any pattern that triggers this.
In general this is a gray area I think: these things could happen as long as Scalos is secondary to Wanderer, but should not happen when Scalos is main desktop.
-
In general this is a gray area I think: these things could happen as long as Scalos is secondary to Wanderer, but should not happen when Scalos is main desktop.
deadwood, if I understand the problem correctly, the gray screen appears even when starting Scalos directly.
I made a small video on AROS Hosted Windows, I will do the test also on native and linux hosted.
This could probably depend on some Aros preference, which apparently cannot be disabled
In the system in the startup-sequence Wandere disabled !
https://drive.google.com/file/d/1bU2-UmeCtNAzJARjmEyKLR4bJdD1O7od/view?usp=sharing
EDIT:
The gray screen disappears if from the startup-sequence you also disable iPrefs, it still remains a small background refresh
-
It's a bit different issue. On you video the gray screen is shown for while but then Scalos window opens and everything is good. In case magorium is desribing (I think) the Scalos screen openes but Scalos window never opens so user gets stuck on empty Scalos screen.
-
Okay I answered based on what I understood, however by disabled iPrefs the gray you saw in the video is no longer there, I also noticed that Scalos when you save to Scalos prefs generates a file named "NewPopupMenu.prefs" in the path "Prefs/Env-Archive/SYS".
-
I always started LoadWB from Scalos:Tools that started Scalos as WB Replacement
-
Natural, you have to start LoadWB native Scalos and disable Wanderer if you want to start Scalos directly, although the Wanderer preferences will always be used, this is why I was saying that Magellan and Scalos will always have the Wanderer skeleton behind their backs.
Example if you disable iPrefs, you will no longer have the gray screen problem in the save, but you will also no longer have the Pointer prefs that is managed by iPrefs
-
I'll respond to many replies, in first place to deadwood later to others (i omitted to quote the exact message id here as there where too many)
Yes I noticed that, but it does not happen all the time for me.
Strange as it seems to happen continuously for me now.
In that case i must have triggered something to cause this (for me) permanent behaviour. Ofc it disappears when starting completely afresh.
I start Scalos from a left out icon on Wanderer desktop, so I don't have any windows opened (apart from Wanderer itself).
OK, i can try that as well as i haven't before. Thank you for the hint. I start scalos as instructed (extra's) then switch back to Wanderer to close the open windows and head back over to scalos. Perhaps that in itself is already enough for scalos/intuition to get confused (although that usually works for me in other/normal situations with Wanderer/Magellan but ofc i do not use scalos as replacement).
If this happens more frequent for you, maybe you can see if there is any pattern that triggers this.
Indeed. I do have a hunch but it is still vague e.g. can't find the exact steps to force it yet as it seems to involve changing different settings in a particular order.
In general this is a gray area I think: these things could happen as long as Scalos is secondary to Wanderer, but should not happen when Scalos is main desktop.
That i have understood from the get-goal.
Also for OlafS3/AMIGASYSTEM:
I am aware that mileage may vary when using scalos as desktop replacement although i do appreciate the hint you guys made.
It was more about the way how scalos acts. For some settings it absolutely makes no sense whatsoever for scalos to re-start, and certainly not in the way it seem to do for me.
In case magorium is desribing (I think) the Scalos screen openes but Scalos window never opens so user gets stuck on empty Scalos screen.
That is affirmative.
The grey workbench screen stays visible and scalos fails to (re)load, although it appears that scalos is making an attempt to load because of the graphical glitches on the Wanderer screen.
There is no debug output that provides helpful information on what goes wrong there.
I also noticed that Scalos when you save to Scalos prefs generates a file named "NewPopupMenu.prefs" in the path "Prefs/Env-Archive/SYS".
That is correct.
If you look at the debug-log (you know: that open terminal window ;-) ) then you can see that this prefs file is being created/written to when saving the preferences.
-
Quick question:
Looking at Scalo_Prefs/Windows/Control Bar there seems to be two ways window behave: 1) double-click on directory opens a new directory window (standard), 2) double-click on directory opens this directory in same window (browser; has control bar at top by default). The default is "standard" view. I don't seem to be able to find an option to change the default to "browser" or even open a directory window in browser mode. However I saw screenshots of @AMIGASYSTEM where browser mode was used. How do you open a directory window in "browser" mode?
-
@deadwood: Delayed answer ;)
Instructions for i386-linux (because it is buggy for me)
- start scalos, then when on desktop
- move mouse pointer to a drive-icon
- right-click on the icon, scalos popup-menu appears
- select properties
- windows opens where you can set properties
- checkmark browser-mode
- press save button
That doesn't change anything for my setup, so i continue with
- close scalos -> crash -> reboot
- start scalos again
- open drive icon, note that browser mode is now activated
Also it seems that doing this that scalos also overwrites my earlier made/created settings with regards to browser buttons.
You can change that also for individual folder-icons, e.g. when you do not have the drive icon set as browser but wish to have a particular directory icon 'change' into browser mode: same procedural steps, only another icon.
-
Thanks - I would not have figured it out. It seems it is somewhat broken though, the toolbar appears, but still opening a drawer opens a new window. Added to my list.
-
Hi All,
Here is a new set of builds, with many fixes, see below. Please follow the same steps integrating with clean releases and updating system components found in the zip. Please do not use your previous .prefs files - there were many bugs related to loading/saving them so they will not work correctly with these executables. Also not that Scalos_Prefs and FileTypes_Prefs need 64kb stack or you will experience random crashes. Happy testing and let me know of outstanding issues.
https://axrt.org/development/scalos-builds-20220721.zip
Fixed:
- Numerous crashes when working on 64-bit with 64-bit heap
- Wrong background color of Scalos logo on Scalos splash window
- Backgroung image of Scalos splash window and Scalos About window is not visible
- Icon labels on desktop and in drawer windows are displayed using Topaz instead of Arial font
- Font.prefs are not being loaded on 64-bit
- Font.prefs are being wrongly saved on 64-bit
- scalos.prefs are not being loaded on x86 and x86_64, scalos is using always default prefecens
- scalos.prefs are being saved on x86 nad x86_64 in format not compatible with m68k
- NewPopupmenu.prefs is wrongly written
- Plugins are not loading at Scalos startup
- wbrexx.plugin is crashing at startup on 64-bit
- Multiple controls missing on Scalos Prefs/Icons page
- System crash when clicking on def icon image on FileTypes Prefs/Recognition page
- Status bar, control bar, buttons sometimes don't have images displayed
- Buttons in Scalos About window have white corneres rendered where they should be transparent
- Crash when leaving out an icon
- Crash when adding a User-defined Button to Control bar without setting it's properties in Scalos Prefs
- Crash when removing any button from Control bar in Scalos Prefs
- Scalos Prefs allows editing TTEngine font properties when TTEngine is not present causing crash in Icons/Labels and Text Windows/Fonts pages
- deficons.prefs are not being loaded on x86 and x86_64
- Reset to default in FileType Prefs and Save does not save prefrences
Won't fix:
- Scroolbars visible on titles of TrueType Fonts, PopupMenu, Menu, FileTypes, Pallette and Pattern pages of Scalos Preferences
Not fixed:
- Wrong rendering on DualPNG icons
- Refreshing drawer windows is slow
- Starting Prefs/Locale or Prefs/Input from Scalos causes other preferences to fail
- Desktop wallpaper is damaged where Splay window was displayed
- When started from Wanderer, after saving Scalos Prefs, reload does not re-open main Scalos window
- Difference in behavior between Cleanup from popup menu and Cleanup from top menu - https://drive.google.com/file/d/1p-SWoWvuZFk8DxwDW5Q6NVFrY7Rjsc8n/view?usp=sharing - possibly due to missing plugin, check Cleanup association in Menu Prefs
- Scalos sees icons of some executables as project instead of tool - example MPlayer
-
Scalos has improved greatly, the buttons now look good even the backgrounds i edited look good.
Only problem encountered at the moment, is that after saving with Scalos Prefs, you are prompted to close applications, what ? there are no applications open ! after saving the screen stays grey !
-
Only problem encountered at the moment, is that after saving with Scalos Prefs, you are prompted to close applications, what ? there are no applications open ! after saving the screen stays grey !
See my reply #62 :)
I still have to verify if it is always reproducible but for me it now seems to crash when attempting to close scalos. If it is then i'll post the crashlog.
-
See my reply #62 :)
Yes I had read it, I had also replied that with the previous version of Scalos, I did not have the gray screen, but only a small flash of gray screen, which could be eliminated altogether by disabling "iPrefs" from the startup-sequence, see my reply #66/68
I confirm the crash if you exit Scalos, it doesn't always happen, it definitely happens if you use some part of Scalos prefs.
The crash also happens if you try to exit Wanderer, again it does not happen all the time !
-
Scalos has improved greatly, the buttons now look good even the backgrounds i edited look good.
Glad to hear that
Only problem encountered at the moment, is that after saving with Scalos Prefs, you are prompted to close applications, what ? there are no applications open ! after saving the screen stays grey !
Added to open issues list
-
Tested Scalos also on AROS One x86, again Scalos improved greatly, no difference from clean AROS.
About icons there is always the problem that Scalos "from its menu" can't fix icons automatically, you have to do it from Wanderer
"Browser Mode" on individual Volumes now works well, but you have to reboot the system to see the change !
-
About icons there is always the problem that Scalos "from its menu" can't fix icons automatically, you have to do it from Wanderer
What do you mean by that? What is "fix"?
-
I do not understand that either... just tested it and snapshot works
tested with the official win hosted version from Deadwood
Great now f.e. thumbnails prefs are there
I have also just updated my aros vision scalos 68k. Looks good. Prefs are working, no freezes anymore. And f.e. Thumbnails dialog is now visible in prefs
-
What do you mean by that? What is "fix"?
Is a problem that I had also reported in previous versions of Scalos, I made a small exhaustive video, used your basic version of AROS hosted Linux
https://drive.google.com/file/d/1p-SWoWvuZFk8DxwDW5Q6NVFrY7Rjsc8n/view?usp=sharing
-
this menu entry is:
plugins/menu/sorted_cleanup.plugin
-
I now know why it not works... the plugin does not exist
-
this menu entry is:
plugins/menu/sorted_cleanup.plugin
What do you refer to?
-
I have also just updated my aros vision scalos 68k. Looks good. Prefs are working, no freezes anymore. And f.e. Thumbnails dialog is now visible in prefs
Thanks for testing 68k version as well. I'm only testing x86 and x86_64 versions so it is good to know things work well also on m68k.
-
if you open scalos prefs and then menu you can edit the menu.
Amigasystem used "Cleanup"... if you look at it, it uses a plugin
Scalos:Plugins/Menu/Sorted_Cleanup.plugin
if you look in the files it does not exist
-
Is a problem that I had also reported in previous versions of Scalos, I made a small exhaustive video, used your basic version of AROS hosted Linux
https://drive.google.com/file/d/1p-SWoWvuZFk8DxwDW5Q6NVFrY7Rjsc8n/view?usp=sharing
I'll added investigating this to the list.
-
if you open scalos prefs and then menu you can edit the menu.
Amigasystem used "Cleanup"... if you look at it, it uses a plugin
Scalos:Plugins/Menu/Sorted_Cleanup.plugin
if you look in the files it does not exist
Ok, now I understand. Thanks for the hint!
-
Is a problem that I had also reported in previous versions of Scalos, I made a small exhaustive video, used your basic version of AROS hosted Linux
https://drive.google.com/file/d/1p-SWoWvuZFk8DxwDW5Q6NVFrY7Rjsc8n/view?usp=sharing
I'll added investigating this to the list.
That is what I was referring to.... the menu does not work because plugin does not exist
-
one I have found... you cannot leaveout a directory without attached icon
Tested on Win Hosted
-
one I have found... you cannot leaveout a directory without attached icon
Tested on Win Hosted
If i understand the problem correctly, this is normal, you can't make a shortcut on an icon that doesn't exist, this also happens on all OS3, except the new OS 3.2
-
ah ok... but would be handy...
-
Solution:
With Menu Scalos:
- Right Mouse Button on Icon
- Properties.
- Save
Or
With Menu Wanderer:
- Right Mouse Button on Icon
- Icon Information
- Save
Now the folder/file icon becomes real and you can safely make the connection
-
if you open scalos prefs and then menu you can edit the menu.
Amigasystem used "Cleanup"... if you look at it, it uses a plugin
Scalos:Plugins/Menu/Sorted_Cleanup.plugin
if you look in the files it does not exist
Ok, now I understand. Thanks for the hint!
The sources of the PlugIn Cleanup can be found HERE (https://aros.sourceforge.io/nightly.php) in contrib-source
-
Started Scalos on AROS One x86 directly by disabling Wander loading, this was used to test some particular applications that used a Wanderer Screen.
Successfully tested Dopus4 which after setting it to Scalos Screen, started without problems, also BoingIconBar opened without problems on a Scalos Screen, also created Scalos DualPNG Icons in AROS One style.
Tonight I will also test the operation of AmiStart and the various Themes settings for both BoingIconBar and AmiStart.
I also noticed on the PNG icons that some Wandere "Tool" icons on Scalos are seen as "Project" icons, I don't know if this is an AROS problem since I produce DualPNG icons on OS3 AfA Os.
It's not a problem though, once you change the Scalos side icon, Wander will also display them correctly the same way :)
-
I also noticed on the PNG icons that some Wandere "Tool" icons on Scalos are seen as "Project" icons, I don't know if this is an AROS problem since I produce DualPNG icons on OS3 AfA Os.
It's not a problem though, once you change the Scalos side icon, Wander will also display them correctly the same way :)
I thought it was a problem only on my DualPNG icons, but no, the problem is also on native AROS Icons.
Basically, an Icon of an Executable (Tools), Scalos sees it as if it were a "data file" and assigns a "Project Icon", even though in the menu it is correctly set as Tools, see exhaustive screenshot.
In practice programs such as MPlayer on Scalos will work badly, practically if MPlayer is run from Icon, MPlayer will not show the GUI, it will work as if run from CLI without any parameters
-
Basically, an Icon of an Executable (Tools), Scalos sees it as if it were a "data file" and assigns a "Project Icon", even though in the menu it is correctly set as Tools, see exhaustive screenshot.
In practice programs such as MPlayer on Scalos will work badly, practically if MPlayer is run from Icon, MPlayer will not show the GUI, it will work as if run from CLI without any parameters
Added to the bug list.
-
On AROS 68k the problem seems not to be there, OS3 native executables, but also AROS native "ELF" executables are displayed correctly as "Tools"
-
@deadwood
Also AmiStart works well with Scalos on-screen Scalos "if started without Wanderer", now to have a big improvement it lacks compatibility with DualPNG icons, I noticed on "AROS One" that if you go deep into the folders, at some point the window background doesn't load and the window freezes and can't be closed anymore.
This I don't know if it depends on the PNG Icons, with your standard version and the native AROS icons this doesn't seem to happen.
(https://ae.amigalife.org/index.php?action=dlattach;topic=774.0;attach=3355;image)
-
This I don't know if it depends on the PNG Icons, with your standard version and the native AROS icons this doesn't seem to happen.
If you can "modify" the reference version in a way to trigger this problem, I'm interested in looking into it.
-
With the reference version I have not encountered any problems, the problem is only present on AROS One on some folders full of DualPNG icons, when you do the swap between Size/Icon visualization see screenshot.
-
With the reference version I have not encountered any problems, the problem is only present on AROS One on some folders full of DualPNG icons, when you do the swap between Size/Icon visualization see screenshot.
Maybe it depends on how the PNG Icons are being loaded & displayed. Scalos originally worked with Classic Amiga Icons.
The Scalos code for loading & displaying icons is interesting.
@deadwood I'm glad that you have decided to fix some of the issues with Scalos. It seems very promising especially for 64bit. But using it as an alternative to Magellan or Wanderer on x86 is also useful. A few years ago in the ABIv1 group we looked at Scalos briefly for use on 64bit. But there were so many small issues it was put on hold.
Great to see some progress.
-
@miker1264
Indeed there was a number of small issues all around (like papercuts) but gradually those will be fixed away :)
-
I think I found something....
In menu you can create menu options you get by right-click
predefined is for example "Amiga+E" to open "execute dialog": This seems not to work on both 68k and Win Hosted X86
The menu works but not the shortcut pressing the keys
-
@miker1264
Indeed there was a number of small issues all around (like papercuts) but gradually those will be fixed away :)
yes great that Deadwood fixes it :) it could become a great desktop on all supported platforms including linux
-
New Teme "Blue" for Scalos ;)
-
looks good :)
-
I am just trying to replicate menu of amigaos and it is possible 1:1 including shortcuts (if they work of course :D ). I think with Scalos it is possible to really build up something that looks & feel like many amiga users expect
The preferences are really stable now, no freeze even after longer time. Thank you Deadwood
Another thing I see...
if you select a icon and rightclick you get mainmenu and all perfect (even shown themed). But if you directly rightclick on a icon you get a different menu that is shown not themed and I do not find a option to edit it. Window popup menu can be edited (the same for mainmenu and desktop) but not icon.
Test done on Aros 68k
-
New Teme "Blue" for Scalos ;)
Looks really good!
-
I am just trying to replicate menu of amigaos and it is possible 1:1 including shortcuts (if they work of course :D ). I think with Scalos it is possible to really build up something that looks & feel like many amiga users expect
The preferences are really stable now, no freeze even after longer time. Thank you Deadwood
Glad it's working for you.
Another thing I see...
if you select a icon and rightclick you get mainmenu and all perfect (even shown themed). But if you directly rightclick on a icon you get a different menu that is shown not themed and I do not find a option to edit it. Window popup menu can be edited (the same for mainmenu and desktop) but not icon.
Test done on Aros 68k
I think you need to "unhide obsolete menu entries". See screenshot.
-
@Deadwood
thanks that did it :)
only small idea... I have to activate the menus every time because they are hidden again even after saving. Would be nice if that would be saved too
-
I have found a new feature unknown to me 8)
In Scalos-Prefs->Filetype->Recognition you can define the filetypes and on "Action" you define specific context menu for all filetypes defined in recognition (similar to magellan)
there is the same you must show all first (list is only limited)
there is only problem I do not how. If I create a new entry in Recognition it is shown as "new" but I cannot edit the name "new"
and how do I define what def icon is connected? To me it looks like something is still missing there
-
@OlafS3
Scalos_Prefs->Filetype doesn't work well
Scalos_Filetype->doesn't work well
@Deadwood
Scalos_Filetype-> Does not save "Reset To Default"
Scalos-Prefs/Menu Filetype-> Does not save "Reset To Default" and also destroys all other settings. basically resets "all prefs" to default
-
@Deadwood
Scalos_Filetype-> Does not save "Reset To Default"
Scalos-Prefs/Menu Filetype-> Does not save "Reset To Default" and also destroys all other settings. basically resets "all prefs" to default
On which architecture you tested this?
-
I was testing the AROS One v1.8, now I will test your standard hosted Linux and Windows version, and let you know
-
@Deadwood
weird... it works on 68k now. Seems to be related to where the new entry is created
also icons are automatically attached by "def_NAME"
I did not found a option to individually do it like on magellan
-
On which architecture you tested this?
Done testing with reference ISO, AROS Hosted linux:
Scalos-Prefs/Menu Filetype->save "Reset To Default", no problem
Scalos-Prefs/Menu Filetype-> save "Reset To Default" and also destroys palette preferences (after reboot), Wallpapers, but I think it resets other things too !
See video:
https://drive.google.com/file/d/1M5OqNq7oJqGfpCU22BrTG7Jjd5dZ_5XS/view?usp=sharing
-
also icons are automatically attached by "def_NAME"
If I remember code correctly this is how it works. If you crated a file type AAABBB, you need to have def_AAABBB icon.
-
On which architecture you tested this?
Done testing with reference ISO, AROS Hosted linux:
Scalos-Prefs/Menu Filetype->save "Reset To Default", no problem
Scalos-Prefs/Menu Filetype-> save "Reset To Default" and also destroys palette preferences (after reboot), Wallpapers, but I think it resets other things too !
See video:
https://drive.google.com/file/d/1M5OqNq7oJqGfpCU22BrTG7Jjd5dZ_5XS/view?usp=sharing
Also AROS One v1.8 behaves the same as the reference ISO AROS Hosted linux
On AROS One v1.8 I had forgotten to update some system files included in "scalos-builds-20220721".
The problem remains that ScalOS Prefs save "Filetype/Reset To Default" and also destroys palette preferences (after reboot), Wallpapers, but I think it resets other things too !
@OlafS3
As you can see from the screenshot, Scalos uses the Def_Icon by Wanderer, the ones that don't have a default icon is because it has to be created first on Scalos/Filetype and then the reference Def_Icon installed on Wanderer.
-
@deadwood
AROS Hosted Windows, it seems not that it cannot rename a file !
-
I can confirm that rename not works on hosted. On 68k it works
-
Associating files with "Scalos_FileTypes" is very simple, practically it is very similar to Dopus4, first you create the Def_icons to assign to the file type (will be seen automatically ), then run "Scalos_FileTypes" you add the extension, fill in the descriptor (MATCH or PATTERN etc..) and save, see screenshot.
The DualPNG Def_icons shown are not beautiful, Scalos_FileTypes distorted them :(
-
when I checked a original 68k Scalos installation and compared files with scalos on aros it seems some are missing in "tools": CreateDefaultIcon, CreateTrash, NewIconUtil, OpenLocation, PictIcon
do not know what they are for
I also do not find the official Scalos help file that seems to exist. For example you can use "%p" as path to icons when using shell commands. Stuff like that is in that file. Somebody knows where to find it?
I found documentation... strange not in current downloads
https://aminet.net/package/util/wb/Scalos
older version but better than nothing
-
You anticipated me, in the attached link there are the tools CreateDefaultIcon, CreateTrash, NewIconUtil, OpenLocation, PictIcon, and also Scalos Guide and FileTypes Guide.
https://aminet.net/package/util/wb/Scalos
http://scalos.noname.fr/downloads.php#modules
-
With the reference ISO on Scalos Prefs, I tried activating the fields in the "True Type Fonts" menu, adding the "ttengine.library". Having done this, the fields in the fields in the "True Type Fonts" menu activated, but as soon as the request for the Scalos Prefs choice opens, it loops.
-
the "Scalos_FileTypes" application works fine with save "Reset To Default," but if a guru happens while configuring an association, it destroys the "deficon.prefs" configuration file that contained all previously associated FileTypes.
It basically destroyed all the video and audio associations I had created :D
-
With the reference ISO on Scalos Prefs, I tried activating the fields in the "True Type Fonts" menu, adding the "ttengine.library". Having done this, the fields in the fields in the "True Type Fonts" menu activated, but as soon as the request for the Scalos Prefs choice opens, it loops.
ttengine.library support was not tested at all and I won't be looking into it right now. What advantage does it give over regular fonts, which are also true type?
-
The problem remains that ScalOS Prefs save "Filetype/Reset To Default" and also destroys palette preferences (after reboot), Wallpapers, but I think it resets other things too !
Reset to Default in Scalos_Prefs resets all settings so I think it is correct that your wallpaper is changed back to default and any changes you made are reversed.
-
In my opinion it is not designed correctly, if I for example am on the True Type Font menu (see screenshot) and decide to reset fonts, Scalos cannot reset everything, or if it does it should give a warning.
This in my opinion will anger many users who may have taken a day to configure everything, as happened to me.
Regarding True Type Fonts the tick in the various menus is accepted and saved for me, the loop happens if I choose a fonts !
Actually after checking "True Type Font" in the various menus I don't notice any difference on Scalos.
Regarding the quality of the fonts, again in the screenshot you can see the difference between the font between Wanderer Vs Scalos
-
Some anomalies found:
AROS Linux and Windows Hosted:
- In Prefs folder "Boot" and "Trident" executables are missing, "only" the icons are present
ISO reference, on Scalos "Input" and "Local" Applications do not work, if run the system becomes very slow.
-
Some anomalies found:
AROS Linux and Windows Hosted:
- In Prefs folder "Boot" and "Trident" executables are missing, "only" the icons are present
Boot and Trident prefs have no function under hosted so they are not built. It would be better if icons were not copied, but AROS uses one icon configuration for all targets.
ISO reference, on Scalos "Input" and "Local" Applications do not work, if run the system becomes very slow.
Added to the list
-
@deadwood
Created a small video showing the crash on "Scalos_Filetype Prefs"
Basically if you try to create a new association and leave the "empty field" without any values, "Scalos_Filetype Prefs" generates a Guru.
On the other hand, if you enter values in the fields, nothing seems to happen or if it does it rarely does.
https://drive.google.com/file/d/1OBBDFu7jtIhSr0c7c9ISIS-WT4YgYzs6/view?usp=sharing
-
I asociated all types of Audio and Video Files on Scalos_FileType, only format that it seems you can't configureare is "M3U" ( Multimedia Playlist) files, the icon is detected but strangely Scalos doesn't associate it.
The icons don't look good because Scalos distorts them :o
On Wandere no problem the "M3U" files and any other extension can be associated, it is not a problem because you can assign a real icon like Windows does :D
-
Can the drop shadow effect be turned off or changed to a transparent value?
-
Can the drop shadow effect be turned off or changed to a transparent value?
As mentioned it is Scalos_Filetype that alters and modifies Icons, on Wanderer as you can see from this screenshot my icons have a very slight shadow effect.
-
short report about using filetypes... as already mentioned you need a def_ icon with the same name predefined
then you create a appropriate entry in the list and rename it, if def icon exists it is shown. Below you can define how files are identified. I use "pattern", similar to magellan to identify file by ending. Then you click on the shown icon and define in it what program is used when you double-klick on it and save it. On the tab action you can define popup menu for it. All in all handling is of course different to magellan but you can do similar. Very impressive.
-
I asociated all types of Audio and Video Files on Scalos_FileType, only format that it seems you can't configureare is "M3U" ( Multimedia Playlist) files, the icon is detected but strangely Scalos doesn't associate it.
The icons don't look good because Scalos distorts them :o
On Wandere no problem the "M3U" files and any other extension can be associated, it is not a problem because you can assign a real icon like Windows does :D
It looks like the icons are displayed as RGB rather than ARGB. So they lose Transparency of the Icon Shadow.
-
short report about using filetypes... as already mentioned you need a def_ icon with the same name predefined
Yes same default name, in my case on AROS One I used individual associations for individual video and audio formats (see screenshot icons), by default Wander associates all video or audio to the same icon, to have an icon for each type of extension you have to create datatype descriptors "by individual format"
then you create a appropriate entry in the list and rename it, if def icon exists it is shown. Below you can define how files are identified. I use "pattern", similar to magellan to identify file by ending.
Basically the procedure and values are always the same as Dopus4, Magellan, Deficons (OS3.9) etc..
In fact, I use the same AROS descriptors even on my OS3.9 systems, AfA OS, Amithlon etc..
-
It looks like the icons are displayed as RGB rather than ARGB. So they lose Transparency of the Icon Shadow.
Yes so it seems, if you look closely at the screenshot you will notice that the "Scalos_Filetype" GUI on the right shows the perfect def_icons, the "corrupted" icons Scalos shows them when from the menu you run "Show All Files".
-
miker, I would add that if the icon shown by "Show All Files "on Scalos is saved (right click properties), the icon is saved in the correct format, the icon becomes perfect again !
-
@deadwood
With ISO reference on Scalos MPlayer does not work well !
Basically if it is run it by Icon does not appear a GUI but a request, basically it does not execute the "GUI" command in the Icon tooltype
If run from a Shell with GUI paramenter it works perfectly, it also works fine if run from BoingIconBar
-
Associated on Scalos "File types," Archive, Document, and MS-DOS files for direct access to DOSBox
EDIT:
Separated the extensions to the .TAR, TAR.GZ archives, now they both have a specific icon
-
the help files I found included not much informations. Online there is not much either. Unfortunately it seems the project stopped and (like always) developers were not very interested in doing (boring) documentations. I am expecially interested to know about constants for using shell commands. The only one I found is "%p" (path to icon). Is somewhere more informations I am not aware of?
-
I cannot find on Scalos how to make the Native Menu "Gray" transparent (see screenshot).
On Scalos Prefs there seems to be nothing to change the background, maybe it's me who can't find it, any of you have any news about it ?
-
@Deadwood
Unfortunately there seem to be no documentation about Scalos. Perhaps you see the constants in source code. I found "%p" for path to icon but there must be more of that, f.e. path to directory. It is needed for many context menues
-
If it may be of interest on Scalos OS3 AfA OS version 41.7 Release 1.8, DualPNG Icons show up fine and there are no icon-cutting artifacts, also "ClenUP" and "Update" in Scalos Menu work fine :)
-
@deadwood
With ISO reference on Scalos MPlayer does not work well !
Basically if it is run it by Icon does not appear a GUI but a request, basically it does not execute the "GUI" command in the Icon tooltype
If run from a Shell with GUI paramenter it works perfectly, it also works fine if run from BoingIconBar
Added to the list
-
I cannot find on Scalos how to make the Native Menu "Gray" transparent (see screenshot).
On Scalos Prefs there seems to be nothing to change the background, maybe it's me who can't find it, any of you have any news about it ?
The menus are rendered by popupmenu.library - not part of Scalos but external project that Scalos uses. Maybe you can find a way looking for popupmenu.library documentation.
-
@Deadwood
Unfortunately there seem to be no documentation about Scalos. Perhaps you see the constants in source code. I found "%p" for path to icon but there must be more of that, f.e. path to directory. It is needed for many context menues
You have to describe better what are you looking for. Perchaps add screen shots? I'm not familar with functionality you are describing.
-
@Deadwood
Unfortunately there seem to be no documentation about Scalos. Perhaps you see the constants in source code. I found "%p" for path to icon but there must be more of that, f.e. path to directory. It is needed for many context menues
You have to describe better what are you looking for. Perchaps add screen shots? I'm not familar with functionality you are describing.
I have to guess but i think OlafS3 is referring to the runcomand parameters... in which case:
%p = parameters
%w = directory path
%d = device-name
%% = literal percentage token
In case that is not what OlafS3 meant then the question becomes with plugin/module is used ?
fwiw: I have only seen the use of %p in the (custom) menu's.
PS: info based on SF project source(s)
-
@magorium
Thanks for looking into that.
-
@magorium
Yes I meant that. I would like to use commands from C with parameters in menu so I need some placeholders for path to selected icon or similar. That is easy in magellan and I guessed something like that also exists in scalos. Unfortunately no documentation.
Typical what you need path to selected icon, path to directory where the file is. For that constants you can use.
It looks good what you wrote. Thanx. I will test it.
-
@magorium
Yes I meant that. I would like to use commands from C with parameters in menu so I need some placeholders for path to selected icon or similar. That is easy in magellan and I guessed something like that also exists in scalos. Unfortunately no documentation.
I'm sorry why don't you use WBRun which among other things also runs the Tooltypes in the icon ?
-
I would like to report that with AROS Native, reference ISO (AROS-20190416-2-pc-i386-boot-iso), on Scalos if you try to do "Information" from both menus (see screenshot), Information does not work and the system becomes very slow.
On AROS Hosted Linux no problem, this makes me think that some library present in AROS-20190416-2-pc-i386-boot-iso creates questio problem.
-
I also noticed that on AROS Hosted, peripherals USB and CD/DVD are not mounted automatically as on AROS Native and Virtual Machines.
On Linux/Windows Hosted AROS do you have to proceed like on OS3 with some Mountlist?
-
I'm sorry why don't you use WBRun which among other things also runs the Tooltypes in the icon ?
Because WBRun is not sufficient for /all/ circumstances. I did write wbxcli with a reason (*) ;)
(*) but to be honest, you can almost accomplish anything using tools like iconX or XIcon in case WBRun is not suffice.
-
I also noticed that on AROS Hosted, peripherals USB and CD/DVD are not mounted automatically as on AROS Native and Virtual Machines.
On Linux/Windows Hosted AROS do you have to proceed like on OS3 with some Mountlist?
Yes you have to add those manually.
For instance I use separate 'mountlists' for adding multiple host directories as it's own 'device'. Same for ISO files (although I usually use the host to access those).
More information about that is available on the wikibook in case you wonder how to do that. But feel free to ask in case you get stuck.
Important note: Be careful when playing around with with real host devices, as you can seriously screw things up if you want.
-
For instance I use separate 'mountlists' for adding multiple host directories as it's own 'device'. Same for ISO files (although I usually use the host to access those).
Mounting a CD/DVD should be simple just set up the right MountList, among other things you can use DiskImageGUI.
Riguarda USB sticks non go idea ho dato uno sguardo su wikibook e non ho trovato la mountlist, se hai una tipica mountlist già pronta mi semplificheresti le cose.
Important note: Be careful when playing around with with real host devices, as you can seriously screw things up if you want.
Here I think you are referring to any errors in parameters, I have mounted CDs thousands of times on my Amiga A4000, A1200 without ever having any problems, i also mounted a device that deletes data from CD/DVD "virtually"
-
Riguarda USB sticks non go idea ho dato uno sguardo su wikibook e non ho trovato la mountlist, se hai una tipica mountlist già pronta mi semplificheresti le cose.
A simple mountlist (https://en.wikibooks.org/wiki/Aros/Platforms/Installing_on_*nix#How_to_mount_some_device_or_directory_(for_example_a_dvd-drive)_as_a_drive_under_aros_hosted?) as shown on the wikibook.
For any other questions regarding off-topic discussions: open up another thread. Please stay on topic in this thread.
edit: fixed url.
-
I'm sorry why don't you use WBRun which among other things also runs the Tooltypes in the icon ?
Because WBRun is not sufficient for /all/ circumstances. I did write wbxcli with a reason (*) ;)
(*) but to be honest, you can almost accomplish anything using tools like iconX or XIcon in case WBRun is not suffice.
I had recommended WBRun, but your wbxcli would also be great, instead of "%p "reported by OlafS3
-
For any other questions regarding off-topic discussions: open up another thread. Please stay on topic in this thread.
Your link does not work you put a double "http", yes I open a thread because I want to understand Mountilist well, in my opinion I was not OT because to me mountlist was for "Scalos Hostes" direct boot without Wanderer !
-
Nice to see that Scalos makes a comeback. I had it ported to i386 many years ago but an attempt to port it to x86-64 broke both i386 and x86-64. I haven't read all messages in this thread. The sort menu plugin needs to be ported from ASM to C.
IIRC Scalos has a command line option to fully replace Workbench/Wanderer.
The Theme: assign is used by both Wanderer and Scalos but I didn't have problems to use both at the same time.
-
For any other questions regarding off-topic discussions: open up another thread. Please stay on topic in this thread.
Your link does not work you put a double "http",
Fixed now (if i have done it correctly). Thank you for reporting.
yes I open a thread because I want to understand Mountilist well, in my opinion I was not OT because to me mountlist was for "Scalos Hostes" direct boot without Wanderer !
Thank you for opening the separate thread.
It is off-topic because if you look closely to where this thread is located: it has nothing to do with the development of scalos.
Mountlists are something that AROS system does, not the WB (replacement). And although I can understand that you don't know the specifics with regards to the latter, it still has nothing to do with scalos development/bug reporting.
Who in his/her right mind is going to start searching on how to mount a device in AROS/AmigaOS in a thread named "scalos-general" in the subforum "development" ? Really, give that question a thought if even for a few seconds.
Because there is also a language barrier you/we/me tend to let such 'side-topics' to get out of hand pretty quick, and such side-topic becomes a whole discussion on its own and that does not belong here in this specific thread.
I'll refrain from commenting on such topics because out of respect for the developer (yet here I am posting something unrelated to the topic again :P ).
Please note that a developer (usually) gets notified each and every time we post something in a thread like this. In case we are too much off-topic a developer will becomes bored/annoyed about it and remove notifications and choose his/her own specific times to check the thread or even let such thread bleed out (=die) because of lost interest. At least that is how such things works on (other) development forums where there are literally 10000's of different topics and where posting unrelated remarks is frowned upon: it even gets you banned if you are doing such things too many times in a row).
More than happy to discuss this topic even further, but /not/ here in this thread (forum feedback comes to mind).
-
Nice to see that Scalos makes a comeback. I had it ported to i386 many years ago but an attempt to port it to x86-64 broke both i386 and x86-64. I haven't read all messages in this thread. The sort menu plugin needs to be ported from ASM to C.
Thank you for all the work you (and fella devs) did on porting scalos. Without it we wouldn't be in writing things in this thread ... uhm... make use scalos in AROS :)
-
magorium I made a small video showing AROS One x86 booting directly from Scalos (only disabled Wanderer from Startup-sequence).
As you will be able to see from the video (watch the whole thing), with Scalos now almost everything works fine, except windows with icons, sure Wanderer is much faster, however I must say that Scalos has improved npoteably
https://drive.google.com/file/d/1gGcQnQ9qrLwc4zE-1kWJtul2Bje0umJK/view?usp=sharing
-
perhaps someone can help me
I want f.e. define a context menu for adf file to mount it
on magellan this is easy: "mountdiskimage drive idf0: {f}"
{f} is a variable defined by magellan giving you the path to the selected file
how can I do the same in Scalos? Unfortunately there is no documentation, at least none I found
-
You can do the same command with Dops4, forward always from Dopus4 with the "xadUnFile" Command you can also "unpack" the ADF file to a folder in RAM (see screenshot), and all the files will be available in a folder with the same name as the ADF file.
Also from the Workbench there is also DiskImageGUI.
-
that is DOpus
but how can I do that just using Scalos? Any clue?
-
From Dopus4 it is convenient, but you can do Floppy ADF mounting also from Workbench "double click icon", to do this in Def_ADF.info you have to set either your "mountdiskimage" or "xadUnFile" Commands.
This is only possible if you use the "wbXcli" command of the bravo magorium :)
-
You can do the same things with DMS files as well.
If you want you can also create icons for the "Eject" DF0, DF1 etc.. either for Dopus4 or directly from the Workbench, I think you can also do it for CD/DVD and USB (not tested).
Of course you can do the same thing with DiskImageGUI.
-
it is working... you can add popupmenu on action that use cli commands with path to file or directory using constant %p
screenshot attached (now you can mount adf by rightclick)
Stack is always needed otherwise it not works
-
Scalos with mounted adf file using popup menu 8)
-
Much better Def_Icons, faster mounting/unmounting no popups, and most importantly works with both Scalos and Wanderer !
-
Scalos with mounted adf file using popup menu 8)
Nice :)
-
On Scalos you can also add an item in the "Popup" Menu (see screenshot), but it is an extra work, in my opinion just and simple double click on Icon is enough, practically nothing changes, the command for Mount ADF is always the same.
Then important thing that Def icon method works "also" from Wanderer while Scalos Menu will stop working on Wanderer.
-
@Amigasystem
That might be but I use context menues in my magellan distribution very extensively with many options and filetypes. I want to implement that also on Scalos. And flexibility also is important for future Linux distributions.
-
Yes of course, the menu can be useful in certain circumstances, for example to disassemble floppies, in this case you simplify the steps, and you can eliminate the second icon, see screnshot.
Of course, it also works with DMS floppy image files. :)
-
I like your optic... I always have the problem that I have no unique icon set because always icons are missing
Yes context menu are making a system much more useable even though much work for the distribution creator :)
-
I created those two PNG icons on the fly but in my opinion they use too large a size 24x24, now try to create them smaller 20x20, creating quality icons so small is very complicated, the smaller the image the more it deteriorates and loses quality, So you have to redesign pixel by pixel by hand.
-
Here 20x20 already are a little better (They are upside down, then I will fix them ;D)
-
nice ;)
-
I am currently trying to get the scalos distribution on the same level as magellan and it is possible
For example I just realized that you can define common context menu for a certain type of files.
In my example I defined all archive types from XAD in "filetypes". If you change to "action" and click on "archive" you can define the context menu that is shown if you do not define a specific context menu for a filetype. Very handy :)
-
Are you talking about AROS 68k or AROS x86 ?
-
I am using it currently on 68k. But it should be the same on X86
-
No XAD on x86 does not work well, you cannot turn an LHA,ZIP etc.. into a folder, also some archive formats are not supported. I have already reported this problem to deadwood.
-
ah ok
XAD I do not know. I only explained how you define common menu for a type of files, in this case archives. There are a number of types predefined.