From: Earnie B. <ea...@us...> - 2012-09-09 16:51:22
|
On Sun, Sep 9, 2012 at 12:29 PM, LRN wrote: > On 09.09.2012 20:23, Earnie Boyd wrote: >> If user is executing 32bit in 64bit windows, the 32bit application >> would be executed from SysWOW64 instead of System32 (yes, it is >> stupid but true). The 64bit applications live in System32 and the >> 32bit applications live in SysWOW64. Where did the telnet >> application come from? It doesn't exist on my Windows 7 system. > Not installed by default, but still available (you need to "change > Windows components" on CP software page to add it). Or from the command line with pkgmgr /iu:"TelnetClient", thanks. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Earnie B. <ea...@us...> - 2012-09-09 17:07:18
|
On Sun, Sep 9, 2012 at 12:51 PM, Earnie Boyd <ea...@us...> wrote: > On Sun, Sep 9, 2012 at 12:29 PM, LRN wrote: >> On 09.09.2012 20:23, Earnie Boyd wrote: >>> If user is executing 32bit in 64bit windows, the 32bit application >>> would be executed from SysWOW64 instead of System32 (yes, it is >>> stupid but true). The 64bit applications live in System32 and the >>> 32bit applications live in SysWOW64. Where did the telnet >>> application come from? It doesn't exist on my Windows 7 system. >> Not installed by default, but still available (you need to "change >> Windows components" on CP software page to add it). > > Or from the command line with pkgmgr /iu:"TelnetClient", thanks. And after installing it isn't available as a file or executable in c:/windows/system32 from MSYS. I can only list the binary in 64bit cmd. If I start 32bit cmd from SysWOW64 I cannot find the file to execute it. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Maximus <Con...@gm...> - 2012-09-09 18:07:33
|
Earnie Boyd <earnie@...> writes: > And after installing it isn't available as a file or executable in > c:/windows/system32 from MSYS. I can only list the binary in 64bit > cmd. If I start 32bit cmd from SysWOW64 I cannot find the file to > execute it. As you said before, "this is stupid, but its true". That's why I said "run 64 bit apps in 64 bit OS" :( However, you may run telnet from msys :) Try this: "c:\windows\sysnative\telnet.exe" regards |
From: Earnie B. <ea...@us...> - 2012-09-09 18:34:53
|
On Sun, Sep 9, 2012 at 2:07 PM, Maximus wrote: > Earnie Boyd <earnie@...> writes: > >> And after installing it isn't available as a file or executable in >> c:/windows/system32 from MSYS. I can only list the binary in 64bit >> cmd. If I start 32bit cmd from SysWOW64 I cannot find the file to >> execute it. > > As you said before, "this is stupid, but its true". > That's why I said "run 64 bit apps in 64 bit OS" :( > > However, you may run telnet from msys :) Try this: > "c:\windows\sysnative\telnet.exe" Ok, yes you can. So if I can run the 64bit telnet in a 32bit system why would it be a problem for a 32bit ConEmu? -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Maximus <Con...@gm...> - 2012-09-09 19:37:57
|
Earnie Boyd <earnie@...> writes: > > As you said before, "this is stupid, but its true". > > That's why I said "run 64 bit apps in 64 bit OS" :( > > > > However, you may run telnet from msys :) Try this: > > "c:\windows\sysnative\telnet.exe" > > Ok, yes you can. So if I can run the 64bit telnet in a 32bit system > why would it be a problem for a 32bit ConEmu? There are two problems 1. telnet will not run at all under Windows 7 x64 & ConEmu x86. The reason explained in Issue on my site http://code.google.com/p/conemu-maximus5/issues/detail?id=65 And on microsoft forum: Console screen buffer corrupts from other console application http://bit.ly/P8o4sZ Problem may be fixed, if ConEmuHk64.dll will be injected in telnet. When it is absent (no 64-bit package) telnet fill fails. 2. some features (ansi-sequences, for example) are not available for 64-bit applications, when ConEmuHk64.dll does not exists. But, as I said before, ConEmu shows the warning in that case, so this is not a critical problem from my point of view. regards |
From: Maximus <Con...@gm...> - 2012-09-09 22:40:36
|
Keith Marshall <keithmarshall@...> writes: > >> ConEmu is free, opensource, and may be compiled with mingw (gcc). Are you > >> interested in it? > > We might be, subject to the following conditions: > > 1) It would need to be packaged in mingw-get friendly tarballs. OK, first try http://sourceforge.net/projects/conemu/files/MinGW/ conemu-5.120909-mingw32-bin.tar.xz conemu-5.120909-mingw64-bin.tar.xz > 2) Release specific source tarballs need to be made available. Few words about source tarballs? Where sources must be located? "$MINGW_ROOT/src/conemu"? Name of tarballs? "conemu-5.minor-src.tar.xz"? > 3) The source should build OOTB, under MSYS, with MinGW tools. New sources uploaded to svn. Try again? > 4) Default configuration should immediately invoke MSYS shell. Done. regards |
From: Keith M. <kei...@us...> - 2012-09-10 19:25:38
|
On 09/09/12 23:40, Maximus wrote: > Keith Marshall <keithmarshall@...> writes: >>>> ConEmu is free, opensource, and may be compiled with mingw (gcc). Are you >>>> interested in it? >> >> We might be, subject to the following conditions: >> >> 1) It would need to be packaged in mingw-get friendly tarballs. > > OK, first try > http://sourceforge.net/projects/conemu/files/MinGW/ > conemu-5.120909-mingw32-bin.tar.xz > conemu-5.120909-mingw64-bin.tar.xz Okay. The names are good; the content isn't. Currently, you have: $ tar tf conemu-5.120909-mingw32-bin.tar.xz bin/ bin/ConEmu.exe libexec/ libexec/conemu/ libexec/conemu/ConEmu.xml libexec/conemu/ConEmuC.exe libexec/conemu/ConEmuCD.dll libexec/conemu/ConEmuHk.dll share/ share/conemu/ share/conemu/About-ConEmu.txt share/conemu/License.txt share/conemu/WhatsNew-ConEmu.txt $ tar tf conemu-5.120909-mingw64-bin.tar.xz bin/ bin/ConEmu64.exe libexec/ libexec/conemu/ libexec/conemu/ConEmu.xml libexec/conemu/ConEmuC64.exe libexec/conemu/ConEmuCD64.dll libexec/conemu/ConEmuHk64.dll share/ share/conemu/ share/conemu/About-ConEmu.txt share/conemu/License.txt share/conemu/WhatsNew-ConEmu.txt Conventionally, we would organise the 'share' content as: share/ share/doc/ share/doc/conemu/ share/doc/conemu/5.120909/ share/doc/conemu/5.120909/About-ConEmu.txt share/doc/conemu/5.120909/License.txt share/doc/conemu/5.120909/WhatsNew-ConEmu.txt However, that's a minor issue. Much more serious is that that 'share' content is duplicated in each of the two binary tarballs. As a matter of policy, we *never* distribute tarballs, in any single release set, with duplicate content; the common content *must* be segregated. The same applies to the libexec/conemu/ConEmu.xml file; it also appears in duplicate, in both tarballs. Finally, and also by convention, we prefer to segregate the licence from other regular documentation. Thus, for a well formed release set, you should have: $ tar tf conemu-5.120909-mingw32-bin.tar.xz bin/ bin/ConEmu.exe libexec/ libexec/conemu/ libexec/conemu/ConEmuC.exe libexec/conemu/ConEmuCD.dll libexec/conemu/ConEmuHk.dll $ tar tf conemu-5.120909-mingw32-conf.tar.xz libexec/ libexec/conemu/ libexec/conemu/ConEmu.xml $ tar tf conemu-5.120909-mingw32-lic.tar.xz share/ share/doc/ share/doc/conemu/ share/doc/conemu/5.120909/ share/doc/conemu/5.120909/License.txt $ tar tf conemu-5.120909-mingw32-doc.tar.xz share/ share/doc/ share/doc/conemu/ share/doc/conemu/5.120909/ share/doc/conemu/5.120909/About-ConEmu.txt share/doc/conemu/5.120909/WhatsNew-ConEmu.txt $ tar tf conemu-5.120909-mingw64-bin.tar.xz bin/ bin/ConEmu64.exe libexec/ libexec/conemu/ libexec/conemu/ConEmuC64.exe libexec/conemu/ConEmuCD64.dll libexec/conemu/ConEmuHk64.dll >> 2) Release specific source tarballs need to be made available. > > Few words about source tarballs? > Where sources must be located? "$MINGW_ROOT/src/conemu"? No. User's current directory, when unpacking the tarball. The top level directory within the tarball should be conemu-5.minor/, with an image of your source tree (for version 5.minor) within it. > Name of tarballs? "conemu-5.minor-src.tar.xz"? No. The convention is to match the name of the primary binary package, substituting 'src' for 'bin', so conemu-5.120909-mingw32-src.tar.xz would be appropriate for the above binary tarball set. >> 3) The source should build OOTB, under MSYS, with MinGW tools. > > New sources uploaded to svn. Try again? Erwin might. I won't, until I can download a source tarball. >> 4) Default configuration should immediately invoke MSYS shell. > > Done. Still disappointing. For me, on virtual WinXP, this now doesn't run at all; just flashes up a dark coloured window, which immediately closes. However, it does run on a real Vista box; it must interact badly with the virtualisation layer, in a way which Console2 doesn't, for it runs absolutely fine on both platforms. -- Regards, Keith. |
From: Maximus <Con...@gm...> - 2012-09-10 23:23:23
|
Keith Marshall <keithmarshall@...> writes: > Okay. The names are good; the content isn't. Currently, you have: New packages uploaded, 120910. https://sourceforge.net/projects/conemu/files/MinGW/ > Still disappointing. For me, on virtual WinXP, this now doesn't run at > all; just flashes up a dark coloured window, which immediately closes. > However, it does run on a real Vista box; it must interact badly with > the virtualisation layer, in a way which Console2 doesn't, for it runs > absolutely fine on both platforms. New build shows more diagnostic information. I've tried new build on virtual WinXP and get the following. When "MINGW_ROOT=C:\MinGW" - all works perfectly. But, when "MINGW_ROOT=Z:\MinGW" - bash failed to start. ConEmu shows following info: Current directory: C:\ Command to be executed: Z:\MinGW\msys\1.0\bin\sh.exe --login -i ConEmuC: Root process was alive less than 10 sec, ExitCode=1. Moreover, when I try to run bash directly (from Win+R) Z:\MinGW\msys\1.0\bin\sh.exe --login -i fails (console blinks and closes), but C:\MinGW\msys\1.0\bin\sh.exe --login -i starts normally. Why? |
From: Maximus <Con...@gm...> - 2012-09-11 07:37:38
|
Erwin Waterlander <waterlan@...> writes: > I have seen the freezes again. They happen with conemu64 when I run an > msys shell and press the cross button to close conemu. It does not > happen when I run normal cmd.exe. This is with ConEmuSetup.120909.exe on > Windows 7, 64 bit. Can you create minidumps of all process in ConEmu tree after freeze? Thought, there are must be 2 or 3 processes: ConEmu64, ConEmuCD(64) and bash. Q. "How to create a minidump" in ConEmu FAQ. http://code.google.com/p/conemu-maximus5/wiki/ConEmuFAQ Full dumps are preferred, but they are much larger. |
From: Erwin W. <wat...@xs...> - 2012-09-12 17:52:42
|
Op 11-9-2012 9:37, Maximus schreef: > Erwin Waterlander <waterlan@...> writes: > >> I have seen the freezes again. They happen with conemu64 when I run an >> msys shell and press the cross button to close conemu. It does not >> happen when I run normal cmd.exe. This is with ConEmuSetup.120909.exe on >> Windows 7, 64 bit. > Can you create minidumps of all process in ConEmu tree after freeze? > Thought, there are must be 2 or 3 processes: > ConEmu64, ConEmuCD(64) and bash. > > Q. "How to create a minidump" in ConEmu FAQ. > http://code.google.com/p/conemu-maximus5/wiki/ConEmuFAQ > > Full dumps are preferred, but they are much larger. > > Hi Maximus, I tried ConEmu64.exe /debugpid=1 /full then I get the message: Unknown switch specified: /debugpid=1 I used version 120909. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Earnie B. <ea...@us...> - 2012-09-12 18:00:13
|
On Wed, Sep 12, 2012 at 1:52 PM, Erwin Waterlander wrote: > Hi Maximus, > > I tried > ConEmu64.exe /debugpid=1 /full > > then I get the message: > Unknown switch specified: /debugpid=1 > > I used version 120909. If you're starting from the MSYS shell you need to use //debugpid and //full to avoid MSYS from thinking it is a PATH that needs converted. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Erwin W. <wat...@xs...> - 2012-09-12 18:02:39
|
Op 12-9-2012 19:52, Erwin Waterlander schreef: > Op 11-9-2012 9:37, Maximus schreef: >> Erwin Waterlander <waterlan@...> writes: >> >>> I have seen the freezes again. They happen with conemu64 when I run an >>> msys shell and press the cross button to close conemu. It does not >>> happen when I run normal cmd.exe. This is with ConEmuSetup.120909.exe on >>> Windows 7, 64 bit. >> Can you create minidumps of all process in ConEmu tree after freeze? >> Thought, there are must be 2 or 3 processes: >> ConEmu64, ConEmuCD(64) and bash. >> >> Q. "How to create a minidump" in ConEmu FAQ. >> http://code.google.com/p/conemu-maximus5/wiki/ConEmuFAQ >> >> Full dumps are preferred, but they are much larger. >> >> > Hi Maximus, > > I tried > ConEmu64.exe /debugpid=1 /full > > then I get the message: > Unknown switch specified: /debugpid=1 > > I used version 120909. > > regards, > Hi Maximus, I used the wrong method. I have made two dumps with Windows 7. See: http://waterlan.home.xs4all.nl/tmp/ best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Maximus <Con...@gm...> - 2012-09-12 18:00:39
|
Hi, Erwin > I tried > ConEmu64.exe /debugpid=1 /full > > then I get the message: > Unknown switch specified: /debugpid=1 1. "ConEmuC64.exe ...", not ConEmu64.exe 2. Hope, you specify real PID, not "1" :) |
From: Erwin W. <wat...@xs...> - 2012-09-12 18:35:53
|
Op 12-9-2012 20:00, Maximus schreef: > Hi, Erwin > >> I tried >> ConEmu64.exe /debugpid=1 /full >> >> then I get the message: >> Unknown switch specified: /debugpid=1 > 1. "ConEmuC64.exe ...", not ConEmu64.exe Okay. > 2. Hope, you specify real PID, not "1" :) > > I don't know what to fill in for PID. How can I find it. The conemu status bar turned blank. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-09-12 18:51:40
|
Op 12-9-2012 20:35, Erwin Waterlander schreef: > Op 12-9-2012 20:00, Maximus schreef: >> Hi, Erwin >> >>> I tried >>> ConEmu64.exe /debugpid=1 /full >>> >>> then I get the message: >>> Unknown switch specified: /debugpid=1 >> 1. "ConEmuC64.exe ...", not ConEmu64.exe > Okay. > >> 2. Hope, you specify real PID, not "1" :) >> >> > I don't know what to fill in for PID. How can I find it. The conemu > status bar turned blank. > > regards, > Hi, I got it. I had to add to column with process-id in the task manager. I tried now also conemu 32 bit. And this one also freezes. I added a third dump file of the 32 bit with conemuc /debugpid=6052 /full See http://waterlan.home.xs4all.nl/tmp/ This is what I do. 1. start conemu, first tab runs cmd.exe 2. open second tab with msys shell: c:\mingw\msys\1.0\bin\sh.exe --login -i 3. press cross to close conemu 4. conemu freezes. Windows 7 64 bit, Home Premium Conemu 120909. I also notice that once I have triggered the freeze, then every next conemu I start also freezes when I press the cross. Even when I run only one tab with cmd.exe. I have to reboot Windows to get this behaviour away. best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-09-12 19:50:32
|
Erwin Waterlander schreef, Op 12-9-2012 20:51: > Hi, > > I got it. I had to add to column with process-id in the task manager. > I tried now also conemu 32 bit. And this one also freezes. > I added a third dump file of the 32 bit with > conemuc /debugpid=6052 /full > > See http://waterlan.home.xs4all.nl/tmp/ > > This is what I do. > 1. start conemu, first tab runs cmd.exe > 2. open second tab with msys shell: c:\mingw\msys\1.0\bin\sh.exe --login -i > 3. press cross to close conemu > 4. conemu freezes. > > Windows 7 64 bit, Home Premium > Conemu 120909. > > I also notice that once I have triggered the freeze, then every next > conemu I start also freezes when I press the cross. Even when I run only > one tab with cmd.exe. I have to reboot Windows to get this behaviour away. > > best regards, > Conemu on Windows Vista 32 problem does not have the problem when I do exactly the same. It does not freeze. Only on Win7 64 bit both conemu and conemu64 hang reproducible. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Keith M. <kei...@us...> - 2012-09-12 19:11:22
Attachments:
mingw32-conemu.xml
|
On 11/09/12 00:22, Maximus wrote: > Keith Marshall <keithmarshall@...> writes: >> Okay. The names are good; the content isn't. Currently, you have: > > New packages uploaded, 120910. > https://sourceforge.net/projects/conemu/files/MinGW/ That's better, thanks. Still missing the requisite source tarballs, but in any case, I've attached a tentative stab at a mingw-get package specification, to facilitate distribution; any comments? >> Still disappointing. For me, on virtual WinXP, this now doesn't run at >> all; just flashes up a dark coloured window, which immediately closes. 5.120910 still fails, for me, but now after integrating the attached specification into my local mingw-get catalogue, running: $ mingw-get install --start-menu conemu-bin and calling out the resultant start menu shortcut... > New build shows more diagnostic information. > I've tried new build on virtual WinXP and get the following. ...at least it no longer vanishes immediately, and I see: Current directory: C:\Documents and Settings\Keith Marshall Command to be executed: C:\MinGW\msys\1.0\bin\sh.exe --login -i ConEmuC: Root process was alive less than 10 sec, ExitCode=128. Press Enter or Esc to close console... (and, unlike previously, I now *can* copy and paste this). At this point, I *can* get to a working configuration by opening the settings dialogue, and changing *both* of the following: Startup --> Command line --> SELECTED, assigned as: %ComSpec% /c C:\MinGW\msys\1.0\bin\sh.exe --login -i Features --> Inject ConEmuHk --> DISABLED > Moreover, when I try to run bash directly (from Win+R) > Z:\MinGW\msys\1.0\bin\sh.exe --login -i > fails (console blinks and closes), but > C:\MinGW\msys\1.0\bin\sh.exe --login -i > starts normally. > > Why? I don't know. Does Z:\MinGW\MSYS\1.0 host a complete MSYS installation? In particular, does directory Z:\MinGW\MSYS\1.0\etc exist? Does your user have write permission in it? Does Z:\MinGW\MSYS\1.0\bin host the necessary binaries? -- Regards, Keith. |
From: Earnie B. <ea...@us...> - 2012-09-12 20:04:52
|
On Wed, Sep 12, 2012 at 7:15 AM, Keith Marshall wrote: > On 11/09/12 00:22, Maximus wrote: >> Moreover, when I try to run bash directly (from Win+R) >> Z:\MinGW\msys\1.0\bin\sh.exe --login -i >> fails (console blinks and closes), but >> C:\MinGW\msys\1.0\bin\sh.exe --login -i >> starts normally. >> >> Why? > > > I don't know. Does Z:\MinGW\MSYS\1.0 host a complete MSYS installation? > In particular, does directory Z:\MinGW\MSYS\1.0\etc exist? Does your user > have write permission in it? Does Z:\MinGW\MSYS\1.0\bin host the necessary > binaries? As a matter of my own policy, I execute from a NDAS on a daily basis without failure. So, Keith's suggestion for you to look at your environment is spot on. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Maximus <Con...@gm...> - 2012-09-12 20:19:57
|
Hi, Erwin > This is what I do. > 1. start conemu, first tab runs cmd.exe > 2. open second tab with msys shell: c:\mingw\msys\1.0\bin\sh.exe --login -i > 3. press cross to close conemu > 4. conemu freezes. > > Windows 7 64 bit, Home Premium > Conemu 120909. > > I also notice that once I have triggered the freeze, then every next > conemu I start also freezes when I press the cross. Even when I run only > one tab with cmd.exe. I have to reboot Windows to get this behaviour away. The source of the freeze: c:\program files (x86)\F-Secure\apps\computersecurity\HIPS\fshook64.dll > ntdll.dll!ZwWaitForSingleObject() + 0xa bytes ntdll.dll!RtlpWaitOnCriticalSection() + 0xe8 bytes ntdll.dll!RtlEnterCriticalSection() - 0x4be5 bytes fshook64.dll!000007fefa38ad9b() or in 32bit dump > ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes fshook32.dll!72f51cea() Seems to me, it is not a ConEmu problem (at least, not only ConEmu). regards. |
From: Earnie B. <ea...@us...> - 2012-09-12 20:28:08
|
On Wed, Sep 12, 2012 at 4:19 PM, Maximus wrote: > Hi, Erwin > >> This is what I do. >> 1. start conemu, first tab runs cmd.exe >> 2. open second tab with msys shell: c:\mingw\msys\1.0\bin\sh.exe --login -i >> 3. press cross to close conemu >> 4. conemu freezes. >> >> Windows 7 64 bit, Home Premium >> Conemu 120909. >> >> I also notice that once I have triggered the freeze, then every next >> conemu I start also freezes when I press the cross. Even when I run only >> one tab with cmd.exe. I have to reboot Windows to get this behaviour away. > > The source of the freeze: > c:\program files (x86)\F-Secure\apps\computersecurity\HIPS\fshook64.dll > >> ntdll.dll!ZwWaitForSingleObject() + 0xa bytes > ntdll.dll!RtlpWaitOnCriticalSection() + 0xe8 bytes > ntdll.dll!RtlEnterCriticalSection() - 0x4be5 bytes > fshook64.dll!000007fefa38ad9b() > > or in 32bit dump > >> ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes > ntdll.dll!_NtWaitForSingleObject@12() + 0x15 bytes > fshook32.dll!72f51cea() > > > Seems to me, it is not a ConEmu problem (at least, not only ConEmu). Which threading model is being used? Whose distribution of GCC are you using? -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Maximus <Con...@gm...> - 2012-09-12 20:28:34
|
Erwin Waterlander <waterlan@...> writes: > This is what I do. > 1. start conemu, first tab runs cmd.exe > 2. open second tab with msys shell: c:\mingw\msys\1.0\bin\sh.exe --login -i > 3. press cross to close conemu > 4. conemu freezes. > > Windows 7 64 bit, Home Premium > Conemu 120909. Btw, does processes ConEmuC64 (ConEmuC) or Bash exists when ConEmu64 freezes? regards |
From: Maximus <Con...@gm...> - 2012-09-12 21:26:31
|
Hi, Earnie > > The source of the freeze: > > c:\program files (x86)\F-Secure\apps\computersecurity\HIPS\fshook64.dll > > > > Seems to me, it is not a ConEmu problem (at least, not only ConEmu). > > Which threading model is being used? Whose distribution of GCC are you using? Earnie, whom is this question for? As for me, this ConEmu release was builded with MS VC 2009 (Win7 SDK) with "Multi-threaded (/MT)" model (not using CRT dlls). So, GCC does not matter. regards |
From: Maximus <Con...@gm...> - 2012-09-13 00:23:00
|
Hi, Erwin > Windows 7 64 bit, Home Premium > Conemu 120909. Freeze confirmed, when F-Secure is installed. try build 120912 |
From: Erwin W. <wat...@xs...> - 2012-09-13 18:34:26
|
Op 13-9-2012 2:22, Maximus schreef: > Hi, Erwin > >> Windows 7 64 bit, Home Premium >> Conemu 120909. > Freeze confirmed, when F-Secure is installed. > try build 120912 > Hi Maximus, Version 120912 works without problems. 32 and 64 bit. Thanks a lot! By the way, on my 32 bit Vista PC I have the same F-Secure installed, which does not seem to be a problem. best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Maximus <Con...@gm...> - 2012-09-13 00:28:51
|
Hi, Erwin > I just built a working ConEmu with mingw32 from svn (rev 1009). > Everything builds (with a lot of warnings), and at the end the cleaning > ends with an error: makefile's updated. I'll look into warnings later. regards |