LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Puppy (https://www.linuxquestions.org/questions/puppy-71/)
-   -   is puppy messing with my boot settings? (https://www.linuxquestions.org/questions/puppy-71/is-puppy-messing-with-my-boot-settings-485443/)

darinbolson 09-20-2006 07:09 PM

is puppy messing with my boot settings?
 
I have been having some very strange problems. I have been using windows and various versions of puppy. I frequently shutdown and boot up from cd or usb, to check out something in a particular puppy version, and then back into windows, and back again. The very strange thing is that sometimes I find that my pc will not boot from the device I want it to. I press F2 during startup, and wow. Things are not the way I left them. Funny thing is it seems to be random. Sometimes it is the boot ORDER, like the hard drive is set to boot before the cd. Last two times it was because the hard drive was DISABLED. Is there any way that puppy is doing this? Is there any way someone is doing this to me remotely? Because it CANNOT be anyone in my home. It has happened with me sitting right here. If this were a battery problem, wouldn't I be seeing boot failures, instead of altered settings?
The reason I post it here is because this has not happened before, with any other distros. I am not saying that puppy is responsible, just that it started happening around the time I started messing with puppy.

GuestToo 09-22-2006 11:50 AM

probably not

Linux does read the time from the hardware clock when it boots, and it might save the system time to the hardware clock when it shuts down, so this could theoretically disrupt your bios settings, especially on older machines with atypical hardware, but it's not really likely

other than setting the clock, Linux really should not be touching your bios settings at all

anyway, i don't think Puppy sets the hardware clock from the system time at shutdown

(the bios setting are stored in the clock chips memory)

jolphil 09-23-2006 08:16 AM

Hi
I am just guessing but I had a similar situation and it turned out
to be a weak cmos battery..Usually a 3 to 5 year old battery may need to be replaced....
Goodluck,
jolphil


All times are GMT -5. The time now is 01:53 AM.