The Quadro FX 540 is a PCIe card, where as the Quadro FX 500 is an AGP card.

That DLL that Henk linked to is the OpenGL library that shipped with Windows NT4.0 (that's 1996)...so like OpenGL 1.2-era. Should Mastercam X use new features from, say, OpenGL 1.5, then you'll run into some problems. Also, I'm not sure where Mastercam X begins looking for the DLL; its install dir or system32. If they explicitly look in system32, it'll do nothing to have that DLL in there. In that case, you could overwrite your existing one with the the one Henk linked to. But if you're running something other than Windows NT4.0, I don't recommend it, unless Mastercam is the only OGL app on your computer. Just something to keep in mind.

Here's a few tips with a nethasp.ini file. Enable TCP/IP in the [NH_COMMON] section, since the majority of LANs will be running TCP/IP (old -school Novell networks will probably be the only ones running IPX): code: NH_TCPIP = Enabled Most don't use NETBIOS (alone) or IPX on their LANs so you can probably ignore the [NH_NETBIOS] and [NH_IPX] sections. The only other section you'd want to worry about is [NH_TCPIP], obviously. First you need to specify the internal IP address of the NetHASP server computer: code: NH_SERVER_ADDR = 192.168.150.111 ; replace with your server's internal IP The default port that NetHASP server uses is 475. It doesn't hurt to explicitly specify it though, and you may need to change it if another application be using this port on their LAN: code: NH_PORT_NUMBER = 475 I've sometimes had trouble getting the UDP protocol to work reliably over a VPN with NetHASP, so I use TCP/IP instead: code: NH_TCPIP_METHOD = TCP Over the VPN, you won't have a persistant connection, so disable the TCP/IP broadcasting feature: code: NH_USE_BROADCAST = Disabled That's it. Mind you, there may be other settings needed, depending on the LAN configuration. But this should work for most typical TCP/IP LANs out there with a NetHASP server using the installation defaults. HTH

Yes, it works for me over our VPN. What does your nethasp.ini currently look like?

You'll likely prefer C# to VB, if you're familiar with C++. C# is a very well-designed language

Yes it is. Sorry about that Here's what I posted in the X Beta forums a couple of months back: ------------ Getting started with Nethooks is super simple. I'm a fan of C# so I'll use that to explain. You'll first create a Class Library project in Visual Studio; C#, VB or J# (does anybody actually use J#?!?!?). Then you'll want to add a COM reference to nethook.dll (it'll be in the root directory fo wherever you installed X). You'll then want to add this to your class's using section: code: using Mastercam; Next you'll have to make the class you (or more specifically, VS .NET) created extend the CMCNETApp. So change this: code: public class CTheClassYouCreate { to: code: public class CTheClassYouCreated : CMCNETApp { Instead of a main() method as the entry point, you have to add an ovverriden method called Run() to your class: code: public override MC_RETURN Run(System.Int32 param) { return MC_RETURN.MC_NOERROR; } Build it and you should be good to go. So for a HelloWorld Nethook: code: using System; using System.Windows.Forms; using Mastercam; namespace HelloWorld { public class CHelloWorldNethook : CMCNETApp { public CHelloWorldNethook() { } public override MC_RETURN Run(System.Int32 param) { MessageBox.Show("Hello World!"); return MC_RETURN.MC_NOERROR; } } } And like Roger mentioned, check out what's available to you in nethook.dll in the Object Browser. HTH ---------- I can whip you up a VB.NET version, if you wish. It basically comes down to replacing C# synatx with VB.NET (Ex:"using" -> "Imports", "override" -> "Overrides", "Implements" when subclassing, etc). HTH

Crashes for me, too.

Here's a quick intro to creating a Nethook with C# (It's very similar in VB.NET). The Nethook API is somewhat self-documenting. Take a look at the nethook.dll in Visual Studio's Object Browser. You can also ask questions on this very forum

Release or debug?

Mastercam X only works with HASP4's. See SimSwap.com and talk to your reseller.

GeForce: aimed at the home user and gamer market Quadro FX: greater speed and stability, aimed at the CAD/CAM market Search the forum for "Quadro" and you'll find a lot of happy people.

So in other words, easier to hardcode the IPs, making sure they're on the same subnet, share folders, use UNC paths and call it good

nVIDIA Quadro FX would be my first choice. nVIDIA GeForce (the high-end of the GeForce line... > $100) would be my second.

