Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-06 Thread Martin Schreiber
On Monday 05 January 2015 22:12:29 Bill Buzzell wrote: I have no problem if I create the repo in Github from the web interface and then clone it. Haven't figured out how to create from a local copy and push it up as a new repo. Open the local repository in MSEgit, add the remote repository in

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-06 Thread Martin Schreiber
On Tuesday 06 January 2015 08:58:34 Martin Schreiber wrote: On Monday 05 January 2015 21:00:25 Bill Buzzell wrote: I have a general Git question: I deleted the /samples/communication/commchannel​ directory intending to pull from origin. Apparently I went about it the wrong way. I tried

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-06 Thread Martin Schreiber
On Tuesday 06 January 2015 08:58:34 Martin Schreiber wrote: On Monday 05 January 2015 21:00:25 Bill Buzzell wrote: I have a general Git question: I deleted the /samples/communication/commchannel​ directory intending to pull from origin. Apparently I went about it the wrong way. I tried

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-06 Thread Bill Buzzell
Hi Martin, I am unable to delete my local Mse git repo. If I open it from MseGit is complains with unable to create file e://msegitmsegitrepo.sta.tmp35208 operation could not be completed because the volume is dirty. Run chkdsk. My permissions are as administrator. ?? I ran chkdsk, it reports

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-06 Thread Bill Buzzell
Ahhh. Looks like a hard drive failure. Please disregard my last post. Ouch! On Tue, Jan 6, 2015 at 11:59 AM, Bill Buzzell captbill...@gmail.com wrote: Hi Martin, I am unable to delete my local Mse git repo. If I open it from MseGit is complains with unable to create file

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Martin Schreiber
On Monday 05 January 2015 21:00:25 Bill Buzzell wrote: I have a general Git question: I deleted the /samples/communication/commchannel​ directory intending to pull from origin. Apparently I went about it the wrong way. I tried to Pull, fetch all, fetch, fetch from origin, and merge... all to

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Martin Schreiber
Her you go. I will try to look if I can notice anything as well. It searches for *.a (smartlinking archive) files. Do you compile with -CX -XX? Please try without, delete all *.ppu, *.o and *.a files in mseide-msegui and mseuniverse clone directories. Can be done for example by git clean -f

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Martin Schreiber
On Monday 05 January 2015 11:15:04 Bill Buzzell wrote: I did git clean -f -x successfully, then built the Mseide.prj using this command string: E:\FPC\2.6.4\bin\i386-win32\fpc.exe -omseide.exe -FuE:\mse-git\lib\addon\* -FiE:\mse-git\lib\addon\* -FuE:\mse-git\lib\common\kernel\windows

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
Ok. The rs232.prj is working. I must enter '\\.\COM34', as previously but it is communicating send and receive now. You should also clean the mseuniverse checkout. Yes, I did both again and seems to have fixed it. Thanks Martin On Mon, Jan 5, 2015 at 5:20 AM, Martin Schreiber

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Martin Schreiber
On Monday 05 January 2015 09:15:53 Bill Buzzell wrote: Please git pull the newest versions of mseide-msegui and mseuniverse from Gitorious and try to compile wit 'Project'-'Build' instead of 'Project'-'Make'. No luck. Still the same errors. Please add -vt to

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
Please add -vt to 'Project'-'Options'-'Make'-'Make Options' Done. Looks like the same output as previously: An unhandled exception occurred at $0044EEAD : EReadError : Ancestor class for tstatfile1 not found. $0044EEAD TREADER__READCOMPONENT, line 6042 of

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Martin Schreiber
On Monday 05 January 2015 09:52:37 Bill Buzzell wrote: Please add -vt to 'Project'-'Options'-'Make'-'Make Options' Done. Looks like the same output as previously: Have you checked the compiler messages ('View'-'Messages')? -vt does not change compilation, it produces info about what files it

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
Please git pull the newest versions of mseide-msegui and mseuniverse from Gitorious and try to compile wit 'Project'-'Build' instead of 'Project'-'Make'. No luck. Still the same errors. On Mon, Jan 5, 2015 at 2:35 AM, Martin Schreiber mse00...@gmail.com wrote: On Monday 05 January 2015

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Martin Schreiber
On Monday 05 January 2015 09:15:53 Bill Buzzell wrote: Please git pull the newest versions of mseide-msegui and mseuniverse from Gitorious and try to compile wit 'Project'-'Build' instead of 'Project'-'Make'. No luck. Still the same errors. Can somebody reproduce Bill's problem? Martin

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
Aha. I was wondering where that window went. I looked it over and see lots of 'not found' listings. Would you like to see it? Very large. Zip file? Thanks On Mon, Jan 5, 2015 at 4:03 AM, Martin Schreiber mse00...@gmail.com wrote: On Monday 05 January 2015 09:52:37 Bill Buzzell wrote: Please

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Fred van Stappen
Same here, works fine. It seems to me the problem is because Bill uses fpc 2.7.x On Monday 05 January 2015 11:33:50 misu kun wrote: i can not reproduce , works fine -- Dive

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Martin Schreiber
On Monday 05 January 2015 13:00:19 Fred van Stappen wrote: Same here, works fine. It seems to me the problem is because Bill uses fpc 2.7.x He uses 2.6.4 now: Configfile search: fpc.cfg Configfile search: E:\FPC\2.6.4\bin\i386-win32\fpc.cfg Reading options from file

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Fred van Stappen
From: mse00...@gmail.com To: mseide-msegui-talk@lists.sourceforge.net Date: Mon, 5 Jan 2015 13:10:30 +0100 Subject: Re: [MSEide-MSEgui-talk] Serial Comm errors On Monday 05 January 2015 13:00:19 Fred van Stappen wrote: Same here, works fine. It seems to me the problem is because Bill

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
Add your public SSH key to https://gitorious.org/~your gitorious login name/ssh-keys I do have an SSH key set up (GitHub) but looked and noticed it has never been used. Looks like the Options: git command maybe needs the login phrase. Hum, i do not think you need to enter a full login for each

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
I have a general Git question: I deleted the /samples/communication/commchannel​ directory intending to pull from origin. Apparently I went about it the wrong way. I tried to Pull, fetch all, fetch, fetch from origin, and merge... all to no avail. Also tried to revert from all. Is there an easy

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Fred van Stappen
-msegui-talk@lists.sourceforge.net Subject: Re: [MSEide-MSEgui-talk] Serial Comm errors I have a general Git question: I deleted the /samples/communication/commchannel​ directory intending to pull from origin. Apparently I went about it the wrong way.I tried to Pull, fetch all, fetch, fetch from

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
and the commit f44ebc3cc1152f9e5db86d77648c888daa23f3f3 adds '\\.\' if necessary: On Mon, Jan 5, 2015 at 7:33 AM, Fred van Stappen fi...@hotmail.com wrote: From: mse00...@gmail.com To: mseide-msegui-talk@lists.sourceforge.net Date: Mon, 5 Jan 2015 13:10:30 +0100 Subject: Re: [MSEide-MSEgui-talk

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
: [MSEide-MSEgui-talk] Serial Comm errors I have a general Git question: I deleted the /samples/communication/commchannel​ directory intending to pull from origin. Apparently I went about it the wrong way. I tried to Pull, fetch all, fetch, fetch from origin, and merge... all to no avail. Also

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Fred van Stappen
How do you get MseGit to auto-login to push to a remote? Options git command maybe? What i do (and trust me (or ask it to Martin) it was absolutely NOT easy to me to do my first push to Gitorious). 1) Create a account + password to Gitorious. 2) Run MSEgit and in File menu = open your

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Bill Buzzell
I have no problem if I create the repo in Github from the web interface and then clone it. Haven't figured out how to create from a local copy and push it up as a new repo. I just don't like having to enter a full login every time I do a small commit. On Mon, Jan 5, 2015 at 4:05 PM, Fred van

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-05 Thread Fred van Stappen
Jan 2015 22:19:39 +0100 Subject: Re: [MSEide-MSEgui-talk] Serial Comm errors I just don't like having to enter a full login every time I do a small commit Then you need to create a SSH key https://help.github.com/articles/generating-ssh-keys/ Add your public SSH key to https

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-04 Thread Bill Buzzell
I have updated to FPC 2.6.4 win32. I have updated with MseGit (Mse 3.7, Mse Universe). Everything seems well except the serial communication. All the comm demos refuse to compile with: An unhandled exception occurred at $0044EEAD : EReadError : Ancestor class for tstatfile1 not found. $0044EEAD

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-03 Thread Bill Buzzell
I tried that. No luck. Putty has no issue communicating. No problem though. I need to install the stable FPC unless you would like to me to investigate it some more. I am more interested in getting Mse running on TinyCore Linux. I'm close. Seem to be encountering a bad memory leak. I will have

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-03 Thread Bill Buzzell
I am having an issue with GDB it seems. If I do view|debugger no window appears, unless it should be 'target console', which is there. I can step through the code but no output is appearing anywhere. On Sat, Jan 3, 2015 at 4:35 AM, Bill Buzzell captbill...@gmail.com wrote: Yes, sorry. It fails

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-03 Thread Bill Buzzell
Yes, sorry. It fails gracefully with the exception dialog : 'port:tsercommcomp: Cannot open com port', then returns to the application no problem. COM1 seems to work fine, if that helps. On Sat, Jan 3, 2015 at 4:17 AM, Martin Schreiber mse00...@gmail.com wrote: On Saturday 03 January 2015

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-03 Thread Martin Schreiber
On 03.01.2015 10:46, Bill Buzzell wrote: I am having an issue with GDB it seems. If I do view|debugger no window appears, unless it should be 'target console', which is there. No, the debugger window means the debugger tool buttons normally located below the main menu. Debugger output windows

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-03 Thread Martin Schreiber
On Saturday 03 January 2015 09:57:54 Bill Buzzell wrote: I tried that. No luck. Putty has no issue communicating. No problem though. I need to install the stable FPC unless you would like to me to investigate it some more. Any error messages when you click on 'active'? Martin

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-02 Thread Bill Buzzell
Can you explain more? I don't understand. I reinstalled Mseide and the prior install (which is still there) was being detected and remapping the correct directories was the initial problem. Then it complained because the tframetemplate.paintoverlay implementation was different from the

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-02 Thread Martin Schreiber
On Friday 02 January 2015 05:39:05 Bill Buzzell wrote: Bill Buzzell captbill279@... writes: I found my issue. My settings were pointing to a previous install. Then I had an error with tframetemplate.paintoverlay (msegui.pas ln 5611). I added the default value to the framestateflagsty and it

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-02 Thread Martin Schreiber
On Friday 02 January 2015 03:08:49 Bill Buzzell wrote: Hi, I am getting errors trying to run the 'RS232.prj' in Mse Universe. Here is the output: * Free Pascal Compiler version 2.7.1 [2014/07/10] for i386* FPC trunk is not supported, please use FPC 2.6.4 or 2.6.5 (SVN branch

Re: [MSEide-MSEgui-talk] Serial Comm errors

2015-01-01 Thread Bill Buzzell
Bill Buzzell captbill279@... writes: I found my issue. My settings were pointing to a previous install. Then I had an error with tframetemplate.paintoverlay (msegui.pas ln 5611). I added the default value to the framestateflagsty and it builds now. procedure tframetemplate.paintoverlay(const