HALLELUJIA!!! A BREAKTHROUGH!! After months of work, I finally have Studio4.5.1 NEARLY working fully. It took a lot of painstaking mouseclicks to make it work, but it's working, sort of. Since I know there are lots of others having problems with Studio4.5.1, I'll spell out what I had to do: (1) Backup my customisation files for Studio - Snippets, toolbar settings, spellcheckers wizards etc. (There's an article on allaire's site at article 1448 about backing up for Studio 3 but it seems to apply) (2) Delete Studio4.0.1, Studio4.5.1, Homesite, CFServer (I don't think server had to be deleted but I wanted to be certain) using the control panel Add/Delete programs. (3) Use Regedit to remove all references to Allaire. (Open the folders in the registry: HKEY_CURRENT_USER, Software, Allaire, then delete the Allaire folder. If you don't want to delete your server, open the Allaire folder and delete the others) (4) Delete the Studio folders, Homesite folders. Empty the recycle bin so there's no chance the installation routines can find the files that might be inside. (5) In C:\Windows\System, move the following files to floppy and delete them from the C:\drive: cfvalidator.dll CFSourceControl.ocx cfproject.dll CFSDebug.dll cfssvradmin.dll CFFtp.dll CFFPTree.dll CFFileProxy.dll CFFileProxy.ocx CFFtp30.ocx CFRds.dll CFRegExp.dll CFRemoting.ocx cfping.dll cfrpchttp.dll Now I was reasonably sure there was no trace of previous or incompatible versions of anything. (6) Restart the PC (7) Use Ctrl-Alt-Delete to open the task manager and shut down every program, TSR, utility except Explorer and Systray. EVERYTHING else shut down. (8) Double click the Studio4.5.1 update executable, and let it take its defaults. (9) After it installs, reboot the PC WARNING WILL ROBINSON WARNING WARNING! ERROR MESSAGE at this point - the Installation Executable has an invalid DLL in it so the installation program bombs at REGSVR32 as it's closing down. CFMLVALIDATOR.DLL is cactus and will kill the reboot. (10) When the PC is eventually restarted, remove CFMLValidator.dll from the main Studio folder, and ensure there is another CFValidator.dll (note the different file name!) is in C:\Windows\System. Since you've just changed a DLL, the PC has to be rebooted a second time. Believe it or not, after all this carry-on, Studio will now start and will connect to my remote server, and I can look at my remote SQLServer7 databases. CAUTION: I haven't tried uploading a project yet, but I already know that the feature where it only uploads the changed files DOES NOT work - its a bug, so you have to upload the whole project every time. (Sigh) So there you have it. A more-or-less working Studio4.5.1. The installation executable contains invalid DLLs, it won't install if there's any sign of a previous or related product on the PC, and even if you manage to obliterate all previous versions, it still won't be fully functional. But it's a lot better than I've had up to now. Allaire's support department can hang their head in shame over this. It's taken more than 2 months and in the end it was mostly my own work and the local distributor Firmware Design who did the work. They got damn-near nothing useful from Allaire. It was Firmware's worrying away at this problem that fixed it, not Allaire's slack, lazy, one-sentence-a-day-and-see-if-that-shuts-him-up approach to solving the problem. And even now it's not solved, only less urgent. I still want to see a proper, valid installation routine that doesnt require major manual work before it will install. I still want to see a Studio that is fully functional. As in, the deployment works. I still want to see an installation file that doesnt have invalid DLLs in it. I still want to have a Studio that will work no matter what other programs are on the system. It's absurd that it won't install properly if a previous version is there or if Homesite is there. We were all quite rightly critical of Microsoft when IE4 wouldn't co-exist with previous versions of IE. I want to be able to support my clients whether they have the new semi-working version 4.5.1 or the old working 4.0.1 and have them both on my system so I can support my clients. But I thought you'd all like to know I'm actually getting somewhere Cheers, Mike Kear AFP Web Development Webmaster, Australian Consumers Association Windsor, NSW, Australia http://www.choice.com.au http://www.afp.zip.com.au ------------------------------------------------------------------------------ Archives: http://www.eGroups.com/list/cf-talk To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
