Hello Guest it is April 25, 2024, 08:45:42 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mcmlv

Pages: 1
1
General Mach Discussion / Re: Mach3 demo GUI behavior
« on: November 04, 2009, 01:38:44 AM »
I've saved some of the tutorial videos for burning to CD so that I can watch them offline since I won't be using a network adapter either.

2
General Mach Discussion / Re: Mach3 demo GUI behavior
« on: November 03, 2009, 05:09:05 AM »
Thanks for the quick responses. I have downloaded the following documents from the Mach3 support web page:

Mach3Mill_Install_Config.pdf
Mach3setup.pdf
Mach3Tutorial.pdf
Addons_Manual_v2_75.pdf

I have also downloaded the configuration file (540B.xml) for the Geckodrive 540 that I will be using. Are there any other documents that you can recommend? I would also like to know if Win2Ksp4 or WinXPsp3 would be preferred as an OS to host Mach3. The Intel Atom 330 based system will be dedicated to the Taig. Since I am just starting out, I would like to have as much reference material available as possible.

3
General Mach Discussion / Mach3 demo GUI behavior
« on: November 03, 2009, 03:05:56 AM »
Hi All,
I have just started a conversion of a Taig mill to CNC and I have installed the Mach3 demo version (ver. R3.042.029). The installation of the software and execution of DriverTest.exe went smoothly. After starting Mach3 I opened the Control Buttons Flyout and since it overlapped the parent window I attempted to move/resize it. This resulted in some of the graphics objects being left behind. Attached are two screen shots:

startup_screenshot.jpg  -- this .jpg shows the startup window for Mach3

modified_screen.jpg -- this .jpg shows the result of trying to move/resize the flyout. Buttons left behind.

I have installed the software on a P4B266 machine running Win2Ksp4. I have also installed the software on an Atom 330 based machine running Win2Ksp4. I have observed this behavior on both machines. I would like to know if anybody else has seen this, or if there is an explanation and suggestion on how to fix this problem. Also, is there any particular advantage to using WinXP instead of Win2K?

Thanks,

mcmlv
 

Pages: 1