Autore Topic: BiNGo: OS 4.1 su WinUAE PPC  (Letto 10271 volte)

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
BiNGo: OS 4.1 su WinUAE PPC
« il: 16 Settembre 2014, 10:07:11 »



Finalmente Toni Wilen ha deciso di emulare il PPC, ora sarà possibile utilizzare i nuovi OS 4.X su PC. Fioccano le discussioni sul forum per segnalare a Toni Wilen i vari bug riscontrati, in QUESTA pagina web è possibile seguire o interagire con il bravo programmatore, allego i primi screenshot fatti dagli utenti del forum e la versione più recente di WinUAE (rilasciate 5 versioni in pochi giorni) by Toni Wilen.

WinUAE 29.2 beta 9




Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #1 il: 16 Settembre 2014, 10:07:48 »
Anche se WinUAE PPC e solo all'inizio, qualche info su quanto emulato in una versione già vecchia, dopo questa, uscite altre 3 versioni.

WinUAE v28.2 beta 6

- Added NCR53C94/FAS216 SCSI chip emulation (from QEMU)
- Added Blizzard1230IV/Blizzard1260 + Blizzard SCSI Kit IV emulation. SCSI Kit v8.5 ROM added to rom scanner.
- Added CyberStorm MK1 and CyberStorm MK2 emulation, map rom and SCSI included.
- Blizzard 2060 (map rom not emulated) and Warp Engine works now.
- CyberStorm PPC and Blizzard PPC 0xFFF00000 mapping improved, now switches correctly between KS map rom and PPC boot code locations. BPPC now correctly attempts to start flash built-in PPC support code during boot and hangs because PPC won't respond.
- Added warning message when BlizzardPPC or CyberStormPPC PPC CPU gets booted.
- Remap UAE Boot ROM (if needed) to secondary backup location if Blizzard PPC is enabled, if MMU emulation is enabled BPPC will remap normal boot ROM backup location causing boot hang.
- Added CyberStorm MK2 flash rom chip emulation, map rom and disable key support (=HALT4).
- Added CyberStorm MK2 full 128k rom image support (64k of autoconfig rom and 64k of diag rom)
- Flash chip emulation compatibility improved, fixed CSMK2 flasher infinite loop.
- Accelerator memory option now automatically changes CPU board memory if accelerator uses same memory type.
- Added keyboard to help Phase5 boot rom key detection, it still wasn't realiable enough with some boards.
- Added one second boot delay option to misc panel, allows easy access to boot menus without need to slow CPU emulation speed.
- Added 'Te' command to debugger, shows expansion autoconfig board information.
- CPU slot memory region was accidentally removed from mman list, causing random crashes in some JIT configurations.
- 68040+ more compatible / "cycle-exact" mode cache flush instructions didn't do anything.


Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #2 il: 16 Settembre 2014, 10:08:08 »



WinUAE v28.2 beta 9 Nuove Specifiche


– PearPC PPC emulator core added. Only because it was very easy to add, it may not be compatible enough. (and it isn’t, at least not fully compatible, at least it has some unimplemented instructions, some programs or operating system surely won’t work)
– PPC disassembler added to debugger (“dp”, PPC mode is remembered, use “do” to switch back to m68k)
– Windowed mode status bar shows PPC state (if CyberStorm PPC or Blizzard PPC selected). Shows 4 possible states: STOP (inactive), RUN (executing instructions), SLEEP (low power state, waiting for interrupt), CRASH (CPU emulator detected something bad, like invalid instruction etc)
– BlizzardPPC memory GUI adjustment fixed.
– Fixed 68020/030 CE + fastest possible hang if program executed loop that didn’t do any memory accesses.
– 68040/060 CINVx instruction was still disassembled strangely.
– Adjusted 68040/060 “cycle-exact” mode timing, also if data cache is enabled, emulate all data memory accesses as immediate. (until data cache is emulated fully)
– CyberStorm MKII F0 ROM section of flash rom is now flashable. (third party mk2diag flash updater works)
– Blizzard PPC flash rom chip emulation now works correctly (was wrong mapping and wrong flash chip device code..)
– Added special JIT indirect CPU core that supports code execution from non-linear and/or aliased memory. Technically also should allow to emulate A2091/A590 but it still crashes for some reason. (But at least now it executes some ROM code before accessing invalid memory. A2091/A590 is perfect test case because it does not copy driver code from autoconfig ROM to RAM like most other HD controller drivers do, code runs directly from ROM and same memory “bank” also has IO registers)
– Memory allocation source clean up. Can break nearly anything..
– SCSI CD READ CD command didn’t read audio tracks 2+.
– Entering debugger forze the emulator if m68k CPU was stopped with STOP instruction and all interrupts disabled.
– NCR53C770 emulation tweaks, fixes netbsd hang. Now it gets unexpected interrupt, no fix available yet.
– Version bumped to 2.9.0

