@geennaam

I totally get where you’re coming from,

AEON, ACube-System or Hyperion is making money, selling your free work is illegal, I totally and I get it, if there is no agreement for distribution, it breaks the copyright end of story.

I do not get what some users have problem with that, they really hard on Hyperion for using free contract work, but at end of day, it should be developers who chose to work for free or not. And if its not paid for its no one’s business how your software is shared or distributed but your own.

And right now we come companies like Cloanto who want to take ownership of AmigaOS and its components by legal trickery, without paying the contractors. From my point of view, it be best to not bundle anything with AmigaOS. To avoid legal entanglement.

@TheMagicSN

Perhaps if you wrote a small DOUBLE class with setter and getters.
you can get around this mess, perhaps some macros pointing to the class.

CPPFLAGS = -Ddouble=doubleClass

or

#define double doubleClass

using a ref, you should get address of, insted value, perhaps better for inline asm. when you don't have a real float or double.

doubleClass::doubleClass();
void doubleClass::operator=(int &value);
void doubleClass::operator=(float &value);
void doubleClass::operator=(double &value);
void doubleClass::operator=(doubleClass &value);
doubleClass &doubleClass::operator+(doubleClass &value);
doubleClass &doubleClass::operator-(doubleClass &value);
doubleClass &doubleClass::operator*(doubleClass &value);
doubleClass &doubleClass::operator/(doubleClass &value);
doubleClass &doubleClass::operator();

@amigakit

That might be, but OS4 used the OLD API’s to find the screen-modes in P96 driver.

@amigakit and joerg

As I remember Picasso96 has shared ownership between Hyperion and Individual computers.

http://wiki.icomp.de/wiki/P96

Technically P96 was replaced by graphic library, but P96 API is used in AmigaOS4 graphic drivers. While Individual computers has opened the development docs, it’s not open for anyone to write a driver for AmigaOS4.x, as it has big holes.

@smarkusg

If I understand you correctly, you fixed few bugs, got it working well.
Nice work.

@AmigaOldskooler

Thanks for long summary, I have barely have time to mess around with anything. I really enjoy reading about what other people have done.

@TheMagicSN

Good summary, I hope more people will buy it when they see the advantage.

@skynet

What would this allow me to do?

use a different driver, get around the problem

@skynet

There is AmiDVD in the Amiga Store, you can buy.

MakeCD should work, maybe your CD/R drive is not supported.

wow they are giving away sil3112 this days..
do you have old school PCI slots.

https://www.aliexpress.com/i/1005002598521420.html

@skynet

Commercial software has advantages and disadvantages, even if was open source, it does not guarantee continued development. Development will continue for sure, but some part of it is already frozen in time. Due to the types of contracts and agreements, some developers did not sell their time under a normal work contract instead they licensed out their software to be bundled. Software can be replaced. But it takes a lot of time and will of course misdirect develop resources that we do not have a lot of.
Several times there has been bounties, collect money to buy the source to open source it, and sometimes source code is acquired by Amiga KIT or Hyperion, but it can be many years too late. Sometimes developers come back, after many years of absence.

@white

Amigaworld.net used to be AmigaOS4.x forum, but it was impossible to talk about anything because everything was trolled on, by other camps, inclusivity destroyed it. sad but true.
Idealism did not work.

@Raziel

if stack is:

02 VAR1
04 VAR2
06 VAR4

you pass a ref to 04, and then replace the stack,
as then something can't access 04 anymore, so you have crash.

if swap out stack and use different stack.
but do not free the old one, you coninue on:

4000 VAR5
4004 VAR6

if you resotre the stack before exiting your function.

@orgin

They have amigaworld.net for that..

@vagappc

Anything is possible if you have the right people working on it, and is willing to spend the time, even sometimes even the wrong people get something done, often is a question of being willing to try, and while you might not be 100% successful, the attempt in the self can be educational.

@vagappc

And DOSBOX, and PCX and PcTask

@Rob

I got the impression trixie, was the person working on it, if so, he probably knows better.

@densho

True, but it runs on top of UAE like install, so emulation takes care of that.

@smarkusg

Looks like one of GUI elements perhaps overwrites the lower border in that program as well.

The calculation of inner Height should be:
InnerHeight = Window->Height – Window->BorderTop – Window->BorderBottom;

http://amigadev.elowar.com/read/ADCD_ ... cs_3._guide/node03D5.html

When opening window, you have WA_InnerWidth, WA_InnerHeight, that preferable to WA_Width and WA_Height.

Scaling should be automatic in Reaction and MUI, but in older GadTools the developer is responsible for scaling and placement of Gadgets.

(I believe MPlayer calculates border size before opening window, using screen title.)

@Magic

No it should be simple just run Hyperion’s AmigaOS4.1 updater tool, (not the AEON one.)

@smarkusg

The author most likely does not have AmigaOS4.1 system, he just lucky getting it working so well,
in any case I try to recommended to everyone in forums using shared amiga libraries, this is what he is using.

I do not know if its because I or some was a pain in the ass. But it’s possible.
(Pretty sure it’s not open source, we can’t look at it, or compile a native version.)

Actually, someone figured it was good idea a long time a ago, before AmigaOS4.1, I see used on Music disks etc, but not so common in the old days, not sure when they started putting player routines in Amiga libraries. Most crap has statically compiled in player routines.

Not sure about instability, noticed it crashes on some music modules, its probably not the gui itself, that’s buggy, most likely its libraries / player routines that has bugs. The OS4.1 preplay.libaray did not have support for vumeter, its worth having good look at stack trace and what module crashed, before reporting bugs.

There are cases where bug is found in old code because the old code did not use semaphore / mutex protection, the bugs go undetected on 68K systems simply because there no memory protection, and if the bug is not triggered often, it can go undetected. If bug happen in forbid state, grim reaper is triggered, and it locks up intuition. But you will find crash log on the RS232 port, in the DumpDebugBuffer of the OS4.1 kernel.