![](https://seccdn.libravatar.org/avatar/7cd6a3c991e28fb7210f7d038810c6e1.jpg?s=120&d=mm&r=g)
Since I am in the process of installing both Win2K and SuSE 7.0 Pro on a Ibm Thinkpad A21p, I might give some tips. I added some comments in the middle of your text: --On Sunday, January 07, 2001 09:03:08 PM +0100 Radule Soskic <rms@telekom.yu> wrote:
1. I cut one half of 20Gb Win2K partition with fips and installed SuSE, but had some problems with lilo and "1024 sector limit". Obviously, my 9Gb were too far from the begining of the disk to keep lilo pleased. I am new to Win2K, and also I read some "not-so-clear-to-me (being newbee)" instructions in the manual about coexistence of NT and Linux (lilo) - not a word on Win2K, so I finally (rather early) switched from Win2K to
I have no problem using Lilo to boot both Linux and Win2K on a 32GB hard drive, but I had to replace the version of Lilo that was on the SuSE disks with a newer one: ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/lilo-21.6-9.i386.rpm This is how my lilo.conf looks like: boot = /dev/hda vga = normal read-only prompt timeout = 100 message = /boot/message lba32 image = /boot/vmlinuz label = linux root = /dev/hda7 initrd = /boot/initrd image = /boot/vmlinuz.suse label = suse root = /dev/hda7 initrd = /boot/initrd.suse other = /dev/hda1 label = win2k table = /dev/hda Notes: 1. The lba32 is very important to solve the 1024 sector limit. 2. In my case /dev/hda7 is where my / is. 3. /dev/hda1 is where Win2K is installed (an NTFS partition). 4. For Win2k I created two partitions, NTFS and (a small) FAT32. The NTFS is accessed from Linux in read only mode while the FAT32 is mounted R/W by Linux so I can use it to transfer files between the two OS.
office" (previously it was "almost everythinng"). 4. Now I had more success. My system was up and running (running in a broad sense of the word) In fact, here's the list of what wasn't running: - Sound system was not found (ESS Maestro PCI Audio)
Did you try Elsa via YAST2? I found it to very good at detecting sound cards.
- Network was not found (3com 10/100 Mini PCI Ethernet) - Modem was not found (3com 56K V.90 Mini PCI)
Ah, this is going to be a problem. I have the same combo in my laptop. First lets start with the modem: its a Winmodem so unless 3COM decides to write linmodem drivers for it, forget about using it from Linux. Now for the Ethernet: there are apparently drivers around for it but the version I need is available only for kernel 2.2.17+. As I understand it, current versions of the kernel support it out of the box. For more information check: http://mobilix.org/minipci_linux.html
- Graphics was only able to work in 1024x768. I tried all the possibilities - no success! (whereas in Win it shows excellent 1400x1050) My ATI Rage Mobility-M1 AGP was simply not on the list... 5. At the end, I was prepared to stick on 1024x768 because it really was clean and nicely working, even though the screen of 15" XGA deserved better. If only I could fix the rest of problems. But, nothing nice happened to
You are luck here, since SAX/SAX2 locked my machine solid. This is something I am still trying to get working. I think I am on the right path to get it to work though.
defunct... 8. To conclude, even my new lilo refused to install. Sorry - I can not recall the reason any more. It just was the part of the night
Did you try to install it with the --nodeps or --force options? Avi -- Avi Schwartz Get a Life avi@CFFtechnologies.com Get Linux!