cholla

Swimmer ; I have my Windows ME cd but I have still used files out of C:WindowsOptionsInstall file for convenience.They appear to be the same files.I can't say if this is the case with XP but worth a try.My OS isn't stored on its own protected partition. bburton86 ;Was cache.dll the correct file name?

bburton86 : Do you have an Options or CABs folder that this might be in inside Windows? You might try search for the cache.dll to see if it can find it but it doesn't always find it in the above folders even when its there. If you have cache.dll then select have disk but go to it in Windows where it is & run it. You can get some .dll files on the internet you might try that before a reinstall.

ROM-DOS; Can you get the system.ini notepad in XP by StartRun type in "system.ini" then hit OK? Same for win.ini. I just wondered if this worked for XP? I could post my system.ini file but it is long.

I've had mine set this way for a while I think that F8 was supposed to do this for ME but it never worked very well at least on my PC. btw those are all the boot options for ME

I have Windows ME so these may not be correct for XP ROM-DOS : I use this IRQ tweak.I also use these in system.ini: [386Enh] COM3IRQ10=230400 COM3IRQ10Buffer=8760 My internal modem is on COM3 I access my system.ini this way :StartRunsystem.ini OK This take you directly to the system.ini notepad instead of the tab in msconfig.I find this is a smoother way to tweak. These are in my win.ini which I access the same way. [Ports] COM3:=230400,n,8,1,x COM4:=115200,n,8,1,x COM2:=115200,n,8,1,x COM1:=115200,n,8,1,x

The following is what I get before Windows boots: Microsoft Windows Millennium Startup Menu 1.Normal 2.Logged (BOOTLOG.TXT) 3.Safe mode 4.Step-by-step confirmation Enter a choice Time remaining (The caps are as the screen shows) If I have made some changes I get this message: "Please wait while Setup updates your configuration files This may take a few minutes Completed file updating, continuing to load Windows It doesn't show the autoexec.bat screen I guess what ROM_DOS awnsered is the way XP does this.What I like about the way Windows ME does it is it gives a selection for safe mode if you put 3 in Enter a choice.If you could do this in XP I thought it might help some that have trouble getting into safe mode.

bburton86: You could try scannow check the MS link below for this. http://support.microsoft.com/kb/310747/EN-US/

This is for XP but if the registry key is in 2000 then you can probably change the MTU to where you want it this way.The PMTUDiscovery is in Cablenut. I made some changes in this I think this is better information. I find some conflicts of information on this .So I guess you need to try it both ways if you are having problems setting the MTU. EnablePMTUDiscovery When set to 1 (True), TCP attempts to discover MTU automatically over the path to a remote host. Setting this parameter to 0 causes MTU to default to 576 which reduces overall performance over high speed connections. Setting MTU overrides the default MTU for the network interface it is added to. Note that if EnablePMTUDiscovery is set to 1, TCP will use the smaller value of this local MTU and the "Discovered" MTU of the underlying network connection. If you'd rather use only the MTU value specified here, you'd have to disable PMTUDiscovery, which would prevent your system from detecting the network MTU. HKLMSYSTEMCurrentControlSetServicesTcpipParameters EnablePMTUDiscovery="1" (DWORD - boolean, valid settings are 0-->False and 1-->True. Many connections perform better with this entry at 1, however, if you prefer to set your upstream to send fixed 1500 packets, you might want to use 0 instead). When set at 1, establishing connections and initial transfer speed might slow down a bit, however you will get better throughput if somewhere in the path large packets need to be fragmented. To modify the PPPoE MTU size, create the following registry key: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNdiswanParametersProtocols0 Then add the following registry entries.Entry name Data type Value data ProtocolType REG_DWORD 0x00000800 PPPProtocolType REG_DWORD 0x00000021 ProtocolMTU REG_DWORD the appropriate MTU size (in decimal) To do this: 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNdiswanParameters 3. On the Edit menu, point to New, and then click Key. 4. Type Protocols, and then press ENTER. 5. On the Edit menu, point to New, and then click Key. 6. Type 0, and then press ENTER. 7. On the Edit menu, point to New, and then click DWORD Value. 8. Type ProtocolType, and then press ENTER. 9. On the Edit menu, click Modify. 10. Type 800, and then click OK. 11. On the Edit menu, point to New, and then click DWORD Value. 12. Type PPPProtocolType, and then press ENTER. 13. On the Edit menu, click Modify. 14. Type 21, and then click OK. 15. On the Edit menu, point to New, and then click DWORD Value. 16. Type ProtocolMTU, and then press ENTER. 17. On the Edit menu, click Modify. 18. Type the appropriate MTU size (decimal value), and then click OK. 19. Quit Registry Editor. Notes

