Dual booting, upgrading M$
Hi folks! I have been happily dual-booting SuSE 8.0 and Win98 for quite awhile now, booting from a SuSE LILO floppy. But I now need to install WinXP Pro for work. I'd like to do this with a minimum of fuss, but I need some advice. Will it be possible to just blow away my current Win98 partition, keep it the same size and install XP without it doing anything to the Linux partitions? Will I have to re-make the boot floppy, and if so, would I need to boot from the SuSE DVD (that isn't a problem)? Is there anything else I need to plan for (aside from backing everything up, which is my plan anyway)? All tips and suggestions greatly appreciated. Many thanks! Mike McCallister
Hi folks!
I have been happily dual-booting SuSE 8.0 and Win98 for quite awhile now, booting from a SuSE LILO floppy. But I now need to install WinXP Pro for work. I'd like to do this with a minimum of fuss, but I need some advice.
Will it be possible to just blow away my current Win98 partition, keep it the same size and install XP without it doing anything to the Linux partitions? If its big enough for XP. I would give 3GB minumum to XP (unless you can store
Will I have to re-make the boot floppy, and if so, would I need to boot from the SuSE DVD (that isn't a problem)? Unfortuantly Windows will NUKE lilo, grub and whatever other boot loader is
On Friday 23 May 2003 02:51 pm, Mike McCallister wrote: programs and other data elsewhere also). Just be very careful not to touch your linux partitions. I would recommend 5-7GB to it, but in your case I wouldn't try to resize the drive beyond what 98 was using. By default Windows will ask about 6 times if you want to delete a partition. Just make sure to delete the old 98 one and format the new one over it as NTFS. As a BARE minumum, i think 1 GIG can squeeze by....but not by much. there. It shouldnt be a problem to boot from DVD or floppy and re-install lilo or grub, esp. if you already have a working configuration. If you were already dual-booting to 98, then you should have a working configuration to boot into XP esp. if you install OVER the old partition. I see no problems with using what you already have with no modifications.
Is there anything else I need to plan for (aside from backing everything up, which is my plan anyway)? I can't think of anything else. I dual boot on my laptop 8.2 and XP Professional. I've tried to do this on my desktop, but a secondary master IDE disk along with LILO on a SCSI chain makes this VERY complicated. I never was able to do a mixed SCSI/IDE boot.
---------------------- Eric Bambach Eric@CISU.net ----------------------
One minor point: If you wish to mount the XP partition under linux,
you'll need to format the partition as FAT32, not NTFS. If you
don't wish to mount the Windoze partition under linux, then NTFS is
probably the better choice.
Cheers,
--Joe :-)
--- Eric
On Friday 23 May 2003 02:51 pm, Mike McCallister wrote:
[ snip ]
If its big enough for XP. I would give 3GB minumum to XP (unless you can store programs and other data elsewhere also). Just be very careful not to touch your linux partitions. I would recommend 5-7GB to it, but in your case I wouldn't try to resize the drive beyond what 98 was using. By default Windows will ask about 6 times if you want to delete a partition. Just make sure to delete the old 98 one and format the new one over it as NTFS. As a BARE minumum, i think 1 GIG can squeeze by....but not by much.
[ snip ] __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
On 05/24/2003 03:51 AM, Mike McCallister wrote:
I have been happily dual-booting SuSE 8.0 and Win98 for quite awhile now, booting from a SuSE LILO floppy. But I now need to install WinXP Pro for work. I'd like to do this with a minimum of fuss, but I need some advice.
I did almost the exact same thing about a month ago.
Will it be possible to just blow away my current Win98 partition, keep it the same size and install XP without it doing anything to the Linux partitions?
Yes, assuming it is big enough.
Will I have to re-make the boot floppy, and if so, would I need to boot from the SuSE DVD (that isn't a problem)?
You can just boot from the 8.0 DVD, boot installed system, write lilo to the MBR (which will be replaced by XP install), and you may be done, if you install as FAT32 (same as win98). If you format as NTFS, you would need to change fstab.
Is there anything else I need to plan for (aside from backing everything up, which is my plan anyway)?
The install that I did was on a fairly fresh 8.0 install, so I did not back up, and I had no problems. I installed XP with FAT32 so that I could use that partition rw from both OSes. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On Friday 23 May 2003 22:24, Joe Morris (NTM) wrote to Mike McCallister who wanted to "upgrade" from Win98 to WinXP on a dual-boot (with SuSE):
You can just boot from the 8.0 DVD, boot installed system, write lilo to the MBR (which will be replaced by XP install), and you may be done, if you install as FAT32 (same as win98). If you format as NTFS, you would need to change fstab.
If you have lotsa room, you might consider formatting a large partition NTFS and a small one FAT. Others can correct me on this, if XP handles things differently, but I'm given to understand that it was/is OK for Linux to *read* files on NTFS partitions, but that NT became unhappy if Linux were to *write* to such a file. But Linux writing to files on FAT partitions caused no problem. So if you wanted to trade files back and forth a lot, you still gave Windows a big NTFS playground, but you used the small FAT partition for "sharing"/copying files between the OSes. I had this arrangement when I dual-booted between NT or 2000 and SuSE 8.x, and it worked fine for OpenOffice files that I was constantly passing back and forth. Again, if XP doesn't have the earlier problem, then there's no need for this workaround. Anybody? /kevin
On Fri, 23 May 2003, Kevin McLauchlan wrote:
I'm given to understand that it was/is OK for Linux to *read* files on NTFS partitions, but that NT became unhappy if Linux were to *write* to such a file.
There are two completely different NTFS drivers for Linux. The old one (version 1.x.y) is included in the official 2.4 kernels but completely abandoned by NTFS developers. It has write support only for NT4 and it can indeed damage NT4 data if one enabled write. However write is totally disabled for Windows XP/2003/2000 NTFS filesystems. In short, nobody can damage data on the later Windows partitions because it's impossible to mount the partition read-write, the driver falls back to read-only mode supposed one uses one of the latest stable kernels. The new, rewritten (version 2.x.y) NTFS driver is included in the 2.5 series development kernels and also has a backported version for the latest 2.4 stable kernel. What's its benefit? + Stable: no known problems in the implemented functionality, it's also multi-processor and reentrant safe. + Supports all NTFS cluster sizes from 512 bytes up to 64 kB. The old one is limited to maximum 4 kB cluster size. + Full support for sparse and compressed files also on Windows XP/2003/2000. + Supports mmap() thus Wine users can start applications from an NTFS partition. + One can setup a loopback device on an NTFS file. TopologiLinux uses this feature to run completely from a Windows NTFS partition (read-write). This is a frequently asked feature by Knoppix users but Knoppix can't do it because it uses the old driver. + Still read-only, but with safe file overwrite support on all Windows versions without changes to the file size. TopologiLinux also heavily uses this feature. + Much better performance. What NTFS driver Linux distributions use? This is what we know about: + New driver: Mandrake, SuSE, Gentoo, ASPLinux, TopologiLinux, Phat Linux. + Old driver: Debian, Knoppix, Slackware. + No driver: Red Hat. If one has comments, problems with the _new_ driver, please let us know at linux-ntfs-dev@lists.sf.net, no subscription is required. Project page is at http://linux-ntfs.sourceforge.net/ Thanks, Szaka
Thanks to all for their advice. I'm feeling much better, and will only format C for NTFS. Mike On Saturday 24 May 2003 4:08 am, Szakacsits Szabolcs wrote:
On Fri, 23 May 2003, Kevin McLauchlan wrote:
I'm given to understand that it was/is OK for Linux to *read* files on NTFS partitions, but that NT became unhappy if Linux were to *write* to such a file.
There are two completely different NTFS drivers for Linux.
The old one (version 1.x.y) is included in the official 2.4 kernels but completely abandoned by NTFS developers. It has write support only for NT4 and it can indeed damage NT4 data if one enabled write. However write is totally disabled for Windows XP/2003/2000 NTFS filesystems. In short, nobody can damage data on the later Windows partitions because it's impossible to mount the partition read-write, the driver falls back to read-only mode supposed one uses one of the latest stable kernels.
The new, rewritten (version 2.x.y) NTFS driver is included in the 2.5 series development kernels and also has a backported version for the latest 2.4 stable kernel. What's its benefit?
+ Stable: no known problems in the implemented functionality, it's also multi-processor and reentrant safe.
+ Supports all NTFS cluster sizes from 512 bytes up to 64 kB. The old one is limited to maximum 4 kB cluster size.
+ Full support for sparse and compressed files also on Windows XP/2003/2000.
+ Supports mmap() thus Wine users can start applications from an NTFS partition.
+ One can setup a loopback device on an NTFS file. TopologiLinux uses this feature to run completely from a Windows NTFS partition (read-write). This is a frequently asked feature by Knoppix users but Knoppix can't do it because it uses the old driver.
+ Still read-only, but with safe file overwrite support on all Windows versions without changes to the file size. TopologiLinux also heavily uses this feature.
+ Much better performance.
What NTFS driver Linux distributions use? This is what we know about:
+ New driver: Mandrake, SuSE, Gentoo, ASPLinux, TopologiLinux, Phat Linux.
+ Old driver: Debian, Knoppix, Slackware.
+ No driver: Red Hat.
If one has comments, problems with the _new_ driver, please let us know at linux-ntfs-dev@lists.sf.net, no subscription is required. Project page is at http://linux-ntfs.sourceforge.net/ Thanks,
Szaka
-- Mike McCallister "The fundamental obligation of a revolutionary New Berlin, WI is to tell the truth; workingwriter@prodigy.net the other is to always carry a pen." Notes from the Metaverse: http://radio.weblogs.com/0124049
On Tue, 27 May 2003, Mike McCallister wrote:
Thanks to all for their advice. I'm feeling much better, and will only format C for NTFS.
Sorry Mike, apparently I was unambiguous. The best way is indeed what others also recommended. I always agreed with that: one big NTFS and another smaller FAT32 for data exchange what both Windows and Linux can _fully_ read and write. The _new_ NTFS driver is still limited in write functionality, e.g. no file/directory creation, deletion, append, only file overwrite however that works safely, at least we didn't get any corruption reports. Hope I could clarify and sorry for the confusion, Szaka
On Saturday 24 May 2003 4:08 am, Szakacsits Szabolcs wrote:
On Fri, 23 May 2003, Kevin McLauchlan wrote:
I'm given to understand that it was/is OK for Linux to *read* files on NTFS partitions, but that NT became unhappy if Linux were to *write* to such a file.
There are two completely different NTFS drivers for Linux.
The old one (version 1.x.y) is included in the official 2.4 kernels but completely abandoned by NTFS developers. It has write support only for NT4 and it can indeed damage NT4 data if one enabled write. However write is totally disabled for Windows XP/2003/2000 NTFS filesystems. In short, nobody can damage data on the later Windows partitions because it's impossible to mount the partition read-write, the driver falls back to read-only mode supposed one uses one of the latest stable kernels.
The new, rewritten (version 2.x.y) NTFS driver is included in the 2.5 series development kernels and also has a backported version for the latest 2.4 stable kernel. What's its benefit?
+ Stable: no known problems in the implemented functionality, it's also multi-processor and reentrant safe.
+ Supports all NTFS cluster sizes from 512 bytes up to 64 kB. The old one is limited to maximum 4 kB cluster size.
+ Full support for sparse and compressed files also on Windows XP/2003/2000.
+ Supports mmap() thus Wine users can start applications from an NTFS partition.
+ One can setup a loopback device on an NTFS file. TopologiLinux uses this feature to run completely from a Windows NTFS partition (read-write). This is a frequently asked feature by Knoppix users but Knoppix can't do it because it uses the old driver.
+ Still read-only, but with safe file overwrite support on all Windows versions without changes to the file size. TopologiLinux also heavily uses this feature.
+ Much better performance.
What NTFS driver Linux distributions use? This is what we know about:
+ New driver: Mandrake, SuSE, Gentoo, ASPLinux, TopologiLinux, Phat Linux.
+ Old driver: Debian, Knoppix, Slackware.
+ No driver: Red Hat.
If one has comments, problems with the _new_ driver, please let us know at linux-ntfs-dev@lists.sf.net, no subscription is required. Project page is at http://linux-ntfs.sourceforge.net/ Thanks,
Szaka
--
participants (6)
-
Eric
-
Joe Buczek
-
Joe Morris (NTM)
-
Kevin McLauchlan
-
Mike McCallister
-
Szakacsits Szabolcs