cluberti

Have you disabled simple file sharing?

Most do run just fine in x64 Windows, but there are some that do not. Also, if your 32bit program has an older 16bit installation routine, it won't install. The reason you need 64bit antivirus is because antivirus software use file-system filter drivers to do their magic (or evil, depending on how you view it), and 32bit filter drivers are not allowed to install on x64 versions of Windows.

Try this: 1. Rename %windir%\system32\clbcatq.dll to %windir%\system32\~clbcatq.dll. Note the tilde "~" at the start of the file name. 2. ***Restart the computer in SAFE MODE*** 3. Start Registry Editor (Regedit.exe). 4. Back up the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3 Delete the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3 5. Open a command prompt (cmd.exe) and type "cd %windir%" (without the quotation marks), then press ENTER. 6. Type "rmdir /s Registration" (without the quotation marks), and press ENTER. This is the location folder of the registration database. 7. ***Restart the computer regularly*** 7. Click on Start, point to Settings, and then select Control Panel. ***THIS REQUIRES THAT YOU HAVE THE WINDOWS CD*** 8. Double-click Add/Remove Programs, and then click Add/Remove Windows Components. 9. Simply click "Next" to go through the reinstall process. This will reinstall COM+. Any third party COM+ applications will also need to be reinstalled. 10. ***Restart the computer***

I suppose it's possible that there's an incompatibility - just seems really, really odd.

How long does it freeze?

http://support.microsoft.com/default.aspx?...ct=windowsxpsp2

Yes, you need 64bit drivers on a 64bit OS. You'll also need 64bit versions of your antivirus software, and any antispyware applications you may use. Check your hardware and applications before making the plunge - if you can find x64 drivers for your hardware, and your software is x64 compatible (or comes in 64bit versions), you'll be fine.

That just does not compute. Why would it only happen to x64? This is weird... Have you reinstalled, no software, no additional drivers than what the OS installs inbox, and see if the problem occurs in x64 at that point? I know it's drastic, but this just doesn't make sense.

Do you have an AMD x64 or Intel EMT64 processor? If so, DEP is enabled by default no matter what is set in the GUI. You have to use boot.ini options to turn it off.

You can always use the desktop engine of SQL server as well, MSDE, if the data set isn't going to be huge.

It could be - there were messages in the dump about the lack of a paging file, so if you were running out of physical RAM to hold virtual address space, this would be the symptoms.

Can't see anything from the dump - it's complaining that the paging file is either not on C, or not at least RAM+50MB. Get a complete memory dump with the paging file on C and at least as large as RAM+50MB, and upload it (if you don't remember the FTP, let me know).

If it works in safe mode but not a regular boot, it's one of 3 things: - non-Microsoft services - 3rd-party drivers - startup items I second the use of msconfig to disable all non-Microsoft services and all startup items, and reboot to see if the problem persists in regular mode. If the problem goes away, you'll have to start re-enabling services and startup items until the problem returns. If the problem does NOT go away after using msconfig, it's going to be a driver issue, and you will have to track down which driver is causing it by upgrading or removing drivers.

Well, event ID 7000's usually mean that a service didn't respond to the Service Control Manager in a timely fashion, or the service reported an error at one of it's checkpoints during boot. Since these both seem to be related to a USB controller, I'd strongly recommend removing and reinstalling the drivers for this device, preferrably the latest WHQL drivers for this device if they exist.

You can create junction points on the same volume, but to do so across volumes requires 3rd party software, unfortunately.

Note that there are references to this utility on Microsoft's site to do this: http://isorecorder.alexfeinman.com/isorecorder.htm

No offense, but setting that key is the same as disabling simple file sharing in the GUI .

The Windows XP firewall should be sufficient, but there are other 3rd party firewalls that may suit your needs (I personally prefer ZoneAlarm's firewall, but that's just a preference). Also, as to spyware removal, try Windows Defender: http://www.microsoft.com/athome/security/s...re/default.mspx

No, unfortunately, simple file sharing must be disabled for the security tab to appear in XP Pro.

From the horse's mouth: http://www.microsoft.com/technet/prodtechn...y/spdeploy.mspx The salient bit of the article you're looking for: The following table describes the command-line options that both the Update.exe and XPsp2.exe programs support. You can include the options you want to use when you enter the command to extract files from XPsp2.exe. Command-line option Description /U or /passive Uses default options and does not require user interaction. If you use this option, only critical error prompts appear on screen during the installation process. /F Forces other applications to close at shutdown. /N Does not back up files for removing the service pack. /O Overwrites OEM files without prompting. /Z Does not restart the computer after the installation is completed. /forcerestart Restarts the computer after the installation is completed. /norestart Specifies that the computer will not restart the when installation is completed. /Q or /quiet Uses quiet mode (the same as unattended mode, but with the user interface hidden from view). If you use this option, no prompts appear on screen during the installation process. /L Lists installed Windows updates, critical updates, and security updates. /integrate:path Combines the operating system with the service pack in a shared distribution folder for an integrated installation. /uninstall Uninstalls the package. /help Displays the same information as /?. /d:path Backs up files for removing the service pack into the folder you specify. /n Does not back up files for uninstalling the service pack.

Thanks! VBScript that runs in XP should run on Vista - all of my current scripts do, including the above, and yours looks like it should be fine.

Windows Server 2003 R2...

xpsp2.exe /F /N

Going with gunsmokingman's vbscript bonanza, here's a vbscript I wrote for RIS that waits until a network share is available, then maps the drive once the remote share is accessible. The script times out after 20 minutes (and tells you so), but this can be modified as necessary for your needs: Dim sTestPath Dim intCount Dim objnet Set objFSO = CreateObject("Scripting.FileSystemObject") Set objShell = CreateObject("WScript.Shell") Set objVolatileEnv = objShell.Environment("VOLATILE") Set objnet = CreateObject("Wscript.Network") ' An UNC path here that will be available when network connection is in place sTestPath = "\\server\share intCount = 1 ' test on volatile environment variable to avoid running logon script ' if the user has already run the logon script. If Not objVolatileEnv("LogonScript") = "Done" Then Do Until objFSO.FolderExists(sTestPath) ' sleep 5 seconds WScript.Sleep 5000 intCount = intCount + 1 If intCount = 240 Then MsgBox "Unable to connect to network share for 20 minutes. Please notify your network administrator." Exit Do End If Loop ' share/folder available on server now, so continue objnet.MapNetworkDrive "Z:", "\\server\share","True","domain\user","password" End If

Well, actually, it may have been. Without a page file, windows can't page idle process virtual address space out to disk - while this is good when you come back from hibernation (the memory manager doesn't have to worry about figuring out what goes in the page file and what is in RAM), there are programs that do need it. Again, ultimately you can alleviate this by making your memory manager's life easier by adding more RAM . Besides, you now have a 64bit processor that can natively address terabytes of RAM, and you gave it 256MB - I'm not saying 256MB shouldn't be enough, but that's still not a lot of RAM for a machine in 2006. I'm guessing you don't plan on upgrading to Vista .