Frantisek Hanzlik | 21 Apr 01:37 2014
Picon

FreeDOS freecom not know 'loadhi', display not know 'vga' (?)

Just when I tried pure autoexec.bat file from latest dosemu-devel,
I bump to problem with loading display.exe. Line 14 in autoexec.bat
is 'rem loadhi display con=(vga,437,2)', but when uncommented, then
give me two errors:

1) 'FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]' which
is in dosemu-freedos-1.0-bin.tgz tarball referenced at:

http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download

not know 'loadhi' command; only 'lh' may be used.

2) display-0.13b report error:

FreeDOS DISPLAY ver. 0.13b
Syntax error (006) Unknown hardware device name

when I retain its parameters. But when I use 'ega' instead of 'vga',
then all is fine. I not know, when it is display.exe problem (it's
documentation say that 'vga' is allowed) or dosemu problem (e.g.
it emulate only EGA card and not VGA).

According this, and as this autoexec.bat file has in its head that
it should be for DOSEMU + FreeDOS, maybe this change should be better:

--- dist/autoexec.bat.old	2014-04-21 00:38:46.273663431 +0200
+++ dist/autoexec.bat	2014-04-21 00:50:12.053661641 +0200
 <at>  <at>  -11,7 +11,7  <at>  <at> 
 lredir d: linux\fs%DOSDRIVE_D%
 :nodrived
(Continue reading)

Frantisek Hanzlik | 20 Apr 18:36 2014
Picon

weird lines in boot.log after 'g_printf("CONSOLE MSG:...'

Hello, I (want minimize boot.log for bug report) noticed a strange
lines in boot.log, that I can not explain. They begins with '3d4 '
string, then is character '{' (mostly, but sometimes also '>' or '<')
and then 1-4 hexadecimal digits. These lines occurs after INT10
debug output (then are usually two):

