public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: phrostie <pfrostie@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: PharLap 386asm crashes every third time
Date: Tue, 19 Nov 2002 10:20:43 -0800 (PST)	[thread overview]
Message-ID: <20021119182043.53171.qmail@web11002.mail.yahoo.com> (raw)
In-Reply-To: <ardta6$3eg$1@main.gmane.org>

being a user and not a programmer i don't understand the details, but in the
end it has to do with Ring-0.  as i under stand it (subject to error) it's a
memory mode that allows direct control of memory.  this creates a conflict with
linux which already has control and has no intention of giving that up.

as to whether or not a pharlap emulator could be created i don't know.

.014999$

--- Arno Seitzinger <spam2_arno@lucienet.de> wrote:
> Hi Newsgroup,
> 
> for developing software which has to run under dos with the Phar Lap dos 
> extender I use the Phar Lap 386asm V8.0. I currently run it under vmware 
> but would like to run it under dosemu because of some unresolved sharing 
> problems. I know that dosemu and Phar Lap are incompatible in some way, but 
> do not understand why the command
> 386asm -nolist sbhd1.asm
> assembles two times and crashes on the third run as, IMHO, it should either 
> run as often as I want to run it or crash dosemu the first time it is run.
> The error message is
> 
> 386|ASM: 8.0 -- Copyright (C) 1986-95 Phar Lap Software, Inc.
> /usr/bin/dosemu: line 327:  3287 Speicherzugriffsfehler  
> $DOSEMU_BIN_PATH/bin/dosemu.bin $XFLAG --Flibdir $BOOT_DIR_PATH/conf 
> --Fimagedir $BOOT_DIR_PATH -f $BOOT_DIR_PATH/conf/dosemurc $OPT_I $STRING_I 
> -O $@ 2>$BOOT_DIR_PATH/boot.log
> esw44@esw44:~>
> 
> Speicherzugriffsfehler means some kind of memory access error.
> I am running Suse Linux 8.1 and dosemu 1.0.2.0 with Freedos (but the problem 
> also occured under previous Linux versions).
> 
> Any help would be appreciated
> 
> Arno
> 
> 
> -
> 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


=====
phrostie
Oh I have slipped the surly bonds of DOS
and danced the skies on Linux silvered wings.
http://pfrostie.freeservers.com/cad-tastrafy/
http://www.freelists.org/webpage/cad-linux

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com

  reply	other threads:[~2002-11-19 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 17:47 PharLap 386asm crashes every third time Arno Seitzinger
2002-11-19 18:20 ` phrostie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 19:50 Stas Sergeev
2002-11-19 22:57 ` Arno Seitzinger

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=20021119182043.53171.qmail@web11002.mail.yahoo.com \
    --to=pfrostie@yahoo.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