DOS ain't dead

Since I upgraded my MS-DOS 7.1 box to Enhanced DR-DOS 7.01.08 I found that filesystems is being slowly corrupted.

The FAT32 volume was 100% under MS-DOS, but after the switch I started experiencing file not found errors and so on.

When I ran the FAT32 enabled SCANDISK from DOS 7.1 in it, it found lots of problems. Can see a screenshot here http://twitpic.com/d1hz5r

Is any experiencing such corruption problems too? Is 7.01.07 stabler on that sense? According to the changelog, it should not have any big changes on the FAT32 handling.

Thanks.

---
Visit my personal blog at https://www.javiergutierrezchamorro.com

> Since I upgraded my MS-DOS 7.1 box to Enhanced DR-DOS 7.01.08 I found that
> filesystems is being slowly corrupted.
>
> The FAT32 volume was 100% under MS-DOS, but after the switch I started
> experiencing file not found errors and so on.
>
> When I ran the FAT32 enabled SCANDISK from DOS 7.1 in it, it found lots of
> problems. Can see a screenshot here http://twitpic.com/d1hz5r
>
> Is any experiencing such corruption problems too? Is 7.01.07 stabler on
> that sense? According to the changelog, it should not have any big changes
> on the FAT32 handling.
>
> Thanks.

I have not used it on FAT32 partitions but rather only FAT16
therefore I can not comment on the FAT32 corruption you are seeing.

However, I think this clipping from the download page says it all.

____________
http://www.drdosprojects.de/index.cgi/download.htm

Enhanced DR-DOS 7.01.08 WIP (21.7.2011)
This is a work-in-progress version of the upcoming DR-DOS 7.01.08
It is to be considered unstable and not ready for general use
other than for testing and demonstration purposes.
____________________________________________________________________

---
--
http://glennmcc.org/

Thank you glennmcc for your reply.
That being WIP is what I thought as the possible cause for the issue. Unfortunatelly stable version at level of 7.01.7, has not the later implemented read/write optimizations, and feels noticeably slower.

Regards.

> > Since I upgraded my MS-DOS 7.1 box to Enhanced DR-DOS 7.01.08 I found
> that
> > filesystems is being slowly corrupted.
> >
> > The FAT32 volume was 100% under MS-DOS, but after the switch I started
> > experiencing file not found errors and so on.
> >
> > When I ran the FAT32 enabled SCANDISK from DOS 7.1 in it, it found lots
> of
> > problems. Can see a screenshot here http://twitpic.com/d1hz5r
> >
> > Is any experiencing such corruption problems too? Is 7.01.07 stabler on
> > that sense? According to the changelog, it should not have any big
> changes
> > on the FAT32 handling.
> >
> > Thanks.
>
> I have not used it on FAT32 partitions but rather only FAT16
> therefore I can not comment on the FAT32 corruption you are seeing.
>
> However, I think this clipping from the download page says it all.
>
> ____________
> http://www.drdosprojects.de/index.cgi/download.htm
>
> Enhanced DR-DOS 7.01.08 WIP (21.7.2011)
> This is a work-in-progress version of the upcoming DR-DOS 7.01.08
> It is to be considered unstable and not ready for general use
> other than for testing and demonstration purposes.
> ____________________________________________________________________

---
Visit my personal blog at https://www.javiergutierrezchamorro.com

Let's see what Udo has to say!
Hope it will be able to clarify/solve it.

> Thank you glennmcc for your reply.
> That being WIP is what I thought as the possible cause for the issue.
> Unfortunatelly stable version at level of 7.01.7, has not the later
> implemented read/write optimizations, and feels noticeably slower.
>
> Regards.
>
> > > Since I upgraded my MS-DOS 7.1 box to Enhanced DR-DOS 7.01.08 I found
> > that
> > > filesystems is being slowly corrupted.
> > >
> > > The FAT32 volume was 100% under MS-DOS, but after the switch I started
> > > experiencing file not found errors and so on.
> > >
> > > When I ran the FAT32 enabled SCANDISK from DOS 7.1 in it, it found
> lots
> > of
> > > problems. Can see a screenshot here http://twitpic.com/d1hz5r
> > >
> > > Is any experiencing such corruption problems too? Is 7.01.07 stabler
> on
> > > that sense? According to the changelog, it should not have any big
> > changes
> > > on the FAT32 handling.
> > >
> > > Thanks.
> >
> > I have not used it on FAT32 partitions but rather only FAT16
> > therefore I can not comment on the FAT32 corruption you are seeing.
> >
> > However, I think this clipping from the download page says it all.
> >
> > ____________
> > http://www.drdosprojects.de/index.cgi/download.htm
> >
> > Enhanced DR-DOS 7.01.08 WIP (21.7.2011)
> > This is a work-in-progress version of the upcoming DR-DOS 7.01.08
> > It is to be considered unstable and not ready for general use
> > other than for testing and demonstration purposes.
> > ____________________________________________________________________

---
Visit my personal blog at https://www.javiergutierrezchamorro.com

> Let's see what Udo has to say!
> Hope it will be able to clarify/solve it.

