Name: herbertfernandes Date: July 23, 2006 at 22:04:47 Pacific Subject: my computer opens search OS: Windows 98 CPU/Ram: 128
Comment:
Hi,
Clicking on my computer or folders opens the windows find box instead of the folder itself. There is a solution for a similar problem with windows XP but could not find anything for Windows 98. Can someone help.
The link to the windows XP Solution: http://www.computing.net/windowsxp/wwwboard/forum/138864.html
I have extensive experience with Windows 98 and I have no idea whatsoever of why this is happening. I'd like to see if anyone else has a solution to this problem, though. :)
You need a good defence if a trojan barges into your territory.
Well, I guess there is no fix. Though there seems to be a long workaround by changing the file associations.
After changing the file associations properties I was able to start opening folders. But the My computer, recycle bin and Network neighbourhood icons still have the same problems.
These things, including associations, are almost always stored in the registry. Did you try scanreg /fix (it's quite harmless and often clears up a few problems)?
Scanreg /restore is OK but if you installed any programs since the chosen date/time they would have to go in again.
Tried the scanreg/restore option and it gave me an error. So now i know its really messed up.
The scanreg/fix did not work too. It like hung. After six hours it was still at 1 %.
So what did i do next, I tried starting it step by step. And it gave me a hel load of errors saying that files are missing or corrupted. Complete list below.
Check to see if the files are actually missing. If so I would go for Windows overlay (which will keep your own stuff).
If the files are there then go to www.docmemory.com and create a floppy from the download (don't just put the download on the floppy). You then boot with the floppy to test your RAM.
Oh, sure, there is something amiss here if scanreg /fix runs for 6 hours (that's insane) - almost certainly a hardware problem, since there's not much going on in a DOS prompt - memory seems probable
I'm just puzzled by the 'missing' file thing, but it's doubtless a red herring
No wiz at this, but did a search for the files mentioned above and found copies of them in a folder. Copied them and pasted it to the c drive and then rebooted, and everything went fine.
Or at least i think it did. After it started up, I noticed that there was an extra drive namely MS-Ramdrive (J). The J drive was previously the disc drive which is now (K).
What does that do. the Ram drive i mean.
But all that for later, im going crazy with these icons not working. I cant open my computer. So i have to first open my documents then move up to the disk drives and then browse through. That too is okay, but the annoying thing is that everything opens up in a new window.
Will run scandisk now and then post back. Till then thanks.
Those files should be in c:\windows\command\ebd (where ebd means "emergency boot disk"). There might be the odd one elsewhere but they've no place in the c root.
I would delete the C root copies or you might create some confusion. You don't want a RAM drive popping up for starters.
Yeah, those files should not be run as part of a normal Windows startup, they belong on a bootdisk (the EBD folder is used to create an 'Emergency Boot Disk') - it's a puzzler how or why you've gotten them to be 'missing' but that seems to be a side issue at the moment - but you'd definitely NOT want to load that stuff, if for no other reason then it complicates matters
RAM refers to system memory - you need to test that to determine if & how many sticks are failing. Bad RAM can be the cause of all sorts of odd computer behaviour - you may also want to reseat the sticks in case of poor contact
Hi, Never had that exact problem but have seen 98SE do lots of similar things. A reinstall of Windoze may be in order. Install it on top of itself. NO FORMAT! Nothing will be lost, but your problem may go away. You will pick up the usual MS garbage, but can dispose of that.
Nothing is ever 100% certain but if you look back through the posts I think we've established that as scanreg from DOS doesn't run then it is unlikely to be a Windows problem, most likely hardware.
well, after a few days got some free time today to work on the comp.
Tried the memory test, loaded the diskette and rebooted. IT started and then gave an error . I/O error and then stopped with the abort/retry/fail message.
Certainly looks like hardware but i wouldnt know it. Is it time to call the tech...
If you are happy inside the case, disconnect the power lead, remove all RAM sticks and clean the edge connectors with a pencil eraser. Then pop them in and out a few times to clear any oxide off the sockets themselves. Refit them firmly.
If this doesn't help then try just one stick at a time in first position. If it's a RAM problem this should tell you which stick is faulty.
If you can't boot with any stick then RAM is pretty well eliminated as the culprit because both sticks being faulty is unlikely.
As an after thought i went got me a new dislette and voila, the test ran.
But now I am not sure i did it right. It kept running in a loop over and over again. The counter showed that it passed 9 times and failed 0 times. Am i good...
As an after thought i went got me a new dislette and voila, the test ran.
But now I am not sure i did it right. It kept running in a loop over and over again. The counter showed that it passed 9 times and failed 0 times. Am i good...
First, apologies for yappering on about creating that disk (I now see I'd said that earlier).
You usually get two options, "Burn-in test" and "Quick Test". Maybe you did the Burn-in test. With Quick Test it runs through a series of tests (takes a while) and eventually stops, saying Passed=1 and Failed=0 if all goes well.
Might as well try that but it's sounding as if the RAM is not the problem - scraching my head rather about what it is.
I would then try scandisk (either from DOS or Windows) to see if that unearths anything.
well just had time to finish the scandisk and it showed no errors or bad sectors or whatever, so every thing seems alright there.... still cant run the scan/fix procedure...comp still hangs
Getting tricky. Run scanreg /restore again and jot down the exact error message you get. It might give us some clue.
Otherwise then Windows overlay I suppose but the symptoms don't fit too well with a Windows problem. Could help if registry is mighty screwed I suppose.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE