Does WinUAE 2.5.1 Work?

[Sim085]

Hello, I have WinUAE 1.6.1 installed on my PC. This works like a charm. I installed WinUAE 2.5.1 ... this does not work. Workbench does not even boot when loading from a CF card and when I load from a Workbench installed on my PC I get very bad graphics (strange arrows!!).

I was wondering is this just me or others have had this problem as well?

[Toni Wilen]

Yes. No. But I guess you wanted some more help too?

(btw, "does not work" = 100% useless information, helps no one)

The bigger the version difference, the bigger the chance that more complex configurations will be incompatible.

Attach your config file, screen shot, 2.5.1 and 1.6.0 winuaebootlog.txt and winuaelog.txt.

[Sim085]

Hi, I am happy with my 1.6.1 setup but I would really like to know why the latest version of WinUAE is not working!

Attached are the winuaebootlog files when I run the with both versions of WinUAE. I am not attaching screenshots because with 2.5.1 I get a black screen while with 1.6.1 everything works fine.

[Toni Wilen]

You need to tick logging checkbox in misc panel to enable winuaelog.txt. (It is more important than winuaebootlogt.xt): load your normal config, tick logging checkbox, start emulation, wait 10 seconds (if it shows only black screen), exit winuae.

Config file is also missing.

You said you get "strange arrows". Thats why I asked for screenshot. Try also windowed mode first if using fullscreen.

[Sim085]

Originally Posted by Toni Wilen

You need to tick logging checkbox

I changed this from "Paths". In Misc panel I only found "Log Illegal Memory Access" and I checked this as well.

I attached the file. Is this the correct file?

[Toni Wilen]

It is correct and it shows that for some reason KS ROM is not loaded and it defaults to built-in development aros m68k replacement ROM (which isn't compatible with most system patches and more)

Attach your config file and winuaelog.txt from 1.6.0, please. There has to be some bug somewhere..

[Sim085]

Originally Posted by Toni Wilen

Attach your config file and winuaelog.txt from 1.6.0, please. There has to be some bug somewhere..

In 1.6.1 I do not know how to turn winuaelog.txt on! I attached my config file.

[Toni Wilen]

Miscellaneous -> Create log file.

But it is not needed anymore. Your config has no ROM image set. I guess old WinUAE versions selected "kick.rom". Now it defaults to AROS ROM replacement.

Open WinUAE GUI ROM panel and select correct ROM image and save the config.

EDIT: I think this is technically a bug in newer versions but I'll think about it after 2.6.0 is out.

[majsta]

I didn't have any single problem until I decided to install new version 2.5.1. i have spend last 3 days to understand what is wrong with this version. Problems with CF cards and many other problems. So today I installed my old 2.1 version and works like a charm. I prepared 3 CF cards without any problems. Only now i don't have integrated virtual drive support. Still I m wondering what went wrong with 2.5.1 version.

[Toni Wilen]

ADDED: This is my standard answer if so called "bug report" only says "it does not work". Nothing more.

"many problems" = 1000% useless information. It can't be that difficult to actually explain the problem! (and include logs!)

The only possible answer without real information: there is no problems and CF installations still work just fine. (I have done it)

One major difference: newer versions refuse to write anything to hard drives unless they are completely blank. (but they do report it)

[Retroplay]

I prepared a 32GB SDHC card as a HDD using WinUAE 2.5.1 no problems.
Just remember to completely wipe the CF or SD card first using Diskpart or similar tool and you shouldn't have any problems.

[Sim085]

Originally Posted by Toni Wilen

But it is not needed anymore. Your config has no ROM image set. I guess old WinUAE versions selected "kick.rom". Now it defaults to AROS ROM replacement.

Thank you very much. That solved the problem. Sorry, could not figure that out on my own.

[majsta]

@Toni Wilen I don't have time to explain what was wrong because for that I would need again to install new version and spend 3 days discovering problems I had last few days. Maybe it just me but I m happy with old version and few minutes ago I prepared another card. With new version I need to use some additional software like Diskpart or something. I remember someone said that is not safe to prepare CF card who are already mounted under windows but for last 3 years I didn't have any single problem with that using every CF I could find. So maybe this new version is technical improvement but for me is just one more complication. Please don't get me wrong I thank God every day for WinUAE. I use it more than 5 hours per day, all the time. Without WinUEA nothing will be possible regarding my Amiga work.

[Toni Wilen]

Originally Posted by majsta

@Toni Wilen I don't have time to explain what was wrong because for that I remember someone said that is not safe to prepare CF card who are already mounted under windows but for last 3 years I didn't have any single problem with that using every CF I could find.

Yes, it did work on some PCs but not all. (Depends on Windows version, driver, security software and so on..). It caused big trouble when it didn't work, for example write appeared to succeed but nothing was actually written.

Now it refuses to mount the drive in read/write mode unless it is not mounted in Windows and does not have any PC partitions. This guarantees there won't be any side-effects.

[Toni Wilen]

Originally Posted by Sim085

Thank you very much. That solved the problem. Sorry, could not figure that out on my own.

I checked default rom image code and it is nearly identical between 1.6 and 2.5.1. What was full path to rom image that 1.6 used?

[Sim085]

Originally Posted by Toni Wilen

I checked default rom image code and it is nearly identical between 1.6 and 2.5.1. What was full path to rom image that 1.6 used?

When I click the "Reset to defaults" button ...

In 1.6.1 the Systems ROMs value is "./"
In 2.5.1 the Systems ROMs value us "E:\Program Files\WinUAE_251\"

Both seem to point to their respective WinUAE installation folder

What I did notice is that in the 1.6.1 installation folder I have kick.rom while in the 2.5.1 installation (installed using installer) I do not have kick.rom!
(in fact I moved the kick.rom file from the 1.6.1 installation folder to the 2.5.1 installation folder and now works fine)

[fishyfish]

2.5.1 works fine for me. I prepared my 32gig CF card on it, which works nicely.