To all that answered:
I also abhor the kludge that I wrote.
I also recognize that the test would catch possible *valid* filenames.
I will attempt to find the keys that cause the rename to occur.
However, the point of the patch was to: 1. Provide the developers with a way not to have their Windows system (real or fake) be renamed during development. I got tired of renaming the directories back to what they should have been.
2. Protect the end users from destroying their Windows system during testing/playing. The last thing we should want is the impression that Wine is dangerous because of unexpected consequences due to simple appearing actions. "comp.emulators.ms-windows.wine" still gets complaints from user that have done this very action.
Guy
On Sun, 29 Sep 2002 20:34:19 -0400, you wrote:
To all that answered:
I also abhor the kludge that I wrote.
I also recognize that the test would catch possible *valid* filenames.
I will attempt to find the keys that cause the rename to occur.
However, the point of the patch was to:
- Provide the developers with a way not to have their Windows system (real or fake) be renamed during development. I got tired of
renaming the directories back to what they should have been.
- Protect the end users from destroying their Windows system during testing/playing. The last thing we should want is the
impression that Wine is dangerous because of unexpected consequences due to simple appearing actions. "comp.emulators.ms-windows.wine" still gets complaints from user that have done this very action.
After removing such entries from system.reg:
| [Software\Microsoft\Windows\CurrentVersion\RenameFiles\ProgramFilesRen] 976188522 | @="D:\" | "!$!$!$!$.pfr"="Program Files,1" | "PROGRA~1"="!$!$!$!$.pfr" |
it stops.
Rein.