A copy can transfer file contents while shortening names. For Windows 95 data, counts and sizes are not enough: full names, subfolders and usability at the destination matter too. This test changes no original files and runs no old programs from unknown sources. Keep the old PC disconnected from the public internet.
1. Distinguish long names from short names
An 8.3 short name has up to eight characters before the dot and three for the extension. Windows may provide a short alias containing a tilde alongside a long name. A name such as PROJEK~1.TXT therefore does not prove that a second file exists. Conversely, an alias alone cannot reliably reconstruct the original long name.
The entire transfer route matters: source application, copying tool, intermediate medium, any archive format and destination application. Old MS-DOS tools or certain CD file systems may pass on only the short form. Current Microsoft documentation also covers newer systems; modern long-path settings are not a Windows 95 solution. A long filename and an excessive total path length are different problems.
2. Create a harmless test set
In a new test folder, create small text files with different contents. For example, use Project Report January.txt and Project Report February.txt, plus a name containing an accented character, such as Prüfung.txt. Add a subfolder with a space in its name. Record the full names, their associated contents and the folder structure beforehand. Do not choose names differing only in case.
Use short, clear paths and avoid reserved device names or special characters such as colon and question mark. Also check extensions in the file view or properties; a hidden extension has not been removed. The test set must not replace production data or reside in an application folder.
3. Test the actual route
- Copy only the test folder using exactly the tool and intermediate medium planned for migration. Copy, do not move.
- If using an archive, check after extracting into a new empty destination folder. Seeing names inside the archive is insufficient.
- At the destination compare all full file and folder names, accented characters, extensions and counts. Pay particular attention to the two similar project names for confusion or overwriting.
- Open every test file and compare its contents with the recorded association. Equal size alone does not prove unchanged data. Record tool version, route, destination and result.
4. Do not rename originals to fix discrepancies
If you encounter only short names, incorrect characters, missing files or overwrite warnings, stop before the real migration. Do not bulk-rename originals. Use another demonstrably suitable copying or archiving route and repeat the entire test. Do not format a new medium without checking its existing contents and compatibility with the old PC first.
Even if long names survive, short aliases may change or be absent at the destination. Old shortcuts and applications with hard-coded short paths therefore need separate testing in a suitable isolated environment. The filename test confirms neither a complete software installation nor its compatibility. Keep originals and an independent backup until acceptance. Only after a successful test should the data copy begin, with further sample content checks.