Menù principale

Notizie  Grafica  Forum  Links  Retro Trailer  Recensioni  Modelli Amiga  Storia Amiga  Retro-Gamers  Lista Utenti  Contatti  Policy sito

Login

Nick Password

Registrati - Recupera dati

05 Maggio 2015 Postato da: carlo WinUAE 3.4.x Beta Series Development

WinUAE 3.X.X Fix Aggiornato Modificato il 26/08/2016 alle ore 19:12:10

Commenti: 247  Aggiungi - Pagine: 1...-9-10-11-12-13

Pagine: -1-2-3-4-5-6-7- [8] -9-10-11-12-13- Alecos Post inviati: 1615 Commento 141 Alecos 15 Febbraio 2016    15:13:54 Tengo a precisare che se non si installano le DirectX9x non va nulla, WinUAE dalle ultime versioni obbliga ad usare le DirectX9x altrimenti non fa il boot correttamente l'emulatore o addirittura non si vede nulla nella finestra dell'emulatore. Prima era d'obbligo per testare OS4.x e adesso sono obbligatorie anche per il vecchio ambiente di emulazione OS3.9. Le DirectX9x funzionano anche su Windows 10 RTM build 1152. DirectX End-User Runtimes (June 2010) Grazie Carlo. Commento modificato il 15/02/2016 alle ore 15:27:04 Commento 142 cip060 15 Febbraio 2016    16:00:37 Esatto infatti sul portstile nuovo con w10 di mia mamma non va un cavolo e anche parecchi emulatori in generale non vanno senza direct x 9c AfAOne Post inviati: 11780 Commento 143 carlo 21 Febbraio 2016    18:16:26 WinUAE 3.3.0 Beta 7 (21 Febbraio 2016) WinUAE 3.3.0 Beta 7 (64Bit) (21 Febbraio 2016) - Fullscreen + paused + enter GUI: GUI was invisible. - OSD FPS counter shows 'P' in pause mode. - Directory filesystem drive total/used values are not anymore converted to internal block count before again converting to AmigaOS block count. Reported Amiga-side size is now accurate. - Create more sane looking fake geometry for directory harddrives. (Not that anyone really cares) - Directory filesystem harddrive block size is dynamically adjusted to enable correct drive size information even if drive is large (>2T), as long as AOS also supports it (OS3.9+ probably required). - If m68k FPU is in float (32-bit) precision mode, force output register value to 32-bit precision after each host FPU operation to guarantee correct result. (Kilofix / Iris missing geometry) - Clear UAE boot ROM temporary variables at reset. (OS4.x reset loop after warm reset) - Added 20 bytes of empty space after directory filesystem volume node. If OS4 decides to use it for something. (OS4 volume node is 20 bytes larger. UAE puts it in hardware board space, it can't use DOS functions to allocate it). - Implemented OS4 ACTION_FILESYSTEM_ATTR directory filesystem dos packet. - Selecting none in Game Ports reverted back to previously selected device/layout. AfAOne Post inviati: 11780 Commento 144 carlo 5 Marzo 2016    13:40:59 Puntuale ecco il nuovo aggiornamento di Toni, in questa release incluso il supporto per le Immagini ISO .NRG di Nero Burning come da me gentilmente richiesto . WinUAE 3.3.0 Beta 8 (05 Marzo 2016) WinUAE 3.3.0 Beta 8 (64Bit) (05 Marzo 2016) - Game Ports joystick type was always empty (undefined). - Quickstart panel CDTV/CD32 CD path name label was "DF1:", not "CD". (Broke when bridgeboard drive support was added) - Dragndrop to emulation window didn't work correctly until GUI was opened at least once. - Added screenshot autoclip mode, uses autoscale display size/position detection. Also added following config file only entries: (all config entries need win32. prefix) - screenshot_min_width and screenshot_min_height: minimum autoclip size in lores pixels. - screenshot_max_width and screenshot_max_height: maximum autoclip size in lores pixels. - screenshot_width and screenshot_height: forced screenshot size (non-autoclip mode only) - screenshot_x and screenshot_y: position/offset of screenshot (non-autoclip mode only) - screenshot_mult_width and screenshot_mult_height: 1x, 2x, 3x, .. 8x screenshot size multiplier. - screenshot_output_width_limit and screenshot_output_height_limit: minimum screenshot size, if original size is smaller, multiplier is increased until width/height is same or larger. - More internal changes to support more than one enabled RTG board at the same time. (Still lots more to do..) - 68020/030 RTE didn't generate exception when it encountered 68040+ or 68010 only stack frame types. - Return error code instead of crashing if bsdsocket emulation sendto() tries to use unsupported raw protocol. - Switching from relative path mode back to normal mode could have caused repeated crashing. - Do not write reserved block at the end of FileInfoBlock back to Amiga side, Pre-2.x dos commands don't allocate complete FIB structure. (Was side-effect of OS4.x compatible trap system) - Basic NERO nrg CD image support added. Data and audio tracks seems to work. - CDFS mounting selects Joliet volume label if found. (Joliet volume label is not restricted to capital ASCII letters) - uaenet.device S2_READORPHAN should not filter unknown multicast addresses. Commento modificato il 05/03/2016 alle ore 14:52:17 AfAOne Post inviati: 11780 Commento 145 carlo 20 Marzo 2016    12:38:22 WinUAE 3.3.0 Beta 9 (19 Marzo 2016) WinUAE 3.3.0 Beta 9 (64Bit) (19 Marzo 2016) - Fixed swapped audio channels if stereo separation was set (b1 cleanup missed code path) - Fixed uaehf.device SCSI emulation sense data possible crash/wrong status. (trap update related) - 32M UAE RTG board was always address space aligned. It is wrong in UAE mapping mode. - Only swallow hardware horizontal and vertical mouse movement when in mouse driver mode, not mouse wheel. - Improved programmed refresh rate hsync start and end validation to prevent crashes if weird mode is set. (BoggleDop / Sanity) - Added hardfile virtual bad block support. uaehf.device and hardware SCSI emulation only. Create geometry text file (<name of hardfile.hdf>.geo) in same directory as hardfile, add badblocks=<blocks> line. (<blocks> can be range, 10-100 or single value or multiple ranges/values, for example 10-100,200,1000-20000) Max 8 bad block values/ranges supported. Error is returned if block in badblock range is attempted to be read or written. - OS4.x UAE trap mode now uses hybrid busy wait mode. Performance has improved again, directory filesystem speed is now fully usable and uaegfx is also noticeably faster. - UAE indirect trap stability updates. Commento modificato il 20/03/2016 alle ore 12:38:59 Post inviati: 46 Commento 146 divsalv 20 Marzo 2016    13:51:45 Scusate l'OT, ma ho appena provato la beta 9, e usando UAE al posto di usare l'scsi della scheda accelleratrice(per impostare l'hdf), il sistema parte, ma non permette la scrittura, anche se i flag di lettura/scrittura sono segnati, poi non riesco a capire se si può usare + di 128 mb di ram per os4.1, perchè vedo che se imposto la f3 fast, il wb (ed anche avail) non la vede, ma showconfig mostra la scheda con la memoria indicata in fase di configurazione, come posso usare + ram? Commento 147 cip060 20 Marzo 2016    17:13:56 Nella realta la cyberstorm ppc mi risulta non supporti piu di 128 mega quindi anche nell'emulazione sara' cosi cpiace64 Post inviati: 4688 Commento 148 cpiace64 20 Marzo 2016    17:55:33 io la sto' testando con 2 moduli da 128 AfAOne Post inviati: 11780 Commento 149 carlo 20 Marzo 2016    18:59:29 Citazione Scusate l'OT, ma ho appena provato la beta 9, e usando UAE al posto di usare l'scsi della scheda accelleratrice(per impostare l'hdf), il sistema parte, ma non permette la scrittura, anche se i flag di lettura/scrittura sono segnati, poi non riesco a capire se si può usare + di 128 mb di ram per os4.1, perchè vedo che se imposto la f3 fast, il wb (ed anche avail) non la vede, ma showconfig mostra la scheda con la memoria indicata in fase di configurazione, come posso usare + ram? Lo abbiamo detto tante volte, WinUAE emula tutti i modelli AMiGA ereditando le stesse limitazioni hardware (kernel), detto questo su OS4 si possono impostare massimo 128MB di RAM su A4000 Cyberstorm e 256 MB su Blizzard A1200, se si vuole impostare su WinUAE 1 GB o più di RAM su Zorro3 lo si può fare solo emulando AmigaOS 68K. Commento modificato il 20/03/2016 alle ore 19:02:54 Post inviati: 46 Commento 150 divsalv 21 Marzo 2016    01:09:44 ok, ed invece per quanto riguarda l'hdf? AfAOne Post inviati: 11780 Commento 151 carlo 21 Marzo 2016    09:32:22 Citazione ok, ed invece per quanto riguarda l'hdf? in che senso? Post inviati: 46 Commento 152 divsalv 21 Marzo 2016    10:44:14 Usando UAE al posto di usare l'scsi della scheda accelleratrice(per impostare l'hdf), il sistema parte, ma non permette la scrittura, anche se i flag di lettura/scrittura sono segnati. ho anche provato a lanciare il prog come amministratore, ma il risultato non cambia. AfAOne Post inviati: 11780 Commento 153 carlo 21 Marzo 2016    14:06:54 Che sistema operativo stai usando? in quale percorso si trova l'hardfile, se hai Windows 10 può essere che nel percorso da te utilizzato il tuo utente non abbia i privilegi di scrittura, se così fosse le soluzioni sono due, una è quella di ereditare sul file i privilegi dal proprietario (operazione non semplice) oppure spostare il file in una zona dove l'utente può avere accesso senza restrizione esempio "Documenti pubblici". Commento modificato il 21/03/2016 alle ore 14:13:28 Post inviati: 46 Commento 154 divsalv 21 Marzo 2016    18:37:05 Come non detto, risolto. Commento modificato il 21/03/2016 alle ore 20:17:45 AfAOne Post inviati: 11780 Commento 155 carlo 21 Marzo 2016    20:41:03 Probabilmente sbagli qualche impostazione, come puoi vedere dal mio screenshot, con l'ultima versione WinUAE 3.3.0 Beta 9 ho avviato os4.1 con queste impostazioni: - Sistema 0S4.1 (Accelerator PPC) HardiskFile - DH2 (Directory Filesystem) Directory Windows - DH0 (UAE.Device) HardFile Partizione Sistema AfA OS - DH1 (UAE.Device) HardFile Partizione Dati AfA OS Suggerimento, ogni volta che setti una nuova configurazione non devi avviarla a caldo, devi chiudere e riavviare WinUAE, se aggiungi HardFile bootable togli la spunta su "bootable" lasciando boot priority a -127, altra cosa da fare ogni tanto è quella di "pulire" WinUAE dal menu tab "Path", in fondo alla gui trovi "reset defaul" e "Clear Disk History" Commento modificato il 21/03/2016 alle ore 20:41:35 AfAOne Post inviati: 11780 Commento 156 carlo 12 Aprile 2016    20:42:13 WinUAE 3.3.0 Beta 10 (9 Aprile 2016) WinUAE 3.3.0 Beta 10 (64Bit) (9 Aprile 2016) - if uaenet.device is online and packet(s) have arrived but there is no pending CMD_READ/CMD_READORPHANs: wait about 2s before dropping it, it is possible that multiple packets will arrive so quickly that Amiga-side TCP/IP stack don't have time to queue more read commands before packets get dropped. - uaenet.device stability fix. - Loading config with unplugged joystick or mouse inserted in either port: previous device was not autoselected. - Filter panel scaling mode active and mouse driver enabled: mouse got stuck in a corner in some situations. - Screenshot input event set to toggle-mode in Input panel: key/button press = create screenshots continuously every frame, following key/button press = stop automatic screenshots. - one genlinetoscr function (16-bit 4x horizontal stretch) used genlock function in non-genlock mode. - Adaptive Sync "vsync" mode added. Optimal setting designed for G-Sync/FreeSync monitors. Also allows 100/120Hz black frame insertion mode. Not very stable yet. (Don't try to use without adaptive sync hardware..) - 68040 MMU mode SR M-bit handling was missing. 68060 SR M-bit handling was not correct. - Disable bsdsocket.library if indirect UAE Boot ROM is enabled, it is not (yet?) compatible. AfAOne Post inviati: 11780 Commento 157 carlo 29 Aprile 2016    14:41:53 WinUAE 3.3.0 Beta 11 (24 Aprile 2016) WinUAE 3.3.0 Beta 11 (64Bit) (24 Aprile 2016) - Screenshot/capture without "before filtering" ticked now uses much faster GetRenderTargetData() function in D3D mode to capture the output. - Ticked 68060 unimplemented CPU emu checkbox also enabled 68030 MMU instructions. - Terminate indirect UAE Boot ROM trap threads before unmapping Amiga side memory to prevent random crashes when exiting emulator with traps active. - Debugger il mask is now accepted in two 32-bit parts, 64-bit values are not supported by debugger input. - Added gfx_black_frame_insertion_ratio config entry, sets timing between normal and black frames in adaptive sync mode. Default is 50 (50%, normal and black frames have same duration). - CD32 emulation updates, mostly previously unknown undocumented features: * - It seems unmapped addresses don't "float", all invalid reads seem to always return zeros. * - CIA chip select, address bits 12 and 13 are CIA selects. Gary: 0=none,1=A,2=B,3=A+B, Gayle: 0=none,1=A,2=B,3=none, Akiko: 0=A,1=A,2=B,3=B (Very unexpected) * - CIA address space: Gary: $A00000-$BFFFFF, Gayle: $BFDxxx and $BFExxx, Akiko: $BFE000-$BFFFFF. * - Custom register mirror at $B90000-$B9FFFF! (This is really weird..) * - Usual custom register mirror at $C00000-$CFFFFF. * - Akiko addresses are mapped from $B80000 to $B87FFF (was $B8FFFF) and has 64 byte mirroring (was no mirroring) * - Akiko ID at $B80000.l is $C0CACAFE (was only $CAFE at $B80002.w, KS checks this address for $CAFE) * - All write-only registers seem to read same data as nearby read-only register. * - Interrupt registers only have bits 24 to 31 writable, other bits always read as zeros. * - Config ($B80024) register has bits 23 to 31 writable, other bits always read as zeros. * - Subchannel arrived interrupt bit is set at boot for some unknown reason, subchannel index register ($B80018) works strangely and has unexpected value at boot ($C2). * - Match Akiko C2P behavior with real hardware when reading bytes/words or when doing multiple read passes. * - When booted with CD inserted: first packet from CD MCU is always "media inserted" packet. * - $B80028.b reads last received command packet byte. * - Writing to $B80028.b sends command bytes to CD MCU. (This is not emulated yet and no program uses it) * - Akiko internal CIAs don't have external TOD input pins. CIA-A TOD which normally counts vsyncs or power supply ticks count rate is selected with $B80020 bit 23 (0=50Hz, 1=60Hz). CIA-B (hsync) timing logic is not known yet but it is also internally generated. * - Old interrupt request set/clear hacks removed. * - All CD status return codes (including errors) include door status (open/closed) in bit 0. * - Contents of unused TOC entry bytes now contain real hardware matching values. Commento modificato il 29/04/2016 alle ore 14:42:28 AfAOne Post inviati: 11780 Commento 158 carlo 30 Aprile 2016    19:52:44 WinUAE 3.3.0 Beta 12 (30 Aprile 2016) WinUAE 3.3.0 Beta 12 (64Bit) (30 Aprile 2016) - Dummy 68030 MMU instructions were also accidentally disabled in "generic" 680x0 core. (b11) - AGA mode HAM6 colors were not 100% accurate. (Was fixed in b11) - Stop with HALT10 if compatible CPU is not ticked and exception begins with SSP pointing to non-existing address space. - Prevent programmed mode display width and height to become too small. Program doing something very stupid or crashing program can write very random values to programmable refresh rate custom registers. - Switching Advanced chipset compatible option off and then back on does not anymore reset chipset extra back to Generic in non-quickstart mode. - 1M/512k+512k Advanced chipset option was not reset when Advanced chipset was in compatibility mode. - A3000 SCSI + any WD based Z2 SCSI controller: autoconfig didn't work. Commento modificato il 30/04/2016 alle ore 19:53:13 AfAOne Post inviati: 11780 Commento 159 carlo 15 Maggio 2016    07:03:04 WinUAE 3.3.0 Beta 13 (14 Maggio 2016) WinUAE 3.3.0 Beta 13 (64Bit) (14 Maggio 2016) - HALT10 was incorrectly triggered in some configurations (b12) - Update ExecBase.MaxLocMem (and ChkSum) if more than 2M chip RAM is configured. - It was not possible to fully disable enabled expansion device without restart. Checkbox was unticked but device was not fully disabled. - Copper COPJMP blitter conflict bug emulation is again disabled (Breaks Batman Vuelve / Batman Group). There is still something unknown. I did some more tests and some blitter cycle sequences do not conflict with buggy copper cycle and correctly wait one extra cycle. - Added IVS Trumpcard Pro/GrandSlam SCSI v4.9 ROM image. Emulation not yet implemented. "Trumpcard Professional Driver 4.9 - devs/IVS_SCSIpro.driver IVSSCSI 4.9 (20 Sep 1991)"' Variable Refresh rate updates. I finally bought G-Sync monitor, Acer Predator X34. Every emulator (any emulator!) user should get G-Sync or FreeSync hardware because variable sync has all the advantages of vsync without any vsync disadvantages!) - Adaptive Sync renamed to Variable Sync. Adaptive Sync is name of DP variable refresh rate standard (which AMD's FreeSync is based on). "Official" generic name is Variable Refresh Rates but Variable Sync fits better with other VSync modes in GUI. - Variable sync + black frame insertion is now supported in windowed and full-window mode. (I couldn't get G-Sync to work in normal windowed mode but it did work in full-window) - Variable sync + black frame insertion is now supported in RTG modes. - Black frame insertion is not enabled in variable sync mode if refresh rate would become larger than selected display refresh rate (fullscreen) or desktop refresh rate (windowed/full-window). - Variable sync + black frame insertion and if doubled refresh rate is equal to selected/max hardware supported refresh rate: automatically reduce internal emulated refresh rate by 0.5Hz to guarantee glitch free display. (Workaround for monitors that have max refresh rate of 100Hz=PAL or 120Hz=NTSC) Commento modificato il 20/05/2016 alle ore 07:17:44 AfAOne Post inviati: 11780 Commento 160 carlo 20 Maggio 2016    07:07:49 WinUAE 3.3.0 Beta 14 (18 Maggio 2016) WinUAE 3.3.0 Beta 14 (64Bit) (18 Maggio 2016) - AGA subpixel scrolling: if line's parameters didn't change compared to previous field's line, line was not marked as "changed" and was not always redrawn correctly. (Roketz scoreboard corruption) - CD32: always generate subchannel interrupts and transfer subchannel frames when reading CD sectors if subchannel DMA channel is enabled. (Previously was only done when playing CD audio) Real hardware also transfer subchannel frames when CD is idle. This is not yet emulated. - Added "Paste" input event (END+INSERT default mapping), injects host clipboard text content using emulated keyboard key codes. Only available when clipboard sharing is not active and only supports ROM default US keyboard layout. For example can be used to paste strings directly to boot CLI, hardware debuggers or non-AmigaOS operating systems. - Mouse/joystick autoswitching broke some betas ago. - Pause/GUI + black frame insertion: don't show black frame. - IVS Trumpcard Pro/GrandSlam SCSI emulation implemented. - AROS ROM updated. - Few weeks ago released new MSVC optimizer enabled (May not have it enabled in final version because it is not yet fully production ready). Report if you notice any performance improvements. IVS Trumpcard Pro/GrandSlam SCSI: - Autoboot, seems to support custom filesystems. - 5380 based. - Fake DMA. Long reads, word wide writes. - "Trumpcard Professional Driver 4.9 - devs/IVS_SCSIpro.driver IVSSCSI 4.9 (20 Sep 1991)" Commento modificato il 20/05/2016 alle ore 07:17:26 Pagine: -1-2-3-4-5-6-7- [8] -9-10-11-12-13-

Utenti Online

Utenti registrati: 1206 dal 1 Gennaio 2006 di cui online: 2 registrati - ilBarbax - amiga1200 - e 38 non registrati Benvenuto all'ultimo utente registrato: zulu Buon Compleanno a kori - galvanica - Maxxx - anemal000 -