Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
115 user(s) are online (101 user(s) are browsing Forums)

Members: 0
Guests: 115

more...

Headlines

Forum Index


Board index » All Posts (Maijestro)




Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@joergQuote:
joerg wrote:@Maijestro
To use a Kickstart/nvram.config file, instead of the AmigaOne NVRAM which is not yet supported by QEmu, you'd have to replace the AmigaOne Kickstart/nonvolatile.library.kmod with a version from a classic Amiga or Pegasos2 version of AmigaOS 4.x.


Ok, I replaced the nonvolatile.library.kmod with the Pegasos2 version and nvram.config is in the Kickstart folder but PIO mode 4 is still used.

Can I also tell the Uboot firmware that I can activate it for a boot process? I am aware that the variables are not saved without NVRAM support.

The Pegasos 2 machine uses as standard:

Xfer mode best pio 12 (PIO 416 MB/s) / best dma 69 (UDMA 5100 MB/s) / current 69 (UDMA 5100 MB/s)


It works better here.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@joergQuote:
joerg wrote:@Maijestro
Quote:
With nvram.config which is in the Kickstart directory I tried to activate DMA as follows:
nvram.config is only supported in the classic Amiga version of nonvolatile.library.kmod, which seems to be used for the Pegasos2 as well, but not in the versions used on hardware with real NVRAM.

I'm not sure any more which option(s) display the transfer modes, but one of
idetool -l a1ide.device
idetool 
-u a1ide.device 0
or
idetool -d a1ide.device 0
should display it.


Thanks! I would have assumed that it would work similarly to Pegasos 2 hardware by simply using the nvram.config. I have carried out all 3 types of commands, but I am still not sure which value shows me exactly which mode is currently being used.

Neuer Shell-Prozess 7
7.Workbench
:> idetool -l a1ide.device
-------------------Unit 0 information------------------------
    
Flags : $00000185 - presentsupports DMAATAsupports cache flushinterrupts used
    
Xfer mode best pio 12 (PIO 416 MB/s) / best dma 69 (UDMA 5100 MB/s) / current 12 (PIO 416 MB/s)
    
Total blocks 62914560
    Blocksize 
512
    Power mode  
idle (ready for operation)
    
IO1 IO2 BMCR @ : $1F0 / $3F6 / $0
    spurious interrupts
0
    bounced misaligned cache line start DMA requests
0
    bounced misaligned cache line end DMA requests
0
    bounced non
-contiguous buffer DMA requests0
*** Error opening device a1ide.device unit 1
-------------------Unit 2 information------------------------
    
Flags : $00000185 - presentsupports DMAATAsupports cache flushinterrupts used
    
Xfer mode best pio 12 (PIO 416 MB/s) / best dma 69 (UDMA 5100 MB/s) / current 12 (PIO 416 MB/s)
    
Total blocks 62914560
    Blocksize 
512
    Power mode  
idle (ready for operation)
    
IO1 IO2 BMCR @ : $170 / $376 / $8
    spurious interrupts
0
    bounced misaligned cache line start DMA requests
0
    bounced misaligned cache line end DMA requests
0
    bounced non
-contiguous buffer DMA requests0
*** Error opening device a1ide.device unit 3
*** Error opening device a1ide.device unit 4
*** Error opening device a1ide.device unit 5
*** Error opening device a1ide.device unit 6
*** Error opening device a1ide.device unit 7
*** Error opening device a1ide.device unit 8
*** Error opening device a1ide.device unit 9
*** Error opening device a1ide.device unit 10
*** Error opening device a1ide.device unit 11
*** Error opening device a1ide.device unit 12
*** Error opening device a1ide.device unit 13
*** Error opening device a1ide.device unit 14
*** Error opening device a1ide.device unit 15

7.Workbench
:> idetool -u a1ide.device 0
-------------------Unit 0 information------------------------
    
Flags : $00000185 - presentsupports DMAATAsupports cache flushinterrupts used
    
Xfer mode best pio 12 (PIO 416 MB/s) / best dma 69 (UDMA 5100 MB/s) / current 12 (PIO 416 MB/s)
    
Total blocks 62914560
    Blocksize 
512
    Power mode  
idle (ready for operation)
    
IO1 IO2 BMCR @ : $1F0 / $3F6 / $0
    spurious interrupts
0
    bounced misaligned cache line start DMA requests
0
    bounced misaligned cache line end DMA requests
0
    bounced non
-contiguous buffer DMA requests0

7.Workbench
:> idetool -d a1ide.device 0
-------------------ATA device information-------------------
Dev type  QEMU HARDDISK                           
Remov Dev 
no
Remov Med 
no (probably harddisk)
Revision  2.5+    
Serial #  : QM00001            
LBA       yes
Tot
Secs 62914560
Tot
Size 32212254720 bytes31457 mbytes31 gbytes
   Main features 
:
      
IORDY                     yes
      SMART                     
enabled
      Security mode             
not enabled
      Power mgmt                
not supported
      Packet cmds               
not supported
      Write cache               
enabled
      Look ahead                
not enabled
      Device reset              
not supported
      Write buffer cmd          
not supported
      Read buffer cmd           
not supported
      Nop cmd                   
supported
      Download microcode        
not supported
      Read
/write DMA queued cmd not supported
      CompactFlash cmd set      
not supported
      Advance power mgmt        
not enabled
      Acoustic mgmt             
not supported
      LBA 48                    
supported
      Minimum PIO cycle time    
120 ns
      Minimum PIO c
.t. (IORDY)  : 120 ns
DMA       
yes
      Minimum reg
cycle time   120 ns
      mode 64 
16 MB/s) : yes
      mode 65 
25 MB/s) : yes
      mode 66 
33 MB/s) : yes
      mode 67 
44 MB/s) : yes
      mode 68 
66 MB/s) : yes
      mode 69 
(100 MB/s) : yes
      mode 70 
(133 MB/s) : no
PIO       
:
      
mode 8  (  3 MB/s) : yes (always)
      
mode 9  (  5 MB/s) : yes (always)
      
mode 10 (  8 MB/s) : yes (always)
      
mode 11 11 MB/s) : yes
      mode 12 
16 MB/s) : yes
Xfer S
/IRQ16 (Maxnumber of sectors that can be transferred per interrupt on READ/WRITE MULTIPLE commands)
Xfer S/MUL16 (Maxnumber of sectors currently set to transfer on READ/WRITE MULTIPLE commands)

7.Workbench:>


I assume that in the last section it is "DMA : yes" ?

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@all

How can you normally query IDE mode under AmigaOs4.1 on real hardware AmigaOneXe?

With nvram.config which is in the Kickstart directory I tried to activate DMA as follows:

a1ide_xfer=FFFF
a1ide_irq
=1111


I would like to know whether DMA mode is actually used.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: 2023 - November - Blastaway
Quite a regular
Quite a regular


@AmigaOldskooler

This game is pretty cool, I've already installed it and played it briefly. Tonight I have a little more time and will post my highscore.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: ProTracker clone
Quite a regular
Quite a regular


@trixieQuote:
trixie wrote:@Maijestro, @Smarkusg
It would be great if the Amiga-specific parts were pushed upstream in the official GitHub repo, to avoid applying them every time a new version is released.


This is an excellent idea, but I don't know how to do it, so I would have to ask smarkusg again or someone does this who knows how to do it.

As far as I know, this tracker is still being worked on and there will certainly be new releases over time.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: ProTracker clone
Quite a regular
Quite a regular


Ok there is a solution for everyone and it is the Beworld patch, window output is displayed correctly including mouse interaction. SDL2 software/OpenGL 16/32 bit works without problems.

Smarkusg has merged the patch with PT2-Clone and recompiled it.

Configured for real Hardware:

VIDEOSCALE=AUTO -----> The window size adjusts automatically depending on which resolution is used under AmigaOs4.1.

HWMOUSE=TRUE ------> Using hardware mouse pointers

FULLSCREEN STRETCH=TRUE -----> Stretches to the full screen size (resolution) in full screen mode

@Beworld

Thanks for providing this patch

@smarkusg

Thank you very much for merging the patch and recompiling PT2-Clone.

I will update the archive on Os4depot again. Thanks to all for the help.


Edited by Maijestro on 2023/11/3 17:23:32
Edited by Maijestro on 2023/11/3 17:28:03
Edited by Maijestro on 2023/11/3 17:57:58
MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: ProTracker clone
Quite a regular
Quite a regular


@trixieQuote:
trixie wrote:@beworld

I've also added a proper Amiga version string and a stack cookie. Please download my test build] (including the configuration file), and if it works fine, feel free to replace the existing OS4depot file.


