Wow, that's really great news!

Further 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.

[quote name=ntromans post=10592]@ntromans - Just tried to reset a running emulation via the gui and recieved the attached illegal instruction error. Cheers, Nigel.[/quote] Yes this is a known issue, already fixed, I’ll include it in the next release

Just tried to reset a running emulation via the gui and recieved the attached illegal instruction error. Cheers, Nigel.

Hi 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: [ulist=disc]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 '}'.[/ulist] But, aside from the above, as I said earlier this is working fantastically well :) Thank you! Cheers, Nigel.

[quote name=Deremon post=10583]@Deremon - [quote name=ntromans post=10565]Lastly since amiberry is a direct WinUAE port it will not be really "lightweight" :)[/quote] 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

[quote name=ntromans post=10565]@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: [ulist=disc]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.[/ulist] Some questions: [ulist=disc]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.[/ulist] 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. [/quote] 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" :)

ModePro 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.

Thanks for the tip usign F9: I can get to the GUI now. However, just to confirm holding the alt key (either left or right) does not allow *any* character to be types into an Amberry requester: possibly this is just the for native but in any cas it would not help to give ':' as this is not selected by caps lock, just the shift key. The FinalCalc issues was solved by using 68020 + 68882 (I find 68020 gives the widest compatability with 68k software): FinalCalc is now nice and fast. Intersting though, as setting FPU emulation in Janus gives problems with FinalCalc, so Amiberry is definitely an advancement there. I'm running 1600x900 RTG screens via ModePro on the 68k side and all programs look fine on this (Amiberry is being run in fullscreen mode). Further tests with PageStream4 confirm it works quickly (with JIT enabled). I loaded up a fairly complex dcoument and all rendered correctly and quickly. PageStream2 and DrawStudio also appear to be working fine. In fact, aside from the inability to see files on partitions other than that Amiberry is installed upon, this looks to be working fantastically well! Cheers, Nigel.

To return to the Amiberry graphical interface, press the F9 key. You can change this key in the ‘Miscellaneous/right side’ menu. You can also enable other keys for other functions such as “Quit” or ‘FullScreen’. You can also disable the Amiberry interface at startup from the ‘Miscellaneous’ menu under ‘Show Gui on startup’. If Guru appears frequently, replace the Amiberry executable, which may have been corrupted by numerous tests. I don't know what you mean by request modules, but the ALT key allows you to write in capital letters. The only problem is that some paths do not work well when clicked with the mouse. In this case, it is best to write the path manually. I tested FinaCalc and it is very fast. You need to set a 68040 CPU, preferably a 060, enable JIT and allocate the right amount of memory. I tested it with 512 MB. FinaCalc does not have good visibility in RTG. Use PAL or interlaced PAL video resolutions. Another minor issue ‘with all operating systems’ is that the menus are very slow to respond. You have to wait a few minutes, but this is resolved if you use full-screen mode.

Trying some useability tests: PageStream4 is very useable - fast typing and rendering of graphics elements. FinaCalc on the other hand is running incredibly slowly compared to Janus on a 1.6 GHz atom, far too slow to be useable. I'll need to try playing with some of the CPU, JIT and resolution settings to see if these make any diffrence. Cheers, Nigel.

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.

[quote name=ntromans post=10565]@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: [ulist=disc]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.[/ulist] Some questions: [ulist=disc]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.[/ulist] 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.[/quote] 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. [img]https://www.arosworld.org/infusions/forum/attachments/afaone_1.jpg[/img]

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: [ulist=disc]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.[/ulist] Some questions: [ulist=disc]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.[/ulist] 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.

After a busy Christmas I've only just now had some time to play with this. Bit of a problem straight off; I've installed my 68k system to a different pratition to the Amiberry program but found in the paths panel I can't set the patition name as the string gadget doesn't recognise the shift key so I can't type ':'. I'll try copying Amiberry to the other partition and try again. Cheers, Nigel.

wow great job!

As mentioned previously, here is the new video showing how WHDLoad games can be run directly from the GUI script I created without using the Amiberry GUI. WHDLoad games, which are generally compressed in LHA format, are run by Amiberry using a special procedure that creates and launches a mini-system in a temporary folder unique to each game. The presence of corrupted temporary files remaining in the mini-system will prevent WHDLoad games from starting, and even the presence of default configurations in the Amiberry folder will prevent WHDLoad games from working. The GUI script I created before launching the WHDLoad game will automatically delete the temp folder and the default configuration file, if present. Regarding WHDLoad games, I also discovered that they will not work from a Shell or from my script if the games are located in the Amiberry folder. https://youtu.be/9U2-rTPTrsE

[quote name=amigamia post=10525]@amigamia - That's fantastic news! Thank you for your excellent work. Just a question, does this driver work on AROS 64bit or is it just for 32bit version?[/quote] Thanks. There will be a 64-bit version once it's out of beta (should be a week or two at most).

- Samsung R730 Alteros AR9285 Wireless Adapter it works well now (It didn't work with the old device before.) - Netbook ACER Aspire One ZG5, Foxconn Atheros XB63 (Atheros Ar 5006 Eg802.11 B/g) works well now

Trank you, great work!