What to expect in dosemu-1.2?

What to expect in dosemu-1.2?

[Samium Gromoff]

 I bet some people are wishing to know what new and cool features
the upcoming yet-to-stabilise dosemu-1.2 is going to provide.
Especially given the long wait since the last 1.0 release :-)

 I think it`d be cool if someone will come up summarizing
both the major user-visible changes and the bleeding edge
infrastructural stuff.

 Besides it`s interesting to know how the dosemu and dosbox projects
interrelate, and whether you share any common codebase?

regards, Samium Gromoff

Re: What to expect in dosemu-1.2?

[Justin Zygmont]

mostly bug fixes now I think.  There was an announcement for 1.1.5 and it 
listed most of the major changes.


On Tue, 22 Jul 2003, Samium Gromoff wrote:

> 
>  I bet some people are wishing to know what new and cool features
> the upcoming yet-to-stabilise dosemu-1.2 is going to provide.
> Especially given the long wait since the last 1.0 release :-)
> 
>  I think it`d be cool if someone will come up summarizing
> both the major user-visible changes and the bleeding edge
> infrastructural stuff.
> 
>  Besides it`s interesting to know how the dosemu and dosbox projects
> interrelate, and whether you share any common codebase?
> 
> regards, Samium Gromoff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: What to expect in dosemu-1.2?

[Stas Sergeev]

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

Hello.

Justin Zygmont wrote:
>> - Client-server approach for port I/O, which allows 
> I wonder if this is why there is a lock file problem with
> a modem now?
No, this has nothing to do with locks.
However there is a bug in a serial code
which, but only in case open() fails,
prints a misleading message that the device
is already locked, and leaves a stale lock
file.
The fix is attached. This may not be the
problem you see however. I have no idea
what you see actually, as you have provided
no details. But as I already have a fix to
something similar - try it and maybe it will
help.

[-- Attachment #2: ser_lock.diff --]
[-- Type: text/plain, Size: 583 bytes --]

--- src/base/serial/ser_init.c	Sun Jul 20 17:43:22 2003
+++ src/base/serial/ser_init.c	Wed Jul 23 07:34:57 2003
@@ -245,6 +245,14 @@
   }
   
   com[num].fd = RPT_SYSCALL(open(com[num].dev, O_RDWR | O_NONBLOCK));
+  if (com[num].fd < 0) {
+    error("SERIAL: Unable to open device %s: %s\n",
+      com[num].dev, strerror(errno));
+    if (tty_lock(com[num].dev, 0) >= 0)   		/* Unlock port */
+      com[num].dev_locked = FALSE;
+    com[num].fd = -2; // disable permanently
+    return -1;
+  }
   RPT_SYSCALL(tcgetattr(com[num].fd, &com[num].oldset));
   return (com[num].fd);
 }

Re: What to expect in dosemu-1.2?

[Justin Zygmont]

> - Client-server approach for port I/O, which allows
> dosemu to drop root at startup and makes it secure
> even when running suid-root.

I wonder if this is why there is a lock file problem with a modem now?

Re: What to expect in dosemu-1.2?

[Stas Sergeev]

Hello.

Samium Gromoff wrote:
> I bet some people are wishing to know what new and cool 
> features the upcoming yet-to-stabilise dosemu-1.2 is 
> going to provide.
Yes, but the best way to find that out,
is simply to get the latest version and
give it a try:)

> I think it`d be cool if someone will come up summarizing 
> both the major user-visible changes
OK, the short list of the top-most user-visible
changes would look like this:

- *Real* DPMI support [havy surgery of an old code]

- Unicode support (no more problems with international
keyboard layouts, no problems when DOS uses different
charset than the one of a Linux etc) [complete rewrite
of the entire subsystem]

- *Real* Sound dupport, up to SB16 [almost a complete
rewrite of DSP code, major rework of DMA code, major
update of midid]. That code still lacks Adlib emulation.

- Many improvements for an X code (full-screen, loadable
fonts, instremu understands more instructions etc)

- Client-server approach for port I/O, which allows
dosemu to drop root at startup and makes it secure
even when running suid-root.

- *Real* joystick support [almost a complete rewrite
of an entire subsystem, as far as I can tell]

- Many improvements to a networking code.

- Many stuff that I forgot to mention

- Unlimited amount of a bug-fixes and a limited
amount of a bug-insertions:)

What does the *Real* stand for? Well, 1.0.x claim
to also support that, and indeed, but not that it
works for anything real there:)


> and the bleeding edge infrastructural stuff.
That is practically not possible to summarize.
Take it as almost every subsystem got a reasonable
amount of an attention, many of the long-standing
problems are magically resolved (magically -
considering the amount of developers involved),
thousands lines of problematic/questionable code
is rewritten etc. ChangeLog can give you a wider
view on that.
All that said, there are still a lot of problems
to resolve and there are certainly things that
used to work before but not any longer (CPU-emu,
for example, is now practically useless, while in
1.0 is was rather strong).

> Besides it`s interesting to know how the dosemu and
> dosbox projects interrelate, and whether you share any
> common codebase?
Not at all. dosemu shares neither the code nor
the ideas with dosbox (probably only a couple of
lines stolen from VDMSound, but only a couple of
lines).
DosBox, being highly portable, has a larger
audience as of now. Dosemu have to catch-up
at that point.