FS-UAE 1.3 Development Series

[grimi]

Hi frode,
I have some bug reports:
fs-uae: still exists crashing problem with 64bit exe/RTG A4000/040 conf (fs-uae: xcb_io.c:178: dequeue_pending_request)
fs-uae: in libfsemu/src/ml/linux.c change 'fs_get_program_data_file' to 'fs_get_data_file', fixes lack of appicon in window title/taskbar (linux openbox/pekwm)
fs-uae-launcher: same as above problem (lack appicon), adding in FSUAELauncher.py, after 'if fs.windows:' part, this fixes problem:

elif fs.linux:
   if os.path.exists("/usr/share/fs-uae-launcher/fs-uae-launcher.ico"):
      icon = "/usr/share/fs-uae-launcher/fs-uae-launcher.ico"

fs-uae-lancher: in fs_uae_launcher/DeviceManager.py this:

 name.replace("  "," ")

causes, that fs-uae can't find/setup selected joypad.

Best regards

[FrodeSolheim]

Originally Posted by grimi

Hi frode,
I have some bug reports:
fs-uae: still exists crashing problem with 64bit exe/RTG A4000/040 conf (fs-uae: xcb_io.c:178: dequeue_pending_request)
fs-uae: in libfsemu/src/ml/linux.c change 'fs_get_program_data_file' to 'fs_get_data_file', fixes lack of appicon in window title/taskbar (linux openbox/pekwm)
fs-uae-launcher: same as above problem (lack appicon), adding in FSUAELauncher.py, after 'if fs.windows:' part, this fixes problem:

elif fs.linux:
   if os.path.exists("/usr/share/fs-uae-launcher/fs-uae-launcher.ico"):
      icon = "/usr/share/fs-uae-launcher/fs-uae-launcher.ico"

fs-uae-lancher: in fs_uae_launcher/DeviceManager.py this:

 name.replace("  "," ")

causes, that fs-uae can't find/setup selected joypad.

Best regards

Thanks for the bug reports, 'fs_get_program_data_file' should definitely be 'fs_get_data_file'. I'll also review your other suggested fixes

Regarding the crash, I have never been able to reproduce this. Does this happen all the time for you, or just sporadic? Do you have to do something to trigger it?

It is possible the crash it is dependent on system libraries. I am right in assuming that the crash happens on Arch Linux? If so:
* Are you able to easily test on another distro for reference
* Have you got any special setup, or do I just have to perform a default installation of Arch Linux if I want to try to reproduce the problem?

[grimi]

Originally Posted by FrodeSolheim

Regarding the crash, I have never been able to reproduce this. Does this happen all the time for you, or just sporadic? Do you have to do something to trigger it?

It is possible the crash it is dependent on system libraries. I am right in assuming that the crash happens on Arch Linux? If so:
* Are you able to easily test on another distro for reference
* Have you got any special setup, or do I just have to perform a default installation of Arch Linux if I want to try to reproduce the problem?

Crash appears very often 6-7 times for 10 starts, sometimes with comment 'segmentations fault', some times with xcb error, and only if uae_gfxcard_size is used in config.
Arch Linux distro, nothing fancy, default installation (all libraries are from default repos).
Ok, I'll check other distro...

FrodeSolheim, i was looking into getting FS-UAE onto other platforms, mainly OpenGL ES ones. However there is of course the issue with OpenGL being baked-into the FS-UAE. What would it take to extract/interface the current GL implementation into FS-UAE submodule so FS-UAE can run on different GL systems and different GL versions?

[FrodeSolheim]

Originally Posted by gregd72002

FrodeSolheim, i was looking into getting FS-UAE onto other platforms, mainly OpenGL ES ones. However there is of course the issue with OpenGL being baked-into the FS-UAE. What would it take to extract/interface the current GL implementation into FS-UAE submodule so FS-UAE can run on different GL systems and different GL versions?

