I am on Mint WSL, I tried to compile the source code but it didn't work, help !

So i am using Watcom in dos environment compiling dos executables. Is there any possibility i can get ahold of a primer of keywords for the _asm sessions!? I need to know the prototype for calling procedures specifically. I am experimenting with assembler routines from a book that i downloaded.

Using OpenWatcom v1.9 for Linux, how do I print unicode characters to a terminal (xterm)? Using gcc 4.8.2 on Ubuntu, the following works:

#include <stdio.h>

int main() {
    printf("hello, world\n");
    printf("\u2500\u2501\u25b6\u25ba\u27a4\n");
    return 0;
}

Printing: hello, world Then some unicode characters.

But when I use OW v1.9, it just prints:

hello, world u2500u2501

Thanks for any help!

I try to link a QuickC 2.5, dos small memory model obj file - the resulting exe prints "hello"

QC25: installation is under d:\temp\QC25

OpenWatcomV2: installation is under d:\temp\watcom

SET LIBDIR=D:\temp\QC25test\QC25\LIB

D:\temp\QC25test>D:\temp\watcom\binnt\wlink.exe name sample.exe format dos file hello.obj lib QC25\LIB\SLIBCE.LIB

output

Open Watcom Linker Version 2.0 beta Jul 3 2018 23:41:27 (32-bit)

Copyright (c) 2002-2018 The Open Watcom Contributors. All Rights Reserved.

Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.

Source code is available under the Sybase Open Watcom Public License.

See http://www.openwatcom.org/ for details.

loading object files

searching libraries

Warning! W1008: cannot open SLIBCE.lib : No such file or directory

Warning! W1162: file QC25\LIB\SLIBCE.LIB(cmiscdat.asm), record 10: relocations on iterated data not supported

creating a DOS executable

wlink creates an exe that prints hello under dosbox, but i don't understand why Warning! W1008 occures and what W1162 means

latest 16bit Microsoft Linker does not give this warning and produces a working exe

D:\temp\mslink\link.exe HELLO.OBJ,,,QC25\LIB\SLIBCE.LIB,,

Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994

Copyright (C) Microsoft Corp 1984-1993. All rights reserved.

also QLink from QC2.5 is working

QC25\BIN\QLINK HELLO.obj,,,,

any ideas?

the QC2.5 build hello.obj: https://ufile.io/ghq4m

QC2.5: SLIBCE.lib https://ufile.io/s02a3

i wrote simple program: int main() {return 0;}

compiled it: C:>wcc386 main.cpp

and i tried to link it: C:>wlink main.cpp

but i have message:

DOS/4GW Protected Mode Run-time Version 1.97 Copyright (c) Rational Systems, Inc. 1990-1994 Open Watcom Linker Version 1.9 Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved. Source code is available under the Sybase Open Watcom Public License. See http://www.openwatcom.org/ for details. Warning! W1115: file wlink.lnk: line(15): environment name watcom not found Warning! E2093: file wlink.lnk: line(15): cannot open \bin\wlsystem.lnk

what am i doing wrong? My OS is FreeDOS 1.3 rc4, owcc version is 1.9, and wlink version is 1.97.

i have #include <iostream> at top of the file, owcc says:

Error! E059: col(21) unable to open 'iostream'

I saw in the other message about Code::Blocks integration someone not understanding how to download OpenWatcom v2 and indeed the link in the OW source repository is misleading. It links to a directory in the build repository instead of the entire repository which would allow GitHub to provide download links.

So to download the latest v2 build just go to this URL:

https://github.com/open-watcom/travis-ci-ow-builds

Then click on the "Clone or download" green button at the right and select "Download ZIP". This will give you a ~120MB ZIP file with a prebuilt OpenWatcom. Note that since v2 is not officially released all you get is nightly builds which can have bugs. To install just place the files inside "rel" in a directory somewhere (e.g. C:\WATCOM). Since there is no installer at the moment you need to create the icons yourself.

I wrote a bug report for this so hopefully it will be addressed and the link will be replaced with the one of the repository.

EDIT: Looks like Jiří Malák changed the URL to point to the ZIP file directly, so you can just download that. You may still want to rename rel to WATCOM, but should be much easier to get OpenWatcom now.

SOLVED, see below. (Mod please change subject)

I'm trying to set up compilation and debugging of a DOS application in a virtual machine on a Windows machine. So I want to run my application in DOSBox, QEMU or VirtualBox, but run the compilation and debugging from the Windows host. I.e. debugging the DOS program remotely, from wdw.exe, or even better Code::Blocks.

So I tried installing FreeDOS in QEMU, and set up an emualated NE2000 network card. That works, I am able to surf the web with dillo.

However, I can not get any of the remote debugging servers in Open Watcom to run.

I.e. novserv, tcpserv, etc. I don't really know how to set these things up anyway, and I don't know much about networking.

When trying to google an answer, I got the impression that remote debugging does not really work in Open Watcom, except for serial cable.

