transfer settings? 3

[cmm]

Is there a way to transfer system options, keyboard shortcuts, toolbars, etc. from one computer to another? Reconfiguring solidworks every time I install is such a pain.

 

[SBaugh]

Keyboard shortcuts - Copy the *.cus file from your Solidworks\user\*.cus

System Options - Use the copyoptwiz.exe (Copy Option Wizard) Soldiworks\setup\i386\copyoptwiz.exe

Toolbars - Your SOL

Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.3dmca.com

faq731-376
When in doubt, always check the help

 

[SeanF]

Scott,
Don't tell me you are gonna "hold out" on these guys

>Toolbars - Your SOL

Ok, for the record the toolbars can be saved. In fact SldWks does it at the following locations it seems.

[HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\SolidWorks 2003\User Interface]

and,

[HKEY_CURRENT_USER\Software\SolidWorks\SolidWorks 2003\User Interface]

respectivly.

So, first if you have no clue as to how to work in/around your registry. I would start here.

http://www.pccomputernotes.com/registry/editregistry.htm

Page 5 deals directly with making changes.

Once you manage to navigate to the listed keys. Right click these keys and export. I recomend giving it a "clear" name. Mine are along the lines of HKCU-Software-SolidWorks-UI-020403.reg and HKLM-Software-SolidWorks-UI-020403. Once you have exported the keys, you have saved them to disk. Then when you upgrade, reinstall, etc you will be able to import the reg files again. This is as easy as right clicking on the saved .reg file in windows explorer and selecting [MERGE].

This has been working well for me.

Sadly, I didn't come up with this. This was Scott's idea. Possibly he "can't" recomend this to others as editing the registry is involved. Again, my thanks to Scott, as this has saved me a gob of time.

Regards,





Sean F
Mechanical Engineer
seanf@newing-halll.com
1 2 many l's in e-mail

 

[SBaugh]

I got to be honest I found this on my own, but I jumped the gun on this method.

I know I told you about that Sean, but that User Interface trick is not recommended by SW and is a use at your own risk method. I didn't see why they were not supporting it till I had to reinstall SW. Once I reinstalled and used those reg settings I had a big problem arise. SW wouldn't open no matter what, (why I don't know) but it had to do with that reg key. The only way around it is delete that key and start SW over. Then build my toolbars from scratch, like we have been doing for the last few years with SW.

So just to let all who read this know THIS IS A USE AT YOUR OWN RISK!! and SW doesn't support this reg key transfering of toolbar options. It shouldn't damage your Registry in anyway. You only need to delete the "User Interface" key out and let SW remake it. Its made when you restart SW.

Best Regards & Best of Luck, Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.3dmca.com

faq731-376
When in doubt, always check the help

 

[SeanF]

Wow, that suckzors. At any rate I agree Scott. Anything registry related is use at risk at best. However, some days I feel the same about SldWks, so what the hell. Nothing risked is nothing gained.

I have used this w/o issue at least 1-3 times. I have also recomended it to several who do this now as well. I suspect that it is just a "crap-shoot".

The real "issue" here is that we have no choice but to do this. SldWks needs to get it together. The copy options wiz is "cheese wiz" at best. We would not even be having this discussion if "copy cheese wiz" worked like we would all so very much like it too. I mean wtf.. I have to back up reg settings, copy the .cus file, and freeking use the copy options wiz to get everything. What a freeking PITA! Personally I have resorted to the following. Waaaay NOT recomended. I just export the top SldWks key. Then import that. This takes care of the "copy cheese wiz" step. I still have to mess around w/cus file. But at least those two things get everything back to the way it was. I do however, suspect that if this bombed it would "bomb big" and I would have to reinstall. As deleting the top level keys would probably kill SldWks I doubt everything is created @ runtime.

This problem, and the part file "baggage" are two of the things that bother me most about upgrades.

Indeed, your heads up on the pitfalls of registry editing/work arounds something people should know.


Regards,

Btw... That spaceball show yet?


Sean F
Mechanical Engineer
seanf@newing-halll.com
1 2 many l's in e-mail

 

[SBaugh]

I know I used to think the Copy options wizard copied everything out and saved it. I think alot of other people think the same way, but now I think the way is like this. The copy options wizard only copies the system options. Where as the Document templates (part, assembly, & Drawing) saves the Document options per template.

So what you need to backup or run is:
1) Copy options wizard
2) Document templates
3) Cus file
4) Any customized Feature Palettes or parts there in.
5) if your willing to take a chance the toolbars (see Sean F. for HKEY path.

Best Regards,

Nope I'm sill waiting on the space ball.... Every time the UPS truck comes by I'm waiting at my front door hoping he's going to stop.... Scott Baugh, CSWP
3DVision Technologies

http://www.3dvisiontech.com

http://www.3dmca.com

faq731-376
When in doubt, always check the help