New Kickstart 3.9.1 68k on the way

[kolla]

KingCON has been ROMable for quite some time, but only for 020+.

[olsen]

KingCON has been ROMable for quite some time, but only for 020+.

That might be more difficult to fix. Sounds like a partial rewrite/patch to me

[som99]

TPB is no longer down

http://thepiratebay.cr/

http://www.reddit.com/r/torrents/comments/2ouk92/thepiratebaycr_is_not_the_new_pirate_bay/

Not the same, but still seems illegal.

http://en.wikipedia.org/wiki/DADVSI#Sharing_of_copyrighted_works_over_peer-to-peer_networks

There are certainly bigger fish to fry though. Although with TPB down the amount of piracy has dropped considerably, which might put you on the radar.

TPB will be up again. But anyhow most of us are using private trackers and has since long stoped using TPB.

The .CR page have fully working magnet links tho, so you can still download the torrents using the magnet links and just ignore the .torrent file link.

Also searching for what you want on example Google and adding piratebay in the search then just open the cached link and you will still be able to get the torrent.

[bloodline]

Cosmos: Here's a plan of action for you -

1. Contact the authors of the various components you want to put in the ROM (I'm sure people here will help).
2. Get approval for the use of the components.
3. Use AROS equivalents for components you can't get approval for.

Simple :-)

[olsen]

WOuld it be possible to integrate CF card drivers somehow? I.E. a way to be able to detect and read CF cards right off the bat without requiring extras software on your boot disk and what not?

I had a quick look at Torsten Jager's "compactflash.device", and I think that there are no technical reasons why it could not be put into ROM.

The harder part is in mounting the file system (such as Torsten Jager's "fat95"), and mounting it early enough so that it becomes available at boot time.

As far as I can tell the "fat95" file system is not suitable for ROM use, but small changes might make it so. I did not check, but if I remember correctly the "CrossDOSFileSystem", which would serve a similar purpose, is not fit to be put into ROM because it was always intended to be loaded from disk. So a modified "fat95" file system suitable for ROM use might be the only option right now.

That leaves the somewhat nontrivial matter of mounting the "CF0:" device. It's doable, though: "carddisk.device" in the A600/A1200 ROM is capable of it, and you can even boot off the volume once it has been mounted, if I remember correctly.

[utri007]

There is a lots of talk how to build a rom with compactflash.device and fat95 in eab.abime.net

[TheMagicM]

Although with TPB down the amount of piracy has dropped considerably, which might put you on the radar.

"dropped considerably"?  Hardly.  There are many ways/sites to find torrents and magnets on.

[Niding]

Usenet...

[Minuous]

3. Use AROS equivalents for components you can't get approval for.

Simple :-)

This is supposed to be 3.9.1. AROS is only equivalent to 3.1, at best, and much less tightly written. So using AROS as a source for a "3.9.1" just won't cut it.

[Terminills]

This is supposed to be 3.9.1. AROS is only equivalent to 3.1, at best, and much less tightly written. So using AROS as a source for a "3.9.1" just won't cut it.

Would you seriously stop talking about what you have no clue about?  There's a huge difference between claiming to be 3.1 compliant and being a 3.1 clone.  AROS already surpasses 3.1 in many ways.

[Gulliver]

Would you seriously stop talking about what you have no clue about?  There's a huge difference between claiming to be 3.1 compliant and being a 3.1 clone.  AROS already surpasses 3.1 in many ways.

Sorry, but not in a real Amiga, over there, it is crappy shame.

In x86 or high speed emulation it is pretty good and I can agree that it surpasses 3.1. But in an Amiga is a big "NO".

[kolla]

This is supposed to be 3.9.1. AROS is only equivalent to 3.1, at best, and much less tightly written. So using AROS as a source for a "3.9.1" just won't cut it.

You have no idea what's in an OS3.9 kickstart do you - it is all just relatively small updates to what's in an OS3.1 kickstart, they are essentially the same.

[QuikSanz]

You have no idea what's in an OS3.9 kickstart do you - it is all just relatively small updates to what's in an OS3.1 kickstart, they are essentially the same.

This brings us back to the start! Replace the old stuff with the new stuff and you eliminate the reboot patch. Perfect sense.

Now the idea to replace the ROM with a small flash and add some stuff that gets everything going in one quick action is an interesting proposition.

This gets my attention real quick. With new FPGA's we may have some very fast 68k machines soon and this would make everything fly.

Chris

[kolla]

Yup

[Cosmos Amiga]

Since I got no answer from the author of the HSMathLibs, I decided to update the original from the OS 3.9 by myself.

They are unoptimized, I just make them romable and removing useless code (fpspresource). Take now in the rom about 20.4 Kb...

These libraries are important for the 3D, and must be available at boot. Please read here : http://warpclassic68k.blogspot.fr/2013/01/romability-eng.html



Kickstart 3.9.1 beta 3

- added mathieeedoubbas.library 45.4
- added mathieeedoubtrans.library 45.6
- added mathieeesingtrans.library 45.5
- added mathtrans.library 37.2
- added xpkDMCB.library 1.1
- added xpkSMPL.library 1.1
- added xpkSHR3.library 3.0 (with the authorisation of his author Cholok, thank you so much guy !)


About 280 Kb free still available into this new Kickstart...

[olsen]

...

- added mathieeedoubtrans 45.6
- added mathtrans.library 37.2

These two libraries are used extremely rarely, and then only by disk-based applications which already take their time loading and running. Software which requires high performance math uses inline FPU instructions, and not this.

There is very little benefit of putting these two libraries into ROM, and you may find much better uses for the space occupied by them.