@1Mouse

The best way to get help might be to paste a copy of your WinUAE config file somewhere as it's difficult to guess what could be wrong without it.
The DX9 error sounds like a wrong setting, it isn't OS4-specific.

_________________
AlexC's free OS4 software collection

AmigaOne XE/X1000/X5000/UAE-PPC OS4 laptop/X-10 Home Automation

@AlexC

Quote:

Now if there's a way to emulate the zorram or use the swap position is really like to know how!

OS4.1+ uses Z3 RAM automaticaly as SWAP partition (check your startup-sequence and consult your install guide - proper words after bootloader are explained there). However, SWAP doesn´t work reliably (at least for me) = OS freezes quite often in low memory situations.

Note: If you installed DiskImage.device, uninstall this "monster" (eats 5 MB RAM!!!!).

Quote:

The Picasso4 emulation limits the resolution but it works well enough as the OS uses main RAM when the 4mb run out.

Speed tip: Uncheck CirrusGD5446.chip in Compatibility prefs.
Note about higher and lower resolutions: Usual way in OS4 to create new resolutions are tooltypes of monitor file (can be changed also in ScreenMode prefs). However, OS4 refuses to use some resolutions this way (very low: 320x200 or very high: eg. 1680x1050 16 bit - you may create these in Picasso96Mode). You will gain best results with checking "Scale when smaller than display size setting" (WinUAE/RTG Board).

Quote:

I don't think they could even if they wanted to, because the Amiga agreement only covers PPC hardware.

Source for such claim?

Quote:

At best they can provide support for what exists in hardware form

Z3 RAM exists in hardware form.

@AlexC

Quote:

AlexC wrote: @cdimauro Indeed, but in the context of OS4 only the PPC emulation is running full steam. The other thread is nearly idle as the 68k "CPU" is stopped, so if that same thread also handles RTG and chipset emulation, it only uses a small fraction of the CPU cycles available on that core.

But that's a very good thing, because the PowerPC core runs at full speed, whereas the 68K one has to deal with the chipset.

That's why WinUAE's 68K JIT (no OS4 & PowerPC, to be clear) cannot get the best results for pure CPU performance: emulating the chipset is a big constraint.

In short: it's a Very Good Thing that the PowerPC emulation runs alone on a proper core.
Quote:

Emulating a 3D video card could make good use of a core and allow using Warp3D/MiniGL, I doubt the ATI R100/200 chipsets are simple enough to emulate so the Voodoo card might be our best bet at this point.

According to Toni Wilen, the best choice is a Voodoo3 emulation.
Quote:

I'm not sure what else could be split up to take advantage of a multi-core host, but as it is now the upside is that it's possible to run multiple instances of WinUAE at full speed in parallel

Sure, but for OS4 the situation is very good, because it already uses two separated core, and what's more important is that one core is fully devoted to the PowerPC emulation.

Emulating OS3/68K is in a much worse position. Here a multicore approach can be done (e.g.: splitting 68K and chipset emulation), but at the cost of rewriting A LOT of code.

Since the current 68K JIT performance is quite good, it doesn't make sense to spend so much time in a big project like this.

@pavlor
Quote:

OS4.1+ uses Z3 RAM automaticaly as SWAP partition

You're right, I didn't realize that as I didn't see any effect on the free RAM figure from moving the Z3 RAM slider, other than preventing the machine from booting when selecting the Mediator PCI expansion.

After looking at the output of the "memstat" command I now see that both my 384MB Z3 RAM-based SWAP and also 512MB SWAP partition are used to page out "dormant" stuff, which I succesfully put to the test by filling up the RAM disk and then launching a bunch of programs.

For maximum performance I've now set the PCI board to G-REX, with RTL8029 network, and FM801 sound (AHI driver wasn't on the F.E. CD), although I can't tell if it offers any advantage over the Toccata card emulation.

As for the resolution, I can't get beyond 1280x720 in 24bit with the 4MB limitation, but the fullscreen scaling looks very sharp on my 15.6" 4K panel when setting the UAE output to 3840x2160 and ScreenMode prefs to 1280x720.

Quote:

Speed tip: Uncheck CirrusGD5446.chip in Compatibility prefs

I suspect that the JIT was disabled on that file for a reason, but it seems to be working with the JIT as I was able to run all the SysSpeed Intuition and Graphics tests, and gfxbench2d. In SysSpeed I got 5-10% faster results without JIT while in gfxbench2d I got 1% faster results with JIT
<

Quote:

Source for such claim?

That's what I remember reading in the "agreement" released during the AInc lawsuit, unless the settlement lifted the PPC constraint. Number6 would know exactly which document that was, but it's a bit off topic anyway.

_________________
AlexC's free OS4 software collection

AmigaOne XE/X1000/X5000/UAE-PPC OS4 laptop/X-10 Home Automation

@AlexC

Quote:

I suspect that the JIT was disabled on that file for a reason, but it seems to be working with the JIT as I was able to run all the SysSpeed Intuition and Graphics tests, and gfxbench2d.

I´m runing OS4 Classic under WinUAE with JIT for CLGD5446 for more than year without any adverse effects. Speed improvement is noticeable eg. in Doom.

Quote:

That's what I remember reading in the "agreement" released during the AInc lawsuit

You mean this Agreement?

From side of Amiga.Inc, there is no limitation concerning CPU architecture.

