Pxi dual boot.ini

Below is my boot.ini for a pxi chassis with win200 and win98. I am OK with default as win2000 and maually select win98. However I wish to make win98 the default timeout boot. Any suggestions on what edits will work?
Thanks
Jim
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
C:\="Microsoft Windows 98"

Running Windows 2000 go to Control Panel/System/Advanced/Init and Restore and then change the default operating system.
I have a spanish version of WIN2000, so the menu names may be wrong.

Similar Messages

Convert PXIe-8135 controller to dual-boot Windows 7 and LabVIEW RT

Hello. I have a PXIe-8135 controller that originally was just running Windows 7. We are trying to convert it to a dual boot system to also run LabView Real Time. (There is host computer that will run LabVIEW 2014 with the RT module, and the controller will become a target).
I have created a FAT32 partition on the hard drive of the controller. Now, I’m trying to install the real-time OS with a USB flash drive made using the MAX utility, but I cannot boot using the USB drive for some reason. I keep getting the message “waiting for USB device to initialize”.
In BIOS, legacy USB support is [ENABLED] and boot configuration is set to [Windows/other OS]. I’ve tried removing the drive, waiting, and reinserting. I’ve tried two different USB drives (both 8 GB, different brands).
I’m not sure what to do next. Apart from the USB boot issue, is converting the PXIe-8135 even possible? I read about SATA/PATA hard drive issues with older controllers, but I don't know about this one.
Thanks, in advance, for your help!
-Jeff
Solved!
Go to Solution.

Per Siana's licensing comment, more information on purchasing a deployment license if you do not have one for this target can be found here.
The RT Utility USB key is used to set up non-NI hardware with LabVIEW Real-Time, but you should not need it in this situation to convert to dual-boot (*). Try this:
1. Since you already have a FAT32 partion created, go into BIOS setup and change to booting 'LabVIEW RT'.
2. The system will attempt to boot LabVIEW RT, see that the partition is empty, and switch over into LabVIEW RT Safe Mode. (this safemode is built into the firmware, which is why you don't really need the USB key).
3. The system should come up correctly and be detectable from MAX, and you can proceed with installing software.
4. To switch back to Windows, go back to BIOS setup and choose 'Windows/Other OS'
(*) One area where the USB key is helpful on a dual boot system is with formatting the disk. If you want to convert from FAT32 to Reliance on the partition designated for LabVIEW RT, the USB key lets you attempt to format a single parition and leave the rest of the disk untouched. If you format from MAX, the standard behavior is to format only one RT partition if found, but if not found, it will format the entire disk. Formatting from MAX on a dual boot system is consequently riskier and you could lose your Windows partition.

Dual-boot LabVIEW RT/Windows 2000 on PXI

Is it possible to configure a PXI-based embedded PC (NI 8176) to run both LabVIEW RT and Windows 2000 in a dual-boot setup? I would like to use the same PXI system to do both real-time system prototyping as well as finished product testing - though not at the same time, of course.

Hi André,
Just to clarify, all dual-boot systems use the same hard drive for both operating systems. The floppy drive is used only for configuration. If you do not have a floppy drive, you can use a USB CD-ROM drive to load the recovery CD that ships with the controller. Please note that using the recovery CD may result in the loss of data from the previous Windows-only configuration. All of the important files should be backed-up prior to any recovery. For a better idea of what specific steps are involved, you can check out the following link:
http://digital.ni.com/public.nsf/websearch/227CF36870DB7BDB86256F790057F20F?OpenDocument
In particular, the section at the bottom goes through the process of converting to a dual-boot controller.
David H.
Applications Engineer
National Instruments
David H.
Systems Engineer
National Instruments

How to implement a dual booting PXI system using windows 7 and labview RT

Good Day
My name is Mariano Ocana from the University of Manitoba, and I want to implement a dual system using windows 7 and labview RT in a PXIe-1082 chassis with a PXIe-8102 embedded controlled (the chassis came with windows 7 installed). What are the steps to use both systems (windows and RT) in the same chassis?, in the NI help comes an example implementing a dual system using windows xp and RT, it is the same procedure?.
Thank you in advance for all your help.
Regards
M. Ocana

Greetings, Mariano.
The real issue you have to contend with is whether or not you have a LabVIEW RT license. If the 8102 controller was purchased Windows-Only, you likely do not have a license to run LabVIEW RT on the controller - you can purchase one, I think it's about $500, and at that point you can request a LabVIEW RT Configuration CD (that's not what it's called, but the sales guy will know what I'm talking about). The Config CD is a CD that will partition your controller correctly with both FAT32 and NTFS filesystems (in the appropriate way) to allow you to run Windows 7 and LabVIEW Real-Time on the controller correctly. Once done, you can then switch within the BIOS between LabVIEW Real-Time and Windows in order to dual-boot.
Either way, you likely need to contact NI sales to either purchase an RT license (if one was not received at the time of purchase) or to request a Configuration CD (it might also be called a dual-boot install CD or similar).
-Danny