ATI cards are notorius for not working well with Mastercam V9 and earlier. Search this forum for "ATI" and you'll see what I mean. You could try turning down accelleration to begin troubleshooting.

quote: Won't Nvidia chipset, high end gaming cards run X just as well as the Quadro's, most of them support open GL? Many video cards support OpenGL but some are better than others. With Mastercam, memory on the video card isn't as big an issue as the chipset on the card when it comes to CAD/CAM apps.

This, perhaps.

quote: One pc will act as the dhcp server and the other pc will gets its ip address info from there. Huh? I know that ICS has a built-in DHCP server, but I'm not sure about WinXP itself connected to a hub

A hub is "dumb", generally just shares a connection and doesn't perform any DHCP so the IPs of the two computers should be manually set before hand and they should be on the same subnet. Routers, on the other hand, are "smart" in that they perform DHCP functions. Also, you could simply directly connect a crossover Ethernet cable to the two computers and network them that way as well, again manually setting their IPs and subnets beforehand.

quote: make sure that as they fix one thing they want to make sure they don't break or affect someting els AKA: regresssion testing (testing for bugs that surface after adding new features or fixing other bugs)

I don't think it's possible.

Using Jeremy's method, you could create three shortucts; one each for Mill, Lathe and Design.

quote: ...with too much time on his hands I wish. Who's with me for 28-hour days? Anyone? Anyone?

If SP1 has installed successfully, you should see "SP1" in the Mastercam title bar and the build number on the About dialog should be 10.0.14.19. Are you installing SP1 with administrative rights on the local computer? Also, are you installing through the built-in Update utility or via a downloaded file?

You could write a start-up Nethook (and probably C-Hook) to handle that. I don't see a way to set gradient background colours from C-Hooks/Nethooks/VBscript, though, so it would only be solid colours. Here's how you'd do it with vb script: code: ' ****************************************************************************** ' * Source Code : ModuleColour.vbs * ' * Description : Set background colour according to Mastercam module * ' * Date : 09/23/2005 4:41 PM * ' * Version : 0.0.1 * ' * Programmer : Christopher V. Bellini * ' * * ' * ---------------- * ' * | REVISION LOG | * ' *----------------------------------------------------------------------------* ' * Programmers Notes: * ' * - cvb (09/23/2005): V0.0.1 completed * ' * * ' * ///////////////////////////////////////////////////////////////////////////* ' * This library is free software; you can redistribute it and/or modify it * ' * under the terms of the GNU Lesser General Public License as published by * ' * the Free Software Foundation; either version 2.1 of the License, * ' * or (at your option) any later version. This library is distributed in the* ' * hope that it will be useful, but WITHOUT ANY WARRANTY; without even the * ' * implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. * ' * See the GNU Lesser General Public License for more details. * ' * * ' * You should have received a copy of the GNU Lesser General Public * ' * License along with this library; if not, visit: * ' * http://www.gnu.org/licenses/lgpl.txt or write to the Free Software * ' * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA* ' * ///////////////////////////////////////////////////////////////////////////* ' *----------------------------------------------------------------------------* ' ///////////////// CONSTANTS ///////////////// Const DEF_DESIGN = 4 Const DEF_MILL = 8 Const DEF_WIRE = 16 Const DEF_LATHE = 32 Const DEF_ROUTER = 64 ' kick off the script Call Main() ' Purpose: the main subroutine Sub Main() Select Case mc_APPMODULE Case DEF_DESIGN Call SetBackgroundColor(mcCOLOR_DARKBLUE) Case DEF_ROUTER Call SetBackgroundColor(mcCOLOR_BROWN) Case DEF_MILL Call SetBackgroundColor(mcCOLOR_LIGHTGREY) Case DEF_LATHE Call SetBackgroundColor(mcCOLOR_DARKGREY) Case DEF_WIRE Call SetBackgroundColor(mcCOLOR_YELLOW) End Select End Sub Then modify your Target for your X shortcut to include the path to the script: C:mcamxmastercam.exe "C:pathtoModuleColour.vbs" HTH

quote: Thanks- I don't suppose that will plug into just any old PCI slot, will it? I mean, could I pull out an old AGP and use a PCI Express in a regular PCI slot instead? Nope. PCI and PCI Express are vastly different from each other.