Creo 2.0 M140?

[ocorten-2]

Creo 2.0 M140 should be available by januari 9th:

[jschaaf]

I heard the release has been moved to January 23rd.

John

[HugoHermans]

Still no release. M130 must be very reliable 🙂

<< ProE WF5 - PDMLink 10.1 M040>>

[mreece1]

I saw a notice today from the PTC Tech SUpport subscriptions that M140 was
available, but I don't see it on the download site yet....

[image: Inline image 1]

On Sat, Jan 24, 2015 at 11:48 AM, Hugo Hermans <->
wrote:

> Still no release. M130 must be very reliable 🙂
>
> << ProE WF5 - PDMLink 10.1 M040>>
>
>

[jschaaf]

The reply I finally received from our PTC TSAM after opening a call is attached.

John

[jschaaf]

Hello All,

Creo 2.0 M140 is available from the PTC.com support page.
Downloading now.

Regards,

John

[RandyJones]

On 01/29/15 07:06, Schaaf, John (MN10) wrote:
>
> Hello All,
>
> Creo 2.0 M140 is available from the PTC.com support page.
>
> Downloading now.
>

I downloaded it last night. Apparently there were no changes or PTC reposted the old download by
mistake. The size, sum, and digest are all the same for the 2 downloads.

server4% ls -l
total 26305566
-rw-rw-r-- 1 randy engrng *4329946404*Jan 28 22:08 MED-100WIN-CD-390_M140_Win32-64.zip
-rw-rw-r-- 1 randy engrng *4329946404*Jan 23 16:05 MED-100WIN-CD-390_M140_Win32-64.zip.bad.pulled
server4% sum MED-100WIN-CD-390_M140_Win32-64.zip MED-100WIN-CD-390_M140_Win32-64.zip.bad.pulled
*24295 8456927*MED-100WIN-CD-390_M140_Win32-64.zip
*24295 8456927*MED-100WIN-CD-390_M140_Win32-64.zip.bad.pulled
server4% digest -a sha1 MED-100WIN-CD-390_M140_Win32-64.zip
MED-100WIN-CD-390_M140_Win32-64.zip.bad.pulled
(MED-100WIN-CD-390_M140_Win32-64.zip) = *fff6c26b971e0f0363d00e5e6d0730ddfd0e036c*
(MED-100WIN-CD-390_M140_Win32-64.zip.bad.pulled) = *fff6c26b971e0f0363d00e5e6d0730ddfd0e036c*
server4% digest -a md5 MED-100WIN-CD-390_M140_Win32-64.zip
MED-100WIN-CD-390_M140_Win32-64.zip.bad.pulled
(MED-100WIN-CD-390_M140_Win32-64.zip) = *f25c01b102ef818fc5a5b0408743a384*
(MED-100WIN-CD-390_M140_Win32-64.zip.bad.pulled) = *f25c01b102ef818fc5a5b0408743a384*
server4%


> Regards,
>
> John
>
> *From:*Randy Jones [

[dgschaefer]

I’m surprised that PTC re-released M140. They know that customers downloaded the bad version. When someone with M140 calls tech support, the support engineer will have to ask which M140 they’ve got.

--

[ScottPearson]

Brilliant observation, Doug.

What the &*%#^&^ was PTC thinking?!?

PTC should immediately republish the “corrected” M140 as M150 and send notices to all registered users to NOT install a-n-y version of M140.

If the glitch in the original, un-corrected M140 was bad enough to force PTC to remove it from their download site then PTC should not want any users to have it installed on their systems.

Once again, “Well done, PTC.”

We can hardly wait for you to take over the Exploder. (Can you blame us?)

Scott Pearson
Senior Designer
CAD System Administrator

[cid:image007.png@01D03BA3.1D3A1C40]S O U T H W E S T R E S E A R C H I N S T I T U T E®
Space Science and Engineering Division
Space Systems Directorate
Department of Space Engineering
6220 Culebra Road, San Antonio, TX 78238

[dgschaefer]

I find it especially ironic from a company whose premier product is a Product Data Management solution.

(I also find it ironic that a company that sells CAD tools to help you get to market faster has been consistently lengthening their time to market on new versions of said CAD tool. But that’s another thread. :-D)

--