Installation Problem

Media · Post by **Media** » Tue Mar 02, 2004 11:39 am

When installing Macro Scheduler Pro, the user is presented with the options to create a desktop shortcut for the control center, another for the script editor, and a shortcut in the startup folder so that Macro Scheduler will run when Windows starts. The installer does not create these shortcuts on my system during the installation. I thought that I would try to uninstall and then reinstall to see if it would happen again. During uninstallation of the program, I get an error that reads MSG_ERR_REMOVE_SHORTCUT (#1, Line 6). When I reinstalled, the shortcuts were still not created. I also tried redownloading...the fresh download didn't help. This happens on both of my systems. (I only run it on one because I only have one license, but for testing purposes I thought I would try the install on a different system.) The behavior was identical on each of my systems. Both systems were clean platforms that never had MSched installed on them before. One is Windows 2000 and the other is XP. Both are very new and well maintained. 2.4 ghz 512mb ram...They never give me any type of trouble.

This is not very major, it seems that the program runs well, and these shortcuts are easy enough to create by hand. I just thought I would post and see if I am the only one who is experiencing this behavior.

Media · Post by **Media** » Tue Mar 02, 2004 2:04 pm

Ok, I worked on this a bit more and I also noticed that the extensions were not being associated either. The extensions .scp, .macro, and .mch were all unassociated. I started to dig through my old Macro Scheduler releases and I found that version 7.1.17 works the way that it is supposed to. The installer for version 7.1.17 creates the appropriate shortcuts and it also adds the three above mentioned extension associations. So somewhere in between version 7.1.17 and the current release, the software installer was broken by the developers. This should not be too hard to fix. I installed 7.1.17 first, rebooted, and then installed the current release over the top; all is well now.

Cheers hope this helps someone out there...