d7x Release Information
[Information may be outdated]
d7x is currently designed to sit beside d7II in the same folder, and maintains backwards compatibility with d7II configurations and active d7II session data (temporary files and settings specific to d7II and the current repair process) so a job can be finished with d7II if necessary. Even if d7x stopped working during an auto mode, d7II should pick up where d7x left off.
We would like to invite any d7x (d7II) subscribers to try d7x and actively participate in the feedback process for current development. We hope to continue to build d7x in a fashion not unlike d7II and d7 before it, where techs in the field contributed real ideas about current needs, and the products reflected that fact by remaining the best.
October 2017: d7x FastTrack Builds Released via d7II Update Mechanisms
September 2017: The latest d7x TestBuild replaced the d7IIx Alpha versions, which could be tested with confidence in a production environment (provided you kept d7II with you as a backup.)
March 2017: d7IIx was released to early adopting d7II subscribers for assistance in testing.
Earlier: d7II specific code was merged with a mostly completed d7x Platform based code project (being ready to adopt specific d7II functionality) under the name “d7IIx Alpha” for a time. This was done in order to provide product updates to d7II subscribers as soon as possible (until a fully unique d7x release was achieved) while simultaneously moving towards that goal. Therefore, an active d7II subscription is required for any testing or usage. In fact, to have an active d7II subscription means you are a d7x subscriber, even if your billing plan doesn’t to change reflect the new name.
d7x Platform code controls the underlying operation of d7II specific functionality (from error handling/debug systems to interfacing with the OS, file system, registry, internet operations, and more…)
d7x interfaces with the OS using new APIs that allow newer OS features and replace older concepts and tools, while preserving Unicode characters with an aim to cover the different needs of those in non-English speaking countries and with localized versions of Windows.
d7x advances client/server communications adding full SSL and verifying server security certificates on connection, for secure update communications to safeguard against attacks. These capabilities will be extended to the “dCloud” communications when accounts can be migrated/converted, and to Self-Hosted FTP options, as well as adding new HTTPS communication abilities for Self-Hosted options.
d7x also interfaces with itself using high accuracy and error correcting routines in certain input data verification code, and includes vastly improved error handling and debug systems that automatically track quite a bit of internal data flow without extra coding.
The initially availability of “d7IIx” (named to reflect a hybrid product) earlier this year began with d7x “Platform” code, built from the ground up with new considerations in design and new fundamental basic lower-level functionality, and integrated the d7II user interface and other code designed for specific purposes and functionality (e.g. specific Windows repair processes, the entire custom apps system, etc.) Then, much of the d7II code was unmodified, although certain things reflected improvement right away (such as Windows 10 recognition.) Now, d7II code and specific functionality is being replaced entirely in areas like config/definitions storage operations and remote deployment options, and more is to come.
To get a better idea of how the d7II code fits in, below are a few examples which illustrate the relationship between new d7x Platform code [represented by (d7x) below] which performs the unseen “grunt work” vs. the ported d7II code [represented by (d7II) below] which still handles the interface and specific/customized functionality.
Current Example #1: Run a custom app from the user interface (d7II), read user config (d7II), determine applicable operating environment/OS version (d7x), file exist/date stamp checking to determine if we should download a new fresh copy (d7x), download the file (d7x), extract file (d7x), find/verify extracted files (d7x), determine/initiate config customizations to app (d7II), perform file/registry operations related to app customizations (d7x), launch executable (d7x), wait for it to complete (d7x) in order to perform any cleanup/post actions like log gathering, etc. (d7II) before continuing with auto mode if in progress (d7II).
Current Example #2: Launch a Windows repair function from the user interface (d7II), read user config if applicable (d7II), determine targeted repair methodologies for the specific circumstances based on the above (d7II), determine operating conditions/perform system checks/download reqs if applicable (d7x), actually perform targeted repairs via any number of file system/registry operations (d7x), report success/failure/subsequent actions determined (d7II).
Now that the d7x Platform code has been integrated fully with the last builds going by the “d7IIx” title, much of the existing d7II specific code (as mentioned above) is being replaced, and fast. The current d7x v0.0.0.88 update brought an entirely new Config Mgmt Portal (older dCloud/Self-Hosted FTP functionality) and introduces the d7x Remote Deployment Tool (aka d7xRDT, the ‘SFX Mini‘ replacement) both of which are all new d7x specific/d7x Platform code (d7x-only) and together replace ALL client/server communications regarding config/definition files, as well as update tracking functionality.
Our first and foremost priority is to document/fix issues with functionality that worked correctly in the last release version of d7II.
New Feature Suggestions: At this time we are open to new feature suggestions, and large ideas are welcome; please visit our support portal to start a community post, but we ask that you understand the consideration is in future implementation, and we may not address all requests.
For the near future: major sections of d7x Platform code are already established (in the binary) and waiting to be integrated into existing d7II code replacements. The new d7x Platform code focuses on advanced, tested, stable, and reusable code to allow for rapid development towards reconstructing many of d7II’s best attributes into a more powerful and more user friendly tool.
Focusing on stability in the integration of d7II specific interfaces and functionality, workflow and data formats must be re-designed before we can drop d7II operational compatibility, and we plan to drop d7II operational compatibility before we move on to newer possibilities and new features.
User Interface: There is no foreseeable ETA on a complete user interface “change” at this time. In valuing function over form, for the most part your familiar interface will change gradually when it isn’t optional, and optional when it isn’t gradual or “under the hood” and does not maintain a familiar d7II form. Currently there may be few UI elements that reflect interface changes conceived for d7x, however there is a lot of re-usable code ready for interface changes or more simple enhancements.
Those hoping for few major “graphical” changes (if any) may delight in seeing the new KillEmAll’s background, which forces a consistent appearance of mostly the same traditional Windows app background color across all versions of Windows, while adding only a slight gradient effect from top to bottom using a bitmap that resizes nicely. It’s worth noting that this bitmap could be replaced as a new brand-able property.
Compatibility issues must also be considered as we apply new interface concepts, not just in maintaining d7II compatibility during the early stages, but also to allow the optional usage of the current d7II interface as a new UI develops, because a large amount of specific d7II functionality is tightly integrated into the existing user interface. In order to replace the d7II user interface that code must be updated heavily or entirely rewritten to work with new d7x code, and to simultaneously continue to work as expected with the existing d7II interface.
In other words, d7x is a ground up replacement, and basically the UI is more or less a major part of the very final stages in a full d7x release, but we’re not quite there yet.
(Current availability) d7x has been released to all d7II subscribers through the standard in-app update system. If you are not yet prompted to update, visit the Main menu (top left) > Check for Updates from within d7II.
After the d7x update, d7II.exe can still be used on the same PC, and within the same session. This is intended as a fail-safe option, in the event of any unexpected d7x crash or functional failure.
Please see the d7x Manual for ALL current information!
Join us for live tech chat, product questions, support, and technical training right here!
Both Foolish IT customers and non-customers alike are welcome to discuss anything Foolish!
d7II to d7x update error corrected, please accept my personal apology for any disruption in usage! Please accept that I deeply regret any inconveniences you and...
d7x is officially updating for all d7II subscribers… d7II subscribers will notice their copy of d7II v3.6.86 now...