WinUAE 1.5.1 beta series

[Marcuz]

[edit]

Originally Posted by Toni Wilen

Can't duplicate, even with your configuration (after fixing rom path and harddrive path)

Logs needed.

same config as before, these are the log and bootlog.

i figure that my problem is at this place of the log:

10-525: PAL mode, V=50Hz H=15600Hz (227x312)
10-525: input devices unacquired
10-525: input devices acquired (all)
2008-06-29 22:33:20
20-253 [484 080x168]: SetSwitch() - Picasso96 800x600x32 (1440x900x32)

there, (i was in windowed mode) i select a pal screenmode in the prefs and the screen turned black. after switching the null filter off, the screen returned and i was able to select an RTG mode again.

Originally Posted by Toni Wilen

Aero gets disabled if program tries to read or write visible display ram directly (instead of blitting)

RTG or native or both?

i was not able to reproduce the aero thing: it happened when i switched from native (fullscreen) to RTG (windowed), i believe.

i was not also able to reproduce the black screen on native fullscreen (i.e. same case as above, with the only option in display panel for native resolution set to fullscreen)

the latter is probably the reason the aero prblem did not happen.

anyway, the important thing is that the black screen happens only with native modes set to windowed and null filter on.

[Toni Wilen]

Originally Posted by marco pedrana

there, (i was in windowed mode) i select a pal screenmode in the prefs and the screen turned black. after switching the null filter off, the screen returned and i was able to select an RTG mode again.

1: Do you get black screen if you boot without bootable harddrives and floppies? Or only if you boot to RTG WB and then switch to native mode?

2: Does it happen if you set display size to 800x600?

3: It is 100% sure it is only null filter that has black screen problem? (d3d/ogl not included)

4: Does 1/2 or 2x scaling setting also show black screen?

[Marcuz]

Originally Posted by Toni Wilen

1: Do you get black screen if you boot without bootable harddrives and floppies?

yes i do even with a bare quick configuration for A1200, with RTG ram settings off: the only relevant setting that, with filter on, switches on and off the black screen is the unusual display size: 1440*900.
800*600 works for instance

2: Does it happen if you set display size to 800x600?

no

3: It is 100% sure it is only null filter that has black screen problem? (d3d/ogl not included)

yes: null filter only

4: Does 1/2 or 2x scaling setting also show black screen?

this is strange:

actually with horizontal 1/2, and 1/2 only (vertical can be whatever ), the screen appears, but it's position is off and it stay visible only if x position is between -1 and +2 and; y position between (roughly) -700 and +700, horizontal size toward the max.

[Toni Wilen]

Originally Posted by marco pedrana

yes: null filter only

Not "PAL" filter? (It really should have exact same problem)

[Marcuz]

Originally Posted by Toni Wilen

Not "PAL" filter? (It really should have exact same problem)

yep sorry, i forgot: PAL too, but not directX, nor OGL.
the super eagle and superSai filters, if selected switch automatically back to null filter.

(the screen flashes a correct, i assume, super-whatever filter for a second, and then it returns to the null one.)

if you switch too many times between them to and from, winuae crashes. here the dump and log

[Toni Wilen]

Originally Posted by marco pedrana

if you switch too many times between them to and from, winuae crashes.

WinUAE 1.5.1 (Public Beta 1, 2008.06.28) (6.0 Service Pack 1 [2]) 64-bit 6.F0B 2.

Too old version

btw, filter problem found, it was ATI 1xxx series weirdness (I had same problem when I had same generation card temporarily few months ago, DD surfaces larger than 4096 pixels fail to blit if they are in VRAM) and workaround that was added in 1.5 betas was broken in 1.5.1b1..

[Marcuz]

Originally Posted by Toni Wilen

Too old version

but.. but... i checked the download, i thought that the version number was not updated in betas 2 and 3.

however, thanks for spotting the filter thing!

Hi, since version 1.5.0 WinUAE crashes on my Vista x64 SP1, this is the dump file, if you can look into it please...

[Toni Wilen]

