Refitting .xinitrc from the bottom up.

[Terry H]

Just tried the modified .xinitrc with radky's dpup stretch. Results not so good.
Initially using fbBox, it boots to a blank screen with a cursor only. I could use keyboard shortcuts for access.

I used Ctr +Alt +Backspace, then followed by xwin jwm, the system successfully restarted and functioned correctly.
Rebooting whilst using JWM was successful, but produced the same blank screen when swapping to FbBox.

[musher0]

Just tried the modified .xinitrc with radky's dpup stretch. Results not so good.
Initially using fbBox, it boots to a blank screen with a cursor only. I could use keyboard shortcuts for access.

I used Ctr +Alt +Backspace, then followed by xwin jwm, the system successfully restarted and functioned correctly.
Rebooting whilst using JWM was successful, but produced the same blank screen when swapping to FbBox.

Thanks much for testing, Terry H.

You mean radky's excellent fbBox package, yes? Radky has everything in
that package so tightly integrated, I am not surprised. A bit sad, but not surprised.

I don't know how to incorporate your info just now, but it's good to know.

For now, a warning to all is in order, I suppose:
This new .xinitrc script is NOT compatible with radky's fbBox package.

You have restored your old .xinitrc, yes?

BFN.

[musher0]

musher0, what do I do with your Frankenstein?
1. clone my current puppy (protecting psave and non-OOTB installed apps)
2. replace /root/.xinitrc
3. boot
4. [can & will check jwm behaviour]

Any specific thing you want to look for/report on?

Hello B.K. Johnson.

No cloning is necessary, this script does not change anything in the Puppy, except
the old .xinitrc script. But still, make sure the neck screws are tight.

"Replace" is a big word. Yes replace /root/.xinitrc, but before, make sure you have
a back-up of your original .xinitrc script. In case something goes wrong with this new
script, you copy back the old one in place, and things are back to normal.

No, no re-booting -- as in poweroff or reboot -- is necessary. Just hit
Ctrl-Alt-BackSpace to get to the initial black console, and then type
< xwin Name-of-Window-Manager >, e.g.< xwin jwm > or < xwin icewm>, or
< xwin echinus >, etc., whatever WM you are currently using.

What to report? Anything funny, fancy or fishy. Especially "fishy". We like fishy
computer behavior on this forum! Even if all goes well, I'd like to know too. With
the name of the WM you used for the test, please.

TIA.

[Terry H]

You have restored you old .xinitrc, yes?

Yes, no issues with switching back.