@Raziel

I believe there is no need for CFE to pass on this information.
AmigaOS4 doesn't have to know if the memory is interleaved or not.
It's the memory controllers that handle everything.

@Raziel

CFE shows that 2x2GB are interleaved.

Shouldn't it be transparent at the OS level whether it's interleaved or not?

@drHirudo

Yes, i know that that currently I can only see 2GB even though I have 4GB = 2x2GB installed.

I wonder if the 2 GB visible are the result of 1GB + 1GB taken from two interlaced RAM modules or if they are taken entirely from just one of the two RAM modules.

@sailor

This is the dramcfg output:

CFE> show dramcfg␍␊
[12:37:25:425] SDRAM: ECC off, Non-ECC DIMM used on channel 0.␍␊
[12:37:25:429] SDRAM: ECC off, Non-ECC DIMM used on channel 1.␍␊
[12:37:25:462] DRAM runtime configuration:␍␊
[12:37:25:462] Total memory: 4096MB␍␊
[12:37:25:462] Channel interleaved ␍␊
[12:37:25:462] XAUI␍␊
[12:37:25:462] ␍␊
[12:37:25:462] Channel 0:␍␊
[12:37:25:462] 2048MB of RAM, Address Range 0 - 6144MB␍␊
[12:37:25:462] Memory clock = 400MHz (DDR2-800), tCK = 2500ps, CL = 6␍␊
[12:37:25:462] Low Latency Config Tuned for Fcore = 2000 MHz␍␊
[12:37:25:462] High performance mode␍␊
[12:37:25:462] MMC advanced features␍␊
[12:37:25:462] DRAM Rtt: 150 Ohms␍␊
[12:37:25:462] MMC Rtt0: 75 Ohms␍␊
[12:37:25:462] MMC Rtt1: 75 Ohms␍␊
[12:37:25:508] MC & DRAM ODT␍␊
[12:37:25:508] Addr/Cmd 2T Timing␍␊
[12:37:25:508] Ctrl Output Phase wrt CLK: 0␍␊
[12:37:25:508] Addr/Cmd Output Phase wrt CLK: 0␍␊
[12:37:25:508] Rank interleaved␍␊
[12:37:25:508] UDIMM␍␊
[12:37:25:508] ␍␊
[12:37:25:508] Channel 1:␍␊
[12:37:25:508] 2048MB of RAM, Address Range 0 - 6144MB␍␊
[12:37:25:508] Memory clock = 400MHz (DDR2-800), tCK = 2500ps, CL = 6␍␊
[12:37:25:508] Low Latency Config Tuned for Fcore = 2000 MHz␍␊
[12:37:25:508] High performance mode␍␊
[12:37:25:508] MMC advanced features␍␊
[12:37:25:508] DRAM Rtt: 150 Ohms␍␊
[12:37:25:508] MMC Rtt0: 75 Ohms␍␊
[12:37:25:508] MMC Rtt1: 75 Ohms␍␊
[12:37:25:508] MC & DRAM ODT␍␊
[12:37:25:508] Addr/Cmd 2T Timing␍␊
[12:37:25:508] Ctrl Output Phase wrt CLK: 0␍␊
[12:37:25:508] Addr/Cmd Output Phase wrt CLK: 0␍␊
[12:37:25:508] Rank interleaved␍␊
[12:37:25:508] UDIMM␍␊

Hello guys,
I used the stream_memspeed program (available on OS4Depot) to measure memory speed with the following two configurations:

1) 2GB module fitted to DIMM1
2) 2GB module fitted to DIMM1 & 2GB module fitted to DIMM3

However the second configuration should use interlaced controllers, so I would have expected a doubling of the memory bandwidth,according to the X1000 documentation (First_contact_Nemo_v1.5.pdf).
Instead I get pretty much the same speed, according to the results of stream_memspeed.

Am I doing something wrong?


Note: AmigaOS4.1, due to the 2GB limit, only sees 2GB even in the second configuration where 4GB of RAM is mounted.

For me it updated to version 2.50 without problems.

But now if I launch it from Workbench, application.library opens this warning dialog:

---application.library----------------------------
The application "AmiUpdate" has opened version 2 of the interface "application",but tried to pass version 1 tag definitions to application.lib!

Please inform the author about this problem.

Note: The called function (and hence probably the application itself) will fall now.

[ OK ]
---------------------------------------------------

