PDIR has trouble processing filenames with embedded percent sign

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
#1
TCC 11.00.33 Windows XP [Version 5.1.2600]

I have many old files archived from the days when MS "expand" expected the 3rd character of the file extension of compressed files to be the percent sign %. Using the command below for such files results in TCC errors:

pdir/(z r dymd thmsd @inode[*] 3@links[*] fpn) E:\ESF\DISKETTE\0026\ENG.LI%

TCC: (Sys) The system cannot find the file specified.
"%@inode[E:\ESF\DISKETTE\0026\ENG.LI]"

The underlying problem is in the passing of the filename to the @INODE function.

Rex, I hope you can solve this problem!
--
Steve
 
#2
On Sun, 15 Nov 2009 16:13:23 -0600, Steve Fábián <> wrote:

|I have many old files archived from the days when MS "expand" expected the 3rd character of the file extension of compressed files to be the percent sign %.

I don't remember that. MS examples from DOS 5 and Windows 3 all show the likes
of MSDOS.SY_.
--
- Vince
 

rconn

Administrator
Staff member
May 14, 2008
10,210
86
#3
> TCC 11.00.33 Windows XP [Version 5.1.2600]
>
> I have many old files archived from the days when MS "expand" expected the
> 3rd character of the file extension of compressed files to be the percent
> sign %. Using the command below for such files results in TCC errors:
>
> pdir/(z r dymd thmsd @inode[*] 3@links[*] fpn)
> E:\ESF\DISKETTE\0026\ENG.LI%
>
> TCC: (Sys) The system cannot find the file specified.
> "%@inode[E:\ESF\DISKETTE\0026\ENG.LI]"
>
> The underlying problem is in the passing of the filename to the @INODE
> function.
>
> Rex, I hope you can solve this problem!
Unlikely I can do anything about that. (And I agree with Vince; that is not
standard MS naming.)

It took 15 years for you to notice this?

Rex Conn
JP Software
 
#4
rconn wrote:
| Unlikely I can do anything about that. (And I agree with Vince;
| that is not standard MS naming.)
|
| It took 15 years for you to notice this?

Sorry, indeed it was not from MS. The example is from an old Logitech
Mouseware distribution diskette.

COPY and MOVE have no trouble with the filenames, when they are used in
wildcards. I tried to use PDIR to catalog all my drives, including the file
identifier returned by @INODE[] in the catalog, and that's the only time the
problem shows up. I think that PDIR should be able to pass any legal
filename to whatever functions it calls during the reporting process.
--
Steve