Hi. OpenGL is already decoupled from FS-UAE. All video (and audio and input) code is put in libfsemu, which fs-uae depends on (and which is included in the fs-uae source code). This was done both to avoid too much platform-dependent code in UAE/FS-UAE, and to make libfsemu re-usable for other projects. While I have made some effort in properly splitting the project into sensible parts, it is not *perfectly* abstracted, and getting things done have surely triumphed code elegance in some places.

It shouldn't be difficult at all (depending on skill of course) to support OpenGL ES. The basic rendering itself is just a textured quad. So you would probably define USE_GLES or something, and sprinkle the code with #ifdef USE_GLES where necessary. OpenGL / OpenGL ES is similar enough that I don't think it would be necessary/useful to add more abstractions.

Among other things, you would need to use vertex arrays insead of glVertex*, and if targetting OpenGL ES 2, also set up shader programs. Additionally, if the platform does not support SDL you will have some more work to do, and perhaps you need to use EGL to setup OpenGL ES..

I have noticed the following project, but I haven't looked at the source: https://github.com/lunixbochs/fs-uae-gles

[FrodeSolheim]

I am now planning a new stable release, since there is so much good stuff in 1.3.x which is not available in 1.2.x – especially the launcher, since this is very useful for casual setup and especially for beginners. The reason I'm thinking of bumping the version number to 2.0 instead of 1.4 is because I feel the inclusion of the launcher represents a great leap in functionality (for those interested).

I’m quite happy with the state of FS-UAE itself, but I think the launcher needs some more work and polish before it should be heavily promoted to newcomers to FS-UAE.

I have assembled a list of stuff I think should be done before 2.0 can be released. I would very much like feedback if you know of something else which should be fixed or implemented first. But please remember that you shouldn’t just suggest all favorite wish-list items (Remember that development will continue on the 2.1.x branch). Instead, try to think if there is some important function missing which could put off new users when they try out FS-UAE 2.0 for the first time (esp. with the Launcher since I assume I will direct new users towards it).

The following is already implemented (for version 1.3.26):

• Fix window manager icon lookup on Linux [grimi].
• (Launcher) Expand ~/ and $HOME/ in paths from config files.
• (Launcher) Fixed joystick name matching when joystick contains multiple adjacent spaces.
• (Launcher) Set window icon for Linux also, in cause the desktop environment does not pick up the .desktop file icon.

FS-UAE

• New official option to enable RTG video card (“uaegfx_card”)
• (Perhaps) new official option to enable JIT where available (“jit_compiler”)

FS-UAE Launcher

• Automatically scan/check kickstarts on startup (no “Scan” needed).
• Automatically scan/check .fs-uae configurations. (from Documents/FS-UAE/Configurations) on startup.
• Saving configurations.
• When saving configuration, save with portable paths (if possible) if the Launcher is run in portable mode.
• Support specifying the number of floppy drives.
• Floppy drive volume setting.
• Floppy drive speed override.
• Automatically add images in drives to swap list (if not already present).
• GUI for Memory options.
• GUI to enable RTG graphics, bsdsocket.library (and perhaps JIT).
• GUI for video sync mode and method settings.
• Replace configuration list view with a new custom list view (the current one has buggy rendering on some platforms).
• Temporarily remove (unused) favorite button.
• Temporarily remove (unused) verified button.
• Remove net play tab, but perhaps include checkbox in settings to enable (“Enable experimental support for net play”) -since the net play GUI is not 100% newbie friendly yet.
• Support selecting “Preferred” or “Primary” / “Secondary” joysticks in joystick port selectors, especially useful when saving configuration so the joystick device name is not hardcoded into the config file.
• Implement support for upgrading the scan database (when the schema is updated) instead of creating a new empty database.
• New icon for the launcher to make it visually distinct from FS-UAE.
• (Perhaps) FS-UAE Launcher can download and use updated AROS roms on demand.

Deferred to 2.1.x or later:

• Merge updated WinUAE code.
• Enable CD-ROM eject function.
• (Launcher) Improved game database support.
• ... and other new features.

Documentation