Advantages and Disadvantages of Dual booting Windows on PXI Device

Hello,
In solving my previous problem of running a DLL in RTOS I've stumbled upon another solution. But i wanted to know the pros and cons of this before i make the leap.
I want to install windows on the PXI device so that the NHR DLL files are run inherently on the windows kernel and i have access over my DAQ devices without placing them in the remote target.
What are the advantages and disadvantages of installing a windows only on the DAQ device and running all my operation from it. Do i loose my real time features? I dont know, I'm really new to LabView and may sound really dumb. Please excuse my lack of knowledge.
With Regards,
Khalid.

Hello Bob,
Thank you for your insightful answer. I also thought this might happen, loosing all the RT features.
I have another question for you. If i use a RT variant of windows like "Windows Embedded 8", will this make any difference? Can i regain my RT features by it or i have to go with the LabView RTOS.
I'm pushing towards a windows system because i have to run this DLL file from NHR which is not supported by the LabView RTOS.
Moreover, I could just install just windows onto the PXI controller. I'm not being able to make it dual boot. Can you guide me towards proper guideline to do so? I looked at the knowledge base file about dual booting, but the instructions dont exactly match with my available options in BIOS setup.
Any suggestions from anyone is much appreciated.
With Regards,
Khalid.

Dual Boot 32 and 64 Bit Xp Pro - boot.ini changes

Well I am up and running both 32 Bit and 64 Bit XP Pro and initially 64 Bit has a few lags up on me. System is as follows
MSI K8N Neo4 Plat with AMD Athlon 64 3000, 2 X Corsair 512-3200C2PT (1GB RAM), Western Digital WD2500JD Caviar SE, WD360 Raptor, WD2500BB Caviar, Seagate ST3300831A, Plextor 712A & 716A, Samsung 816A, ATI X600 All-in-Wonder with 256MB RAM, Sound Blaster Audigy 2 ZS.
I used the 32bit drivers provided on a disk and for 64 Bit I was able to get ATI, nVidia, and that is all. Bot 32bit and 64 bit are working well. On several occasions more often than not. i have to edit the boot.ini to add back in the 64 bit option. Why? I can not link the deletion to anything specific. Now if it is supposed to delete to option that woul dbe a new one.
Any thoughts?

Did you write the initial boot.ini file or is it one that Windows automatically wrote for you? Are the two OS's on the same HDD or on different HDD's? Which OS did you install last?
The Windows written boot.ini has always worked fine for me. If you installed Win 64 first and then Win 32, that could cause problems.

Dual boot enviorment on primary IDE channel Diamond Plus tried everything!!

Whats up everybody? For some reason I am unable to achieve a dual boot enviorment on my primary IDE channel! I have tried numerous things and for the life of me I cant get it to work! I just bout a new Hitachi 250 gb ultra ata 133 drive and it works great I formatted it by itself with no other drives present and ony one of my optical drives hooked up. Runs great but as soon as I hook up my Hitachi 160 gb ata100 drive and try to boot from the 160 gb drive I get a message that states windows cannot complete youre request the boot ini file is missing or corrupt! So I reformatted that drive with the same proceedure with complete success loaded all of my drivers and updates made sure everthing was fine double checked my bios settings powered down and hooked everything back up the new 250 gb Hitachi is faster so it is allocated as the master on the cable in relation with jumper settings and the 160 gb ATA100 Hitachi Drive is of course set on the slave hook up with cable and jumpers. What gives???? I have 2 western Digital Sata 2 drives in raid 0 and I can get them to boot in a multiboot enviorment!!!!! Is anyone else haveing this kind of problem with IDE drives? Is this a protocol developed by mother board manurefacturers too phase out PATA DRIVES? Please if anyone else is have this problem respond to this post.
Brother Esau

