Not sure about m4, but I probably have perl since the script starts and looks for its companion autom4te.

Haven't installed new gcc or binutils.

I tried to ask but their comment section is broken and I got no answer on an e-mail I sent somewhere.

I'm not paying for anything without knowing it works, when it doesn't say explicitly that it works with Win8 nor 10.

Hi!

Any chance there is a working RDesktop client for OS4 that can connect to a Win10 machine?

Thanks all!

@Hans

That's quite some description, just to install a compiler!

I guess I'll install all this and then snapshot the directory as a backup...

Hi!

I want to build something but autoconf doesn't work.

I downloaded new autoconf from OS4depot and set the S-flag on them, but they won't execute:

> sh
abc:/Project> autoconf
/SDK/Local/C/autoconf[510]: /SDK/Local/C/autom4te: No such file or directory

But the file is there and has s+rwed flags.

Any idea?

Thanks for the info! FIB is really totally outdated...

Thanks.

The program is unfortunately an old 68k program written in AmigaE. I develop on OS4 though, and people use it on OS4. But I'm stuck with fib.

I'll simply put in an exception for -1. The user must have reported the problem from a 68k system where the nfs-handler file system is broken since I would assume the OS4 emulator would/could not put -1 in there.

@MickJT

So it is caused by different amigaos.x files? These are text files. Any diff available?

Hi

Does anyone know if fib_DirEntryType = -1 has a special meaning, or is it just a bug in the "nfs-handler" filesystem driver?

This is what I can find in the SDK:
#define ST_ROOT 1
#define ST_USERDIR 2
#define ST_SOFTLINK 3 /* looks like dir, but may point to a file! */
#define ST_LINKDIR 4 /* hard link to dir */
#define ST_FILE -3 /* must be negative for FIB! */
#define ST_LINKFILE -4 /* hard link to file */
#define ST_PIPEFILE -5 /* for pipes that support ExamineFH */

-1 does not exist, but a macro indicates any negative number is a file:
#define FIB_IS_FILE(fib) ((fib)->fib_DirEntryType < 0)

Any thoughts? Do I have to implement a special case here? I'm handling links too, so can't just use this macro.

Thanks.

@stonecracker

Hi, and welcome!

Our current browser (Odyssey) is based on Webkit (which is good), but the latest versions of Webkit dropped big-endian support in the JS engine (not good). So someone here needs to reimplement big-endian support in the JS-engine to prevent it from crashing at the first JS it runs.

Problem is: Noone who actually has the skills to do it (like for example me) have the time to do it. It seems like a pretty big job with lots and lots of code to go through and understand and test and fix. (Assuming, since I haven't actually looked at the code.)

Just setting up the build environment, which has to be cross-compile, and get all the dependencies together is a big hurdle. I tend to get so pissed of when I have to deal with dependencies and make problems that I almost throw the computer out, so I need a simple idiot-proof setup if I'm even going to think about trying to work on it. Maybe someone can help here...

@daveyw

To emulate Altivec (at any useful speed), Xena would have to be about 4 times faster than the PPC CPU itself, which it isn't. More like 1/20..? It would also be able to transparantly intercept any Altivec instruction the CPU 'accidently' consumes. The CPU itslef would be MUCH better at emulating missing Altivec, just like the FPU, or other missing instructions, can be emulated on 68EC-machines.

Video mixing is probably also out of reach considering the data rate of 3Gbit/s just to maintain a 24-bit fullHD image on screen.

S/PDIF digital audio on the other hand should be perfectly doable.

The thing is I did a mirror copy (using BackUp, no errors) and only softrebooted between partitioning and restoring so the original RadeonHD.chip should still be in memory (as we speek).

In the meantime I let it boot up on an older (FE) partition. But it is also new enough to use the same RadeonHD.chip, and the resolution was OK here.

Only when I did the final reboot after restoring it came up without my modes.

So wierd... I solved it temporarily by simply adding 1920x1080 to the default Radeon monitor and softrebooted again, so now I get the correct resolution. But selecting "Radeon HD 6570" still doesn't make its modes availble...

I needed to repartition my SYS partition, so I made a backup of all files, repartitioned and copied back the backup and rebooted.

But now Workbench boots into a 1280x1024 display and my other modes are gone. WTF?

Anyone seen anything similar?

------------------------

In ScreenMode I can see my two monitors "Radeon" and "Radeon HD 6570" in the dropdown list. It seems to be using the plain Radeon monitor now. Changing to the other one does not give me its list of monitors on the "Available Modes" tab.

What do I need to do to 'enable' the Radoen HD 6570 monitor again? What could have caused it to be disabled such that I can't use its modes?

During the restoring process I booted up from an older workbench backup partition which displayed correctly and had the same screenmode prefs, which I haven't changed for years.

@all

kas1e, as always, brings reality to people! I love it!

One question: Is it the JS JIT that has endian issues, or the plain interpreter?

We have been living without JIT since the beginning of time, so let's not waste time on that to begin with. I think I heard someone (Fab?) was working on the JIT engine at some point..?

@BSzili

Quote:

I totally agree! You still end up with a non-working/non-compilable webkit.

Getting Odyssey up-to-date is BY FAR the easiest route to a very well functioning browser.

Trying to restart Timberwolf, or port Chrome from scratch is just a shitload more work.

One must not forget all the manyears of work Fab has put into Odyssey to make it a very good Amiga application.

What's needed is a C++11 compiler for AmigaOS and to fix the JS-engine. The latter is the hard and time consuming part.

@ChrisH

It doesn't matter. Thesites that complain now actually do use functions not supported by our old webkit. Can't comment on facebook, can't open the chat. Lots of things stopped working recently. Spoofing doesn't appear to help much. I tried most options....

@JosDuchIt

Quote:
Noone in their right mind would reimplement the missing features in webkit.
Quote:

Yes, by replacing the current webkit core with a new one. This is what causes the problems we have:

1. There was no compiler modern enough to build it for OS4 (don't know if they fixed that), otherwise a fairly big task. The newest webkit uses C++11 features. Our compiler only supports C++9 (I think).

2. The java-script engine is written for little-endian (x86, arm) now, and will crash on PPC big-endian hardware. Fixing this is very tedious and time consuming. The developers of webkit simply stopped caring about PPC support.

@Atheist

Quote:

That's comic
Rewrite the entire Internet for Amiga (instead of rewriting Amiga software to work with the Internet). Seem a lot easier, and less work to maintain... NOT

Custom standards (like Flash, Silverlight) is exactly what we DON'T want. We want open standards like HTML5.

Quote:

amigans.net and amigaworld.net, not accessible with Firefox or IExploder?

There seems to have been some kind API switch in the world of www which has rendered a lot of web sides useless in just a few month using Odyssey.

Facebook fails on many functions, including chat, and complains about obsolete browser.
Google doesn't display pictures anymore, unless one spoofs to get some old interface.
Outlook falls back to a basic interface (that actually works!).
Gmail also falls back, but it doesn't really work, or lack functionality. Confusing to use.
Finn.no (the norwegian ebay) can't create or edit ads anymore.
I guess it's just a matter of time until the banks start failing again too.

Here I am, complaining, and all I do all day long is feed my kid and work on the new (old) house. Wish I had the time to help Odyssey development, but I really don't.

Does anyone know if there is any progress being made on a new Odyssey with a smoking fresh webkit engine that could last us a few more years?

@Futaura

It was a while since I tried IBrowse, but my god how increadibly fast it is!! It's just instant!! Odyssey really crawls in comparison. X1000.

Too bad it doesn't support CSS/HTML5, but then again it would probably be just as slow...