php those are the msdos.sys file the first screen is how to open the file so it will let you edit it.. The second screen is the edit msdos.sys screen.Another OS might not want all the settings in mine but the Logo=0 & BootMenu=1 are probably alright.I would like to have the 98 boot menu because it is longer I'm not sure it would actually function though. This is a screenshot of my autoexec.bat

Can you do this in Windows XP? I have done this in my Windows ME. 1.Go to folder options from MY Computertoolsveiw check "show hidden files & folders" 2.StartProgramsAccessoriesMS-DOS Prompt 3.In the MD-DOS screen type what is in the first screen shot below. 4.In the second screenshot type logo=0 like in the screenshot. This should give you a black screen on startup instead of the windows logo screen This black screen has information in it sometimes. In mine I also have BootMenu=1 this gives an easy way to go to safe mode.

Windows Update still works for Windows ME I don't know if it does for 98 or 98se.I don't think any of these have tech support anymore but if you pay MS might.

boywonder : Good hint on unplugging the satellite box.This is the receiver box for DISH or Direct TV.If you leave it plugged into a wall jack & your PC is on the same line (not just the same jack) you will get a slowdown & sometimes more disconnects.The only thing it needs to be plugged in for is ordering pay for veiw or accessing your account for customer service .The rest of the time it can be unplugged.Mine is most of the time & I haven't had any problems receiving the channels or gotten a letter from DISH.So that makes at least 2 of us that had a slowdown from the satellite box being plugged in.

To show the accuracy of the NDT tests here is how it reads my dial-up. WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 123.16Kb/s running 10s inbound test (server to client) . . . . . . 113.79kb/s ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Full Duplex mode No network congestion discovered. Good network cable(s) found Normal duplex operation found.

Gib4500 : Read & do the things in this sticky it is the first step in getting help. http://www.testmy.net/forum/index.php?topic=2097.0 After that it never hurts to contact your ISP & make sure you are getting what you are paying for meaning that your modem is not capped lower than what your paying for.

My ISP is just OK so I wouldn't recomend it.I just hate to try another one that might be worse. Mine blocks ping & tracert so I can't do them.Their plus is the techs are local so I don't have to talk to someone in India.

asubaseball727: Heres the tutorial the link wasn't complete http://www.testmy.net/forum/index.php?topic=890.msg8017#msg8017

DMN;Maybe this will help with changing the MTU I didn't ask but I assumed you have XP. .I didn't find 3 pages of options for Internet Tweak at the link or anything about xD. A lot of the information below is for PPPoE but I think some of it can be applied to Dial-up so XP will use MTU of 576 & MSS of 536 for dial-up.When this is what is wanted. I find some conflicts of information on this .So I guess you need to try it both ways if you are having problems setting the MTU. EnablePMTUDiscovery When set to 1 (True), TCP attempts to discover MTU automatically over the path to a remote host. Setting this parameter to 0 causes MTU to default to 576 which reduces overall performance over high speed connections. OR Setting MTU overrides the default MTU for the network interface it is added to. Note that if EnablePMTUDiscovery is set to 1, TCP will use the smaller value of this local MTU and the "Discovered" MTU of the underlying network connection. If you'd rather use only the MTU value specified here, you'd have to disable PMTUDiscovery, which would prevent your system from detecting the network MTU. The above information seems to conflict. HKLMSYSTEMCurrentControlSetServicesTcpipParameters EnablePMTUDiscovery="1" (DWORD - boolean, valid settings are 0-->False and 1-->True. Many connections perform better with this entry at 1, however, if you prefer to set your upstream to send fixed 1500 packets, you might want to use 0 instead). When set at 1, establishing connections and initial transfer speed might slow down a bit, however you will get better throughput if somewhere in the path large packets need to be fragmented. To modify the PPPoE MTU size, create the following registry key: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNdiswanParametersProtocols0 Then add the following registry entries.Entry name Data type Value data ProtocolType REG_DWORD 0x00000800 PPPProtocolType REG_DWORD 0x00000021 ProtocolMTU REG_DWORD the appropriate MTU size (in decimal) To do this: 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNdiswanParameters 3. On the Edit menu, point to New, and then click Key. 4. Type Protocols, and then press ENTER. 5. On the Edit menu, point to New, and then click Key. 6. Type 0, and then press ENTER. 7. On the Edit menu, point to New, and then click DWORD Value. 8. Type ProtocolType, and then press ENTER. 9. On the Edit menu, click Modify. 10. Type 800, and then click OK. 11. On the Edit menu, point to New, and then click DWORD Value. 12. Type PPPProtocolType, and then press ENTER. 13. On the Edit menu, click Modify. 14. Type 21, and then click OK. 15. On the Edit menu, point to New, and then click DWORD Value. 16. Type ProtocolMTU, and then press ENTER. 17. On the Edit menu, click Modify. 18. Type the appropriate MTU size (decimal value), and then click OK. 19. Quit Registry Editor. Notes

