WHDLoad Installation Problem

[Lockon_15]

No.
A bare 68000 is enough for installation and running at least 50% of all slaves, only if you have enough RAM (1Mb CHIP and 2Mb Fast is a working config for A500). That's a functional setup, not an ideal.
68020 would make system more responsive in terms of overall speed and it would allow all WHDLOAD games to support quiting back to OS.
 
Can you quote error message ?

[Lockon_15]

You have wrong version of Installer (compiled for 68020).
Get this one:
 
http://aminet.net/util/misc/Installer-43_3.lha

[Lockon_15]

Yes, you could.
Some WHDLOAD installs are compiled to run at 020 as minimum, some require rare 010 for so called VBR support which you cannot get on plain 68000.
I have found at least 2 games from my personal interest (Amiga Karate, F/A-18 Interceptor) which failed to run on configuration similar of your own. The issue was resolved as slave/install author was kind enough to re-compile stuff compatible for 68000. However, I find that a rather exceptional case, not a common among a niche of WHDLOAD slave/install authors.
 
At the end, at least you got one more reason to start over getting A500 accelerator.
Or switch to A1200 which is, hands down, a WHDLOAD gaming champ, right from bootstart.

[Lockon_15]

Yes, but honestly I don't see you doing that alone.
That's way over your league (me included!) and your best bet would be to contact author if he can reconsider recompile for 68000.

[Lockon_15]

I do really admire your determination, even if it's bound to fade abrupty when you actually realize what WHDLOAD slave writing is all about.
 
Back to the topic, WHDLOAD does need some extra system resources since it's a OS wrapper. Games run on same hardware would suffer some speed loss, but I guess on plain A500 things are slow as default and thus little affected.
 
WHDLOAD tries to allow/recreate same or near same experience (with respect to original), but that's only an attempt being constantly improved from each new release. There are known limits (it won't work under Kick<2.0), and know issues (68040 is a bad WHDLOAD host choice, many games need additional tweaking).
In fact, I'm aware for few games which are too fast on my 030, but that can be handle by smart slave option set.

[Lockon_15]

I might been a bit over the line.
Sorry for that.
 
Extracting file "Installer" from archive into "C" drawer would be enough.

[Lockon_15]

"Install" found in C: is part of Workbench command set. It's used to write bootblock, something not even remotely connected to your issue. Forget about it.
 
Let's see if you have stuff set right at proper palces.
You should open shell and type Installer. If set correctly, you should get something like:
 
Installer 43.3 (30.4.96)
 
USAGE: Installer ...
 
Any other message, like "Installer: Unknown command" would mean Installer is not in path accessible to shell and thus to ToolTypes, too.

[Lockon_15]

Workbench attempts to search at locations defined through PATH command. PATH is invoked inside S:startup-sequence file.