Re: [Oorexx-devel] I/O again
Ok, I have one more thing to try. I'm starting to think this might be a memory-management issue, not an I/O issue. The buffer used for the I/O is one of the few places in the ooRexx code where malloc() is used to allocate memory. In fact, it wouldn't surprise me if this is the first malloc request done by the interpreter. I'm starting to wonder if the overlay might be related to some sort of activity taking place to manage the .exe program in the window, and there is some sort of race condition that occurs with that memory when enter is pressed. I've sent Mark a patch that changes the mechanism used to allocate this buffer and we'll give it one more try. If this fails, then I'm am totally out of ideas. We're running out of things to try changing. Rick On Mon, Apr 27, 2009 at 4:33 AM, Mike Cowlishaw m...@uk.ibm.com wrote: Sorry to report that the dreaded 'r' still appears with Rick's latest (build 4507). sigh Maybe best to just document this in the readme as a probable Windows problem? Everything else is working beautifully! Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
I've applied the patch and am building the install package right now. I'll let you know when it's ready Mike. Rick, I'm hopeful about this. On Windows I really think we should only use GlobalAlloc and its relatives instead of malloc. The only time I use malloc is when I'm going to free it right there within the same function. -- Mark Miesfeld On Mon, Apr 27, 2009 at 4:40 AM, Rick McGuire object.r...@gmail.com wrote: Ok, I have one more thing to try. I'm starting to think this might be a memory-management issue, not an I/O issue. The buffer used for the I/O is one of the few places in the ooRexx code where malloc() is used to allocate memory. In fact, it wouldn't surprise me if this is the first malloc request done by the interpreter. I'm starting to wonder if the overlay might be related to some sort of activity taking place to manage the .exe program in the window, and there is some sort of race condition that occurs with that memory when enter is pressed. I've sent Mark a patch that changes the mechanism used to allocate this buffer and we'll give it one more try. If this fails, then I'm am totally out of ideas. We're running out of things to try changing. Rick On Mon, Apr 27, 2009 at 4:33 AM, Mike Cowlishaw m...@uk.ibm.com wrote: Sorry to report that the dreaded 'r' still appears with Rick's latest (build 4507). sigh Maybe best to just document this in the readme as a probable Windows problem? Everything else is working beautifully! Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Okay, it's built. I sent Mike the link to get it. -- Mark Miesfeld On Mon, Apr 27, 2009 at 5:48 AM, Mark Miesfeld miesf...@gmail.com wrote: I've applied the patch and am building the install package right now. I'll let you know when it's ready Mike. Rick, I'm hopeful about this. On Windows I really think we should only use GlobalAlloc and its relatives instead of malloc. The only time I use malloc is when I'm going to free it right there within the same function. -- Mark Miesfeld On Mon, Apr 27, 2009 at 4:40 AM, Rick McGuire object.r...@gmail.com wrote: Ok, I have one more thing to try. I'm starting to think this might be a memory-management issue, not an I/O issue. The buffer used for the I/O is one of the few places in the ooRexx code where malloc() is used to allocate memory. In fact, it wouldn't surprise me if this is the first malloc request done by the interpreter. I'm starting to wonder if the overlay might be related to some sort of activity taking place to manage the .exe program in the window, and there is some sort of race condition that occurs with that memory when enter is pressed. I've sent Mark a patch that changes the mechanism used to allocate this buffer and we'll give it one more try. If this fails, then I'm am totally out of ideas. We're running out of things to try changing. Rick On Mon, Apr 27, 2009 at 4:33 AM, Mike Cowlishaw m...@uk.ibm.com wrote: Sorry to report that the dreaded 'r' still appears with Rick's latest (build 4507). sigh Maybe best to just document this in the readme as a probable Windows problem? Everything else is working beautifully! Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say sa Der Befehl RAY ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: 1. First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit 2. Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) 3. Open a new command line window 4. Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here is another run, where this error occurs for the exit statement! Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit Der Befehl RXIT ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT HTH, ---rony -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Rick On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld miesf...@gmail.com wrote: Well, okay. By pasting lines into a console window, I got RXIT: D:\Interpreters\Rexxrexx -v Open Object Rexx Version 4.0.0 Build date: Apr 20 2009 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html D:\Interpreters\Rexxrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Interpreters\Rexxrexxtry REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT Prior to that I tried typing the lines in the console window and had no luck. When I pasted the lines it was the same console window I had been using before. In the pasting case, the keyboard buffer would have data in it when the second interpreter started. -- Mark Miesfeld On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa Der Befehl RAY ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) Open a new command line window Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here is another run, where this error occurs for the exit statement! Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit Der Befehl RXIT ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT HTH, ---rony -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial
Re: [Oorexx-devel] I/O again
I'm just about to try that. I was seeing how reliable it was that I saw RXIT. Seems to be ever time when I paste the text into the window. I think another key is that Rony says he sees it when: immediately issuing a say statement (typing while rexxtry.rex starts up). So here, the keyboard buffer has data in it (probably, depending on fast he is typing) when the interpreter starts. I'll post as soon as I try it with the patched version. -- Mark Miesfeld. On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire object.r...@gmail.com wrote: Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Rick On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld miesf...@gmail.com wrote: Well, okay. By pasting lines into a console window, I got RXIT: D:\Interpreters\Rexxrexx -v Open Object Rexx Version 4.0.0 Build date: Apr 20 2009 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html D:\Interpreters\Rexxrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Interpreters\Rexxrexxtry REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT Prior to that I tried typing the lines in the console window and had no luck. When I pasted the lines it was the same console window I had been using before. In the pasting case, the keyboard buffer would have data in it when the second interpreter started. -- Mark Miesfeld On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa Der Befehl RAY ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) Open a new command line window Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here is another run, where this error occurs for the exit statement! Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit Der Befehl RXIT ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT HTH, ---rony -- Crystal Reports #45; New
Re: [Oorexx-devel] I/O again
Hmmm, this is starting to push the issue back to being an I/O problem. Here's something to try. In SysFile::setStdIn(), try commenting out the line _setMode(fileHandle, _O_BINARY); and see if you can recreate the problem. I'm wondering if switching the mode while characters are already in the buffer are causing this problem. This line was added because redirected input was causing problems. Rick On Mon, Apr 27, 2009 at 10:51 AM, Mark Miesfeld miesf...@gmail.com wrote: I'm just about to try that. I was seeing how reliable it was that I saw RXIT. Seems to be ever time when I paste the text into the window. I think another key is that Rony says he sees it when: immediately issuing a say statement (typing while rexxtry.rex starts up). So here, the keyboard buffer has data in it (probably, depending on fast he is typing) when the interpreter starts. I'll post as soon as I try it with the patched version. -- Mark Miesfeld. On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire object.r...@gmail.com wrote: Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Rick On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld miesf...@gmail.com wrote: Well, okay. By pasting lines into a console window, I got RXIT: D:\Interpreters\Rexxrexx -v Open Object Rexx Version 4.0.0 Build date: Apr 20 2009 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html D:\Interpreters\Rexxrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Interpreters\Rexxrexxtry REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT Prior to that I tried typing the lines in the console window and had no luck. When I pasted the lines it was the same console window I had been using before. In the pasting case, the keyboard buffer would have data in it when the second interpreter started. -- Mark Miesfeld On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa Der Befehl RAY ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) Open a new command line window Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here is another run, where this error occurs for the exit statement! Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go
Re: [Oorexx-devel] I/O again
On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire object.r...@gmail.com wrote: Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Yes, I just tried with the patched build I did earlier this morning and get the same RXIT: E:\rexx -v Open Object Rexx Version 4.0.0 Build date: Apr 27 2009 Addressing Mode: 32 E:\rexxtry say hallo HALLO ... rexxtry.rex on WindowsNT E:\rexxtry REXX-ooRexx_4.0.0(MT) 6.03 27 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few...Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT When I paste the text in, everything runs and ends up on the line with exit already on it. When I then hit ENTER, I get the RXIT. I just tried not hitting ENTER, but instead using the arrow key to move to the start of the line and retype 'exit' I still get the RXIT. I haven't tried this 'pasting' think on 3.2.0. Going to do that next. -- Mark Miesfeld -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Okay, I'll try that. Tried with 3.2.0 about 10 times and it never happened. On 4.0.0, it happens for me every single time I paste the lines into the console window. -- Mark Miesfeld On Mon, Apr 27, 2009 at 8:01 AM, Rick McGuire object.r...@gmail.com wrote: Hmmm, this is starting to push the issue back to being an I/O problem. Here's something to try. In SysFile::setStdIn(), try commenting out the line _setMode(fileHandle, _O_BINARY); and see if you can recreate the problem. I'm wondering if switching the mode while characters are already in the buffer are causing this problem. This line was added because redirected input was causing problems. Rick On Mon, Apr 27, 2009 at 10:51 AM, Mark Miesfeld miesf...@gmail.com wrote: I'm just about to try that. I was seeing how reliable it was that I saw RXIT. Seems to be ever time when I paste the text into the window. I think another key is that Rony says he sees it when: immediately issuing a say statement (typing while rexxtry.rex starts up). So here, the keyboard buffer has data in it (probably, depending on fast he is typing) when the interpreter starts. I'll post as soon as I try it with the patched version. -- Mark Miesfeld. On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire object.r...@gmail.com wrote: Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Rick On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld miesf...@gmail.com wrote: Well, okay. By pasting lines into a console window, I got RXIT: D:\Interpreters\Rexxrexx -v Open Object Rexx Version 4.0.0 Build date: Apr 20 2009 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html D:\Interpreters\Rexxrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Interpreters\Rexxrexxtry REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT Prior to that I tried typing the lines in the console window and had no luck. When I pasted the lines it was the same console window I had been using before. In the pasting case, the keyboard buffer would have data in it when the second interpreter started. -- Mark Miesfeld On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa Der Befehl RAY ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) Open a new command line window Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here is another run, where this error occurs for the exit statement! Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex
Re: [Oorexx-devel] I/O again
Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. Rick On Mon, Apr 27, 2009 at 11:05 AM, Mark Miesfeld miesf...@gmail.com wrote: Okay, I'll try that. Tried with 3.2.0 about 10 times and it never happened. On 4.0.0, it happens for me every single time I paste the lines into the console window. -- Mark Miesfeld On Mon, Apr 27, 2009 at 8:01 AM, Rick McGuire object.r...@gmail.com wrote: Hmmm, this is starting to push the issue back to being an I/O problem. Here's something to try. In SysFile::setStdIn(), try commenting out the line _setMode(fileHandle, _O_BINARY); and see if you can recreate the problem. I'm wondering if switching the mode while characters are already in the buffer are causing this problem. This line was added because redirected input was causing problems. Rick On Mon, Apr 27, 2009 at 10:51 AM, Mark Miesfeld miesf...@gmail.com wrote: I'm just about to try that. I was seeing how reliable it was that I saw RXIT. Seems to be ever time when I paste the text into the window. I think another key is that Rony says he sees it when: immediately issuing a say statement (typing while rexxtry.rex starts up). So here, the keyboard buffer has data in it (probably, depending on fast he is typing) when the interpreter starts. I'll post as soon as I try it with the patched version. -- Mark Miesfeld. On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire object.r...@gmail.com wrote: Have you tried reproducing using the patched version? I tried this technique this morning both the unpatched and official beta version and didn't get any failures. Rick On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld miesf...@gmail.com wrote: Well, okay. By pasting lines into a console window, I got RXIT: D:\Interpreters\Rexxrexx -v Open Object Rexx Version 4.0.0 Build date: Apr 20 2009 Addressing Mode: 32 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2009. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html D:\Interpreters\Rexxrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Interpreters\Rexxrexxtry REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa SA ... rexxtry.rex on WindowsNT rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. exit 'RXIT' is not recognized as an internal or external command, operable program or batch file. rc = 1 rexxtry.rex on WindowsNT Prior to that I tried typing the lines in the console window and had no luck. When I pasted the lines it was the same console window I had been using before. In the pasting case, the keyboard buffer would have data in it when the second interpreter started. -- Mark Miesfeld On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher rony.flatsc...@wu-wien.ac.at wrote: Pretty regularly I can get that problem too when opening a command line window, and first thing I would do is using rexxtry and immediately issuing a say statement (typing while rexxtry.rex starts up). Here's an example that works *quite reliably* for me: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Dokumente und Einstellungen\Administratorrexxtry say hallo HALLO ... rexxtry.rex on WindowsNT D:\Dokumente und Einstellungen\Administratorrexxtry REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 rexxtry.rex lets you interactively try REXX statements. Each string is executed when you hit Enter. Enter 'call tell' for a description of the features. Go on - try a few... Enter 'exit' to end. say sa Der Befehl RAY ist entweder falsch geschrieben oder konnte nicht gefunden werden. rc = 1 rexxtry.rex on WindowsNT Here is what maybe work for you: First copy the following lines into the clipboard (note there is a trailing blank line): rexxtry say hallo rexxtry say sa exit Make sure no Rexx program runs, and no command line window is open in which a Rexx program ran (not sure whether that is really necessary, but who knows) Open a new command line window Just paste the above lines into the window; if necessary repeat steps 2 through 4 Eventually (within ten attempts) the error comes up again (although I might have waited in between invocations, after having all command line windows closed). Here
Re: [Oorexx-devel] I/O again
On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire object.r...@gmail.com wrote: Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); in setStdIn and it didn't seem to help. -- Mark Miesfeld -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
This is useful. I now have a consistent means of reproducing this, I'm able to gather a little more debug info. Unfortunately, what I've gotten so far just confirms what I already new...that the bogus character is coming from the C runtime routine. RIck On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld miesf...@gmail.com wrote: On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire object.r...@gmail.com wrote: Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); in setStdIn and it didn't seem to help. -- Mark Miesfeld -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again .. using Rexxtry
I hadn't thought of trying Rexxtry. Thanks Rony! An even simpler scenario: start Rexxtry, then just type a single letter command (and Enter) that is valid and does nothing (so returns very fast) (I have a c.rex that contains only a comment), and repeat, fast. Below is what I just got --- almost *every* 'c' command got converted to 'r' (which invokes r.rex - remind.rex for me, which is invalid on its own hence the message).This seems to be much more repeatable than in my elap program. [Strangely .. then got in a mode where each empty command went very slow .. 0.5 seconds perhaps .. and did not fail. With some disk thrashing.] All this with today's build. Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT c rc = 0 .. rexxtry.rex on WindowsNT c rc = 0 .. rexxtry.rex on WindowsNT c Remind needs a time (in minutes) rc = 0 .. rexxtry.rex on WindowsNT Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
I think I've fixed this! A big thanks to Rony...his method for reproducing this was 100% effective once Mark gave me the key to getting it to work. The problem only seemed to occur if our buffering is turned off for stdin. When buffering was turned off, I would consistently see the bogus character when _read() was called for the first line. With buffering turned on, the _read() call would generally retrieve up to the next complete line in one call and all of the characters look good. Now comes the concrete test...seeing if this works for Mike! Rick On Mon, Apr 27, 2009 at 11:28 AM, Rick McGuire object.r...@gmail.com wrote: This is useful. I now have a consistent means of reproducing this, I'm able to gather a little more debug info. Unfortunately, what I've gotten so far just confirms what I already new...that the bogus character is coming from the C runtime routine. RIck On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld miesf...@gmail.com wrote: On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire object.r...@gmail.com wrote: Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); in setStdIn and it didn't seem to help. -- Mark Miesfeld -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
I saw your commit and am building from trunk right now. (Guess I should have built from the beta.) But, I think trunk is good enough for Mike to just try. -- Mark Miesfeld On Mon, Apr 27, 2009 at 9:20 AM, Rick McGuire object.r...@gmail.com wrote: I think I've fixed this! A big thanks to Rony...his method for reproducing this was 100% effective once Mark gave me the key to getting it to work. The problem only seemed to occur if our buffering is turned off for stdin. When buffering was turned off, I would consistently see the bogus character when _read() was called for the first line. With buffering turned on, the _read() call would generally retrieve up to the next complete line in one call and all of the characters look good. Now comes the concrete test...seeing if this works for Mike! Rick On Mon, Apr 27, 2009 at 11:28 AM, Rick McGuire object.r...@gmail.com wrote: This is useful. I now have a consistent means of reproducing this, I'm able to gather a little more debug info. Unfortunately, what I've gotten so far just confirms what I already new...that the bogus character is coming from the C runtime routine. RIck On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld miesf...@gmail.com wrote: On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire object.r...@gmail.com wrote: Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); in setStdIn and it didn't seem to help. -- Mark Miesfeld -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
It's fixed for me also. The new test build is almost ready, I'll let Mike know as soon as it is available. -- Mark Miesfeld On Mon, Apr 27, 2009 at 9:20 AM, Rick McGuire object.r...@gmail.com wrote: I think I've fixed this! A big thanks to Rony...his method for reproducing this was 100% effective once Mark gave me the key to getting it to work. The problem only seemed to occur if our buffering is turned off for stdin. When buffering was turned off, I would consistently see the bogus character when _read() was called for the first line. With buffering turned on, the _read() call would generally retrieve up to the next complete line in one call and all of the characters look good. Now comes the concrete test...seeing if this works for Mike! Rick On Mon, Apr 27, 2009 at 11:28 AM, Rick McGuire object.r...@gmail.com wrote: This is useful. I now have a consistent means of reproducing this, I'm able to gather a little more debug info. Unfortunately, what I've gotten so far just confirms what I already new...that the bogus character is coming from the C runtime routine. RIck On Mon, Apr 27, 2009 at 11:17 AM, Mark Miesfeld miesf...@gmail.com wrote: On Mon, Apr 27, 2009 at 8:09 AM, Rick McGuire object.r...@gmail.com wrote: Ok, I've got the magic incantation correct now too. The key was not picking up the EOL for the exit command but physically hitting enter. I seem able to reproduce this reliably now too. That's good. I tried commenting out _setMode(fileHandle, _O_BINARY); in setStdIn and it didn't seem to help. -- Mark Miesfeld -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Well, installed latest (Rick new file I/O) but unfortunately had to back it out almost immediately, because now stream 'query datetime' and 'query size' both return empty string for a directory. The former I can work around (and did when it changed a week or two ago), but the latter I have several hundred instances of So I then went back to Mark's VS 2008 version ... ... and immediate got a 'r' overlay, on the first parse pull after install. sigh Staying with that one for now, however. Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
Sigh, this is why I was really hoping the 2008 conversion would make the problem go away. I figured it would take a couple of iterations to get all of the conversion bugs worked out. I think I know how to fix this one, so I'll probably have a fix available shortly. Rick On Sun, Apr 26, 2009 at 8:15 AM, Mike Cowlishaw m...@uk.ibm.com wrote: Well, installed latest (Rick new file I/O) but unfortunately had to back it out almost immediately, because now stream 'query datetime' and 'query size' both return empty string for a directory. The former I can work around (and did when it changed a week or two ago), but the latter I have several hundred instances of So I then went back to Mark's VS 2008 version ... ... and immediate got a 'r' overlay, on the first parse pull after install. sigh Staying with that one for now, however. Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
I know exactly what you mean. The first few times I saw the error 'RAY' is not recognized as an internal or external command, operable program or batch file. I thought I'd just mistyped something. I don't even have any theories on how/why this is happenng based on the symptoms we're seeing. I have enough debug evidence from the times I have been able to reproduce this to be very certain the bad character is coming directly from the CRT _read() function. At least in my situation, everything was single threaded. I do have a questions for you Mike. I've only ever seen this on a first read. Have you ever seen the overlay occur in any place other than the first character or a line? Have you noticed any pattern as to things you might have done *before* the command with the overlay? Mark, you might want to spin a new install package from the sandbox. I've fixed the query size/query datetime problems for directories. Rick On Sun, Apr 26, 2009 at 12:52 PM, Mike Cowlishaw m...@uk.ibm.com wrote: Yeah .. sorry about that. I was really hoping VS2008 fixed it, but always knew that 'not seeing the dreaded r' was a negative report, not a definitive one. Darn thing seems almost determined to hide itself. I'm just glad you (Rick) saw it too, as I'm sure no one would believe me otherwise! Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Rick McGuire object.r...@gmail.com wrote on 26/04/2009 13:31:02: Rick McGuire object.r...@gmail.com 26/04/2009 13:31 Please respond to Open Object Rexx Developer Mailing List oorexx-devel@lists.sourceforge.net To Open Object Rexx Developer Mailing List oorexx-devel@lists.sourceforge.net cc Subject Re: [Oorexx-devel] I/O again Sigh, this is why I was really hoping the 2008 conversion would make the problem go away. I figured it would take a couple of iterations to get all of the conversion bugs worked out. I think I know how to fix this one, so I'll probably have a fix available shortly. Rick On Sun, Apr 26, 2009 at 8:15 AM, Mike Cowlishaw m...@uk.ibm.com wrote: Well, installed latest (Rick new file I/O) but unfortunately had to back it out almost immediately, because now stream 'query datetime' and 'query size' both return empty string for a directory. The former I can work around (and did when it changed a week or two ago), but the latter I have several hundred instances of So I then went back to Mark's VS 2008 version ... ... and immediate got a 'r' overlay, on the first parse pull after install. sigh Staying with that one for now, however. Mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Mike Cowlishaw, IBM Fellow http://bit.ly/mfc IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I/O again
On Sun, Apr 26, 2009 at 11:01 AM, Rick McGuire object.r...@gmail.com wrote: Mark, you might want to spin a new install package from the sandbox. I've fixed the query size/query datetime problems for directories. Actually I just started that, should be done shortly. Great ... send me the coords when done and I'll run with that from first thing tomorrow morning (UK time). Done for this evening, here ... fresh air/refreshment calls ... :-) Mike Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
