(This is a guest post of Antoni Sawicki aka Tenox)
This is not strictly new. DG/UX worked on 86box before, but only partially. Low resolution and no networking made it almost unusable. Now it all has been patched up!
Ready to run image available here: https://files.42718.net/mirror/tenox/os/dgux/Virtual/DGUX-R4.20MU07-86Box-20261010.tar.lz
(This is a guest post by Antoni Sawicki aka Tenox)
Behold! AIX 3.2.5 now runs in QEMU!
Along with full X11 AIXwindows Desktop support on emulated GXT150L.
Also featuring the 3 digit diag display with key switch for service mode!
There are some gnu/pds apps in /usr/local/bin.
The exact machine emulated is 7006-41T (POWERstation 41T, 1994) + GXT150L
The QEMU branch: https://github.com/tenox7/qemu/tree/aix3
Ready to run portable QEMU image: https://tenox.pdp-11.net/os/aix/Virtual/aix325rs6000-qemu.tar.lz
Have fun with Virtualization!
(This is a guest post by Antoni Sawicki aka Tenox)
Yesterday I featured a QEMU branch capable of booting Windows NT PowerPC. I was asked in comments if this by any chance also supports OS/2 on this architecture. The answer is: YES!
Here is the result:
Here is a link to a ready to run image: https://tenox.pdp-11.net/os/os2/virtual/os2powerpc-qemu.tar.lz – it takes a little bit of time appearing stuck on PowerPC logo with a warning sign, but not too worry it will boot up.
The branch is https://github.com/tenox7/qemu/tree/powerpc
You can learn more about OS/2 PowerPC edition at OS/2 Museum.
(This is a guest post by Antoni Sawicki aka Tenox)
Another day another NT QEMU post. This time we have stock Windows NT 4.0 PowerPC running on QEMU, with complete emulation of the BIOS / Firmware and everything. Networking and 1280×1024 resolution.
QEMU branch: https://github.com/tenox7/qemu/tree/powerpc
Ready to run image: https://tenox.pdp-11.net/os/winnt/VMs/qemu-ppc/nt40powerpc-qemu.tar.lz
The image includes recently acquired Microsoft Office, SDK Tools, Visual Studio and a bunch of ported tools and utilities.
You may also be interested in Windows NT on IBM RS/6000 – Definitive Guide
(This is a guest post by Antoni Sawicki aka Tenox)
In the previous post I build at NT 3.1 MIPS based QEMU image based on Jazz architecture.
Today another NT 3.1 but on Jensen! An early Alpha XP NT DEC box – I have an entire blog post about it.
1280×1024 resolution, networking, SP3, Alpha SDK preinstalled!
Ready to run image: https://tenox.pdp-11.net/os/winnt/VMs/qemu-axp/nt31axp-qemu.tar.lz
QEMU Branch: https://github.com/tenox7/qemu/tree/jensen
More software apps etc in the previous post.
Have fun with virtualization!
(This is a guest post by Antoni Sawicki aka Tenox)
Behold! QEMU Jazz emulator can now boot and run NT 3.1 MIPS
With high res and networking fully working!
Github: https://github.com/tenox7/qemu/tree/jazz
Ready to run image: https://tenox.pdp-11.net/os/winnt/VMs/qemu-mips/nt31mips-qemu.tar.lz
(This is a guest post from Antoni Sawicki aka Tenox)
In my previous post I featured SINIX-N on MIPS based Siemens RM-200 emulated in QEMU.
Since I did some work on RM-200 QEMU and this system is also capable of running Windows NT MIPS in Lite Endian mode (the CPU can switch endianness) I decided to also get it working:
I have previously covered NT on MIPS QEMU Jazz emulated machine. This is not that much different and fundamentally very close. Just a different machine with different firmware and peripherals. Also much newer QEMU version.
https://github.com/tenox7/qemu/tree/rm200
Ready to run image: https://tenox.pdp-11.net/os/winnt/VMs/qemu-mips/NTRM200-QEMU.tar.lz
(This is a guest post by Antoni Sawicki aka Tenox)
Previously I got SINIX-Z running on 86box! But I really really wanted to run SINIX-N the MIPS counterpart!
Behold! MIPS R4000 SINIX-N running on QEMU emulated SNI RM-200!
After some time and couple of reboots we get to this:
and this:
This latest version 5.45 also features CDE:
The emulated Cirrus Logic GD5434 does 1152×864 and AMD PCnet NIC works fine. Not bad.
The QEMU branch is here. If you fancy submitting it to upstream go ahead.
If you want to install from scratch, my collection of SINIX install images and various application software is here.
For the lazy, I have prepared a ready to run image with all dependencies and QEMU binaries for Mac, Linux and Windows. The root password is just password. I have included bash and a bunch of GNU tools from gnustuff package under /home/tools. You can get gcc and others from here. There are some commercial apps here.
Have Fun with Virtualization!
(This is a guest post by Antoni Sawicki aka Tenox)
In the previous post I mentioned working on a large deployment of Citrix and NeoWare thin terminals. We were using Citrix ICA exclusively. But the NeoWare terminals also had this mysterious “NTRIGUE” protocol that I never had a chance to use:
Various brochures, press articles and ads about the HDS @workStation also mentioned that this thin client is for NTRIGUE with zero mention of Citrix or ICA!
Very strangely all NTRIGUE and no mention of ICA/Citrix! What is going on here?
And what exactly is this NTRIGUE?
In a nutshell: Isignia company was mainly known for SoftPC and SoftWindows – PC emulators for Mac and Unix.
Insignia NTRIGUE product was a version of Citrix WinFrame that used Xwindow / X11 protocol for the transport. X11 appears beside ICA in the WinStation protocol list.
And that would be all… if I didn’t score a red box on eBay!
Behold! After 30 years of waiting, I present you NTrigue:
The CDROM is essentially Citrix WinFrame but everything is find / replace rebranded as NTRIGUE.
Even the NTOS kernel prints NTRIGUE…
And the login screen
The real deal comes from WinStation configuration. You can create one with X11 protocol instead of ICA:
But how do you use it? Very simply! In two ways:
XDMCP Query, either from a physical Xterminal or Xnest or Xephyr:
…yes so now any plain regular Xterminal like NCD, HP, Tek, IBM, DEC, etc can connect to a Windows host!
Second way – export NTRIGUE X11 client via remote display export. Like you would with xterm -display x.x.x.x:N or export DISPLAY=..... You RSH into NTRIGUE box and request a client:
rsh <target> <client_ip> <resolution> <colors>In practice:
It seems that the NT box runs a rsh daemon and can send you an X11 exported client via x11.dll. It looks like they ported xlib to NT:
I find it curiously odd that the NTRIGUE client “app” runs on the host and exports display via X11 protocol. This is unlike ICA or RDP where the client runs on … the client.
Citrix ultimately acquired NTrigue from Insignia. Never to be heard from again and the tech essentially being buried. Is possible that this became their X11 ICA Client, but more likely they just bought it to kill competition to ICA protocol. After Microsoft released Terminal Server Edition with RDP, the ICA protocol and app management was all that Citrix had left to offer. NTrigue offered a “client-less” alternative. That couldn’t be good for business.
Finally a gallery of various UNIX systems talking to NTRIGUE:
You can download NTRIGUE from here: https://tenox.pdp-11.net/os/winnt/MultiWin/ntrigue/
PS
I do have the license disk but it’s unreadable because of 720k format trickery. I will read it with a flux reader in a few days.
Update: Rairii crafted a keygen for it.
(This is a guest post by Antoni Sawicki aka Tenox)
Around 1998/99 or so I was involved in a large deployment of Windows NT TSE (Terminal Server Edition) with Citrix Metaframe, for a Forbes top-100 listed corporation. The general population were using plain boring Neoware thin terminals with ICA client for their daily tasks.
Managers and higher ups were using “high end” Neoware “workstations”. Actually named “@workStation Prima”. They had options for TV and AV capture cards, teleconferencing, streaming and multi screen. However no one really used these advanced features and the expensive workstations didn’t provide any extra functionality or value in practice. Just bigger, fancier and made you look more important in the corporate rat race.
For the more perceptive observer however they did have some interesting curiosities hiding inside the pizza box. Firstly they were rocking Intel i960 !
Secondly if you pressed the odd “Don’t login” button at the ICA screen, you would land at a full blown desktop with some apps, games and a terminal with local shell. The OS (named netOS) was some proprietary i960 UNIX. Because it did feature mostly GNU apps I assumed it simply must have been an embedded Linux distro and didn’t make much of it.
Fast forward almost 30 years, Rico scored a copy of Neoware netOS install media and some people even got it installed. Out of nostalgia, I also wanted to do some archeology here and play with i960 iron. Bought one of these Neoware @workstation terminals at eBay and got the OS copied to my tftp/nfs server and booted it up.
Good memories and fun with ICA and XDMCP terminal. But I wanted to see what else can be done with the weird i960 system. I started looking at the kernel and tools. Upon closer inspection of the binaries, turns out these are not Linux at all (also i960 doesn’t have MMU so it could not run it anyhow), instead it seem to be 4.4-BSD based.
AFAIK an official SDK was never publicly available. But applications like NEdit, XScreensaver and even Netscape Navigator shipped with the OS so they must have been ported to netOS internally. Fortunately with help of LLM I was able to do some reverse engineering and map out the binary format and syscall interface. GCC 2.95 did support i960 ISA and Binutils 2.11 was able to produce somewhat compatible binary format. i960-intel-nindy is the closest triplet (nindy is the i960 ROM monitor). The rest was history. An unofficial netOS SDK was born in an evening.
For now it can compile just the simplest C apps, but I will expand it more. I want to port SimCity!
Last but not least the “premium workstation” has an IDE port and allows installation of a hard disk for local boot. This makes it lot less of a network booted terminal and more of a proper workstation. I slapped on an industrial IDE DOM, fdisk/newfs and got the OS copied to it using provided script:
Now I have a full blown i960 UNIX graphical workstation with local OS and SDK. Hopefully one day it can self host its own toolchain!
netOS documentation is available from https://tenox.pdp-11.net/os/netos/Documentation/
netOS sdk https://github.com/tenox7/netos-sdk
Update: now we have rshd, telnetd and even busybox !!
studio:/Users/tenox> telnet 192.168.1.11
Trying 192.168.1.11...
Connected to 192.168.1.11.
Escape character is '^]'.
netOS telnetd - exit or ^D to quit
NETOS> busybox sh
BusyBox v1.00 (2026.09.27-09:42+0000) hush - the humble shell v0.01 (testing)
Enter 'help' for a list of built-in commands.
~ # version
Server Code Version: 3.2-D (Build 560)
PLCC Boot PROM Version: 3.1.1-E (Build 12)
netOS Version: 3.2 netOS for the Enterprise with ICA
~ #
Update: Thanks to Ajfa netOS is now running on MAME!
