Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!wuarchive!udel!mmdf From: archer%segin4.segin.fr@relay.prime.com (Vincent Archer) Newsgroups: comp.os.minix Subject: Re: ST1.5.10 patch2 scrolling problem Message-ID: <29616@nigel.ee.udel.edu> Date: 6 Sep 90 11:20:06 GMT Sender: mmdf@ee.udel.edu Lines: 40 Frans Meulenbroeks said: (after some explanations on the awful /etc/ttys file) >Yes, I'd like to know too if anyone else encountered this problem. >I can think of a few things to try to get this running: >- try NR_CONS set to 1 >- try the following change in kernel/stmain.c line 248. > current contents: > ad -= 0x7d00L; /* size of VIDEO memory */ > Instead of 0x7d00L there used to be 0x8000L. > The docs say the screen memory used is 32000 bytes. > Therefore I changed the 8000 into 7d00. > This saves 768 bytes but puts the screen pointer on a 256 byte boundary, > while 8000 puts the screen pointer on a 512 byte boundary. > If the STe has different conventions with respect to its screen > memory this change may cure it. > For virtual consoles there is a similar change required in stvdu.c > (around line 950) Now, the STe really has different hardware: Its screen base is not constrained by a boundary anymore!!! You still need to use a word-aligned screen base; it's 68000 world we're talking about. But there's an additional screen controller byte (can't remember the exact address, it's somewhere in my notes) to specify the low bytes of screen base. >stvdu has been reworked greatly between 1.5.10 patch 1 and patch 2. >I've tested this on my 1040, where it ran without problem. >However, since I do not have an STe, it has not been tested on that >hardware. > >Any suggestions/feedback/fixes are greatly appreciated. If I get my hands on a STe (there's one at my local computer club), I'll try a STf-working kernel on it. Vincent Vincent Archer | Email:archer%segin4.segin.fr@relay.prime.com "Wrong thing to say, right thing to do; do as I say, not as I do..."