mcphail@dataco.UUCP (Alex McPhail) (01/24/91)
I have MKS Toolkit, and DesqView (the latest version). When I try to run 'vi' in MKS Toolkit while I am in a DesqView window, it starts to run, then it beeps forever. I can get Deskview's attention with the ALT key, but the beeping doesn't stop until I actually close the window. My vi works perfectly otherwise (ie: not under DesqView). I have a 386SX with 2M RAM. Does anyone out there have any ideas? Have you had this problem before? Thanks in advance. ________ |\ / (613) 592-6500 | \ / FAX: 592-7427 | \ / Alex McPhail |---X Email to mcphail@dataco | / \ The opinions are mine alone. | / \ The rest is yours. |/_____\ Alex
plim@hpsgwp.sgp.hp.com (Peter Lim) (01/25/91)
/ mcphail@dataco.UUCP (Alex McPhail) / 3:55 am Jan 24, 1991 / writes:
$ I have MKS Toolkit, and DesqView (the latest version). When I
$ try to run 'vi' in MKS Toolkit while I am in a DesqView window,
$ it starts to run, then it beeps forever. I can get Deskview's
$ attention with the ALT key, but the beeping doesn't stop until
$ I actually close the window.
$
$ My vi works perfectly otherwise (ie: not under DesqView). I
$ have a 386SX with 2M RAM.
$
$ Does anyone out there have any ideas? Have you had this
$ problem before?
$
Co-incidentally, I have seen exactly this problem on my 25 MHz 386 before.
I was using DesqView 2.26 and QEMM 4.23 then. I can't remember if I tried
after upgrading to QEMM 5.0. I thought it was probably some compatibility
problems with my 386 then. So, I didn't ask the net. May be using
DesqView 2.30 will solve the problem. .... but I don't use DesqView
anymore. .... I just like Windows more .... No flame ..
$ Thanks in advance.
$
Sorry I can't give you a verified fix.
Regards, . .. ... .- -> -->## Life is fast enough as it is ........
Peter Lim. ## .... DON'T PUSH IT !! >>>-------,
########################################### :
E-mail: plim@hpsgwg.HP.COM Snail-mail: Hewlett Packard Singapore, :
Tel: (065)-279-2289 (ICDS, ICS) |
Telnet: 520-2289 1150 Depot Road, __\@/__
Singapore 0410. SPLAT !
#include <standard_disclaimer.hpp>ian@unipalm.uucp (Ian Phillipps) (01/28/91)
plim@hpsgwp.sgp.hp.com (Peter Lim) writes: >/ mcphail@dataco.UUCP (Alex McPhail) / 3:55 am Jan 24, 1991 / writes: >$ I have MKS Toolkit, and DesqView (the latest version). When I >$ try to run 'vi' in MKS Toolkit while I am in a DesqView window, I don't know if it's relevant, but the free "vi" (now called Calvin) needs two text screens to run properly. This is set up in the "advanced" screen.
mlord@bwdls58.bnr.ca (Mark Lord) (01/29/91)
In article <3360011@hpsgwp.sgp.hp.com> plim@hpsgwp.sgp.hp.com (Peter Lim) writes: </ mcphail@dataco.UUCP (Alex McPhail) / 3:55 am Jan 24, 1991 / writes: < <$ I have MKS Toolkit, and DesqView (the latest version). When I <$ try to run 'vi' in MKS Toolkit while I am in a DesqView window, <$ it starts to run, then it beeps forever. I can get Deskview's <$ attention with the ALT key, but the beeping doesn't stop until <$ I actually close the window. <$ <$ My vi works perfectly otherwise (ie: not under DesqView). I <$ have a 386SX with 2M RAM. <$ <$ Does anyone out there have any ideas? Have you had this <$ problem before? <$ <Co-incidentally, I have seen exactly this problem on my 25 MHz 386 before. <I was using DesqView 2.26 and QEMM 4.23 then. I can't remember if I tried <after upgrading to QEMM 5.0. I thought it was probably some compatibility <problems with my 386 then. So, I didn't ask the net. May be using <DesqView 2.30 will solve the problem. .... but I don't use DesqView I missed the start of this thread, but I have an idea anyway.. When using an initial screen size of 50x80 for a desqview window, DV does not correctly program the screen buffer length. It leaves it set to 4096, which would be correct for a 25x80 screen size. DV does set the rows/columns variables (BIOS stuff) correctly, but seems to miss out on the buffer size. This causes ELVIS (a VI clone) to mess up under desqview. Perhaps MKS has the same troubles? Then again, maybe my machine is weird, and nobody else has this problem. -- ___Mark S. Lord__________________________________________ | ..uunet!bnrgate!mlord%bmerh724 | Climb Free Or Die (NH) | | MLORD@BNR.CA Ottawa, Ontario | Personal views only. | |________________________________|________________________|
andy@mks.com (Andy Toy) (01/30/91)
In article <328@dcsun21.dataco.UUCP> mcphail@dataco.UUCP (Alex McPhail) writes: >I have MKS Toolkit, and DesqView (the latest version). When I >try to run 'vi' in MKS Toolkit while I am in a DesqView window, >it starts to run, then it beeps forever. You must set the DESQview window to indicate that the application does not write text directly to the screen and not to virtualise text and graphics. The beeping is caused by vi's clear screen sequence which writes SPACE followed by \007 (character and attribute screen bytes). It does this for each screen location. If you watch the cursor, you will notice that it moves before each beep. This will take a long time to complete since the BEL \007 will take a while to `print'. DESQview is somehow converting the screen writes to "printing". This will be fixed in the next release. -- Andy Toy <andy@mks.com> UUCP: ...!uunet!watmath!mks!andy Technical Support <support@mks.com> Phone: +1-519-884-2270 Mortice Kern Systems Inc. <inquiry@mks.com> Phone: +1-519-884-2251 35 King Street North, Waterloo, Ontario N2J 2W9, CANADA Fax: +1-519-884-8861