NSA - Non Solo Amiga

SOFTWARE => Emulazione & virtualizzazione => Topic aperto da: MazinKaesar - 06 Giugno 2011, 12:47:35

Titolo: WinUAE 2.3.2
Inserito da: MazinKaesar - 06 Giugno 2011, 12:47:35
E' disponibile da qualche giorno la nuova versione del famoso emulatore di Amiga per Windows.

Citazione
New features:

- AROS ROM replacement development snapshot included, replaces old
  very basic ROM replacement feature, used by default if official
  KS ROM is not found.
- New autofire option. Button released = autofire. Button pressed = normal
  non-autofire firebutton.
- Stop the CPU and wait until blitter has finished if any blitter register
  is accessed while blitter is busy and CPU mode is fastest possible.
  Better workaround than immediate blitter for programs that have blitter
  wait bugs with fast CPU.
- Serial port telnet server.

Updates:

- Disk emulation accuracy improved
  (Codertrash / Mexx, El Egg Tronic Quarts / Quadlite)
- CIA timer undocumented startup delays emulated (Risky Woods sound
  glitches)
- win32.floppy_path and win32.hardfile_path really works as expected.
- Display panel refresh rate accepts non-integer values.

Bug fixes:

- Implemented workaround that should fix Direct3D blank screen problem.
- Sample ripper crash.
- 68000 exception 3 emulation fixed again. (Broke compatibility with some
  very old copy protections, for example Soldier of Light and Zoom!)
- Reset bug that broke Arcadia mode, A1000 mode and Action Replay ROMs.
- Automatic resolution switch interlace detection was unreliable.
- CD32 early boot menu is accessible again.
- Rare crash when switching from fullscreen RTG mode to native mode.
- Borderblank chipset feature didn't work in ECS Denise mode.
- Possible input configuration corruption due to uninitialized variable.
- Color change table overflow crash that can happen when emulated
  program crashes really badly.

http://http://www.winuae.net/

Fonte: AmigaNews.it (http://http://amiga.ikirsector.it/forum/viewtopic.php?f=39&t=15609)
Titolo: Re: WinUAE 2.3.2
Inserito da: TheKaneB - 06 Giugno 2011, 12:56:57
Citazione
- AROS ROM replacement development snapshot included, replaces old
very basic ROM replacement feature, used by default if official
KS ROM is not found.

:-o muoio
Titolo: Re: WinUAE 2.3.2
Inserito da: AmigaCori - 06 Giugno 2011, 13:00:21
Citazione da: "TheKaneB"
Citazione
- AROS ROM replacement development snapshot included, replaces old
very basic ROM replacement feature, used by default if official
KS ROM is not found.

:-o muoio

Cavolo che occhio! :D non ci avevo fatto caso!, ma sarebbero le stesse ROM 68k che permettono agli AmigaClassic di "cestinare" quelle di Mamma C=?  :?:
Titolo: Re: WinUAE 2.3.2
Inserito da: TheKaneB - 06 Giugno 2011, 13:13:31
zi  :ugeek:
Titolo: Re: WinUAE 2.3.2
Inserito da: AmigaCori - 06 Giugno 2011, 13:19:03
Da provare!...il primo KickStart non C=, almeno che io sappia :P
Titolo: Re: WinUAE 2.3.2
Inserito da: TheKaneB - 06 Giugno 2011, 16:17:41
Piccolo screenshot...
[attachment=0:2lvq4v3a]AROS68k-ks.png[/attachment:2lvq4v3a]
Titolo: Re: WinUAE 2.3.2
Inserito da: TheKaneB - 06 Giugno 2011, 16:34:22
Altri due screens... KickStart AROS, immagine floppy di Workbench 3.1 Install Disk
[attachment=0:1mbmr0k8]AROS68k-Workbook02.png[/attachment:1mbmr0k8]
[attachment=1:1mbmr0k8]AROS68k-Workbook01.png[/attachment:1mbmr0k8]
 :character-beavisbutthead:
Titolo: Re: WinUAE 2.3.2
Inserito da: Alblino - 06 Giugno 2011, 17:14:08
Ma in pratica con questo Kickstart può girare Aros su 68K? Si emula un super Amiga4000
con 68060 e ci fai girare Aros 68k figata.
Natami ringrazia  :handgestures-thumbup:
Titolo: Re: WinUAE 2.3.2
Inserito da: TheKaneB - 06 Giugno 2011, 17:17:29
esattamenteeee  :text-woo:
Titolo: Re: WinUAE 2.3.2
Inserito da: AmigaCori - 06 Giugno 2011, 17:49:31
Citazione da: "TheKaneB"
esattamenteeee  :text-woo:

Hai pensato se Flashare un vero AmigaClassic per vedere come va?  :mrgreen:
Titolo: Re: WinUAE 2.3.2
Inserito da: TheKaneB - 06 Giugno 2011, 17:55:15
Si, ci pensavo, ma le EPROM puoi cancellarle al massimo una ventina di volte e quelle per Amiga (27C400) sono fuori produzione, quindi cerco di non sprecarle con versioni pre-alpha come questa :-)
Titolo: Re: WinUAE 2.3.2
Inserito da: AmigaCori - 07 Giugno 2011, 00:07:03
Capisco, quando lo farai...indubbiamente ci delizierai del resoconto.  :dance:
Titolo: Re: WinUAE 2.3.2
Inserito da: divina - 29 Agosto 2011, 20:21:38
informazioni in merito a WinUAE 2.3.3

WinUAE 2.3.3 WIP (28.08.2011)
=============================

Estimated release date: mid-September.

New features:

- New very low latency VSync mode, autodetects real refresh rate, no more 100% CPU usage, supports also windowed modes.
  (Not compatible with fastest possible CPU modes but planned in future)
- Experimental rawinput joystick/joypad support. (-rawhid command line parameter)
  Added because DirectInput is said to introduce some extra input lag.

Updates:

- Real cause for Max Transfer IDE problem found. IDE emulation detects and logs it now. (*)
- CD image audio buffer increased slightly, some systems had glitches in CD audio.
- Non-configured joystick/mouse autoswitch update: short firebutton press or move left = insert into joystick port,
  longer press or move right = insert into mouse port.
- Add Harddrive option does not require Administrator privileges anymore, most removable drives can be used without
  higher privileges, at least under Windows 7.

Bug fixes:

- IDE emulation write hang introduced in 2.3.2.
- A590/A2091 emulation crash if CPU was 68020+.
- On the fly CD switching (both images and real CDs) reliability improved.
- Direct3D blank screen problem is now 100% fixed. Really.
- win32.hardfile_path didn't work.
- On the fly resolution change didn't work correctly, resolution autoswitch improved.
- Key or joystick button mapped to mouse direction didn't work.
- Analog stick mapped to mouse had too fast and unstable speed.

*) Max Transfer problem was introduced with ATA v2 specification. ROM built-in IDE driver assume ATA v1 behavior,
some drives are compatible with ATA v1, some are not and will require Max Transfer fix. It is NOT a drive bug.
Click for details