🚀 go-pugleaf

I had a similar problem like this at work two weeks ago. I'm a support tech
at a sawmill, and the scalers in the yard have a handheld log tallier that
runs under DOS 3; (it's not pretty, but it works). The short of the long of
it is that they saved a log tally as something like: "BIG LAKE.DEC", "JW
CONRA.JAN" with the spaces in the filenames. (Really poor program to let
them do this, but....)

They have to dump all the files from the handheld tallier to an old 286;
which of course can't read the files with spaces in it. The only work
around I could come up with is using wildcards with 'ren' to rename those
files to a legal DOS filename. For example, I used "ren big*.* biglake.dec"
to change the 'big lake.dec' file. 

Just make sure that you have no other files that are going to be included
in the rename command and it might work for you.

Chris Ross 

Snakeman <snakeman@cybercomm.net> wrote in article
<6ajv74$iav$2@ostrich.cybercomm.net>...
> patrick O'Neill <patrick.oneill@nf.sympatico.ca> wrote:
> : Hello:
> : I downloaded some software from the net and following installing and
trying
> : the software, I wanted to delete it at it was of no interest.  However,
two
> : files within the directory will not delete when I try to clear my
recycle
> : bin.  The files in question are shown as follows:
> : name                            size                type
> 
> : (s_w_o_r._d)                  1kb                _d)
> : _androme.da_                1kb                da_
> 
> : When I attempt to delete these files I get the following error:
> : Cannot delete (s_w_o_r: cannot find the specified file.
> 
> : I am also unable to delete then in DOS.  I cannot rename the file
either.
> : If you have any suggestions on fixing the problem please let me know.
> 
> 
> There are a bunch of fucking idiots and pathetic wannabe hackers who
> insist on violating basic rules of filenames so they can paste others
hard
> drives with their insipid advertisements. 
> 
> A good dosshell such as Norton Commander or Far will handle these easily.

> Or else deltree the directory. Or, boot to straight DOS, lock the drive,
> and run DISKEDIT (from Norton) on it, and rename directly. 
> 
> Rule of thumb: No matter how tempted, NEVER, EVER use spaces or control
> characters or high ascii in filenames for communications. And avoid long
> filenames whenever possible. Its not only bad manners, but its rude,
since
> not everyone will be running the same OS, and many may be running
multiple
> OS's and some will choke on this bullshit. As an example, I run 95, but
> routinely use a Unix shell, and occasionally run straight from DOS.
Spaces
> will screw up files in the Unix shell ( foo bar #1 will be simply
> overwritten by foo bar #2 and named foo) and LFN's will screw up DOS 
> (longname1 will be overwritten by longname2 and called longname). 
> And I cannot speak for those with MAC's who might wish to DL wintel files
> for use on their other machines. 
> 
> 
> 
> 
> 
> 
>