Need a Win 98 Boot Up Disc!

http://support.microsoft.com/kb/q118579/

October 9, 2007

Re: Need a Win 98 Boot Up Disc!

Lil' Dave wrote:

| "Jim.Flack" <a-jflack@microsoft.com> wrote in message

| news:F783C36D-5CC1-43DD-9814-5D0160FE2A7E@microsoft.com...

|> Help! I'm getting the notorious "Type in the name of the Command

|> Interpretor"

|> error message and it appears that my HD is missing the Comman.com

|> (and maybe

|> other files) so that my laptop won't boot up. Can anyone send me a

|> Windows 98

|> boot up disk?

|>

|> I would hate to junk this laptop. It's not the greatest but it does

|> have a lot of PM type software on it. Email me at

|> jim.flack@gmail.com. Thanks!

|

| Just some add-ons to the comments already made.

|

| You may get a message that command.com is missing, but may find later

| its there and may be identical to the command com on your boot

| diskette.

|

| When doing sys c: when booted from the boot floppy diskette

| (sys.com), the msdos.sys is incorrect for booting windows

| automatically. It may only take you to the command prompt after the

| sys.com procedure. If sys.com is not present and the boot diskette,

| simply copy it from your C: drive to the floppy.

It is true the MSDOS.sys on the Startup Diskette is inadequate to boot

to Windows. However, SYS won't copy it to C:\-- if one already exists on

C:\. It will do whatever else it needs to do, though.

Here is mine, in case Flack has lost his, as it appears on C:\...

;..........START........... <<<You may remove this line.

[Paths]

WinDir=c:\windows

WinBootDir=c:\windows

HostWinBootDrv=c

[Options]

AutoScan=1

BootMenu=1 ;Per Win98 Secrets

BootMenuDelay=10

Dblspace=0 ;Per Win98

Drvspace=0 ; Secrets

DoubleBuffer=1

Logo=0

Network=0

WinVer=4.10.2222

;

;The following lines are required for compatibility with other programs.

;Do not remove them (MSDOS.SYS needs to be >1024 bytes).

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxg

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxh

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxi

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxl

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxm

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxn

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxo

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxp

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxq

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxr

;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxs

;..............END........ <<<You may remove this line.

NOTES:

(1) If you use CVFs (Compressed Volume Files), do not include Dblspace=0

& Drvspace=0.

(2) Do not include Network=0, if you connect to a Network.

(3) Logo=0 suppresses the Windows logo at boot.

(4) Finally, is you are First Edition, then use... WinVer=4.10.1998.

Contents of the Windows Msdos.sys File

| Let the group know any subsequent problems.

| Dave

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

http://support.microsoft.com/kb/178947/en-us

October 12, 2007

Re: Need a Win 98 Boot Up Disc!

"PCR" <pcrrcp@netzero.net> wrote in message

news:eijdyGsCIHA.3916@TK2MSFTNGP02.phx.gbl...

> Lil' Dave wrote:

> | "Jim.Flack" <a-jflack@microsoft.com> wrote in message

> | news:F783C36D-5CC1-43DD-9814-5D0160FE2A7E@microsoft.com...

> |> Help! I'm getting the notorious "Type in the name of the Command

> |> Interpretor"

> |> error message and it appears that my HD is missing the Comman.com

> |> (and maybe

> |> other files) so that my laptop won't boot up. Can anyone send me a

> |> Windows 98

> |> boot up disk?

> |>

> |> I would hate to junk this laptop. It's not the greatest but it does

> |> have a lot of PM type software on it. Email me at

> |> jim.flack@gmail.com. Thanks!

> |

> | Just some add-ons to the comments already made.

> |

> | You may get a message that command.com is missing, but may find later

> | its there and may be identical to the command com on your boot

> | diskette.

> |

> | When doing sys c: when booted from the boot floppy diskette

> | (sys.com), the msdos.sys is incorrect for booting windows

> | automatically. It may only take you to the command prompt after the

> | sys.com procedure. If sys.com is not present and the boot diskette,

> | simply copy it from your C: drive to the floppy.

>

> It is true the MSDOS.sys on the Startup Diskette is inadequate to boot

> to Windows. However, SYS won't copy it to C:\-- if one already exists on

> C:\. It will do whatever else it needs to do, though.

You are mistaken. Sys.com is unconditional.

Sys.com copies from the original boot media the following:

msdos.sys

command.com

io.sys

The 4th file, I won't talk about regarding drive compression. Not a factor

in this thread.

Sys.com also updates the partition table as to the location of the initial

boot file. Msdos.sys is not the initial boot file. Copying an undamaged,

unaltered msdos.sys on the C: root drive to another folder, then copying

back to the root drive after effecting sys.com will put you back to a

version that will boot to windows.

Dave

October 13, 2007

Re: Need a Win 98 Boot Up Disc!

Lil' Dave wrote:

| "PCR" <pcrrcp@netzero.net> wrote in message

| news:eijdyGsCIHA.3916@TK2MSFTNGP02.phx.gbl...

|> Lil' Dave wrote:

|> | "Jim.Flack" <a-jflack@microsoft.com> wrote in message

|> | news:F783C36D-5CC1-43DD-9814-5D0160FE2A7E@microsoft.com...

|> |> Help! I'm getting the notorious "Type in the name of the Command

|> |> Interpretor"

|> |> error message and it appears that my HD is missing the Comman.com

|> |> (and maybe

|> |> other files) so that my laptop won't boot up. Can anyone send me a

|> |> Windows 98

|> |> boot up disk?

|> |>

|> |> I would hate to junk this laptop. It's not the greatest but it

|> |> does have a lot of PM type software on it. Email me at

|> |> jim.flack@gmail.com. Thanks!

|> |

|> | Just some add-ons to the comments already made.

|> |

|> | You may get a message that command.com is missing, but may find

|> | later its there and may be identical to the command com on your

|> | boot diskette.

|> |

|> | When doing sys c: when booted from the boot floppy diskette

|> | (sys.com), the msdos.sys is incorrect for booting windows

|> | automatically. It may only take you to the command prompt after

|> | the sys.com procedure. If sys.com is not present and the boot

|> | diskette, simply copy it from your C: drive to the floppy.

