SoFo HELP? Crash on reinstall V4 on XP Pro

AFSDMS wrote on 7/20/2003, 4:46 PM
I searched for this problem, but it seems it hasn't been resolved in the three months since I last experienced it.

I upgraded the C: drive to a from a 120 to a 120, but the newer drive has 8 MB cache. Of course this trashed all the registrations for SF (Sound Forge, Vegas 4, MPEG plug-ins, etc.)

OS is Windows XP Pro SP-1. D: drive is a 200 GB and machine is a Dell 4550 2.4GHz.

I began by using Add/Remove to remove all SF apps. ALL SF APPS. I had learned before that doing a reinstall over the top didn't work. (Seemed like it used to, but whatever. . .) First I installed Vegas 4 from the CD, got the new Machine ID and got the new registration code via the web.

Finish the registration in the application and when Vegas tries to start I get a fatal error or whatever that error is that wants to go to Microsoft. (So I can get a reply sometime in the year 2032 :-) The application will not run. Here is some of the info from the dialog:

AppName: vegas40.exe AppVer: 4.0.0.119 ModName: mcplug.dll
ModVer: 1.0.0.684 Offset: 0008455a

Last time this happened was before I upgraded to the new machine. This is not hardware specific, but may only be an XP Pro issue. What I ended up doing that time was uninstalling every SF application (still wasn't enough) then I went to the Registry (don't like doing this blindly, but what's a person to do) and removing all entries I could find associated with SF. I also cleared all the folders under Programs for either Sonic Foundry or Sonic Foundry Setup. The latter seems to be created when I install a patch, such as for Vegas 4.0c.

After I did that the applications installed fine, giving me the same machine code as before the house-cleaning, and the applications registered and ran normally.

Is there anything simpler that someone can suggest that will make this work? Might be just one thing in the registry?

Any help greatly appreciated!

Comments

AFSDMS wrote on 7/21/2003, 8:19 AM
I did try nuking all the SF related folders in WinXP Pro after the uninstalls. Did a reinstall of V4 and it still doesn't work. (I am running with Admin authority BTW.) So, it looks like there is something hanging around in the Registry that is mucking things up.

Any help greatly appreciated.

Wayne
AFSDMS wrote on 7/22/2003, 8:23 AM
Knock-knock anyone home???
mikkie wrote on 7/22/2003, 9:31 AM
"I upgraded the C: drive to a from a 120 to a 120, but the newer drive has 8 MB cache. Of course this trashed all the registrations for SF (Sound Forge, Vegas 4, MPEG plug-ins, etc.)"

If you've still got the old drive, use Ghost to copy from one to the other and shouldn't have any problems. Ghost: a command line prog sold by Norton/Symantic now days, you'd use it either to clone one drive to the other if both plugged in, or it can write to sequential CDR/CDRW, then read them onto new drive.

If not, if the old drive's unavailable or has been formatted etc...

"mcplug.dll" is a mainconcept plugin. There have been some issues with these [see the FAQ at http://www.nwlink.com/~zachd/]

Might work to install in Safe Mode.

It *might* help to rename, relocate, or otherwise uninstall other mpg1/2 codecs, even if temporarily, untill you get the install to work. A coupl of prog. named Gspot and DXman might help [http://www.headbands.com/gspot/ & http://www.analogx.com/contents/news.htm]

Either will tell you what's installed, & the files used - DXman will unregister them if you want. Optionally, sort of a worst case IMO, HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\ is the reg key where the codecs to use are set. Back up first, set a restore point, then alter or eliminate whichever subkeys.
AFSDMS wrote on 7/22/2003, 2:56 PM
Thanks for the suggestions. When I migrated to the new drive I used Casper XP a very nice program that I've heard is better than even Ghost. (Like the little ripoff on the name?)

It was after the clone that all the SF stuff was hosed. Always happens. SF creates a new Machine ID and they once told me part of it was a hashing algorithm that included some sort of drive signature. I can see why they do it, but it is a real pain as I upgrade to the added disk storage I need.

If SF doesn't have an idea I may just go back to the full uninstall and the nuking of the folders and Registry keys :-(

Thanks much for the help and sharing!