Re: [FreeBSD] 6.3-R diskhandling
Gerard wrote: There have been several articles written describing how to install Vista after installing another OS. You could start with this one, or Google for others. http://apcmag.com/5045/how_to_dual_boot_vista_with_linux That probably works with the retail versions of Vista, but the OEM version that came with my laptop removes all partitions on the disk, period. Thinking of it, it might be that this is not Microsoft's fault, but that of the laptop manufacturer for making such a braindamaged installer. This thread is getting off-topic... Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
On Sun, 27 Jan 2008 14:22:21 + "Alphons \"Fonz\" van Werven" <[EMAIL PROTECTED]> wrote: [ snip ] > I believe that in Redmond you'll find some people who disagree with > you... I can't re-install Vista here without it wiping the entire > disk. Older versions of DOS/Windows merely overwrote the MBR, > something that wasn't right either, but at least it could be fixed. > Vista doesn't seem willing to share at all. There have been several articles written describing how to install Vista after installing another OS. You could start with this one, or Google for others. http://apcmag.com/5045/how_to_dual_boot_vista_with_linux I ran across a Microsoft KB article describing how to accomplish it also; but for the life of me, I cannot find it again. If I feel ambitious at some future point, I might re-investigate it. BTW, from what I have read, Vista does not have to be on the primary partition any longer. It simply needs to be on the active one to boot. I have not investigated that however. -- Gerard [EMAIL PROTECTED] QOTD: "Sure, I turned down a drink once. Didn't understand the question." signature.asc Description: PGP signature
Re: [FreeBSD] 6.3-R diskhandling
Gerard wrote: Come to think of it, does sysinstall keep a copy of the MBR as it was before the installation? I checked and it doesn't seem to be the case. Might be worth a PR? No OS, irregardless of whether it is a *.nix *.BSD or Microsoft Windows should overwrite or disable another OS or it's files, period, unless the user so configures the new installation to do so. I believe that in Redmond you'll find some people who disagree with you... I can't re-install Vista here without it wiping the entire disk. Older versions of DOS/Windows merely overwrote the MBR, something that wasn't right either, but at least it could be fixed. Vista doesn't seem willing to share at all. Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
On Sun, 27 Jan 2008 13:07:59 + "Alphons \"Fonz\" van Werven" <[EMAIL PROTECTED]> wrote: > Chuck Swiger wrote: > > [Bootloader overwrites Vista's "UID" in the MBR] > > > This has been informative-- perhaps someone ought to file a PR > > about having the installer try to preserve this UID in the MBR...? > > Or perhaps send a message to -hackers. > > I have been using FreeBSD for a long time so I wanted to have this > fixed somehow (and it has been). But I can imagine it might scare away > people who are new to FreeBSD: "What a bonehead system, it hosed my > Windows. I'll never use that crap again!" > > Come to think of it, does sysinstall keep a copy of the MBR as it was > before the installation? That way, at least people can get their > precious little Windows (yuck) back without having to reinstall it. > If it doesn't, I think it would be a very desirable feature. No OS, irregardless of whether it is a *.nix *.BSD or Microsoft Windows should overwrite or disable another OS or it's files, period, unless the user so configures the new installation to do so. -- Gerard [EMAIL PROTECTED] Lysistrata had a good idea. signature.asc Description: PGP signature
Re: [FreeBSD] 6.3-R diskhandling
Chuck Swiger wrote: [Bootloader overwrites Vista's "UID" in the MBR] This has been informative-- perhaps someone ought to file a PR about having the installer try to preserve this UID in the MBR...? Or perhaps send a message to -hackers. I have been using FreeBSD for a long time so I wanted to have this fixed somehow (and it has been). But I can imagine it might scare away people who are new to FreeBSD: "What a bonehead system, it hosed my Windows. I'll never use that crap again!" Come to think of it, does sysinstall keep a copy of the MBR as it was before the installation? That way, at least people can get their precious little Windows (yuck) back without having to reinstall it. If it doesn't, I think it would be a very desirable feature. Just a thought (or two), Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
Alphons "Fonz" van Werven wrote: Ghirai wrote: This article might help: http://www.clearchain.com/wiki/FreeBSD_%26_Windows_Vista Okay, thanks for the link. I was not aware of that. However, I do think there's more to it than that. After all, Slackware was able to install LILO without any problems whatsoever. Both Vista and Linux would boot just fine. This has been informative-- perhaps someone ought to file a PR about having the installer try to preserve this UID in the MBR...? - [ cue link to somewhat related thread "Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1" ...in the freebsd-stable mailing list... ] Gah. :-) I'm facing a similar situation coming up, as one of my machines has a: Model Family: Maxtor MaXLine Plus II Device Model: Maxtor 7Y250M0 Serial Number:Y65V3WKE Firmware Version: YAR51HW0 User Capacity:251,000,193,024 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0 Local Time is:Sat Jan 26 19:50:00 2008 EST SMART support is: Available - device has SMART capability. Enabled status cached by OS, trying SMART RETURN STATUS cmd. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 118) The previous self-test completed having the read element of the test failed. [ after a long self-test: ^^^ bad ^^^ ] Total time to complete Offline data collection: ( 363) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 107) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE 3 Spin_Up_Time0x0027 180 180 063Pre-fail Always -24027 4 Start_Stop_Count0x0032 253 253 000Old_age Always -430 5 Reallocated_Sector_Ct 0x0033 217 217 063Pre-fail Always -373 6 Read_Channel_Margin 0x0001 253 253 100Pre-fail Offline -0 7 Seek_Error_Rate 0x000a 253 252 000Old_age Always -0 8 Seek_Time_Performance 0x0027 249 244 187Pre-fail Always -46905 9 Power_On_Minutes0x0032 240 240 000Old_age Always -362h+29m 10 Spin_Retry_Count0x002b 253 252 157Pre-fail Always -0 11 Calibration_Retry_Count 0x002b 253 252 223Pre-fail Always -0 12 Power_Cycle_Count 0x0032 253 253 000Old_age Always -253 192 Power-Off_Retract_Count 0x0032 253 253 000Old_age Always -0 193 Load_Cycle_Count0x0032 253 253 000Old_age Always -0 194 Temperature_Celsius 0x0032 253 253 000Old_age Always -36 195 Hardware_ECC_Recovered 0x000a 253 252 000Old_age Always -2950 196 Reallocated_Event_Count 0x0008 252 252 000Old_age Offline -1 197 Current_Pending_Sector 0x0008 217 217 000Old_age Offline -364 198 Offline_Uncorrectable 0x0008 252 252 000Old_age Offline -1 199 UDMA_CRC_Error_Count0x0008 199 198 000Old_age Offline -1 200 Multi_Zone_Error_Rate 0x000a 253 252 000Old_age Always -0 201 Soft_Read_Error_Rate0x000a 253 252 000Old_age Always -8 20
Re: [FreeBSD] 6.3-R diskhandling
Alphons "Fonz" van Werven wrote: Manolis Kiagias wrote: then download and install the EasyBCD That too seems a solution worth considering. I'll think about it. Thanks! Alphons May I add I used this successfully on a number of occasions, including my current laptop. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
Manolis Kiagias wrote: then download and install the EasyBCD That too seems a solution worth considering. I'll think about it. Thanks! Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
Ghirai wrote: This article might help: http://www.clearchain.com/wiki/FreeBSD_%26_Windows_Vista Okay, thanks for the link. I was not aware of that. However, I do think there's more to it than that. After all, Slackware was able to install LILO without any problems whatsoever. Both Vista and Linux would boot just fine. Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
Manolis Kiagias wrote: Alphons "Fonz" van Werven wrote: Hi, I have a recent model Toshiba laptop here, dual-booting Windows Vista and Slackware Linux (not my call, so no flames please). When I got the go-ahead to replace Linux with FreeBSD 6.3-RELEASE, the following happened: The partitioner complained that the found geometry 232581/16/63 is invalid and it's using a more likely geometry instead. Closer inspection reveals that this "more likely" geom (14593/255/63) is actually the real geometry, so question 1 is: where did FreeBSD get this other weird-ass geometry from? When installing the boot manager, it hosed Windows' bootability. I could mount and access the Windows partition from within FreeBSD just fine so the partition itself seemed to be okay, but it just wouldn't boot. When I selected it in the bootmanager menu, it showed a screen saying Windows can't boot and I should use the recovery disk to repair Windows. Since everything on the machine that was even remotely important had just been backed up and Windows was due for a reinstall anyway, I just reinstalled it and no harm was done, but I still wonder what happened. How come FreeBSD's boot manager stopped Windows from booting? The reinstall of Windows wiped away everything else, so I can retry installing FreeBSD. But given the troubles described above, what's the best way to do it? Currently, I'm considering the following: 1. Boot this Live Linux CD I have lying around here and which finds the correct geometry for the disk right away. 2. Make a backup of the MBR. 3. Create a partition (slice) for FreeBSD. 4. Boot the FreeBSD install disk and run through sysinstall (partitioning the slice Linux just created) but don't let it install a boot loader. 5. Boot the Live Linux again and install LILO from there. But if you have any other suggestions I'm all ears of course. Oh, and a final question: the Windows installer creates a partition table in which partitions (slices) don't end on cylinder/track boundaries. Is this a big deal? Linux notices it but doesn't seem bothered much by it and FreeBSD appears to act likewise. But I thought I'd better ask, just to be sure. Thanks in advance, Alphons When installing FreeBSD and you are asked what boot manager to install select to not install anything. In this way your Vista boot will not be affected. If after this you find that at startup you are not given ANY choice but FreeBSD starts automatically, this is simply because it's partition is marked active. Boot with a CD like Norton Partition Magic or GParted and mark the Vista partition active. Boot Vista, then download and install the EasyBCD from www.neowin.net It is then trivial to add a stanza to Vista bootloader (!) to boot FreeBSD. Sorry the correct link is: http://neosmart.net/dl.php?id=1 Manolis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
Alphons "Fonz" van Werven wrote: Hi, I have a recent model Toshiba laptop here, dual-booting Windows Vista and Slackware Linux (not my call, so no flames please). When I got the go-ahead to replace Linux with FreeBSD 6.3-RELEASE, the following happened: The partitioner complained that the found geometry 232581/16/63 is invalid and it's using a more likely geometry instead. Closer inspection reveals that this "more likely" geom (14593/255/63) is actually the real geometry, so question 1 is: where did FreeBSD get this other weird-ass geometry from? When installing the boot manager, it hosed Windows' bootability. I could mount and access the Windows partition from within FreeBSD just fine so the partition itself seemed to be okay, but it just wouldn't boot. When I selected it in the bootmanager menu, it showed a screen saying Windows can't boot and I should use the recovery disk to repair Windows. Since everything on the machine that was even remotely important had just been backed up and Windows was due for a reinstall anyway, I just reinstalled it and no harm was done, but I still wonder what happened. How come FreeBSD's boot manager stopped Windows from booting? The reinstall of Windows wiped away everything else, so I can retry installing FreeBSD. But given the troubles described above, what's the best way to do it? Currently, I'm considering the following: 1. Boot this Live Linux CD I have lying around here and which finds the correct geometry for the disk right away. 2. Make a backup of the MBR. 3. Create a partition (slice) for FreeBSD. 4. Boot the FreeBSD install disk and run through sysinstall (partitioning the slice Linux just created) but don't let it install a boot loader. 5. Boot the Live Linux again and install LILO from there. But if you have any other suggestions I'm all ears of course. Oh, and a final question: the Windows installer creates a partition table in which partitions (slices) don't end on cylinder/track boundaries. Is this a big deal? Linux notices it but doesn't seem bothered much by it and FreeBSD appears to act likewise. But I thought I'd better ask, just to be sure. Thanks in advance, Alphons When installing FreeBSD and you are asked what boot manager to install select to not install anything. In this way your Vista boot will not be affected. If after this you find that at startup you are not given ANY choice but FreeBSD starts automatically, this is simply because it's partition is marked active. Boot with a CD like Norton Partition Magic or GParted and mark the Vista partition active. Boot Vista, then download and install the EasyBCD from www.neowin.net It is then trivial to add a stanza to Vista bootloader (!) to boot FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] 6.3-R diskhandling
On Sat, 26 Jan 2008 13:55:26 + "Alphons \"Fonz\" van Werven" <[EMAIL PROTECTED]> wrote: > Hi, > > I have a recent model Toshiba laptop here, dual-booting Windows Vista and > Slackware Linux (not my call, so no flames please). When I got the > go-ahead to replace Linux with FreeBSD 6.3-RELEASE, the following > happened: > > The partitioner complained that the found geometry 232581/16/63 is invalid > and it's using a more likely geometry instead. Closer inspection reveals > that this "more likely" geom (14593/255/63) is actually the real geometry, > so question 1 is: where did FreeBSD get this other weird-ass geometry > from? > > When installing the boot manager, it hosed Windows' bootability. I could > mount and access the Windows partition from within FreeBSD just fine so > the partition itself seemed to be okay, but it just wouldn't boot. When I > selected it in the bootmanager menu, it showed a screen saying Windows > can't boot and I should use the recovery disk to repair Windows. Since > everything on the machine that was even remotely important had just been > backed up and Windows was due for a reinstall anyway, I just reinstalled > it and no harm was done, but I still wonder what happened. How come > FreeBSD's boot manager stopped Windows from booting? > > The reinstall of Windows wiped away everything else, so I can retry > installing FreeBSD. But given the troubles described above, what's the > best way to do it? Currently, I'm considering the following: > 1. Boot this Live Linux CD I have lying around here and which finds the > correct geometry for the disk right away. > 2. Make a backup of the MBR. > 3. Create a partition (slice) for FreeBSD. > 4. Boot the FreeBSD install disk and run through sysinstall (partitioning > the slice Linux just created) but don't let it install a boot loader. > 5. Boot the Live Linux again and install LILO from there. > But if you have any other suggestions I'm all ears of course. > > Oh, and a final question: the Windows installer creates a partition table > in which partitions (slices) don't end on cylinder/track boundaries. Is > this a big deal? Linux notices it but doesn't seem bothered much by it and > FreeBSD appears to act likewise. But I thought I'd better ask, just to be > sure. > > Thanks in advance, > > Alphons > This article might help: http://www.clearchain.com/wiki/FreeBSD_%26_Windows_Vista -- Regards, Ghirai. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[FreeBSD] 6.3-R diskhandling
Hi, I have a recent model Toshiba laptop here, dual-booting Windows Vista and Slackware Linux (not my call, so no flames please). When I got the go-ahead to replace Linux with FreeBSD 6.3-RELEASE, the following happened: The partitioner complained that the found geometry 232581/16/63 is invalid and it's using a more likely geometry instead. Closer inspection reveals that this "more likely" geom (14593/255/63) is actually the real geometry, so question 1 is: where did FreeBSD get this other weird-ass geometry from? When installing the boot manager, it hosed Windows' bootability. I could mount and access the Windows partition from within FreeBSD just fine so the partition itself seemed to be okay, but it just wouldn't boot. When I selected it in the bootmanager menu, it showed a screen saying Windows can't boot and I should use the recovery disk to repair Windows. Since everything on the machine that was even remotely important had just been backed up and Windows was due for a reinstall anyway, I just reinstalled it and no harm was done, but I still wonder what happened. How come FreeBSD's boot manager stopped Windows from booting? The reinstall of Windows wiped away everything else, so I can retry installing FreeBSD. But given the troubles described above, what's the best way to do it? Currently, I'm considering the following: 1. Boot this Live Linux CD I have lying around here and which finds the correct geometry for the disk right away. 2. Make a backup of the MBR. 3. Create a partition (slice) for FreeBSD. 4. Boot the FreeBSD install disk and run through sysinstall (partitioning the slice Linux just created) but don't let it install a boot loader. 5. Boot the Live Linux again and install LILO from there. But if you have any other suggestions I'm all ears of course. Oh, and a final question: the Windows installer creates a partition table in which partitions (slices) don't end on cylinder/track boundaries. Is this a big deal? Linux notices it but doesn't seem bothered much by it and FreeBSD appears to act likewise. But I thought I'd better ask, just to be sure. Thanks in advance, Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
