-----BEGIN PGP SIGNED MESSAGE----- I suffer from the great misfortune of a dos computer, and despite my anti-micro$oft efforts, I still am stuck, most of the time, with Windows 95. This OS assigns long filenames (the sensible kind, that is) to the old-style eight-character and three-character separated by a dot. However, they did it in such a way that old filenames still work. So if I have a file I want to encrypt, PGP will mess up this system. oldname.txt -> oldname.asc This is the normal way PGP would encrypt. However, f I have assigned the oldname.txt file a new file name under the win95 system, it will look something like this. "Old File" (oldfil~1.txt) This conforms with the new scheme. If I PGP encrypt, this happens: oldfil~1.txt -> oldfil~1.asc Thus, the new filename is lost, both for the ciphered file, and for the file once I decrypt. Is there a way (aside from not using long filenames) such as a hacked version of PGP that has a workaround for this problem? Also, is this an issue on the list of improvements for future official versions of PGP? =============================================================================== David Rosoff (nihongo o chiisaku dekimasu) -------------> drosoff@arc.unm.edu For PGP key 0xD37692F9, finger drosoff@acoma.arc.unm.edu or get from keyservers pub 1024/D37692F9 1995/07/01 David Rosoff <drosoff@arc.unm.edu> Key fingerprint = 25 7D AA 01 85 41 43 89 50 5A 33 76 F1 F1 99 67 I accept anonymous mail. If I didn't sign it, you don't know I wrote it. === "Made weak by time and fate, but strong in will / To strive, to seek, to find-- and not to yield." <---- "Ulysses", by Alfred, Lord Tennyson -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMbTExRguzHDTdpL5AQGo5QP/QqZw0PLK5/jNY42nbJ/VRrAj8g62FK7q zxWMVbindqQZaOYRtNVHy28rzjkBy+ybzhWetmLgny4f2zdUFkTf5OgZ0r27oOGQ 93VmAK8FoMTBhtje3y4OjWc2uqqHWSYkhjZVYWVCxVcFL1GA6FMkIs8pnzqb5Ohy ShWTgpaV6OM= =SLEx -----END PGP SIGNATURE-----