Brian Masinick
@BobC: it sounds like you had good success with your first venture into this.
Your experience matches the experiences I have had (even before we added the great software we have available now).
I’ve had really good experiences running from a flash drive; one thing I want to “revisit” when I get a chance is to compare how my antiX installations that I’ve put on HDD compare to running similar software directly from USB on those same older devices. When I was using two of my oldest systems the other day, I noticed that I put antiX 19.5 on one of them and antiX 21 runit on the other one; both of them were working flawlessly on the two oldest computers I have.
A week or two ago I noticed that I must have mis-configured something on my 5-6 year old Dell Inspiron 5558 laptop on my antiX 19.5 installation because it wasn’t going to my selected window manager or connecting to the Internet properly; antiX 21 on another partition on that same computer worked fine; when time permits I’ll go back and see what was happening because I didn’t have any issues at all with antiX 19.5 when I first installed it; so I suspect an update accidentally broke something; I don’t have a defect to report; (I’m suspecting unintentional “operator error!” ????
More to come one of these days; I’ll try to run some further unofficial, seat of the pants impressions of frugal flash drive runs versus hard drive installations; unofficially both of them have run well for me.
Regarding antiX 19.5 on my Dell Inspiron 5558 laptop, I grabbed the USB I used, and booted into it on this system. I do have to use a safe video boot mode, but then I got in. I saved it in a persistent root on the USB, logged out and in and it works. I’ll try rebooting but this does indeed indicate that some kind of change after I initially installed this version on THIS particular laptop caused the issue, because I also have this installed on a much older laptop and it works fine. Anyway, I confirmed that I can indeed boot it and run antiX here; working fine now, so yup, some packaging change or other user error caused the problem!
No defect to report, as I suspected!
--
Brian Masinick
Alternate "Search B":
This search page