Then I notice 1mb of "unformatted space"... So I decide to expand the partition to fill it, because I told it to fill the drive dammit >_<
A small amount of space ending up outside your partitions is common. My Windows 7 install in VirtualBox has 9MB at of unformatted space at the end of the drive. Honestly not sure what's causing it. I have a couple guesses about where to look, but wasn't able to turn anything up quickly. It's generally not worth worrying about such a small amount of space on such a large disk.
Linux, telling you to do something via Windows? Epic fail.
Would you rather it just said "You're fucked. Nothing you can do"? I'm sorry nobody working on this piece of software for free has implemented the incredibly complicated thing that is a filesystem repair tool. Especially for a filesystem as undocumented as NTFS. At least it tried to tell you something to try.
Too bad surface mount parts are basically impossible to fix. ;_; Tricky, but not nearly impossible. Especially for something like a capacitor or
( ... )
Generally that happens when the drive partition isn't set to "ACTIVE", as in, a bootable system partition. Except, I already set it to ACTIVE.
A partition being marked "active" doesn't mean much. See wikipedia. The status field for a partition (which is what can mark the partition as active) is only there for use by the bootloader. The bootloader isn't part of the BIOS, it's whatever is stored at the very beginning of the hard drive (we already established this was GRUB). It's up to the bootloader to decide what the status flags mean, and if it cares.
Almost certainly, what you actually need(ed) to do is reinstall the windows bootloader in the MBR. You used to be able to do this from DOS/windows by running fdisk /mbr. Not sure if that's still the way to do it.
And, even though Kaya was formatted with HFS+ filesystem, and still full of data, data I hadn't had access to in years... Somehow both Linux and Windows saw it as unformatted for some reasonDifferent systems (PC and Macs
( ... )
I had already run fdisk /mbr. First step in a number of steps to rebuild the bootloader. It simply wouldn't work. Various steps kept failing, usually with an error "element not found".
And yeah, I did lose everything on Kaya, because it did create and install a 100mb partition on it the first time. Before I disconnected everything, beat it with a wet fish, and told it that it's grounded from playing with other children until it stops trying to force its religious views upon them.
Also, the current Windows partition manager really sucks. Gparted, with all it's little flaws here and there, is still the best I've ever used.
Also, the current Windows partition manager really sucks.
For extending a single partition like it sounded like you were trying to do, I expect it's more than adequate.
Gparted, with all it's little flaws here and there,
Have you reported these flaws? Software only gets better when the people working on it know what areas could be improved. Maybe they already know, but maybe they don't. If you have a bug or feature request, it goes here. I'm sure writing something up there nicely goes a lot more towards getting it fixed than bitching about it on a blog somewhere the developers will never see.
In other news, I realize I didn't post the wifi problems here because I ran across that issue the following day. So Nick has a Linksys PCI wifi adapter. It was tested working under Windows 7 on his computer. For logistical reasons, we stuck it in mine
( ... )
You should bitch about what the problem actually is. Your problem has nothing to do with wifi, and everything to do with shoddy or nonexistent drivers.
There are wifi devices with good drivers, and there are other types of hardware with the same driver problems. The two aren't particularly related.
Maybe not, but in my experience on all systems, wifi devices have been the largest sore spot when it comes to drivers. Are the drivers particularly hard to write compared to other devices, or are the manufacturers just lazier? Or have I just had a major run of bad luck with them?
Would you rather it just said "You're fucked. Nothing you can do"? I'm sorry nobody working on this piece of software for free has implemented the incredibly complicated thing that is a filesystem repair tool. Especially for a filesystem as undocumented as NTFS. At least it tried to tell you something to try.
Kind of, yeah. By telling you to use Windows to try and fix it, it implies that you have Windows available. Which might be a somewhat valid assumption seeing as the fs is NTFS, but it's still an assumption that won't always be true. And don't use the "It's free, so expect it not to work" line. That's a cop-out excuse FOSS devs use a lot that then gets re-used by anti-FOSS people as the reason FOSS will never be good, and it's all around a bad thing.
Tricky, but not nearly impossible. Especially for something like a capacitor or resistor, which are readily available parts.I could *possibly* do it given a soldering iron with a MUCH finer tip then the one I have, and even then I'd have to know what kind of cap it is. I guess
( ... )
By telling you to use Windows to try and fix it, it implies that you have Windows available.
Not really. It's telling you that there's a possibility that may work. Obviously if you don't windows you can't do it, but if it doesn't tell you, you might not think to try it even if you do have windows. Telling you it's an option hurts nothing. Not telling you does. I don't see why this is even a point of argument.
And don't use the "It's free, so expect it not to work" line. That's a cop-out excuse FOSS devs use a lot that then gets re-used by anti-FOSS people as the reason FOSS will never be good, and it's all around a bad thing.Bull fucking shit
( ... )
And don't use the "It's free, so expect it not to work" line. That's a cop-out excuse FOSS devs use a lot that then gets re-used by anti-FOSS people as the reason FOSS will never be good, and it's all around a bad thing.To clarify, my view isn't that FOSS isn't or can't be good. It's that as long as you don't contribute, you have no right to complain. FOSS only gets better when people contribute. When people sit back and complain (especially when they do it because they clearly think they're entitled to have everything they need developed by others for free), that does nothing to help make it better. If anything, it just works to burn out the developers, which is obviously counter-productive
( ... )
The website for gparted is http://gparted.sourceforge.net/index.php. Can you please point me to the part of the website that advertizes it "as the greatest thing since sliced bread, and specifically as good or better than the commercial alternative"? Can you tell me where it claims to "attempt to compete with for-profit products"?
If I write a piece of software and release it, and others hype it up, that's not my fault, and I don't deserve the bitching. And I'm not obligated to fulfill any implied promises someone completely unrelated to the project may have given.
With the major FOSS projects that have a sizable user-base, you have to work through the community as if it was a corporate ladder. You have to be around, get known, get respected, and then be ALLOWED to submit things.What gives you that impression
( ... )
A small amount of space ending up outside your partitions is common. My Windows 7 install in VirtualBox has 9MB at of unformatted space at the end of the drive. Honestly not sure what's causing it. I have a couple guesses about where to look, but wasn't able to turn anything up quickly. It's generally not worth worrying about such a small amount of space on such a large disk.
Linux, telling you to do something via Windows? Epic fail.
Would you rather it just said "You're fucked. Nothing you can do"? I'm sorry nobody working on this piece of software for free has implemented the incredibly complicated thing that is a filesystem repair tool. Especially for a filesystem as undocumented as NTFS. At least it tried to tell you something to try.
Too bad surface mount parts are basically impossible to fix. ;_; Tricky, but not nearly impossible. Especially for something like a capacitor or ( ... )
Reply
Generally that happens when the drive partition isn't set to "ACTIVE", as in, a bootable system partition. Except, I already set it to ACTIVE.
A partition being marked "active" doesn't mean much. See wikipedia. The status field for a partition (which is what can mark the partition as active) is only there for use by the bootloader. The bootloader isn't part of the BIOS, it's whatever is stored at the very beginning of the hard drive (we already established this was GRUB). It's up to the bootloader to decide what the status flags mean, and if it cares.
Almost certainly, what you actually need(ed) to do is reinstall the windows bootloader in the MBR. You used to be able to do this from DOS/windows by running fdisk /mbr. Not sure if that's still the way to do it.
And, even though Kaya was formatted with HFS+ filesystem, and still full of data, data I hadn't had access to in years... Somehow both Linux and Windows saw it as unformatted for some reasonDifferent systems (PC and Macs ( ... )
Reply
And yeah, I did lose everything on Kaya, because it did create and install a 100mb partition on it the first time. Before I disconnected everything, beat it with a wet fish, and told it that it's grounded from playing with other children until it stops trying to force its religious views upon them.
Also, the current Windows partition manager really sucks. Gparted, with all it's little flaws here and there, is still the best I've ever used.
Reply
For extending a single partition like it sounded like you were trying to do, I expect it's more than adequate.
Gparted, with all it's little flaws here and there,
Have you reported these flaws? Software only gets better when the people working on it know what areas could be improved. Maybe they already know, but maybe they don't. If you have a bug or feature request, it goes here. I'm sure writing something up there nicely goes a lot more towards getting it fixed than bitching about it on a blog somewhere the developers will never see.
Reply
Reply
There are wifi devices with good drivers, and there are other types of hardware with the same driver problems. The two aren't particularly related.
Reply
Reply
Kind of, yeah. By telling you to use Windows to try and fix it, it implies that you have Windows available. Which might be a somewhat valid assumption seeing as the fs is NTFS, but it's still an assumption that won't always be true. And don't use the "It's free, so expect it not to work" line. That's a cop-out excuse FOSS devs use a lot that then gets re-used by anti-FOSS people as the reason FOSS will never be good, and it's all around a bad thing.
Tricky, but not nearly impossible. Especially for something like a capacitor or resistor, which are readily available parts.I could *possibly* do it given a soldering iron with a MUCH finer tip then the one I have, and even then I'd have to know what kind of cap it is. I guess ( ... )
Reply
Not really. It's telling you that there's a possibility that may work. Obviously if you don't windows you can't do it, but if it doesn't tell you, you might not think to try it even if you do have windows. Telling you it's an option hurts nothing. Not telling you does. I don't see why this is even a point of argument.
And don't use the "It's free, so expect it not to work" line. That's a cop-out excuse FOSS devs use a lot that then gets re-used by anti-FOSS people as the reason FOSS will never be good, and it's all around a bad thing.Bull fucking shit ( ... )
Reply
Reply
Reply
If I write a piece of software and release it, and others hype it up, that's not my fault, and I don't deserve the bitching. And I'm not obligated to fulfill any implied promises someone completely unrelated to the project may have given.
With the major FOSS projects that have a sizable user-base, you have to work through the community as if it was a corporate ladder. You have to be around, get known, get respected, and then be ALLOWED to submit things.What gives you that impression ( ... )
Reply
Leave a comment