Strange problem with FPC 3.0.2 lazarus / 67-Windows ---------------------------------------------------------------------- even · 2017-04-03 01:43 I installed the 3.0.2 version of the free pascal compiler on my desktop（Windows 10-x64), there was a very strange question: when testing the console program, I entered a number in the console and press Enter, the cursor jumped back to the beginning of the line and didn't wrap to the next line, Ctrl+C break function didn't work too. please help ... ---------------------------------------------------------------------- Thaddy · 2017-04-03 04:51 I just tested the 3.0.2 fp.exe from the official distribution on windows 10.1 64 and it works fine. That version is a 32 bit executable one of course. To stop the ide you do not use ctrl-c but alt-x by the way. ctrl-c is intentionally intercepted. ---------------------------------------------------------------------- even · 2017-04-03 05:30 Thanks, I also tested version 3.0.0 and had the same results on my desktop, It seems "Enter" didn't wrap to new line in console program and Ctrl-C resulted "^C". But it does work fine on my laptop which is also window 10 x64. ---------------------------------------------------------------------- even · 2017-04-03 06:58 I found that someone on the Internet had the same problem, but there was no solution. ---------------------------------------------------------------------- Thaddy · 2017-04-03 08:22 I also built a 64 bit version. Same thing: everything works as expected on windows 10.1 64 bit. Try re-downloading and re-installing FPC and use only an official installer from here http://www.freepascal.org/download.var If you found something on the internet and it is NOT on this forum, plz provide a link: there's lots of bogus info around and you will find many experts - if not all - only here. ---------------------------------------------------------------------- even · 2017-04-04 06:46 I tried all the installation again according to your suggestions, unfortunately didn't work it out. Free pascal works fine except the Enter-wrap problem while debuging console program. Is it possible windows configuration caused this? The following is the same problem searched from web, sorry for the language http://www.imooc.com/wap/wenda/id/335248 ---------------------------------------------------------------------- enzo740 · 2017-08-29 06:19 Hello! I also have windows 10-x64 and the same thing happened to me. When I used the 'Run' option or when using the 'Debugger' with the 'Step Over' (F8), the console appeared, and when I had to type some number or character and pressed enter, the cursor was down and I received erroneous results. What I did to fix it was, add the 'Clrscr' command, which cleans the console. I am going  to attach the command line and how the console would look. Hope it works for you, regards! ---------------------------------------------------------------------- dsp2009 · 2018-01-07 18:53 thank you, enzo740! Your solution is works fine! The main thing is "uses crt" clause, in my case "clrscr" itself is not nesessary. I use "uses crt" in my program and this fixed the problem ---------------------------------------------------------------------- turrican · 2018-01-10 11:29 Quote from: enzo740 on August 29, 2017, 08:19:00 amHello! I also have windows 10-x64 and the same thing happened to me. When I used the 'Run' option or when using the 'Debugger' with the 'Step Over' (F8), the console appeared, and when I had to type some number or character and pressed enter, the cursor was down and I received erroneous results. What I did to fix it was, add the 'Clrscr' command, which cleans the console. I am going  to attach the command line and how the console would look. Hope it works for you, regards! Why are you using Write and not Writeln? i'm curious. ---------------------------------------------------------------------- molly · 2018-01-10 11:33 Quote from: turrican on January 10, 2018, 12:29:52 pmWhy are you using Write and not Writeln? i'm curious. To have the cursor wait for input directly after the colon ? (with a writeln it would appear on the next line). ---------------------------------------------------------------------- enzo740 · 2018-01-15 08:11 Quote from: dsp2009 on January 07, 2018, 07:53:03 pmthank you, enzo740! Your solution is works fine! The main thing is "uses crt" clause, in my case "clrscr" itself is not nesessary. I use "uses crt" in my program and this fixed the problem ohh, great! you're welcome!  Edit: I tried what you mentioned and it's true! It is not necessary to use the 'ClrScr'. Only with the 'Uses CRT' works! Thanks! ---------------------------------------------------------------------- enzo740 · 2018-01-15 08:23 Quote from: molly on January 10, 2018, 12:33:01 pmQuote from: turrican on January 10, 2018, 12:29:52 pmWhy are you using Write and not Writeln? i'm curious. To have the cursor wait for input directly after the colon ? (with a writeln it would appear on the next line). In effect, it is to keep the cursor on the same line. In general I use 'writeln', but if after a text there is an input, I use 'write'. It's purely aesthetic, my programming teacher taught it to me