WinUAE 2.0.0 beta series

[Toni Wilen]

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

- automatically enable ini-mode if registry initialization fails (this should never happen, something is wrong if HKEY_CURRENT_USER is read-only or admin-only..)
- August 2009 DX SDK (you know the drill, latest DX runtime required)
- A2065 Ethernet card emulation. winpcap required.
- mostly useless "kickstart replacement" works again. Broke long long time ago..
- hrtmon v2.32
- 68030 "MMU" "emulation" instruction decoding fixes
- 68040 MMU on the fly switching supported
- fixed 1 lores pixel background color gap in some copper effects
- renamed display card panel to expansions and moved misc expansion related options from misc panel (still work to do)
- 1.5M slow ram was 1.0M+0.5M mirrored (non-power-of-2 memory sizes are not really supposed)
- MMU: hardreset if double bus error (real CPU would freeze and wait for reset in this situation, not worth the trouble)
- IDE emulation updates, read/write multiple implementation fixed, write interrupt fixed, 128-256 sector transfers supported, status register DSC must be always set. Compatible with Linux IDE driver

[Steve]

I tried all the webpage links to see if any were broken. Picasso96 homepage is not found and Amiga in a Box page gives a forbidden access screen. Maybe these two should be removed?

[andreas]

I've contacted the AIAB author under his new e-mail address (note: don't even think of finding it on the net!) and I hope I'll get a reply. I'll keep you posted.

[Toni Wilen]

I thought 1.6.1 had exact same URLs.. (do not reply to this)

[NewDeli]

Originally Posted by Steve

I tried all the webpage links to see if any were broken.

Now, that's some hardcore testing !

Originally Posted by andreas

AIAB

I wouldn't bet on this package to resurface in Amiga land , for many reasons (including possibly legal ones, even though it didn't bear any Amiga ROM).
Deceptively simple to configure WB and utterly user-friendly bonuses made this distro a must-have.

...to the point it has an entry in the Green Alien guides
and it was an inspiration for Bloodwych's Classic WBs !

[thomas]

Bsdsocket emulation settings cannot be changed in GUI. If it is enabled in config file, it cannot be disabled and vice versa.

[Toni Wilen]

Originally Posted by Toni Wilen

- fixed 1 lores pixel background color gap in some copper effects

This breaks some demos, it seems this is yet another undocumented feature.. (graphics corruption in B2 "earth" rotozoomer and Lazy Bones anniversary intro. On the other hand black gap in Coppermaster is gone and T-racer border is correct..)

Interesting..

EDIT: yes, it is undocumented feature, changing background color when hpos equals horizontal diwstop background color change is delayed by 2 lores pixels... (Leander border, Coppermaster. T-Racer looks "wrong" on real A500 too)

[NewDeli]

Originally Posted by thomas

Bsdsocket emulation settings cannot be changed in GUI. If it is enabled in config file, it cannot be disabled and vice versa.

Same goes for uaenet.device & uaescsi.device.
WinUAE activates them, thus bypassing the GUI settings .

[Toni Wilen]

Originally Posted by Deleauvive

Same goes for uaenet.device & uaescsi.device.
WinUAE activates them, thus bypassing the GUI settings .

What? Please stop replying totally useless replies and without some extra crap.

[NewDeli]

What's wrong with my reply ?
With beta 15, I cannot tick uaescsi.device nor uaenet.device.
it always get unticked automatically, before loading the WB, or even while loaded.

I've noticed I've got those "drivers" activated (bsdsocket is loaded into memory, too) : I can surf online with Voyager, and mounted ISO images do appear on my WB.

It's not very different from what Thomas wrote, but I myself never activate bsdsocket.


Just tell me what .log files I need to attach, if you need any.
May be I should learn some German to better communicate with you .

[Toni Wilen]

Your replies are always confusing, incomplete and sometimes include too much noise. More like riddles than bug reports.. I always need to ask for more information and that is extremely annoying. (probably going to just ignore them in future)

I can't duplicate and I don't care unless someone else reports something similar. Sorry.

[NewDeli]

Well, I'll try to go into further details next time, if I can be bothered to do so.

