Need a Win 98 Boot Up Disc!

[PCR]

MEB wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
|| MEB wrote:

....snip[
|| | Check the original KB query for additional related issues during
|| | install and other failures. Such as:
|| | http://support.microsoft.com/kb/136416/en-us - Windows does not
|| | start normally with bootgui=1 in msdos.sys - winboot.ini present
||
|| I'm looking at it now. Yes-- I knew that: When a Winboot.ini file
|| exists, it takes the the place of MSDOS.sys. That is just as cquirke
|| always said it would be!
|
| And winboot.sys over-rides io.sys, hence the issues involved with the
| temprary files and an already installed system, or in other
| circumstances.

Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot Partition
Record). That is how a partition knows how to start booting. Therefore,
the presence of Winboot.sys is very unlikely to cause it to override
IO.sys.

||
|| | --
|| | MEB
|| | ________
||
|| --
|| Thanks or Good Luck,
|| There may be humor in this post, and,
|| Naturally, you will not sue,
|| Should things get worse after this,
|| PCR
|| pcrrcp@netzero.net
||
||
|
| --
| MEB
| http://peoplescounsel.orgfree.com
| ________

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[MEB]

"PCR" <pcrrcp@netzero.net> wrote in message
news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
| MEB wrote:
| | "PCR" <pcrrcp@netzero.net> wrote in message
| | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
| || MEB wrote:
|
| ...snip[
| || | Check the original KB query for additional related issues during
| || | install and other failures. Such as:
| || | http://support.microsoft.com/kb/136416/en-us - Windows does not
| || | start normally with bootgui=1 in msdos.sys - winboot.ini present
| ||
| || I'm looking at it now. Yes-- I knew that: When a Winboot.ini file
| || exists, it takes the place of MSDOS.sys. That is just as cquirke
| || always said it would be!
| |
| | And winboot.sys over-rides io.sys, hence the issues involved with the
| | temporary files and an already installed system, or in other
| | circumstances.
|
| Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot Partition
| Record). That is how a partition knows how to start booting. Therefore,
| the presence of Winboot.sys is very unlikely to cause it to override
| IO.sys.

Perhaps that was a poor choice of words,,, think indicator . . . it ain't
necessarily hard coded IN Windows. You're thinking DOS, the original
discussion rambled off into a thread on Windows Setup.
SURELY you aren't attempting to start another DOS verses Windows
discussion.

Okay, let's see if we can end this part of the discussion. Using WinDiff -
the files [io.sys and winboot.sys] are identical. Using UltraEdit - the
files are the same.
BUT they aren't NAMED the same. Windows looks for winboot.sys to indicate
the setup is in progress or failed [still there? okay either the install
failed, cleanup failed, or a prior install failed]... I have already posted
several segments of io.sys which SHOWS checks for winboot.ini, some other
potential files like *.wos, *.w40, and guess what, it also shows checks for
io.sys [that would be itself unless named winboot.sys]. . . .

Ever check out the precopy cabs?
Not that it really matters much, but if you've got something like File
Investigator look at some of the setup files for Windoz .. . like
suwin.exe, and the infs in cab 2, might explain some stuff ..

BTW, winboot.sys is in precopy2.cab and base5.cab.

|
| ||
| || | --
| || | MEB
| || | ________
| ||
| || --
| || PCR
| | --
| | MEB
| | ________
|
| --
| Thanks or Good Luck,
| There may be humor in this post, and,
| Naturally, you will not sue,
| Should things get worse after this,
| PCR
| pcrrcp@netzero.net
|
|

--
MEB
http://peoplescounsel.orgfree.com
________

 

[PCR]

