KGLoad Requirements

[killergorilla]

Just a general opinion poll really.

(Ignoring any future OCS/Low-Mem versions)

KGLoad is currently an AGA frontend, primarily made for use with WHDLoad games.

It has a gamescanner which will build a custom database with all the games you have installed in your games directories.

I'm currently debating features and am tying up some stuff that will affect how I progress forward, and a few key decisions have to be made on RAM usage vs speed and functionality.

So, if you do plan on using KGLoad, even once or twice, please let me know how much RAM you have.

Or if you intend to use it in the future, on a system you are looking to buy, list the RAM it'll have.

And if you intend to use it in WinUAE, then put whatever your intended virtual Amiga would have

[Bloodwych]

I think you should aim at a 2MB CHIP 4MB FAST Amiga configuration.

The A1200 can accept 4MB FAST without affecting the PCMCIA port, so it seems like a good config to aim at. Plus some expansions for the A1200 came with 4MB FAST soldered onto the board.

In my opinion KGLoad shouldn't aim at using anymore than 2MB for its features - the lower the better. On a 6MB machine, that leaves 4MB for WHDLoad games if run from a boot menu and about 3MB if run from an expanded Workbench.

If too limiting, then the next step is obviously a 10MB Amiga - an A1200 with 8MB FAST. A launcher shouldn't eat too many resources however and I'd look at iGame to see what it uses and not go too far above its limit. Hopefully KGLoad can be a lighter launcher than iGame.

You can always allow people to enable memory intensive features via tool types or release a few different versions.

[TCD]

*WinUAE for me

Originally Posted by Bloodwych

On a 6MB machine, that leaves 4MB for WHDLoad games if run from a boot menu and about 3MB if run from an expanded Workbench.

You will be surprised how much RAM KGLoad uses after WHDLoad is launched

[killergorilla]

Originally Posted by Bloodwych

I think you should aim at a 2MB CHIP 4MB FAST Amiga configuration.

The A1200 can accept 4MB FAST without affecting the PCMCIA port, so it seems like a good config to aim at. Plus some expansions for the A1200 came with 4MB FAST soldered onto the board.

In my opinion KGLoad shouldn't aim at using anymore than 2MB for its features - the lower the better. On a 6MB machine, that leaves 4MB for WHDLoad games if run from a boot menu and about 3MB if run from an expanded Workbench.

If too limiting, then the next step is obviously a 10MB Amiga - an A1200 with 8MB FAST. A launcher shouldn't eat too many resources however and I'd look at iGame to see what it uses and not go too far above its limit. Hopefully KGLoad can be a lighter launcher than iGame.

You can always allow people to enable memory intensive features via tool types or release a few different versions.

KGLoad uses about 1kb after it launches a WHDLoad game

[seuden]

I would have 8MB fast and 2MB chip ram for my KGLoad machine but as Bloodwych has stated 4MB fast and 2MB chip is probably gonna appeal to a LOT more users.

[Bloodwych]

Originally Posted by TheCyberDruid

*WinUAE for me



You will be surprised how much RAM KGLoad uses after WHDLoad is launched

Oh right, I take it it quits and remembers its settings, then relaunches after the game exits? I still think a 6MB Amiga is a nice config to aim at.

[Bloodwych]

Originally Posted by killergorilla

KGLoad uses about 1kb after it launches a WHDLoad game

This makes me do a happy dance!

[TCD]

It's mainly about the time certain things in KGLoad will take to be performed. The minimum amount of RAM will be quite low

[Bloodwych]

Originally Posted by TheCyberDruid

It's mainly about the time certain things in KGLoad will take to be performed. The minimum amount of RAM will be quite low

This makes me do a second happy dance!

[Graham Humphrey]

My A1200 that I would use it on has 32MB Fast RAM... is this too low?

[TCD]

It will barely run, but don't take my word for that

[Calgor]

I have a lot more than 8MB and would like it to use some more memory if it makes it faster. But I agree with Bloodwych's comments overall.

Maybe have a config with 2mb chip / 4mb fast as default (to get as many ppl as can use it - which I suppose what your poll is to gather info for) as well as 2MB chip only (maybe this can be default instead) and also using tooltypes or options you can set it to use more or even exactly however much more you want.

But don't know how hard it is for you to cater for more than 1 minimum memory configuration.

[Anemos]

Whdload & a lot of memory is good..
i have buy 2 accelerators, Apollo with 32MB and Blizz 64mb only for Whdload ,and KG packet ,the best think! so why not to spend some money for yourself?
Buy memory, this would faster and easier his work so bravely KG.

[TCD]

No panic and no 'buy more RAM!' advice please

[killergorilla]

Send the money you would have spent on RAM to me!

[TCD]

Yes, yes send all your money to KG

[Anemos]

Make donation account first!

[meega]

Originally Posted by Anemos

Make donation account first!

Direct bank transfer not good enough for you?

[killergorilla]

Cheers for the info guys...

Ironically, in receiving this info and discussing it with TCD, we've got the RAM usage down to much lower than we had previously.

So hoorah for that.

I've not looked into how much RAM it is actually using but if it doesn't run on a plain CD32 I will be very surprised.

[pbareges]

cool to hear you're progressing on this great promising tool!
i have a little question for you : i'm currently using toolmanager as a launch tool on my wb...i spent a lot of time in configuring the toolmanager exec objects (which points to the game folder, record exec filename, tooltypes, exec types -ie wb, cli, shell...) which are mostly but non only whd/jst games... i know you intend to make your tool a whd launcher, but as you said it would be customizable, i wonder if we could consider any batch conversion of toolmanager exec database to make it fits your tool ?
Once again good luck with your project and thanks for your dedication to this community!