Hi, Bas
I have tried doing that and I get the same thing when I originally got the new Hitachi drive I put that on master and put the other one on slave already formatted does shiffting the c:\ drive to slave make that kind of impact? Also why is the formatte process for sata successful and the IDE is not? Its recommended on these forums that every time you ad a os you should remove all drives that has windows already installed ,does that apply only to sata drives?

Dual boot windows from USB via grub?

HI all:
I recently had a motherboard failure on an existing PC on which I dual-booted Windows XP and Gentoo. I replaced that box with a new HP PC preloaded with Vista. Wiped that immediately, and installed ARCH. But, I would like to also boot XP, and, since my old hard drive is still OK (I have it in an external USB adapter), I was thinking that I might configure grub to point at an external USB drive like this:
# Windows XP
title Windows XP
root (hd1,0)
makeactive
chainloader +1
where "hd1" (I hope) would point at my old drive, now connected via USB. In this way, I am really booting from my HDD (where grub lives), but "chain loading" from my USB external. Can this work??
-dvh

dvh wrote:
I configured as shown in the wiki, but when I try to boot XP, I get a message that says something to the effect of "missing or corrupted <windows root>\system32\ntoskrnl.exe". I checked the disk and it seems to be there and OK. I get the feeling that it is either NOT finding the hard disk (or partition) or it cannot interpret the NTFS file system (but grub was able to boot this before,...). So, two questions...
1) how do I know what the designator for the external USB hard disk will be? I have speculated that grub will find it at "hd1", but maybe not?
2) does the target disk NEED a windows boot loader? as I said earlier, I used to dual boot it, so there is a grub loader on that disk also.
...ok, three questions...
3) anything else that I should consider??
Thanks again for any help.
-dvh
1) i don'tknow a way to check this, but the
missing or corrupted <windows root>\system32\ntoskrnl.exe message comes from the windows boot process,
so it seems grub is configured correctly.
The main problem is that BOTH grub and windows boot need to have the correct settings.
Windows takes the settings for boot from the boot.ini file in the root of C:\ , and that probably needs to be changed.
You will need some way to get read/write access to the windows C-drive partition.
Install ntfs-3g in archlinux (see NTFS_Write_Support ) and post the contents of boot.ini .

Deleting dual boot OS

