Ghost is a _VERY SIMPLE PROGRAM_ that only understands 1) sectors 2) partitions... and.... that's it.
So anyone who claims ghost is re-encoding firmware, or using different error correction, or changing "cluster sizes" OR WHATEVER.
Just stop. Stop. Ghost can't do any of that. 1) That stuff is complicated 2) Ghost would be like 40 floppies to handle all the different combinations of things if it could. 3) They'd advertise all that AS FEATURES because it'd probably cost someone a lot of money to develop all that shit.
It's fake. The guy made an idiot mistake, and Ghost just makes an overlapping partition for it's own benefit. Big deal.
YOU'RE ALL GULLIBLE IDIOTS. Get back to me once you understand how hard drives work.
So did you have to wait 10 hours while it took over the firmware in the drive, re-encoded all the domains, and then only worked with a very _specific_ partition map?
is done inside the hard drive itself, and a firmware flash won't help you. They have specialized chips that (among other things) encode your data 32-bits at a time into magnetic domains or what have you... and they do it "at the last minute". So you can't get more space that way, sorry.
the entire chip is "scale-free" which means it is designed to work at a variety of speeds and tolerances.
HOWEVER! The manufacturing process is much more of a crap shoot. You have to grow this perfect layer of silicon in the shape of a disc (usually it's cut from a cylinder), and grind it to be incredibly smooth. It has to be perfect. Then you expose it to one chemical, then light which reacts with it, then you expose it to another chemical to leave behind something where the light hit. And you do this over, and over again to deposit layers of different dopants to the chip to build it's structure. Except if the tiniest bit of dust, or particle gets in the way, that whole chip is ruined. And you can't make it in a vacuum, so you have to have filtered air. But even then, you can't filter perfectly, so you have some loss. And even then, the wafer is not guaranteed to be 100% flat all over to within a nanometer (whereas the chip components themselves are only 130-90nm these days) so there is going to be some chips whose parts are better lined up or formed more evenly than others, overall. So you make about 200 or so on a wafer, then cut them apart and test them, to see which ones work, and how well they do.
It's the manufacturing that makes the cost-competetive tradeoffs...
You make an a new partition covering the whole drive, and then Norton instructs itself to back THAT up to another drive using the same code that it uses to back up any other single partition.
So they use the same backup code for ghosting a single partition or whole disk by using a little partition mangling before the reboot.
but I remember ALWAYS having trouble with floppy disks. It's just that back then (early 90s) there was nothing else, so it didn't seem so bad. So you carried them around in protective boxes, and you made two copies if it was REALLY important (and never deleted the original).
Even if you have three file systems sharing the same space, you still can't store more than the new, magic E: drive, total. This is because the new partition is the size of the WHOLE disk that the system can directly address.
So if you had an 80GB disk, you still can't store more than 80GB of stuff, and now you've got a FUCKED set of partitions and file system tables.
Okay, here's the thing. If you're familiar with Solaris, you'll know that the 2nd "slice" of your disk is always set to map to all the visible sectors of the disk. This is used for backup purposes. So all you'd have to do is tell your backup software to copy the "#2" slice of your disk to tape, and you get all the other partitions at the same time!
But if you add up the total size of all your slices, it'll be way beyond the reported capacity, twice the capacity, at least, since the 2nd slice will be, by defintion, as big as all the others combined.
Ghost2003 must be creating a parition that's the size of the whole disk that covers all the other ones for the purpose of copying it to the target disk. This way it can get all of them at once using simple BIOS calls dealing with only "one" partition (which happens to save the data from all of them). That explains why it's an unlabeled partition that's roughly the size of the whole disk, thus doubling the capacity, and it only appears right before you do the backup after a reboot (and it disappears later).
This makes a lot of sense from a programming perspective.
But it's totally useless, because if you try to format it, it'll format into the special VSGHOST partition. So it'll "work" if you do a quick format. But let's say you had a D: drive too. If you WRITE in the new E:, and thenit walks over parts of the disk that may be occupied by the D: drive, YOU'RE SCREWED.
So effectively you gain nothing, except a huge headache down the road. You can't store more than the capacity. You can be tricky and try to have two, or even three filesystems share the same sector space, but then, why would you do that? It'll work, until you step all over yourself and all your filesystems are hosed.
That being said, there is an element of truth to what you are saying too. But I'll never rush out to buy a monitor just so I can shove the old one in a landfill. It's full of particularly toxic parts, and I'd rather not.
I even keep all my old motherboards.
I'm saving up $500 for an iHP-400
on
Real's Reality
·
· Score: 1
Just for that very reason. Get every format under the sun. And there is a gain in sound quality at the same bitrate, but I wouldn't expect you to know what things like "noise floor" and "spectral flattening + DCT vs. filter banks" means... so I'll skip the technical discussion and just assert that the OGGs I make sound better than the MP3s I labouriously made of CDs and they took up 40% less space, so I felt like a JACKASS having done all the work previously to only throw it all away, because I knew I'd never be able to stand it after the third listen.
MP3 is a dead technology. Use it only when you have a hardware decoder and you're forced to use it, because vorbis is superior in every way (including computational complexity during decode).
It's not about being different, it's about knowing a good thing when you see it, and supporting it. HOW THE FUCK CAN IT BECOME DEFACTO IF NO ONE DARES TO USE IT?
Well I dare goddamn it, and I double dare you.
If no one did that, then we'd be using MP3s with it's dumb-ass channel coupling for fucking EVER, not moving on.
primarily merit based, and almost all the big schools participate.
And the thing is he didn't really need the assistance, but he won it anyway, and that must mean something, because they just don't give those things away.
If you wanted to find streams for WinAMP...
on
Real's Reality
·
· Score: 1
The article is essentially a sham. I've seen more than enough AC comments in response that claim that Andrew Kirch is nothing more than a lowly script kiddie (trelane of sigdie). While there is some truth to what he's saying, he's putting it in a light which makes it seem all more impressive (because he was a part of it).
Is he distancing himself from it, or just trying to get more attention? I don't know.
But take it all with a large grain of salt. Your own experiences with kiddi3s (if they differ, and according to some other comments they do) - are probably more accurate.
where they mention that "no one wants to download grsecurity" or "tru64 is where it's at" or "some kiddies target Solaris and Irix because that usually means a big pipe".
You set up a user called "name_of_uncooperative_program", then put them in the Administrators group, but then go into the security policy editor and prevent that user from logging in interactively (but give it "logon as service").
Then make a batch file that calls "su.exe" using -s to login as a serivce as that account (with password in tow), with the command set to the path to the program.
Set the batch file executable by users, and readable by no one (owned by administrator). Make a shortcut to the program on your desktop or whatever.
Ghost is a _VERY SIMPLE PROGRAM_ that only understands 1) sectors 2) partitions... and .... that's it.
So anyone who claims ghost is re-encoding firmware, or using different error correction, or changing "cluster sizes" OR WHATEVER.
Just stop. Stop. Ghost can't do any of that. 1) That stuff is complicated 2) Ghost would be like 40 floppies to handle all the different combinations of things if it could. 3) They'd advertise all that AS FEATURES because it'd probably cost someone a lot of money to develop all that shit.
It's fake. The guy made an idiot mistake, and Ghost just makes an overlapping partition for it's own benefit. Big deal.
YOU'RE ALL GULLIBLE IDIOTS. Get back to me once you understand how hard drives work.
You put a lot of faith in Norton Ghost...
So did you have to wait 10 hours while it took over the firmware in the drive, re-encoded all the domains, and then only worked with a very _specific_ partition map?
Some people...
So no, that's not it.
Their slogan is truncated. It should be...
"You've got questions, we've got answers, but not neccessarily the right ones, just anything to get you to buy something and another battery charger."
Really. They are NEVER any help. You can learn more from the printed catalogues and via inference than from the sales monkeys.
where now you just send SCSI-like block commands, and the drive does all the work.
Sigh.
is done inside the hard drive itself, and a firmware flash won't help you. They have specialized chips that (among other things) encode your data 32-bits at a time into magnetic domains or what have you... and they do it "at the last minute". So you can't get more space that way, sorry.
the entire chip is "scale-free" which means it is designed to work at a variety of speeds and tolerances.
HOWEVER! The manufacturing process is much more of a crap shoot. You have to grow this perfect layer of silicon in the shape of a disc (usually it's cut from a cylinder), and grind it to be incredibly smooth. It has to be perfect. Then you expose it to one chemical, then light which reacts with it, then you expose it to another chemical to leave behind something where the light hit. And you do this over, and over again to deposit layers of different dopants to the chip to build it's structure.
Except if the tiniest bit of dust, or particle gets in the way, that whole chip is ruined. And you can't make it in a vacuum, so you have to have filtered air. But even then, you can't filter perfectly, so you have some loss.
And even then, the wafer is not guaranteed to be 100% flat all over to within a nanometer (whereas the chip components themselves are only 130-90nm these days) so there is going to be some chips whose parts are better lined up or formed more evenly than others, overall.
So you make about 200 or so on a wafer, then cut them apart and test them, to see which ones work, and how well they do.
It's the manufacturing that makes the cost-competetive tradeoffs...
I've had about 85-95% success rate for about as long as I can remember.
It hasn't gotten any worse, as far as I can tell. I mean, use them as boot floppies all the time, without issue. Maybe you're just unlucky?
You make an a new partition covering the whole drive, and then Norton instructs itself to back THAT up to another drive using the same code that it uses to back up any other single partition.
So they use the same backup code for ghosting a single partition or whole disk by using a little partition mangling before the reboot.
Makes sense to me.
but I remember ALWAYS having trouble with floppy disks. It's just that back then (early 90s) there was nothing else, so it didn't seem so bad. So you carried them around in protective boxes, and you made two copies if it was REALLY important (and never deleted the original).
Nowadays they are totally unacceptable.
Even if you have three file systems sharing the same space, you still can't store more than the new, magic E: drive, total. This is because the new partition is the size of the WHOLE disk that the system can directly address.
So if you had an 80GB disk, you still can't store more than 80GB of stuff, and now you've got a FUCKED set of partitions and file system tables.
Any Norton engineers want to back me up on this?
Okay, here's the thing. If you're familiar with Solaris, you'll know that the 2nd "slice" of your disk is always set to map to all the visible sectors of the disk. This is used for backup purposes. So all you'd have to do is tell your backup software to copy the "#2" slice of your disk to tape, and you get all the other partitions at the same time!
But if you add up the total size of all your slices, it'll be way beyond the reported capacity, twice the capacity, at least, since the 2nd slice will be, by defintion, as big as all the others combined.
Ghost2003 must be creating a parition that's the size of the whole disk that covers all the other ones for the purpose of copying it to the target disk. This way it can get all of them at once using simple BIOS calls dealing with only "one" partition (which happens to save the data from all of them). That explains why it's an unlabeled partition that's roughly the size of the whole disk, thus doubling the capacity, and it only appears right before you do the backup after a reboot (and it disappears later).
This makes a lot of sense from a programming perspective.
But it's totally useless, because if you try to format it, it'll format into the special VSGHOST partition. So it'll "work" if you do a quick format.
But let's say you had a D: drive too.
If you WRITE in the new E:, and thenit walks over parts of the disk that may be occupied by the D: drive, YOU'RE SCREWED.
So effectively you gain nothing, except a huge headache down the road. You can't store more than the capacity. You can be tricky and try to have two, or even three filesystems share the same sector space, but then, why would you do that? It'll work, until you step all over yourself and all your filesystems are hosed.
Give me the handheld rail gun. You'll never get a shot off, and half the time you're looking for ammo.
Why use an axe when you can have a bad-ass sword of legends?
...even the LCDs.
That being said, there is an element of truth to what you are saying too. But I'll never rush out to buy a monitor just so I can shove the old one in a landfill. It's full of particularly toxic parts, and I'd rather not.
I even keep all my old motherboards.
Just for that very reason. Get every format under the sun.
And there is a gain in sound quality at the same bitrate, but I wouldn't expect you to know what things like "noise floor" and "spectral flattening + DCT vs. filter banks" means... so I'll skip the technical discussion and just assert that the OGGs I make sound better than the MP3s I labouriously made of CDs and they took up 40% less space, so I felt like a JACKASS having done all the work previously to only throw it all away, because I knew I'd never be able to stand it after the third listen.
MP3 is a dead technology. Use it only when you have a hardware decoder and you're forced to use it, because vorbis is superior in every way (including computational complexity during decode).
It's not about being different, it's about knowing a good thing when you see it, and supporting it. HOW THE FUCK CAN IT BECOME DEFACTO IF NO ONE DARES TO USE IT?
Well I dare goddamn it, and I double dare you.
If no one did that, then we'd be using MP3s with it's dumb-ass channel coupling for fucking EVER, not moving on.
Who the hell are you talking about? I'm talking about Bill Clinton, father, W.J. Blythe, who was not a politician in the remotest sense.
primarily merit based, and almost all the big schools participate.
And the thing is he didn't really need the assistance, but he won it anyway, and that must mean something, because they just don't give those things away.
... you should have scooted on over to The ShoutCAST Yellow Pages
... have you... come on, admit it.
Pansy.
Ooooh, vorbis, sounds scary. I bet MP3 was scary too the first time you tried to fire up BladeENC you anal monkey.
ID3 tags, WHATS THAT??!?!?!!
Seriously, vorbis is idiot-stupid to create and sounds as good as AAC without the licensing. So eat a dick my friend.
The article is essentially a sham. I've seen more than enough AC comments in response that claim that Andrew Kirch is nothing more than a lowly script kiddie (trelane of sigdie). While there is some truth to what he's saying, he's putting it in a light which makes it seem all more impressive (because he was a part of it).
Is he distancing himself from it, or just trying to get more attention? I don't know.
But take it all with a large grain of salt. Your own experiences with kiddi3s (if they differ, and according to some other comments they do) - are probably more accurate.
I don't like the CAN-SPAM act at all.
BUT... it is somewhat satisfying to use it against them, ridding the Internet of another vaccous marketing firm, regardless of the circumstances.
In an ideal world, my upstream mail relay would reject all email that wasn't signed, and I'd have all my friends keys on my keyring.
But I will have to settle for this...
I mean, does anyone cry if a slashdot troll dies? I know I wouldn't.
where they mention that "no one wants to download grsecurity" or "tru64 is where it's at" or "some kiddies target Solaris and Irix because that usually means a big pipe".
Try a little reading comprehension first.
You set up a user called "name_of_uncooperative_program", then put them in the Administrators group, but then go into the security policy editor and prevent that user from logging in interactively (but give it "logon as service").
Then make a batch file that calls "su.exe" using -s to login as a serivce as that account (with password in tow), with the command set to the path to the program.
Set the batch file executable by users, and readable by no one (owned by administrator). Make a shortcut to the program on your desktop or whatever.
Easy!