Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A1200/A600 4xIDE Interface

AuthorTopic: The Os 3.1.4 Thread  (Read 126471 times)

0 Members and 4 Guests are viewing this topic.

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #180 on: October 05, 2018, 03:26:17 PM »
Is it possible to make a Super Kickstart Disk with the A3000 ROM images using your tool Olsen?
I don't know, we haven't tested. Actually, the build chain does generate a superkickstart compatible version of exec, and probably even builds the superkickstart, but in how far this is working I do not know. It certainly lacks testing, and for that it is not sold.

This being said, we can probably arrange something if you are aware of the limitations. I would suggest that you go for an A3000 ROM, and then send a small mail to Hyperion asking them for the A3000 superkickstart version of it, and I'll see what I can do about it.

Wether this will work I cannot promise, of course.

 
The following users thanked this post: nicholas

Offline vxm

Re: The Os 3.1.4 Thread
« Reply #181 on: October 05, 2018, 03:27:01 PM »
"( list || dir ) | more" is okay but "list | sort | more" gives me "required argument missing".

And about the ability to display a file according to its datatype via multiview?
 

Offline BozzerBigD

Re: The Os 3.1.4 Thread
« Reply #182 on: October 05, 2018, 03:36:55 PM »
@Thomas Richter

Quote
I'm sorry, I really don't get your attitude.

Just checking that it won't further fragment development resources etc. It's great that OS3.x is under development again and it is a shame it ever stopped to be honest. A clean version of OS3.1.4 deserves a clean machine IMHO and I'm sadly not really interested until a Vampire standalone is available. Then I think this project has legs.
« Last Edit: October 05, 2018, 04:36:19 PM by BozzerBigD »
"Art challenges technology. Technology inspires the art."

John Lasseter, Co-Founder of Pixar Animation Studios
 

Offline olsen

Re: The Os 3.1.4 Thread
« Reply #183 on: October 05, 2018, 03:56:31 PM »
Is it possible to make a Super Kickstart Disk with the A3000 ROM images using your tool Olsen?


http://aminet.net/package/util/misc/MakeSuperDisk

Yes, but some assembly is required.

Both the 1.3 and 2.x (and by extension the 3.x) ROMs on a SuperKickstart disk consist of both the respective ROM image (256 KB for Kickstart 1.3, 512 KB for everything else) and what's called "bonus" code which is appended to the ROM. The Kickstart selection menu of the A3000 boot roms checks if the bonus code is present, and if it's not it will refuse to load the respective Kickstart ROM image.

The purpose of this specific "bonus" code (there's a bonus module in the A3000 ROM which has a different purpose) is to set up the MMU and exception handlers which allow for the respective Kickstart loaded to remain in memory until you switch it off. It's a software solution for what the Amiga 1000 did in hardware back in the day ;)

You can make the AmigaOS 3.1.4 A3000 Kickstart ROM suitable for use on a SuperKickstart disk by copying the respective bonus code from what's in your A3000 "WB_2.x:devs/kickstart" file and appending it to the Kickstart ROM image. If the "WB_2.x:devs/kickstart" file is larger than 524288 bytes, then copy all the data which begins at the 524289th byte until the end of the kickstart file. That data contains the bonus code which the Kickstart selection menu expects. Append this bonus code to the AmigaOS 3.1.4 A3000 ROM file and the MakeSuperDisk program should be able to use it.

Come to think of it, we could add the A3000-specific bonus code to the ROM image and include it in the A3000 download package as a "SuperKickstart ROM image" file.
« Last Edit: October 05, 2018, 04:00:15 PM by olsen »
 
The following users thanked this post: nicholas

Offline bubbob42

Re: The Os 3.1.4 Thread
« Reply #184 on: October 05, 2018, 04:56:08 PM »
Just checking that it won't further fragment development resources etc.

On the contrary - our goal has always been to unite our resources with other developers'. That's the only reason why the Vampire supported 3.1.4 even before release. And not some tin foil hat conspiracy about Hyperion trying to rip off Vampire users, I'm afraid.

So, the truth may be a bit boring, but at least gratifying. :)

 
 

Offline stx