MEB wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
|| MEB wrote:
|| | "PCR" <pcrrcp@netzero.net> wrote in message
|| | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
|| || MEB wrote:
||
|| ...snip[
|| || | Check the original KB query for additional related issues
|| || | during install and other failures. Such as:
|| || | http://support.microsoft.com/kb/136416/en-us - Windows does not
|| || | start normally with bootgui=1 in msdos.sys - winboot.ini present
|| ||
|| || I'm looking at it now. Yes-- I knew that: When a Winboot.ini file
|| || exists, it takes the place of MSDOS.sys. That is just as cquirke
|| || always said it would be!
|| |
|| | And winboot.sys over-rides io.sys, hence the issues involved with
|| | the temporary files and an already installed system, or in other
|| | circumstances.
||
|| Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot Partition
|| Record). That is how a partition knows how to start booting.
|| Therefore, the presence of Winboot.sys is very unlikely to cause it
|| to override IO.sys.
|
| Perhaps that was a poor choice of words,,, think indicator . . . it
| ain't necessarily hard coded IN Windows. You're thinking DOS, the
| original discussion rambled off into a thread on Windows Setup.

You are right, things could be different during the running of Windows
Setup. Afterwards, for sure, the BPR (Boot Partition Record) will
contain the name "IO.sys". IO.sys will load during boot & eventually
will lead to the loading of Windows, if MSDOS.sys (or Winboot.ini) calls
for it. IO.sys, itself, is likely a big part of DOS.

| SURELY you aren't attempting to start another DOS verses Windows
| discussion.

No, no!

| Okay, let's see if we can end this part of the discussion. Using
| WinDiff - the files [io.sys and winboot.sys] are identical. Using
| UltraEdit - the files are the same.

Correct-- & just as FC did report.

| BUT they aren't NAMED the same. Windows looks for winboot.sys to
| indicate the setup is in progress or failed [still there? okay either
| the install failed, cleanup failed, or a prior install failed]... I
| have already posted several segments of io.sys which SHOWS checks for
| winboot.ini, some other potential files like *.wos, *.w40, and guess
| what, it also shows checks for io.sys [that would be itself unless
| named winboot.sys]. . . .

A good point. Sounds like it could be as you say. It might even be that
Winboot.sys is used to write code to the BPR.

| Ever check out the precopy cabs?
| Not that it really matters much, but if you've got something like
| File Investigator look at some of the setup files for Windoz .. .
| like suwin.exe, and the infs in cab 2, might explain some stuff ..
|
| BTW, winboot.sys is in precopy2.cab and base5.cab.

That is true, Winboot.sys is in both .cab's, which is unusual.

 

[Bill Blanton]

"PCR" <pcrrcp@netzero.net> wrote in message news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
> MEB wrote:
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
> || MEB wrote:
>
> ...snip[
> || | Check the original KB query for additional related issues during
> || | install and other failures. Such as:
> || | http://support.microsoft.com/kb/136416/en-us - Windows does not
> || | start normally with bootgui=1 in msdos.sys - winboot.ini present
> ||
> || I'm looking at it now. Yes-- I knew that: When a Winboot.ini file
> || exists, it takes the the place of MSDOS.sys. That is just as cquirke
> || always said it would be!
> |
> | And winboot.sys over-rides io.sys, hence the issues involved with the
> | temprary files and an already installed system, or in other
> | circumstances.
>
> Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot Partition
> Record). That is how a partition knows how to start booting. Therefore,
> the presence of Winboot.sys is very unlikely to cause it to override
> IO.sys.

The string WINBOOT SYS is also contained in the boot record code.
(in addition to IO SYS )

http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#DATA

I don't know for a fact, but It may be the boot code that looks for winboot.sys.

e.g.

If exists winboot.sys
then winboot.sys
else io.sys

 

[PCR]

