WinUAE 3.0.0 beta series (was 2.8.2/2.9.0)

[amigafreak68k]

Maybe. I'd now copied the full ENVARC folder from OS4 CD-ROM to Harddisk! Booting is now ok.

Thanks for your time!

[DarrenHD]

Originally Posted by Toni Wilen

Nothing in logs -> not my problem, I don't do OS4 or PPC debugging. Possibly OS4.0 only issue.

Toni, I got the latest beta 16 working - and with accelerator SCSI OS4.1 is _very fast_. Really amazing work! Thank you so much!

Did you ever think about emulating the Mediator or Prometheus PCI busboards? If that was present likely Radeon could work ? Or maybe not.

Darren

[FOL]

Found cause of my problem.
All none booting problems seem to relate to No buffering on host card and you have to set VSYNC to VSync 50 VS 60 for native window mode. It then seems to work every time.
Wierd as I had it working with buffering etc etc fine before.

Just need to find out why my old 3.9 isnt working now.
Might go back to an early version before PPC and see if issue goes away.

Originally Posted by DarrenHD

Toni, I got the latest beta 16 working - and with accelerator SCSI OS4.1 is _very fast_. Really amazing work! Thank you so much!

Did you ever think about emulating the Mediator or Prometheus PCI busboards? If that was present likely Radeon could work ? Or maybe not.

Darren

That would be cool, as it will allow 3D and compositing.
When was beta 16 released?

[prowler]

Originally Posted by FOL

When was beta 16 released?

http://eab.abime.net/showpost.php?p=...&postcount=638

[FOL]

Originally Posted by prowler

http://eab.abime.net/showpost.php?p=...&postcount=638

Thanks.
With beta 16, using my working beta 15 config all I get now is rainbow flashing screen.

[mritter0]

AMD FX-8350 8-core 4GHz, 16GB RAM, SSDs, Win7 x64

I am having differing results with the beta16. Here are some times with OS4.1.6 Classic:

With IDE:
Time to black screen after logo: 13 secs
Time to Workbench loaded: 4 mins 3 secs

With Accelerator board SCSI:
Time to black screen after logo: 1 min 13 secs
Time to Workbench loaded: 1 min 55 secs

I did not reformat/reinstall the HDF from IDE to SCSI, just switched the controller option.

The times to Workbench loaded are from start, not from after logo screen.

My Workbench is much more stable and compatible. Many more programs run, mainly OS3.9 programs. AmiUpdate does not abort with "End of file" errors now.

BUT, I think it is only slightly faster. I still have terrible mouse ghosting and screen refreshing. I have to move the mouse up and down the screen to get it to redraw itself.

Attached is a screen shot to show the poor refresh I am getting. It is worse at times.

Also attached are the logs for IDE and SCSI.

[Toni Wilen]

Originally Posted by FOL

Thanks.
With beta 16, using my working beta 15 config all I get now is rainbow flashing screen.

Stop posting so called "it does not work reports"! Logs and config required. Always, check first post. Only possible to reply: buy a new PC.

Originally Posted by mritter0

Also attached are the logs for IDE and SCSI.

Make sure CPU Idle is disabled in CPU page and don't use MMU emulation if config is for OS4. M68K MMU does nothing in this config. (EDIT: CPU Idle problem will be fixed in next beta, currently when m68k CPU is idle, PPC CPU can't do any IO..)

EDIT: Switch to Direct3D mode.

[FOL]

Originally Posted by Toni Wilen

Stop posting so called "it does not work reports"! Logs and config required. Always, check first post. Only possible to reply: buy a new PC.

I just quickly tried before going to bed, will attach logs later.
Not trying to be funny, but if you give a new exe and qemu and it doesnt work with a config that worked 5 minutes before. What else can I say. As I said though, had a quick go before bed.

[Toni Wilen]

Originally Posted by FOL

I just quickly tried before going to bed, will attach logs later.
Not trying to be funny, but if you give a new exe and qemu and it doesnt work with a config that worked 5 minutes before. What else can I say. As I said though, had a quick go before bed.

You say nothing until you have some information available. "Not working" or "was working" = USELESS!

[FOL]

Originally Posted by Toni Wilen

You say nothing until you have some information available. "Not working" or "was working" = USELESS!

Well, with regard to my other UAE.gfx freezing issue on other machine. If I change to UAE.gfx Z2, then it works fine, no freeze. Will sort logs for that to.

[Toni Wilen]

Just a reminder: do not use any kind of vsync with PPC emulation. It is not designed for that. Make also sure CPU Idle is disabled and fastest possible is enabled.

OS4 boot time should be about 30s if config is correct and PC is modern enough!

[FOL]

Heres my logs for UAE.gfx Z3 lockups.

[Toni Wilen]

Originally Posted by FOL

Heres my logs for UAE.gfx Z3 lockups.

Attach also config file, for some reason it was not included with debug log.

[FOL]

Originally Posted by Toni Wilen

Attach also config file, for some reason it was not included with debug log.

Went to attach config, then noticed while looking at it. I have an A1200 kickstart, not sure how that happened. As I was originally using 40.70 ROM, set kickstart to 4000T ROM and it works fine now. Sorry for not spotting this stupid mistake before.

[Toni Wilen]

Originally Posted by FOL

Went to attach config, then noticed while looking at it. I have an A1200 kickstart, not sure how that happened. As I was originally using 40.70 ROM, set kickstart to 4000T ROM and it works fine now. Sorry for not spotting this stupid mistake before.

I'd still like to see that "wrong" config because it shouldn't cause that kind of log messages. Some test may be missing.

[FOL]

Originally Posted by Toni Wilen

I'd still like to see that "wrong" config because it shouldn't cause that kind of log messages. Some test may be missing.

Here's the config.

[Toni Wilen]

Originally Posted by FOL

Here's the config.

Your custom ROM does things that normal A1200 ROM does not so it seems there is nothing to see after all

[FOL]

Originally Posted by Toni Wilen

Your custom ROM does things that normal A1200 ROM does not so it seems there is nothing to see after all

As I thought as soon as I saw the rom, how the hell the config changed though, I dont know.

Its a standard BB2 ROM, so not sure how that would cause a problem.

[FOL]

Right, Im home now and have a log for my rainbow issue.
Now heres the odd thing, it doesnt give winuae log, only winuae bootlog and config log.

The other odd thing, with full logging enabled it seems to work randomly. It rainbows for about 10 secs, then boots. If I dont do any logging, it just rainbows forever.

Manually did winuaelog, its attached but I dont think it shows anything wrong.
EDIT:- If I F12 it while its rainbowing. Then cancel, it sometimes boots. Other times it resets back to rainbow.

EDIT2:- Its definitely reproducable by F12, then cancel, then F12, then cancel until it goes to os4.1 boot logo.

EDIT3:- It seems to be if I hit F12 while FPS = 59.8 then cancel, it boots every time.

[fitzsteve]

Just to say Kudos, OS4.1 is really snappy now (around the OS) on my PC:

AMD FX4170/4.2ghz & 8gb DDR3 1800

Not run anything serious on it, played some MP3's with AmigaAmp that's all but the OS seems really stable now, no crashes like before when moving Icons.

Accelerator SCSI makes a massive difference, boots and runs really fast!

Mouse trails and screen refresh issues go away with full screen mode

Great work