7561
Mach3 under Vista / Re: Use of Embeeded Widows OS - Good, Bad, or Ugly?
« on: May 20, 2014, 06:25:26 AM »
I have just bought an Atom based single board computer an a Windows 7 Embedded Standard (WE7S) license. Have yet to receive it so have yet to establish whether it is a good idea.
I would have preferred XP Embedded but the supplier told me that the Atom graphics unit was better under WE7S. XP Em. can be made shrunk down to a smaller footprint than WE7S, really tho storage is not much of an issue these days, I selected a 64G SSD and 4G DDR3 800Mhz, more than enuf for even a fullblown OS.
WE7S does have better configuration/authoring tools than XP and given I'm no geek that will be important. One issue that concerned me is that so many software components depend on yet other components some of which are mutually exclusive. One piece of the configuration suite (trial free 180 days) explicitly highlights those dependencies and resolves them prior to deployment. Another of the suite allows additional modules to be added/deleted/modified on the target machine. The distribution share supplied has both 32 and 64 bit options, I will concentrate on 32 bit.
As the previous responder has suggested it really comes down to what you can leave out and still have Mach3 run. If anyone has any suggestions I'm all ears. For instance .NET support
from level 2 to 3.5 (I think) is offered and can be included. As to whether Mach3 requires .NET support I have no idea. Certainly other useful programs do use it and I have yet to decide whether to try them. The question is what modules I can include without 'stealing' too many resources from Mach3.
Craig
I would have preferred XP Embedded but the supplier told me that the Atom graphics unit was better under WE7S. XP Em. can be made shrunk down to a smaller footprint than WE7S, really tho storage is not much of an issue these days, I selected a 64G SSD and 4G DDR3 800Mhz, more than enuf for even a fullblown OS.
WE7S does have better configuration/authoring tools than XP and given I'm no geek that will be important. One issue that concerned me is that so many software components depend on yet other components some of which are mutually exclusive. One piece of the configuration suite (trial free 180 days) explicitly highlights those dependencies and resolves them prior to deployment. Another of the suite allows additional modules to be added/deleted/modified on the target machine. The distribution share supplied has both 32 and 64 bit options, I will concentrate on 32 bit.
As the previous responder has suggested it really comes down to what you can leave out and still have Mach3 run. If anyone has any suggestions I'm all ears. For instance .NET support
from level 2 to 3.5 (I think) is offered and can be included. As to whether Mach3 requires .NET support I have no idea. Certainly other useful programs do use it and I have yet to decide whether to try them. The question is what modules I can include without 'stealing' too many resources from Mach3.
Craig