From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: compiles, but will not run on newer cpu's
Date: Fri, 26 Dec 2003 15:37:11 -0600 [thread overview]
Message-ID: <20031226213711.GD7902@dbz.icequake.net> (raw)
In-Reply-To: <3FE81004.5797C172@firstlight.net>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Tue, Dec 23, 2003 at 09:51:00AM +0000, norseman wrote:
> Old machine died. Kept HardDrive. Got new machine.
> Transfered over sys and pgms. New machine boots, runs.
> DOSEMU 1.0.2 was in use. Will not run. Re-compiled OK,
> still will not run. Got 1.1.14. Compiles OK. Won't run.
> New machine has Intell P-4 Mobile 2.4Ghz. Slackware 8.0
> on old and new. Anybody have an idea what is happening?
>
> (same is true of WINE if interested.)
With "will not run" you should also give some more information.
A strace would be helpful.
--
Ryan Underwood, <nemesis@icequake.net>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-26 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 9:51 compiles, but will not run on newer cpu's norseman
2003-12-23 18:24 ` Justin Zygmont
2003-12-26 21:37 ` Ryan Underwood [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=20031226213711.GD7902@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.