“not allowing direct access to hardware” means that the CPU state is set so that trying to write into the I/O address space (e.g. > of the hard disk under an NT based OS? I know NT doesnt > I thought it wasnt possible for programs to write to sectors Maybe having the boot sector, protected by the BIOS somehow prevented it from doing whatever it was trying to do properly and caused the mess in the first place. In the light of this Quicken/sector 33 story, maybe the software was trying to do something similar to keep a permanent record of some sort on the hard drive (It absolutely refuses to reinstall in spite of having cleaned the folders & registry manually), and it was somehow interfering with the boot process. The weirdest thing: the problem apparently solved itself when I loaded BIOS defaults (unprotects the boot sector), after which it booted as if nothing was ever wrong with it.
#2014 turbotax return pro
I had a dual-boot Suse 8.0/Win XP Pro with lilo as the boot manager, but I wasnt able to fix anything using the Suse boot disk, or the windows XP CD (recovery console).
I also have Norton systemworks installed, which was the first thing that came to my mind when all this happened (I’ve read stuff about norton messing up windows in many different ways). Last time I uninstalled the 30-day trial version of a package called DNAsis Max, I booted up with the machine telling me that it couldnt read from the hard disk.
how many other softwares use such devious methods.
0 kommentar(er)
