• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
brenryan

Multiboot USB issues

30 posts in this topic

How would you force such a background-OS not getting aborted as soon as some other environment gets chain-loaded? Let's say you boot-linux and call BartsPE, using grub. I suggest bartspe would just hard-reset linux as soon as it's graphical interfaces pops up. However you need to keep the network-connection in background, when bartspe-iso is streamed from a NAS.

0

Share this post


Link to post
Share on other sites

How would you force such a background-OS not getting aborted as soon as some other environment gets chain-loaded? Let's say you boot-linux and call BartsPE, using grub. I suggest bartspe would just hard-reset linux as soon as it's graphical interfaces pops up. However you need to keep the network-connection in background, when bartspe-iso is streamed from a NAS.

Booting Linux to boot a BartPE from the network makes no sense, you can boot the BartPE locally instead of the Linux (though you can use the Linux to download *something* from the network, store it in a RAM area and then boot the *whatever* is in this RAM area).

We were talking of installing a NT based OS.

As said, the procedure in this case would be to make (which is BTW "good" practice) a "local" copy of the install files (still if we are talking of NT/2K/XP/2003, later systems may differ).

A minimal PE can access a "network drive" just fine, and a tool like WINNTSETUP:

http://www.msfn.org/board/topic/149612-winntsetup-v33-v34-beta-1/

should work fine using as "source" a network drive.

jaclaz

0

Share this post


Link to post
Share on other sites

You just wrote:

But again, most probably they do exist, in the form of a (minimal) OS, i.e. a PE or a Linux that can boot locally and access the (wi-fi) network.

Now you tell me:

Booting Linux to boot a BartPE from the network makes no sense,

It doesn't matter if booting BartPE makes sense or not. Problem is always the same: On a NAS, holding several Isos (e.g. WinXP, BartPE, PartedMagic, Ubuntu, Win7, Antivir-disk and whatever-else) none of them can be booted from a miniOS since they're all not be able to continue running from RAMDisk or holding the network-connection the miniOS created. As soon as a new OS-environment is loaded, all pre-configurations are forgotten. Exception is firadisk, though it's only for ramdisks.

The "good practice" you describe is very slow and not usefull for DVD-Isos. Only new computers have 4GB RAM or more. Loading/transferring-time was unbearable with pre-loading such an iso.

0

Share this post


Link to post
Share on other sites

Well,

a good practice is a "good practice".

In the case of deciding to have not a PXE server (not a WinAoE, nor a iScsi one) in the network it becomes "only possible practice".

jaclaz

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.