Classic Memory Limits in Emulation

A forum for Classic Amiga specific support issues.
headkase
Posts: 15
Joined: Sat Jun 25, 2016 10:45 pm

Classic Memory Limits in Emulation

Post by headkase »

Please excuse my ignorance if this has already been posted - I didn't see anything current about it on first blush.

I bought AmigaOS 4.1 FE Classic and am running it in emulation. I know it's not a "supported" configuration but that's okay: I'm not running it as my "daily" system, I'm running it out of nostalgia and past love for the Amiga platform. As everyone is no doubt aware the memory limits are hard-coded for 256MB for a BlizzardPPC setup and 128MB for a CyberStormPPC setup. Emulation-wise the CyberstormPPC setup works much better than the BlizzardPPC setup - hard drive access times, graphically updating the screen and such. Both however are crippled by that low memory limit. I know nothing can be done for real Amigas but could the limit be relaxed for emulation? Set a new limit of say 512MB or such. Enough to run a modern web-browser without running out of memory. As for "cannibalizing" sales it would do no such thing. The market segments for emulated and modern Amiga hardware are completely different. I am not in the market for a modern Amiga, I don't have the cash, but I am - along with no doubt many others - willing to run an "Amiga LITE" in emulation and would just like a little bit more RAM. An emulated system wouldn't be used for heavy lifting, that would be the purpose of actual modern Amiga hardware. Emulated systems fall into the "masses" "Amiga 500" while modern Amigas are the "Amiga 2000's" of this time. All that has to be recognized is that they are actually different market segments and can be addressed differently.

With the purchase of Cloanto's Amiga Forever that also includes, legally, the Amiga 4000 Kickstart ROM, the CyberStormPPC ROM, and the Picasso IV ROM. So that gives a completely legal path to AmigaOS 4.1 FE Classic emulation: no shenanigans.

Thank you,
Bill.
headkase
Posts: 15
Joined: Sat Jun 25, 2016 10:45 pm

Re: Classic Memory Limits in Emulation

Post by headkase »

Wow. What a deafening response. As a paying customer, you can check the main website - same name to see I put my money down, there is absolutely no response of any kind?
User avatar
jaokim
Beta Tester
Beta Tester
Posts: 90
Joined: Sat Jun 18, 2011 12:41 am

Re: Classic Memory Limits in Emulation

Post by jaokim »

This has been discussed here and there, although I can't find the threads now.

If I understand it correctly, the memory limit isn't explicitly set in software, but rather a "physical" constraint of the PPC-cards (real or emulated). Since emulation isn't supported, there's also nothing that can really be done about it.
headkase
Posts: 15
Joined: Sat Jun 25, 2016 10:45 pm

Re: Classic Memory Limits in Emulation

Post by headkase »

From what I've read there are two places for the memory limit. In the ROM used by the emulated PPC hardware, and this has been patched to a higher amount, and then the memory limit as defined in OS 4.1 FE. I'm sure that I've read that no matter what you set the emulated RAM to - you can set it as high as you want - OS 4.1 FE when it takes the boot after that does not recognize the increased memory.
headkase
Posts: 15
Joined: Sat Jun 25, 2016 10:45 pm

Re: Classic Memory Limits in Emulation

Post by headkase »

Also, as an aside, in my opinion is seems foolish that emulation is "not supported." Not everyone has a few grand to drop on real Amiga hardware, classic or modern, but practically everyone has a decent PC. Every person who owns one of those PC's is a potential customer. Take the population of Europe, America, and such and say "if we officially supported emulation then one out of fifteen-thousand would purchase OS 4.1 FE." When you consider those populations are in the hundreds of millions that is a lot of money to be "not supported." Again, in my opinion, Hyperion shouldn't say no to that money. And, to repeat myself, with Cloanto's Amiga Forever providing ALL the required ROMs and such there is a completely legal path to get to OS 4.1 FE on a PC.
User avatar
DarrenHD
Beta Tester
Beta Tester
Posts: 636
Joined: Mon Dec 20, 2010 3:38 pm
Location: London, Ontario, Canada
Contact:

Re: Classic Memory Limits in Emulation

Post by DarrenHD »

headkase wrote:Please excuse my ignorance if this has already been posted - I didn't see anything current about it on first blush.

I bought AmigaOS 4.1 FE Classic and am running it in emulation. I know it's not a "supported" configuration but that's okay: I'm not running it as my "daily" system, I'm running it out of nostalgia and past love for the Amiga platform. As everyone is no doubt aware the memory limits are hard-coded for 256MB for a BlizzardPPC setup and 128MB for a CyberStormPPC setup. Emulation-wise the CyberstormPPC setup works much better than the BlizzardPPC setup - hard drive access times, graphically updating the screen and such. Both however are crippled by that low memory limit. I know nothing can be done for real Amigas but could the limit be relaxed for emulation? Set a new limit of say 512MB or such. Enough to run a modern web-browser without running out of memory. As for "cannibalizing" sales it would do no such thing. The market segments for emulated and modern Amiga hardware are completely different. I am not in the market for a modern Amiga, I don't have the cash, but I am - along with no doubt many others - willing to run an "Amiga LITE" in emulation and would just like a little bit more RAM. An emulated system wouldn't be used for heavy lifting, that would be the purpose of actual modern Amiga hardware. Emulated systems fall into the "masses" "Amiga 500" while modern Amigas are the "Amiga 2000's" of this time. All that has to be recognized is that they are actually different market segments and can be addressed differently.

With the purchase of Cloanto's Amiga Forever that also includes, legally, the Amiga 4000 Kickstart ROM, the CyberStormPPC ROM, and the Picasso IV ROM. So that gives a completely legal path to AmigaOS 4.1 FE Classic emulation: no shenanigans.

Thank you,
Bill.
You are correct that is how it is currently. That could change in a future update, but no promises.
AmigaOS 4.x Beta Tester - Classic Amiga enthusiast - http://www.hd-zone.com is my Amiga Blog, check it out!
headkase
Posts: 15
Joined: Sat Jun 25, 2016 10:45 pm

Re: Classic Memory Limits in Emulation

Post by headkase »

Thank you DarrenHD, I do hope that the RAM situation can be improved. Napkin math says that if properly advertised and marketed that it could even be a tidy extra profit.

Thanks,
Bill.
Elowan
Posts: 45
Joined: Tue Aug 16, 2016 9:54 pm

Re: Classic Memory Limits in Emulation

Post by Elowan »

Yes, I am totally "in" for that. even if I have to buy another OS4.1FE version "extra for emulation" - I gladly would spend the money and support this!

I also made a topic on that, see: http://forum.hyperion-entertainment.biz ... =14&t=3517

kind regards
headkase
Posts: 15
Joined: Sat Jun 25, 2016 10:45 pm

Re: Classic Memory Limits in Emulation

Post by headkase »

Elowan wrote:Yes, I am totally "in" for that. even if I have to buy another OS4.1FE version "extra for emulation" - I gladly would spend the money and support this!

I also made a topic on that, see: http://forum.hyperion-entertainment.biz ... =14&t=3517

kind regards
Thanks for the link. After having bought 4.1FE I used it for about a week - it was very nice to see what a modern AmigaOS could do - but once the novelty wore off I've used it less since. The main reason for using it less is that I can't run a modern web-browser in the emulated RAM that is left over after the OS claims its chunk. If I could do so then I could very well see myself spending more time in AmigaOS because of the very fond memories I have associated with it.
headkase
Posts: 15
Joined: Sat Jun 25, 2016 10:45 pm

Re: Classic Memory Limits in Emulation

Post by headkase »

Isn't it as simple as poking a magic byte (a value you know) into each increasing megabyte increments and stop adding RAM to the available pool when the corresponding peek didn't match the magic byte?
Post Reply