Windows 95/98/Me/NTPost your Windows 95 / 98 / ME and NT questions here. Please make sure you specify your OS version.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
I have performed a reinstall: CDRom > Setup > 30 min process
While in progress I got a message saying "something the matter with
CAB35 > some INF or INI.dll and could possibly cause WIN98 not to function correctly"
Indeed, when starting up it says: fatal exception OE 0028: C02A27A8 in VXD
VWIN32(05) + 000012D0.
After clicking a key, everything proceeds smoothly.
However, how to find that CAB35 folder, see whether there is such a dll and
reinstall it.
Help will be appreciated.
Adriaan
Didn't find the information you thought to find? Check out these Similar Threads
The CAB35 folder should be on the windows CD in the i386 folder, viewed in explorer. I think you can point sfc to that folder and file and tell it to reinstall.
In your other post i believe I'm working on the other part of your question. Please don't double post. It's too hard for readers and me to follow.
As I could not find i386 in CAB.35 of the C:\Win98 CDRom, I tried to perform
a new Windows Setup (lasts about 30 minutes)
While in progress I get:
Setup cannot find:
sourcefile G:\win98/msltus40.dll
targetfile C:\windows\system\msltus40.dll
When clicking skip, I get:
Cannot find 35.CAB on Win98 CD
sourcefile: G:\win98\Win98_35.CAB
targetfile: C:\win98\msjter40.dll
Both are version 4.0.2521.8 (date 5.5.1999) fresh copy and present copy.
Then I tried to transfer the identical files from my main PC to the network PC
and stored them in C:\Windows\System.
The files from my main PC are working correct, while the files on the network PC are mentioning a lot of errors: heap, etc etc.
Though I get the question "do you want to change this file into that file" and
answer YES, the faulty files remain present; so they are not replaced by
the tranferred files from my main PC.
I did not dare to delete the faulty files first and then add the proper dlls
as I am not sure about what is going happen. It might be possible that when
I delete them first the Network PC or the network itself does not function nomore.
by a.ruiterI have performed a reinstall: CDRom > Setup > 30 min process
How did you preform the reinstall ?
Did you boot to the Startup disk or boot from the HD ? Bootng from the HD allows thing to be loaded that may well mess up an install/reinstall.
Before you started the reinstall did you shut down EVERYTHING that was not necessary to run Windows. This includes AV & Firewalls. Anything that is running and using files MAY NOT get overwritten properly.
When doing a reinstall it seems much better to boot from the floppy ( which according to your other post you can't do ( unless that has been fixed)) Set the path to CDROM Letter/Win98/setup. ie: D:/Win98/Setup
Or better yet. Copy the files in the Win98 folder to a folder on the HD ( in a partition other than C: ) set to install path to that to run setup. ie: D:/Opitons/setup. This also makes it easier for Windows to make reapirs on the fly if needed.
Going to see what up in your other post.
BillyBob
Last edited by BillyBob; 20th January 2005 at 21:25.
When doing a reinstall and booting from the HD there is a STRONG possibility ( unless the user watchs CAREFULLY ) that a new Windows folder will be created. ie c:/Windows001 instead of just C:/Windows
I have not seen this happen when booting from the Floppy.
I have started the reinstall from CDRom, by going to SETUP.
Indeed, I remember another possibility by starting from a floppy.
I am sure to have made copies of the description of that process, but have not been able to find it.
I think it is abt the very same 30 min Setup-process.
I did not know that there is a difference in the 0000 or 0001 files.
I have to do another setup anyway as the fatal error is back again.
I have made a copy of your posting containg the question "How did you perform the reinstall + instructions"
I am sure not to have shutdown any of the programs on the PC when
starting to the new setup.
I am pretty sure that WIN98SE is not on my HD.
Furthermore I have a second partition D:\. I think it is abt. 8 Gb.
I need to study your instructions on how to get WIN98SE from CDRom
to the HD and consider the partition letters.
Reinstalling from CDRom will be G:\ and reinstalling by means of the floppy
after WIN98SE has been put to HD will be C:\.
I have started the reinstall from CDRom, by going to SETUP.
Indeed, I remember another possibility by starting from a floppy.
I am sure to have made copies of the description of that process, but have not been able to find it.
Very simple. Boot to the floppy. Type CD letter:\Win98\Setup.
I think it is abt the very same 30 min Setup-process.
I did not know that there is a difference in the 0000 or 0001 files.
Time wise I never paid attentiton too.
There may not be any real difference in the folder BUT having multiple installs may well cause CONFUSION for Windows itself and/or programs. And A LOT OF WASTED Space.
I have to do another setup anyway as the fatal error is back again.
Is this the same machine that won't boot to the floppy ? If it is you may well have other problems.
And if you do indeed have multiple installs it just might be the reason ( or part of ) the reason for the error. Windows just can't find it.
And if you can not get a boot to the floppy in order to get a good clean install you may well continue to have proplems.
I would suggest that you delete any Windows folders other than C:\Windows and see if you can get a good clean reinstall which you may well not get when booting from the HD.
I only have WIN98SE CDRom.
I will clean it and try to install the files mentioned by means of SFC.
Just suppose it does not work.
How to get the same files (from the other network PC) into
WINDOWS\System of this PC. At this moment it seems as if they are
not accepted > the crippled versions remain present)
to follow.
