Forums - All Posts - The Amigans website

Forum Index

Board index » All Posts (FlynnTheAvatar)

Bottom

(1) 2 3 4 ... 7 »

FlynnTheAvatar

Re: Introducing Gabrielle - Xena's companion

Posted on: 1/13 7:34 #1

Just popping in

@jaokim

These are the results on my X5000/20 after a fresh boot:


3. > Workbench:Utilities/XTools > XenaStatus 

Warning: This set of XTools currently only tested on X1000

Setting up x5000

The support for X5000 is UNTESTED!

----------------------------------

If you'd like to continue, a few tests will be performed.

They will be performed with a varying delay

betweeen the read and writes.



The only reason you would want to run these tests is to

inform the developer on your progress.



You can abort this process by entering 'q' at any testpoint.



You will be asked to enter something to continue before each test.



 YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!



Creating Xena memory space for INDEX reg: e0000000

Creating Xena memory space for DATACHANNEL reg: e0008000

About to do some tests.

Enter 'q' to quit, anything else to continue... a

-----------------------------------------------------

Performing test with delay 5, with read/write 0x8000

with read/write 0x8000. Res in SIG1 is:   0xdead. Should be 0xdead

with read/write 0x8000. Res in SIG2 is:   0xdead. Should be 0xbeef.

with read/write 0x8000. Res in REG_HWREV: 0xdead.

