I'm at a loss on this one....help???

Ok, I just bought a Nikon Coolpics 4300. I go to install the software and when I boot my computer back up, I get the these error messages. (See first picture)



When I click ok, I get the other error message behind the first one. (See picture two)


After I click ok for everything and now I am at the desktop, I click on Start, Programs, Nikon, and then the Nikon software, and bamm...same two error messages pop up.

Now, let me explain about my computer. I have top of the line hardware. I did a clean Win98se install, then I used a program similar to 98Lite and installed the Win95 shell replacing the 98 shell. (In other words, I have Windows98se with the 95 shell) I have the latest Java installed. The only thing I do not have is Microsoft Virtual Machine. (Doesn't the Java replace that, sort of??)

Everything on my computer works as normal. IE, Kmeleon, Eudora, Medal of Honor Allied Assault, Nero, everything works fine. I have had this configuration for over two years. Recently, when I went to install Battlefield 1942, same error message. So, I have Battlefield 1942 and the Nikon Coolpics software that will not work on my computer.

Has anyone ever seen these messages, does anyone know what these error messages mean, and does anyone have a fix for it? Yes, I can reformat and do a regular Win98se clean install and not do the 98Lite mod but since everything else works fine, I don't understand why the game and now my digital camera software would do this.

Please help. This is fustrating me alot. I like my digital camera.

 

Did the problem with the game start after trying to install the Nikon software or before? If after, ask Nikon.
If before perhaps uninstall the game.

 

I played a bit with 98lite a long time ago. If memory serves me correctly, if you choose to use the 95 shell, the win98 version of the shell32.dll gets replaced with the win95 version. Most likely the camera software wants the 98 version of the file. You'll have to extract a copy of it from your win98 setup files and replace the one you currently have. Being that you're running the 95 shell this may or may not cause other problems. I don't know.

Just thought of another way you might get it to work. Extract a copy of the file from your 98 setup files and put it in the folder where the exe file for the camera software is located. This might do the trick. If it works, it shouldn't have any ill effects on windows. This is the main reason I only played with 98 lite for a short while. Too many gotchas.

 

I just noticed the thing about the game. I would guess the same thing applys here too. It's your choice which of my two methods to try. If you overwrite the one you currently have in the windows\system folder it should take care of both the troublesome programs. Either that or put up with duplicate files and copy the 98 ver to each of the other programs folders.

 

Zander, good info. I have been using the 95 shell for two years and no glitches. Only with Battlefield 1942 and now this Nikon digital camera software. I will extract it and update this post. I don't think it will work but I'll try it sometime tomorrow.

*Update* I put in the Win98se cd.....now where is the shell32.dll file on the cd?? I did a search for it but nothing. Besides, how can I replace the shell32.dll file while Windows is running? It will tell me that I cannot replace or delete the file because Windows is using it at the moment.

 

You can always boot from a 98SE floppy, pop in the Win98SE
CD and run setup.exe from the CD.
regards

 

You can use system file checker to extract one. Click start>run and type sfc and then click ok. Choose the option to extract a file from installation disk (something like that). Then specify the path to the location of the win98 cab files. Then click ok. There's no need to specify which cab file. This may not be exact. Don't have a 98 machine handy right now and I'm just doing this from memory. It's been a while.

 

ok, I'm going to keep my 98Lite setup because it is just too good and smooth to throw away. How can I replace the Shell32.dll file in dos? I haven't messed with DOS commands too much but I guess I can do it before Windows boots up so I can replace the 95 dll file with the 98se version on the cd.

All because of a stupid digital camera........arghh

 

You don't have to do it from dos if you use SFC. Just type in the name of the file you want to restore. There will be a box where you can specify the location where you want it to put the file. By default, it'll be set to windows\system which is where it's supposed to go. Click ok and you'll then be prompted to restart the computer. When windows restarts, you'll have the new version of the file. Before doing this you should copy the shell32.dll file you're currently using to another folder in case this doesn't fix your problem or if it causes some other problem so you can change back if you want to. I'd make a new folder for it on the c: drive and use a name for the folder that is no longer that eight characters. You'll avoid long file name problems in dos if you do this. Then if you want to change the file back all you have to do is boot to a dos prompt and type the following line. This assumes copied the file to a folder on your c: drive named temp.

Copy C:\temp\shell32.dll C:\windows\system

If it were me, I'd first try extracting it to the folder that the program is located in. It won't hurt anything and if it doesn't work (it should) you can always use sfc again and extract it to the system folder.

 

Ok, for anyone else wanting to replace the Shell32.dll file. Don't do it.

I just had to reformat and do a clean install of my Windows because when you replace the shell32.dll with the newer one, Windows just simply refused to boot up. I tried everything, registry backups, accessing through DOS.

No, I didn't back up the file because it seemed logical to replace that file with a newer one.

Oh well.

 

Lighthammer - this thread had too many replies by the time I noticed so will be left alone but as stated in Rule #3, please put a meaningful title on future posts.