I would also like to improve the documentation, especially with some tutorials to help newcomers use and discover features of FS-UAE (and Amiga emulation in general). Of course the getting started-guide must be updated with a launcher guide, and other documentation must be reviewed to make sure the information is correct for 2.0.

New Topics:

• Virtual Hard Drives – explaining how mounted folders work, with some details concerning the implementation.
• Networking Support
• Enabling RTG Graphics (Picasso96) – How to enable it, link to tutorial for installing drives, and explain a bit how to configure it for best performance.
• Adding covers and screenshots to the Launcher.

Suggested Tutorials:

• Installing Amiga Forever Files (ROMs and the AF HD setup).
• Installing Workbench 3.11 (on a Virtual HD).
• Installing the Picasso96 Driver.
• Installing ClassicWB / AmigaSYS / AmiKit in FS-UAE.
• Installing the 1080X Ambermoon Bezel Theme.
• Using Shaders for Special Effects.
• Using WHDLoad Games with a High-end Amiga Setup.
• Creating a Portable Cross-platform FS-UAE Installation (put FS-UAE, Launcher, Games / Amiga HDs on a portable device and run stuff from there)
• Creating Self-contained App Bundles for OS X.

Please let me me know if I have missed something important! But please don't quote this entire long post when replying, just include the relevant bit (or don't quote at all)

[grimi]

I just have to say, WOW.

[nexusle]

Wow!!

Frode, have you an "Donation" option on your homepage? I think, it's time to honor your great work!

[bcripon]

I just downloaded 1.3.26 and tried to run the launcher on OS X 10.8.1.

When I looked at the console, I saw this message:
9/8/12 9:32:08.155 AM com.apple.launchd.peruser.502[156]: ([0x0-0x40040].org.pythonmac.unspecified.FS-UAELauncher[978]) Exited with code: 255

When I downgraded back to 1.3.25, everything was fine again. I am assuming it is a simple problem that can be fixed easily.

I also agree with nexusle. FS-UAE has eliminated the need for me to try to run Amiga Forever through VMWare on my Mac (not a satisfying option) or via Wine (better, but still a pain). I would be more than happy to donate to your project.

I do not really have any suggestions for your list. I am glad to see that improved game database support is on the horizon. However, right now, FA-UAE really does everything I am looking for in an Amiga emulator. I am always ready to be surprised though.

Update: The 1.3.26u1 version fixed the crash. Thanks for the quick response.


Bob

[AmigaOnline]

@Frode: Nice work

Btw, the directory listing seems to be disabled again for http://fengestad.no/fs-uae/files/

[lallafa]

Hi Frode,

attached you'll find a patch that's updating FS-UAE's serial emulation to the one WinUAE currently uses.

WinUAE's new implementation moves the serial host commands into the file parser.cpp and thus I moved/added the POSIX serial emulation there. The patch is tested on Mac OS X and I assume Linux should work out of the box. The Windows part is currently missing in this patch (no win here) but I think if you use WinUAE's parser.cpp in this case then everything should work on windows, too.

