public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Mushroom <p.hayes1@ntlworld.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Terminal Video Problem Solved (and sound too!)
Date: Mon, 02 Dec 2002 21:02:24 +0000	[thread overview]
Message-ID: <asghq2$vfv$1@main.gmane.org> (raw)
In-Reply-To: 3DEB392F.4050504@yahoo.com

Hi

>Stas Sergeev wrote:
>> Mushroom wrote:

> OK, try the attached patch.
>> That's fixed it!!!
> Great!
> Hmm, that was just too easy, there
> is still something fishy about that.
> Do you have $_pci option disabled
> or enabled?

The pci option is disabled - have never enabled it.


> If it is enabled, could you try to undo
> the patch, set $_pci=(off) and reproduce
> the problem?
> Oh, please, do that carefully this time:)
> The suggested way would be to just
> erase and re-install the entire 1.1.3
> sources with 1.1.3.7 patchset (1.1.3.7
> patchset is an essential part here, as
> 1.1.3.0 have its own problems with some
> video boards). You may also use a default
> dosemu.conf as $_pci is disabled there.
> That way the chances of any mistake are
> minimized.

I effectively have that as the builds for 1.1.3.0
1.1.3.7 and 1.1.3.7 patched are all separate and am simply copying the 
binaries to the top of the dosemu tree created by 1.0.2.1
I will however re-do it just to make sure.
 
> I want to be certain that it is not a
> $_pci option guilty for your problems at
> a first place.

I am almost certain I have never changed that flag - in my dosemu.conf I 
have ORIGINAL then a value written next to the description of everything 
I've changed. There is no marker on this line and it says off.

I shall however do as you say as I was obviously not at my most careful when 
I started on this :)
  
>> The graphic card details no longer come up when dosemu starts
> Yes, it was printed by the POST routines,
> which are now bypassed.

Thanks for the explanation.
 
>> The console is left in video mode
> Could you elaborate on that?

The visible text part of the screen is 24 characters wide with the text 
stretched. The first line appears about quarter of the way down the screen. 
If for example I do a dir it appears split into 3 sections vertically down 
the screen:

Correct version:
[root@mushroom dosemu ]#dir
bin       conf    FDChange.log  mkhdimage  README.bindist  Xfonts 
boot.log  dosemu  freedos       pauldos    xdosemu 
[root@mushroom dosemu ]#

What i see (stretched accross whole screen):
GAP
semu ]#dir
 FDChange.log mkhdimage
 freedos      pauldos
GAP
khdimage  README.bindlist
auldos    xdosemu
GAP
.bindist  xfonts
u


> This happens only when you terminate dosemu
> while in graphics mode, right? 

This happens whenever I enter dosemu on the console (as su or graphics are 
disabled) even if my only other command is exitemu. It effects all 
consoles.

>How exactly are you terinating it?
With exitemu. If I tab back to X without exiting the screen is dead as it 
was before but I can get back to x to kill the process.

> I've never seen such a strange behaveour
> here with my Radeon unless I was playing
> with VESA (which is disabled for most
> dosemu users including you).
 
It does seem very strange. I hope to get round my mum & dad's later in the 
week and try a few different hardware combinations.

Paul




  reply	other threads:[~2002-12-02 21:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 10:42 Terminal Video Problem Solved (and sound too!) Stas Sergeev
2002-12-02 21:02 ` Mushroom [this message]
2002-12-02 21:33   ` Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2002-12-03 16:12 Stas Sergeev
2002-12-02 22:24 Stas Sergeev
2002-12-03  5:27 ` Mushroom
2002-12-01 18:37 Newbie with terminal video problems Stas Sergeev
2002-12-01 23:47 ` Terminal Video Problem Solved (and sound too!) Mushroom

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='asghq2$vfv$1@main.gmane.org' \
    --to=p.hayes1@ntlworld.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