AROS ABIv0 20180415 Development

[deadwood]

It has been moved to Development/Debug/Hardware drawer.

[Amiwell]

ok thanks

[AMIGASYSTEM]

It has been moved to Development/Debug/Hardware drawer.

Sorry deadwood, if I understand correctly we can replace PCITool that we had in Utilities with the v0.8 of PCITool that is in "Debug/Hardware drawer" ?

I take advantage to ask you a question, I have created some icons to perform links with OpenURL, on OS3 they work perfectly on AROS x86 I get errors, see screenshot

[deadwood]

I will move PCITool back to previous location in next build.

With regards to the crash - can you share the icon with me that causes this on my clean build so that I can debug?

[AMIGASYSTEM]

I attach link your ISO "20180415-1" with my icons inside, you can find them in the folder Extras

You have to add OWB (I tried all versions)

https://drive.google.com/file/d/1Vv1UTXQWpxMH0GxpqWxmoAx8LTQmoY7m/view?usp=sharing


On your Distro you have the old version OpenURL package, on Aminet there is a newer version OpenURL v7.18, I attach link

http://aminet.net/package/comm/www/OpenURL-7.18

[deadwood]

Which version of OpenURL causes crash? From my ISO or the one from Aminet?

[AMIGASYSTEM]

With both

EDIT

Amigapage icon generates error followed by crash, this is because link it uses protocol HTTPS

[magorium]

- Wireless network drivers (atheros) if they still work

Unable to test because not supported (same behaviour as previous release)

info: 04:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01)

- Nvidia accelerated 3D - does it still work? is it as fast as reference version

Unable to test because no output (almost (*) same behaviour as previous release)

A question: see info below, should it be supported ? (because according to the sources it should)

info: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1)

When time permits i'll check further to see if a) aros crashes, b) driver is not displaying output on the HDMI connector that i have connected or c) the driver is displaying video that is out of range of my monitor

* the thing that is different is that in the previous release, just when the boot process tries to display something to the screen, i was able to detect some random red, green and blue lines (not straight lines but more diagonally, seems random) on my screen before turning black and my monitor starts to display that it is not receiving an input signal.

In this release there are no such red, green and blue lines, other then an empty black rectangle the size of the monitor to look at 

- HDAudio - check for regression on your hardware

Seem to work as intended for me.

info: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06)

Although i did not test this release extensively yet the usual suspects (Wanderer, pcitool, Trident, shell, some examples etc) seems to work for me like the previous release did.

[deadwood]

Thanks!

[nikos]

Here everything works as normal on my DELL Latitiude D520 

3D hardware speed is same as before. Tried GL test and one game.

[AMIGASYSTEM]

@deadwood
If it is of interest, I installed AROS on my Aspire 5920 (what you see in the screenshot), both the audio (Intel High Definition), Video Card (NVIDIA GeForce 8600M), and the Wireless Card (Intel Pro 3945ABG 802.11a/g/n) are not supported.

[miker1264]

@deadwood

I submitted a PR for ABIv1 for updates to Picture Datatype.

I added DT_WRITE to Save ILBM Pics with 8bitplanes and below and ILBM Deep Images with 24bitplanes.

I also added two new methods in "methods.h" and "pictureclass.c". These methods are PDTA_GetNumPictures and PDTA_WhichPicture. They are intended for datatypes dealing with files that contain multiple images such as TIFF files or Icon Files. It is currently working with INFO Datatype.

I'm working on updates for ILBM Datatype, TARGA Datatype and PCX Datatype. I also wrote a new TIFF Datatype in the last couple weeks. I'll provide that here as well. It uses Tiff Lib.

Here is the DT_Write Function to Save ILBM Images:

[deadwood]

@miker1264

I'm currently doing some spring gardening, so no much time spent on AROS. For ABI_V0 its probably best if you publish your updated datatypes on AROS-archives for people to use (together with sources). I will either grab your changes from AROS master or if you want you can submit PR to my repository master (https://github.com/deadw00d/AROS).

Do I understatement correctly that the methods you mention are not part of "3.1 compatibility" for datatypes but new extension methods? If they are extensions, have you made sure they are not using IDs already allocated to extension methods of other platforms (3.1.x, 4.0, MorphOS)?

[miker1264]

@deadwood

In the next couple of weeks I will be installing wood flooring and doing some other spring chores. So I know what you mean. 

In the last few weeks you have worked very hard and contributed greatly to AROS. Some rest and relaxation doing spring chores is well deserved. You and Mazze are the maintainers of AROS now that Nick has disappeared again. Michal Schultz is off working on his own projects or maybe he joined the AROS 68k team.

I don't mind contributing directly to the ABIv0 repository if you don't mind my wild caveman coding style. I make the code work and I test it as much as possible but it sometimes requires fine tuning. The substance is there but it is sometimes rough around the edges.

The two new datatype attributes are the same as used for Amiga OS4. I was trying to use INFO Datatype that was originally intended for OS4. In order to get both icon images I needed the two new attributes (get/set methods). They are ULONG values similar to NumColors. I'm writing three new dataypes for AROS.

[miker1264]

@deadwood

TIFF Datatype works and it can Load and Save 24bit images. But I have interesting issues to look into for that one as far as interaction with MultiView. It uses TIFF Lib which is a Link Lib.

The ILBM Datatype has been missing a Save Function for many years. About a year ago I added code to Save ILBM for saving images with 8bitplanes and below. Now I am ready to add support for saving images with 24bitplanes - SaveRGBPic.

Both functions - SaveBitMapPic and SaveRGBPic took over a year of research and testing on my part. I had to learn everything about ILBM Images. I also assembled the code to convert 24bit RGB to Save As HAM6/HAM8. That was very difficult to do.

Late last year I added the functionality of SaveBitMapPic to Picture Datatype. When I tried to enable DT_Write Framework I realized that Mazze had already done that part. But the important part was missing. At the time no one knew where to insert the Save ILBM code to enable MultiView to Save As IFF.

I found it though by enabling debug. When attempting to Save As IFF the debug gave a "Not Yet Implemented" error. So I did a search for the error string to find DT_Write in Picture Datatype. Then I inserted my Save ILBM (SaveBitMapPic) and it worked. Likewise, now I'm ready to add support for SaveRGBPic as well.