Thanks for the suggestions.
Have tried the registry edits and what seemed the relevant SpeedXP options
(e.g. not using NTFS) There seems to be a little improvement, but much of
the slowness compared with the lower spec Win98 system remains.
The slowness is not be purely an Internet Explorer issue. Playing DVD's
produces some break-up on sound, though the picture is tolerable. The
previous owner (with a previous installation of XP) did not have this
problem. Also I mentioned in a separate thread that there is a delay before
modem dialling, but this may be a different problem.
John
The Unknown P said in
There are several problems with IE that make it slow. First of all it
checks all remote computers for scheduled tasks. It also limits the
number of simultaneous downloads so that pages with many graphics on
them will take longer to load.
go>start\run and type in regedt32 and click
There is no need to run regedt32.exe in Windows XP as it does nothing more
than regedit.exe. regedt32's functions got rolled into the regedit.exe
program. All that regedt32.exe does is to load regedit.exe. See
http://support.microsoft.com/?id=141377.
ok or hit enter on your keyboard. Now follow this route by clicking
the +symbol beside the entries in the following order.
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Eplorer\RemoteC
omputer\NameSpace
Key is misspelled. There should be an "x" in "Eplorer". Don't know why
this poster thinks IE goes polling around all remote computers (as there
could be millions of them enabled) for scheduled tasks. Also, the Explorer
registry subkey affects Windows Explorer, not Internet Explorer. This key
affects how *Windows* Explorer will poll shared folders.
Now once you have clicked the + beside namespace you should see two
keys under it. Locate and delete the following key by right clicking
on it and then click delete. D6277990-4C6A-11CF-8D87-00AA0060F5BF
That stops IE from searching for scheduled tasks.
No, that stops *Windows* Explorer (not *Internet* Explorer) from searching
for Scheduled Tasks in *shared* folders (and does NOT apply when using
Windows Explorer to view web sites). Go read:
http://www.winnetmag.com/Article/ArticleID/41109/41109.html
http://www.jsiinc.com/SUBG/TIP3400/rh3492.htm
http://www.windows-help.net/WindowsXP/troub-02.html
I suppose you could use IE to browse shared folders instead of using Windows
Explorer, just like you can use Windows Explorer to browse web sites. It
didn't sound like the OP was trying to use IE to browse shared folders on
their network but instead using it in the most common scenario of browsing
to a web site. Deleting this key (to prevent Windows Explorer from
retrieving the Scheduled Tasks from a shared folder) might speed up network
browsing if you happened to use IE for that, but it won't change when using
HTTP to browse web sites. Also, browsing a shared folder is not the same as
browsing a web folder. When you right-click on a folder and go under the
Web Sharing tab, you must be running a web server to proffer that path to
visitors. File/folder sharing does not require nor use a web server.
Now we'll increase
the max number of downloads IE can do. You may have these sub keys
already installed but if you don't I will talk you through the
<snip>
Might be lot easier to just read Microsoft's own KB article at:
INFO: WinInet Limits Connections Per Server
http://support.microsoft.com/?id=183110
However, note that the values entered are hexidecimal by default. If you
enter a value of 10 (without clicking the radio checkbox for Decimal), you
will enter 10 hex which is 16 decimal. Although this may appear to let you
have more concurrent connections, that only works on sites that do not limit
your connections at their end. Many web sites will limit the total number
of concurrent connection from the same IP address. You might configure IE
to have 100 decimal concurrent connections but the web site sees your IP
address on every connection and could reject any further connections after,
say, 4 connections were already established. You can only widen the
connection limit on your end, not on their end.