FS-UAE <= 2.9.x development series

[FrodeSolheim]

@Goingdown Please try now, there's a 2.7.14dev2 version in the Fedora repo now

[Goingdown]

Originally Posted by FrodeSolheim

@Goingdown Please try now, there's a 2.7.14dev2 version in the Fedora repo now

Hi,

My version was compiled from source, how I can implement that fix on source version? Fedora 24 repo is not net available, and Fedora 23 repo does work because FS-UAE requires specific version of libGLEW. Fedora 24 has version 1.13 of that lib.

Error: nothing provides libGLEW.so.1.10()(64bit) needed by fs-uae-2.7.14dev2-1.1.x86_64

Fedora 24 is still about one month away, so this is little bit too early

[FrodeSolheim]

You can check out the GIT source repository from https://github.com/FrodeSolheim/fs-uae. The only difference is that you must run ./bootstrap (requires autoconf/automake and friends) before you can run ./configure:

git clone https://github.com/FrodeSolheim/fs-uae.git
cd fs-uae
./bootstrap
./configure

[...] etc

[Goingdown]

Thank you Frode, everything works like a charm with GIT version now

[MrGimper]

Hi all

I'm a bit confused .... somewhere between 2.7.3 dev and 2.7.14 dev, the launcher fullscreen mode of "Desktop" has changed on Mac OS X. On 2.7.3 FS-UAE launches in it's own desktop allowing access back to the default desktop, whereas 2.7.14 opens on the current desktop and hijacks it.

Sorry if I'm a little behind the times .... is this intentional?

Thanks

[S0ulA55a551n]

Originally Posted by MrGimper

Hi all

I'm a bit confused .... somewhere between 2.7.3 dev and 2.7.14 dev, the launcher fullscreen mode of "Desktop" has changed on Mac OS X. On 2.7.3 FS-UAE launches in it's own desktop allowing access back to the default desktop, whereas 2.7.14 opens on the current desktop and hijacks it.

Sorry if I'm a little behind the times .... is this intentional?

Thanks

I had noticed this too. Pretty annoying

[TEOL]

All the other Blizzards seem to run but not the Blizzard PPC in the 64-Bit one.

Although I have a file named blizzardppc.rom and it's 512k big the emulator doesn't notice this rom and flashes a messege at startup.

ONE OF THE FOLLOWING EXPANSION BOOT ROMS IS REQUIRED - BLIZZARD PPC 68060 (512K) when the one I have scanned in is the 512k one blizzardppc.rom.

I even tried changing the name to BLIZZARD PPC 68060 (512K).ROM it still deosn't work as it should and scanning even said that it scanned blizzardppc.rom in as well so the entire problem is weird.

(SHA-1: d206ada7edb18664fbead3e38dd6232297df20b1) is the CRC code for the 512K bios file I have for the Blizzard PPC board emulation and it's the only 512k one I can find on the net from the posted expansion roms zip file here on EAB so it should be loading in with no problems with the config switched to on which isn't the case.

I for one are completely baffled as all the other Blizzards for a non Power PC scan and work flawlessly for me even all the Cyberstorm's for the A4000 work flawlessly but this troublesome Blizzard PPC I have had had no chance running on FS-UAE as of yet.

This problem is on a brand new i7 Quad Core 64-Bit PC with 8GB RAM but I don't think that is relivent to this problem otherwise on Windows 10 I would have no working program if it was to do with that which isn't the case as it works and at full speed but no working Blizzard PPC config.

[jbl007]

Originally Posted by TEOL

I have scanned in is the 512k one blizzardppc.rom.

Hm, the one I have here is only 256k and it seems to work. Original name is

blizzardppc_44.71.rom

Rename to

blizzardppc_060.rom

and FS-UAE should detect it.

[TEOL]

Originally Posted by jbl007

Hm, the one I have here is only 256k and it seems to work. Original name is

blizzardppc_44.71.rom

Rename to

blizzardppc_060.rom

and FS-UAE should detect it.

That worked, great thanks. Needs to be fixed to work from the originals though as having to rename is not on.

[amigafreak68k]

Does exist plans to update the emulation core to the actual WinUAE beta?

[TEOL]

Originally Posted by amigafreak68k

Does exist plans to update the emulation core to the actual WinUAE beta?

Yes always, thats what the FS-UAE dev versions use from what I understand so if theres a new WinUAE Beta already it will be here in a couple of hours to a couple of days range almost always.

[FrodeSolheim]

Originally Posted by MrGimper

Hi all

I'm a bit confused .... somewhere between 2.7.3 dev and 2.7.14 dev, the launcher fullscreen mode of "Desktop" has changed on Mac OS X. On 2.7.3 FS-UAE launches in it's own desktop allowing access back to the default desktop, whereas 2.7.14 opens on the current desktop and hijacks it.

Sorry if I'm a little behind the times .... is this intentional?

Thanks

Yes, this is intentional. There are usability issues when FS-UAE quits and tries to return to the Launcher/Arcade when fullscreen spaces are used. But, you can enable the older behavior (FS-UAE opens in its own fullscreen space) by adding this to advanced settings in the Launcher:

