Hi,
I just tried the actual LAMW manager on a fresh Win10/64 install. In Windows, with disabled Quick Edit Mode for the console
Install stops on start compiling package utils-fpcm for target i386-win32
It stays foreverr at that point and nothing happen. I can only abbort with control-c now.
Start compiling package utils for target i386-win32.
Compiling BuildUnit_utils.pp
Compiling usubst.pp
Compiling ptopu.pp
Compiling ptop.pp
Linking bin\i386-win32\ptop.exe
Compiling ppdep.pp
Linking bin\i386-win32\ppdep.exe
Compiling rstconv.pp
Linking bin\i386-win32\rstconv.exe
Compiling data2inc.pp
Linking bin\i386-win32\data2inc.exe
Compiling delp.pp
Linking bin\i386-win32\delp.exe
Compiling bin2obj.pp
Linking bin\i386-win32\bin2obj.exe
Compiling mkinsadd.pp
Linking bin\i386-win32\mkinsadd.exe
Compiling postw32.pp
Linking bin\i386-win32\postw32.exe
Compiling rmcvsdir.pp
Linking bin\i386-win32\rmcvsdir.exe
Compiling fpcsubst.pp
Linking bin\i386-win32\fpcsubst.exe
[ 5%] Compiled package utils
[ 10%] Skipped package utils-dxegen which has been disabled for target i386-win32
Start compiling package utils-fpcm for target i386-win32.
Any suggestions ? I know the LAMW Thread, where the hint is written down to disable the quick edit mode. I have disabled this for the cmd now, but the problem is still active.
Thanks
Edit: I have edited the title, because it is LAMW-Manager not LAMW itself