Which boot loader are you using: GRUB or lilo? If lilo, then (as root) edit /etc/lilo.conf and insert a windows option like this: other=/dev/hda1 label=Windows98 Then execute the command "/sbin/lilo -v" to update the bootloader
If GRUB then (as root) edit /boot/menu.lst to include a section like this: title Windows98 rootnoverify (hd0,0) makeactive chainloader +1 boot Now you should be able to boot into windows98. Good luck. Hendrik Schaink Nick W wrote: > Hi all, > > I recently put a 120GB drive in a P3-500, and was very happy to see the BIOS > correctly set the disk size. > > When I tried this setup: > > hda1- 15GB FAT32 for Win98 > hda4- extended partition > hda5- 1GB swap > hda6- Rest of drive ext3 for Suse 9.3 pro > > everything went well through the windows setup until I tried to reboot, I got > a disk I/O error. So I put Suse in, thinking maybe grub/lilo [I tried both] > would solve my problem, but no good. Suse boots perfectly, but Win98 gives a > disk I/O error. > > I had thought the Win98 partition had to be smaller than 137GB and a primary > partition and all should be fine. Anyone have any insight? > > Thanks, > Nick > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying -- Hendrik M. Schaink Chief Consultant "Integrated Business Solutions & Dependable Service" InfoVision Consulting Calgary, Alberta, Canada Phone: (403) 239-0099 "The Vision: We are the partners of choice for companies and organizations that share our commitment to creating a world that is truly wise, courageous, prosperous, innovative, inclusive, sustainable and humane." --Ruben Nelson GPG Fingerprint: 1371 0927 8C3C 831F A838 C312 68BC F5DB 010D F3D7 _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
