SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello, I have been searching here and Google for an answer to this but have not found an answer that works for me. I recently upgraded my WinXP partition to Win7 Enterprise 32-bit, installed without the 100MB system reserved partition. I always had LILO installed in the MBR with XP, but when LILO is in the MBR now Win7 fails to boot, just a blank screen with blinking cursor. Is the problem in my lilo.conf or the lack of the system partition or something else? As a workaround I have LILO on the Linux partition and using EasyBCD to add Slackware to the Windows boot menu, but I would like to boot to LILO again. Below is cfdisk of sda where Win7 and Slackware are installed, followed by my lilo.conf. Thanks in advance for any suggestions.
Disk Drive: /dev/sda
Size: 250059350016 bytes, 250.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 30401
Name Flags Part Type FS Type [Label] Size (MB)
Primary Free Space 1.05*
sda1 Boot Primary ntfs 42081.46*
Pri/Log Free Space 6.26*
sda5 Logical vfat 127903.11
sda6 Logical ext2 80067.49*
#Normal VGA mode
vga = 791
#vga = 872
#VESA framebuffer console mode 1024x768x256
# vga = 773
# End LILO global section
# Begin Linux OS entries
image = /boot/bzImage-3.12
label = Linux-3.12
append = "irqpoll"
image = /boot/vmlinuz
label = Linuz-3.10.17
append = "irqpoll"
# End Linux OS entries
# Begin Windows menu entry
other = /dev/sda1
label = Windows7
table = /dev/sda
# End Windows menu entry
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
When I did this some time ago, I had to fully install Win7 (with its defaults) then install Slackware (as with WinXP). Win7 seems to need that system partition no matter what. Dual-booting worked but other (Windows, of course) problems arose and I decided to abandon dual-booting completely. There may be a way to fix that missing partition, but, sorry, I don't know what it might be.
I wiped the drive clean, installed Slackware, installed VirtualBox and installed Win7 in that, with a 90-some GB partition for virtual machines to live in (Win7 really needs at least 20 GB to be useful, more is better, a separate drive for virtual machines is even better). Given that I don't have much use for Win7 (Stamps.com, Turbotax, Acrobat Reader, Firefox are the only things installed in it), I kept it about 30 GB virtual and left enough room for additional virtual machines. Oh, yeah, I did license Uniblue Registry CleanKit (Win7 has registry problems all the time); worth the $20 to not have problems.
That works. Lilo is a happy camper booting Slackware, life is good, VirtualBox starts up, Win7 loads and goes quickly (it takes about a minute to boot 64-bit Win7, YMMV), runs just fine, shuts down quickly, life is good.
From my experience with Win7, you really have to install and get it working first (in a sufficient-sized partition), then cut down the size of it to something reasonable, then install Slackware in the disk space you've freed from Windows' deadly grip. There's a utility in Win7 that you can use to reduce the size of the partition to make space for Slackware. Win7 eats three partitions, you can use logical partitions to install Slackware in a dual-boot system.
With the availability of VirtualBox (and other virtual systems), why bother with dual-booting? You can run large Win7 virtual machines, they run fine, no fuss, no muss.
No version of Windows needs that boot partition per se. It is only needed for special cases, for example if you use the BitLocker Drive Encryption to encrypt your Windows partition.
I dual boot with Windows 7 Ultimate 64 bit (without that boot partition) and have this entry in my lilo.conf:
other = /dev/sda1
label = Windows
table = /dev/sda
Since you have laready restored your MBR to the Windows bootloader I would just try it again and see if it works now.
Thank you all for the informative replies. Win7 Enterprise is working perfectly without the system partition. I will try LILO again, as TobiSGD suggests, and hope it works. And maybe without the 'table =' line as in enorbet's example.
tronayne, I do use VirtualBox and have had a Win7 vm for a while. That is how I became comfortable with it enough to replace XP. I need to keep a Win installation for a few games, some student stuff and sharing the pc.
If all else fails I can continue using my EasyBCD setup. lol
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Originally Posted by DaiWu Bonsai
I was under the impression system-reserved was needed for expanding start-up files and MS Recovery Environment.
Just to avoid any misunderstandings, while OEMs that pre-install windows often create a recovery environment to avoid both shipping optical media and tech calls, this is not the same as the one often created by simply installing Win 7 from such media onto a hard drive. With sufficient backups even the OEM one can be deleted but it would void your warranty, if that matters. There is no penalty for either not creating one or removing one (properly) from a self installed system.
I just reinstalled my lilo to mbr and everything is working well now. I left out the 'table = /dev/sda' line, not sure if that makes any difference ... probably not. When selecting Windows from lilo, it booted to the menu I had setup using EasyBCD. I then edited the bcd menu, removing the Slackware entry and disabling the timer/wait, so now it boots straight into Windows. Makes me wonder if somehow using EasyBCD repaired a missing or damaged config. Anyhow, my lilo + Slackware + Win7 is working properly now. Thank you all.