[Mono-bugs] [Bug 50306][Blo] New - can't run exes

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 12 Jan 2004 05:54:22 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gonzalo@ximian.com.


--- shadow/50306	2004-01-12 05:54:22.000000000 -0500
+++ shadow/50306.tmp.21712	2004-01-12 05:54:22.000000000 -0500
@@ -0,0 +1,51 @@
+Bug#: 50306
+Product: Mono/Runtime
+Version: unspecified
+OS: unknown
+OS Details: Windows 2000 SP4
+Status: RESOLVED   
+Resolution: DUPLICATE
+Severity: Unknown
+Priority: Blocker
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: Mark_Kuschnir@yahoo.co.uk               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: can't run exes
+OtherBugsDependingOnThis: 50432[FIXED]
+Mono 0.28 on Windows 2000
+It is disappointing that I have never succeeded in running a 
+networked .NET prog using Mono on Windows 2000. We have tested this to 
+attempt to provide a chance of cross platform support.
+The current problem is that when I attempt to run my mono built progs I 
+get the following error:
+** Warning **: cannot find "C:\Program Files\Mono-0.28
+Trying to load app config file...
+I attempted to work around this by setting MONO_CFG_DIR. However, that 
+appeared to get stomped on by the next execution. I then tried to copy the 
+config stuff down into a second mono dir under etc\mono. That didn't work 
+either. I assume that it is the quotes that are breaking the runtime.
+In earlier versions these env vars were set in a .bat/.cmd file that one 
+could alter to make further attempts at execution. Having done a search 
+for them I can only assume that the .exes are calculating these env vars?
+It looks like there are not many people using/testing this on a Windows 
+2000 platform?
+------- Additional Comments From Mark_Kuschnir@yahoo.co.uk  2003-11-04 01:27 -------
+It is indeed a repeat of 50432. The solution in 50432 fixes this 
+problem. Sorry - I wasn't aware of files in the Windows directory 
+that modified the Mono runtime behaviour.
+*** This bug has been marked as a duplicate of 50432 ***