Page 1 of 1
					
				Systemmemory
				Posted: 10 May 2011, 12:56
				by Fishbone222
				I have tested the software on different systems.
Here I noticed that the startup fails on systems with less than 2GB of RAM. It does not matter which version of .net Framework is installed.
Will there be another future version that will run on systems with less than 2 GB of RAM.
			 
			
					
				Re: Systemmemory
				Posted: 10 May 2011, 14:23
				by yani
				What happens when you have more than 2GB? Program crashes? Doesn't connect?
I don't think that there is any problem with the memory requirements. I regularly test with my ASUS 900HA Netbook which is running Vista and has only 1GB of memory. I've NEVER had any problem with it. I also test with an old DELL Latitude which is running XP and has only 256MB of memory. Never had any memory problems with it either.
			 
			
					
				Re: Systemmemory
				Posted: 11 May 2011, 07:30
				by Fishbone222
				Every Version until 2.7.2 works fine on all tested systems.
The Version 2.8.x doesn't start up. Some times there is a message equal to that which is shown if the false/none framework installed. Other times  the program hangs up. If I upgrade the systemmemory to minimum 2gb ram every thing is allright.
I have Windows 7 Home Premium on all systems.
I`ve used dotnetfx 1.1 sp1; 2.0 sp1/2; 3.5 sp1 and 4.0.
			 
			
					
				Re: Systemmemory
				Posted: 12 May 2011, 12:13
				by sixpotman
				Windows 7 requires
1 gig of ram for 32bit Operating System
2 gig of ram for 64bit Operating System
John
			 
			
					
				Re: Systemmemory
				Posted: 12 May 2011, 15:11
				by yani
				Is it a 64bit or 32bit Windows 7?
There was a report from another user with HP version of 64bit Windows 7 who has similar problem with the memory.
Multiecuscan usually uses ~20-30MB of RAM.
			 
			
					
				Re: Systemmemory
				Posted: 12 May 2011, 21:34
				by Fishbone222
				Yes that are both x64 Systems.
I`ll check again with windows kompatiblity settings and vm.
			 
			
					
				Re: Systemmemory
				Posted: 13 May 2011, 14:20
				by yani
				Ok, I found the problem.
It happens with the x64 version of Windows 7...
Will try to post a fixed release in the next few days.