NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/os/msdos/misc/5034

Internet Message Format | 1992-09-03 | 1.8 KB

Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!news.cs.indiana.edu!bsu-cs!news.nd.edu!bach!rwilliam
From: [e-mail] (richard williams)
Newsgroups: in.pc,comp.os.msdos.misc
Subject: Re: Missing character questions....
Message-ID: <[e-mail]>
Date: 3 Sep 92 16:06:49 GMT
References: <[e-mail]>
Sender: [e-mail] (USENET News System)
Organization: University of Notre Dame, Notre Dame
Lines: 31

In article <[e-mail]> [e-mail] (Bob Baker) writes:
>While working on converting some VERY old DOS files at work, we've
>discovered an interesting dilemma.  When we do a directory listing of
>the files, we see things like:
>
>H FRAME   TXT   09-01-84  etc., etc.
>S H HOUS  TXT   09-01-84
>.
>Our problem comes when we want to copy these files to other disks.
>Whatever character the blank space is in the directory listing, it
>does not get read in the copy program.  We see:

Usually you can get around a problem like this by using wildcards or
by using some sort of DOS shell.  Try this:

Copy H?frame.txt hframe.txt   or else maybe
copy H?frame?.txt hframe.txt

Basic and other programs can create file names with spaces in them, but
then regular Dos can't handle them, except as above.  The filename might
also include some weird nonprinting character.

If this doesn't work, you might also run chkdsk or else the Norton Disk
Doctor, especially if on old floppies the disk might have gotten a
little zapped somehow.

--
---------------------------------------------------------------------------
Richard Williams, N.D. Sociology Department         Office:   [phone]
BITNET:    F67TEL@IRISHMVS                          Messages: [phone]
INTERNET:  [e-mail]                FAX:      [phone]