Yes.. thanks guys for all your suggestions. Truth be known though.. I already covered most of the suggestions but I'm beginning to see the picture now as to what's happening because of them.
husker..
My AV is Kaspersky and although it's good at not spewing out false positives.. I DID disable it anyway during install.. and even play.. because it takes forever to scan that huge install executable before it lets it run and I just couldn't have that. I thought possibly letting Crossfire sit too long before it gets ''permission'' from Kaspersky.. may be mucking it up some, so I can say my AV is not involved.
I think I'm gonna' try what you suggested again and just go back to v1.9. I didn't try all the features of 1.9 out (regular SP and MP) but what you say about the launcher downloading current updates and applying them to older installs makes sense as I suspected that was what may have been happening and then messing up my older installs (even though the launcher versions are different). I guess the only way to get around that would be to disable my internet connection during play.. but then I wouldn't be able to try out MP without it wanting to download the updates anyway. BTW.. I did disable 3D sound right off the bat. I do have FL installed to my C: drive (C:\Games\) but FLMM installed in it's own dir on my E: drive (along with mods); both drives have over 100GB free on them though. I used to install FL,FLMM,FLID and FLAM all together in Freelancer's own dir.. but I stopped doing that this round because I thought it best.
Michael..
Thanks for your suggestions as well. What you say about Crossfire ''breaking'' from FLMM on deactivation makes sense.. and also would explain my ''Unable to..'' messages. Like I said.. what I actually did last night was to back up the entire ''clean'' game dir.. the saves dir.. and I even (hadn't mentioned yet) exported all of FL's reg entries to mergeable executables. So at worst.. all I would have to do is deactivate the mod.. delete everything (ignoring the restoration ''errors'') and then ''restore'' my clean install back after crossfire.. I can live with that.
@Cresthen..
Not certain.. but I think I may have read one of your older posts about your problems with open SP (may have been somebody else's though). It was from those previous posts that guided me to try what I did already.. thanks.
@SWAT_OP-R8R..
Thanks chief! I DID try the openspfix with 1.9 but the install was already broke by then, and then I even noticed it after my 1.82 install which is what led me to believe that no matter what version install I had.. the launcher would download the latest files. I didn't think the .cmd file was even supposed to be there in a clean 1.82 install, at least.. I didn't see you mention it to anybody until after 1.9 came out, so I didn't run it after that.
What I'm gonna' do is another fresh clean install (Uninstall,>My Games dir delete, reg wipe [BTW.. besides a manual reg sweep I DO use CCleaner and Wise registry Cleaner first to keep me from having to manually delete as much as possible]then a new FL and CF install of v1.9) then I'll try to only use the openspfix.cmd start like SWAT_OP-R8R said. Even if that doesn't work.. I'm sure the rest of the mod will work fine and like I said it's not that open SP is a ''must'' for me anyway.
I'll report back.
One last question though..
When using the openspfix.cmd file though.. what is the proper sequence of events? I noticed that when you execute the command.. a command prompt comes up and says something about making sure your internet is disabled.. then it says something about press any key. IIRC after that there's a quick blip about some files being written and then nothing (at least for me). Is it itself supposed to launch the game? Is this the order? Disable internet>Activate CF in FLMM>run command fix>Launch CF from FLMM using the CF Launcher and pick ''Single Player"? I'm a little confused as to how.. or what launches the game when using the .cmd fix.
Thanks again to all.