kjellc

Hi there ofelas! You aren't the only one experiencing this problem. As a matter of fact SAVCORP 9 does not work with WinXP SP2(RC1?), neither does Symantec Client Security 2.0 (esentially the same thing), not without some pretty advanced registry hacking (I've seen it in some forum but don't know if it actually works). This will probably be corrected in the final release of SP2, but don't bet on it! As I see it, you have three choices: 1) Go back to SAV 8.1 2) Uninstall SP2 3) Try to find a proper registry hack somewhere (Can't help you there I'm afraid, don't remember where it was ;Try different forums, search with Kazaa or eDonkey or whatever...)

As far as I can see it works rather well so far, with the exception of FAT32 partitions, where performance seems very much slower than in version 7. Of course this is not really relevant when it comes to server use, where NTFS is first choice. The standard and enterprise versions of Diskeeper 8 are supposed to be certified for use with Windows Server 2003, but you should study the table in the readme file to see which version goes with what. I have had what seems to be a communications problem between the Diskeeper Administrator console on a W2K Pro machine and Windows 2003, but I am not sure what causes it, as I am quite new at Win 2003. I would be most interested to hear if anyone else has had similar problems. Hope this was of some help.

This thread is gettin' better and better, eh? You're lucky, I had to pay with my blood (well, almost) for my dual BX'es! Of course its been a while since that...

It's good to hear! Have fun!

Actually almost all of these dual-processor BX boards had similar problems with ACPI and dual processor mode already with Windows 2000. The solutions can vary somewhat depending on the board model. In this specific case If the PCB revision is 1.05 or below, the board must be electrically modified as well as equipped with the latest BIOS. You must be skilled with a mini soldering iron and comfortable with SMD components to do this! If not, perhaps you know someone who is. If the PCB revision is 1.06 or higher only a new BIOS is required, unless you want to use Coppermines or later P3's, in which case PCB revision 1.06 with subrevision D03 or higher is necessary to work well. The PCB revision is found printed on the board between the two ISA slots. I would recommend the P2B-DS ACPI BIOS 1014 beta 03 which is the latest available and wellknown to be very stable and reliable. It can be found at ftp//ftp.asuscom.de/pub/ASUSCOM/ I don't know if ASUS still has any relevant information about this at any of their websites. If you leave your email address here, I can try to make some PDF's for you. Another good place to look for tips is the forum at http//www.2cpu.com/ where there are lots of skilled and experienced people. Next, these old boards are generally not recognized correctly by the installation program of Windows 2000 and later. You must therefore choose ACPI (multiprocessor) HAL manually in the beginning of the installation. This is described in MS KB-article Q216251 . I don't think that PNP OS setting matters at all in this case, unless you need to make some specific BIOS settings to make old hardware work. Come back here if there are any problems!

You must alter the dependencies for the netlogon service HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\\DependOnService Add "DNS" (without quotes). There should already be "lanmanserver" and "lanmanworkstation". In this way the netlogon service will not start until the DNS service has started. This must of course only be done if the DNS server is installed on the domain controller. If you are uncomfortable working with the registry, you can download a very nice and absolutely free tool http//www.nttools-online.de/english/srvmgr.htm Good Luck!