Date: Fri, 11 Feb 2000 12:11:44 +0100 From: Abercromby James TSgt 31CS/SCBBMA <James.Abercromby@aviano.af.mil> To: "'freebsd-questions@FreeBSD.org'" <freebsd-questions@FreeBSD.org>, "'freebsd-newbies@FreeBSD.org'" <freebsd-newbies@FreeBSD.org> Subject: RE: Dual Booting Win98 and FreeBSD 2 sep. HDs-Continued Message-ID: <78944D1EBF2BD3119DBF0008C75DEDFF0301BA@avo-exch-l3.aviano.af.mil>
next in thread | raw e-mail | index | archive | help
All, I also tried one last ditch attempt and method to get it installed. I also have FreeBSD Ver. 3.3 on CD so I threw in the first boot disk and rebooted went into the install program fine finished the filesystem, and boom brought up the emergency holographic shell and it initialized the installation media fine, but then it acted alittle shady because I was using the 3.4 boot disks and sig11ed again. What is this? Is it a hardrive, bios, or cdrom problem or what? Should I go out and buy a different CD drive? -----Original Message----- From: Abercromby James TSgt 31CS/SCBBMA Sent: Friday, February 11, 2000 7:01 AM To: 'Peter Schwenk'; 'freebsd-questions@FreeBSD.org'; 'freebsd-newbies@FreeBSD.org' Subject: RE: Dual Booting Win98 and FreeBSD 2 sep. HDs-Continued Importance: High Peter, After I got your last email I tried to go to the FIC site to see if they had any new bios upgrades for the AMI BIOS on this ol' FIC PA-2011. NOT. SO, I went ahead and did what you said/suggested. I just selected boot mgr for the 1.2gid wd0 running win98 and did not select bootmgr for wd1 17.2 maxtor. Same thing. Also, on a side note, since I couldn't find a damn bios upgrade, I stupidly ran that maxtor hd prep software. BAD MOVE - wiped out the MBR on the win98 drive. Anyway- again over and over again trying to install. I finally have come this conclusion-I think? The FreeBSD install has no problems with the drives anyway, BECAUSE it finishes writing the file systems. And I get the message stating "All filesystems have been written successfully" FOLLOWING MAYBE 30 Secs after this is when it fails. First. It spawns the Emergency VTY holographic shell (or trys to so it says) Then this is where it goes to try to initialize the CD (hi-val 40x=Kenwood CDROM). Sometimes it will actually fail and say that FreeBSD couldn't initialize the installation media itself. Other occasions it will just immediately sig11. I even clean the CD with a cd cleaner-no luck. NOTE: That during the initial load of the kernel it finds the exact model number of the cdrom with 0 problems, but it's wierd. Sometimes during kernel load it sees cd in the drive and other times it will just say unknown media. So.... I am going crazy pretty much. Maybe FreeBSD doesn't like it! I installed Slackware in like 20 minutes with no problems after my failed attempt at FREEBSD again. Plus Win98 didn't have any problems either. I am really losing it/sleep also. Later Jim PS. Everyone in the lists and Peter also thanks for your continued support and help, I WILL GET IT INSTALLED. -----Original Message----- From: Peter Schwenk [mailto:schwenk@math.udel.edu] Sent: Thursday, February 10, 2000 8:23 PM To: Abercromby James TSgt 31CS/SCBBMA; avi890k1@pn.nettuno.it Subject: Re: Dual Booting Win98 and FreeBSD 2 sep. HDs-Continued Hmm. I guess I'm kinda stumped at this point. I have a couple questions though. Why did you make two slices on the 17GB drive? If you are dedicating the whole disk to FreeBSD, then you only need to make one slice (aka. Microsoft-terminology: partition). Then within that one slice you make FreeBSD partitions (at least one for / and one for swap, possibly one each for /usr, /var, /home, but this is up to you and your admin style). You don't need to mess with the MBR of the second disk or any of the boot blocks of the slices on the second disk. Booteasy only goes on the first disk. After telling you all this, there's really nothing that you seem to have done that should cause a crash like you describe. But if I were you, I'd try once again and make only one slice on the second disk and not put anything in the MBR or boot blocks of the second disk. Also you can see error messages on the other virtual terminals sometimes that are helpful when there's a problem. I think the first four (ALT-F1 through ALT-F4) are used during the install, so check them out, too. Abercromby James TSgt 31CS/SCBBMA wrote: > > Peter, > > Please send your reply to avi890k1@pn.nettuno.it > I wasn't using the "Custom" install option. I was using the NOVICE options > exclusively. > > BTW: DId you see this part of my post? > > - Fdisk for wd0 leave it alone press Q > > -- Select the BootMGR for wd0 > > 2- Fdisk for wd1-Create 2 slices for FreeBSD > > wd1s1-8000M/wd1s2-8400M > > -- Select the BootMGR also for wd1 (is this what I am doing > wrong?) -- PETER SCHWENK | UNIX System Administrator Department of Mathematical Sciences | University of Delaware schwenk@math.udel.edu | (302)831-0437 <-NEW!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78944D1EBF2BD3119DBF0008C75DEDFF0301BA>