2004 SP1.0 is available

It's now up on the subscription service site.
Reply to
Dave H
Loading thread data ...
Looks like they added some interesting new features. Here are a few nice ones..
Import/Export: Versions 17 through 2001 of Pro/ENGINEER®
Options: A new option, Save tessellation with part document, is available in Tools, Options, Document Properties, Image Quality. This option saves disk space and decreases save time when the part has detailed surfaces where the tessellation data is larger than the size of the geometry on disk.
I did a quick test on this and it was as if I used EcoSqueeze on it. The file size was reduced considerably. Very interesting indeed!
Drawing Sheet Properties: You can now access the properties of an inactive drawing sheet. Right-click the sheet icon in the FeatureManager design tree and select Properties.
Bill of Materials: Under Part Configuration Grouping in the Bill of Materials PropertyManager, selecting Display as one item number resulted in components with multiple configurations being listed in one row with the quantity increased appropriately. Now components are listed in separate rows for each configuration, but with the same item number.
Mike Wilson
Reply to
Mike J. Wilson
grrr.... can't install it (french version) on 2 machines (XP french)... it says the program doesn't exist or isn't the correct version... tried to uninstall/reinstall 2004SP0, changed localization to US, ... any other idea ?
Reply to
Philippe Guglielmetti
Try with copying the .exe-file directly to the C-root....if it's in a folder beside You usually get that message
Krister
Reply to
Krister L
Freaking sweet, well a start (see below).
Anyhow, between 30-60% reduction typ when it's off! So, when saving a 40meg part, this will help.
Thanks at least for the sldprt, SW Programmers, I appreciate that one!
But,... does this apply to the sldasm's as well?? The sldasm image quality has a line option as well but it's grayed out with a check mark "on"?? Hmm,... it does not seem to be an option....??
Ok, so now we will have to ask for a ER on giving us the sldasm tessellation off??
C'mon, SW Corp, clearly the sldasm's are the ones which are the memory hogs... so having this option as well will make sense, no? Ah, I see, this may effect some VAR demos opening 11K parts in less than 30 secs... and that won't be the case if someone turns off aldasm tessellation now will it!?
damn...
"Mike J. Wils>
Reply to
Paul Salvador
thanks... but it didn't help...
Reply to
Philippe Guglielmetti
Sorry ...forget about last post....this seems to be handeled in a different way then before
Krister
Reply to
Krister L
BTW, using EcoSqueeze, it seems it's still saving some information!?
For example:
13.7 meg's, with tessellation storage on. 5.7 meg's, saved w/o tessellation. 2.5 meg's, EcoSqueeze'd removing display list. 550K, EcoSqueeze'd, removing display list and parasolid(not recommended). 150K, zipped.
.. that's a lot a data still being stored!!!
So, there's the M$ mirror data still being stored before EcoSqueeze?
..
"Mike J. Wils>
Reply to
Paul Salvador
Problem, still.... Not all surface bodies are showing!!!!
..
Reply to
Paul Salvador
For example:
The "Surface Bodies(5)" folder shows quantify "5", which is correct, but the folder only has "3" surfaces in it!?
..
Paul Salvador wrote:
Reply to
Paul Salvador
I'm hoping the presence of the greyed check box is a clue that they intend to implement this for assemblies. My theory is that it was implemented and validated on part documents first. It's a nice hopeful theory, anyway.j
Reply to
Dale Dunn
Anyone else having problems with the service patch install? Several errors relating to disk space on C: drive when SOlidworks is installed on the D: drive. The numbers don't make sense when the error occurs. For example I currently have 268MB free on the C: drive, The installer says that 436kb req'd but only 425kb available. After several aborts and disk cleaning sessions I finally got to the point where the message says that install can continue but without rollback options. I went ahead and said go for it. Now I have a dialog box that says, "Preparing to remove older versions of this application". The status bar is about at 75% and has not moved for 30 minutes, the task manager says the process is still running. How long should this take and if I click 'Cancel' what will be the result?
I wish they would have stuck with the traditional installer...
thanks.
Jeff Cox CAD/CAM DEPT. BYERS PRECISION FABRICATORS
Reply to
Not Necessarily Me
Everything for me was fine until I got to the removing older versions dialog. just like you it stopped at about 75% done. I caneled out and then killed the program in task manager. I then installed SolidWorks 2004 disk one and waited for the install dialog box to pop up. When it did I chose repair installation. It cruched away for a while and then told me I had successfully loaded 2004 SP1. I have been using it all morning with no problems.
Reply to
Rob Rodriguez
I have a problem updating an administrative image. It gives me an error that it's not able to write a temp file to finish the update. Can't get it to finish. Even re-downloaded the patch. Nothing. The first time I got the error it even stripped out the .msi file needed to run the update.
Ken
Reply to
CSWP
So what bright spark at Solidworks Corporation decided that the Solidworks 2004 downloadable version could not be updated. After multiple attempts I called my VAR and was told this mindblowing fact. I now have to do a full uninstall and reinstall from the disks to get it to update.
Reply to
Phil Evans
Also clean the registry of anything to do with solidworks. I had 2003 still on my system and some remnants of 2001+ but after uninstalling 2003 & 2004 and cleaning the registry then reinstalling 2004 the service patch worked fine. Can't blame this on Solidworks but maybe the windows installer?
Reply to
Not Necessarily Me
Why not? Certainly sounds like a failure to do even minimal testing. It's not as if M$ released the SP....
Reply to
Michael
I would think so as well?
..
Dale Dunn wrote:
Reply to
Paul Salvador
Hmm... I did not get those errors but...
When the install said it had finished and for me to either reboot or not, I choose not to reboot, a message was on the top left of the finished installation window and it said "sp error (3010)".
Does anyone know if that is a bad thing?? Otherwise, everything seems fine?
..
Not Necessarily Me wrote:
Reply to
Paul Salvador
Yep, dat is the truth. I had to do a uninstall and remove any 2004 registries. I think it was Per who brought this up here?
..
Phil Evans wrote:
Reply to
Paul Salvador

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.