DOS ain't dead - Graphic Vision File Manager 2.65

Graphic Vision File Manager 2.65 | "A"-bug (Announce)

posted by DOS386, 22.12.2007, 20:52

Rugxulo wrote (in old thread):

> ke2007sep15.zip has the latest kernel

But it's not from 2007-Sep-15. There are 2 dates, one before and one after Sep-15 in :confused:

Laaca wrote:

> once FreeDOS installed you don't need SYS to update kernel.
> It is enough just to rewrite it by newer version.

:-) No other OS can update the kernel that easily (but need to reboot to activate)

Jaybur wrote:

> And this kernel contains a bug fix for 21h/29xx - Parse Filename into FCB
> means that GVFM no longer thinks that every drive up to LASTDRIVE is valid

Confirm :-)

> New video memory write speed test added to the "Change Video Mode" dialog.

Funny colourful garbage :-) but I have no clue why you test the bankswitch time for the LFB - is it related to your 16-bit DPMI ?

> Some changes made to README.TXT
>
> VESAMTRR can improve graphics throughput by as much as 50 times on

Should be 5 only ?

> MACHINES WITH PENTIUM 1 OR OLDER PROCESSORS DO NOT NEED AND SHOULD NOT USE
> IT.

No big danger, NO NEED FOR ALL UPPERCASE ;-) - maybe "VESAMTRR (or any other product with same goal) won't work with Pentium 1 or older processors.

> that VESAMTRR needs a DPMI host such as HDPMI32.EXE that runs in ring 0

Complaining again :crying: - I've not yet seen a DPMI host that would be that evil to run itself outside of Ring0 :clap: - maybe "VESAMTRR is a 32-bit DPMI application and needs access to Ring0 via an IDT gate, and requires an appropriate DPMI host like HDPMI32 to run."

> \DOS\DRIVERS\VIDEO\VESAMTRR -c=A000-BFFF

Your path ? ;-)

> VESAMTRR is not a TSR and so will not ...

maybe "VESAMTRR is not a TSR and so will not take up any memory once it has
done its thing (change special resisters inside the CPU)."

> that enables write combining to the video display memory.

add "replacing "FASTVID" product distributed with GVFM in the past." ? ;-)

The "A"-bug persists with new GVFM and new kernel. Anyway, I got additionally
a "Runtime error 216 at C7:969D" followed by a GPF in Ring0 :lol3:

It's pretty random whether the floppy access gives up silently after some time, complains about "Drive A is not ready" (it's still on the ban list, BTW), or aborts with error 216 and boom.

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Post reply

Complete thread:

Graphic Vision File Manager 2.65 - jaybur, 22.12.2007, 19:21 (Announce)
- Graphic Vision File Manager 2.65 | "A"-bug - DOS386, 22.12.2007, 20:52
  - Graphic Vision File Manager 2.65 | "A"-bug - jaybur, 22.12.2007, 21:18
    - Graphic Vision File Manager 2.65 | "A"-bug - DOS386, 22.12.2007, 21:41
      - Graphic Vision File Manager 2.65 | "A"-bug - jaybur, 22.12.2007, 21:56
  - Graphic Vision File Manager 2.65 | "A"-bug - Steve, 23.12.2007, 04:58
  - GVFM 2.65 | "A"-bug | FreeDOS "Sep. 15" kernel - Rugxulo, 24.12.2007, 14:32
    - GVFM 2.65 | "A"-bug | FreeDOS "Sep. 15" kernel - jaybur, 26.12.2007, 17:16
- GVFM 2.66 beta /"Drive A" bug - jaybur, 26.12.2007, 17:42
  - GVFM 2.66 beta / "Drive A" bug / DEC CX LOOP @b - DOS386, 26.12.2007, 22:36
  - GVFM 2.66 beta /"Drive A" bug - Laaca, 27.12.2007, 23:04
    - GVFM 2.66 beta /"Drive A" bug - jaybur, 28.12.2007, 03:47
    - GVFM 2.66 beta /"Drive A" bug - jaybur, 28.12.2007, 05:27
      - GVFM 2.66 beta /"Drive A" bug - Laaca, 28.12.2007, 17:15
        GVFM 2.66 beta /"Drive A" bug - jaybur, 28.12.2007, 18:56