Is it possible that I am the only one here that knows something ..

[b11_]

Is it possible that I am the only one here that knows something about cross
booting?

I experienced cross booting not once but on 2 different occasions.

I was not using a boot manager!

 

[Stanislaw Flatto]

Re: Is it possible that I am the only one here that knows something..

b11_ wrote:
> Is it possible that I am the only one here that knows something about cross
> booting?
>
> I experienced cross booting not once but on 2 different occasions.
>
> I was not using a boot manager!
Can you induce this condition intentionally?
How? Explain.

Stanislaw
Slack user from Ulladulla.

 

[Gary S. Terhune]

What you described, that one OS started the boot and another finished it, is
not possible. Again, how do you know that's what happened?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"b11_" <b11@discussions.microsoft.com> wrote in message
news:A7C364AE-23B0-4372-B034-38A9602C2A92@microsoft.com...
> Is it possible that I am the only one here that knows something about
> cross
> booting?
>
> I experienced cross booting not once but on 2 different occasions.
>
> I was not using a boot manager!

 

[Jeff Richards]

He didn't say that one OS started the boot and another OS finished it. What
he described (eventually) was that the system appeared to start booting from
one drive, but eventually booted an operating system on another drive.
There are probably several ways that could happen.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Gary S. Terhune" <nobody@nowhere.not> wrote in message
news:OIFzra$zHHA.3400@TK2MSFTNGP03.phx.gbl...
> What you described, that one OS started the boot and another finished it,
> is not possible. Again, how do you know that's what happened?
>
> --
> Gary S. Terhune
> MS-MVP Shell/User
> www.grystmill.com

 

[Gary S. Terhune]

<quote>
"I beieve that when a drive starts booting and then another drive finishes
booting then that is called cross booting"
<unquote>

If cross-booting is a term that encompasses any procedure wherein one OS
starts to boot and then passes control to another OS, well in that case
*any* machine is cross-booting to load, since the BIOS is an OS that boots
and then passes control to another OS. Same for any boot manager.

Anyway, I don't see how the case described could happen without deliberately
configuring the first instance of Win98 to do so. Even then, I don't see how
Win98 could be cross-booted as it's been defined here. Do you have a
scenario that fits?

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Jeff Richards" <JRichards@msn.com.au> wrote in message
news:OocHNVE0HHA.1164@TK2MSFTNGP02.phx.gbl...
> He didn't say that one OS started the boot and another OS finished it.
> What he described (eventually) was that the system appeared to start
> booting from one drive, but eventually booted an operating system on
> another drive. There are probably several ways that could happen.
> --
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "Gary S. Terhune" <nobody@nowhere.not> wrote in message
> news:OIFzra$zHHA.3400@TK2MSFTNGP03.phx.gbl...
>> What you described, that one OS started the boot and another finished it,
>> is not possible. Again, how do you know that's what happened?
>>
>> --
>> Gary S. Terhune
>> MS-MVP Shell/User
>> www.grystmill.com
>
>

 

[Jeff Richards]

That might be a description of cross booting, but I think it's clear that
cross booting was not what happened. The actual description of events was "I
entered BIOS and selected drive 2, which has W98 on an active
partition, to boot. Well 2 started to boot but then I noticed a different
drive, which has W98, booting" In other words, the second drive was set as
the boot drive, some sort of access occurred to that second drive (how much
is not clear) and then the boot continued on the other drive.

My comment that there are several ways that this could happen assumes that
"drive 2" means some drive other than the master on the primary IDE
controller, and "other" means the master on the primary controller.

