Amiberry preview-v6.3.4 x86_64 - alpha!
Last updated on 1 day ago
AMIGASYSTEMDistro Maintainer@ntromans - OK, up an running now. Booted into workbench with no errors and was able to start Pagerstream4; this is as far as the tests go so far but initial observations are:
- With JIT turned on it's fast :)
- RTG emulation works and I was able to run on a custom screen.
- Looks to be working fine with Amiga Forever roms and rom key.
- I was not able to use shift key again in hard-drive/drawer requester so again I was unable to set drawers in other particitons. Also I found that once an emulated partition was set you can't edit it; if you want to make any changes you have to delete the entry and cerate again from scratch.
Some questions:
- Will resolutions greater than 800 x 600 will be avaialble at some point?
- Is it possible to have more that 64MB of Z3 ram? In Janus I normally run with 512MB ram.
- Is it possible to bring up the Amiberry GUI from Exchanged rather than just remove the program.
Anyway, I'll test furter but looks like an incredibly strong relese for an alpha - really brilliant :)
Cheers,
Nigel.
P.S. tests ae on native 64 bit aros running an Intel i5 processor.
If by resolutions you mean those of the Workbench, you can have as many resolutions as you want. See my attached screenshot of my AfA One (OS3.9 BB4 +AfA OS) resolution 1024x768.
What OS do you have installed? Have you installed the RTG libraries?
As for RAM, you can safely set it to 512 MB, see screenshot. Read the first few pages of the post.
For the Caps Lock key, hold down the ALT key and then type the letter.
Regarding closing the GUI, I don't understand what you want to do! to exit the Amiberry GUI, you can set a key of your choice.
AMIGASYSTEM attached the following image:
ntromansSenior Member
Posted 13 days agoEdited by ntromans on 04-01-2026 11:11, 13 days ago
ntromans attached the following image:
AMIGASYSTEMDistro MaintainerntromansSenior Member
Posted 12 days agoAMIGASYSTEMDistro MaintainerModePro is an excellent Screenmode Promotion to use in RTG with native PAL programmes 
Regarding the Alt key, I still don't understand, I think you hold it down while typing!
I made a short video showing the problem with some paths that don't work with the mouse, but you can solve it by typing manually. In the video, you can see that I type in capital letters using the Alt key.
Regarding the Alt key, I still don't understand, I think you hold it down while typing!
I made a short video showing the problem with some paths that don't work with the mouse, but you can solve it by typing manually. In the video, you can see that I type in capital letters using the Alt key.
DeremonMember
Posted 12 days ago@ntromans - OK, up an running now. Booted into workbench with no errors and was able to start Pagerstream4; this is as far as the tests go so far but initial observations are:
- With JIT turned on it's fast
- RTG emulation works and I was able to run on a custom screen.
- Looks to be working fine with Amiga Forever roms and rom key.
- I was not able to use shift key again in hard-drive/drawer requester so again I was unable to set drawers in other particitons. Also I found that once an emulated partition was set you can't edit it; if you want to make any changes you have to delete the entry and cerate again from scratch.
Some questions:
- Will resolutions greater than 800 x 600 will be avaialble at some point?
- Is it possible to have more that 64MB of Z3 ram? In Janus I normally run with 512MB ram.
- Is it possible to bring up the Amiberry GUI from Exchanged rather than just remove the program.
Anyway, I'll test furter but looks like an incredibly strong relese for an alpha - really brilliant
Cheers,
Nigel.
P.S. tests ae on native 64 bit aros running an Intel i5 processor.
-----
Hmm, I thought the first post said that only 800x600 worked for fullscreen... Thanks for the tip, I have been able set a higher resolution via screenmode (Picasso96 RTG installed on the Amiga side), which is a definite advantage over Janus where you have to set the fullscreen size before launching the emulation.
Being able to go back to the gui is useful for quickly changing some options (e.g. contents of a floppy drive) rather than fully shutting down and restarting: this is possible in Janus but not a must-have I guess.
I'm getting an occasional crash on startup - plese see attached image.
Holding down 'alt' does not allow any character to be typed into the paths requester on native. I have added the other partitions by editing the hardrive path to leave the ':' present from the default path presented and then typed in the remainder of the partition name. However, once in the emulation on selecting the partition in a file requester I can't see its contents, i.e. it seems the emulated system cannot 'see' across partions.
Cheers,
Nigel.
P.S. on native i5 setting tooltype NATMEM_SIZE=512 works giving 128MB od Z3 ram but setting NATMEM_SIZE=1024 prevents the emulator from starting (either does not start at all or gives the privilidge violation error). Not due to a lack of memory - this machine has 8GB installed.
Sorry I could not connect much these days I'll try to give you some extra info
First, thank you very much for the detailed testing on a real hardware AROS, there are some things that behave differently from any other AROS "version" (hosted or native under VM), for example if you use the button Paths>Rescan ROMs it will crash, you can only do it on native under VM and hosted at the moment.
Fullscreen is limited to 800x600 (no matter what you choose in the upper box), if the PC cannot fullscreen to a real 800x600, for example if you use VESA > 800x600, it will automatically switch to "full-window", can be ok but it is slower especially on older machines, in any case if you want to use a "fullscreen" > 800x600 you have to go for full-window.
Another consideration to be made is that amiberry is designed to use SMP which ABIv0 and v11 does not have at the moment so it cannot "offload" the load.
Having "real" full screen > 800x600 is on the to-do pile so it may not be "soon"
As @AMIGASYSTEM said F9 is the default key to bring the GUI up, you can change it in any saved .uae configuration setting amiberry.open_gui=<key> or change it from the GUI and save the .uae file, lastly you can edit conf/amiberry.conf to change the default setting.
I can confirm amiberry linux let you click alt+shift to make a colon, I have to investigate that, at the moment you can use the line editing workaround provided by @AMIGASYSTEM
The crash you are seeing are there if you do an "avail FLUSH" from shell before starting amiberry? This is also linked to the NATMEM_SIZE question, "indirect JIT" is not working (even if selected it will use direct JIT) so you have to use only 32bit addresses for memory and you cannot assign the >2GiB range since is 64bit.
Also amiberry will allocate the NATMEM_SIZE size, if specified, in a single big chunk of memory, if 32bit memory is "fragmented" due to previous usage it will crash, using NATMEM_SIZE=1024 will work if used after an avail FLUSH?
If not, you have to "find" the maximum memory between 512 and 1024 that can be allocated so amiberry can calculate a bigger size for Z3
Lastly since amiberry is a direct WinUAE port it will not be really "lightweight"
Edited by Deremon on 05-01-2026 15:48, 12 days ago
pixieMember@Deremon - [quote name=ntromans post=10565]Lastly since amiberry is a direct WinUAE port it will not be really "lightweight"
I hope that having a minimal system running underneath would help in the user experience, having less lag and hickups... but it might not do all that jazz I reckon
ntromansSenior Member
Posted 11 days agoHi Deremon,
Thanks for the feedback. As mentioned, overll it's working fantastically well on my i5; the only major issue I've found is not being able to 'see' files on other partions from within the emulation.
From your feedback:
But, aside from the above, as I said earlier this is working fantastically well Thank you!
Cheers,
Nigel.
Thanks for the feedback. As mentioned, overll it's working fantastically well on my i5; the only major issue I've found is not being able to 'see' files on other partions from within the emulation.
From your feedback:
- I set NATMEM_SIZE to 1024, rebooted the machne (so nothng aside from the programs started at boot was running) and did avail flush. Unfortunately, Amiberry still refused to start. On changing NATMEM_SIZE back to 512 I had the priveledge violation error and had to reboot.
- Re. fullscreen, this is odd. As Amigasytem suggested, I used screenmode prefs in the emulated AmigaOS to change to 1600x800 and this definitely giving a custom screen at 1600x800 for the emulation (I can drag down the Wanderer screen to see this custom screen). I do agree though it bascially just ignores the resolution set in the Amiberry gui.
- Re. Amiberry string gadegets, just to confirm whilst you can get capital letters by pressing shift, no combination of shift, alt or ctrl gives ':' or indeed any other special character that needs shift such as '$', '*' or '}'.
But, aside from the above, as I said earlier this is working fantastically well
Thank you!Cheers,
Nigel.
Edited by ntromans on 06-01-2026 09:14, 11 days ago
ntromansSenior Member
Posted 2 days agoFurther testing. Not only does the Hollywood X gui/compiler run under the emulation, its possible to compile an AROS x86 executable (to then run via emuv0) using it, meaning for 64bit it's now possible to develop using Hollywood without going back to 32 bit - great stuff
Cheers,
Nigel.
Cheers,
Nigel.
4 users reacted to this post
retrofaza, Deremon, aha, Argo
deadwoodAROS Dev
Posted 1 day agoYou can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You can download attachments in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You can download attachments in this forum.
Moderator: Administrator