DMN:Unless the changes in cablenut change the MTU then I don't know maybe ROM can help you with this when hes here. I'm not much of a fan of tweak programs they mostly make system changes for you you can make yourself & may make some changes you don't want. But I will give it a look.

DMN; The shortest phone cable from the PC to the wall is best .But you need to have it usable not many will use a cable so short they have to set the PC on the floor by the wall jack On this setting if you don't like the way it performs change back to 1.EnablePMTUDiscovery = 0 On the phone cable if you can make your own with twisted pair CAT3 or Cat5 they are the best quality.You probably already do this but your modem internal or external should be the only thing plugged into the wall jack.& no phone plugged into the modem .Most have a place for this but it lowers performance.

DMN some of the information in this MS article may help trobleshoot & fix your network places. http://support.microsoft.com/kb/825826/en-us I think the regedit settings in this link are not for XP but 98 &ME. http://www.webnovice.com/dec00/modemoverclock.htm The only way to find your line or loop distance then will be to call your telephone company.You need to talk to a tech. I will do some checking into compuserve but the few disconnects sounds good. Your ISP is probably setting the MTU at 1400 but it could be something else maybe ROM could help with this.I think he had to get his to work at 576 for gaming. Have you installed cablenut?The settings below in cablenut may help this.It makes the settings in the registry for you. TcpWindowSize = 6432 GlobalMaxTcpWindowSize = 6432 TcpRecvSegmentSize = 536 TcpSendSegmentSize = 536 EnablePMTUDiscovery = 0

Hey DMN.First ROM has an exceptional connection I think he would be the first to admit that.Most of us with dial-up do not.Yours may be already as good as you are going to get it but trying the tweaks can make your connection perform better in a lot of cases.The testmy test shows you have AOL a lot of people complain about AOL I haven't had an AOL connection so I don't know but in general if you can get an ISP thats not AOL it will probably be better. ROM suggests disabling compression but when he does this it forces MSMPPC compression. My ISP doesn't support this so when I disabled all compression I experienced a real slow down It may be the same for you. I will see if I can find you something on getting the network places to work. There are several regedits in the link so which one do you have a question about? Try the tcpip analyzer at the site below & post the results. https://www.speedguide.net/ Also you line or loop distance is a major factor on dial-up speed.Thee best way to find legnth is to call your telephone company but the CO distance here is a good estimate to start with. post your distance after checking. http://www.dslreports.com/prequal/distance

resopalrabotnick ;Thanks the water cooling makes more sense now.I didn't realize it just cooled the warm(hot) water back to room temp(or about).The PC in a refrigerator didn't worry me much about condensation because most are frost free basically this is a warming cycle that dries the air in the refrigerator.But a lot of the compact refrigerators like a lot would try to use just for a computer are not frost freeso might pose a problem.You are right though almost never opening one would keep a lot of moisture out of the refridgerator. My concern was using very cold air or liquid directly into the PC for cooling & this causing condensation. I still think a humidity sensor in a PC case would be interesting.

