Again, what OS and software was used to create these files?

0

You could use something like an OS/2 boot disk, or even a windows 9x one. These do have support for spaces in names. I suppose you could use 4dos as well. I never had probs deleting sf data. ea when the need arose. This had two spaces. The dream you dream alone is only a dream, The dream we dream together is reality.

0

A 9x bootdisk won't do it. Even 9x pure dos doesn't preserve the space, at least using its available internal commands. I have used NTFS4DOS to copy LFN correctly. I don't know about OS/2. Technically, H START.G isn't an LFN if the space is an unseen character instead of a space. (But then the wildcard ? should have worked.) Kardian, it'd be helpful to know how the file was created. Also, can you just use COPY *.* or COPY *.G? Even if that copies more files than you want, try it and post back what the copied files look like. Oh, and I don't think your using win 3.11 makes any difference. On my 3.1 the file I created shows the same as with dos--HSTART~1.G.

0

The files were created by the DOS program I'm trying to transfer (from a DOS computer to a Win95 computer). Normally, I'd just slave the DOS computer's hard drive in the Windows 95 computer, but the DOS computer's hard drive uses a floppy drive cable instead of the standard IDE cable. Plugging the old hard drive into the Windows 95 computer's floppy controller didn't work. I did try using COPY *.*, COPY *.G, COPY HSTART~1.G, and COPY H?START.G, but no matter what command I use, it tries to copy the file as HSTART.G and gives a file not found error. The file appears to be a critical part of the program, as the program won't function correctly without it. MCP CCNP

0

It seems unlikely in the extreme that the HD is connected to a floppy cable. Could be a RLL/MFM drive connected to a 34 pin AND A 20 pin. I would get a LapLink cable and use DOS 6.22 intersvr/inetrlnk to xfer files. ===================================== If at first you don't succeed, you're about average. M2

0

About 2/3 the way down this page: http://www.ahuka.com/dos/lesson7.html it tells how to add a space to a file name using the ASCII 255 character. Maybe that's what your software did. Try this: With numlock on type COPY H then hold the ALT key down and type 255 on the keypad. The dos icon should move one space. Type in the rest of the file name, START.G. It should show as COPY H START.G--exactly the same as if you used a regular space but dos will see it differently. Then finish the line with the destination of where you want to copy the file. Here's a list of the ascii characters: http://www.techweb.com/encyclopedia... Ascii 32 is also a space but it's used as a control character. I don't know if that makes a difference. You can experiment with the various ascii codes and see if any others result in a blank space. Also, take a close look at the 'space'. Is it possible there's a barely legible character there--maybe ascii 250? It seems obvious that dos isn't seeing the space as a regular space so maybe this will work.

0

Hi DAVEINCAPS, Good idea. ASCII 32 is a 'real' space. As generated by the space bar. 255 is sometimes called 'nul'. As you say it will 'look like' a space. ===================================== If at first you don't succeed, you're about average. M2

0

I created a file with ascii 255 instead of the space and dos did see it as H START.G instead of HSTART~1.G so it's getting close. But I had no problems copying it using any wildcard scenario. Kardian, does the file by chance have a hidden or system attribute?

0

I frequently create filenames with spaces (and other things) in pure DOS. There are a number of ways to do this, including tricks with PKZIP, QBASIC, and with Win 9x's native DOS commands. I'll give you one of the easiest methods. But first, check DAVEINCAPS' suggestion above regarding file attributes (this is too often overlooked) and remove them if necessary. Then do the following: 1. Get PKZIP for DOS if you don't already have it. Version 2.04 is common and sufficient for this task, but 2.50 is even better. (Google PKZIP250.EXE). 2. On the DOS machine, PKZIP temp.zip h?start.* (just in case it's really h start. g). If it's the only file, then PKZIP temp.zip *.* will suffice instead. 3. Copy the temp.zip onto your Win95 machine by the method of your choice. 4. Boot the Win95 machine in pure DOS mode and PKUNZIP temp.zip in the directory where it belongs. 5. DOS will see the file name exactly as it was before, spaces and all. Change file attributes back if necessary. Even Windows will see the 8.3 name with spaces and no tildes.

0

Just try putting the file in quotes "" and doing it again.        My blog

0