The main issue with FreeCom would be the location of its resources
changing. As long as the comspec env variable still pointed to the same
(or an identical) copy of the strings, it would probably be ok, but
honestly I don't know if FreeCom closes/opens or keeps open the file
with its
Hello Kenneth,
The main issue with FreeCom would be the location of its resources
changing.
under normal circumstances, FreeCom-xmsswap will have it's resources
loaded at startup and touch them never again.
Tom
---
This SF.Net email is
firstly, I never said FreeCom couldn't handle drive letter changes, I
said if one did something, then they need to make sure it can; in
particular the way it loads strings; although from my experience not
being able to load its strings usually just results in FreeCom issuing
useless messages
Hi,
Very very nice discussion, I am enjoying this a lot, thanks!
Kenneth J. Davis escribió:
various details like that. And really if you wanted to be clever,
maintain the needed information about open files and TSRs won't even
notice the change, even if the file is now on a different drive