II still believe anytime you cool a computer with anything but heat sinks & air flow there is potential for condensation.The easiest example is put icewater in a glass & see how much water it condenses on the outside of the glass.The more humid the atmosphere you live in the more condensation.That being said I would like to see some experiments where the air was cooled by refrigeration or thermoelectric into a computer case that had a humidity meter to measure the humidity in the case.I think a humidity meter would be an interesting sensor on any computer even a stock air cooled one.

When setting the RWIN in XP this is some good information. AFD(Ancillary Function Driver for Winsock http://support.microsoft.com/kb/Q214397 http://support.microsoft.com/kb/Q246984 http://support.microsoft.com/kb/Q314053#top In the WinNT network architecture a layer is placed on top of the TCPIP layer called AFD(Ancillary Function Driver for Winsock). The AFD provides the winsock interface, which is used by most network applications in Windows and is also supporting things like DNS and DHCP. The AFD provides two windows which acts as a flowcontrol for the application creating the socket: AFD-Send-Window: Used when the application is sending data over a connection, if if more data is sent than the receiver is able to acknowledge then the AFD-Send-Window will block the transfer for the application, when it reaches the limit of the AFD-Send-Window. AFD-Receive-Window: Used when the application is receiving data over a connection, if the application is not able to receive data fast enough or is blocked by other processing which keeps it from receiving data, then the AFD-Receive-Window will act as a buffer until it reaches the limit of the AFD-Receive-Window, where it will then block the remote-application from sending data. The two default AFD-Windows is by default self tuning using the following values depending on the total amount of RAM detected. When an application creates a socket it can specify a different AFD-Window than the default. Default AFD Send- & Receive-Window = 4096 Bytes (If less than 19 MByte RAM) Default AFD Send- & Receive-Window = 8192 Bytes (If more than 19 MByte RAM) In the scenario where using a network with high latency or high bandwidth the AFD-Send-Window will constantly be blocking the application's transfer if the AFD-Send-Window is set too low. The AFD-Send-Window should have the same value as the optimal TCPIP-Receive-Window to get the best upload-speed. In the scenario where using an application which is not able to handle situations where the data is being sent in bursts. Then increasing the AFD-Receive-Window will allow to smooth out the bursts, and avoid blocking the remote-application sending and will increase the overall download speed. Also making sure that the window is larger than any reply being sent back will avoid blocking of the sender of the reply, as it has to wait for ACK to complete it's reply. EDIT: To make this clearer the settings right below are examples .They would be good for some OS's but you need to calculate the correct one for yours. To set the default size of the AFD-Windows use the following DWORD registry keys : [HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Afd Parameters] DefaultReceiveWindow = 16384(Example) DefaultSendWindow = 16384(Example) Note that the AFD-Windows should be rounded to a multiple of page size(Usually 4096 Bytes). Not a multiple of the Maximum Segment Size(MSS) which is recommended for the TCPIP-Window. Note that applications which specifies their own AFD-Windows for each of their sockets by using setsockopt and specifying a new value for the SO_RCVBUF parameter (Not possible for RPC services), will not be affected by changing the default AFD-Windows. DefaultReceiveWindow - The number of receive bytes that AFD buffers on a connection before imposing flow control. For some applications, a larger value here gives slightly better performance at the expense of increased resource utilization. Value Type: REG_DWORD Default: 4096/8192/8192 DefaultSendWindow - This is similar to DefaultReceiveWindow, but for the send side of connections. Value Type: REG_DWORD Default: 4096/8192/8192 GlobalMaxTcpWindowSize - The TcpWindowSize parameter can be used to set the receive window on a per-interface basis. This parameter can be used to set a global limit for the TCP window size on a system-wide basis. Value Type: REG_DWORD

Sharky2006 ;I'm going to let FallowEarth help you for the most part .The NDT tests are a guide at best.this part you ask about is your RWIN setting " Increasing the current receive buffer (121.0 KB) will improve performance This connection is network limited 14.34% of the time." I have dial-up & this test never tells you your RWIN is large enough.That being said it does some usuable readings I will put in a lint to some topics on interpreting the test results. On the speedguide test it says you should change your rwin to127776 so it is a multiple of your MSS.There are 4 RWIN settings in XP & all of them do not use the MSS as the multiplier. http://www.testmy.net/forum/index.php?topic=9537.0 http://www.testmy.net/forum/index.php?topic=9538.0