I think what hes getting at is more on the lines of tricking a program into thinking a reboot has taken place, just like what brought me here, I installed the latest daemon tools distro and im kinda mad. im in the middle of working on a project. my buddy sends me his C++ code, and i relaize i do not have Borland C++ Builder 6 installed, so i break out my DVD's with archived CD Images on them, and when i go to run Daemon tools, its not even there, I should of been paying more attention to the installer which instead of actually updating to the newest version (the option i chose), it uninstalled the existing version and now wont continue setup till i reboot. In the past daemon tools said u needed to reboot after install, but i just find the RUN entry in regedit, launch the command and daemon tools works fine, along with its Virtual drives. Now i am pretty sure this stupid thing will want a reboot out of me after i install. "Update(Uninstall)", reboot, Install, reboot. waist of my time if u ask me. Sorry about my rant but it really p***es me off when companies design software that claims it needs a reboot after install, when it truly does not. Given, it DOES emulate a hardware device, and you'd think something like that would need a reboot but in this case it did not. The Questions are: When a setup program requests that the system be rebooted before it can continue, what exactly takes place? what gets changed? HOW does it know that i didnt, HOW does it know when i have? Unless this event is at the kernel level loaded into memory, something like "WinRebootRequired", that wont go away until the memory is flushed, And if thats it, so be it, but i dont think it is and i dont think anyone here should dismiss this topic until it really is investigated. Because I, like so many others, would like to know. Thank you for your time and your help, and again, my apologies on the rant. -Cypris