Re: The Os 3.1.4 Thread
« Reply #185 on: October 05, 2018, 07:27:31 PM »
I'm having the following issue:
https://forum.icomp.de/index.php?thread/40-x-surf-100-and-rapid-road-not-working-after-amigaos-3-1-4-upgrade

According to Jens, there is something broken with the freemem list in the 3.1.4 kickstart.

For those having the same issue with an X-Surf 100 card, see the workaround using the MuSetCacheMode tool.
« Last Edit: October 05, 2018, 07:35:08 PM by stx »
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #186 on: October 05, 2018, 08:00:02 PM »
According to Jens, there is something broken with the freemem list in the 3.1.4 kickstart.
The Kickstart doesn't set any cache modes, it never did. The mmulib does.

For those having the same issue with an X-Surf 100 card, see the workaround using the MuSetCacheMode tool.
I have an XSurf-100 and see no issues.

Do you have an issue with it? If so, please report the output of MuScan and ShowConfig *without* any MuSetCacheMode workaround. In case you use an ENVARC:MMU-Configuration, please report this as well.

 

Offline kamelito

Re: The Os 3.1.4 Thread
« Reply #187 on: October 05, 2018, 08:24:44 PM »
@thor,
You probably have seen Bryce Nesbitt interview, at one point he spoke about memory protection, was it ready? code was available? is this something that can be added to AmigaOS knowing that they knew how to do it back then?
Are you going to follow CBM roadmap at one point?

https://vimeo.com/272762254
 

Offline stx

Re: The Os 3.1.4 Thread
« Reply #188 on: October 05, 2018, 09:35:49 PM »
Thanks Thomas for helping on my X-Surf 100 issue.

Output of MuScan just after running setpatch:

Code: [Select]
MuScan 46.1 (02.07.2016) <A9> THOR

68040 MMU detected.
MMU page size is 0x1000 bytes.

Memory map:
0x00000000 - 0x001FFFFF CacheInhibit
0x00200000 - 0x00BBFFFF CacheInhibit Blank
0x00BC0000 - 0x00BFFFFF CacheInhibit I/O space
0x00C00000 - 0x00D7FFFF CacheInhibit Blank
0x00D80000 - 0x00DFFFFF CacheInhibit I/O space
0x00E00000 - 0x00E8FFFF CacheInhibit Blank
0x00E90000 - 0x00EAFFFF CacheInhibit I/O space
0x00EB0000 - 0x00EFFFFF CacheInhibit Blank
0x00F00000 - 0x00F7FFFF CacheInhibit
0x00F80000 - 0x00FFFFFF ROM CacheInhibit
0x01000000 - 0x06FFFFFF Blank
0x07000000 - 0x07FFFFFF
0x08000000 - 0x3FFFFFFF Blank
0x40000000 - 0x4000FFFF I/O space
0x40010000 - 0x43FFFFFF Blank
0x44000000 - 0x44FFFFFF I/O space
0x45000000 - 0x4FFFFFFF Blank
0x50000000 - 0x5FFFFFFF
0x60000000 - 0xFFFFFFFF Blank

Output of showconfig:
Code: [Select]
PROCESSOR:      CPU 68040/68882fpu/68040mmu
CUSTOM CHIPS:   AA NTSC Alice (id=$0033), AA Lisa (id=$00F8)
VERS:   Kickstart version 46.45, Exec version 46.45, Disk version 45.194
RAM:    Node type $A, Attributes $505 (FAST), at $7000000-$7FFFFFF (16.0 meg)
        Node type $A, Attributes $405 (FAST), at $50000000-$5FFFFFFF (256.0 meg)
        Node type $A, Attributes $703 (CHIP), at $4000-$1FFFFF (~2.0 meg)
BOARDS:
 individual Computers X-Surf 100 Rev.3 Z-II/Z-III Ethernet:   Prod=4626/100($1212/$64)
     (@$40000000, size 64meg, subsize 64K)
 Great Valley Products Spectrum Memory:   Prod=2193/1($891/$1)
     (@$44000000, size 2meg, subsize same)
 Great Valley Products Spectrum:   Prod=2193/2($891/$2) (@$E90000 64K)
 Commodore (West Chester) A 590/2091 SCSI:   Prod=514/3($202/$3) (@$EA0000 64K)
 E3B ZorRAM/BigRam+/256MB Zorro III memory Expansion:   Prod=3643/32($E3B/$20)
     (@$50000000, size 256meg, subsize autosized Mem)

