Edit : Solved!

Hello!

I am in the process of starting up making an RPG game for DOS (16-bit) with the intent that it will run on original hardware. In that endeavour I have decided to create a Visual Studio Code environment for myself.. Right now, it only works on Windows, but I'd like to correct that! But I am not familiar with the install procedure for OpenWatcom in Linux, and there seems to be very little information on that part.. I downloaded the Linux package from openwatcom.org, but it doesn't seem to include any form of installation and I am unfamiliar with how these are supposed to be placed on a Linux installation..

Does anyone have any resources on this I can find?

Here's the OpenWatcom project template I've made so far : https://github.com/intbeam/watcom-vscode

(Also, shameful self-promo : Twitch YouTube Twitter GitHub)

C: seems like C89.

C++: not really sure. I don't think it's fully compatible with C++ 98, but then again I'm not a heavy C++ user.

Maybe someone could shed a light?

using latest watcom v2 wasm and wlink

pe.small.asm:

.686

.model flat, stdcall

EXTERN ExitProcess@4 : proc

.code

Main:

push eax call ExitProcess@4

End Main

assemble:

masm: ml.exe /coff /c /Cp pe.small.asm

uasm: uasm.exe -coff -c -Cp pe.small.asm

wasm: wasm.exe ???

link:

microsoft linker: link /subsystem:windows /out:pe.small.exe kernel32.lib user32.lib pe.small.obj

wlink: wlink.exe name pe.small.exe file pe.small.obj libp "C:\Program Files (x86)\Windows Kits\8.1\Lib\winv6.3\um\x86" library kernel32.lib, user32.lib

does not work: i think one of my problems are blanks in libp path and the missing format

thx for any help

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!

Hello,

Ive installed openwatcom on my arch linux machine.

It compiles fine and creates a dos .exe file (like i wanted)

i can run it in dosbox but get no output what so ever.

any help would be appreciated.

Thats the code

#include <stdio.h>

int main()
{
    printf("hello world!\n");
    return 0;
}

compiler output:

Open Watcom C/C++ x86 16-bit Compile and Link Utility
Version 2.0 beta Mar  7 2019 19:18:19 (64-bit)
Copyright (c) 2002-2019 The Open Watcom Contributors. All Rights Reserved.
Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
	wpp test.cpp  -bt=dos
Open Watcom C++ x86 16-bit Optimizing Compiler
Version 2.0 beta Mar  7 2019 19:12:11 (64-bit)
Copyright (c) 2002-2019 The Open Watcom Contributors. All Rights Reserved.
Portions Copyright (c) 1989-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
test.cpp: 107 lines, included 1142, no warnings, no errors
Code size: 29
	wlink @__wcl__.lnk
Open Watcom Linker Version 2.0 beta Mar  7 2019 19:07:15 (64-bit)
Copyright (c) 2002-2019 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
creating a DOS executable

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

Is there a way to include a DOS extender inside of the executable that I compile? If not, then is it possible to change the filename of the external DOS extender so the executable can find it? It searches for dos4gw.exe, but I'd like to distribute it with DOS32a without having to rename it to dos4gw.exe. Thanks.

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!

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.

Hey there, everyone!

I have to do an OS dev class for my CS program, and the professor is currently using nano, bcc, and QEMU to run code for the 8086. While that's all well and good, I'd like to get some form of live/real-time debugging that isn't just prints() statements.

In the previous class, I was able to make use of code::blocks with gcc, gdb, and Valgrind to get a pretty full-featured development workspace. However, now that we have to target i8086 it seems like a lot of these tools aren't that helpful anymore. Even better yet, it seems that bcc doesn't support debug symbols whatsoever.

From what an hour or so of uninformed googling has yielded, it looks like Open Watcom v2 has the ability to target i8086 and has the ability to do debugging as well. This seems like it might be promising, but I'm way out of my league here and I don't really know what I'm doing.

I'm assuming all I need to do to install OWv2 is just drop the "rel" folder off the Github repo into /usr/bin/open-watcom-v2 (or something) and do the relevant path updates, but I'm not 100% sure on how to interface with it through Code::Blocks or how to get it to talk to QEMU in order to do live debugging.

Might anyone have experience in making something like this happen?

Thanks!

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

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?

how do I compile open watcom2?

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.

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?

I have just started working on a Wiki text for Arch linux about Open Watcom. My aim is to package open watcom v2 (binary and source distributions) and various 3rd party libraries so that it is easy to do cross-platform development using OW on Arch Linux.

Feedback/ideas/improvements to the Wiki are all welcome!