UAE Boot ROM is needed if any following option is enabled:
- "UAE" HD controller (HDF or directory)
- automount removable drives
- bsdsocket.library
- uaeserial.device
- uaescsi.device
- uaenet.device
- tablet emulation
- uaegfx RTG
- >2M chip RAM
- 32bit chip RAM

PPC Notes:

– Only a proof of concept currently.
– Automatically enabled when CyberStorm PPC or Blizzard PPC emulation is selected.
– Only PearPC interpretive PPC emulation is currently supported. Speed is totally irrelevant at this point.
– PPC emulator runs in separate thread, it requires special handling with PPC IO accesses, IO accesses are serialized and sent to m68k-side. Plain memory accesses are direct. (This assumes M68K is still doing Amiga housekeeping duties and PPC is mainly used as a co-processor, probably will cause huge performance hit if PPC does everything, for example when running PPC-only operating systems)
– Should be fully m68k JIT compatible, at least in indirect mode.
– Dual core CPU or better required. If you don’t have one, you are not allowed to report anything, sorry.
– PowerUP kernel does not work (hardware is not fully emulated). WarpOS appears to work.
– Do not use BlizzardPPC, it has (currently incompatible) PowerUP in flash and it runs at boot.
– Make sure CPU speed is fastest possible. PPC IO access serialization will be slowed down if m68k is waiting for chipset.

(Donations would be nice because PPC stuff is even more boring than “normal” stuff. Thanks Toni)

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #3 il: 16 Settembre 2014, 10:08:57 »
QUI si possono scaricare le flash rom e il flash update della cyberstorm

A distanza di 24 ore una nuova release WinUAE v28.2 beta 10 Nuove Specifiche, ecco le nuove specifiche:

WinUAE v28.2 beta 10

- Added CyberStormI/II/II/PPC and Blizzard PPC flash rom images to rom scanner, name based detection only. (Remember to click ROM rescan button) Now opens usual ROM missing dialog when flash rom image can't be opened.
- Added GUI support for manual accelerator board ROM image selection.
- NCR53C770 emulation spurious interrupt fix.
- Reset/exit froze the emulation if PPC CPU was in sleeping state.
- Map ROM checkbox was checked if 128M CPU slot memory was configured (old bug).
- 68030 more compatible/CE with MMU does not use data cache anymore, 68030 caches logical addresses (which will get really difficult and complex to emulate), 68040+ caches physical addresses.
- CyberStorm PPC/Blizzard PPC board emulation improved, PowerUP also works.
- Do not map PPC board FFF00000 memory mirror if no on-board RAM installed.
- Generate CyberStorm/BPPC fake flash rom hardware idenfication data and serial if it is missing.
- If CyberStorm MK3/PPC flash image is 256k or larger, map it like BPPC does it. (Not sure if this is correct)
- Reset with Picasso IV enabled forced hard reset.
- Z2 RTG crash fixed (some configurations).
- Added PPC GUI option to CPU panel. If ticked, selects matching board automatically. Becomes ticked and disabled if board was already selected. 68040/060 only. (CSPPC/BPPC flash boot code uses 68040+ only instructions)
- Move PPC thread to main thread when m68k gets disabled, improves performance of native PPC operating systems. (No need to move IO access messages between threads)
- Disable RTG board if >2M chip ram configured and Z2 RTG configured. (Forgotten address conflict check)
- OSD CPU led changes to "PPC" when PPC is active and m68k is disabled.

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #4 il: 16 Settembre 2014, 10:09:48 »


