Bug 44831 - After installing Linux, NT crashes
Summary: After installing Linux, NT crashes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-18 06:30 UTC by Ved Singh
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-06-20 03:56:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Ved Singh 2001-06-18 06:30:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0; netcompass)

Description of problem:


How reproducible:
Always

Steps to Reproduce:
1.Have a windows NT installation in primary partition(c: FAT16)
2.Install Linux. Choose to partition the available space
3.Now boot through NT
	

Actual Results:  NT crashes

Expected Results:  Nt should have come up.

Additional info:

Comment 1 Michael Schwendt 2001-06-18 16:01:13 UTC
Any hdd/partition layout details available? Where did you install LILO? What
type of crash? When exactly?

Comment 2 Ved Singh 2001-06-19 05:24:01 UTC
I have 20 GB HDD.
/dev/hda1 - (2.1GB) FAT partition where NT is installed.
/dev/hda2 - (8 GB) FAT partition
Rest around 9 GB remain unpartitioned.  I installed Linux on this unpartitioned space. Created following partitions - /, /boot, /home,/usr,/usr/local, /var, 
/tmp.
At the LILO configuration step - chose Skip LILO configuration and created a boot diskette.
After that , I am able to boot through the boot floppy.
Now , when I boot without floppy, the machine boots trhough NT and when it reaches, blue screen of OS loading, it crashes there.

Comment 3 Brent Fox 2001-06-19 15:35:52 UTC
I can't explain why this would happen.  The installer doesn't write anything at
all to the FAT partitions.  I haven't seen this happen before, and we test
dual-booting pretty regularly.

Comment 4 Ved Singh 2001-06-20 03:55:36 UTC
Actually, the problem was bacause of NT service packs. You need to have at 
least service pack 3. Thank you all for your efforts.


Note You need to log in before you can comment on or make changes to this bug.