i only found one post that was somewhat applicable to my issue of removing a dual boot (http://forums.lenovo.com/t5/ThinkStation/Thinkstation-E20-Dual-boot-from-Windows-7-into-XP/m-p/21871... and that led me on a merry chase. if this is useful to anyone else, great - if posting a solution as an FYI is inappropriate and i should wait to reply to someone with the same issue, pls let me know
the situation: my former IT guys installed W7 Pro x64 (thx, Lenovo, for the free upgrade from Vist Business ) on a new partition alongside XP Pro x32 and it worked great, but i only kept using XP for my !@#$%^ genius scanner, which i have never gotten to run under XP Mode/Virtual PC in W7.
one day, after several months of XP inactivity, i decided to boot into it for some reason and had a BSOD. so then i set out to just eradicate the offending OS and its partition...simple, right? not in this case. i found the guys had put the W7 OS onto a logical drive not a primary:
Local Disk (C
156.71 GB NTFS
Healthy (Boot, Page File, Crash Dump, Logical Drive)
my boot.ini was on the XP partition and W7 uses bootmgr so i poked around and found that EasyBCD should take care of the issue by copying the boot.ini info to bootmgr on C:\ through this link in the SevenForums:
http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html
again, not so easy. i could not move the bootmgr because of the logical status of the partition and also because the partition wasn't set to active; i converted the partition to active with no troubles under the native Disk Managment but failed when i tried to convert the partition to primary.i feared having to do a wipe and reinstall to tidy up as i saw some (forums unnamed) folks advocating.
i looked into it a bit further and found that i needed to use use a partition tool from bootable media (i used a CD with EaseUS Partition Master - the freeware version ) to convert to primary at boot and then i used the above link to copy the bootmgr to C:\ with EasyBCD
now my OS drive looks like so (the partition is large owing to the GIS files that like living there):
Local Disk (C
226.71 GB NTFS
Healthy (System, Boot, Page File, Active, Crash Dump, Primary Partition)
that solved the problem of the W7 OS being on an inactive, logical drive instead of an active primary - and in future if i set up a dual boot for any other OS, i'll make sure the disk is set as primary before i install and the backwater IT guys here will never touch my machine again
S10 - 642327A

HI Manish_5
"Is it possible to role back to my previous Windows 7 in future" but you have to create now the backup (recovery disk) to later use:
Creating Recovery Discs or Saving a Recovery Image to a USB Flash Drive (Windows 7) | HP® Support
Rollback:
Performing an HP system recovery (Windows 7)

Dual boot issues

I've been attempting to get up to speed on labview, labview RT, the PXI (8106), and getting the PXI to dual boot labview RT and windows XP. Question here is only about dual booting. I have the PXI set up with a fat32 partition physically before (C the NTFS partition that windows XP is installed on (E. I installed windows, worked great. I then tried to boot in to labview RT/communicate with the PXI (booting into RT using the bios software switch). No dice since no RT software was installed. So I used a USB memory stick and the software from MAX to install RT on to the PXI. Worked, I can communicate with the PXI, awesome. Today I wanted to boot back in to windows. Go in to the bios, set it to boot windows/other OS . . . and it boots in to labview RT. Dammit. What did I do wrong? What can I do to correct this? Please tell me I don't have to re-do the windows install. It will be my fourth time and installing all that NI software takes a painful amount of time!
Thanks,
Chris

If you attempt to fix your master boot record, here's a couple other things to keep in mind:
1. When you used the RT USB key, did you select the Format option to only update the 1st available partition or format the entire disk? Gerardo's suggested approach will of course only work if you did the former.
2. If you don't have any success with FixMBR since it is a slightly more complicated disk configuration with two partitions, there is another approach you can try if you meet the following requirements:
(a) You originally set up two partition configuration on your disk with the NI OS Recovery media
(b) You have another disk of the exact same type that you are willing and able to erase.
(c) You only did the partital format of the original drive from the RT USB key (see item #1 above)
(d) You have a bootable USB key (see note below)
If so, you could do the following:
1. Put the 2nd disk on your PXI-8106
2. Run the OS installer, and configure it exactly as you did with the first disk.
3. You should now have a disk with a master boot record that exactly matches the one you'd like on your original controller.
4. Boot to DOS from your USB key and run MBRWizard to save a copy of the master boot record (http://mbrwizard.com)
5. Put the original disk back on your PXI-8106, boot to DOS again, and run MBRWizard to restore that saved MBR file to update the master boot record on the original disk.
It sounds pretty involved but really can be done in a few minutes because for step 2 -you don't need to fully install the OS. We're only interested in getting a copy of the master boot record, which is one of the first things that the installer will configure. Once you see the installer copying files to the disk, you can stop the system and proceed to step 3.
Note on DOS-bootable USB key: If you don't have a DOS-bootable USB key, there is a variety of ways to set one up but a relatively easy one is to grab this disk diagnostic tool from NI: Fujitsu Disk Diagnostic. Careful, once you run the tool, IT WILL ERASE YOUR ENTIRE USB KEY. Technically it is for setting up a disk diagnostic, but you should be able to copy the mbr wizard tool to the key and also run that from DOS. Delete the autoexec.bat file that gets created on the USB key to prevent the Fujitsu tool from running automatically. You could for example re-use the RT USB key you previously configured, although it will be wiped and new files put on it.
Last thing: If you don't have a second drive available, please post the exact details on the drive you do have and the specifics on how you originally partitioned the drive (what tools, what partition sizes). I might be able to help you out and create the MBR file for you, so you would only need to worry about step 5 above (and setting up a DOS bootable USB key).
Cheers,
Josh

Convert dual boot to RT

Hello all,
Does anyone know if it is possible to convert a dual-boot controller to RT only? I have a hard disk that just died and to simplify things I would like to install RT only on the new drive as we are moving over to RT only. The PXI controller (8110) ships with backup software, but you have to install both Windows and the RT OS if using this. Any thoughts are appreciated.
Thanks, Matt
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC
Solved!
Go to Solution.

Hi Matt,
Sorry for the lack of clarity. Here are the steps to follow.
1. Boot controller into RT Safe Mode. In the left pane in MAX, right-click the target and select "Format Disk."
2. After completion, reboot controller into LabVIEW RT. In MAX, the target should appear in its default state, without any user-defined settings or parameters.
3. Expand the target in the left pane of MAX, and right-click the item labeled "Software." The only option that will appear is "Add/Remove Software." Selecting this item will launch the RT Software Installation wizard, which will walk you through installing the necessary software on the target.
Let me know if you have any other questions, and have a Happy Thanksgiving!
Andy H.
National Instruments

Win XP/Win 7 dual boot question and

My replacement motherboard for my crapped out Dell one that was a replacement, crapped out the other week and it was tested with a new power supply to no avail. it was also tested in a shortcut, (connecting the two wires directly, the two that "short out" that turns on the power) and that didnt work either.. (something like that)
My options are:
buy another replacment motherboard and hope it stays working longer than the six months the other did
Buy a new computer and use my old hard drive
thus arising this question:
since the new computer will have Windows 7 on it, can I use that as a slave drive and use my primary drive (not going to loose my data and stuff) I have the primary drive as XP but the new one will use 7, when I put in the win 7 drive as a slave drive, will it boot to 7 or XP and would I have the option to dual boot, even if they are seperate drives..
I think I am writing it a confusing way but I hope you can understand what I am getting at....
Simply put--
I have XP drive
I buy new computer it has Win 7 drive
Xp drive becomes master, win 7 becomes slave
Will XP boot or Win 7 boot when its set as the slave drive? what about XP/7 dual boot? they are on seperate drives, will it let me dual boot?
I want my XP drive to boot.
I hope you can understand that..
If I can, I would like to reformat the win7 drive and just use that for storage. is that possioble?
Ethan
I just want some help or even an opinion, is that so hard to ask for?

Okay I read through your post a few times and I am still a bit confused about what your setup looks like. I am going to assume you bought a new computer with Windows 7 on it thus you DID NOT replace the motherboard on the old one. With that assumption, then your answer would be no, only Windows 7 would boot (and it might have some problems if you have it set as the slave drive). Windows XP from your old hard drive would not boot because simply put, the BIOS will not detect a proper boot.ini file and the hardware configuration (partitions and/or disk types) does not match up.
If you want to set up a dual boot, you would have to install the secondary hard drive (or partition the primary one) and perform a destructive OS restore on it AND find the drivers for it (if the manufacturer of the computer even supports it). When I used to work for the Geek Squad, numerous clients asked about this and the general consensus was that the Geek Squad strongly opposed it because of the drivers. Being that XP and 7 are a generation apart, the chances of the manufacturer of the computer or motherboard releasing drivers for both was unlikely. Sometimes the client would opt to have it done anyway but my former Precinct would always warn them that some features may not work correctly.
If you want Windows XP and Windows 7, I suggest the XP Mode that Windows Pro and Ultimate offers. You literally run Windows XP inside a window of Windows 7.
I DO NOT work for Best Buy. Whatever I post are just educated guesses or common sense.

Portege R500: XP - Vista Dual Boot

After much struggling I have R500 XP Vista Dual Boot working fine.
I bought the R500 with Vista but found it not so good for real use.
Microsoft have announced that you can go back to XP if you have a Vista Business licence - but Toshiba won't as yet supply an install CD.
I decided to set up a dual boot with another XPPro licence rather than do a reinstall. Many of my problems would apply equally to a straight XP reinstall.
You need to shrink the Vista and/or data partitions to create space for a new primary partition, and then boot from an XP disk to install it in the new partition.
When you do the XP install you'll get a blue scren crash before you get to the screen asking where you want to install because the XP CD doesn't have a sata driver for the hard disk unless you slipstream the OS to include the right driver, or use F6 to load the drivers you need.
You need the Intel Matrix drivers - available from their website - here
http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2800&OS FullName=Windows*+XP+Professional&lang=eng&strOSs= 44&submit=Go%21
and you need Item 7 which you put on a usb floppy to use when you press F6.
But watch out - when the XP Install shows you a choice of your special controllers and you have to choose one - there seem to be about 4 in the list. I had no idea which to choose. In fact the list scrolls and the one you want is 82801GBM SATA AHCI (mobile) which is near the bottom of the list. if you choose the wrong one the process will end with a blue screen 0007B Stop crash.
With the correct driver XP installs fine. Then when you reboot Vista appears to have gone (although it hasn't and you can see the Vista drive and files from within XP). The problem is that XP overwrote the Vista boot file so you need to repair Vista.
The way to fix this is to use a Vista boot CD, get past the first screen, select Repair, select Command prompt, and then at the command prompt, type:
bootrec.exe /fixMBR
and then
bootrec.exe /fixBoot
then exit and reboot.
Vista will then work, but XP will have gone!
then you need a utility to help you modify the Vista boot record - I used EasyBCD (readily available on the web) having failed with Acronis OS Loader.
One other problem - I had a "missing hal.dll" message which stopped XP installing as well. This was because the partition number in the boot.ini file it built was wrong - for me the correct number was 3. As XP had failed to installat hat stage I could get into Vista and use notebook to edit boot.ini
Once I had both systems booting I could bring XP up to date and load the Toshiba drivers. Once all the Toshiba drivers had been installed the system tree had no yellow warnings and everything seems to work OK.
The whole process is well documented on the web but the points I've highlighted here were not or caused me particular grief and took much trial and error and reseach to work out and when I called them last week some of these points were not apparently known to and were certainly not solved by Toshiba UK support.
I now have a satisfactory dual boot - XP is much better for me than Vista - and I will revert to Vista if and when the service packs etc mean that it seems to have adequate performance.
I hope Toshiba will document this process properly and publish the results and supply an easy way of getting the files you need in one operation rather than having to download each bit separately.
Good luck!

Hi Richard
Thank you very much for this interesting posting.
I think its useful and many users appreciate your information.
Best regards

Dual-boot Kubuntu and XP with RnR

Hi
I'm trying to dual-boot windows XP and kubuntu 9.10 and I think it makes sense to separate the so called boot and system partition in windows' term (i.e. having \Windows on one partition and the boot.ini, ntldr stuff on another)... But I can't figure out how to separate them...
Since I'm dual-boot I am aware XP should be installed first...what I did was installed it onto the second partition while at the partition screen in the XP install and left a smaller NTFS partition as the first one on the list. Not sure if that would cause the boot and the system to separate...(it seem so since the boot-related file is on C:\ while the Windows directory is on D:\)
However I install RnR on this Windows and tried to boot into the RnR workspace through the Think button but it notes NTLDR is missing...Windows still boot normally on startup (to me the workspace was probably not installed to the right place perhaps? ; shouldn't it be in like a new service partition called S:\ or something? maybe it got installed into C:\) I read somewhere that RnR workspace has it's own bootloader and write into the MBR or something...
since I'll also be installing kubuntu the bootloader will surely get messed up again by Grub...so that might completely screw up everything on Windows side...
I have no idea what to do to make kubuntu, windows, and RnR all compatible with each other...
I'm not very familiar with booting and disk management but any help would be appreciated...

sry i did not meant to emphasize on installation of kubuntu...my thread got moved here becuase the mod thought I was talking about how to install kubuntu....
i really don't want to complicate thing by installing kubuntu inside windows... because my windows frequently die on me...i prefer them to be separate and interact only at the boot level in a separate "boot partition (windows' term: system partition)
this is really about RnR and Windows...the kubuntu install was only a byproduct that I thought might mess thing up even more since it replace the boot loader upon install
so first thing first: my RnR cannot boot into its own service partition (think button f11); say something about ntldr is missing, however XP still boot fine....it seem like when I install XP it split the boot and the other file into two partition because I chose the second partition on the list during the install, and the boot files got put into the first partition (C:\) and when I install RnR it seem to used C:\ as the service partition (i assume that the service partition is related to RnR?). But since file such is ntldr in C:\ is XP'sm I guess it didn't get overwritten by RnR?
Basically the main issue at the moment is I can't get the service partition to work with Windows...i guess kubuntu can come later...

Dual boot with WinXp and Arch-Solved

Hi friends,
I was using windows boot loader to boot into arch instead of grub. I used this:
dd if=/dev/hda7 of=arch.lnx bs=512 count=1
to get the first 512 bytes of the partition in which I installed arch and then added a line directing towards arch.lnx (moved to windows partition) in boot.ini. But now after reinstalling arch, when i do the same to get first 512 bytes of the partition, it generates a blank file and hence using that I'm not able to boot into arch. Grub is installed in this partition only. Any hints about this issue.
EDIT: I dont know what was the problem exactly, but after I reinstalled grub by "grub-install /dev/hda7" and then did the above command, it worked fine.

moderator comment: This is a question on Kubuntu installation but it seems to me OP specifically wants to know how to set up his partitions without harming Arch. As long as the discussion remains about Arch Linux this thread can stay. I'm going to have to move this from Installation to Newbie Corner.
Annorax wrote:I assure you that I am doing my own research. I am new to Linux and new to dual booting and was just looking for some pointers and a place to start reading.
Please see this. I advise you to read the links 2ManyDogs gave. You also need to give us more information about your partitions, such as what is mounted where. I suspect you only have primary partitions and will need to convert one into an extended partition.

Pxi dual boot.ini

Similar Messages

Maybe you are looking for