definately interested. Once I complete the vision stuff and put out the next version I will email you. Any ideas on how to parse differently, I am definitely interested in.

@d.cochran,

David, couple of things I am wondering. I run MS SQL server 2005 on a dedicated server where I keep all my databases. I also run an IIS 7.5 webserver and connect to it for my DNN sites (sql databases). What I am after is;

any problems running your database on SQL Server 2005? Shouldn't be but just checking.

Also I would like the ability to install EZ-AI on a different drive other than C:. I see you are pushing this through the pipeline quickly but how about giving us a custom install option?

So I run a rack of Wintel servers with some virtual Linux security servers in my house. All the physical servers running 2008(R3). So I think I might fire up a virtual server and put your program on there to access it through the network. Have you had the opportunity to test this on various OS'? 2008(R3) by chance?

Really appreciate your knowledge and sharing this program.

I dont see any reason that it would have any issue running on SQL 2005. It uses the System.Data.SqlClient components to access the SQL server and there is a configuration option for the sql connection in the config file, but I haven't tested with other versions of SQL server. If you run into issues, I could easily make a configuration option that uses 2005.

I agree about running from a different drive letter or different path all together. Right now, this is setup to run from C:\EZ-AI. This would require an install application which is on my todo list.

As far as running on different server platforms...
Merne is running this on Windows 7 without any issue. I am running on Windows 8.1 without any issues. Merne is running with IIS7 and the only issue he had was that he had to set the application pool execution authority to run as his account. Windows 8 doesn't have this issue.

I dont see a reason why it wouldnt run on server 2008. The only thing that I can think of that might be affected is the System.SpeachRecognition stuff, but I am pretty sure that 2008 R3 has it in there.

If you would like to setup a VM with 2008 on it, and put TeamViewer on it, I would be happy to perform the install and see if there are any issues with your config.

@Pacowang,

I see that you have the MendelMax 1.5. These guys are about 10 miles from my house. Great group of guys and a gal at the front desk. We also have a 1.5 at the makergroup that I am a member of. Its rock solid. Just creeping and found that. Good choice.

Ok, when I get out of the hangar and back to the house I'll get one spun up. I'm running it on Win 7 now. I have a virtual Win 10 Technical running, I'll try it there to.

In the end I would like this on a dedicated server. That would be the best solution.

Thanks

I understand completely. It is possible to have some parts running server side and others running client side. The client side stuff would be things like the roborealm and the actual app. The server side would be the chat client and database. I have included configurable items in the config file to point to other servers if you decide to run it like that. I did a bit of planning ahead Let me know if you have any issues. I would be interested in knowing so that I can make some changes where needed.

Thanks pacowang

Will do

@Pacowang, The only part that I see you having issues with in running it on its own server is the outdoor navigation mode. It needs to use the GPS which is client based and the server to store the route in the database. If you have wifi connection still while outside, you wouldn't have an issue. If you built a tunnel from your cellphone which is attached to the robot and your home network, that too could eliminate the issue. Just thinking out loud about running EZ-AI database off of a dedicated server. It would be easy though to have a local database that was replicated from the server, and I could handle the System.Data.SqlClient.Connection in a try/catch to first try the server location and then the client location for a database....