[Power Hungry]

Hey all,

It has come to my attention that a few people have been having problems updating not only their Gryphon, but the Pegasus software as well. Here's what's going on...

As of 05/18/2009, we have restructured the software's communications handler and have replaced the FTP communications protocols with HTTP. This should eliminate the connection problems many people were having due to firewall and anti-virus issues blocking the connection to the server.

We had to set up a new section on the server to handle the new communications structure and because of this, all previous versions of Pegasus will no longer be able to retrieve custom files. You must update to the new version of Pegasus in order to get your custom files.

This brings us to our second problem...

There is a problem with older versions of the Pegasus software that occasionally doesn't allow it to shut down properly after it downloads the updates. This is a problem with the communications handler itself, although this is resolved in the latest version of Pegasus. This issue prevents the external update application from working properly since the Pegasus application isn't shutting down properly and Windows can't update a file if it is open or active.

The solution is pretty simple. Since the downloads should already be on your computer, we just need to manually run the Update application. Please use the following procedure to manually update Pegasus.

• Go to the [Start] menu and then click [Run]. (Alternately, you can press the [Window] key in the lower left corner of the keyboard and the press the [R] key. This will also open a "Run" dialog window.)
• In the "Open" box, copy and past the following (including the quotation marks): "C:Program FilesPHPPegasusUpdate.exe"
• Click [Ok] and the update application will apply all the updates currently found in the Pegasus folder.

Next time you run Pegasus, the application should show version v2.01.0532 (or later) and you should now be able to download Custom files, Updates, and everything else.

Just to let everyone know, with the restructure of the Pegasus communications we now have the capability of adding new features to Pegasus. Some of the features on the drawing board are:

• Automatic notification of Pegasus Software updates.
• Automatic notification of Calibration and Firmware updates.
• The capability to check Custom files status without having to remove the unit from the vehicle.
• The capability for users to be able to change the individual files in the Gryphon without having to go through full rebuilds on our end.
• Storage of your vehicle's stock information on our server.

We hope these new features will improve the quality of our customer's experience. If anyone has any suggestions for features to add to the Pegasus software, we would certainly be happy to consider them for inclusion.

Take care.

[JackandJanet]

These are great additions to Pegasus, Bill! Should make things easier for everyone.

Is it too much work right now to update the Pegasus download on PHP's download page to version 2.01.0532? I think some people are confused about having to "update" something they just downloaded. I know you have to rebuild the installer, but it might take care of a few problems.

- Jack

[Power Hungry]

The only reason I haven't done it yet is because my InstallShield builder is on another machine that is off-network. It is a bit of a pain to get everything copied over to the machine to run the builder and then copy everything back so I try to avoid it if at all possible.

We'll have this all straightened out the next day or two and rebuild it so it won't be an issue.

Take care.

[JackandJanet]

Originally Posted by Power Hungry

The only reason I haven't done it yet is because my InstallShield builder is on another machine that is off-network. It is a bit of a pain to get everything copied over to the machine to run the builder and then copy everything back so I try to avoid it if at all possible.

We'll have this all straightened out the next day or two and rebuild it so it won't be an issue.

Take care.

Makes sense. And, InstallShield is SUCH fun, isn't it? To be fair, I've tried several different install programs, and I think they're all pretty "hit and miss".

- Jack

[Afrancis]

When I try to update pegasus, I get the following message. Component 'MSCOMM32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid. Ive tried uninstalling pegasus and reinstalling, but I still get same message. Any ideas?

[Power Hungry]

I'm not sure what the deal is with MSCOMM32.OCX but I had another person recently indicate they had a problem as well. As near as I can figure, InstallShield is not correctly registering that component although I'm not really sure why.

I expect to have a fresh install package on Tuesday and I will make sure that we address that issue in the build.

In the mean time, we had added an install package on the website a few weeks back that is a temporary fix for this. You can find it on the Downloads page of the Power Hungry Website. Here is the link:

http://dygytalworld.ehost-services13...32_install.exe

This should get you up and running.

Take care.

[Afrancis]

Thx Bill

[PhqChevys]

Originally Posted by Afrancis

When I try to update pegasus, I get the following message. Component 'MSCOMM32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid. Ive tried uninstalling pegasus and reinstalling, but I still get same message. Any ideas?

I'm getting the same problem Bill. I have Pegasus v2.01.0575 on Vista HP 64-bit. Pegasus wont let me do anything with the Gryphone, and it wont update itself with the Pegasus Update Manager. What can I do?

[Power Hungry]

Tom,

Unfortunately, still can't speak intelligently about V64 since we don't have a platform here that runs it. Up until now, the biggest issue had been the USB driver which the manufacturer seems to have resolved.

As for the MSCOMM32 thing, I've found that there seems to be some further issues with Vista locking certain files/folder based on user permissions and whether or not the UAC is on or off. I'm still trying to get those issues resolved, but since Microsoft doesn't really seem to care about anything written for the 32 bit platforms it's really down to just hammering things out and hunting solutions down on the internet.

One thing we've been able to include this weekend is the ability to do live, remote support (basically a remote desktop) to help diagnose and resolve these type of issues. Again, will it work on Vista 64? If you're willing to give this a shot, let me know and we can give it a try.

Take care.