We are excited to announce the launch of our new forums! You can access it forums.aavso.org. For questions, please see our blog post. The forums at aavso.org/forum have become read-only.
Announcement: New Applications
We are excited to announce the launch of our new applications! We're opening up early access to our new applications for searching, downloading, and submitting photometric observations. You can now access these applications through these links:
We ask for your feedback in order to help us improve these applications. Please send feedback for the applications above to feedback@aavso.org. Note: please avoid duplicating submissions across the two submit applications.
I use AIP4WIN version 1.4.25 for each photometry run to look at my images and use the star image tool, and occasionally, to stack and calibrate images.This runs under my laptop, Windows 10, 64-bit version without any problem.
I'm not familar with COMDLG32.OCX error. A quick Google search suggested that it is a Windows file tht may be corrupted or have difficulty loading rather than with AIP4WIN itself? Best regards.
Contact Wilman Bell. This is a common problem and there is a fix and instructions for it. I had the same issue when I upgraded to Win 10 and after talking to the company and getting the new instructions on loading it I finally got it instaled!
I have read that COMDLG.OCX is a file used by Vusual Basic, and is not a native Windows file. A computer store fixed the problem for me, at a cost, but after a while it recurred. I gave up and stopped using AIP4Win. There are various fixes described, if you go searching. I found them to be difficult to implement. Thanks for the suggestion about contacting Wilman Bell.
Perry Remaklus at W-B has more experience troubleshooting AIP4Win install problems than anyone else in the world, and he will work with you to fix the install. There's an updated install package (updated in 2020) at the Willbell website that does a good job about 95% of the time when the directions are followed.
When Win10 does an update, it sometimes "breaks" legacy software, but the next update corrects it. Also, when you encounter a problem after a Win10 update, reboot the computer. That often allows Win10 to find the "missing" components and the problems go away.
I quit using AIP4WIN for my image calibration because it has not kept up with Win10. I realize that the price point of tiny market software is not worth putting money and/or time into upgrades when Microsoft decides to change the game and I respect that decision. I had the same problem with MPO Canopus. Having followed all the (welcomed) advice on how to make these programs work on my Win10 machine and failing, I arrived at a solution for all older programs that resist my efforts to make them run consistently in Win10. (This includes not only Canopus and AIP4WIN but programs such as the GUI version of Phoebe 0.3a; so there are other fish to fry.)
I had a legacy Win7 Pro computer in the observatory doing nothing, a standby for emergency use. It’s an older dual-core machine, but lots of legacy software was written with these machines in mind. So, I brought it home and installed AIP4WIN and Canopus. Both run fine on it. Although I use AIP4WIN only occasionally, I use MPO Canopus a lot. Works like a charm in Win7Pro. It shares a screen and accessories with my Linux computer. My wife now thinks I am a computer geek, like I actually know what I am doing. In fact, it’s the path of least resistance.
AIP4Win and Canopus were both written using VB6, and share the same problems with Microsoft's support for its older software. Win 10 is not all that bad if you update regularly. If you continue using Win 7, it's a good idea to stay off the wide-open Internet and visit only trust sites as the newer virus can bypass its protections. The cost in time and effort to chase operating systems probably means fewer programs for specialized interests like astronomy and photometry, and lots more "gee-whiz-ware."
Hello! Brian Warner recently sent out an email to users of Canopus who are on the Canopus Group asking for feature suggestions.
It lools like he wants to significantly update the software, both for capabilities and for the operating system.
What sort of problem did you have with Windows 10? It took me a bit to get it working up my system, but most of that ended up me not following the instructions for the Windows 10 installation. Best regards.
Not following the instructions for the Windows 10 installation..
That is the common factor with those having install problems.
There's quite a bit of legacy VB6-based business software still out there. That's probably why MS allows it. But it has to be done exactly the right way. What users don't see is that Win10 is much harder to hack than Win 7 was, and hacker became much more sophisticated. The OCX files are hacker gateways, and that's why they need to be installed correctly..
VB6 was the end of the line for "semi-OOP" VBs. VB.net follwed it, but moving from VB6 to VB.net required rethinking the code at a very basic level.
Thank you Paul, Gordon, Richard for your advice. I hope other AIP/Win10 users will post their experiences with these fixes.
Like Ed, I have AIP4W on a Windows 7 computer (in my home office). I only use that computer for AIP, Guide, and a few other Windows astronomy programs. I use this all the time, and it works just fine. In the observatory I have another Win7 box which controls the mount and the cameras.
I'm with deleemoon. I see no need to go any deeper into the MS House of Pain.
This is a serious problem. I hope someone has a solution.
Has anyone used Virtual Box or Parallels, or something else, to run XP or Win 7 on a Mac and then been able to run AIP4Win on that Mac?
Has anyone tried running AIP4Win using Wine for Mac?
Phil
Hello! Which version of AIP4WIN are you using?
I use AIP4WIN version 1.4.25 for each photometry run to look at my images and use the star image tool, and occasionally, to stack and calibrate images.This runs under my laptop, Windows 10, 64-bit version without any problem.
I'm not familar with COMDLG32.OCX error. A quick Google search suggested that it is a Windows file tht may be corrupted or have difficulty loading rather than with AIP4WIN itself? Best regards.
Mike
Contact Wilman Bell. This is a common problem and there is a fix and instructions for it. I had the same issue when I upgraded to Win 10 and after talking to the company and getting the new instructions on loading it I finally got it instaled!
Paul
I have read that COMDLG.OCX is a file used by Vusual Basic, and is not a native Windows file. A computer store fixed the problem for me, at a cost, but after a while it recurred. I gave up and stopped using AIP4Win. There are various fixes described, if you go searching. I found them to be difficult to implement. Thanks for the suggestion about contacting Wilman Bell.
Roy
I have three fixes. Try this one first -
Right click on the AIP4WiN icon, select Properties
On the Shortcut tab, select the Advanced box
Keep the run in separate memory space box checked
If I check the Run as administer box, the COMCTL32.0CX problem APPEARS
If I remove the check in the Run as administer box, the COMCTL32.0CX problem GOES AWAY
If this doesn't work, let me know and i'll send a more complicated fix I used.
Gordon
Contact Willmann-Bell. Contact Willmann-Bell. Contact Willmann-Bell!
Perry Remaklus at W-B has more experience troubleshooting AIP4Win install problems than anyone else in the world, and he will work with you to fix the install. There's an updated install package (updated in 2020) at the Willbell website that does a good job about 95% of the time when the directions are followed.
When Win10 does an update, it sometimes "breaks" legacy software, but the next update corrects it. Also, when you encounter a problem after a Win10 update, reboot the computer. That often allows Win10 to find the "missing" components and the problems go away.
Richard
Richard I never connect my Win 7 machine to the Internet when I can help it. Your advice should be followed by all.
Re Win 10, I am obviously part of the 5%. Glad to see that others have had more success.
Ed
Thank you! Good to know if I have problems since I use it regularly. Best regards.
Mike
I quit using AIP4WIN for my image calibration because it has not kept up with Win10. I realize that the price point of tiny market software is not worth putting money and/or time into upgrades when Microsoft decides to change the game and I respect that decision. I had the same problem with MPO Canopus. Having followed all the (welcomed) advice on how to make these programs work on my Win10 machine and failing, I arrived at a solution for all older programs that resist my efforts to make them run consistently in Win10. (This includes not only Canopus and AIP4WIN but programs such as the GUI version of Phoebe 0.3a; so there are other fish to fry.)
I had a legacy Win7 Pro computer in the observatory doing nothing, a standby for emergency use. It’s an older dual-core machine, but lots of legacy software was written with these machines in mind. So, I brought it home and installed AIP4WIN and Canopus. Both run fine on it. Although I use AIP4WIN only occasionally, I use MPO Canopus a lot. Works like a charm in Win7Pro. It shares a screen and accessories with my Linux computer. My wife now thinks I am a computer geek, like I actually know what I am doing. In fact, it’s the path of least resistance.
Ed
AIP4Win and Canopus were both written using VB6, and share the same problems with Microsoft's support for its older software. Win 10 is not all that bad if you update regularly. If you continue using Win 7, it's a good idea to stay off the wide-open Internet and visit only trust sites as the newer virus can bypass its protections. The cost in time and effort to chase operating systems probably means fewer programs for specialized interests like astronomy and photometry, and lots more "gee-whiz-ware."
--Richard.
So now I understand why I should give up hope for a Linux port . . .
Hello! Brian Warner recently sent out an email to users of Canopus who are on the Canopus Group asking for feature suggestions.
It lools like he wants to significantly update the software, both for capabilities and for the operating system.
What sort of problem did you have with Windows 10? It took me a bit to get it working up my system, but most of that ended up me not following the instructions for the Windows 10 installation. Best regards.
Mike
That is the common factor with those having install problems.
There's quite a bit of legacy VB6-based business software still out there. That's probably why MS allows it. But it has to be done exactly the right way. What users don't see is that Win10 is much harder to hack than Win 7 was, and hacker became much more sophisticated. The OCX files are hacker gateways, and that's why they need to be installed correctly..
VB6 was the end of the line for "semi-OOP" VBs. VB.net follwed it, but moving from VB6 to VB.net required rethinking the code at a very basic level.
Richard
Best solution is to never upgrade from a fairly good OS to a new bad OS.
Thank you Paul, Gordon, Richard for your advice. I hope other AIP/Win10 users will post their experiences with these fixes.
Like Ed, I have AIP4W on a Windows 7 computer (in my home office). I only use that computer for AIP, Guide, and a few other Windows astronomy programs. I use this all the time, and it works just fine. In the observatory I have another Win7 box which controls the mount and the cameras.
I'm with deleemoon. I see no need to go any deeper into the MS House of Pain.
Phil
Hello!
True! The world ran so much better under Windows XP! Best regards.
Mike