On Thu, 3 Dec 2020, Basil Hussain wrote:
However, ucSim seems to hang when I try this! All I get is these startup messages:
I do not have too much experience with windows, but on unix, this is normal. This is the behavior of the pipe, not the app. When first program opens one end of the pipe, it will be blocked by the OS. It waits to open other end. You have to start a program which opens other end of the pipe (in opposite direction of course), then the first app will be unlocked and able to continue. uCsim will open serial files in order they are specified in the command line. If they are pipes, you have to open them in the same order by other programs.
You can start your consumer and producer program first, and start uCsim after. This way, your outsider programs will be blocked first...
P.S. By the way, I thought maybe the fact I was running ucSim through ansicon (to get ANSI colour rendering on the Windows command prompt) was affecting it, but doing so without gives same results. It is annoying that ucSim has no way to run on Windows without making provisions to handle ANSI colour. The "no-color" -b command line option does not help, ucSim just spits out raw escape codes instead. Maybe I should file a feature request ticket...
I have tried ConEmu, win10 powershell and win10 cmd.exe. All of them looks to be OK in color mode and in bw (-b) mode as well.
win7 cdm.exe can not handle ansi, but with -b it works well too. Daniel _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
