.... no, I don't get it either. Seems like I have a few more on my list but no idea if it matters. DerekW

0

... yeah - they're Indeo Video Codecs. How they're tied into 'IRQ Holder for PCI Steering Device' (other than beginning with "IR") or how any of that impacts TXT files is difficult to imagine I wonder if any further explanation will be an aid or an impediment to understanding(?) Should be interesting (if we get one) I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter

0

Yeah, it was a screwy delete. Using Total Uninstall program instead of Add/Remove.When I uninstalled a program that looks for unused dll files it deleted the dll backup folder with the program.Not like if you use the programs own uninstall. I found out the only file in my list not a codec was Ir32_32.dll.Some kind of 32bit app presenter. Wanted to get rid of the infrared devices libraries. Thank you Derek W for the list,I'll check. bug

0

Ok, well my #8 has been answered I don't think running through all of the DLLs beginning with "IR" is going to be helpful, and your 'PCI steering' & infrared library ideas are equally suspect Ok, the $64 question - - Notepad has quite a few dependencies, many of which, if missing would lead to other serious or fatal windows errors. Kind of guessing, but some possiblilities might be GDI32.DLL, COMDLG32.DLL or ADVAPI32.DLL You might try running SFC and check for missing or altered files - but only replace those that are actually missing, the 'altered' ones require a bit of thought I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter

0

"it deleted the dll backup folder with the program" Files stored in a backup folder would not be of any use to Windows, so deleting those should have no effect. Those kinds of programs employ a backup folder for the very reason that the files might need to be returned to their original location - so unless you installed the program and then uninstalled it as well as the backups during the same Windows session, they are unlikely to be involved, as they would have been 'missing' for some time I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter

0

The 2 backup files in backup folder were Win System dll.s so I think the problem isn't a missing notepad.exe dependency but a Windows system module being called and not available. I was getting rid of infrared device libraries since I don't use any such devices and had two files I wasn't sure of. Those got deleted and I remember one started with "Ir". The infrared libraries were identified as such in the text within the files. Their deletion caused no problem. The "Ir" file acc. deleted had no "infrared" text in it's body. Thanks jboy,I have those 3 files. I checked notepad.exe with a module dependency program and it didn't show any missing dependencies. bug

0

Your symptoms and your methodology are a bit hard to fathom - - from what you've said, the only error comes from attempting to open a TXT file (and the default association for that is notepad), where you receive the "required library is not available" message (probably not the "exact" wording) - that suggested a missing dependency I'm reasonably certain that whatever you've 'discovered' via hwinfo is a red herring - 'IRQ holders' relate to hardware interrupts and there is no connection that I can see involving TXT files - not too much credence should be given to a single warning from a single analyzer, confirmation from another app would be more convincing It's virtually guaranteed that 'file deleters' come to grief one way or another - the potential gains are miniscule while the risks are anything but If it is a file deletion issue (and that's far from certain) then check for missing files with SFC, and replace from the CD as required I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter

0

Yeah, those programs which look for files no longer necessary nearly always get it wrong and lead to the sort of trouble you are having (as does picking off files manually). If all else fails then try Windows overlay. DerekW

0

"If it is a file deletion issue (and that's far from certain) then check for missing files with SFC, and replace from the CD as required" as in - Start - Run - type: msinfo32 (press Enter) choose Tools in the top menu bar of System Information - System File Checker - insert your Windows 98 CD in a CD drive, run SFC.

0

If you do find missing files with SFC keep a note of their names before replacing them. Some files get updated so that way if you have any problem in specific areas you can look into the possibility of downloading updated versions as necessary. This might help: SFC CAN GET IT WRONG (see my collation and WhitPhils additions). DerekW

0

If SFC in Win98 finds a newer version of a file it will ask you whether you want to keep the newer version or load the older one. In this case, since the problem is seemingly a missing dll, you keep the newer version because that hasn't got anything to do with a missing dll.

0

Thanks for the input. Who the heck knows? I ran system file checker at first and got no hits. Maybe it's a BIOS problem. I'm not messing with it since I have notepad in my context menu. It's just a hassle. Also, when I have an archive opened with the 7-Zip file manager I can't click on a text file and open it, but have to extract it first. Thanks again for the replies. bug

0

If SFC didn't find a missing dll that helped, it probably isn't a file on the Win 98 CD. No, it's not a bios problem. "...when I have an archive opened with the 7-Zip file manager I can't click on a text file and open it, but have to extract it first." If you're sure that isn't the way it worked before, un-install it in Add and Remove programs, install it again.

0

"as in - Start - Run - type: msinfo32 (press Enter) choose Tools in the top menu bar of System Information - System File Checker" How about just type SFC in the 'run box'? ... or do you just like making things unnecessarily complicated? (I think I already know the answer to that one) SFC was *suggested* way back in #10, with the admonition to replace only missing files - - I suppose by dint of repetition... ? It was worth a shot - although I am unsurprised at the lack of progress BIOS problem? Oh, c'mon now(!) I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter

0

"How about just type SFC in the 'run box'?" That doesn't work in Win 98 or 98SE. It does work in XP.

0

Oops. Typing SFC in the Run box box does work. But it doesn't work if you type command (Enter)and then SFC.

0

I just reviewed this thread and response #9 jumped out at me. If you used a program to remove unused dlls then chances are there are more missing than you are aware of. I can't fathom why you worried about unused dlls, but that doesn't matter right now. I suggest you try an over the top installation of Win98, as Derek suggested in #14, seeing that SFC didn't seem to solve the problem.

0

an over the top or overtop install of Windows or a Windows overaly (that's one I hadn't heard of) = an overtop Setup - Insert your Windows CD in a drive. - Start up your computer with a Win 98 Startup floppy disk in the floppy drive. Your floppy drive must be first in the boot order in your bios Setup of course. If you don't have a Startup disk you can make one in Control Panel - Add/Remove Programs - Startup Disk tab. - Let the Startup disk load support for a CD drive, the default, and let it finish loading. type: setup (Enter) at the prompt - Install Windows in the SAME directory it is now in - usually that's C:\Windows. It MUST be installed in the same directory in order to preserve the data and settings in your present Windows installation. It's called an "overtop" Setup because it won't wipe out was is already there. - Setup proceeds much like it does when you install from scratch, except you will be asked a lot fewer questions, and you will not be asked for the Product Key unless that info has been corrupted. If that doesn't help your problem, the dlls or whatever you removed are not part of a standard Windows 98 installation either.

0