An email from QC this morning

[gcode]

We have just released a new update for Mastercam X SP1. The Update is called Mastercam X Service Pack 1 Update 2. This update affects the following areas.

 

 

 

Nesting – Check for Maintenance removed.

 

Posting – Mp fixes for:

 

Arc/linear movement Breakup

 

FS2 and metric output

 

prapid$ and pzrapid$ postblock call

 

ipr_actv$ now functions correctly

 

`(graves) symbol update only on output fix

 

Clearsub$, clearaux$, clearext$ now deletes temporary files

 

User prompt questions will now work even if fq after q call.

 

Exitpost$ fix

 

Crash Reporting Mechanism – Updated.

 

Mastercam Editor / Communications – Software Handshaking fix, Port Busy fix.

 

UpdatePost C-Hook – PSB update fixes, Read only posts fixes

 

 

 

This update also contains a new C-Hook "VersionChecker.dll". This C-Hook will aid you in providing detailed information to Technical Support by reporting all update files and versions. C-Hook can be run using Alt-C

 

 

 

 

 

** PLEASE NOTE: Due to an issue with the SP1 installation, you may lose your hasp connection after running this update. If this happens, download and run drivers.bat from this location:

 

" target="_blank">http://www.mastercam.com/Support/Downloads...s/drivers_x.zip

 

Removing your HASP while running this update will make it much less likely this issue will occur.

[Thad]

Those are hasp drivers.

 

There's nothing at MC's website about this update.

 

Thad

[Storkman]

Update 2

[Guest]

Hey Storky, bad link

 

All fixed,

 

Muchas Gracias

 

[dwsz71]

I just got an email from my reseller as well.

[Storkman]

Fixed John, try again

[dwsz71]

quote:

---

Hey Storky, bad link

---

Worked for me John.

[Storkman]

He was right, it was bad. But I fixed it.

[dwsz71]

quote:

---

Fixed John, try again

---

Late again, sorry John...

[Thad]

Thanks, Terry.

 

Thad

[Lathe-Mill]

just download it....too bad does not show the las fixed like ver. 9 shows at the top of the window..it only says sp1 and using the scrip shows 10.0.14.30

[Bullines]

quote:

---

...and using the scrip shows 10.0.14.30

---

10.0.14.30 is X SP1 Update 2, AFAIK. Good to go

[?Mark]

10.0.14.19 here

 

Mark

[?Mark]

Looks like the update went thru here.

Just posted a file to see if there are any differences and sure enough there are

Tool comments are moved one tool down.

T1 ()-------should read (CENTER)

T2(CENTER)--should read (DRILL 3/16)

 

and so on

 

Mark

[DavidB]

quote:

---

10.0.14.19 here

---

I updated and now when I go to update MC it says there are no updates available, but I have 10.0.14.19 too

[Thad]

Mark,

 

I had a posting issue like that too. If I posted 2 ops together, the tool comment was there on the second tool, but there was no tool comment on the first. Posting one op by itself had no tool comment.

 

I was going to post here but it was almost quitting time so I figured I'd just lump it in with all the other headaches on Monday. With these updates, it never fails!

 

Thad

[?Mark]

Thad, ain't this fun

 

Every new update it takes somebody no more than 5 minutes to find something like this...

 

Mark

[DavidB]

Same here after updating the tool coments in the posted code are a tool out

 

This is getting behond a joke. A major release (X)with so many things wrong with it.Then an update then an update for the update and now this posting issue.

Dont CNC check anythink before they release it?????

 

Is it possible to uninstall this last update???

[dwsz71]

Looks like I'll be skipping this one...

 

Doesn't CNC Sofware beta tests these "updates"? Or is this caused by user modified posts?

 

quote:

---

Is it possible to uninstall this last update???

---

You might be able to do a System Restore, if a check point was created prior to the update. That's assuming your running WinXP. If one wasn't created, we should all get in the habit.

[?Mark]

quote:

---

is this caused by user modified posts?

---

Nope, same thing happens with generic mill post

 

Mark

[dwsz71]

I guess that's "good" to know Mark, thanks.

[DavidB]

If it happens to a generic post that proves CNC did not even check this update

 

It also keeps the first toolpaths comment for all other toolpaths posted together.It puts the wrong tool comments for each posted toolpath too.

[Thad]

quote:

---

You might be able to do a System Restore, if a check point was created prior to the update.

---

Oh yeah? Try using a system restore point with SP1 and tell me how that works out for ya? Don't get me wrong, Dave. I see your point.

 

I'll tell you what, I try to stay positive on this stuff, but it just keeps going downhill. These updates are a goat-fuk every time. Why can't I execute an .exe, click a couple of "OK" buttons and eventually have a dialog box come up that says "You have successfully installed the update."? Instead, I sit around waiting until I think it's done. Then, how do I check it? I have to run a chook which is still unclear...listing my version number as one thing and then a list of other files that have been updated with another version number. What is so goddamn difficult about letting me know what version I'm running? On every other Windows program on the planet, Help-About will say "V3.127.472" What's the problem, CNC Software?

 

Thad

[Bullines]

quote:

---

Instead, I sit around waiting until I think it's done.

---

If an SP or update install isn't installed through the Update Manager, I fire up a Task Manager window, switch to the Processes tab and keep an eye on msiexec.exe. When that's gone, it's probably safe to assume that the install is done.

[?Mark]

quote:

---

Try using a system restore point with SP1 and tell me how that works out for ya?

---

I think I remember now that you tried

 

Mark