|>

|> It is true the MSDOS.sys on the Startup Diskette is inadequate to

|> boot to Windows. However, SYS won't copy it to C:\-- if one already

|> exists on C:\. It will do whatever else it needs to do, though.

|

| You are mistaken. Sys.com is unconditional.

| Sys.com copies from the original boot media the following:

| msdos.sys

| command.com

| io.sys

| The 4th file, I won't talk about regarding drive compression. Not a

| factor in this thread.

| Sys.com also updates the partition table as to the location of the

| initial boot file. Msdos.sys is not the initial boot file. Copying

| an undamaged, unaltered msdos.sys on the C: root drive to another

| folder, then copying back to the root drive after effecting sys.com

| will put you back to a version that will boot to windows.

No-- it was written up that way in an article, which MEB may once have

posted here. But I can't find it! STILL, it makes no sense that SYS run

from a Startup Diskette would wipe MSDOS.sys-- & prevent a boot to

Windows. Why would it be mentioned in its ReadMe to be a cure for the

inability to boot to Windows , then...?...

......Quote the Startup Diskette ReadMe........

Setup Fails and the Computer Will Not Start

-------------------------------------------

There are a few common reasons why Windows 98

Setup may fail to complete successfully. The following

section explains what you can do to recover from these

situations. For more information on other Setup problems,

see the Setup.txt file in the Win98 folder of your

Windows 98 CD or Setup Disk #1.

If you encounter any of these error messages while

running Setup:

* Invalid System Disk

* Incorrect MS-DOS Version

* Missing or Corrupted Command.com

* Compression Driver errors

It is likely that your computer's startup drive may

need updated system files. You can use the SYS command

to copy the needed files to your computer.

NOTE: If you are currently loading compression software,

you will need to know your host drive letter. This is

typically H. If you are not loading any compression

software, then you will need to SYS your C drive.

>>>To use the SYS command to copy system files to your

computer:

1. Restart your computer using the Windows 98 Startup

Disk, select option 2 on the Startup menu, and then

press ENTER.

2. At the A:\ prompt, type: SYS X: (where X is your

Host or Startup drive).

3. If the procedure is successful, a "System transferred"

message appears. If it is not successful, check to be

sure you are typing the correct drive letter for your

Host Drive.

IMPORTANT: If you have installed software that came with

your hard drive, be sure to read the documentation that

describes how to start your computer using a floppy disk.

........EOQ..............

Here is another article, speaking of why the Startup Diskette doesn't

have a complete MSDOS.sys...

Err Msg: Registry File Was Not Found. Registry Services May...

.......Quote..................

MORE INFORMATION

The Msdos.sys file is a text file located in the root folder. It

contains a [Paths] section that lists the locations of other Windows 98

files (such as the registry). When you create a Windows 98 Startup disk,

the Msdos.sys file on the Startup disk contains only the following line:

;W98ebd

Because the Startup disk contains only this line, you can use the

Startup disk to start most computers and access a command prompt, but

you cannot start Windows 98 because Windows cannot locate the Ifshlp.sys

file or the registry. If you copy the Msdos.sys file from your hard disk

to the Windows 98 Startup disk, you may not be able to use the Startup

disk to start Windows 98 on another computer. This can occur if Windows

is installed in a different folder or on a different logical drive than

the computer from which the Msdos.sys file is copied. However, you can

still use the Startup disk to start another computer and access the

command prompt by pressing and holding down the CTRL key when your

computer starts, and then choosing Safe Mode Command Prompt Only from

the Startup menu.

.......EOQ.....................

| Dave

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

| http://support.microsoft.com/kb/178947/en-us

October 13, 2007

Re: Need a Win 98 Boot Up Disc!

"PCR" <pcrrcp@netzero.net> wrote in message

news:OIloS6SDIHA.536@TK2MSFTNGP06.phx.gbl...

| Lil' Dave wrote:

| | "PCR" <pcrrcp@netzero.net> wrote in message

| | news:eijdyGsCIHA.3916@TK2MSFTNGP02.phx.gbl...

| |> Lil' Dave wrote:

| |> | "Jim.Flack" <a-jflack@microsoft.com> wrote in message

| |> | news:F783C36D-5CC1-43DD-9814-5D0160FE2A7E@microsoft.com...

| |> |> Help! I'm getting the notorious "Type in the name of the Command

| |> |> Interpretor"

| |> |> error message and it appears that my HD is missing the Comman.com

| |> |> (and maybe

| |> |> other files) so that my laptop won't boot up. Can anyone send me a

| |> |> Windows 98

| |> |> boot up disk?

| |> |>

| |> |> I would hate to junk this laptop. It's not the greatest but it

| |> |> does have a lot of PM type software on it. Email me at

| |> |> jim.flack@gmail.com. Thanks!

| |> |

| |> | Just some add-ons to the comments already made.

| |> |

| |> | You may get a message that command.com is missing, but may find

| |> | later its there and may be identical to the command com on your

| |> | boot diskette.

| |> |

| |> | When doing sys c: when booted from the boot floppy diskette

| |> | (sys.com), the msdos.sys is incorrect for booting windows

| |> | automatically. It may only take you to the command prompt after

| |> | the sys.com procedure. If sys.com is not present and the boot

| |> | diskette, simply copy it from your C: drive to the floppy.

| |>

| |> It is true the MSDOS.sys on the Startup Diskette is inadequate to

| |> boot to Windows. However, SYS won't copy it to C:\-- if one already

| |> exists on C:\. It will do whatever else it needs to do, though.

| |

| | You are mistaken. Sys.com is unconditional.

| | Sys.com copies from the original boot media the following:

| | msdos.sys

| | command.com

| | io.sys

| | The 4th file, I won't talk about regarding drive compression. Not a

| | factor in this thread.

| | Sys.com also updates the partition table as to the location of the

| | initial boot file. Msdos.sys is not the initial boot file. Copying

| | an undamaged, unaltered msdos.sys on the C: root drive to another

| | folder, then copying back to the root drive after effecting sys.com

| | will put you back to a version that will boot to windows.

|

| No-- it was written up that way in an article, which MEB may once have

| posted here. But I can't find it! STILL, it makes no sense that SYS run

