@daveyw

It is writing to stderr. To redirect that, use *>

e.g. Delete RAM:ThisDoesntExist *>NIL:

@kas1e

I experienced the exact same thing with the fan coming off. I overcame it the lowest tech way possible ... I keep the motherboard facing up so my mini-tower must lie on its side.

@LiveForIt

I don’t know what opcodes they are but the address looks suspiciously like something trying to access the Amiga chipset.

Thanks Walkero. This could be really handy!

It's interesting that you should notice this yesterday. I noticed the same thing, also yesterday but specifically with FAT32 drives that had been inserted into a Windows 11 machine. The USB message on the Amiga says it could not recognise the drive though the Win 11 PC has no issue.

I grabbed a different USB stick from a drawer that wasn't used much and it showed up.

I wonder if something changed with the FAT32 format that the OS4 driver doesn't know about.

@LiveForIt

Nah. We haven't needed an extension before. Why start now?
Plus DOS/Windows will execute a .bat file without you needing to type the extension, but you would have to include the extension to run it from Amiga which is not that helpful really.

@broadblues

Amazing once again.

Merry Christmas to you!

@NinjaCyborg

I guess not, and I don't know either.

However, I do know that Hyperion has a forum for it. Perhaps you can ask there.

It is https://forum.hyperion-entertainment.c ... 8490151ad2f71b8edd900392a

@alfkil

Unfortunately the link gives a 404 error.

@broadblues

Amazing! Such talent.

Yes, start with checking FailAt. Increase it and see if that helps.

@Daedalus

Yes, you are correct. Thanks Daedalus.

@TSK

Yes, definitely read the manual and FAQ. There is much useful information there.

As to your memory issue, a FFS partition using 512 byte blocks (usual set up) requires about 1MB of memory per GB from my understanding. If you have a 2GB partition then that explains about 2MB or RAM being chewed up. Try 2KB or even 4KB blocks and see what that does for you ... but read the FAQ to verify and catch anything I may have forgotten or misremembered here!

Also, see the FAQ on AmiNet for answers to almost all the questions you are likely to have.

http://aminet.net/package/docs/help/AmigaOS_3.2-FAQ

@TSK

The minimum is 2MB of RAM but it also requires a hard drive so it can be installed on a vanilla HD Amiga 1200 *AS LONG AS YOU USE 3.2 ROM*

If you still retain the 3.1 or 3.1.4 ROM then extra memory will be needed to load the required modules which takes the minimum RAM required to 2.5MB.

If you have the 3.2 ROM installed then there is no need to load those modules into RAM.

@amigakit

What about these situations then?

1. The user chooses not to install your commands/components of the same name but then want to install some software of yours in the future that requires those? There is no choice then?

2. The user chooses to install your commands/components of the same name but then Hyperion update os 4.1 and that clobbers your installed components, where both now have different capabilities? Worse, programmers expect that opening a version number of a library will ensure that a particular API exists (I am thinking of your datatypes.library here, now and in the future) and so programs will start crashing unexpectedly. You can't expect Hyperion to respect any API additions you make when releasing a new version because your API is not part of AmigaOS, yet masquerades as such by using the same name and versioning.

For those reasons they simply should be different names. Then programmers can choose to support your (possibly superior) library functionality optionally by attempting to open your library, call your command, etc.

I know there doesn't seem to be any chance, but I really wish this could be addressed.

I do also understand that you are trying to move development forward without being tied to lawsuit results et al but that can definitely happen with different names.

@amigakit

It's great that you are writing software to support and/or enhance the experience for AEON customers ... just don't give the programs the same name as those supplied in AmigaOS itself. Simple!

@NinjaCyborg

A GUI Amiga program will always use shared memory as it is required for the message passing from Intuition to the program.

@NinjaCyborg

If it were ported/created, what hardware would be used?

@arfcarl

Just set it in your Makefile. That's what I do.

gcc with -lstdc++ seems to work but I changed it to be g++ which implies the stdc++ lib.

I think my compiler setting (with -lstdc++) was before I started modifying the Makefile directly and so is not needed with g++.