public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Baldo <ibaldo@adinet.com.uy>
To: Jens Knoell <jens@surefoot.com>
Cc: linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: Unable to run two instances (dosemu + foxpro)
Date: Thu, 13 Nov 2008 10:30:54 -0200	[thread overview]
Message-ID: <491C1DFE.1040502@adinet.com.uy> (raw)
In-Reply-To: <491B6146.2080201@surefoot.com>

    Hello.
    Have you looked at the .dosemu/boot.log file?
    BTW, never saw a DOS with more than 64Mib of XMS or EMS memory, at 
least DR-DOS or MS-DOS didn't allow it! Maybe a FreeDOS extension? :-)
    Having much less EMS and XMS memory would be better, since those 
programs wheren't designed for so much memory, so, using 4Mib or 8Mib 
should be plenty for them, try reducing the amount of memory, maybe that 
causes the problem?
    Bye.



El 12/11/08 21:05, Jens Knoell escribió:
> Hi
>
> I've been banging my head against the wall for a few days now and 
> cannot seem to find a solution.
>
> My problem is that I cannot seem to run FoxPro for DOS more than once 
> at the same time. I've basically set dosemu as a log in shell for a 
> user, lets name him Mike. He logs in, opens foxpro, works. At the same 
> time I want to open up foxpro as a different user, lets name him John. 
> Foxpro just exits without any error message.
>
> I'm stumped. Any ideas?
>
> -Jen
>
> ---Some info about the installation---
> Versions:
> FreeCom version 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00]
> dosemu-1.4.0.0
> foxpro 2.6 (DOS)
>
> Memory:
> Memory Type        Total       Used       Free
> ----------------  --------   --------   --------
> Conventional          640K        10K       630K
> Upper                 140K        21K       119K
> Reserved              244K       244K         0K
> Extended (XMS)    131,136K       164K   130,972K
> ----------------  --------   --------   --------
> Total memory      132,160K       439K   131,721K
>
> Total under 1 MB      780K        31K       749K
>
> Total Expanded (EMS)                  128M (134,217,728 bytes)
> Free Expanded (EMS)                   128M (134,217,728 bytes)
>
> Largest executable program size       630K (644,768 bytes)
> Largest free upper memory block       116K (119,200 bytes)
> FreeDOS is resident in the high memory area.
>
> -- 
> 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
>

-- 
Ivan Baldo - ibaldo@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: ibaldo@codigolibre.net - http://go.to/ibaldo

--
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

      reply	other threads:[~2008-11-13 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 23:05 Unable to run two instances (dosemu + foxpro) Jens Knoell
2008-11-13 12:30 ` Ivan Baldo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=491C1DFE.1040502@adinet.com.uy \
    --to=ibaldo@adinet.com.uy \
    --cc=jens@surefoot.com \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox