Our SHARE is quite simplistic, and my attempt to reduce size / TSR size did not involve improved function either. I am told that Word is not happy with it either, and that ROMDOS SHARE (which traps int 21 directly, while FreeDOS SHARE gets called by FreeDOS kernel through int 2f) works better.
And here's (at least one) of your SHARE problems with Ensemble, possibly other problematic apps:
If a file is opened 3D20 (Deny Write, Read Only) and then later 3D00 (Compatibility, Read Only), your SHARE chart generates an INT 24h. That behavior is documented in RBIL for DOS pre-7.0. Seems stupid, but that's what RBIL says.
However, 7.0+ versions -- which is the version that FreeDOS returns, as 7.10 -- according to RBIL should return an "open succeeds" behavior. Which incidentally makes a lot more sense, in my opinion.
INT 24h message is fairly bizarre at that point too, but looks like the kernel might be giving weird and likely wrong feedback based on the passed error bitcodes.
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
