Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
24 user(s) are online (14 user(s) are browsing Forums)

Members: 2
Guests: 22

sailor, BillE, more...

Support us!

Headlines

Forum Index


Board index » All Posts (joerg)




Re: Mount HDF on OS4?
Just can't stay away
Just can't stay away


@LiveForIt
For example for FFS/FFS2 partitions it should work if you make a copy of a single partition, something like "cp /dev/sda3 partition3.hdf" on Unix, but it can't work for SFS partitions since they include the offsets of the first and last bytes on the HD of the partition in it's root blocks, and it's checked when mounting partitions.
If the values don't match mounting the partition is aborted by the file system to prevent data corruption.
In such a single partition SFS HDF file those 2 values would have to be changed to 0 (first byte) and file size -1 (last byte) in both root blocks of SFS to make it work.

Go to top


Re: Mount HDF on OS4?
Just can't stay away
Just can't stay away


@broadblues
If the HDF file includes a RDB, i.e. it's an image file of a complete HD with several partitions, there should be no problems.
If the HDF is an image of a single partition instead you may need to set the correct values in the DOSDriver/MountList for it (LowCyl, HighCyl, Surfaces, BlocksPerTrack, etc., and of course the correct DOSType), and with some file systems, for example SFS, it can't work at all if the source of it had different LowCyl, etc. values than the HDF file.

Go to top


Re: Recompiling MiniGL 68k ?
Just can't stay away
Just can't stay away


@TheMagicSN
Quote:
As to the "AmigaOS" requirement and legal stuff I cannot say much .
It's in https://www.hyperion-entertainment.com ... es/updates-kc/License.txt
Quote:
1. MiniGL may only be compiled for/incorporated in/linked with code running on
AmigaOS running on Amiga branded or Amiga licensed hardware. This only applies to MiniGL, you are free to port an
application using MiniGL to another OpenGL implementation on other
platforms.
[...]
Other use will require a special license. Contact the authors for details.
Using it on other OSes like AROS or MorphOS, hardware like Pegasos2 (even when running AmigaOS 4.x on it), Vampire, A600GS, etc., as well as on emulation like UAE, Fellow or QEmu, is obviously not allowed without first getting a special licence from the Friedens.

Go to top


Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
Just can't stay away
Just can't stay away


