Since the other IO.SYS post is further down and went *way off* how I expected it to...plus the fact that I have more to say...I'll start a new post.

IO.SYS from Win9x, yes, is 220k...which compared to todays drives *is* awefully small. But when you can save around 100k on a bootdisk...that's a *lot* more files...for TechW0rm this would be unbelievably useful.

Anyway, as for my site...it's not exactly on stable ground. Verizon screwed over the owners of jason-n3xt...they offered them DSL speeds they didn't have...so they're going to move to another DSL provider eventually...at 1.1mbps (wohoo).

- W0rm
- http://jason-n3xt.org/dos

I have never tried to remove the logo from io.sys but I remember my brother saying something about it a long time ago and how he did not find the data in there.

I never figured why it was in there when they use to put logo.sys in the root directory also?

the only thing I can think of to help is that logo.sys was an RLE file and even if you cannot match the file byte-by-byte there must be some part of io.sys which resembles some RLE data even if it's in chunks and has no header data.

Hi W0rm. I was able to find and delete the logo a couple of years ago using a decompiler only to discover that IO.sys does a self-test and returns an error:
!L=unpacked file is corrupted
when recompiled. b---tards. Even when you fill with //comments// it does a byte length test again and guess what? There are null characters they inserted so the length can never match. That was quite the weekend. I thought I had them beat for a couple of hours there.

HOPEFULLY you made a mistake...I'm prayin' this isn't the end! heh...but DOS 8 has theirs compressed...strange :/ - can you at least give me some addresses and information on where you found it?
- W0rm
- http://jason-n3xt.org/dos

If I recall correctly, the logo is 47 or 49 KB. When you decompile the file it is exploded into ascii text and when you compile it it is compressed into hex code. That's why it's so big. Also, that's why you get the:
!L=unpacked file is corrupted
error when the byte length isn't right when you compile it.