| from a Startup Diskette would wipe MSDOS.sys-- & prevent a boot to

| Windows. Why would it be mentioned in its ReadMe to be a cure for the

| inability to boot to Windows , then...?...

|

| .....Quote the Startup Diskette ReadMe........

| Setup Fails and the Computer Will Not Start

| -------------------------------------------

| There are a few common reasons why Windows 98

| Setup may fail to complete successfully. The following

| section explains what you can do to recover from these

| situations. For more information on other Setup problems,

| see the Setup.txt file in the Win98 folder of your

| Windows 98 CD or Setup Disk #1.

|

| If you encounter any of these error messages while

| running Setup:

|

| * Invalid System Disk

| * Incorrect MS-DOS Version

| * Missing or Corrupted Command.com

| * Compression Driver errors

|

| It is likely that your computer's startup drive may

| need updated system files. You can use the SYS command

| to copy the needed files to your computer.

|

| NOTE: If you are currently loading compression software,

| you will need to know your host drive letter. This is

| typically H. If you are not loading any compression

| software, then you will need to SYS your C drive.

|

| >>>To use the SYS command to copy system files to your

| computer:

|

| 1. Restart your computer using the Windows 98 Startup

| Disk, select option 2 on the Startup menu, and then

| press ENTER.

|

| 2. At the A:\ prompt, type: SYS X: (where X is your

| Host or Startup drive).

|

| 3. If the procedure is successful, a "System transferred"

| message appears. If it is not successful, check to be

| sure you are typing the correct drive letter for your

| Host Drive.

|

| IMPORTANT: If you have installed software that came with

| your hard drive, be sure to read the documentation that

| describes how to start your computer using a floppy disk.

| .......EOQ..............

|

| Here is another article, speaking of why the Startup Diskette doesn't

| have a complete MSDOS.sys...

| Err Msg: Registry File Was Not Found. Registry Services May...

| ......Quote..................

| MORE INFORMATION

| The Msdos.sys file is a text file located in the root folder. It

| contains a [Paths] section that lists the locations of other Windows 98

| files (such as the registry). When you create a Windows 98 Startup disk,

| the Msdos.sys file on the Startup disk contains only the following line:

|

| ;W98ebd

|

| Because the Startup disk contains only this line, you can use the

| Startup disk to start most computers and access a command prompt, but

| you cannot start Windows 98 because Windows cannot locate the Ifshlp.sys

| file or the registry. If you copy the Msdos.sys file from your hard disk

| to the Windows 98 Startup disk, you may not be able to use the Startup

| disk to start Windows 98 on another computer. This can occur if Windows

| is installed in a different folder or on a different logical drive than

| the computer from which the Msdos.sys file is copied. However, you can

| still use the Startup disk to start another computer and access the

| command prompt by pressing and holding down the CTRL key when your

| computer starts, and then choosing Safe Mode Command Prompt Only from

| the Startup menu.

| ......EOQ.....................

|

| | Dave

|

| --

| Thanks or Good Luck,

| There may be humor in this post, and,

| Naturally, you will not sue,

| Should things get worse after this,

| PCR

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

|

Hmm, my name mentioned and something I might/supposedly have posted ,,,

let's look at some information if we are intending to discuss this [and

before I start posting contents of files and my thoughts]:

http://mirror.href.com/thestarman/asm/mbr/SYSDIFFS.txt

http://mirror.href.com/thestarman/asm/mbr/SYSCOM.htm

XP - DOS

http://www.msfn.org/board/lofiversion/index.php/t87269.html

"Can I create a DOS only (7.10) machine from a Windows 98 system or CD?"

http://www.d-a-l.com/articles/library/35.html

Personal Computers: Disk Partitions and Formatting

http://www.windowsitlibrary.com/Content/175/07/1.html

http://www.windowsitlibrary.com/Content/175/07/2.html

http://www.windowsitlibrary.com/Content/175/07/3.html

Create DOS boot from Winpe using diskpart & format /fs:fat

http://www.911cd.net/forums//lofiversion/index.php?t16869.html

see links in posts

http://www.mdgx.com/msdos.htm

http://support.microsoft.com/default.aspx?kbid=314057

MSDOS.SYS

http://support.microsoft.com/kb/118579

http://support.microsoft.com/kb/129998

http://www.mdgx.com/msdos.htm

http://www.pchell.com/software/msdos-sys.shtml

http://www.multiboot.ru/msdos8.htm

ME - DOS

http://www.geocities.com/mfd4life_2000/

--

MEB

|| http://support.microsoft.com/kb/178947/en-us

________

October 13, 2007

Re: Need a Win 98 Boot Up Disc!

MEB wrote:

| "PCR" <pcrrcp@netzero.net> wrote in message

| news:OIloS6SDIHA.536@TK2MSFTNGP06.phx.gbl...

|| Lil' Dave wrote:

....snip

|| |> | When doing sys c: when booted from the boot floppy diskette

|| |> | (sys.com), the msdos.sys is incorrect for booting windows

|| |> | automatically. It may only take you to the command prompt after

|| |> | the sys.com procedure. If sys.com is not present and the boot

|| |> | diskette, simply copy it from your C: drive to the floppy.

|| |>

|| |> It is true the MSDOS.sys on the Startup Diskette is inadequate to

|| |> boot to Windows. However, SYS won't copy it to C:\-- if one

|| |> already exists on C:\. It will do whatever else it needs to do,

|| |> though.

|| |

|| | You are mistaken. Sys.com is unconditional.

|| | Sys.com copies from the original boot media the following:

|| | msdos.sys

|| | command.com

|| | io.sys

|| | The 4th file, I won't talk about regarding drive compression. Not

|| | a factor in this thread.

|| | Sys.com also updates the partition table as to the location of the

|| | initial boot file. Msdos.sys is not the initial boot file.

|| | Copying an undamaged, unaltered msdos.sys on the C: root drive to

|| | another folder, then copying back to the root drive after

|| | effecting sys.com will put you back to a version that will boot to

|| | windows.

||

|| No-- it was written up that way in an article, which MEB may once

|| have posted here. But I can't find it! STILL, it makes no sense that

