But it says that

Whats happening

It also works in 0.4.15-dev-1, as I reported.

guess I missed that then :)

guess I missed that then :)

0.4.15-dev-392 is affected.

As I reported in JIRA.

Whats happening

You are using outdated build in QEMU, that's what happens

When the 4.14 release will be out ?

https://twitter.com/reactos/status/1366037478357012485?s=20

https://twitter.com/InvisibleUp/status/1366431351675748352

i don't see why not

apparently it somewhat works in XP :p

<hbelusca (Gmunu=8PiG/c4Tmunu+)> it ought to be, since it has been developed on XP/server 2003.

<hbelusca (Gmunu=8PiG/c4Tmunu+)> (and is meant to be compatible with these)

it's a bit broken compared to actual ReactOS though

the tray icons are messed up and it won't open its own explorer

<hbelusca (Gmunu=8PiG/c4Tmunu+)> hmhm

Compile 16-bit app! https://stackoverflow.com/questions/20511577/create-a-16bit-application https://stackoverflow.com/questions/227762/looking-for-16-bit-x86-compiler

but why? 👀

but why? 👀

For compatibility with legacy DOS applications!

eh?

eh?

There are no compilers for 16-bit open source, FreeDOS uses proprietary compilers!

<hbelusca (Gmunu=8PiG/c4Tmunu+)> openwatcom

Free Pascal can also target Win16

There are no compilers for 16-bit open source, FreeDOS uses proprietary compilers!

FreeDOS doesn't use proprietary compilers.

also I just noticed it's about a 16-bit DOS application. Free Pascal can target that too, and also OpenWatcom

and if you don't mind good ol' assembly (pretty reasonable given a 16-bit DOS target, actually), you have even more options. nasm tends to be the most popular.

<hbelusca (Gmunu=8PiG/c4Tmunu+)> openwatcom

Look at the license, there are a lot of restrictions! ftp://ftp.openwatcom.org/install/license.txt

It's one of those rare licenses that the FSF and OSI disagree on. FSF says it's not free software because it requires you to publish source code no matter what. OSI is ok with it being considered open source.

It's honestly probably good enough for any practical uses.

FreeDOS doesn't use proprietary compilers.

"If you’ve got some programming experience Port FreeDOS utilities to OpenWatcom C and NASM—our preferred C compiler and Assembler for FreeDOS. (Some older FreeDOS programs were probably written for Borland C or Turbo C or Microsoft C, or Microsoft ASM or Turbo ASM)" https://www.freedos.org/contribute/

There are no compilers for 16-bit open source, FreeDOS uses proprietary compilers!

your not making sense to me tbf

your not making sense to me tbf

Read the messages, I wrote above about the openwatcom license and FreeDOS!

yeah still not making sense: why would one write a 16 bit program

yeah still not making sense: why would one write a 16 bit program

In order to interact with 16-bit software, as FreeDOS does, you cannot use legacy software properly without an ntvdm unless it is compiled into 16-bit parts!

In order to interact with 16-bit software, as FreeDOS does, you cannot use legacy software properly without an ntvdm unless it is compiled into 16-bit parts!

but your talking about writing 16 bit software 👀

but your talking about writing 16 bit software 👀

The small niche for 16-bit software, this one is more attached to enthusiasts!

sooo let me ask again: why would you write 16 bit software 🤔

i dont get anything

nor why it's being discussed here

there's that too lol

/id@matrix_t2bot

/id@matrix_t2bot

-1001060350882

sooo let me ask again: why would you write 16 bit software 🤔

First you want to use legacy hardware and run 16-bit systems, that's for any old 16-bit platform! In the case of Reactos, 64-bit does not run all 16-bit software! http://techgenix.com/Identifying16-bitapplicationsthatwontrunon64-bitWindows/

ok and?

just use 32-bit reactos lmao

just use 32-bit reactos lmao

Here is an explanation and links on the topic covered! https://reactos.org/wiki/User:Petr-akhlamov/WOW

thats cool and all

https://jira.reactos.org/browse/CORE-8254

but why go through the effort of running 64-bit reactos (which is probably worse than the 32-bit version) instead of being a normal person and y'know use 32-bit reactos

but why go through the effort of running 64-bit reactos (which is probably worse than the 32-bit version) instead of being a normal person and y'know use 32-bit reactos

Use two things, current and legacy software!

win10 is very bloated, does not have good compatibility with legacy software, it would be better to use DosBox!

i mean i get running legacy software that simply don't have a modern equivalent, and i suppose i get running it on 16 bit hardware 🤔

I imagine ReactOS could do a Wine-like approach where Win16 applications are actually run in 32-bit mode

wine just calls out to dosbox for that

<hbelusca (Gmunu=8PiG/c4Tmunu+)> well basically, our ntvdm.

wine just calls out to dosbox for that

I'm talking about Win16 programs, not DOS programs.

Linux can't run 16-bit processes. Wine segments memory in 32-bit mode and basically upgrades the executable code in Win16 applications to run as native 32-bit programs.

finally found this document that explains it... that took a while xD

https://web.archive.org/web/20160822191913/http://www.wine-staging.com/news/2016-02-10-blog-wine-16bit.html

<hbelusca (Gmunu=8PiG/c4Tmunu+)> Well... isn't that the usual thunking technique? (it's used by wow16 too)

https://twitter.com/filipnavara/status/1367418498146795521

<hbelusca (Gmunu=8PiG/c4Tmunu+)> In any case we haven't seen any trace of it.

sooo let me ask again: why would you write 16 bit software 🤔

I have an example in my family: my brother is a chemist, he sometimes needs to use a spectrometer that only works with an old DOS program on a pentium class pc. Sometimes he needs to do trivial tasks on that pc, so he writes small programs in Fortran, and he sometimes needs to use his program on a newer pc. Ofc I know this is a one in a million case. But some cases like this still exist

i mean that more a case for 16 bit software on modern pcs no?

He needs his program on both, sometimes. Yes, I agree it's really rare.

<hbelusca (Gmunu=8PiG/c4Tmunu+)> I've already seen quite a few instances, especially in biology, but in chemistry as well, of programs that control some particular hardware, or some educational programs, that are DOS apps or similar.

<hbelusca (Gmunu=8PiG/c4Tmunu+)> So I'm not surprised.

<hbelusca (Gmunu=8PiG/c4Tmunu+)> And if the hardware associated with these apps still work after 10 or 20+ years (it's not like Apple BS or similar, i.e. doesn't have to break every 2 years), then there is no reason to change it.

yeah i've heard of those cases

why not just use freebasic, it works on dos and has a compiler for dos and also works on new oses and has a compiler on them too

<hbelusca (Gmunu=8PiG/c4Tmunu+)> And if the hardware associated with these apps still work after 10 or 20+ years (it's not like Apple BS or similar, i.e. doesn't have to break every 2 years), then there is no reason to change it.

Yes, scientific strumentation can have enormous prices, both direct and for resampling/measure adaptations/human work hours to reset everything at the same point

why not just use freebasic, it works on dos and has a compiler for dos and also works on new oses and has a compiler on them too

Because some of these damn things require their very own language and program

i really see a good case for reactos 64 bit here, if it keeps the great ntvdm of the 32 bit version

https://twitter.com/filipnavara/status/1367418498146795521

I'm mostly out of tests, especially USB testing will be much appreciated and probably shared instantly.

Is it yours?

ReactOS boots on Dell Inspiron N4020 with LiveUSB, resolution up to 1024x768, internal mouse and keyboard works (no reaction to Ctrl-Alt-Del though), drives correctly detected.

Is it yours?

Yes, mine.