The Woof build script '3builddistro' now asks if the mechanism is to be disabled or not, along with some explanation of the consequences of either choice.
There are some other possibilities under consideration, such as reading the shift or control key status at bootup, however for now I want to move ahead with getting Precise Puppy to RC status, so minimizing changes.
Comments:Posted on 18 May 2013, 7:17 by scsijon
it seems that if I say yes to using the flag in the woof build, adding 'pfix=ram,nox' to the startup line is ignored.
I'm also getting a vbe: error (0x4f15): 0x034f now appearing onscreen after it's login line.
Posted on 18 May 2013, 8:35 by BarryK
re pfix problem
I just looked at the code in the init script, dated 14 May, and it seems that pfix=ram should work.
I'll test it anyway.
Posted on 18 May 2013, 12:01 by BarryK
Hmmm, there's a bug in the rewritten pupdesk.flg mechanism. I will fix it this afternoon.