Was wading through log list entries when hard power-off occurred. 1st in >36hrs. Restarted and the same thing happened when I opened up the last-viewed log. Machine now fails to boot into LXLE. Much activity after boot screen, but resolving finally into repeated error msgs.
Cannot chkdsk and the mfrs Data Lifeguard Tools cannot report on disk status - generating a 'fatal error'.
I'm looking at my HD morgue. This will be the third HDD that has gone nonrecoverable shortly after attempting dual boot install with LXLE. I find that curious.
The first two were from DELL Optiplex 270 refurbs with WXP, from first LXLE attempts in ~2020. These machines are still running with replacement drives, restored from WXP-only, no-grub-boot back-ups. They're used on the lab bench for test equipment comms and logging (since ~2013).
I'll be restoring the W2K OS on another HDD to recover the current machine (PCC A13+ w Sempron - home-built), which has been performing basic office, lab and library functions since 2004. I'd like to transfer this role to a non-MS OS.
Maybe dual-boot is the wrong way to go. It obviously isn't a major priority in development and the antagonism between various developers and other commercial producers is possibly poisonous in this regard.
The Ubuntu 18.04 OS, recently installed (by itself) in fairly current street trash, doesn't even have an LPT1 . . . . just rebooted it (with it's 32char encryption password) and can't even remember how to start LTspice in wine, or get back desktop links present prior to reboot.
All off topic. Need to add [Fails] to subject line.
The machine with the new LXLE install, as dual boot with venerable W2K, is now retired.
Unavoidable and increasingly predictable power-down situations eventually killed the SATA HDD, its back-up and the IDE optical disk drive. This in spite of replacements to PSU, motherboard (PCCA13G+ V3.0), processor (sempron and athlon), bios (re-flash), harnessing etc etc etc.
Bare bones hardware fresh install of either W2K or LXLE on new HDD fails to complete in this box due to this power-down event. Enough's enough.
Slightly more on-topic; When the DJ720C was plugged into a riser board LPT1 in a separate Ubuntu 18.04.3 LTS (dual boot W7) system, it registered and printed without issues.