Arriva una nuova release WinUAE v28.2 beta 11


Over these last few weeks or so, Toni Wilen has been hard at work on the latest version of the Amiga Emulator WinUAE, which provided brand new features for PPC emulation. But as is the case with beta's, Toni was not happy with the current bug problems that caused a number of issues including a non bootable AmigaOS 4.1. But the good news today is, the developer has released WinUAE 2.9.0 beta 11 which not just fixes bugs but allows AmigaOS 4.1 Classic to boot. It would be well worth you updating if you wish to use AmigaOS 4.1 and to get the latest other bug fixes included in the changelog.

Beta 11:

- P5_AMIGA_RESET CSMK3/CSPPC/BPPC bit can be only changed if P5_SELF_RESET is cleared first.
- Never use normal Z3 autoconfig mapping if Blizzard board is emulated to reduce address space conflicts with Blizzard RAM mirror at 0x48000000. Note that this is impossible config, there is no way to have any Z3 boards with BPPC in real world.
- Blizzard PPC rom name renamed to blizzardppc_060.rom and added blizzardppc_040.rom. 68040 and 68060 variants have different (and incompatible) flash rom contents.
- 68000 + no cycle exact and no "more compatible" used wrong memory access method. (b9)
- RTD instruction was set as 68000 compatible (should be 68010+). Incorrect since the beginning.
- Accelerator board ROM select menus didn't select anything.
- Added full CyberStorm MK1 image ($F00000 ROM code is 68060-only), added another 68040 compatible ROM that simulates boards with boot rom jumper disabled or boot rom chip removed. (Original non-flash based boards had separate ROM chip for boot and diag ROMs and boot was only installed if CPU was 68060)
- CyberStorm MK1 SCSI works again.
- Automatically update accelerator board ROM settings when board type is changed in GUI.
- PPC BAT register handling fixed (Technically not emulation bug but OS bug, PPC documentation says '... BEPI and BRPN fields must have at least as many low-order zeros as there are ones in BL.', BEPI and BRPN needs to be masked with BL instead of trusting software doing as documentation says..)
- Added missing PearPC divwu, divwuo, addco, subfco PPC instructions. (Variants of already existing instructions).
- See more at: http://www.indieretronews.com/2014/08/winuae-282-beta-11-amigaos-41-classic.html
« Ultima modifica: 16 Settembre 2014, 10:10:03 da Carlo »

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #5 il: 16 Settembre 2014, 10:10:39 »
Due piccole guide su Screenshot che mostrano come configurare WinUAE e le fasi d'installazione di AMiGA OS 4.0 Classic.
Se si usa l'immagine ISO di OS4 come da Screenshot "nella settima immagine" bisogna spuntare CDFS AutoMount CD/DVD Driver, senza di questa voce il CD non sarà montato automaticamente, stessa cosa se si usa il CD reale, bisogna sempre spuntare CDFS AutoMount CD/DVD Driver altrimenti il BootFloppy non potrà iniziare l'installazione.

Cofiguare WinUAE per Amiga PPC Classic




Fasi installazione AMiGA OS 4.0 Classic

« Ultima modifica: 16 Settembre 2014, 10:10:53 da Carlo »

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #6 il: 16 Settembre 2014, 10:11:48 »
WinUAE v28.2 beta 12



- Windowed mode status bar button mouse click off-by-one fix.
- If command line has more than one -f/-config= parameters, config will be now reset to built-in defaults only once, before first config file is loaded.
- Updated CHD support, uncompressed CHD write support added, can be mounted as read-write hardfile. (CD subchannel support may or may not work, there does not appear to be easy way to convert ccd/sub/img combination to chd)
- CSPPC/BPPC IPL_EMU register's M68K_IPL bits only change when PPC is interrupt master.
- b11 Blizzard accelerator Z3 autoconfig hack didn't work correctly.
- BlizzardPPC flash mapping fixed (b11)
- 68000 mode, without CE and more compatible, RTE instruction didn't check for odd program counter.

- See more at:

http://www.indieretronews.com/2014/08/winuae-290-beta-12-amiga-emulator.html#sthash.oyq3GgA0.dpuf

