09-17-2001
multiboot
problem with multibooting
Ever since my new harddisk I encounter many problems creating an multiboot enviroment.
This is the problem:
First I installed win98, secondly win-nt server, third win2k server.
Before installing win2k u have to use sp5 on win-nt, otherwise it is not possible to install win2k.
So I did.
What happened is that win2k had removed the bootsector of win-nt.
Than I had to face a problem, which is the os is removed, but not the bootsector.
My question:
1st, How do I remove that bootsector of both the systems, win-nt and win2k, for re-installing these os.
2nd, why is installing several os on one disk giving now that much problems, I never had this before.
What did I do wrong or what did I overlooked?
With regards, Mario
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have installed Win98 OS .......1st
then RH7.2
with GRUB bootloader okay
i.e in the Grub there is two choices 1-Linux
2-Dos
also I install bootloader of linux in MBR -master boot record-
when select Linux an error :
... (6 Replies)
Discussion started by: atiato
6 Replies
2. UNIX for Advanced & Expert Users
Hi there,
Can I install on the same Ultra10/Ultra60 machine 2 diferrent OS
Solaris8/9 and Linux(any version that would be possible) and choose the appropriate one at boot time ?
Have anyone done this ?
thnx,
GISMO (1 Reply)
Discussion started by: Gismo
1 Replies
3. UNIX for Dummies Questions & Answers
hi ... thanx for the advice last time ....
i have another query ....
now that i haf installed red hat linux version 9 i think ....i have allocated a free space to load windows.... but during windows xp installation ,
it does not recognise the free space to be userable for installing of the winxp... (1 Reply)
Discussion started by: kaya
1 Replies
4. Red Hat
Hello,
I have a multi-boot system with windows and openSuse. The boot loader is from Suse and the menu worked fine. Today I installed Scientific Linux and am having trouble with the boot loader. The SL install is on a different drive than the windows and Suse. As is typical, the SL installer has... (3 Replies)
Discussion started by: LMHmedchem
3 Replies
5. Solaris
Hi
Just want to share....
Multiboot: winlinsos; June 2016
Lenovo x230, 4GB - No internal DVD driver
I have
# fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O... (0 Replies)
Discussion started by: van12
0 Replies
6. UNIX for Beginners Questions & Answers
I want to install Slackware 14.2, FreeBSD and Solaris 10 on a p4 machine but multiboot is not working as lilo overwrites grub and btx boot loader can't detect others. I had to boot slackware and Solaris with the installation disc for a good number of times. I installed all boot loaders on MBR. The... (0 Replies)
Discussion started by: vectrum
0 Replies
7. UNIX for Beginners Questions & Answers
I want to install Slackware 14.2, FreeBSD and Solaris 10 on a p4 machine but multiboot is not working as lilo overwrites grub and btx boot loader can't detect others. I had to boot slackware and Solaris with the installation disc for a good number of times. I installed all boot loaders on MBR. The... (3 Replies)
Discussion started by: harveyclayton
3 Replies
WIPE(1) LAM TOOLS WIPE(1)
NAME
wipe - Shutdown LAM.
SYNTAX
wipe [-bdhv] [-n <#>] [<bhost>]
OPTIONS
-b Assume local and remote shell are the same. This means that only one remote shell invocation is used to each node. If -b is
not used, two remote shell invocations are used to each node.
-d Turn on debugging mode. This implies -v.
-h Print the command help menu.
-v Be verbose.
-n <#> Wipe only the first <#> nodes.
DESCRIPTION
This command has been deprecated in favor of the lamhalt command. wipe should only be necessary if lamhalt fails and is unable to clean up
the LAM run-time environment properly. The wipe tool terminates the LAM software on each of the machines specified in the boot schema,
<bhost>. wipe is the topology tool that terminates LAM on the UNIX(tm) nodes of a multicomputer system. It invokes tkill(1) on each
machine. See tkill(1) for a description of how LAM is terminated on each node.
The <bhost> file is a LAM boot schema written in the host file syntax. CPU counts in the boot schema are ignored by wipe. See bhost(5).
Instead of the command line, a boot schema can be specified in the LAMBHOST environment variable. Otherwise a default file, bhost.def, is
used. LAM searches for <bhost> first in the local directory and then in the installation directory under etc/.
wipe does not quit if a particular remote node cannot be reached or if tkill(1) fails on any node. A message is printed if either of these
failures occur, in which case the user should investigate the cause of failure and, if necessary, terminate LAM by manually executing
tkill(1) on the problem node(s). In extreme cases, the user may have to terminate individual LAM processes with kill(1).
wipe will terminate after a limited number of nodes if the -n option is given. This is mainly intended for use by lamboot(1), which
invokes wipe when a boot does not successfully complete.
EXAMPLES
wipe -v mynodes
Shutdown LAM on the machines described in the boot schema, mynodes. Report about important steps as they are done.
FILES
$LAMHOME/etc/lam-bhost.def default boot schema file
SEE ALSO
recon(1), lamboot(1), tkill(1), bhost(5), lam-helpfile(5)
LAM 6.5.8 November, 2002 WIPE(1)