WHDLoad Installation Problem

[Lockon_15]

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

[sim085]

I might been a bit over the line.
Sorry for that.

Not at all I know this stuff is very hard. I really admire the people that actually managed to first understand and then make all this stuff work
 

Extracting file "Installer" from archive into "C" drawer would be enough.

Thank you for that, you can see what a big newb I am from the questions I ask but I keep notes, and therefore I learn!

[sim085]

Extracting file "Installer" from archive into "C" drawer would be enough.

I did this, however it still gives me the same error. Also I noticed that in C I have another file called install. However I went on the Install icon and went to Tools > Information and here it says that the Default Tool is Installer.

However as I said I still have the same problem!

[sim085]

Hi,

sorry to bring this up again, but cannot manage to understand how to make the installer of WHDLoad use the installer tool I moved in C:

Also when I moved the installer tool there was no previous installer tool in C: there was only an install tool. However the Default Tool for the WHDLoad installer is equal to "Installer" but do not know what this means!

[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.

[sim085]

Installer 43.3 (30.4.96)

Yes I do get this result from shell. However when I double click on the install icon of WHDLoad I still get the same error as before:

Installer
Program failed (error #80000003)
Wait for disk activity to finish.

Do I need to start the installer of WHDLoad from shell?

[save2600]

Install and Installer are two separate programs. Be sure you have both since some
programs call on one or the other. AND...

Check to be sure the protection bits are set right. When downloading things from the net,
often these get messed up. In other words, make sure the important and obvious
files (like WHDLoad itself) you are playing around with are all "executable". When
doing an 'info' on the file, be sure that option is checked.

Not sure why else you are having all this trouble installing a simple program.

Should just be able to throw that program into 'C', place your key in 'S' (yes, you
should register this) and be done with it. Maybe an assign in user-startup pointing
to WHDLoad, but come to think of it, not even sure that's necessary. Good luck!

[sim085]

Not sure why else you are having all this trouble installing a simple program.

I think the problem is related with the WHDLoad installer (which fails to install under a 68000 processor but works fine on a 68020 processor).

I say this because the sample script works fine when I put the installer under Sys:C which means that this is installer works fine (with out the installer under Sys:C this would give an error)

I think I need to modify something in the WHDLoad installer! Is this possible? Maybe it is not using the new installer I just placed in Sys:C

[Marcb]

I think that because you are using Winuae, it'll more likely be a Winuae config issue, try 68000 with an older kickstart image and see what happens..

[sim085]

I think that because you are using Winuae, it'll more likely be a Winuae config issue, try 68000 with an older kickstart image and see what happens..

I can not do that because I am using Workbench 3.1. Doesn't workbench 3.1 need at least Kickstart 3.1?

[sim085]

I was also thinking the following ...

I did not have any Installer tool before putting the downloaded one under Sys:C (I mentioned this in some post about).

So how come the Installer tool refered to by the WHDLoad install script has worked fine under the 68020 processor? shouldn't have it also failed because there was no Installer tool under Sys:C?

Not that my Workbench 3.1 is a fresh installation and did not havbe the installer tool under Sys:C. Is this normal? If yes, then where is the default installer tool of Workbench 3.1 located?

[Matt_H]

SYS:Utilities is another common place for Installer.

[BooBoo1200]

Just copy WHDload to your C folder manually.

[sim085]

Just copy WHDload to your C folder manually.

Ok, I managed to make the installer work. There was another 'Installer' tool in the directory of WHDLoad and it seems the latter used this one rather then the one in System:C! I removed the installer tool inside the WHDLoad and its installer started using the one in System:C.

SYS:Utilities is another common place for Installer.

Thanks, it seems that workbench finds the installer tool regardlessly if it is in System:C or System:Utilities! How does Workbench work in this regard? What does workbench do to find a tool such as installer?

[Lockon_15]

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

[sim085]

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

Thank you very much I understand now. This is very interesting stuff ... I am looking forward to learn more on Workbench