MfgSys64.exe Blank Title 98250

Hi Pim,



The 64 bit client executable (mfgsys64.exe) is provided for instances
where it is necessary to have custom code that references other 64 bit
3rd party dlls. This is not a common occurrence. In general, the 64 bit
client executable uses more system resources than the 32 bit client
executable (mfgsys.exe) and may run slower on your machine. The 32 bit
client is compiled for both 32 and 64 bit windows operating systems and
is recommended in most cases.



Thanks!

~Nathan



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of jfmartin67
Sent: Tuesday, June 14, 2011 3:33 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: MfgSys64.exe





pim,

i don't have an answer for you, but actually we are facing something
that might be related and wanted to see if you heard from anyone on your
issue.

we are getting hard errors running the 64 bit epicor with the 32 bit
crystal reports.

we are trying to find out if:

1) is there is a 64 bit crystal reports version or

2) does someone know how to make the 64 bit epicor (we're running
905.602) with the 32 bit crystal reports

john martin

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , Pim
Zandbergen <P.Zandbergen@...> wrote:
>
> Recent Epicor versions come with what appears to be a native 64-bit
> client, named MfgSys64.exe. I tried it, and it works. Task Manager
> confirms this program indeed does not use WoW64, like MfgSys.exe does.
>
> But I don't see any reference to it. Is it official? Is it beta?
>
> From my knowledge of .Net, there is no such thing as a 32-bit or
> a 64-bit .Net application, but rather "true" .Net programs, which
> run on any architecture (the framework should handle that) and
> "not-so-true" .Net programs, ones that make calls to the win32 API.
>
> Apparently MfgSys.exe is marked as an application that calls the
> win32 API, and MfgSys64.exe as "true". But the real danger is that
> every .dll called needs to be clean as well. Is that the case for
> all Epicor and third party assemblies, like Crystal Reports?
>
> Also, I would assume that any report called from MfgSys64.exe
> would use 64-bit ODBC drivers if that report would use ODBC.
>
> Does anyone have more experience with this?
>
> Pim
>





Click here
<https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==
GjnEzg0z7O0GWzZAQ1ICD44IXvT!cBpuimT5CCz92bNxfg==> to report this email
as spam.
--------------------------------------------------------

This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. Any views and/or opinions expressed in this e-mail are of the author only and do not represent the views of Epicor Software Corporation or any other company within its group.


This message has been scanned for malware by Websense. www.websense.com


[Non-text portions of this message have been removed]
Recent Epicor versions come with what appears to be a native 64-bit
client, named MfgSys64.exe. I tried it, and it works. Task Manager
confirms this program indeed does not use WoW64, like MfgSys.exe does.

But I don't see any reference to it. Is it official? Is it beta?

From my knowledge of .Net, there is no such thing as a 32-bit or
a 64-bit .Net application, but rather "true" .Net programs, which
run on any architecture (the framework should handle that) and
"not-so-true" .Net programs, ones that make calls to the win32 API.

Apparently MfgSys.exe is marked as an application that calls the
win32 API, and MfgSys64.exe as "true". But the real danger is that
every .dll called needs to be clean as well. Is that the case for
all Epicor and third party assemblies, like Crystal Reports?

Also, I would assume that any report called from MfgSys64.exe
would use 64-bit ODBC drivers if that report would use ODBC.

Does anyone have more experience with this?

Pim
pim,

i don't have an answer for you, but actually we are facing something that might be related and wanted to see if you heard from anyone on your issue.

we are getting hard errors running the 64 bit epicor with the 32 bit crystal reports.

we are trying to find out if:

1) is there is a 64 bit crystal reports version or

2) does someone know how to make the 64 bit epicor (we're running 905.602) with the 32 bit crystal reports

john martin

--- In vantage@yahoogroups.com, Pim Zandbergen <P.Zandbergen@...> wrote:
>
> Recent Epicor versions come with what appears to be a native 64-bit
> client, named MfgSys64.exe. I tried it, and it works. Task Manager
> confirms this program indeed does not use WoW64, like MfgSys.exe does.
>
> But I don't see any reference to it. Is it official? Is it beta?
>
> From my knowledge of .Net, there is no such thing as a 32-bit or
> a 64-bit .Net application, but rather "true" .Net programs, which
> run on any architecture (the framework should handle that) and
> "not-so-true" .Net programs, ones that make calls to the win32 API.
>
> Apparently MfgSys.exe is marked as an application that calls the
> win32 API, and MfgSys64.exe as "true". But the real danger is that
> every .dll called needs to be clean as well. Is that the case for
> all Epicor and third party assemblies, like Crystal Reports?
>
> Also, I would assume that any report called from MfgSys64.exe
> would use 64-bit ODBC drivers if that report would use ODBC.
>
> Does anyone have more experience with this?
>
> Pim
>
It is official, we called support a while back and they actually told us to
use the 64bit one w/ our 64 bit clients.

*Jose C Gomez*
*Software Engineer*
*
*
*checkout my new blog <http://www.usdoingstuff.com> *
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*



On Tue, Jun 14, 2011 at 4:33 PM, jfmartin67 <jfmartin67@...> wrote:

>
>
> pim,
>
> i don't have an answer for you, but actually we are facing something that
> might be related and wanted to see if you heard from anyone on your issue.
>
> we are getting hard errors running the 64 bit epicor with the 32 bit
> crystal reports.
>
> we are trying to find out if:
>
> 1) is there is a 64 bit crystal reports version or
>
> 2) does someone know how to make the 64 bit epicor (we're running 905.602)
> with the 32 bit crystal reports
>
> john martin
>
>
> --- In vantage@yahoogroups.com, Pim Zandbergen <P.Zandbergen@...> wrote:
> >
> > Recent Epicor versions come with what appears to be a native 64-bit
> > client, named MfgSys64.exe. I tried it, and it works. Task Manager
> > confirms this program indeed does not use WoW64, like MfgSys.exe does.
> >
> > But I don't see any reference to it. Is it official? Is it beta?
> >
> > From my knowledge of .Net, there is no such thing as a 32-bit or
> > a 64-bit .Net application, but rather "true" .Net programs, which
> > run on any architecture (the framework should handle that) and
> > "not-so-true" .Net programs, ones that make calls to the win32 API.
> >
> > Apparently MfgSys.exe is marked as an application that calls the
> > win32 API, and MfgSys64.exe as "true". But the real danger is that
> > every .dll called needs to be clean as well. Is that the case for
> > all Epicor and third party assemblies, like Crystal Reports?
> >
> > Also, I would assume that any report called from MfgSys64.exe
> > would use 64-bit ODBC drivers if that report would use ODBC.
> >
> > Does anyone have more experience with this?
> >
> > Pim
> >
>
>
>


[Non-text portions of this message have been removed]