Bill Blanton wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
|> MEB wrote:
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
|> || MEB wrote:
|>
|> ...snip[
|> || | Check the original KB query for additional related issues
|> || | during install and other failures. Such as:
|> || | http://support.microsoft.com/kb/136416/en-us - Windows does not
|> || | start normally with bootgui=1 in msdos.sys - winboot.ini present
|> ||
|> || I'm looking at it now. Yes-- I knew that: When a Winboot.ini file
|> || exists, it takes the the place of MSDOS.sys. That is just as
|> || cquirke always said it would be!
|> |
|> | And winboot.sys over-rides io.sys, hence the issues involved with
|> | the temprary files and an already installed system, or in other
|> | circumstances.
|>
|> Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot Partition
|> Record). That is how a partition knows how to start booting.
|> Therefore, the presence of Winboot.sys is very unlikely to cause it
|> to override IO.sys.
|
| The string WINBOOT SYS is also contained in the boot record code.
| (in addition to IO SYS )
|
| http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#DATA
|
| I don't know for a fact, but It may be the boot code that looks for
| winboot.sys.
|
| e.g.
|
| If exists winboot.sys
| then winboot.sys
| else io.sys

Yow. That didn't occur to me. Yep, that sounds like a possibility. It
doesn't sound to tough to test for that. I might just rename IO.sys to
Winboot.sys, create a phony IO.sys-- & see whether I can boot! What do
you think?

 

[Bill Blanton]

"PCR" <pcrrcp@netzero.net> wrote in message news:%23fvCjRSEIHA.1208@TK2MSFTNGP05.phx.gbl...
> Bill Blanton wrote:
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
> |> MEB wrote:
> |> | "PCR" <pcrrcp@netzero.net> wrote in message
> |> | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
> |> || MEB wrote:
> |>
> |> ...snip[
> |> || | Check the original KB query for additional related issues
> |> || | during install and other failures. Such as:
> |> || | http://support.microsoft.com/kb/136416/en-us - Windows does not
> |> || | start normally with bootgui=1 in msdos.sys - winboot.ini present
> |> ||
> |> || I'm looking at it now. Yes-- I knew that: When a Winboot.ini file
> |> || exists, it takes the the place of MSDOS.sys. That is just as
> |> || cquirke always said it would be!
> |> |
> |> | And winboot.sys over-rides io.sys, hence the issues involved with
> |> | the temprary files and an already installed system, or in other
> |> | circumstances.
> |>
> |> Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot Partition
> |> Record). That is how a partition knows how to start booting.
> |> Therefore, the presence of Winboot.sys is very unlikely to cause it
> |> to override IO.sys.
> |
> | The string WINBOOT SYS is also contained in the boot record code.
> | (in addition to IO SYS )
> |
> | http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#DATA
> |
> | I don't know for a fact, but It may be the boot code that looks for
> | winboot.sys.
> |
> | e.g.
> |
> | If exists winboot.sys
> | then winboot.sys
> | else io.sys
>
> Yow. That didn't occur to me. Yep, that sounds like a possibility. It
> doesn't sound to tough to test for that. I might just rename IO.sys to
> Winboot.sys, create a phony IO.sys-- & see whether I can boot! What do
> you think?

Sounds like a reasonable test to me.. -)

 

[PCR]

Bill Blanton wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23fvCjRSEIHA.1208@TK2MSFTNGP05.phx.gbl...
|> Bill Blanton wrote:
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
|> |> MEB wrote:
|> |> | "PCR" <pcrrcp@netzero.net> wrote in message
|> |> | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
|> |> || MEB wrote:
|> |>
|> |> ...snip[
|> |> || | Check the original KB query for additional related issues
|> |> || | during install and other failures. Such as:
|> |> || | http://support.microsoft.com/kb/136416/en-us - Windows does
|> |> || | not start normally with bootgui=1 in msdos.sys - winboot.ini
|> |> || | present
|> |> ||
|> |> || I'm looking at it now. Yes-- I knew that: When a Winboot.ini
|> |> || file exists, it takes the the place of MSDOS.sys. That is just
|> |> || as cquirke always said it would be!
|> |> |
|> |> | And winboot.sys over-rides io.sys, hence the issues involved
|> |> | with the temprary files and an already installed system, or in
|> |> | other circumstances.
|> |>
|> |> Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot
|> |> Partition Record). That is how a partition knows how to start
|> |> booting. Therefore, the presence of Winboot.sys is very unlikely
|> |> to cause it to override IO.sys.
|> |
|> | The string WINBOOT SYS is also contained in the boot record code.
|> | (in addition to IO SYS )
|> |
|> | http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#DATA
|> |
|> | I don't know for a fact, but It may be the boot code that looks for
|> | winboot.sys.
|> |
|> | e.g.
|> |
|> | If exists winboot.sys
|> | then winboot.sys
|> | else io.sys
|>
|> Yow. That didn't occur to me. Yep, that sounds like a possibility. It
|> doesn't sound to tough to test for that. I might just rename IO.sys
|> to Winboot.sys, create a phony IO.sys-- & see whether I can boot!
|> What do you think?
|
| Sounds like a reasonable test to me.. -)

