DOSLFN and File Wizard

[Marcos Favero Florence de Barros]

Hi,

Two months ago I sent a few messages about file corruption
problems with DOSLFN which I had experienced back in 2008. Now
finally I could do some more testing. Here are the results.

The test was simple: compressing a couple of long-name files with
InfoZip, with help of the File Wizard file manager. This is what
I intended to do with DOSLFN, so this is what I tested.

After doing that, I ran DOSFSCK (two-pass mode), which found
numerous errors. The same kind of problem observed last year
occurred again. Damaged files were in folders (apparently)
unrelated to the tested files. This is an example of the DOSFSCK
screen output:

Checking files and directories.../BANC/SEG/COPIAS
  Has a large number of bad entries. (31/39)

/BANC/INSPECAO
  Has a large number of bad entries. (31/40)

./DOC/AMBI/DIVERS
  Has a large number of bad entries. (28/67)

In addition to damaged files and folders, several undeletable
files and folders appeared, with names composed of illegal
characters.

I decided to run further tests using other file managers, because
of what Eric had said:

> Note that NDN or FileWizard might cause some troubles when
> used in together with DOSLFN etc, you never know?

So the file managers Connect and DosZip were tested for file
compression, decompression and deletion from archives. This time
everything went smoothly, and DOSFSCK did not detect any errors
afterwards. The test was repeated a couple of times.

The conclusion seems to be that the problem lies with the
combination of File Wizard, DOSLFN and perhaps InfoZip; they are
somehow incompatible.

I'm not asking the FreeDOS team to do anything about it, because
this doesn't seem to be a big priority, since it apparently
affects only File Wizard. I'm simply reporting the fact.

Regards,

Marcos

--------------------------------
Marcos Favero Florence de Barros
Campinas, SP, Brazil
55-19-3231-8194
favero@...



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-user mailing list
Freedos-user@...
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Buzzer-4]

11-Nov-2009 числа в 11:32 часов, Marcos Favero Florence de Barros написал(а) следующее:

> Two months ago I sent a few messages about file corruption
> problems with DOSLFN which I had experienced back in 2008. Now
>
> /BANC/INSPECAO
>   Has a large number of bad entries. (31/40)
>
> ./DOC/AMBI/DIVERS
>   Has a large number of bad entries. (28/67)

I have the same problem. Advice is: try to use "doslfnms" instead of
"doslfn".

--
/Buzzer         () кампания ascii ribbon - против писем в html формате
                /\ www.asciiribbon.org   - против проприетарных вложений



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-user mailing list
Freedos-user@...
https://lists.sourceforge.net/lists/listinfo/freedos-user

[dos386]

> file corruption problems with DOSLFN which I had experienced

I had got same problem (crosslinked files), also A.P. (author of
MPXPLAY) discourages writing with DOSLFN.

> Advice is: try to use "doslfnms" instead of "doslfn".

What is it ???

http://www-user.tu-chemnitz.de/~heha/viewzip.cgi/hs_freeware/doslfnjh.zip/readme.txt?auto=TXT

BTW, my (well known) advice is: don't use DOSLFN :-|

BTWW, King Udo (EDR-DOS maintainer) reportedly uses it and is happy
(the only one user ???), possibly the problems occur with FreeDOS
only, not with EDR-DOS. No idea why and no ambition to debug this type
of problem :-|




--
~~~ wow ~~~

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-user mailing list
Freedos-user@...
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Christian Masloch]

> BTWW, King Udo (EDR-DOS maintainer) reportedly uses it and is happy
> (the only one user ???), possibly the problems occur with FreeDOS
> only, not with EDR-DOS. No idea why and no ambition to debug this type
> of problem :-|

I'm using it too on MS-DOS (for both read and write access) and it didn't  
corrupt anything yet. The way DOSLFN is implemented however is messy; it  
depends on DOS's behaviour (it was developed on MS-DOS 6.22 and 7.10).  
Either DOSLFN depends on something it shouldn't, or the FreeDOS kernel  
fails to behave similar to MS-DOS somewhere. (Or both.) A FreeDOS kernel  
developer would have to work through the DOSLFN source to check this.

Regards,
Christian

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-user mailing list
Freedos-user@...
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Buzzer-4]

15-Nov-2009 числа в 01:50 часов, dos386 написал(а) следующее:

> > file corruption problems with DOSLFN which I had experienced
>
> I had got same problem (crosslinked files), also A.P. (author of
> MPXPLAY) discourages writing with DOSLFN.
>
> > Advice is: try to use "doslfnms" instead of "doslfn".
>
> What is it ???

It is DOSLFNMS.COM.
MD5 (DOSLFNMS.COM) = 2841b95fccf0edc191f71ad34c7cda9a
DOSLFNMS is intended for use with MS-DOS 7 (but may also work with
FreeDOS) and also has some features removed to reduce its size:
- doesn't disable itself when starting Windows;
- doesn't recognise codepage changes;
- doesn't handle double-byte character sets.

> http://www-user.tu-chemnitz.de/~heha/viewzip.cgi/hs_freeware/doslfnjh.zip/readme.txt?auto=TXT
What is it?

> BTW, my (well known) advice is: don't use DOSLFN :-|
Then your FreeDOS will loss such useful LFN ability. :-)

--
/Buzzer         () кампания ascii ribbon - против писем в html формате
                /\ www.asciiribbon.org   - против проприетарных вложений



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-user mailing list
Freedos-user@...
https://lists.sourceforge.net/lists/listinfo/freedos-user