WinUAE 3.3.x Beta Series Development

Riflessioni, eventi, curiosità

Re: WinUAE 3.2.x Beta Series Development

Messaggioda AMIGASYSTEM » dom gen 10, 2016 7:56 am

Immagine


WinUAE 3.3.0 Beta 1 (09 Gennaio 2016)

WinUAE 3.3.0 Beta 1 (64Bit) (09 Gennaio 2016)

Main rule: Before reporting, make sure bug is NOT in previous offical version. It must be unique to this beta series! (If it is -> post in separate thread). No feature requests.

More information

UAE Configuration

Game Ports panel custom mapping finally makes sense.

First phase of hardware based host/emulation interface done. uae-configuration is now OS4 compatible. Add "uaeboard_mode=1" to config file to enable it.

- Added extra validation checks for STORAGE_DEVICE_DESCRIPTOR, buggy drivers may return invalid (negative) offset values.
- 64-bit JIT harmless "Warning! 12 is locked" log spamming disabled.
- Updated copper/blitter cycle conflict emulation. It only triggers when CPU writes to COPJMP, Copper is waiting and Copper DMA is enabled (and blitter uses same cycle). If Copper DMA was off, bug won't trigger, even if DMA gets
enabled few cycles later. Copper bug emulation is again always enabled if 68000 and cycle-exact config.
- Cancel main thread sleep state immediately (Sleep due to CPU idle or similar) if PPC thread caused mainboard interrupt. This should reduce PPC to M68K interrupt emulation latency.
- Hardware RTG emulation rendered same frame twice in some situations. Caused very slow performance in triple buffered mode.
- Debugger keyboard presses were buffered and output to Amiga-side when debugger was exited.
- Starting disk DMA does not flush Paula internal 16 bit buffer. Poll DSKBYTR for DSKSYNC, immediately start disk DMA with WORDSYNC enabled: following sync word must not be missed. (Original Virus really slow loading in cycle-exact mode)
- Chip ram was marked as 16-bit Fast RAM for the CPU (no DMA contention emulation) if any memwatch point was active.
- Amithlon partition type (0x78/0x30) support was broken, partitions were detected but it was not possible to mount them.
- Added SX32 Pro board and ROM image. (Not all RAM sizes are correctly mapped)
- Only unmap Z3 Fast RAM at reset if Z3 mapping mode is "Real" for better compatibility with old configs that assume Z3 RAM does not temporarily disappear at boot.
- JIT on/off on the fly change without other CPU settings changed at the same time with uae-configuration didn't work.
- Hardware emulation autoconfig board UAE interface first working feature: uae-configuration now works under OS4 Requires also updated uae-configuration, interface can also work under other non-m68k AmigaOS operating systems, only requirement is simple native uae-configuration port. Interface design is not final yet.
- If CSPPC or BPPC is booted with empty or zero size flash rom image, fake resident idtag is automatically added that fools official flash rom updater to detect working board, "updating" the empty flash with full image (updater contains full flash rom image in encrypted format)
- Debugger memwatch points can now match only CPU instruction (CPUI) or only CPU data accesses (CPUD, CPUDR, CPUDW)
- "Heat map" debugger added, shows optional visual heatmap of CPU and DMA accesses. Can list highest addresses used by CPU instruction fetches or all addresses that single device accessed (Some DMA channel, CPU)
- Some AGA modes were incorrectly detected as bitplane DMA overrunning causing screen corruption.
- AROS ROM updated.

Input system and mapping updates:

- Added SPC_SWAPJOYPORTS input event, swaps gameports joystick ports.
- Added END+J default mapping = SPC_SWAPJOYPORTS.
- Device autoswitch didn't ignore button release without matching press.
- Device autoswitch switches to new Game Ports custom event if it has fire button mapped to mouse or gamepad.
- "WinUAE null keyboard" renamed to "WinUAE keyboard", this is now the default global virtual keyboard. GamePorts panel only uses this keyboard, multiple keyboards are only supported in Input panel mode and only if manually enabled. Reduces complexity and confusion when moving configurations between systems with different number of keyboards.
- Game Ports custom mapping rewritten. Now Game Ports list has 6 custom slots which can me inserted to any joystick port. New custom mapping data is also saved to separate config entries, one per slot.
- Old Game Ports custom config is automatically converted to new custom mapping system.
- Removed X-Arcade built-in layouts. Re-create them with new custom mapping system if needed.
- Cleared custom input event string equals setting event to "<none>".
- Fixed since the beginning bug that caused incorrectly matched input device(s) and input config when config was loaded with different connected input devices and order of devices was also different.
- Rewritten game ports validation (Detect and fix if same device in multiple ports etc..).
- Old config files should still work like previously except: game Ports custom mapping and first keyboard input config goes to WinUAE keyboard slot.
- Last few Game Ports panel inserted devices (layout or real input device) are remembered. For example if config is loaded with joypad A inserted in port 2 but pad is not plugged in, then user manually changes it to joypad B. Now if pad A is later reinserted and pad B is removed, A is automatically put in port 2. It also works with keyboard layouts or new custom layouts, if keyboard layout was previously selected, then it was later replaced with gamepad, if gamepad is unplugged on the fly, previous keyboard layout is automatically selected.

