I just installed fedora 2, the fedora 3 anaconda would crash when it looked at my partitions, put in 2.6.9, then updated last night to 2.6.10.... I have fat32 and ntfs partitions, w98 and w2k installed but oopsie, i told it to put the boot loader on main disk and w2k won't load. tried to mount them and doesn't know about ntfs. How do I add ntfs support to kernel or restore the windoze boot loader to "C:"?
Gentlemen: I have a second issue. I need to use swig version 1.3.22 and my FC3 system has 1.3.21, just one version behind.
Using "yum upgrade" or "yum update" doesnt update swig.
Is there any "yum" method to get swig version 1.3.22 into my FC3 system?
By the way, all of this is in preparation for compiling the new gnuradio software for the SDR (Software Defined Radio) whose new USRP hardware is just being released.
Charles
Ron Watson wrote:
I just installed fedora 2, the fedora 3 anaconda would crash when it looked at my partitions, put in 2.6.9, then updated last night to 2.6.10.... I have fat32 and ntfs partitions, w98 and w2k installed but oopsie, i told it to put the boot loader on main disk and w2k won't load. tried to mount them and doesn't know about ntfs. How do I add ntfs support to kernel or restore the windoze boot loader to "C:"?
Well, it is relatively easy to restore the Win2K boot loader. You just need its installation disc, then you boot from it into recovery console and fixboot fixmbr should do the trick. However then you will need to reinstall your grub through recovery disc, and I suggest you to search through the posts here as the problem of dual (and even triple) boot was discussed several times. Good luck, Maxim.
Maxim Eremeev wrote:
Ron Watson wrote:
I just installed fedora 2, the fedora 3 anaconda would crash when it looked at my partitions, put in 2.6.9, then updated last night to 2.6.10.... I have fat32 and ntfs partitions, w98 and w2k installed but oopsie, i told it to put the boot loader on main disk and w2k won't load. tried to mount them and doesn't know about ntfs. How do I add ntfs support to kernel or restore the windoze boot loader to "C:"?
Well, it is relatively easy to restore the Win2K boot loader. You just need its installation disc, then you boot from it into recovery console and fixboot fixmbr should do the trick. However then you will need to reinstall your grub through recovery disc, and I suggest you to search through the posts here as the problem of dual (and even triple) boot was discussed several times. Good luck, Maxim.
Thanks, will make a recovery disk, test it, try to get w2k back up, get linux back up. As for ntfs support... went to /boot/config-2.6.10-1.9_FC2 and it says auto generated... auto generated by what? Noticed it does not set ntfs support, e.g.
# CONFIG_NTFS_FS is not set
so is it "safe" to add
CONFIG_NTFS_FS=y
to the config file, will it just get overwritten at next boot, or what?
Ron;
Ron Watson kirjoitti viestissään (lähetysaika lauantai, 29. tammikuuta 2005 23:56):
As for ntfs support... went to /boot/config-2.6.10-1.9_FC2 and it says auto generated... auto generated by what?
The kernel configuration program.
Noticed it does not set ntfs support, e.g.
# CONFIG_NTFS_FS is not set
so is it "safe" to add
CONFIG_NTFS_FS=y
to the config file, will it just get overwritten at next boot, or what?
It's safe, but it won't change anything if you don't recompile the kernel with the new config file.
Markku Kolkka wrote: <snip>
It's safe, but it won't change anything if you don't recompile the kernel with the new config file.
Ah, well if I need to do that, I suppose I should just build FC3 while I'm at it. Excuse me, I come from Suns, just getting started with Linux, not used to all this automated help and config stuff. Basically, go to the source, uncompress, check and set config --with-this and --without-that, ./configure, make all, make install, reboot into new kernel?
Ron;
On Sat, 29 Jan 2005 16:56:25 -0500, Ron Watson res1eiyi@verizon.net wrote:
Maxim Eremeev wrote:
Ron Watson wrote:
I just installed fedora 2, the fedora 3 anaconda would crash when it looked at my partitions, put in 2.6.9, then updated last night to 2.6.10.... I have fat32 and ntfs partitions, w98 and w2k installed but oopsie, i told it to put the boot loader on main disk and w2k won't load. tried to mount them and doesn't know about ntfs. How do I add ntfs support to kernel or restore the windoze boot loader to "C:"?
Well, it is relatively easy to restore the Win2K boot loader. You just need its installation disc, then you boot from it into recovery console and fixboot fixmbr should do the trick. However then you will need to reinstall your grub through recovery disc, and I suggest you to search through the posts here as the problem of dual (and even triple) boot was discussed several times. Good luck, Maxim.
Thanks, will make a recovery disk, test it, try to get w2k back up, get linux back up. As for ntfs support... went to /boot/config-2.6.10-1.9_FC2 and it says auto generated... auto generated by what? Noticed it does not set ntfs support, e.g.
# CONFIG_NTFS_FS is not set
so is it "safe" to add
CONFIG_NTFS_FS=y
to the config file, will it just get overwritten at next boot, or what?
Ron;
Sure you can change it, but it won't do anything. You can either change it and then recompile your kernel or you can go the easy route and go to the great http://linux-ntfs.sourceforge.net/ website and download the kernel module rpm and install it. Then you can mount your NTFS drive. You may not have to restore the Win2k boot loader to get things fixed. You probably just need to configure GRUB to chainload Windows. If you installed GRUB to the MBR of the main disk, this is what you want. You can then tell GRUB about the Windows installs and it can get them booting too. The installer should have done something like this for you. Do you have an "Other" boot option? When the GRUB screen comes up, press a key and you should see a list of systems to boot. I suggest you look around in the archives and on Google for stuff about dual booting so that you can understand what you want to do. If you get stuck with something, then shoot another email at the list.
Jonathan
On Mon, 2005-01-31 at 00:06 -0500, Ron Watson wrote:
The W2k bootloader that comes up doesn't show anything but Win98 and Win2k for options. I can't figure out where they're storing this info, there doesn't seem to be BOOT.INI, it's not in the registry, duh. The only file in the whole system with the string "/fastdetect" is ntldr.
boot.ini is a hidden file in the root directory of the partition the bootloader is installed into, usually C:\
You'll need to turn on the option in Explorer to "View Hidden and System Files" to see it.
Paul.
On Mon, 2005-01-31 at 22:53 -0500, Ron Watson wrote:
Tried that, it still wasn't there. It's a mystery....
Ron;
Paul Howarth wrote:
On Mon, 2005-01-31 at 00:06 -0500, Ron Watson wrote:
The W2k bootloader that comes up doesn't show anything but Win98 and Win2k for options. I can't figure out where they're storing this info, there doesn't seem to be BOOT.INI, it's not in the registry, duh. The only file in the whole system with the string "/fastdetect" is ntldr.
boot.ini is a hidden file in the root directory of the partition the bootloader is installed into, usually C:\
You'll need to turn on the option in Explorer to "View Hidden and System Files" to see it.
Did you look in the root directory of all of your drives?
You could also try starting notepad and opening C:\BOOT.INI by actually typing in the full name of the file in the file selection dialog, which would open the file even if it was hidden, as long as it's there of course.
Paul.
Just to point out that the first reply you had (see the bottom of this), told you exactly where it was c:\boot.ini and now that I've read your last, I'm wondering what the point of this gymnastic exercise was...
On Tue, 2005-02-01 at 22:18 -0500, Ron Watson wrote:
Yup, it wasn't on the W2k drive, it was on the master boot drive. C:\boot.ini but since the system does what I want it to, I'm going to leave well enough alone. Probably as a side effect of BootMagic, the master boot drive, which had been I:, is now where it should be, intuitively anyway, at C:
Ron;
Paul Howarth wrote:
On Mon, 2005-01-31 at 22:53 -0500, Ron Watson wrote:
Tried that, it still wasn't there. It's a mystery....
Ron;
Paul Howarth wrote:
On Mon, 2005-01-31 at 00:06 -0500, Ron Watson wrote:
The W2k bootloader that comes up doesn't show anything but Win98 and Win2k for options. I can't figure out where they're storing this info, there doesn't seem to be BOOT.INI, it's not in the registry, duh. The only file in the whole system with the string "/fastdetect" is ntldr.
boot.ini is a hidden file in the root directory of the partition the bootloader is installed into, usually C:\
You'll need to turn on the option in Explorer to "View Hidden and System Files" to see it.
Did you look in the root directory of all of your drives?
You could also try starting notepad and opening C:\BOOT.INI by actually typing in the full name of the file in the file selection dialog, which would open the file even if it was hidden, as long as it's there of course.
Paul.
-- === Ron Watson === rw@compukitty.com === Nisi potestatam dabis, non habebunt. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
On Mon, 2005-01-31 at 00:06 -0500, Ron Watson wrote:
My, my, where to start. It's been, as the Chinese might say, interesting. To summarize, I started with a Win2k/Win98 dual boot system, the Win2k on a SCSI drive, Win98 on IDE primary master, CD/DVD primary slave, a data drive on secondary master, and added a new drive as secondary master to use fo Linux. Trying the Core 3 CD's, anaconda crashed
I assume from you comments below you meant the new drive was secondary slave.
on assert failures trying to detect drive geometry and partitions. The Core 2 complained, but came up to DiskDruid, and I set up 20G /, 12G /home, 4G swap and installed it. I
10G is more than enough for / in most cases. 1G is a very large swap, the rest in /home would more closely fit what most people use.
My pc with 512mb ram almost never touches swap.
somewhat innocently let it put GRUB over top of the W2k boot loader on /hda, and after install, could not boot W2k/98 anymore. At this point I solicited advice here and received much cheerful and willing assistance, mainly these two (below)....
First, I tried restoring the W2k bootloader, successfully, on /hda, but could no longer get to Linux. So I did the dd and saved the first block, then went looking for BOOT.INI on the W2k system. Hmmm, there wasn't one. So I started looking on the net for info on where it might be, and found some pointers to Micro$oft support pages about it, which mentioned that 'ntldr' uses BOOT.INI to load NT(W2k), and went looking for ntldr, finding it in \WINNT\ServicePackFiles\i386, and dropped the file there and created a BOOT.INI with the incantation noted below. Nope, that didn't do it. Rummaging around, I discovered I have a PartitionMagic 6.0 CD I had never used, and thought maybe this might help. For starters, it noticed partition table irregularities on the Windows drives, and helpfully offered to fix them. That at least got the Core 3 install to stop crashing while examining drives.
<soapbox> Just as an aside, my own opinion is that assert() has no place in released code, as useful as it may be on occasion in development. ESPECIALLY in code looking at read/write storage that could be in any state. Speaking as a programmer, I take it as a given that there are NO impossible conditions. It's just defensive programming. If quantum theory can assign a nonzero probability to a black hole materializing over my CPU, making assumptions about the state of a disk is glibly optimistic, I think. </soapbox>
Anyway, PartitionMagic comes with BootMagic, their own boot loader. So I tried that, to no avail. I should mention here that the first sector of the drive (what dd captured) is apprently the drive geometry and partition table, so I'm thinking this probably wouldn't
first sector is boot sector.
work anyway. I found this out the hard way by dropping it onto the first sector of my /hdd
NEVER copy from disk to disk with dd unless the drives are exactly the same (brand, model, etc). dd is powerful and does a bit for bit copy and overwrites what is already there. You found this out the hard way.
In the scenario you were given, dd copies from disk to file which is OK. And back from that file to the same disk and same location would be OK. However disk to different disk is BAD.
Note, in the procedure below, I use the partition boot sector and not the drive boot sector. Thus I do not deal with geometry/partition table/ etc.
(Linux drive), and the system then thought it was an 8GB FAT32 drive and became horribly confused. I tried reconstructing my original partition table, without success. Core 3's anaconda went back to crash-n-burn, so I tried to see what PartitionMagic could do with it. It refused to touch the Linux drive, totally corrupted as it was. The Win2k drive manager was willing to delete the corrupt partition so I tried that. Sadly, I forgot that help from Redmond frequently has a high price, as I discovered it appears to have blown away the firmware on the CD/DVD on the secondary IDE channel that the Linux drive is on. Oopsie. Okay, it was a Samsung, and I wasn't all that happy with it anyway. Went down and got a new Plextor after I got an RMA for the Samsung. Put everything back together, Core 3 install came up ok, and installed Core 3. Updated to 2.6.10-1.741_FC3, and now trying to decide if Thunderbird needs to get blown away, but that's another story. THIS time, however, I had it put GRUB on the Linux boot drive (/hdd) instead of the master boot disk. Now at boot, the BootMagic comes up, offers Windows and Linux, and both actually work. Would this work with the normal W2k bootloader? I don't know, and since it works ok like this, I'll leave that as an exercise for the reader. :+) Probably not, since the W2k bootloader that comes up doesn't show anything but Win98 and Win2k for options. I can't figure out where they're storing this info, there doesn't seem to be BOOT.INI, it's not in the registry, duh. The only file in the whole system with the string "/fastdetect" is ntldr.
Ron;
Boot.ini is a hidden system file in W2K (usually c:\boot.ini) and can be edited with notepad or wordpad
The drive geometry errors that caused problems for the initial install were your real problem at the beginning.
Now those have been fixed you should be able to do a reinstall, put grub on the MBR of hda, and it should give you the option of configuring for booting the other installed OSes. It has always written a menu option in /boot/grub/grub.conf for me to chainload each windows OS installed.
Alternatively you can use the boot.ini modification to boot Linux from the win2K ntldr.
I have done this in the past, and it works easily. It used to be the only way to dual boot with NT4.0 and linux.
the steps are: ---------------------------------------------------------------------- 1. install linux. When installing specify the boot sector of the boot partition for placing the boot loader. (this should be the partition where you installed /boot) If the initial install does not allow putting the bootloader on the partition but forces it to the MBR, then within Linux, before you do step 2 you can do the following "grub-install /dev/hdd1" Which will write the boot loader to the boot sector of the partition before continuing with step 2.
2. use dd to create the file needed. I will assume you put /boot on /dev/hdd1, so the command will be "dd if=/dev/hdd1 of=linux.img bs=512 count=1"
3. Now put the file linux.img on c:\ of your win2k boot disk. This can be done in many ways, but I use a floppy or usb drive for that.
4. edit c:\boot.ini and add a line that reads Linux = c:\linux.img following the entries for win2k and win98
5. Boot from the win2k boot loader and it should provide the option to boot linux as well as windows and just work.
Ron Watson wrote:
Maxim Eremeev wrote:
Ron Watson wrote:
I just installed fedora 2, the fedora 3 anaconda would crash when it looked at my partitions, put in 2.6.9, then updated last night to 2.6.10.... I have fat32 and ntfs partitions, w98 and w2k installed but oopsie, i told it to put the boot loader on main disk and w2k won't load. tried to mount them and doesn't know about ntfs. How do I add ntfs support to kernel or restore the windoze boot loader to "C:"?
Well, it is relatively easy to restore the Win2K boot loader. You just need its installation disc, then you boot from it into recovery console and fixboot fixmbr should do the trick. However then you will need to reinstall your grub through recovery disc, and I suggest you to search through the posts here as the problem of dual (and even triple) boot was discussed several times. Good luck, Maxim.
Thanks, will make a recovery disk, test it, try to get w2k back up, get linux back up. As for ntfs support... went to /boot/config-2.6.10-1.9_FC2 and it says auto generated... auto generated by what? Noticed it does not set ntfs support, e.g.
# CONFIG_NTFS_FS is not set
so is it "safe" to add
CONFIG_NTFS_FS=y
to the config file, will it just get overwritten at next boot, or what?
Ron;
Actually, if you have your W2K installation CD you do not need to make any additional recovery disk - just boot from the CD and through several screens choose the recovery console (you have to remember the admin password, though). As for configuring the boot loader for the multiple boot I would suggest another decision (wasn't discussed, as far as I remember): 1. Now, as I can understand, you can boot just into Fedora and you have its boot loader installed onto hda. So boot it and in the terminal type something like: dd if=/dev/hda bs=512 count=1 of=/bootsect.lnx Note that I put hda here as you mentioned that BL was installed there. Move the file bootsect.lnx onto diskette. 2. Boot from W2K CD and do all this funny stuff with fixboot fixmbr 3. Now you should be able to load your W2K installation. Go there and find where the file boot.ini is located. Copy the bootsect.lnx to the same location. Normally it's just C:, but as you have Win98 it could be E:, D:\ or whatever where your W2K resides. Add the following line to boot.ini: %path to bootsect.lnx%="Fedora" (it could be D:\bootsect.lnx="Fedora" for example) 4. Restart and choose Fedora from the boot menu - see whether it does the trick.
It worked for me when I used FC1 on a dual boot machine - haven't tried it since that time, though, as I quitted all this multiple boot stuff. Any way you won't risk anything: in the worst case you'll just have to do what you'd do without those manipulations - boot from Fedora rescue disc and try to figure out how to make all your systems bootable. In the best case you will get the so much desired multiple boot system right away. Good luck (send me a feedback, if possible, as I wonder if this trick still can be useful :) ) Maxim.
-
cfk -
Craig White -
Jeff Vian -
Jonathan Berry -
Markku Kolkka -
Maxim Eremeev -
Paul Howarth -
Ron Watson