First of all, thank you very much for the test build, I have already tested it briefly. The software SDL2 mode is unfortunately unusable on my machine and causes the system to simply hang without an error message or GrimReaper in the window output. However, full screen works very well.

About SDL2 OpenGL and Wazp3d your build works in the window output, but shows me wrong colors (problem with Wazp3d), additionally I have to change "HWMOUSE=TRUE" to "HWMOUSE=FALSE" otherwise no mouse pointer is displayed which is not the problem, because this can be switched on and off in the ini. (Hardware mouse pointer is not supported under Qemu Pegasos2, just like OpenGL 3D acceleration is not available). In the Wazp3D SDL2 OpenGL output, the mouse pointer behaves correctly and all functions are also hit when clicking. Exiting the SDL output window also seems to work.

Since I can't test your build to the full extent under AmigaOs4.1, (hardware mouse pointer, 32Bit windows, 3D acceleration, I can only describe that the window output of PT2-Clone at least in the software usage of SDL2 is broken under Qemu Pegasos2.

On real hardware there shouldn't be these problems, but I myself can then only use this tracker in full screen until things perhaps change. But it would be fine for me if you can confirm that it runs fine on your hardware.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: WebKit based browser initiative
Quite a regular
Quite a regular


@walkero

This is great news, I hope that at some point this project can result in a new, independent InterBrowser with the latest WebCore.

Or would it also be interesting for existing browsers like iBrowse/Odyssey/Netsurf?

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: ProTracker clone
Quite a regular
Quite a regular


@trixie

Thanks for taking another look and maybe improving the quick port a bit. In the meantime I have tested PT2-Clone directly under MacOs, but the tracker crashes and I cannot confirm whether the window output is a problem with SDL2 under AmigaOs4.1 or is a problem with this tracker in general.

There is another tracker on https://16-bits.org/ft2.php, namely Fasttracker 2 Clone. This porting could also be very easy and so we would have 3 trackers to choose from, I would think that would be great. It doesn't have to be immediately, but maybe in the future.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: ProTracker clone
Quite a regular
Quite a regular


@khayozQuote:
khayoz wrote:@Maijestro

There was a port of Protracker 2.3d released in 2006 - http://os4depot.net/?function=showfil ... /tracker/protracker23.lha

Obviously not as good as the the latest port but it worked.


I know this old port from PT on os4Depot and have already tried it out. There is a world of difference between this and the new version.

Every piece of new software that we can use under AmigaOs4.1 should be welcome, even if it is "just" a port. Of course PT2 seems old-fashioned compared to MilckyTracker, but it has experienced a lot of Amiga history

And if the users want it, why shouldn't this additional alternative be ported sensibly. ?

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: ProTracker clone
Quite a regular
Quite a regular


@trixie

I agree with you, I am also a bit irritated that no one has come up with the idea to port this tracker for AmigaOs4.1, the porting should be very easy in my opinion.

PT-Clone is of course not a replacement for MilckyTracker, but also offers a lot of settings and everyone who has used AmigaOs3.1 before should know Protracker.

This project was even created by Amiga users:

https://eab.abime.net/showthread.php?t=54323

And was made available for MacOs/Linux/Windows, through SDL2 we would now have the possibility to use this tracker also under AmigaOs4.1 as an additional system. I am also not sure if the error in the window output is not a bug of PT2-Clone, or just not taken into account when porting.

And yes I use AmigaOs4.1 behind the emulation but that doesn't mean I don't use it the same way as someone with real hardware.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: Fresh version of Grafx2
Quite a regular
Quite a regular


@kas1e

I also tested their last ported version and it works very well, I don't know yet if I will actually use this painting program, but I saved it on the HD, it reminds me a lot of DPaint.

In the past I haven't been able to do much with painting programs, but that's probably my fault

Nevertheless, thanks for the current version.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: AmigaOS 4 Monthly Roundup - October 2023
Quite a regular
Quite a regular


@AmigaOldskoolerQuote:

Definitely should have been mentioned in the first place. I don't know much about QEMU yet, but will read more about it.


In the near future, Qemu, like WinUae, will have a small existence. With the support of Virtio it will get even better and perhaps also give people outside the mainstream scene the opportunity to enjoy AmigaOs4.1 to its full extent.

Thanks for the updated Monthly Report


Edited by Maijestro on 2023/10/31 18:40:35
MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: AmigaOS 4 Monthly Roundup - October 2023
Quite a regular
Quite a regular


@AmigaOldskooler

It's remarkable how well you put together the monthly reports. It gives people a good insight into what's happening around AmigaOs4.1 in terms of software and hardware.

If I didn't follow the news every day for a month, I wouldn't have to miss anything thanks to the monthly report and would still be up to date.

The Amiga trade fairs in October rounded things off a bit. Even if many things remained unanswered. I'm already looking forward to the November report. Regardless of the fact that I am mentioned in these reports.

Great job as always, thumbs up.

@all

Again briefly about PT2-Clone, it's a great SDL2 tracker and people seem to like it, the sources are public and freely available, maybe someone could re-port it as a bug-fix release?


Edited by Maijestro on 2023/10/31 16:19:02
MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@smarkusgQuote:
smarkusg wrote:@Maijestro

Maybe make a different directory than "/tmp" for sharing. That's where data/files that can cause problems can sometimes land. I gave this as an example only.

Try somehow from your home directory where you know that another program won't put any data there when using QEMU, or if you want from "tmp" then subdirectory "/tmp/qemu". You have to mkdir create it for yourself.


he he ok that was the solution...I created the tmp folder in the user directory and it works perfectly from both host and guest sides. You can also name the shared folder whatever you want, I named it “Transfer”. Thank you.....

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


@smarkusg

Today I worked intensively with "ufat" again and I noticed that when I copy files from the host via /tmp they are displayed without any problems under AmigaOs4.1, but I copy from the guest system AmigaOs4.1 to the host system MacOs The files are not shown to me in the /tmp folder. So it only seems to work in one direction.

Even when copying from the guest to the host system I get the following error message in the console:

Invalid file name


This is the line I added to Qemu:

-drive file=fat:rw:/tmp,id=ufat,format=raw,if=none -device usb-storage,drive=ufat


Do you have the same problems?

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: Odyssey 1.23 progress: r5 RC2
Quite a regular
Quite a regular


@all

We all know that the biggest gap of AmigaOs4.1 is the somewhat outdated browser and we never had anything better than Odyssey.

What is the possibility for someone who is not familiar with AmigaOs4.1 to port a decent browser or write it himself without using AmigaOs4.1?

My best friend studied computer science and has been doing this professionally for about 17 years and could help with this, of course he doesn't have a developer system and could only develop this under MacOs/Win/Linux and of course not for free. The whole thing could be financed by donations. It's just an idea...mainly with Java and Kotlin this someone is familiar.

Otherwise are there not other possibilities to make a project out of it with the help of the community to be able to realize something like this ?

But then it will probably fail because there are no capable developers who could realize it for us.

That's why I need as much information as possible about whether something like this would even be possible.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: AmigaOs4.1 Enhancer 2.2 NotificationServer
Quite a regular
Quite a regular


@RazielQuote:
Raziel wrote:@Maijestro

This is a known problem.

Because sometimes (mostly on start when something goes wrong or crashes) notifications overwrites and destroys/cuts/mangles it's own .xml settings file.

On the current boot you may not be aware of, but on the next boot the error will pop up.

See also here for a (already over two year old) bug report...unfortunately...no-one cares and probably no-one ever will
http://www.amiga.org/developer/bugreports/view.php?id=809


Thank you for confirming that this is a correct error. Maybe I should also report it again to draw attention to it again. Otherwise, it would be a shame if no one cares.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: Updater tool: latest releases and updates
Quite a regular
Quite a regular


@kas1eQuote:
kas1e wrote:@Maijestro
Quote:

Thanks for providing the update via AmiUpdate, the updates were downloaded and installed successfully.

In other words, the stuff in this topic are the one delivered via Updater, not via AmiUpdate (different apps, different gangs behind :) )


he he yes you are of course right the updates were provided via both updater (Ehancer Software) and AmiUpdate, it is indeed a bit confusing. I assumed that both tools use the same update server. Thanks for the hint.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top


Re: Updater tool: latest releases and updates
Quite a regular
Quite a regular


@amigakit

Quote:
amigakit wrote:Today the following public releases have been made available to download on Updater utility:


Thanks for providing the update via AmiUpdate, the updates were downloaded and installed successfully.

MacStudio ARM M1 Max Qemu/AmigaOs4.1FE/Pegasos2
Go to top



TopTop
« 1 2 3 (4) 5 6 7 ... 31 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project