Amiga.org
Amiga computer related discussion => General chat about Amiga topics => Topic started by: tonyvdb on December 27, 2015, 09:41:21 PM
-
So installing a larger 4gb hard drive on my a2000. I don't want to spent the money upgrading the roms right now so can I install OS 3.1 on the 2.0roms or should I just stick to OS2.1?
-
I always found this chart very handy.
http://wiki.classicamiga.com/Kickstart_Roms_Explained
Looks like OS2.1 is max for 2.0, 2.4 and 2.5 ROMs.... :)
Also, very informative....;)
https://en.wikipedia.org/wiki/AmigaOS
-
Nope, requires new ROM chips. Ebay typically has them between 15-30 bucks, and I would invest in the newer ROMS and install 3.1 then go to at least OS 3.5. I have 3.5 on my 2000 HD.
-
Great info, thanks!
Any patches on aminet that would help "upgrade" this OS a bit? (That's probably a loaded question) but maybe just the must have ones if any.
-
I had similar situation, I wanted to have one machine with KS2.0-
It is OK, but everything is x times difficult than with KS3.1/OS3.1, so I give up and bought 3.1 roms.
-
It's strictly a gaming machine so 2.1 is fine as long as I can get WHDload working on it?
-
Any patches on aminet that would help "upgrade" this OS a bit? (That's probably a loaded question) but maybe just the must have ones if any.
Personally if I was building a low/mid-end gaming system, I'd start by putting 3.1 + BetterWB on it:
http://lilliput.amiga-projects.net/BetterWB.htm
The ROM can be bought on Amigakit or eBay for under $20.
Max out the ram in your 2091 would give you 2MB fast/1MB chip, that'll get you started with most basic Whdload games, although I've found you'll probably be happier with at least 4MB/2MB. ;)
You can also replace your 68000 with a 68010 for around $5, that'll give you about a 5% speed boost, but more importantly allow you to make use of the 'quit' key in most Whdload games. ;)
-
It is OK, but everything is x times difficult than with KS3.1/OS3.1, so I give up and bought 3.1 roms.
+1. You can do everything with the older versions that you can with the newer versions, but you're just making your life a whole lot harder. ;)
-
You will need old version for new icons, it will gave you some problems.
Without it you will get strange screen corruption when you open folder wich has game inside, wich doesn't have that few pixel bog normal icon, wich should be there. Some of them doesn't have that.
You can't use PeterK's icon.library because it doesn't support KS2.0. That would be best/easiest solution.
You might want to have magic menu wich has also some problems.
-
If he's only using it for gaming, then Peter K's icon.library or Magic-Menu doesn't matter. Just stay with ROM 2.x. The standard icon set is the same as the icons from 3.1.
And WHDLoad works just fine. No problems at all!
-
You can always softkick 3.1 if you have enough free RAM.
-
If he's only using it for gaming, then Peter K's icon.library or Magic-Menu doesn't matter. Just stay with ROM 2.x. The standard icon set is the same as the icons from 3.1.
And WHDLoad works just fine. No problems at all!
It sound logical, but it doesn't work that way.
Prety much every whdload game you can found has new icon. It is not easy to start those games with that bog standard icon wich is sized to 0,5mmx0,5mm. And there is also some games wich doesn't have event that and they crash system with KS2.0
-
It sound logical, but it doesn't work that way.
Prety much every whdload game you can found has new icon. It is not easy to start those games with that bog standard icon wich is sized to 0,5mmx0,5mm. And there is also some games wich doesn't have event that and they crash system with KS2.0
He could use TinyLauncher or AGLaunch, I use TinyLauncher perfectly well on a 2.0 rom A600.
I never go into the icons to launch a game, even on my beefed up A1200!
Or he could use a file manager like dopus or filemaster or dirworks and add a WHDLoad button and launch his games that way.
-
You can always softkick 3.1 if you have enough free RAM.
Anything to add Mike? :)
-
Anything to add Mike? :)
Oh, you already know. Just buy the doggone 3.1 ROM. For the love of god, it's $16 bucks. I can't take my girlfriend to McDonalds for less than that, lol. ;)
-
LOL, ok ok I'll get the 3.1 roms.
-
It sound logical, but it doesn't work that way.
Prety much every whdload game you can found has new icon. It is not easy to start those games with that bog standard icon wich is sized to 0,5mmx0,5mm. And there is also some games wich doesn't have event that and they crash system with KS2.0
One can simply change or design new icons. There are lots of icon editing programs floating around for that purpose. And I never had a WHDLoad game crash on my 2.x system.
-
Editing some hundresds icons would be pain.
About a crash. It happens when you open a folder wich has a newicon wich doesn't have that bogus standard icon sized to few pixels. It corrupts screen and it you try to do anything else than close a folder, it leads to crash.
-
Editing some hundresds icons would be pain.
About a crash. It happens when you open a folder wich has a newicon wich doesn't have that bogus standard icon sized to few pixels. It corrupts screen and it you try to do anything else than close a folder, it leads to crash.
Who's talking about "hundreds of games"? And if so, then get rid of the new icons, they're ugly anyway! And I never had any crash as you described on my 2.x system.
And like Paul1981 said: you can always use a game-launcher or file-manager.
-
Who's talking about "hundreds of games"?
Any of the better "game packs" a user might download will contain hundreds of games, already set up with NewIcons (typically a picture of the box art, or something similar).
-
Who's talking about "hundreds of games"? And if so, then get rid of the new icons, they're ugly anyway! And I never had any crash as you described on my 2.x system.
And like Paul1981 said: you can always use a game-launcher or file-manager.
Another solution is to delete all the .info files. I've never had a crash either on my 2.0 system (not due to Newicons).
-
Another solution is to delete all the .info files. I've never had a crash either on my 2.0 system (not due to Newicons).
Ummm, the .info file contains all of the settings for running the game (for example: PAL or NTSC screenmode, Preload size, NOAUTOVEC, etc. are all contained as tooltypes). Guess if you manually transfer each setting into a button on a task launcher or something, but wow. Once again, just making a whole lot more work for yourself. ;)
-
Ummm, the .info file contains all of the settings for running the game (for example: PAL or NTSC screenmode, Preload size, NOAUTOVEC, etc. are all contained as tooltypes). Guess if you manually transfer each setting into a button on a task launcher or something, but wow. Once again, just making a whole lot more work for yourself. ;)
All my WHDLoad games work without any adjustments to tooltypes. They're launched from TinyLauncher which just runs the command WHDLoad. I'm sorry to hear you're having to fiddle around with those settings.
-
All my WHDLoad games work without any adjustments to tooltypes. They're launched from TinyLauncher which just runs the command WHDLoad. I'm sorry to hear you're having to fiddle around with those settings.
I think most people do. ;)
Preload helps large games run faster (less disk access). Noautovec, NoMMU, etc., are for more upgraded systems. NTSC and PAL switches should be obvious (e.g., for opening a game with a PAL screenmode on a NTSC system --- obviously not an issue for you, since you run in PAL natively). I had to use some of these with my '040, on my '030 A500 games required far less tweaking.
These can be set globally through the config file in S:, or individually in each game's icon .info tooltypes.
A complete list of options is on the WHDLoad site: http://whdload.de/docs/en/opt.html
-
I think most people do. ;)
Preload helps large games run faster (less disk access). Noautovec, NoMMU, etc., are for more upgraded systems. NTSC and PAL switches should be obvious (e.g., for opening a game with a PAL screenmode on a NTSC system --- obviously not an issue for you, since you run in PAL natively). I had to use some of these with my '040, on my '030 A500 games required far less tweaking.
These can be set globally through the config file in S:, or individually in each game's icon .info tooltypes.
A complete list of options is on the WHDLoad site: http://whdload.de/docs/en/opt.html
That's what I mean, all the settings I need are set in S:WHDLoad.prefs.
I must say, I love the new slave version check feature which pops up a handy message when online.