|| SYS run from a Startup Diskette would wipe MSDOS.sys-- & prevent a

|| boot to Windows. Why would it be mentioned in its ReadMe to be a

|| cure for the inability to boot to Windows , then...?...

....snip the ReadMe quote...

|| Here is another article, speaking of why the Startup Diskette doesn't

|| have a complete MSDOS.sys...

|| Err Msg: Registry File Was Not Found. Registry Services May...

....snip the article quote...

|| | Dave

....snip my sig...

| Hmm, my name mentioned and something I might/supposedly have posted

| ,,, let's look at some information if we are intending to discuss

| this [and before I start posting contents of files and my thoughts]:

|

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

|

| http://mirror.href.com/thestarman/asm/mbr/SYSDIFFS.txt

|

| http://mirror.href.com/thestarman/asm/mbr/SYSCOM.htm

|

| XP - DOS

| http://www.msfn.org/board/lofiversion/index.php/t87269.html

|

| "Can I create a DOS only (7.10) machine from a Windows 98 system or

| CD?" http://www.d-a-l.com/articles/library/35.html

|

| Personal Computers: Disk Partitions and Formatting

| http://www.windowsitlibrary.com/Content/175/07/1.html

| http://www.windowsitlibrary.com/Content/175/07/2.html

| http://www.windowsitlibrary.com/Content/175/07/3.html

|

| Create DOS boot from Winpe using diskpart & format /fs:fat

| http://www.911cd.net/forums//lofiversion/index.php?t16869.html

| see links in posts

|

| http://www.mdgx.com/msdos.htm

|

| http://support.microsoft.com/default.aspx?kbid=314057

|

| MSDOS.SYS

| http://support.microsoft.com/kb/118579

|

| http://support.microsoft.com/kb/129998

|

| http://www.mdgx.com/msdos.htm

|

| http://www.pchell.com/software/msdos-sys.shtml

|

| http://www.multiboot.ru/msdos8.htm

|

| ME - DOS

| http://www.geocities.com/mfd4life_2000/

Thanks, MEB. I must have already looked at 2 dozen articles at the MSKB.

And now I've been clicking & clicking these URLs you posted-- & STILL I

cannot find the article you or someone DID once post that said... SYS

run from a floppy will NOT copy the floppy's MSDOS.sys to C:\, if one

already exists there. I guess I'll have to just try it, if I can

remember before my next boot.

I do note there is some conflicting information out there. The XP

article you posted...

http://support.microsoft.com/default.aspx?kbid=314057

"NTLDR is missing" error message when you install or upgrade Windows XP

over Windows 95, Windows 98, or Windows Millennium Edition

.... seems to confirm Lil' Dave's contention-- but it is clearly

XP-irradiated! It says (for one thing) SYS.com needs Winboot.sys to be

present to function-- but I have no such file on my floppy or on my hard

drive! That looks like it applied only if one is using an ME Startup

Diskette, though. Still, I do not trust the article at all!

| --

| 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

||| http://support.microsoft.com/kb/178947/en-us

October 14, 2007

Re: Need a Win 98 Boot Up Disc!

PCR wrote:

| MEB wrote:

|| "PCR" <pcrrcp@netzero.net> wrote in message

|| news:OIloS6SDIHA.536@TK2MSFTNGP06.phx.gbl...

||| Lil' Dave wrote:

|

| ...snip

||| |> | When doing sys c: when booted from the boot floppy diskette

||| |> | (sys.com), the msdos.sys is incorrect for booting windows

||| |> | automatically. It may only take you to the command prompt

||| |> | after the sys.com procedure. If sys.com is not present and

||| |> | the boot diskette, simply copy it from your C: drive to the

||| |> | floppy.

||| |>

||| |> It is true the MSDOS.sys on the Startup Diskette is inadequate to

||| |> boot to Windows. However, SYS won't copy it to C:\-- if one

||| |> already exists on C:\. It will do whatever else it needs to do,

||| |> though.

||| |

||| | You are mistaken. Sys.com is unconditional.

||| | Sys.com copies from the original boot media the following:

||| | msdos.sys

||| | command.com

||| | io.sys

||| | The 4th file, I won't talk about regarding drive compression. Not

||| | a factor in this thread.

||| | Sys.com also updates the partition table as to the location of the

||| | initial boot file. Msdos.sys is not the initial boot file.

||| | Copying an undamaged, unaltered msdos.sys on the C: root drive to

||| | another folder, then copying back to the root drive after

||| | effecting sys.com will put you back to a version that will boot to

||| | windows.

|||

||| No-- it was written up that way in an article, which MEB may once

||| have posted here. But I can't find it! STILL, it makes no sense that

||| SYS run from a Startup Diskette would wipe MSDOS.sys-- & prevent a

||| boot to Windows. Why would it be mentioned in its ReadMe to be a

||| cure for the inability to boot to Windows , then...?...

|

| ...snip the ReadMe quote...

||| Here is another article, speaking of why the Startup Diskette

||| doesn't have a complete MSDOS.sys...

||| Err Msg: Registry File Was Not Found. Registry Services May...

|

| ...snip the article quote...

||| | Dave

|

| ...snip my sig...

|| Hmm, my name mentioned and something I might/supposedly have posted

|| ,,, let's look at some information if we are intending to discuss

|| this [and before I start posting contents of files and my thoughts]:

....snip MEB's URLs

| Thanks, MEB. I must have already looked at 2 dozen articles at the

| MSKB. And now I've been clicking & clicking these URLs you posted-- &

| STILL I cannot find the article you or someone DID once post that

| said... SYS run from a floppy will NOT copy the floppy's MSDOS.sys to

| C:\, if one already exists there. I guess I'll have to just try it,

| if I can remember before my next boot.

|

| I do note there is some conflicting information out there. The XP

| article you posted...

| http://support.microsoft.com/default.aspx?kbid=314057

| "NTLDR is missing" error message when you install or upgrade Windows

| XP over Windows 95, Windows 98, or Windows Millennium Edition

|

| ... seems to confirm Lil' Dave's contention-- but it is clearly

| XP-irradiated! It says (for one thing) SYS.com needs Winboot.sys to be

| present to function-- but I have no such file on my floppy or on my

