Does Zeus work under win98SE?

Jack · Post by **Jack** » Thu Jan 20, 2005 4:57 pm

I have zeus working fine under win2k. I just installed it on a win98SE system in our lab where we do debugging. When I attempt to invoke a compile, the status bar correctly shows the make command line, but no compiler output window opens. Zeus won't allow a 2nd try because it knows it has a spawned process. The windows system monitor shows that an additional virtual machine was started and 100% of the CPU is being consumed. If I invoke the compiler (watcom) from a DOS box, I discovered that wmake is prompting for a response to an error, the same as it doesn't under win2k.

Any ideas?

Jack

Jack · Post by **Jack** » Thu Jan 20, 2005 7:07 pm

Some additional info.

I changed the compiler switches to provide default actions so no prompting occurs during make. Now the make completes, but there is no output in the compiler output window. Just the default text zeus puts there.

-------------------------------------------------------------------------
Zeus for Windows Programmers Editor - Version 3.93d
Copyright (c) Xidicone Pty Ltd 1993-2004. All rights reserved.
-------------------------------------------------------------------------

--------------------Configuration: 2_debug - Debug--------------------

Jack

Post by **jussij** » Thu Jan 20, 2005 11:20 pm

Hi Jack,

Zeus should run fine on Windows 98 but you have found the one area where there can be problems

Windows 98 is a MS-DOS based system and MS-DOS handle the redirection of output very poorly

MS-DOS is particularly bad at handling stderr, so the firstly, check to see if Watcom is writing to stderr rather than stdout. If this is the case then see if there is an option to send the output to stdout.

Next I would try running the make via a batch file using something like this:

Code: Select all

wmake -f %1 > output.txt
type output.txt

Use this batch file in place of your current Zeus compile/make command line.

If this fails I would try creating a batch file to run the make, using something like this:

Code: Select all

wmake -f %1

Next I would create a Zeus compile/make command line batch file to run the first batch file, using something like this:

Code: Select all

call wmake.bat %1 > output.txt
type output.txt

Hopefully one of these options will enable you to capture the output into Zeus.

Cheers Jussi

Jack · Post by **Jack** » Mon Jan 24, 2005 2:55 pm

Thanks for the reply, Jussij,

Unfortunately, none of your suggestions work. In all cases, the file output.txt contains the correct compiler output. However, this output never shows up in the Zeus compile output window.

Any other ideas?
Jack

Post by **jussij** » Mon Jan 24, 2005 10:33 pm

I do not have access to Windows 98SE so I had to settle with running a test using Windows Me instead.

What I did was go to the Watcom download page:

http://openwatcom.mirrors.pair.com/watcom/11.0c/zips/

and download these zip files:

core_binnt.zip
c_binnt.zip
core_all.zip

I extracted these to the C:\watcom directory to give me the following directory structure:

Code: Select all

   Volume in drive C is WINDOWS ME
 Volume Serial Number is 382C-10F2
 Directory of C:\watcom

.              <DIR>        25/01/05   7:52 .
..             <DIR>        25/01/05   7:52 ..
BINNT          <DIR>        25/01/05   7:53 binnt
TEST     MAK           197  25/01/05   8:42 test.mak
BINW           <DIR>        25/01/05   7:53 binw
LICENSE  TXT         3,182  15/05/02  17:52 license.txt
         1 file(s)      3,338,719 bytes
         4 dir(s)     522,547,200 bytes free

I then created this simple test.mak make file as follows:

Code: Select all

CC = wcl.exe

.BEFORE
    @set PATH=.;c:\watcom\binnt\;

CFLAGS  = -zq -oentx

test.obj : test.c
    $(CC) $(CFLAGS) test.c

Next I create this test.c file with the obvious coding error:

Code: Select all

int main(int argc, char *argv)
{
    int  i = 10;

    return j;
}

Next I created a Zeus workspace in the c:\watcom directory, setting the project make command line for both debug and release to be:

Code: Select all

C:\watcom\binnt\wmake -d -f test.mak

Now when I now runmake using the Project, Make menu I get this captured output:

Code: Select all

---------------------------------------------------------------------------
     Zeus for Windows Programmers Editor - Version 3.93
     Copyright (c) Xidicone Pty Ltd 1993-2004.  All rights reserved.
---------------------------------------------------------------------------

Debug: Changed to the 'C:\watcom\' directory supplied
Debug: Command: c:\watcom\binnt\wmake -d -f test.mak
--------------------Configuration: watcom - Debug--------------------
Debug: Command Line: x95.exe c:\watcom\binnt\wmake -d -f test.mak
Debug: Started Process ID: 0xFFFB5E0F

Watcom Make Version 11.0c
Copyright by Sybase, Inc., and its subsidiaries, 1988, 2002.
All rights reserved.  Watcom is a trademark of Sybase, Inc.
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Warning(W47): Assuming target(s) are .SYMBOLIC
Entering file (test.mak)...
test.mak(10): ...Finished file (test.mak)
Updating (test.obj):has Single-colon explicit rule
Updating (test.c):has no explicit rule
	(test.c) has no implicit rules
	Oldest Possible    	(test.obj)
	Oldest Possible    	(test.obj)
	25-Jan-05  08:07:12	(test.c)
	wcl.exe -zq -oentx test.c
test.c(5): Error! E1011: Symbol 'j' has not been declared
Error: Compiler returned a bad status compiling 'test.c'
Error(E42): Last command making (test.obj) returned a bad status
Error(E02): Make execution terminated

Notice that at least for me the captured output seems to have worked just fine as it contains the test.c(5): Error! E1011: Symbol 'j' has not been declared coding error.

So unfortunately I am at a loss for a reason as to why this is not working on Windows 98SE

Cheers Jussi

Guest · Post by **Guest** » Tue Jan 25, 2005 2:30 pm

I guess there are differences between win98 and win ME. The other symptom I see under win98 is the mouse cursor is constantly flickering between an hourglass and the normal mouse pointer, at least a few times a second. I don't know if this is related to the bigger problem or not. I have the exact same behavours on 3 different win98 computers.

Jack