Hmmmmm. The problem happens only with my customized pproconf.pcf and only if ppro is loaded at startup (either via registry entry or via a link in the startup folder of the start menu).
When using default.pcf I cannot replicate the problem at all. With my customized pproconf.pcf, if i start ppro after logon the problem may or not may not occur no matter how much i wait between the "end" of the logon (desktop shown, no hdd working) and loading ppro. Once ppro loads without causing the beeping problem, the only way to replicate the problem is to reboot. You must be right, it must be related to the sequence the programs load during startup.
