Jump to content

Patched IO.SYS for 9x/ME


jaclaz

Recommended Posts

I have two IO.SYS files on the system, one in the root of C:\ which is dated 23/04/99 22.22, which I assume is the 98SE original version.

I also have a copy in my Emergency Boot Disk folder, which is dated 01/12/01 09.37.

The two files are not the same as they are slightly different sizes.

It just may be correct. The original file IO.SYS with Windows 98SE Polish version has a volume of 222,390 bytes, while the volume of the IO.SYS file after you apply hotfix 311561 is 222,670 bytes - in both cases is good.

Sometimes (read often) reality becomes a myth, the fact that traditionally an OS behaves in a given way makes people assume that the new version will behave the same (actually this happens often) but some things "remain" and little by little it becomes a myth.

Of course I agree with the above finding.

Link to comment
Share on other sites


And "bit rot"... bit rot is the informatics equivalent to material's fatigue, or, in other words, bit rot is the cumulative collection of small non fatal registry errors and file corruptions that can happen on a system over a really long time. To fight it, using periodical images to fall back to, whenever something perceptible is noticed, is part of the game, but the problem are those small damages that don't lead to any symptoms, until activated by some other such "harmless-in-itself" damage. My current main Win 98SE was originally installed back in 2001, and never reinstalled so far, so I do think I'm fighting bit rot effectively, but one can never really know for sure.

Yes, that's the best theory so far!

Joe.

Link to comment
Share on other sites

Well, I finally updated IO.SYS on my desktop PC using the same procedure (from DOS) without loading the 311561USA8.EXE update beforehand and everything seems to work fine, at least so far. I didn't get the immediate Windows registry error that I did on my laptop for some reason, which is quite puzzling. I understand the "bit rot" concept but I really don't think that's the situation with my laptop. I routinely run System File Checker, registry scans, and numerous other system utilities to ensure things are in order. Of course, that's no guarantee but I feel quite confident about the OS integrity overall.

I was hoping the updated IO.SYS would solve the annoying bug in Windows Explorer of having multiple entries for discs mounted in my CD/DVD drives but that's not the case, as those multiple entries still occur. And yes, the original Win98SE IO.SYS has a file size of 222,390 bytes while the updated IO.SYS installed by the 311561USA8.EXE update is 222,670 bytes.

Link to comment
Share on other sites

I was hoping the updated IO.SYS would solve the annoying bug in Windows Explorer of having multiple entries for discs mounted in my CD/DVD drives but that's not the case, as those multiple entries still occur. And yes, the original Win98SE IO.SYS has a file size of 222,390 bytes while the updated IO.SYS installed by the 311561USA8.EXE update is 222,670 bytes.

This is an unrelated problem. Try disabling any DOS CD/DVD Drivers in your CONFIG.SYS File.

Link to comment
Share on other sites

About R.Loew PATCHPAR.EXE (and the other patches), for greater clarity:

I do not know if I understood correctly, but this (R.Loew PATCHPAR.EXE)

1) is the latest patch and then all the other patches (by jds , Saunderson, the first by R.Loew by hex editing

) have to be applied and then lastly this one too,

or

2) is equivalent to the previous R.Loew by hex editing,

or

3) is an all inclusive cumulative patch and I should apply only this one (bugfix for all problems)?

Excuse me if I am misundestood something, but i'm beginning to have a headache!

Thank you all.

Link to comment
Share on other sites

About R.Loew PATCHPAR.EXE (and the other patches), for greater clarity:

I do not know if I understood correctly, but this (R.Loew PATCHPAR.EXE)

1) is the latest patch and then all the other patches (by jds , Saunderson, the first by R.Loew by hex editing Quote of the post#72 by rloew on 04 December 2011, 06:28 PM : This Patch is "complete") have to be applied and then lastly this one too,

or

2) is equivalent to the previous R.Loew by hex editing,

or

3) is an all inclusive cumulative patch and I should apply only this one (bugfix for all problems)?

Excuse me if I am misundestood something, but i'm beginning to have a headache!

Thank you all.

The Patch is complete. You do not need any other Patch. It is recommended that you use the Updated IO.SYS from 311561USA8.EXE as your starting point.

It is not truly cumulative as I created a single Patch that solves the issues dealt with by all of the prior patches, so the earlier ones are not present.

It is the same as the Hex Editing instructions for the 311561USA8.EXE version only. It will insert slightly different Patches into the original IO.SYS and possibly localized versions as it uses an adaptive algorithm.

My previously posted Patch, not the Hex Edit, is obsolete and should not be used.

Link to comment
Share on other sites

OK, now I'm a little confused. Which patch is obsolete?

Here is RLoew's complete patch, as a patch pattern, so that those interested may create the patched IO.SYS.

patch -p winboot.98s IO_RRL.PAT IO.SYS

Use the following commands to perform the Patch.

C:

CD \

REN IO.SYS IO.OLD

PATCHPAR IO.OLD IO.SYS

Link to comment
Share on other sites

Rloew's original patch, linked to from my post #49 in this thread, required also jds' version of the phellum patch. The combined patches should be aplied to the Q311561 version of IO.SYS. These combined patches were superseded by RLoew's complete patch, released in his post #67, then converted to a patch pattern to be used with the IO.SYS from Q311561, in my post #80, and then presented as an adaptive standalone patcher by RLoew himself, in post #98

Link to comment
Share on other sites

Just wanted to report that I patched my IO.SYS using the MS patch and then rloew's latest patch, and no problems.

I was a bit apprehensive as the last time i tried anything like that all my drive letters got scrambled!

http://www.msfn.org/board/topic/118119-patched-iosys-for-98se-and-me/page__view__findpost__p__768159

Fortunately all OK this time, I guess I'll never know what happened before!

:)

Link to comment
Share on other sites

Is it possible to make the patch for Win ME, too? Till now I've hidden phantom drives. :whistle:

Rloew wrote a decompressor for WinMe's IO.SYS: http://rloew1.no-ip.com/prerel.htm

So I guess it should be possible to make a patch for it without too much difficulty.

I've never seen phantom drives on my ME system, perhaps because, since I encountered those ugly things in my distant win95 days, I always zero a drive before (re)partitioning it (with Paragon Partition Manager 2000 if that's relevant).

Link to comment
Share on other sites

Is it possible to make the patch for Win ME, too? Till now I've hidden phantom drives.  :whistle:

I have updated my PATCHPAR Program to Patch the Unpacked Windows ME IO.SYS as well. You will need to get the Unpacker from my Website.

Let me know if it solves your problem.

Link to comment
Share on other sites

Is it possible to make the patch for Win ME, too?...

I have updated my PATCHPAR Program to Patch the Unpacked Windows ME IO.SYS as well....

For completeness sake, is it possible to get these bugfixes applied to the Windows 95 IO.SYS from Q185301 KB Article HotFix?

(I believe that's the last official version for 95, but I'm not at my usual "project machine" so I can't check right now.)

Link to comment
Share on other sites

Is it possible to make the patch for Win ME, too?...

I have updated my PATCHPAR Program to Patch the Unpacked Windows ME IO.SYS as well....

For completeness sake, is it possible to get these bugfixes applied to the Windows 95 IO.SYS from Q185301 KB Article HotFix?

(I believe that's the last official version for 95, but I'm not at my usual "project machine" so I can't check right now.)

It appears to work for both of the Hotfix files as well.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...