with read/write 0x8000. Read scratch1:    0xdead (don't know what it should be)

with read/write 0x8000. Read scratch2:    0xdead (don't know what it should be)

with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0000 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0001 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0002 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0003 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0004 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x000c is 0xdead 1101111010101101

with read/write 0x8000. REG:0x000d is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0010 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0020 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0021 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0022 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0023 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0024 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x002f is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0030 is 0xdead 1101111010101101

with read/write 0x8000. REG:0x0031 is 0xdead 1101111010101101

Tests done.

If you got good values back from test, things seem to work.

If there were good results for the delay 10 test, then you could continue to run

and stuff might work. If no good results were seen then you might as well abort now.

Enter 'q' to quit, anything else to continue... a

fatal: chain too long returned 128

Hope this log helps you troubleshoot more.

Topic | Forum

FlynnTheAvatar

Re: Introducing Gabrielle - Xena's companion

Posted on: 1/12 18:37 #2

Just popping in

@jaokim

Thanks a lot for the new version.

This is the result of XenaStatus:


Warning: This set of XTools currently only tested on X1000

Setting up x5000

The support for X5000 is UNTESTED!

----------------------------------

If you'd like to continue, a few tests will be performed.

They will be performed with a varying delay

betweeen the read and writes.



The only reason you would want to run these tests is to

inform the developer on your progress.



You can abort this process by entering 'q' at any testpoint.



You will be asked to enter something to continue before each test.



 YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!



Creating Xena memory space for INDEX reg: e0000000

Creating Xena memory space for DATACHANNEL reg: e0008000

About to do some tests.

Enter 'q' to quit, anything else to continue... 

a

-----------------------------------------------------

Performing test with delay 2, with read/write 0x8000 Delay(1)

with read/write 0x8000 Delay(1). Res in SIG1 is:   0xdead. Should be 0xdead

with read/write 0x8000 Delay(1). Res in SIG2 is:   0xdead. Should be 0xbeef.

with read/write 0x8000 Delay(1). Res in REG_HWREV: 0xdead.

with read/write 0x8000 Delay(1). Read scratch1:    0xf0cc (should be 0xf0cc)

with read/write 0x8000 Delay(1). Read scratch2:    0xd1d0 (should be 0xd1d0)

with read/write 0x8000 Delay(1). Again scratch1:   0xa12f (should be 0xabcd)

with read/write 0x8000 Delay(1). Again scratch2:   0xa12f (should be 0xa12f)

with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0001 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0002 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0003 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0004 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x000c is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x000d is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0010 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0020 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0021 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0022 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0023 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0024 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x002f is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0030 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0031 is 0xa12f 1010000100101111

-----------------------------------------------------

Performing test with delay 5, with read/write 0x8000 Delay(1)

with read/write 0x8000 Delay(1). Res in SIG1 is:   0xa12f. Should be 0xdead

with read/write 0x8000 Delay(1). Res in SIG2 is:   0xa12f. Should be 0xbeef.

with read/write 0x8000 Delay(1). Res in REG_HWREV: 0xa12f.

with read/write 0x8000 Delay(1). Read scratch1:    0xf0cc (should be 0xf0cc)

with read/write 0x8000 Delay(1). Read scratch2:    0xd1d0 (should be 0xd1d0)

with read/write 0x8000 Delay(1). Again scratch1:   0xa12f (should be 0xabcd)

with read/write 0x8000 Delay(1). Again scratch2:   0xa12f (should be 0xa12f)

with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0001 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0002 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0003 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0004 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x000c is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x000d is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0010 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0020 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0021 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0022 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0023 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0024 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x002f is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0030 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0031 is 0xa12f 1010000100101111

-----------------------------------------------------

Performing test with delay 10, with read/write 0x8000 Delay(1)

with read/write 0x8000 Delay(1). Res in SIG1 is:   0xa12f. Should be 0xdead

with read/write 0x8000 Delay(1). Res in SIG2 is:   0xa12f. Should be 0xbeef.

with read/write 0x8000 Delay(1). Res in REG_HWREV: 0xa12f.

with read/write 0x8000 Delay(1). Read scratch1:    0xf0cc (should be 0xf0cc)

with read/write 0x8000 Delay(1). Read scratch2:    0xd1d0 (should be 0xd1d0)

with read/write 0x8000 Delay(1). Again scratch1:   0xa12f (should be 0xabcd)

with read/write 0x8000 Delay(1). Again scratch2:   0xa12f (should be 0xa12f)

with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0000 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0001 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0002 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0003 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0004 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x000c is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x000d is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0010 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0020 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0021 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0022 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0023 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0024 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x002f is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0030 is 0xa12f 1010000100101111

with read/write 0x8000 Delay(1). REG:0x0031 is 0xa12f 1010000100101111

Tests done.

If you got good values back from test, things seem to work.

If there were good results for the IDOS->Delay(1) test, then you could continue to run

and stuff might work. If no good results were seen then you might as well abort now.

Enter 'q' to quit, anything else to continue...

The results are ... strange.

Topic | Forum

FlynnTheAvatar

Re: Introducing Gabrielle - Xena's companion

Posted on: 1/11 14:09 #3

Just popping in

@jaokim

I tried the latest XTools from your blog on my X5000/20.

This is the output. It does not seem to work fully and the tools can only be run once:


3. > Workbench:Utilities/XTools > XenaStatus

Warning: This set of XTools currently only tested on X1000

Setting up x5000

The support for X5000 is UNTESTED!

----------------------------------

If you'd like to continue, a few tests will be performed.



1. The first test is according to the X5000 Curys TRM.

   It seemed to work for one test. But then not.

2. The second test is based on loose assumptions on how

   AEons Tabor motherboard works.



The only reason you would want to run these tests is to

inform the developer on your progress.



You can abort this process now by pressing Ctrl-C and enter.



You will be asked to enter something to continue before each test.



 YOU HAVE BEEN WARNED. NO RESPONSIBILITY IS TAKEN WHEN RUNNING THIS SOFTWARE!



About to setup mem space. Enter something to continue...

asd

Creating Xena memory space for INDEX reg: e0000000

Creating Xena memory space for DATACHANNEL reg: e0008000

About to do test 1. Enter something to continue...

asd

--- Performing Test 1 ---

Res in SIG1 is dead. This is good.

Res in SIG2 is dead. It is not 0xBEEF. That's wrong.

Res in REG_HWREV (2) is dead.

Writing D00F to scratch1

Writing BABE to scratch2

Read babe from scratch1 (should be D00F)

Read babe from scratch2 (should be BABE)

About to do test 2.

Enter something to continue...

asd

--- Performing Test 2 ---

Res in SIG1 is babe. It should be 0xDEAD.

Res in SIG2 is bebe. It is not 0xBEEF. That's wrong. You should not continue.

Res in REG_HWREV (2) is beef.

Writing F0BB to scratch1

Writing D00D to scratch2

Read f0d0 from scratch1 (should be F0BB)

Read d00d from scratch2 (should be D0DE)

If you got good values back from test 1, things seem to work.

If you got good values back from test 2, things in the code have to change!

If you didn't get good values, stuff will NOT work.

Press Ctrl-C to abort...



*** BREAK

3. > Workbench:Utilities/XTools > XenaStatus

Warning: This set of XTools currently only tested on X1000

Cannot allocate XTAGPORT resource: already used by XTAG Command line tools.

Hope this helps.

Topic | Forum

FlynnTheAvatar

Re: SDL3

Posted on: 12/10 10:44 #4

Just popping in

Okay, I figured it out. I have also HunoPPC's libegl wrapper installed.

It has its only set of configuration files in ENV/ENVARC:EGL_wrap directory. But SDL3 scans all sub directories it also picks up ENV:EGL_wrapper/SDL_RENDER_DRIVER and overwrites ENV:SDL_RENDER_DRIVER.

My suggestion is to call ScanVars with the flag GVF_SCAN_LEVEL (do not recurse into sub dirs).

Topic | Forum

FlynnTheAvatar

Re: SDL3

Posted on: 12/10 10:09 #5

Just popping in

@Capehill

Thanks a lot. Looking the Snoppy log it seems that ScanVars fails on my system.

Not sure why, but that would explain why using the SDL3 Prefs does not do anything.

Somehow I cannot get the Debug output to work, even when rebuilding SDL3 with debug.

I see if I can use printf to get the exact error.

Topic | Forum

FlynnTheAvatar

Re: SDL3

Posted on: 12/9 18:37 #6

Just popping in

@Capehill

Thanks a lot for checking. It is really strange that there are no GetVar calls in SDL3's testsprite.

I checked SDL2's testsprite2, and it works correctly; it defaults to compositing and the renderer can be set by setenv SDL_RENDER_DRIVER.

Strange thing is that I also do not see any GetVar calls in testsprite2, too. But it seems to work.

Is there another way to get the variable besides GetVar?

BTW, this what testsprite logs regarding the renderer:


> SDL3/test/testsprite --info render --log render

Built-in render drivers:

  compositing

  opengles2

  software

Couldn't create renderer: opengl not available

I am not sure where the opengl is coming from...

Topic | Forum

FlynnTheAvatar

Re: SDL3

Posted on: 12/9 7:36 #7

Just popping in

@smarkusg @Capehill

It works when I set the renderer with the option "--renderer".

Not sure why the renderer defaults to opengl on my system. Any idea how SDL3 gets the renderer from? It clearly ignores SDL_RENDER_DRIVER.


3. > RAM Disk:SDL3/test > testsprite --renderer opengles2

1067.20 frames per second

3. > RAM Disk:SDL3/test > testsprite --renderer compositing

396.24 frames per second

3. > RAM Disk:SDL3/test > testsprite --renderer software

196.44 frames per second

Topic | Forum

FlynnTheAvatar

Re: SDL3

Posted on: 12/8 20:02 #8

Just popping in

@Capehill:

Not that I am aware of. I tried to set a different driver with SDL3 prefs, but the test program failed with the same error regardless of the selected driver (compositing, opengles2, software).


3. > RAM Disk:SDL3/test > setenv SDL_RENDER_DRIVER opengles2

3. > RAM Disk:SDL3/test > getenv SDL_RENDER_DRIVER

opengles2

3. > RAM Disk:SDL3/test > testsprite 

Couldn't create renderer: opengl not available

Topic | Forum

FlynnTheAvatar

Re: SDL3

Posted on: 12/8 19:21 #9

Just popping in

Thank you for the new version.

Not sure if this is my system or a new problem with SDL3. But the testsprite program does no longer run on my X5000:


> testsprite

Couldn't create renderer: opengl not available

The Minigl test programs in SDK:Examples/MiniGL do work, so I think there is no problem with my system.

Topic | Forum

FlynnTheAvatar

Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report

Posted on: 2025/11/17 7:09 #10

Just popping in

@Hypex

Debugging never worked on the X5000... there was a bug in the X5000's kernel since day one.

Update 3 claimed that the X5000's kernel was finally fixed.

Topic | Forum

FlynnTheAvatar

Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report

Posted on: 2025/10/20 17:37 #11

Just popping in

The update on my X5000 with Enhancer 2.2 did installed fine. Although I needed 6-7 attempts for the download on Saturday.

USB-Stack works much better - my A500 keyboard with a Keyrah 3 now attaches properly and HiDPI mice no longer only go up and down. Console seems to be a bit more stable and debugging looks better.

But I noticed following bugs:
- fast clicking and dragging in a console windows freezes the OS (no GR, no serial log)
- HiDPI mice loose their mouse rad scrolling sometimes. Might be causes by detaching/attaching via my KVM
- gdb crashes with DSI after running a program, step does run the complete program

Topic | Forum

FlynnTheAvatar

Re: Using Keyrah V3 (Amiga 500 keybord) with Amiga OS 4.1 (X5000)?

Posted on: 2025/9/12 17:16 #12

Just popping in

Hi Thomas,

Yes, I connect the Keyrah 3 via a KVM switch. But I also tried to plug Keyrah into one of the USB slots on the backside of the X5000. No difference.

And the port is fine because the other machines (Raspberry Pi 5, two Windows laptops) do not have any issues when attach/detaching Keyrah. Or switching between the hosts with the KVM switch.

But I can create another set of logs using one of the backside USB ports (and detach all other USB devices but the mouse) if this would help you.

Topic | Forum

FlynnTheAvatar

Re: Using Keyrah V3 (Amiga 500 keybord) with Amiga OS 4.1 (X5000)?

Posted on: 2025/9/12 6:53 #13

Just popping in

Hi Thomas,

thanks a log for your help on this.

I don’t have usbinfo available — neither on Workbench nor in the SDK.

I’ve prepared the requested files as follows:

- usb_versions.txt – contains the version numbers of all the USB modules you listed.
- usb_success.log – logs from a successful attach of the keyboard. For this to work, I had to completely shut down the X5000 and disconnect the keyboard for more than 5 seconds before powering back on.
- usb_failed.log – logs from a failed attempt after a cold reboot.
- usb_detach_and_attach.log – after the successful attach (as in usb_success.log), I unplugged and re‑plugged the Keyrah. The attach failed again in this case.

Please check if you can access the archive from OneDrive:
usb_logs.lha

Best regards,
Josef

Topic | Forum

FlynnTheAvatar

Using Keyrah V3 (Amiga 500 keybord) with Amiga OS 4.1 (X5000)?

Posted on: 2025/9/9 8:07 #14

Just popping in

Hi,

I am trying to use a Samsung A500 keyboard with my X5000. But it seems that Amiga OS 4.1 USB stack has some issues with the Keyrah.

Amiga OS 4.1 will not detect the Keyrah when plugged in after booting. Restarting the machine will also not detected it. The only way to make it work is to shutdown the X5000, wait a bit, and then start the OS while the Keyrah is attached. Even then it only works 1 in 3 tries. Either the Keyrah is not detected at all, or even if it is detected the OS does not register any key presses.

I do not see any messages on the serial debug when plugging in Keyrah.

When the Keyrah is detected and working, I see the following USB device in SysMon:


Keyrah V3;3-0 (HDI);Keyrah Joystick Port 1;hid.usbfd;Individual Computers;222510120D9406B1

Keyrah V3;3-0 (HDI);Keyrah Joystick Port 2;hid.usbfd;Individual Computers;222510120D9406B1

Keyrah V3;3-0 (HDI);Keyrah Keyboard;hid.usbfd;Individual Computers;222510120D9406B1

Keyrah V3;3-0 (HDI);Keyrah Keyboard2;hid.usbfd;Individual Computers;222510120D9406B1

Keyrah V3;3-0 (HDI);Keyrah Multimedia Controll;hid.usbfd;Individual Computers;222510120D9406B1

Keyrah V3;3-0 (HDI);Keyrah ACPI Power Control;;Individual Computers;222510120D9406B1

Keyrah works fine with the other machines (A600GS, two Windows laptops and a Raspberry Pi5).

Any ideas how to make the Keyrah V3 more reliable on AOS 4.1?

Thanks a lot,
Josef

System:
AmigaOne X5000/20
AmigaOS 4.1 FE Update 2
Enhancer 2.2

Topic | Forum

FlynnTheAvatar

Re: Bug on Makedir command (Enhancer)

Posted on: 2025/9/4 16:51 #15

Just popping in

@amigakit

Thank you for releasing the fix. And sorry, I had to poke you because promised the fix already in 2022.

Topic | Forum

FlynnTheAvatar

Re: Bug on Makedir command (Enhancer)

Posted on: 2025/9/3 10:56 #16

Just popping in

@smf

Thanks a lot. Yes, this seems to be the same issue. But the SDL3 installer is no longer using a trailing '/' for creating the directories so I could not reproduce the issue by installing SDL3.

Let's see if we ever see an update by amigakit.

Topic | Forum

FlynnTheAvatar

Re: Bug on Makedir command (Enhancer)

Posted on: 2025/9/3 9:27 #17

Just popping in

@samo79:

I have MakeDir 54.11 (28.07.2022) from Enhancer, and SYS:Documentation/SDL3 is created just fine for when installing SDL3.

What version of MakeDir do you have?

Topic | Forum

FlynnTheAvatar

Re: infinite icons theme pack

Posted on: 2025/7/27 11:03 #18

Just popping in

@nbache

Thanks for the suggestion! I actually tried using FOREACH, but I couldn't get it to work recursively across subdirectories based on a pattern. To make it viable, I’d need to first feed it the output from a LIST command anyway. So at that point, I don’t see a clear advantage over just sticking with LIST and EXECUTE directly.

Topic | Forum

FlynnTheAvatar

Re: infinite icons theme pack

Posted on: 2025/7/26 18:42 #19

Just popping in

Detailed steps to resize PNG icons on AmigaOS 4.1:

1. Save this script as s:resize.py


#!/usr/bin/env python



import sys

import re

import StringIO

from PIL import Image



def find_pngs(file_path):

    f = open(file_path, 'rb')

    try:

        content = f.read()

    finally:

        f.close()



    png_header = '\x89PNG\r\n\x1a\n'

    positions = []

    index = 0

    while True:

        index = content.find(png_header, index)

        if index == -1:

            break

        positions.append(index)

        index += 1



    images = []

    for i in range(len(positions)):

        start = positions[i]

        end = positions[i + 1] if i + 1 < len(positions) else len(content)

        images.append(content[start:end])



    return images



def resize_and_export(png_bytes, size=(64, 64)):

    image = Image.open(StringIO.StringIO(png_bytes))

    resized = image.resize(size, Image.ANTIALIAS)

    output = StringIO.StringIO()

    resized.save(output, format='PNG')

    return output.getvalue()



def process_and_concat(input_file, output_file, size=(64, 64)):

    png_raw_data = find_pngs(input_file)

    concatenated = ''



    for png in png_raw_data:

        small_png = resize_and_export(png, size)

        concatenated += small_png



    f = open(output_file, 'wb')

    try:

        f.write(concatenated)

    finally:

        f.close()



def main():

    if len(sys.argv) < 2:

        print "Usage: python convert.py <input_file> [width height]"

        sys.exit(1)



    input_path = sys.argv[1]

    if len(sys.argv) >= 4:

        width = int(sys.argv[2])

        height = int(sys.argv[3])

        size = (width, height)

    else:

        size = (64, 64)



    process_and_concat(input_path, input_path, size)



if __name__ == "__main__":

    main()

2. Install PIL (https://os4depot.net/share/development/library/misc/pil.lha)
2a. Extract to RAM
2b. Execute RAM:PIL/Install_PIL

3. Create a script that calls s:resize.py on each #?.info file. Execute in Shell in the directory containing the info files:


LIST PAT=#?.info ALL FILES TO t:resize_all LFORMAT="python s:resize.py *"%P%N*" 64 64"

3.a (Optional) Check the t:resize_all script in an editor

4. Execute created script in the same Shell:


EXECUTE T:resize_all

EDIT: Please note the *" around %P%N. It is needed because the Path/filenames might contain spaces.

Edited by FlynnTheAvatar on 2025/7/26 19:28:07
Edited by FlynnTheAvatar on 2025/7/26 19:39:58

Topic | Forum

FlynnTheAvatar

Re: infinite icons theme pack

Posted on: 2025/7/26 18:42 #20

Just popping in

@DigitalDesigns

I am working on a version that works on Amiga OS 4.1. The initial script uses a few features that are not available on Python 2.5. The script is ready, but you need to install PIL from os4depot to make the script work.

Additionally, I need to figure out an easy way to call the script on each file. I keep you updated and I will provide steps how to do the conversion on AmigaOS.

Topic | Forum

Top

(1) 2 3 4 ... 7 »