It didn't work! I tried it twice (with & w/o a dummy IO.sys), & each
time Win98SE would not boot with Winboot.sys as a replacement...

Invalid System Disk
Replace the disk, & then press any key

It was important to have a Startup Diskette on hand, because the above
message came before the Windows Startup Menu (which makes sense).

SO... The mystery still is in effect as to why Winboot.sys exists in two
..cab's (PreCopy2.cab & Base5.cab) & each of them is identical to
IO.sys...

C:\>FC /b /c C:\IO.sys C:\Windows\Temp\Winboot.sys
Comparing files c:\IO.SYS and C:\Windows\Temp\Winboot.sys
FC: no differences encountered

...., but IO.sys, itself is in no .cab. Also, within Winboot.sys is the
name "IO.sys".

 

[Bill Blanton]

"PCR" <pcrrcp@netzero.net> wrote in message news:u%234skwcEIHA.3332@TK2MSFTNGP04.phx.gbl...
> Bill Blanton wrote:
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:%23fvCjRSEIHA.1208@TK2MSFTNGP05.phx.gbl...
> |> Bill Blanton wrote:
> |> | "PCR" <pcrrcp@netzero.net> wrote in message
> |> | news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
> |> |> MEB wrote:
> |> |> | "PCR" <pcrrcp@netzero.net> wrote in message
> |> |> | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
> |> |> || MEB wrote:
> |> |>
> |> |> ...snip[
> |> |> || | Check the original KB query for additional related issues
> |> |> || | during install and other failures. Such as:
> |> |> || | http://support.microsoft.com/kb/136416/en-us - Windows does
> |> |> || | not start normally with bootgui=1 in msdos.sys - winboot.ini
> |> |> || | present
> |> |> ||
> |> |> || I'm looking at it now. Yes-- I knew that: When a Winboot.ini
> |> |> || file exists, it takes the the place of MSDOS.sys. That is just
> |> |> || as cquirke always said it would be!
> |> |> |
> |> |> | And winboot.sys over-rides io.sys, hence the issues involved
> |> |> | with the temprary files and an already installed system, or in
> |> |> | other circumstances.
> |> |>
> |> |> Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot
> |> |> Partition Record). That is how a partition knows how to start
> |> |> booting. Therefore, the presence of Winboot.sys is very unlikely
> |> |> to cause it to override IO.sys.
> |> |
> |> | The string WINBOOT SYS is also contained in the boot record code.
> |> | (in addition to IO SYS )
> |> |
> |> | http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#DATA
> |> |
> |> | I don't know for a fact, but It may be the boot code that looks for
> |> | winboot.sys.
> |> |
> |> | e.g.
> |> |
> |> | If exists winboot.sys
> |> | then winboot.sys
> |> | else io.sys
> |>
> |> Yow. That didn't occur to me. Yep, that sounds like a possibility. It
> |> doesn't sound to tough to test for that. I might just rename IO.sys
> |> to Winboot.sys, create a phony IO.sys-- & see whether I can boot!
> |> What do you think?
> |
> | Sounds like a reasonable test to me.. -)
>
> It didn't work! I tried it twice (with & w/o a dummy IO.sys), & each
> time Win98SE would not boot with Winboot.sys as a replacement...
>
> Invalid System Disk
> Replace the disk, & then press any key
>
> It was important to have a Startup Diskette on hand, because the above
> message came before the Windows Startup Menu (which makes sense).

