Re: Concurrent use of SWX 06 and 07



Bo,

The toolbox problems with running multiple versions has to do with how you
install the seperate versions. Never go with the default install locations.
I specify seperate folders, off the root (not programs directory), on my "D"
drive for each version. The important part of the install is the Solidworks
"data" location. This is where your toolbox stuff lives. You don't want two
versions to share it. Make them seperate as well.

You'll also want to immediatly change the "tools-options-file locations" on
the new version. New versions allways install with these things (like
..sldmat material file) pointing to the locations in the last of the previous
installations. Once you change these, you're running two isolated
installations. I've been doing this for years with no problems. I've had as
many as four versions installed at once, and no problems.


Mark


Bo" <bo@xxxxxxxxxxx> wrote in message
news:1173819110.594859.85150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The problem is when I "screw up" and get in a hurry and overwrite a
critical file. Then I'm in trouble.

CPUs are cheap, and I always have a spare hard drive or box, & hence I
just decided to put different releases on different computers (laptops
in my case). The additional reason is as follows because of "no way
back":

Right now I have a key critical mold cavity inserts from a tool vendor
in SWks 2007. I don't consider 2007 release ready for me, but I have
to open those files and work on them. Hence I will use another PC to
run 2007, and I can keep 2006 open on the other machine and I will
duplicate the key critical parts manually back into SWks 2006 so I can
keep on developing the products.

I do know from reading prior years posts that if you put two Swks
versions on the same machine, you can get funny things happening
(wrong) with Toolbox. Might search for prior messages on that.

SolidWorks & Computers are supposed to minimize ROTE TIME WASTING
B.S. This non-backward compatibility is yucky.

I would vote for SWks to consider a translator that allowed a part in
Swks 2007 to be SavedAs with ONLY 2006 FEATURES, and maybe options on
how to translate 2007 features into 2006. I will bet that 99% of
prismatic construction in 2007 is NO DIFFERENT than 2006.

How about it guys? Is this worth peppering SWks with?

Bo



On Mar 13, 3:06 am, "Flynt" <f...@xxxxxxx> wrote:
I posted a message along these lines a couple of hours ago and it has
never appeared. I say this to explain just in case it does!

Anyway, I have various models in SWX 06. I want to install 07 but need
to make sure that older projects remain associated with earlier
versions of SWX. That is to say that I don't want to accidently allow
conversion with no way back. If I did, I couldn't then provide the
files to my customer with an earlier version of SWX. I am sure you
get the idea and in any case I doubt that my need is unique. Not
forgetting that some parts could be common to various projects.

What is the best way of dealing with this?

Of course, non of this would be relevent if later files were backwards
compatible!

Thanks in advance,

F




.



Relevant Pages

  • Re: Just got this from a reseller!!!!
    ... I think the VARs have been warned to make sure SWks users do NOT ... Obviously SWks can't support a virtualized OS environment as the ... Those limitations on Tech. Support are fair as far as I am concerned. ... So far the person I heard this quote from could install the update to ...
    (comp.cad.solidworks)
  • Re: Firefox update
    ... as long as its seperate from a mozilla or firefox install ... you stick all that stuff in a seperate dir, ... to each of the installs real pluggins directory. ...
    (Fedora)
  • Re: Thousands of Event Log Entries
    ... I'm assuming your server is a DC hence the 538/540/576 entries in the ... Toolbox that was installed on some of the users pc's. ... directly from your desktop then you need to install the full ... blown HP Toolbox - which includes TomCat. ...
    (microsoft.public.windows.server.general)
  • Error message when opening matlab
    ... I have given up installing the toolbox. ... Warning: Name is nonexistent or not a directory: ... > That's not the right way to install a toolbox. ...
    (comp.soft-sys.matlab)
  • Re: openSUSE 10.3 Alpha 5 released
    ... I also saw no seperate /home, but that might be because I only ... First test run using just the CDs fails, whereas by turning them into a ... DVD lets the install complete. ... Just out of curiosity, ...
    (alt.os.linux.suse)

Loading