| hard drive! That looks like it applied only if one is using an ME

| Startup Diskette, though. Still, I do not trust the article at all!

UPDATE:

WELL... I did the experiment on my Win98SE machine with a Startup

Diskette made on this machine. SYS would NOT copy MSDOS.sys from the

floppy to C:\-- UNTIL I deleted the one that was already there...!...

Before running SYS...

Directory of C:\

MSDOS SYS 1,784 06-15-04 6:40p

MSDOS SY_ 1,784 06-15-04 6:40p

2 file(s) 3,568 bytes

After running SYS (before deleting MSDOS.sys from C:\)...

Directory of C:\

MSDOS SYS 1,784 06-15-04 6:40p

MSDOS SY_ 1,784 06-15-04 6:40p

2 file(s) 3,568 bytes

After running SYS (after deleting MSDOS.sys from C:\)...

Directory of C:\

MSDOS SYS 6 10-13-07 8:48p

MSDOS SY_ 1,784 06-15-04 6:40p

2 file(s) 1,790 bytes

SO... there it is! SYS won't do it-- if MSDOS.sys already exists! That

may also be true of IO.sys & Command.com-- but it was impossible to

tell, because they are the same on my floppy & hard drive...

IO FLP 222,390 04-23-99 10:22p

IO SYS 222,390 04-23-99 10:22p

WARNING: DOS is very exacting! I must have typed each command 20 times

each before I got done! I don't recommend you do it, but, if you

do...!...

(a) Ensure you copy protect your floppy.

(b) Make a copy of MSDOS.sys, IO.sys & even Command.com

before proceeding.

that may become disrupted.

|| --

|| MEB

|| http://peoplescounsel.orgfree.com

|| ________

....snip one of my sig

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

| | http://support.microsoft.com/default.aspx?kbid=314057

October 14, 2007

Re: Need a Win 98 Boot Up Disc!

"PCR" <pcrrcp@netzero.net> wrote in message

news:OJAD9igDIHA.5160@TK2MSFTNGP05.phx.gbl...

| PCR wrote:

| | MEB wrote:

| || "PCR" <pcrrcp@netzero.net> wrote in message

| || news:OIloS6SDIHA.536@TK2MSFTNGP06.phx.gbl...

| ||| Lil' Dave wrote:

| |

| | ...snip

| ||| |> | When doing sys c: when booted from the boot floppy diskette

| ||| |> | (sys.com), the msdos.sys is incorrect for booting windows

| ||| |> | automatically. It may only take you to the command prompt

| ||| |> | after the sys.com procedure. If sys.com is not present and

| ||| |> | the boot diskette, simply copy it from your C: drive to the

| ||| |> | floppy.

| ||| |>

| ||| |> It is true the MSDOS.sys on the Startup Diskette is inadequate to

| ||| |> boot to Windows. However, SYS won't copy it to C:\-- if one

| ||| |> already exists on C:\. It will do whatever else it needs to do,

| ||| |> though.

| ||| |

| ||| | You are mistaken. Sys.com is unconditional.

| ||| | Sys.com copies from the original boot media the following:

| ||| | msdos.sys

| ||| | command.com

| ||| | io.sys

| ||| | The 4th file, I won't talk about regarding drive compression. Not

| ||| | a factor in this thread.

| ||| | Sys.com also updates the partition table as to the location of the

| ||| | initial boot file. Msdos.sys is not the initial boot file.

| ||| | Copying an undamaged, unaltered msdos.sys on the C: root drive to

| ||| | another folder, then copying back to the root drive after

| ||| | effecting sys.com will put you back to a version that will boot to

| ||| | windows.

| |||

| ||| No-- it was written up that way in an article, which MEB may once

| ||| have posted here. But I can't find it! STILL, it makes no sense that

| ||| SYS run from a Startup Diskette would wipe MSDOS.sys-- & prevent a

| ||| boot to Windows. Why would it be mentioned in its ReadMe to be a

| ||| cure for the inability to boot to Windows , then...?...

| |

| | ...snip the ReadMe quote...

| ||| Here is another article, speaking of why the Startup Diskette

| ||| doesn't have a complete MSDOS.sys...

| ||| http://support.microsoft.com/kb/178947/en-us

| ||| Err Msg: Registry File Was Not Found. Registry Services May...

| |

| | ...snip the article quote...

| ||| | Dave

| |

| | ...snip my sig...

| || Hmm, my name mentioned and something I might/supposedly have posted

| || ,,, let's look at some information if we are intending to discuss

| || this [and before I start posting contents of files and my thoughts]:

|

| ...snip MEB's URLs

| | Thanks, MEB. I must have already looked at 2 dozen articles at the

| | MSKB. And now I've been clicking & clicking these URLs you posted-- &

| | STILL I cannot find the article you or someone DID once post that

| | said... SYS run from a floppy will NOT copy the floppy's MSDOS.sys to

| | C:\, if one already exists there. I guess I'll have to just try it,

| | if I can remember before my next boot.

| |

| | I do note there is some conflicting information out there. The XP

| | article you posted...

| | "NTLDR is missing" error message when you install or upgrade Windows

| | XP over Windows 95, Windows 98, or Windows Millennium Edition

| |

| | ... seems to confirm Lil' Dave's contention-- but it is clearly

| | XP-irradiated! It says (for one thing) SYS.com needs Winboot.sys to be

| | present to function-- but I have no such file on my floppy or on my

| | hard drive! That looks like it applied only if one is using an ME

| | Startup Diskette, though. Still, I do not trust the article at all!

|

| UPDATE:

|

| WELL... I did the experiment on my Win98SE machine with a Startup

| Diskette made on this machine. SYS would NOT copy MSDOS.sys from the

| floppy to C:\-- UNTIL I deleted the one that was already there...!...

|

| Before running SYS...

|

| Directory of C:\

| MSDOS SYS 1,784 06-15-04 6:40p

| MSDOS SY_ 1,784 06-15-04 6:40p

| 2 file(s) 3,568 bytes

|

| After running SYS (before deleting MSDOS.sys from C:\)...

|

| Directory of C:\

| MSDOS SYS 1,784 06-15-04 6:40p

| MSDOS SY_ 1,784 06-15-04 6:40p

