Bridgeboard emulation (x86 CPU, for example A2286)

[AMIGASYSTEM]

Originally Posted by AnnaWu

OK, it is working now.

Before I used the hard disk image which was new created with the AT IDE Primary and then used with the XTIDE Universal BIOS HD expansion.
Now I created a new hard disk image with the XTIDE Universal BIOS HD expansion.

PS: same settings, except the new hard disk image.

Hello Anna testing you did with OS 1.3?

[Toni Wilen]

Originally Posted by AnnaWu

Before I used the hard disk image which was new created with the AT IDE Primary and then used with the XTIDE Universal BIOS HD expansion.
Now I created a new hard disk image with the XTIDE Universal BIOS HD expansion.

Probably normal. XTIDE document says not to move HD between XTIDE and "normal" BIOS HD controllers.

Originally Posted by rbm

The cga color refresh screen is very slow in the official beta 3.2b11.

I don't know if this helps with your problem but winuae.7z update now delays MDA and CGA video update interrupt until next vblank, reduces useless interrupts and should increase performance. (Real hardware may do the same)

[AnnaWu]

Originally Posted by AMIGASYSTEM

Hello Anna testing you did with OS 1.3?

Yes
Right now I only use KS/WB 1.3 for my tests.

[AnnaWu]

XTIDE Universal BIOS HD expansion (bootable floppy- /hard disk test)

A2088T > ROM Address: 0xEC000 > OK
A2286 > ROM Address: 0xDC000 > OK
A2386SX > ROM Address: 0xDC000 > OK

[AMIGASYSTEM]

Originally Posted by AnnaWu

Yes
Right now I only use KS/WB 1.3 for my tests.

You can attach your file .uae (WB 1.3) to compare my, perhaps as usual I did not understand the signs of Toni; with OS 2.x and later have no problem all OK

[AnnaWu]

Originally Posted by amigasystem

you can attach your file .uae (wb 1.3) to compare my, perhaps as usual i did not understand the signs of toni; with os 2.x and later have no problem all ok

a2386sx

[AnnaWu]

Originally Posted by Toni Wilen

I don't know if this helps with your problem but winuae.7z update now delays MDA and CGA video update interrupt until next vblank, reduces useless interrupts and should increase performance. (Real hardware may do the same)

For me it is a bit faster.

[rbm]

Originally Posted by Toni Wilen

I don't know if this helps with your problem but winuae.7z update now delays MDA and CGA video update interrupt until next vblank, reduces useless interrupts and should increase performance. (Real hardware may do the same)

A little bit faster, but still a lot slower than the previous beta dated 2015.09.02.

[Toni Wilen]

Originally Posted by rbm

A little bit faster, but still a lot slower than the previous beta dated 2015.09.02.

I still need much more information: A2386SX only? (Does A2286 have same problem?) What about older models? (and when using older models, if it happens, does it only happen in dosbox-mode?)

[AMIGASYSTEM]

Originally Posted by AnnaWu

XTIDE Universal BIOS HD expansion (bootable floppy- /hard disk test)

A2088T > ROM Address: 0xEC000 > OK
A2286 > ROM Address: 0xDC000 > OK
A2386SX > ROM Address: 0xDC000 > OK

Thanks Anna, through your config I understood where he was the enigma, basically I had configured a Os expanded 1.3 "CPU-060 JIT, 2M RAM CHIP, Z3 Fast Ram 128MB, the same config the successful use with OS2.1 and OS3.9 and everything works great and great speed. Well doing various tests I realized that not to start "xtide Universal BIOS" was the Z3 Fast RAM, I'm no expert but the Hardware System 1.3 for everything else was fine

In your configuration I noticed you the reader Floppy DF0 (Amiga side) and off, this should slow you down much of the system, trying to turn it on (you just have to check).

"About A2386SX > ROM Address: 0xDC000"

On my OS 2.1 e 3.9 (i attach screenshots) XTIDE Universal BIOS on A2386SX it works with all three ROM Address

A2386SX > ROM Address: 0xDC000 > OK
A2386SX > ROM Address: 0xCC000 > OK
A2386SX > ROM Address: 0xEC000 > OK

[rbm]

Originally Posted by Toni Wilen

I still need much more information: A2386SX only? (Does A2286 have same problem?) What about older models? (and when using older models, if it happens, does it only happen in dosbox-mode?)

Tested all posibilities and only works fast with the "fake86 / 2088T" CPU core option. All the other combinations gives the same low speed cga screen refresh.

[Toni Wilen]

Originally Posted by rbm

Tested all posibilities and only works fast with the "fake86 / 2088T" CPU core option. All the other combinations gives the same low speed cga screen refresh.

Could you attach test case? (bootable dos floppy or hdf)

Originally Posted by AMIGASYSTEM

Z3 Fast RAM

You tried to use Z3 boards with KS ROM that does not support Z3 boards. Z3 board was not initialized and because all non-autoconfig HD expansions (bridgeboard or not) are always initialized last, they were never initialized.

Bridgeboard expansions will be initialized after Z2 (before Z3) in next update.

[rbm]

Originally Posted by Toni Wilen

Could you attach test case? (bootable dos floppy or hdf)

This is a 1.44MB dos boot floppy with norton sysinfo included.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

.
Bridgeboard expansions will be initialized after Z2 (before Z3) in next update.

Strangely without the Z3 Fast RAM installing Windows 3.1 and run the game Prince Of Persia make a step forward, now instead of the black screen you can see something!

[AMIGASYSTEM]

Well Toni, with latest update "XTIDE Universal BIOS" WB1.3/060/2MB CHIP/Z3 Fast RAM 128/ It works fine, now Prince Of Persia somehow starts with this setting. I do not play anymore, but Prince of Persia is a great tool to test operation emulation

[Toni Wilen]

Originally Posted by rbm

This is a 1.44MB dos boot floppy with norton sysinfo included.

Thanks, fixed. (It waited for hblank/vblank period before updating screen and reporting was quite unreliable since last updates. It still quite hacky..)

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Strangely without the Z3 Fast RAM installing Windows 3.1 and run the game Prince Of Persia make a step forward, now instead of the black screen you can see something!

Do you have some bootable DOS disk that can be quickly used to duplicate your screen corruption? (It probably is cirrus logic emulation issue, I don't think it was designed for full VGA emulation)

[AnnaWu]

I guess the cirrus logic emulation for the VGA is very limited.
Maybe a reason why the standard VGA driver doesn't work in Window 3.x?

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Do you have some bootable DOS disk that can be quickly used to duplicate your screen corruption? (It probably is cirrus logic emulation issue, I don't think it was designed for full VGA emulation)

If I understand correctly, I have to attach my Hardfile Amiga WB1.3 and PC?

[Toni Wilen]

Originally Posted by AMIGASYSTEM

If I understand correctly, I have to attach my Hardfile Amiga WB1.3 and PC?

I only need bootable PC hardfile that includes some program that shows VGA display glitches.