After pressing OK, the AmiUpdate window opens and everything works normally.

However, it no longer opens when you click on the AmiDock icon.

@AmigaOldskooler

And the winner is....

Hello!
Is there any possibility to port FLTK 1.3.x to AmigaOS4.1?

@TSK

I don't know how much benefit a touchscreen has.
It probably gives more advantage in the initial phase when there aren't many viruses and allows you to move instantly from one point to another on the screen.


Dragging with the Lilliput is not comfortable, i know.
I'm using an LG 17" Touchscreen, more stable and responsive.

Advise:
Use the following tooltypes for point&click games:
DONOWAIT
MODE=RAW
ANTIBOUNCE=100

I also noticed the problem of coordinate drift. I'm investigating.
As a workaround, when this happens, move the cursor to the edge of the screen to "crush" the drift, this way it realigns.

p.s.
On January 31st we will find out who wins between mouse or touchscreen :)

@AmigaOldskooler

Score: 1600250 ( TouchBench Powered ) )

@trixie

Thanks for your work!
Sounds like great software!

I did a quick test trying various modules on the X1000 and it seems to me that there are no performance problems, neither in fullscreen nor in window mode.
On average I have 30% CPU, rarely reaches 60%.


Can you tell if there is a way to import Protracker and Octamed .mod files?

My score:

Hi guys!
VirusKiller can be fun to play with a touchscreen.

https://youtu.be/17kwkmRZjUY

@mcleppa ,
I sent an email on December 5, 2023.
Have you received it?

I would gladly help as a beta tester.
Airscan works really well with my Canon TS8350.
I guess it's compatible with AirPrint too.

p.s.: until a month ago I could only print with Linux Mint. Windows 10 recognizes the printer but the data is sent endlessly and I have never been able to print anything.
After the latest Linux Mint update, I also have the same problems on Linux as on Windows.
So if I can print with AmigaOS, it would be a nice revenge against Windows and Linux.

Merry Christmas, Andy!
Thanks for this nice card video.

@gerograph
Quote:
As mentioned about the hidtouch.usbfd driver in my website, it is impossible to know for sure which devices it supports.
In general all modern USB-connected multitouch screens work with the HID protocol, so these smartboards are probably compatible too. In any case, if it isn't compatible, with a little feedback I can write a dedicated driver in 2 or 3 weekends.

@Maijestro

There are two ways:
1) adding the USB device directly into the command line that launches QEMU. In this way the emulated machine starts already seeing the connected USB device
2) using QEMU Monitor to add or remove USB device.

I prefer way #2, a few times I have had problems if the USB device is already connected when booting AmigaOS4.1 with an emulated machine.

Practical example:
- assuming that you have a USB touchscreen with vendorID=0x0eef and productID=0x0001.
- the touchscreen is already connected to the host machine
- you have to launch qemu with the following additional parameters: -usb -device usb-ehci,id=ehci
- to "connect" it to the guest machine you must type in the QEMU Monitor console: device_add usb-host,bus=usb-bus.0,vendorid=0x0eef,productid=0x0001,id=mytouchscreen
- to remove the device from the guest machine you must type: device_del mytouchscreen

You can choose any identifier of your choice instead of mytouchscreen.

Note: to be able to use USB on Linux, I had to configure qemu in the following way, before recompiling it: ./configure --enable-libusb --target-list=ppc-softmm
I don't know if it's enabled by default on Windows or not.

To learn more about QEMU and USB: QEMU USB emulation
In particular, you must be careful to correctly set the permissions to allow QEMU to access USB devices, as described in the following paragraph: QEMU - Using host usb devices on a linux host

Note: to open the QEMU Monitor console, press Ctrl+Alt+2 on the QEMU window.

@tekmage

Sure, the SDK is technically ready.
I'm using it to develop TouchBench.
I haven't published it yet because I believe that the Touch Device API needs to be improved and the definitive changes will be with the next version of Touch Device.
But if some developers already want to experiment, knowing that they will probably have to recompile when the new version comes out, I can provide the SDK privately.

A demonstration application that I would like to see built would be a simulation of something like this:
Sand Art video

I think a modified version of ShaderJoy that handles multitouch events directly would also be nice.

@Hans
Yes, it works.
I tested this driver on QEmu 8.1 (Pegasos2) too, connecting USB touchscreen monitors and configuring USB passthrough.