Yep. And a good thing you know your DOS..


> SO... The mystery still is in effect as to why Winboot.sys exists in two
> .cab's (PreCopy2.cab & Base5.cab) & each of them is identical to
> IO.sys...

...and why the string is in the boot sector. For that matter why is the
string MSDOS SYS in there?


> C:\>FC /b /c C:\IO.sys C:\Windows\Temp\Winboot.sys
> Comparing files c:\IO.SYS and C:\Windows\Temp\Winboot.sys
> FC: no differences encountered
>
> ..., but IO.sys, itself is in no .cab. Also, within Winboot.sys is the
> name "IO.sys".

There might be a clue here, but I don't have time to digest it right now.
I need to get ready to watch the BoSox's big comeback!

 

[BD]

"Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message
news:%23P0IJDeEIHA.4196@TK2MSFTNGP04.phx.gbl...
>
<snip>
> I need to get ready to watch the BoSox's big comeback!
>
Dream on Bill. Dream on. <g>

 

[PCR]

Bill Blanton wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:u%234skwcEIHA.3332@TK2MSFTNGP04.phx.gbl...

....snip
| There might be a clue here, but I don't have time to digest it right
| now.
| I need to get ready to watch the BoSox's big comeback!

I have to go too to watch Smallville. But I want Cleveland to win-- JUST
to justify the horrible Yankee loss! Then, I want Colorado to crush
them!

I'll get to the rest later or tomorrow.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[Bill Blanton]

"BD" <JustMe@nothome.net> wrote in message news:eJJPPNeEIHA.3400@TK2MSFTNGP03.phx.gbl...
> "Bill Blanton" <bblanton@REMOVEmagicnet.net> wrote in message news:%23P0IJDeEIHA.4196@TK2MSFTNGP04.phx.gbl...
>>
> <snip>
>> I need to get ready to watch the BoSox's big comeback!
>>
> Dream on Bill. Dream on. <g>

Actually George, I've been a Cubs fan all my life... The Red Sox are my
backup heartbreak -)

 

[Bill Blanton]

"PCR" <pcrrcp@netzero.net> wrote in message news:e1CIBZeEIHA.5976@TK2MSFTNGP02.phx.gbl...
> Bill Blanton wrote:
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:u%234skwcEIHA.3332@TK2MSFTNGP04.phx.gbl...
>
> ...snip
> | There might be a clue here, but I don't have time to digest it right
> | now.
> | I need to get ready to watch the BoSox's big comeback!
>
> I have to go too to watch Smallville. But I want Cleveland to win-- JUST
> to justify the horrible Yankee loss! Then, I want Colorado to crush
> them!
>

I don't think Colorado's that good.. though if they can extend their streak
four more games... -/

 

[PCR]

Bill Blanton wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:e1CIBZeEIHA.5976@TK2MSFTNGP02.phx.gbl...
|> Bill Blanton wrote:
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:u%234skwcEIHA.3332@TK2MSFTNGP04.phx.gbl...
|>
|> ...snip
|> | There might be a clue here, but I don't have time to digest it
|> | right now.
|> | I need to get ready to watch the BoSox's big comeback!
|>
|> I have to go too to watch Smallville. But I want Cleveland to win--
|> JUST to justify the horrible Yankee loss! Then, I want Colorado to
|> crush them!
|>
|
| I don't think Colorado's that good.. though if they can extend their
| streak
| four more games... -/

It looks to me they've become an unstoppable force the way they've won
21 of 22 games or something incredible like that. BUT, now that
Cleveland has shown it really was good (& it wasn't just that the
Yankees stunk)-- I'll settle for Boston coming back to beat them 3 in a
row!

I've sworn not to watch the Yanks next year for this! (But I swore it
last year too.)

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[PCR]

