I forgot:

qemu RTL 8139 I access the Linux shell with AmiCygnix "sshterm" but not the graphics part for example "Firefox" or FFPlayer is executed because you only hear the sound inside AmiCygnix.

WinUae RTL 8139 I can't access the Linux shell with AmiCygnix or even the graphics part in any way.

WinUae RTL 8029 with AmiCygnix I access both the shell and the graphics part therefore FFPlay Firefox etc.
always using sshterm .

a little note:
I use qemu with Linux but also on Windows.

I use Windows 10 LTSC 2021 and no automatic patch has been released to fix the recovery partition with this update KB5034441 to resolve a vulnerability.

So I solved it manually by following this:

https://support.microsoft.com/en-us/to ... 43-461c-ada9-24c8229763bf

now I understand how diskpart works with Windows and how to mount the various partitions with qemu even with Windows by correctly identifying them with the correct ID.

I will try running the various X graphics for Windows with AmiCygnix.

This is just a little note.

@balaton
@Maijestro

As soon as the final version 9 comes out I'll try it.
A thousand thanks.
Of course I always appreciate your work.

I'm currently playing "Elden Ring" and have almost played 150 hours.
I haven't had this much fun with a game in years, aside from swearing
I haven't finished the first "run" yet, I'm practically at the end, just long enough to wait for "qemu 9"

I must have said it a thousand times.
RTL8029 is the only driver in "EMULATION" that supports AmiCygnix.

Even with WinUAE RTL8029 is the only one that supports AmiCygnix.

All other drivers do not support AmiCygnix.

The reasons ?

I don't know, I'm not a programmer.

But there must be a reason if it works so if possible I would dedicate myself with qemu to the RTL8029.

AmigaOS is dead and buried for 30 years and maybe more.
I completely deleted everything including Winuae from my system.
The AmigaOS community of any forum no longer reflects my pastime.

Rude people are unable to share their work.
We weren't even talking about a cutting-edge operating system.
Where 30 year old application ports still struggle to be emulated.

So best wishes to everyone.

Big work !

Uncivilized people.

@orgin
Delete my account I no longer need it.
And above all my personal data.

I will check if my data has been deleted.

@TheMagicSN
@smarkusg

It is possible to have these versions that you are using.
I'd like to try them.
All available betas are fine, MPlayer Quake 2 etc.

(the executables)

If possible.

A thousand thanks.

@Cageman
@LiveForIt

I am a simple fan of the AmigaOS system.
Like all of you.

So every now and then I like to talk about this system.
And I express my thoughts.

I imagine we are all more or less the same age given the origins of AmigaOS.

And that OWB 68k is perfect with "Browservice".
But not being a programmer I can only talk to all of you.

As an ignorant person on the subject, I thought the support for "Browservice" was simple to implement.

Since the old OWB for AmigaOS 4.1 also supports the one on OSDepot.

I like emulation since I can't buy real hardware.

I tried with Voodoo 3 all games with MiniGL work
except "Shogo" and "Heretic2" they are actually very fast but they have the wrong textures and are messy.
Probably due to "Voodoo drivers"

But all AmigaOS 4.1 games work fine.

And I'm here and every now and then I participate in the forum like everyone else.

For the rest I follow the evolution day by day

Thanks as always for the work done. With the "IBrowse 3" version.
Too bad you can't implement "a function" to use it with "Browservice".
It would be very fast and usable.

OWB 68k is supported without problems and navigation is very fast.

Regardless of "the emulator" used for 4.1.

AmigaOS 4.1 is increasingly becoming a machine to be used without being connected to the internet.
If used in "Local" AmigaOS is also perfect in emulation.

Thanks again for the new "IBrowser3".

@joerg
@Maijestro

It was just a note if it could be useful in any way.
I haven't tried but after updating update 1&2
Booting slows down.
Obviously just putting the old files back will overcome the problem.
Maybe it was due to cd-rom+floppy in the hardware boot chain

But at this point in the command line:
-cdrom
is if you also wanted to emulate the floppy

what should be added ?
if it is possible to do so

----
you can do it with the cd-rom

From the qemu terminal you can mount an empty -cdrom drive
at boot
you can then mount it later but now I don't remember which command to enter in the "qemu console"

I don't know if this is also valid for a floppy drive

it would still be an additional option to use.

@balaton

I don't know if this is important in the qemu version (even if older) of winUAE.

I remembered now.

Using AmigaOS 4.1 Classic in this case.
Verbatim words by (Tony) in various topics dedicated to 4.1
And personally tested (boot is faster)

The hardware control chain process of the "boot" machine
By enabling floppy and cdrom, AmigaOS boot is much faster.
Disabling the floppy and cd-rom makes booting slower.

I don't know if this is automatically included in the "qemu" version
for Pegasos2 or AmigaONE.
Or whether it should be enabled on the "qemu" command line regardless of whether it is used or not.

I'm writing this in case it might be useful.

In practice, not finding the cdrom and floppy will make booting slower.

@Maijestro

I agree with the current state.
It is assumed that with a graphics driver the disparity between processors will be made less demanding in the future.
Unfortunately, we will have to wait to make good use of AmigaOS 4.1 on the graphics side.

But I will definitely be one of the first to buy it if put on sale on the A-EON store.

Currently emulating with qemu "morphos" with the "ATI" the videos with OWB are very smooth even the video players and the E-UAE itself is very fast.
They can all be used together without the slightest slowdown.
Too bad only about the audio
it's obviously the "license" but that's an old story.

