cross booting

[b11_]

I check the Microsoft website but can not find any article pertaining to
cross booting. Your suggestions please.

 

[Stanislaw Flatto]

Re: cross booting

b11_ wrote:
> I check the Microsoft website but can not find any article pertaining to
> cross booting. Your suggestions please.
And what OS is "cross" that should boot on x86 hardware?
If you are relating to dual/tripple/quadrupple booting of different OS's
then MS is NOT a place to ask.
Try a Unix/Linux crowd.

HTH

Stanislaw
Slack user from Ulladulla.

 

[PCR]

Re: cross booting

b11_ wrote:
| I check the Microsoft website but can not find any article pertaining
| to cross booting. Your suggestions please.

I, TOO, was trying to guess what cross booting was. I was ashamed to
admit I didn't know! But, for dual or triple booting, (I don't do it,
but) I think I might recommend...

http://www.bootitng.com/ 's BootIt NG, has a variety of backup
capabilities & works with all OS: Copy partition(s) to HDD, or Image to
HDD or to CD or DVD. Create, move, shrink or expand partitions without
data loss. Multi-boot too. To install & use beyond 30 days, $34.95.

For... what's that other thing... OS Emulation... best talk to Terhune
or glee or Brian A. But you will become irradiated, if you do it with
XP!


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

 

[philo]

Re: cross booting


"b11_" <b11@discussions.microsoft.com> wrote in message
news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
> I check the Microsoft website but can not find any article pertaining to
> cross booting. Your suggestions please.


You will get plenty of results on Google if you use the term "Dual Booting"

If you want to mention which OS's you want to run...you can also get some
help here.

As a general rule however... each OS should be on it's own partition...with
the oldest OS installed first.

 

[b11_]

Re: cross booting

Sometime ago, 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. I beieve that when a drive starts booting and
then another drive finishes booting then that is called cross booting.
_________________________________________________________
"philo" wrote:

>
> "b11_" <b11@discussions.microsoft.com> wrote in message
> news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
> > I check the Microsoft website but can not find any article pertaining to
> > cross booting. Your suggestions please.
>
>
> You will get plenty of results on Google if you use the term "Dual Booting"
>
> If you want to mention which OS's you want to run...you can also get some
> help here.
>
> As a general rule however... each OS should be on it's own partition...with
> the oldest OS installed first.
>
>
>

 

[Gary S. Terhune]

Re: cross booting

There is no such thing as you're describing, not the term, not the activity.
It's not possible, at least not in normal situations. How do you know it
booted from drive 1 after starting on drive 2? (I presume drive 1 is where
the other Win98 system is located.)

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

"b11_" <b11@discussions.microsoft.com> wrote in message
news:AA62239E-2E28-48FA-ABD9-2804D510DCD4@microsoft.com...
> Sometime ago, 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. I beieve that when a drive starts booting
> and
> then another drive finishes booting then that is called cross booting.
> _________________________________________________________
> "philo" wrote:
>
>>
>> "b11_" <b11@discussions.microsoft.com> wrote in message
>> news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
>> > I check the Microsoft website but can not find any article pertaining
>> > to
>> > cross booting. Your suggestions please.
>>
>>
>> You will get plenty of results on Google if you use the term "Dual
>> Booting"
>>
>> If you want to mention which OS's you want to run...you can also get some
>> help here.
>>
>> As a general rule however... each OS should be on it's own
>> partition...with
>> the oldest OS installed first.
>>
>>
>>

 

[Gary S. Terhune]

Re: cross booting

Plenty of people multi-boot various MS OSes, using various boot managers.
Yes, if one contemplates using a 'nix OS then it would be good to ask around
for hints, but multi-booting itself is OS agnostic. You can get *plenty* of
good multi-booting advice from this group.

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

"Stanislaw Flatto" <compaid@brownbear.com.au> wrote in message
news:46a6f988@news.comindico.com.au...
> b11_ wrote:
>> I check the Microsoft website but can not find any article pertaining to
>> cross booting. Your suggestions please.
> And what OS is "cross" that should boot on x86 hardware?
> If you are relating to dual/tripple/quadrupple booting of different OS's
> then MS is NOT a place to ask.
> Try a Unix/Linux crowd.
>
> HTH
>
> Stanislaw
> Slack user from Ulladulla.

 

[Brian A.]

Re: cross booting

You sure Linux wasn't installed and you weren't "Cross-LFS-Network-Booting". I'm
sure you didn't have a Windows Based Server over an IP SAN and you were running a
"Cross Platform".

I think you may be mistaken but I can't judge, you saw what you saw and I didn't.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375


