DOS ain't dead - FreeDOS EDIT 0.9

DOS386

15.09.2008, 06:05

FreeDOS EDIT 0.9 (Users)

Released 10 days ago ... but doesn't work :-( Anyone else tested ?

Staying with 0.7d + INFOPAD + Kinesics + FASMD.

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edit/
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/libs/dflat/

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

Rugxulo Usono, 15.09.2008, 07:32 @ DOS386	FreeDOS EDIT 0.9 Post reply
	> Released 10 days ago ... but doesn't work Anyone else tested ? I don't really use it (64k limit, meh), but it at least seems to work okay. Why, what does it not do (or do incorrectly) unlike 0.7d?

DOS386

16.09.2008, 01:53

@ Rugxulo

FreeDOS EDIT: No BUG, shame on me :-(

Post reply

> at least seems to work okay.
> Why, what does it not do (or do incorrectly) unlike 0.7d?

Ghosted mouse cursor maybe ? :-P

Anyway, I found the problem: I had tested on FreeDOS and EDR-DOS only (where it securely fails), inside NTVDGM it works excellently of course :-)

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

Japheth

Germany (South),
16.09.2008, 06:01

@ DOS386

confirmed: No bug

Post reply

> > at least seems to work okay.
> > Why, what does it not do (or do incorrectly) unlike 0.7d?
>
> Ghosted mouse cursor maybe ? :-P
>
> Anyway, I found the problem: I had tested on FreeDOS and EDR-DOS only
> (where it securely fails)

It doesn't "securely fail" on my machines. It works in NTVDM, FreeDOS and MS-DOS 7.1.

---
MS-DOS forever!

Berlin, Germany,
15.09.2008, 23:30

@ DOS386

FreeDOS EDIT 0.9

Post reply

> Released 10 days ago ... but doesn't work :-( Anyone else tested ?

Works.

EDIT: I used FreeDOS 1.0 in my home-brewn QEMU version 0.9.1.

---
Forum admin

DOS386

18.09.2008, 00:54

@ DOS386

B.S. movie available of FD EDIT 0.9 bug

Post reply

[image]
Bugshot movie ( .OGV , 9 MiB)

