cluberti

Have you run performance monitor on your machine to see what is using that memory? If you run lots of apps or third-party services, you will use lots of memory on your system. If you set up performance monitor on your box, make sure that you are using the following counters: Memory: - %Committed bytes in use; page file actually used (%) - Available Bytes; Available memory - Committed Bytes; Total bytes written into virtual memory space on physical disk - Pool Nonpaged Bytes; Kernel nonpaged memory pool usage - Pool Paged Bytes; Kernel paged memory pool usage Process: - Handle count; for each process, shows the number of handle resources created - Working set; for each process, shows the amount of physical memory in use - Private bytes; for each process, shows the amount of memory the process has allocated to it Run a perfmon against your system for a day or two, and take a look at your averages (especially for counters under process). Note if any have high handle counts (anything over 3 or 4,000 is suspicious), and note the working set and private bytes of each process. You should be able to tell what exactly is using all of the memory on your box.

Are you using passive or active (port) transfer mode?

Yeah, I should probably have stated that. Be careful that you convert your advertised speed from bits to bytes - 6Mbit service should give less than 1MByte download speeds.

Yes, just changing the path will indeed do it.

I wouldn't necessarily say it uses RAM for nothing . Yes, XP uses more memory in general than previous versions of Windows - so what? Especially with SP2, it's also doing A LOT under the hood to make sure that the OS and the apps running on it stay stable, and to a lesser extent, secure. A default XP install (without third-party apps) should run very comfortably on 128MB of RAM. As soon as you add antivirus, firewalls, etc, the footprint goes up. Are these necessary? Yes. But using RAM for nothing? No.

XP embedded is a limited version of Windows XP that is meant to be run on dedicated hardware. It is also componentized, meaning that a developer can pick and choose (for the most part) what components to include and not include in their design. Windows XPe is bigger than it's counterpart, WindowsCE, but it has much better driver and application support (as it's truly Windows XP). This is not something you can go out and purchase - you have to license use of XPe from Microsoft. However, you only have to pay for products you actually sell - test and demo versions of your product using XPe can be used without paying licensing fees for their usage. Also, you can download the evaluation kit and development tools freely from the website, and use them for 120 days before you have to pay for them. http://msdn.microsoft.com/embedded/howtobuy/default.aspx If you're building a hardware device that will run Windows, XPe is a pretty good choice - it can even be made into a RTOS (like WindowsCE) with some third-party add-ons.

You could always just replace the "Locale" values in: HKU\.DEFAULT\Control Panel\International and HKCU\Control Panel\International with the correct values. The change should take place after a reboot, so if you've got a runonce script you could run it there and have the machine reboot to make it work.

If you have system file protection enabled on your machine, your script won't run fast enough to delete the files before they're overwritten again from dllcache. You should really be modifying these files in dllcache first, THEN make the changes to other locations on your system. If you disable the System File Protection, this will not be a problem.

From an explorer window: Tools > Folder Options > View tab > Remember each folder's view settings If it isn't checked, you'll need to check it.

I'm sure it was recognized, but you have to understand that version 1.x and version 2.0 of the .net framework install to two different locations in your Windows directory, and apps written for a specific version of the .net framework will only look for the framework in that framework's specific installation location. Thus, a .net 1.1 application won't even attempt use the 2.0 installation files, and vice versa, because they're in different locations. This is why you should install both 1.1 and 2.0 if you're going to install the .net framework on your machines.

I need some more information about this than just an error number, unfortunately. Can you answer these questions for me? 1. What machine is sharing the files, and what version of XP and service pack level is it running? 2. What machine is trying to access the files, and what version of XP and service pack level is it running? 3. What user accounts are you using to acces these files? 4. Do these user accounts (and requisite passwords) exist on both machines? 5. If you browse to \\<pcname>\IPC$ from the machine trying to access the files, do you get prompted for a username and password? 6. If you browse to \\<pcname> from the machine trying to access the files, do you see the shares you created?

You use the CMAK to do this. That's why it exists . Otherwise, you could do this with a product like AdminStudio or some other .msi repackaging program. It's much easier with the CMAK, but it can be done otherwise - it's a PITA to do this without using the CMAK though .

yes, but those exploits have long been removed from the cable modem. And the equipment I speak of is not the equipment you get in your house, it's the huge "connection point" for all of the cable conections in an area - it's called a "head end", and it's a feeding point for all of the cable customers in an area. They all feed into the head end, and from there everything is routed to either another head end, or to the cable company's CO.

I second the previous post - you sure you've got the proper files for an SP2 CD on the root of said CD? Sounds like you're missing something there...

You are correct, it is invalid. However, you can still set OemPreinstall = YES and not use the $OEM$ folder structure. Just omit the $OEM$ structure from your installation medium and it won't get copied.

The view settings for folders are stored in a few registry keys. The only way to know for sure which of these keys and values get modified when changing a folder's view is to get to a clean system state. First, clear the following registry values: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer delete the value "Shellstate" HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Cabine­t State delete the value "Settings" Then, delete the following registry keys: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Stream­s HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Stream­MRU HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\BagMRU HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\BagMRU HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\Bags Reboot for effect. Now, set all folders to a default view, then use a tool like inctrl5 or regmon to watch the registry changes that occur when you actually set a folder's view state (most folder settings changes are written somewhere in the \BagMRU subkeys, for a reference point - not all, but most). Once you see what changed, go into the registry and back up the changed key or value to a .reg file. Repeat for each folder you'd like to change, exporting each change to a separate .reg file. Once you've gotten all of your registry changes exported to .reg files, combine them all into one larger .reg file using a text editor (like notepad or wordpad), and you can then merge that into your new installations or other machines in order to set the registry keys that will control folder views.

In your DNS server, do you have an actual domain called "acharrow.org.uk"? If so, add an A record in that domain named "www" (minus the quotes, of course) and point it to 192.168.155.1. Perhaps I misunderstood your post, but it sounded like you created an A record called "www.acharrow.org.uk", instead of just "www" in the DNS domain zone "acharrow.org.uk". Doing it the first way will not work - you'll actually end up with a host record in the domain zone you put the A record in that will look like: www.acharrow.org.uk.<domain zone>.<tld>

You need to have the .net framework 1.1 SP1 installed for WSUS to install properly. .NET framework versions are not backwards compatible - meaning you need 1.x installed if your app requires a 1.x version.

Unless you understand cable modem equipment and have the key to unlock the actual location of the docsis equipment, I'd say no .

If you're paying for the 6MB service (and most times, you have to actually call and request the service - little trick they use to conserve bandwidth), and your head-end is the problem, the cable company will have to come out and either upgrade the equipment or create a new head-end.

Have you run msconfig to disable it's startup item? Sounds like malicious code, and a good A/V scanner should fix it. This is the sort of thing safe mode with networking was made for . You could also use the recovery console to view the file on the hard disk - boot from the installation media and run the recovery console. This gives you access to the hd without Windows running, so you can delete the file that way.

Then I'd suggest using a network monitoring tool (such as netmon or ethereal) to get a look at what's actually going on during the network transfer. I'd bet that would have some very salient information during the failure time periods. Also, you could enable logging on the userenv errors by adding the following to your registry: Key: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon Value: UserEnvDebugLevel Value Type: REG_DWORD Value Data: 10002 (Hex) The log file will be located in %windir%\debug\usermode\userenv.log. A few things to check as well: - Netlogon, Workstation, and Server services: are they all started? - NIC driver: are you using the latest version? If so, is there a driver on the Windows CD that you can try? - IPSec: are you using it on your network to secure transfers? - DNS Server: set to allow dynamic updates (all, not just secure!)? - Server's SID in AD: have you made sure that the account properties in AD match the server's UUID? - Gigabit NICs: Have you disabled media sense? Key: HKLM\System\CurrentControlSet\Services\Tcpip\Parameters Value: DisableDHCPMediaSense Value Type: REG_DWORD Value Data: 1 (Hex) - Group policy: Have you configured the DC Locator entry in this server's GPO? Group policy > Computer Configuration > Administrative Templates > System > Net Logon > DC Locator DNS Records Value: Dynamic Registration of the DC Locator DNS Records Value Data: Enabled Check all of these things, one at a time, to see if any help you.

Did you format the drive FAT32? Also, how big is the drive, and are you using winnt.exe from a DOS prompt to begin the installation?

Put your Windows Server 2003 CD in the drive, go into setup, and do a repair installation.

I would have to throw in a vote for Diskeeper, but since most of the recent defragmenting programs use Windows API's to defrag the hard disk or disks, it becomes more of an added feature set race to see which is the "best". I use Diskeeper 9 Pro and Server because of the AD integration, as that's the feature I like .