DOS ain't dead

A question about the new /J switch for TSRs (Developers)

posted by ecm  , Düsseldorf, Germany, 02.04.2023, 08:50

> I'm confused about exactly what you're trying to accomplish. It kind of
> looks like you're trying to have all your TSRs use the same switches,

That's correct, the TSRs share a lot of code especially for the transient, and once I'm satisfied with the changes I will pick them for all the TSRs based on the same codebase.

> and
> want to use the /J as sort of an "entry point" into memory related
> functions instead of having several different switches?

Don't know what you mean by "entry point" but I certainly don't want to assign half a dozen switches just for the various options now provided for /J. (And they aren't all memory-related.)

/J was originally chosen because RxANSI already used both /U (Uninstall) and /L+/- (set LESS state), so for "disable DOS UMB use" an unused switch had to be selected. The new /J switch could be called "jettison" because it "jettisons features" of the TSR's transient application.

---
l

Complete thread:

• A question about the new /J switch for TSRs - ecm, 01.04.2023, 09:09
  • A question about the new /J switch for TSRs - bretjohn, 02.04.2023, 06:13
    • A question about the new /J switch for TSRs - ecm, 02.04.2023, 08:50
      • A question about the new /J switch for TSRs - bretjohn, 03.04.2023, 06:27
        • A question about the new /J switch for TSRs - ecm, 04.04.2023, 14:12