I think he would need to reproduce this bug first to be able to fix it. This maybe hard task. Can you provide some test case - exact partition and FS properties, how it was formated, what was on FS and when exactly it broke...

---
DOS gives me freedom to unlimited HW access.

Can you recommend me a tool for getting partition information?

> > Let's see what Udo has to say!
> > Hope it will be able to clarify/solve it.
>
> I think he would need to reproduce this bug first to be able to fix it.
> This maybe hard task. Can you provide some test case - exact partition and
> FS properties, how it was formated, what was on FS and when exactly it
> broke...

---
Visit my personal blog at https://www.javiergutierrezchamorro.com

> Since I upgraded my ME 7.1 box to Enhanced DR-DOS 7.01.08

Congratulations

> Can you recommend me a tool for getting partition information?

You know how you did brew your partitions?

> Let's see what Udo has to say!

Nothing - King Udo is dead

> Hope it will be able to clarify/solve it.

Provide more details:

- HD types and sizes
- partitioning
- addons used (HIMEM UDMA LBACACHE DUMBDRV ...) btw, don't use M$ addons with EDR-DOS, especially not those from ME
- at what occasion does the problem start ?
- does the BUG persist if you remove all addons ?
- does the BUG persist with 7.01.07 ?
- does the BUG persist with FAT16 ?
- does the BUG persist with only 1 disk or 1 partition ?
- does the BUG persist with FreeDOS ?
- how does the directory listing look like (shot of DIR, shot of WDE, ...)

> I think he would need to reproduce this bug first to be able to fix it.
> This maybe hard task. Can you provide some test case - exact partition
> and FS properties, how it was formated, what was on FS and when exactly it
> broke...

exactly ...

> That being WIP is what I thought as the possible cause for the issue.
> Unfortunatelly stable version at level of 7.01.7, has not the later
> implemented read/write optimizations, and feels noticeably slower.

see above

FYI, I DO USE EDR-DOS 7.01.08 and I DON'T have this problem. Known BUG's:

* Writing a file to FAT28 at EOF EDR-DOS sets all 32 bits to 1 , should set only 28 bits (that's why we call the "technology" FAT28 ) - don't use old versions of FreeDOS having BIG problems with those 4 extra bits

* Broken NTLFN support (use "UI21DEB N")

* Values written into FSInfo are marginally off is some cases

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

> Nothing - King Udo is dead
I am quite frozen now. Was not aware on that. I am so sorry for his loss

---
Visit my personal blog at https://www.javiergutierrezchamorro.com

> > Nothing - King Udo is dead
> I am quite frozen now. Was not aware on that. I am so sorry for his loss
>

Uh, I haven't heard anything from Udo recently (not that I was supposed to), but I seriously doubt this was meant literally. He's most likely not physically dead, it's just DOS386's weird way of talking about the project's lack of activity.

In particular, once before some misinformed people on DR-DOS Forum proclaimed Jack Ellis dead, and that wasn't true at all! I don't know where such rumors start, but here it's almost definitely not intentional on DOS386's part.

Thank you for the clarification.
Glad to hear Udo is fine, even if the project is stoped/abandoned.

Regards.


> > > Nothing - King Udo is dead
> > I am quite frozen now. Was not aware on that. I am so sorry for his loss
> >
>
> Uh, I haven't heard anything from Udo recently (not that I was supposed
> to), but I seriously doubt this was meant literally. He's most likely not
> physically dead, it's just DOS386's weird way of talking about the
> project's lack of activity.
>
> In particular, once before some misinformed people on DR-DOS Forum
> proclaimed Jack Ellis dead, and that wasn't true at all! I don't know where
> such rumors start, but here it's almost definitely not intentional on
> DOS386's part.

---
Visit my personal blog at https://www.javiergutierrezchamorro.com

> Glad to hear Udo is fine

Where do you find this information?

PS: Is your filesystem now fine too ?

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

> > Glad to hear Udo is fine
>
> Where do you find this information?
>

Well then,

Please clarify.

You have stated several times.. "King Udo is dead".

Are you simply referring to his EDR-DOS project (and others)

Or do you mean to tell us that Udo has actually physically died ?

---
--
http://glennmcc.org/

I created a new empty disk, and using MS-DOS 7.1, proceed to create a new partition on it (FDISK), and formated it using DRFORMAT (Udo's version of FreeDOS format).

It worked fine, and started an MS-DOS 7.1 XCOPY command in order to duplicate everything on my C drive to the new D one. After some files copied, it gave an error about impossible to write on drive D. After that using a DIR command, it showed strange directory names on it, so FAT was probably corrupted.

After that, I booted with EDR-DOS 7.01.08, and DRFORMATed again drive D, in order to XCOPY from inside it, everything to D. It seemed to work fine, so I guess the problem could be more related to some MS-DOS 7.1 kermel/utilities issues with FAT-32, or either some kind of interoperability problems (no all implementing FAT-32 handling the same).

Will wait some days with this setup before confirming it is OK.

Thanks.


> > Glad to hear Udo is fine
>
> Where do you find this information?
>
> PS: Is your filesystem now fine too ?

---
Visit my personal blog at https://www.javiergutierrezchamorro.com