AROS World Exec
Development => Development (General) => Topic started by: deadwood on April 07, 2023, 12:24:10 PM
-
Hi All,
As mentioned in development plan, I'm not moving to next release of ABIv11 based on work done in Q1 2023.
Here is reference ISO: https://axrt.org/development/aros-pc-x86_64-alpha-3.zip
Here is first ISO: https://axrt.org/development/AROS-202304XX-D1-pc-x86_64-boot-iso.zip
The following problems are known issues to be addressed:
- InstallAROS does not install Development directory
- Shutting down in VirtualBox no longer works
- Warm reboot causes crash
- When using SATA, disk names are not automatic pre-filled in InstallAROS blocking installation
- Configuring NVMe disk in VirtualBox causes booting to freeze
Please report regression compared with reference ISO on your hardware. If you have NVMe disk in your hardware, please try if installing on it works using new nvme.device.
Changelog:
AROS ABIv11 202304XX-D1 changes:
Functionalities:
Implemented network driver for certain nVidia chipsets (Neil)
Synchronize Zune configuration across all builds (deadwood)
Restore build and functioning on pc-x86_64 AROS (deadwood)
Make native kernel more reselient in case of early error (deadwood, Kalamatee)
Added broadcom4400.device network driver (Neil)
Synchronize on use of ISO-8859-2 for Polish across all builds (deadwood)
First working version of nvme.device is available (Kalamatee)
Implemented FORMAT64 and SEEK64 commands in ahci.device (Kalamatee)
Stabilized handling of WARM reset, implemented missing shutdown handlers (Kalamatee)
Requesters add scroll bars if too much text is shown (Kalamatee)
64-bit support:
Correct size of fpos_t and ino_t C library types (deadwood)
68k support:
ARM support:
muimaster.library (bugs: MUI_Request not compiling) (deadwood)
Restore build of armhf AROS (deadwood)
Updates:
AROS build system (Kalamatee)
libz 1.2.13 (Kalamatee)
libpng 1.6.39 / png.library v53.2 (Kalamatee)
freetype 2.13.0 / freetype2.library v6.6 (Kalamatee)
libudis86 (Kalamatee)
Functional fixes:
Correctly handle __stdiowin when also using C library (deadwood)
gl.library (bugs: race condition during initialization) (deadwood)
hostgl.library (make it work with newer 64-bit hosts) (deadwood)
exec.library (bugs: wrong disassembly due to wrong start address) (deadwood)
ata.device (bugs: media insert/eject detection not working) (deadwood)
muimaster.library (bugs: MUIA_String_Acknowledge not readable) (deadwood)
png.datatype (bugs: 1-bit APLHA pngs not supported) (deadwood)
fat-handler (bugs: partition check too strict) (deadwood)
InstallAROS (bugs: not working with > 2GB RAM) (deadwood)
dos.library (bugs: SFS not working with > 4GB RAM) (deadwood)
C:Install-Grub2 (bugs: not working with > 4GB RAM) (deadwood)
GCC (bugs: sometimes generates non-loadable executables) (deadwood)
Kernel (bugs: wrong configuration of IRQ pins in IO-APIC) (deadwood)
Area.mui (bugs: events sent when not expected to) (deadwood)
pciusb.device (bugs: EeePC USB boot not working) (Neil)
Register.mui (bugs: tab text cannot be formatted) (deadwood)
String.mui, Area.mui, Cycle.mui (bugs: setting same value is causing notification) (deadwood)
pciusb.device (bugs: too long boot delay on AspireOne ZG5) (Neil)
ntfs-handler (bugs: accessing non existent entries) (Kalamatee)
DiskInfo (recognize more filesystems) (Kalamatee)
pciusb.device (workaround for MosChip MCS9990, detect addtional ports) (Kalamatee)
Kernel (bugs: SSE registers not preserved during interrupt) (Kalamatee)
timer.device (bugs: can issues interrupt after warm reboot) (Kalamatee)
C:Decoration (bugs: wrong rendering of paletted pngs) (Kalamatee)
Stability fixes:
graphics.library (bugs: boot driver not unregistered correctly) (deadwood)
MultiView (bugs: crash in About window when using amigaguide.datatype) (deadwood)
exec.library (bugs: crash when showing disassembly in alert requester) (deadwood)
Prefs/ScreenMode (bugs: crash on certain drivers) (deadwood)
acpica.library (deadwood)
-
Just one question: does it support trimming?
-
Meanwhile thanks deadwood do some tests
-
deadwood, I did some tests on VMware, ABIv11 is very fast, Wanderer is very fast, all System Applications work fine, these are the anomalies found on VMware which then are the ones already reported for the previous buil.
- Network does not work
- Mplayer cannot be associated with an Icon (works very well if you drag Video or Music Files)
- USB devices must be mounted later after AROS is started (if mounted earlier Wanderer crashes)
-
- Mplayer cannot be associated with an Icon (works very well if you drag Video or Music Files)
Thanks for the tests. Is this happening when the video file has it's own icon or when you associate the video file via def_Icon or both?
-
I created a comprehensive video where you can see what I described !
https://drive.google.com/file/d/1Uh19B3UWpTBww812pW00I9wIQC12BWgh/view?usp=share_link
-
Ok, thanks for the video.
-
deadwood, I did some tests on VMware, ABIv11 is very fast, Wanderer is very fast, all System Applications work fine, these are the anomalies found on VMware which then are the ones already reported for the previous buil.
- Network does not work
- Mplayer cannot be associated with an Icon (works very well if you drag Video or Music Files)
- USB devices must be mounted later after AROS is started (if mounted earlier Wanderer crashes)
How do you mount a USB device before AROS starts? Do you mean just attaching the device in VMWare or VirtualBox then starting AROS or trying to use it as a boot device?
I'm not having that problem when I attach the USB device after AROS starts. But I haven't tried to boot from USB.
-
I am not talking about Booting from USB, that works fine !
On WMware if you mount the Pendrive on AROS and" leave it mounted", if you reboot "cold", AROS will crash before loading Wanderer
If instead you unmount the pendrive before rebooting, on reboot everything will work
-
I am not talking about Booting from USB, that works fine !
On WMware if you mount the Pendrive on AROS and" leave it mounted", if you reboot "cold", AROS will crash before loading Wanderer
If instead you unmount the pendrive before rebooting, on reboot everything will work
Have you tried different USB devices? On VMWare I have left my Philips USB 2.0 drive attached and restarted the VM. It doesn't cause a problem. I will do some more testing to see if I can recreate the freeze you mentioned.
-
Yes I have tried several different brand pendrives, even external USB HDs are not seen by AROS ABIv11 if the automount of "WMware and active
With ABIv0 this never happened, and it works regularly even now.
-
I get a similar problem with USB drives if they are attached to VMware at boot. With one SFS stick (an Icaros installation which I presume 64-bit AROS doesn't try to boot from), Wanderer starts but hangs immediately after showing the desktop. With a FAT stick, Wanderer only hangs after I double-click its icon.
I also find that USB volumes inserted after boot stay on the desktop after being removed from the VM.
-
I also find that USB volumes inserted after boot stay on the desktop after being removed from the VM.
I have two USB ports on the front of the PC, if I connect the Pendrive on the first USB port, the pendrive removes right away.
On the other hand, if I connect the Pendrive on the second USB port, the pendrive is removed after about thirty seconds
On both ports, once the pendrive is removed, if I reinsert it, it is no longer mounted !
-
I get a similar problem with USB drives if they are attached to VMware at boot. With one SFS stick (an Icaros installation which I presume 64-bit AROS doesn't try to boot from), Wanderer starts but hangs immediately after showing the desktop. With a FAT stick, Wanderer only hangs after I double-click its icon.
I also find that USB volumes inserted after boot stay on the desktop after being removed from the VM.
I have noticed the second problem as well when the mounted volume icon stays on the workbench screen even after it has been removed.
Also, in some cases on ABIv11 icons that are left out on Workbench refuse to be put away. They remain on the workbench screen just like the USB disk icons.
-
I did some tests with other builds regarding the USB-attached-at-boot bug:
"alpha-1": bad
"alpha-3": bad
2023-03-19 (32-bit ABIv1): good
2023-04-08 (64-bit ABIv1): bad
2023-04-08 (32-bit ABIv1): broken (doesn't boot, even without USB drives)
-
I also did some tests with various builds regarding the networking regression. The test I did was as follows:
1. Open network prefs, add an interface, keep the default PCNet driver, click Use.
2. Run "ifconfig net0" a few times with some seconds waiting in between, and check if a DHCP address has been assigned.
Results:
"alpha-1": bad
"alpha-3": bad
"alpha-4": bad
2023-04-xx-d1: bad
2023-03-19 (32-bit ABIv1): good
2023-04-08 (64-bit ABIv1): bad
2023-04-08 (32-bit ABIv1): does not boot
EDIT: these tests were with VirtualBox.
-
Thanks for reporting network and USB problems. They are documented here for future solving:
https://github.com/deadw00d/AROS/issues/99
https://github.com/deadw00d/AROS/issues/98
FYI, I was thinking of adding pc-x86_64 ISOs to official releases but with existing problems that is too soon. I will continue with these builds as "alpha" status until the major issues are resolved.
-
In my Acer Aspire 5630 and HP Z400 Workstation does not boot in native mode or vesa, reference iso works fine on vesa
-
@Amiwell
Can you please try this ISO on your hardware?
https://axrt.org/development/aros-pc-x86_64-alpha-4.zip
-
do not work deadwood, again i can use only the laptop acer aspire 5630 for testing
-
without the module i8042.hidd it works but the keyboard doesn't go and only in vesa
-
Ok, for me to understand correctly:
alpha-3 works in VESA with module i8042.hidd
alpha-4 works in VESA but only when module i8042.hidd is removed
D1 - does not work in VESA even with module i8042.hidd remove
Is that correct understanding?
-
no
alpha 3 works whitout module i8042
alpha 4 works whitout module i8042
d1 do not works maybe whitout module i8042 yes works
ps. I forgot Happy Easter and thank you
-
Can you then check D1 without module i8042.hidd and report?
-
ok i will try again
-
Hello,
New ISO is available, fixing mostly issues with boot: https://axrt.org/development/aros-pc-x86_64-alpha-5.zip
There are two more open topics before the release is made, unless some other major problems are found.
Open topics:
- Regression in Cycle.mui when clicking cycle gadget
- MPlayer does not play video when video opened from icon
Fixed:
- Shutting down in VirtualBox no longer works
- Warm reboot causes crash
- When using SATA, disk names are not automatic pre-filled in InstallAROS blocking installation
- InstallAROS does not install Development directory
- Configuring NVMe disk in VirtualBox causes booting to freeze
- Warm reboot on VirtualBox and Qemu
- nvme.device crash in VirtualBox when booting
- i8042.hidd delays/freezes boot on certain hardware
- crash in pciusb.device when booting
Wont-fix:
- USB mouse/keyboard is only detected is connected during boot
- Delay ~10 seconds when booting SATA disk
- nvme.device/SFS error in VirtualBox when installing
-
ok deadwood test it on my acer aspire 5630 at moment
-
deadwood works fine on default mode the system utilities and programs also works
-
Thanks for testing :)
-
After doing an installation on USB stick the mouse pointer is not seen, the command "c:partition" at the beginning gave me problems doing wipedisk from the system installer everything crashed the first time, only after a restart and repeating the operation worked
-
Yes, I've seen some problems with USB live installation as well. Once a partition was created from InstallAROS, I had to format it from Wanderer menu only then I was able to run second stage of InstallAROS on it.
-
With the alpha 3 build I was able to install the system on USB stick without problems on HD I encountered problems I could not install it the pointer was visible
-
Did some testing with AROS ABIv11 alpha-5
VMWare Player:.
- Installation to HardFile done correctly, no problems
- Development folder installed correctly
- Reboot and Reboot Cold, worked fine
- Dopus4 did not work well
- Installation on Pendriver worked fine, only once I got a Guru with InstallAROS (Wipe Disk -> USB)
Native Mode:
Tried booting Pendrive and I get error, I think it is on Filesystem !
-
deadwood there will be an update of gallium because I thought if aros now supports SATA and NVMe devices to take a more performing laptop not again in the future since you also want to implement the layer for 32-bit software :)
-
I'm not planning on updating 3D system, at least not this year.
-
@AMIGASYSTEM
For MPlayer not playing video when clicked on file, it seems to be MPlayer bug. Here is a new version, let me know if it works for you: https://axrt.org/development/MPlayer-x86_64-20230427.zip
-
deadwood, this version of MPlayer works fine, problem solved, it happens though that a guru appears now and then when you exit video.
-
I'm not planning on updating 3D system, at least not this year.
ok thanks
-
deadwood there will be an update of gallium because I thought if aros now supports SATA and NVMe devices to take a more performing laptop not again in the future since you also want to implement the layer for 32-bit software :)
There's still issues with nvme on some machines. or maybe it's the number of drives.. :D
-
deadwood, this version of MPlayer works fine, problem solved, it happens though that a guru appears now and then when you exit video.
Be sure to have enought stack set on the icon. If you start MPlayer from a video, the stack is take from video icon / def icon not from MPlayer icon.
-
Ok solved, I had high Stack "210000" on Video/Def Icon, then changing the icon had reset the stak to zero
-
There's still issues with nvme on some machines. or maybe it's the number of drives.. :D
I wait for further changes and fixes and it will be necessary to understand which new cards will support the new graphics engine however there is no hurry
-
Deadwood there are fixes or there will be on the TCP stack at least in this version of AROS
-
@Amiwell
I don't understand your question.
-
Ok solved, I had high Stack "210000" on Video/Def Icon, then changing the icon had reset the stak to zero
Ok, I'll upload new MPlayer release to archives in coming days
-
@Amiwell
I don't understand your question.
I meant there will be an evolution of the TCP stack
-
I haven't seen anyone working on it.
-
ok deadwood thanks
-
if I don't use the usb mouse the pointer is visible
-
Hello,
New ISO is available, fixing mostly issues with boot: https://axrt.org/development/aros-pc-x86_64-alpha-5.zip
There are two more open topics before the release is made, unless some other major problems are found.
Open topics:
- Regression in Cycle.mui when clicking cycle gadget
- MPlayer does not play video when video opened from icon
Fixed:
- Shutting down in VirtualBox no longer works
- Warm reboot causes crash
- When using SATA, disk names are not automatic pre-filled in InstallAROS blocking installation
- InstallAROS does not install Development directory
- Configuring NVMe disk in VirtualBox causes booting to freeze
- Warm reboot on VirtualBox and Qemu
- nvme.device crash in VirtualBox when booting
- i8042.hidd delays/freezes boot on certain hardware
- crash in pciusb.device when booting
Wont-fix:
- USB mouse/keyboard is only detected is connected during boot
- Delay ~10 seconds when booting SATA disk
- nvme.device/SFS error in VirtualBox when installing
For those who are stuck on a black screen on native with NVME drives try adding NVME=disable to your boot line.
-
I Installed on VB and it seems to be running well.It booted well after install and auto and chose 1024x768.Looks awesome already! Network configuration recognized PCNet after i hit the add.Very Excited about this 64 Awesome work!
-
I Installed on VB and it seems to be running well.It booted well after install and auto and chose 1024x768.Looks awesome already! Network configuration recognized PCNet after i hit the add.Very Excited about this 64 Awesome work!
It's good that it's working for you. My x86-64 installation works in Hosted Mode on Linux. It's just that I don't have mouse and keyboard at the boot screen so I can't choose the screen resolution. I have to use the default settings.
-
It's just that I don't have mouse and keyboard at the boot screen so I can't choose the screen resolution. I have to use the default settings.
miker, you can solve it safely by copying the "screenmode.prefs" file to SYS:Prefs/Env-Archive/SYS
You can copy the "screenmode.prefs" that you use on AROS x86
-
Hi All,
The new release is now completed and can be downloaded from:
https://github.com/deadw00d/AROS/releases/tag/ABIv11_20230430-1
https://axrt.org/downloads-aros
Below you will find final change log. Thank you everyone who tested this version. Enjoy using this release :)
I also prepared another alpha ISO, this time combining core system with contrib programs, including C and C++ compiler: https://axrt.org/development/aros-pc-x86_64-alpha-6.zip
Here is a list of known issues for the ISO:
- USB mouse/keyboard is only detected is connected during boot
- delay ~10 seconds when booting SATA disk
- nvme.device/SFS error in VirtualBox when installing
- possible NVME crash on some hardware, add 'NVME=disable' to grub command line as a workaround
- if you experience issues booting, try adding 'noacpi' or 'noioapic' to grub command line
Change log
AROS ABIv11 20230430-1 changes:
Functionalities:
Implemented network driver for certain nVidia chipsets (Neil)
Synchronize Zune configuration across all builds (deadwood)
Restore build and functioning on pc-x86_64 AROS (deadwood)
Make native kernel more reselient in case of early error (deadwood, Kalamatee)
Added broadcom4400.device network driver (Neil)
Synchronize on use of ISO-8859-2 for Polish across all builds (deadwood)
First working version of nvme.device is available (Kalamatee)
Implemented FORMAT64 and SEEK64 commands in ahci.device (Kalamatee)
Stabilized handling of WARM reset, implemented missing shutdown handlers (Kalamatee)
Requesters add scroll bars if too much text is shown (Kalamatee)
64-bit support:
Correct size of fpos_t and ino_t C library types (deadwood)
68k support:
ARM support:
muimaster.library (bugs: MUI_Request not compiling) (deadwood)
Restore build of armhf AROS (deadwood)
Updates:
AROS build system (Kalamatee)
libz 1.2.13 (Kalamatee)
libpng 1.6.39 / png.library v53.2 (Kalamatee)
freetype 2.13.0 / freetype2.library v6.6 (Kalamatee)
libudis86 (Kalamatee)
Functional fixes:
Correctly handle __stdiowin when also using C library (deadwood)
gl.library (bugs: race condition during initialization) (deadwood)
hostgl.library (make it work with newer 64-bit hosts) (deadwood)
exec.library (bugs: wrong disassembly due to wrong start address) (deadwood)
ata.device (bugs: media insert/eject detection not working) (deadwood)
muimaster.library (bugs: MUIA_String_Acknowledge not readable) (deadwood)
png.datatype (bugs: 1-bit APLHA pngs not supported) (deadwood)
fat-handler (bugs: partition check too strict) (deadwood)
InstallAROS (bugs: not working with > 2GB RAM) (deadwood)
dos.library (bugs: SFS not working with > 4GB RAM) (deadwood)
C:Install-Grub2 (bugs: not working with > 4GB RAM) (deadwood)
GCC (bugs: sometimes generates non-loadable executables) (deadwood)
Kernel (bugs: wrong configuration of IRQ pins in IO-APIC, TaskReady list damaged) (deadwood)
Area.mui (bugs: events sent when not expected to) (deadwood)
pciusb.device (bugs: EeePC USB boot not working) (Neil)
Register.mui (bugs: tab text cannot be formatted) (deadwood)
String.mui, Area.mui, Cycle.mui (bugs: setting same value is causing notification) (deadwood)
pciusb.device (bugs: too long boot delay on AspireOne ZG5) (Neil)
ntfs-handler (bugs: accessing non existent entries) (Kalamatee)
DiskInfo (recognize more filesystems) (Kalamatee)
pciusb.device (workaround for MosChip MCS9990, detect addtional ports) (Kalamatee)
Kernel (bugs: SSE registers not preserved during interrupt) (Kalamatee)
timer.device (bugs: can issues interrupt after warm reboot) (Kalamatee)
C:Decoration (bugs: wrong rendering of paletted pngs) (Kalamatee)
i8042.hidd (bugs: regression in mouse detection) (deadwood)
crt.library (bugs: wrong time returned by clock_gettime) (deadwood)
Stability fixes:
graphics.library (bugs: boot driver not unregistered correctly) (deadwood)
MultiView (bugs: crash in About window when using amigaguide.datatype) (deadwood)
exec.library (bugs: crash when showing disassembly in alert requester) (deadwood)
Prefs/ScreenMode (bugs: crash on certain drivers) (deadwood)
acpica.library (deadwood)
-
deadwood, thanks for the new ISO, the parameter "NVME=disable", of precise where should it be placed ?
-
This parameter is only needed if you have NVME hardware in your machine and AROS does not boot. It needs to be added to kernel command list in GRUB (same ways like 'noacpi' and 'noioapic' options)
-
OK
-
deadwood I have a new laptop I know it's soon but I will test aros x64, I can't boot from usb even if I disabled secure boot from bios so I took an external cd reader that must arrive I will let you know
-
deadwood I have a new laptop I know it's soon but I will test aros x64, I can't boot from usb even if I disabled secure boot from bios so I took an external cd reader that must arrive I will let you know
There's a good chance you still won't be able to boot until XHCI is finished being fixed by kalamatee if that's a USB CD Drive.
-
I have two USB 2.0 compatible ports
-
I have two USB 2.0 compatible ports
Needs to be USB compatible chipset not a usb 2 port via legacy emulation.
-
ah ok thanks from the boot menu the stick is not recognized, the same with linux is recognized
-
Amiwell go to the Bios and verify the Boot Menu options, it may be that USB Boot is disabled !
-
everything is ok in the bios the boot from usb is active
-
Strange to me it starts on all PCs, tried all the ports USB? on the PC when you avii it the Choice Menu comes out?
--- Ita ----
Strano a me si avvia su tutti i PC, provato tutte le porte USB? sul PC quando lo avii esce il Menu scelta?
-
It is a new generation computer aros is not seen from a usb stick i also tried your distribution, linux and windows are recognized.
At this point I just have to try to boot with an external cd reader, however only x86_64 abiv11 I can try I have a nvme disk and achi system there is no legacy mode
-
OK then it may be that it depends on AROS !
-
I'll keep you updated especially because the computer has a network card that should be compatible you also have an nvidia graphics card that should be recognized with the next gallium update so let's see :)
-
Tested AROS ABIv11, and integrated on AROS One 64Bit, the system I see it much more stable, the incompatibilities with the software included Extras and in Contrib remain.
With Dopus4 nothing has changed, it is not usable, you can't configure or change anything, otherwise text disappears from buttons, also frequently crashes !
-
ah ok thanks from the boot menu the stick is not recognized, the same with linux is recognized
the EFI stuff needs to be on a fat32 formatted drive according to Kalamatee
-
ok I understand
-
Finally had some time to download a copy of ABIv1, specifically the alpha 6 iso, for testing. All of my testing will be native.
First impressions are, really fast! Stabillity wise it feels pretty solid and great to see 4 GB being recorded by AROS. I've been able to boot both from the ISO and USB after using the install AROS tool. One very small issue with the latter - I had to manually format the partition on the USB after creating it before I could install the system.
A couple of bumps in the road - my Celeron desktop has a (fairly old now) Nvidea Geforce; works fine under ABI0 but ABI1 thought it was IntelGMA and crashed out, so I had to boot under VESA. I also tried the USB on a HP laptop (Elitebook). Audio on that works fine under AHI under ABI0 but, whilst it does produce output for ABI1, every sound output produces this error in the attahced image. The USB boots on a another HP laptop but I cant't check audio for that as it's not supported (same as ABI0).
Loking forwards to trying out ABI1 further,
Cheers,
Nigel.
-
@ntromans
Thanks for the tests. At this point you indeed should assume that VESA is the way to go as well as AHI won't work correctly.
PS. The alpha-6 ISO is ABIv11 - it's different than ABI1 from official repository.
-
@ntromans
Thanks for the tests. At this point you indeed should assume that VESA is the way to go as well as AHI won't work correctly.
PS. The alpha-6 ISO is ABIv11 - it's different than ABI1 from official repository.
Of course - I appreciate very much 'work in progress'.
A few further tests:
Networking - unfortunately the HP Elitbook does not have a supported WiFi card, so I'm having to use a Netgear 8180 dongle which is tempremental under ABI0. I always found I got a moie consistent connection to the router if I executed startnet, then stopped the network using stopnet, and then restarted. Trying this (when I issued stopnet) caused an error in bsdsocket (please see attached). Wirelessmanager put up its icon but did not show any networks or connect to my router (output below).
I tried some of the demos; quite a few worked fine but 'teapot' threw up the error shown below.
Finally, when I tired to 'ctrl-alt-delete' to reset the computer I recieved an error from the shutdown process; when I tried to click on .more. the machine reset to bios.
Cheers,
Nigel.
-
Wirelessmanager output:
-
'Teapot' error:
-
For Teapot try to increase stack to something like 1MB and see if that helps.
-
For Teapot try to increase stack to something like 1MB and see if that helps.
Increasing the stack by 100x briefly helped but then it threw out an untrapped signal error ('abort' called 'before program startup'). It complained about an unknown CPU error - jpg attached in case it is of any value tot he wider development process.
Cheers,
Nigel.
-
@ntromans
I tried reproducing teapot problem on linux-hosted where debugging would be easier, but I can't get it to crash. This has to be something related to native build. For the time being I won't be investigating this problem.
-
@ntromans
I tried reproducing teapot problem on linux-hosted where debugging would be easier, but I can't get it to crash. This has to be something related to native build. For the time being I won't be investigating this problem.
Of course - just putting up any information that may be of use :)
Cheers,
Nigel.
-
Even on X86 some Demo included in the "GL" folder went to Guru, today I found out how to avoid the guru, the GL folder was included on the next version of AROS One.
-
Due to Aros-Exec shutting down this thread is now locked and moved to arosworld.org
https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1119