[Prev][Next][Index][Thread]

Re: Odd problem with E/DOS 2.0b1 on Toshiba notebook



>>>>> "Donald" == Donald Burr <d_burr@ix.netcom.com> writes:
In article <31c31330.1203630@smtp.ix.netcom.com> d_burr@ix.netcom.com (Donald Burr) writes:


    Donald> due to various misfortunes, I have had to exchange my old
    Donald> notebook computer for a Toshiba Satellite 105CS machine.
    Donald> Ok, I'm not too disappointed, hey I went from a 486DX4/100
    Donald> to a Pentium-75 for about the same price.  Only one
    Donald> problem: Executor and perhaps UniVBE/Display Doctor are
    Donald> behaving oddly.

    Donald> The first problem is that, when Executor quits, it does
    Donald> not clear the screen.  I run Exec from a batch file which
    Donald> writes some things to the screen after Executor runs.
    Donald> Now, those messages still get written, but ON TOP OF the
    Donald> Executor graphic display.  Weeeeird, no?

Yes, weird.  The whole reason Display Doctor (formerly UniVBE) is
needed is that although VESA 1 and VESA 2 are standards, most
combinations of video cards and video drivers don't properly implement
the standards!

Of course it *could* be a bug in Executor, but we're not aware of this
problem elsewhere, so I'd guess it's an improper VESA implementation.
Is this with Display Doctor 5.1 or 5.2?

    Donald> I've also noticed some problems with graphics artifacts in
    Donald> at least one program (Bolo 0.99.7 (I think that's the
    Donald> version, anyway it's the one on the E2 CD).  Although I
    Donald> did notice that Bachman was behaving "strangely", though I
    Donald> can't really define what "strangely" is -- maybe the
    Donald> screen is a tad more sluggish, or what?

If you're not linearly mapped, some applications will be slower and/or
leave artifacts.  With Bolo you should be able to choose "QuickDraw
Only" or something like that from one of the menus.  NOTE: Bolo was
only on the beta0 CD-ROM, it never made it onto the more widely
distributed beta1 CD-ROM and it won't be on E2.  There were other
problems with it under Executor.

    Donald> The problem in Bolo is that the screen does not update
    Donald> properly.  When I try pulling down menus, I get nothing,
    Donald> although if I keep the mouse down and "paint" the cursor
    Donald> over where the menu should be, the menu gradually fades
    Donald> in.  If I select "About Executor" the dialog does not
    Donald> appear, although if I move the mouse around enough, I can
    Donald> "paint it in".

Right.

    Donald> Perhaps these are related to the fact that neither UniVBE
    Donald> 5.1 nor Display Doctor 5.2 offers VBE 2.0 features (mainly
    Donald> linear framebuffer), even though I install them properly
    Donald> (follow all the instructions like a good little boy).
    Donald> Hmm... probably time to contact SciTech support by e-mail.
    Donald> Wish I had their e-mail address...

Their web page is http://www.scitechsoft.com

I'm surprised it can't drive your new machine in linear frame buffer
mode.  We just got a Micron Transport for demo purposes and we
verified that the chipset in it was supported by Display Doctor before
we bought the machine, but I was astounded by the number of chipsets
they support, although support doesn't necessarily imply the ability
to linearly map.

    Donald> Anyway, here's the details of my old system (where
    Donald> Executor worked 100%, and UniVBE 5.1 did linear
    Donald> framebuffer and all) and my new notebook (where neither
    Donald> works right): Any and all help is greatly appreciated.
    Donald> Thanks!

    Donald> Old system: CTX EzBOOK Intel 486DX4/100 8 MB RAM 540 MB HD
    Donald> Western Digital 90C24x graphics chip 1 MB video RAM 10.4"
    Donald> active matrix TFT screen

    Donald> New system: Toshiba Satellite 105CS Intel Pentium/75 8 MB
    Donald> EDO RAM 540 MB HD Chips & Technologies F65548 graphics
    Donald> chip 1 MB video RAM 10.4" DSTN dual-scan screen

I'm not familiar with that chipset.  I think you should tool around on
the SciTechSoftware web site.  Good luck.

One more reason for us to wrap up E2 and get to work on the native
Win32 version.

--Cliff
ctm@ardi.com



References: