From: Chris Landauer <cal@rushe.aero.org> To: freebsd-questions@freebsd.org Cc: cal@rushe.aero.org, kstewart@owt.com Subject: thanx for dual boot help, problem not yet solved Message-ID: <200203012210.g21MAwX15686@rushe.aero.org>
next in thread | raw e-mail | index | archive | help
hihi - thanx to all (especially kent) for your quick responses about dual booting - and yes, i know, rtfm (and i did) - i started by assuming that the problem was on the w2k pro side, and was looking for successful experiences with dual-booting freebsd and w2k pro from different disks, since i did all the proper things on the freebsd 4.5 install side (i've been installing dual boot systems since freebsd 2.1.5 or 2.2.8 or something like that, and with windows 95, 98 and windows me, beos and several versions of suse and red hat linux distributions - this was the first one i tried with w2k pro) the first problem was that none of the dos programs that come with the 4.5 cds would run on this windows system (includign fbsdboot.exe and all the others) - when i try to run them, the system complains about the program accessing the hard drive directly, and apparently the programs are not actually able to do so - so i couldn't rearrange the partitions the way i wanted to under windows (even with a dos boot disk) - that is why i separated the two disks, one for windows and one for freebsd - i wrote a new partition table on the freebsd disk (from the install program), and installed freebsd 4.5 with lotsa packages (as i usually do) the original problem was that the freebsd install worked in the usual and expected way, but apparently did not write the appropriate boot information onto the disks (this is why i thought the problem was with windows) after your messages, i looked, but i couldn't find anything about boot.ini in the freebsd handbook (i hadn't remembered that name from anything i read before in the handbook, and the search process doesn't seem to find that file name in the top 30 or 40 pages of search results from the freebsd site), so knowing about that name will be helpful for later actually, i just checked and there doesn't seem to be any boot.ini file on my windows machine either, according to the search function - in any case, i always make all of my hidden files visible by default, but i didn't see an option not to search for hidden files, so i assume that if the file were there, then the windows search would have found it (the system is windows 2000 professional, which is apparently some kind of nt-based system, even though it says that it has fat32 file systems on the disks, as i had requested from the manufacturer, dell) - i will start by assuming that there is some default behavior in case such a file is not there, and that putting one there will supersede that default it sounds like its windows homework time 8-( well, if it turns out to be too hard or too annoying, i know i can just junk w2k entirely, and install one of my old w98 systems - the only reason i don't have w98 on this machine already as it came from dell is that there is 1GB of main memory and i was told that w98 can't use more than 512MB - oh, well more later, cal Dr. Christopher Landauer Aerospace Integration Science Center The Aerospace Corporation, Mail Stop M6/214 P.O.Box 92957 Los Angeles, California 90009-2957, USA e-mail: cal@aero.org, Phone: +1 (310) 336-1361 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?200203012210.g21MAwX15686>