InstallAware

Hi
I have been using an installation script under test for about 20+ download tests to ensure that it could handle all of the currently conceivable user machine configurations we could think of - it was working perfectly.
Given one particular rebuild, no great changes made, just a mod to a 'Call DLL' to rename (MoveFileA) a folder in the prerequisites section of the script. Then the update script no longer worked. Reverting to the original code did not reinstate it.
By did not work I mean, the update script no longer places the IA icon in the system tray for the user to schedule updates. I have not modified updates.mia in any way. What I now get for this installation is a Windows Explorer window opening, after a reboot, at the folder location of C:\\Documents & Settings\\All Users\\Application Data\\{GUID of this revision}\\App Name. This contains a sub folder with the App executable in it and one other file named {GUID of this revision} with a size of 0 bytes.
No scheduled update functionality at all but the link I put on the start menu for a manual update check works fine !
To try and resolve this I have :
1. Removed the updates script from the project, rebuilt, then reinstated updates.mia and rebuilt - no change.
2. Deleted all updates files from project folder eg. .mia, .mia.bak, .brk and rebuilt - no joy.
3. Tried installing on 3 different machines, same behaviour on all.
4. Tried both local installs as well as remote server installs - no fix.

Even a very basic install of the app, which uses none of the prerequisite jiggerypokery I referred to earlier, will setup scheduled updates.

Please can anybody suggest what has happened to the scheduled update functionality and what more I can do to fix it.

Currently using v 6.23 Build Santacruz_sp3 020107

thanks and best wishes

Pete B.

Further to the above ...
I wrote a very simple, web based, test install script and it works fine - the scheduled updates service is there. I was suspecting that I had corrupted my installation of IA but it seems not.
I guess now that the emphasis must be along the lines that my original script has become corrupted in some way and I suspect will have to be rewritten as a new project. Oh well ...

If anyone else has a better idea, yes please ...

Pete B.

Episode 3 : Space, the final frontier or in this case a pain in the ...

Completely rewrote the script that wouldn't schedule updates, convinced it was corrupt. Took several hours and guess what, it still didn't work. Spent a lot more time searching for the possible differences between this script and the little test script I mentioned above. I finally found one thing that was different.

The name of the installer file for the non scheduling script had a space in it, the working one did not. Remove the space from the installer name and hey presto, script returns to being fully functional with regard to scheduling updates. So, NO spaces in installer file names seems to be the order of the day.
If this is written anywhere in the help files or elsewhere in this forum, then I apologise for missing it but I hope this post will serve to save anyone else who confronts this issue a bit of time.

Life is now good

best wishes

Pete B.