Bill Blanton wrote:
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:u%234skwcEIHA.3332@TK2MSFTNGP04.phx.gbl...
|> Bill Blanton wrote:
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:%23fvCjRSEIHA.1208@TK2MSFTNGP05.phx.gbl...
|> |> Bill Blanton wrote:
|> |> | "PCR" <pcrrcp@netzero.net> wrote in message
|> |> | news:%23LW4q8DEIHA.5160@TK2MSFTNGP05.phx.gbl...
|> |> |> MEB wrote:
|> |> |> | "PCR" <pcrrcp@netzero.net> wrote in message
|> |> |> | news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...
|> |> |> || MEB wrote:
|> |> |>
|> |> |> ...snip[
|> |> |> || | Check the original KB query for additional related issues
|> |> |> || | during install and other failures. Such as:
|> |> |> || | http://support.microsoft.com/kb/136416/en-us - Windows
|> |> |> || | does not start normally with bootgui=1 in msdos.sys -
|> |> |> || | winboot.ini present
|> |> |> ||
|> |> |> || I'm looking at it now. Yes-- I knew that: When a Winboot.ini
|> |> |> || file exists, it takes the the place of MSDOS.sys. That is
|> |> |> || just as cquirke always said it would be!
|> |> |> |
|> |> |> | And winboot.sys over-rides io.sys, hence the issues involved
|> |> |> | with the temprary files and an already installed system, or
|> |> |> | in other circumstances.
|> |> |>
|> |> |> Wait a minute-- no! IO.sys is hard-coded into the BPR (Boot
|> |> |> Partition Record). That is how a partition knows how to start
|> |> |> booting. Therefore, the presence of Winboot.sys is very
|> |> |> unlikely to cause it to override IO.sys.
|> |> |
|> |> | The string WINBOOT SYS is also contained in the boot record
|> |> | code. (in addition to IO SYS )
|> |> |
|> |> | http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#DATA
|> |> |
|> |> | I don't know for a fact, but It may be the boot code that looks
|> |> | for winboot.sys.
|> |> |
|> |> | e.g.
|> |> |
|> |> | If exists winboot.sys
|> |> | then winboot.sys
|> |> | else io.sys
|> |>
|> |> Yow. That didn't occur to me. Yep, that sounds like a
|> |> possibility. It doesn't sound to tough to test for that. I might
|> |> just rename IO.sys to Winboot.sys, create a phony IO.sys-- & see
|> |> whether I can boot! What do you think?
|> |
|> | Sounds like a reasonable test to me.. -)
|>
|> It didn't work! I tried it twice (with & w/o a dummy IO.sys), & each
|> time Win98SE would not boot with Winboot.sys as a replacement...
|>
|> Invalid System Disk
|> Replace the disk, & then press any key
|>
|> It was important to have a Startup Diskette on hand, because the
|> above message came before the Windows Startup Menu (which makes
|> sense).
|
| Yep. And a good thing you know your DOS..
|
|
|> SO... The mystery still is in effect as to why Winboot.sys exists in
|> two .cab's (PreCopy2.cab & Base5.cab) & each of them is identical to
|> IO.sys...
|
| ..and why the string is in the boot sector. For that matter why is the
| string MSDOS SYS in there?

I'm trying, but can't come up with an answer, except... maybe... can it
be for backward compatibility to some older OS that needed those names
in there? Or, it is just a vestige of what was there even though it
never will be used again?

I'll do a little Googling for it & get back if I find something.

|> C:\>FC /b /c C:\IO.sys C:\Windows\Temp\Winboot.sys
|> Comparing files c:\IO.SYS and C:\Windows\Temp\Winboot.sys
|> FC: no differences encountered
|>
|> ..., but IO.sys, itself is in no .cab. Also, within Winboot.sys is
|> the name "IO.sys".
|
| There might be a clue here, but I don't have time to digest it right
| now.
| I need to get ready to watch the BoSox's big comeback!

Looks like they are winning 2 to 1 in the top of the 5th with a man on
base!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net