My questions, are: Is there a way to fix the last line of the OBJECT code?
I don't mind creating a utility to modify the last line of the object, but I suspect that there is at least a CRC or byte count that might throw things off. We tried to modify the last line in the .O code pointing to the original path, using the editor, but that does bizarre things, like multiple paths.
You are correct. Editing in a new path would invalidate the stored checksum.
or
Is there some feature that can be turned on (or off) to prevent DEBUG from attempting to read the object pointer shown in the last line of the .O entry?
There is no way to prevent DEGUG from reading the pointer from the .O entry. However, since this is a UNIX system, I would create a symbolic link of the ORIGINAL path ' c:\binarystar\dist' that actually points to the NEW path 'D:\UV\ACCOUNTS\Binarystar'. Give that a try and let us know how you fare.
Glenn -------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
