AROS World Exec
Development => Development (General) => Topic started by: deadwood on November 21, 2021, 12:52:28 PM
-
Hi,
As mentioned in another thread, I'm applying selected commits to my repository. Here is first build of the ROMs: https://axrt.org/development/aros-rom-20211121.zip
I held off for now specific changes to joystick and AGA - they will be included in next versions. Please test for know if these ROMs are "good enough".
Here is list of applied changes:
Marlon Beijer Sat Mar 20 16:15:03 2021 +0100 Fix Z includes
Marlon Beijer Sun Jan 31 14:48:25 2021 +0100 Solve issue where ADATE wasn't properly defined when compiling alib
Marlon Beijer Sun Mar 14 15:26:22 2021 +0100 429c26980abdc2e7b1af3cf4e4566f64c99620e9
Marlon Beijer Sun Mar 14 15:32:57 2021 +0100 429c26980abdc2e7b1af3cf4e4566f64c99620e9
Marlon Beijer Sat Feb 6 11:29:54 2021 +0100 Add VASM crosstool on m68k target
ronybeck Wed Mar 10 20:34:08 2021 +0100 Delete arch/m68k-amiga/hidd/sagasd directory
Ronnie Beck Fri Feb 26 15:57:09 2021 +0100 Moved the sagasd driver from hidd to dev
Ronnie Beck Mon Feb 22 21:54:36 2021 +0100 - Set nominal bit depth for the Amiga GFX driver to 2 bit. This ensures that booting without startup-sequence results in at least a 2 bit colour screen (before it was 1 bit which is horrible).
Ronnie Beck Sun Feb 14 12:53:22 2021 +0100 - New graphics modes for SAGA
Ronnie Beck Thu Jan 7 22:44:22 2021 +0100 - SD Card driver update to recognise RDB partitions - Theoretically it should make booting from SD Card possible if the filesystem is a standard file system but this is only partialy tested on AOS. - This is a WIP and based on the work of Alynna
Ronnie Beck Tue Dec 29 17:25:45 2020 +0100 Added SD Card driver modification from Alynna
Ronnie Beck Tue Dec 15 20:55:35 2020 +0100 Added new SAGA modes
Ronnie Beck Sun Dec 13 16:11:59 2020 +0100 - Updated scripts to compile without MMU support.
Ronnie Beck Sun Nov 8 23:11:21 2020 +0100 More experimental changes
Ronnie Beck Sat Aug 15 15:17:02 2020 +0200 Increase speed of PutPixel in AmigaVideo driver
Thomas Scheller Wed Aug 12 19:35:27 2020 +0200 Fix Workbook filter Icons and AllFiles
Ronnie Beck Thu Aug 6 22:58:21 2020 +0200 Fix that enables NTSC modes
Ronnie Beck Mon Aug 3 21:14:26 2020 +0200 Removed debug printf() from sagagfx
Ronnie Beck Sun Aug 2 16:19:27 2020 +0200 New SAGAGFX Driver from Flype. This supports the new V4 graphics architecture. LORES is still half height/width and a TODO.
Ronnie Beck Fri Jul 31 22:05:28 2020 +0200 BigGun's save/restore register fixes. Should fix some AMMX applications that suffered.
Ronnie Beck Sat Jul 25 19:31:16 2020 +0200 Added AMMX register patch
Ronnie Beck Fri Jul 17 19:17:36 2020 +0200 Alternate fix for Early Boot on NTSC. Buttons should be correctly placed
Ronnie Beck Thu May 7 21:43:28 2020 +0200 Added short delay after re-enabling interrupts
Ronnie Beck Sat Jul 11 15:59:55 2020 +0200 Small correction to P96
Ronnie Beck Sat May 9 17:58:14 2020 +0200 Changes from Flype so that a single SAGA driver can work both on a V2 and a V4
Ronnie Beck Sat May 9 13:01:28 2020 +0200 Fix to stop debug output from being printed when debugging is not active
Ronnie Beck Fri May 8 01:15:29 2020 +0200 First working SAGA driver for the V2
Michal Schulz Mon Mar 9 20:16:11 2020 +0100 Send a handshake and set CIA serial in input mode during keyboard initialization. This helps against keyboard missing after reset.
Michal Schulz Tue Feb 25 00:16:54 2020 +0100 typo fixed
-
Tested your ROMs with the latest "Nightly build" and on WinUAE they don't work well, the Wanderer volume is requested, tried to rename the volume Wanderer but then it doesn't start the Wanderer command, from the prompt no command works, not even the DIR command.
I hope they are not Vampire-only Roms, otherwise they can't be used for standard AROS 68k anymore!
-
You can only take over selected commits (f.e. bugfixes) not the whole rom. As I understand it they have changed it to a degree that it no longer works with UAE. ApolloOS still boots with normal roms so you can propably use Aros 68k with the roms but only on vampire.
-
@AMIGASYSTEM
No, they are "generic" 68k roms. I only applied certain commits that are not Vampire specific.
Looks like something went bad with my ROMs. I'll see what's the problem and post new version of ROMs in coming days.
-
Yes nothing works, I deleted the FixFont from the Startup-sequence, or even started the system from "AROS Early Startup Control" and from the propmt no command works, surely something is corrupted or missing !
Moreover, the Wanderer folder is located in SYS:\System\Wanderer
Instead it is searched in SYS:Wanderer or more precisely in Wanderer:Wanderer
-
@AMIGASYSTEM
No, they are "generic" 68k roms. I only applied certain commits that are not Vampire specific.
Looks like something went bad with my ROMs. I'll see what's the problem and post new version of ROMs in coming days.
Ah OK I understood something wrong. Thanks for your help
-
@AMIGASYSTEM, OlafS3
Can you tell me if you take these system files and attached ROM if they boot for you?
https://sourceforge.net/projects/aros/files/nightly2/20211017/Binaries/AROS-20211017-amiga-m68k-boot-iso.zip/download
-
Aros Vision boots with the roms
-
and the nightly also boots
-
Hmm, I'm using FS-UAE with A4000 template and all I get booting the linked nightly is black screen with some white stripes from time to time. :/
-
I use WinUAE
all boots OK
-
What CPU do you have set in WinUAE and do you use JIT?
-
68020 and yes JIT
Config attached
-
BTW, I tried downloading AROS Vision (aros_2020_Basis_UAE.7z) twice and each time I get "unexpected end of archive" error under Mint 20 when trying to decompress.
-
I used 7-zip to pack it
first time I am informed about problems to unpack it
-
It might be something related to 7z available on linux systems (might too old)
7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
-
These are the most important options, AROS 68k on WinUAE with a Dual-Core PC boots in 5 seconds.
Better to use WinUAE, FS-UAE is based on an old 3.x version of WinUAE so many new things are missing.
WinUAE: Config
If you need I can send you my WinUAE config
- CPU 060 (you can also use 020/040, the speed doesn't change)
- FPU enabled
- FAST RAM 256, you can also use 8MB ChipRAM
- JIT enabled
- Video Card UAE Zorro III 256 MB RAM
- Add the two news ROMs (WinUAE built-in ROMs are obsolete)
On FS-UAE I don't remember if the two ROMs have to be merged into one file
I merge the ROMs for Amilator and Janus-UAE, creating a single 1MB ROM.
-
BTW, I tried downloading AROS Vision (aros_2020_Basis_UAE.7z) twice and each time I get "unexpected end of archive" error under Mint 20 when trying to decompress.
Tried WinRAR, no problem unpacking!
-
also 7-zip is great
-
deadwood I enclose a small video that shows the configuration and the startup of AROS One 68k on WiNUAE, if you need I can send you in private my HardFile of my distribution AROS One 68k "at the moment not distributed" + the WinUAE configuration file
AROS One 68k on WinUAE Video Tutorial:
https://drive.google.com/file/d/1eq6ELK16JOqmB5WSAHnLV0DgH_0mruq1/view
-
So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading.
Can you make available for me your distribution?
Ok, I've been able to repeat the problem using an emergency.adf. Nightly indeed boots to Workbook, while my ROM stops. I'll continue invastigating.
-
thanks
-
So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading. Can you make available for me your distribution?
Ok, I've been able to repeat the problem using an emergency.adf. Nightly indeed boots to Workbook, while my ROM stops. I'll continue invastigating.
I have no problem booting 17.10 nightly
OK time to send it on Google Driver and I send you my Distribution and WinUAE config in PM.
Using the Filesystem Directory doesn't change anything, I prefer to use HardFiles SFS formatted to keep all the files together for a better management.
In My Distribution you will find only "some" libraries renamed and replaced with OS3 libraries, this is so that some native Amiga Applications could work, see ModExplorer, AmiModRadio etc...
If you need it I can also create a HardFile with only 17.10 nightly native "standard".
-
So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading.
You have problems because he didn't do the right configuration, check the WinUAE config data posted above! Also I suggest you to use a window instead of full screen and change the resolution to 1024x768 or bigger if you have a big monitor.
This way you can drag volumes, folders or files from the Desktopo to Wanderer.
-
deadwood
Workbook is experimental. I believe Ronney Beck was working on it.
I believe Nightlies should boot to Wanderer. But I could be wrong.
My AROS (Plain) Vanilla is based on Nightlies. It has a custom backround and WBDock and a Workspace Test Directory.
I'll setup a new version based on the latest Nightly 68k files. :)
-
So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading.
You have problems because he didn't do the right configuration, check the WinUAE config data posted above! Also I suggest you to use a window instead of full screen and change the resolution to 1024x768 or bigger if you have a big monitor.
This way you can drag volumes, folders or files from the Desktopo to Wanderer.
At this point I think the FS-UAE disk support is somehow not compatible with AROS. It used to work though - this is how I was testing. Using an emergency.adf works around this problem.
-
I think so, this morning I tried to boot FS-UAE from Amilator (Linux distribution that uses FS-UAE) and I got an error on the Cooprocessor, see screenshot, I reported the problem on EAB
Now I tried again on WinUAE the 17.10 nightly and it started perfectly, see small video attached
https://drive.google.com/file/d/1iIce-veOEYgOu0AqYl9jFcQg6VnWRvRQ/view?usp=sharing
-
Strange the Cooprocessor error because always on FS-UAE "Amilator" AfA One works perfectly (same requirement and same configuration used for AROS One), see my old video !
https://www.youtube.com/watch?v=b5XaU77f8eg
https://www.youtube.com/watch?v=0mqJtNg3KKs
-
Now I tried again on WinUAE the 17.10 nightly and it started perfectly, see small video attached
Yes. I use WinUAE for testing the 68k builds. It also has debug if you start it with -log -serlog parameters. It also starts and closes quickly and VMWare can copy/paste directly to the directories.
So I prefer using WinUAE with AROS directories hosted on Windows rather than hdf files.
-
I know how to make logs and other operations on WinUAE, I usually use them when I report problems on WinUAE to Toni Wilen.
Directory Filesystems in some cases are not good, there are native Amiga or AROS files or folders that use special characters will not be handled by windows.
Try to create unnamed folders or files (only spaces) or folders or files with the character ???
Windows will show these folders with the name "__uae__".
EDIT:
Do you mean copy/paste on VMWare Emulation "Windows"? It doesn't work VMWare Emulation AROS x86.
-
I know how to make logs and other operations on WinUAE, I usually use them when I report problems on WinUAE to Toni Wilen.
I didn't know about copy/paste on VMWare, can you explain me how to do it? A little video would be better to understand it
Directory Filesystems in some cases are not good, there are native Amiga or AROS files or folders that use special characters will not be handled by windows.
Try to create unnamed folders or files (only spaces) or folders or files with the character ???
Windows will show these folders with the name "__uae__".
VMWare Workstation Player 15 running Ubuntu 16.04 can Copy/Paste from Linux to Windows 10 and from Windows to Linux. It's very convenient.
-
@deadwood
I set up my AROS Vanilla based on Latest 68k Nightly Build.
With the ROMs from the Nightly it boots nicely in WinUAE.
But not with the ROMs provided earlier in this thread.
-
you mean the roms deadwood first published? Yes there is a problem with it
-
VMWare Workstation Player 15 running Ubuntu 16.04 can Copy/Paste from Linux to Windows 10 and from Windows to Linux. It's very convenient.
Yes my old VMwarerPlayer does it too, there is also the possibility to create a Shared Folder or a Network Drive, but with AROS x86 this feature is not supported.
To share WMWare and WinUAE (HardFile), I use external USB HD, MemoryCard or PenDrivers which are fast to share Wandere with Workbench via WinUAE.
-
But not with the ROMs provided earlier in this thread.
As mentioned those ROMs are corrupted FixFont and Wanderer are searched in the wrong places also no command works, try to go in the "AROS Early Startup Control" hold down the two keys Mouse in AROS startup, from the prompt nothing works !!!
-
Strange the Cooprocessor error because always on FS-UAE "Amilator" AfA One works perfectly (same requirement and same configuration used for AROS One), see my old video !
https://www.youtube.com/watch?v=b5XaU77f8eg
https://www.youtube.com/watch?v=0mqJtNg3KKs
Which version of FS-UAE are you running? I'm using 3.0.2
-
Amilator should include version 2.8.4, today I'll install version 3.0.5 and do some tests !
http://eab.abime.net/showthread.php?t=91638&highlight=amilator
-
FYI, it looks like FS-UAE "directory as disk" works, but it is super slow. I don't know yet if this is FS-UAE problem or my ROM is even more damaged.
-
I have installed the updated version of Amilator with FS-UAE 3.0.5, see link, and I get the same error as the Cooprocessor with AROS One 68k, now I will try with FS-UAE 3.0.5 Windows version.
http://eab.abime.net/showpost.php?p=1403596&postcount=104
Anyway it should not be slow, on WinUAE it starts in 5 seconds despite I have an old Dual-Core "with a good video card".
If you use Linux you could try WinUAE with Wine, eventually I'll pass you my config, you just have to change the paths of ROM, Hardfile or Directory System
-
FYI, it looks like FS-UAE "directory as disk" works, but it is super slow. I don't know yet if this is FS-UAE problem or my ROM is even more damaged.
I had used the roms from the archive you posted and it booted in normal speed
-
@AMIGASYSTEM, OlafS3
Can you tell me if you take these system files and attached ROM if they boot for you?
https://sourceforge.net/projects/aros/files/nightly2/20211017/Binaries/AROS-20211017-amiga-m68k-boot-iso.zip/download
Sorry I didn't read this post, the ISO you attached boots perfectly on WinuAE with old ROMs, with your new ROMs you always have the same errors Wanderer, Fontfix etc... that you have on my AROS One 68k
-
Also tested FS-UAE 3.0.5 for Windows, it works only without JIT so very slow, with JIT active FS-UAE crashes.
Best choice remains WinUAE, extremely simple, fast and functional!
-
Also tested FS-UAE 3.0.5 for Windows, it works only without JIT so very slow, with JIT active FS-UAE crashes.
Best choice remains WinUAE, extremely simple, fast and functional!
Ok, at least you confirm that JIT crashes the machine, so this is not specific to my config. Thanks.
-
Yes, but strangely with my AfA One (OS 3.9 BB4 + AfA OS), same configuration, only the ROMs change, FS-UAE 3.0.5 + JIT works fine and AfA-One is also quite fast "almost" like WinUAE
-
Ok, at least you confirm that JIT crashes the machine, so this is not specific to my config. Thanks.
Further confirmation, deactivated JIT on FS-UAE also on Amilator AROS One 68k starts without problems, of course it turns out to be slow
-
deadwood, on the report made on EAB, FS-UAE developer "FrodeSolheim" intervened and asked me if it was easy to boot AROS 68k, and that he would like to try it.
I immediately prepared and attached on the post a HardFile with the "clean" Nightly Build installed (copied ISO content) and configured a RTG screen.
http://eab.abime.net/showthread.php?t=108477
-
Good, I see Frode has found the issue. At least we have clarity it is not related to AROS ROM itself. Thanks for taking this up!
-
Yes with that fix now also on Amilator AROS One 68k works perfectly with JT active, and everything is as fast as on WinUAE
Frode also said that on his new version 4 that will be released, based on a newer version of WinUAE the problem will no longer be present.
-
thanx for your help on this
-
Good, I see Frode has found the issue. At least we have clarity it is not related to AROS ROM itself. Thanks for taking this up!
I do not know if it can be fixed with the apolloos commits already...
there were two bugs I saw a number of times... the problems with fire constantly pressed (joystick)
the second when file requester opened the system freezes
both problems affect a number of programs but not all. For the second problem I have attached "cli-tracker". If you start it in cli the system immediately freezes (in my system) or at least application creates error and not continues (Wanderer). It also happened in last available nightly. Perhaps you could look at this issue that affects expecially applications.
Thanks in advance
-
there were two bugs I saw a number of times... the problems with fire constantly pressed (joystick)
The "fire that stays pressed" is caused by the "Lowlevel.library" if you replace it with an Amiga version the problem is solved.
the second when file requester opened the system freezes
Regarding "cli-tracker" please send me a command string to test it on my system, thanks !
Also here I think it is a problem of a library "reqtools.library", if you replace it with an OS the problem will be solved.
-
There are other native AROS 68k libraries that have problems with "AMiGA Applications" most recent and they are:
Icon.library -> to be replaced immediately to handle Dual-PNG, OS4 etc.. without this library by PeterK AROS One 68k could not exist.
Rexxsyslib.library -> important to start applications like ModExplorer
Warp3D.library -> With WinUAE version you have a hardware acceleration
XadMaster.library -> To transform archives into folders
There are other less important libraries that at the moment I don't remember
-
there were two bugs I saw a number of times... the problems with fire constantly pressed (joystick)
The "fire that stays pressed" is caused by the "Lowlevel.library" if you replace it with an Amiga version the problem is solved.
the second when file requester opened the system freezes
Regarding "cli-tracker" please send me a command string to test it on my system, thanks !
Also here I think it is a problem of a library "reqtools.library", if you replace it with an OS the problem will be solved.
the lowlevel problem might be fixed by apollo team, the reqtools problem I am not sure
only use cli-tracker without any parameter, then it opens requester to let you select a file to play and in this moment a error occurs
-
There are other native AROS 68k libraries that have problems with "AMiGA Applications" most recent and they are:
Icon.library -> to be replaced immediately to handle Dual-PNG, OS4 etc.. without this library by PeterK AROS One 68k could not exist.
Rexxsyslib.library -> important to start applications like ModExplorer
Warp3D.library -> With WinUAE version you have a hardware acceleration
XadMaster.library -> To transform archives into folders
There are other less important libraries that at the moment I don't remember
I use icon library from PeterK and xadmaster works (I am not sure which version I now use ;) ). Modexplorer CE (or how it is called) works but of course having full Arexx support would be nice. Copying system files from original installation is no option for me (in Aros Vision).
If you are about it, does printing in file work for you? Also do amiga applications work with it? i have not managed to print in file. It would be a workaround for real world using because it is possible to convert Postscript in PDF and the PDF could be printed on another system or even directly printed with certain printers.
-
New roms: https://axrt.org/development/aros-rom-20211124.zip
They don't have any of the Apollo team changes yet, but should work unlike previous ones. Please let me know if you notice any issues compare to "Nightly build" ROMs.
-
New roms: https://axrt.org/development/aros-rom-20211124.zip
They don't have any of the Apollo team changes yet, but should work unlike previous ones. Please let me know if you notice any issues compare to "Nightly build" ROMs.
thanks. I am not at home and will do later
-
Modexplorer CE (or how it is called) works but of course having full Arexx support would be nice. Copying system files from original installation is no option for me (in Aros Vision).
No I'm talking about Modexplorer Full version, AmimodModRadio works discretely, see screenshot !
only use cli-tracker without any parameter, then it opens requester to let you select a file to play and in this moment a error occurs
I don't have any crashes, see screenshot
If you are about it, does printing in file work for you? Also do amiga applications work with it? i have not managed to print in file. It would be a workaround for real world using because it is possible to convert Postscript in PDF and the PDF could be printed on another system or even directly printed with certain printers.
I have not tried, I will test as soon as possible
-
@AMIGASYSTEM
No error with cli-tracker?
i am only a little surprised. i got this error even with plain nightly (the last one officially available on the main branch)
Do you replace something in your distribution compared to a nightly? I use the original aros libs (except icon lib of course)
-
If you are about it, does printing in file work for you?
With which tool would you print to File, is there a virtual printer on Amiga ?
It would be a workaround for real world using because it is possible to convert Postscript in PDF and the PDF could be printed on another system or even directly printed with certain printers.
Why do so much work? on Amiga/AROS x86/68k thanks to an Italian user/developer there is a small program that converts text directly to PDF, you can also use it as an editor and print directly to PDF, see my little video attached.
TXT to PDF on AROS 68k
https://drive.google.com/file/d/1rMs1YjWj0PXsmtfEKq-BKUIE9uMo8df1/view
-
@AMIGASYSTEM
No error with cli-tracker?
I have tried to load files and at the moment I have no errors, the reqtools.library crashes I had also found on other applications. Anyway in my opinion it is not a problem of reqtools.library AROS but of the amiga programs not compatible with AROS 68k, it would be necessary to convert them to the native AROS 68k exe.
-
there is some sort of incompatibility in aros that should be fixed if possible in my view, changing the programs is not a option in all cases, be it that not all programs have sources that are accessible, be it that the developer behind not want to do it.
-
If you are about it, does printing in file work for you?
With which tool would you print to File, is there a virtual printer on Amiga ?
It would be a workaround for real world using because it is possible to convert Postscript in PDF and the PDF could be printed on another system or even directly printed with certain printers.
Why do so much work? on Amiga/AROS x86/68k thanks to an Italian user/developer there is a small program that converts text directly to PDF, you can also use it as an editor and print directly to PDF, see my little video attached.
TXT to PDF on AROS 68k
https://drive.google.com/file/d/1rMs1YjWj0PXsmtfEKq-BKUIE9uMo8df1/view
I know the converters but I also think of complex applications like final writer and not just plain text. Or you want to print a picture. And so on... of course you could easier that do on a modern system not using Aros at all... but I would like to offer at least a path to even use Aros more seriously
-
If you are about it, does printing in file work for you? Also do amiga applications work with it?
Tried it and on AROS One 68k it works, I loaded a text with Multiview and printed it to file, see screenshot !
-
New roms: https://axrt.org/development/aros-rom-20211124.zip
They don't have any of the Apollo team changes yet, but should work unlike previous ones. Please let me know if you notice any issues compare to "Nightly build" ROMs.
your roms boot aros vision normally to me
-
New roms: https://axrt.org/development/aros-rom-20211124.zip
They don't have any of the Apollo team changes yet, but should work unlike previous ones. Please let me know if you notice any issues compare to "Nightly build" ROMs.
your roms boot aros vision normally to me
What settings do you use in Printer?
-
New roms: https://axrt.org/development/aros-rom-20211124.zip
They don't have any of the Apollo team changes yet, but should work unlike previous ones. Please let me know if you notice any issues compare to "Nightly build" ROMs.
your roms boot aros vision normally to me
Thx for the confirmation.
-
your roms boot aros vision normally to me
Yes they work with Aros Vision, I use only, and always the roms included in the latest Nightly builds
What settings do you use in Printer?
With your Aros Vision i printed to file without problems, to activate the printing after setting "Print To File" in "Printer Preferences " i have to click on "Save".
Once this is done from the Multiview menu go to Print and you will get a Request to Save File.
By the way, you are using the old Multiview version by Miker that doesn't allow to resize the window.
-
Yes "save in file" works for me too...
the problem was I had to select the driver in driver preferences. Postscript was shown but obviously not used if not selected and then saved. It is ok now. I will see how it will work in future
-
For file printing to work, the file "printer.prefs" must be present in the path Prefs\Env-Archive\SYS, without this file you cannot print to file. For this reason I said that you must first save, this creates the file "printer.prefs".
-
For file printing to work, the file "printer.prefs" must be present in the path Prefs\Env-Archive\SYS, without this file you cannot print to file. For this reason I said that you must first save, this creates the file "printer.prefs".
that was not enough...
you also must select the postscript driver before saving. I saw it and thought it was selected already but it was not.
-
Yeah right, i always found them selected by default.
-
Here is first ROM with some Apollo changes integrated:
https://axrt.org/development/aros-rom-20211125.zip
Here is a list of changes that are non-SAGA related. Please let me know if you see any regression/improvement.
df4845030f ("Send a handshake and set CIA serial in input mode during keyboard initialization. This helps against keyboard missing after reset.", 2020-03-09)
2bddf34f2d ("Alternate fix for Early Boot on NTSC. Buttons should be correctly placed", 2020-07-17)
5c8b858746 ("Fix that enables NTSC modes", 2020-08-06)
f0e3be2fd7 ("Increase speed of PutPixel in AmigaVideo driver", 2020-08-15)
226c2faa3d ("- Set nominal bit depth for the Amiga GFX driver to 2 bit. This ensures that booting without startup-sequence results in at least a 2 bit colour screen (before it was 1 bit which is horrible).", 2021-02-22)
67b3424ce6 ("Fix Workbook filter Icons and AllFiles", 2020-08-12)
-
Tested the new roms and they work fine, I don't see any particular difference though, on startup without startup I don't notice the 2 bit difference, I think even the previous roms already had a 2 bit color screen on startup without startup-sequence.
-
Noi problems either
the first fix also is vampire V4 related as far as I can remember
sometimes keyboard was lost after boot and that fix solved the issue
-
About AROS 68k I would like to report a problem "GURU" with the application "FTPManager", the problem occurs even with the Nightly Build and with any Rom, the cause could be the freetype2.library
-
Noi problems either
the first fix also is vampire V4 related as far as I can remember
sometimes keyboard was lost after boot and that fix solved the issue
Thanks. Is there a way to confirm that first change is V4 specific? I see it was applied on AROS in the past and then reverted...
EDIT: Ok, I found comment in pull request - indeed only for V4 so I will remove it.
-
Hi,
Next ROM: https://axrt.org/development/aros-rom-20211125-2.zip
Contains two changes on top of previous:
4db0aecbc0 ("Update setchiprev.c", 2021-04-13)
d2e34179c9 ("Default AROS behavior is not AmigaOS-default and thus breaks compatibility", 2020-02-25)
Change 1) is supposed to make Deluxe Galaga AGA start on AROS (game should detect AGA correctly)
Change 2) is supposed to make "old applications requesting screen without mode id" work. The change does not say which applications it targets.
Also it has impact AROS behavious. So far if you had GFX card, it was automatically selected over Amiga Chipset. Now, the chipset mode will
be selected and you will have to select GFX mode manually in ScreenPrefs
Please validate 1) and let me know if 2) gives any real improvement.
-
Made some tests even if it was not easy, there are many versions 1.x and 2x of Deluxe Galaga ECS/AGA, in addition to WHDLoad versions.
In fact the last two ROMs improve and fix the graphic aspect, menus and windows are full screen, with the other ROMs they were narrow/cut, in the game there are no more graphic artifacts.
Remains the problem fire that does not work or remains enchanted,
-
Hi,
Next ROM: https://axrt.org/development/aros-rom-20211125-2.zip
Contains two changes on top of previous:
4db0aecbc0 ("Update setchiprev.c", 2021-04-13)
d2e34179c9 ("Default AROS behavior is not AmigaOS-default and thus breaks compatibility", 2020-02-25)
Change 1) is supposed to make Deluxe Galaga AGA start on AROS (game should detect AGA correctly)
Change 2) is supposed to make "old applications requesting screen without mode id" work. The change does not say which applications it targets.
Also it has impact AROS behavious. So far if you had GFX card, it was automatically selected over Amiga Chipset. Now, the chipset mode will
be selected and you will have to select GFX mode manually in ScreenPrefs
Please validate 1) and let me know if 2) gives any real improvement.
Second should affect many Games and older Applications who expect Pal or ntsc and often got rtg
-
Hi,
Next ROM: https://axrt.org/development/aros-rom-20211125-2.zip
Contains two changes on top of previous:
4db0aecbc0 ("Update setchiprev.c", 2021-04-13)
d2e34179c9 ("Default AROS behavior is not AmigaOS-default and thus breaks compatibility", 2020-02-25)
Change 1) is supposed to make Deluxe Galaga AGA start on AROS (game should detect AGA correctly)
Change 2) is supposed to make "old applications requesting screen without mode id" work. The change does not say which applications it targets.
Also it has impact AROS behavious. So far if you had GFX card, it was automatically selected over Amiga Chipset. Now, the chipset mode will
be selected and you will have to select GFX mode manually in ScreenPrefs
Please validate 1) and let me know if 2) gives any real improvement.
Thanks
-
Made some tests even if it was not easy, there are many versions 1.x and 2x of Deluxe Galaga ECS/AGA, in addition to WHDLoad versions.
In fact the last two ROMs improve and fix the graphic aspect, menus and windows are full screen, with the other ROMs they were narrow/cut, in the game there are no more graphic artifacts.
Remains the problem fire that does not work or remains enchanted,
Thanks for the tests and confirmation. I have changes to joystick lined up next.
Can you describe how you test joystick? Do you connect real joysting or emulate it via keyboyard?
Can you give me names of 2-3 non-WHDLoad games that have joystick not working?
-
I enclose a HardFile with two games installed (last porting) for OS3, as a matter of space I have not added the audio tracks, the games work perfectly if I replace the "lowlevel.library" of the system.
I use Keyboard (I will make a test also with a USB JoyPad in the afternoon):
Blood:
- Enchanted Fire (fire button constantly pressed)
- Directional arrows, don't go back and forth
Exiting Blood Wanderer is frozen, no folders open.
Shadow Warrior:
The game can't start because the enter/fire key doesn't work in the menu, for the same keys you can't even exit the game anymore.
HardFile Bootable AROS One 68k + Games Blood and Shadow Warrior:
Posted in PM my HardFile with games
-
Made some tests even if it was not easy, there are many versions 1.x and 2x of Deluxe Galaga ECS/AGA, in addition to WHDLoad versions.
In fact the last two ROMs improve and fix the graphic aspect, menus and windows are full screen, with the other ROMs they were narrow/cut, in the game there are no more graphic artifacts.
Remains the problem fire that does not work or remains enchanted,
Thanks for the tests and confirmation. I have changes to joystick lined up next.
Can you describe how you test joystick? Do you connect real joysting or emulate it via keyboyard?
Can you give me names of 2-3 non-WHDLoad games that have joystick not working?
To me it seems sometimes fire button is constantly pressed or not recognized at all
Exhumed is not working too. I do not know what it causes. I will upload it and givr you a link, And also look if I find some games with problems.
-
To me it seems sometimes fire button is constantly pressed or not recognized at all
Yes that's what happens on the game/porting Blood, I as said solved this problem by replacing the "lowlevel.library", see flooded video of Blood working on AROS One 68k.
https://www.youtube.com/watch?v=CqS9qW3cAN4
-
I enclose a HardFile with two games installed (last porting) for OS3, as a matter of space I have not added the audio tracks, the games work perfectly if I replace the "lowlevel.library" of the system.
I use Keyboard (I will make a test also with a USB JoyPad in the afternoon):
Blood:
- Enchanted Fire (fire button constantly pressed)
- Directional arrows, don't go back and forth
Exiting Blood Wanderer is frozen, no folders open.
Shadow Warrior:
The game can't start because the enter/fire key doesn't work in the menu, for the same keys you can't even exit the game anymore.
HardFile Bootable AROS One 68k + Games Blood and Shadow Warrior:
Posted in PM my HardFile with games
Are there any ADF-based games that have problem with joystick?
-
Try it now, no need to be a Google user, I distribute all my files this way !
Now I see to find some game from Floppy that has the same problems, however it is better to test the games that I have sent you because they interest almost all the porting
-
I'm using your new ROMs
For me with WinUAE/AROS 68k ShadowWorrior and Blood work perfectly without JIT but are very slow (you have to wait a long time) "unplayable".
Many of these kinds of games require JIT and FPU.
There are plenty of ADF OCS/ECS/AGA games that don't work with AROS 68k, so it becomes difficult to find the ones that have keyboard/Joystik problems.
I'll try searching my archives, I haven't played a game in over 30 years :)
-
Thanks. If my ROMs work for you I'll just assume this this something FS-UAE related again and will use ShadowWarrior to test changes from Apollo team.
[/quote
One game with problems is exu]t, I have uploaded it
http://www.aros-platform.de/exult.zs
-
this game not reacts on fire button
http://www.aros-platform.de/Galagawars.7z
-
in this demo fire button also not works
http://www.aros-platform.de/tinylittleslug.7z
-
Thanks. If my ROMs work for you I'll just assume this this something FS-UAE related again and will use ShadowWarrior to test changes from Apollo team.
Maybe you haven't configured FS-UAE well, I'll do some tests with Amilator and FS-UAE Windows version, with Linux you could try WinUAE with Wine and use my config, eventually I'll attach it here.
You have to test both with ShadowWorrior and Blood, this is because the two games have different and common problems for other games, as said if I change the librearia the problems will be solved for both ShadowWorrior and Blood.
@OlafS3
Even TinyLittleSlug and Galagawars work perfectly by replacing the library !
-
Replacing with what?
The idea is to have aros as a full replacement of amigaos. I cannot distribute original files legally.
-
I think like you, my AROS One 68k does not include OS3 software, the only OS3 software included is free software taken from Aminet that is used to solve "momentarily" the shortcomings of AROS 68k
The library to replace is "lowlevel.library" that I have mentioned several times in this thread, of course it is a specific library for games distributed on Aminet !
https://aminet.net/package/driver/input/NewLowLevel
-
I think like you, my AROS One 68k does not include OS3 software, the only OS3 software included is free software taken from Aminet that is used to solve "momentarily" the shortcomings of AROS 68k
The library to replace is "lowlevel.library" that I have mentioned several times in this thread, of course it is a specific library for games distributed on Aminet !
https://aminet.net/package/driver/input/NewLowLevel
Thanks for the idea. I have replaced it in rom using remlib and now the problem is solved. What library did you use for asl library?
-
despite that (even with that) it should be solved in rom too
-
Thanks for the idea. I have replaced it in rom using remlib and now the problem is solved.
Yes do you have to use RemLib, same procedure as for Icon.library
What library did you use for asl library?
asl.library or reqtools.library?
-
I (at the moment) use remlib to replace icon and lowlevel library
what do you replace? Reqtools? and from where?
-
I have found one to replace reqtools. Now the problem seems to be away
-
You can almost always find something to replace it, which applications were giving you problems with reqtools?
-
there were several. Expecially viewers and players but also applications
-
There were a lot of them, of course the fault of the old OS3 programs, a good App to test the various Request Files is EaglePlayer that allows you to choose reqtools, asl.library or req.library
-
@AMIGASYSTEM, @OlafS3
Do the replacement you found for lowlevel and reqtools come with source code?
-
@AMIGASYSTEM, @OlafS3
Do the replacement you found for lowlevel and reqtools come with source code?
for reqtools I used this:
http://aminet.net/package/util/libs/ReqToolsUsr
Funnily I find somewhere the name of the author Magnus Holmgren as aros dev and also him involved in a backport of reqtools from aros
perhaps it is the aros library but without some commits done since then that harm
-
here is the archive with the backport from aros
not sure if both reqtool libs are identical
http://aminet.net/package/util/libs/ReqToolsLib
-
lowlevel is this:
http://aminet.net/package/driver/input/NewLowLevel
without sources
-
here is the archive with the backport from aros
not sure if both reqtool libs are identical
http://aminet.net/package/util/libs/ReqToolsLib
Thank you. Can you give me a name of application and description how to trigger a "reqtools" problem with current AROS ROMs?
-
I have just tested the aros backport (with sources)
it seems reqtools library from aros works. It is from 2001 so my guess is that there were commits that causes trouble for some aspplications
-
the problem was that some applications that opened file requester caused errors and then my system freezes, on nightly the system still works but the application stops and there is a error requester. I just see requester open.
example the attached file if you start it from cli without parameters
-
Thanks, but report created:
https://github.com/deadw00d/AROS/issues/50
-
@OlafS3
For Galagawars, keyboard also does not seem to be working: pressing ESC does not exit game
For Tinylittleslug -> I think fire is working. I can go into level pressing R-Ctrl (mapped to fire). I think fire has no use in the game itself (only joy directions are used)
-
@AMIGASYSTEM
For Shadow Warrior, can you switch controller in WinUAE to CD32 gamepad and let me know if fire works then?
-
@AMIGASYSTEM
For Shadow Warrior, can you switch controller in WinUAE to CD32 gamepad and let me know if fire works then?
No any controller works with your ROMs, not even the USB GamePad works.
I add that the GamePad doesn't work with the "NewLowLevel", but with this library the GamePad doesn't work on OS3 either.
The GamePD instead works fine on OS3 with the system library, in my case I used OS 3.9 AfA One
-
That's weird. Under FS-UAE switching emulation from joystick to CD32 pad makes the fire work.
-
Here is new ROM: https://axrt.org/development/aros-rom-20211128.zip
With this ROM, FIRE in emulated joystick in FS-UAE does not get stuck anymore. Let me know if it works for you.
-
Yes with these Rom Shadow Warrior works great on WinUAE even the JoyPad USB, but the graphics are bad, there are many bars and after a while 'that you play WinUAE crashes!
-
Here is new ROM: https://axrt.org/development/aros-rom-20211128.zip
With this ROM, FIRE in emulated joystick in FS-UAE does not get stuck anymore. Let me know if it works for you.
looks good. I copied the roms and exhumed works too now. Up to now there was a constant hitting.
-
looks good. I copied the roms and exhumed works too now. Up to now there was a constant hitting.
Yes but these new rom has problems with the graphics even with programs, ModExplorer NG crashes the system!
-
looks good. I copied the roms and exhumed works too now. Up to now there was a constant hitting.
Yes but these new rom has problems with the graphics even with programs, ModExplorer NG crashes the system!
Does it work with "Nightly Build" ROM?
-
Here is new ROM: https://axrt.org/development/aros-rom-20211128.zip
With this ROM, FIRE in emulated joystick in FS-UAE does not get stuck anymore. Let me know if it works for you.
looks good. I copied the roms and exhumed works too now. Up to now there was a constant hitting.
Thx for confirmation
-
Does it work with "Nightly Build" ROM?
Yes with Nightly Build ROMs it works fine.
Before reporting I always test with all Roms, and I test with both Nightly Build and AROS One 68k.
-
Does it work with "Nightly Build" ROM?
Yes with Nightly Build ROMs it works fine.
Before reporting I always test with all Roms, and I test with both Nightly Build and AROS One 68k.
Ok, got it. Looking where regression happened now.
-
It turns out that flickering and crash is caused by the screen mode change I integrated two days ago (select PAL instead of RTG). The comment there
reads that:
"the legacy software opening a screen without PAL or NTSC ModeID provided will fail or crash entire AROS if it attempts to use low-level components such as blitter. "
@OlafS3, @AMIGASYSTEM: Do you know examples of such legacy software I could use for testing?
EDIT:
What I think is happening is: SW requests 640x400x8 mode and instead of using GFX card, it selected AGA mode (due to change mentioned above). AGA modes (6,7 and 8 bit plance modes) don't work correctly on AROS for some reason. This causes the flickering and crashes. The change to provide chipset modes first can be re-introduced when AGA gets fixed on AROS.
-
Next ROM: https://axrt.org/development/aros-rom-20211128-2.zip
FIRE fix, GFX modes have priority over chipset modes
-
Next ROM: https://axrt.org/development/aros-rom-20211128-2.zip
FIRE fix, GFX modes have priority over chipset modes
Shadow Warrior and Ehumed look good to me. I have played both a short time without problems
-
Thanks!
Last ROM for today: https://axrt.org/development/aros-rom-20211128-3.zip
This time more fixes from Apollo:
1) BugFIX: removed limit of 64Mb (by HUNK-Size) in Amiga executable files
2) FIXES: DEVPAC Editor (When user insert a new line, text bellow NOT disappears now)
3) FIXED: HippoPlayer Prefs window (when user changes between TABS)
4) FIXES: HippoPlayer: now SLIDER gadgets in PREFS shows your linked label
5) FIXES: ASM-ONE preferences window (now all checkbox are not erased)
Let me know if you find any regression compared to 20211128-2 version.
-
Sorry for the delay I just got home, tested the latest aros-rom-20211128-3.zipper
- Shadow Warrior -> Works well with Keyboard and JoyPad
- Blood -> Works well with keyboard, with JopPad does not work Directional Arrows and Fire, if I access the game the weapon turns automatically without stopping
ModExplorer NG -> As soon as it starts it crashes the system
-
I will look into ModExplorer NG problem.
Can anyone check DEVPAC, ASM-ONE and HippoPlayer if the mentioned fixes actually work?
-
ModExplorer NG -> As soon as it starts it crashes the system
Where can I download the version you are using?
-
I will look into ModExplorer NG problem.
Can anyone check DEVPAC, ASM-ONE and HippoPlayer if the mentioned fixes actually work?
I do not own dev-pac. I have tested both hippo-player and asm-one and did not find problems.
-
I have found another problem that affects different programs (not just games)
it is there for some time (before recent fixes)
if you start f.e. a demo it works but if you stops it you only get a empty screen and not return to OS
Example (recent) attached
-
and another thing from testing...
I successfully print from applications in a file (postscript). If you look in the file it seems sucessful. I then tried to convert the postscript file to pdf using online converter but it only resulted in empty pages. Anyone has a idea what to do? Or is the aros driver too old and postscript has changed?
-
Where can I download the version you are using?
I attach link, Download ModExplorer NG OS3, don't download the FPU version because it won't start on OS3, I reported the error found to the developer.
http://evil.bplaced.net/index.php?%20name=ModExplorer&page=ModExplorerNG
Requirements:
- Nightly Build ROM ModExplorer NG (your Roma ones crash the system)
- MCC_TextEditor-15.56 (the ones included in Nightly Build are old)
(ModExplorer looks for these libraries in LIBS/MUI, do not copy them to Classes/Zune because they will not be found)
- MCC_TheBar-26.22 (also copy these libraries to LIBS/MUI)
Using the Nightly Build, Modexplorer as soon as you open it will freeze the pointer, I have to find out why, on AROS One 68k no problem Modexplorer works perfectly with the requirements mentioned above...
Regarding HIP there is a small imperfection in the underlying GUI, a white bar that is eliminated if you enlarge the window.
-
Can you make a zip file of your version of Mod Explorer as well as needed MUI classes for me to download?
-
Yes, now in the Hardfile I sent you I'll add working Mod Explorer (if you use Nightly Build ROMs) otherwise you'll have a crash, you have to solve the Pointer freezing problem.
In the hardfile you will also find HIP updated a few weeks ago that includes improvements.
-
Sent in PM the HardFile with ModExplorer and HippoPlayer Update
I fixed the frozen pointer freze, it was due to the usual lowlevel.library, these are the changes compared to the Nightly Build:
- Nightly Build ROMs
- Lowlevel.library replacement
- MCC_TheBar-26.22
- MCC_TextEditor-15.56
- All libraries/PlugIns to start any "Hollywood" application
- Black-white pointer
- Set config ModExplorer in Tooltypes Icon
- Installed uae.audio, setting AHI UAE WIFI 16Bit (if you do not use WinUAE you have to change the setting, because this driver may not being present on FS-UAE
In the screenshot shown also the white band on the request of HippoPlayer
-
Ok, I'll see if I can find the problem.
-
@AMIGASYSTEM
Are any of the libraries (Holywood, MUI classes) that you need to install to have Mod Player NG working special versions for AROS m68k or are they generic versions for AmigaOS 3.1?
-
Hollywood libraries are generic OS3.x, there are no specific Hollywood libraries for AROS 68k, however Hollywood OS3.x libraries work fine on AROS 68k.
Also for MUI in the original package there are no native AROS 68k libraries, native MUI libraries for AROS 68k exist only in the Nightly Build.
The problem is that native AROS 68k applications look for MUI libraries in the "SYS:Classes/Zune" path, while native OS 3.x applications look for MUI libraries in the SYS:MUI or SYS:Libs/MUI paths.
All this can create duplicate libraries and conflicts, this for example does not happen on AfA OS where you can disable MUI and use Zune or vice versa.
-
An example how on OS3.9 AfA OS you can use MUI and ZUNE separately.
I ran the new ModExplorer on AfA One in the two modes, MUI Vs Zune
-
This ROM should solve the Mod Player NG freeze (not related to lowlevel.library)
https://axrt.org/development/aros-rom-20211201.zip
Please let me know it it works.
-
I have included the "light" version of modexplorer. That worked not too but now with your new roms works again.
thanx
-
Please let me know it it works.
Right now it's perfect, now Blood works fine, Shadow Warrior works fine too.
ModExplorer NG and ModExplorer Lite work well.
Now it seems that there is no more need of lowlevel.library and rexxsyslib.library
I'll do more tests and let you know.
As libraries would be essential to include in the Rom the icon.library of PeterK if he agrees, it is a library essential for AROS 68k.
Alternatively you could do a porting of the icon.library of AROS x86, more advanced library that manages the Dual-PNG.
Regarding the test I did for the Midi Play, it would be necessary to check the library "camd.library" that seems not to work, those posted on aminet all work well.
-
Please let me know it it works.
As libraries would be essential to include in the Rom the icon.library of PeterK if he agrees, it is a library essential for AROS 68k.
Alternatively you could do a porting of the icon.library of AROS x86, more advanced library that manages the Dua PNG.
The icon library for AROS 68k, x86 & x86_64 should be the same. If not identical there are only slight differences.
-
I am only 68k guy ;) but at least on 68k PeterKs library always was better. If it was possible to integrate it on Aros 68k officially it would be nice
-
@AMIGASYSTEM, @Olaf3S
Thanks for confirmation.
As miker says, the icon library used in ABIv0 and 68k is pretty much the same. If ABIv0 one "does more" it probably means there is regression in newer versions (which is used for 68k).
-
As miker says, the icon library used in ABIv0 and 68k is pretty much the same. If ABIv0 one "does more" it probably means there is regression in newer versions (which is used for 68k).
No, they are not the same, try these Dual-PNGs first on AROS x86 and then on AROS 68k
My AROS One 68k includes all high quality Dual-PNG icons, on AROS x86 they look great while on AROS 68k they are ugly, on AROS One 68k by default I use an icon.library by PeterK expressly created for AROS 68k.
All Distros Aros 68k including use the Icon.library by PeterK
-
No, they are not the same, try these Dual-PNGs first on AROS x86 and then on AROS 68k
Ha, you are right! The problem is not 68k related - actually all ABIv11 (also linux) renders these icons wrong while ABIv0 renders them correctly. Ok, added to my TODO list.
-
No, they are not the same, try these Dual-PNGs first on AROS x86 and then on AROS 68k
Ha, you are right! The problem is not 68k related - actually all ABIv11 (also linux) renders these icons wrong while ABIv0 renders them correctly. Ok, added to my TODO list.
It seems that AROS 68k tries to make an approximation of an IFF Icon from the PNG Icon Data. But it does it very badly.
The poor quality IFF Icons you get in AROS 68k when viewing PNG Icons looks like what ILBM2ICON produces. The color reduction code isn't very well optimised. Introducing Real Color Quantizing would probably improve the resulting IFF Icons.
On the other hand icons designed specifically for AROS 68k are quite nice! See screenshot. Those are IFF Icons with signature "E3 10" (Legacy Amiga Icon).
Not the Gorilla Icons, the other ones.
It's the same code for ABIv1 and AROS 68k so there must be a switch in Icon Library for 68k maybe activated by Build Script.
Maybe it would be useful to have a user option in IControl for which Icon Mode the Icon Library uses such as "Classic" or "Enhanced" like Wanderer options for opening of windows.
-
Also on my IcarosDesktop x86_64 based on ABIv1 the PNG MultiView Icons look great.
My system files are from June 28 2019.
-
for testing I have just uploaded a snapshot of my current aros vision
https://www.aros-platform.de/test/aros_2020_basis_UAE.7z
Except minor changes and iGame and of course the updated roms from Deadwood this will be the final version for me
Screenshot:
http://www.aros-platform.de/ArosVision_Final.png
-
Also on my IcarosDesktop x86_64 based on ABIv1 the PNG MultiView Icons look great.
My system files are from June 28 2019.
Thanks. That narrows down search window :)
-
Also on my IcarosDesktop x86_64 based on ABIv1 the PNG MultiView Icons look great.
My system files are from June 28 2019.
Thanks. That narrows down search window :)
As you know I use Magellan as desktop. For me (using Magellan) the icon library never worked. I do not know if it is Magellan related and easy solvable. So I load PeterKs icon library. Also at the moment I load the regtools library (backport from aros 2001) we discussed already at the moment
-
As you know I use Magellan as desktop. For me (using Magellan) the icon library never worked. I do not know if it is Magellan related and easy solvable. So I load PeterKs icon library. Also at the moment I load the regtools library (backport from aros 2001) we discussed already at the moment
I understand. Currently I'm not looking into general improvement, rather fixing regressions. The reqtools regression is on my list.
-
New rom:
https://axrt.org/development/aros-rom-20211202.zip
Two changes:
1) BugFIX: Not autoScroll-up screen when user drag screen (with mouse pointer) until bottom-limit of screen.
2) BugFIX: Support for partitions with NOMOUNT flag set FIXES: HDD partitions marked as NOMOUNT are ignored and AUTOMOUNTed under AROS.
-
I am not sure how to test the changes. I assume it works, the rest not seems to be affected
-
I am not sure how to test the changes. I assume it works, the rest not seems to be affected
Thx
-
deadwood also I have not found anomalies even if I have not understood well the problem "autoScroll-up", maybe a small video would help me to understand.
EDIT:
On AROS x86 there are other things to solve, some time ago I reported HERE (https://ae.amigalife.org/index.php?topic=760.0) problem with the Italian keyboard, now there are also problems with languages, you can not change the language to the system.
-
As you know I use Magellan as desktop. For me (using Magellan) the icon library never worked. I do not know if it is Magellan related and easy solvable. So I load PeterKs icon library. Also at the moment I load the regtools library (backport from aros 2001) we discussed already at the moment
I understand. Currently I'm not looking into general improvement, rather fixing regressions. The reqtools regression is on my list.
the problem that f.e. demos that are closed leave a empty screen I already mentioned is also on your list? It affects both demos, games and older applications
-
New rom:
https://axrt.org/development/aros-rom-20211202.zip
Two changes:
1) BugFIX: Not autoScroll-up screen when user drag screen (with mouse pointer) until bottom-limit of screen.
2) BugFIX: Support for partitions with NOMOUNT flag set FIXES: HDD partitions marked as NOMOUNT are ignored and AUTOMOUNTed under AROS.
anything new for us to test?
-
deadwood also I have not found anomalies even if I have not understood well the problem "autoScroll-up", maybe a small video would help me to understand.
EDIT:
On AROS x86 there are other things to solve, some time ago I reported HERE (https://ae.amigalife.org/index.php?topic=760.0) problem with the Italian keyboard, now there are also problems with languages, you can not change the language to the system.
Not sure but I believe AROS 68k is based on ABIv1 much like AROS x86_64.
Several months ago on the Slack Channel their was a discussion about languages and keyboard layouts. I believe the English Keyboard & German Keyboards work. I don't know about others.
Also Mazze and some others were updating languages. Maybe something got broken in the process. Sorry it's so vague.
-
New rom:
https://axrt.org/development/aros-rom-20211202.zip
Two changes:
1) BugFIX: Not autoScroll-up screen when user drag screen (with mouse pointer) until bottom-limit of screen.
2) BugFIX: Support for partitions with NOMOUNT flag set FIXES: HDD partitions marked as NOMOUNT are ignored and AUTOMOUNTed under AROS.
anything new for us to test?
You could test German Keyboard Layout. And try to switch languages.
-
New rom:
https://axrt.org/development/aros-rom-20211202.zip
Two changes:
1) BugFIX: Not autoScroll-up screen when user drag screen (with mouse pointer) until bottom-limit of screen.
2) BugFIX: Support for partitions with NOMOUNT flag set FIXES: HDD partitions marked as NOMOUNT are ignored and AUTOMOUNTed under AROS.
anything new for us to test?
You could test German Keyboard Layout. And try to switch languages.
I use german language layout normally ;) I cannot remember any problems. Do you have a hint where I can find discussion about this? On this forum?
-
Yes AROS One 68k should be ABI-v1, this is proved by the fact that it is in the page dedicated to ABI-v1 systems
https://aros.sourceforge.io/nightly1.php
Yes German Keyboard Layout works well, but Italian, Spanish, French and other languages have a partial translation (see screenshot), Wandererer is not translated, even some system apps are not fully translated.
Also, the Italian keyboard is unusable, many characters don't work and others crash the system, try typing the two points :, the keyboard will crash.
-
it seems to be possible to use this software to edit keymaps
http://aminet.net/package/util/misc/KeyMapEd
it not works for me on aros but I can use it on 3.1 and there edit the aros keymaps
-
The problem may be on the App and not on the data files, I think have changed changed/broken something, on my old AROS One 68k the Italian localization of wandere working fine (see screenshot), only some App was not totally translated in the menus.
Now I'll try to use something from my old system !
-
for keymap I found a quick fix
http://aminet.net/package/driver/input/EuroMaps
the italian euromap seems to work (and the other too I think, aros keymaps are compatible to amiga keymaps)
Regarding locale I see the same on the nightly... Prefs from Wanderer translated to italian but menu english
-
attached are are keymaps from euromaps and aros keymaps including italian
perhaps it works for you
-
Thanks, about the Italian keyboard I solved it by taking the Keymaps from my old version of AROS One68k v1.1 that work fine.
For the Wandere translation was as I suspected, it seems not to depend on the Catalogs, the ones from the old version of AROS One v1.1 did not work, they gave the same result.
-
attached are are keymaps from euromaps and aros keymaps including italian
perhaps it works for you
Your Keymaps.7z work fine, but the Keymaps I have on AROS One 68k v1.1 are many more files, there are more languages, in the recent version of AROS 68k there are many missing Keymaps as well as some corrupted ones like for Italian.
-
Regarding the localization of Wanderer that does not exist in Italian, French, Spanish etc ... my suspicion is confirmed, everything depends on the App "Wanderer" I replaced it with the old version installed on my old AROS One 68k v1.1 and the Italian translation of Wanderer worked fine.
Of course it was just a test, the old "Wanderer" is not compatible with the new AROS 68k, if you use it the system crashes.
-
@deadwood
With your permission I'd like to do some testing and research to find out why PNG Icons don't display correctly on AROS 68k.
I've done some testing already and I'm somewhat familiar with the inner workings of Icon Library.
So far I have noticed that AROS 68k and AROS x86_64 share the same code base. So in theory 68k should be able to use PNG Icons. But when we use a PNG Icon on 68k what gets displayed is the planar gadget images. However Classic OS3.5 Icons show correctly. And Hybrid OS3.5 Icons with ARGB Data displays ok.
So maybe it isn't that Icon Library on 68k can't display ARGB. Maybe the diskobjpngio module isn't loading the ARGB Data?
For some reason I can't seem to enable debug in AROS 68k in WinUAE for Icon Library. It works for Icon Library in x86_64.
-
New rom:
https://axrt.org/development/aros-rom-20211202.zip
Two changes:
1) BugFIX: Not autoScroll-up screen when user drag screen (with mouse pointer) until bottom-limit of screen.
2) BugFIX: Support for partitions with NOMOUNT flag set FIXES: HDD partitions marked as NOMOUNT are ignored and AUTOMOUNTed under AROS.
anything new for us to test?
Not at the moment, but there should be something next week. There are still around 8 changes to be merged.
-
Regarding the localization of Wanderer that does not exist in Italian, French, Spanish etc ... my suspicion is confirmed, everything depends on the App "Wanderer" I replaced it with the old version installed on my old AROS One 68k v1.1 and the Italian translation of Wanderer worked fine.
Of course it was just a test, the old "Wanderer" is not compatible with the new AROS 68k, if you use it the system crashes.
I think you should report this to Mazze. I think he is maintaining the translations.
-
@deadwood
With your permission I'd like to do some testing and research to find out why PNG Icons don't display correctly on AROS 68k.
I've done some testing already and I'm somewhat familiar with the inner workings of Icon Library.
So far I have noticed that AROS 68k and AROS x86_64 share the same code base. So in theory 68k should be able to use PNG Icons. But when we use a PNG Icon on 68k what gets displayed is the planar gadget images. However Classic OS3.5 Icons show correctly. And Hybrid OS3.5 Icons with ARGB Data displays ok.
So maybe it isn't that Icon Library on 68k can't display ARGB. Maybe the diskobjpngio module isn't loading the ARGB Data?
For some reason I can't seem to enable debug in AROS 68k in WinUAE for Icon Library. It works for Icon Library in x86_64.
Sure, go ahead :) If you can fix it, it would be great.
For debug, you need to build with --with-serial-debug=yes and then redirect WinUAE serial port to a console (at least that's how things are done on Linux)
-
New rom:
https://axrt.org/development/aros-rom-20211202.zip
Two changes:
1) BugFIX: Not autoScroll-up screen when user drag screen (with mouse pointer) until bottom-limit of screen.
2) BugFIX: Support for partitions with NOMOUNT flag set FIXES: HDD partitions marked as NOMOUNT are ignored and AUTOMOUNTed under AROS.
anything new for us to test?
Not at the moment, but there should be something next week. There are still around 8 changes to be merged.
Thanks Deadwood
-
Regarding the localization of Wanderer that does not exist in Italian, French, Spanish etc ... my suspicion is confirmed, everything depends on the App "Wanderer" I replaced it with the old version installed on my old AROS One 68k v1.1 and the Italian translation of Wanderer worked fine.
Of course it was just a test, the old "Wanderer" is not compatible with the new AROS 68k, if you use it the system crashes.
I think you should report this to Mazze. I think he is maintaining the translations.
I don't know how to contact Mazze, if you can do it I thank you ! it's just a matter of time.
-
I don't know how to contact Mazze, if you can do it I thank you ! it's just a matter of time.
Here is a user here on Aros-Exec:
https://ae.amigalife.org/index.php?action=profile;u=103
-
Ok then a PM is fine, I thought there was somewhere to communicate !
-
@deadwood
I reconfigured my target just to be sure using this to enable debug but other apps showed debug in 68k previously.
./configure --target=amiga-m68k --with-aros-prefs=classic --with-binutils-version=2.32 --with-gcc-version=9.1.0 --with-serial-debug=yes
I recompiled icon library and made sure to include "debug.h" with debug = 1. But still no output messages from icon library in AROS 68k.
Attached is a text file of a write test in support.c in the function "ReadIcon". If we are using Icon Library it will surely use this function...but I get nothing.
I'll try the same write test on AROS x86_64 to verify the results. If it writes the test file then that leads me to believe something is odd with AROS 68k.
Is AROS 68k using Icon Library? It must be. How could it display icons?
-
Miker be careful, the icon.library of AROS 68k is fictitious, even if you delete it the icon.library will still work because "it is resident", this may mean that there is another copy of icon.library in the ROM.
-
Miker be careful, the icon.library of AROS 68k is fictitious, even if you delete it the icon.library will still work because "it is resident", this may mean that there is another copy of icon.library in the ROM.
I suspect something is fishy with AROS 68k Icon Library. You may be right. It isn't using the Icon Library in Libs. So what is it using.
I performed the same write test in Icon Library for x86_64 and the test file was written correctly. But it didn't work for 68k. Hmmm...
-
It is clear that there is an icon.library in Ram present in ROM or loaded through a command as OS 3.1.4 and OS 3.2 and OS 3.9, in fact if you try to copy the icon.library of PeterK in your AROS 68k you will see that it will not work because it is ignored, to activate it and have the system recognize it you must first clean the resident one from Ram through a command to put in the startup-sequence.
-
Hah!
Icon Library on AROS 68k is an imposter! What shenanigans is this?
I renamed icon.library and restarted AROS 68k. Everything displayed normally. All the icons were still there.
Then I simply removed Icon Library and same effect. Everything displayed as usual. So we aren't using Icon Library 68k. What are we using and why?
AMIGASYSTEM
How do you go about installing PeterK's Icon Library? Anything special I should know about?
-
It is clear that there is an icon.library in Ram present in ROM or loaded through a command as OS 3.1.4 and OS 3.2 and OS 3.9, in fact if you try to copy the icon.library of PeterK in your AROS 68k you will see that it will not work because it is ignored, to activate it and have the system recognize it you must first clean the resident one from Ram through a command to put in the startup-sequence.
I see you answered my question about PeterK's icon library.
What is the command in startup-sequence. Could you post the startup-sequence so i can take a look at it to trace the location of icon lib 68k?
I'll start another thread about Icon Library 68k so as to not clutter this one.
-
It's not an impostor the icon.library AROS 68k, probably it will be used for something, maybe to replace the one in RAM in case of deletion. or they forgot to delete it from the system, in fact on OS 3.1 exists only in ROM and in the OS it's not there :)
To install the icon.library of PeterK, first of all you have to download the most recent, this is because after a report of mine has been changed the path of ENV.... AROS uses a different path and without this change was not recognized def_icon, then maybe I'll attach the link where we have discussed with Peter.
Installation Icon.library PeterK
- Download THIS (https://aminet.net/package/util/libs/IconLib_46.4) Archive
- From the folder "Bonus" take the file "icon.library_Aros" and rename to icon.library
- Copy icon.library by Peter in LIBS and delete the one of AROS
- From the ThirdParty/RemLib folder take the file "RemLib" and copy it in C
- In the Startup- sequence add this command "C:Remlib >Nil: icon.library".
- You can put the command "C:Remlib >Nil: icon.library" after SetClock LOAD
If you have the dummy icons "the transparent ones created by the system" to make them active add the command "C:IconGhostingOff"
IconGhostingOff and other important commands for icons and more are in the same package of iconLib by PeterK
-
Hah!
Icon Library on AROS 68k is an imposter! What shenanigans is this?
I renamed icon.library and restarted AROS 68k. Everything displayed normally. All the icons were still there.
Then I simply removed Icon Library and same effect. Everything displayed as usual. So we aren't using Icon Library 68k. What are we using and why?
AMIGASYSTEM
How do you go about installing PeterK's Icon Library? Anything special I should know about?
icon.library is indeed in ROM. The one you get created in Libs is not used. To rebuild ROM you need to:
make workbench-libs-icon-kobj-quick
make kernel-link-amiga-m68k-quick
-
FYI1, I'm not using GC 9.1 for my builds, but the original 6.5.0.
FYI2, elements of ROM can be found in AROS/arch/m68k-amiga/boot/mmakefile.src
-
Hah!
Icon Library on AROS 68k is an imposter! What shenanigans is this?
I renamed icon.library and restarted AROS 68k. Everything displayed normally. All the icons were still there.
Then I simply removed Icon Library and same effect. Everything displayed as usual. So we aren't using Icon Library 68k. What are we using and why?
AMIGASYSTEM
How do you go about installing PeterK's Icon Library? Anything special I should know about?
icon.library is indeed in ROM. The one you get created in Libs is not used. To rebuild ROM you need to:
make workbench-libs-icon-kobj-quick
make kernel-link-amiga-m68k-quick
@deadwood
Thank you. That was a bit puzzling at first. It is resident in ROM.
Which Icon.Library will be included in ROM? The one present in Libs/icon.library?
So after I rebuild the ROM I then substitute the ROM. Ok.
-
Hah!
Icon Library on AROS 68k is an imposter! What shenanigans is this?
I renamed icon.library and restarted AROS 68k. Everything displayed normally. All the icons were still there.
Then I simply removed Icon Library and same effect. Everything displayed as usual. So we aren't using Icon Library 68k. What are we using and why?
AMIGASYSTEM
How do you go about installing PeterK's Icon Library? Anything special I should know about?
icon.library is indeed in ROM. The one you get created in Libs is not used. To rebuild ROM you need to:
make workbench-libs-icon-kobj-quick
make kernel-link-amiga-m68k-quick
in iconlib archive remlib is included in third parties. It can be used to replace the library in rom with the library in libs during startup
-
@miker
you do not necessarily need new roms
you can replace any library from rom with one library from harddrive during booting
RemLib >NIL: Libs:icon.library
-
Which Icon.Library will be included in ROM? The one present in Libs/icon.library?
Nope. Another trick ;)
<build_dir>/bin/amiga-m68k/gen/kobjs/icon_library.ko
-
@miker
you do not necessarily need new roms
I think instead it's better to delete the icon.library from the ROM, in this way you can use any updated icon.library without the need to use remLib !
in addition to some possible conflict with some application, that happen, already happened !
-
Which Icon.Library will be included in ROM? The one present in Libs/icon.library?
Nope. Another trick ;)
<build_dir>/bin/amiga-m68k/gen/kobjs/icon_library.ko
Is the library new? I have removed PeterK icon library from startup and it looks very similar even on magellan
looks good :)
-
@deadwood
Hmmm....
My ROM failed. But your most recent ROM files work fine.
Maybe my system files are too old? The AROS Vanilla 68k I'm running is based on a more recent Nightlly.
The 68k system file sources I'm using is a few years old. What is the date of the 68k sources you are using?
-
That error indeed looks like lack of compatibility.
I'm using ABIv11 latest sources:
https://github.com/deadw00d/AROS
-
That error indeed looks like lack of compatibility.
I'm using ABIv11 latest sources:
https://github.com/deadw00d/AROS
Once I update my sources and can compile a good ROM then I can proceed. I suspect that the GetFileSize method in ReadIconPNG fails on 68k. Why? Because I used that method in my Icon2PNG app recently and it failed on 68k. So I replaced it with a FileInfoBlock method and now it works correctly.
Once I enable debug I will check that first then write the ARGB Data to a bin file and check it's contents. I'll keep looking at it.
-
@deadwood
I'm having problems with the 68k build system using sources from ABIv11.
So it ocurred to me that my source files are a little older but I have about 8 AROS 68k test configs in WinUAE.
Each one is from a different time period. I don't throw anything away! ;)
So I matched up my newly rebuilt ROM files with the version of AROS 68k. Simple trial and error. I found a winner! Mar 3, 2020.
In addition to that I believe we fixed the problem. The MultiView Icon you see is the PNG Icon from X86_64. No tricks! It looks great. Plenty of debug information too! :)
Maybe the new ROM fixed the problem? I don't know. But it seems they work fine with PNG Icons.
So now what?
-
@miker1264
What sort of problems you are having with build?
With regards to your findings, are you saying that the last working ROM is 3rd March 2020?
Here is how these icons look like on my linux-x86_64 build:
-
@miker1264
What sort of problems you are having with build?
With regards to your findings, are you saying that the last working ROM is 3rd March 2020?
Here is how these icons look like on my linux-x86_64 build:
Yes. Last working ROM was Mar 3, 2020. Icons look great.
As far as build it keeps stopping searching for packages such as "cunit-3.2.6 and a few others. Maybe I should try gcc 6.5. ?
-
I'd propose to first do a build using the official method (./rebuild.sh script) and once that works, check other compilers :)
EDIT: I think compiler versions other then 6.5.0 won't work with ABIv11 for the moment. I didn't maintain them when making changes.
-
I did some tests these are the results
If I use my old AROS One 68k v1.1 from 2019 with deadwood's recent ROM, Dual-PNG icons show up perfectly, see screenshot (peterK's icon.library was not present in the system)
So ROMs work fine, icon.library works fine, in my opinion in 2020 something was broken
-
@AMIGASYSTEM
Mystery thinkens. The screen shot I made from linux-x86_64 showing wrong icons rendering is the same code base that I use for ROMs I posted. So it seems it sometimes works and sometimes does not. Can you show output of liblist showing version of icon.library when it works for you.
-
@deadwood
I can verify that the latest ROM you posted does NOT work to display PNG Icon Images.
AMIGASYSTEM would have missed it since he uses PeterK's Icon Library for his latest AROS One 68k.
According to the commits log for ABIv1 there were changes to Icon Library 9 months ago.
-
No miker I used only the icon.library that is in ROM, if you look at the screenshot you will notice that the icon.library in use on my old AROS One is v44.4 date 02 12 2021 the one inserted in the last deadwood ROM
deadwood i hope this is what you wanted to see
-
AMIGASYSTEM
The change in Icon Library happened in about March 2021 about 9 months ago. If your Icon Library is from February 2021 then it's good. But the Icon Library in ABIv11 has issues as we see in deadwoods screenshot of his x86_64. So the latest ROM uses code from after the change 9 months ago.
-
@deadwood
Here's a theory.
Either a change was introduced into Icon Library in the past that prevents PNG Icon Images from displaying properly or the change happened outside Icon Library.
Such as the Graphics HIDD driver, RTG driver. To narrow it down I would copy your Icon Library sources from ABIv11 into my x86_64 build system which is based on ABIv1 from 1 yr ago.
-
Sounds like a plan to narrow down what happened :)
-
Sounds like a plan to narrow down what happened :)
@deadwood
I copied your Icon Library sources from ABIv11 to my x86_64 build system then recompiled it.
On the IcarosDesktop x86_64 with system files from about two years ago, mid 2019 the icons display just fine.
For the sake of the pseudo-scientific method I will repeat the process to verify the results.
So it's entirely possible that the latest ROM file you posted could work correctly on AROS One 68k from February 2021 like he said.
Apologies to AMIGASYSTEM. I didn't mean to doubt you good sir. ;)
@deadwood
I did the easy part. I'll leave it to the master to do the hard part.
It must be graphics changes outside Icon Library at fault. :)
If it's not a graphics driver change could it be a change in Wanderer? How would we test Wanderer changes?
Ronny Beck was making changes to update Workbook for Apollo OS. Maybe workbook is sufficiently advanced to show icons on AROS 68k? If it works it could be a problem with Wanderer.
Just a few ideas. :)
-
Thanks, I'll look into this.
-
deadwood I think I have discovered the culprit, now even your Distribution shows well the DualPNG icons with the icon.library present in ROM, as I suspected it is not the fault of your icon.library and it is not the fault of the ROM, I'll finish to do the tests and probably I'll say the culprit, I hope I was not wrong.
miker don't worry you made me do a test that confirmed what I said, given my old age I could also be wrong :)
miker IcarOS uses Dopus5 which handles icons in its own way, this could divert the study, PeterK has also fixed the icon.library for those who use Dopus Magellan.
-
deadwood I think I have discovered the culprit, now even your Distribution shows well the DualPNG icons with the icon.library present in ROM, as I suspected it is not the fault of your icon.library and it is not the fault of the ROM, I'll finish to do the tests and probably I'll say the culprit, I hope I was not wrong.
miker don't worry you made me do a test that confirmed what I said, given my old age I could also be wrong :)
miker IcarOS uses Dopus5 which handles icons in its own way, this could divert the study, PeterK has also fixed the icon.library for those who use Dopus Magellan.
I would place my bets on Wanderer being the culprit. But some system file changed from Mar 2020 till now. And PeterK's Icon Library fixes the problem so that icons display properly.
But I will wait to see what you find. The ROM and Icon Library from ABIv11 is not the problem. I can confirm that also.
-
The culprit is something you are very familiar with, it is a datatype PNG.DATATATYPE :)
AROS relies heavily on datatypes, even executables stop working if there is no datatype :)
I attach a screnshot with the latest Nightly Build and deadwood ROM, I just replaced the png.library and removed the icon shadow when dragging from Wanderer prefs.
-
The culprit is something you are very familiar with, it is a datatype or PNG.DATATATYPE :)
AROS relies heavily on datatypes, even executables stop working if there is no datatype :)
I attach a screnshot with the latest Nightly Build and deadwood ROM, I just replaced the png.library and removed the icon shadow when dragging from Wanderer prefs.
You replaced PNG.Library with what version? An older version?
Don't confuse PNG.Datatype with PNG.Library. Not the same.
Later today I'll try to duplicate your findings.
-
I didn't make a mistake, it's the png.datatypes, the old version I used is v42.0
-
I didn't make a mistake, it's the png.datatypes, the old version I used is v42.0
I just meant that I was curious why png datatype wasn't working.
I don't doubt what you did. I can see the results. Good job! :)
-
No worries my friend, have you tried your Aros 68k if it works well with the old png.datatype!
-
@deadwood:
One thing that I would like to be addressed in Aros 68k, is the "native" (PAL) screen. It needs love.
There are historical software (like Bars & Pipes, Lightwave, DPaint, Scala and others) that currently don't work (or work in part).
They MUST be made working under Aros 68k; a user should NOT be compelled to buy a 30 yo OS from cloanto, or download an illegal copy from the internet, in order to run those programs.
-
AMIGASYSTEM
Sure enough! Replacing PNG Datatype solved the ugly icon problem.
I wouldn't have thought of that till I had exhausted all my other choices.
Thanks for finding that and for fixing the icon display problem.
So the AROS Icon Library is ok. But the PNG Datatype v42.1 is not good. Replace with 42.0
-
Yes maybe now there will be a png.datatype v.43 ;D
The icon.library/png.datatype will probably fix other problems, for example I had a problem with WBDock with the Style Funny that prevented me with Dopus4 to click on "C" to recall the config, I solved it by doing a refresh from the appropriate entry on WBDock, now it works perfectly.
There's still a problem on the WBDock with the MagicWB Style where sometimes the icons remain fixed and cannot be clicked anymore.
The window request GUIs also seem to be improved.
-
@deadwood:
One thing that I would like to be addressed in Aros 68k, is the "native" (PAL) screen. It needs love.
There are historical software (like Bars & Pipes, Lightwave, DPaint, Scala and others) that currently don't work (or work in part).
They MUST be made working under Aros 68k; a user should NOT be compelled to buy a 30 yo OS from cloanto, or download an illegal copy from the internet, in order to run those programs.
There are limits of how far I want to go with 68k. If these problems are solved in ApollOS, let me know and I will happilly port back changes.
-
So the AROS Icon Library is ok. But the PNG Datatype v42.1 is not good. Replace with 42.0
Thanks. It should be relativelly easy to find where regression happened now :)
-
AMIGASYSTEM
Sure enough! Replacing PNG Datatype solved the ugly icon problem.
I wouldn't have thought of that till I had exhausted all my other choices.
Thanks for finding that and for fixing the icon display problem.
So the AROS Icon Library is ok. But the PNG Datatype v42.1 is not good. Replace with 42.0
Found an incompatibility of the Icon.library AROS 68k with some App OS 3.x, the programs to exchange icons "DualPNG" do not work, icons are not managed and the copy does not work, I will test other similar apps OS3
With PeterK's icon.library worked perfectly, icons shown with color and icon swap working
-
Also Dopus4 "Icon Info tool" doesn't show correctly Dual-PNG icons anymore, no colors.
I don't think it's icon.library's fault because on AROS x86 you can see the icons from Dopus4 correctly.
On AROS 68k the only program that allows icon swapping is CopyIcon44 (Aminet), the only problem is that it doesn't show the icons when you drag them on its GUI.
-
on Magellan you do not need that
Open information and drag and drop the new icon on the picture of current icon
Cool :)
perhaps it works for you too
for me it perfectly works and shows correctly on aros 68k using PeterK icon library
-
on Magellan you do not need that
Yes, I know Magellan can do it because it has its own internal icon manager, Wanderer is based on OS 3.1 that didn't have this icon swapping function or change icon function (project, tools etc...)
With OS 3.5/39 these functions have been enabled on the Workbench.
There are tools that enable these functions for OS3.1 it's called "SwazInfo" but on AROS 68k it doesn't work, there is also "Rawbinfo" but it works only on OS 3.5/3.9, also the new OS 3.1.4/3.2 have this function.
-
I add that even on AROS x86 Wanderer doesn't have these "important" functions and there is no tool to swap icons or modify its functions.
-
I add that even on AROS x86 Wanderer doesn't have these "important" functions and there is no tool to swap icons or modify its functions.
it is indded something important for users
-
Wanderer needs Built-in Icon Exchange.
(On a separate thread) ;)
Magellan already has that feature.
-
I don't know how to contact Mazze, if you can do it I thank you ! it's just a matter of time.
I'll probably have no time before Saturday.
-
Thanks Mazze for stepping in, the problem is not urgent
-
@deadwood
There would be another major problem on AROS 68k, the Font Prefs often crashes the system when you want to try and set some system Fonts.
Also it is not possible to change the Font color, very important when choosing a light background, white fonts do not have a good visibility on light backgrounds
-
@deadwood
There would be another major problem on AROS 68k, the Font Prefs often crashes the system when you want to try and set some system Fonts.
Does this happen on ABIv0 as well?
How do you trigger this problem?
-
New ROM: https://axrt.org/development/aros-rom-20211216.zip
Two changes integrated:
Modified path copying in CreateNewProc() so that it was compatible with Workbench
From Gunnar von Boehn - Changed default mouse to something more Amiga like <-- you can observe new cursor in early boot menu for example
I rejected as few changes. A also submitted two fixes to ApollOS repository.
All in all there is only one more change related to improvement in early boot menu left.
-
Does this happen on ABIv0 as well?
How do you trigger this problem?
No on AROS x86 ABI-v0 there are no system crashes, however it lacks the ability to change the color of the fonts
-
Can you try these system files and let me know if crash is there?
https://build.axrt.org/download/builds/AROS-ABIv11/amiga-m68k-20211216-143610.tar.gz
-
It seems to be stable Fonts Prefs in your distribution and your new ROMs, I should test them more time to be sure.ų
The problem could also be caused by the Request Preview Fonts, but I may be wrong.
On my system with your new ROMs the Crash with Fonts Prefs still happens.
-
@Deadwood:
You should commit new changes & fixes in the MASTER branch, so that it can be downloaded from the usual place: http://www.aros.org/nightly1.php
-
@deadwood
With your new ROM today Fonts Prefs seems to be stable also on my AROS One 68k
-
New ROM: https://axrt.org/development/aros-rom-20211216.zip
Two changes integrated:
Modified path copying in CreateNewProc() so that it was compatible with Workbench
From Gunnar von Boehn - Changed default mouse to something more Amiga like <-- you can observe new cursor in early boot menu for example
I rejected as few changes. A also submitted two fixes to ApollOS repository.
All in all there is only one more change related to improvement in early boot menu left.
looks good
I have played around in my distribution without problems
-
Thx for tests
-
New ROM: https://axrt.org/development/aros-rom-20211217.zip
Contains these two changes:
0d0399e504 ("EarlyBootMenu BOOT page improved - Boot selection from a list - Enable/Disable devices from a list", 2021-09-28)
b79a0cd29b ("EarlyBootMenu BOOT page FIXES", 2021-09-29)
Check the new boot devices page in early startup menu for changes.
-
works
-
Sorry deadwood, I haven't tried the new ROM yet because today I was checking some strange things that happen when using SFS with AROS 68k (important because installAROS uses this Filesystem).
In practice in the latest Nightly Builds the file moving from one window to another has been corrected, now in fact if you drag a file from one window to another of the same vulme, the file is moved, in the old Nightly Builds instead of moving only a copy happened.
Well, now I discovered that if you try to drag a file or a folder in a new folder created, you get the error message "Object is in use", see attached video
The problem doesn't exist if you use FFS, PFS or Directory Filesystem.
I add a detail the PFS Filesystem (used PFS3-Aio) as said works fine but AROS 68k recognizes it as FFS Intl
Video Test Error SFS
https://drive.google.com/file/d/1ZfUXZe8S6H-8bmRvR2gIkTvBrkThWM6W/view?usp=sharing
-
Tested the new ROM, perfect, the HardFile PFS-Aio is recognized, also recognized HardFile SFS and CD0
-
Thanks for the tests. This conclused migrating code from ApollOS repository for now.
I will still look into regression in ReqTools as well as regression in png.lbrary v42.0 vs v42.1
-
one could you please also look at... if you f.e. start demos from aminet they work but if you close it then you only get empty screen and have to reboot and not return to OS. Example attached but it affects both applications and demos.
-
Thanks for the tests. This conclused migrating code from ApollOS repository for now.
I will still look into regression in ReqTools as well as regression in png.lbrary v42.0 vs v42.1
thank you deadwood :)
-
Thanks for the tests. This conclused migrating code from ApollOS repository for now.
I will still look into regression in ReqTools as well as regression in png.lbrary v42.0 vs v42.1
Yes ReqTools and png.datatype reported previously are important.
Regarding the test done on the SFS problem on AROS 68k, I tried what happens on AROS One x86, in this system let's say that we are still behind, that is if you try to move a file from a folder to another "of the same volume", instead of moving it makes a normal copy, this should happen if the folders were in different volumes :)
-
@deadwood
I may be mistaken but the problem with displaying png icon images was caused by regression in png.datatype not png.library. When I replaced png.datatype v42.1 with v42.0 per directions from AMIGASYSTEM then the images are correct.
Also Icon Library uses png direct access rather than pngclass. But for v42.1 there were significant changes in both modules.
I hope that helps to clarify.
-
Yes I confirm, correct, I had only made a copy-paste without reading, old age problems :)
-
Yes I confirm, correct, I had only made a copy-paste without reading, old age problems :)
Undersrood. Try reading this forum on a cell phone like I do. :P
-
I don't use my cell phone very much to read on the forums, the screens are too small and then intrusive ads and redirects bother me.
-
@miker1264
Thanks for clarification. I must have made a bad note on this one.
-
one could you please also look at... if you f.e. start demos from aminet they work but if you close it then you only get empty screen and have to reboot and not return to OS. Example attached but it affects both applications and demos.
I will try but chances are slim if this is related to m68k binary compatibility.
-
one could you please also look at... if you f.e. start demos from aminet they work but if you close it then you only get empty screen and have to reboot and not return to OS. Example attached but it affects both applications and demos.
I will try but chances are slim if this is related to m68k binary compatibility.
thanks
-
one could you please also look at... if you f.e. start demos from aminet they work but if you close it then you only get empty screen and have to reboot and not return to OS. Example attached but it affects both applications and demos.
I will try but chances are slim if this is related to m68k binary compatibility.
It's not a m68k binary compatibility issue, but as it happens with many OS3 software it's just a lack of RTG support of the software.
The Andy_and_Blondie Demo can be run several times without causing crashes or reboots if you use a PAL screen
I did a test on WinUAE with two monitors, one RTG and one PAL, Andy_and_Blondie starts automatically on the PAL screen without causing any problems.
WinUAE DoubleMonitor: Demo Andy_and_Blondie
https://drive.google.com/file/d/1bDZAyfvYPeEmZ3V-RG4LsLlUExZnLiW8/view?usp=sharing
-
one could you please also look at... if you f.e. start demos from aminet they work but if you close it then you only get empty screen and have to reboot and not return to OS. Example attached but it affects both applications and demos.
I will try but chances are slim if this is related to m68k binary compatibility.
I do not know if you mean the same
the issue is not that it not works (many demos f.e. work) but if you end it there is only a black screen and you not return to the OS
It's not a m68k binary compatibility issue, but as it happens with many OS3 software it's just a lack of RTG support of the software.
The Andy_and_Blondie Demo can be run several times without causing crashes or reboots if you use a PAL screen
I did a test on WinUAE with two monitors, one RTG and one PAL, Andy_and_Blondie starts automatically on the PAL screen without causing any problems.
WinUAE DoubleMonitor: Demo Andy_and_Blondie
https://drive.google.com/file/d/1bDZAyfvYPeEmZ3V-RG4LsLlUExZnLiW8/view?usp=sharing
-
It's not a m68k binary compatibility issue, but as it happens with many OS3 software it's just a lack of RTG support of the software.
The Andy_and_Blondie Demo can be run several times without causing crashes or reboots if you use a PAL screen
I did a test on WinUAE with two monitors, one RTG and one PAL, Andy_and_Blondie starts automatically on the PAL screen without causing any problems.
WinUAE DoubleMonitor: Demo Andy_and_Blondie
https://drive.google.com/file/d/1bDZAyfvYPeEmZ3V-RG4LsLlUExZnLiW8/view?usp=sharing
The question from me is how it behaves on OS3.1 with RTG. Does it also crash there?
-
On OS 3.1 RTG no problem on "WinUAE", you can exit the Demo and restart it, see video:
https://drive.google.com/file/d/1Otq2YAJlnkvSixcnt4y2RdHcF-31fOPO/view?usp=sharing
-
On OS 3.1 RTG no problem on "WinUAE", you can exit the Demo and restart it, see video:
https://drive.google.com/file/d/1Otq2YAJlnkvSixcnt4y2RdHcF-31fOPO/view?usp=sharing
Ok, thanks. Now I understand the problem.
-
Sorry deadwood, I haven't tried the new ROM yet because today I was checking some strange things that happen when using SFS with AROS 68k (important because installAROS uses this Filesystem).
In practice in the latest Nightly Builds the file moving from one window to another has been corrected, now in fact if you drag a file from one window to another of the same vulme, the file is moved, in the old Nightly Builds instead of moving only a copy happened.
Well, now I discovered that if you try to drag a file or a folder in a new folder created, you get the error message "Object is in use", see attached video
The problem doesn't exist if you use FFS, PFS or Directory Filesystem.
I add a detail the PFS Filesystem (used PFS3-Aio) as said works fine but AROS 68k recognizes it as FFS Intl
Video Test Error SFS
https://drive.google.com/file/d/1ZfUXZe8S6H-8bmRvR2gIkTvBrkThWM6W/view?usp=sharing
I would like to add that some of the reports made in the past were due to the SFS filesystem with the PFS filesystem the errors are no longer there.
These were the reports:
- Moved file is not deleted
- Single icon "from Wanderer" cannot be deleted or copied
With other filesystems the following errors remain:
- Cannot rename icon without file
- Icon cannot be renamed lowercase/uppercase
-
I have tested the newest roms
the gadtools problem (freeze when filesselect opens) is solved
thanks a lot Deadwood :)
from my side only the problem with demos (and other software and games) not correctly closing is the only problem left
-
one additional problem...
on some programs are buttons missing. It seems also related to gadtools. Perhaps you could look at it too
http://aminet.net/package/disk/moni/FileX-68K
about dialog
Buttons can be pressed but are not visible at first
-
https://drive.google.com/file/d/1ZfUXZe8S6H-8bmRvR2gIkTvBrkThWM6W/view?usp=sharing
I would like to add that some of the reports made in the past were due to the SFS filesystem with the PFS filesystem the errors are no longer there.
These were the reports:
- Moved file is not deleted
- Single icon "from Wanderer" cannot be deleted or copied
With other filesystems the following errors remain:
- Cannot rename icon without file
- Icon cannot be renamed lowercase/uppercase
Discovered the cause of almost all the problems found on HardFile SFS! Now only the problem remains "Icon cannot be renamed lowercase/uppercase"
Basically what gave this problem were HardFiles created with HDToolbox on OS3.
I tried to do an AROS 68k installation with InstallAROS and the HardFile initialized and SFS formatted did not give those problems anymore.
About InstallAROS, after installing the latest Nightly Build AROS-20211229-amiga-m68k, I've noticed that when using a RAW HardFile the installation with InstallAROS crashes and restarts the system, but then if you manually copy the system everything works fine with the SFS filesystem
If instead you use a SFS HardFile prepared on OS3 with HDToolBox, installAROS has no problem, but then SFS has the mentioned problems.
Could someone try to do some installation and check if he meets the same problems ?
-
I've tried the latest Nightly Build 68k and the InstallAROS problem persists, I don't think anyone can ever install AROS 68k directly from the ISO, I can't use a real Amiga but I suppose InstallAROS won't work on Amiga too.
From what I can guess the problem is in the HD initialization, I can create a video to show the error.
The problem is solved if you initialize the Hardisk on OS3.9, but SFS cannot be used for the reasons mentioned above.
P.S..
I noticed that on AROS 68k there is the CD command, in my opinion it can be eliminated since the CD Command is in the ROM !
-
I copied my VM in VMWare Player. It's Ubunutu 18.04 64bit.
Then I followe the Install.md instructions to setup Alt-ABIv0.
I built the toolchain and AROS i386 without issues. :)
-
Sorry miker from the translation I did not understand if it is addressed to my report, the problem I mentioned is on "AROS 68k"
-
Sorry miker from the translation I did not understand if it is addressed to my report, the problem I mentioned is on "AROS 68k"
No sir. I was just commenting that I finally setup my x86 Build System. That's all.
I can't seem to compile applications in Contrib though. Hmmm....user error somewhere.
-
I can't seem to compile applications in Contrib though. Hmmm....user error somewhere.
You need to move contrib directory into AROS and do 'make contrib'. Don't symlink contrib into AROS - symlinking does not work.
-
I can't seem to compile applications in Contrib though. Hmmm....user error somewhere.
You need to move contrib directory into AROS and do 'make contrib'. Don't symlink contrib into AROS - symlinking does not work.
There seems to be something in contrib that keeps it from building correctly. But I don't want to build all of contrib just certain items, mostly ones that I put there. So I can place them in a separate subdirectory under AROS/Extras and change the mmakefile.src accordingly. That works.
Is there a separate contrib for ABIv0 or is it the same as for ABIv11 ? My contrib won't build.
-
Yes, there is separate contrib for ABIv0. Same repository, different branch.
https://github.com/deadw00d/contrib/tree/alt-abiv0
-
the problem was that some applications that opened file requester caused errors and then my system freezes, on nightly the system still works but the application stops and there is a error requester. I just see requester open.
example the attached file if you start it from cli without parameters
Hi Olaf,
I tried CLI-Tracker under OS3.1 from shell and it did not display any requester - it silently exited. Are there any dependencies needed for it?
EDIT: Ok, I found it. It was reqtools.library missing.
-
@OlafS3
Do you an example of another (simple) tool that has the same problem as CLI-Tracker?
-
Please try this version of reqtools.library. It should fix the freeze issues:
https://axrt.org/development/reqtools.library-20220118.zip
-
deadwood your reqtools.library on my AROS One 68k generates this error:
-
New package, containing missing libraries:
https://axrt.org/development/reqtools.library-20220119.zip
-
Perfect, also the request file of HippoPlayer works fine, thanks !
-
@OlafS3
Do you an example of another (simple) tool that has the same problem as CLI-Tracker?
If I remember right the last version already solved the freeze problem. There was only the problem that sometimes if a kind of requester opened the GUI seemed not to show the buttons, if you pressed on it the buttons reacted and were shown.
-
From how the bug looked like, it might have been random - sometimes it worked and other times it would not. Now it should work (show file listing in requester window) all the time.
-
From how the bug looked like, it might have been random - sometimes it worked and other times it would not. Now it should work (show file listing in requester window) all the time.
just tested it. That has fixed the problem. Thanks
-
@AMIGASYSTEM, @OlafS3
I'm looking now into the issues of not closing window after running some demos like "Andy_And_Blondie". Do you know if the software that causes this problem is system friendly or does it take over Amiga? AMIGASYSTEM - your video shows kind of dual-screen setup when the demo is running on separate screen. Can you - when the demo is running do anything in Wanderer?
-
Yes, on WinUAE I had configured two screens, one RTG and one PAL, just to avoid the system freezing when the Demo was exited.
On OS3 RTG systems this does not happen, you can exit the Demo and use the operating system
-
What I'm interested in is whether you can use the system while the demo is running?
-
When you exit the Demo you have a gray screen and the system is no longer visible.
-
What I'm interested in is whether you can use the system while the demo is running?
you mean multitasking and system friendly? Certainly not... software like demos squeezzes everything out of the system it can. It takes over the system for sure. Thanks in advance for trying to find the problem. I saw this only with software or demos using PAL screens so I assume the problem are games, demos and software using PAL screens taking over the system.
-
I'm at least giving it a try. It requires m68k assembler debugging from within AROS so it's quite painful...
-
Well, the good news is that I located what triggers the problem, so I don't need to continue debugging asm 68k ;) The problem is somewhere in p96 driver. The same sequence works on amiga chipset driver and on linux hosted driver, but fails on p96. The system actually continues working, you just can't see anything that is displayed. I'll look into the driver issue.
-
Well, the good news is that I located what triggers the problem, so I don't need to continue debugging asm 68k ;) The problem is somewhere in p96 driver. The same sequence works on amiga chipset driver and on linux hosted driver, but fails on p96. The system actually continues working, you just can't see anything that is displayed. I'll look into the driver issue.
great progress ;D
thanks
-
Well, the good news is that I located what triggers the problem, so I don't need to continue debugging asm 68k ;) The problem is somewhere in p96 driver. The same sequence works on amiga chipset driver and on linux hosted driver, but fails on p96. The system actually continues working, you just can't see anything that is displayed. I'll look into the driver issue.
In fact the Video Card on AROS 68k has never worked well, many software have jerky graphics, see AmigaAMP, Dopus4 and many others.
I would like to point out that on AROS 68k the Picasso96 software is not installed! on WinUAE the only working Video Card is UAE-GFX (UAE Zorro III) which is automatically recognized without the need for software
On FS-UAE I don't know which Video Card is recognized, on my Amilator that uses FS-UAE AROS 68k it doesn't work and I think it depends on the unsupported Video Card.
-
Well, the good news is that I located what triggers the problem, so I don't need to continue debugging asm 68k ;) The problem is somewhere in p96 driver. The same sequence works on amiga chipset driver and on linux hosted driver, but fails on p96. The system actually continues working, you just can't see anything that is displayed. I'll look into the driver issue.
Great progress. Troubleshooting can be a tedious process but debugging ASM doesn't sound like much fun in itself.
Thank you for your efforts to make AROS better. :)
-
@OlafS3, @AMIGASYSTEM
Can you give me an example (link) of simple application where I can choose to open a custom screen and I can select PAL mode or an RTG mode with different resolution than current Wanderer screen?
-
Troubleshooting can be a tedious process but debugging ASM doesn't sound like much fun in itself.
I was using native debugger/monitor written in 1994... I didn't even have an AMIGA back then. :O
-
@OlafS3, @AMIGASYSTEM
Can you give me an example (link) of simple application where I can choose to open a custom screen and I can select PAL mode or an RTG mode with different resolution than current Wanderer screen?
Picasso96Modes is not needed and won't work when using uaegfx. All modes are autogenerated and already listed in prefs ScreenMode, see screenmode
-
I'm asking for an application that allows opening a custom screen which I can select from a requester. I'm pretty sure I saw such applications in the past but can't remember now which are those.
-
On AROS 68k I don't remember if there are applications where you can change the resolution, if it's ok I tested FinalWrite OS3
-
On AROS 68k I don't remember if there are applications where you can change the resolution, if it's ok I tested FinalWrite OS3
there are amiga applications where you can select the mode. I will search for it
-
On Amiga there are many (Office programs, Graphics, Music, Games), on AROS 68k not !
-
I'm fine with Amiga applications of course. As long as they start under AROS68k.
-
Yes some of them work but as said they are slow, Finalwrite is unusable too slow :)
-
Ok it seems DOpus can be made to open different screen. This was enough for basic tests.
Here is new ROM package that makes Andie and Blondie demo exit correctly. Let me know how it works for you.
https://axrt.org/development/aros-rom-20220127.zip
-
Perfect, now on AROSOne 68k you can exit the Demo "Andy_and_Blondie" and continue to use the operating system!
-
Ok it seems DOpus can be made to open different screen. This was enough for basic tests.
Here is new ROM package that makes Andie and Blondie demo exit correctly. Let me know how it works for you.
https://axrt.org/development/aros-rom-20220127.zip
For example Amos Pro returns correctly
but demos seems to freeze
-
My pleasure. Debugging asm was kind of fun, but that's not something I want to repeat too often ;)
-
Regarding Amilator I have to correct myself, the Video Card works fine, the failure to boot was due to "JIT", it seems that FS-UAE does not support JIT on AROS 68k, deactivated "JIT" on Amilator AROS One 68k booted quietly even if it is slower.
On WinUAE JIT works fine with AROS One 68k !
-
My pleasure. Debugging asm was kind of fun, but that's not something I want to repeat too often ;)
i DO NOT Want to spoil the fun but for me the demos do not start at all now like this one
-
I have downloaded newest nightly and copied your roms but it seems there is still a problem (screenshot attached)
-
Are these demos working on regular nighlty build (with regular ROMs)?
What CPU/chipset requirements they have?
I tried 1daydemo.exe on reference nightly build that I have and it also does not work.
-
I get always errors
for exmple http://aminet.net/package/demo/ecs/afl_demo
-
I have tried it with the official nightlies... there seem to be also crashes >:(
-
When was it working last time? Do you have ROM and system files with which these demos work?
-
The demos "1daydemo.exe" and "afl_demo" do not support RTG screens this also happens on OS 3 RTG, also afl_demo does not support AGA and does not support Quit.
I don't think these demos can ever boot on AROS 68k RTG.
-
I did a small test to verify the functionality of the new ROMs with the two demos.
If you configure on WinUAE an A1200 with 2MB fast + the two new ROM AROS 68k the two demos work perfectly!
This demonstrates that it is the high CPU and the RTG Graphic Card that do not make the demos work.
-
When was it working last time? Do you have ROM and system files with which these demos work?
I did some testing... I just found a demo that worked and returned correctly to OS. Also another application that had a problem worked now. I did tests with some other demos and it seems that not even on 3.1 everything works. Expecially demos seem to be very sensible. So I think you solved what was possible. 100% is not possible I think. Thanks
-
Made a small video showing how "1daydemo" and "afl_demo" work with AROS ROMs used on an A1200/2MB
https://drive.google.com/file/d/1ymatGtx11akS_sewOiO7bvBh7Ysd2RV5/view?usp=sharing
-
another demo that worked and correctly returned to OS. To me problem seems to be solved
-
one demo I downloaded and unpacked and started in my distribution and returned to OS
thanks Deadwood... for me problem is solved :)
not everything works everywhere but even you cannot do wonder ;)
-
Made a small video showing how "1daydemo" and "afl_demo" work with AROS ROMs used on an A1200/2MB
https://drive.google.com/file/d/1ymatGtx11akS_sewOiO7bvBh7Ysd2RV5/view?usp=sharing
Thanks for confirmation. :)
-
one demo I downloaded and unpacked and started in my distribution and returned to OS
thanks Deadwood... for me problem is solved :)
not everything works everywhere but even you cannot do wonder ;)
Glad we have this sorted out :)
-
@Deadwood
Can you have a look at "compositor", please ?
It 's broken; it can't drag screens in RTG, any more. (since 2020, I think)
-
@Gundam
Created bug report here: https://github.com/deadw00d/AROS/issues/56
-
@deadwood
I may be mistaken but the problem with displaying png icon images was caused by regression in png.datatype not png.library. When I replaced png.datatype v42.1 with v42.0 per directions from AMIGASYSTEM then the images are correct.
Also Icon Library uses png direct access rather than pngclass. But for v42.1 there were significant changes in both modules.
I hope that helps to clarify.
This should now be fixed in 42.3.
https://axrt.org/development/png.datatype_42.3_m68k.zip
-
@AMIGASYSTEM
I think at some point you mentioned that ModExplorerNG is freezing AROS when launching. I tried it with my latest build and it is no longer freezing. Can you confirm the problem has already been solved? For some reason I still had this on my TODO list.
-
With AROS One 68k I had no problems, now works well even the FPU version, I had encountered the block with the Nightly Build, I had reported HERE (https://ae.amigalife.org/index.php?topic=798.120)
I'm glad the problem has been solved, in the next days I'll test better to verify if there are other problems
-
@deadwood
I may be mistaken but the problem with displaying png icon images was caused by regression in png.datatype not png.library. When I replaced png.datatype v42.1 with v42.0 per directions from AMIGASYSTEM then the images are correct.
Also Icon Library uses png direct access rather than pngclass. But for v42.1 there were significant changes in both modules.
I hope that helps to clarify.
This should now be fixed in 42.3.
https://axrt.org/development/png.datatype_42.3_m68k.zip
Thank you.
-
I found this (from 2020):
" dont think i can view a file in your home folder just like that?
you would have to add:
boot/amiga/AROSBootstrap ROM boot/amiga/aros.hunk.gz
at the beginning of your s-s. that with an amiga or linux editor, or notepad++ on windows.
unfortunately currently bootstrapping upon amiga ks is broken anyway. we wait for a fix. ill try to remember to let you know, when it will be worth to test."
Is this still valid or fixed? In UAE I only get a error. I get several lines of "AddMemList" as output and then error #8000000B
-
@deadwood
I must report that the Nightly Build does not include the latest things discussed in this forum, every time I update my AROS One 68k I have to reinsert the various updated files, for example your reqtools.library, Miker's new Datatypes, the Italian keymap that is always the corrupted one.
I think you need a readme in the Nightly Build that lists the updated files so that you can immediately identify what has been updated, avoiding to copy the entire contents of the Nightly Build that maybe contains old libraries or that do not work like the camd.library.
-
@deadwood
I must report that the Nightly Build does not include the latest things discussed in this forum, every time I update my AROS One 68k I have to reinsert the various updated files, for example your reqtools.library, Miker's new Datatypes, the Italian keymap that is always the corrupted one.
I think you need a readme in the Nightly Build that lists the updated files so that you can immediately identify what has been updated, avoiding to copy the entire contents of the Nightly Build that maybe contains old libraries or that do not work like the camd.library.
I have been neglecting AROS lately. I haven't submitted the updated datatypes to the repository. ;D
-
@AMIGASYSTEM
The closes thing there is to the readme you suggest is commit log of repository: https://github.com/aros-development-team/AROS/commits/master. By comparing build dates with commit date you can derive the change.
If you are looking for full system builds with my changes, they can be downloaded from here: https://build.axrt.org/download/builds/AROS-ABIv11/ with commit log here: https://github.com/deadw00d/AROS/commits/master
A more user-friendly description of changes I'm attaching to full releases (see here: https://axrt.org/index.php?tab=releasenotes-aros-v0). For automated builds this won't be available and you need to use commit history as shown above.
-
Thanks for the links, if I understand correctly, regarding the date of the files in the Nightly Build, "all files" and folders contained in the ISO have the same date as the day the ISO was created.
-
Yes, I believe so.
-
I would like to report that on AROS x86 and AROS 68k the XAD library cannot unpack RAR and 7zip archives due to the lack of 7zip clients and the RAR client not working.
On AROS 68k if i use XAD 12.1 OS3 version and its RAR and 7zip clients, these two types of Archives unzip easily, the only problem is that UnARC does not work with XAD 1.21, it requires XAD 13
-
Thanks. Noted: https://github.com/deadw00d/AROS/issues/58
-
Thanks, I add one more important thing, with AROS One 68k thanks to XAD 1.2 with Dopus4 it is possible to click on an LHA, LZX, RAR, 7Zip, BZ2 and TGZ Archive, and turn the archives into a normal folder and use it as such, I attach a video that shows both how to compress and unzip an archive into a folder:
Tutorial Dopus4 archives creation and unpacking in folder:
https://drive.google.com/file/d/1jYpP2fgjIRNG9BgTxrGRgSB3nsyFXesz/view?usp=sharing
Everything seen in the video with Dopus4 on AROS x86 doesn't work, probably Dopus4 x86 version doesn't recognize and use XAD library, XAD option on Dopus4 is added in Icon Tooltype.
Another thing that does not work with Dopus4 on AROS x86 is the display of a text file, Dopus4 recognises it as if it were an executable, we have discussed this problem here in the past.
-
If you are looking for full system builds with my changes, they can be downloaded from here: https://build.axrt.org/download/builds/AROS-ABIv11/ with commit log here: https://github.com/deadw00d/AROS/commits/master
The latest AROS 68k versions downloaded from this link include a bug on Wanderer Prefs, in practice you can no longer change the value in the Tab "Max. Label Line lenght" Tab, see screenshot, in some cases it's difficult to check the boxes below.
I had updated my AROS One 68k and discovered the problem !
-
@deadwood
Found the problem, to generate the bug is the muimaster.library, once replaced with that of the Nightly Build everything works normally.
In your Builds to start the system, after replacing the Nightly Build you must also copy the stdc.library that is not present in your Builds.
-
Thanks, bug report submitted: https://github.com/deadw00d/AROS/issues/62
-
I located the change the created the problem - I'll see about providing a fix, but it might be slightly complex. I'll let you know when a test version of muimaster.library is available.
-
Encountered another problem with EaglePlayer, when exiting the program generates an error, see screenshot
Link EaglePlayer: https://aminet.net/package/mus/play/Eagleplayer
-
Is this something that started happening with recent updates or already existing problem?
-
Did some testing, the problem is present even with my old versions of AROS 68k
-
I located the change the created the problem - I'll see about providing a fix, but it might be slightly complex. I'll let you know when a test version of muimaster.library is available.
I'm having problem providing a logical, good fix for that. Does anyone know active developers forums, especially for OS programming (so not low level assember/demos/games)? I tried posting my questions on EAB but didn't get any answer.
I'll repost my question here as well:
I'm currently looking into an incompatibility with HandleEvent implementaiton in AROS and looking for some help understanding a specific situation. Please note that I'm limiting the scope to handling IDCMP_MOUSEBUTTONS only.
What believe is happening under MUI 3.8 is:
a) Area object is not "eating" a IDCMP_MOUSEBUTTONS event. An event handler registered at priority -20 still received IDCMP_MOUSEBUTTONS event regardless on coordinates of click - even if valid button was clicked.
b) An object that is hidden (MUIA_ShowMe, FALSE) will still receive events via HandleEvent as long as it's event node is not removed via MUIM_Window_RemEventHandler.
Using a button usecase (MUIC_Text), my question is how does and object know that it should handle that click.
In the MUI examples and in open source custom classes I see this kind of code in MUIM_HandleEvent
Code:
if (_isinobject(msg->imsg->MouseX,msg->imsg->MouseY))
Which essentially says: if the coordinates are within my bounds, I should handle the click. This works in the following situation:
Have a horizontal group with two button. Click on left one - the click is not within bounds of right button, so it does not react. Click on the right one, the left one does not react. However, now hide (MUIA_ShowMe, FALSE) right button. What happens is that left button is extended to covert the empty space. Now clicking on where where right button was, because of a) and b) above causes the hidden right button to still receive the event. The right button, although not visible, still retain bounds which make the check above pass. So the hidden right button should react to the click, but obviously it does not.
Does anyone who why the hidden button is not reacting to a click?
The ideas that came to my mind are:
1) The checks in MUI classes check not only coordinates of the click, but also if object is not hidden. However why the would all the examples of custom classes check only coordinates of click?
2) MUI classes remove event handler node as reaction to MUIM_ShowMe, FALSE. However example show manipulation of event handler nodes only in MUIM_Setup/MUIM_Cleanup. Example which have event handler node are not handling MUIM_ShowMe
-
What do yout think of posting it on morph.zone?
They use MUI too on MorphOS (even though the implementation is different of course)
-
Thanks, I haven't considered it, but it may be a good place.
-
@deadwood
On EAB someone has provided some information on your post !
http://eab.abime.net/showthread.php?t=109948
-
there is a small fix on apolloos github
perhaps also interesting for this rom
https://github.com/ApolloTeam-dev/AROS/commit/cefc910dd99968da73df07ff5bbc4caa0f6e067d
-
@deadwood
On EAB someone has provided some information on your post !
http://eab.abime.net/showthread.php?t=109948
It's a good hint. I will look into this further.
-
@OlafS3
I think this fix is specific for ApollOS, see this: https://github.com/ApolloTeam-dev/AROS/commit/57a54ffc4a3952435927fae8ddb93a5df54b4a01
-
yes looks so
I was not sure
-
Ok, this is probably a silly question, but I need help.
I need to install MUI 3.9 on a clean 3.1 installation. MUI 3.9 requires "C:Installer" which is not present on clean 3.1 installation. Where do I get the Installer from?
-
From "Install" disk or here http://aminet.net/package/util/misc/Installer-43_3
-
Thank you. 43_4 worked for me.
-
@AMIGASYSTEM
Please try this muimaster.library (for Wanderer prefs issue): https://axrt.org/development/muimaster.library_19.57_m68k.zip
Note that some elements still might have problems being clicked if they are on different tabs. If you come across such problems, please report them here.
-
Perfect bug fixed, on my configuration however "sometimes" even if rarely it is no longer possible to remove/add the check on the two tabs shown in the screenshot
It might depend on my system, on your Distribution it seems not to happen.
Regarding your latest Distribution I noticed that you are missing the "stdc.library", on my system it seems to be indispensable, without "stdc.library" in system startup I have a request for this library, many applications use it.
-
Ok, glad to hear that. I will still publish another build of muimaster.library with changes for testing before pushing to repository.
About stdc.library - that is correct, my builds no longer have this library. You can switch fully to my distribution (so there is no need for it) or you can keep the one you have and keep using it. This is related to C library changes that I announced in December.
-
Ok, I already use all your Distribution, stdc.library seems to be required is required by some graphical datatype or other sodftware integrated in my system, question, what is it for, and who exactly needs the stdc.library ?
-
stdc.library is another C library implementation. Maybe datatypes/multiview from MikeR require it? He might still be using old SDK?
-
Yes, the miker datatypes require the stdc.library, try to copy all the new miker datatypes in your Distribution and in system startup you will immediately notice the request of the stdc.library.
-
Just keep copying stdc.library for now. Once MikeR commits his hew datatypes to the repository, the problem will be solved.
-
@Deadwood:
ImageFX crashes upon launch (input.device issue).
Can you have a look at it, please ?
here's a lite version of ImageFX: http://os4depot.net/share/graphics/edit/ifx.lha
-
@AMIGASYSTEM
Here is another version of muimaster.library for test. If things are ok, I will push the fixes to repository:
https://axrt.org/development/muimaster.library_19.57_m68k_20220311.zip
-
@Gundam
I'm not currently looking into specific binary compatibility issues for m68k. Probably best would be to approach Apollo OS team about this.
-
@deadwood
However ApolloOS is another world, it doesn't use Wanderer, many system applications are not native AROS but OS3, they use their own KickStart.
Basically if you start ApolloOS with your ROM, the few remaining native AROS applications on ApolloOS don't work, they require the posixc.library and the stdc.library
-
That can you basically also say for my distribution, I also use not wanderer and many applications are OS3. The main branch also benefitted from bugfixes like the fix of the lowlevel library. The same is true in the other direction too of course.
-
Yes, but this will increase incompatibility between systems and there will no longer be an AROS standard.
As I've said many times, if I'm going to use a system with old OS3 applications, it's better to use a native OS3, mixed systems lead nowhere and only create incompatibility, if you want to grow you have to cut out the past.
-
Yes, but this will increase incompatibility between systems and there will no longer be an AROS standard.
As I've said many times, if I'm going to use a system with old OS3 applications, it's better to use a native OS3, mixed systems lead nowhere and only create incompatibility, if you want to grow you have to cut out the past.
:o
*sigh*
I am tired from the discussions outside now they start here too. Amiga the new religion >:(
let people do what they want. Simple as that
-
I don't like to make controversy, I just said what "I" think, everyone is free to choose and say his thought!
I have my A4000/060 in my garage together with all my other Amigas, I have used them for 30 years, now it's time to grow up with AROS I just want to
-
@deadwood
However ApolloOS is another world, it doesn't use Wanderer, many system applications are not native AROS but OS3, they use their own KickStart.
Basically if you start ApolloOS with your ROM, the few remaining native AROS applications on ApolloOS don't work, they require the posixc.library and the stdc.library
I directed Gundam to Apollo OS team, because I believe they have greater incentive to fix these kind of incompatibility issues. Once the fix is done, I will port it back to my repository so the benefit is there.
-
Thanks, hopefully it will be solved, it's not the only OS3 software to have that problem on AROS 68k, AmigaAMP for example after playing an mp3 can't be closed! the latest version of AmigaAMP just ran sends crashes WinUAE.
-
works on winuae but I can't on janus-uae :(
-
@Deadwood:
When trying to run RexxMast (in contrib here: http://www.aros.org/nightly1.php), in YOUR aros 68k distribution, it says it requires posixc.library, but your aros68k distro does not have posixc.library.
You should compile rexxmast and regina.library without that dependancy, so that it can be used in your distribution.
-
That's a good point. I made a note of that and will take care of this once I do major work with core targets. For the time being, you can copy missing libraries from the nightly you mentioned.
-
@deadwood
As mentioned on another post, on Wanderer there are problems to run an application when using the CLI parameter in the Tooltype, in my opinion it is a very important problem.
In practice if you want to run an executable from icon with CLI parameter, the executable doesn't execute any parameters included in the config file.
To check the problem just run the application TKUnpacker (http://web.archive.org/web/20210423224624/http://www.hd-rec.de/Archive/TKUnpacker2.lha).
TKUnpacker allows with a Click to automatically unzip an Archive, on OS3 when you click on an Archive file a request asks where to unzip the archive, on Wanderer instead the request asks the path of the Archive file, if executed you get the error Unknow format or file not found - Ram", practically the archive is not found!
I attach screenshots exhaustive, the problem should also be present on AROS x86
-
In practice if you want to run an executable from icon with CLI parameter, the executable doesn't execute any parameters included in the config file.
What do you mean by "config file"? Can you be more specific what config file you are referring to and what is contains? I'm not familiar with functionality you described.
-
TKUnpacker as soon as it runs looks for and executes its configuration file located in the ENV "TKUnpacker.config".
Wanderer doesn't seem to know how to interpret the script, on OS 3 everything works normally
This problem happened to me also with other applications that work from Workbench through the "CLI" parameter.
-
Ok, bug report created: https://github.com/deadw00d/AROS/issues/64
-
Ok, bug report created: https://github.com/deadw00d/AROS/issues/64
Thanks
-
@ deadwood
On AROS x86 I happened a few times to access "Early Startup Menu", I don't remember if with the two pressed Mouse keys or if from the Spacebar.
It seems to be not easy to access Early Startup Menu, to my important for maintenance, I also noticed that the Early Startup Menu GUI is outdated and the cursor moves by itself, basically you can't boot the system "without startup-sequence" as you can do AROS 68k.
It would be nice to have on AROS x86 the new "Early Startup Menu" GUI that you created on AROS 68k !
-
@ deadwood
On AROS x86 I happened a few times to access "Early Startup Menu", I don't remember if with the two pressed Mouse keys or if from the Spacebar.
It seems to be not easy to access Early Startup Menu, to my important for maintenance, I also noticed that the Early Startup Menu GUI is outdated and the cursor moves by itself, basically you can't boot the system "without startup-sequence" as you can do AROS 68k.
It would be nice to have on AROS x86 the new "Early Startup Menu" GUI that you created on AROS 68k !
You can enter bootmenu by editing grub command line and adding "bootmenu" argument.
The changes to bootmenu will eventually make their way to x86 AROS once it catches up with Core.
-
Ok thanks
-
Bootmenu was active on my AROS One x86, you just had to have the Grub window active and be quick to press the spacebar.
I booted the system from the prompt and ran Dopus4, handy for doing any maintenance when the system doesn't boot.
I would like to put Dopus4 on the Grub so that I can boot AROS directly from Dopus4, is this possible?
-
No, I don't think so without major development.
-
Ok that's ok, I created a little script now at the prompt just type Dopus, noticed that many things work fine like editing text, watch a video listen to music and much more.
I will inform AROS One x86/68k users about this important feature for OS maintenance.
I wanted to create a function key ALT+F1 but there is no Keymaps Editor, FKey unfortunately works only on Wanderer
-
new fixes
perhaps you (Deadwood) could look at it
https://github.com/ApolloTeam-dev/AROS/commit/9bc0a17d5c4702a2a03a2d898cd0009e5b20e5a1
https://github.com/ApolloTeam-dev/AROS/commit/76e477c6682d92ca30a520e7b6f4e1af16d6511b
https://github.com/ApolloTeam-dev/AROS/commit/cefc910dd99968da73df07ff5bbc4caa0f6e067d
-
Yes, I've seen those. I generally wait until there a bigger batch of changes before porting, unless there is something that would immediately help someone.
-
...now there are also problems with languages, you can not change the language to the system.
Catalogs have a version number. AROS applications try to open a particular version number. If it doesn't match the catalog won't be opened and the default language (usually English) is opened.
See here for Wanderer:
https://github.com/aros-translation-team/wanderer/tree/c4d7be1dd5116b26825f721a41435880c3df159c
You can see in file catalog_version.h the version number 4. That's the required version.
But italian.ct has this line
## version $VER: wanderer.catalog 3.0 (08.06.2017)
i.e. it has only version 3.
Someone has to update the ct files.
-
I believe that besides "wanderer.catalog" there are other Italian catalogs with the same problem.
With a Hexadecimal Editor I tried to modify the date of "wanderer.catalog" and it worked, but not everything was lacalized in Italian
-
I believe that besides "wanderer.catalog" there are other Italian catalogs with the same problem.
With a Hexadecimal Editor I tried to modify the date of "wanderer.catalog" and it worked, but not everything was lacalized in Italian
I think that the new version has to be translated first (from scratch if it does not exist or updating the previous version).
When the file has been updated and has all the messages that the new version needs, the catalog has to be generated with flexcat.
Several years ago I tried to update and complete the spanish catalogs and itīs not very difficult:
https://ae.amigalife.org/index.php?topic=651 (https://ae.amigalife.org/index.php?topic=651)
-
Thanks Telematix, I tried FlexCat (it seems to be only for Windows systems) but I have the doubt that the catalogs created are for AROS x86, and not compatible with AROS 68k !
-
I used a linux version, compiled from the AROS sources.
Tried it on linux hosted and, when it had no errors, uploaded the source file to the git server so it can be used.
https://github.com/aros-translation-team (https://github.com/aros-translation-team)
-
@AMIGASYSTEM
The closes thing there is to the readme you suggest is commit log of repository: https://github.com/aros-development-team/AROS/commits/master. By comparing build dates with commit date you can derive the change.
If you are looking for full system builds with my changes, they can be downloaded from here: https://build.axrt.org/download/builds/AROS-ABIv11/ with commit log here: https://github.com/deadw00d/AROS/commits/master
A more user-friendly description of changes I'm attaching to full releases (see here: https://axrt.org/index.php?tab=releasenotes-aros-v0). For automated builds this won't be available and you need to use commit history as shown above.
I have a question. The full builds here are identical to the main branch (http://aros.org/nightly1.php) or your specific branch? The commits on main branch (often from Kalamatee) sound interesting but I am not sure what is what. In my case I am of course mainly interested in ABI11 (68k). I have just tested. With your nightly all is ok, in the main download page the fix seens not to be commited on ABI1. What is difference between both? Identical (including recent fixes and additionally yours) or different and only updated from time to time?
-
Ok, for simplicity:
This repository: https://github.com/aros-development-team/AROS/commits/master
m68k builds are available here: http://aros.org/nightly1.php
This repository: https://github.com/deadw00d/AROS/commits/master
m68k builds are available here: https://build.axrt.org/download/builds/AROS-M68K/
The relations between both repositories is that I, from time to time, mostly every quarter or every half year, take changes from first and apply on second and take changes from second and submit for application on first. 99% of changes gets synchronized this way. Some never do. Then the repositories start living their own life until the next synchronization work.
-
I still do not understand. Are they currently synchron or has it updated again? So for now I will stick to your nightlies
-
Currently, they are not. A synchronization is followed by a new release and last release was on 2022-12-22.
-
On AROS ABI-v1 68k night 2023-08-23, I encountered an InstallAROS Guriucon.
Basically if you go into the Drive 6 Partitioning section. if you try to exit through the "Cancel" Tab you get a Guru, see screenshot.
-
@AMIGASYSTEM
I'd suggest reporting the bug here: https://github.com/aros-development-team/AROS/issues. It might be related to recent changes with how InstallAROS works.
-
Ok i registered and reported !