Originally Posted by chris70c

Hi, since version 1.5.0 WinUAE crashes on my Vista x64 SP1, this is the dump file, if you can look into it please...

Don't see much background information but it crashes in avioutput, are you trying to record? Used codec etc please..

[Toni Wilen]

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

Beta 4:

- input panel custom events in slots 2+ were not saved if previous slot was empty
- debugger memwatch points were still broken in byte and word modes
- debugger movem was disassembled incorrectly (wrong source/dest address shown) if addressing mode was not address register relative
- raw mouse friendly names added (was easier said than done..), defaults to old-style "RAW Mouse" if name can't be found
- directdraw max surface size driver workaround fixed
- game Lancaster ce-mode blank-screen tweak

Hi Toni, yes, I'm trying to record an avi with audio only, the audio codec is PCM 44100 16bit stereo (tried the 8 bit version too), as soon as I press the "AVI output enabled" and the "OK" button WinUAE crashes; everything works fine with 1.4.x versions.

My PC config is as follow:

Intel Core Duo E6700
4GB DDR2
Asus Striker Extreme (nForce 680i chipset)
SoundMAX HD integrated audio card
Geforce 7700 gts (512mb)
Windows Vista 64bit SP1

Thnx
Chris

[Marcuz]

filters and RTG in beta 4 are ok!

[Toni Wilen]

Originally Posted by chris70c

Hi Toni, yes, I'm trying to record an avi with audio only, the audio codec is PCM 44100 16bit stereo (tried the 8 bit version too), as soon as I press the "AVI output enabled" and the "OK" button WinUAE crashes; everything works fine with 1.4.x versions.

Confirmed, only happens when recording audio only (stupid bug)

[Toni Wilen]

Originally Posted by marco pedrana

filters and RTG in beta 4 are ok!

Good

Does mouse names in ports-list look correct? (everyone, please check) No more "Raw mouse [x]", i hope

[Marcuz]

i have listed:

mouse*
windows mouse
mousehack mouse (required for tablets)
catweasel mouse [1]
catweasel mouse [2]
microsoft mobile memory mouse 8000 (intellipoint) [that's the main mouse and do not buy it, it's not worth the money]
wacom mouse

so i would say it's perfect! well... i have just two hands anyway...
out of curiosity and not beta related, sorry: there is a way to use 2 of them but the catweasel ones as second pointer in emulation, like in cooperative environment?

Originally Posted by Toni Wilen

Good

Does mouse names in ports-list look correct? (everyone, please check) No more "Raw mouse [x]", i hope

I still have Raw mouse[1] and [2] in Beta 4. In Game&IO-Ports -> Mouse/Joystick ports and in Input -> mouse.

Win XP Professional Version 2002 Service Pack 2

[Toni Wilen]

Originally Posted by selco

I still have Raw mouse[1] and [2] in Beta 4. In Game&IO-Ports -> Mouse/Joystick ports and in Input -> mouse.

Win XP Professional Version 2002 Service Pack 2

It is not USB mouse, right? (it may not be possible to get name from non-USB devices)

[Toni Wilen]

Originally Posted by marco pedrana

out of curiosity and not beta related, sorry: there is a way to use 2 of them but the catweasel ones as second pointer in emulation, like in cooperative environment?

Possible but not worth the trouble if it requires catweasel.. It may be possible with rawinput (If I understood the documentation correctly). Perhaps someday..

Originally Posted by Toni Wilen

It is not USB mouse, right? (it may not be possible to get name from non-USB devices)

Yes, you are right, I have a PS2 mouse.

Hi there (Toni),
i experienced a weird bug in WinUAE 1.5.1 beta 4.
When opening a .uae config-file and changing the following line to:

floppy_volume=25

and loading the config into WinUAE, it says in the 'sound'-tab:

floppy_volume=75

So i guess the internal 'handling' of the 'floppy_volume' variable
is inverted

I'd call it a very minor bug, but maybe Toni wanted it to be that way?
Maybe someone can clear things up?