Sure thing. Beware this is basically a proof-of-concept and only tested on my system. It relies on the screenmode.prefs file being in the same exact format on every system.

TARGET should be the host-side absolute path to your Prefs/Env-Archive/SYS/screenmode.prefs file.

I keep this script under System/Host/bin and execute (backgrounded) from the bootaros script before booting AROS. It must be backgrounded as it will watch the screenmode.prefs file for further changes (only occurs when changes are saved in AROS) ie. something like this:

# start AROS
cd /AROS
./System/Host/bin/watch-aros-screenmode.sh &
./Arch/linux/AROSBootstrap -m 512

It requires inotify-tools and xrandr. Also I'm running an Ubuntu-based system, so the paths may be different on Fedora et al.

I was toying with the idea of a generic compatibility layer for AROS to interface with the host. It would be interesting to see how much of the native experience can be replicated when running hosted. Actually I need to give AEROS another try too..

Attach file:

---

Link only for registered users

If you don't mind sharing your script... I guess also X modifying its resolution to match the AROS one would be pretty.

Fullscreen or windowed would be down to the window manager. Eg. in KDE you can remember window settings per application - fullscreen or windowed, which screen and which virtual desktop to open on etc.

On my dedicated AROS machine I'm using Ratpoison as the WM for Icaros-Hosted. Ratpoison's default operation is fullscreen windows with no window decoration, titlebar etc.. You can configure a preferred shorcut key for switching between the fullscreen windows (actually "frames") which works much like switching screens within AROS, but your frames could be whole AROS or UAE sessions, or any other program running on the host. This way the host system can be concealed pretty well.

My hosted system only runs AROS, so I use a script to set the X resolution to match that in AROS prefs, this way AROS is always fullscreen at any resolution, just like it should be ;). This could probably also be done in reverse (set AROS resolution to match X) by hacking the screenmode.prefs file before startup, but it will still open in a window if that's what the WM chooses. I can share the script here but it's still pretty crappy as I'm no bash expert. :)

Quote:
Current available aros drivers do not support switching to full-screen resolution on host side.

I doubt it ever will because afaik that depends on the desktop manager in use (and there are many of them).

For example with my pi it is possible to press F11 to go full-screen. A small correction to the AROS video settings and that takes care of things but, i still have to press F11 each and every time.

Perhaps someone more experienced with X11 (development) could elaborate a bit more on the topic.

fwiw: It doesn't work for windows either but, that is possible to address with manipulating the hosted window with a small program.

I have more questions.

I tried running AROSBootstrap with -f and --fullscreen options but the best I could achieve was running AROS in a window as big as the desktop (after manually setting the AROS resolution with ScreenMode), with its titlescreen on the top (and bottom pixel lines pushed out of the visibile area of the screen).

Is there a way to make AROS run in real full screen on X11?

Moreover, I barely remember having read something, somewhere in the neighborhood of this topic, about the chance to script a procedure which would adapt AROS resolution to Linux one automatically at startup. Unfortunately I looked for this solution again, but without luck. Is this feasible?

Quote:

Many thanks!!!

<p><iframe frameborder="0" height="350" src="http://www.youtube.com/embed/R3DMdVjzsmE" width="425"></iframe></p><p>I KNEW I could not just stop...</p>

I followed the hint to delete nvidia from Devs/Monitors and everything seems fine. Not that I know how it all works but I assume linux-hosted only makes use of Devs/Monitors/X11 anyway.

The nvidia driver at Devs/Drivers/nouveau.hidd still remains on my system and doesn't seem to be doing any harm.

Just a question: is "delete the Nvidia driver" hint still applicable? And what's exactly to delete? Files from devs/monitors or devs/drivers?

Awesome! Thanks Paolo.

I've been playing with native for a couple of years now, but just recently started playing with hosted to see what sort of experience is possible due to the many advantages.

I'm looking forward to trying out the new version soon!