If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Win98SE Explorer Large File Properties Slow
Hello,
in Windows 98SE Explorer, when I right-click and choose Properties on a file larger than 30 MB's, it takes a long time to open. I read somewhere that Windows Installer v2.0.2600.2 could be the cause, which I did install. I tried to downgrade to Windows Installer 1.1 but it didn't work and no files were changed. Could someone tell me why, when I use Windows Explorer Properties on a large file, it now takes so long to view Properties? This is very noticeable on files larger than 50 MB's and the drive seems to be reading the entire file just to view its properties. Is there a fix for this Microsoft bug? Thanks. |
#2
|
|||
|
|||
Hello,
I found the solution he http://groups-beta.google.com/group/...delay+OR+read+ The MSISIP.DLL v2.0.2600.2 has a bug in it. You must download MSISIP.DLL v2.0.2600.0 such as from he http://support.microsoft.com/default...b;en-us;836013 Do NOT double-click to install the install.exe file you download. Instead, right-click to open install.exe with a ZIP utility such as WINZIP.EXE and extract InstMsiW.exe from it. Right-click and open InstMsiW.exe again with WINZIP. Now you can extract MSISIP.DLL v2.0.2600.0. You should be able to simply drop it into the C:\Windows\System folder, replacing the defective file. If your system is not fixed, reboot. You may want to keep the defective file instead of replacing it. I suggest you keep/ZIP both versions. If you cannot replace the MSISIP.DLL file in Explorer, you will need to replace it in MS-DOS mode. Anonymous wrote: Hello, in Windows 98SE Explorer, when I right-click and choose Properties on a file larger than 30 MB's, it takes a long time to open. I read somewhere that Windows Installer v2.0.2600.2 could be the cause, which I did install. I tried to downgrade to Windows Installer 1.1 but it didn't work and no files were changed. Could someone tell me why, when I use Windows Explorer Properties on a large file, it now takes so long to view Properties? This is very noticeable on files larger than 50 MB's and the drive seems to be reading the entire file just to view its properties. Is there a fix for this Microsoft bug? Thanks. |
#3
|
|||
|
|||
Interesting. I was worried a bit that I don't have a MSISIP.DLL at all,
any version. However, I see one of the solutions at that Google search of yours is to delete that file. I guess you don't get one unless you've taken Windows Installer v2.0, (which I have never found the need to do). http://www.microsoft.com/downloads/r...eleaseID=32831 Windows Installer v.2.0 Using WinZip to look inside "InstMsiA.exe" downloaded to TEMP from there, it did indeed have an "msisip.dll". Extracting that into TEMP, indeed it is v.2.0.2600.2. Also, I note the one/only "InstMsiA.exe" I had before this was in a McAfee "setup" folder. Looking inside, there is no "msisip.dll" in that one. So, what you say has the ring of truth, BUT... well, I guess I'd rather replace the file if I had one instead of just deleting it. ANYWAY... How are installations going, now that you've replaced yours? -- Thanks or Good Luck, There may be humor in this post, and, Naturally, you will not sue, should things get worse after this, PCR "Anonymous" wrote in message ... | Hello, | I found the solution he | http://groups-beta.google.com/group/...delay+OR+read+ | | The MSISIP.DLL v2.0.2600.2 has a bug in it. You must download MSISIP.DLL | v2.0.2600.0 such as from he | http://support.microsoft.com/default...b;en-us;836013 | | Do NOT double-click to install the install.exe file you download. Instead, | right-click to open install.exe with a ZIP utility such as WINZIP.EXE and | extract InstMsiW.exe from it. Right-click and open InstMsiW.exe again with | WINZIP. Now you can extract MSISIP.DLL v2.0.2600.0. You should be able to | simply drop it into the C:\Windows\System folder, replacing the defective | file. If your system is not fixed, reboot. You may want to keep the | defective file instead of replacing it. I suggest you keep/ZIP both | versions. If you cannot replace the MSISIP.DLL file in Explorer, you will | need to replace it in MS-DOS mode. | | | Anonymous wrote: | Hello, | in Windows 98SE Explorer, when I right-click and choose Properties on a | file larger than 30 MB's, it takes a long time to open. I read | somewhere that Windows Installer v2.0.2600.2 could be the cause, which I | did install. I tried to downgrade to Windows Installer 1.1 but it | didn't work and no files were changed. | | Could someone tell me why, when I use Windows Explorer Properties on a | large file, it now takes so long to view Properties? This is very | noticeable on files larger than 50 MB's and the drive seems to be | reading the entire file just to view its properties. Is there a fix for | this Microsoft bug? | | Thanks. | |
#4
|
|||
|
|||
I have not installed anything YET. I do plan to install Norton Utilities
2004 and Anti-Virus 2004 soon, probably tonight. I do not expect any problems because the version downgrade was only from 2.0.2600.2 to 2.0.2600.0 which is a 5 month difference. If I do not post any further replies, then I did not have any problems installing. BTW, as you probably already know, many programs come with their own copy of Windows Installer 2.0. If you install any new programs with it, you will be involuntarily "upgraded" to Installer 2.0. The best way to avoid problems is to download that INSTALL.EXE file, extract the v2.0.2600.0 MSISIP.DLL, and ZIP it into an archive. You can always delete the 8.5 MB INSTALL.EXE file. I already did. I was pretty tired last night when I tried to install Installer 1.1 over 2.0. When I first looked at the 1.1 Archive file, I thought there was an MSISIP.DLL file in there. Looking again, however, I see there is no such file. Finally, did you happen to notice the date of that GoogleGroups post? It's dated August 2002. This has been a known bug for 2 years, 4 months and Microsoft has done NOTHING about it! GRRRRRRR. I wonder if XP has this same problem since they are more likely to have Installer 2.0. I'll bet you one MSISIP.DLL file XP has this bug too. LOL. PCR wrote: Interesting. I was worried a bit that I don't have a MSISIP.DLL at all, any version. However, I see one of the solutions at that Google search of yours is to delete that file. I guess you don't get one unless you've taken Windows Installer v2.0, (which I have never found the need to do). http://www.microsoft.com/downloads/r...eleaseID=32831 Windows Installer v.2.0 Using WinZip to look inside "InstMsiA.exe" downloaded to TEMP from there, it did indeed have an "msisip.dll". Extracting that into TEMP, indeed it is v.2.0.2600.2. Also, I note the one/only "InstMsiA.exe" I had before this was in a McAfee "setup" folder. Looking inside, there is no "msisip.dll" in that one. So, what you say has the ring of truth, BUT... well, I guess I'd rather replace the file if I had one instead of just deleting it. ANYWAY... How are installations going, now that you've replaced yours? |
#5
|
|||
|
|||
Oh. Better be careful, then, if you haven't tried an install yet. The
number of months difference isn't as important as... the interaction of the files inside "InstMsiA.exe". Perhaps one of them may need the newer ..dll under a particular circumstance. YOU KNOW... there are many threads here about serious failures to install Norton Anti-Virus 2004. Better make a full system backup before trying it! Checking Modified Date on about 7 of the files inside my own McAfee-supplied "InstMsiA.exe" against what is in my system folders, it seems everything is as old or older than what McAfee supplied. The McAfee dates (as shown in WinZip) are all '00. I have some system files (such as cabinet.dll & imagehlp.dll) of '99 (looking at Properties). What could that mean? Why didn't the newer McAfee files replace older ones? Can it be... McAfee extracted it's "InstMsiA.exe", used it's files, then deleted them? | Finally, did you happen to notice the date of that GoogleGroups post? | Microsoft has done NOTHING about it! GRRRRRRR. No, but I believe you. Yea, would be nice if MS did something about it. | I wonder if XP has this | same problem since they are more likely to have Installer 2.0. I am more worried about my earlobes turning purple of XP-radiation. -- Thanks or Good Luck, There may be humor in this post, and, Naturally, you will not sue, should things get worse after this, PCR "Anonymous" wrote in message ... | I have not installed anything YET. I do plan to install Norton Utilities | 2004 and Anti-Virus 2004 soon, probably tonight. I do not expect any | problems because the version downgrade was only from 2.0.2600.2 to | 2.0.2600.0 which is a 5 month difference. If I do not post any further | replies, then I did not have any problems installing. | | BTW, as you probably already know, many programs come with their own copy | of Windows Installer 2.0. If you install any new programs with it, you | will be involuntarily "upgraded" to Installer 2.0. The best way to avoid | problems is to download that INSTALL.EXE file, extract the v2.0.2600.0 | MSISIP.DLL, and ZIP it into an archive. You can always delete the 8.5 MB | INSTALL.EXE file. I already did. I was pretty tired last night when I | tried to install Installer 1.1 over 2.0. When I first looked at the 1.1 | Archive file, I thought there was an MSISIP.DLL file in there. Looking | again, however, I see there is no such file. | | Finally, did you happen to notice the date of that GoogleGroups post? It's | dated August 2002. This has been a known bug for 2 years, 4 months and | Microsoft has done NOTHING about it! GRRRRRRR. I wonder if XP has this | same problem since they are more likely to have Installer 2.0. I'll bet | you one MSISIP.DLL file XP has this bug too. LOL. | | | PCR wrote: | Interesting. I was worried a bit that I don't have a MSISIP.DLL at all, | any version. However, I see one of the solutions at that Google search | of yours is to delete that file. I guess you don't get one unless you've | taken Windows Installer v2.0, (which I have never found the need to do). | | http://www.microsoft.com/downloads/r...eleaseID=32831 | Windows Installer v.2.0 | | Using WinZip to look inside "InstMsiA.exe" downloaded to TEMP from | there, it did indeed have an "msisip.dll". Extracting that into TEMP, | indeed it is v.2.0.2600.2. | | Also, I note the one/only "InstMsiA.exe" I had before this was in a | McAfee "setup" folder. Looking inside, there is no "msisip.dll" in that | one. | | So, what you say has the ring of truth, BUT... well, I guess I'd rather | replace the file if I had one instead of just deleting it. ANYWAY... | | How are installations going, now that you've replaced yours? | |
#6
|
|||
|
|||
Hello,
Although I fixed the long pause problem while using Properties in Explorer on large files, I have noticed another small problem after upgrading from FE to SE. While using SE Explorer, inside ANY lowest hierarchical subfolder (deepest) and I click the minus (-) sign of the folder directly above each subfolder, Explorer pauses for a second before moving to the next higher folder above it. I am aware of the 9x slow "My Documents" folder and I do not use them. This occurs in ANY folder on ANY drive. I switched back to my Win98FE(1) partition, installed Windows Installer 2.0, and it does not have this problem. In FE while doing the above, movement is instantaneous when moving upwards in a folder structure. I'm not sure why this 1 second pause exists in SE. It might have something to do with memory usage. Because I did an upgrade, all the drivers are the same. Does anyone know why SE takes this extra second while moving upwards in a folder structure? Also, booting in SE takes an extra 10 seconds while my mouse cursor has an hourglass on it. FE does not have this extra 10 seconds and there is no extra hourglass time. In SE, I removed the Audio and Video drivers, using only the M$ generic video drivers, and it still has this extra 10 second boot hourglass time. Does anyone know what exactly SE is doing during this time? This are my system components. The system is stable and works correctly. Unless otherwise stated, all drivers were used successfully for years with FE: ----------------------------------------------- Abit KG7-RAID (RAID disabled) with last DM BIOS version with embedded RAID HPT 37x BIOS v2.0.1024 Promise Ultra66 Controller with v2.00.0.29 drivers Asus Geforce 2 GTS 64 MB with 6.31c drivers reinstalled 1 GB DDR266 RAM memory Hercules GTXP 6.1 with v6.09 drivers. FE uses v4.1. AMD Windows 98/98SE AGP Miniport Driver v4.8 VIA 4.37 4-in-1 Drivers VIA Bus Master (miniport) PCI IDE Driver v3.01.14 Good for all O/S's. Microsoft Disk Cache "[vcache]" maxed to 115,000 KB. "Chunk Size" set to 2048. Computer Role optimized using CacheMan v3.8 (no TSR) SYSTEM.INI: [386Enh] ConservativeSwapfileUsage=1 Internet Explorer 6 SP1 installed for SE. FE has IE 5.5 SP1. Will test FE with IE 6 SP1 soon. Task Manager OFF Norton Anti-Virus Auto-Protect not loaded All partitions were defragged. SE Registry was SCANREG/OPT in MS-DOS mode. DirectX v8.1 (I do not play games on this PC). Microsoft Intellipoint Drivers v4.12 (FE has 4.0). Anonymous wrote: Hello, I found the solution he http://groups-beta.google.com/group/...delay+OR+read+ The MSISIP.DLL v2.0.2600.2 has a bug in it. You must download MSISIP.DLL v2.0.2600.0 such as from he http://support.microsoft.com/default...b;en-us;836013 Do NOT double-click to install the install.exe file you download. Instead, right-click to open install.exe with a ZIP utility such as WINZIP.EXE and extract InstMsiW.exe from it. Right-click and open InstMsiW.exe again with WINZIP. Now you can extract MSISIP.DLL v2.0.2600.0. You should be able to simply drop it into the C:\Windows\System folder, replacing the defective file. If your system is not fixed, reboot. You may want to keep the defective file instead of replacing it. I suggest you keep/ZIP both versions. If you cannot replace the MSISIP.DLL file in Explorer, you will need to replace it in MS-DOS mode. Anonymous wrote: Hello, in Windows 98SE Explorer, when I right-click and choose Properties on a file larger than 30 MB's, it takes a long time to open. I read somewhere that Windows Installer v2.0.2600.2 could be the cause, which I did install. I tried to downgrade to Windows Installer 1.1 but it didn't work and no files were changed. Could someone tell me why, when I use Windows Explorer Properties on a large file, it now takes so long to view Properties? This is very noticeable on files larger than 50 MB's and the drive seems to be reading the entire file just to view its properties. Is there a fix for this Microsoft bug? Thanks. |
#7
|
|||
|
|||
Anonymous wrote:
Hello, Although I fixed the long pause problem while using Properties in Explorer on large files, I have noticed another small problem after upgrading from FE to SE. While using SE Explorer, inside ANY lowest hierarchical subfolder (deepest) and I click the minus (-) sign of the folder directly above each subfolder, Explorer pauses for a second before moving to the next higher folder above it. I am aware of the 9x slow "My Documents" folder and I do not use them. This occurs in ANY folder on ANY drive. Hi, This isn't exactly what you are describing, but, on several 98SE boxes I noticed it was a little slow to display the contents of the folder, some very brief pauses while the icons were being displayed. The short of it is, I had to add a registry entry for MaxIcons or something like that, and delete the ShellIconCache file(which forced Windows to rebuild it). A noticeable improvement on every machine I did it to. If you're interested, I'll dig up the procedure tomorrow morning and post it. A little tired right now, way past my bedtime. Maybe PCR has it available as a master post... MM |
#8
|
|||
|
|||
MM,
yes, I did that some time ago. I have copied and pasted the procedure below for anyone who is interested. I set my "Max Cached Icons" to the maximum years ago, which is supposed to be 2000. I will delete my ShellIconCache file and see what happens. Since I did upgrade from FE to SE, maybe there was some kind of corruption. If this isn't the solution, it'll probably be some time before I track down the problem. I can't believe SE is so much slower in Explorer and booting than FE. I might even need to call Microsoft and pay $50 for their support but let's hope it doesn't come to this. From "Tweaking your Windows Registry" http://www.techspot.com/tweaks/registry/print.shtml =========================================== Icon cache Windows stores Icons it displays in a cache file called ShellIconCache. This allows icons to appear quickly, as Windows doesn’t have to load the icons from programs that contain them. However, by default the cache holds 512 icons. Once the cache is full Windows it gets destroyed & begins again. When this happens desktop activity slows to a crawl & the desktop will most likely redraw. Increasing the Icon Cache size will decrease the amount of times this may happen in a session. Open this key [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Explorer]. Add a New string value entitled Max Cached Icons. The default value is 512. You should increase this value. I’d recommend doubling it to 1024. The maximum value for this is 2000 & minimum is 100 according to Microsoft. =========================================== Mostly Me (MM) wrote: Anonymous wrote: Hello, Although I fixed the long pause problem while using Properties in Explorer on large files, I have noticed another small problem after upgrading from FE to SE. While using SE Explorer, inside ANY lowest hierarchical subfolder (deepest) and I click the minus (-) sign of the folder directly above each subfolder, Explorer pauses for a second before moving to the next higher folder above it. I am aware of the 9x slow "My Documents" folder and I do not use them. This occurs in ANY folder on ANY drive. Hi, This isn't exactly what you are describing, but, on several 98SE boxes I noticed it was a little slow to display the contents of the folder, some very brief pauses while the icons were being displayed. The short of it is, I had to add a registry entry for MaxIcons or something like that, and delete the ShellIconCache file(which forced Windows to rebuild it). A noticeable improvement on every machine I did it to. If you're interested, I'll dig up the procedure tomorrow morning and post it. A little tired right now, way past my bedtime. Maybe PCR has it available as a master post... MM |
#9
|
|||
|
|||
It didn't work. Plus, SE wouldn't rebuild my ShellIconCache file after I
deleted it. I reduced "Max Cached Icons" to 1.5K or 1536 and it did rebuild it. Apparently, 2000 was too high a figure. I'm going to install VIA 4-in-1 driver version 4.43 tomorrow. Since it's dated 7/30/2002, I think it's a better choice than 4.37 which is dated 12/5/2001. It still doesn't explain why FE is so much faster in Explorer and why FE boots faster. I can't understand why I am having this problem. M$ should be able to handle a simple upgrade from FE to SE. There's hardly any difference between these two O/S's. If I find any answers, I'll post it here for others should they have the same problem. Anonymous wrote: MM, yes, I did that some time ago. I have copied and pasted the procedure below for anyone who is interested. I set my "Max Cached Icons" to the maximum years ago, which is supposed to be 2000. I will delete my ShellIconCache file and see what happens. Since I did upgrade from FE to SE, maybe there was some kind of corruption. If this isn't the solution, it'll probably be some time before I track down the problem. I can't believe SE is so much slower in Explorer and booting than FE. I might even need to call Microsoft and pay $50 for their support but let's hope it doesn't come to this. From "Tweaking your Windows Registry" http://www.techspot.com/tweaks/registry/print.shtml =========================================== Icon cache Windows stores Icons it displays in a cache file called ShellIconCache. This allows icons to appear quickly, as Windows doesn’t have to load the icons from programs that contain them. However, by default the cache holds 512 icons. Once the cache is full Windows it gets destroyed & begins again. When this happens desktop activity slows to a crawl & the desktop will most likely redraw. Increasing the Icon Cache size will decrease the amount of times this may happen in a session. Open this key [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Explorer]. Add a New string value entitled Max Cached Icons. The default value is 512. You should increase this value. I’d recommend doubling it to 1024. The maximum value for this is 2000 & minimum is 100 according to Microsoft. =========================================== Mostly Me (MM) wrote: Anonymous wrote: Hello, Although I fixed the long pause problem while using Properties in Explorer on large files, I have noticed another small problem after upgrading from FE to SE. While using SE Explorer, inside ANY lowest hierarchical subfolder (deepest) and I click the minus (-) sign of the folder directly above each subfolder, Explorer pauses for a second before moving to the next higher folder above it. I am aware of the 9x slow "My Documents" folder and I do not use them. This occurs in ANY folder on ANY drive. Hi, This isn't exactly what you are describing, but, on several 98SE boxes I noticed it was a little slow to display the contents of the folder, some very brief pauses while the icons were being displayed. The short of it is, I had to add a registry entry for MaxIcons or something like that, and delete the ShellIconCache file(which forced Windows to rebuild it). A noticeable improvement on every machine I did it to. If you're interested, I'll dig up the procedure tomorrow morning and post it. A little tired right now, way past my bedtime. Maybe PCR has it available as a master post... MM |
#10
|
|||
|
|||
Anonymous wrote:
MM, yes, I did that some time ago. I have copied and pasted the procedure below for anyone who is interested. I set my "Max Cached Icons" to the maximum years ago, which is supposed to be 2000. I will delete my ShellIconCache file and see what happens. Since I did upgrade from FE to SE, maybe there was some kind of corruption. If this isn't the solution, it'll probably be some time before I track down the problem. I can't believe SE is so much slower in Explorer and booting than FE. I might even need to call Microsoft and pay $50 for their support but let's hope it doesn't come to this. From "Tweaking your Windows Registry" http://www.techspot.com/tweaks/registry/print.shtml =========================================== Icon cache Windows stores Icons it displays in a cache file called ShellIconCache. This allows icons to appear quickly, as Windows doesn’t have to load the icons from programs that contain them. However, by default the cache holds 512 icons. Once the cache is full Windows it gets destroyed & begins again. When this happens desktop activity slows to a crawl & the desktop will most likely redraw. Increasing the Icon Cache size will decrease the amount of times this may happen in a session. Open this key [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Explorer]. Add a New string value entitled Max Cached Icons. The default value is 512. You should increase this value. I’d recommend doubling it to 1024. The maximum value for this is 2000 & minimum is 100 according to Microsoft. =========================================== Ok, Sorry it didn't help. A few notes on the procedure above: I had to create the reg key and add the string value in every instance. The notes I have mention the value needs to be 512, 1024, 2048, or 4096; and if you like 8192. Seems there was some banter on which number was the actual maximum. 4096 seemed to be a popular suggestion, though many swore 8192 worked also. So, I went for the biggest number, 8192. All is well on all the machines I altered. Not to say that 4096 wouldn't have produced the same results. I did dump & rebuild the ShellIconCache file first, but I don't know if it really matters which one you do first. As far as SE booting slower than FE, I never really noticed. Although, it has been a long time since I've even seen an FE box. Does it happen when booting into safe mode too? Maybe it's just a built in thing. In my experiences with XP, it is a lot slower booting and shutting down than 98SE. I also understand it supposed to be that way, though the exact reasons escape me. MM |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
EXPLORER caused a page fault in module EXPLORER.EXE. Can't start | bubbaaaa | General | 12 | October 20th 04 03:30 AM |
Help! SE won't boot | Ken Knecht | Setup & Installation | 8 | October 2nd 04 01:55 PM |
running many files through the same command | Ivan Bútora | General | 32 | July 12th 04 01:20 AM |
Continued - Windows Explorer is slow reading directories | Mario | Improving Performance | 1 | May 23rd 04 04:32 AM |
Continued - Windows Explorer is slow reading directories | Mario | Disk Drives | 0 | May 11th 04 11:37 PM |