AROS 68k updates from ApollOS repository

[deadwood]

It might be something related to 7z available on linux systems (might too old)

Code: [Select]

7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21


[AMIGASYSTEM]

These are the most important options, AROS 68k on WinUAE with a Dual-Core PC boots in 5 seconds.
Better to use WinUAE, FS-UAE is based on an old 3.x version of WinUAE so many new things are missing.

WinUAE: Config
If you need I can send you my WinUAE config

- CPU 060 (you can also use 020/040, the speed doesn't change)
- FPU enabled
- FAST RAM 256, you can also use 8MB ChipRAM
- JIT enabled
- Video Card UAE Zorro III 256 MB RAM
- Add the two news ROMs (WinUAE built-in ROMs are obsolete)

On FS-UAE I don't remember if the two ROMs have to be merged into one file

I merge the ROMs for Amilator and Janus-UAE, creating a single 1MB ROM.

[AMIGASYSTEM]

BTW, I tried downloading AROS Vision (aros_2020_Basis_UAE.7z) twice and each time I get "unexpected end of archive" error under Mint 20 when trying to decompress.

Tried WinRAR, no problem unpacking!

[Amiwell]

also 7-zip is great

[AMIGASYSTEM]

deadwood I enclose a small video that shows the configuration and the startup of AROS One 68k on WiNUAE, if you need I can send you in private my HardFile of my distribution AROS One 68k "at the moment not distributed" + the WinUAE configuration file

AROS One 68k on WinUAE Video Tutorial:

https://drive.google.com/file/d/1eq6ELK16JOqmB5WSAHnLV0DgH_0mruq1/view

[deadwood]

So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading. Can you make available for me your distribution?

Ok, I've been able to repeat the problem using an emergency.adf. Nightly indeed boots to Workbook, while my ROM stops. I'll continue invastigating.

[OlafS3]

thanks

[AMIGASYSTEM]

So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading. Can you make available for me your distribution?

Ok, I've been able to repeat the problem using an emergency.adf. Nightly indeed boots to Workbook, while my ROM stops. I'll continue invastigating.

I have no problem booting 17.10 nightly

OK time to send it on Google Driver and I send you my Distribution and WinUAE config in PM.

Using the Filesystem Directory doesn't change anything, I prefer to use HardFiles SFS formatted to keep all the files together for a better management.

In My Distribution you will find only "some" libraries renamed and replaced with OS3 libraries, this is so that some native Amiga Applications could work, see ModExplorer, AmiModRadio etc...

If you need it I can also create a HardFile with only 17.10 nightly native "standard".

[AMIGASYSTEM]

So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading.

You have problems because he didn't do the right configuration, check the WinUAE config data posted above! Also I suggest you to use a window instead of full screen and change the resolution to 1024x768 or bigger if you have a big monitor.
This way you can drag volumes, folders or files from the Desktopo to Wanderer.

[miker1264]

deadwood

Workbook is experimental. I believe Ronney Beck was working on it.

I believe Nightlies should boot to Wanderer. But I could be wrong.

My AROS (Plain) Vanilla is based on Nightlies. It has a custom backround and WBDock and a Workspace Test Directory.

I'll setup a new version based on the latest Nightly 68k files. 

[deadwood]

So far I have no luck with 17.10 nightly. I can boot to "kitty eyes", but adding a directory harddrive causes AROS to stop somewhere when loading.

You have problems because he didn't do the right configuration, check the WinUAE config data posted above! Also I suggest you to use a window instead of full screen and change the resolution to 1024x768 or bigger if you have a big monitor.
This way you can drag volumes, folders or files from the Desktopo to Wanderer.

At this point I think the FS-UAE disk support is somehow not compatible with AROS. It used to work though - this is how I was testing. Using an emergency.adf works around this problem.

[AMIGASYSTEM]

I think so, this morning I tried to boot FS-UAE from Amilator (Linux distribution that uses FS-UAE) and I got an error on the Cooprocessor, see screenshot, I reported the problem on EAB


Now I tried again on WinUAE the 17.10 nightly and it started perfectly, see small video attached

https://drive.google.com/file/d/1iIce-veOEYgOu0AqYl9jFcQg6VnWRvRQ/view?usp=sharing

[AMIGASYSTEM]

Strange the Cooprocessor error because always on FS-UAE "Amilator" AfA One works perfectly (same requirement and same configuration used for AROS One), see my old video !

https://www.youtube.com/watch?v=b5XaU77f8eg

https://www.youtube.com/watch?v=0mqJtNg3KKs

[miker1264]

Now I tried again on WinUAE the 17.10 nightly and it started perfectly, see small video attached

Yes. I use WinUAE for testing the 68k builds. It also has debug if you start it with -log -serlog parameters. It also starts and closes quickly and VMWare can copy/paste directly to the directories.

So I prefer using WinUAE with AROS directories hosted on Windows rather than hdf files.

[AMIGASYSTEM]

I know how to make logs and other operations on WinUAE, I usually use them when I report problems on WinUAE to Toni Wilen.

Directory Filesystems in some cases are not good, there are native Amiga or AROS files or folders that use special characters will not be handled by windows.

Try to create unnamed folders or files (only spaces) or folders or files with the character

Windows will show these folders with the name "__uae__".


EDIT:

Do you mean copy/paste on VMWare Emulation "Windows"? It doesn't work VMWare Emulation AROS x86.