If you have shut down problems, try this bat file. You will need to copy the code below into Notepad or some other text editor, give it a name (e.g. 'shutdown.bat' (no quotes)), and place it on your desktop or wherever you want it. When you get ready to shutdown, double-click the 'shutdown.bat' and it will shut down the computer for you.
net use * /delete /y
C:\WINDOWS\RUNDLL32.EXE user.exe,ExitWindows
More below on shutdown problems (or above as the case may be)..
There is a intermittent problem where Win95 hangs while disconnecting from an ISP when using the Dial-up Networking. For reasons unknown, it affects some people, but not others. Those affected typically encounter the problem for about 10% of disconnects.
There are 2 possible workarounds, provided that you don't also use your PC on a LAN using Netbios over TCP/IP.
Preferred:
1) In Control Panel, Network TCP/IP, Properties, WINS Configuration
- disable WINS Resolution.
If the above doesn't help try:
2) Rename file C:\WINDOWS\SYSTEM\VNBT.386 to something else
(e.g. OLD_VNBT.386)
You should restart Win95 after applying either change to make sure it takes effect.
Notes:
- Option #1 may cause the file C:\WINDOWS\WINSOCK.DLL to be renamed
C:\WINDOWS\WINSOCK.OLD. This would prevent 16-bit programs from accessing
the Internet (32-bit programs would not be affected as they use
WSOCK32.DLL). If you use 16-bit programs, rename the file back to its
original name to fix the problem.
Thanks to Michael Santovec
When you upgraded your Winsock, the upgrade installer should have left a folder titled 'ws2bakup' in your windows directory. In that folder is a batch file 'ws2bakup.bat'. Run this batch file after completing a clean reboot. When I first ran this I received errors but the second time I ran it, it worked. In any case if it works you will have your previous Winsock back.
If you want to see what this batch file does just call it up in any text editor.
Thanks to Shawn Thomas.
For all those who need a workaround for the 'History not displaying grouped by day bug', first find CACHEVU.DLL on your system and rename it to CACHEVU.BAK, then run Regedit and find all references to CACHEVU.DLL and rename them to SHDOCVW.DLL.
Then, restart your system and all should be fixed!
Thanks to Brian.
1. I think I may have found the answer to one of the cache problems in IE4. The one where when you go back to an already visited page IE checks it again instead of just using the local stored cache page immediately and so you get modem lights and a delay... I discovered the key in the following location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main
Change:
AutoRefreshLocalPages "yes"
to
AutoRefreshLocalPages "no"
Having tested it, it seems to work fine with no modem lights coming on for pages already visited( as long as all items in page where originally downloaded of course) and of course it's now very fast..( update ..this works so well I don't know why MS hadn't pointed it out ages ago.)
2. I found some registry key settings for Sockets and Connections at : HKLocal_Machine\System\CurrentControlSet\Services\VxD\NWLink\Ndi\params\maxs ockets
and
HKLocal_Machine\System\CurrentControlSet\Services\VxD\NWLink\Ndi\params\maxc onnect
I noticed that the `maxconnect' minimum settings and `maxsockets' minimum settings were very low (set at 1 or 2). I decided to change them in the registry and once found set the defaults higher for both minimum settings and for the normal default settings . I found it worked better if the minimum setting is lower than the default setting.
Browsing has now taken on a huge leap in speed to equal or better Netscape. I am not sure if these settings are doing what I think they are doing so if a few more of you could try it and see what results you get it would be interesting.( Many people have already responded that it has indeed worked) I've seen my modem download speeds for web pages hit new highs never seen before! With more sockets and connections open as minimum, lots more web page items get down loaded at the same time...the speed is probably twice as fast as before if not more..
Try changing the defaults and minimums to experiment for best settings on your system.
In Maxsockets registry folder I now have Default "25" Max "255" Min "25" Optional "1" ParamDesc "Maximum Sockets" Type "int"
In Maxconnect registry folder I now have : Default "15" Max "128" Min "12" Optional "1" ParamDesc "Maximum Connections" Type "int"
I also use MTUSpeed which sets the MAXMTU AND RWIN settings etc. I use 1500 maxmtu as thats what my ISP is set at, RWIN 6X, 64 hops, NDI cache 32k
3. I noticed on my system that there are two `main' folders for IE that contain a lot of settings. They are:
HK_local_machine\software\Microsoft\Internet Explorer\Main
and...
HK_users\Default\Software\Microsoft\Internet Explorer\Main
Some entries in these folders conflicted. Especially the search page settings which after having corrected them here now call the page that I want to do my searching with. Also conflicting were the cache directories and others so make sure that all your directories are correct in both these registry folders.
I also noticed that even though I had selected that `temp internet files should not be deleted on exit' in the IE4 advanced settings tab, I found that the entry in the former registry folder still had the entry as `yes' to clear the temp files. This could be the reason that so many sites just visited seem to disappear so quickly. Once set to `no' everything is fine and now I can browse my history folder off line and everything is there.
There are other entries to turn off the cache completely (not tested by me yet) and others. Check em out, it could solve some of your probs..
So check out those two registry folders and make sure nothing conflicts and that the `delete temp files on exit' setting is changed to `no'...The entry doesn't actually say delete temp `internet' files so I'm not 100% on this one. Tests have shown that this last one actually doesnt seem to make any difeerence so it's up to you wether you set the temp files to no.
Thanks to Dane.
You sate that you are receiving an error message after installing PWS 4.0 stating that MSIMN.EXE caused a fault in INETCOMM.DLL.
PWS 4.0 updates the TCP/IP Stack and does not update the INETCOMM.DLL file to work with it. This issue has been resolved by downloading and installing the following files:
http://support.microsoft.com/download/support/mslfiles/VIPUP20.EXE
http://support.microsoft.com/download/support/mslfiles/VTCPUP20.EXE
Thanks to Andrew Robinson
You may have selected Control Panel, Internet, Connect As Needed (IE3) or Connect using a Modem (IE4), and at boot are automatically starting some program that uses TCP/IP. This could even be a program such as Norton Utilities that is configured to monitor TCP/IP activity. You'll need to disable one or the other.
Although most settings in this area are specific to Internet Explorer, the Connection setting applies to any TCP/IP activity in the PC.
Thanks to Michael Santovec.
For more information on this, see the article: How to Create and Use the Modemlog.txt File http://support.microsoft.com/support/kb/articles/q142/7/30.asp
If that doesn't show anything helpful, I would recommend recording a ppplog.txt file. This will show the negotiations between the Win95 DUN and the ISP.
For information on this, see article: How to Create a Ppplog.txt File http://support.microsoft.com/support/kb/articles/q140/7/91.asp
Thanks to Michael Santovec.
If you get this error, try this. In Outlook Express, go to Tools|Options|Send. Check if not checked - Send messages immediately. Or if checked, uncheck and recheck and click on Apply.