Do INT0x10: Using caller_function()
INT10: near fc00:00000114
INT10: AH=0e AL=53 'S'
3d4 { 30e
3d4 { 210f
...
Do INT0x10: Using caller_function()
INT10: near fc00:00000114
INT10: AH=0e AL=72 'r'
3d4 { 30e
3d4 { 230f

but I see more also:

INT10: cleared screen: screen_adr b8000
3d4 { e
3d4 { f
3d4 { e
3d4 { f
3d4 { e
3d4 { f
3d4 { e
3d4 { f
3d4 { e
(Continue reading)

Frantisek Hanzlik | 20 Apr 13:07 2014
Picon

dosemu devel from git start DOS only from C:?

Hello, I just trying compile and run last dosemu devel branch, with
dosemu dosemu-freedos-1.0-bin.tgz and it see as now dosemu starts dos
from drive C: (resp from '~/.dosemu/drives/c', which is symlink to
 '~/.dosemu/drive_c' - where are only autoexec.bat, config.sys and
tmp/). Thus dosemu will not find DOS and ends with message:

Sorry, there is no operating system here:
/home/hanzlik/.dosemu/drives/c

Please try to install FreeDOS from dosemu-freedos-*-bin.tgz

Just when I copy FreeDOS 'kernel.sys' (from 'D:', which is symlink
'~/.dosemu/drives/d' pointing to '/usr/share/dosemu/drive_z', where
dosemu-freedos-1.0-bin is installed/unpackaged) to 'C:'
('~/.dosemu/drives/c') and dosemu starts fine.

Please, it is intended to be DOS started from C: now? IMO in earlier
(maybe 'stable' version) was DOS started from drive D: (and this is
perhaps still supposed in config.sys, where commands refer to D: and
as lately as its end is DOS lredir-ed to Z:)
Or I'm doing some mistake?

Thanks, Franta

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
(Continue reading)

Edward Mendelson | 20 Apr 12:44 2014

Re: VESA mode 0x10B - 132 columns ? 50 rows -, is it possible?

I don't have a Linux system running at the moment, but I was able to get 
a 132x50 DOSEMU through the methods described here:

http://www.columbia.edu/~em36/wpdos/linux.html#screensize

This does not use a VESA mode. Instead, it simply displays the default 
text font in a larger window, which I think is preferable because far 
easier to read.

Edward Mendelson

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
Frantisek Hanzlik | 20 Apr 11:35 2014
Picon

Debug classes not complete in man pages?

'man dosemu.bin' shows these 29 classes:
        d  disk            R  disk read        W  disk write
        D  int 21h         C  cdrom            v  video
        X  X support       k  keyboard         i  port I/O
        s  serial          m  mouse            #  default ints
        p  printer         g  general          c  configuration
        w  warning         h  hardware         I  IPC
        E  EMS             x  XMS              M  DPMI
        n  IPX network     P  Pkt-driver       S  SOUND
        r  PIC             T  IO-tracing       Z  PCI-BIOS
        A  ASPI driver     Q  mapping driver

but these 33 are printed with
sed -n -e "/register_debug_class('/{ s/[^(]*(//; s/,[^,]*, \"/ /;
s/\");$//;p}" src/base/async/dyndeb.c|sort|pr -3 -w 90

'A' ASPI		    'i' i/o instructions (in/out)  'r' PIC request
'a' Set all levels	    'I' IPC			   's' serial
'C' CDROM		    'j' joystick		   'S' SOUND
'c' configuration	    'k' keyboard		   't' dpmi trace
'd' disk msgs		    'M' DPMI			   'T' I/O trace
'D' dos int 21h		    'm' mouse			   'v' video
'#' default int		    'n' IPX network		   'W' disk WRITE
'e' cpu-emu		    'P' Packet driver		   'w' warnings
'E' EMS			    'p' printer		           'x' XMS
'g' general messages	    'Q' Mapping driver  	   'X' X support
'h' hardware		    'R' disk READ		   'Z' PCI

(or 32 when leave out 'a': Set all levels)
Some perhaps are missing.
(Continue reading)

Frantisek Hanzlik | 8 Apr 07:39 2014
Picon

VESA mode 0x10B - 132 columns × 50 rows - is it possible?

Hello all DOSEMU enthusiasts,

first, thanks for developing and evolving this powerfull SW piece!
And now my current research (so far in vain): I want my DOS text app
run in text mode with resolution 132 columns × 50 rows - which should
be VESA 2.0 (maybe as early as VESA 1.2) mode 0x10B, according e.g.:

http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Modes_defined_by_VESA

but so far I'm unsuccessfull (except in the case when I run DOSEMU in
console mode in console/X window with this resolution, but this is
perhaps obvious).
Nevertheless, modes 0x10A (132 x 43) and 0x010C 132 x 60 are working
fine under xdosemu. Problem I have only with this 132 x 50 mode.

I'm using DOSEMU + FreeDOS 1.0, and thus potentially may be problem
in FreeDOS, but I suspect rather DOSEMU, as:

1) when I run commands 'mode con cols=132 lines=43', resp. 'mode con
cols=132 lines=60', I will get responses:

VESA 2.0 'DOSEMU VGA/VBE 2.0 Emulator', mode 0x0003, 4096k for BIOS, 57 modes.
VESA mode 0x010A: 132 x 43 with 8 x 11 font.

resp.

VESA 2.0 'DOSEMU VGA/VBE 2.0 Emulator', mode 0x0003, 4096k for BIOS, 57 modes.
VESA mode 0x010C: 132 x 60 with 8 x 8 font.

and right mode is set.
(Continue reading)

Andrew Bird | 30 Mar 12:03 2014
Picon

Some patches against the devel branch

Hi Stas, Bart,
     Firstly, sorry if you already saw this on linux-msdos list, I 
didn't realise this list existed but I'll only post here from now on.
     Here are some patches I made against today's devel branch. I had no 
specific bug to fix, but just wanted to fix some minor bounds checks and 
initialisation issues. If you appreciate what I am trying to do I'll 
spend some more time looking for others.

	All compile successfully, but I have very few DOS programs to exercise 
Dosemu properly. Any standalone memory exerciser programs for XMS, EMS 
or DPMI would be helpful?

Hope it helps,

Andrew
------------------------------------------------------------------------------
_______________________________________________
Dosemu-devel mailing list
(Continue reading)

Stas Sergeev | 30 Dec 19:33 2013
Picon

vde networking

Hi, I've created a "vde" branch in git and added
some basic vde support there.
With slirpvde it does mostly the same that the
current "slirp" branch does. Except:
- pings are not supported (there are _fake_ pings in "slirp" branch)
- automatically starting vde_switch is not yet implemented

And it is not packaged by fedora, just the same way
slirp is not.

Whoever is interested, please test, send patches. :)

How to test:
$ vde_switch -s /tmp/switch1 2>/dev/null </dev/null &
$ slirpvde -s /tmp/switch1 --dhcp
In dosemu.conf:
$_vdeswitch = "/tmp/switch1"
... and run dosemu.

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
Bart Oldeman | 28 Jul 20:03 2013
Picon
Picon

Re: Merging master/devel (was DOSEMU Version 2 has been Released)

On 10 July 2013 12:27, Stas Sergeev wrote:
> But, out of sudden, "devel" happened to have so many
> big or untrivial changes, that no one seems to be willing
> to spend the time on sorting them out and merge to master.
> I think I'll just end up merging it to master as-is eventually,
> but Bart promised to take a look at a few things, so it is
> all upside down for now.

As you could see I finally started merging pieces of devel back to
master, mostly using "git cherry-pick". I am now at the point where
plain cherry-picks no longer work and some patches need backporting,
but it's not very hard (e.g. commit 15863b65).

Where it breaks for me (for console graphics vc switching) is patch

commit 0932e960ee46d151ef6e96f78bc0427f41305b10
Author: Stas Sergeev <stsp@...>
Date:   Mon Jan 28 15:48:29 2013 +0400

    lowmem: add api for rm stack switching, and use it for vbe int10 callback

the api itself is harmless of course, but there is also this change in
the same patch:

   *p = 1;
-  pic_cli();
+  clear_IF();
   do_intr_call_back(0x10);
-  pic_sti();
   *p = 0;
(Continue reading)

Stas Sergeev | 22 Jul 12:43 2013
Picon

Fwd: Mail delivery failed: returning message to sender

Eric, again mail bounces...

-------- Исходное сообщение --------
Тема: 	Mail delivery failed: returning message to sender
Дата: 	Mon, 22 Jul 2013 14:41:33 +0400
От: 	mailer-daemon@...
Кому: 	stsp@...

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

   ebiederm@...
     SMTP error from remote mail server after RCPT TO:<ebiederm@...>:
     host mx.xmission.com [166.70.12.20]: 550-XM-RJCT22:
     [94.100.176.90] is prohibited from connecting to XMission mail
     550-servers due to high spam volume. See the following for more information:
     550 http://postmaster.xmission.com/senders/rbls.php?check_rbl=Submit&address=94.100.176.90

------ This is a copy of the message, including all the headers. ------

Return-path: <stsp@...>
Received: from [176.120.3.179] (port=35108)
	by smtp13.mail.ru with esmtpa (envelope-from <stsp@...>)
	id 1V1DYI-0000wn-G0; Mon, 22 Jul 2013 14:41:14 +0400
Message-ID: <51ED0C5C.9010305@...>
Date: Mon, 22 Jul 2013 14:41:32 +0400
From: Stas Sergeev <stsp@...>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
(Continue reading)

Stas Sergeev | 10 Jul 18:27 2013
Picon

Re: Revisit COPYING.DOSEMU (Re: DOSEMU Version 2 has been Released)

10.07.2013 19:58, solarflow99 пишет:
> oh ok, I thought it was more of them taking 1.4.0 and not allowed to 
> take from git.
No, I think everyone moved to git, even debian.
That's good, at least better than to abandon completely. :)
It would be a shame if someone takes a "very buggy"
git by chance, but, if it was taken from "master", the
"coloured cap" cannot happen; its just better to fix the bug
instead and ask to re-package.

>   I've also been making RPM releases from the latest git which may 
> have had some bugs but was better than using the very old 1.4.0 :)
Maybe the master had fewer problems by that date, I
am not sure. Right now I wouldn't package out of it.

>    And like you mention we just didn't have the resources to maintain 
> different branches and stable releases, I guess now there is more of a 
> stable/devel branch in git right?
Yes, that should be the case.
But, out of sudden, "devel" happened to have so many
big or untrivial changes, that no one seems to be willing
to spend the time on sorting them out and merge to master.
I think I'll just end up merging it to master as-is eventually,
but Bart promised to take a look at a few things, so it is
all upside down for now.

> Thanks for cc'ing this to the list, I keep getting rejected with my 
> gmail account.
OK.

(Continue reading)


Gmane