@FlynnTheAvatar
Quote:
I tried to rewrite it as
if ((ULONGglob->prwin <= || !glob->prwin->UserPort
         
|| (glob->prwin->UserPort->mp_SigTask != ThisProcess()))
An unsigned integer (ULONG, uint32, etc.) can't be < 0, only signed integers (LONG, int32, etc.) can.
Try
if ((LONGglob->prwin <= || !glob->prwin->UserPort
         
|| (glob->prwin->UserPort->mp_SigTask != ThisProcess()))

Go to top


Re: NetSurf 3.11 has been released!
Just can't stay away
Just can't stay away


deleted double post

Go to top


Re: NetSurf 3.11 has been released!
Just can't stay away
Just can't stay away


@Chris
Quote:
There's an open source reimplementation of Notepad++, it needs Qt5 though so not an easy port. https://github.com/dail8859/NotepadNext
We have https://github.com/elfpipe/amiga-qt6
Probably misses a lot of parts available on other OSes, but might be worth a try?

Go to top


Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
Just can't stay away
Just can't stay away


@FlynnTheAvatar
Quote:
Arexx fault or ReqTools?
If it's checking struct Process pr_WindowPtr it's ReqTools fault.
Possible values for pr_WindowPtr, check for example https://wiki.amigaos.net/wiki/AmigaDOS_Data_Structures :
1. A pointer to a window. The requester is opened on the same screen on which this window is.
2. NULL: The requester is opened on the default public screen (usually Workbench).
3. -1/~0/0xFFFFFFFF: DOS requesters are disabled. If I understand the m68k assembly code from GrimReaper correctly, I never did any m68k asm programming and might be wrong, the code fails to check for that case and tries to access 0xFFFFFFFF+0x56=0x55 which causes the invalid data access (zero page) DSI.

If I'm right the DAR (on most PPC CPUs, on 405/44x/46x CPUs it has a different name) of the crash should be 0x00000055.


Edited by joerg on 2024/12/1 16:14:55
Go to top


Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
Just can't stay away
Just can't stay away


@FlynnTheAvatar
Quote:
Is there is way to extract the exact location of the failing code in the 68k library from the GrimReaper?
Should be in the stack trace and disassembly of GrimReaper, it supports emulated m68k code as well.

Go to top


Re: NetSurf 3.11 has been released!
Just can't stay away
Just can't stay away


@nbache
By default locale.library converts the strings from the charset of the .catalog to the system default one. If it's not possible to convert a char because it's not in the destination charset you get a '?'.
Using the OC_WantedCodeSet tag of OpenCatalog[A]() the program can get the strings in a different charset, incl. UTF-8 (106).

In case the MIBenums are not in the locale.library docs: AmigaOS 4.x uses the IANA standard https://www.iana.org/assignments/chara ... sets/character-sets.xhtml
Additionally to the internal UTF-7/8/16/32 ones only the 8 bit charsets stored in L:Charsets are supported. Missing ones can be created with C:BuildMapTable.

@LiveForIt
You could open the catalog twice, for example
catalog_8bit ILocale->OpenCatalog(NULL"foobar.catalog", ..., TAG_DONE);
catalog_utf8 ILocale->OpenCatalog(NULL"foobar.catalog", ..., OC_WantedCodeSet106TAG_DONE);
Use the strings from catalog_utf8 in the parts of your program supporting Unicode and the strings from catalog_8bit for parts like menus, window/screen titles, etc. which only support 8 bit strings.

Go to top


Re: NetSurf 3.11 has been released!
Just can't stay away
Just can't stay away


@nbache
Even if you don't want to switch to an editor with Unicode support like lite-xl but keep using your favourite, 8 bit only, text editor there are tools like C:CharSetConvert and you can use something like
CharSetConvert foobar_ISO-8859-15.ct ISO-8859-15 foobar.ct UTF-8
to convert it to UTF-8 before using CatComp (or replacement tools) to create the UTF-8 .catalog file from the .ct file.
Except for executing an additional command to create the UTF-8 .catalog file all you have to do is to set "## codeset" to the UTF-8 "mibenum" 106 in the .ct file.

Go to top


Re: Sam460LE - linux Debian / Ubuntu instalation questions
Just can't stay away
Just can't stay away


@Hypex
Quote:
That's good to know it can modify existing images.
It can't, it only supports adding it to new images, but if you mount an ISO image with something like diskimage.device it's no problem to create a new one from an existing one.

Quote:
Are the older AmiDVD restricted to pre-FE? I recall reading about some issue.
The versions illegally distributed with AmigaOS 4.1 FE (and newer) releases/CDs of AmigaOS 4.1 by Hyperion, despite explicit prohibition to continue including it, are.
Not sure about the os4depot and AmiNet versions any more.

Quote:
so my chain loader is found instead on USB which then loads in the real boot code from the El Torino boot block. Since UBoot doesn't directly support booting ISO9660 off CD, this transparently works around it and unlike some ISO/USB Linux installers, my method works without needing FAT DOS BOOT CD image hackers.
It's based on El Torito, but IIRC there were some small differences required for AmigaOS 4.x or U-Boot.
IIRC U-Boot itself doesn't support booting any OS at all, except for Linux with TFTP maybe, but can only load and start the SLB, which then boots AmigaOS 4.x or Linux from HD partitions (FAT, ext2fs, FFS/FFS2, SFS/SFS2, etc.) or ISO 9660 (CD/DVD or USB), or with ub2lb/Parthenope instead of SLB_v2 AROS, MorphOS and Linux, but not AmigaOS from SFS partitions. However using FFS, maybe DOS\0-DOS\5 only, not the new FFS2 DOS\6 and DOS\7 formats, for the AmigaOS Kickstart partition should work with ub2lb/Parthenope as well.

Quote:
Provided SFS format was public SFS support could have been added.
The format of SFS 1.84, the last version from John Hendrikx, is public, but that didn't help much.
The easiest way to destroy any SFS partition is using the broken Linux implementation of SFS based on his public documentation in r/w mode
In my AmigaOS version of SFS I added some improvements which aren't backwards compatible, except to my own implementations of it (AmigaOS 3.x/m68k SFS, AmigaOS 4.x/PPC SFS and the SLB_v2 SFS code), but not to John's <= 1.84 versions and independent implementations of SFS like the AROS, MorphOS and Linux versions.

Go to top


Re: NetSurf 3.11 has been released!
Just can't stay away
Just can't stay away


@Maijestro
Quote:
Will our AmigaOs4.1 ever be able to do this? Or is it the font system....I have no idea what exactly is missing maybe you could explain it briefly?
Unicode is fully supported by the outline font engines, even since AmigaOS 2.1 the AGFA bullet.library already supported some parts of it (16 bit only, i.e. only the first 65536 Unicode chars, and because of some different encoding even less than that).
It's more work than using the 8 bit graphics.library Text#?() functions, but for example my AmigaOS 4.x ports of OWB supported 32 bit Unicode completely.

The only important limit is that the AmigaOS outline font engines are black/white only (+ alpha sub-pixel rendering in AmigaOS 4.x).
Colour outline fonts, which are used in current web browser for emoji for example, are not supported.

utility.library and locale.library include some support for UTF-8 as well, for example the catalog translation files can, and should, use UTF-8 instead of a 8 bit charset like the default ISO-8859-15, or other language/country specific 8 bit charsets.

BOOPSI gadgets could use UTF-8, or 32 bit, Unicode as well for texts. AFAIK most (or even all?) still don't, but rendering Unicode in the webview of a browser is no problem at all.
I always tested OWB with some Chinese, Japanese and Korean web pages as well. I did't understand anything at all on such pages, but comparing the OWB results with the ones from FireFox and Chrome was enough to check that it was working correctly

Go to top


Re: Sam460LE - linux Debian / Ubuntu instalation questions
Just can't stay away
Just can't stay away


@Hypex
Quote:
I wonder if genisoimage or similar can inject data into the reserved system area? Most CD image builders, likely due to using a limited GUI, didn't let you select a file to inject in there I could see. I modified some Amiga program that overwrote the system area of a CD image with a file to get the job done once.
My AmiDVD tool (Enhancer Software, old versions are available for free on os4depot and AmiNet) supports adding the slb_v2 to ISO 9660 images, setting the required flags, etc., and burning them to CDs and DVDs.
I never tested it with AROS/MorphOS/Linux-only 2nd level bootloaders like ub2lb/Parthenope, which can't boot AmigaOS 4.x (at least not from AmigaOS SFS partitions), but since it shouldn't make any difference for U-Boot those should work as well, if you only want to boot AROS, MorphOS and/or Linux with them but not AmigaOS 4.x.


Edited by joerg on 2024/11/28 18:34:02
Edited by joerg on 2024/11/28 18:34:33
Go to top


Re: ScummVM and AmigaOS4.1 F.E.
Just can't stay away
Just can't stay away


@Raziel
Quote:
its far too long ago that I'd be able to remember, but would a newlib.library, placed inside a libs/ directory, inside the scummvm directory be used proritized before the libs: assign?
or does that only work with sobjs/
Additionally to what Nils wrote:
It would be even worse doing that with shared AmigaOS libraries than with sobjs.

If you have a foobar.library in PROGDIR:Libs instead of LIBS: and start a program using it as the first program using this library it may be loaded from POROGDIR:Libs and stays in memory. All other programs using foobar.library started later will use this version instead of the one from LIBS:.
If the program with a POROGDIR:Libs/foobar.library is started after another program using foobar.library the one from LIBS: now in RAM will continue to be used, not the one in PROGDIR:Libs.

I'm not sure if it works that way as I don't remember the order in which ramlib searches for libraries, first in POGDIR:Libs, PROGDIR:, etc. and last in LIBS:, or if LIBS: is used first and PROGDIR:Libs, etc. only if it's not found in LIBS:, but in any case it's not possible to have different versions of a foobar.library in LIBS: and PROGDIR:Libs, some programs would always use the wrong one.

Go to top


Re: Video editing software
Just can't stay away
Just can't stay away


@davec555
Quote:
This just came up in my feed. Not sure if it's possible to port but worth a look?

https://github.com/paulpacifico/shutter-encoder

Dave
Java? Seriously? Ok, there were some "recent" (in Amiga terms) updates in https://github.com/jaokim/jamiga-jamvm , "only" about 8 years ago, but most of it is 19 years old and AFAIK nothing of it was was ever usable at all, except for some extremely simple and shell only "hello world" kind example programs...

Even Amiga Inc.'s "AmigaOS 5" (aka "AmigaDE", the Elate OS from Tao group), which was based on Java, would have had a much higher chance to be able to run such software

Go to top


Re: ScummVM and AmigaOS4.1 F.E.
Just can't stay away
Just can't stay away


@Raziel
Quote:
ah, so it could be newlib.lib...
The A1222+ version of newlib.library includes some SPE code (internal functions only, AFAIK not callable by SPE compiled software).
Should be faster than emulated FPU code, maybe with less precision in the SPE math functions compared to the FPU ones but that shouldn't cause crashes.

@Mr_byte
Quote:
But I understand that other software stops working when he switched.
Except for software requiring the newer version of newlib.library using an older one from another system shouldn't cause problems - it's just slower than a special SPE A1222+ version because the FPU code in the other versions has to be emulated on the A1222+.

Go to top


Re: ScummVM and AmigaOS4.1 F.E.
Just can't stay away
Just can't stay away


@Maijestro
Quote:
This is worth a try, but does not explain why there are no problems here on my machine with the same build.
Same scummvm executable, but maybe different shared objects (*.so) installed on your machine used by it.

Unfortunately most AmigaOS 4.x developers still don't understand at all how shared objects work on AmigaOS 4.x.
1. Although it's supported by ramlib/elf.library PROGDIR:Sobjs must never be used for shared objects.
2. All .sos have to be installed in the SOBJS: assign (SYS:Sobjs) instead, and there only have to be regular files in it, never any soft links. If you'd use soft links there you'd get the same .so/.dll hell as on Linux and Windows...
3. OTOH soft links have to be used in the SDK:libs (GCC:lib, etc.) directories for building executables. Just like for the runtime linker (elf.library) it can only work correctly for the executable linker (GCC:ld, vbcc:vlink, etc.) if the -soname was set correctly when building the shared object.
4. All .sos have to be build with a proper -soname, without it it can't work, and it has to include any dependencies:
For example when building a shared object for clib4 instead of the default AmigaOS 4.x newlib C library the .soname has to include something like ".clib4" or "_clib4" in it's file- and -sonames, to make sure the incompatible newlib and clib4 shared objects can't be mixed.

As an user there isn't much you can do, with one exception:
If there is a problem with a shared object (.so) use "readelf libfoobar.so" (maybe additional arguments are required) and if there is no "SONAME" section in it it's broken and has to be fixed.

Go to top


Re: NGFS new version
Just can't stay away
Just can't stay away


@smarkusg
Quote:
NGFS is not very fast at copying - not the fastest system.
Here is @mufa's test https://youtu.be/HMCxxFOxKgs?t=2283
(include subtitles in English)
C:Copy with defaults isn't usable, if https://wiki.amigaos.net/wiki/AmigaOS_ ... OS_Command_Reference#COPY is correct it still copies the files in tiny 100 KB parts (on SFS partitions with a block size of 512 bytes).
Especially when copying large files something like "C:Copy BUFFER 10240 ..." (5 MB parts) should be much faster.
May not be such a big problem with NGFS as AFAIK it's using 16 KB or even 64 KB blocks, which would be 3.125 MB or 12.5 MB parts with the default BUFFER 200.

For SFS partitions it's important to use a lot of file system buffers, much more than the default used when creating partitions.
At least 5000 (* 512 bytes = 2.4 MB RAM), but it depends on the partition size and especially the number of files and directories on the partition.
NGFS may be much faster with too few buffers, because of it's larger block size.

Except for copying large files NGFS should be faster for nearly all operations. It's not only an about 20 years newer file system design, SFS was created when the average partition size was only a few 100 MB and doesn't scale well to partition sizes of several GB or even TB, NGFS uses the new vector port file system API.
SFS doesn't which means dos.library has to convert the arguments and results of each file system call to/from the old packet API, which can be a large overhead if there are a lot of small operations done.

Go to top


Re: QuakeII OS4 Version problems...
Just can't stay away
Just can't stay away


@nubechecorre
Quote:
3) Last problem is about the audio cd..

I use an iso of Quake 2 (created from an original cd using amidvd)
AmiDVD only supports data CDs/DVDs, not audio CDs nor mixed data and audio CDs.
You probably have the AIFF files created by CDFileSystem from the audio tracks of the CD in the ISO image now, but that can't work.

You need to use a different program to create an exact image file of the CD incl. the audio tracks, and you have to use a different file format like CUE which supports audio tracks as well.
ISO can only be used for data only CD/DVD image files.

Go to top


Re: Amiga OS4, virtual memory and swap partition..
Just can't stay away
Just can't stay away


@LiveForIt
There is no such thing as MEMF_VIRTUAL. Maybe it was in very early beta versions of AmigaOS 4.x, about 25 years ago (there were some plans for it, but I don't remember if it ever was implemented/used), but not in any current version of AmigaOS.

There are basically only 2 memory types in AmigaOS 4.x:
- MEMF_SHARED (incl. MEMF_KICK, similar to MEMF_PUBLIC on AmigaOS <= 3.x): locked (can't be paged out and the physical address stays the same from AllocVecTags() until FreeVec()), shareable between different tasks and can be accessed from interrupt handlers.
- MEMF_PRIVATE: Task local memory, unlocked (can be paged out to the swap partition or other, slower RAM (for example with my ZorroIII RAM pager on classic Amigas) and the physical address may change), can't be accessed from other tasks nor interrupt handlers.

Go to top



TopTop
(1) 2 3 4 ... 95 »




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project