I just hope I don't get too old in the meantime.
I'm already starting to get very lazy now.

I've been using OWB for 68k for two years
The videos on YouTube and the navigation is perfect
with AmigaOS 3.9.
I use "browservice" for a modern view.

Also works with the QT browser included with the "QT-minimal" package
and also with "InternetSurfBoard" present on OSDepot.

But the speed is slower with OS4.1

I hope to be able to try the updated QTBrowser as soon as possible

Thanks for your work.

Here OWB 68k at work without any script but just simply using "Browservice" on youtube:

https://youtu.be/Gj0RPKWR83w

@miggymac

Thanks for the tips,
if you have time
and you want to try "browservice"
https://github.com/ttalvitie/browservice

here you can already find the image for raspberry
with "browservice" preconfigured at startup.

https://www.mediafire.com/file/bu9ksr6 ... bian_Browservice.rar/file


here is the tool for the sdcard if necessary
https://www.raspberrypi.com/software/

add :
wpa_supplicant.conf
in the same directory:
example:

country=IT
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid=""
scan_ssid=1
psk=""
key_mgmt=WPA-PSK
}

Instead
on your old operating system with outdated browser.

example manual
IP
192.168.0.14
mask
255.255.255.0

type from your old browser (Odyssey)

192.168.0.15:8080
or
192.168.0.15:8080/goto/google.it
or
192.168.0.15:8080/goto/youtube.it

clearly it is ONLY if you feel like testing it out of curiosity.

I don't take responsibility

you can use the ethernet cable or wifi (depends on the model).

Thanks again for your suggestion.
I appreciate it

@All

My topic is OT
but it is related to qemu emulation for AmigaOS 4.1

Does anyone know how the exact command line to emulate a RaspBerry
Pi or Pi2 with "qemu"

I would need it to create a dedicated "browservice".

Thank you.

@all

I changed Linux distribution
nothing in particular
but I like it and I also don't have to disable the Nvidia Nouveau drivers because the distribution already has the drivers being installed.
even if in the end there are just a few steps to do.
And few things installed
Ideal for me who only use it for qemu.
I just had to add the packages to compile qemu including the annoying "meson"

And light and I notice that it is faster than "kali"
Also now I can compile directly from the qemu master branch.
Without mistakes.

Other than that the idea of creating a sharing directory was a simple additional option.

With the ramdisk configuration I thought it was possible to choose a "raw" filesystem but I couldn't find anything on the subject although there is certainly something out there to read.

Now qemu no longer gives the "floating point" error
But if I try to initialize the ramdisk it tells me that it cannot initialize RDB "0"

It would also be fine in fat32 for sharing or some compatible format.
But it doesn't matter it was just something more to add.

On the other hand, why not try it when it takes a few minutes to restore the Linux backup, it costs nothing and is fun

Thanks for all the suggestions.

Since I'm here I wanted to ask if "aiostrems" still works for you and twitchTV doesn't seem to work for me anymore.
While YT.rexx works fine.

This is the distro I'm using:
https://pop.system76.com/

@balaton
once again thank you for your work.

I'll write it here if it might be found interesting by others too
otherwise it's not important.

sudo mkdir -p /media/ramdisk
sudo mount -t tmpfs -o size=2048M tmpfs /media/ramdisk

sudo fdisk -l
we obtain:

/dev/ram0

then we add:
-drive format=raw,file=/dev/ram0

è "hdtoolbox" recognizes the new "virtual partition created with the ramdisk" ready to be initialized

at that point "qemu" comes out giving me the error:
"floating point error"

Not knowing AmigaOS I really don't know if it is possible to manage this type of volume by mounting them in other ways

Or if there is some utility in AmigaOS that can handle all this.

If anyone finds it interesting, we could look into it further.

by modifying "fstab" it can be made permanent or simply the volume disappears upon reboot.

@Maijestro

the ideal would be to find a way with qemu to share a directory with linux for exchanging files on the fly.

using only qemu
something similar could be done by mounting a "shared virtual hd"
always with a similar command for example:

-drive format=raw,file=/dev/sdd2

I did it some time ago with a program similar to this:

http://radeonramdisk.com/software_downloads.php

It worked well and was very fast
I had put the entire AmigaOS 4.1 Classic directly into "RAM"
WinUAE

it was very fast

But it could be done with a shared virtual-hd without using RAM.

But I don't remember the exact command I used in qemu 3.1 version

With "Browservice" the page is displayed correctly with Odyssey.

now I'm trying the new "sdl" maybe with a bit of luck it works "UAE" it already works with the -7447 cpu but it's not perfect
with some betas who wrote "kas1e" is "FlynnTheAvatar"
but at the moment they only work with an 8bit screen
waiting for a 32bit video driver but that will take time.

And I don't think they want to adapt it for 16bit screens.
and if it is possible

but I'm the one doing something wrong
every time I have to download "sdl" if I use Odyssey or "IBrowse"
the page is not displayed correctly to download the latest "sdl" version
And I have to use "firefox linux or windows" every time to download the file and then import it in the form of "iso" to be able to install the sdl file.

It seems strange to me that the file is not accessible with the Amiga Browser given that it is a file for the Amiga.

under the ASSETS heading the field is empty to be able to download the file with Odyssey or IBrowse

Does it happen to you too ?

@balaton

Yes it is exactly as you described.
That's why I had to give chmod 777 every time

at every reboot to access the AmigaOS partition
and the qemu command line didn't work normally.

so in summary
better a completely dedicated SSD in case you want to opt for this choice.