certain sites hang up
9 min read
Laptop? PC? Version of Windows?
How does this computer connect to the Internet?
Are there other computers at your location that connect fine?
When did this start? Any recent changes in hardware or software?
What have you done to try and fix it so thus far?
You say "certain sites" - does that mean you can consistently (within reason) connect to other sites with no problems?
Have you done a complete malware scan? One of the firsts thing I do when troubleshooting a PC is make sure I have a clean platform to work from. That's clean of heat trapping dust and dirt, as well as malware. Here's a link to my canned text on Cleaning Out Malware. Use it if you don't already have a complete security suite and disk cleaning utilities to rid your system of malware and clutter. You can also use it as a guide to augment or build your own security suite, and to help you develop or enhance a "Practicing Safe Computing" self-discipline.
Haven't updated to 7.0 b/c I understood there were problems with OE (email).
With any major upgrade of any complex product, a few (hopefully, only a few) will have problems. Considering Windows and IE is expected to work perfectly on close to 1Billion PCs, from 10,000s of PC makers using 1000s of different motherboards, with 100s of different CPUs, and 1000s of graphics cards, again, from 1000s of different makers, of whom they have no control over (how many different possible HW configurations is that?). Let's not forget that each PC off the assembly line becomes a unique PC just seconds after the first user turns it on for the first time, and Windows starts to configure itself for the network, printer, monitor, and other hardware it suddenly "discovers", and as each machine then takes on a different "quality" as defenses are setup to thwart the near immediate onslaught from bad guys!
So while I certainly have some "issues" with Microsoft's "business/marketing" tactics (past and current) that causes even me to stop and question just about everything Microsoft does, from the "engineering" (HW and SW) aspects, MS has done remarkably well. If you don't think so, there are plenty of free alternatives.
So for all reading, if you have not upgraded to the latest patches and upgrades because you heard there were some problems, check the facts. Are they still true? Probably not if your hardware was designed to support XP or later.
This is where I normally would take the liberty to chastise the poster a little bit for not being a responsible Internet user by staying back at IE6. By staying back at IE6 (even if using an alternative browser), the PC is more vulnerable to compromise, and more importantly, is more susceptible in becoming a threat to the rest of us! And this is where I would normally say as soon as your current problems are resolved, you need to get your system up to the latest security levels, which includes IE7, and the latest OS security patches.
But, you said you have Win2K and according the IE7 System Requirements Page, you need XPSP2, WS2003SP1, or Vista - no Win2K, for IE7. So assuming your system is fully updated with all necessary security patches and critical updates, then as Roseanne Roseannadana would say, "Never-mind!"
Although the old rule of thumb for setting the page file size is just that, "old", it is still good for a starting place. The old rule says to set your PF to 1.5 X RAM. So in your case, with 1Gb of RAM, that should be 1536Mb (1024 + 512). I normally recommend a "fixed" size PF as that eliminates the chances for file (including the page file) fragmentation due to PF dynamic resizing, a "potential" problem when running low on disk space, and/or with a heavily fragmented drive.The virtual memory window indicates: 768 MB initial size; 1115MB max size
If you have more than one hard drive, I generally recommend putting the PF on the second drive (preferably as the very first file saved on the second drive). In any case, I recommend you:
- Run Disk Cleaner or CCleaner from the above link (ALWAYS delete the 1000s of temporary files off your drive before defragging drives)
- Remove old PF (Remember to click on "Set")
- Reboot into Safe Mode
- Run chkdsk /r (note the space before the "/")
- Defrag the hard drive while in Safe Mode
- Set up new PF (again, click "Set")
- Reboot
Sorry, it would seem I was not too comprehensive!You are very comprehensive… …but have a couple of questions first:
(1) "remove old PF" - not exactly sure what that means. I could go to the virtual memory screen and remove the setting of 768MB but what would I put in instead?
(2) Remember to click on "SET" - what does that mean? How do I do that?
(3) "Run chkdsk /r (note the space before the "/")" - does that mean that once the safe mode screen is up click on start/run and type in that block? And what will that command do? or what will that command tell me about the computer?
(4) "Set up new PF (again, click "Set")" - does this mean to return again to virtual memory and type in 768MB?
Sorry about these questions. I just needed to make sure so I don't have any other foolish things that I do.
I know XP's page file works the same way as W2K, but the menu and setup screens may be slightly different. I am using XP for example, so do ask questions if W2K is too different.
My instructions were vague. Assuming you have one drive and you want to change the PF on that drive, removing the old PF and "setting" a new is done in one step. The "Set" part is just that - you must click the "Set" button for your changes to actually take place. I am pretty sure that is the same with W2K. To ensure there is no confusion in terms, the Page File is the name of the actual file the operating system uses for it's Virtual Memory (VM) - though technically different, the terms are often used interchangeably. Also seen is swap file, swap disk, disk cache and probably several other.
So, to change your current Virtual Memory setting to 1536 Mb (1.5 times your RAM) you would enter 1536 for both the initial and maximum sizes. This will create a fixed size page file on your disk.
Chkdsk is a command-line (DOS prompt) tool within Windows that checks disk volumes for errors. If run with the proper switch, it will also attempt to repair errors it finds. Chkdsk can repair bad sectors, lost clusters, cross-linked files, and directory errors. To use chkdsk, you must be logged on as an administrator, or be in the administrators group.
1. Click Start, and then Run.
2. In the 'Open' text box, enter cmd, then press Enter.
3. At the command prompt, enter chkdsk [drive]: /r (note the space before the "/r" and be sure to replace [drive] with the applicable drive letter). Press Enter to start.
Note: If chkdsk finds files in use (and it probably will), you will receive the following message:
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)
Press Y then press Enter to allow chkdsk to run at next bootup, then reboot.Note: You will see many folks suggest using the /f switch instead of /r. The /r switch is often considered better because it also instructs chkdsk to search for and attempt to repair bad sectors. /r includes /f. To see the switch descriptions, enter chkdsk /? at that command prompt, and press Enter.Ask AI
AI can make mistakes. Check the cited posts. Archived advice can be out-of-date
Don't include personal information. Questions and selected public posts go to OpenAI. About Ask AI