Hi,

I have not had a problem with Win/7 and other installs. As long as you perform or setup things properly then no issues. I did use the Win/7 tools to re-size and move partitions to allow a Slackware LEET Install (13.37) on available space with extended partition and logical partitions within for my install.

Works!

So did I. (Actually, I used Slackware's fdisk because of problems I had with Vista's partition tools in the past).

Like I said, it worked fine on one laptop (compaq) but not on my emachines PC and the only obvious difference between the two was the order in which the Windows 7 partitions were set up. Obviously, I could have re-ordered the partitions but it seemed like too much effort for too little results (not to mention that I left <100GB for the Windows 7 partition which might not be enough).

The only time I need to use windows is if I need to do my taxes on-line or run some commercial accounting software. (I prefer "hledger" when in Slackware and avoid the more sophisticated packages if I can). Windows XP is more than adequate for such needs and when you have 2GB of memory, it runs almost as fast as Linux.

Hi,

Really, Win7 should perform within the 100GB allocation. I still have units with WinXp installed to support clients that still use that OS. As for using native tools for M$, I have less problems when using the tools provided for Win7 & WinVista.

For Win7 I just align the partitions with sufficient allocations. Recovery partition size is not adjusted but moved to align partition boundaries. All three partitions for Win7 are contiguous with space allocations, partition2 is around 40GB which is more than enough for operations. External Data drives provide extension for music & other system needs.

I find Slackware to be crisp and responsive as compared the Xp. Xp is used to support clients that run that OS, find it to be no better than before on older hardware. Since the hardware comparisons are apple to oranges. Not everyone has WinXP Pro-64bit! I really did not care for WinXp-Pro 64bit, too costly.
Most of my boots are dual with either Win7 & Slackware or WinVista & Slackware.

What can I say except that my experiences have been the opposite of yours.

On my PC the "C DRIVE" was the third partition so nothing fancy was required - just shrink the partition (even Windows 7 could handle that). Yet once I ran lilo Window$ would only boot in recovery mode. liloconfig picked up the first partition as the one to be booted off even though the C_DRIVE was the third (and the bootable) partition. Of course, editing lilo.conf to fix up that error didn't work.

All in all, it proved to be too much trouble for something I might only use a couple of times per year. I prefer WinXP anyhow.

On the laptop, the C_DRIVE was the first partition which meant a lot more partition juggling. Having shrunk the C_DRIVE, I then had to move the other partitions to the end of the C_DRIVE before creating an extended partition for my linux partitions. I wasn't prepared to trust Window$ with this task but slackware's fdisk did it all without blinking. The dual setup worked exactly how it is supposed to.

Slackware is still the superior system but at least WinXP runs fast enough so that I don't get frustrated waiting (not so with Vista or Win7).