What one can see is the ghosted mouse cursor, then it becomes visible when I click the bar on the top, remains good as long as I move there around, then reghosts just after clicking "Display" ... and then I try to click "Mono" ... and finally get it, cursor is ghosted all the time, instead of a stable red rectangle there is an almost invisible (you can see it in the movie if you look well) thin flickering line :-(

Note: of course I did use Khusraw's encoder :-) (progress indicator is bad, output good)

Warning: the movie is bloated and lousy ... an example how a movie should NOT look like :-( ... reasons are in camera rather in the Theora codec, but should be sufficient for the given purpose here.

The bug securely occurs in both 25 and 50 lines mode, with and without JEMM, and in EDR-DOS and FreeDOS. FreeDOS EDIT 0.7d doesn't have this bug, nor INFOPAD, nor any other text mode mouse controlled application.

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

Berlin, Germany,
18.09.2008, 11:35

@ DOS386

B.S. movie available of FD EDIT 0.9 bug

Post reply

> The bug securely occurs in both 25 and 50 lines mode, with and without
> JEMM, and in EDR-DOS and FreeDOS. FreeDOS EDIT 0.7d doesn't have this bug,
> nor INFOPAD, nor any other text mode mouse controlled application.

Did you also try a clean boot (not only w/o Jemm)?
Did you try another graphics card? If not, please do so, if you have a spare one available.

---
Forum admin

ecm

Düsseldorf, Germany,
18.09.2008, 17:28

@ rr

B.S. movie available of FD EDIT 0.9 bug

Post reply

> [...] mouse controlled application [...]
>
> Did you also try a clean boot (not only w/o Jemm)?

A clean booted DOS disables any mouse control anyway :-D

---
l

Berlin, Germany,
19.09.2008, 10:45

@ ecm

B.S. movie available of FD EDIT 0.9 bug

Post reply

> > [...] mouse controlled application [...]
> >
> > Did you also try a clean boot (not only w/o Jemm)?
>
> A clean booted DOS disables any mouse control anyway :-D

Oops, you're right! :-) Then he should load just the mouse driver. He could also try different mouse drivers from, e.g., Microsoft or Logitech.

---
Forum admin

DOS386

21.09.2008, 02:07

@ rr

B.S. movie available of FD EDIT 0.9 bug | Buggy BIOS ???

Post reply

> EDIT: I used FreeDOS 1.0 in my home-brewn QEMU version 0.9.1.

For me it also works (or at least this bug doesn't arise) in QEMU (0.9.0 "official").

BTW, why did you brew your QEMU version ? Did you fix the PS/2 emulation ? :-)

> Did you also try a clean boot (not only w/o Jemm)?
> should load just the mouse driver.

My boot was already 98% clean. OK, deleting HIMEMX also ... no effect (same bug symptoms still present).

> also try different mouse drivers from, e.g., Microsoft or Logitech.

LOGI 6.50 -> same bug still present (+ bloat + delay on EDIT startup).

Last thing: mouse driver removed -> no bug anymore :clap:

> Did you try another graphics card?
> If not, please do so, if you have a spare one available.

OK ... finally got DOS into an other PC -> no bug. Problem seems to be hardware / BIOS sensitive :-(

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

Berlin, Germany,
21.09.2008, 15:48

@ DOS386

B.S. movie available of FD EDIT 0.9 bug | Buggy BIOS ???

Post reply

> BTW, why did you brew your QEMU version ?

To have a less "hacked" version. Japanese or French builds look a little suspicious to me. ;-)

> Did you fix the PS/2 emulation ?

Do you mean the keybord problem mentioned by Japheth? No, but it's one of my goals. Any volunteers are welcome. :-)

---
Forum admin

Khusraw

Bucharest, Romania,
22.09.2008, 11:24
(edited by Khusraw, 22.09.2008, 12:48)

@ DOS386

B.S. movie available of FD EDIT 0.9 bug

Post reply

> Note: of course I did use Khusraw's encoder :-) (progress indicator
> is bad, output good)

Unfortunately (for me) it isn't mine. I just compiled it.

I'm sorry to say, but many of your bug reports seems to be related to the fact that you own/use indeed a very cheap/buggy system. Try at least some BIOS updates, but if you have the possibility to replace your system, please do it.

---
Glory to God for all things

DOS386

23.09.2008, 15:52

@ Khusraw

B.S. movie available of FD EDIT 0.9 bug | BIOS bugs

Post reply

> Unfortunately (for me) it isn't mine. I just compiled it.

I know.

> many of your bug reports seems to be related to the
> fact that you own/use indeed a very cheap/buggy system.

Not many.

> possibility to replace your system, please do it.

With what ? Newest PC with FFI instead of BIOS ? :confused:

> Try at least some BIOS updates, but if you have the

The newest BIOS existing for given mainboard is already in, and still buggy.

I have following BIOS BUG's:

- FONT8x14 bug ... maybe rr could help ? :hungry:
- B.S. VESA readout bug ... but Loren Blaney came around it :-)
- Restore screen bug AKA text too dark bug :-(
- INT $13 128 sectors bug ... AKA "IDECHECK-bug" :-(

So far no evidence that FD EDIT mouse cursor ghosting bug or "your"
encoder bug (progress indicator shows just "-1" most of the time,
input is YUV4MPEG2, no sound) is a BIOS bug in fact, it still could maybe :-|

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

Khusraw

Bucharest, Romania,
23.09.2008, 16:33

@ DOS386

B.S. movie available of FD EDIT 0.9 bug | BIOS bugs

Post reply

> With what ? Newest PC with FFI instead of BIOS ? :confused:

I really can't understand, you have the possibility to replace it only with the "newest PC with FFI"?

> So far no evidence that FD EDIT mouse cursor ghosting bug or "your"
> encoder bug (progress indicator shows just "-1" most of the time,
> input is YUV4MPEG2, no sound) is a BIOS bug in fact, it still could maybe
> :-|

I tested both FD EDIT 0.9 and the OGG encoder on various computer systems and I can't reproduce the "bugs". I'm almost sure that the cursor problem is related to buggy video card BIOS, about the cause of the progress indicator problem I have no idea, but it shows correctly on all the systems I tested it.

---
Glory to God for all things

ecm

Düsseldorf, Germany,
23.09.2008, 16:33

@ DOS386

B.S. movie available of FD EDIT 0.9 bug | BIOS bugs

Post reply

> - FONT8x14 bug ... maybe rr could help ? :hungry:

Did you try the "written for BTTR Software" FIX8X14 driver? (To Robert: I read the ASM source some days ago. Looks good.)

---
l

Berlin, Germany,
23.09.2008, 16:41

@ ecm

B.S. movie available of FD EDIT 0.9 bug | BIOS bugs

Post reply

> (To Robert: I read the ASM source some days ago. Looks good.)

Today I'd write things differently. ;-)

---
Forum admin

Berlin, Germany,
23.09.2008, 16:40

@ DOS386

B.S. movie available of FD EDIT 0.9 bug | BIOS bugs

Post reply

> I have following BIOS BUG's:

It's "bugs" not "BUG's"! Will you learn?

> - FONT8x14 bug ... maybe rr could help ? :hungry:

Maybe. However I need decent bug report. Yours is not. Again...

---
Forum admin

DOS386

25.09.2008, 15:59

@ rr

B.S. movie available of FD EDIT 0.9 bug | BIOS bugs

Post reply

> need decent bug report

About what ? No bugs found in FIX8X14. Or you want to fix the BIOS ?

BTW, the original EDIT bug occurs with LOGI-mouse 6.50, CTMOUSE 2.1b4, 1.9.1a1, and 2.0b4 - no PS/2 BIOS involved. Any idea what piece of BIOS could cause it ?

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

Berlin, Germany,
25.09.2008, 16:33

@ DOS386

B.S. movie available of FD EDIT 0.9 bug | BIOS bugs

Post reply

> > need decent bug report
>
> About what ? No bugs found in FIX8X14. Or you want to fix the BIOS ?

You didn't tell us, that FIX8X14 works for you.

> BTW, the original EDIT bug occurs with LOGI-mouse 6.50, CTMOUSE 2.1b4,
> 1.9.1a1, and 2.0b4 - no PS/2 BIOS involved. Any idea what piece of BIOS
> could cause it ?

The graphics card's BIOS, of course. Or maybe the card isn't fully compatible to the VGA standard.

---
Forum admin