Hi,
I have made an administrative install for SW2010 sp4. I have client with WinXP SP3 32bit.
We uninstall the SW2008, reboot the PC and install SW2010 without problem.
But the first time we start SolidWorks 2010, we received this message "preparing solidworks for first use". I'm waiting appr. 30min and nothing append. Try to quit and restart SW, but the same problem.
Thank you for your help and regards,
Alain
SolidworksAdministration
Alain welcome to SW forums.
Did you got any License Agreement to accept?? Did you removed the SW2008 completely.
Hi,
Thank you for the answer.
No, I didn't have any license agreement. Yes, we have uninstalled all SW2008 components from Add/Remove Programs adn removed the folder in C:\Program Files\SolidWorks.
But apparently, we only have this problem on PC who had SW2008 installed, on a new PC, we don't have this problem.
Regards,
Alain
One of the reason can be that SW2008 was not removed properly. Check this: CleanUpdate
Hi,
Thank you I will try it on Monday.
Regards,
Alain
Hi,
I've tried it, but I have the same problem.
Thank you,
Alain
Hi,
Apparently by me it works with :
SolidWorks uses .NET technology and to gain maximum performance the SolidWorks components based on .NET are compiled to native dlls at installation time.
"
Depending on the characteristics of the hardware and the machine load this step may take a few minutes longer than the actual SolidWorks installation.
To ensure correct functioning SolidWorks 2010 SP3 and later will wait for that compilation step to complete, showing the message "Preparing SolidWorks for first use. This may take several minutes."
In case the message does not disappear within a reasonable period of 2 hours, please open a DOS command prompt, navigate to one of these folders:
Use "cd
32bit machine:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
x64 machine:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727
and type the following command:
ngen.exe executeQueueditems
This should cause .NET to compile all .NET components that have been queued up as soon as possible instead of in the background when the machine is idle.
The .NET components in the queue may come from SolidWorks, 3rd party applications based on .NET, and the .NET framework itself.
On a 64-bit machine, please invoke the above command from both a 32-bit and a 64-bit DOS command prompt.
Thanks Alain for sharing that and good to hear that you finally resolved it
The full solution can be found as S-050248 in the SolidWorks Knowledge Base.
Regards,
Frank
SolidWorks Partner Technical Manager
SolidWorks R&D Ltd, Cambridge, UK
good