Recent content by Phaedros

Is there a way in Win-XP, to protect a process from being killed by any user? In Unix/Linux a normal user can be restricted to stop only proccesses of his own. In XP anybody may kill any process, which makes pc security a matter of voluntarity. Phaedros

Well, nothing worked. Finally I scrapped this Windows, formatted the system drive and installed everything from scratch. Took me considerable time, but now it's clean again.

Thanks SimonDavies, I checked the registry but all the keys "BootExecute" have already the presumed values "autocheck autochk *". boot.ini is pretty empty, and shows no suspicious entries. still, windows begins a chkdsk at every startup, and the loop must be left manually before it starts...

my windows-xp pc (up to now running perfectly) has started to go into endless loops of CHKDSK /F and reboot. although i can escape CHKDSK manually and start windows normally, on next bootup it begins again. how can i escape this vicious cycle? i have tried to boot from the windows cd and run...

microsoft access allows to specify a default path, where user data are stored generally. this is done in the ini-file, e.g. as "C:\programs\access\data\my_data". i would like to specify a second path, to have a choice later in the context menu, pointing to a backup drive for instance. hope...

netgear claim to reach 400ft, at full speed and with less interferences, with their rangemax products: http://www.netgear.com/products/details/WPN824.php´ if you wanna try... regards, phaedros

hello, is it possible to specify more than one data storage paths for access? i tried it (semicolon separation , space etc.) but nothing worked. hints welcome, phaedros (user)

thanks, this was really fast response. i'll try it asap back home. regards, phaedros

i have recently restored my system from a saved checkpoint. therefore i also have lost a few windows updates, which had been loaded in between. however, trying to reload them doesn't work because windows treats them as 'successfully loaded'. some newer updates also fail now; i guess it's because...