@number6

Quote:

number6 wrote: @number6 Not knowing when the news will get approved, I'll post this here: Announcement download #6

What! No CD32 version? Those bastards!

@number6

Quote:

number6 wrote: @number6 Not knowing when the news will get approved, I'll post this here: Announcement download #6

What! No CD32 version? Those bastards!

Is the 1200 version possible to use it for an installation on a CD32?
Having a terrible fire would be very useful this update

@Lou

The 1200 version should be fine also for the Cd32 I see no difference

@cip060

I bought three sets of the newer Roms for the A500, A1200 and A4000.

I have to say it was a pleasant surprise that they included not only the rom images that can be soft-kicked but the burnable to Eprom images as well. I have already burned a set for my stock A1200. Soon I will test the soft-kick version on my Tower setup and see how that goes. Overall I am pretty happy with the newer Kickstart Roms and Bundled Software, anything new and Amiga related I am always happy to see.

Drewlio77

Last edited by Drewlio77 on 01-Oct-2018 at 03:51 PM.

@Drewlio77
Do you have the chance to create a rom for the cd32?
And test it?

@cip060

Sadly, I do not have an Amiga Cd32 to test the new ROMs on. Still plan on getting one eventually.

Drewlio77

@cip060

Quote:

cip060 wrote: @Lou The 1200 version should be fine also for the Cd32 I see no difference

The ROM contents are sufficiently different as to cause problems for users who want to keep using the CD32 as a game system. For example, the CD32 has a different exec which pays attention to the CD32-specific 512 KB ROM. The boot menu is different and the nonvolatile library is specific to the CD32 hardware. The A1200 ROM lacks the cd.device which is crucial for the CD32, as is the CD user interface. All of this is in the "main" ROM which is similar to the A1200 ROM.

If done right, an updated CD32 AmigaOS 3.1.4 would need to be able to use the full CD32-specific ROM components, including the CD32-specific 512 KB ROM part.

@olsen

One question regarding CDRom support, as A1200 and A600 supports bigger roms maybe it would be doable to add cdrom support (with boot option) to A1200/A600 roms (and make them 1MB by default, 512kB is so nineties). It doesn't seem to be rocket science and having bootable cds would be a nice addition.


And one bug more, CDboostrap from CDTV doesn't allow to boot from roms added from autoconfig devices (only from cdrom/floppy/scsi). This could be fixed.

@rzookol

Quote:

rzookol wrote: @olsen One question regarding CDRom support, as A1200 and A600 supports bigger roms maybe it would be doable to add cdrom support (with boot option) to A1200/A600 roms (and make them 1MB by default, 512kB is so nineties). It doesn't seem to be rocket science and having bootable cds would be a nice addition.