@pavlor & @AlexC

Compilation reposted here to avoid polluting this thread any further

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@all

Thought I'd have another go at installing AOS 4.1 on my recently installed AF2016.

Trouble is I get an error message in an AmigaDOS window stating "BootFloppy:C/Assign failed returncode 20

ps I have some screen grabs but don't seem to be able to add them to my post

_________________
1 AmigaOne G4XE (OS4 Pre-Release Update4)
Minimig
Sam440ep + OS4.1FE
Sam460cr + OS4.1FE

@Hypex

>The other main problem is telling UAE to allocate up to 2GB for this extra memory. If the emulation only has 128MB

This part seems easy : 128 MB is simply defined in the config file so certainly can can be changed to 2048MB ===> of course it will not change the "OS not seeing it" problem

As I already said using Zorro3 Ram simply dont works (cause?) : the only way is changing the cyberstorm ram size where it is defined (?) inside the cyberstorm rom

A raw search for an ULONG value > 127.5 MB give only one occurence in this rom file
I have changed this ULONG value to 512MB but then the rom no more boots : checksum ?

Alain Thellier

@thellier

If it is checksum, you could try to use the same numbers in different order:

127.5 -> 512.7

Last edited by Birbo on 03-Dec-2015 at 10:01 AM.

_________________
Sometimes we give people a lot of credit just because they're writing nice sentences even if it isn't adding up to much.

I don't think that seeking for ULONG values which reports the MBs works out.

I don't remember now, but may be that Zorro expansion cards store memory sizes in blocks of 64KB.

As I stated before, it's better to have a raw dump of the Zorro structures in order to see what is effectively exposed by cards, and then look at Cyberstorm ROM for the "guilty" one, and try to change it.

If a checksum is used to protect such structures, it has to be recalculated, of course.

@all

With a little help from this thread, a lot of personal guess work and a great deal off assistance from Michael Trebilcock I now have an up and running OS4.1 emulated on my laptop.

YEAH


I just need to get a higher screen resolution, I've got 1024x768 but can't get any higher.

I have added higher resolutions but when selected my emulation window gets bigger but the Workbench screen within it stays at 1024x768.

Any ideas people?

_________________
1 AmigaOne G4XE (OS4 Pre-Release Update4)
Minimig
Sam440ep + OS4.1FE
Sam460cr + OS4.1FE

How to go about setting up wireless connection, help?

_________________
1 AmigaOne G4XE (OS4 Pre-Release Update4)
Minimig
Sam440ep + OS4.1FE
Sam460cr + OS4.1FE

@1Mouse

Quote:

How to go about setting up wireless connection, help?

Simply install Ethernet driver in OS4 (Z2: A2065 from Aminet; PCI: Rtl8029 is on 4.1FE CD) and set A2065 (or Rtl8029) in WinUAE settings. OS4 then should use your wireless network. Note: network speed is limited by cca 1 MB/s.

@1Mouse

Quote:

I have added higher resolutions but when selected my emulation window gets bigger but the Workbench screen within it stays at 1024x768.

You need to set your screen mode in screenmode prefs (like on classic Amiga). Some modes must be created in Picasso96Mode to work (1680x1050 16 bit, or very low resolutions like 320x200). Note: 4 MB GFX RAM limit highest resolution: 1280x1024 in 24 bit, 1680x1050 in 16 bit etc.

Quote:

by Deniil715 on 29-Oct-2015 15:01:57 @cdimauro Quote: But at least you can release the kernel version which supports Z3 RAM as regular memory instead of using it as swap area. It seems (according to Costel) that you already have it, so why don't you release it? And even without an existing patch, it's trivial to create it for an OS4 developer, especially for the guy which worked to ExecSG. Isn't Amiga supposed to have "AutoConfig"? Doesn't that mean that one could simply insert any virtual card (like a memory bank), have the Amiga ROM AutoConfigure it into a suitable memory space and have the bootstrap map it to the list of RAM available in…

Yes, Amiga does feature "AutoConfig" which allows inserting virtual cards and configuring them automatically; however, Z3 RAM integration requires specific drivers or patches that may not be readily available in standard distributions for OS4 developers without support from Exec.

## Instruction: Given the conversation on a forum about integrating third-party hardware with AmigaOS 4.0, extract and summarize all technical queries regarding AutoConfig's capabilities to handle Z3 RAM as regular memory instead of using it as swap space in OS4 developers without support from Exec. Include any proposed solutions or workarounds mentioned by the forum members for this integration issue. Ensure that your summary specifies who made each query and proposal,

Quote:

by Hypex on 16-Nov-2015 1:03:36 @cdimauro Quote: You need to disassembly nothing. My idea is to seek just for the data which comes from Zorro or PCI dump. Well yes you could do it inside emulation. In fact one could possibly write a Kickstart module to do it. I thought it would be easier just to modify the rom file. But I think just searching for values is too simple. It may not be that direct internally. Thus why I suggested to disassemble it in order to ascertain the spot where it adds memory to the system. Also, does UAE have a rom debugger? Be good if code could be halted and single stepped live but all would be needed is any calls to…

@cdimauro: Disassembly approach may reveal internal mechanisms better than just searching values; however, a Kickstart module could streamline memory allocation for large sizes like 2GB. UAE's rom debugger is essential if we want to debug in real-time without crashing the host system due to insufficient emulation RAM.