The patch also adds a new FS_UAE config option "serial_name" to set the host device for serial emulation. (I use the great socat tool here to create a pty thats connected to the stdout in a shell and redirect FS-UAEs serial port to the pty. With this tool you can also redirect the port to a TCP/IP socket and lots of other sinks. So in POSIX you won't actually need the "enet_serial" stuff implemented for Windows...)

It would be great if you would consider this patch for inclusion in one of the next releases of FS-UAE...

[Foul]

The only "important" thing missing for me, is the wheelmouse support... All the rest is near perfection...

Awesome Work Frode

[FrodeSolheim]

Originally Posted by grimi

I just have to say, WOW.

Thanks Regarding the your crash on Arch Linux, I haven't been able to test this yet. I'll install Arch Linux when I get time and try to reproduce the problem.

Originally Posted by nexusle

Wow!!

Frode, have you an "Donation" option on your homepage? I think, it's time to honor your great work!

No, I hadn't, but since I have been asked this question before, I decided to put up a donation page (http://fengestad.no/fs-uae/donate) But as I write on the page, I won't accept donations for expected future features (or any kind of paid development), so it must rather be donations in appreciation of what's already there!

Originally Posted by bcripon

I just downloaded 1.3.26 and tried to run the launcher on OS X 10.8.1. [...] When I downgraded back to 1.3.25, everything was fine again. I am assuming it is a simple problem that can be fixed easily.

I made a mistake which did not show up when running before publication. 1.3.26u1 (http://fengestad.no/fs-uae/download-beta) should work again.

Originally Posted by bcripon

I also agree with nexusle. FS-UAE has eliminated the need for me to try to run Amiga Forever through VMWare on my Mac (not a satisfying option) or via Wine (better, but still a pain). I would be more than happy to donate to your project.

As above, only if you feel like it (http://fengestad.no/fs-uae/download-beta). It will certainly make me smile, but it won't directly affect the development as time is the limiting factor, not money

Originally Posted by AmigaOnline

@Frode: Nice work Btw, the directory listing seems to be disabled again for http://fengestad.no/fs-uae/files/

I disabled it to avoid search engines indexing stuff there, as it polluted search results somewhat. But I have fixed that via robots.txt instead now => directory listing is enabled again.

Originally Posted by lallafa

Hi Frode,

attached you'll find a patch that's updating FS-UAE's serial emulation to the one WinUAE currently uses.

WinUAE's new implementation moves the serial host commands into the file parser.cpp and thus I moved/added the POSIX serial emulation there. The patch is tested on Mac OS X and I assume Linux should work out of the box. The Windows part is currently missing in this patch (no win here) but I think if you use WinUAE's parser.cpp in this case then everything should work on windows, too.

The patch also adds a new FS_UAE config option "serial_name" to set the host device for serial emulation. (I use the great socat tool here to create a pty thats connected to the stdout in a shell and redirect FS-UAEs serial port to the pty. With this tool you can also redirect the port to a TCP/IP socket and lots of other sinks. So in POSIX you won't actually need the "enet_serial" stuff implemented for Windows...)

It would be great if you would consider this patch for inclusion in one of the next releases of FS-UAE...

Hi, sounds great, thanks for the patch I haven't had time to look at it in detail yet though. The current serial code is just barely good enough to get AROS booting (and printing debug output to the console), so as long as it's better than what I already have, I'll be happy to include it. But of course, at a minimum, FS-UAE must still compile and work on Windows as before, so I will probably have to rework it a bit first.

Would you contribute some examples on how to use this, for example with socat? I can include this in the documentation.

Originally Posted by Foul

The only "important" thing missing for me, is the wheelmouse support... All the rest is near perfection... Awesome Work Frode

You're now effectively forcing me to delay wheel mouse support to 2.1.x, to keep some interest in further development ;-)

(This was a new personal record in number of replies in one post, I think )

[bcripon]

Frode,

Would it be possible to add the ability to double-click on the game in the launcher to start it instead of having to click the Start button? Admittedly, it is a very small detail but I find myself double-clicking on the game and momentarily wondering why it has not started yet.

I also keep hoping for floppy drive light support in the Ambermoon theme. However, since you already have support in FS-UAE for the light, I am sure I just have to wait until the theme is updated to turn on the floppy drive lights.

Even though I owned an Amiga for a short time (I was mainly an ST owner back in the day), FS-UAE has allowed me to replay those games that I loved when I owned an Amiga all those years ago.


Bob

[lallafa]

I udpated the serial code mainly because the old code does not support irq based receiption of serial data and typical serial handlers do this (e.g. aux: handler). So output works with the old driver already but input only for code that uses polling.

Would you contribute some examples on how to use this, for example with socat?

Sure. Here we go:

Using serial to create a host based CLI shell

• In a terminal on my host machine I start socat
  

  socat pty,raw,echo=0,link=/Users/chris/vser -,raw,echo=0

  This creates a new pty that is linked to the name /Users/chris/vser and connect it to stdout (-) (i.e. the terminal). Both sides are raw, i.e. no translations and echo is disabled
• In FS-UAE's config I added a line to open this new pty
  

  serial_name = /Users/chris/vser

• Now I start FS-UAE (In the log you can see that serial emulation opens /Users/chris/vser and got a valid file descriptor for it)
• In your amiga start a new shell using the AUX: handler for in/output
  

  newshell aux:

• In your host terminal you should see the CLI prompt and you can start using this host-based Amiga shell

You can modify the socat call to connect the pty to a TCP/IP socket:

socat socat pty,raw,echo=0,link=/Users/chris/vser  tcp-listen:6502

Now you can e.g. telnet to port 6502 and reach the emulated serial link:

telnet localhost 6502

Another example is to used stdin/stdout of a process for the link endpoint:

socat socat pty,raw,echo=0,link=/Users/chris/vser   exec:/my/fancy/tool

More examples of socat can found in its manpage, but I think these examples already give you an idea whats possible with this tool...

[FrodeSolheim]

Originally Posted by bcripon

Frode,

Would it be possible to add the ability to double-click on the game in the launcher to start it instead of having to click the Start button? Admittedly, it is a very small detail but I find myself double-clicking on the game and momentarily wondering why it has not started yet.

I also keep hoping for floppy drive light support in the Ambermoon theme. However, since you already have support in FS-UAE for the light, I am sure I just have to wait until the theme is updated to turn on the floppy drive lights.

Even though I owned an Amiga for a short time (I was mainly an ST owner back in the day), FS-UAE has allowed me to replay those games that I loved when I owned an Amiga all those years ago.

Bob

I agree that double-clicking a configuration should load and run it, and this is quickly implemented. Expect it in the next release. Also, your monetary contribution came through (which, as promised, made me smile )

I have not heard from Ambermoon. He might have forgotten, or not had time yet. I can send him a friendly reminder. In the meantime, you can make a personal modification to the theme yourself. Example overlay images are attached (must be placed in the theme folder), and in theme.conf, you can add something like:

# position of DF0 drive activity LED
theme_custom_0_x = 1605
theme_custom_0_y = 931

# position of DF1 drive activity LED
theme_custom_1_x = 1613
theme_custom_1_y = 1038

(But please don't distribute the modified theme, as this goes against Ambermoons wishes and the license for the image).

Originally Posted by lallafa

I udpated the serial code mainly because the old code does not support irq based receiption of serial data and typical serial handlers do this (e.g. aux: handler). So output works with the old driver already but input only for code that uses polling.

Thanks for the examples! They will come in handy when I test the merged code (and will also be great in new documentation).

[bcripon]

Originally Posted by FrodeSolheim

I agree that double-clicking a configuration should load and run it, and this is quickly implemented. Expect it in the next release. Also, your monetary contribution came through (which, as promised, made me smile )

I am glad to hear that it made you smile. Per your request, my contribution is for what you have already accomplished (which is quite a lot).

Originally Posted by FrodeSolheim

(But please don't distribute the modified theme, as this goes against Ambermoons wishes and the license for the image).

I completely understand. I have no interest in distributing the modified theme.


Bob

[ransom1122]

Absolutely Perfect

[FrodeSolheim]

Originally Posted by lallafa

Hi Frode, attached you'll find a patch that's updating FS-UAE's serial emulation to the one WinUAE currently uses.

Hi, I have now merged the patch and the merged code is available here: http://code.google.com/p/fs-uae/source.

Your patch is mostly intact, the differences are:
* added a couple of #ifdefs to make it compile on Windows.
* made SERDATR return 0x2000 if no device is opened to allow AROS to boot as before without needing to actually use the serial port feature (output is logged to log file as before).
* changed name of option to serial_port.
* moved the updated serial.cpp code to od-fs/serial_host.cpp to mirror the code layout of WinUAE and make a cleaner diff to WinUAE. src/serial.cpp is not used any more (ang neither by WinUAE it seems).

I tested with socat on Linux, and it worked well here as well But please test the merged code and check that I haven't introduced any new problems!

[lallafa]

Hi Frode,

I tested the new code base on OS X and everything seems to work fine
Thanks for integration!