On 07/04/2007 09:52 PM, Stephan G wrote: > OK Gary, you rock. > > First off, I was able, finally, to successfully install 2.2.1. > > Not sure if a bug report would still be appreciated, let me know. > > Here is a summary and details of what happened. For those who have > followed this thread in detail, you can skip down to step 6. > > 1. In a completely casual way, I downloaded OO 2.2.1 (w/ JRE) and > attempted to install. > > 2. After it had unpacked all the files and started the installation > routines, after indeed I had "Accepted" the license, Windows Installer > terminated and I received an error message saying the DEP had been > invoked, and the installer was being terminated. > > 3. At suggestions in this thread, I turned off DEP. To do this, I > followed the instructions at > http://vista.beyondthemanual.com/2006/11/vista_tip_turn_off_data_execut.html > and in an elevated command window, executed the command: > > bcdedit /set {current} nx AlwaysOff > > 4. I rebooted. > > 5. I re-attempted to install OO 2.2.1, and was halted at the same > point. The error message just said something general about Windows > Installer closing, rather than saying anything about DEP. > > 6. At the suggestion of this thread, I downloaded the md5sum.exe > utility, and checked the checksum of the executable I had downloaded > against the published executable. They were identical, so corruption > was unlikely. > > 7. At the suggestion of this thread, I downloaded ccleaner and ran it. > > 8. At the suggestion of this thread, I disconnected from the internet > and turned off my anti-virus (avast!). DEP was already off. I > attempted to install, and the installation was successful. > > 9. I turned the anti-virus back on, and reconnected to the internet. > > 10. At the advice of the web page listed in step 3 above, I executed > the following command to re-start DEP: > > bcdedit /set {current} nx AlwaysOn > > 11. I rebooted. > > 12. All hell broke loose. Everything was being halted for DEP > violations, any program I tried to run, and several programs that are > part of my boot sequence. > > 13. I turned DEP back off with: > > bcdedit /set {current} nx AlwaysOff > > 14. After some rather extensive research on the Microsoft website (and > I don't know why they made this so hard) I discovered that the Beyond > the Manual folks were incorrect. To turn DEP back on in a way that > makes sense for a home user, this is the correct command: > > bcdedit /set {current} nx OptOut > > 15. After this, I rebooted and all seems fine. > > I regret that I didn't isolate whether the problem was corrected by > running ccleaner or by turning off the anti-virus. I now believe that > DEP was not at fault. > > I am also still a bit non-plussed that only OO, and only version 2.2.1 > at that, have had installation problems on this machine. With advice > and encouragement of folks who know more than I, I would be happy to > file a bug report with my experience. > > Thanks again. > > -stephan >
Nah... you rock for trying all of that and getting it to work and figuring out the proper way to turn DEP back on!-) Filing a bug without being able to determine if it was: a) antivirus, b: corrupt registry etc, or c: DEP probably won't go anywhere. However, your steps to fix will certainly be archived here and be most helpful for others that experience the same problem. Nice work & thanks again for coming back and explaining what steps you took to get it up and running! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