The simplest explanation, of course, is that the system couldn't detect a
valid boot sector on "Drive 2" and defaulted to the next listed drive in the
BIOS boot sequence. But I assume OP would be aware of this behaviour. --
Jeff Richards
MS MVP (Windows - Shell/User)
"Gary S. Terhune" <nobody@nowhere.not> wrote in message
news:OqCqkhG0HHA.3788@TK2MSFTNGP02.phx.gbl...
> <quote>
> "I beieve that when a drive starts booting and then another drive finishes
> booting then that is called cross booting"
> <unquote>
>
> If cross-booting is a term that encompasses any procedure wherein one OS
> starts to boot and then passes control to another OS, well in that case
> *any* machine is cross-booting to load, since the BIOS is an OS that boots
> and then passes control to another OS. Same for any boot manager.
>
> Anyway, I don't see how the case described could happen without
> deliberately configuring the first instance of Win98 to do so. Even then,
> I don't see how Win98 could be cross-booted as it's been defined here. Do
> you have a scenario that fits?
>
> --
> Gary S. Terhune
> MS-MVP Shell/User
> www.grystmill.com
>
> "Jeff Richards" <JRichards@msn.com.au> wrote in message
> news:OocHNVE0HHA.1164@TK2MSFTNGP02.phx.gbl...
>> He didn't say that one OS started the boot and another OS finished it.
>> What he described (eventually) was that the system appeared to start
>> booting from one drive, but eventually booted an operating system on
>> another drive. There are probably several ways that could happen.
>> --
>> Jeff Richards
>> MS MVP (Windows - Shell/User)
>> "Gary S. Terhune" <nobody@nowhere.not> wrote in message
>> news:OIFzra$zHHA.3400@TK2MSFTNGP03.phx.gbl...
>>> What you described, that one OS started the boot and another finished
>>> it, is not possible. Again, how do you know that's what happened?
>>>
>>> --
>>> Gary S. Terhune
>>> MS-MVP Shell/User
>>> www.grystmill.com
>>
>>
>
>

 

[Gary S. Terhune]

Well, you and I are on the same page, anyway, <s>.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Jeff Richards" <JRichards@msn.com.au> wrote in message
news:uAE%23DoK0HHA.5884@TK2MSFTNGP02.phx.gbl...
> That might be a description of cross booting, but I think it's clear that
> cross booting was not what happened. The actual description of events was
> "I entered BIOS and selected drive 2, which has W98 on an active
> partition, to boot. Well 2 started to boot but then I noticed a different
> drive, which has W98, booting" In other words, the second drive was set
> as the boot drive, some sort of access occurred to that second drive (how
> much is not clear) and then the boot continued on the other drive.
>
> My comment that there are several ways that this could happen assumes that
> "drive 2" means some drive other than the master on the primary IDE
> controller, and "other" means the master on the primary controller.
>
> The simplest explanation, of course, is that the system couldn't detect a
> valid boot sector on "Drive 2" and defaulted to the next listed drive in
> the BIOS boot sequence. But I assume OP would be aware of this
> ehaviour. --
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "Gary S. Terhune" <nobody@nowhere.not> wrote in message
> news:OqCqkhG0HHA.3788@TK2MSFTNGP02.phx.gbl...
>> <quote>
>> "I beieve that when a drive starts booting and then another drive
>> finishes booting then that is called cross booting"
>> <unquote>
>>
>> If cross-booting is a term that encompasses any procedure wherein one OS
>> starts to boot and then passes control to another OS, well in that case
>> *any* machine is cross-booting to load, since the BIOS is an OS that
>> boots and then passes control to another OS. Same for any boot manager.
>>
>> Anyway, I don't see how the case described could happen without
>> deliberately configuring the first instance of Win98 to do so. Even then,
>> I don't see how Win98 could be cross-booted as it's been defined here. Do
>> you have a scenario that fits?
>>
>> --
>> Gary S. Terhune
>> MS-MVP Shell/User
>> www.grystmill.com
>>
>> "Jeff Richards" <JRichards@msn.com.au> wrote in message
>> news:OocHNVE0HHA.1164@TK2MSFTNGP02.phx.gbl...
>>> He didn't say that one OS started the boot and another OS finished it.
>>> What he described (eventually) was that the system appeared to start
>>> booting from one drive, but eventually booted an operating system on
>>> another drive. There are probably several ways that could happen.
>>> --
>>> Jeff Richards
>>> MS MVP (Windows - Shell/User)
>>> "Gary S. Terhune" <nobody@nowhere.not> wrote in message
>>> news:OIFzra$zHHA.3400@TK2MSFTNGP03.phx.gbl...
>>>> What you described, that one OS started the boot and another finished
>>>> it, is not possible. Again, how do you know that's what happened?
>>>>
>>>> --
>>>> Gary S. Terhune
>>>> MS-MVP Shell/User
>>>> www.grystmill.com
>>>
>>>
>>
>>
>
>