WinUAE 3.0.0 beta series (was 2.8.2/2.9.0)

[dlfrsilver]

Hi Toni, i have posted the binary dump of my GVP impact series II A500 HD + fastrom in the zone, can you support it ?

[Toni Wilen]

Originally Posted by dlfrsilver

Hi Toni, i have posted the binary dump of my GVP impact series II A500 HD + fastrom in the zone, can you support it ?

WD33C93 SCSI emulation is currently hardwired to Commodore DMAC/SDMAC only. Which needs to be fixed first, someday..

[dlfrsilver]

ah ok

[Toni Wilen]

Originally Posted by narutard

Trying to boot to Workbench, while still loading workbench, it just freezes.
Tried with own configs and quickstart --> A4000 + Kick 3.1 + OS3.x

Hope this helps in a way better, sry I'm kinda new here.

Can't duplicate (and seems to be exact same as in ppc thread, nothing to do with PPC). Which is practically guaranteed when having HD setups because no one has identical ones (different startup-sequence, different versions of libraries, mmu libraries, setpatch and so on..)

So the usual debugging steps needed:
- Does it happen with 2.8.1? If not, find which beta introduced it.
- First step: disable JIT. Always compared with/without configs JIT.
- Remove all unneeded variables, no fullscreen, no vsync, only single boot drive, all expansions. As long as there is nothing left (only that is really needed) and it still crashes.
- Does same happen with normal WB3.1 boot disk
- Does it happen if you boot without startup-sequence and run setpatch manually?
- Last step: run programs in startup-sequence one by one until something happens..

[Seiya]

however, after beta24, Winuae sait me that it not find Qemu-uae v3.4..

i have v3.3.
Where i find new dll?

[Arnie]

Originally Posted by Seiya

however, after beta24, Winuae sait me that it not find Qemu-uae v3.4..

i have v3.3.
Where i find new dll?

Hi Seiya,

You can get it from here......

http://eab.abime.net/showthread.php?...light=Qemu-uae

[Seiya]

Thanks, now it works again

[Toni Wilen]

Originally Posted by Toni Wilen

That makes no sense. Neither does setting c00000 is fast option. There is something else. Going to do some testing later (and confirming on real A500)

Tested on my real A500 (KS 1.3, 0.5M+05.M ECS Agnus config): does not work, boots to KS 1.3 = nothing wrong with emulation as far as I can see.

EDIT: More interesting is how someone has (is it really confirmed?) managed get it working in that configuration..

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2900b25.zip

Beta 25:

- Added 1M/0.5M+0.5M chip/slow ram option checkbox to Advanced Chipset (for example in rev6 A500 it is JP2 solder pad). If hardware is configured for 1M chip without 512k slow ram, normal chip ram alias at upper 512k of chip ram address space gets replaced with "bus noise". Can be only changed when chip RAM size is less than 1M. (ECS Agnus + 512k chipram without slow ram configuration always used this option previously, now it is optional and not enabled by default)
- Map Chip RAM mirror at 0x01000000 in A2620/A2630 config, to prevent A26x0 built-in monitor program detecting huge ram expansion at 0x01000000.
- uaenet.device + slirp combination was broken (probably has always been).
- uaegfx modeid space increased, reduces modeid conflicts if host os has huge amount of modes.
- Debugger does not anymore exit stopped CPU state (STOP instruction) after exiting debugger.
- "SCSI (Auto)" priorities changed: mainboard built-in first, then accelerator board, expansions last. (Expansions was first previously)
- More accurate 68000 prefetch mode instruction cycle usage, added non-static cycle counting (mul, div etc..)
- Most CDTV-CR built-in CD audio player features, including CD+G, are now working. Media changes supported. 3.44 ROM CD player works better than 3.32.

[mark_k]

Originally Posted by Toni Wilen

ROM seems to support memory at 0x01000000->, detected by writing value to address zero, then some other value to 0x01000000, if address zero changes: no memory! If same, check 0x012000000 and so on.. Strange hardware if all non-existing address space gets aliased to address zero..

Perhaps the region (not sure how large that region is) starting at $01000000 contains repeated mirrors of the lowest 2MB address space when there's no extra memory on the A2630 card?

[Toni Wilen]

Originally Posted by mark_k

Perhaps the region (not sure how large that region is) starting at $01000000 contains repeated mirrors of the lowest 2MB address space when there's no extra memory on the A2630 card?

Perhaps but I don't do guesses and choose easiest possible solution (especially because no one cares except that single monitor command). No hardware = no better fix.

[BlackByte]

Hi Toni, the display resolution for OS4.1 WinUAE v2.9.0 b25 can be set higher than 1280x720?
If so, how?

[FOL]

Originally Posted by BlackByte

Hi Toni, the display resolution for OS4.1 WinUAE v2.9.0 b25 can be set higher than 1280x720?
If so, how?

Depends if your talking about the OS or the Emulator.

[DDNI]

Some users have run AmigaOS4 in 4K resolutions...

[ Show youtube player ]

[tero]

Originally Posted by DDNI

Some users have run AmigaOS4 in 4K resolutions...

[ Show youtube player ]

That's on a X1000. I Doubt it uses a picassoIV

[BlackByte]

Yes with PicassoIV (BGR24), higher resolution, if so how?

[Toni Wilen]

Originally Posted by BlackByte

Hi Toni, the display resolution for OS4.1 WinUAE v2.9.0 b25 can be set higher than 1280x720?
If so, how?

Most limits are exact same as real PicassoIV, mainly limited by VRAM size. (Memory bandwidth limits of course don't exist in emulation)

It is hardware emulation (only way to make it work in non-m68k operating systems), increasing VRAM would only break compatibility with all existing drivers.

[FOL]

Originally Posted by BlackByte

Yes with PicassoIV (BGR24), higher resolution, if so how?

I cant use BGR24 as it crashes. I think its what toni said.
I ended up creating a 16 bit screen mode in picasso and that lets me use my native resolution of 1366x768 in fullscreen.

[mark_k]

Originally Posted by Toni Wilen

Perhaps but I don't do guesses and choose easiest possible solution (especially because no one cares except that single monitor command). No hardware = no better fix.

Okay, well I don't have an A2630, but check the A2630 schematic...

All 32 address lines are pulled down to GND via resistor packs RP100, RP101, RP102, RP103 (see page 2).

Address lines A0 to A26 are connected to the expansion connector (page 4). As far as I could see, A27-A31 are unconnected except for being pulled to GND.

Thus with an expansion board, the address space is limited to 128MB, which explains the 112MB DKB 2632 limit. And an A2630 without expansion board has 24-bit address space.

[Presumably the expansion board would be responsible for having the region past the end of its RAM map to address 0??? Though of course that would only benefit the ROM monitor program. I have yet to disassemble the DKB 2632 memory-adding program to see how it determines the memory size.]

[Arnie]

OS4 + Picasso IV Z3 has stopped working since b23. logs and pics attached.

EDIT: I've just noticed that the NTSC box in the display settings is always selected. If I set it to PAL restart and then press F12, after WB has loaded, it's gone back to NTSC?

Edit: Picasso IV Z2 works OK.