- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We've had a report from one of our users that our installation installs DFORRT.DLL read-only (this is true). When he runs the program it crashes in DFORRT. He then claims:
"I then removed the read-only attribute from the DFORRT.dll, and repeated the action. RTO+ did not crash, and no run-time error was produced."
I don't believe this is the real cause of the problem, is there any way a read-only runtime could cause a crash? (historically our crashes have been mostly generated by maths errors or by writes to non-existant units).
Dan
"I then removed the read-only attribute from the DFORRT.dll, and repeated the action. RTO+ did not crash, and no run-time error was produced."
I don't believe this is the real cause of the problem, is there any way a read-only runtime could cause a crash? (historically our crashes have been mostly generated by maths errors or by writes to non-existant units).
Dan
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DFORRT.DLL gets installed as read-only on a lot of systems. I've never heard of a problem with this. Lots of DLLs are read-only, and Windows doesn't care.
It would be interesting to know the exact text of the error message, but I'd be more inclined to attribute this to a problem on the user's local system (though what, I can't imagine.)
Steve
It would be interesting to know the exact text of the error message, but I'd be more inclined to attribute this to a problem on the user's local system (though what, I can't imagine.)
Steve
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page