EDIT: Last minute bug found, Game Ports panel keyboard layouts A/B/C do not load correctly from config file.
Ultima modifica di AMIGASYSTEM il dom gen 17, 2016 12:17 am, modificato 3 volte in totale.
Immagine - AROS One Home Site - AfA One - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 5513
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: WinUAE 3.3.x Beta Series Development

Messaggioda AMIGASYSTEM » mar gen 12, 2016 8:56 pm

WinUAE 3.3.0 Beta 2 (12 Gennaio 2016)

WinUAE 3.3.0 Beta 2 (64Bit) (12 Gennaio 2016)

- Game Ports panel keyboard layouts didn't load from config file. (b1)
- Only first (of 3) Input panel keyboard config slot was loaded correctly. (b1)
- Other input handling fixes (very old, old and b1) and updates. Some problems probably still remain unfixed.
- GUI allowed unsupported combination: more compatible CPU ticked in JIT + 68040/68060 modes.
- Hardfile SCSI emulation READ CAPACITY block count off by one if PMI bit was set.
- MODE SENSE (10) added to HD SCSI emulator.

This should fix most b1 input compatibility problems. Complain immediately if old Game Ports or Input panel input mapping does not work anymore. (But rememeber to explain it better than "it does not work"
Immagine - AROS One Home Site - AfA One - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 5513
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: WinUAE 3.3.x Beta Series Development

Messaggioda AMIGASYSTEM » dom gen 17, 2016 12:09 am

Importanti novità riguardo l'emulazione di OS4, il bravo Toni Wilen ci sta lavorano a spron battuto grazie anche alle donazioni che sono sempre benaccette, nelle parossime release anche OS4 potrà scambiare dati con lle directory di Windows e non solo, allego due citazione integrale di Toni.

Big update!

uaehf.device ("UAE" controller) hardfile works in OS4!. Directly booting from UAE hardfile not yet tested but at least automount works as expected.

Communication protocol is currently very simple, not thread safe, busy looping, lots of logging and so on. Don't ask about performance. Functionality and stability always comes first.

There is still some really nasty and tricky cases to support before directory hardfiles or bsdsocket or any other more complex expansion can work, for example ability to call Amiga library functions from host side.

This is not yet stable enough for public tests but soon, I expect something usable will be available in few days to 1 week or so..

This information can be posted in other forums/news sites. I think many users have been waiting for this.. And donations are still accepted


------------------------------------

[b]And even more bigger update!

Directory harddrives now work in OS4!

(Directory hardfiles didn't need library calls, only uaegfx and bsdsocket needs those)
Immagine - AROS One Home Site - AfA One - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 5513
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: WinUAE 3.3.x Beta Series Development

Messaggioda AMIGASYSTEM » dom gen 17, 2016 1:22 pm

Nuovo comunicato di Toni

Some notes, there is also possibility for "you are completely on your own" test version later today..

Currently supported UAE devices:

- Directory harddrives.
- uaehf.device (hardfiles). HD_SCSICMD is NOT supported yet.

Supported but not tested:

- uae.resource
- Some "uaelib" functions

Not yet supported (lots more work needed):

- uaegfx
- bsdsocket.library
- uaenative.library
- clipboard sharing
- uaescsi.device
- uaenet.device
- virtual mouse driver
- on the fly directory harddrive changes.

And everything else that was not mentioned.

Notes:

Host<>Amiga communication system is currently busy waiting, both PC and Amiga sides. Until it gets replaced with proper waits/interrupts (very complex task) at least triple core CPU is recommended.. (one for main thread, one for PPC, one for trap thread). I don't know if there is any difference but it is not my problem as usual

Communication is also slower than normal host<>Amiga (which is practically instant) because every read or write that accesses Amiga memory needs to be done in Amiga side (due to non 1:1 logical/physical mapping). Lots of easy improvents to do here but optimizations come later

As usual, stable and working implementation is the most important and first requirement.
Any non-trivial optimizations will come (much) later.
Immagine - AROS One Home Site - AfA One - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 5513
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: WinUAE 3.3.x Beta Series Development

Messaggioda AMIGASYSTEM » dom gen 17, 2016 8:27 pm

Prima versione Alfa di WinUAE OS4UAE, al momento non ho capito bene cosa eliminare o aggiungere alla configurazionie di WinUAE, se qualcuno vuole sperimentare e magari postare i risultati, allego la prima Alpha Release:

WinUAE 3.3.0 OS4UAE


Very alpha quality test version:


If you post about any problem: log and winuaelog.txt MUST BE included. Log illegal memory accesses in Misc panel must be checked.

Posts that are useless or annoying will disappear.

See my previous post for supported features.

Extra notes: shutting down emulation can crash if trap thread is still waiting. It is considered normal at this point.

Directory harddrive performance is not that good (dozens of context switches/dos packet). Make sure hardfile/directory harddrive boot priority is below CSPPC SCSI if booting from SCSI. Equal boot priorities = UAE device will boot.

Add "uaeboard=full+indirect" to config file to enable new trap system.
Immagine - AROS One Home Site - AfA One - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 5513
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: WinUAE 3.3.x Beta Series Development

Messaggioda AMIGASYSTEM » gio gen 21, 2016 1:34 am

Update:

- Lots of internal updates. Performance is still not that good.
- uaegfx is now working!
- uaehf.device HD_SCSICMD should also work (Updated)

Simply copy uaegfx and uaegfx.info from OS3 WB to OS4 devs:monitors. Note that NOBLITTER tooltype may be currently faster due to slow traps.

WinUAE 3.3.0 OS4UAE


Do not forget "uaeboard=full+indirect" config file entry.
Immagine - AROS One Home Site - AfA One - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 5513
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: WinUAE 3.3.x Beta Series Development

Messaggioda AMIGASYSTEM » ven gen 22, 2016 1:02 pm

OK ci siamo primo screenshot che mostra come l'Hardisk OS4.1 non è caricato più come Accelerator (Cyberstorm PPC) ma come HD Controller UAE (come si faceva con OS3), questo significa che ora tutti i volumi o cartelle Windows sono supportate e possono comparire sul Workbench e quindi condivise con OS4, stessa cosa per gli HardFile di qualsiasi OS Amiga e qualsiasi filesystem. Altra novità è che tutte le Scheda Video sono supportate, ora oltre alle Picasso II e IV su OS4.1 si può utilizzare anche la UAEGFX usata comunemente su OS3 GFX. Naturalmente siamo ancora agli inizi e OS4.1 al momento risulta essere più lento rispetto a prima almeno sul mio ormai vecchio PC, aspettimo che il bravo Toni finisca il lavoro e poi ne vedremo di belle !

Immagine
Immagine - AROS One Home Site - AfA One - AROS One x86 - AROS One 68K - WinUAE OS 4.1 -

Miei AMIGA
Amiga 4000/Cyberstorm MK II/060/Picasso RAM 6MB Kick 3.1
Amiga 1200/030 Ram 16 Mega HD 500 MB
Amiga 1200/040 Ram 32 Mega HD 500 MB
Amiga 600 HD 20 MB
Amiga 600 Doppio Kickstart 2.05-1.3
Amiga 500 Plus Doppio Kickstart 204-1.3
Amiga 500
CD32/SX-32 MK1 RAM 8 MB HD 4G
CD32 Standard
Avatar utente
AMIGASYSTEM

Staff
 
Messaggi: 5513
Iscritto il: ven lug 25, 2008 8:39 pm
Località: Brindisi

Re: WinUAE 3.3.x Beta Series Development

Messaggioda provolik » ven gen 22, 2016 1:48 pm

WOW! Bisogna ammettere che sta facendo veramente un bel lavoro!
ProvoliK
Avatar utente
provolik

Veterano
 
Messaggi: 107
Iscritto il: lun ago 10, 2015 2:54 pm

Re: WinUAE 3.3.x Beta Series Development

Messaggioda marmotta » ven gen 22, 2016 1:58 pm

Ora manca solo abbattere il limite della ram! Non so in che modo.... ma sarebbe la ciliegina sulla torta! :ammicca:
Avatar utente
marmotta

Eroe
 
Messaggi: 1851
Iscritto il: gio dic 30, 2010 11:07 pm

Re: WinUAE 3.3.x Beta Series Development

Messaggioda Kyle » ven gen 22, 2016 3:11 pm

Ottimo lavoro Toni :felice:
AmigaOne X5000/20 - 4GB - RadeonHD 4670 - HD 1TB + 512GB- AmigaOS 4.1 Final Edition / MorphOS 3.16
A1200 Diamond Red - Vampire V1200 - 130 MB - CF 32GB - Gotek Drive - Coffin R59
A1200 - Blizzard 1230 IV + FPU - 34 MB - KS 3.1 - CF 4GB - ClassicWB Full
A3000 - 18 MB - KS 3.1.4 - ClassicWB 3.1.4
CDTV - 10MB - T30 - Extended roms 2.30 - KS 1.3/3.1 - built in Gotek Drive - ClassicWB 68K
A500 & A570 - 3MB - KS 1.3 - OS1.3
Avatar utente
Kyle

Leggenda
 
Messaggi: 8787
Iscritto il: dom dic 24, 2006 11:15 am
Località: Livorno

Re: WinUAE 3.3.x Beta Series Development

Messaggioda cip060 » ven gen 22, 2016 5:23 pm

eh quello mi sa che non ci puo' fare nulla!!visto che e' un probema di os4 e della versione blizzard ppc il limite della ram!!non dipende da toni
Avatar utente
cip060

Leggenda
 
Messaggi: 7933
Iscritto il: lun feb 17, 2003 9:19 pm
Località: Usa

Re: WinUAE 3.3.x Beta Series Development

Messaggioda Mck » ven gen 22, 2016 5:26 pm

Toni è instancabile.
I MIEI AMIGA
4000T OS 3.9 PPC/68060+CyberVisio 64/3D
4000D in Tower OS 3.9 PPC/68060+usb Deneb+Toccata+Mediator
4000D OS 3.9 68060 ram 32m+V-lab+Sch.video EGS
3000T OS 3.9 PPC/68060+Usb Deneb+mediator+Voodoo 5
3000 OS 3.1 68040+emul. pc 286
2000 processore 68030+genlock+emulatore pc 8080
1200 Tower OS 3.9 PPC/68060+Mediator
1200 OS 3.1 68060+Rete pcmcia
1000 esp. Ram 4M
600 esp. ram+HD
500 Plus esp. ram
500 esp. ram
CDTV
CD32
CLONI AMIGA
Sam440ep-Flex OS 4.1
EFIKA MorphOS 2.6
Avatar utente
Mck

Eroe
 
Messaggi: 827
Iscritto il: ven nov 26, 2010 1:11 pm

Re: WinUAE 3.3.x Beta Series Development

Messaggioda marmotta » ven gen 22, 2016 5:58 pm

cip060 ha scritto:eh quello mi sa che non ci puo' fare nulla!!visto che e' un probema di os4 e della versione blizzard ppc il limite della ram!!non dipende da toni


Credo che un modo per aggirarlo ci possa essere, ad esempio non ho ancora capito se si puo' usare la Z3 ram come swap... oppure UAE potrebbe usare la Vram come fast ram come fa la Mediator.
Avatar utente
marmotta

Eroe
 
Messaggi: 1851
Iscritto il: gio dic 30, 2010 11:07 pm

Re: WinUAE 3.3.x Beta Series Development

Messaggioda MacGyverPPC » mar gen 26, 2016 10:35 pm

Penso che sul mio notebook abbastanza scarso per AOS4, metterò AOS3.9 ,che dovrebbe risultare abbastanza decente e simile al mio vecchio 1200 PPC con BVision :felice:
Sempre che non ci siano problemi , dato che WinUAE sembra più mirato a OS4 in fatto di ottimizzazioni,
ma credo che il fatto renda anche su OS 3.9 se in emulazione hanno lasciato la migrazione tra PPC e 680xx attiva.
Se non è così , posso lasciar perdere da subito l'idea di sprecare tempo a riesumare i dischi delle schede dedicati al 3.9 per la parte PPC :riflette:
OS4.1.3Immagine+SAM= ImmagineNG c'è!
SAM440EP: OS4.1.4Up4:con USB2.0 UP,RunInUae integrato con Kickstart 3.1,1.3,CD32 originali, MUI migliorato ecc/HD400GbSata/masterizzatore sataDVD/SB Audigy5.1.
AMIGA1200PPC/060(HomeTower):OS4Classic/USB/BlizzardPPC/BVision/Ram128Mb/HD/CD-DVD/RW :rock:
AMIKIT WinUAE:OS3.9/OS4 FE : AMD A8 x64
Advance
Multitask
Integrated
Grafic
Architecture
Avatar utente
MacGyverPPC

Leggenda
 
Messaggi: 10872
Iscritto il: sab set 22, 2007 4:51 pm
Località: Alessandria

Re: WinUAE 3.3.x Beta Series Development

Messaggioda Seiya » mer gen 27, 2016 1:12 pm

WinUAE sarà sempre meglio emulando il 68k, stai tranquillo.
Le ottimizzazioni restano per la maggiore su questo sistema. Aggiorna anche la parte relativa a OS4 per sistemare qualcosa qui e li.
Il grosso del lavoro è sull'emulazione cpu e fpu PPC che mi sa ferma da un sacco di tempo ormai..
Seiya

Supremo
 
Messaggi: 3654
Iscritto il: sab lug 04, 2009 11:22 pm

PrecedenteProssimo

Torna a Amiga in generale

Chi c’è in linea

Visitano il forum: Nessuno e 26 ospiti

cron