| 2 file(s) 3,568 bytes

|

| After running SYS (after deleting MSDOS.sys from C:\)...

|

| Directory of C:\

| MSDOS SYS 6 10-13-07 8:48p

| MSDOS SY_ 1,784 06-15-04 6:40p

| 2 file(s) 1,790 bytes

|

| SO... there it is! SYS won't do it-- if MSDOS.sys already exists! That

| may also be true of IO.sys & Command.com-- but it was impossible to

| tell, because they are the same on my floppy & hard drive...

|

| IO FLP 222,390 04-23-99 10:22p

| IO SYS 222,390 04-23-99 10:22p

There you go, confirmed results of your own, when using the boot disk.

sys.com from ebd.cab - 18,967 05/06/98 8:01 PM

sys.com from \COMMAND - 18,967 04/23/99 10:22 PM

sys.com from ME ebd.cab - 21,943 11/06/06 [bootdisk.com]

There's a lot of checking for files, registry, and other going on in

io.sys, command.com, and sys.com.

You are correct, there is an awful lot of conflicting information on the

net. Users of one OS may bring their findings and attempt to apply them to

others, which may not be applicable.

Just as they do when working with other aspects of hard drives ...

|

| WARNING: DOS is very exacting! I must have typed each command 20 times

| each before I got done! I don't recommend you do it, but, if you

| do...!...

|

| (a) Ensure you copy protect your floppy.

| (b) Make a copy of MSDOS.sys, IO.sys & even Command.com

| before proceeding.

| © Ensure you are not running a hard drive overlay (like EZ-BIOS)

| that may become disrupted.

I would recommend the same. Good job PCR... of course you don't need me to

say that.

Now what happened with this party's attempt to fix the issues?

Issues such as this do not automatically mean a trashed disk or computer.

IF they copied autoexec.bat and config.sys to the hard drive [or if they

were also corrupted, or if they did] then the original error [command.com]

may have been compounded.

Seems advisable to have asked/advised concerning those and other issues.

Could be a virus, or some other issue.

|

| || --

| || MEB

| || ________

|

| ...snip one of my sig

| --

| Thanks or Good Luck,

| There may be humor in this post, and,

| Naturally, you will not sue,

| Should things get worse after this,

| PCR

|

--

MEB

http://support.microsoft.com/default.aspx?kbid=314057

________

October 14, 2007

Re: Need a Win 98 Boot Up Disc!

MEB wrote:

| "PCR" <pcrrcp@netzero.net> wrote in message

| news:OJAD9igDIHA.5160@TK2MSFTNGP05.phx.gbl...

|| PCR wrote:

....snip

|| UPDATE:

||

|| WELL... I did the experiment on my Win98SE machine with a Startup

|| Diskette made on this machine. SYS would NOT copy MSDOS.sys from the

|| floppy to C:\-- UNTIL I deleted the one that was already there...!...

||

|| Before running SYS...

||

|| Directory of C:\

|| MSDOS SYS 1,784 06-15-04 6:40p

|| MSDOS SY_ 1,784 06-15-04 6:40p

|| 2 file(s) 3,568 bytes

||

|| After running SYS (before deleting MSDOS.sys from C:\)...

||

|| Directory of C:\

|| MSDOS SYS 1,784 06-15-04 6:40p

|| MSDOS SY_ 1,784 06-15-04 6:40p

|| 2 file(s) 3,568 bytes

||

|| After running SYS (after deleting MSDOS.sys from C:\)...

||

|| Directory of C:\

|| MSDOS SYS 6 10-13-07 8:48p

|| MSDOS SY_ 1,784 06-15-04 6:40p

|| 2 file(s) 1,790 bytes

||

|| SO... there it is! SYS won't do it-- if MSDOS.sys already exists!

|| That may also be true of IO.sys & Command.com-- but it was

|| impossible to tell, because they are the same on my floppy & hard

|| drive...

||

|| IO FLP 222,390 04-23-99 10:22p

|| IO SYS 222,390 04-23-99 10:22p

|

| There you go, confirmed results of your own, when using the boot

| disk. sys.com from ebd.cab - 18,967 05/06/98 8:01 PM

| sys.com from \COMMAND - 18,967 04/23/99 10:22 PM

| sys.com from ME ebd.cab - 21,943 11/06/06 [bootdisk.com]

| There's a lot of checking for files, registry, and other going on in

| io.sys, command.com, and sys.com.

I'm not sure the results would be the same with an ME Startup Diskette

or when XP is involved, going by that irradiated article you posted...

"NTLDR is missing" error message when you install or upgrade Windows XP

over Windows 95, Windows 98, or Windows Millennium Edition

...., which seems to confirm Lil' Dave's contention-- but it is clearly

XP-irradiated! It says (for one thing) SYS.com needs Winboot.sys to be

present to function-- but I have no such file on my floppy or on my hard

drive with just Win98SE! That looks like it applied only if one is using

an ME Startup Diskette.

| You are correct, there is an awful lot of conflicting information on

| the net. Users of one OS may bring their findings and attempt to

| apply them to others, which may not be applicable.

| Just as they do when working with other aspects of hard drives ...

Yea. There is truth to that.

||

|| WARNING: DOS is very exacting! I must have typed each command 20

|| times each before I got done! I don't recommend you do it, but, if

|| you do...!...

||

|| (a) Ensure you copy protect your floppy.

|| (b) Make a copy of MSDOS.sys, IO.sys & even Command.com

|| before proceeding.

|| © Ensure you are not running a hard drive overlay (like EZ-BIOS)

|| that may become disrupted.

|

| I would recommend the same. Good job PCR... of course you don't need

| me to say that.

Thanks. As I said, I had to type each command 44 times each, before they

would work twice!

| Now what happened with this party's attempt to fix the issues?

I don't know. But my lawyers are saying we should leave soon!

| Issues such as this do not automatically mean a trashed disk or

| computer. IF they copied autoexec.bat and config.sys to the hard

| drive [or if they were also corrupted, or if they did] then the

| original error [command.com] may have been compounded.

| Seems advisable to have asked/advised concerning those and other

| issues. Could be a virus, or some other issue.

