Oh found it, under the (!) in the files heading under the ops manager. Sorry someone delete this if you want. Dave

I've got a few things in there I do not like and want to delete them can't seem to figure out how. Any one know? Dave

Holy s^%$ I just read through how to fix it...I have a headache. Where is the easy button? It's coolant fer cryin out loud. Dave

To dual boot there are several free utilities out there I'm using Vista boot pro 3.3

Best "fix" is to make a partition on your HDD and do a dual boot setup with XP or just roll back to XP. I struggled with vista and X2 mr1 for weeks. At best it was not livable fixed all of the graphics issues but the tool paths were agonizingly slow.

I'm using SW 2008 pre release now works fine in Vista. Vista has been great except for MC it's the only program I'm having problems with. I finally made a partition on my HDD and installed XP in a dual boot configuration. I have MCX there all by itself now, runs great in XP.

Have they addressed any of the vista issues in MR2?

I do. The tool paths run very slow. Had a lot of graphics issues until I set the graphics to "best performance". Tool paths run so slow (like ten seconds for a simple profile operation) that I'm looking into a dual boot configuration with XP. My advice is don't switch to vista yet. Dave

Yours is a lot more sophisticated, very nice, thanks for posting it up for all to see. That's mighty nice of you. I may use it someday. Thanks for your help, it worked perfect. Dave

Thanks, that sounds like it will get me there. Just curious why the " ,e$" ?

My current Haas post, pretty much stock but professionally modded to use G10s, is not outputting a G90 at the start, causing issues. I need the start line (G90 et. al.)to be right at the beginning of the program before all of the G10 calls. I do not have any experience modding posts besides flipping switches on and off (like the A axis) so I'm pretty much in the dark here. Anyone know where such a line would go and how it should look? Thanks for any help Dave

Vista ultimate, GTS 6800 card, turned off SLI (have 2 of them) latest drivers. 4 gig of ram intel dual core 2.66gig I know. I was crazy to do this (maybe stupid) but I'm willing to wait out till the next update to see if anything is fixed. In the mean time I could use any advice you've got. I already have hardware accel off. It helped get rid of the "smears" but now when I generate a tool path it takes way too long. 20 seconds to run a simple contour path. A full minute to generate a pocket with a .25 EM that is .3 deep. Verify runs very fast. Moving a simple solid results in the jitters. Solid faces select really slow, they will highlight about 1-2 seconds after I run the cursor over them. Anyone found any settings that fix any of this? Any hope for a fix in the next update? How about with X3? Dave

You have to DL solidworks 2008 beta to get it to run on Vista. Dave

It did work, had to shut down and restart MC after the changes. Thanks. Dave

Yep made this game rig and knew I was asking for trouble. I'll keep hacking at it.

link I saw this advice, it did not help. using vista ultimate I'm running an intel MB with 3gig dual core chip, 4 megs ram, 2 NVIDIA 8800 GTS cards in SLI latest nforce drivers. Latest MCX2 mill 3 version When I drag a line or anything across the screen it whites the screen out with a big smudge, screen will reset with clear colors, looks like a video card or driver issue but I'm not sure what might fix it. Any ideas? Dave

All the time, sometimes I get $$$$$$$ in the min max fields and the message "stock size failure" or something to that effect, blank simulation area. I always have to set the stock size every time I simulate, even if I've set it up in the ops manager. Drives me nuts.

The standard Haas 4 axis post. Funny that my machine did not used to care, until I hooked up the A axis and then shut it off. If I turn on the indexer without it hooked up and try to reset I get an error that it does not get a servo signal or something to that effect. I'll just set up another post. Thanks for the help guys. Dave

So I had my indexer on the table for a while (2006 Haas vf-2) and recently took it off and disbled it in the control. Prior I would have no problems running a program with an A0 move (as my Haas post outputs) even with no indexer on there. No since I removed it I get errors if the control reads an A move. Anyone know how to fix this? Dave

You know I like this forum, but it takes so damn long to get an answer come on... 5 minutes? Who has that kind of time anymore? Thanks John (again) Dave

Making a prismatic part on a Haas with HRT 160. The post is outputting indexer moves reversed ie: should be 13 degrees but post outputs -13 degrees. The planes are correct in angle, visually and as analyzed. Is there a post setting I need to flip what could be the problem. Did a search but did not find anything about this. Dave

Thanks Ron.

So I have this indexer part, on a VMC typical X axis position. Haas mill, stock Haas 4x post. Program from centerline. I made named views and just rotated the tool plane (at least I think I did) by picking plane, rotate around x, 90 degrees, 180, 270, all the way around the part. I renamed them as I went. To do the tool paths I picked WCS view manager, put the C and T icons in the correct named view slot and made the tool paths. The back plot looks good, sim looks good too. The posted code does not want to output a 270 or 180 A axis moves. I get A90, A-90, and A0 moves. I kept the origin and work offset set to -1 the whole time not sure if this is correct. So question can it be done this way and there is some radio buttin I missed or am I going about this the wrong way? Post issue?

So overcut is the thread desired thread depth?

I sent it to you, also uploaded it to the solids folder on the FTP site. Called "Fadal VH-165 and VMC 15 table " Dave