http://eab.abime.net/showthread.php?t=74263&page=25

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #7 il: 16 Settembre 2014, 10:12:14 »
Nuove release WinUAE v28.2 beta 13

Altro ricco Thred "27 pagine" dedicate a WinUAE PPC  su English Amiga Board



Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #8 il: 16 Settembre 2014, 10:12:41 »
BiNGo, ci sono riuscitooooooooooo ecco il mio primo screenshot di AMiGA OS 4, sul sito inglese stavo passando per uno che non capisce na mazza di AMiGA, in vece non capivo na mazza di Inglese


Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #9 il: 16 Settembre 2014, 10:13:15 »
Nuove release WinUAE v28.2 beta 13

Allego il mio file .uae (file configurazione WinUAE ) OS4 HD.uae

Qualcuno cita una mia scoperta su "English Amiga Board" :)

In attesa di fare qualche montaggio grafico ecco le cose essenziali e più importanti da settare nella GUI di WinUAE

Screenshot WinUAE per Amiga PPC Classic

- Creare un HarFile (misura quanto volete) e formattatelo FFS (importante OFS non booterà mai, altri filesystem non testati)
- CPU come nelle figure postate, 68060, FPU 6882, (JIT ancora non funziona si disattiverà da solo, per il resto guardate lo screnshot allegato)
- ChipSet AGA ( peri resto guardate screnshot allegato)
- ROM (qui attenzione, "cyberstormppc_44.71.rom e cyberstormmk3_44.71.rom" funzionano solo con Kickstart 3.1 A1200, ma non vanno con Kickstart 3.1 A4000, usate cyberstormppc_44.69.rom e cyberstormmk3_44.69, queste ROM invece funzionano con entrambi i Kickstart e sono le più compatibili, usate solo queste per il momento.
- RAM, qui vi troverete già settato "Cyberstorm PPC" per il resto guardate screnshot
- Floppy, qui caricate il floppy se dovete installare da floppy, io ho usato la copiatura manuale del sistema da CD ad HardFile con Dopus4 usando un vecchio sistema OS3, attenzione se usate questo metodo non dimenticatevi di copiare la directory C-68k si trova nella Root del CD, e da qui che parte la prima Startup-Seqence
- CD &  Hardisk Driver, qui maggiore attenzione, l'Hardfile deve essere settato su IDE altrimenti non fa il boot, quando lo dovete usare nel vecchio sistema per copiarci sopra il sistema lo lasciate su UAE (UAE funziona solo su 68k)
- Expansion, qui settate Picasso IV Zorro III per il resto guardate lo screnshot IMPORTANTE, prima di avviare il sistema da qui togliete la spunta su uaescsi.device, (piccola mia scoperta) anche se lo memorizzate al prossimo lancio di WinUAE, lo ritroverete con la spunta, bisogna rimuoverla se volete avviare nuovamente OS4
- Bene accendetevi una sigaretta, o un sigaro per chi ha un sistema scarso e dopo una schermata Blu, una a fasce colorate e una in ROSA, avete vinto il giro d'Italia, scherzo, solo due minuti e AMiGA OS 4.0 sarà pronti all'uso.

QUI invece una bel tutorial i 4 Parti, incluso i settahhi per la connessione in rete, al momento sulla GUI di WinUAE non si può settare nulla in questo senso, pena il mancato avvio di OS4.

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #10 il: 16 Settembre 2014, 10:13:58 »

Nuovo aggiornamento WinUAE 29.2 beta 14


QEMU PPC is still work in progress (by Frode and me), QEMU-side is not yet included. It run for the first time few days ago. It is not stable enough yet but hopefully soon....

- Autoconfig stopped immediately after first A590/A2091 board was configured.
- If VHD check/validation failed after VHD type was fetched (static vs dynamic), VHD was still accepted as valid, possibly crashing soon after. HDF type variable was not cleared, bug since VHD support was added.
- Automatically extend internal SCSI emulation buffer size if larger than current buffer size transfer is requested.
- If 68060 and "Unimplemented CPU emu" is ticked: 68060 unimplemented instructions that are completely unimplemented (CHK2/CMP2/CAS2/MOVEP) still triggered illegal instruction exceptions.
- 68000/010 configuration with 32-bit address space is now allowed.
- Blizzard 2060 ROM loading special case handling didn't work. (Has odd/even parts, others don't)
- Redesigned GUI SCSI expansion ROM selection, easier to add new boards in future.
- Fastlane Z3 SCSI board emulation implemented, another FAS216 based SCSI controller. z3scsi.device from phase5.a1k.org in rom scanner, but it would be nicer to have full dump. SCSI part only, memory part ignored.
- Oktagon 2008 SCSI board emulated. This was interesting, it has "software DMA" (SCSI chip is told to do DMA transfer but "DMA controller" is IO space that CPU reads or writes), it also have 512 byte serial EEPROM used to store config (with only 15 bytes used). EEPROM data is internal, not saved to any file. 6.12 (last release?) boot ROM added to rom scanner. Autoconfig data is currently not confirmed. Support added only because it was quite different than most other SCSI controllers.
- TekMagic 2040/2060 board added. 1.0 tekscsi2.device ROM added to ROM scanner, both odd/even pair and merged rom supported. NOTE: tekscsi2.device has a bug that does not allow RDB filesystem loading. Fast RAM expansion is not supported, it seems TekMagic fast RAM can also start from 0x02000000, not the usual 0x08000000. tools/showconfig output needed.
- NCR53C710 SCRIPTS DMA wasn't correctly started when in manual start mode. (tekscsi2.device)
- Added support for non-MMU bus error caused by invalid memory accesses, including 68000/010/020 models which normally can't generate bus errors but perhaps some expansion hardware will need it in future.
- Screenshot with D3D shader filter + take screenshot before filtering ticked saved final D3D output, not original unfiltered buffer.
- "SCSI (auto)" now works with all SCSI boards. Selects first SCSI board that is enabled. (In same order as select menu lists SCSI controllers)