I don't have a file named ENVARC:MMU-Configuration yet.
« Last Edit: October 05, 2018, 09:51:51 PM by stx »
 

Offline stx

Re: The Os 3.1.4 Thread
« Reply #189 on: October 05, 2018, 10:06:33 PM »
Here is another output of MuScan. This time also after setpatch but skipping the "LoadModule ROMUPDATE" (meaning running 3.1 kickstart instead of 3.1.4):

Code: [Select]
MuScan 46.1 (02.07.2016) <A9> THOR

68040 MMU detected.
MMU page size is 0x1000 bytes.

Memory map:
0x00000000 - 0x001FFFFF CacheInhibit Imprecise NonSerial
0x00200000 - 0x00BBFFFF Blank
0x00BC0000 - 0x00BFFFFF CacheInhibit I/O space
0x00C00000 - 0x00D7FFFF Blank
0x00D80000 - 0x00DFFFFF CacheInhibit I/O space
0x00E00000 - 0x00E8FFFF Blank
0x00E90000 - 0x00EAFFFF CacheInhibit I/O space
0x00EB0000 - 0x00EFFFFF Blank
0x00F00000 - 0x00F7FFFF CacheInhibit
0x00F80000 - 0x00FFFFFF ROM
0x01000000 - 0x06FFFFFF Blank
0x07000000 - 0x07FFFFFF CopyBack
0x08000000 - 0x3FFFFFFF Blank
0x40000000 - 0x4000FFFF CacheInhibit I/O space
0x40010000 - 0x43FFFFFF Blank
0x44000000 - 0x44FFFFFF CacheInhibit I/O space
0x45000000 - 0x4FFFFFFF Blank
0x50000000 - 0x5FFFFFFF CopyBack
0x60000000 - 0xFFFFFFFF Blank
« Last Edit: October 06, 2018, 01:24:14 AM by stx »
 

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #190 on: October 06, 2018, 01:07:37 AM »
Thanks. This is not related to 3.1.4 or rather, only very indirectly. The mmulib setup code is too critical about a particular decision and rejects a test because the ColdReboot() vector is now in RAM, not in ROM. The issue will go away with a ROM, or I check what I can do with the next release of the mmu.lib.

For the time being, please create a file

ENVARC:MMU-Configuration

and add the following single line:

ClearTTx

on top. This should resolve the issue.
 
The following users thanked this post: LoadWB, stx

guest11527

  • Guest
Re: The Os 3.1.4 Thread
« Reply #191 on: October 06, 2018, 01:10:38 AM »
Memory protection is not going to work on AmigaOs. This is because there is no clear indication as which resource is owned by which task (or "MMU context"). The Os nicely shifts resources back and forth, so you never know where it belongs.

There are a couple of simpler forms of "memory protection" you can play, of course. MuProtectModules, for example, adds write protection for the modules that have been installed by LoadModule. In principle, you could do the same with resources loaded by "Resident", except that I haven't done that yet.

 

Offline stx

Re: The Os 3.1.4 Thread
« Reply #192 on: October 06, 2018, 02:05:11 AM »
Quote
For the time being, please create a file

ENVARC:MMU-Configuration

and add the following single line:

ClearTTx

This trick works great! Thanks a lot!

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #193 on: October 06, 2018, 06:35:13 AM »
Quote from: Thomas Richter
We'd love to include reaction, but we cannot.

Because Hyperion is not exclusive owners of either?
Is Reaction licensed from Caldi etc, under conditions that restricts Hyperion to only use it on OS4/PPC?
« Last Edit: October 06, 2018, 06:43:50 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline kolla

Re: The Os 3.1.4 Thread
« Reply #194 on: October 06, 2018, 07:00:11 AM »
I saw on a different forum that someone wrote ...
Quote
Personally, I'd choose to buy the version that fits best to the majority of Amigas in one's household.
I am not sure what this person implicitly meant with this.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS