Sure, I would be happy to help where I can. Not all emulators work great or I haven't figured them out yet, but the OpenGL did help with some of them, and the Compositing got faster with the updated Radeon Card.
### Added - Added a search field at the top to search for applications among all the categories - Added a new Highlighted section that promotes some applications. This is the default view when Vault starts - Added a Preview window, showing a bigger application image when the user clicks on the small screenshot - Added AutoInstall script for using it with AmiUpdate
### Changed - Changed the left sidebar to have the categories in their own group - Compiled with Hollywood v11
I have a lot of performance issues with emulators on SAM460LE, but I think I installed all the requered stuff. I will double check - eventually may ask you for some support?
If you plan to replace assist with more demanding assets, or you want better controller over input, or scaling or want to use 3d features.
A emulator is demanding, and the game might not run well on a slower computer like sam440, or on Amiga4000/CyberStormPPC or something old like that inside emulator.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Neuer Shell-Prozess 7
7.AmigaOs4:> cd Download:Testen/neu/XTools/
7.Download:Testen/neu/XTools> XenaStatus
Warning: This set of XTools currently only tested on X1000
Setting up x5000
The support for X5000 is UNTESTED!
----------------------------------
If you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.
The only reason you would want to run these tests is to
inform the developer on your progress.
You can abort this process by entering 'q' at any testpoint.
You will be asked to enter something to continue before each test.
YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!
Creating Xena memory space for INDEX reg: e0000000
Creating Xena memory space for DATACHANNEL reg: e0008000
About to do some tests.
Enter 'q' to quit, anything else to continue...
loop-check check1: dead, check2: dead, waits: 24972, i: 5000
-----------------------------------------------------
Performing test with ITimer->MicroDelay 10, with read/write to 0x8000
with read/write to 0x8000. Res in SIG1 is: 0xdead. Should be 0xdead
with read/write to 0x8000. Res in SIG2 is: 0xdead. Should be 0xbeef.
with read/write to 0x8000. Res in REG_HWREV: 0xdead.
with read/write to 0x8000. Read scratch1: 0xdead (don't know what it should be)
with read/write to 0x8000. Read scratch2: 0xdead (don't know what it should be)
with read/write to 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0000 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0001 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0002 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0003 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0004 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x000c is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x000d is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0010 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0020 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0021 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0022 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0023 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0024 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x002f is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0030 is 0xdead 1101111010101101
with read/write to 0x8000. REG:0x0031 is 0xdead 1101111010101101
Tests done.
If you got good values back from test, things seem to work.
If there were good results for the delay 10 test, then you could continue to run
and stuff might work. If no good results were seen then you might as well abort now.
fatal: chain too long returned 128
Enter 'q' to quit, anything else to continue... 7.Download:Testen/neu/XTools>
7.Download:Testen/neu/XTools> XenaStatus
Warning: This set of XTools currently only tested on X1000
Setting up x5000
The support for X5000 is UNTESTED!
----------------------------------
If you'd like to continue, a few tests will be performed.
They will be performed with a varying delay
betweeen the read and writes.
The only reason you would want to run these tests is to
inform the developer on your progress.
You can abort this process by entering 'q' at any testpoint.
You will be asked to enter something to continue before each test.
YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!
Xena memory space is already setup for INDEX reg
FALSE:MEMATTRF_WRITETHROUGH
TRUE:MEMATTRF_CACHEINHIBIT
TRUE: MEMATTRF_SUPER_RW
TRUE:MEMATTRF_SUPER_RW_USER_RW
FALSE:MEMATTRF_NOT_MAPPED
FALSE:MEMATTRF_SUPER_RO_USER_RO
FALSE:MEMATTRF_REFERENCED
FALSE:MEMATTRF_SUPER_RO_USER_RO
FALSE:MEMATTRF_EXECUTE
FALSE:MEMATTRF_RESERVED1
FALSE:MEMATTRF_RESERVED2
FALSE:MEMATTRF_RESERVER3
Xena memory space is already setup for DATACHANNEL
FALSE:MEMATTRF_WRITETHROUGH
TRUE:MEMATTRF_CACHEINHIBIT
TRUE: MEMATTRF_SUPER_RW
TRUE:MEMATTRF_SUPER_RW_USER_RW
FALSE:MEMATTRF_NOT_MAPPED
FALSE:MEMATTRF_SUPER_RO_USER_RO
FALSE:MEMATTRF_REFERENCED
FALSE:MEMATTRF_SUPER_RO_USER_RO
FALSE:MEMATTRF_EXECUTE
FALSE:MEMATTRF_RESERVED1
FALSE:MEMATTRF_RESERVED2
FALSE:MEMATTRF_RESERVER3
About to do some tests.
Enter 'q' to quit, anything else to continue...
loop-check check1: 4, check2: 4, waits: 26287, i: 5000
-----------------------------------------------------
Performing test with ITimer->MicroDelay 10, with read/write to 0x8000
with read/write to 0x8000. Res in SIG1 is: 0x0004. Should be 0xdead
with read/write to 0x8000. Res in SIG2 is: 0x0004. Should be 0xbeef.
with read/write to 0x8000. Res in REG_HWREV: 0x0004.
with read/write to 0x8000. Read scratch1: 0x0004 (don't know what it should be)
with read/write to 0x8000. Read scratch2: 0x0004 (don't know what it should be)
with read/write to 0x8000. REG:0x0000 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0000 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0001 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0002 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0003 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0004 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x000c is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x000d is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0010 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0020 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0021 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0022 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0023 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0024 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x002f is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0030 is 0x0004 0000000000000100
with read/write to 0x8000. REG:0x0031 is 0x0004 0000000000000100
Tests done.
If you got good values back from test, things seem to work.
If there were good results for the delay 10 test, then you could continue to run
and stuff might work. If no good results were seen then you might as well abort now.
fatal: chain too long returned 128
Enter 'q' to quit, anything else to continue... 7.Download:Testen/neu/XTools>
7.Download:Testen/neu/XTools>
I repeated the test once and you can see it in the output, which then showed completely different values. I'm not sure if that's the way it should be.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
I had bought a Radeon Rx 550 card for my A1222+ which I have not assembled yet. And thanks to that great chart (thanks sailor for the tip), I see that is supports everything.
For fun, I put it in my AmigaOne 500 without updating the uboot. No output from uboot, but I read about this, however once I put the Radeon RX driver into kickstart, it booted into OS 4.1 no problem.
I did buy the Radeon HD V5 driver to have and the Warp 3d Nova Bridge as well and I do have Enhancer V2.2 installed. Anyways, I looked up how to probably install Warp 3D, minigl, opengl, etc and the post from kasel1 was invaluable. I had a lot of old Warp 3d stuff on here and I had to get rid of Warpz since I had a proper 3d card now.
After I did all that, it is amazing to see this old AmigaOne 500 play movies in high definition with no problem, gl screenblankers work beautifully, I have even tried some gl games and they work great. The best part, I love emulators, and they are running better with the help of opengl support and ScummVm looks great now!
This is one tough motherboard is all I can say (I have had it running non stop for over 13 years and still has the original uboot). I did order a new ROM chip with the latest uboot from Acube so I hear that will solve the RX Uboot problem. But to be honest, don't need output from Uboot once you have uboot setup.
I want to thank everyone that has done the great work on these drivers. Way to go guys! And of course A-Eon and Hans.
The only complaint is we as a community need to simplify this process a little. I can see how a new person to the AmigaOne seen would be a bit confused by all this.
Testing Cloud Sync for upcoming Version on different Systems:
Move an copy list items to another list has still to be implemented....everything else works fine. Also tested a bit on Android. Sync works there as well
BTW: Find new Downloadlink for Linux PPC Version in Post 20
Find new Downloadlink for Linux PPC Version in Post 20
Yep, on modern systems the parts written in assembler may also be rewritten in C, after all there are only a bunch of files, but I have no idea of the feasibility or difficulty
@MigthyMax That looks great actually! Thanks! It seems you have rev 2.2 (that 2210 value). The manual I have is for revision 2.1. I wonder if that is different from those who have tested the XTools? Are there even different revision in circulation, or should all X5000 be the same?
I mean, it looks good from uboot. Don't quite understand why it looks different when done from AmigaOS.
it’s better than what I get with my PiStorm32-CM4 and OS3.2.3. I get blank spaces on the opening screen. NovaCoder said on EAB it’s most likely to P96.
@ NovaCoder
great to see you here
Hi mate :)
Yes it seems to have trouble with the newer Individual Computers builds of P96. When I get time, I'll change my development tools over to use the newer P96 to get it working.