Categorysolidworks

Tortoise SVN freezes when trying to lock/add/commit changes of SolidWorks files

Tortoise SVN sometimes freezes when SolidWorks files get changed when the user tries to lock/add/commit files.  This is caused by the sldShellExtServer.exe process conflicting with Tortoise.  Disabling the shell extensions that SolidWorks installs on the computer removes the conflict so that SVN can work properly.

The Fix

The fix involves disabling the shell extensions, so disabling them is not recommended if the user makes use of these features.

  1. Download ShellExView from http://www.nirsoft.net/utils/shexview.html
  2. Disable the following items:
    • SLDASMIcons Class
    • SLDDEWIcons Class
    • SLDPRTIcons Class
    • SldShellExtension Class
    • Solidworks Document Thumbnail Handler
    • SolidWorks file Info Tips Class
    • SolidWorks file Preview Class

Once these items are disabled, SVN should work properly.

SolidWorks Side-By-Side Configuration Error Fix

I finally found the fix to the error in SolidWorks 2010 (also reported to work for SW 2011, 2015 and 2016) that prevented me from running the program.  The computer uses Windows 7 32-bit (works also for Windows 8 and 10 as pointed out in the comments), and every time I started up the program it would something like:

The application failed to start because its side-by-side configuration is incorrect.  Please see the application event log or use the command-line sxstrace.exe tool.

I used my Google-fu and found that the cause of this error is due my computer not having the Microsoft Visual C++ 2005 Redistributable.  A copy of the setup file for this is in the SolidWorks 2010 disc.  It is in the folder (DVD Drive):PreReqsVCRedist.  After installing that, the error disappeared and SolidWorks starts properly.

How to Install Solidworks 2008 on a x64 Operating System

This guide will describe how to install Solidworks 2008 on a 64 bit operating system.  This has been tested on Windows 7 Professional x64 and with Solidworks 2008 SP4.0.

Update (Dec 8, 2009): I know that there is a copy of Solidworks 2008 that was released for 64 bit operating systems, but this article is talking purely about getting the 32 bit copy to work.  Also, there are also other distributions of Solidworks 2008 available, but this article is only concerned with the “Solidworks 2008 SP3.0 w/ COSMOS” on PirateBay, which I am not going to link to.

INSTALLING SOLIDWORKS

  1. Download and Install Orca MSI Editor.
    • link: http://www.technipages.com/download-orca-msi-editor.html
    • its use should be very straight forward
  2. Open English_i386_Solidworks.MSI inside the Solidworks set up files.  It should be in “Solidworks 2008 Office Premium SP 3.0 w COSMOSswwidata”
    • this file is included in the Pirate Bay release of Solidworks 2008 SP3.0 w/ COSMOS
  3. Under “LaunchCondition”, change the “Not” to an “Or” in the line that has a description saying “x64 operating systems are incompatible/not supported”
  4. Disable any anti-virus programs
    • I’ve never had an anti-virus program cause any problems until now.  I had Bitdefender 2010 on my computer and it caused the installation to hang.
  5. Install Solidworks and apply the updates
    • DO NOT CRACK THE PROGRAM YET

CRACKING SOLIDWORKS

  1. Find the crack files for the most recent version of SolidWorks 2008 installed.  I used SP4.0
  2. Move ibfs32.dll to “C:WindowsSysWOW64”
    • this folder doesn’t exist on x86 systems.  I believe that this folder above contains system files necessary for 32 bit apps to operate
    • the dll file should be included in the Solidworks release
  3. Open the “.reg” file included with the crack with Notepad
  4. Under “[HKEY_LOCAL_MACHINE…]”, add “Wow6432Node” after “Software” so it says “…SoftwareWow6432NodeFLEXlm…”
    • apparently 32 bit apps have their own place in the registry and it is not mixed with the registry keys of x64 apps
  5. Create directory “C:Program FilesSolidworks” and put the solidworks license file inside.
    • the license file has extension “.lic”
    • for the SP4.0 update, the license file was called “sw2008.lic”
    • other releases have a similar filename, but the “.lic” should give it away
    • the registry keys tell Solidworks to look in that directory for the license file.  The program itself was installed in “Program Files (x86)” so the folder had to be created

Remembrance Day + Solidworks Hacks

Although today is Rememberance Day, I did not go through my yearly tradition of playing World War II themed computer games.  Yes, the idea of doing that might be stange or create a bad image, but I mean no disrespect.

Today was supposed to be the day for me to catch up on homework since I had missed a week of class due to my Class 5 road test and my gum graft surgery.  Ivan was nice enough to lend me his notes.  Rather than doing homework today, I decided that I was fed up with Solidworks 2008 not running properly on my Windows 7 x64.

I had previous downloaded the SP4.0 for Solidworks 2008 in hopes that it will allow me to run it on my computer.  To try to get that update to work I would have to install Solidworks 2008 SP0.0.  Due to an unknown reason it would not install on my computer.  Despite the fact that Solidworks would say ‘this program does not support Vista x64’, I had gotten it to install by setting the compatibility mode.  This time around, the installer simply got stuck.

I then thought of alternate methods of getting the program on my computer.  I looked to my virtual machine, which was my temporary solution.  It ran Windows XP and could barely run SW08.  I tried to send the files through the network.  I couldn’t send the files through with a hard drive since it was being used to install the program (yes, the installer was stuck, but I left it running to see if it would respond).  I had trouble sending the files through the network since I had disabled all the network services on the virtual machine to save memory.

A few hours later I still did not have Internet back, but I did however have access to the LAN.  That was all I needed.  While doing the network transfer, an idea hit me.  I turned off Bitdefender and the Solidworks install worked.

After the install, I immediately updated the installation to SP4.0.  I cracked the program as was instructed by the readme.  The program still didn’t work.  I was not shocked.  It told me that it could not find license information.  I figured that it was a side effect of the 64 bit OS.  I took another look at my patch files and saw that it was a 32 bit patch (the title never said).  I looked for x64 versions of SW08 on eMule, but could not find any fast downloads.

Later on an idea for a fix hit me.  I realized that the 32 bit programs were stored in ‘Program Files (x86), which meant I put the license file in the wrong place.  It was supposed to go into ‘C:Program FilesSolidWorks’. I missed the x86 part.  I changed that and ran the program again.  Still no good.  I looked in the registry to see if my registry keys were correct and I stumbled upon the folder where 32 bit software registry entries were stored.  I then realized that my registry info had to go in there instead.  I fixed that and tried it one more time.  It was still no good.  Then i thought, ‘if there was a place for 32 bit registry keys, would that apply for system32 as well?’  Turns out I was correct.  I put the dll file in ‘c:WindowsWow6432’.  I ran SW again and it works.  I felt like a total genius.

© 2017 Henry Poon's Blog

Theme by Anders NorénUp ↑