"b11_" <b11@discussions.microsoft.com> wrote in message
news:AA62239E-2E28-48FA-ABD9-2804D510DCD4@microsoft.com...
> Sometime ago, 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. I beieve that when a drive starts booting and
> then another drive finishes booting then that is called cross booting.
> _________________________________________________________
> "philo" wrote:
>
>>
>> "b11_" <b11@discussions.microsoft.com> wrote in message
>> news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
>> > I check the Microsoft website but can not find any article pertaining to
>> > cross booting. Your suggestions please.
>>
>>
>> You will get plenty of results on Google if you use the term "Dual Booting"
>>
>> If you want to mention which OS's you want to run...you can also get some
>> help here.
>>
>> As a general rule however... each OS should be on it's own partition...with
>> the oldest OS installed first.
>>
>>
>>

 

[Jeff Richards]

Re: cross booting

Note that if you are not talking generic Windows machines, then the process
you describe is fairly common. For instance, in embedded systems it's not
unusual for the boot process to load a partition image into memory and then
boot from that image instead of the disk (or ROM device more usually) from
which the boot code was loaded.

Here's an example:
http://www.patentstorm.us/patents/6996706-description.html

The only circumstance I can think of where the hard drive boot process gets
restarted with a standard PC is with some drive overlay software. The first
part of the boot loads a BIOS replacement which then takes over the boot
process. In order to do this successfully the overlay software needs to
look as much as possible like the original BIOS boot code, and to do this it
effectively restarts the boot from scratch once it gets loaded. So if drive
2 has this sort of BIOS overlay software installed, but it was not expecting
to get started from drive 2, and it didn't understand about BIOS settings
that re-assigned the drive order (or, it replaced the code that responded to
those settings), then I guess what you are describing is a possibility.

It's a bit like the process that occurs when you want to boot a system with
drive overlay software installed from floppy - you can actually interrupt it
in the time between loading the overlay and loading the OS, and tell it to
load the OS from the floppy.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"b11_" <b11@discussions.microsoft.com> wrote in message
news:AA62239E-2E28-48FA-ABD9-2804D510DCD4@microsoft.com...
> Sometime ago, 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. I beieve that when a drive starts booting
> and
> then another drive finishes booting then that is called cross booting.
> _________________________________________________________
> "philo" wrote:
>
>>
>> "b11_" <b11@discussions.microsoft.com> wrote in message
>> news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
>> > I check the Microsoft website but can not find any article pertaining
>> > to
>> > cross booting. Your suggestions please.
>>
>>
>> You will get plenty of results on Google if you use the term "Dual
>> Booting"
>>
>> If you want to mention which OS's you want to run...you can also get some
>> help here.
>>
>> As a general rule however... each OS should be on it's own
>> partition...with
>> the oldest OS installed first.
>>
>>
>>

 

[Gary S. Terhune]

Re: cross booting

Still, this does not match the description given. Yes, a boot can be
interrupted and another OS booted, but the second OS doesn't "finish" the
booting process, it's an entirely new process.

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

"Jeff Richards" <JRichards@msn.com.au> wrote in message
news:eo7ZfSE0HHA.3400@TK2MSFTNGP03.phx.gbl...
> Note that if you are not talking generic Windows machines, then the
> process you describe is fairly common. For instance, in embedded systems
> it's not unusual for the boot process to load a partition image into
> memory and then boot from that image instead of the disk (or ROM device
> more usually) from which the boot code was loaded.
>
> Here's an example:
> http://www.patentstorm.us/patents/6996706-description.html
>
> The only circumstance I can think of where the hard drive boot process
> gets restarted with a standard PC is with some drive overlay software.
> The first part of the boot loads a BIOS replacement which then takes over
> the boot process. In order to do this successfully the overlay software
> needs to look as much as possible like the original BIOS boot code, and to
> do this it effectively restarts the boot from scratch once it gets loaded.
> So if drive 2 has this sort of BIOS overlay software installed, but it was
> not expecting to get started from drive 2, and it didn't understand about
> BIOS settings that re-assigned the drive order (or, it replaced the code
> that responded to those settings), then I guess what you are describing is
> a possibility.
>
> It's a bit like the process that occurs when you want to boot a system
> with drive overlay software installed from floppy - you can actually
> interrupt it in the time between loading the overlay and loading the OS,
> and tell it to load the OS from the floppy.
> --
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "b11_" <b11@discussions.microsoft.com> wrote in message
> news:AA62239E-2E28-48FA-ABD9-2804D510DCD4@microsoft.com...
>> Sometime ago, 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. I beieve that when a drive starts booting
>> and
>> then another drive finishes booting then that is called cross booting.
>> _________________________________________________________
>> "philo" wrote:
>>
>>>
>>> "b11_" <b11@discussions.microsoft.com> wrote in message
>>> news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
>>> > I check the Microsoft website but can not find any article pertaining
>>> > to
>>> > cross booting. Your suggestions please.
>>>
>>>
>>> You will get plenty of results on Google if you use the term "Dual
>>> Booting"
>>>
>>> If you want to mention which OS's you want to run...you can also get
>>> some
>>> help here.
>>>
>>> As a general rule however... each OS should be on it's own
>>> partition...with
>>> the oldest OS installed first.
>>>
>>>
>>>
>
>

 