Here is a screenshot, it shouldn't involve contextual missups I guess.

[Toni Wilen]

Originally Posted by Deleauvive

Well, I'll try to go into further details next time, if I can be bothered to do so.

Here is a screenshot, it shouldn't involve contextual missups I guess.

That explains the problem, do not use 1.6.x translations. They never work after GUI changes. (actually they shouldn't even load, hmm...)

[Toni Wilen]

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

Beta 16:

- Faster RTG moved to misc panel
- TD_REMOVE implemented in uaescsi.device (BabelCDRomFS media changes work under KS 1.3) and in uaehf.device
- bsdsocket GUI checkbox didn't work
- delay copper writes by 2 lores pixels if hpos >= 0xe0 (I am not sure 100% why but I guess extra 0.5 cycle in PAL 227.5 color clock horizontal timing causes this) Fixes Leander "border", can fix other similar border problems. Previous fix in b15 was wrong.
- disable new expansion checkboxes when emulation is running
- CE linemode blitter non-nasty broke in b14

[NewDeli]

So I was holding you back from releasing beta 16 , my apologizes.

I don't have any v1.6.1 GUI translation, it's beta 14's.
These guys from Emu-France have been translating every beta quite rapidly, that's what I was saying in my winuae.net review.

Thing is, the translation loads everytime I bootup a beta, even after reverting to English (builtin) in the misc panel. Of course, after renaming the .dll, the English GUI would start.

They are two subversions late now, but I guess they will catchup eventually !

[crusader86x]

simply delete the other .dll with the french translation

[Maren]

Pay attention to the second shot, right below Rolling Ronny's feet there's a garbage line extending horizontally through the screen. First shot shows how it's supposed to look.

I can reproduce this on demand (latest beta) but might be a little tricky nonetheless. Doesn't happen with the latest official release and according to my tests, it appears to be a glitch triggered by enabling cycle-exact.

Here's how to reproduce it:

1. Load the savestate attached below.

2. Press the jump key as soon as you see something on screen but don't release it.

3. Let him jump and don't take your eyes off the screen because it flashes very quickly. Might happen in a couple of seconds, though it generally takes at least 16.

Sorry if this has been already reported, but right now I'm a lil short of time for adequate thread research

CRC32 for the Rolling Ronny IPF image: 9EE14640

[Maren]

Damn, nothing changed. The savetsate, however, shouldn't be that important as this I can reproduce by starting the game the regular way, I just uploaded it for convenience, so people didn't have to wait for the disk to load, the game to start and then move to the top of the building.

Anyways, thanks a bunch for having bothered with my problem

[NewDeli]

Originally Posted by Deleauvive

Thing is, the translation loads everytime I bootup a beta, even after reverting to English (builtin) in the misc panel. Of course, after renaming the .dll, the English GUI would start.

Pity da fool !
It's not even a WinUAE bug. The German translation can be reverted to English with the .dll still in place.

Although it's not really my business, I am trying to understand why Tradu-France would not offer the .dll as a separate download.

They don't want the .dll to "travel" from site to site, or could be that they simply couldn't find a way to accomplish what the Germans did with their own translation.

[Toni Wilen]

Originally Posted by dlfrsilver

Ok configure the exact speed in cycle exact mode please. It's 7.19 mhz and not 7MHZ. I have the IPF too, and i don't get your bug. It runs flawlessly for me with winuae 2.0.0 b16.

Argh..

....

Read the changelogs. It is exactly correct. DO NOT CHANGE IT. (and 7.19 is wrong anyway)

NEVER EVER change anything in hardware settings if you are using quickstart, especially A500.

EDIT: all 7MHz talk posts removed. They had no sense at all.

You can argue that "7MHz" is technically wrong thing to show in GUI (but showing long 7 digit value that is different in PAL/NTSC isn't very good idea either) but to simply assume that it is wrong and you should type 7.xx in QUICKSTART mode is something I don't really understand.. (there is no real CPU clock internally, CPU clock is color clock * 2 in 68000 based Amigas or main clock / 4. Other GUI choice would have been divider/multiplier but it would not look better either..)