Problem fixed

Thanks to Ball000, who showed me a way, to hide a window (and make in reappear again!), no bad hack is necessary any more to hide the main uae window. ChangeWindowShape is my new friend now :). But I still have no idea, how to make a window opened with WA_Visible=FALSE visible again ;). But it does not matter any more.

clusteruk wanted more memory in amigaOS, the next version will have it:

If you try to give too much memory to amigaOS, you don't get an error message, you just get 0MB of ZIII ram.


From hosted to virtual

When I spread a v0.5 to some people, I did get quite disappointing results. Not many of them managed to get it working. It worked perfectly for my AROS hosted on Linux, but only very rare and unstable on their native machines.

Up to now, I did not have a native AROS around, but I did not want to get some real hardware here. QEMU and VirtualBox are not really working stable on this machine, I think they don't like VMWare already running. But I found an old Icaros VE 1.1 image for VMWare, so I will use that for my native tests. Network works, so I wrote a little script, which fetches the binaries from my build machine (another virtual VMWare guest). WGet is really working well on AROS. I was really happy, that wget is available and a little bit surprised, too ;).

And yes, j-uae does not run well on a native host, if it runs at all. Strange..

Back when I started, I had to hide the main UAE window in order to show only the coherent windows. I tried a hack, just resize it to a 1x1 pixel big window and place it in the lower right corner of the screen. If the user switches back from coherent mode, I just resized it to the original values again. Works nice on hosted. Works *not* on native, as it seems.

But UAE does not really run well without its main window. And I did not want to fix that. So I saw, that you can open a window with WA_Hide in AROS. And it is really hidden! The only thing I did not find (not even in the sources) was a way, to show it again (is there one?).

So now I open a hidden window for coherent mode, if the user changes, I open a visible window and close the invisible one. Problem is, I have to protect all accesses to the main window struct with a semaphore. I hope, this does not cost too much of performance, but so far it seems ok.

So at the moment, j-uae runs on my "native" machine, too :). But I just did a quick test, there are for sure still some bugs remaining..


Just a test ..

and no, it is not working. No, I don't know, if I will finish it ;).

This is just a dummy stub, which lacks all host features. The only thing it can do, is print some debug messages:

bsdsock.c:314 host_sbinit(): NOT YET IMPLEMENTED!
bsdsock.c:274 locksigqueue(): NOT YET IMPLEMENTED!
bsdsock.c:282 unlocksigqueue(): NOT YET IMPLEMENTED!
bsdsock.c:2750 host_gethostname(): NOT YET IMPLEMENTED!
bsdsock.c:2616 host_getservbynameport(): NOT YET IMPLEMENTED!
bsdsock.c:344 host_sbcleanup(): NOT YET IMPLEMENTED!
bsdsock.c:274 locksigqueue(): NOT YET IMPLEMENTED!
bsdsock.c:282 unlocksigqueue(): NOT YET IMPLEMENTED!

This is totally unrelated to AROS, but it gives you an impression, what I did last weekend :)))) :


Wanderer integration part 2

All the missing parts are done now, so if you click on a editor and then double click a text file, the editor opens the text file. If it is a 68k AmigaOS editor or not, does not matter anymore. Of course, both the editor and the text file must be accessible (mounted) in AmigaOS.

To make all that stuff safe, to add configuration parameters and to be able to switch it on and off easily, is more work than to get it working for a first time..

And a GUI was missing, too, of course. As the old GUI was not very intuitive (I never was good at GUI design), I gave it another try. So it looks like that now:

So what is the current bounty status?

1. Must be able to run some classical software which must include: WordWorth 6, Organizer 2, Datastore 2 and Money Matters 4.*

2. Must provide support for window and screen based apps so they appear to be running on the host system - including access to public screens.

3. Doubling-clicking a 68k application in Wanderer will cause that application to be run in the emulation.

4. Each instance of emulation will be a commodity that can be shut down via Exchange.

5. Port over a Zune based UAE prefs application.

6. UAE to use AROS clipboard.

7. separate directory (for 68K files) dictated by the chosen config.

So all features are implemented. Bug fixing and test time!