Like many of you, I downloaded and installed the new VFP 9 Service Pack 2 and Sedna betas (available from here). I was careful to first uninstall the previous SP2 and Sedna CTPs, and while SP2 installed just fine, I got error 2869 at the end of the Sedna installation. Because I was busy, I didn't have time to dig in and figure out what caused the error.
Fortunately, I didn't need to. The next day, Rick Bean posted a message on a forum with the same problem, then later posted the solution. Like Rick, I'm using Windows Vista, and it looks like the installer needs admin rights to do its job but it isn't set up to request elevation automatically. So, Rick's solution is to choose Start, All Programs, Accessories, Command Prompt (Rick, if you're reading this, here's a shortcut: click Start and type "cmd"; it'll appear at the top of the search list), then right-click and choose Run as Administrator. Then, using good old-fashioned DOS commands, CD to the directory where the Sedna installer is located, type the installer name, and press Enter. Since it's launched from an elevated process, it also runs as administrator and successfully installs.
I hope everyone gets some time to work with SP2 and Sedna. I haven't gone through all of the Sedna tools yet, but have spent a fair bit of time with the My namespace and Upsizing Wizard (duh {g}), and love the work Craig Boyd has done with the Vista Toolkit. If you come to Southwest Fox or the German DevCon, attend my Developing Visual FoxPro Application for Windows Vista session and I'll show you how cool this toolkit is.
Happy Halloween!
22 hours ago
3 comments:
Yes Doug I'm reading this. Thanks for the mention and the alternative fix. Like most, I find that once I have A solution, I don't go looking for another. Now I've got a better way for the next roadblock that Vista's UAC presents to me.
Rick
How to open an elevated Command Prompt from the folder context menu in Windows Vista
http://www.winhelponline.com/articles/113/1/
Nice! Thanks, Carl.
Post a Comment