Trouble Installing WHDLoad 17

[rossb]

Hi All,

Firstly apologies if this is a silly question but I am pulling my hair out!

I am currently running WHDLoad 16.9 (Registered) and wanted to have a play with version 17.0

I have downloaded whd170.lha (31/12/2010) and extracted the lha file, I see the Install script and have used protect +se to set execute and script, but whenever I try and run it it moans about:
(procedure: Unknown command

Almost as though I have no Installer installed. It seems that the installer is different from 16.9? 16.9 installs with no problem.

Am I missing something obvious?

Any help would be much apprecited.

Regards,

Ross.

[TCD]

If you have 16.9 running, why don't you just update the WHDLoad file in 'C' ? I mean your system's c folder of course. Will have a look if I get the same error later at home.

[rossb]

Originally Posted by TheCyberDruid

If you have 16.9 running, why don't you just update the WHDLoad file in 'C' ? I mean your system's c folder of course. Will have a look if I get the same error later at home.

Hi TCD,

Thanks for the quick response, and that's a good point, I didn't know if there were other dependencies that were installed as part of the 17.0 install.

Regards,

Ross.

[TCD]

I just updated the WHDLoad file itself and it worked fine so far. Wonder what the problem with the install script is, so if you can hold back until tonight, you might not have to install it manually

[rossb]

Originally Posted by TheCyberDruid

I just updated the WHDLoad file itself and it worked fine so far. Wonder what the problem with the install script is, so if you can hold back until tonight, you might not have to install it manually

That's good news, thank you, I will hold off for the time being. Appreciate your help!

Regards,

Ross.

[desiv]

Originally Posted by TheCyberDruid

Wonder what the problem with the install script is,

I had that happen as well...
It's been a week, so my memory is foggy (OK, if it was yesterday, I wouldn't remember :-), but I think the Install script wasn't pointing at the Install app in the tool type.
I seem to remember I just pointed it at the Installer and then it worked...
Not sure why it would be hit/miss tho.. That's weird..

I thought about just copying the executable also, but wasn't sure about dependencies either..

desiv