[Jeff Richards]

Re: cross booting

If you move outside the PC world it is quite common for one OS to start the
boot process and another OS to finish it.

The minicomputers I used to work with had a microprocessor-based I/O
controller. The boot process started with a boot to an embedded OS (which
was actually the previous generation 16-bit OS) running on this
microprocessor. This OS started the basic I/O procedures (including disk)
and then loaded and started the 32-bit OS on the main CPU. The original boot
OS then reverted to its job of managing I/O while the OS running on the CPU
started the CLI and all the higher level services. Both OSes were then
running simultaneously. It was possible to stop the boot process after the
16-bit OS was running and perform tasks such as diagnostics or upgrades to
the 32-bit OS. At that point it was a standard dual-ground single-user
16-bit OS with its own CLI and access to most of the I/O. Then, when
diagnostics or whatever are finished, the operator would issue a CLI command
to boot the 32-bit OS, using the I/O services provided by the 16-bit OS.

That might not be quite what OP was referring to, but I would certainly call
it starting the boot with one OS and finishing the boot with a different OS.
--
Jeff Richards
MS MVP (Windows - Shell/User)

"Gary S. Terhune" <nobody@nowhere.not> wrote in message
news:%23gek5aG0HHA.5800@TK2MSFTNGP05.phx.gbl...
> Still, this does not match the description given. Yes, a boot can be
> interrupted and another OS booted, but the second OS doesn't "finish" the
> booting process, it's an entirely new process.
>
> --
> Gary S. Terhune
> MS-MVP Shell/User
> www.grystmill.com
>
> "Jeff Richards" <JRichards@msn.com.au> wrote in message
> news:eo7ZfSE0HHA.3400@TK2MSFTNGP03.phx.gbl...
>> Note that if you are not talking generic Windows machines, then the
>> process you describe is fairly common. For instance, in embedded systems
>> it's not unusual for the boot process to load a partition image into
>> memory and then boot from that image instead of the disk (or ROM device
>> more usually) from which the boot code was loaded.
>>
>> Here's an example:
>> http://www.patentstorm.us/patents/6996706-description.html
>>
>> The only circumstance I can think of where the hard drive boot process
>> gets restarted with a standard PC is with some drive overlay software.
>> The first part of the boot loads a BIOS replacement which then takes over
>> the boot process. In order to do this successfully the overlay software
>> needs to look as much as possible like the original BIOS boot code, and
>> to do this it effectively restarts the boot from scratch once it gets
>> loaded. So if drive 2 has this sort of BIOS overlay software installed,
>> but it was not expecting to get started from drive 2, and it didn't
>> understand about BIOS settings that re-assigned the drive order (or, it
>> replaced the code that responded to those settings), then I guess what
>> you are describing is a possibility.
>>
>> It's a bit like the process that occurs when you want to boot a system
>> with drive overlay software installed from floppy - you can actually
>> interrupt it in the time between loading the overlay and loading the OS,
>> and tell it to load the OS from the floppy.
>> --
>> Jeff Richards
>> MS MVP (Windows - Shell/User)
>> "b11_" <b11@discussions.microsoft.com> wrote in message
>> news:AA62239E-2E28-48FA-ABD9-2804D510DCD4@microsoft.com...
>>> Sometime ago, 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. I beieve that when a drive starts booting
>>> and
>>> then another drive finishes booting then that is called cross booting.
>>> _________________________________________________________
>>> "philo" wrote:
>>>
>>>>
>>>> "b11_" <b11@discussions.microsoft.com> wrote in message
>>>> news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
>>>> > I check the Microsoft website but can not find any article pertaining
>>>> > to
>>>> > cross booting. Your suggestions please.
>>>>
>>>>
>>>> You will get plenty of results on Google if you use the term "Dual
>>>> Booting"
>>>>
>>>> If you want to mention which OS's you want to run...you can also get
>>>> some
>>>> help here.
>>>>
>>>> As a general rule however... each OS should be on it's own
>>>> partition...with
>>>> the oldest OS installed first.
>>>>
>>>>
>>>>
>>
>>
>
>

 

[Gary S. Terhune]

Re: cross booting

Sounds a *bit* like how Win3.1, 95 and 98 load, with MSDOS as the first OS.
Except DOS doesn't stay resident (does it?)

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