Rocket science? What kind of rockets are we talking about (compare William Burrows' book "This new ocean", chapter 2)?

Seriously, the problem is with the IDE scsi.device which in its current state is "rigged" not to try and boot from CD-ROM devices. In part this limitation is due to the fact that when the code was originally written (1991-1994) CD-ROM devices didn't all properly report their block sizes, and not at the right time during the system startup procedure. Some drives would even hang if you tried to read from them at the wrong moment, or using the wrong block size.

So there's a battery of workarounds in place which prevent both the IDE and the SCSI scsi.device from shooting themselves where it hurts. Changing this code would be possible, and you'd either have an RDB on the CD-ROM or take a chance and assume it might be something which CDFileSystem could deal with. All of this would be doable, but hard to implement and to test.

Quote:

And one bug more, CDboostrap from CDTV doesn't allow to boot from roms added from autoconfig devices (only from cdrom/floppy/scsi). This could be fixed.

It could, but we cannot currently rebuild the CDTV ROM (this goes for both the Kickstart 1.3 image and the CDTV-specific ROM portion). The knowledge of how this is supposed to be done was lost a very long time ago

Last edited by olsen on 01-Oct-2018 at 06:47 PM.

@rzookol

I made some test with romdisk.device https://github.com/cnvogelg/romdisk and CD32 emulator from IdeFix / CacheCDFS.

I think that would be easiest way to make amiga boot from CD. Romdisk.device and required floppyimage file with CD32 emulator inside of kickstart. Less than 300kb.

Last edited by utri007 on 01-Oct-2018 at 11:16 PM.

Update XE and buy One. OS4 too. No 3,1x

I'm a bit confused by this update - this is definitely my fault at least in part, for having been distant from the Amiga scene for a very good while. But let's not digress.

I am sure Kickstart 3.1 is required (either in ROM or SoftKick variant) tu run this brand new update, but I see there are now different KS versions available.

Which version should I get and what would be the actual differences? Would it be possibile to purchase a ROM file to be used under emulation (UAE and things like that) as well?

Last edited by Turrican3 on 02-Oct-2018 at 12:06 PM.
Last edited by Turrican3 on 02-Oct-2018 at 11:51 AM.

@Turrican3

This is a new Kickstart image and OS floppy images. A matched set. Your old ROM will be replaced.

Eventually physical ROMs and floppies will be available from the usual stores.

The different ROM versions are for different Amiga models. They each have always required a slightly different ROM, although some models are so similar that they use the same one. A500/A2000, A3000/A3000T, etc.

You can use these in an emulator, but you will need to emulate the machine that matches the ROM. This has always been the case too.

I hope this helps.

-

Last edited by utri007 on 02-Oct-2018 at 08:17 PM.

So, this is interesting, may need to get this soon. But since I no longer have any hardware to run this directly, I'd be running in WinUAE on my PC. My A3000 had died years ago when the CSPPC board I had in it fried and took out several chips on the motherboard. And more recently the AmigaOne XE G4 system is out, since the on-board NIC died and I can't find a suitable replacement card that I can use (every slot was used up for other stuff that didn't work right on the board either).

In any case, what would be the best option for WinUAE use? And now that everything's been made 68060-friendly, what would actually be the best CPU/FPU options in WinUAE for it?

I had tried to get OS4 working in recent WinUAE versions, but it's just too fiddly to get it working well, and is too slow for what I want to do. 68K emulation is more than fast enough to do what I want to do on an Amiga anymore.

_________________
This posting, in it's entirety, is the opinion and/or statement of the author and does not reflect the views and/or position of this site.

@Wumpus

Thanks for the answer... in the meantime I googled a bit and found out that there is indeed a "3.X" Kickstart produced by Cloanto that, as far as I understand, is actually different from the (good?) old one dated back to Commodore days.

I did know about the different ROM versions for different Amiga models but I was actually interested in those kind of differences.

So I'd like to know if there are any other versions available other than those two and whether this updated AmigaOS will work with any of them or not.

Sorry for not being clear enough before.

@Turrican3

No problem.

For most emulation use it probably won't matter much, especially for just playing old games.

These help more on real machines because they support big hard drives "out of the box".

I'm not sure about the slightly updated Cloanto stuff, but with 3.1, 3.5 and 3.9, you could still get yourself in trouble using a hard drive over 4GB pretty easily.

This version supports them with far fewer details that the user needs to be aware of, fixes a lot of other nagging issues and adds some new functionality.

The numbering scheme is off because due to changing hands and 3.5-3.9 being largely contract work and contributions, the current developers don't have access and/or license to use some of the 3.5-3.9 source code. IMHO, the other company was very short sighted on handling those two releases, but the code was pretty good at least.

Because of that, this one is based on the original 3.1 source, some bits from OS4 development and a lot of newly written code. In some ways it's better than 3.9, in some ways it's missing a few non-essential things, but that's what happens when you have to restart development from an older version.

I do think they chose wisely on what areas they improved though. Less eye candy and more about hardware support, bugfixes and removing hidden gotchas the user needs to be aware of.

Maybe that's in the ballpark of what you're looking for.

@DWolfman

Quote:

what would actually be the best CPU/FPU options in WinUAE for it?

68020+68882 (for compatibility). However, you may choose any CPU, there is next to no speed difference.

@thread

Does anyone know what EEPROM's the Amiga uses?

Model numbers, so I can buy blank chips and get the correct equipment to write them

_________________
Fred Booth
========================================
A500, A600, A1200 c/w Mediator and 030
AmigaOne and OS4.1
Mac LCII, G4 Powermac running OSX + Amigakit and MorphOS 3.0
Dell Mini 10 Netbook running IcAros and AmigaForever+Amikit+AmigaSys
2006 Macb