|
Hello everyone,
As part of my continuing research into the internal evolution of XyWrite, I am now focusing specifically on its development process, toolchains, and engineering history.
I would like to ask whether anyone in the community may have access to, or knowledge of, any original developer-related materials, including:
• Internal development notes or design documents
• Build scripts, makefiles, or toolchain documentation • Source code fragments (even partial or archival) • Assembler/C environment configuration details • Overlay manager documentation • Internal memos discussing architectural changes • Conference talks, interviews, or technical presentations by former developers • Early beta distribution notes • Engineering commentary related to IBM Signature / Project J • Documentation describing the transition from DOS to Windows builds
In addition, I am especially interested in any information related to XyWrite 4.018, the final official DOS release.
Specifically:
• Was v4.018 still written entirely in assembly language?
• Or had portions of the codebase transitioned to C by that point? • If C was used, do we know which compiler and memory model were involved? • Was the build system hybrid (ASM + C), and if so, how was it linked?
Understanding whether the final DOS generation remained pure assembly or incorporated C would significantly clarify the architectural evolution of the product.
Even anecdotal recollections from those who worked with or alongside the original team would be extremely valuable.
My goal is to better understand:
• The development cycle structure (release cadence, internal milestones)
• The assembler/linker/compiler environments used across eras • Major architectural turning points (II → III, III → III Plus, III → 4) • The shift, if any, from assembly dominance to C integration • Build and testing practices during the newsroom-heavy years
This research is strictly historical and technical in focus, aimed at accurately documenting how XyWrite was engineered over time.
If you have materials you are willing to share — or can point me toward interviews, archived talks, or former developers — I would be deeply appreciative. Private replies are absolutely welcome.
Thank you again to everyone who has contributed knowledge and archival insight thus far.
Sincerely,
XYGHOST358B
(Prefer to remain anonymous)
|