@jahc

Actually that is the site I uploaded it to. The upload is currently in progress (actually the binary upload is finished, the source is just uploading).

@samo79

Thanks a lot.

Problem fixed. Or more workarounded. I noticed that the problem does not happen with tar, so I just tar'ed the source-code

As soon as the friend whom I sent the source+binaries for repacking to lha (which I cannot do here on the windows machine, no working Amiga right now :((( ) I will release xMame 1.06.

Thanks to all for the patience.

Note this is only xMame right now, not mess. Not sure if I will still bother with Mess in the old 1.06 version or if I will look into this for 1.23 only then. Most likely the latter.

Steffen

@afxgroup

When I try this it says "permission denied" for most files.

Steffen

Hi!

Is there a pthread implementation for AmigaOS? As I wrote at another place, I am parallel to the current work on xMame 1.06 for OS 4 I am working on a port on a new Mame implementation based on Mame 1.23 which has a complete new implementation of the OS dependent layer.

This layer uses pthread. Of course I could reimplement the code part in question using IExec functionality, but using pthread would have the advantage of making portability for future Mame Updates higher.

So my question: Is there a pthread implementation for OS 4, and if yes, could someone point me to where to get it from ? (complete with makefile+source preferred, the crosscompiler I use is quite an old one, not sure if it is still compatible with recent stuff, as you know I have been - away for quite a while from the Amiga scene).

Thanks in advance.

Steffen Haeuser

@afxgroup

The problem is not related to cygwin I think. It is that the source-files are read-protected. Compiling them works fine. Just packing them into an archive doesn't (the source-files, I *can* pack the Binaries).

Hmmm, chmod, how is the syntax to use (if I want to make the files accessible for a directory, including all subdirectories).

Steffen

@samo79

Thanks, this article looks like it describes exactly what I need. Not feeling today like more "fighting against Windows", but I will work through it the next day and try if it helps.

ZeroG: The problem is both to files and directories. What I was trying was to set the new rights to the directory containing the files (with settings that it would be applied to files contained there as well). But as I said it did not work.

Steffen

Hi!

Mame new version for OS 4 (1.06) is ready for release. There is only one stupid problem left. And I fear it is a Windows problem (Windows preventing xMame from release???) Maybe someone here knows Windows well enough to help me fix the problem?

The problem:

Originally I copied the Mame source as downloaded from a Linux system and written there to a CD to my Windows system. Then I compiled+ported it using cygwin OS 4 crosscompiler.

Now the problem was: A lot of files where stated as "you have no permission to read this file". The compiler still could read them, I just could not copy or edit or archive them. I tried to use Windows Explorer to change the permissions. Most of the times after I pressed ok they were still at "write protected" (and obviously read protected, what is entirely stupid). Sometimes if I did this attribute change several times in a row after 4-5x it finally was readable. There was no logic in how often I needed to try until it worked. Fortunately for porting I did not need to edit ALL files. And after a lot of trying I could edit the files I needed to edit. And weirdly the compiler could still compile the read-protected files, only copying+archiving+editing was not possible.

Now the Mame licence requires me to release the source-code when I release the new version. Which means I need to "fix" all thousands of Mame files from the stupid read-protection-bug.

Does anybody have an idea how I can fix this, either with Cygwin or windows? My guess is that when I wrote the source to cd on the linux system the file permissions from the Linux system were still "active" and windows is confused by it.

Windows is soooo stupid !!!! This is a single user machine, file permissions MAKE NO SENSE HERE !!! I am the only one using this computer !!!

Any help appreciated.

Best would be some sort of "this is my computer, I can access all files on it any ways I want" tool for Windows, does something like this exist? (I fear not...).

As soon as I can fix this STUPID problem I can release the new xMame for OS 4.

Steffen Haeuser

I have no idea what the Sam does there... maybe some Driver issue or something like that? Nothing I can change from my side I fear...

The problem with N64 Emulators is that most are either Binary only or the Source of the Video-Plugin (and without it is useless for commercial games) is not available. I think Amidog had the source code of one version of a video-plugin for one Emulator. Not 100% sure, but I think it was Nemu64.

The only Emulator with public source-code release for the Video Module I know of is Mupen64 (no idea how good it is).

Also most N64 Emulators use tons of Windows code (Well, mupen instead uses tons of GTK code... is there any GTK port available for OS 4, does anyone know?)

Sure, it is doable. But it is MUCH MUCH harder to port than any other emulator. Added to this, sometimes a N64 Emulator stops development, while most other Emulation projects "hold much longer".

Steffen

I am sort of "ok" again, at least sort of.

News:

- Sent a new Mame version to my betatester. Hope to release the new version to the public next week
- This xmame OS4 version will be the LAST version.

But before you are shocked: I will work after this on a totally new Mame port for OS 4 not based on the current source.

Reasons for this step: Up to now xmame for os4 was always very close in source-code to the xmame Mame port for Linux. Sadly xmame has been discontinued. I now started on a new Mame port which is based on the recent Mame source from scratch and which probably will be much better. Especially it will be easier to update so that updates do not take years like currently

It of course will still take some time till the new port will arrive. But before this at least I will release this last xmame for OS 4 version. I started on the new Mame for OS 4 today.

I also took up contact with a guy who offered to help me with the MUI part of WarpSNES, so maybe there will be a new WarpSNES in some time as well.

Steffen

Sorry for the delay in the Mame release, it was something having nothing to do with the software, but actually a health issue. Just came back from hospital a few days ago (do not worry, nothing serious, an inflammation of the appendix - everything went well, and I think in 1-2 weeks I should be back to normal again... till then I won't do any computer stuff though).

Steffen

@kas1e

It does, if you have the ROMs for them.

And I expect to release a version in a timeframe of let's say next 2 weeks.

Steffen

Some good news: I had the first successful test of a game on the new Mame OS 4 version from a tester reported. Before I release some other stuff needs to be checked, though, so I do not release a buggy version. But you can assume release will now come soon.

Steffen

Since a while I do not get a reply from my tester anymore. So I need a new tester.

Anyone interested email to tirionareonwe@gmail.com

People who have the "strip" command for OS 4 installed (part of the OS 4 gcc) preferred, as the test exe needs to get stripped.

MagicSN

@jahc

If someone provides me with a cygwin Crosscompiler for this...

More testers: Well, until a game is up and running on the emulator not much point. Output "could not initialize video" is enough from one person already

Steffen

Just to let you know: test of xMame for OS 4 has started. No, the exe does not work yet (it outputs some errors right now, might be a config file issue or such, though), so no new testers needed right now. But hopefully it soon will.

Steffen

@MamePPCA1

It crashes when you click on what icon? I am not aware of any tricks. I am aware though of some joysticks causing "trouble". But first I would need to know:

- which icon you clicked (try running from a shell, maybe! Some error messages might not appear if you start by mouse)
- Snoopdos log?
- In which way did the crash manifest?

News on xMame:

- It linked finally!!! So I now need testers.

There is now one thing, though. I remember that linking xMame "correctly" for OS 4 was always a bit a "problem". I think to remember I had to strip the exe, but I do not know anymore (someitmes past ) how I did this, so I would need to try out (and I currently have no working Amiga, so I would need a tester for this).

Principially it will work with one of the options:

- Run it unstripped
- Run strip on the Windows crosscompiler
- Run strip on a crosscompiler running on LinuxPPC
- run Strip on a crosscompiler running on Linux-x86
- Run Strip on AmigaOS4

I know for sure one of these 5 methods worked, but I cannot remember which of the 5 it was So I will just have to try out.

The catch: Every testexe is a 60 MB Executable So it would be best if I had a tester who can provide me with a ftp server, where I can upload the test exe (I do not want to use a public upload yet, as it is a BETA VERSION).

So if you can offer me a ftp site for this purpose and are willing to test, send me an email to tirionareonwe@gmail.com.

Thanks in advance!

Steffen

@nubechecorre

I hope to find some time this week to continue to work on xMame OS 4. Maybe even to get it to the point were it fully links and a first testable version is ready.

As to Joystick Support... I did play Mame with AmigaInput on my A1, just not sure if I released the A1 version ever outside AmigaOS betatesters. But might be it is only an issue in the config file of mame. The new version is definitely compiled with AmigaInput support enabled.

MagicSN
ware.lha[/quote]

Update:

In the past weeks I could reduce the amount of linker problems from several hundreds to *8*. So we are getting closer to a first testable executable, sorry for the time it took, I have some important non-computer-issues to handle lately.

Will work some more today on it.

A question to CountRaven: On the Peg2 this is also my port of Mame which is running? so same Mame-exe on both tests?

@jahc: thanks for the comparision numbers A1 vs. Sam. This sort of confirmed what I feared, that it is a special issue with the Sam. And yes, if Sam has like you say no L2 Cache then I agree with you that this is most likely the problem.

From the early days of WarpUP and OS 4 Porting I still know how much memory speed is an issue with Emulators. I had been working on a CyberstormPPC back then, and sometimes something which ran like a dream on my machine was awfully slow on BlizzardPPC (which had a slower memory interface).

I will ask around a bit if I can get more info concerning Sam and memory speed.

SteffenQuote: