public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Junior Alves <alves@coslinux.com.br>
To: Bart Oldeman <oldeman@math.ohio-state.edu>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Invalid Opcode
Date: Tue, 11 Feb 2003 15:31:22 -0200	[thread overview]
Message-ID: <3E49336A.9050100@coslinux.com.br> (raw)
In-Reply-To: <Pine.LNX.4.33.0302111213430.1209-100000@enm-bo-lt.localdomain>

Strange.... I got the exactly same message from MS-DOS and DR-DOS on 
DOSEMU, but without DOSEMU everything goes fine, including on FreeDOS.

I looked by this message on FreeDOS and I found anything.

There is another thing to do?

Thanks,

Gustavo

Bart Oldeman wrote:

>On Tue, 11 Feb 2003, Gustavo Junior Alves wrote:
>
>  
>
>>I tried with version 1.1.4.1 and 1.1.4.13, but still the same error message.
>>
>>    
>>
>>>On Tue, Feb 11, 2003 at 10:57:19AM -0200, Gustavo Junior Alves wrote
>>>
>>>
>>>      
>>>
>>>>I trying to call a clipper application, but the system returns:
>>>>
>>>>Invalid Opcode at 009B 202E 0246 2499 0246 0000 0000 0000 0000 0000 0000
>>>>0000 0000
>>>>
>>>>What this means???
>>>>        
>>>>
>
>it's a message from FreeDOS that your application tries to execute an
>invalid instruction. The hex numbers form a stack trace.
>
>Your application may or may not work in other DOSes than FreeDOS.
>
>Bart
>
>-
>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:[~2003-02-11 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11 12:57 Invalid Opcode Gustavo Junior Alves
2003-02-11 13:03 ` Reinhard Karcher
2003-02-11 13:55   ` Gustavo Junior Alves
2003-02-11 17:15     ` Bart Oldeman
2003-02-11 17:31       ` Gustavo Junior Alves [this message]
2004-04-12  9:38 ` Mickey

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=3E49336A.9050100@coslinux.com.br \
    --to=alves@coslinux.com.br \
    --cc=linux-msdos@vger.kernel.org \
    --cc=oldeman@math.ohio-state.edu \
    /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