"Jeff Richards" <JRichards@msn.com.au> wrote in message
news:uupF94K0HHA.5380@TK2MSFTNGP04.phx.gbl...
> If you move outside the PC world it is quite common for one OS to start
> the boot process and another OS to finish it.
>
> The minicomputers I used to work with had a microprocessor-based I/O
> controller. The boot process started with a boot to an embedded OS (which
> was actually the previous generation 16-bit OS) running on this
> microprocessor. This OS started the basic I/O procedures (including disk)
> and then loaded and started the 32-bit OS on the main CPU. The original
> boot OS then reverted to its job of managing I/O while the OS running on
> the CPU started the CLI and all the higher level services. Both OSes
> were then running simultaneously. It was possible to stop the boot
> process after the 16-bit OS was running and perform tasks such as
> diagnostics or upgrades to the 32-bit OS. At that point it was a standard
> dual-ground single-user 16-bit OS with its own CLI and access to most of
> the I/O. Then, when diagnostics or whatever are finished, the operator
> would issue a CLI command to boot the 32-bit OS, using the I/O services
> provided by the 16-bit OS.
>
> That might not be quite what OP was referring to, but I would certainly
> call it starting the boot with one OS and finishing the boot with a
> different OS.
> --
> Jeff Richards
> MS MVP (Windows - Shell/User)
>
> "Gary S. Terhune" <nobody@nowhere.not> wrote in message
> news:%23gek5aG0HHA.5800@TK2MSFTNGP05.phx.gbl...
>> Still, this does not match the description given. Yes, a boot can be
>> interrupted and another OS booted, but the second OS doesn't "finish" the
>> booting process, it's an entirely new process.
>>
>> --
>> Gary S. Terhune
>> MS-MVP Shell/User
>> www.grystmill.com
>>
>> "Jeff Richards" <JRichards@msn.com.au> wrote in message
>> news:eo7ZfSE0HHA.3400@TK2MSFTNGP03.phx.gbl...
>>> Note that if you are not talking generic Windows machines, then the
>>> process you describe is fairly common. For instance, in embedded systems
>>> it's not unusual for the boot process to load a partition image into
>>> memory and then boot from that image instead of the disk (or ROM device
>>> more usually) from which the boot code was loaded.
>>>
>>> Here's an example:
>>> http://www.patentstorm.us/patents/6996706-description.html
>>>
>>> The only circumstance I can think of where the hard drive boot process
>>> gets restarted with a standard PC is with some drive overlay software.
>>> The first part of the boot loads a BIOS replacement which then takes
>>> over the boot process. In order to do this successfully the overlay
>>> software needs to look as much as possible like the original BIOS boot
>>> code, and to do this it effectively restarts the boot from scratch once
>>> it gets loaded. So if drive 2 has this sort of BIOS overlay software
>>> installed, but it was not expecting to get started from drive 2, and it
>>> didn't understand about BIOS settings that re-assigned the drive order
>>> (or, it replaced the code that responded to those settings), then I
>>> guess what you are describing is a possibility.
>>>
>>> It's a bit like the process that occurs when you want to boot a system
>>> with drive overlay software installed from floppy - you can actually
>>> interrupt it in the time between loading the overlay and loading the OS,
>>> and tell it to load the OS from the floppy.
>>> --
>>> Jeff Richards
>>> MS MVP (Windows - Shell/User)
>>> "b11_" <b11@discussions.microsoft.com> wrote in message
>>> news:AA62239E-2E28-48FA-ABD9-2804D510DCD4@microsoft.com...
>>>> Sometime ago, 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. I beieve that when a drive starts
>>>> booting and
>>>> then another drive finishes booting then that is called cross booting.
>>>> _________________________________________________________
>>>> "philo" wrote:
>>>>
>>>>>
>>>>> "b11_" <b11@discussions.microsoft.com> wrote in message
>>>>> news42BD8D1-1D06-4808-9373-167B61FB2F82@microsoft.com...
>>>>> > I check the Microsoft website but can not find any article
>>>>> > pertaining to
>>>>> > cross booting. Your suggestions please.
>>>>>
>>>>>
>>>>> You will get plenty of results on Google if you use the term "Dual
>>>>> Booting"
>>>>>
>>>>> If you want to mention which OS's you want to run...you can also get
>>>>> some
>>>>> help here.
>>>>>
>>>>> As a general rule however... each OS should be on it's own
>>>>> partition...with
>>>>> the oldest OS installed first.
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>>
>
>

 

[cquirke (MVP Windows shell/user)]

Re: cross booting

On Tue, 24 Jul 2007 16:58:01 -0700, b11_

>I check the Microsoft website but can not find any article pertaining to
>cross booting. Your suggestions please.

Define( cross booting )

Do you mean...
- booting from one OS to another on the same PC
- booting one OS within another on the same PC
- booting one device from another on the PC
- hit keys to make the &%$ thing boot faster
....?



>--------------- ----- ---- --- -- - - -
To one who only has a hammer,
everything looks like a nail
>--------------- ----- ---- --- -- - - -