SDL_VIDEO_MAC_FULLSCREEN_SPACES = 1

Originally Posted by amigafreak68k

Does exist plans to update the emulation core to the actual WinUAE beta?

Yes, when FS-UAE 2.8 is launched, soonish, I'll start merging updated WinUAE code into a new 2.9.x development series.

[amigafreak68k]

Hi Frode,

I can't get the Blizzard SCSI Kit working. The needed ROM is in Kickstart path, but FS-UAE seems to ignore it.

[MrGimper]

Originally Posted by TEOL

That worked, great thanks. Needs to be fixed to work from the originals though as having to rename is not on.

I've had the same issue for ages too, and after reading this I renamed blizzardppc_060_44.71.rom to blizzardppc_060.rom and it worked fine. The file is 524K in size. Thanks.

[ztronzo]

I have experienced a problem with latest FS-UAE development 2.7.14 and thought I should share in case someone else runs into the same problem.

So if you ever get a problem similar to this:
FS-UAE.exe runs with a black screen, you can hear the floppy loading and the music of the intro screen, but there is no display and doesnt seem to respond to whatever input keyboard/mouse or joystick buttons.. a few seconds after FS-UAE shows as "Not Responding"

Now most of us know that the Windows version of FS-UAE works better with the latest update of MicroSoft .Net FrameWorks. But some people with multiple language packs might experience problems.. Doing a windows update and choosing to update the .Net Language pack will install all languages available by the OS. as I did on a Laptop with Windows 7 32bit Ultimate which allows you to have additional language packs for the OS.. The one I tried had English, French and Greek.

To fix this I simply uninstalled the Greek language pack for .Net Framework 4.6.1
and I just kept the French Language pack, as French didnt seem to bother.

Im guessing this might be due to translation incompatibilities for the certain Greek language and maybe it wont be an issue in future dev releases.

Hope this information helps in-case people have the same issue with other languages.

[FrodeSolheim]

Originally Posted by ztronzo

Now most of us know that the Windows version of FS-UAE works better with the latest update of MicroSoft .Net FrameWorks.

I didn't know this...

Originally Posted by ztronzo

To fix this I simply uninstalled the Greek language pack for .Net Framework 4.6.1 and I just kept the French Language pack, as French didnt seem to bother.

This is very strange, as FS-UAE does not use the .NET framework, at least not directly. It's not that I don't believe you, but I do not understand why this should affect FS-UAE...

(Maybe another installed system utility which depends on .NET framework and which can interfere with FS-UAE...?)

[ztronzo]

Originally Posted by FrodeSolheim

I didn't know this...

In another case I couldnt get FS-UAE 2.6.2 Launcher to start on an old Windows XP Pro computer, including a VirtualBox Installation, but once I installed .Net Frameworks 3.5 SP1 they both worked like a charm!! So I assumed .NET FW always helps.. :-)

Originally Posted by FrodeSolheim

This is very strange, as FS-UAE does not use the .NET framework, at least not directly. It's not that I don't believe you, but I do not understand why this should affect FS-UAE...

Not sure why either. but it has to do only with the Greek language as it seems. I can test with older dev versions to track and see on which version this problem started appearing on..

Edited: Seems to be laptop specific problem... I cannot re-create it on any other system...
but has something to do with the combination of FS-UAE 2.7.14, the touchpad input drivers, .Net Framework 4.6.1, .Net Greek translation and that specific Laptop...
since I found a work-around and I did not hear anyone complaining on something similar, I am closing this issue... Thanks for your time!

[TEOL]

Any chance we can get some updates on the database for EAB File Server TOSEC and WHDLoad 2016 entries.

Some of the WHDLoad configs don't work for me anymore especially Brain The Lion because I like to replace my existing files on the slaves front with the 2016 ones by Retro Play here on EAB.

ADF TOSEC 2016 EAB

ftp://grandis.nu/Commodore_Amiga/TOSEC%20[2016-01-03]/
ftp://grandis.nu/Commodore_Amiga/TOSEC%20Updates/

WHD 2016

ftp://grandis.nu/Commodore_Amiga/Ret...DLoad_Updates/

[Romanujan]

I have a stupid question: how do I enable CD-ROM in 2.7.14? Back then it was enough to specify cdrom_image_0 = (image) and cdrom_drive_count =1. It seems something has changed...

[edit] I start suspecting something is wrong in FS-UAE - if these options are not enough to enable CD-ROM (or at least not enough to allow me to select CD-ROM image from the GUI), then why they cause the emulator to spawn uaescsi.device (otherwise absent)? All the paths are OK, as with FS-UAE-2.7.9 everything works correctly, only starting from 2.7.10 I can't use the CD-ROM.

[jbl007]

Originally Posted by Romanujan

Back then it was enough to specify cdrom_image_0 = (image) and cdrom_drive_count =1. It seems something has changed...

Looks like you have to set

cdrom_drive_0

to get it enabled. Try

cdrom_drive_0=empty

and

cdrom_image_0=yourimage

.

as with FS-UAE-2.7.9 everything works correctly, only starting from 2.7.10 I can't use the CD-ROM.

Perhaps a side effect of those changes!?