Here is what comes up after 4 seconds of trying to open the program.
InDesign.exe had encountered a problem and needs to close.
App Name: indesign.exe
Mod Name: Ntdll.dll
I thought you might want or need this information.
Thanks again for you help.
If removing the recovery folder didn't work, I suspect you're going to need to remove the existing installation and reinstall (is this on a server, or local?). You'll probably need to run both the CS3 clean script and the Microsoft msicuu2 cleanup utility before reinstalling. That .dll, by the way, seems to be a Windows component, though from what I gather through Google it is a common source of trouble with calls from other software.
InDesign is installed on the workstation not the server. I did not have the beta versions of InDesign and had it for a couple of years with out a problem. I have not used the utilities you suggested and just read a little about them and sounds like it could effect some other programs. Do you suggest that I just try the uninstall and reinstall first or run the CS3 clean script and the Microsoft msicuu2 cleanup utility?
Thanks for your input.
Installing CS3 was a pain, and the installer is very sensitive to conflict with just about everything under the sun, so you need to run it in a bare-bones boot (but not safe mode). I turn off ALL non essential programs and services using MSConfig when doing a CS3 install.
That said, yes, running the CS3 clean script will probably remove all things Adobe from the system. The Microsoft utility is much more benign than the description makes it sound -- it removes registry information for previous installations so there is no trace of them to confuse the OS. I'm not aware that it has removed anything other than what it was told to remove, but I've only had to use it once, I think.
You can try a simple uninstall/reinstall first (and you should be able to remove and reinstall just ID from the suite if you use the original disks). That will certainly be faster and less painful than the clean script, but may not work. Seems odd that a serrver crash should have corrupted a local installation, though, so you might want to take a close look at the machine for other problems, perhaps some sort of malware invasion.
Maybe try pulling the network cable then start up ID first? Then it would eliminate the chance its reading something off the netowrk on startup...
Per you suggestion I went for a manual virus scan and noticed that my Norton was only up a 8/30/2009 Virus definition file, once updated to 9-24-09 and ran a manual scan I found: W32.Netsky.P@mm!enc, adware.gen, Trojan.zlob. This allowed me to run a restore point but then had to update and check for virus again and tried to run Adobe InDesign again with the same failure at start up.
I am now trying to remove InDesign and reinstall to see if that works.
I pulled the network cable and tried to start up InDesign still it crashed. Thanks for the idea.
In my experience running a system resore on an infected machine will not clean out the infection. You need to use whatever tools are available to kill it, then purge the restore data which is usually also infected, and set a new restore point for going forward.
I had exactly the same thing happen...all of a sudden. Guess what. After spending HOURS and HOURS trying all the suggestions from this
posting, i did a properties of the InDCS3 icon on my desktop and noticed that under Compatibility, the Windows 95 was selected. Unchecked it and WHAM, fixed. What would have caused this to be checked on it's own.
KEN PANTHEN, Albany, NY