That's right. One should post one's plan to the NG, if one is unsure of

the result. Config.sys & Autoexec.bat should not be copied to the hard

drive from the Startup Diskette. Also, MSDOS.sys should not be copied

from it.

||

|| || --

|| || MEB

|| || ________

||

|| ...snip one of my sig

|| --

|| 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

| ________

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&spid=&query=winboot.sys&adv=

October 15, 2007

Re: Need a Win 98 Boot Up Disc!

As you say, this part of the query's discussion seems to be over, however,

in response to the winboot.sys issue:

That *in file* check is contained in 95 (07-11-95 - upgrade), 95B

(08-24-96), 98 (FE/SE), and ME sys.com {MSDOS 7 & 8}. It is not in 6.22

sys.com.

The check [and file] is for install/deployment aspects related to Windows.

The winboot files [temporary files] are created/installed during the Windows

[95, 98, ME] install process, and must be removed or replaced during that

process [prior to final boot] or errors will occur.

Having both an io.sys and winboot.sys may cause failure during the install.

Corruption of either, or perhaps using a cloned drive image, may also

require the manipulation of io.sys or winboot.sys, or both. Potentially

effects the installation of all Windows up to XP [using upgrade process].

http://support.microsoft.com/kb/135542/en-us - 95 DMF floppies

http://support.microsoft.com/kb/135540/en-us - 95 CDROM

http://support.microsoft.com/kb/191054/en-us - 98 DMF floppies

http://support.microsoft.com/kb/189503/en-us - 98 cdrom

http://support.microsoft.com/kb/238664/en-us - 98SE CDROM 1 of 14

http://support.microsoft.com/kb/238666/en-us - 98SE CDROM 2 of 14

http://support.microsoft.com/kb/235380/en-us - 98SE year 2000 update

http://support.microsoft.com/kb/272253/en-us - ME CDROM

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

--

MEB

http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&spid=&query=winboot.sys&adv=

________

October 15, 2007

Re: Need a Win 98 Boot Up Disc!

MEB wrote:

| As you say, this part of the query's discussion seems to be over,

| however, in response to the winboot.sys issue:

| That *in file* check is contained in 95 (07-11-95 - upgrade), 95B

| (08-24-96), 98 (FE/SE), and ME sys.com {MSDOS 7 & 8}. It is not in

| 6.22 sys.com.

|

| The check [and file] is for install/deployment aspects related to

| Windows. The winboot files [temporary files] are created/installed

| during the Windows [95, 98, ME] install process, and must be removed

| or replaced during that process [prior to final boot] or errors will

| occur.

There may be truth to what you say. Now, I do find even my own Win98SE

contains that file in a .cab...

Cabinet BASE5.CAB

04-23-1999 10:22:00p A--- 222,390 winboot.sys

Could be something is done with it during the install of Win98, but

later it is deleted or renamed. Another thing: Here is a quote (I

recently posted to another thread) of Andrew Schulman in "Unauthorized

Windows 95"...

"If I had to explain how Windows 95 relates to DOS in 25

words or less, I'd say this: Windows 95 relates to DOS in

the same that WFW 3.11 does. Windows provides 32BFA

[32-bit file access]. For non-file calls, it calls (in V86 mode)

the real-mode DOS code in Winboot.sys [called IO.sys since

the released version of Windows 95]. Windows 95 is a

genuine operating system; so were WFD 3.1, Windows 3.1

Enhanced mode, and Windows 3.0 Enhanced mode."

| Having both an io.sys and winboot.sys may cause failure during the

| install. Corruption of either, or perhaps using a cloned drive image,

| may also require the manipulation of io.sys or winboot.sys, or both.

That has the ring of truth. Could even be the universe would explode, if

those two files ever were to be found in the same place at the same

time!

| Potentially effects the installation of all Windows up to XP [using

| upgrade process].

|

| http://support.microsoft.com/kb/135542/en-us - 95 DMF floppies

| http://support.microsoft.com/kb/135540/en-us - 95 CDROM

| http://support.microsoft.com/kb/191054/en-us - 98 DMF floppies

| http://support.microsoft.com/kb/189503/en-us - 98 cdrom

| http://support.microsoft.com/kb/238664/en-us - 98SE CDROM 1 of 14

| http://support.microsoft.com/kb/238666/en-us - 98SE CDROM 2 of 14

| http://support.microsoft.com/kb/235380/en-us - 98SE year 2000 update

| http://support.microsoft.com/kb/272253/en-us - ME CDROM

|

| 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!

| --

| 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

http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&spid=&query=winboot.sys&adv=

October 15, 2007

Re: Need a Win 98 Boot Up Disc!

"PCR" <pcrrcp@netzero.net> wrote in message

news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...

| MEB wrote:

| | As you say, this part of the query's discussion seems to be over,

| | however, in response to the winboot.sys issue:

| | That *in file* check is contained in 95 (07-11-95 - upgrade), 95B

| | (08-24-96), 98 (FE/SE), and ME sys.com {MSDOS 7 & 8}. It is not in

| | 6.22 sys.com.

| |

| | The check [and file] is for install/deployment aspects related to

| | Windows. The winboot files [temporary files] are created/installed

| | during the Windows [95, 98, ME] install process, and must be removed

| | or replaced during that process [prior to final boot] or errors will

| | occur.

|

| There may be truth to what you say. Now, I do find even my own Win98SE

| contains that file in a .cab...

|

| Cabinet BASE5.CAB

| 04-23-1999 10:22:00p A--- 222,390 winboot.sys

|

| Could be something is done with it during the install of Win98, but

| later it is deleted or renamed. Another thing: Here is a quote (I

| recently posted to another thread) of Andrew Schulman in "Unauthorized

| Windows 95"...

|

| "If I had to explain how Windows 95 relates to DOS in 25

| words or less, I'd say this: Windows 95 relates to DOS in

| the same that WFW 3.11 does. Windows provides 32BFA

| [32-bit file access]. For non-file calls, it calls (in V86 mode)

| the real-mode DOS code in Winboot.sys [called IO.sys since

| the released version of Windows 95]. Windows 95 is a

| genuine operating system; so were WFD 3.1, Windows 3.1

| Enhanced mode, and Windows 3.0 Enhanced mode."

From the above, one could get a somewhat false impression that winboot.sys

isn't involved in 9X. Which it isn't, but only AFTER it is removed

during/after the install is finished.

And I'm not so sure I would make such a broad statement of *genuine

operating system*, which could also be misconstrued. But that's an old

debate dating to the Win 3 days, and only enhanced via 9X. It all depends

upon WHAT one considers as an operating system.

|

| | Having both an io.sys and winboot.sys may cause failure during the

| | install. Corruption of either, or perhaps using a cloned drive image,

| | may also require the manipulation of io.sys or winboot.sys, or both.

|

| That has the ring of truth. Could even be the universe would explode, if

| those two files ever were to be found in the same place at the same

| time!

|

| | Potentially effects the installation of all Windows up to XP [using

| | upgrade process].

| |

|

| | http://support.microsoft.com/kb/135542/en-us - 95 DMF floppies

| | http://support.microsoft.com/kb/135540/en-us - 95 CDROM

| | http://support.microsoft.com/kb/191054/en-us - 98 DMF floppies

| | http://support.microsoft.com/kb/189503/en-us - 98 cdrom

| | http://support.microsoft.com/kb/238664/en-us - 98SE CDROM 1 of 14

| | http://support.microsoft.com/kb/238666/en-us - 98SE CDROM 2 of 14

| | http://support.microsoft.com/kb/235380/en-us - 98SE year 2000 update

| | http://support.microsoft.com/kb/272253/en-us - ME CDROM

| |

| | 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.

|

| | --

| | 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

|

--

MEB

http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&spid=&query=winboot.sys&adv=

________

October 16, 2007

Re: Need a Win 98 Boot Up Disc!

MEB wrote:

| "PCR" <pcrrcp@netzero.net> wrote in message

| news:OLj7AN3DIHA.3548@TK2MSFTNGP06.phx.gbl...

|| MEB wrote:

|| | As you say, this part of the query's discussion seems to be over,

|| | however, in response to the winboot.sys issue:

|| | That *in file* check is contained in 95 (07-11-95 - upgrade), 95B

|| | (08-24-96), 98 (FE/SE), and ME sys.com {MSDOS 7 & 8}. It is not in

|| | 6.22 sys.com.

|| |

|| | The check [and file] is for install/deployment aspects related to

|| | Windows. The winboot files [temporary files] are created/installed

|| | during the Windows [95, 98, ME] install process, and must be

|| | removed or replaced during that process [prior to final boot] or

|| | errors will occur.

||

|| There may be truth to what you say. Now, I do find even my own

|| Win98SE contains that file in a .cab...

||

|| Cabinet BASE5.CAB

|| 04-23-1999 10:22:00p A--- 222,390 winboot.sys

||

|| Could be something is done with it during the install of Win98, but

|| later it is deleted or renamed. Another thing: Here is a quote (I

|| recently posted to another thread) of Andrew Schulman in

|| "Unauthorized Windows 95"...

||

|| "If I had to explain how Windows 95 relates to DOS in 25

|| words or less, I'd say this: Windows 95 relates to DOS in

|| the same that WFW 3.11 does. Windows provides 32BFA

|| [32-bit file access]. For non-file calls, it calls (in V86 mode)

|| the real-mode DOS code in Winboot.sys [called IO.sys since

|| the released version of Windows 95]. Windows 95 is a

|| genuine operating system; so were WFD 3.1, Windows 3.1

|| Enhanced mode, and Windows 3.0 Enhanced mode."

|

| From the above, one could get a somewhat false impression that

| winboot.sys isn't involved in 9X. Which it isn't, but only AFTER it

| is removed during/after the install is finished.

It sounds like something mysterious is involved with that file. It's

interesting, though; NOW, I have extracted Winboot.sys-- & it appears to

be identical to my IO.sys, except in name...!...

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

Also, IO.sys, itself, does not exist in any .cab under its own name.

Therefore, I think this file must be one of those that lives in its .cab

under a false name!

| And I'm not so sure I would make such a broad statement of *genuine

| operating system*, which could also be misconstrued. But that's an old

| debate dating to the Win 3 days, and only enhanced via 9X. It all

| depends upon WHAT one considers as an operating system.

Here is one definition of it, from "Windows 98 Secrets" (Livingston &

Straub), p.1055...

"Andrew Schulman argued in his book, 'Unauthorized Windows 95', that

with the advent of Windows/386 2.x in 1988, Windows became a real

operating system. Windows is an operating system because it handles the

requests that programs make of the computer. When necessary, it hands

those requests to DOS to let it do some of the work. Since the advent of

Windows for Workgroups 3.11, and especially the 32-bit file access that

came with it, DOS has handled even less of the grunt work to do."

||

|| | Having both an io.sys and winboot.sys may cause failure during the

|| | install. Corruption of either, or perhaps using a cloned drive

|| | image, may also require the manipulation of io.sys or winboot.sys,

|| | or both.

||

|| That has the ring of truth. Could even be the universe would

|| explode, if those two files ever were to be found in the same place

|| at the same time!

||

|| | Potentially effects the installation of all Windows up to XP [using

|| | upgrade process].

|| |

||

|

|| | http://support.microsoft.com/kb/135542/en-us - 95 DMF floppies

|| | http://support.microsoft.com/kb/135540/en-us - 95 CDROM

|| | http://support.microsoft.com/kb/191054/en-us - 98 DMF floppies

|| | http://support.microsoft.com/kb/189503/en-us - 98 cdrom

|| | http://support.microsoft.com/kb/238664/en-us - 98SE CDROM 1 of 14

|| | http://support.microsoft.com/kb/238666/en-us - 98SE CDROM 2 of 14

|| | http://support.microsoft.com/kb/235380/en-us - 98SE year 2000

|| | update http://support.microsoft.com/kb/272253/en-us - ME CDROM

|| |

|| | 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.

Maybe. Sounds like it could be, going by the names of them.

||

|| | --

|| | 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

| ________

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

October 16, 2007

Re: Need a Win 98 Boot Up Disc!

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

| ________

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

October 17, 2007

Re: Need a Win 98 Boot Up Disc!

"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

|

--

MEB