Installation problem on XP with omnetpp-4.1

[calb]

Hi,

Tried to install omnetpp-4.1 on a Windows XP SP3 machine and failed.
When executing "mingwenv.cmd" the command window is briefly shown then
it closes without any error message or warning (or displayed too
quickly).
However trying the same procedure with omnetpp-4.0 works fine, I was
able to build it and run a sample program.
It seems to be the fault of MSYS (msys.bat execution also fails in
4.1).
Am I the only one having this problem ?
Are there any known workarounds ?
Regards,

Cristian

[calb]

Hello again,
I have not received any reply. Am I the only one experiencing this
problem ?
Are there users of XP that installed omnet 4.1rc2 for the first time
smoothly ?
I had no preexisting mingw/msys installed on my machine.
Should I log a report in bugzilla ?
Cristian

[bolovox]

Hi, it seems that I have similar problem. I think, I saw sth about
Cygwin in cmd window that disappeared quickly.
After installing Cygwin I put '@echo on' instead of '@echo off' in bat
and I got this (in some lines there're double back-slashes '\\' -
maybe this is the problem?):

D:\omnetpp-4.1\msys>rem Copyright (C): 2001, 2002, 2003, 2004, 2005
Earnie Boyd

D:\omnetpp-4.1\msys>rem mailto:ear...@users.sf.net

D:\omnetpp-4.1\msys>rem This file is part of Minimal SYStem

D:\omnetpp-4.1\msys>rem http://www.mingw.org/msys.shtml

D:\omnetpp-4.1\msys>rem

D:\omnetpp-4.1\msys>rem File: msys.bat

D:\omnetpp-4.1\msys>rem Revision: 2.4

D:\omnetpp-4.1\msys>rem Revision Date: December 8th, 2005

D:\omnetpp-4.1\msys>rem ember to set the "Start in:" field of the
shortcut.

D:\omnetpp-4.1\msys>rem A value similar to C:\msys\1.0\bin is what the
"Start in:" field needs

D:\omnetpp-4.1\msys>rem to represent.

D:\omnetpp-4.1\msys>rem ember value of GOTO: is used to know recursion
has happened.

D:\omnetpp-4.1\msys>if "" == "GOTO:" goto

D:\omnetpp-4.1\msys>if NOT "x" == "x" set WD=

D:\omnetpp-4.1\msys>rem ember command.com only uses the first eight
characters of the label.

D:\omnetpp-4.1\msys>goto _WindowsNT

D:\omnetpp-4.1\msys>rem Hopefully a temporary workaround for getting
MSYS shell to run on x64

D:\omnetpp-4.1\msys>rem (WoW64 cmd prompt sets PROCESSOR_ARCHITECTURE
to x86)

D:\omnetpp-4.1\msys>if not "xx86" == "xAMD64" goto _NotX64

D:\omnetpp-4.1\msys>if NOT EXIST msys-1.0.dll set WD=D:
\omnetpp-4.1\msys\\bin\

D:\omnetpp-4.1\msys>rem ember Set up option to use rxvt based on value
of

D:\omnetpp-4.1\msys>set MSYSCON=unknown

D:\omnetpp-4.1\msys>if "x" == "x-norxvt" set MSYSCON=sh.exe

D:\omnetpp-4.1\msys>if "x" == "x--norxvt" set MSYSCON=sh.exe

D:\omnetpp-4.1\msys>if "x" == "x-rxvt" set MSYSCON=rxvt.exe

D:\omnetpp-4.1\msys>if "x" == "x--rxvt" set MSYSCON=rxvt.exe

D:\omnetpp-4.1\msys>if NOT "xunknown" == "xunknown" shift

D:\omnetpp-4.1\msys>if "xunknown" == "xunknown" set MSYSCON=sh.exe

D:\omnetpp-4.1\msys>if "x" == "x" set MSYSTEM=MINGW32

D:\omnetpp-4.1\msys>if "" == "MINGW32" set MSYSTEM=MINGW32

D:\omnetpp-4.1\msys>if "" == "MSYS" set MSYSTEM=MSYS

D:\omnetpp-4.1\msys>if NOT "x" == "x" set DISPLAY=

D:\omnetpp-4.1\msys>if "xsh.exe" == "xrxvt.exe" goto startrxvt

D:\omnetpp-4.1\msys>if "xsh.exe" == "xsh.exe" goto startsh

D:\omnetpp-4.1\msys>if NOT EXIST D:\omnetpp-4.1\msys\\bin\sh.exe goto
notfound

D:\omnetpp-4.1\msys>start D:\omnetpp-4.1\msys\\bin\sh --login -i

D:\omnetpp-4.1\msys>exit