Some code restructuring:

- Autoconfig board handling rewritten yet again, removed lots of code duplication and moved most duplicated autoconfig logic from board specific files to common expansion.cpp.
- Autoconfig board ROM config handling reorganized, now it is much easier to add new Z2/Z3 boards.
- Replaced my hacky serial EEPROM emulation with better one from QEMU, made it generic (previously only used in CD32 emulation).
- Removed A590/A2091 and A4091 Expansion panel checkboxes, enable/disable is now ROM selection. (ROM selected = enabled, ROM selection empty = not enabled)
« Ultima modifica: 23 Dicembre 2016, 19:01:45 da Carlo »

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #11 il: 16 Settembre 2014, 10:15:57 »
WinUAE 29.2 Beta 15


- "ROM disabled" A2091/A590 ROM option was not visible (b14)
- Blizzard board ROM code was ignored (b14)
- Log window was opened when PPC CPU started (b14)
- Dragging adf file over window mode bottom bar HD led didn't mount it as a harddrive.
- Mounting adf as a harddrive uses adf's real volume name instead of host-side file name.
- Added support for sub memory banks, can divide normal 64k UAE memory bank in to smaller sub memory banks. Mainly needed to properly map PPC CyberStorm MK3/PPC SCSI IO and SCRIPTS RAM for QEMU PPC.
- SCSI CD emulation via NCR SCSI (53C94/FAS216 or NCR53C710+) chip didn't flash CD led.
- Added hack that prevents Picasso IV switching temporarily to RTG mode immediately after reset. (Picasso IV does not use simple signal passthrough like other cards)
- Switch to/from hardware RTG mode only after mode has been stable at least 0.5 seconds.
- Show CD insert/eject messages in new status bar message area. (Should it show real volume name instead of file name?)
- Quickstart CD eject button was always disabled.
- Status bar NVRAM led also shows accelerator board flash write accesses. Includes also writes that only enable chip ID read mode.