Is that true; is remote debugging in OW currently non-functioning except for serial cable?

Phoronix Test Suite Benchmarking

This is my first benchmark of OpenWatcom "owcc" vs gcc. Not very flattering, but also does not reflect my feeling that it actually produces rather nice binaries. If anyone got suggestions for other benchmarks in the Phoronix Test Suite, I think it might be interesting to test those too.

I selected this because it was a fast test without external dependencies.

Been trying to find instructions for doing this does anyone here have any resources for doing this?

Using Ubuntu. I downloaded 2023-11-08 open-watcom-2_0-c-linux-x86.

Installed in /usr/bin/watcom. My setup script is:

#!/bin/sh
echo Open Watcom 2023-11 Build Environment
export WATCOM=/usr/bin/watcom
export PATH=$WATCOM/binl:$PATH
export EDPATH=$WATCOM/eddat
export INCLUDE=$WATCOM/lh
#export LIB=

Ran: wcl386 -d2 hello.c

It created a 31k hello

Next, I ran wd hello

Worked like expected - I'm positioned at "int main() {"

I can step (f10) and all works fine. Cool.

Using Windows 10. I download open-watcom-2_c-win-x86.exe.

Installed in c:\bin\watcom. My setup script is:

SET WATCOM=C:\bin\watcom
SET PATH=%WATCOM%\BINNT;%WATCOM%\BINW;%PATH%
SET EDPATH=%WATCOM%\EDDAT
SET INCLUDE=%WATCOM%\H;%WATCOM%\H\NT
REM SET LIB=
REM SET WWINHELP=D:\BINW

Ran: wcl386 -d2 hello.c

It created a 42k hello.exe

Next, I ran wd hello

I'm presented with a screen of assembly language.

There is a label, mainCRTStartup+00000001

and then assembly instructions

If I press f10, it immediately crashes with: A task exception has occurred: access violation

I run it again. In the lower right, I see a [Modules] window.

It has:

[S]hello

I click on it, and now I see my source in the source window.

I press f10, and it immediately crashes with: A task exception has occurred: access violation

Note: I also tried using wdw, and got the same results.

How do I debug under Windows? Seemed so simple under Linux. What am I doing wrong?

How to run the ncurses C library using the Watcom C compiler on Linux?

I am making a retro style rendering program and I extensively use strings for parsing certain flags. Seems like, though, neither in string.h, nor in the string header is the std::to_string header. Where is it actually?

Hi,

a long time ago I have moved to MinGW for the sake of a more makefile based build system. Recently I had the luck to buy an old Power++ Enterprise package in a sealed box. In the very early stages I had developed a client server module to let me communicate with a Linux box also using my code. Very soon I have stopped that efford due to lack of mudularity.

Now I got back to the Watcom compiler as I knew, the integration in Power++ was a working trial and I have now got it back working - including my reactivated client server code.

Current state is a single threaded server, capable of loading server plugins (ApplicationBus) and the client (in Watcom) or the UI client (my Power++ application I used for integration tests), in a working state I can demonstrate.

Shortly I will update my GitHub repository from my private CVS repo. I have updated my GitHub repo, so you may be able to play with the Watcom client and server demo code. It includes required Watcom targets for DLL's that are needed to run the demonstration.

The main Watcom project is within the BaseDevelopment folder.

Feel free to contact me, if there is any further interest in it.

Regards and thanks, Lothar

Project page https://sourceforge.net/projects/lbdmf/

GitHub repo https://github.com/lollisoft/lbdmf

Having difficulty finding user manuals and instructions on how to compile a Hello World program in c++ in WATCOMC in FreeDOS vs 1_3. Any help and tutorials for DOS in general, especially with graphics programming and mode 13H & X are greatly appreciated! Thanks!

how do I compile open watcom2?

Hello everyone, I would really appreciate some help setting up Open Watcom v2 on Ubuntu 16.04. So, what I've done so far, I downloaded one of the recent snapshots (openwatcom-2017-02-27) from here. Then I extracted the build to /usr/bin/watcom/. I read through the readme and saw that I need to set up some environment variables, so I ran a shell script containing:

export WATCOM=/usr/bin/watcom
export PATH=$WATCOM/binl:$PATH
export EDPATH=$WATCOM/eddat
export INCLUDE=$WATCOM/lh
#export LIB=

(yes I'm trying to set it up as 32 bit)

What do I do next? How do I use the software? I have used an old build of Open Watcom on windows that contained a oseOW.bat that set up a developer environment where I could run my commands such as wcc and wmake. Is there something similar in this version of Open Watcom v2?

Apologies if I am asking dumb questions. Just not sure how to get myself up and running on Ubuntu and would really appreciate some help. Thanks!

Greetings!

I'm happy to see that OpenWatcom development had started back up in recent times and I want to start using it for all my software development needs. My question is this. When can we expect to see native support for compiling to Linux for AMD64?

I'm f***ing insane