- PPC IO access completely rewritten, most IO areas are now directly accessible and only special regions (custom chipset and CIA require locking. Very slow IO message passing system is completely gone.
- QEMU PPC core support. Read separate notes!

QEMU built as a library (qemu-uae.dll) e QEMU dependencies  (Estrarre nella stessa directory dove risiede winuae.exe)


QEMU PPC instructions and information

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #12 il: 16 Settembre 2014, 10:16:41 »
WinUAE 29.2 beta 16

- GUI (and log) showed wrong size for very large drives (>1T). Visual problem only.
- Fixed F12/pause hang when PPC was active.
- Fixed uaegfx RTG in Z2 mode memory mapping (b14)
- 68040 MMU MOVE16 fault size was wrong. (Cache line, not long)
- 68060 MMU read-modify-write fault had inverted read/write status.
- QEMU PPC vs UAE side memory banks are now dynamically mapped.
- PPC CPU HID1 set to more correct value, detected CPU clock is not same as bus clock anymore.
- QEMU TCG (JIT) buffer was too small, real world PPC programs run now much faster.

Nuova qemu-uae.dll   (Estrarre nella stessa directory dove risiede winuae.exe)

N.B. Just a note for better performance: I recommend to use CyberStorm SCSI instead of mainboard IDE (SCSI works since QEMU PPC was added). Select "Accelerator board SCSI".

SCSI is fully DMA, software basically only needs to say "transfer this much data from block x to block y, transfer all data to/from address z", everything else is done by UAE host side code.

IDE is PIO = emulated code needs to do everything "manually", (reading or writing requires word by word CPU reads or writes) and running emulated code is always slower than native code, especially JITs rarely work very fast when they need to continuously access IO addresses.

Dopo aver provato la beta 16, aggiornato la qemu-uae.dll, settato l'hardfile da IDE a SCSI, OS4.0 Classic è diventato velocissimo, carica il sistema in meno di 2 minuti e le finestre si aprono velocemente, OWB si carica quasi immediatamente, calcolando che ho solo 2 core, se andiamo avanti così con un i7 si rischia di superare il "reale"

Per i curiosi cliccando QUI è possibile smanettare su un OS4 Virtuale (solo piccole funzioni)


Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #13 il: 08 Dicembre 2014, 21:53:19 »



WinUAE 29.2 Beta 17


- Hard reset now forces reload of KS ROM if maprom is active, previously map rom mapped image was still in use after hard reset.
- Fixed some more Z3 autoconfig bugs introduced in recent betas autoconfig updates.
- Only add VirtualAlloc() MEM_TOP_DOWN flag when OS is XP. For some unknown reason with MEM_TOP_DOWN my system suddenly started giving less address space than without it..
- A1000 with full KS ROM configured (instead of A1000 boot strap ROM) didn't boot since b9.
- Reset didn't clear QEMU PPC JIT translation buffer, fixes mysterious hangs after reset.
- Added main thread sleep option slider to GUI, reduces CPU usage when M68K is stopped and only PPC is active.
- PPC CPU model can be manually configured using ppc_model=<name> config entry. Can be any QEMU supported
PPC CPU model name string. (Model strings are in qemu source file target-ppc/cpu-models.c)
- Automatically disable m68k JIT autoconfig hack if only PPC CPU is active when autoconfig starts after reset.
- Fixed WarpOS (possible PowerUP too) semi-random program hang caused by lost PPC interrupt(s).
- Allow m68k JIT direct with accelerator board if board is not Blizzard model (no Blizzard memory aliases) CyberStorm PPC + m68k JIT direct at least seems to work, no guarantees.

Important:

- QEMU PPC libraries are now loaded from <winuae path>pluginsqemu. Old location is not supported anymore. Move all qemu dependency libraries and qemu-uae.dll to new path.

Offline Carlo

  • Moderatore globale
  • Utente storico
  • *****
  • Post: 3078
  • > BRINDISI <
    • Mostra profilo
    • www.plagimusicali.net
    • E-mail
Re: BiNGo: OS 4.1 su WinUAE PPC
« Risposta #14 il: 08 Dicembre 2014, 21:53:51 »
WinUAE 29.2 Beta 18


- "Pause emulation when xyz" option remained forever stuck in pause mode if PPC CPU was active.
- PearPC PPC emulation removed.
- Freezer cartridge ROMs had disappeared from GUI.
- Freezer cartridges didn't work.
- Force Direct3D mode if hardware RTG board + PPC enabled. DirectDraw has glitches. (Will also have glitches in non-PPC mode but there is no need to change it yet)
- CSPPC/BPPC interrupt controller IO address accesses were not thread safe, caused random lost or stuck interrupts.

qemu-uae.dll has not changed since b17.